Opened 5 years ago
Closed 5 years ago
#57889 closed defect (fixed)
py27-pyobjc-cocoa conflict AppKit/_AppKit.so with py27-pyobjc
| Reported by: | vallon (Justin) | Owned by: | reneeotten <reneeotten@…> |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | py-pyobjc-cocoa py-pyobjc |
Description
There was a recent update to py27-pyobjc from 5.1.1_0 to 5.1.2_0. Since then, there has been a conflict between py27-pyobjc and py27-pyobjc-cocoa:
$ port install py-matplotlib ... ---> Activating py27-pyobjc-cocoa @3.0.4_1 Error: Failed to activate py27-pyobjc-cocoa: Image error: \ /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/AppKit/_AppKit.so \ is being used by the active py27-pyobjc port. Please deactivate this port first, or use \ 'port -f activate py27-pyobjc-cocoa' to force the activation. ... $ port installed py27-pyobjc The following ports are currently installed: py27-pyobjc @5.1.2_0 (active)
py27-pyobjc-cocoa depends on py27-pyobjc, so doesn't seem like a case of alternative files.
Filing it against the one that fails to install.
Change History (9)
comment:1 Changed 5 years ago by mf2k (Frank Schima)
| Port: | py-pyobjc-cocoa py-pyobjc added; py27-pyobjc-cocoa removed |
|---|
comment:2 follow-up: 3 Changed 5 years ago by reneeotten (Renee Otten)
this commit had a few issues and was quickly reverted by this one. So if someone upgraded in between these two commits, it will result in the reported problems.
I think what will work is to uninstall py27-pyobjc (which will probably result in a message that it will break ports, just say "Yes") and then reinstall. That should get you to the same, working state as before the above-mentioned commits.
comment:3 follow-up: 6 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to reneeotten:
this commit had a few issues and was quickly reverted by this one.
Hardly quickly: 4 days elapsed between.
So if someone upgraded in between these two commits, it will result in the reported problems.
That's why when reverting to an earlier version the epoch must be increased.
comment:4 Changed 5 years ago by vallon (Justin)
To clarify what seemed to happen: py27-pyobjc was upgraded from 5.1.1 to 5.1.2, and I grabbed that. The upgrade broke py27-pyobjc-cocoa. py27-pyobjc was downgraded to 5.1.1, but it would seem that macports kept me at 5.1.2 since the repo had 5.1.1 (ie: it will not downgrade from 5.1.2 to 5.1.1 automatically).
I purged the rdependentsof py27-pyobjc, and cleared everything out. Reinstalled my requested packages, and I am back to py27-pyobjc 5.1.1, and no conflicts.
comment:5 Changed 5 years ago by vallon (Justin)
Ok to close. Doesn't look like I can close this ticket.
comment:6 follow-up: 8 Changed 5 years ago by reneeotten (Renee Otten)
Replying to ryandesign:
That's why when reverting to an earlier version the
epochmust be increased.
True... I guess now the other option is to actually do the update correctly, and set the revision to 1 so that even if someone is still in the intermediate state gets the new update. Or would you recommend to increase the epoch first and worry about updating later?
comment:7 Changed 5 years ago by reneeotten (Renee Otten)
see PR3428 for an attempt to resolve this...
comment:8 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to reneeotten:
I guess now the other option is to actually do the update correctly, and set the revision to 1 so that even if someone is still in the intermediate state gets the new update.
That would be great, thanks!
comment:9 Changed 5 years ago by reneeotten <reneeotten@…>
| Owner: | set to reneeotten <reneeotten@…> |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Where are you getting version 5.1.2?