Re: mirrors.kernel.org (Re: rsync and debian mirror consistency)
- To: debian-mirrors@lists.debian.org
- Subject: Re: mirrors.kernel.org (Re: rsync and debian mirror consistency)
- From: Justin Pryzby <justinpryzby@users.sourceforge.net>
- Date: Sun, 2 Mar 2008 14:58:11 -0500
- Message-id: <20080302195810.GA2774@libra>
- In-reply-to: <20080227215454.GA10591@libra>
- References: <20080221000726.GA3909@libra> <47BCC7FD.403@kernel.org> <20080221010157.GA17281@cetus> <47BCE67E.4050706@kernel.org> <20080221151458.GA26723@cetus> <20080226121055.GA6201@keid.carnet.hr> <20080227215454.GA10591@libra>
On Wed, Feb 27, 2008 at 04:54:54PM -0500, Justin Pryzby wrote:
> On Tue, Feb 26, 2008 at 01:10:55PM +0100, Josip Rodin wrote:
> > On Thu, Feb 21, 2008 at 10:14:58AM -0500, Justin Pryzby wrote:
> > > He seems to say that debian.org pushes archive content to the kernel.org
> > > mirrors (rather than running an ssh trigger causing them to immediately
> > > do a "pull"). It seems that consistency between the .deb files and the
> > > Packages.gz files isn't maintained by this special push, as it is with
> > > the anonftpsync template script. Is this correct?
> >
> > No, it's not, I fixed that a few months ago. The script rsyncs over the
> > index files first, doesn't delete, and then in the second run rsyncs
> > everything else with --delete-after. Can you demonstrate a problem, what
> > error messages did you get that led you to the conclusion that this is
> > broken on .k.o sites?
> By adding a cronjob, the following was caused within a few hours.
>
> */5 * * * * root nice apt-get -q -q update && apt-get -q -q -d -y dist-upgrade
> Failed to fetch http://mirrors.kernel.org/debian/pool/main/c/cdebootstrap/cdebootstrap_0.4.9_i386.deb 404 Not Found [IP: 204.152.191.7 80]
Do you know how this can happen if they really use a 2 stage rsync? I
understand that it can happen if I used an old packages file (and no,
I didn't immediately rerun apt-get update && apt-get -d upgrade to
reproduce it). However it seems to me that, since the error refers to
the *new* .deb package file, that I really was using the new
Packages.gz file and that all the debs should have been in place.
Perhaps that's related to use of Package diff files?
Justin
Reply to: