On Fri, June 11, 2004 11:35, Alexander Dalloz said: > Am Fr, den 11.06.2004 schrieb P. Ekholm um 18:25: > >> The output of kernel-2.6.6-1.427.i686.rpm md5sum is different from the >> announcement md5sum. Have downloaded the files from different mirrors. >> Don´t >> want to install the kernel if i´m not shure. Please correct this. > >> P. Ekholm > > Here does the md5sums from announcement differ with my own checks too. > > md5sums from announcement: > d3d3605bc24d574cd0813edc0be8d65c > i386/kernel-sourcecode-2.6.6-1.427.noarch.rpm > db2fad6f1bc995fca31f1558aafe8d8a i386/kernel-2.6.6-1.427.i686.rpm > > md5sums self generated: > 29dfd66fd621e25b7f4ba396b330c8ce kernel-2.6.6-1.427.i686.rpm > f656ea8b93ae896d00970c480db37596 > kernel-sourcecode-2.6.6-1.427.noarch.rpm > > $ rpm -K kernel-* > kernel-2.6.6-1.427.i686.rpm: (sha1) dsa sha1 md5 gpg OK > kernel-sourcecode-2.6.6-1.427.noarch.rpm: (sha1) dsa sha1 md5 gpg OK > $ la kernel-* > -rw------- 1 adalloz adalloz 14047835 11. Jun 17:24 > kernel-2.6.6-1.427.i686.rpm > -rw------- 1 adalloz adalloz 45273157 11. Jun 17:37 > kernel-sourcecode-2.6.6-1.427.noarch.rpm I am having similar problems when running up2date, although here it's with GPG signatures. I first encountered this on Friday, June 11 around 0100 CDT, and just got it again a few minutes ago: "The package kernel-2.6.6-1.427 does not have a valid GPG signature. It has been tampered with or corrupted. Continue?" -- Anthony Jeffries | ajeffri@xxxxxxxxxxxxx People often find it easier to be a result of the past than a cause of the future. -- Unknown