portupgrade/make install problem.

Andy Hauser andy-freebsd at splashground.de
Thu Jul 31 18:02:26 PDT 2003


On Mon, Jul 14, 2003 at 12:48:55PM -0400, Tim Kellers wrote:
> On Monday 14 July 2003 12:07 pm, Michael Edenfield wrote:
> > * Tim Kellers <timothyk at wallnet.com> [030714 11:33]:
> > > The port built and installed without a hitch.
> > >
> > > uname -a from the troublesome fileserver:
> > >
> > > FreeBSD 10.0.1.2 4.8-STABLE FreeBSD 4.8-STABLE #1: Fri Jul 11 15:57:18
> > > EDT 2003     timothyk at 10.0.1.9:/usr/obj/usr/src/sys/CHANGLING  i386
> > >
> > > uname -a from the laptop with /usr/ports NFS mounted:
> > > FreeBSD mts-128.wallnet.com 4.8-STABLE FreeBSD 4.8-STABLE #10: Fri Jul 11
> > > 13:31:14 EDT 2003     timothyk at 10.0.1.9:/usr/obj/usr/src/sys/NEMESIS 
> > > i386
> >
> > 4.8 should definitely not be having this problem.  Try to run:
> >
> > pkg_info -q -O some/portname
> >
> > and see what reply you get.
> >
> > --Mike
> 
> On the broken fileserver:
> 
> su-2.03# pkg_info -q -O aim-1.5.234/
> pkg_info: package cvsupd-bin-16.1 has no origin recorded
> pkg_info: package ghostscript-6.01_1 has no origin recorded
> pkg_info: /var/db/pkg/jdk-tutorial-1.1.8/+CONTENTS: No such file or directory
 
I just experienced the same problem on a 5.1-RELEASE.

rm -rf the /var/db/pkg/$PORT

where $PORT are the ones pkg_info complains
about with "/var/db/pkg/$PORT/+CONTENTS: No such file or directory"
seemed to have fixed the problem.

Andy


More information about the freebsd-ports mailing list