> -----Message d'origine----- > De : [email protected] > [mailto:[email protected]] De la part de Michael > Tautschnig > Envoyé : 29 avril 2009 16:12 > À : [email protected] > Objet : Re: Etch amd64 mirror broken? - Packages.gz was corrupt > > [...] > > > > > > I've tried changing my FAI_DEBOOTSTRAP="etch > > http://ftp.debian.org/debian"; but I get the exact same error with > > debian.org: > > Calling debootstrap etch > > /data/fai/nfsroot/QC/amd64/live/filesystem.dir > > http://ftp.debian.org/debian [^] > > I: Retrieving Packages > > I: Validating Packages > > W: > > > http://ftp.debian.org/debian/dists/etch/main/binary-amd64/Packages.gz > > [^] was corrupt > > I: Retrieving Packages > > I: Resolving dependencies of required packages... > > I: Resolving dependencies of base packages... > > W: Failure trying to run: chroot > > /data/fai/nfsroot/QC/amd64/live/filesystem.dir mount -t proc proc > > /proc > > > > > > Everything used to be working really really smoothly until recently > > (we actually noticed that on april 17th). > > > > Lastly, our 32bit fai runs without a flaw and I can update my nfsroot > > without any problems using either debian.org or my local debmirror. > > > > Just a really blind guess: Are you working behind some proxy? > Has it cached that file (in a broken way)? Its just > debootstrap that is running here ...
Nope... and that is why I'm really really wondering what might be causing this??? It does the same error either directly on debian.org or on my internal debmirror ONLY on amd64 etch ??? And that is totally new since perhaps 2-3 week? I'm probably mistaking but it makes me wonder if there could be a real corruption of the "Pacakges" files for amd64 etch on the official debian repository??? Or curiously enough, a "new" bug in the debootstrap that suddently appeared 2-3 weeks ago? What's wierd is that it never stopped working on i386 but suddently got marked as "corrupted" by debootstrap only for amd64 ? Wierd guess: official etch amd64 repository broken? - vin
