-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Julien Cabillot wrote:
> # ebuild path_to_the_ebuild/sun-jdk-1.5.0.07.ebuild digest
> After that emerge sun-jdk
Beware that this bypasses any security measure that portage provides and
is not the preferred way to "fix" this issue. If you are positive that
the package is legit I would run that command suggested but otherwise
that is the only way that portage will know if the files are legit. It
could be that the mirror corrupted the file (which happens when disks
become full) or someone *could* have put a malicious file there.
Normally this can be fixed by waiting a day and syncing again or by
using a different mirror to sync. HTH..
- --
Jeremy Olexa
([EMAIL PROTECTED])
Office: EE/CS 1-201
CS/IT Systems Staff
University of Minnesota
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEtG86FN7pD9kMi/URAu6oAKCIPRACuaxmUvBKlLHkK5BJWNC5swCfQ+KF
gFhHd8kjKY+QZYnMNpvu3+w=
=iIvJ
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
I'll build a little more on the 2 previous repliers. I've received md5 errors before on emerges; refetching the sources fixed the issue. Emerge --fetchonly <package> used to work to make it refetch packages, but I don't think that works anymore. I would recommend manually deleting the ebuild files then doing a --fetchonly <package> to refetch them.
--
- Mark Shields
