On Tue, Sep 02, 2008 at 05:36:23PM +0200, Christoph Martin <[EMAIL PROTECTED]> was heard to say: > > > Daniel Burrows schrieb: > > On Tue, Sep 02, 2008 at 10:47:36AM +0200, Christoph Martin <[EMAIL > > PROTECTED]> was heard to say: > >> I have a bunch of packages which aptitude upgrade everytime wants to > >> upgrade > >> but which are really at the correct version. apt-cache policy shows, that > >> the packages have the correct versions but don't get recognised to come > >> from the stable distribution. > > > > What does "apt-cache show -v time" show you? > > "apt-cache show -v time" shows the same as "apt-cache show time" which I > attach to this mail.
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?) The output of "apt-cache showpkg time" would help; it should say which archive each md5sum is from. 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. What I don't understand is why apt is accepting a Packages file that's corrupted. Do you get GPG failures when you update? Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
