Re: Ruby port advice needed [Was: rubyripper-0.6.0_1 failed on amd64 9]

2011-09-17 Thread Steve Wills
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/01/11 04:28, Alexey Dokuchaev wrote: > Hi there, > > There is a ruby-written port I maintain, and several months ago it was > working just fine. However, apparently, our default Ruby bits got updated > or something, and now it currently does no

Re: Ruby port advice needed [Was: rubyripper-0.6.0_1 failed on amd64 9]

2011-09-01 Thread Alexey Dokuchaev
On Thu, Sep 01, 2011 at 02:40:12AM -0700, Stanislav Sedov wrote: > Hi! > > It turned out the ruby-gettext method your port is using has triggered > a bug in the new version of rubugems. I filed the issue with the upstream. > > Nonetheless, the Gem::all_load_paths method gettext is using is depre

Re: Ruby port advice needed [Was: rubyripper-0.6.0_1 failed on amd64 9]

2011-09-01 Thread Stanislav Sedov
On Thu, 1 Sep 2011 08:28:16 + Alexey Dokuchaev mentioned: > Hi there, > > There is a ruby-written port I maintain, and several months ago it was > working just fine. However, apparently, our default Ruby bits got updated > or something, and now it currently does not build as quoted in point

Ruby port advice needed [Was: rubyripper-0.6.0_1 failed on amd64 9]

2011-09-01 Thread Alexey Dokuchaev
Hi there, There is a ruby-written port I maintain, and several months ago it was working just fine. However, apparently, our default Ruby bits got updated or something, and now it currently does not build as quoted in pointyhat log below (trimmed for your convenience). I'm not a Ruby expert; per