proposing a SRU for trusty, changing the ruby default from 1.9.1 to 2.0, and stop building the tcltk ruby bindings.
rationale: trusty currently has two ruby versions and two Tcl/Tk versions in main. reducing these one of each lowers the maintenance burden for the LTS.
The transition to ruby2.0/ruby2.1 in utopic is almost done, so problems and fixes are already known on a large scale.
Packages which would need updating:
- update ruby2.0 to the version from utopic (this one was used for all uploads in utopic,
so it would be good to use this working version.
- update the gem2deb and rubygems-integration packages to drop ruby1.9.1 support.
- rebuild all packages having a Ruby-Version: attribute without 2.0 (this is not strictly related
to the SRU, but should be done anyway). you currently can't use ruby2.0 gems where
this information is missing for 300+ packages. These are no-change rebuilds.
- fix build failures with 2.0 as the default. The majority of these are caused by .install
files pointing to outdated ruby1.9.1 locations.
Testing:
- explicity test puppet working with 2.0
- a test rebuild of the archive, or a partial test rebuild.
Implementation:
- use a ppa to prepare all these changes, and then copy these changes to trusty-proposed.
proposing a SRU for trusty, changing the ruby default from 1.9.1 to 2.0, and stop building the tcltk ruby bindings.
rationale: trusty currently has two ruby versions and two Tcl/Tk versions in main. reducing these one of each lowers the maintenance burden for the LTS.
The transition to ruby2.0/ruby2.1 in utopic is almost done, so problems and fixes are already known on a large scale.
Packages which would need updating:
- update ruby2.0 to the version from utopic (this one was used for all uploads in utopic,
so it would be good to use this working version.
- update the gem2deb and rubygems- integration packages to drop ruby1.9.1 support.
- rebuild all packages having a Ruby-Version: attribute without 2.0 (this is not strictly related
to the SRU, but should be done anyway). you currently can't use ruby2.0 gems where
this information is missing for 300+ packages. These are no-change rebuilds.
- fix build failures with 2.0 as the default. The majority of these are caused by .install
files pointing to outdated ruby1.9.1 locations.
Testing:
- explicity test puppet working with 2.0
- a test rebuild of the archive, or a partial test rebuild.
Implementation:
- use a ppa to prepare all these changes, and then copy these changes to trusty-proposed.