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

Re: unrebuildable ruby packages (Re: ruby-defaults 1.8.0)

On Mon, Sep 08, 2003 at 04:01:31AM +0900, Fumitoshi UKAI wrote:
> As Marcelo pointed out on Bug#209052, ruby-dev has been obsoleted, so
> packages that build-depend on ruby-dev can't be built now.
> We have ruby1.6-dev (for ruby1.6) and ruby1.8-dev (for ruby1.8), so
> please rebuild your packages to use ruby1.6-dev and/or ruby1.8-dev.

I've uploaded libyaml-ruby_0.49.1-2 and libdbd-ruby_0.0.20-3 which
follow the Debian Ruby Policy.

I see no point in uploading new libjttui-ruby, since I've orphaned this
package (see #206718) and it should not go into Debian/stable in its
current form anyway (it is unused and its upstream is inactive for well
over a year).

Four of new Ruby/DBI packages, libdbd-pg-ruby1.6, libdbd-pg-ruby1.8,
libdbd-mysql-ruby1.6, and libdbd-mysql-ruby1.8 depend on libpgsql-ruby
and libmysql-ruby, respectively. This is required for these packages to
be installable right now, but is obviously not correct: current versions
of libpgsql-ruby and libmysql-ruby provide modules only for Ruby 1.6,
and upcoming versions will expectedly depend on -ruby1.6 variants, and
later on -ruby1.8 variants. Hence:

Taku, Christian,

Please let me know when you upload new modules for both Ruby 1.6 and
Ruby 1.8, so that I can upload DBDs with correct dependencies. Or let me
know if you don't have time to do it and approve someone to NMU it for
you; beware that adopting these packages to the Ruby policy will require
major changes to their build system, thus it's better that you do it

Dmitry Borodaenko

Reply to: