Date: Sun, 5 Oct 2008 17:57:58 +0200 From: Martin Schweizer <lists_freebsd@bluewin.ch> To: freebsd-questions@freebsd.org Subject: portupgrade troubles Message-ID: <20081005155758.GB65233@saturn.pcs.ms>
next in thread | raw e-mail | index | archive | help
Hello I post the questions several months a go but I find until now no solutions. If I use portupgrade -fa I get the folowing error: /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 But get no answer and find no solution for my problem. Any ideas Regards, In the past I did a lot: - /usr/ports/UPDATING: checked all the ruby hints - Find and read the following posts: [snip] Re: portupgrade error - `deorigin': cannot convert nil into String (PkgDB::DBError) From: Kent Stewart (kstewart_at_owt.com) Date: 06/25/04 To: freebsd-stable@freebsd.org Date: Fri, 25 Jun 2004 13:10:44 -0700 On Friday 25 June 2004 12:25 pm, Andy Smith wrote: > Ever since a recent cvsup of ports and a portsdb -Uu, portupgrade > has been giving the following error: > > ---> Session started at: Fri, 25 Jun 2004 18:58:25 +0000 > ---> Session ended at: Fri, 25 Jun 2004 18:58:28 +0000 (consumed > 00:00:03) /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in > `deorigin': cannot convert nil into String (PkgDB::DBError) from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from > /usr/local/sbin/portupgrade:674:in `main' > from /usr/local/sbin/portupgrade:207:in `initialize' > from /usr/local/sbin/portupgrade:207:in `new' > from /usr/local/sbin/portupgrade:207:in `main' > from /usr/local/sbin/portupgrade:1845 > > I have tried: > > - Waiting a day and doing another cvsup > > - Doing make index / portsdb -Uu > > - Removing ruby and portupgrade and reinstalling > > but I still get the same error. > > I also searched the mailing list archives and found someone with a > very similar error: > > http://lists.freebsd.org/pipermail/freebsd-stable/2003-May/001255.htm >l > > however, I've already learnt my lesson about refusing ports, and so > my sup/refuse contains only: > > ports/INDEX > ports/INDEX-5 > > Anyone have any other ideas? Someone on ports said to run portsdb -fu to fix this one. The cooment was > Probably a ruby bug. Rebuilding {pkg|ports}.db from scratch will do, I think. But I thought that was a pkgdb -fu. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" __________________________________________________________________ [snip] Newsgroups: mailing.freebsd.ports Von: s...@FreeBSD.org (Sergey Matveychuk) Datum: Sun, 27 Jan 2008 04:20:30 +0800 (CST) Lokal: Sa 26 Jan. 2008 22:20 Betreff: ports-mgmt/portupgrade-devel Antwort an Autor | Weiterleiten | Drucken | Einzelne Nachricht | Hi! After a long time, I've got a little free time and spent it working for portupgrade. A new version (2.4.0) was released. * Many bugs fixed (thanks to reporters). * At last I've finished rewriting code and portupgrade now controls all tasks (before some port installed without a portupgrade note). As a result portupgrade gathers all depends for a port. It spends a time for preparing in the beginning of a upgrade process. * I've change unused -c and -C options to allow run 'make config-conditional' and 'make config' (force options change) before all processing. Test the release please. To move from portupgrade to portupgrade-devel port, use the command: portupgrade -fo ports-mgmt/portupgrade-devel portupgrade If you'll want to back to stable porupgrade, use the command: portupgrade -o ports-mgmt/portupgrade portupgrade-devel -- Dixi. Sem. _______________________________________________ Von: aryeh.fried...@gmail.com ("Aryeh M. Friedman") Datum: Sun, 27 Jan 2008 07:12:37 +0800 (CST) Lokal: So 27 Jan. 2008 01:12 Sergey Matveychuk wrote: > Hi! > After a long time, I've got a little free time and spent it working for > portupgrade. > A new version (2.4.0) was released. > * Many bugs fixed (thanks to reporters). > * At last I've finished rewriting code and portupgrade now controls all > tasks (before some port installed without a portupgrade note). As a > result portupgrade gathers all depends for a port. It spends a time for > preparing in the beginning of a upgrade process. > * I've change unused -c and -C options to allow run 'make > config-conditional' and 'make config' (force options change) before all > processing. > Test the release please. To move from portupgrade to portupgrade-devel > port, use the command: > portupgrade -fo ports-mgmt/portupgrade-devel portupgrade > If you'll want to back to stable porupgrade, use the command: > portupgrade -o ports-mgmt/portupgrade portupgrade-devel This breaks certain ports (portupgrade -a) that have multiple ports that can satisfy a depends. For example net-p2p/deulge depends on devel/boost but multimedia/miro depends on devel/boost-python. The only difference between boost and boost-python is boost-python sets the -DWITH_PYTHON flag and lists lang/python - -2.5 while boost does not depend on it and makes the user specify the above flag from the command line. Under the old portugrade it relied on miro and/or deluge to detect its own depends and since both did it by xDEP on the installed files either whould be accepted. Under the new one portupgrade attempts to build from index depends thus does not allow this interchangablity. - -- Aryeh M. Friedman FloSoft Systems, Java Tool Developers Developer, not business, friendly http://www.flosoft-systems.com "Free software != Free beer" Blog: Von: do...@FreeBSD.org (Doug Barton) Datum: Sun, 27 Jan 2008 08:26:12 +0800 (CST) Lokal: So 27 Jan. 2008 02:26 Betreff: Re: ports-mgmt/portupgrade-devel On Sat, 26 Jan 2008, Aryeh M. Friedman wrote: > Sergey Matveychuk wrote: >> Hi! >> After a long time, I've got a little free time and spent it working for >> portupgrade. >> A new version (2.4.0) was released. Congrats on both the new version, and finding the time. :) > This breaks certain ports (portupgrade -a) that have multiple ports > that can satisfy a depends. For example net-p2p/deulge depends on > devel/boost but multimedia/miro depends on devel/boost-python. The > only difference between boost and boost-python is boost-python sets > the -DWITH_PYTHON flag and lists lang/python > -2.5 while boost does not depend on it and makes the user specify the > above flag from the command line. Under the old portugrade it relied > on miro and/or deluge to detect its own depends and since both did it > by xDEP on the installed files either whould be accepted. Under the > new one portupgrade attempts to build from index depends thus does not > allow this interchangablity. I handled this in portmaster by analyzing the CONFLICTS. If a requested dependency has a CONFLICTS line I check the glob patterns against the installed ports with pkg_info and keep going if we already have something installed that will work. That's not a perfect solution, but it handles all the cases I've seen personally, or users complained about before that feature was introduced. hope this helps, Doug ------------------------ Newsgroups: mailing.freebsd.ports Von: me...@cox.net ("Jeremy Messenger") Datum: Sun, 27 Jan 2008 12:29:24 +0800 (CST) Lokal: So 27 Jan. 2008 06:29 Betreff: Re: ports-mgmt/portupgrade-devel On Sat, 26 Jan 2008 17:10:50 -0600, Aryeh M. Friedman = <aryeh.fried...@gmail.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > Sergey Matveychuk wrote: >> Hi! >> After a long time, I've got a little free time and spent it working f= or >> portupgrade. >> A new version (2.4.0) was released. >> * Many bugs fixed (thanks to reporters). >> * At last I've finished rewriting code and portupgrade now controls a= ll >> tasks (before some port installed without a portupgrade note). As a >> result portupgrade gathers all depends for a port. It spends a time f= or >> preparing in the beginning of a upgrade process. >> * I've change unused -c and -C options to allow run 'make >> config-conditional' and 'make config' (force options change) before a= ll >> processing. >> Test the release please. To move from portupgrade to portupgrade-deve= l >> port, use the command: >> portupgrade -fo ports-mgmt/portupgrade-devel portupgrade >> If you'll want to back to stable porupgrade, use the command: >> portupgrade -o ports-mgmt/portupgrade portupgrade-devel > This breaks certain ports (portupgrade -a) that have multiple ports > that can satisfy a depends. For example net-p2p/deulge depends on > devel/boost but multimedia/miro depends on devel/boost-python. The > only difference between boost and boost-python is boost-python sets > the -DWITH_PYTHON flag and lists lang/python > - -2.5 while boost does not depend on it and makes the user specify th= e > above flag from the command line. Under the old portugrade it relied > on miro and/or deluge to detect its own depends and since both did it > by xDEP on the installed files either whould be accepted. Under the > new one portupgrade attempts to build from index depends thus does not= > allow this interchangablity. The boost and boost-python ports need to be fix, not other tools or othe= r = stuff. It will be great if you quit email me related with this as I am = getting tired with this issue, thanks. Cheers, Mezz > - -- > Aryeh M. Friedman > FloSoft Systems, Java Tool Developers > Developer, not business, friendly > http://www.flosoft-systems.com > "Free software !=3D Free beer" > Blog: > http://www.flosoft-systems.com/flosoft_systems_community/blogs/aryeh/i= ndex.php _______________________________________________ Newsgroups: mailing.freebsd.ports Von: me...@cox.net ("Jeremy Messenger") Datum: Sun, 27 Jan 2008 12:40:17 +0800 (CST) Lokal: So 27 Jan. 2008 06:40 Betreff: Re: ports-mgmt/portupgrade-devel On Sat, 26 Jan 2008 18:25:01 -0600, Doug Barton <do...@FreeBSD.org> wrote: > On Sat, 26 Jan 2008, Aryeh M. Friedman wrote: >> Sergey Matveychuk wrote: >>> Hi! >>> After a long time, I've got a little free time and spent it working for >>> portupgrade. >>> A new version (2.4.0) was released. > Congrats on both the new version, and finding the time. :) >> This breaks certain ports (portupgrade -a) that have multiple ports >> that can satisfy a depends. For example net-p2p/deulge depends on >> devel/boost but multimedia/miro depends on devel/boost-python. The >> only difference between boost and boost-python is boost-python sets >> the -DWITH_PYTHON flag and lists lang/python >> -2.5 while boost does not depend on it and makes the user specify the >> above flag from the command line. Under the old portugrade it relied >> on miro and/or deluge to detect its own depends and since both did it >> by xDEP on the installed files either whould be accepted. Under the >> new one portupgrade attempts to build from index depends thus does not >> allow this interchangablity. > I handled this in portmaster by analyzing the CONFLICTS. If a requested > dependency has a CONFLICTS line I check the glob patterns against the > installed ports with pkg_info and keep going if we already have > something installed that will work. > That's not a perfect solution, but it handles all the cases I've seen > personally, or users complained about before that feature was introduced. I love this solution, I remember this: http://lists.freebsd.org/pipermail/freebsd-ports/2006-August/034434.htm l http://lists.freebsd.org/pipermail/freebsd-ports/2006-August/034579.htm l :-) Cheers, Mezz Weitere Optionen 27 Jan., 19:19 Newsgroups: mailing.freebsd.ports Von: ger...@seibercom.net (Gerard) Datum: Mon, 28 Jan 2008 01:19:42 +0800 (CST) Lokal: So 27 Jan. 2008 19:19 Betreff: Re: ports-mgmt/portupgrade-devel Sergey Matveychuk <s...@FreeBSD.org> wrote: > Hi! >=20 > After a long time, I've got a little free time and spent it working > for portupgrade. > A new version (2.4.0) was released. > * Many bugs fixed (thanks to reporters). > * At last I've finished rewriting code and portupgrade now controls > all tasks (before some port installed without a portupgrade note). As > a result portupgrade gathers all depends for a port. It spends a time > for preparing in the beginning of a upgrade process. > * I've change unused -c and -C options to allow run 'make > config-conditional' and 'make config' (force options change) before > all processing. >=20 > Test the release please. To move from portupgrade to portupgrade-devel > port, use the command: > portupgrade -fo ports-mgmt/portupgrade-devel portupgrade >=20 > If you'll want to back to stable porupgrade, use the command: > portupgrade -o ports-mgmt/portupgrade portupgrade-devel I just installed the updated version. Unfortunately, it is not working correctly. This is the pertinent output. FreeBSD scorpio.seibercom.net 6.3-STABLE FreeBSD 6.3-STABLE #0: Sat Jan 19 22:26:50 EST 2008 ger...@scorpio.seibercom.net:/usr/obj/usr/src/sys/SCORPIO i386 Script started on Sun Jan 27 06:46:32 2008 /usr/local/sbin/portupgrade:697:in `main': undefined method `get_uninstalled_depends' for main:Object (NoMethodError) from /usr/local/sbin/portupgrade:677:in `each' from /usr/local/sbin/portupgrade:677: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' from /usr/local/lib/ruby/1.8/optparse.rb:1299:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1247:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1247:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1241:in `order!' from /usr/local/lib/ruby/1.8/optparse.rb:1234:in `order' from /usr/local/sbin/portupgrade:554:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize' from /usr/local/sbin/portupgrade:223:in `new' from /usr/local/sbin/portupgrade:223:in `main' from /usr/local/sbin/portupgrade:2096 Script done on Sun Jan 27 06:46:39 2008 This was started with the command: portupgrade -N devel/ccache --=20 Gerard ger...@seibercom.net Why be difficult, when, with just a little more effort, you can be impossible? Weitere Optionen 30 Jan., 00:29 Newsgroups: mailing.freebsd.ports Von: bucka...@gmx.de (Mark Nowiasz) Datum: Wed, 30 Jan 2008 06:29:53 +0800 (CST) Lokal: Mi 30 Jan. 2008 00:29 Betreff: ports-mgmt/portupgrade-devel Hi, when using portupgrade-devel, I'm getting the following errors: ---> Session ended at: Tue, 29 Jan 2008 22:58:52 +0100 (consumed 00:02:01) /usr/local/lib/ruby/site_ruby/1.8/pkgversion.rb:41:in `initialize': : Not in due form: '<version>[_<revision>][,<epoch>]'. (ArgumentError) from /usr/local/sbin/portupgrade:630:in `new' from /usr/local/sbin/portupgrade:630:in `main' from /usr/local/sbin/portupgrade:618:in `each' from /usr/local/sbin/portupgrade:618:in `main' from /usr/local/sbin/portupgrade:582:in `catch' from /usr/local/sbin/portupgrade:582: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:228:in `new' from /usr/local/sbin/portupgrade:228:in `main' from /usr/local/sbin/portupgrade:2110 portupgrade --version portupgrade 2.4.1 Regards, Mark -- Q: How do you play religious roulette? A: You stand around in a circle and blaspheme and see who gets struck by lightning first. _______________________________________________ Newsgroups: mailing.freebsd.ports Von: nak...@jp.freebsd.org (NAKAJI Hiroyuki) Datum: Thu, 31 Jan 2008 13:54:06 +0800 (CST) Lokal: Do 31 Jan. 2008 07:54 Betreff: Re: ports-mgmt/portupgrade-devel Hi, I have another error with portupgrade-devel-2.4.1. # portupgrade -a ... ** Port directory not found: japanese/dpkey7 /usr/local/sbin/portupgrade:1357:in `get_pkgname': port directory error (PortDirError) from /usr/local/sbin/portupgrade:623:in `main' from /usr/local/sbin/portupgrade:618:in `each' from /usr/local/sbin/portupgrade:618:in `main' from /usr/local/sbin/portupgrade:582:in `catch' from /usr/local/sbin/portupgrade:582: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:228:in `new' from /usr/local/sbin/portupgrade:228:in `main' from /usr/local/sbin/portupgrade:2110 Dpkey7 is a third-party product and I add it in HOLD_PKGS list. But now HOLD_PKGS has no effect. Regards, >>>>> In <200801292301.44482.bucka...@gmx.de> >>>>> Mark Nowiasz <bucka...@gmx.de> wrote: > when using portupgrade-devel, I'm getting the following errors: > ---> Session ended at: Tue, 29 Jan 2008 22:58:52 +0100 (consumed 00:02:01) > /usr/local/lib/ruby/site_ruby/1.8/pkgversion.rb:41:in `initialize': : Not in > due form: '<version>[_<revision>][,<epoch>]'. (ArgumentError) > from /usr/local/sbin/portupgrade:630:in `new' > from /usr/local/sbin/portupgrade:630:in `main' > from /usr/local/sbin/portupgrade:618:in `each' > from /usr/local/sbin/portupgrade:618:in `main' > from /usr/local/sbin/portupgrade:582:in `catch' > from /usr/local/sbin/portupgrade:582: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:228:in `new' > from /usr/local/sbin/portupgrade:228:in `main' > from /usr/local/sbin/portupgrade:2110 > portupgrade --version > portupgrade 2.4.1 > Regards, > Mark -- NAKAJI Hiroyuki _______________________________________________ Von: bucka...@gmx.de (Mark Nowiasz) Datum: Sat, 2 Feb 2008 04:14:01 +0800 (CST) Lokal: Fr 1 Feb. 2008 22:14 Betreff: Re: ports-mgmt/portupgrade-devel > > Hi, > > when using portupgrade-devel, I'm getting the following errors: > > ---> Session ended at: Tue, 29 Jan 2008 22:58:52 +0100 (consumed > > 00:02:01) /usr/local/lib/ruby/site_ruby/1.8/pkgversion.rb:41:in > > `initialize': : Not in due form: '<version>[_<revision>][,<epoch>]'. > > (ArgumentError) > What port exactly did you upgraded please? Nothing particular - I tried portupgrade (devl) -a -v. Downgrading to the "normal" portupgrade did the trick, though. Regards, Mark -- Hurewitz's Memory Principle: The chance of forgetting something is directly proportional to ..... to ........ uh .............. _______________________________________________ -- Martin Schweizer <office@pc-service.ch> PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch; public key : http://www.pc-service.ch/pgp/public_key.asc; fingerprint: EC21 CA4D 5C78 BC2D 73B7 10F9 C1AE 1691 D30F D239;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081005155758.GB65233>