On Fri, Oct 20, 2006 at 11:35:12PM +0200, Andreas Janssen wrote: > [...] > I found out that the md5sum and sha1sum of the package match that in > the Packages.bz2 file, but the sha256sum is actually different. > > Running the checksum programs on my machine results in: > > ae435c503465b91c7eadc19b234370b6 > 9081951967a54c91315a5ba29337597bb6b2f8af > a16e38d82dc830769b89e1f7e213f65e0214fd064bf42350f184205ab0afbc85 > > The Packages file however says: > > MD5sum: ae435c503465b91c7eadc19b234370b6 > SHA1: 9081951967a54c91315a5ba29337597bb6b2f8af > SHA256: 2b32376a31b621266012b90910927eca18a701b76150e700289f7856b8d8bd3b > > Looks like a problem with the Packages file to me.
Yes, the packages file is wrong. It might be this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378183 I have emailed Christian Marillat to point it out to him. I missed that because the "--quiet" option to gc_approx doesn't print anything -- they were just being removed silently. I guess gc_approx should have an option to disable SHA256 checking, or be more verbose in gc_approx, or both. -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]