Opened 7 years ago
Closed 7 years ago
#55738 closed defect (fixed)
py-josepy @1.0.1 conflicts with py-acme @0.20.0
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | Schamschula (Marius Schamschula) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | py-josepy py-acme |
Description
---> Activating py27-josepy @1.0.1_0+universal Error: Failed to activate py27-josepy: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/jws is being used by the active py27-acme port. Please deactivate this port first, or use 'port -f activate py27-josepy' to force the activation.
Change History (4)
comment:1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | py-josepy conflicts with py-acme → py-josepy @1.0.1 conflicts with py-acme @0.20.0 |
---|
comment:2 Changed 7 years ago by Schamschula (Marius Schamschula)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | fixed |
---|---|
Status: | closed → reopened |
The deactivate hack is needed in the py-josepy port, not in the py-acme port.
comment:4 Changed 7 years ago by Schamschula (Marius Schamschula)
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Note: See
TracTickets for help on using
tickets.
Looks like
jws
has moved from py-acme to py-josepy. If I forcibly deactivate py27-acme @0.20.0, then of course I can activate py27-josepy @1.0.1, and I can also upgrade py27-acme to @0.21.0. So py-josepy needs to use the deactivate hack to deactivate py27-acme < 0.21.0 before activating.