Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Apr 2009 10:23:24 -0400
From:      Jerry <gesbbb@yahoo.com>
To:        freebsd-ports@freebsd.org
Subject:   Re: Portupgrade still broken?
Message-ID:  <20090408102324.3b1cec27@scorpio>
In-Reply-To: <b79ecaef0904080551x74c80227h1a4ba5d2adcca905@mail.gmail.com>
References:  <b79ecaef0904080551x74c80227h1a4ba5d2adcca905@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/iZ3WUwL7YKPRJnqjXFRb.qw
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, 8 Apr 2009 13:51:48 +0100
Chris Rees <utisoft@googlemail.com> wrote:

>Dear all on freebsd-ports@,
>
>I recall from
>http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
>that there was a bug in portupgrade last year, causing it to break
>when a port is recursively (-R) upgraded; it's surfacing for me too :(
>
>[chris@amnesiac]/usr/ports/ports-mgmt/portupgrade% portupgrade
>--version portupgrade 2.4.6
>
>Is this a 'fixed' version, or not? I think it's the most recent...
>
>[chris@amnesiac]/usr/ports/ports-mgmt/portupgrade% sudo portupgrade
>-rR emacs xterm curl php5-mbstring
>otp-md5 488 am9338 ext
>Password:
>[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 263
>packages found (-3 +3) (...)... done]
>[Gathering depends for editors/emacs
>..........................................................................=
...........................................................................=
...........................................................................=
.......................................................................
>done]
>[Exclude up-to-date packages
>..........................................................................=
.............
>done]
>/usr/local/lib/ruby/site_ruby/1.8/pkginfo.rb:74:in `initialize': : Not
>in due form: <name>-<version> (ArgumentError)
>        from /usr/local/sbin/portupgrade:614:in `new'
>        from /usr/local/sbin/portupgrade:614: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:1305:in `call'
>        from /usr/local/lib/ruby/1.8/optparse.rb:1305:in
> `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1301:in
> `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1301:in
> `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1249:in
> `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1249:in
> `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1243:in
> `order!' from /usr/local/lib/ruby/1.8/optparse.rb:1236:in `order'
>        from /usr/local/sbin/portupgrade:565:in `main'
>        from /usr/local/lib/ruby/1.8/optparse.rb:787:in `initialize'
>        from /usr/local/sbin/portupgrade:229:in `new'
>        from /usr/local/sbin/portupgrade:229:in `main'
>        from /usr/local/sbin/portupgrade:2208
>
>Is the bug still there, or is my pkgdb hosed? If so, how do I fix it?

I have just started getting the same error output. I switched back to
portmanager.

--=20
Jerry
gesbbb@yahoo.com

The primary function of the design engineer is to make things
difficult for the fabricator and impossible for the serviceman.

--Sig_/iZ3WUwL7YKPRJnqjXFRb.qw
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)

iEUEARECAAYFAkncs2UACgkQBvaKIJWWCO1/GgCRAS2n1DPzdhQY2e4s3E7Wid9Z
SQCfV+3uG6hWNC7Tm9KTbdahWMGrKF4=
=u9+4
-----END PGP SIGNATURE-----

--Sig_/iZ3WUwL7YKPRJnqjXFRb.qw--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090408102324.3b1cec27>