When I run emerge --update --deep world (from a recently synced tree), I get (in this case): emerge --update --deep world These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild U ] kde-base/kdelibs-3.5.4-r2 [3.5.4-r1] USE="alsa cups ssl -acl -arts -debug -doc -fam -jpeg2k -kdeenablefinal -kdehiddenvisibility -kerberos -legacyssl -noutempter -openexr -spell -tiff -xinerama -zeroconf" 35 kB But for example, you can see this: emerge kdm These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] kde-base/kdm-3.5.4-r2 [3.5.4-r1] USE="pam -arts -debug -kdeenablefinal -kdehiddenvisibility -xinerama" 0 kB (a new version of kdm is available but not handled by --update --deep options! (and may be other applications too))
Created attachment 97485 [details] emerge --info
I must say that I have all kde components in /etc/portage/package.keywords (as ~amd64 keyworded)
If you are still able to reproduce the problem, then please attach emerge --debug output for the command that behaves unexpectedly.
Yes I can still reproduce it. First I run emerge --debug --update --deep world (as the first attachment) and after I run emerge --debug kdm.
Created attachment 97519 [details] emerge --debug --update --deep world This is the debug file of the failing update
Created attachment 97520 [details] emerge --debug kdm And this is the prove that update fails (there are packages not detected by update wich can be upgraded)
On my system, kdm is pulled in as a dependency of kdebase-meta, which is in turn pulled in as a dependency of kde-meta. In your case, what would you expect to pull it in? The debug ouput shows that you have kdebase-startkde (which is typical for a minimal kde installation), but that doesn't depend on kdm. If you use `emerge --noreplace kdm` to add kdm to /var/lib/portage/world, then it will be updated automatically with world updates.
Yes, I emerged kdebase-startkde, but also after this, I emerged kdm, so kdm should be in my world file, and so selected from upgrading.
Is kdm recorded in /var/lib/portage/world or not? If so, another thing that could cause this would be to have kdm listed in /etc/portage/profile/package.provided.
It is not listed, maybe an error while I was merging kdm for first time. This way, it may not be a bug of portage? (if so, please close this thread)
I haven't heard any other complaints about packages not being added to the world file, so I guess it's not a common problem. One possible explanation is that a parallel instance of emerge overwrote the world file that contained kdm.
This is possible... thus, could be possible to have portage not overwriting world? (instead of this, only adding the current ebuild to world) and maybe allowing paralel executions of emerge?
(In reply to comment #12) > This is possible... thus, could be possible to have portage not overwriting > world? (instead of this, only adding the current ebuild to world) and maybe > allowing paralel executions of emerge? We don't officially support parallel invocations of emerge in any way at this time. Maybe someday, but it's a very low priority. We might support parallel builds soon (see bug 147516), but those builds would all be managed from a single parent process (only the parent process would need to modify the world file).
