OK, this one's obviously connected to bug 572792 and commit f520d401 in some way, but I've no clue how bad it is or how to fix it, all I know is that I've a nice bit of red-starred text telling me a file couldn't be installed due to a directory of the same name already being there. * Messages for package dev-python/six-1.10.0: * * Installation of a regular file is blocked by a directory: * '/usr/lib64/python2.7/site-packages/six-1.10.0-py2.7.egg-info' * This file will be merged with a different name: * '/usr/lib64/python2.7/site-packages/six-1.10.0-py2.7.egg-info.backup.0000' * * * Installation of a regular file is blocked by a directory: * '/usr/lib64/python3.4/site-packages/six-1.10.0-py3.4.egg-info' * This file will be merged with a different name: * '/usr/lib64/python3.4/site-packages/six-1.10.0-py3.4.egg-info.backup.0000' * In my case this was a rebuild of the same package, probably triggered by f520d401 and --changed-deps in my EMERGE_DEFAULT_OPTS. As I said, the stars are red, making the above message look pretty alarming, but there's absolutely nothing there about how to fix it. There's some similar (2007) bugs with egg-info files vs. dirs as well, suggesting this is somewhat normal, but if it's truly harmless and there's no way to script removal of the directory on upgrade/remerge so the flat-file can go there, but... Do I manually delete the directory and rename the file into its place, or what, and why isn't it either done in the ebuild or at least some message printed telling me how to fix it manually?
[Can't assign the bug, but CCing floppym as he's the author of commit f520d401 that seems to have triggered this.]
commit caab06d4a89e612d7d7deef236d5fba61a98e576 Author: Mike Gilbert <floppym@gentoo.org> Date: Wed Jan 27 09:11:44 2016 -0500 dev-python/six: Remove any existing egg-info directory Bug: https://bugs.gentoo.org/573114 Package-Manager: portage-2.2.27_p49 dev-python/six/six-1.10.0.ebuild | 13 +++++++++++++ dev-python/six/six-1.9.0-r1.ebuild | 13 +++++++++++++ 2 files changed, 26 insertions(+)
(In reply to Duncan from comment #0) > Do I manually delete the directory and rename the file into its place, or > what, and why isn't it either done in the ebuild or at least some message > printed telling me how to fix it manually? You can simply remove these files and reinstall dev-python/six. /usr/lib64/python2.7/site-packages/six-1.10.0-py2.7.egg-info.backup.0000 /usr/lib64/python3.4/site-packages/six-1.10.0-py3.4.egg-info.backup.0000
