Re: [solved]: r2421600 amd64 /var/db/pkg

From: Bryan Drewery <bryan_at_shatow.net>
Date: Sun, 04 Nov 2012 07:58:11 -0600
On 11/4/2012 5:06 AM, Darrel wrote:
> 
> On Sat, 3 Nov 2012, Garrett Cooper wrote:
> 
>> On Sat, Nov 3, 2012 at 6:15 PM, Darrel <levitch_at_iglou.com> wrote:
>>
>> ...
>>  
>> Yes, the existing man 8 pkg does not seem to match all of the facts.
>>
>>
>>     What you probably ran into is the common chicken and egg problem
>> where
>> if pkgng is upgraded ports, it blows up when it tries to deinstall the
>> package, or similarly, when portmaster is upgraded, it doesn't halt the
>> upgrade and restart it properly.
>>     It's most likely still a problem; I'm going to doublecheck to make
>> sure
>> that's the case and file PRs if it is.
> 
> Thanks, Garrett.  For my current problem I am simply going to delete the
> errant portmaster-3.14 from /var/db/pkg and then run 'portmaster -a -f
> -D' with the hope that portmaster-3.14_7 can fix things.  If not I will
> try reinstalling, the are only a few things installed- freeradius,
> postgresql, and about a dozen others.

This is overkill. You either have a pkg_install database or a pkgng
database. Determining which will save you time.

After you run pkg2ng, pkg_info will no longer work. It will complain
about corrupted packages, since all the data is gone, but portmaster has
stored additional information there, which confuses pkg_info.

Check the output of 'pkg info'. If it lists all your packages, you are
done. Nothing more to do.

If not, run pkg2ng.

Also, you can see any packages that have not converted with:
    find /var/db/pkg -name +CONTENTS
If nothing comes up, they are already all converted.


Bryan
Received on Sun Nov 04 2012 - 12:58:21 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:31 UTC