Quoting Pierre Frenkiel (pierre.frenk...@gmail.com): > On Wed, 13 May 2015, David Wright wrote: > > >What happens if you perform this sort of conversation: > >. . . > >~ $ wget > >http://ftp.fr.debian.org/debian/dists/jessie/main/binary-amd64/Packages > >~ $ md5sum Packages > >~ $ wget http://ftp.fr.debian.org/debian/dists/jessie/InRelease > >~ $ grep 854af4d1ea9bce473bd82c11fb62f5bb InRelease > >. . . > >Do they match as shown? > >Do the md5sums of your files in /var/lib/apt/lists match your wife's? > > hi David, > fortunately, I get the same result as you after the wget ... > I couldn't imagine that wget doesn't give always the same file > > here is what I got on the 2 laptops. Can you interpret that? I can't... > > after wget ... > -------------- > =>md5sum Packages > 854af4d1ea9bce473bd82c11fb62f5bb Packages > > =>grep 854af4d1ea9bce473bd82c11fb62f5bb InRelease > 854af4d1ea9bce473bd82c11fb62f5bb 9019439 main/binary-amd64/Packages.gz > > =>grep 7da350516909a92ebfe504d8b0bde8a6 InRelease > 7da350516909a92ebfe504d8b0bde8a6 33775581 main/binary-amd64/Packages
Well, that looks fine. Bear in mind that the wget'd Packages is still compressed with gz, though not in name (ie no .gz suffix). > ->> ls partial > ftp.fr.debian.org_debian_dists_jessie_main_binary-amd64_Packages > > ftp.fr.debian.org_debian_dists_jessie_main_binary-amd64_Packages.decomp.FAILED > ftp.fr.debian.org_debian_dists_jessie_main_binary-i386_Packages > > ftp.fr.debian.org_debian_dists_jessie_main_binary-i386_Packages.decomp.FAILED The question here (having not seen files like this on my system) is what does FAILED mean. > ->> md5sum > partial/ftp.fr.debian.org_debian_dists_jessie_main_binary-amd64_Packages > 8b72b60bfb915f1fd4bc043e1288b1ff > partial/ftp.fr.debian.org_debian_dists_jessie_main_binary-amd64_Packages That is the correct digest for the Packages file but compressed with .xz rather than .gz ... > ->> grep 8b72b60bfb915f1fd4bc043e1288b1ff * > ftp.fr.debian.org_debian_dists_jessie_Release: > 8b72b60bfb915f1fd4bc043e1288b1ff 6765188 main/binary-amd64/Packages.xz ... as confirmed here. If you decompress it with unxz -c ...Packages > /tmp/Packages and then md5sum /tmp/Packages you may see ... > ->> grep 7da350516909a92ebfe504d8b0bde8a6 * > ftp.fr.debian.org_debian_dists_jessie_Release: > 7da350516909a92ebfe504d8b0bde8a6 33775581 main/binary-amd64/Packages ... a digest like that. So it would appear to me that your machine is downloading the .xz file from http://ftp.fr.debian.org/debian/dists/jessie/main/binary-amd64/ but treating it as a .gz file which will make it fail. I don't know where this decision is made. (I also don't know where the decision is made by wget as to which Packages file to download, the .gz or the .xz one.) My wheezy apt-cacher-ng had a similar problem with serving the jessie tree. Because a file arrived in .xz format and failed to decompress, it could never get as far as pruning the jessie pool cache which grew and grew. It was fixed by installing the wheezy-backport version. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150514152614.GA8152@alum
