During the last few days I've seen some people on IRC and on the gentoo-user mailing list who experience digest verification errors due to changes to ebuilds and files in distfiles what hasn't resulted in a change of revision. Some people tend to recommend that those people should just digest the ebuild whenever they experience this. I really miss some documentation to refer to, that explains what to do in these situations (sync, delete the file in distfiles, search/file a bug?) and why people shouldn't just blindly digest ebuilds in the tree, when they have no idea what's wrong. I would suggest that this be added to "1.d. When Portage is Complaining..." [1] in the handbook. Sounds like a good idea? (I find that my ability to argue/explain this aren't too convincing, so I'm probably not the right person to write this though.) [1] http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1
the FAQ seems most appropriate to me
We should probably add a "how to submit a patch" to correct the problem, as "Digest verification Failed" bugs don't seem to get much attention. This way, the user can submit a patch, and the dev teams can concentrate on real bugs. An example of a long-standing digest bug. http://bugs.gentoo.org/show_bug.cgi?id=127204 Thank you for your time, Frank Russo
(In reply to comment #1) > the FAQ seems most appropriate to me So you're saying it we be good to add this to the FAQ, right?
Added to the Portage handbook, instead. ("When portage is complaining...") Fixed in CVS; thanks for reporting.
