Summary: | emerge -avDut world fails to update some of the packages in world | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Tres 'RiverRat' Melton <RiverRat> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
The requested Output
Output cut&pasted from "esync" and "emerge -avDut world" emerge -dep emerge -dDup emerge --pretend --depclean emerge --pretend --deep --update emerge --pretend --emptytree portage/world New Output |
Description
Tres 'RiverRat' Melton
2005-04-17 17:48:54 UTC
Have you confirmed that they are part of world? Both of the packages are indeed part of /var/lib/portage/world. This is not the first time I have suffered from this error but it is the first time I have taken the time to file a bug report. Because of this I save the output from esync until I'm sure that I've updated all of the listed packages. I noticed that this started with AMD64. On my x86 (last year) I was curious about this and watched it through more than a few updates but they were always complete. On my AMD64 (recently upgraded from 2004.3 --> 2005.0) the first time I noticed it esync told me there were about 25 packages needing updated; emerge world reported about five. It seems that most emerge worlds miss a few packages that esync tells me about. emerge -ept world, please. thor:/etc/ppp # emerge -ept These are the packages that I would merge, in reverse order: emerge: please tell me what to do. Usage: emerge [ options ] [ action ] [ ebuildfile | tbz2file | dependency ] [ ... ] emerge [ options ] [ action ] < system | world > emerge < --sync | --metadata | --info > emerge --resume [ --pretend | --ask | --skipfirst ] emerge --help [ system | config | sync ] Options: -[abcCdDefhikKlnoOpPsSuUvV] [--oneshot] [--newuse] [--noconfmem] [--columns] [--nospinner] Actions: [ --clean | --depclean | --inject | --prune | --regen | --search | --unmerge ] For more help try 'emerge --help' or consult the man page. thor:/etc/ppp # Created attachment 56692 [details] The requested Output My apologies for the stupidity of Comment #4, I should have noticed the grey matter cache miss prior to Submitting. This is the requested output. Thanks for taking the time to look Jason. Strange. Both appear in the --emptytree output and both are at the root of the tree... Created attachment 56723 [details]
Output cut&pasted from "esync" and "emerge -avDut world"
I cut and pasted this output from the terminal where I ran "esync" and "emerge
-avDut". I did change a line in my /etc/portage/package.keywords file:
FROM: =x11-terms/eterm-0.9.3 ~amd64
TO: >=x11-terms/eterm-0.9.3 ~amd64
in between the two commands but nothing else. (I wanted eterm-0.9.3-r1)
Never mind the esync output. The differing packages will likely be listed if you run emerge -p depclean. The interesting thing is that packages show up with --emptytree but not with --deep --update. If you can reproduce it, please attach the output with both -dep and -dDup. Created attachment 56800 [details]
emerge -dep
Reproduction is easy: perform my daily update. emerge gets about 80% of the
packages and I have to explicitly tell it to get the rest of them when it is
done with world. Here are some files. (Is there some way to attach more than
one thing to a note?) I'm going to go ahead and update things because I want
to use the newest Eterm package since I wrote the patch in 0.9.3-r2. I'm sure
tomorrow will bring a new set of packages that slip between emerge's cracks. I
don't know python or portage that well but I do know C/C++/Asm so feel free to
ask me to dig if you need me to.
Created attachment 56801 [details]
emerge -dDup
Created attachment 56803 [details]
emerge --pretend --depclean
Created attachment 56804 [details]
emerge --pretend --deep --update
Created attachment 56805 [details]
emerge --pretend --emptytree
Created attachment 56806 [details]
portage/world
Umm.. all of those emerges should have been done with world except for depclean. Need info... Created attachment 59479 [details]
New Output
New output as requested.
Here is the 'NEEDINFO' that is needed You missed `emerge info` ;) dev-libs/elfutils: Not in world Is a dependency from net-analyzer/net-snmp Appears USE="-elf" net-analyzer/nmap: Not in world Nothing depends on it My guess is that you're confused about the meaning of "world". It is not the sum of all installed packages. It is only what you have specifically emerged on the command line. There was a bug that would sometimes miss adding packages when --update was specified which would probably be why nmap is missing. This bug is a duplicate of bug #48181 and as jstubbs mentioned, it is resolved in the next version of portage. Don't use -u when emerging new packages. |