Your message dated
with message-id <[email protected]>
and subject line apt-proxy removed from Debian unstable
has caused the Debian Bug report #295329,
regarding Occasionally fails to update Packages list
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 [email protected]
immediately.)
--
295329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295329
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-proxy
Version: 1.9.25
Severity: normal
For a long time apt-proxy appears to have been getting quite confused
over what constitutes an up-to-date Packages file. For example, right
now for me the local apt-proxy cache shows this (for sid/main):
-rw------- 1 aptproxy nogroup 3401444 Feb 14 07:06 Packages.gz
The upstream mirror its connected to shows this:
-rw-r--r-- 1 mirror mirror 3401217 Feb 14 20:10 Packages.gz
and by HTTP instead of FTP:
Packages.gz 15-Feb-2005 06:10 3.2M GZIP compressed file
(the time difference between FTP & HTTP being the GMT offset of my TZ)
Doing an apt-get update claims that the Packages file is unchanged, even
though I'm quite certain at least one package has been changed in Debian
during the past 24 hours ;)
It's my suspicion that timezone differences causes calculation problems
in determining when to fetch the Packages list from upstream (note:
there is no timezone difference between myself and my upstream mirror,
but certainly between ftp-master or whatever is the central control
now, and my mirror). Also, its been my observation that although the
time claims to be changed at 6am, I seem to have to wait until 9:30am or
later before the update will actually happen. I'm confident in
guaranteeing come 20:10 tonight I'll be able to do the update
successfully. It's been my observation that once GMT rolls over to the
same day I'm on (being GMT+10) things work a lot happier.
I have come across mirroring issues when investigating this in the past,
so I know what to expect in that regard. This isn't simply a matter of
my upstream (which is a primary mirror anyway) being out of date.
What else can I do to help diagnose this problem?
--
Matt
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.9.37+rm
apt-proxy has been removed from Debian unstable: http://bugs.debian.org/576821
Closing its bugs with a Version higher than the last unstable upload.
More information about this script at:
http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD
--- End Message ---
