On Wed, Sep 03, 2008 at 09:22:52AM +0200, Christoph Martin <[EMAIL PROTECTED]> was heard to say: > Daniel Burrows schrieb: > > Ok. Well, it looks like a problem with your mirrors to me. Each > > of the version 1.7-21s is actually different from the others (it has a > > different md5sum). > > > >> Package: time > >> Version: 1.7-21 > >> MD5sum: b320ca25662e5621e6ddc8cad6a1343f > > > >> Package: time > >> Version: 1.7-21 > >> MD5sum: cf0078ab0c573281d96411894d807469 > > > >> Package: time > >> Version: 1.7-21 > > > > (no md5sum?) > > Is this the installed version?
Yes. > > The output of "apt-cache showpkg time" would help; it should say > > which archive each md5sum is from. > > The output is attached. Bleh, the feature I was counting on is only present in newer versions of apt. Sorry about that. > > On my system, time version 0.7-21 > > (from stable and oldstable) has the md5sum > > 09df22253b46100e61c770e89872cc3c. Neither of the packages in the above > > archives has the right md5sum. > > Is your system amd64? Nope. > > What I don't understand is why apt is accepting a Packages file > > that's corrupted. Do you get GPG failures when you update? > > No I don't get any Errors. But it might be that the versions on > oldstable are different from the versions in stable since oldstable of > amd64 was not in the main archive and all the packages were recompiled > for the etch release but the version number was not bumbed. So this > might be why the package has different md5s in oldstable and stable. But > still apt-get should register correctly the installed version and > identify it. You're right that the md5sums are different. Here the md5sums I get if I download the .debs and run "md5sum" on them: oldstable: 90f88e5cb63fbc4da70b30fd57bc623b oldstable: b320ca25662e5621e6ddc8cad6a1343f oldstable: ab99593efdf397078f11d9c37dd218a1 stable: cf0078ab0c573281d96411894d807469 The multiple occurrences of "oldstable" are from different mirrors that I tried. Your archive (ftp.de) has a package whose md5sum matches the md5sum of its Packages file, so that should be OK. I wonder if apt is reusing a file in its cache. Have you tried running apt-cache clean and then installing "time"? After you do that, what's the md5sum of /var/cache/apt/archives/time_1.7-21_amd64.deb? Does it change if you clean the cache and install time again? > If I understand this correctly, in the above output the installed > version should have an md5sum and this would identify the installed > version with the version in der Package file? So the question would be, > why is apt-get not writing the installed versions md5 into the status db? apt has never done well with situations where there are multiple versions of a single package. Personally, I would remove the oldstable line. I could reassign this to apt if you like. I thought this was already reported multiple times (it's certainly well-known), but I can't find the duplicates in the bug list. #351056 is close, but that turned out to be a situation where the md5sums were identical after all. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
