Your message dated Thu, 23 Nov 2006 06:47:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#399827: fixed in cron-apt 0.4.10
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: cron-apt
Version: 0.4.9
Severity: normal
Hi,
on systems with a long sources.list, servers unreachable and cron-apt
being invoked often, it is possible that a new cron-apt is started
while the old one is still running. In this case, the new cron-apt
terminates with a message that it cannot acquire the cron-apt log. So
far, so good.
At this time, $TMPDIR/initlog was already created, but onexit()
doesn't zap $TMPDIR/initlog, and thus the rmdir $TMPDIR in onexit()
fails ("Directory not empty"). This error message is delivered by cron
in an extra mail message.
Greetings
Marc
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.3-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages cron-apt depends on:
ii apt 0.6.46.3 Advanced front-end for dpkg
ii debianutils 2.17.3 Miscellaneous utilities specific t
Versions of packages cron-apt recommends:
ii liblockfile1 1.06.1 NFS-safe locking library, includes
ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cron-apt
Source-Version: 0.4.10
We believe that the bug you reported is fixed in the latest version of
cron-apt, which is due to be installed in the Debian FTP archive:
cron-apt_0.4.10.dsc
to pool/main/c/cron-apt/cron-apt_0.4.10.dsc
cron-apt_0.4.10.tar.gz
to pool/main/c/cron-apt/cron-apt_0.4.10.tar.gz
cron-apt_0.4.10_all.deb
to pool/main/c/cron-apt/cron-apt_0.4.10_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ola Lundqvist <[EMAIL PROTECTED]> (supplier of updated cron-apt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 23 Nov 2006 06:28:28 +0100
Source: cron-apt
Binary: cron-apt
Architecture: source all
Version: 0.4.10
Distribution: unstable
Urgency: low
Maintainer: Ola Lundqvist <[EMAIL PROTECTED]>
Changed-By: Ola Lundqvist <[EMAIL PROTECTED]>
Description:
cron-apt - automatic update of packages using apt-get
Closes: 399827
Changes:
cron-apt (0.4.10) unstable; urgency=low
.
* Make sure that initlog is removed on exit, closes: #399827.
Files:
239e4206ea98d26aca4d0eff4c53db74 529 admin optional cron-apt_0.4.10.dsc
c40ed1c7e1bafd7365160ea19e0c298b 34301 admin optional cron-apt_0.4.10.tar.gz
dac608f58ab02cf85c996844f398fe7b 21912 admin optional cron-apt_0.4.10_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFZTG+GKGxzw/lPdkRAnhkAJ9/kQnNw4U8sv6OWSbfQZTgprzRbgCeOd+I
2o/3Xwc6Hzo4YKRIRMweOyc=
=8wed
-----END PGP SIGNATURE-----
--- End Message ---
