[MacPorts] #14321: Moving from DarwinPorts to MacPorts: Registry corruption (was: Moving from Darwin Ports to MacPorts: Registry corruption)
MacPorts
noreply at macports.org
Tue Nov 11 01:55:28 PST 2008
#14321: Moving from DarwinPorts to MacPorts: Registry corruption
-----------------------------------+----------------------------------------
Reporter: jlnicolson at gmail.com | Owner: jmpp at macports.org
Type: defect | Status: new
Priority: High | Milestone: MacPorts base bugs
Component: base | Version: 1.6.0
Resolution: | Keywords:
Port: |
-----------------------------------+----------------------------------------
Changes (by ryandesign at macports.org):
* cc: wheinbockel at gmail.com, ryandesign at macports.org (added)
Comment:
Replying to [comment:3 wheinbockel@…]:
> Since this issue does not appear to have been fixed and there has been
no activity for ~6 months, here was at least a related issue that I had:
It's hard to know what to fix; there aren't enough specifics about the
issues. The first issue, that of an allegedly corrupted registry, is hard
to debug since the user already deleted the MacPorts installation,
complete with its registry. The second issue, that of a failed preflight
script during reinstallation, is hard to debug without some output from
that preflight script.
> Since /opt is present, but the link target /private/opt does not exist,
the mkdir /opt/* in the preflight script fails.
> A simple {{{sudo mkdir /private/opt}}} will fix the issue.
I don't think this issue is related to the ones reported in this ticket.
That's also not the recommended fix for it. See issue #13707.
--
Ticket URL: <http://trac.macports.org/ticket/14321#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list