#47849 closed defect (fixed)
select-1.0: overwrites "name" portfile option
Reported by: | zzanderr | Owned by: | lpsinger (Leo Singer) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | seanfarley (Sean Farley), mndavidoff (Monte Davidoff), cooljeanius (Eric Gallager) | |
Port: | select-1.0 |
Description
Attempted to build with the variants +notebook+parallel+pyqt4+terminal.
py27-ipython with the same variants (and +scientific) builds fine. I tried building py34-ipython with py27-ipython deactivated and obtained the same result.
Attachments (1)
Change History (8)
Changed 9 years ago by zzanderr
Attachment: | py34-ipython_log added |
---|
comment:1 Changed 9 years ago by mf2k (Frank Schima)
Cc: | aronnax@… removed |
---|---|
Keywords: | powerpc leopard added; PPC ipython removed |
Owner: | changed from macports-tickets@… to aronnax@… |
Port: | py-ipython added; py34-ipython removed |
comment:2 follow-up: 4 Changed 9 years ago by mndavidoff (Monte Davidoff)
comment:4 Changed 9 years ago by larryv (Lawrence Velázquez)
Keywords: | powerpc leopard removed |
---|---|
Port: | select-1.0 added; py-ipython removed |
Resolution: | → fixed |
Status: | new → closed |
Summary: | py34-ipython fails in destroot stage on PPC Leopard → select-1.0: overwrites "name" portfile option |
Replying to md14-macports@…:
I suspect this problem is related to the changes for #34326.
It is, but probably not in the way you expect.
comment:5 Changed 9 years ago by zzanderr
Apparently that solves it.
For a minute it looked like sheer magic, until I realized I did a "port selfupdate" automatically (and unconsciously) a few minutes before.
Thanks for your help.
Note: See
TracTickets for help on using
tickets.
I get the same error trying to install py34-ipython on Yosemite, so the problem is not specific to either PPC or Leopard. Note these lines in the py34-ipython_log attachment:
The py34-ipython port is trying to install files in the python27 framework instead of the python34 framework.
This problem does not seem to be specific to the py-ipython port either. I get similar errors with other py34-* ports.
I suspect this problem is related to the changes for #34326.