[MacPorts] #62951: port - unable to recover
MacPorts
noreply at macports.org
Tue May 25 11:10:13 UTC 2021
#62951: port - unable to recover
-------------------------+--------------------
Reporter: mouse07410 | Owner: (none)
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: base | Version:
Resolution: worksforme | Keywords:
Port: |
-------------------------+--------------------
Changes (by jmroot):
* status: new => closed
* resolution: => worksforme
Comment:
Replying to [comment:2 mouse07410]:
> @Joshua, first - thank you for answering my pretty vague cry for help.
You're welcome.
> screwed up the existing installation, probably by allowing two port
updates to start at the same time;
There should be locking in place to prevent that from causing problems.
Bugs are always possible of course, so let us know if you can ever
reproduce such a problem (admittedly unlikely now I know.)
> It would be great if there were tools to repair and/or restore Macports
registry either from {{{/opt/local/var/macports/software}}} or from what's
in {{{/opt/local/bin}}}.
Could be an interesting research problem to see how good a job you can do
reconstructing the registry from that information. Some of it just plain
doesn't exist (like requested status), some of it suffers from ambiguity
(multiple ports could have provided a given file.)
> But if I decide to build for Intel and M1 - what should I specify as
"universal arch"? {{{universal_archs arm64 x86_64}}}?
Yes, that would be the correct setting on Big Sur. It's also the default,
so you could just comment out universal_archs in macports.conf.
--
Ticket URL: <https://trac.macports.org/ticket/62951#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list