Your message dated Wed, 1 Dec 2010 17:08:30 -0800
with message-id <20101202010830.gc17...@talon.fglan>
and subject line Re: Bug#605527: approx: routinely has inconsistant Release*
and Packages* files
has caused the Debian Bug report #605527,
regarding approx: routinely has inconsistant Release* and Packages* files
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 ow...@bugs.debian.org
immediately.)
--
605527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: approx
Version: 4.5-1
Severity: grave
Justification: renders package unusable
approx is failing to cache the mirror correctly.
i routinely end up with apt-get update from approx resulting in:
W: Failed to fetch
http://127.0.0.1:9999/debian/dists/squeeze/main/binary-i386/PackagesIndex
MD5Sum mismatch
W: Failed to fetch
http://127.0.0.1:9999/debian/dists/experimental/main/source/SourcesIndex
MD5Sum mismatch
W: Failed to fetch
http://127.0.0.1:9999/debian/dists/sid/main/binary-i386/Packages.gz Hash Sum
mismatch
W: Failed to fetch
http://127.0.0.1:9999/debian/dists/sid/main/source/Sources.gz Hash Sum mismatch
E: Some index files failed to download, they have been ignored, or old ones
used instead.
with both approx entries and direct entries to the exact same mirrors
configured in apt's sources.list, at least one of my approx entries results in
a "Hash Sum mismatch" on nearly every apt-get update, while the directly
configured entries work without problems.
it's not always the same entries... sometimes sid, sometimes squeeze, sometimes
experimental, but nearly always at least one of them fails. two subsequent runs
often end up with different results.
sometimes, manually removing the /var/cache/approx/debian*/dists/ directories
or specific Packages*/Release* files fixes it for a day or so, but it doesn't
take long for it to consistantly fail again.
i've been a largely happy long-time user of approx, and have encountered
infrequent occasional glitches like this before, but this problem seems to have
gotten increasingly worse since upgrading to squeeze a few months ago.
live well,
vagrant
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (102, 'unstable'), (101,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-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/dash
Versions of packages approx depends on:
ii adduser 3.112 add and remove users and groups
ii bzip2 1.0.5-6 high-quality block-sorting file co
ii curl 7.21.0-1 Get a file from an HTTP, HTTPS or
ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi
ii openbsd-inetd [inet-superse 0.20080125-6 The OpenBSD Internet Superserver
ii update-inetd 4.38 inetd configuration file updater
approx recommends no packages.
Versions of packages approx suggests:
pn libconfig-model-approx-perl <none> (no description available)
-- Configuration Files:
/etc/approx/approx.conf changed:
debian http://debian.osuosl.org/debian
debian-security http://security.us.debian.org/debian-security
debian-volatile http://volatile.debian.org/debian-volatile
debian-backports http://backports.debian.org/debian-backports
skolelinux http://ftp.skolelinux.org/skolelinux
debian-ports http://debian-ports.org/debian
$verbose true
$offline true
$debug true
/etc/cron.weekly/approx changed:
if [ -x /usr/sbin/approx-gc ]; then
/usr/sbin/approx-gc --verbose
fi
-- debconf information:
approx/port: 9999
--- End Message ---
--- Begin Message ---
On Wed, Dec 01, 2010 at 11:17:39PM +0100, Simon Paillard wrote:
> > with both approx entries and direct entries to the exact same mirrors
> > configured in apt's sources.list, at least one of my approx entries results
> > in a "Hash Sum mismatch" on nearly every apt-get update, while the directly
> > configured entries work without problems.
>
> DNS Round robin might mislead your conclusions.
i had though of that, so tried ftp.us.debian.org, but i think it had included
the bunk mirror at the time (and has even more servers in the list for
potential round-robin issues). although specifying debian.osuosl.org directly
worked every single time, so i didn't *think* that was what the problem was.
though it was probably getting some files from the working server and some from
the not working server...
> > i've been a largely happy long-time user of approx, and have encountered
> > infrequent occasional glitches like this before, but this problem seems to
> > have
>
> s/approx/debian.osuosl.org/
>
> > -- Configuration Files:
> > /etc/approx/approx.conf changed:
> > debian http://debian.osuosl.org/debian
>
> osuosl is having issues with ftp-chi.osuosl.org (on top of performing sync in
> a
> non-atomic way on this server) and we (mirr...@d.o) are aware of this, hence
> removal of this specific server from ftp.us.debian.org.
>
> http://64.50.233.100/debian/project/trace/ is ok
using this directly seems to have fixed the problem, at least on my first
run... thanks for the suggestion!
> http://64.50.236.52/debian/project/trace/ is not ok (and 1 day late)
>
> Please check with ftp.us.d.o (or some other official ftp.CC.d.o) as source for
> approx, I'm pretty sure it will solve your issues.
> (trying to blaming the conf before blaming the software is worth :)
since it seems to be working with a different (more specific) mirror, i'll
close the bug.
guess i should've been more thorough in my testing. sorry for the noise.
live well,
vagrant
--- End Message ---
