Your message dated Wed, 9 May 2012 00:19:29 +0200
with message-id <20120508221929.GA8212@yellowpig>
and subject line Re: [Popcon-developers] Bug#635673: popcon won't run
consistently on machines that sleep at night
has caused the Debian Bug report #635673,
regarding popcon won't run consistently on machines that sleep at night
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.)
--
635673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635673
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: popularity-contest
Version: trunk
As configured in Debian, popularity-contest can miss sending reports.
The day parameter specifies a day, but it is possible that a particular
machine will be consistently asleep at that time. For example a machine
in a 9-5 Monday-Friday office. Even if anacron is in place to run the
script, the given DAY may have already passed.
A mixture of anacron and a change to the DAY="X" parameter would solve
this, ensuring some randomness in the reporting, but not skipping out
hearing from some classes of machines.
--- End Message ---
--- Begin Message ---
On Thu, Jul 28, 2011 at 10:44:13AM +0200, Bill Allombert wrote:
> On Wed, Jul 27, 2011 at 06:39:05PM -0700, Bryce Nesbitt wrote:
> > Package: popularity-contest
> > Version: trunk
> >
> > As configured in Debian, popularity-contest can miss sending
> > reports. The day parameter specifies a day, but it is possible that
> > a particular machine will be consistently asleep at that time. For
> > example a machine in a 9-5 Monday-Friday office. Even if anacron is
> > in place to run the script, the given DAY may have already passed.
> >
> > A mixture of anacron and a change to the DAY="X" parameter would
> > solve this, ensuring some randomness in the reporting, but not
> > skipping out hearing from some classes of machines.
>
> Hello Bryce,
> You are reporting this bug against the trunk. Please explain why the fix for
> #610876 which was released in 1.52 does not adress your concern.
Hello, you did not reply, so I have to assume that they were addressed.
Thanks for your interest in popularity-contest,
--
Bill. <[email protected]>
Imagine a large red swirl here.
--- End Message ---
