Damaged database?

[Ryan Schmidt]

On Feb 25, 2013, at 16:40, Adam Dershowitz wrote:

> On Feb 25, 2013, at 1:48 PM, Ryan Schmidt wrote:
> 
>> On Feb 24, 2013, at 17:20, Adam Dershowitz wrote:
>> 
>>> dersh$ sqlite3 /opt/local/var/macports/registry/registry.db "select load_extension('/opt/local/var/db/dports/sources/rsync.rsync.darwinports.org_dpupdate1/base/src/cregistry/macports.sqlext');select t1.id, t1.name from ports t1 where t1.name = 'gst-plugins-base'"
>> 
>> This project changed its name and domains from DarwinPorts to MacPorts in 2006:
>> 
>> https://trac.macports.org/wiki/MacPortsHistory
> 
> I know, but this has me really confused.  The only reason that I needed a path like that is that I was trying to build macports.sqlext.  As a user, that shouldn't be necessary, but to try to test it, I was trying to use it.  
> I know that I have reinstalled macports in the past few years, so I don't understand at all where that old URL is coming from.

What all is in /opt/local/var/db/dports/sources? As you said below, you may have old directories there that should be removed.


>> Please update your rsync URL to match.
> 
> I am not sure where this is located?  I haven't put in a URL, and my sources.conf and macports.conf don't have anything about darwin.  

It would be in sources.conf. What do you have in sources.conf?


> I think that the path might be an old path, that I haven't done an rsync in many years.

What do you use instead? svn?


> I think that I just never deleted it.  But, I was doing a search for macports.autoconf.mk, since I needed it to build macports.sqlext and that is where I found it.  Which probably means that it is an old version of macports.autoconf.mk

Possibly, and also possibly an old version of the extension; we should make sure you're building the current version of the extension.



>> Error: no such collation sequence: VERSION
>> 
>> This means the extension did not actually load; it's the extension that provides the VERSION collation sequence.
> 
> I tried making macports.sqlext, and if it finds it, then I get the same error.  So, it seems that it is no loading, both if I do it by hand, or just using normal macports commands.
> 
> Perhaps it really is getting to the point, where I should just wipe all my macports and rebuild?   

You can do that if you like. But we may be able to repair your registry, depending on how it's damaged. To know how it's damaged, we need to be able to SELECT from it. To be able to SELECT from it, we need to load the MacPorts SQLite extension.