/[gentoo]/xml/htdocs/doc/en/handbook/hb-working-portage.xml
Gentoo

Contents of /xml/htdocs/doc/en/handbook/hb-working-portage.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.75 - (show annotations) (download) (as text)
Sat Oct 30 01:54:20 2010 UTC (3 years, 11 months ago) by nightmorph
Branch: MAIN
Changes since 1.74: +6 -6 lines
File MIME type: application/xml
Update license_group location, bug 343279

1 <?xml version='1.0' encoding='UTF-8'?>
2 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4 <!-- The content of this document is licensed under the CC-BY-SA license -->
5 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6
7 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.74 2010/03/03 00:36:42 nightmorph Exp $ -->
8
9 <sections>
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
16 <version>2</version>
17 <date>2010-10-29</date>
18
19 <section>
20 <title>Welcome to Portage</title>
21 <body>
22
23 <p>
24 Portage is probably Gentoo's most notable innovation in software management.
25 With its high flexibility and enormous amount of features it is frequently seen
26 as the best software management tool available for Linux.
27 </p>
28
29 <p>
30 Portage is completely written in <uri link="http://www.python.org">Python</uri>
31 and <uri link="http://www.gnu.org/software/bash">Bash</uri> and therefore fully
32 visible to the users as both are scripting languages.
33 </p>
34
35 <p>
36 Most users will work with Portage through the <c>emerge</c> tool. This chapter
37 is not meant to duplicate the information available from the emerge man page.
38 For a complete rundown of emerge's options, please consult the man page:
39 </p>
40
41 <pre caption="Reading the emerge man page">
42 $ <i>man emerge</i>
43 </pre>
44
45 </body>
46 </section>
47 <section>
48 <title>The Portage Tree</title>
49 <subsection>
50 <title>Ebuilds</title>
51 <body>
52
53 <p>
54 When we talk about packages, we often mean software titles that are available to
55 the Gentoo users through the Portage tree. The Portage tree is a collection of
56 <e>ebuilds</e>, files that contain all information Portage needs to maintain
57 software (install, search, query, ...). These ebuilds reside in
58 <path>/usr/portage</path> by default.
59 </p>
60
61 <p>
62 Whenever you ask Portage to perform some action regarding software titles, it
63 will use the ebuilds on your system as a base. It is therefore important that
64 you regularly update the ebuilds on your system so Portage knows about new
65 software, security updates, etc.
66 </p>
67
68 </body>
69 </subsection>
70 <subsection>
71 <title>Updating the Portage Tree</title>
72 <body>
73
74 <p>
75 The Portage tree is usually updated with <uri
76 link="http://rsync.samba.org/">rsync</uri>, a fast incremental file transfer
77 utility. Updating is fairly simple as the <c>emerge</c> command provides a
78 front-end for rsync:
79 </p>
80
81 <pre caption="Updating the Portage tree">
82 # <i>emerge --sync</i>
83 </pre>
84
85 <p>
86 If you are unable to rsync due to firewall restrictions you can still update
87 your Portage tree by using our daily generated Portage tree snapshots. The
88 <c>emerge-webrsync</c> tool automatically fetches and installs the latest
89 snapshot on your system:
90 </p>
91
92 <pre caption="Running emerge-webrsync">
93 # <i>emerge-webrsync</i>
94 </pre>
95
96 </body>
97 </subsection>
98 </section>
99 <section>
100 <title>Maintaining Software</title>
101 <subsection>
102 <title>Searching for Software</title>
103 <body>
104
105 <p>
106 To search through the Portage tree after software titles, you can use
107 <c>emerge</c> built-in search capabilities. By default, <c>emerge --search</c>
108 returns the names of packages whose title matches (either fully or partially)
109 the given search term.
110 </p>
111
112 <p>
113 For instance, to search for all packages who have "pdf" in their name:
114 </p>
115
116 <pre caption="Searching for pdf-named packages">
117 $ <i>emerge --search pdf</i>
118 </pre>
119
120 <p>
121 If you want to search through the descriptions as well you can use the
122 <c>--searchdesc</c> (or <c>-S</c>) switch:
123 </p>
124
125 <pre caption="Searching for pdf-related packages">
126 $ <i>emerge --searchdesc pdf</i>
127 </pre>
128
129 <p>
130 When you take a look at the output, you'll notice that it gives you a lot of
131 information. The fields are clearly labelled so we won't go further into their
132 meanings:
133 </p>
134
135 <pre caption="Example 'emerge --search' output">
136 * net-print/cups-pdf
137 Latest version available: 1.5.2
138 Latest version installed: [ Not Installed ]
139 Size of downloaded files: 15 kB
140 Homepage: http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/
141 Description: Provides a virtual printer for CUPS to produce PDF files.
142 License: GPL-2
143 </pre>
144
145 </body>
146 </subsection>
147 <subsection>
148 <title>Installing Software</title>
149 <body>
150
151 <p>
152 Once you've found a software title to your liking, you can easily install it
153 with <c>emerge</c>: just add the package name. For instance, to install
154 <c>gnumeric</c>:
155 </p>
156
157 <pre caption="Installing gnumeric">
158 # <i>emerge gnumeric</i>
159 </pre>
160
161 <p>
162 Since many applications depend on each other, any attempt to install a certain
163 software package might result in the installation of several dependencies as
164 well. Don't worry, Portage handles dependencies well. If you want to find out
165 what Portage <e>would</e> install when you ask it to install a certain package,
166 add the <c>--pretend</c> switch. For instance:
167 </p>
168
169 <pre caption="Pretend to install gnumeric">
170 # <i>emerge --pretend gnumeric</i>
171 </pre>
172
173 <p>
174 When you ask Portage to install a package, it will download the necessary source
175 code from the internet (if necessary) and store it by default in
176 <path>/usr/portage/distfiles</path>. After this it will unpack, compile and
177 install the package. If you want Portage to only download the sources without
178 installing them, add the <c>--fetchonly</c> option to the <c>emerge</c> command:
179 </p>
180
181 <pre caption="Download the sourcecode for gnumeric">
182 # <i>emerge --fetchonly gnumeric</i>
183 </pre>
184
185 </body>
186 </subsection>
187 <subsection>
188 <title>Finding Installed Package Documentation</title>
189 <body>
190
191 <p>
192 Many packages come with their own documentation. Sometimes, the <c>doc</c> USE
193 flag determines whether the package documentation should be installed or not.
194 You can check the existence of a <c>doc</c> USE flag with the <c>emerge -vp
195 &lt;package name&gt;</c> command.
196 </p>
197
198 <pre caption="Checking the existence of a doc USE flag">
199 <comment>(alsa-lib is just an example, of course.)</comment>
200 # <i>emerge -vp alsa-lib</i>
201 [ebuild N ] media-libs/alsa-lib-1.0.14_rc1 -debug +doc 698 kB
202 </pre>
203
204 <p>
205 The best way of enabling the <c>doc</c> USE flag is doing it on a per-package
206 basis via <path>/etc/portage/package.use</path>, so that you get documentation
207 only for packages that you are interested in. Enabling this flag globally is
208 known to cause problems with circular dependencies. For more information, please
209 read the <uri link="?part=2&amp;chap=2">USE Flags</uri> chapter.
210 </p>
211
212 <p>
213 Once the package installed, its documentation is generally found in a
214 subdirectory named after the package under the <path>/usr/share/doc</path>
215 directory. You can also list all installed files with the <c>equery</c> tool
216 which is part of the <c>app-portage/gentoolkit</c> <uri
217 link="/doc/en/gentoolkit.xml">package</uri>.
218 </p>
219
220 <pre caption="Locating package documentation">
221 # <i>ls -l /usr/share/doc/alsa-lib-1.0.14_rc1</i>
222 total 28
223 -rw-r--r-- 1 root root 669 May 17 21:54 ChangeLog.gz
224 -rw-r--r-- 1 root root 9373 May 17 21:54 COPYING.gz
225 drwxr-xr-x 2 root root 8560 May 17 21:54 html
226 -rw-r--r-- 1 root root 196 May 17 21:54 TODO.gz
227
228 <comment>(Alternatively, use equery to locate interesting files:)</comment>
229 # <i>equery files alsa-lib | less</i>
230 media-libs/alsa-lib-1.0.14_rc1
231 * Contents of media-libs/alsa-lib-1.0.14_rc1:
232 /usr
233 /usr/bin
234 /usr/bin/alsalisp
235 <comment>(Output truncated)</comment>
236 </pre>
237
238 </body>
239 </subsection>
240 <subsection>
241 <title>Removing Software</title>
242 <body>
243
244 <p>
245 When you want to remove a software package from your system, use <c>emerge
246 --unmerge</c>. This will tell Portage to remove all files installed by that
247 package from your system <e>except</e> the configuration files of that
248 application if you have altered those after the installation. Leaving the
249 configuration files allows you to continue working with the package if you ever
250 decide to install it again.
251 </p>
252
253 <p>
254 However, a <brite>big warning</brite> applies: Portage will <e>not</e> check if
255 the package you want to remove is required by another package. It will however
256 warn you when you want to remove an important package that breaks your system
257 if you unmerge it.
258 </p>
259
260 <pre caption="Removing gnumeric from the system">
261 # <i>emerge --unmerge gnumeric</i>
262 </pre>
263
264 <p>
265 When you remove a package from your system, the dependencies of that package
266 that were installed automatically when you installed the software are left. To
267 have Portage locate all dependencies that can now be removed, use
268 <c>emerge</c>'s <c>--depclean</c> functionality. We will talk about this later
269 on.
270 </p>
271
272 </body>
273 </subsection>
274 <subsection>
275 <title>Updating your System</title>
276 <body>
277
278 <p>
279 To keep your system in perfect shape (and not to mention install the latest
280 security updates) you need to update your system regularly. Since Portage only
281 checks the ebuilds in your Portage tree you first have to update your Portage
282 tree. When your Portage tree is updated, you can update your system with
283 <c>emerge --update world</c>. In the next example, we'll also use the
284 <c>--ask</c> switch which will tell Portage to display the list of packages it
285 wants to upgrade and ask you if you want to continue:
286 </p>
287
288 <pre caption="Updating your system">
289 # <i>emerge --update --ask world</i>
290 </pre>
291
292 <p>
293 Portage will then search for newer version of the applications you have
294 installed. However, it will only verify the versions for the applications you
295 have <e>explicitly</e> installed (the applications listed in
296 <path>/var/lib/portage/world</path>) - it does not thoroughly check their
297 dependencies. If you want to update <e>every single package</e> on your system,
298 add the <c>--deep</c> argument:
299 </p>
300
301 <pre caption="Updating your entire system">
302 # <i>emerge --update --deep world</i>
303 </pre>
304
305 <p>
306 Since security updates also happen in packages you have not explicitly installed
307 on your system (but that are pulled in as dependencies of other programs), it
308 is recommended to run this command once in a while.
309 </p>
310
311 <p>
312 If you have altered any of your <uri link="?part=2&amp;chap=2">USE flags</uri>
313 lately you might want to add <c>--newuse</c> as well. Portage will then verify
314 if the change requires the installation of new packages or recompilation of
315 existing ones:
316 </p>
317
318 <pre caption="Performing a full update">
319 # <i>emerge --update --deep --newuse world</i>
320 </pre>
321
322 </body>
323 </subsection>
324 <subsection>
325 <title>Metapackages</title>
326 <body>
327
328 <p>
329 Some packages in the Portage tree don't have any real content but are used to
330 install a collection of packages. For instance, the <c>kde-meta</c> package will
331 install a complete KDE environment on your system by pulling in various
332 KDE-related packages as dependencies.
333 </p>
334
335 <p>
336 If you ever want to remove such a package from your system, running <c>emerge
337 --unmerge</c> on the package won't have much effect as the dependencies remain
338 on the system.
339 </p>
340
341 <p>
342 Portage has the functionality to remove orphaned dependencies as well, but since
343 the availability of software is dynamically dependent you first need to update
344 your entire system fully, including the new changes you applied when changing
345 USE flags. After this you can run <c>emerge --depclean</c> to remove the
346 orphaned dependencies. When this is done, you need to rebuild the applications
347 that were dynamically linked to the now-removed software titles but don't
348 require them anymore.
349 </p>
350
351 <p>
352 All this is handled with the following three commands:
353 </p>
354
355 <pre caption="Removing orphaned dependencies">
356 # <i>emerge --update --deep --newuse world</i>
357 # <i>emerge --depclean</i>
358 # <i>revdep-rebuild</i>
359 </pre>
360
361 <p>
362 <c>revdep-rebuild</c> is provided by the <c>gentoolkit</c> package; don't forget
363 to emerge it first:
364 </p>
365
366 <pre caption="Installing the gentoolkit package">
367 # <i>emerge gentoolkit</i>
368 </pre>
369
370 </body>
371 </subsection>
372 </section>
373 <section id="license">
374 <title>Licenses</title>
375 <subsection>
376 <body>
377
378 <p>
379 Beginning with Portage version 2.1.7, you can accept or reject software
380 installation based on its license. All packages in the tree contain a
381 <c>LICENSE</c> entry in their ebuilds. Running <c>emerge --search
382 packagename</c> will tell you the package's license.
383 </p>
384
385 <p>
386 By default, Portage permits all licenses, except End User License Agreements
387 (EULAs) that require reading and signing an acceptance agreement.
388 </p>
389
390 <p>
391 The variable that controls permitted licenses is <c>ACCEPT_LICENSE</c>, which
392 can be set in <path>/etc/make.conf</path>:
393 </p>
394
395 <pre caption="Default ACCEPT_LICENSE in /etc/make.conf">
396 ACCEPT_LICENSE="* -@EULA"
397 </pre>
398
399 <p>
400 With this configuration, packages that require interaction during installation
401 to approve their EULA <e>will not</e> be installed. Packages without an EULA
402 <e>will</e> be installed.
403 </p>
404
405 <p>
406 You can set <c>ACCEPT_LICENSE</c> globally in <path>/etc/make.conf</path>, or
407 you can specify it on a per-package basis in
408 <path>/etc/portage/package.license</path>.
409 </p>
410
411 <p>
412 For example, if you want to allow the <c>truecrypt-2.7</c> license for
413 <c>app-crypt/truecrypt</c>, add the following to
414 <path>/etc/portage/package.license</path>:
415 </p>
416
417 <pre caption="Specifying a truecrypt license in package.license">
418 app-crypt/truecrypt truecrypt-2.7
419 </pre>
420
421 <p>
422 This permits installation of truecrypt versions that have the
423 <c>truecrypt-2.7</c> license, but not versions with the <c>truecrypt-2.8</c>
424 license.
425 </p>
426
427 <impo>
428 Licenses are stored in <path>/usr/portage/licenses</path>, and license groups
429 are kept in <path>/usr/portage/profiles/license_groups</path>. The first entry
430 of each line in CAPITAL letters is the name of the license group, and every
431 entry after that is an individual license.
432 </impo>
433
434 <p>
435 License groups defined in <c>ACCEPT_LICENSE</c> are prefixed with an <b>@</b>
436 sign. Here's an example of a system that globally permits the GPL-compatible
437 license group, as well as a few other groups and individual licenses:
438 </p>
439
440 <pre caption="ACCEPT_LICENSE in /etc/make.conf">
441 ACCEPT_LICENSE="@GPL-COMPATIBLE @OSI-APPROVED @EULA atheros-hal BitstreamVera"
442 </pre>
443
444 <p>
445 If you want only free software and documentation on your system, you might use
446 the following setup:
447 </p>
448
449 <pre caption="Use only free licenses">
450 ACCEPT_LICENSE="-* @FREE"
451 </pre>
452
453 <p>
454 In this case, "free" is mostly defined by the <uri
455 link="http://www.gnu.org/philosophy/free-sw.html">FSF</uri> and <uri
456 link="http://www.opensource.org/docs/osd">OSI</uri>. Any package whose license
457 does not meet these requirements will not be installed on your system.
458 </p>
459
460 </body>
461 </subsection>
462 </section>
463 <section>
464 <title>When Portage is Complaining...</title>
465 <subsection>
466 <title>About SLOTs, Virtuals, Branches, Architectures and Profiles</title>
467 <body>
468
469 <p>
470 As we stated before, Portage is extremely powerful and supports many features
471 that other software management tools lack. To understand this, we explain a few
472 aspects of Portage without going into too much detail.
473 </p>
474
475 <p>
476 With Portage different versions of a single package can coexist on a system.
477 While other distributions tend to name their package to those versions (like
478 <c>freetype</c> and <c>freetype2</c>) Portage uses a technology called
479 <e>SLOT</e>s. An ebuild declares a certain SLOT for its version. Ebuilds with
480 different SLOTs can coexist on the same system. For instance, the
481 <c>freetype</c> package has ebuilds with <c>SLOT="1"</c> and <c>SLOT="2"</c>.
482 </p>
483
484 <p>
485 There are also packages that provide the same functionality but are implemented
486 differently. For instance, <c>metalogd</c>, <c>sysklogd</c> and <c>syslog-ng</c>
487 are all system loggers. Applications that rely on the availability of "a system
488 logger" cannot depend on, for instance, <c>metalogd</c>, as the other system
489 loggers are as good a choice as any. Portage allows for <e>virtuals</e>: each
490 system logger provides <c>virtual/syslog</c> so that applications can depend on
491 <c>virtual/syslog</c>.
492 </p>
493
494 <p>
495 Software in the Portage tree can reside in different branches. By default your
496 system only accepts packages that Gentoo deems stable. Most new software titles,
497 when committed, are added to the testing branch, meaning more testing needs to
498 be done before it is marked as stable. Although you will see the ebuilds for
499 those software in the Portage tree, Portage will not update them before they are
500 placed in the stable branch.
501 </p>
502
503 <p>
504 Some software is only available for a few architectures. Or the software doesn't
505 work on the other architectures, or it needs more testing, or the developer that
506 committed the software to the Portage tree is unable to verify if the package
507 works on different architectures.
508 </p>
509
510 <p>
511 Each Gentoo installation adheres to a certain <c>profile</c> which contains,
512 amongst other information, the list of packages that are required for a system
513 to function normally.
514 </p>
515
516 </body>
517 </subsection>
518 <subsection id="blocked">
519 <title>Blocked Packages</title>
520 <body>
521
522 <pre caption="Portage warning about blocked packages (with --pretend)">
523 [blocks B ] mail-mta/ssmtp (is blocking mail-mta/postfix-2.2.2-r1)
524 </pre>
525
526 <pre caption="Portage warning about blocked packages (without --pretend)">
527 !!! Error: the mail-mta/postfix package conflicts with another package.
528 !!! both can't be installed on the same system together.
529 !!! Please use 'emerge --pretend' to determine blockers.
530 </pre>
531
532 <p>
533 Ebuilds contain specific fields that inform Portage about its dependencies.
534 There are two possible dependencies: build dependencies, declared in
535 <c>DEPEND</c> and run-time dependencies, declared in <c>RDEPEND</c>. When one of
536 these dependencies explicitly marks a package or virtual as being <e>not</e>
537 compatible, it triggers a blockage.
538 </p>
539
540 <p>
541 While recent versions of Portage are smart enough to work around minor blockages
542 without user intervention, occasionally you will need to fix it yourself, as
543 explained below.
544 </p>
545
546 <p>
547 To fix a blockage, you can choose to not install the package or unmerge the
548 conflicting package first. In the given example, you can opt not to install
549 <c>postfix</c> or to remove <c>ssmtp</c> first.
550 </p>
551
552 <p>
553 You may also see blocking packages with specific atoms, such as
554 <b>&lt;</b>media-video/mplayer-1.0_rc1-r2. In this case, updating to a more
555 recent version of the blocking package would remove the block.
556 </p>
557
558 <p>
559 It is also possible that two packages that are yet to be installed are blocking
560 each other. In this rare case, you should find out why you need to install both.
561 In most cases you can do with one of the packages alone. If not, please file a
562 bug on <uri link="http://bugs.gentoo.org">Gentoo's bugtracking system</uri>.
563 </p>
564
565 </body>
566 </subsection>
567 <subsection id="masked">
568 <title>Masked Packages</title>
569 <body>
570
571 <pre caption="Portage warning about masked packages">
572 !!! all ebuilds that could satisfy "bootsplash" have been masked.
573 </pre>
574
575 <pre caption="Portage warning about masked packages - reason">
576 !!! possible candidates are:
577
578 - gnome-base/gnome-2.8.0_pre1 (masked by: <i>~x86 keyword</i>)
579 - lm-sensors/lm-sensors-2.8.7 (masked by: <i>-sparc keyword</i>)
580 - sys-libs/glibc-2.3.4.20040808 (masked by: <i>-* keyword</i>)
581 - dev-util/cvsd-1.0.2 (masked by: <i>missing keyword</i>)
582 - games-fps/unreal-tournament-451 (masked by: <i>package.mask</i>)
583 - sys-libs/glibc-2.3.2-r11 (masked by: <i>profile</i>)
584 - net-im/skype-2.1.0.81 (masked by: skype-eula <i>license</i>(s))
585 </pre>
586
587 <p>
588 When you want to install a package that isn't available for your system, you
589 will receive this masking error. You should try installing a different
590 application that is available for your system or wait until the package is put
591 available. There is always a reason why a package is masked:
592 </p>
593
594 <ul>
595 <li>
596 <b>~arch keyword</b> means that the application is not tested sufficiently
597 to be put in the stable branch. Wait a few days or weeks and try again.
598 </li>
599 <li>
600 <b>-arch keyword</b> or <b>-* keyword</b> means that the application does
601 not work on your architecture. If you believe the package does work file
602 a bug at our <uri link="http://bugs.gentoo.org">bugzilla</uri> website.
603 </li>
604 <li>
605 <b>missing keyword</b> means that the application has not been tested on
606 your architecture yet. Ask the architecture porting team to test the package
607 or test it for them and report your findings on our <uri
608 link="http://bugs.gentoo.org">bugzilla</uri> website.
609 </li>
610 <li>
611 <b>package.mask</b> means that the package has been found corrupt, unstable
612 or worse and has been deliberately marked as do-not-use.
613 </li>
614 <li>
615 <b>profile</b> means that the package has been found not suitable for your
616 profile. The application might break your system if you installed it or is
617 just not compatible with the profile you use.
618 </li>
619 <li>
620 <b>license</b> means that the package's license is not compatible with your
621 <c>ACCEPT_LICENSE</c> setting. You must explicitly permit its license or
622 license group by setting it in <path>/etc/make.conf</path> or in
623 <path>/etc/portage/package.license</path>. Refer to <uri
624 link="#license">Licenses</uri> to learn how licenses work.
625 </li>
626 </ul>
627
628 </body>
629 </subsection>
630 <subsection id="missingdependencies">
631 <title>Missing Dependencies</title>
632 <body>
633
634 <pre caption="Portage warning about missing dependency">
635 emerge: there are no ebuilds to satisfy "&gt;=sys-devel/gcc-3.4.2-r4".
636
637 !!! Problem with ebuild sys-devel/gcc-3.4.2-r2
638 !!! Possibly a DEPEND/*DEPEND problem.
639 </pre>
640
641 <p>
642 The application you are trying to install depends on another package that is not
643 available for your system. Please check <uri
644 link="http://bugs.gentoo.org">bugzilla</uri> if the issue is known and if not,
645 please report it. Unless you are mixing branches this should not occur and is
646 therefore a bug.
647 </p>
648
649 </body>
650 </subsection>
651 <subsection id="ambiguousebuild">
652 <title>Ambiguous Ebuild Name</title>
653 <body>
654
655 <pre caption="Portage warning about ambiguous ebuild names">
656 [ Results for search key : listen ]
657 [ Applications found : 2 ]
658
659 * dev-tinyos/listen [ Masked ]
660 Latest version available: 1.1.15
661 Latest version installed: [ Not Installed ]
662 Size of files: 10,032 kB
663 Homepage: http://www.tinyos.net/
664 Description: Raw listen for TinyOS
665 License: BSD
666
667 * media-sound/listen [ Masked ]
668 Latest version available: 0.6.3
669 Latest version installed: [ Not Installed ]
670 Size of files: 859 kB
671 Homepage: http://www.listen-project.org
672 Description: A Music player and management for GNOME
673 License: GPL-2
674
675 !!! The short ebuild name "listen" is ambiguous. Please specify
676 !!! one of the above fully-qualified ebuild names instead.
677 </pre>
678
679 <p>
680 The application you want to install has a name that corresponds with more than
681 one package. You need to supply the category name as well. Portage will inform
682 you of possible matches to choose from.
683 </p>
684
685 </body>
686 </subsection>
687 <subsection id="circulardependencies">
688 <title>Circular Dependencies</title>
689 <body>
690
691 <pre caption="Portage warning about circular dependencies">
692 !!! Error: circular dependencies:
693
694 ebuild / net-print/cups-1.1.15-r2 depends on ebuild / app-text/ghostscript-7.05.3-r1
695 ebuild / app-text/ghostscript-7.05.3-r1 depends on ebuild / net-print/cups-1.1.15-r2
696 </pre>
697
698 <p>
699 Two (or more) packages you want to install depend on each other and can
700 therefore not be installed. This is most likely a bug in the Portage tree.
701 Please resync after a while and try again. You can also check <uri
702 link="http://bugs.gentoo.org">bugzilla</uri> if the issue is known and if not,
703 report it.
704 </p>
705
706 </body>
707 </subsection>
708 <subsection id="fetchfailed">
709 <title>Fetch failed</title>
710 <body>
711
712 <pre caption="Portage warning about fetch failed">
713 !!! Fetch failed for sys-libs/ncurses-5.4-r5, continuing...
714 <comment>(...)</comment>
715 !!! Some fetch errors were encountered. Please see above for details.
716 </pre>
717
718 <p>
719 Portage was unable to download the sources for the given application and will
720 try to continue installing the other applications (if applicable). This failure
721 can be due to a mirror that has not synchronised correctly or because the ebuild
722 points to an incorrect location. The server where the sources reside can also be
723 down for some reason.
724 </p>
725
726 <p>
727 Retry after one hour to see if the issue still persists.
728 </p>
729
730 </body>
731 </subsection>
732 <subsection id="profileprotect">
733 <title>System Profile Protection</title>
734 <body>
735
736 <pre caption="Portage warning about profile-protected package">
737 !!! Trying to unmerge package(s) in system profile. 'sys-apps/portage'
738 !!! This could be damaging to your system.
739 </pre>
740
741 <p>
742 You have asked to remove a package that is part of your system's core packages.
743 It is listed in your profile as required and should therefore not be removed
744 from the system.
745 </p>
746
747 </body>
748 </subsection>
749 <subsection id="digesterror">
750 <title>Digest Verification Failures</title>
751 <body>
752
753 <p>
754 Sometimes, when you attempt to emerge a package, it will fail with the message:
755 </p>
756
757 <pre caption="Digest verification failure">
758 &gt;&gt;&gt; checking ebuild checksums
759 !!! Digest verification failed:
760 </pre>
761
762 <p>
763 This is a sign that something is wrong with the Portage tree -- often, it is
764 because a developer may have made a mistake when committing a package to the
765 tree.
766 </p>
767
768 <p>
769 When the digest verification fails, do <e>not</e> try to re-digest the package
770 yourself. Running <c>ebuild foo manifest</c> will not fix the problem; it will
771 almost certainly make it worse!
772 </p>
773
774 <p>
775 Instead, wait an hour or two for the tree to settle down. It's likely that the
776 error was noticed right away, but it can take a little time for the fix to
777 trickle down the Portage tree. While you're waiting, check <uri
778 link="http://bugs.gentoo.org">Bugzilla</uri> and see if anyone has reported
779 the problem yet. If not, go ahead and file a bug for the broken package.
780 </p>
781
782 <p>
783 Once you see that the bug has been fixed, you may want to re-sync to pick up
784 the fixed digest.
785 </p>
786
787 <impo>
788 This does <e>not</e> mean that you can re-sync your tree multiple times! As
789 stated in the rsync policy (when you run <c>emerge --sync</c>), users who sync
790 too often will be banned! In fact, it's better to just wait until your next
791 scheduled sync, so that you don't overload the rsync servers.
792 </impo>
793
794 </body>
795 </subsection>
796 </section>
797 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20