make install, portupgrade, etc broken
Jonathan
jonathan at sirtis.org.uk
Tue Jul 15 02:55:31 PDT 2003
Tim Kellers wrote:
I think we've got 2 threads mixed here, but to review.
>
> I cvsupped July 11 and did a make buildworld, make buildkernel
> KERNCON=CHANGLING, reboot make installworld, mergemaster on 3 different
> boxes. All is/was well on 2 of the 3 boxes, but on the third any/every make
> install or portupgrade [filename] errors out with Error Code 1 right after
> make install checks for a previous installation. The option
> FORCE_PKG_REGISTER="yes'" allows the installation to completesuccessfully,
> the portupgrade -m FORCE_PKG_REGISTER="yes'" switch also succeeds. I NFS
> mounted /usr/ports from the broken fileserver on a laptop (4.8-STABLE from
> same cvs updated sources) and I can make install or portupgrade with no
> errors at all.
>
> pkg_info -q -O some/port on the laptop returns the package name of the
> installed port
>
> pkg_info -q -O some/port on the fileserver returns:
>
> 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 found this on Google which might help:
http://lists.freebsd.org/pipermail/freebsd-questions/2003-March/000349.html
which says:
########################################################################
> Upon attempts to use 'pkg_add' utility, I get a string of error messages
> such as the following:
>
> pkg_add: package wterm-6.2.7a1 has no origin recorded
> pkg_add: package wmtime-1.0b2 has no origin recorded
>[...]
> 2) Theories about what causes this condition.
> (Least important)
That's easy - the packages are old enough that they didn't record
their origin.
> 1) The methodology by which I can correct this error condition.
> (Most important)
Installing newer versions of the packages is the obvious way. You can
also go into /var/db/pkg/wterm-6.2.7a1/+CONTENTS and add a line that
says "@comment ORIGIN:x11/wterm" after the @name line. There may be
other magic required as well, but this worked for the one I did it to.
########################################################################
Regards,
Jonathan
More information about the freebsd-questions
mailing list