Your message dated Sun, 30 Apr 2006 11:32:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#358136: fixed in cron-apt 0.4.6 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.5 Severity: minor Hi, I am running cron-apt on an hourly basis. This might lead to the following situation: Prerequisite: One of the apt servers is down causing apt-get update to take a _loooong_ time. nn:00 cron-apt is started by cron, sleep time 3540 seconds nn:59 apt-get update starts, stalls due to the apt server being down nn+1:00 cron-apt is started by cron, sleep time 120 seconds nn+1:02 apt-get update starts, reports "can't obtain apt lock" due to the still running apt from the last round This happens surprisingly often and increases the number of e-mails generated since the "can't obtain apt lock" error message completely messes up diff handling. cron-apt should be changed to do the following sleep take out a lock check if lock successful if lock successful, continue if lock unsuccessful, terminate with a log message, but not messing up the diffs Greetings Marc -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-zgsrv Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages cron-apt depends on: ii apt 0.6.43.3 Advanced front-end for dpkg ii debianutils 2.15.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.6 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.6.dsc to pool/main/c/cron-apt/cron-apt_0.4.6.dsc cron-apt_0.4.6.tar.gz to pool/main/c/cron-apt/cron-apt_0.4.6.tar.gz cron-apt_0.4.6_all.deb to pool/main/c/cron-apt/cron-apt_0.4.6_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: Sun, 30 Apr 2006 18:09:02 +0200 Source: cron-apt Binary: cron-apt Architecture: source all Version: 0.4.6 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: 358136 Changes: cron-apt (0.4.6) unstable; urgency=low . * Move dotlock code so that now the entire cron-apt run is protected by locking, closes: #358136. Thanks to Marc Haber <[EMAIL PROTECTED]> for the patch. Files: ad5cabf3f75feb2011f0237a5d41442f 515 admin optional cron-apt_0.4.6.dsc d8631b06f5c44d5d05c41393d4e41f51 33742 admin optional cron-apt_0.4.6.tar.gz f935e6e563d4c48ad82c79581af78b98 21606 admin optional cron-apt_0.4.6_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEVP5tGKGxzw/lPdkRAtK3AJ96D1MoSi5DiTdCk+pqjnCTqu2sgQCfUHbo 9RFaM9Xt5XLZP8CWGkkjcXw= =brZH -----END PGP SIGNATURE-----
--- End Message ---
