Updating ports with portmaster after two month "vacation"

Jeffrey Bouquet jeffreybouquet at yahoo.com
Mon Jan 28 19:29:50 UTC 2013

Probably will follow someone else with the same reply but even more  informative than this one...  reply is at the bottom.  Sorry for the formatting...

--- On Mon, 1/28/13, Edwin L. Culp W. <edwinlculp at gmail.com> wrote:

From: Edwin L. Culp W. <edwinlculp at gmail.com>
Subject: Updating ports with portmaster after two month "vacation"
To: "freebsd-ports" <freebsd-ports at freebsd.org>
Date: Monday, January 28, 2013, 10:56 AM

I have not updated all my ports since the end of Noviember.

I am still using cvsup to update the machine daily and have, what I hope
is, an uptodate kernel and all programes.

# uname -a
FreeBSD home.encontacto.net 9.1-STABLE FreeBSD 9.1-STABLE #391 r229960M:
Sat Jan 26 05:06:18 CST 2013
root at home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO

The first strange thing that I notice is:

#  portversion -v portmaster
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... USING PKGNG
- 959 packages found (-2 +3) (...)... done]
portmaster-3.14_8           >  succeeds port (port has 3.11)

The last thing I remember doing era updating ports to PKGNG and that could
be my problem.  If so, I have no idea how to reconstruct and I'm also not
sure that cvsup is still working as before.   The kernel seems to work fine.

Another error message that I find unusual and can't explain is:

# portmaster -a
===>>> Gathering distinfo list for installed ports

===>>> Starting check of installed ports for available updates

===>>> The ports-mgmt/portmanager port has been deleted: Has expired: Does
not support modern ports features such as MOVED, is lacking upstream and
active contributions, and does not support pkgng.  Consider using
ports-mgmt/portmaster, ports-mgmt/portupgrade or pkgng
===>>> Aborting update

I can't understand the relationship to portupgrade.

I'm sure that I missed something very important since portmaster is trying
to use portupgrade.

Thanks for any help.


Bienes Raíces in Coatepec, Veracruz, Mexico

freebsd-ports at freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"

The message about portmanager > portupgrade is not "using" it AFAIK.
Portmanager may still work unless you remove it or permit portmaster to do so.
AFAIK csup/cvsup will no longer work to upgrade ports, I switched all CPU over to svn (devel/subversion) awhile back and have posted in the forum informative
posts.  As to svn for the kernel sources, the freebsd-questions list this month
(jan/enero 2013) has a detailed howto also in that regard.
I would hesitate to use portmaster -a...
portmaster -L --index-only | tee -a /tmp/upgrade.log
wait a while...
grep -A 3 -B 3  version /tmp/upgrade.log  | tee -a /tmp/upgrade2.log
in one xterm   "head -10 /tmp/upgrade2.log | tail -12
 ......................"head -20 /tmp/upgrade2.log | tail -12
......................."head -30 /tmp/upgrade2.log | tail -12
then in another xterm...
portmaster -d -B -P -i -g devel/doxygen devel/cmake # etc as shown in each
segment of the latter file from the pipes.

Sorry for any typos or incomplete information or inaccuracies or easier ways others may currently do it,
especially if one has lesser than thousands of ports installed.

J. Bouquet

More information about the freebsd-ports mailing list