jkt         08/01/31 21:30:23

  Modified:             hb-working-portage.xml
  Log:
  Change digest verification error message to match the real one as reported by
  current Portage

Revision  Changes    Path
1.70                 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.70&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?rev=1.70&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?r1=1.69&r2=1.70

Index: hb-working-portage.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -r1.69 -r1.70
--- hb-working-portage.xml      31 Jan 2008 14:37:51 -0000      1.69
+++ hb-working-portage.xml      31 Jan 2008 21:30:23 -0000      1.70
@@ -4,7 +4,7 @@
 <!-- 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.69 
2008/01/31 14:37:51 jkt Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.70 
2008/01/31 21:30:23 jkt Exp $ -->
 
 <sections>
 
@@ -13,7 +13,7 @@
 maintain the software on his system.
 </abstract>
 
-<version>1.62</version>
+<version>1.63</version>
 <date>2008-01-31</date>
 
 <section>
@@ -635,8 +635,13 @@
 </p>
 
 <pre caption="Digest verification failure">
-&gt;&gt;&gt; checking ebuild checksums
+&gt;&gt;&gt; Verifying ebuild Manifests...
+
 !!! Digest verification failed:
+!!! /usr/portage/virtual/c++-tr1-memory/c++-tr1-memory-0.ebuild
+!!! Reason: Failed on MD5 verification
+!!! Got: cccc4738cc08ac3c67b14932c85d7cb2
+!!! Expected: cccc4738cc08ac3c67b14932c85d7cb3
 </pre>
 
 <p>



-- 
[email protected] mailing list

Reply via email to