Package database problems

Paul Schmehl pschmehl_lists at tx.rr.com
Thu Nov 16 21:20:03 UTC 2017


--On November 16, 2017 at 9:34:05 PM +0100 Kurt Jaeger <lists at opsec.eu> 
wrote:

>
> You probably have to clean it up.
>
> I would do this:
> - use the list of old-style packages in /var/db/pkg, together
>   with the output of pkg info, to generate a list of
>   packages that you need after clean up.
>   My list looks like this, approx. 2000 entries:
> -------------
> [...]
> devel/automake
> devel/automake-wrapper
> devel/automoc4
> devel/binutils
> devel/bison
> [...]
> -------------
> - Then build all the packages from your list via poudriere,
>   and generate a repo of all those up2date packages.
> - Then (this is dangerous, if done via remote, keep a few
>   ssh sessions running in parallel, if one fails):
>   mkdir /usr/local/OLD
>   cd /usr/local
>   mv * OLD/
> - Now no packages are installed
> - re-add all the packages, restore the config from OLD/...
>

Ugh.

>> I didn't setup this server to begin with. I recall, a
>> while back, instructions for switching to pkgng. Is that what wasn't
>> done?
>
> Yes, something like that.

Should I run pkg2ng now? Would that help?

Paul Schmehl, Retired
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell



More information about the freebsd-ports mailing list