Portage Frequently Asked Questions (FAQ)How can "blocks" between packages be resolved? See the Blocked Packages section in the Gentoo Handbook. Why is it that emerge does not update all packages? By default, the dependency graph may not include some packages. For example, it will not include any packages that are listed in the output of emerge --pretend --depclean. It will also not include any build time dependencies for installed packages or binary packages. If you would like to include such build time dependencies even though they are not strictly required, use --with-bdeps=y. You can set EMERGE_DEFAULT_OPTS="--with-bdeps=y" in /etc/portage/make.conf if you would like this option to be enabled by default. If you would like a specific package to be updated in any case, you can use emerge --noreplace <atom> to have it added to the world set. After running emerge --deep --with-bdeps=y --update world, it is a good idea to use emerge --pretend --depclean to see if there are any packages that it would remove. If that command shows a package that you would like to keep, use emerge --noreplace <atom> to have it added to the world set.
How can I check for reverse dependencies of a package, to know if it can be safely uninstalled? Run emerge --depclean --pretend --verbose [atom]... to see if there are any reverse dependencies for matched packages.
Why does emerge --depclean sometimes remove system packages? For system dependencies that are specified as virtuals, such as virtual/editor, it's common to have multiple packages installed that are capable of satisfying the dependency. In this case, redundant packages may be removed by emerge --depclean unless they are explicitly added to the world set. You can use emerge --noreplace <atom> to have a package added to the world set, and this will guarantee that this package will not be removed by emerge --depclean. Why doesn't emerge account for reverse dependencies sometimes? Complete accounting for reverse dependencies is time-consuming, and many users would be likely to complain about poor performance if this was the default behavior. So, reverse dependencies will often be neglected by dependency calculations unless the emerge --complete-graph option is enabled. You can set EMERGE_DEFAULT_OPTS="--complete-graph" in /etc/portage/make.conf if you would like this option to be enabled by default. Refer to the emerge manual page (run man emerge) for more information about the --complete-graph option. Can I mount the portage tree (/usr/portage) via NFS? It is possible to share the portage tree (/usr/portage) over NFS so that emerge --sync only needs to be run on an NFS server. However, even though NFS clients do not need to run emerge --sync, they must run emerge --metadata each time that the portage tree is updated since otherwise their dependency calculations will slow down due to their metadata cache (located in /var/cache/edb/dep) becoming stale.
If you encounter problems with an NFS setup it is important that you ensure you have the proper locking daemons on both the NFS client machines and the NFS server machine. Portage uses hardlinks over NFS in an attempt to lock files; if the locking daemon fails to lock files Portage may complain about failed or stale locks. There is a script /usr/lib/portage/bin/clean_locks that can be used to clean out old lockfiles. Why does emerge display "waiting for lock" messages? The most common reason is due to FEATURES="parallel-fetch" which is enabled by default in /usr/share/portage/config/make.globals. Set FEATURES="-parallel-fetch" in /etc/portage/make.conf if you would like to disable this feature. Refer to the make.conf manual page (run man make.conf) for more information about FEATURES. If the emerge is invoked multiple times concurrently, or if DISTDIR is on a shared network file system, this may also trigger similar "waiting for lock" messages. Such locks are necessary in order to prevent interference between concurrently running processes. Why does the @preserved-rebuild set contain packages that have already been rebuilt? This is a common problem which indicates that the build system for the given ebuild causes the package to inappropriately link against the old (preserved) version of the library, instead of the new one. As a workaround, you can manually remove the old library (such as libreadline.so.5.2) and then run revdep-rebuild in order to rebuild the packages which linked against it. A list of all preserved libraries may be obtained from the command `portageq list_preserved_libs /`. As a safety precaution, installation actions for system packages and their deep dependecies are executed only when no other packages are building. This behavior is required in order to avoid cases like bug 256616 (unspecified system dependencies) and bug 259954 (temporarily unsatisfied system dependencies). Why doesn't emerge --pretend output show the correct SLOT for a package with USE=multislot enabled? Since ebuilds that support USE=multislot violate established rules about "constant metadata", cached SLOT value differs from the SLOT value that you will actually get once the package is installed. There is nothing portage can do about this except to implement an extension such as bug #174407. How do I configure environment variable settings that apply only to specific packages? Put an entry such as "sys-libs/glibc debug.conf" in /etc/portage/package.env, and put your variable settings in /etc/portage/env/debug.conf (using the same format as make.conf). An example debug.conf might appear as follows:
Portage 2.2 is masked due to known bugs in the package sets ( bug #144480) and preserve-libs features ( bug #240323). See bug #253802 for details. The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-2.5 license. The Gentoo Name and Logo Usage Guidelines apply. |
|