Hi Greg,
Greg Troxel wrote:
Riccardo Mottola <[email protected]> writes:
There may well be a bug in pkg_rr, but you are reporting that the system
has multiple issues. pkg_rr is just a shell script and is not that
complicated. First:
A) check that you have only one pkgdb, in /usr/pkg/pkgdb, and not in
/var/db/pkg
Wow, you got it. I didn't think of this, because this is a system that
was born with 10.0 updated to 10.1, it is not a historical upgraded system!
The bad news is that actually /var/db/pkg is more up-to-date, it
contains all recent built and replaced files, but /usr/pkg/pkgdb is also
very recent.
It looks like "make install" is installing in /var/db/pkg and "pkg_add"
in /usr/pkg/pkgdb
I fear actually that 10.1 upgrade broke something here and found out why.
Read below for my idea:
B) pkg_admin {rebuild, rebuild-tree, check}
C) update pkgsrc to a consistent view (pkgsrc-2025Q3, or head, all of
it the same). run cvs diff to understand that all changes are
intended
It is, I have it on a shared NFS for a couple of systems. But clear that
I first need to fix somehow the pkgdb mess
You might have stuff in mk.conf that is wrong. Reduce it to the bare
minimum, and include it when asking for help.
Overall I suspect a broken pkgdb situation but I'm guessin.
It is broken ! mk.conf contains a line it shouldn't:
more /etc/mk.conf
MAKE_JOBS= 2
PKG_DBDIR=/var/db/pkg
# define things for pkgsrc
# create also all dependencies
DEPENDS_TARGET=package-install
# work here
WRKOBJDIR=/disk2/pkg-workdir
# save our tarball packages here
PACKAGES=/disk2/pkg-bin
I wonder how PKG_DBDIR got in here, I suppose an error in merge after
10.1 upgrade
I have an idea on how to fix it: delete all packages, delete /usr/pkg,
delete db's and since I saved all binary packages built up to now,
install those. What is obsolete/missing will be built later from source
Riccardo
