Gentoo Archives: gentoo-doc-cvs

From: Josh Saddler <nightmorph@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: hb-working-portage.xml
Date: Mon, 04 Sep 2006 13:18:26
Message-Id: 20060904112106.A1FB96514F@smtp.gentoo.org
1 nightmorph 06/09/04 11:21:06
2
3 Modified: hb-working-portage.xml
4 Log:
5 Added a section on digest verification errors, bug 134574
6
7 Revision Changes Path
8 1.59 xml/htdocs/doc/en/handbook/hb-working-portage.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?rev=1.59&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?rev=1.59&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?r1=1.58&r2=1.59
13
14 Index: hb-working-portage.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v
17 retrieving revision 1.58
18 retrieving revision 1.59
19 diff -u -r1.58 -r1.59
20 --- hb-working-portage.xml 1 Aug 2006 17:35:05 -0000 1.58
21 +++ hb-working-portage.xml 4 Sep 2006 11:21:06 -0000 1.59
22 @@ -4,12 +4,12 @@
23 <!-- The content of this document is licensed under the CC-BY-SA license -->
24 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
25
26 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.58 2006/08/01 17:35:05 swift Exp $ -->
27 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.59 2006/09/04 11:21:06 nightmorph Exp $ -->
28
29 <sections>
30
31 -<version>1.53</version>
32 -<date>2006-08-01</date>
33 +<version>1.54</version>
34 +<date>2006-09-04</date>
35
36 <section>
37 <title>Welcome to Portage</title>
38 @@ -614,5 +614,52 @@
39
40 </body>
41 </subsection>
42 +<subsection id="digesterror">
43 +<title>Digest Verification Failures</title>
44 +<body>
45 +
46 +<p>
47 +Sometimes, when you attempt to emerge a package, it will fail with the message:
48 +</p>
49 +
50 +<pre caption="Digest verification failure">
51 +&gt;&gt;&gt; checking ebuild checksums
52 +!!! Digest verification failed:
53 +</pre>
54 +
55 +<p>
56 +This is a sign that something is wrong with the Portage tree -- often, it is
57 +because a developer may have made a mistake when committing a package to the
58 +tree.
59 +</p>
60 +
61 +<p>
62 +When the digest verification fails, do <e>not</e> try to re-digest the package
63 +yourself. Running <c>ebuild foo digest</c> will not fix the problem; it will
64 +almost certainly make it worse!
65 +</p>
66 +
67 +<p>
68 +Instead, wait an hour or two for the tree to settle down. It's likely that the
69 +error was noticed right away, but it can take a little time for the fix to
70 +trickle down the Portage tree. While you're waiting, check <uri
71 +link="http://bugs.gentoo.org">Bugzilla</uri> and see if anyone has reported
72 +the problem yet. If not, go ahead and file a bug for the broken package.
73 +</p>
74 +
75 +<p>
76 +Once you see that the bug has been fixed, you may want to re-sync to pick up
77 +the fixed digest.
78 +</p>
79 +
80 +<impo>
81 +This does <e>not</e> mean that you can re-sync your tree multiple times! As
82 +stated in the rsync policy (when you run <c>emerge --sync</c>), users who sync
83 +too often will be banned! In fact, it's better to just wait until your next
84 +scheduled sync, so that you don't overload the rsync servers.
85 +</impo>
86 +
87 +</body>
88 +</subsection>
89 </section>
90 </sections>
91
92
93
94 --
95 gentoo-doc-cvs@g.o mailing list