On Sat Dec 08, 2001 at 12:34:15PM -0600, David Wollmann wrote:

> > > tetex-1.0.7-6.1mdk.i586.rpm: MD5 GPG NOT OK
> > > tetex-doc-1.0.7-6.1mdk.i586.rpm: MD5 GPG NOT OK
> > > 
> > > 
> > > I haven't checked these files on other servers.
> > > 
> > > Any chance we can get someone to check this out and see what the problem 
> > > is?
> > 
> > I assume you have the security team gpg keys installed?  (Of course
> > you do, otherwise they would all fail).  I know the files are fine
> > because:
> > 
> > (vdanen@logan: /mnt/updates/BIG/updates/7.1/RPMS)$ rpm --checksig tetex*
> > tetex-1.0.7-6.1mdk.i586.rpm: md5 gpg OK
> > tetex-afm-1.0.7-6.1mdk.i586.rpm: md5 gpg OK
> > tetex-doc-1.0.7-6.1mdk.i586.rpm: md5 gpg OK
> > tetex-dvilj-1.0.7-6.1mdk.i586.rpm: md5 gpg OK
> > tetex-dvips-1.0.7-6.1mdk.i586.rpm: md5 gpg OK
> > tetex-latex-1.0.7-6.1mdk.i586.rpm: md5 gpg OK
> > tetex-xdvi-1.0.7-6.1mdk.i586.rpm: md5 gpg OK
> > (vdanen@logan: /mnt/updates/BIG/updates/7.1/RPMS)$
> > 
> > Can you do a "rpm --checksig -v" on the two packages and see exactly
> > what fails?  You may have had a bad download.
> 
> I ran rpm with the verbose switch and the MD5 chksums are bad, _not_ 
> the signatures.

Try re-downloading the two files then.

> I'll have a go with a couple other download methods and see if I can get
> better results.

Yup.. likely a bad download (off by one byte or something maybe which
would still make the gpg sig valid).

-- 
OpenPGP key available on www.keyserver.net
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD

Current Linux kernel 2.4.8-34.1mdk uptime: 20 days 20 hours 50 minutes.

Attachment: msg45920/pgp00000.pgp
Description: PGP signature

Reply via email to