/[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.54 Revision 1.59
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
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.0 --> 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.54 2005/06/11 12:16:14 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.49</version> 11<version>1.54</version>
12<date>2005-06-11</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
197</pre> 197</pre>
198 198
199<p> 199<p>
200You can enable or disable the <c>doc</c> USE flag either globally in the 200You can enable or disable the <c>doc</c> USE flag either globally in the
201<path>/etc/make.conf</path> file or per package in the 201<path>/etc/make.conf</path> file or per package in the
202<path>/etc/portage/package.use</path> file. The <uri 202<path>/etc/portage/package.use</path> file. You can also create a directory
203called <path>/etc/portage/package.use</path> and list it in a file inside this
204directory. The <uri
203link="?part=2&amp;chap=2">USE Flags</uri> chapter covers this aspect in detail. 205link="?part=2&amp;chap=2">USE Flags</uri> chapter covers this aspect in detail.
204</p> 206</p>
205 207
206<p> 208<p>
207Once the package installed, its documentation is generally found in a 209Once the package installed, its documentation is generally found in a
272<p> 274<p>
273To keep your system in perfect shape (and not to mention install the latest 275To keep your system in perfect shape (and not to mention install the latest
274security updates) you need to update your system regularly. Since Portage only 276security updates) you need to update your system regularly. Since Portage only
275checks the ebuilds in your Portage tree you first have to update your Portage 277checks the ebuilds in your Portage tree you first have to update your Portage
276tree. When your Portage tree is updated, you can update your system with 278tree. When your Portage tree is updated, you can update your system with
277<c>emerge --update world</c>: 279<c>emerge --update world</c>. In the next example, we'll also use the
280<c>--ask</c> switch which will tell Portage to display the list of packages it
281wants to upgrade and ask you if you want to continue:
278</p> 282</p>
279 283
280<pre caption="Updating your system"> 284<pre caption="Updating your system">
281# <i>emerge --update world</i> 285# <i>emerge --update --ask world</i>
282</pre> 286</pre>
283 287
284<p> 288<p>
285Portage will then search for newer version of the applications you have 289Portage will then search for newer version of the applications you have
286installed. However, it will only verify the versions for the applications you 290installed. However, it will only verify the versions for the applications you
418<subsection id="blocked"> 422<subsection id="blocked">
419<title>Blocked Packages</title> 423<title>Blocked Packages</title>
420<body> 424<body>
421 425
422<pre caption="Portage warning about blocked packages (with --pretend)"> 426<pre caption="Portage warning about blocked packages (with --pretend)">
423[blocks B ] gnome-base/bonobo-activation (from pkg gnome-base/libbonobo-2.4.0) 427[blocks B ] mail-mta/ssmtp (is blocking mail-mta/postfix-2.2.2-r1)
424</pre> 428</pre>
425 429
426<pre caption="Portage warning about blocked packages (without --pretend)"> 430<pre caption="Portage warning about blocked packages (without --pretend)">
427!!! Error: the gnome-base/bonobo-activation package conflicts with another package. 431!!! Error: the mail-mta/postfix package conflicts with another package.
428!!! both can't be installed on the same system together. 432!!! both can't be installed on the same system together.
429!!! Please use 'emerge --pretend' to determine blockers. 433!!! Please use 'emerge --pretend' to determine blockers.
430</pre> 434</pre>
431 435
432<p> 436<p>
438</p> 442</p>
439 443
440<p> 444<p>
441To fix a blockage, you can choose to not install the package or unmerge the 445To fix a blockage, you can choose to not install the package or unmerge the
442conflicting package first. In the given example, you can opt not to install 446conflicting package first. In the given example, you can opt not to install
443<c>libbonobo</c> or to remove <c>bonobo-activation</c> first. 447<c>postfix</c> or to remove <c>ssmtp</c> first.
448</p>
449
450<p>
451It is also possible that two packages that are yet to be installed are blocking
452each other. In this rare case, you should find out why you need to install both.
453In most cases you can do with one of the packages alone. If not, please file a
454bug on <uri link="http://bugs.gentoo.org">Gentoo's bugtracking system</uri>.
444</p> 455</p>
445 456
446</body> 457</body>
447</subsection> 458</subsection>
448<subsection id="masked"> 459<subsection id="masked">
601from the system. 612from the system.
602</p> 613</p>
603 614
604</body> 615</body>
605</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>
606</section> 664</section>
607</sections> 665</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20