Date: Tue, 13 May 2008 11:04:01 +0200 From: "Martin Schweizer" <schweizer.martin@gmail.com> To: Kent <kstewart@owt.com> Cc: freebsd-ports@freebsd.org Subject: Re: portupgrade -faP after update to FreeBSD 7.0 Message-ID: <380ccfd60805130204h402caa38s83855c1ae98aab63@mail.gmail.com> In-Reply-To: <200805121004.16951.kstewart@owt.com> References: <380ccfd60804272207i5bfeab97v5ea9966d77456361@mail.gmail.com> <200804280028.32882.kstewart@owt.com> <380ccfd60805120814h5c45948atbaae906a58735936@mail.gmail.com> <200805121004.16951.kstewart@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Kent 2008/5/12, Kent <kstewart@owt.com>: > > > > After successfully update to FreeBSD 7.0 (a described in the > > > > handbook) I startet several times portupgrade -faP after several > > > > pkgdb -F. But now I get the following error: > > > > > > > > portupgrade -faP > > > > > > > > /usr/local/lib/ruby/site_ruby/1.8/pkgversion.rb:41:in `initialize': > > > > ,2: Not in due form: '<version>[_<revision>][,<epoch>]'. > > > > (ArgumentError) > > > > from /usr/local/sbin/portupgrade:638:in `new' > > > > from /usr/local/sbin/portupgrade:638: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' ... 7 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 > > > > > > > > I checked the portupgrade version and also ruby but did not find any > > > > mistakes. What do I wrong? > > > > > > I am assuming that 7.0 has changed ruby/portupgrade processing. There > > > have been problems like this when ruby and the ruby??_bdb? get out of > > > sequence. I would delete portupgrade and ruby\* and then rebuild > > > everything including the index.db. > > > > > > You may get a different answer tomorrow but if rebuilding everything > > > works, you could be half way to being done. > > > > I deleted all ruby ports (as I got from pkg_info) and I also fetch > > /usr/ports/INDEX-/ by makeing make index and by make fetchindes (both > > get the same results). But I still get the same error. > > What do you mean exactly with "I would delete portupgrade and ruby\* > > and then rebuild everything including the index.db."? The same as I > > did? > > The index-?.db has gotten messed up several times after some updates. My > experience was that you have to get portupgrade and ruby in sync and then use > portsdb -fu to rebuild the database. I created the INDEX-7.db by portsdb -fu and yes, portupgrade and ruby are in sync. > Your error looks like a mismatch between portupgrade and ruby. Did you > manually rebuild portupgrade? Yes I did it with make and then make install Regards, -- Martin Schweizer schweizer.martin@gmail.com Tel.: +41 32 512 48 54 (VoIP) Fax: +1 619 3300587
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?380ccfd60805130204h402caa38s83855c1ae98aab63>