Bug#509126: apt-cacher: cron job reports error 25

[Ross Boylan]

Package: apt-cacher
Version: 1.6.5pre1rb1
Severity: normal

Today, cron reported
run-parts: /etc/cron.daily/apt-cacher exited with return code 25

Other than that, I don't see anything in the logs.

-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt-cacher depends on:
ii bzip2 1.0.5-1 high-quality block-sorting file co
ii ed 0.7-2 The classic unix line editor
ii libdigest-sha1-perl 2.11-2+b1 NIST SHA-1 message digest algorith
ii libfreezethaw-perl 0.43-4 converting Perl structures to stri
ii libwww-curl-perl 4.05-1 Perl bindings to libcurl
ii libwww-perl 5.813-1 WWW client/server library for Perl
ii perl 5.10.0-18 Larry Wall's Practical Extraction

Versions of packages apt-cacher recommends:
ii libberkeleydb-perl 0.34-1+b1 use Berkeley DB 4 databases from P

Versions of packages apt-cacher suggests:
ii libio-socket-inet6-perl 2.54-1 Object interface for AF_INET6 doma

-- no debconf information

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Ross Boylan]

I don't see how this is a fix.

First, the errors weren't hidden to begin with. Or maybe there was some
change; my last exit 25 is Mar 08; after that I have two "return code 2"
and, most recently, a "return code 1".

Second, while showing the error is good, it's not really as good as
fixing whatever is causing the error :). Admittedly this is hard
because it's a bit random.

Ross

On Mon, 2009-10-19 at 19:18 +0000, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the apt-cacher package:
>
> #509126: apt-cacher: cron job reports error 25
>
> It has been closed by Mark Hindley <ma...@hindley.org.uk>.
>

> > * Don't hide cron errors. (closes: #509126)
> > -----END PGP SIGNATURE-----
> >
> >
> email message attachment

> > -------- Forwarded Message --------
> > From: Ross Boylan <RossB...@stanfordalumni.org>
> > To: Debian Bug Tracking System <sub...@bugs.debian.org>
> > Subject: apt-cacher: cron job reports error 25
> > Date: Thu, 18 Dec 2008 09:16:58 -0800
> >
> > Package: apt-cacher
> > Version: 1.6.5pre1rb1
> > Severity: normal
> >
> > Today, cron reported
> > run-parts: /etc/cron.daily/apt-cacher exited with return code 25
> >

--

[Mark Hindley]

On Tue, Oct 20, 2009 at 10:53:38AM -0700, Ross Boylan wrote:
> I don't see how this is a fix.
>
> First, the errors weren't hidden to begin with. Or maybe there was some
> change; my last exit 25 is Mar 08; after that I have two "return code 2"
> and, most recently, a "return code 1".
>
> Second, while showing the error is good, it's not really as good as
> fixing whatever is causing the error :). Admittedly this is hard
> because it's a bit random.

OK, I accept that the changelog entry could have been clearer about
this, but there is a fix too. The underlying problem was changes to the cache
directory whilst apt-cacher-cleanup.pl was running. See bug #537189.

I chose to split the changes between the 2 bugs in the changelog. Sorry
if tat was not helpful/clear.

Mark