Khairil Yusof wrote:
On Sat, 2003-08-09 at 22:07, Bob Perry wrote:
I run FreeBSD 4.7 RELEASE. Just ran the portversion command for the
first time since last Saturday and the ouptut indicated that my
installed packages were up-to-date. Thought it odd so I ran pkg_version
command and picked
It doesn't read the tree. It uses INDEX.db, which you are supposed to
build after each cvsup of ports-all. To build INDEX.db, you need a
current version of INDEX. I get too many messages from portsdb -U and
use the sequence make index and then portsdb -u. I run these
everytime I cvsup
On Sunday 10 August 2003 07:55 am, Bob Perry wrote:
Khairil Yusof wrote:
On Sat, 2003-08-09 at 22:07, Bob Perry wrote:
I run FreeBSD 4.7 RELEASE. Just ran the portversion command for
the first time since last Saturday and the ouptut indicated that
my installed packages were up-to-date.
All better! I brought the 9 packages in need of upgrade up to-date and
deinstalled two of the three orphaned packages, per FreshPorts. The
third orphan, ruby-1.6.8.2003.04.19, found a home somehow.
Bob
Original Message
Subject:Portupgrade Broke?
Date: Sat, 09 Aug
On Sat, 2003-08-09 at 22:07, Bob Perry wrote:
I run FreeBSD 4.7 RELEASE. Just ran the portversion command for the
first time since last Saturday and the ouptut indicated that my
installed packages were up-to-date. Thought it odd so I ran pkg_version
command and picked up 9 packages in
I run FreeBSD 4.7 RELEASE. Just ran the portversion command for the
first time since last Saturday and the ouptut indicated that my
installed packages were up-to-date. Thought it odd so I ran pkg_version
command and picked up 9 packages in need up upgrade and several
orphaned packages
