buildr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Toulme <anto...@lunar-ocean.com>
Subject Re: Releasing 1.4.7 -- was: [VOTE] Buildr 1.4.7 RC1
Date Wed, 08 Feb 2012 16:56:45 GMT
Please go ahead. Our son showed up last week and I'm busy changing diapers
for the foreseeable future.

On Wed, Feb 8, 2012 at 08:07, Alex Boisvert <alex.boisvert@gmail.com> wrote:

> Antoine,
>
> If you don't mind, I'll take up the release and get started this week.
>  We're far into overdue territory :)
>
> Pepijn:  can you file an issue with the JRuby/Rubygems warning you're
> seeing?  Just to make sure I can reproduce the same and address the issue.
>
> alex
>
>
> On Tue, Jan 31, 2012 at 5:28 AM, Pepijn Van Eeckhoudt <
> pepijn@vaneeckhoudt.net> wrote:
>
> > Any news on the 1.4.7 release? 1.4.6 with JRuby 1.6.6 is giving me tons
> of
> > rubygems related deprecation warnings which is rather annoying.
> >
> > Pepijn
> >
> >
> > On 13/01/2012 20:32, Antoine Toulme wrote:
> >
> >> I was hoping to come back here and give better news. Alas my time has
> run
> >> so scarce, I couldn't even come up with time to write up an email for
> the
> >> last months.
> >>
> >> I apologize for leaving this release open-ended. I have recently changed
> >> jobs (now a Rails developer at collaborative drug.com) and got a baby
> on
> >> the way.
> >>
> >> If you don't hear much from me in the coming months, don't panic :)
> >>
> >> I would like to try again releasing 1.4.7 before things get out of
> control
> >> at home. I'll give it a shot this weekend. Please let me know if you
> have
> >> objections.
> >>
> >> Cheers,
> >>
> >> Antoine
> >>
> >>
> >>
> >>
> >> On Fri, Nov 25, 2011 at 12:59, Antoine Toulme<antoine@lunar-ocean.com**
> >> >wrote:
> >>
> >>  OK, will do.
> >>>
> >>>
> >>> On Fri, Nov 25, 2011 at 12:51, Alex Boisvert<alex.boisvert@gmail.
> **com<alex.boisvert@gmail.com>
> >>> >wrote:
> >>>
> >>>  Since we're voting on the source release, here's my +1.
> >>>>
> >>>> I believe the binary distros need to be re-generated -- at least the
> >>>> -java one.
> >>>>
> >>>> Antoine, you should run "gem update --system" and "bundle update" on
> >>>> your
> >>>> system to generate binaries that will install correctly.   I've done
> so
> >>>> on
> >>>> my system and now all the distros install cleanly (assuming latest
> >>>> rubygems
> >>>> is installed)
> >>>>
> >>>> alex
> >>>>
> >>>>
> >>>> On Fri, Nov 25, 2011 at 11:22 AM, Antoine Toulme<
> >>>> antoine@lunar-ocean.com
> >>>>
> >>>>> wrote:
> >>>>> I am in favor of giving this vote one more week to conclude - with
> >>>>> Thanksgiving, I didn't have time to run all tests yet.
> >>>>>
> >>>>> Please let me know if you favor a different solution.
> >>>>>
> >>>>> Antoine
> >>>>>
> >>>>> On Wed, Nov 23, 2011 at 13:35, Alex Boisvert<alex.boisvert@gmail.
> **com<alex.boisvert@gmail.com>
> >>>>>
> >>>>>> wrote:
> >>>>>> On Tue, Nov 22, 2011 at 6:05 PM, Peter Donald<
> peter@realityforge.org
> >>>>>>
> >>>>>>> wrote:
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> I attempted to get the packages at
> >>>>>>> http:/people.apache.org/~**toulmean/buildr/1.4.7/dist/<
> http://people.apache.org/~toulmean/buildr/1.4.7/dist/>working but ran
> >>>>>>> into some issues. I then did a blank rvm install and attempted
> again
> >>>>>>> with no success. Here is what happened...
> >>>>>>>
> >>>>>>> $ wget
> >>>>>>>
> >>>>>>>  http://people.apache.org/~**toulmean/buildr/1.4.7/dist/**
> >>>>> buildr-1.4.7.gem<
> http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7.gem>
> >>>>>
> >>>>>> $ rvm use ruby-1.8.7-p352
> >>>>>>> $ gem install buildr-1.4.7.gem
> >>>>>>> ERROR:  While executing gem ... (ArgumentError)
> >>>>>>>    Illformed requirement ["#<YAML::Syck::DefaultKey:**
> >>>>>>> 0x2b2e99223290>
> >>>>>>> 2.0.23"]
> >>>>>>>
> >>>>>>>  Looks like a bug in rubygems (see below);  try running
"gem update
> >>>>>> --system".
> >>>>>>
> >>>>>> $ rvm install ruby-1.8.7-p352^C
> >>>>>> [...]
> >>>>>> $ rvm use 1.8.7-p352
> >>>>>> Using /home/boisvert/.rvm/gems/ruby-**1.8.7-p352
> >>>>>> $ gem -v
> >>>>>> 1.6.2
> >>>>>> $ gem install buildr-1.4.7.gem
> >>>>>> ERROR:  While executing gem ... (ArgumentError)
> >>>>>>     Illformed requirement ["#<YAML::Syck::DefaultKey:**
> >>>>>> 0x7fdfa1c9c448>
> >>>>>> 2.0.23"]
> >>>>>> $ gem update --system
> >>>>>> Fetching: rubygems-update-1.8.11.gem (100%)
> >>>>>> Installing RubyGems 1.8.11
> >>>>>> RubyGems 1.8.11 installed
> >>>>>> [...]
> >>>>>> $ gem install buildr-1.4.7.gem
> >>>>>> [...]
> >>>>>> Successfully installed buildr-1.4.7
> >>>>>> 19 gems installed
> >>>>>>
> >>>>>>
> >>>>>>  $ wget
> >>>>>>>
> >>>>>>>  http://people.apache.org/~**toulmean/buildr/1.4.7/dist/**
> >>>>> buildr-1.4.7-java.gem<
> http://people.apache.org/~toulmean/buildr/1.4.7/dist/buildr-1.4.7-java.gem
> >
> >>>>>
> >>>>>> $ rvm use jruby-1.6.3
> >>>>>>> $ gem install buildr-1.4.7-java.gemERROR:  While executing
gem ...
> >>>>>>> (NoMethodError)    undefined method `call' for nil:NilClass
> >>>>>>>
> >>>>>>> Any ideas?
> >>>>>>>
> >>>>>>>  Also a rubygems issue... although upgrading to 1.8.11 led
to a
> >>>>>>
> >>>>> different
> >>>>>
> >>>>>> issue:
> >>>>>> https://github.com/carlhuda/**bundler/issues/1235<
> https://github.com/carlhuda/bundler/issues/1235>
> >>>>>>
> >>>>>> Not sure how to resolve this yet.
> >>>>>>
> >>>>>> alex
> >>>>>>
> >>>>>>
> >>>>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message