[MacPorts] #71365: mumps upgrade from 5.7.3_0 fails to configure
MacPorts
noreply at macports.org
Thu Nov 21 18:15:16 UTC 2024
#71365: mumps upgrade from 5.7.3_0 fails to configure
----------------------+---------------------------
Reporter: murrayE | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.10.4
Resolution: | Keywords: sequoia arm64
Port: mumps |
----------------------+---------------------------
Comment (by jmroot):
Let me prefix this by saying that a port declaring a build conflict with
itself results in very bad UX and such cases should be fixed properly so
manual intervention by the user isn't necessary.
The rebuild is being triggered by rev-upgrade, which can only detect
broken linking in ports that are active. So by definition it can never
rebuild any port that has a built conflict with itself. It would be good
to see what exactly is broken, which will be shown by `sudo port -dy rev-
upgrade`.
Because mumps is not outdated, running `sudo port -f deactivate mumps` and
then `sudo port install mumps` will just reactivate the still-broken
version that was already installed. To get a new build, you would have to
run:
{{{
sudo port -f deactivate mumps
sudo port destroot mumps +gfortran+mpich+openblas
sudo port -f uninstall mumps
sudo port -s install mumps +gfortran+mpich+openblas
}}}
--
Ticket URL: <https://trac.macports.org/ticket/71365#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list