I've installed rpm 5.1.6 in my system with perl USE flag on. When I installed xfconf-4.6.0, I got the following error message: ---- This package will overwrite one or more files that may belong to other packages (see list below). You can use a command such as `portageq owners / <filename>` to identify the installed package that owns a file. If portageq reports that only one package owns a file then do NOT file a bug report. A bug report is only useful if it identifies at least two or more packages that are known to install the same file(s). If a collision occurs and you can not explain where the file came from then you should simply ignore the collision since there is not enough information to determine if a real problem exists. Please do NOT file a bug report at http://bugs.gentoo.org unless you report exactly which two packages install the same file(s). Once again, please do NOT file a bug report unless you have completely understood the above message. Detected file collision(s): /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/perllocal.pod Searching all installed packages for file collisions... Press Ctrl-C to Stop app-arch/rpm-5.1.6 /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/perllocal.pod Package 'xfce-base/xfconf-4.6.0' NOT merged due to file collisions. If necessary, refer to your elog messages for the whole content of the above message. Reproducible: Always Steps to Reproduce: 1. emerge -va1 =app-arch/rpm-5.1.6 2. emerge -va1 =xfce-base/xfconf-4.6.0 3. Error is thrown as explained above. Actual Results: Collision error on perllocal.pod. Expected Results: xfconf should be installed correctly. Downgrading to rpm-4.4.6-r6 avoids the error.
Reassigning to xfce herd. rpm package is currently maintainer-wanted so useless to add any CC for that package right now...
Just to note that I had the same file collision on amd64, but in my case perllocal.pod was not claimed by any other package (I don't have rpm installed) so I went ahead and re-installed xconf with '-collision protect'.
no package should be installing that perllocal.pod file
aye, removed perllocal.pod
