emerge --emptytree -p system | grep tar [ebuild R ] app-arch/tar-1.22 <<------------------ ok !! [ebuild R ] x11-libs/startup-notification-0.10 emerge --emptytree -p world | grep tar [ebuild R ] app-arch/rpm2targz-9.0.0.3g [ebuild R ] x11-libs/startup-notification-0.10 [ebuild R ] kde-base/kstartupconfig-4.3.2 [ebuild R ] kde-base/kstart-4.3.2 [ebuild R ] kde-base/kstars-4.3.2 [ebuild R ] kde-base/kdebase-startkde-4.3.2 ???? where is app-arch/tar-1.22 ???!!! not ok !!! idem with emerge --emptytree --deep -p world | grep tar many other packages belonging to system have the same behaviour on one computer where openssh is not in /var/lib/portage/world file has the same thing Reproducible: Always Steps to Reproduce: 1.look before ;) 2. 3. Actual Results: idem same behaviour on 6 computers using wonderfull gentoo ;)
Created attachment 206804 [details, diff] add system to world If this is saved as /tmp/system_world.patch, then it can be applied as follows: patch /usr/lib/portage/pym/portage/_sets/files.py /tmp/system_world.patch
I've also been a bit surprised by the new portage: Now for updating world you *must* use --update (while it could be omitted before) Additionally you need to include system - which makes me wonder whether the --deep flag makes still sense? previously I update like that: emerge -ND world now it's: emerge -uND system world What does --deep currently do?
(In reply to comment #2) > I've also been a bit surprised by the new portage: > > Now for updating world you *must* use --update (while it could be omitted > before) That's intended, see bug 275945. > Additionally you need to include system - which makes me wonder whether the > --deep flag makes still sense? > > previously I update like that: > > emerge -ND world > > now it's: > > emerge -uND system world > > What does --deep currently do? > The deep flag is the same as always. It means that dependencies will be traversed recursively from the given argument(s). You've missed some updates because the world argument didn't include system like it was supposed to, and that's fixed by the attached patch.
This is fixed in 2.1.7.1.
