/[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.61
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.61 2006/11/12 21:28:30 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<abstract>
12This chapter explains the "simple" steps a user definitely needs to know to
13maintain the software on his system.
14</abstract>
15
11<version>1.49</version> 16<version>1.55</version>
12<date>2005-06-11</date> 17<date>2006-11-12</date>
13 18
14<section> 19<section>
15<title>Welcome to Portage</title> 20<title>Welcome to Portage</title>
16<body> 21<body>
17 22
197</pre> 202</pre>
198 203
199<p> 204<p>
200You can enable or disable the <c>doc</c> USE flag either globally in the 205You 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 206<path>/etc/make.conf</path> file or per package in the
202<path>/etc/portage/package.use</path> file. The <uri 207<path>/etc/portage/package.use</path> file. You can also create a directory
208called <path>/etc/portage/package.use</path> and list it in a file inside this
209directory. The <uri
203link="?part=2&amp;chap=2">USE Flags</uri> chapter covers this aspect in detail. 210link="?part=2&amp;chap=2">USE Flags</uri> chapter covers this aspect in detail.
204</p> 211</p>
205 212
206<p> 213<p>
207Once the package installed, its documentation is generally found in a 214Once the package installed, its documentation is generally found in a
272<p> 279<p>
273To keep your system in perfect shape (and not to mention install the latest 280To 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 281security 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 282checks 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 283tree. When your Portage tree is updated, you can update your system with
277<c>emerge --update world</c>: 284<c>emerge --update world</c>. In the next example, we'll also use the
285<c>--ask</c> switch which will tell Portage to display the list of packages it
286wants to upgrade and ask you if you want to continue:
278</p> 287</p>
279 288
280<pre caption="Updating your system"> 289<pre caption="Updating your system">
281# <i>emerge --update world</i> 290# <i>emerge --update --ask world</i>
282</pre> 291</pre>
283 292
284<p> 293<p>
285Portage will then search for newer version of the applications you have 294Portage will then search for newer version of the applications you have
286installed. However, it will only verify the versions for the applications you 295installed. However, it will only verify the versions for the applications you
287have explicitly installed - not the dependencies. If you want to update every 296have <e>explicitly</e> installed (the applications listed in
288single package on your system, add the <c>--deep</c> argument: 297<path>/var/lib/portage/world</path>) - it does not thoroughly check their
298dependencies. If you want to update <e>every single package</e> on your system,
299add the <c>--deep</c> argument:
289</p> 300</p>
290 301
291<pre caption="Updating your entire system"> 302<pre caption="Updating your entire system">
292# <i>emerge --update --deep world</i> 303# <i>emerge --update --deep world</i>
293</pre> 304</pre>
418<subsection id="blocked"> 429<subsection id="blocked">
419<title>Blocked Packages</title> 430<title>Blocked Packages</title>
420<body> 431<body>
421 432
422<pre caption="Portage warning about blocked packages (with --pretend)"> 433<pre caption="Portage warning about blocked packages (with --pretend)">
423[blocks B ] gnome-base/bonobo-activation (from pkg gnome-base/libbonobo-2.4.0) 434[blocks B ] mail-mta/ssmtp (is blocking mail-mta/postfix-2.2.2-r1)
424</pre> 435</pre>
425 436
426<pre caption="Portage warning about blocked packages (without --pretend)"> 437<pre caption="Portage warning about blocked packages (without --pretend)">
427!!! Error: the gnome-base/bonobo-activation package conflicts with another package. 438!!! Error: the mail-mta/postfix package conflicts with another package.
428!!! both can't be installed on the same system together. 439!!! both can't be installed on the same system together.
429!!! Please use 'emerge --pretend' to determine blockers. 440!!! Please use 'emerge --pretend' to determine blockers.
430</pre> 441</pre>
431 442
432<p> 443<p>
438</p> 449</p>
439 450
440<p> 451<p>
441To fix a blockage, you can choose to not install the package or unmerge the 452To 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 453conflicting package first. In the given example, you can opt not to install
443<c>libbonobo</c> or to remove <c>bonobo-activation</c> first. 454<c>postfix</c> or to remove <c>ssmtp</c> first.
455</p>
456
457<p>
458It is also possible that two packages that are yet to be installed are blocking
459each other. In this rare case, you should find out why you need to install both.
460In most cases you can do with one of the packages alone. If not, please file a
461bug on <uri link="http://bugs.gentoo.org">Gentoo's bugtracking system</uri>.
444</p> 462</p>
445 463
446</body> 464</body>
447</subsection> 465</subsection>
448<subsection id="masked"> 466<subsection id="masked">
601from the system. 619from the system.
602</p> 620</p>
603 621
604</body> 622</body>
605</subsection> 623</subsection>
624<subsection id="digesterror">
625<title>Digest Verification Failures</title>
626<body>
627
628<p>
629Sometimes, when you attempt to emerge a package, it will fail with the message:
630</p>
631
632<pre caption="Digest verification failure">
633&gt;&gt;&gt; checking ebuild checksums
634!!! Digest verification failed:
635</pre>
636
637<p>
638This is a sign that something is wrong with the Portage tree -- often, it is
639because a developer may have made a mistake when committing a package to the
640tree.
641</p>
642
643<p>
644When the digest verification fails, do <e>not</e> try to re-digest the package
645yourself. Running <c>ebuild foo digest</c> will not fix the problem; it will
646almost certainly make it worse!
647</p>
648
649<p>
650Instead, wait an hour or two for the tree to settle down. It's likely that the
651error was noticed right away, but it can take a little time for the fix to
652trickle down the Portage tree. While you're waiting, check <uri
653link="http://bugs.gentoo.org">Bugzilla</uri> and see if anyone has reported
654the problem yet. If not, go ahead and file a bug for the broken package.
655</p>
656
657<p>
658Once you see that the bug has been fixed, you may want to re-sync to pick up
659the fixed digest.
660</p>
661
662<impo>
663This does <e>not</e> mean that you can re-sync your tree multiple times! As
664stated in the rsync policy (when you run <c>emerge --sync</c>), users who sync
665too often will be banned! In fact, it's better to just wait until your next
666scheduled sync, so that you don't overload the rsync servers.
667</impo>
668
669</body>
670</subsection>
606</section> 671</section>
607</sections> 672</sections>

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

  ViewVC Help
Powered by ViewVC 1.1.20