Date: Tue, 25 Sep 2001 20:11:35 +0200 (SAST) From: The Psychotic Viper <psyv@sec-it.net> To: Francesco Casadei <fcasadei@inwind.it> Cc: freebsd-questions mailing list <freebsd-questions@FreeBSD.ORG> Subject: Re: ``? origin unknown'' using portversion Message-ID: <20010925200757.I69917-100000@lucifer.fuzion.ath.cx> In-Reply-To: <20010925123534.A3954@goku.kasby>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Tue, 25 Sep 2001, Francesco Casadei wrote: > Hi all, > I'm having problems using portversion. I do not understand how to fix "? > origin unknown" for certain ports. > > # cd /usr/ports > # portversion -v > XFree86-3.3.6 ? origin unknown > XFree86-aoutlibs-3.3.3 ? origin unknown > XFree86-contrib-3.3.6 ? origin unknown > Xaw3d-1.5 ? origin unknown > apache-1.3.20 ? origin unknown > autoconf-2.13_1 = up-to-date with port > automake-1.4.5_1 = up-to-date with port > bash-2.04 ? origin unknown > boehm-gc-5.3_1 = up-to-date with port > bpft-2.0 ? origin unknown > bzip2-1.0.1 = up-to-date with port > cdrecord-1.9 ? origin unknown > crack-5.0 ? origin unknown > cvsup-16.1d ? origin unknown > cvsweb-1.112.1.82 = up-to-date with port > daemontools-0.70_1 ? origin unknown > djbdns-1.05 ? origin unknown > docbook-1.2 ? origin unknown > docbook-241 ? origin unknown > docbook-3.0 ? origin unknown > docbook-3.1 ? origin unknown > docbook-4.0 ? origin unknown > docbook-4.1 ? origin unknown > docproj-1.9 ? origin unknown > [...] > > From portversion(1) manpage: > > [...] > ? The installed package does not appear in the database. This > could be because the port has been removed from the official > ports tree, or because the package was installed from an unoffi- > cial (or not yet committed) port, or because the index file has > not been updated in sync with the tree yet. > > ! The installed package does not have an origin recorded. This > could be because the package was installed long ago. You can run > ``pkgdepfix -o'' to complete missing origins. > > You can cope with most out-of-date situations by updating the ports tree > and running ``portsdb -U''. (See portsdb(1) for details) > [...] > > So, I CVSup'd the Ports Collection, ran ``portsdb -Uu'' to rebuild INDEX and > ``pkgdepfix -o'' to fix missing origins. > I'm still having the same output from portversion. Furthermore, not all ports > are found running a ``make search name=portname''. For example: > > # cd /usr/ports > # make search name=samba > # cat /usr/ports/net/samba/pkg-comment > A free SMB and CIFS client and server for UNIX > > Actually, I have installed samba-2.0.7 from the Ports: > > # portversion -v samba > samba-2.0.7 ? origin unknown > > but portversion is unable to detect that this port needs updating: > > # grep PORTVERSION /usr/ports/net/samba/Makefile > PORTVERSION= 2.0.10 > > The problem does not show up using the good 'old' pkg_version: > > # pkg_version -vs samba > samba-2.0.7 < needs updating (port has 2.0.10) > > OS version is: > > # uname -a > FreeBSD goku.kasby 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Sep 19 20:12:40 CEST > 2001 root@goku.kasby:/usr/obj/usr/src/sys/GOKU i386 > > portupgrade version is: > > # pkg_info -I 'portupgrade*' > portupgrade-20010818b Very powerful FreeBSD ports/packages upgrading tool and > mor > > Francesco Casadei > -- Is the ports directory complete? If so check permissions, seems the system cant find/see the ports to compare against. HTH PsyV To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010925200757.I69917-100000>