/[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.55 - (hide annotations) (download) (as text)
Fri Jun 24 19:28:48 2005 UTC (8 years, 9 months ago) by fox2mike
Branch: MAIN
Changes since 1.54: +7 -7 lines
File MIME type: application/xml
#96926 - Updating blockage text as shown by > portage-2.0.51.16

1 swift 1.18 <?xml version='1.0' encoding='UTF-8'?>
2     <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3    
4 swift 1.1 <!-- The content of this document is licensed under the CC-BY-SA license -->
5 fox2mike 1.55 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 swift 1.1
7 fox2mike 1.55 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.54 2005/06/11 12:16:14 swift Exp $ -->
8 swift 1.1
9     <sections>
10 swift 1.43
11 fox2mike 1.55 <version>1.50</version>
12     <date>2005-06-25</date>
13 swift 1.43
14 swift 1.1 <section>
15 swift 1.39 <title>Welcome to Portage</title>
16 swift 1.1 <body>
17    
18 swift 1.2 <p>
19 swift 1.39 Portage is probably Gentoo's most notable innovation in software management.
20     With its high flexibility and enormous amount of features it is frequently seen
21     as the best software management tool available for Linux.
22 swift 1.2 </p>
23    
24     <p>
25 swift 1.39 Portage is completely written in <uri link="http://www.python.org">Python</uri>
26     and <uri link="http://www.gnu.org/software/bash">Bash</uri> and therefore fully
27     visible to the users as both are scripting languages.
28 swift 1.2 </p>
29    
30     <p>
31 swift 1.39 Most users will work with Portage through the <c>emerge</c> tool. This chapter
32     is not meant to duplicate the information available from the emerge man page.
33     For a complete rundown of emerge's options, please consult the man page:
34 swift 1.2 </p>
35    
36 swift 1.39 <pre caption="Reading the emerge man page">
37     $ <i>man emerge</i>
38 swift 1.2 </pre>
39    
40     </body>
41 swift 1.1 </section>
42     <section>
43 swift 1.39 <title>The Portage Tree</title>
44 swift 1.1 <subsection>
45 swift 1.39 <title>Ebuilds</title>
46 swift 1.2 <body>
47    
48     <p>
49 swift 1.39 When we talk about packages, we often mean software titles that are available to
50     the Gentoo users through the Portage tree. The Portage tree is a collection of
51     <e>ebuilds</e>, files that contain all information Portage needs to maintain
52     software (install, search, query, ...). These ebuilds reside in
53     <path>/usr/portage</path> by default.
54 swift 1.2 </p>
55    
56     <p>
57 swift 1.39 Whenever you ask Portage to perform some action regarding software titles, it
58     will use the ebuilds on your system as a base. It is therefore important that
59     you regularly update the ebuilds on your system so Portage knows about new
60     software, security updates, etc.
61 swift 1.2 </p>
62    
63     </body>
64     </subsection>
65     <subsection>
66 swift 1.39 <title>Updating the Portage Tree</title>
67 swift 1.1 <body>
68 swift 1.2
69     <p>
70 swift 1.39 The Portage tree is usually updated with <uri
71 yoswink 1.50 link="http://rsync.samba.org/">rsync</uri>, a fast incremental file transfer
72 swift 1.39 utility. Updating is fairly simple as the <c>emerge</c> command provides a
73     front-end for rsync:
74 swift 1.2 </p>
75    
76 swift 1.39 <pre caption="Updating the Portage tree">
77 cam 1.38 # <i>emerge --sync</i>
78 swift 1.2 </pre>
79    
80     <p>
81 swift 1.39 If you are unable to rsync due to firewall restrictions you can still update
82 swift 1.40 your Portage tree by using our daily generated Portage tree snapshots. The
83 swift 1.39 <c>emerge-webrsync</c> tool automatically fetches and installs the latest
84     snapshot on your system:
85 swift 1.2 </p>
86    
87 swift 1.39 <pre caption="Running emerge-webrsync">
88 swift 1.2 # <i>emerge-webrsync</i>
89     </pre>
90 swift 1.1
91     </body>
92     </subsection>
93     </section>
94     <section>
95     <title>Maintaining Software</title>
96     <subsection>
97 swift 1.39 <title>Searching for Software</title>
98 swift 1.1 <body>
99    
100 swift 1.3 <p>
101 swift 1.39 To search through the Portage tree after software titles, you can use
102 cam 1.47 <c>emerge</c> built-in search capabilities. By default, <c>emerge --search</c>
103 neysx 1.42 returns the names of packages whose title matches (either fully or partially)
104 swift 1.39 the given search term.
105 swift 1.3 </p>
106    
107     <p>
108 swift 1.39 For instance, to search for all packages who have "pdf" in their name:
109 swift 1.3 </p>
110    
111 swift 1.39 <pre caption="Searching for pdf-named packages">
112 cam 1.47 $ <i>emerge --search pdf</i>
113 swift 1.39 </pre>
114    
115 swift 1.3 <p>
116 swift 1.39 If you want to search through the descriptions as well you can use the
117     <c>--searchdesc</c> (or <c>-S</c>) switch:
118 swift 1.3 </p>
119    
120 swift 1.39 <pre caption="Searching for pdf-related packages">
121     $ <i>emerge --searchdesc pdf</i>
122     </pre>
123    
124 swift 1.3 <p>
125 swift 1.39 When you take a look at the output, you'll notice that it gives you a lot of
126     information. The fields are clearly labelled so we won't go further into their
127     meanings:
128 swift 1.3 </p>
129    
130 swift 1.49 <pre caption="Example 'emerge --search' output">
131 swift 1.39 * net-print/cups-pdf
132     Latest version available: 1.5.2
133     Latest version installed: [ Not Installed ]
134     Size of downloaded files: 15 kB
135     Homepage: http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/
136     Description: Provides a virtual printer for CUPS to produce PDF files.
137     License: GPL-2
138     </pre>
139    
140 swift 1.3 </body>
141     </subsection>
142     <subsection>
143 swift 1.39 <title>Installing Software</title>
144 swift 1.3 <body>
145    
146     <p>
147 swift 1.39 Once you've found a software title to your liking, you can easily install it
148     with <c>emerge</c>: just add the package name. For instance, to install
149 swift 1.3 <c>gnumeric</c>:
150     </p>
151    
152 swift 1.39 <pre caption="Installing gnumeric">
153 swift 1.3 # <i>emerge gnumeric</i>
154     </pre>
155    
156     <p>
157 swift 1.39 Since many applications depend on each other, any attempt to install a certain
158     software package might result in the installation of several dependencies as
159     well. Don't worry, Portage handles dependencies well. If you want to find out
160     what Portage <e>would</e> install when you ask it to install a certain package,
161     add the <c>--pretend</c> switch. For instance:
162 swift 1.3 </p>
163    
164 swift 1.39 <pre caption="Pretend to install gnumeric">
165 swift 1.3 # <i>emerge --pretend gnumeric</i>
166     </pre>
167    
168     <p>
169 swift 1.39 When you ask Portage to install a package, it will download the necessary source
170     code from the internet (if necessary) and store it by default in
171     <path>/usr/portage/distfiles</path>. After this it will unpack, compile and
172     install the package. If you want Portage to only download the sources without
173     installing them, add the <c>--fetchonly</c> option to the <c>emerge</c> command:
174 swift 1.3 </p>
175    
176 swift 1.39 <pre caption="Download the sourcecode for gnumeric">
177 swift 1.3 # <i>emerge --fetchonly gnumeric</i>
178     </pre>
179    
180     </body>
181     </subsection>
182     <subsection>
183 neysx 1.52 <title>Finding Installed Package Documentation</title>
184     <body>
185    
186     <p>
187     Many packages come with their own documentation. Sometimes, the <c>doc</c> USE
188     flag determines whether the package documentation should be installed or not.
189     You can check the existence of a <c>doc</c> USE flag with the <c>emerge -vp
190     &lt;package name&gt;</c> command.
191     </p>
192    
193     <pre caption="Checking the existence of a doc USE flag">
194     <comment>(alsa-lib is just an example, of course.)</comment>
195     # <i>emerge -vp alsa-lib</i>
196     [ebuild N ] media-libs/alsa-lib-1.0.9_rc3 +doc -jack 674 kB
197     </pre>
198    
199     <p>
200     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
202     <path>/etc/portage/package.use</path> file. The <uri
203     link="?part=2&amp;chap=2">USE Flags</uri> chapter covers this aspect in detail.
204     </p>
205    
206     <p>
207     Once the package installed, its documentation is generally found in a
208     subdirectory named after the package under the <path>/usr/share/doc</path>
209     directory. You can also list all installed files with the <c>equery</c> tool
210     which is part of the <c>app-portage/gentoolkit</c> <uri
211     link="/doc/en/gentoolkit.xml">package</uri>.
212     </p>
213    
214     <pre caption="Locating package documentation">
215     # <i>ls -l /usr/share/doc/alsa-lib-1.0.9_rc3</i>
216     total 28
217     -rw-r--r-- 1 root root 669 May 17 21:54 ChangeLog.gz
218     -rw-r--r-- 1 root root 9373 May 17 21:54 COPYING.gz
219     drwxr-xr-x 2 root root 8560 May 17 21:54 html
220     -rw-r--r-- 1 root root 196 May 17 21:54 TODO.gz
221    
222     <comment>(Alternatively, use equery to locate interesting files:)</comment>
223     # <i>equery files alsa-lib | less</i>
224     media-libs/alsa-lib-1.0.9_rc3
225     * Contents of media-libs/alsa-lib-1.0.9_rc3:
226     /usr
227     /usr/bin
228     /usr/bin/alsalisp
229 neysx 1.53 <comment>(Output truncated)</comment>
230 neysx 1.52 </pre>
231    
232     </body>
233     </subsection>
234     <subsection>
235 swift 1.39 <title>Removing Software</title>
236 swift 1.3 <body>
237    
238     <p>
239 swift 1.39 When you want to remove a software package from your system, use <c>emerge
240 cam 1.47 --unmerge</c>. This will tell Portage to remove all files installed by that
241 swift 1.39 package from your system <e>except</e> the configuration files of that
242     application if you have altered those after the installation. Leaving the
243     configuration files allows you to continue working with the package if you ever
244     decide to install it again.
245 swift 1.3 </p>
246    
247     <p>
248 swift 1.39 However, a <brite>big warning</brite> applies: Portage will <e>not</e> check if
249     the package you want to remove is required by another package. It will however
250     warn you when you want to remove an important package that breaks your system
251     if you unmerge it.
252 swift 1.3 </p>
253    
254 swift 1.39 <pre caption="Removing gnumeric from the system">
255 cam 1.47 # <i>emerge --unmerge gnumeric</i>
256 swift 1.3 </pre>
257    
258     <p>
259 swift 1.39 When you remove a package from your system, the dependencies of that package
260     that were installed automatically when you installed the software are left. To
261     have Portage locate all dependencies that can now be removed, use
262 cam 1.47 <c>emerge</c>'s <c>--depclean</c> functionality. We will talk about this later
263     on.
264 swift 1.3 </p>
265    
266 swift 1.39 </body>
267     </subsection>
268     <subsection>
269     <title>Updating your System</title>
270     <body>
271 swift 1.32
272 swift 1.3 <p>
273 swift 1.39 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
275     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
277     <c>emerge --update world</c>:
278 swift 1.3 </p>
279    
280 swift 1.39 <pre caption="Updating your system">
281     # <i>emerge --update world</i>
282 swift 1.3 </pre>
283    
284     <p>
285 swift 1.39 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
287     have explicitly installed - not the dependencies. If you want to update every
288     single package on your system, add the <c>--deep</c> argument:
289 swift 1.3 </p>
290    
291 swift 1.39 <pre caption="Updating your entire system">
292     # <i>emerge --update --deep world</i>
293 swift 1.3 </pre>
294    
295     <p>
296 swift 1.54 Since security updates also happen in packages you have not explicitly installed
297     on your system (but that are pulled in as dependencies of other programs), it
298     is recommended to run this command once in a while.
299     </p>
300    
301     <p>
302 swift 1.39 If you have altered any of your <uri link="?part=2&amp;chap=2">USE flags</uri>
303     lately you might want to add <c>--newuse</c> as well. Portage will then verify
304     if the change requires the installation of new packages or recompilation of
305     existing ones:
306 swift 1.3 </p>
307    
308 swift 1.39 <pre caption="Performing a full update">
309     # <i>emerge --update --deep --newuse world</i>
310 swift 1.3 </pre>
311    
312 swift 1.1 </body>
313     </subsection>
314     <subsection>
315 neysx 1.51 <title>Metapackages</title>
316 swift 1.11 <body>
317    
318     <p>
319 swift 1.39 Some packages in the Portage tree don't have any real content but are used to
320     install a collection of packages. For instance, the <c>kde</c> package will
321     install a complete KDE environment on your system by pulling in various
322     KDE-related packages as dependencies.
323 swift 1.11 </p>
324    
325     <p>
326 swift 1.39 If you ever want to remove such a package from your system, running <c>emerge
327 cam 1.47 --unmerge</c> on the package won't have much effect as the dependencies remain
328     on the system.
329 swift 1.11 </p>
330    
331     <p>
332 swift 1.39 Portage has the functionality to remove orphaned dependencies as well, but since
333     the availability of software is dynamically dependent you first need to update
334     your entire system fully, including the new changes you applied when changing
335 cam 1.47 USE flags. After this you can run <c>emerge --depclean</c> to remove the
336     orphaned dependencies. When this is done, you need to rebuild the applications
337     that were dynamically linked to the now-removed software titles but don't
338     require them anymore.
339 swift 1.11 </p>
340    
341     <p>
342 swift 1.39 All this is handled with the following three commands:
343 swift 1.11 </p>
344    
345 swift 1.39 <pre caption="Removing orphaned dependencies">
346     # <i>emerge --update --deep --newuse world</i>
347 cam 1.47 # <i>emerge --depclean</i>
348 swift 1.39 # <i>revdep-rebuild</i>
349 swift 1.11 </pre>
350    
351 swift 1.34 <p>
352 swift 1.39 <c>revdep-rebuild</c> is provided by the <c>gentoolkit</c> package; don't forget
353     to emerge it first:
354 swift 1.34 </p>
355    
356 swift 1.39 <pre caption="Installing the gentoolkit package">
357     # <i>emerge gentoolkit</i>
358 swift 1.34 </pre>
359    
360 swift 1.11 </body>
361     </subsection>
362 swift 1.39 </section>
363     <section>
364     <title>When Portage is Complaining...</title>
365 swift 1.11 <subsection>
366 swift 1.39 <title>About SLOTs, Virtuals, Branches, Architectures and Profiles</title>
367 swift 1.1 <body>
368    
369 swift 1.3 <p>
370 swift 1.39 As we stated before, Portage is extremely powerful and supports many features
371     that other software management tools lack. To understand this, we explain a few
372 neysx 1.46 aspects of Portage without going into too much detail.
373 swift 1.3 </p>
374    
375     <p>
376 swift 1.39 With Portage different versions of a single package can coexist on a system.
377     While other distributions tend to name their package to those versions (like
378     <c>freetype</c> and <c>freetype2</c>) Portage uses a technology called
379     <e>SLOT</e>s. An ebuild declares a certain SLOT for its version. Ebuilds with
380     different SLOTs can coexist on the same system. For instance, the
381     <c>freetype</c> package has ebuilds with <c>SLOT="1"</c> and <c>SLOT="2"</c>.
382 swift 1.3 </p>
383    
384     <p>
385 swift 1.39 There are also packages that provide the same functionality but are implemented
386     differently. For instance, <c>metalogd</c>, <c>sysklogd</c> and <c>syslog-ng</c>
387     are all system loggers. Applications that rely on the availability of "a system
388     logger" cannot depend on, for instance, <c>metalogd</c>, as the other system
389     loggers are as good a choice as any. Portage allows for <e>virtuals</e>: each
390     system logger provides <c>virtual/syslog</c> so that applications can depend on
391     <c>virtual/syslog</c>.
392 swift 1.3 </p>
393    
394     <p>
395 swift 1.39 Software in the Portage tree can reside in different branches. By default your
396     system only accepts packages that Gentoo deems stable. Most new software titles,
397     when committed, are added to the testing branch, meaning more testing needs to
398     be done before it is marked as stable. Although you will see the ebuilds for
399     those software in the Portage tree, Portage will not update them before they are
400     placed in the stable branch.
401 swift 1.3 </p>
402    
403     <p>
404 swift 1.39 Some software is only available for a few architectures. Or the software doesn't
405     work on the other architectures, or it needs more testing, or the developer that
406     committed the software to the Portage tree is unable to verify if the package
407     works on different architectures.
408 swift 1.25 </p>
409    
410     <p>
411 swift 1.39 Each Gentoo installation adheres to a certain <c>profile</c> which contains,
412     amongst other information, the list of packages that are required for a system
413     to function normally.
414 swift 1.3 </p>
415    
416 swift 1.1 </body>
417     </subsection>
418 swift 1.39 <subsection id="blocked">
419     <title>Blocked Packages</title>
420 swift 1.1 <body>
421    
422 swift 1.39 <pre caption="Portage warning about blocked packages (with --pretend)">
423 fox2mike 1.55 [blocks B ] mail-mta/ssmtp (is blocking mail-mta/postfix-2.2.2-r1)
424 swift 1.39 </pre>
425 swift 1.3
426 swift 1.39 <pre caption="Portage warning about blocked packages (without --pretend)">
427 fox2mike 1.55 !!! Error: the mail-mta/postfix package conflicts with another package.
428 swift 1.39 !!! both can't be installed on the same system together.
429     !!! Please use 'emerge --pretend' to determine blockers.
430 swift 1.3 </pre>
431    
432     <p>
433 swift 1.41 Ebuilds contain specific fields that inform Portage about its dependencies.
434 swift 1.39 There are two possible dependencies: build dependencies, declared in
435     <c>DEPEND</c> and run-time dependencies, declared in <c>RDEPEND</c>. When one of
436     these dependencies explicitly marks a package or virtual as being <e>not</e>
437     compatible, it triggers a blockage.
438 swift 1.3 </p>
439    
440 swift 1.11 <p>
441 swift 1.39 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
443 fox2mike 1.55 <c>postfix</c> or to remove <c>ssmtp</c> first.
444 swift 1.11 </p>
445    
446 swift 1.1 </body>
447     </subsection>
448 swift 1.39 <subsection id="masked">
449     <title>Masked Packages</title>
450 swift 1.1 <body>
451    
452 swift 1.39 <pre caption="Portage warning about masked packages">
453     !!! all ebuilds that could satisfy "bootsplash" have been masked.
454     </pre>
455    
456     <pre caption="Portage warning about masked packages - reason">
457     !!! possible candidates are:
458 swift 1.3
459 swift 1.39 - gnome-base/gnome-2.8.0_pre1 (masked by: <i>~x86 keyword</i>)
460     - lm-sensors/lm-sensors-2.8.7 (masked by: <i>-sparc keyword</i>)
461     - sys-libs/glibc-2.3.4.20040808 (masked by: <i>-* keyword</i>)
462     - dev-util/cvsd-1.0.2 (masked by: <i>missing keyword</i>)
463     - media-video/ati-gatos-4.3.0 (masked by: <i>package.mask</i>)
464     - sys-libs/glibc-2.3.2-r11 (masked by: <i>profile</i>)
465 swift 1.35 </pre>
466    
467 swift 1.3 <p>
468 swift 1.39 When you want to install a package that isn't available for your system, you
469     will receive this masking error. You should try installing a different
470     application that is available for your system or wait until the package is put
471     available. There is always a reason why a package is masked:
472 swift 1.3 </p>
473    
474 swift 1.35 <ul>
475     <li>
476 swift 1.39 <b>~arch keyword</b> means that the application is not tested sufficiently
477     to be put in the stable branch. Wait a few days or weeks and try again.
478 swift 1.35 </li>
479     <li>
480 swift 1.39 <b>-arch keyword</b> or <b>-* keyword</b> means that the application does
481     not work on your architecture. If you believe the package does work file
482     a bug at our <uri link="http://bugs.gentoo.org">bugzilla</uri> website.
483 swift 1.35 </li>
484     <li>
485 swift 1.39 <b>missing keyword</b> means that the application has not been tested on
486     your architecture yet. Ask the architecture porting team to test the package
487     or test it for them and report your findings on our <uri
488     link="http://bugs.gentoo.org">bugzilla</uri> website.
489 swift 1.35 </li>
490     <li>
491 swift 1.39 <b>package.mask</b> means that the package has been found corrupt, unstable
492     or worse and has been deliberately marked as do-not-use.
493 swift 1.35 </li>
494     <li>
495 swift 1.39 <b>profile</b> means that the package has been found not suitable for your
496     profile. The application might break your system if you installed it or is
497     just not compatible with the profile you use.
498 swift 1.35 </li>
499     </ul>
500    
501 swift 1.1 </body>
502     </subsection>
503 swift 1.39 <subsection id="missingdependencies">
504     <title>Missing Dependencies</title>
505 swift 1.1 <body>
506    
507 swift 1.39 <pre caption="Portage warning about missing dependency">
508 neysx 1.48 emerge: there are no ebuilds to satisfy "&gt;=sys-devel/gcc-3.4.2-r4".
509 swift 1.3
510 swift 1.39 !!! Problem with ebuild sys-devel/gcc-3.4.2-r2
511     !!! Possibly a DEPEND/*DEPEND problem.
512 swift 1.3 </pre>
513    
514     <p>
515 swift 1.39 The application you are trying to install depends on another package that is not
516     available for your system. Please check <uri
517     link="http://bugs.gentoo.org">bugzilla</uri> if the issue is known and if not,
518     please report it. Unless you are mixing branches this should not occur and is
519     therefore a bug.
520 swift 1.3 </p>
521    
522 swift 1.39 </body>
523     </subsection>
524     <subsection id="ambiguousebuild">
525     <title>Ambiguous Ebuild Name</title>
526     <body>
527 swift 1.3
528 swift 1.39 <pre caption="Portage warning about ambiguous ebuild names">
529     !!! The short ebuild name "aterm" is ambiguous. Please specify
530     !!! one of the following fully-qualified ebuild names instead:
531 swift 1.35
532 swift 1.39 dev-libs/aterm
533     x11-terms/aterm
534 swift 1.3 </pre>
535    
536     <p>
537 swift 1.39 The application you want to install has a name that corresponds with more than
538     one package. You need to supply the category name as well. Portage will inform
539     you of possible matches to choose from.
540 swift 1.35 </p>
541    
542 swift 1.39 </body>
543     </subsection>
544     <subsection id="circulardependencies">
545     <title>Circular Dependencies</title>
546     <body>
547 swift 1.35
548 swift 1.39 <pre caption="Portage warning about circular dependencies">
549     !!! Error: circular dependencies:
550 swift 1.35
551 swift 1.39 ebuild / net-print/cups-1.1.15-r2 depends on ebuild / app-text/ghostscript-7.05.3-r1
552     ebuild / app-text/ghostscript-7.05.3-r1 depends on ebuild / net-print/cups-1.1.15-r2
553 swift 1.35 </pre>
554    
555     <p>
556 swift 1.39 Two (or more) packages you want to install depend on each other and can
557     therefore not be installed. This is most likely a bug in the Portage tree.
558     Please resync after a while and try again. You can also check <uri
559     link="http://bugs.gentoo.org">bugzilla</uri> if the issue is known and if not,
560     report it.
561 swift 1.3 </p>
562    
563 swift 1.39 </body>
564     </subsection>
565     <subsection id="fetchfailed">
566     <title>Fetch failed</title>
567     <body>
568 swift 1.29
569 swift 1.39 <pre caption="Portage warning about fetch failed">
570     !!! Fetch failed for sys-libs/ncurses-5.4-r5, continuing...
571     <comment>(...)</comment>
572     !!! Some fetch errors were encountered. Please see above for details.
573 swift 1.3 </pre>
574    
575 swift 1.35 <p>
576 swift 1.39 Portage was unable to download the sources for the given application and will
577     try to continue installing the other applications (if applicable). This failure
578     can be due to a mirror that has not synchronised correctly or because the ebuild
579     points to an incorrect location. The server where the sources reside can also be
580     down for some reason.
581 swift 1.35 </p>
582    
583     <p>
584 swift 1.39 Retry after one hour to see if the issue still persists.
585 swift 1.35 </p>
586    
587 swift 1.1 </body>
588     </subsection>
589 swift 1.39 <subsection id="profileprotect">
590     <title>System Profile Protection</title>
591 swift 1.1 <body>
592 swift 1.3
593 swift 1.39 <pre caption="Portage warning about profile-protected package">
594     !!! Trying to unmerge package(s) in system profile. 'sys-apps/portage'
595     !!! This could be damaging to your system.
596 swift 1.3 </pre>
597    
598     <p>
599 swift 1.39 You have asked to remove a package that is part of your system's core packages.
600     It is listed in your profile as required and should therefore not be removed
601     from the system.
602 swift 1.3 </p>
603    
604 swift 1.1 </body>
605     </subsection>
606     </section>
607     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20