Re: Portupgrade still broken?
Torfinn Ingolfsen wrote: Hello again, Just a reminder: portupgrade 2.4.6 hasn't been fixed yet - it is still broken: Yes, I remember, thanks. I'm very busy this year. I'd glad to give maintainership to somebody else. Write me, if you like. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
Hello, On Thu, Apr 9, 2009 at 6:37 PM, Parv p...@pair.com wrote: Does this Perl (5.8 onwards) program ... http://www103.pair.com/parv/comp/src/perl/check-portupgrade-00 ... produces anything when run *without any arguments*? FWIW, I tried it on two machines, no it does not produce any output. -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
in message b79ecaef0904091219t4f20f65br36f6e2405ff60...@mail.gmail.com, wrote Chris Rees thusly... 2009/4/9 Parv p...@pair.com: in message b79ecaef0904080551x74c80227h1a4ba5d2adcca...@mail.gmail.com, wrote Chris Rees thusly... 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 :( ... [ch...@amnesiac]/usr/ports/ports-mgmt/portupgrade% sudo portupgrade -rR emacs xterm curl php5-mbstring otp-md5 488 am9338 ext ... /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' ... Does this Perl (5.8 onwards) program ... http://www103.pair.com/parv/comp/src/perl/check-portupgrade-00 ... produces anything when run *without any arguments*? Purpose of the program is to find a port name (based on directory name in /var/db/pkg) which fails to match the regular expression /^(.+)-([^-]+)$/ used in pkginfo.rb, among other files of portupgrade. ... No, sorry, no messages :( Thank you Chris Kent. No output means that all the port names (based on directory names) match the expected format in pkginfo.rb which tries to parse the names. So that implies that whatever name is being sent to pkginfo.rb is not really a port name per expectation. Internal API seemed to have changed (since whenever), but somebody failed to update the name parsing code, and/or to generate the complete name from partial name before passing it to port name-version parsing code. What was the last working version? It would be simpler for this Ruby simpleton to generate a patch than to debug through the stack trace. - Parv -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
Hi, On Fri, Apr 10, 2009 at 2:57 PM, p...@pair.com wrote: What was the last working version? It would be simpler for this Ruby simpleton to generate a patch than to debug through the stack trace. FWIW, my current workaround for thi problem is to portdowngrade to the latest portupgrade 2.4.3 portupgrade-2.4.3_2,2 is working. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
Torfinn Ingolfsen writes: What was the last working version? It would be simpler for this Ruby simpleton to generate a patch than to debug through the stack trace. FWIW, my current workaround for thi problem is to portdowngrade to the latest portupgrade 2.4.3 portupgrade-2.4.3_2,2 is working. However, portupgrade-devel (2.4.6) is not. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
in message b79ecaef0904080551x74c80227h1a4ba5d2adcca...@mail.gmail.com, wrote Chris Rees thusly... 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 :( [ch...@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... [ch...@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' ... Does this Perl (5.8 onwards) program ... http://www103.pair.com/parv/comp/src/perl/check-portupgrade-00 ... produces anything when run *without any arguments*? Purpose of the program is to find a port name (based on directory name in /var/db/pkg) which fails to match the regular expression /^(.+)-([^-]+)$/ used in pkginfo.rb, among other files of portupgrade. If the Perl program is run with any arguments, then a sorted list of matched names will be printed, something like ... aalib-1.4.r5_4 : aalib 1.4.r5_4 acroread8-8.1.2_2 : acroread8 8.1.2_2 acroreadwrapper-0.0.20080906 : acroreadwrapper 0.0.20080906 agg-2.5_5 : agg 2.5_5 aircrack-ng-1.0.r1 : aircrack-ng 1.0.r1 amspsfnt-1.0_5 : amspsfnt 1.0_5 ... - Parv -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
On Thursday 09 April 2009 09:37:49 am Parv wrote: in message b79ecaef0904080551x74c80227h1a4ba5d2adcca...@mail.gmail.com, wrote Chris Rees thusly... 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 :( [ch...@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... [ch...@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' ... Does this Perl (5.8 onwards) program ... http://www103.pair.com/parv/comp/src/perl/check-portupgrade-00 ... produces anything when run *without any arguments*? It doesn't produce any messages. Purpose of the program is to find a port name (based on directory name in /var/db/pkg) which fails to match the regular expression /^(.+)-([^-]+)$/ used in pkginfo.rb, among other files of portupgrade. If the Perl program is run with any arguments, then a sorted list of matched names will be printed, something like ... aalib-1.4.r5_4 : aalib 1.4.r5_4 acroread8-8.1.2_2 : acroread8 8.1.2_2 acroreadwrapper-0.0.20080906 : acroreadwrapper 0.0.20080906 agg-2.5_5 : agg 2.5_5 aircrack-ng-1.0.r1 : aircrack-ng 1.0.r1 amspsfnt-1.0_5 : amspsfnt 1.0_5 ... check-portupgrade p5 produced a list of 632 names, which is about what I have installed. I ran portupgrade -rR libxcb recently and it failed with the same pkginfo.rb error you are listing. Kent -- kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
2009/4/9 Parv p...@pair.com: in message b79ecaef0904080551x74c80227h1a4ba5d2adcca...@mail.gmail.com, wrote Chris Rees thusly... 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 :( [ch...@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... [ch...@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' ... Does this Perl (5.8 onwards) program ... http://www103.pair.com/parv/comp/src/perl/check-portupgrade-00 ... produces anything when run *without any arguments*? Purpose of the program is to find a port name (based on directory name in /var/db/pkg) which fails to match the regular expression /^(.+)-([^-]+)$/ used in pkginfo.rb, among other files of portupgrade. If the Perl program is run with any arguments, then a sorted list of matched names will be printed, something like ... aalib-1.4.r5_4 : aalib 1.4.r5_4 acroread8-8.1.2_2 : acroread8 8.1.2_2 acroreadwrapper-0.0.20080906 : acroreadwrapper 0.0.20080906 agg-2.5_5 : agg 2.5_5 aircrack-ng-1.0.r1 : aircrack-ng 1.0.r1 amspsfnt-1.0_5 : amspsfnt 1.0_5 ... - Parv -- No, sorry, no messages :( [ch...@amnesiac]~% sudo perl check-portupgrade.pl [ch...@amnesiac]~% -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
Chris Rees 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 :( Assuming you are talking about the feature of rebuilding ports that depend on a given port, you might want to give portmaster a try. The -r option will do what you want. You can also combine -r with -i to only rebuild certain ports that depend on the given port. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Portupgrade still broken?
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 :( [ch...@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... [ch...@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? Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
Hello, On Wed, Apr 8, 2009 at 2:51 PM, Chris Rees utis...@googlemail.com wrote: Is the bug still there, or is my pkgdb hosed? If so, how do I fix it? IMO, the bug is still in portupgrade, even in the latest 2.4.6 version. I have also seen it very recently. -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
On Wed, 8 Apr 2009 13:51:48 +0100 Chris Rees utis...@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 :( [ch...@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... [ch...@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. -- Jerry ges...@yahoo.com The primary function of the design engineer is to make things difficult for the fabricator and impossible for the serviceman. signature.asc Description: PGP signature
Re: Portupgrade still broken?
On Wednesday 08 April 2009 05:51:48 am Chris Rees 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 :( [ch...@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... [ch...@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 still get the optparse.rb:787:in stop. It seems to happen quicker, when you have a larger number of ports in the rR tree. I hadn't updated my ports since 4 Apr. I did a cvsup update and and checked to see how many needed updating. There were 15 ports. I then did a portupgrade -rRp libxcb and it died fairly quickly. Libxcb on my system, has 173 ports that depend on it. I find that portupgrade -pa works for me. Kent Chris -- kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
2009/4/8 Kent Stewart kstew...@owt.com: On Wednesday 08 April 2009 05:51:48 am Chris Rees 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 :( Is the bug still there, or is my pkgdb hosed? If so, how do I fix it? I still get the optparse.rb:787:in stop. It seems to happen quicker, when you have a larger number of ports in the rR tree. I hadn't updated my ports since 4 Apr. I did a cvsup update and and checked to see how many needed updating. There were 15 ports. I then did a portupgrade -rRp libxcb and it died fairly quickly. Libxcb on my system, has 173 ports that depend on it. I find that portupgrade -pa works for me. Kent That's a bugger, I may check out portmaster. Thanks for all the replies. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Portupgrade still broken?
Hello again, On Wed, Apr 8, 2009 at 4:17 PM, Torfinn Ingolfsen tin...@gmail.com wrote: IMO, the bug is still in portupgrade, even in the latest 2.4.6 version. I have also seen it very recently. Yep, still there with latest portupgrade: r...@kg-v2# portupgrade -R ImageMagick diablo-jdk ffmpeg gsm gstreamer-plugins-good jackit mesa-demos py25-tkinter vlc x264 xf86-video-via xfce4-clipman-plugin xfce4-mixer [Gathering depends for graphics/ImageMagick done] [Exclude up-to-date packages ... done] [Gathering depends for java/diablo-jdk16 done] [Exclude up-to-date packages done] [Gathering depends for multimedia/ffmpeg done] [Exclude up-to-date packages done] [Exclude up-to-date packages done] [Gathering depends for multimedia/gstreamer-plugins-good ... done] [Exclude up-to-date packages done] [Gathering depends for audio/jack ... 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 r...@kg-v2# r...@kg-v2# portversion -vF | grep portupgrade portupgrade-2.4.6_1,2 = up-to-date with port r...@kg-v2# uname -a FreeBSD kg-v2.kg4.no 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #5: Sat Apr 4 21:43:24 CEST 2009 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Portupgrade still broken?
I've wrote many time to the maintainer about the problem, I think since about 2 years ago, and I've also received some answer from him about other issues. But he never answered about that problem. regards Barbara ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
