Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#34872 closed defect (wontfix)

Failed to install ncurses

Reported by: erik@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.1
Keywords: Cc: jmroot (Joshua Root)
Port: ncurses

Description

port upgrade oudated results in

--->  Deactivating ncurses @5.7_0+darwin_10
--->  Activating ncurses @5.9_1
Error: org.macports.activate for port ncurses returned: Image error: /opt/local/bin/captoinfo is being used by the active ncursesw port.  Please deactivate this port first, or use 'port -f activate ncurses' to force the activation.

Attachments (1)

main.log (204.0 KB) - added by erik@… 9 years ago.

Download all attachments as: .zip

Change History (3)

Changed 9 years ago by erik@…

Attachment: main.log added

comment:1 Changed 9 years ago by ryandesign (Ryan Schmidt)

Cc: jmr@… added
Resolution: wontfix
Status: newclosed

You must not have upgraded your ports in a very long time. The ncursesw port became obsolete 16 months ago (#12605); its functionality was integrated into the existing ncurses port. An upgrade path existed to make this process seamless, but that upgrade path was removed a couple months ago (r91972) because we assumed everyone would have upgraded by now. We usually remove such upgrade paths after 12 months, so you should upgrade your ports at least once every 12 months.

To work around this problem for this port now, you should force ncursesw to uninstall:

sudo port -f uninstall ncursesw

Then you can activate ncurses:

sudo port activate ncurses @5.9_1

comment:2 Changed 9 years ago by erik@…

Thanks for clarifying. I'm learning every day.

Re: long time no upgrade... For a long time, we were content with our setup: If it works, don't fix it:)

Re: upgrade path I appreciate the push to clean current code of (near-)obsolete elements. However, I wonder how much overhead such an upgrade path adds to a port. Is the gain from removing it worth the loss of causing slight trouble for users like myself? I imagine that having it in place is maintenance free. Ignorance is bliss...

Note: See TracTickets for help on using tickets.