Your message dated Sat, 17 Feb 2018 00:22:47 +0100
with message-id <20180216232247.GA19974@yellowpig>
and subject line Re: Bug#867056: popularity-contest: debconf prompt on upgrade
to stretch
has caused the Debian Bug report #867056,
regarding popularity-contest: debconf prompt on upgrade to stretch
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
867056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867056
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: popularity-contest
Version: 1.64
Severity: serious
Upon upgrading hosts from jessie to stretch I get the popcon prompt
about whether to participate. That should only be shown on initial
install, not for subsequent upgrades.
Cheers,
Julien
--- End Message ---
--- Begin Message ---
On Mon, Jul 03, 2017 at 09:53:34PM +0200, Julien Cristau wrote:
> On Mon, Jul 3, 2017 at 20:55:57 +0200, Bill Allombert wrote:
>
> > On Mon, Jul 03, 2017 at 08:41:06PM +0200, Julien Cristau wrote:
> > > Control: severity -1 minor
> > >
> > > On Mon, Jul 3, 2017 at 20:03:41 +0200, Julien Cristau wrote:
> > >
> > > > Upon upgrading hosts from jessie to stretch I get the popcon prompt
> > > > about whether to participate. That should only be shown on initial
> > > > install, not for subsequent upgrades.
> > > >
> > > Apparently this is due to us creating /etc/popularity-contest.conf
> > > through puppet, possibly before the package is installed, so the prompt
> > > is (from debconf's perspective) unseen.
> >
> > Why not use debconf preseeding as recommended and let popcon postinst
> > generate /etc/popularity-contest.conf ?
> >
> preseeding is a terrible way to manage configurations.
As long as you set distinct random MY_HOSTID for all the host, this is
your call (alas I see lots of MY_HOSTID reuse).
But I do not think the package behaviour is incorrect. You could also
use puppet to mark the question as seen by debconf.
Closing this report,
Cheers,
--
Bill. <[email protected]>
Imagine a large red swirl here.
--- End Message ---
