I have been fighting with an "emerge -uDN world" update in one of the systems I didn't update for some months. At the end, all the conflicts were caused by an old package that was removed some months ago that was still requiring python3.7 and, as a consequence, was preventing the upgrade. The errors where misleading (but that is a different old bug hard to fix) pointing to boost consumers or qt...
I realized that maybe it would be nice if "emerge -vuDN world" would have warned me about some packages being pulled in even if their ebuild was removed from all the repos I have in my system (but package.mask entry dropped as it was dropped some months ago)
Thanks a lot
Would this be solved with a depclean after world upgrades? Or am I misunderstanding?
(In reply to Sam James from comment #1)
> Would this be solved with a depclean after world upgrades? Or am I
It won't removed it if it's in your world file. The behavior related to bug 266836 and bug 651018 is related because it can prevent updates, causing older things to linger around.
Rethinking about this, I think that maybe it would be enough with adding a warning when running depclean and packages without existing ebuilds are present in the system
The warning would also be really useful when updating a system after some months as , most of the times, package.mask entries are removed upon removal.
Thanks a lot
I'm sorry, yes, I understand you now!
Aside: emerge -ep @world --backtrack=0 is quite good at exposing all of these, but people shouldn't have to do that.