Comparing the distfile of x11-proto/printproto-1.0.5 with 1.0.4 shows that it now includes a man page, which is automatically installed by the ebuild: printproto-1.0.5 |-- man | |-- Xprint.man | `-- Xprint.sgml However, this man page is also installed by app-doc/xorg-docs-1.4-r1: * Detected file collision(s): * * /usr/share/man/man7/Xprint.7.bz2 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-doc/xorg-docs-1.4-r1 * /usr/share/man/man7/Xprint.7.bz2 Reproducible: Always Steps to Reproduce:
xorg-docs has been gone from portage for a looooooooooooong time. Thanks
(In reply to comment #1) > xorg-docs has been gone from portage for a looooooooooooong time. Which doesn't make it magically vanish from users' systems. ;) Putting a blocker against it into printproto cannot harm.
Hit by this bug too. A blocker would be welcome.
Ran into the same problem. No matter how old the package is, if one blocks the other it should remain in there if you don't update your box very often. In my case I do update it fairly often and yet I still ran into this issue.
Not too often? This package is masked for removal since 19 September 2009 and gone from main tree 30 days after that. For how long we should support removed things from main tree? Anyway we could add the blocker to eclass given the fact quite more packages now pull in the manpages from old xorg-docs. Or we can make portage scream way way harder on users keeping removed packags.
I'm for screaming harder with keeping unused packages. A file collision error is not obvious as to what's going on. It would help if there was a list of packages which were not found in any repo when running emerge -uDNa world even if there wasn't a blocked for removal message for them. I'm not sure how this problem arised since I update this system on a fairly regular basis other than a perfect storm where I did not update it during the time there existed a blocked for removal message and when the package was removed, so was that message thereby not notifying me that I needed to remove the package.
(In reply to comment #6) > I'm for screaming harder with keeping unused packages. Sorry I meant removed packages not existing in any repo.
I think this is a symptom of people not using emerge --depclean as they should. I'm planning to add a suggestion about --depclean to the emerge man page, as a response to bug 354787. Maybe emerge should also display a reminder after world updates.
(In reply to comment #8) > I think this is a symptom of people not using emerge --depclean as they should. > I'm planning to add a suggestion about --depclean to the emerge man page, as a > response to bug 354787. Maybe emerge should also display a reminder after world > updates. > Sounds good to me. I was not aware that depclean is used for obsolete packages. A reminder after a world update would help.
Since portage-2.1.9.41 and 2.2.0_alpha25, emerge suggests to run --depclean after world updates: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=550795df709cfa9ec4a9502a4ad835319f778e95 The message looks like this: * After world updates, it is important to remove obsolete packages with * emerge --depclean. Refer to `man emerge` for more information.
*** Bug 358521 has been marked as a duplicate of this bug. ***
