I've got a little trouble with the keys used to sign packages. I'm running squeeze-lts, wheezy, and jessie; and there are local mirrors of parts of wheezy and jessie.
When aptitude on squeeze tries to update its repository, it says: > │W: A error occurred during the signature verification. The repository is not > updated and the previous index files will be used. GPG error: > http://http.debian.net squeeze-lts Release: The following signatures were > invalid: BADSIG 8B48AD6246925553 Debian Archive Automatic Signing Key > (7.0/wheezy) <ftpmas...@debian.org> There is no mention of wheezy in the squeeze machine's apt/sources.list. When debmirror runs, the reported problem is a failed checksum verification: > Wed Jun 18 15:10:52 MDT 2014 > > ------- creating/updating a mirror of arch(s) i386,amd64 ------- > ------- repository at ftp.us.debian.org/debian ------- > ------- dist: wheezy,jessie, sections: main,contrib ------- > Mirroring to /var/www/debian from http://ftp.us.debian.org/debian/ > Arches: i386,amd64 > Dists: wheezy,jessie > Sections: main,contrib > Pdiff mode: use > Passive mode on. > Will clean up after mirroring. > Attempting to get lock ... > Updating remote trace files (using rsync) ... > receiving incremental file list > deleting project/trace/debian.gtisc.gatech.edu > ./ > project/ > project/trace/ > project/trace/ftp-master.debian.org > 104 100% 101.56kB/s 0:00:00 (xfer#1, to-check=3/7) > project/trace/ftp-nyc.osuosl.org > 269 100% 5.15kB/s 0:00:00 (xfer#2, to-check=2/7) > project/trace/ftp-osl.osuosl.org > 275 100% 5.27kB/s 0:00:00 (xfer#3, to-check=1/7) > project/trace/syncproxy.wna.debian.org > 270 100% 5.17kB/s 0:00:00 (xfer#4, to-check=0/7) > > 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? -- Glenn English -- 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/0bb93d5c-723a-4c19-abb0-56c82d469...@richeyrentals.com
