Richard Freeman wrote:
-----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.
All of this is great information, and something I've needed to know for
quite a while. I really like Gentoo, so much so, that I've migrating to
it from Fedora on all my boxes at home (13 at last count). Other than
this laptop refusing to play nice with the ATI drivers, I've had nothing
but great experiences from it.
Thanks for the help and the info.
--
Fere libenter homines id quod volunt credunt.
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
--
[email protected] mailing list
