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

Re: key troubles



On 06/18/2014 01:29 PM, Glenn English wrote:

> When debmirror runs, the reported problem is a failed checksum verification:
> 
>> sent 228 bytes  received 1702 bytes  1286.67 bytes/sec
>> total size is 918  speedup is 0.48
>> Getting meta files ...
>> [  0%]	 #** GET http://ftp.us.debian.org/debian/dists/wheezy/Release ==> 200 OK (1s)
>> [  0%]	 #** GET http://ftp.us.debian.org/debian/dists/wheezy/Release.gpg ==> 200 OK
>> [  0%]	 #** GET http://ftp.us.debian.org/debian/dists/jessie/Release ==> 200 OK (1s)
>> [  0%]	 #** GET http://ftp.us.debian.org/debian/dists/jessie/Release.gpg ==> 200 OK
>> [ 75%]	 #** GET http://ftp.us.debian.org/debian/dists/jessie/main/binary-amd64/Packages.diff/Index ==> 200 OK
>> [ 75%]	 #** GET http://ftp.us.debian.org/debian/dists/jessie/main/binary-amd64/Packages.diff/2014-06-18-0257.24.gz ==> 200 OK (1s)
>> [ 75%]	 #** GET http://ftp.us.debian.org/debian/dists/jessie/main/binary-amd64/Packages.diff/2014-06-18-1455.18.gz ==> 200 OK
>> [ 75%]	 #** GET http://ftp.us.debian.org/debian/dists/jessie/main/binary-amd64/Packages.gz ==> 200 OK (50s)
>> [ 80%]	 #** GET http://ftp.us.debian.org/debian/dists/jessie/main/binary-amd64/Packages ==> 404 Not Found
>> failed 404 Not Found
>> Errors:
>>  Download of dists/jessie/main/binary-amd64/Packages failed: 404 Not Found
>>  dists/jessie/main/binary-amd64/Packages failed checksum verification
>> Failed to download some Package, Sources or Release files!
>> WARNING: releasing 1 pending lock...
> 
> I have what claims to be the most recent key for both wheezy and jessie, and I've looked for others. The keys aptitude uses work fine for reloading its repositories, but apparently not for debmirror. These all worked a few days ago, and, IIRC, they all broke at the same time...
> 
> Can someone see what's going wrong?
> 

The 404 Not Found on the Packages file is because that file does not
exist in the repositories.  You can get rid of the debmirror error by
using an --exclude='/Packages$' option.

I don't know what might be causing the aptitude update errors.

Mark Neyhart


Reply to: