Re: wrong number of ruby 1.9 args for portupgrade's realpath

2011-08-21 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/21/11 06:31, Andrey Chernov wrote: # portupgrade -vuR /usr/local/lib/ruby/site_ruby/1.9/pkgmisc.rb:104:in `realpath': wrong number of arguments (2 for 1) (ArgumentError) from /usr/local/lib/ruby/1.9/pathname.rb:446:in `realpath'

Re: ports/140273: ports-mgmt/portupgrade-devel chokes on bsdpan pkgs

2011-08-21 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/21/11 13:30, Fabian Wenk wrote: The following reply was made to PR ports/140273; it has been noted by GNATS. From: Fabian Wenk fab...@wenks.ch To: bug-follo...@freebsd.org Cc: do...@oitsec.umn.edu Subject: Re: ports/140273:

Re: ports/140273: ports-mgmt/portupgrade-devel chokes on bsdpan pkgs

2011-08-21 Thread Steve Wills
The following reply was made to PR ports/140273; it has been noted by GNATS. From: Steve Wills swi...@freebsd.org To: Fabian Wenk fab...@wenks.ch Cc: r...@freebsd.org, bug-follo...@freebsd.org Subject: Re: ports/140273: ports-mgmt/portupgrade-devel chokes on bsdpan pkgs Date: Sun, 21 Aug 2011 14

Re: ports/140273: ports-mgmt/portupgrade-devel chokes on bsdpan pkgs

2011-08-21 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/21/11 14:18, Steve Wills wrote: On 08/21/11 13:30, Fabian Wenk wrote: The following reply was made to PR ports/140273; it has been noted by GNATS. From: Fabian Wenk fab...@wenks.ch To: bug-follo...@freebsd.org Cc: do...@oitsec.umn.edu

Re: ports/140273: ports-mgmt/portupgrade-devel chokes on bsdpan pkgs

2011-08-21 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/21/11 14:44, Fabian Wenk wrote: Hello Steve On 21.08.2011 20:18, Steve Wills wrote: If you're using Ruby 1.9, give this patch a try. I am, and your patch is working: root@batman:~# portupgrade -an --- Session started at: Sun, 21

Re: ports/140273: ports-mgmt/portupgrade-devel chokes on bsdpan pkgs

2011-08-21 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/21/11 15:14, Fabian Wenk wrote: Hello Steve I did (again with Ruby 1.9) and it builds and installs fine and it is still working: Thanks! I'll see about getting this committed to portupgrade-devel and portupgrade then try to close the PR.

Ruby 1.9 this weekend

2011-08-19 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm mailing you because you are listed as part of the ruby@ team on http://wiki.freebsd.org/Ruby. The last exp-run of my patch to make Ruby 1.9 default was very clean. There are still a good number of ports that are marked as broken with 1.9,

Ruby 1.9 as default

2011-08-06 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We're pretty much ready to go. Most of the issues that I mentioned in my previous mail have been fixed. Specifically: * All Ruby 1.9 incompatible ports have been marked as such. I'll include the list at the bottom of this email. Would it be

Re: Status of migration to ruby 1.9 as default

2011-08-03 Thread Steve Wills
On Aug 1, 2011, at 11:50 PM, dirk.me...@dinoex.sub.org (Dirk Meyer) wrote: Steve Wills schrieb:, If you'd like to try to fix things, the possibly incomplete and/or inaccurate list of ports that don't work with 1.9 is: I can't figure out how to add patches to a gem distribution so i can

Re: Time to mark portupgrade deprecated?

2011-07-26 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/25/11 08:25, Tilman Keskinöz wrote: I shortly went through the list. There are currently 22 PRs filed against portupgrade Of these: 4 are general problems of the ports collection/pkg_tools. (architecture-specific INDEX,

Re: Time to mark portupgrade deprecated?

2011-07-24 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/24/11 22:20, Eitan Adler wrote: At this point noone is maintaining portupgrade any more and a large number of PRs have been filed against it (see http://www.freebsd.org/cgi/query-pr-summary.cgi?text=portupgrade). No one has stepped up to do

Status of migration to ruby 1.9 as default

2011-07-06 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, In case anyone is interested, here's where we are with migrating to Ruby 1.9 as the default version: * Good progress has been made on marking the incompatible ports and we have deprecated a good number of them. The remaining incompatible ports

Re: Status of migration to ruby 1.9 as default

2011-07-06 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/06/11 22:57, Steve Wills wrote: On 07/06/11 22:39, Stanislav Sedov wrote: On Wed, 06 Jul 2011 22:28:00 -0400 Steve Wills swi...@freebsd.org mentioned: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, In case anyone is interested

upcoming ruby-gnome update

2011-07-01 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The ruby-gnome stuff is due for an update. I've got a patch here: http://people.freebsd.org/~swills/ruby_gnome_0.90.9_update.diff.txt Not included in that diff is the removal of these ports: devel/ruby-gconf2 devel/ruby-gnomevfs

Re: ruby 1.9 update patch

2011-06-12 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/25/11 09:12, Eric wrote: From: Steve Wills st...@mouf.net -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for the feedback! I was attempting to do some run time testing of this and stumbled upon a strange issue. It seems that even

ruby 1.9 update patch

2011-05-18 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, As part of the quest to get Ruby 1.9 as default, I'd like to consider this patch (attached and available here: http://people.freebsd.org/~swills/ruby19_and_gems_changes.diff ). This will bring Ruby 1.9 up to patch 180 and make it so that we

Re: making Ruby 1.9 default

2011-03-26 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've submitted a PR with a request for an exp-run with my patches. I'm waiting for that, but in the mean time, I've been doing some build testing of my own. I've found these ports fail to build with Ruby 1.9: archivers/ruby-bz2 audio/liblastfm

<    1   2