Damaged database?

[Adam Dershowitz]

On Feb 25, 2013, at 5:58 PM, Ryan Schmidt wrote:

> On Feb 25, 2013, at 17:01, Adam Dershowitz wrote:
> 
>> On Feb 25, 2013, at 2:44 PM, Ryan Schmidt wrote:
>> 
>>> 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.
>> 
>> All that is in there is rsync.rsync.darwinports.org_dpupdate1
> 
> I looked on my system (which doesn't use rsync but svn) but as far as I can tell that must be an old directory and can be deleted. Sources currently go in /opt/local/var/macports/sources.

I think that it is probably irrelevant, except that I had a copy of macports.autoconf.mk sitting there, and I used it to build macports.sqlext.  Otherwise, I could not get it to build, because that file was missing.  But, it could be an old version of that file.


> 
> 
>>>>> 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.
>> 
>> Given the above series of questions, clearly something is very screwed up in my install.  I am thinking that the restore didn't go as it appeared.  So, I am going to just try to wipe and rebuild macports.  
> 
> The only thing that we know is screwed up is that something is wrong with the registry entry for this one port on your system, and since we haven't yet seen what the entry says, we don't yet have any ideas about why this happened. There may also be other problems that we don't know about yet. We can either try to repair that one entry and see what happens, or you can uninstall and reinstall MacPorts and all ports if you'd prefer that.
> 

I think that it is better use of time to just reinstall.  So, I am going to go ahead with that.  My initial problems were computer hardware problems, but the first problems showed up while trying to upgrade some ports.  So, the less I have to trust my backup, the better.  I might as well just start fresh.  

Thanks,

--Adam