On Wed, Aug 10, 2016 at 11:58:48PM +0200, Emmanuel Bourg wrote: > > [...] > > I was a bit reluctant to upgrade again bnd and maven-bundle-plugin for > stretch but we have a good reason to do it now.
Hi Emmanuel, I have concluded the only feasible way to get out of this hole with jruby is to revert yecht its 1.0 behavior. This means to remove YechtService class from yecht.jar. I can take care of that. This way, I can get jruby 1.7.25 building in the archive with available versions of bnd and maven-bundle-plugin. The remaining hurdle is to get all its tests passing. I apologize for basically dropping the ball with jruby maintenance on this release cycle, but I had too many stuff to deal with in real life. My plan here is: * Hack/patch yecht jar and upload yecht 1.1-2 to get jruby buildable again. * Upload jruby 1.7.25-1 to unstable once all tests are passing, to fix a couple of FTBFS and remaining RC bugs. * Later (before the freeze), check if it's possible to upload the latest 1.7.x release (1.7.26). Unfortunately, this means "stretch" will include a jruby release with no support from upstream [1]. Cheers, 1. https://github.com/jruby/jruby/issues/4112 -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche
signature.asc
Description: Digital signature