/[gentoo]/xml/htdocs/doc/en/handbook/hb-working-portage.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-working-portage.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.58 Revision 1.59
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.58 2006/08/01 17:35:05 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.59 2006/09/04 11:21:06 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.53</version> 11<version>1.54</version>
12<date>2006-08-01</date> 12<date>2006-09-04</date>
13 13
14<section> 14<section>
15<title>Welcome to Portage</title> 15<title>Welcome to Portage</title>
16<body> 16<body>
17 17
612from the system. 612from the system.
613</p> 613</p>
614 614
615</body> 615</body>
616</subsection> 616</subsection>
617<subsection id="digesterror">
618<title>Digest Verification Failures</title>
619<body>
620
621<p>
622Sometimes, when you attempt to emerge a package, it will fail with the message:
623</p>
624
625<pre caption="Digest verification failure">
626&gt;&gt;&gt; checking ebuild checksums
627!!! Digest verification failed:
628</pre>
629
630<p>
631This is a sign that something is wrong with the Portage tree -- often, it is
632because a developer may have made a mistake when committing a package to the
633tree.
634</p>
635
636<p>
637When the digest verification fails, do <e>not</e> try to re-digest the package
638yourself. Running <c>ebuild foo digest</c> will not fix the problem; it will
639almost certainly make it worse!
640</p>
641
642<p>
643Instead, wait an hour or two for the tree to settle down. It's likely that the
644error was noticed right away, but it can take a little time for the fix to
645trickle down the Portage tree. While you're waiting, check <uri
646link="http://bugs.gentoo.org">Bugzilla</uri> and see if anyone has reported
647the problem yet. If not, go ahead and file a bug for the broken package.
648</p>
649
650<p>
651Once you see that the bug has been fixed, you may want to re-sync to pick up
652the fixed digest.
653</p>
654
655<impo>
656This does <e>not</e> mean that you can re-sync your tree multiple times! As
657stated in the rsync policy (when you run <c>emerge --sync</c>), users who sync
658too often will be banned! In fact, it's better to just wait until your next
659scheduled sync, so that you don't overload the rsync servers.
660</impo>
661
662</body>
663</subsection>
617</section> 664</section>
618</sections> 665</sections>

Legend:
Removed from v.1.58  
changed lines
  Added in v.1.59

  ViewVC Help
Powered by ViewVC 1.1.20