Subject: apticron: At least avoid hard-coding 2:32 (or 1:32) as the
time at which to run
Package: apticron
Version: 1.1.42
Severity: normal
*** Please type your report below this line ***
I got <quote>
Date: Sun, 27 Mar 2011 03:00:03 +0200
From: r...@vortex.getinternet.no (Cron Daemon)
To: r...@vortex.getinternet.no
Subject: Cron <root@vortex> test -x /usr/sbin/apticron &&
/usr/sbin/apticron --cron
Content-Type: text/plain; charset=ISO-8859-15
date: invalid date `2:32'
date: invalid date `@'
touch: invalid date format `'
</quote> and inspection of /etc/cron.d/apticron revealed that 2:32 is
indeed the time hard-coded for the script to run. This is a bad choice
of time because once per year it doesn't exist (as above) and once per
year it happens twice in the same night. Here in Norway, the time
switch happens between two and three am (I'm sure that's how it used to
be in Britain, too, although the report above indicates someone
experiencing it between one and two; perhaps Britain has changed its DST
habits). Fixed locally by changing the time to 3:42, but it would be
better fixed in the package.
-- System Information:
Debian Release: 6.0.1
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Versions of packages apticron depends on:
ii apt 0.8.10.3 Advanced front-end for dpkg
ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent
ii cron 3.0pl1-116 process scheduling daemon
ii debconf [debconf-2 1.5.36.1 Debian configuration
management sy
ii mailx 1:20071201-3 Transitional package for
mailx ren
ii ucf 3.0025+nmu1 Update Configuration
File: preserv
Versions of packages apticron recommends:
ii apt-listchanges 2.85.7 package change history
notificatio
ii iproute 20100519-3 networking and traffic
control too
apticron suggests no packages.
-- debconf information:
apticron/notification: root
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
