emerge output confusion regarding upgradeable packages
Alan McKinnon wrote:
This is expected behaviour.
The three packages you mention are not in world and thus don't form part
of the initial search. Even though you are using -uN, nothing in world
*requires* specifically those updated/latest versions, so they never
make it into the dependency tree as a suitable version is already
I think the end of my message was a little confusing, if you look
earlier, you'll see I'm using "--deep". (emerge -pv --update --deep
When you add -t though, you clear out the dependency tree, fooling
portage into thinking the packages are not installed. dnspython,
xcursorgen and yasm are needed and not installed so portage does the
normal thing of selecting the latest versions that match your rules
I think you mean -e (--emptytree) here. Using -t (--tree) just adds a
whole bunch of stuff to help you see what is pulling in particular
packages. I seem to recall at one time using -e actually showed all
packages as N (new), but now it seems to indicate their current status
(R for replace).
According to the emerge man page, "-u" (--update) will update the
specified set and its direct dependencies. "-d" (--deep) will update the
specified set and its entire dependency tree (dependencies of its
dependencies, and so on). My final comment was simply noting that two
of the three were direct dependencies and should show up with just -u.
In any case, they should all show up with -d.
email@example.com mailing list