[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Status of ruby transition in testing



The following is a summary of the state of the  ruby 1.6 -> 1.8
transition currently in progress.  For the most part, this is a soft
transition, with individual packages making the jump to testing as they
become ready, so a full transition is by no means mandatory for sarge.
However, a few of the packages may be of interest because of connections
to other library packages; and if people want ruby1.8 to be the default
ruby in sarge, there's a fair amount of work still needing to be done
because of the shuffling of binary package names between source
packages.


These packages are more or less ready to go:

libeb-ruby: eligible in spite of 212282 because there are no out-of-date
  binaries; however, it's waiting for eblook to be a valid candidate.
  An NMU is in DELAYED/3-day -- a maintainer upload would speed things
  up, otherwise this should all be ready by 10/18.
libwrap-ruby: too young, needs one more day day.
libxmms-ruby: valid candidate once the powerpc build is in (tomorrow).


These packages are ready on their own, but need ruby-defaults to be
ready at the same time because of other packages which depend on both
ruby and libstrscan-ruby:

libstrscan-ruby
libtmail-ruby
racc-runtime


These packages have no RC bugs and are up to date on all archs, but they
have dependencies on other packages that are not yet valid candidates.
Two of these are specifically tied up with the ruby-defaults knot.

rubymagick: waits on imagemagick, ruby-defaults.  We may want to remove
  rubymagick from testing, so that imagemagick et al. can be moved in
  the meantime.
libapache-mod-ruby: waiting on apache.  Should be rebuilt once
  apache 1.3.28 hits the archive (to use the new module package
  interface), but this won't hold it out.
libzlib-ruby: waits for apt-listbugs to be a valid candidate, which
  requires ruby1.6 on mips first.  Also invalidates debpartial, which
  needs libzlib-ruby (binary package), which now comes from
  ruby-defaults.


These packages all have outstanding RC bugs in unstable which keep the
respective packages out of testing:

libdb-ruby: 212103
libgd-ruby: 212105
libiconv-ruby: 214035
libpcap-ruby: 212265
libsdl-ruby: 212266
libshadow-ruby: 212268
libsufary-ruby: 212269
xmlrpc4r: 212298
vim: 211710; also out of date on sparc due to what looks like buildd
  breakage, and waiting on python2.3.


These packages are out of date on some architectures due to bug
#212282, which appears to now be fixed thanks to upstream.  They will
need to be re-queued on powerpc and/or arm.

eruby
libfam-ruby
libmysql-ruby
widestudio


These packages are also out of date on mips, because they build-dep on
ruby1.6 which has never been built there.  There's no sign that the
build has problems on mips, it's simply never been attempted.  Since
mips has been lagging behind recently, this will just need to run its
course, unless a decision is made to ignore mips for now.

gnome-ruby
libdbi-ruby
libexif-ruby
libpgsql-ruby
libvorbisfile-ruby
quantlib-ruby
mhc-utils


The ruby-defaults source package, which replaces the ruby source package
in testing, provides a number of binary packages previously provided by
other source packages.  These packages must therefore all be ready to go
into testing at the same time.  Maintainers of any of the packages
listed below are encouraged to exert peer pressure to get the rest of
the packages into order. :)

libstrscan-ruby
libtmail-ruby
racc
libiconv-ruby
libzlib-ruby

These packages also need to be updated in testing before ruby-defaults
can go in, although they don't have to be hinted in at the same time.
(Two of them should make it in tomorrow, in fact.)

libpcap-ruby
libpgsql-ruby
libshadow-ruby
libsufary-ruby
libwrap-ruby
libxmms-ruby
mhc-utils


Cheers,
-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: