[MacPorts] #48486: lion buildslave registry damaged
MacPorts
noreply at macports.org
Thu Oct 15 12:39:24 PDT 2015
#48486: lion buildslave registry damaged
-----------------------------+---------------------
Reporter: snc@… | Owner: admin@…
Type: defect | Status: new
Priority: High | Milestone:
Component: server/hosting | Version:
Resolution: | Keywords:
Port: |
-----------------------------+---------------------
Comment (by ryandesign@…):
How much disk space is free? Some ports, like clang, need 10-20GB free,
and the free space on the builders does decrease over time as more and
more ports get added to MacPorts (since all ports stay installed (though
inactive) on the builders).
I don't know how one would rebuild a corrupted sqlite database. Looking
around on the internet, one suggestion is to try to dump the data to a new
database, like:
{{{
sqlite3 registry.db ".dump" | sqlite3 registry.db.new
mv registry.db registry.db.old
mv registry.db.new registry.db
}}}
But this might not work, depending on the nature of the corruption.
The next best solution would be to restore the virtual machine to a state
before the registry corruption occurred (before August 1, 2015).
If we can't repair the registry and can't restore the machine, the next
idea would be to delete the registry.db file and the contents of the
/opt/local/var/macports/software directory, which should make MacPorts
think no ports are installed. If no ports were active when the corruption
occurred, I think this should work. If the corruption occurred in the
middle of a build, when ports were active, we will soon learn about it
through activation failure messages.
--
Ticket URL: <https://trac.macports.org/ticket/48486#comment:5>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list