* Matt Palmer <mpalmer@debian.org> [140304 22:54]: > On Tue, Mar 04, 2014 at 05:02:31PM +0100, Christian Hofstaedtler wrote: > > As per the Debian Ruby team bits, all versions of Ruby < 2.1 will be > > removed from jessie. > > A month ago you told me to migrate to Ruby 1.9, now you're saying that isn't > enough. Can you make up your mind, please? The purpose of the previous bug was to have everybody migrate away from 1.8, because it was clear that jessie won't ship with 1.8. IIRC, at that point in time, no other decision had been made, and we didn't even have 2.1 in sid. > > Please test your package with Ruby 2.0 and 2.1, and then switch the > > Why do I need to test against 2.0 if you're removing everything earlier than > 2.1? Feel free to skip 2.0 if you want and can. > > Depends: line to read "ruby" instead of "ruby1.9.1". > > Is that going to break when you upgrade the "ruby" package to pull in Ruby > 2.2, and my code isn't 2.2 compatible? Or has Ruby upstream finally decided > that backwards-compatibility is a worthy goal? The current plan is to have the "ruby" meta-package depend on the one and only shipping Ruby version for a given Debian release. If you decide on staying with a Depends: on a specific ruby version you'll need to update your package even if it would work without any other changes. Regarding backwards-compatibility this is not something I can answer; I'm not Ruby upstream. If you have issues with Ruby upstream, please talk to them. -- ,''`. Christian Hofstaedtler <zeha@debian.org> : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `-
Attachment:
signature.asc
Description: Digital signature