New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
file collisions: /usr/bin/python-exec2 #337
Comments
I should have posted the failure:
|
Not present here. I will have to see if it is something from an eclass update. |
eclass flip-flopping, are you a late upgrader for dev-lang/python-exec? It should be 2.0.1-r1. |
That's the python-exec that I have. FWIW this appeared after a sync and updating world. |
OK doing that just now, we'll see. |
Just reinstalled git, still no |
Ahh. python-exec is old! It was never updated. Let me manually do it and then see. |
The python-exec is old
I manually updated python-exec and I still get the collisions when installing
And now
with
Strange? |
I have a dim memory that the file needed to be removed manually.
|
Here after removing the symlink |
With what message? |
I think it failed because of file collisions, although I'm not now positive. I did
without a problem. And
pulled in git first and then sage-baselayout. So there must be a correct order of merging. I guess. |
Still very curious. I wonder if we should ask someone like mgorny. Then again I am surprised you have not been forced to upgrade earlier so it may be a pitfall due to slow removal of the link. |
Both sage-baselayout and dev-vcs/git install the symlink
and I get file collisions that don't seem to be resolvable. I don't recall seeing this previously? And I have collision-protect turned off in
make.conf
. Perhaps the order of install is important. This appeared while rebuilding git-2.0.5 with sage-baselayout-9999 installed.The text was updated successfully, but these errors were encountered: