-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Haney wrote: > > Since I'm not as up to speed as I really want to be on manipulating > ebuilds and portage, I simply deleted the ebuild and re-sync'd, this one > came down fine and is compiling now. I thought about a bug report, but > I felt that to be too extreme a measure if I was the only person seeing > the problem.
If an emerge sync doesn't fix the problem filing a bug is a perfectly appropriate solution - any dev can fix this in 30 seconds (assuming it is obvious the ebuild wasn't tampered with). Most likely a dev forgot to run repoman when doing a commit - otherwise the digest error would have been caught (in theory they are supposed to do this all the time, but it can be slow). Ditto for problems when a package is marked stable and one of its dependencies is not. 90% of the time it was noticed 5 minutes later and fixed, and you might have done your last emerge sync in the interim. As a result I usually resync before filing a bug. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEz0X9G4/rWKZmVWkRAsTgAJ0UfDfcyiStNZDuhfV47x4zw29KAACcD3Ht Ilg3uGqR1lIeznRHBdyR+Dw= =anj+ -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
