public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Damian Kuras (shadow)" <shadow@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/doc/pl/handbook: hb-working-portage.xml
Date: Fri, 01 Feb 2008 11:32:21 +0000	[thread overview]
Message-ID: <E1JKu85-00061A-Cu@stork.gentoo.org> (raw)

shadow      08/02/01 11:32:21

  Modified:             hb-working-portage.xml
  Log:
  sync to 1.70

Revision  Changes    Path
1.26                 xml/htdocs/doc/pl/handbook/hb-working-portage.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/handbook/hb-working-portage.xml?rev=1.26&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/handbook/hb-working-portage.xml?rev=1.26&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/pl/handbook/hb-working-portage.xml?r1=1.25&r2=1.26

Index: hb-working-portage.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/pl/handbook/hb-working-portage.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- hb-working-portage.xml	10 Nov 2007 15:02:12 -0000	1.25
+++ hb-working-portage.xml	1 Feb 2008 11:32:20 -0000	1.26
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/handbook/hb-working-portage.xml,v 1.25 2007/11/10 15:02:12 shadow Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/pl/handbook/hb-working-portage.xml,v 1.26 2008/02/01 11:32:20 shadow Exp $ -->
 
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
@@ -12,8 +12,8 @@
 skutecznie zarządzać systemem.
 </abstract>
 
-<version>1.61</version>
-<date>2007-11-01</date>
+<version>1.63</version>
+<date>2008-01-31</date>
 
 <section>
 <title>Witamy w Portage</title>
@@ -657,8 +657,13 @@
 </p>
 
 <pre caption="Błąd sprawdzania sumy kontrolnej">
-&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>
@@ -668,7 +673,7 @@
 
 <p>
 Kiedy zobaczymy taki błąd <e>nie</e> należy samemu tworzyć nowych sum
-kontrolnych. Wydanie polecenia <c>ebuild foo digest</c> nie sprawi, ze
+kontrolnych. Wydanie polecenia <c>ebuild foo manifest</c> nie sprawi, ze
 naprawimy problem, możemy go nawet pogłębić!
 </p>
 



-- 
gentoo-commits@lists.gentoo.org mailing list



             reply	other threads:[~2008-02-01 11:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 11:32 Damian Kuras (shadow) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-06-27 18:17 [gentoo-commits] gentoo commit in xml/htdocs/doc/pl/handbook: hb-working-portage.xml Damian Kuras (shadow)
2010-06-27 17:57 Damian Kuras (shadow)
2008-12-26 12:50 Damian Kuras (shadow)
2008-03-03  0:57 Lukasz Damentko (rane)
2007-11-10 15:02 Damian Kuras (shadow)
2007-10-22 12:04 Damian Kuras (shadow)
2007-09-24  1:25 Lukasz Damentko (rane)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1JKu85-00061A-Cu@stork.gentoo.org \
    --to=shadow@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox