* Messages for package dev-python/logilab-constraint-0.4.0: * 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/share/jython-2.5/Lib/site-packages/logilab/__init__.py * /usr/lib64/pypy1.8/site-packages/logilab/__init__.py * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-python/logilab-common-0.57.1 * /usr/lib64/pypy1.8/site-packages/logilab/__init__.py * /usr/share/jython-2.5/Lib/site-packages/logilab/__init__.py
I guess this is another one of those fun namespace issues.
Created attachment 303701 [details, diff] ebuild patch for logilab-constraint-0.4.0
Created attachment 303707 [details, diff] ebuild patch logilab-common-0.57.1 and the other
+ 12 Mar 2012; Patrick Lauer <patrick@gentoo.org> logilab-common-0.57.1.ebuild: + Fix for 405535 thanks to Ian Delaney
