New Ticket     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #19912 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

texlive_base @2007_7+no_x11 now requires openmotif

Reported by: macports@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.7.1
Keywords: Cc: macports@…
Port: texlive_base

Description

texlive_base requires openmotif when upgrading from 2007_6 to 2007_7 with no_x11 variant selected. 2007_6+no_x11 did not require openmotif

Change History

  Changed 3 years ago by macports@…

  • cc macports@… added

Cc Me!

follow-up: ↓ 3   Changed 3 years ago by blb@…

  • status changed from new to closed
  • resolution set to fixed

Try selfupdating again, as that was only a brief issue (r52085 should have fixed this by moving the openmotif dependency into a +motif variant).

in reply to: ↑ 2   Changed 3 years ago by macports@…

Replying to blb@…:

Try selfupdating again, as that was only a brief issue (r52085 should have fixed this by moving the openmotif dependency into a +motif variant).

Sorry, it does not work. r52085 still pulls in openmotif while trying to upgrade with no_x11 variant selected. What looks strange, openmotif is not reported as dependency when no_x11 variant is selected. I would say we need to put back lib:libXm:openmotif in depends_lib-delete in line 83

follow-up: ↓ 5   Changed 3 years ago by blb@…

Hmm, it could be that the registry is remembering it, so try uninstalling then reinstalling:

sudo port -f uninstall texlive_base
sudo port install texlive_base +no_x11

in reply to: ↑ 4   Changed 3 years ago by macports@…

Replying to blb@…:

Hmm, it could be that the registry is remembering it, so try uninstalling then reinstalling: {{{ sudo port -f uninstall texlive_base sudo port install texlive_base +no_x11 }}}

Uninstalling texlive_base did the trick. I wonder if my previous (and canceled) attempt to do upgrade without specifying no_x11 variant poisoned the registry. Thanks a lot for your help!

Note: See TracTickets for help on using tickets.