Created attachment 408866 [details] emerge --info The package app-i18n/man-pages-pl-0.6 fails to merge with a file collision detected: >>> Failed to install app-i18n/man-pages-pl-0.6 * Messages for package app-i18n/man-pages-pl-0.6: (cut the std. message part...) * * Detected file collision(s): * * /usr/share/man/pl/man1/groups.1.bz2 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-apps/shadow-4.2.1-r1:0::gentoo * /usr/share/man/pl/man1/groups.1.bz2 * * Package 'app-i18n/man-pages-pl-0.6' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message.
I can confirm that this happens. New manpages-pl package contains man for groups, which collides with shadow's. In earlier versions there was a crude fix, by removing duplicate man pages. See attached patch for similar fix in this version.
Created attachment 409270 [details, diff] Fixes the problem, by removing the offending man page.
I saved the patch in: # pwd /etc/portage/patches/app-i18n/man-pages-pl-0.6 It should be picked be emerge automatically from that location. As it does not so, it seems that man-pages-pl package has another problem, which is lack of call for custom patches in the ebuild. I will report that bug later on. All I have time for right now is to confirm that I also am affected by the file conflict.
https://bugs.gentoo.org/show_bug.cgi?id=558542 There you go. The proper bug report I promised two days ago about the automatic patching.
Looks ok to me, i'll just test it later today. Sorry for delay.
Created attachment 410712 [details] updated ebuild attaching updated ebuild, also with user patch support from #558542
commit 4250008b825166d449d66e2df174a7364db0d4a2 Author: Ian Delaney <idella4@gentoo.org> Date: Fri Sep 4 14:18:30 2015 +0800 app-i18n/man-pages-pl-0.6: fix file collisions with sys-apps/shadow-4.2.1-r1 patch submitted by Marek Paśnikowski, endorsed by maintainer with user patch support added, fixes Bugs #557372 #558542
*** Bug 559690 has been marked as a duplicate of this bug. ***