nightmorph 06/09/04 11:21:06 Modified: hb-working-portage.xml Log: Added a section on digest verification errors, bug 134574
Revision Changes Path 1.59 xml/htdocs/doc/en/handbook/hb-working-portage.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?rev=1.59&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?rev=1.59&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?r1=1.58&r2=1.59 Index: hb-working-portage.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v retrieving revision 1.58 retrieving revision 1.59 diff -u -r1.58 -r1.59 --- hb-working-portage.xml 1 Aug 2006 17:35:05 -0000 1.58 +++ hb-working-portage.xml 4 Sep 2006 11:21:06 -0000 1.59 @@ -4,12 +4,12 @@ <!-- The content of this document is licensed under the CC-BY-SA license --> <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.58 2006/08/01 17:35:05 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.59 2006/09/04 11:21:06 nightmorph Exp $ --> <sections> -<version>1.53</version> -<date>2006-08-01</date> +<version>1.54</version> +<date>2006-09-04</date> <section> <title>Welcome to Portage</title> @@ -614,5 +614,52 @@ </body> </subsection> +<subsection id="digesterror"> +<title>Digest Verification Failures</title> +<body> + +<p> +Sometimes, when you attempt to emerge a package, it will fail with the message: +</p> + +<pre caption="Digest verification failure"> +>>> checking ebuild checksums +!!! Digest verification failed: +</pre> + +<p> +This is a sign that something is wrong with the Portage tree -- often, it is +because a developer may have made a mistake when committing a package to the +tree. +</p> + +<p> +When the digest verification fails, do <e>not</e> try to re-digest the package +yourself. Running <c>ebuild foo digest</c> will not fix the problem; it will +almost certainly make it worse! +</p> + +<p> +Instead, wait an hour or two for the tree to settle down. It's likely that the +error was noticed right away, but it can take a little time for the fix to +trickle down the Portage tree. While you're waiting, check <uri +link="http://bugs.gentoo.org";>Bugzilla</uri> and see if anyone has reported +the problem yet. If not, go ahead and file a bug for the broken package. +</p> + +<p> +Once you see that the bug has been fixed, you may want to re-sync to pick up +the fixed digest. +</p> + +<impo> +This does <e>not</e> mean that you can re-sync your tree multiple times! As +stated in the rsync policy (when you run <c>emerge --sync</c>), users who sync +too often will be banned! In fact, it's better to just wait until your next +scheduled sync, so that you don't overload the rsync servers. +</impo> + +</body> +</subsection> </section> </sections> -- [email protected] mailing list
