>>> Extracting xdm-1.0.4 * checking 27 files for package collisions existing file /usr/lib64/X11/xdm/GiveConsole is not owned by this package existing file /usr/lib64/X11/xdm/TakeConsole is not owned by this package existing file /usr/lib64/X11/xdm/Xsetup_0 is not owned by this package existing file /usr/lib64/X11/xdm/Xwilling is not owned by this package existing file /usr/lib64/X11/xdm/chooser is not owned by this package existing file /usr/lib64/X11/xdm/Xsession is not owned by this package existing file /usr/lib64/X11/xdm/pixmaps/xorg-bw.xpm is not owned by this package existing file /usr/lib64/X11/xdm/pixmaps/xorg.xpm is not owned by this package # equery b /usr/lib64/X11/xdm/{{Give,Take}Console,Xsetup_0,Xwilling,chooser,Xsession,pixmaps/{xorg-bw.xpm,xorg.xpm}} [ Searching for file(s) /usr/lib64/X11/xdm/GiveConsole,/usr/lib64/X11/xdm/TakeConsole,/usr/lib64/X11/xdm/Xsetup_0,/usr/lib64/X11/xdm/Xwilling,/usr/lib64/X11/xdm/chooser,/usr/lib64/X11/xdm/Xsession,/usr/lib64/X11/xdm/pixmaps/xorg-bw.xpm,/usr/lib64/X11/xdm/pixmaps/xorg.xpm in *... ] //empty//
Created attachment 88897 [details] emerge --info
Hmm, I think this is the consequence of a config-protect setting we used to have. There's not much we can do about it from an automatic sense. Emerging xdm without that feature once appears to make this problem go away for good.
Yep, not much we can do about files not owned by any package. IMHO they shouldn't be covered by collision-protect, but they are.