Bug#693010: unblock: bundler/1.1.4-6
* Adam D. Barratt <adam@adam-barratt.org.uk> [121112 10:52]:
> On Mon, 2012-11-12 at 01:22 +0100, Christian Hofstaedtler wrote:
> > In bundler 1.2.0 a new keyword was added to the Gemfile DSL,
> > named 'ruby' which allows users to specify a ruby version.
> > Upstream has a patch in 1.1.5 that basically ignores this keyword
> > but allows installation (otherwise, bundler would just abort).
>
> What's the likelihood of such a combination (i.e. older bundler with
> newer files) occurring during wheezy's lifetime?
Heroku recommends [1] switching to this new keyword over their
legacy configuration variables. I expect various smaller open source
projects (which might never get packaged) will just put this into
their Gemfile.
I *think* there are no bundler rdepends in testing right now, so
all possible Gemfiles will come from some random open source project
or from developers working on private projects. The open source
projects will likely use a free Heroku app for testing purposes,
and the other group might use it as well.
I haven't seen any Gemfile generators that put this in by default
_now_.
The thing is, the patch adds a warning/notice and no functionality,
but the old version just explodes into the user's face when it
encounters the new keyword.
> > Applying this patch is the only change from the version
> > currently in testing. 1.1.4-6 should now be in the t-p-u queue.
>
> It is. Whether is should be is a different question, given the lack of
> pre-upload discussion. ;-p
If the upload caused any harm at this point, I'm sorry.
[1] https://devcenter.heroku.com/articles/ruby-versions
--
Christian Hofstaedtler | design, deploy, scale
http://christian.hofstaedtler.name/ | phone +43 720 699846
Reply to: