On Tue, 7 Nov 2000, Ryan Ordway wrote:

> > Do you have a "/usr/pkgsrc/packages" directory?
> 
> 	Yes.
>  
> > The problem is that unexpected output of "pkg_info" is being fed,
> > inappropriately, to "dc" as part of the overall size calculation
> > ("pkg_info -qS"). The unexpected output is a complaint that PKG_PATH
> > does not exist. This complaint won't occur with NetBSD-1.4.3 and
> > NetBSD-1.5, for which "pkg_info -q" is quieter.
> 
> 	Do you mean PKGPATH? One thing I HAVE done is set the base
> directory to /usr/local instead of /usr/pkg in my mk.conf file... 

No, it's PKG_PATH. What does "pkg_info -qs perl" give? If you get text
in addition to the numbers, you may be able to keep it quiet by
setting "PKG_PATH" to a directory that exists (/usr/local/pacakges?)

> > > 	So what is up with all of these dc errors? Anyone else have a
> > > problem with this? Is there an easy fix?
> > 
> > Most people saw this only when PKG_PATH was set to empty in certain
> > versions of bsd.pkg.mk, but this was later reverted. So you shouldn't
> > see this with the _latest_ pkgsrc, even with the old pkg_info, unless
> > /usr/pkgsrc/packages doesn't exist.
> 
> 	I'm unpacking the most recent pkgsrc.tar.gz tarball right now,
> I'll see how it goes...
> 
> 	Welp... using the new pkgsrc didn't help, I'm still getting all of
> the dc errors. More ideas? :-)

It's not that big of a deal. The only problem is that the
/var/db/pkg/<package>/+SIZE_ALL file is filled with garbage, so
"pkg_info -S <package>" will spew garbage. If you it really bugs you,
you could upgrade to 1.4.3/1.5_BETA2/1.5 as available, to get the
quieter "pkg_info", and rebuild all the affected packages.


Frederick