Subject: Re: Debugging pkg_comp
To: None <>
From: Christopher W. Richardson <>
List: tech-pkg
Date: 04/05/2005 16:56:14
Hash: SHA1


I've now put the crack pipe down.  Please allow me to rephrase my

"Christopher W. Richardson" <> writes:

> PKG_COMP ==> Checking if pkg_install is up to date
> PKG_COMP ==> pkg_install is out of date; rebuilding
> [...]
> ===> Installing for pkg_install-20050318
> pkg_admin: Cannot chdir to /var/db/pkg: No such file or directory
> But if I enter the chroot and try to make package in
> pkgtools/pkginstall, I get:
> ==> Installing for pkg_install-20050318
> ===> pkg_install-20050318 is already installed - perhaps an older version?
> *** If so, you may use either of:
> ***  - "pkg_delete pkg_install-20050318" and "/usr/bin/make reinstall" to upgrade properly
> ***  - "/usr/bin/make update" to rebuild the package and all of its dependencies
> ***  - "/usr/bin/make replace" to replace only the package without re-linking
> ***    dependencies, risking various problems.
> *** Error code 1

And, in point of fact:

cwr@achilles#pkg_info -a | grep -i pkg_install
pkg_install-20050318 Package management and administration tools
for pkgsrc

and also in the chroot:

pkg_comp:default.conf# pkg_info -a | grep -i pkg_install
pkg_install-20050318 Package management and administration tools for pkgsrc

Now, if I'm understanding things correctly, it's trying to build
pkg_install at makeroot time presumably because the pkg_install
that gets installed in the chroot from the 2.0.2 sets is older
thank the one installed from pkg_src on the running system.

So, I guess the first outstanding question remains as to whether
the failure to chdir to /var/db/pkg for the creation of
pkg_install is a problem.  Is anyone else seeing this?  Any ideas
on how to track down the source of the problem?

The second question is, is there (should there be?) a way to let
it know that pkg_install on the installed system is current?

Version: GnuPG v1.4.1 (NetBSD)
Comment: Processed by Mailcrypt 3.5.8 <>