Bug#789077: transition: ruby2.2

[Emilio Pozuelo Monfort <pochu@debian.org>]

On 08/07/15 14:11, Christian Hofstaedtler wrote:
> Hi,
> 
> Please schedule binNMUs for these packages, which now have their 
> dependencies fulfilled (and build fine in my tests):
> 
> ruby-eventmachine_1.0.7-1
> ruby-hpricot_0.8.6-5
> ruby-lapack_1.6-2
> ruby-lapack-dbg_1.6-2
> unicorn_4.8.3-1

Scheduled. You listed ruby-lapack and ruby-lapack-dbg. I guess the latter was a
mistake.

> I think after those we're left mostly with packages that only build
> for the first ruby version they find, some broken "leaf-y" ruby
> libs, plus ruby-yajl and ruby-redcloth which impact a larger chain.

ruby-yajl and ruby-redcloth are marked as good in the tracker. What's the
problem with them?

I guess the next step is making ruby2.2 the default (probably in experimental
first and making sure things still build properly, particularly those that only
build for the default version).

Cheers,
Emilio

P.S.: try not to break threading