[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New Packages generator



>> As we have received no notice of errors and as we also do not see
>> anything bad ourself, I just activated the new generator for the
>> archive. Starting with the next dinstall run in a few minutes all
>> Packages and Sources files[2] will be generated using the new tool.
> is that a related breakage?
> $ sudo debootstrap --arch=i386 sid sid-32 http://ftp.debian.org/debianI: Retrieving Release
> I: Retrieving Release.gpg
> I: Checking Release signature
> I: Valid Release signature (key id 9FED2BCBDCD29CDF762678CBAED4B06F473041FA)
> I: Retrieving Packages
> I: Validating Packages
> W: http://ftp.debian.org/debian/dists/sid/main/binary-i386/Packages.bz2 was corrupt
> I: Retrieving Packages
> I: Validating Packages
> W: http://ftp.debian.org/debian/dists/sid/main/binary-i386/Packages.gz was corrupt
> I: Retrieving Packages
> E: Couldn't download dists/sid/main/binary-i386/Packages
> Same happens with ftp{.fr,.uk,.de,}.debian.org; with i386 and amd64.

It wasn't. Entire different area did this.

Well. We now have a function RIGHT before the mirrorpush goes out that
does a has sum check using the InRelease files before we send the
push. Instead of assuming that noone might ever change the files between
the "rsync into public place" and "now push the mirrors".
Should help against those errors.

-- 
bye, Joerg
<ribnitz> Ganneff: NM-queue ist das schnellste zu uploadrechten für ein paket,
	oder?
<youam> ach aqua^Wribnitz


Reply to: