Date: Tue, 12 Feb 2008 09:17:54 -0600 From: "Conrad J. Sabatier" <conrads@cox.net> To: freebsd-ports@freebsd.org Subject: Numerous unpleasant surprises in latest portupgrade Message-ID: <20080212091754.28821ab4@serene.no-ip.org>
next in thread | raw e-mail | index | archive | help
The latest portupgrade suddenly seems to have become *very* unintuitive,
and extremely quirky/buggy. Some of the error/info messages no longer
make any sense at all to me, either!
For instance, I've always used the following options in pkgtools.conf:
PORTUPGRADE_ARGS = ENV['PORTUPGRADE'] || \
'--distclean ' + \
'--new' + \
'--uninstall-shlibs'
But now, it seems that the "--new" switch disables portupgrade entirely,
even if the "-f" switch is used! I've had to remove it to get anything
done at all. For instance (with --new enabled):
# portupgrade -fOv TekNap
---> Reading default options: --distclean --uninstall-shlibs
---> Session started at: Tue, 12 Feb 2008 09:03:50 -0600
** None has been installed or upgraded.
---> Session ended at: Tue, 12 Feb 2008 09:03:50 -0600 (consumed
00:00:00)
Huh? What is that supposed to even mean???
In addition, there seem to be some parsing errors going on re: MAKE_ARGS.
I've had the following defined for TekNap for quite some time now
and never had any trouble before (ignore wrap):
'net-p2p/teknap' =>
'CONFIGURE_ARGS+="--with-default-server=foo-bar.org:8888:user:pass
--with-pthread"',
(note the embedded hyphen in the server name; perhaps the culprit?). This
now causes the following output from portupgrade -akO and similar
multi-package commands:
# portupgrade -akO
** Makefile possibly broken: net-p2p/teknap:
make: illegal option -- -
usage: make [-BPSXeiknqrstv] [-C directory] [-D variable]
[-d flags] [-E variable] [-f makefile] [-I directory]
[-j max_jobs] [-m directory] [-V variable]
[variable=value] [target ...]
/usr/local/sbin/portupgrade:1433:in `get_pkgname': Makefile broken
(MakefileBrok enError)
from /usr/local/sbin/portupgrade:622:in `main'
from /usr/local/sbin/portupgrade:613:in `each'
from /usr/local/sbin/portupgrade:613:in `main'
from /usr/local/sbin/portupgrade:588:in `catch'
from /usr/local/sbin/portupgrade:588:in `main'
from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `call'
from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `parse_in_order'
from /usr/local/lib/ruby/1.8/optparse.rb:1299:in `catch'
... 6 levels...
from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize'
from /usr/local/sbin/portupgrade:229:in `new'
from /usr/local/sbin/portupgrade:229:in `main'
from /usr/local/sbin/portupgrade:2173
In addition, after upgrading icu, I decided to try upgrading all the
packages that required it as well, with:
#pkg_info -qR icu|xargs portupgrade --batch -fkOv (to avoid any of the
bugginess seen with some of the recursive stuff)
This seems to trigger a near-endless cycle of information fetching of
the type:
97401 p0 S+ 0:00.01 sh -c cd /usr/ports/deskutils/alacarte && env
make -V PKGNAME -V IGNORE -V NO_IGNORE 2>&1
97402 p0 R+ 0:00.00 make -V PKGNAME -V IGNORE -V NO_IGNORE
What in the world happened? And when will it be back to normal?
--
I turned to speak to God,
About the world's despair,
But to make bad matters worse,
I found God wasn't there.
-- Robert Frost, American poet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080212091754.28821ab4>