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