libruby1.9.1 shouldn't install ruby - remove ruby1.9.1

Bug #1426828 reported by Javier López
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
notmuch (Ubuntu)
Invalid
High
Unassigned
ruby1.9.1 (Debian)
Fix Released
Unknown
ruby1.9.1 (Ubuntu)
Fix Released
Undecided
Unassigned
ruby2.1 (Debian)
Fix Released
Unknown

Bug Description

Release of Ubuntu: Vivid, Trusty
Package Version: ruby1.9.1
Expected Results: vim-nox or any other program who depends on libruby should install the library but not the whole ruby programming language
Actual Results: vim-nox install ruby since it depends on libruby and libruby depends on ruby

According to:

               ruby1.9.1 (1.9.3.484-2) unstable; urgency=medium

                 * new strategy for Ruby version transitions:
                   - ruby1.9.1 depends on ruby
                   - libruby1.9.1 depends on ruby1.9.1
                 * Drop alternatives entries.

libruby1.9.1 now depends on ruby1.9.1. This causes than installations of packages such us vim-nox (who depends on libruby) pull the whole ruby programming language.

In my opinion it shouldn't be this way (unless the transition fixes some important bugs). It could be suggested but not forced. vim-nox also depends on liblua and its installation doesn't pull the Lua programming language into the system.

Related branches

description: updated
Changed in ruby1.9.1 (Debian):
status: Unknown → New
Revision history for this message
Martin Pitt (pitti) wrote :

This was fixed in ruby2.1 in Debian a while ago, and ruby1.9.1 is unmaintained and obsolete. We won't fix anything there any more, just remove it. The only remaining reverse dependencies are

  - facter-customfacts-plugin: facter-plugins does not exist in Debian and is obviously unmaintained according to https://launchpad.net/ubuntu/+source/facter-plugins/+changelog

 - ruby-notmuch from source notmuch; in Debian a newer version depends on libruby2.1, but this version fails to build: https://launchpad.net/ubuntu/+source/notmuch/0.18.2-1

So sorting out these two is obviously the better way forward here.

Removing packages from wily:
 facter-plugins 1.1-0ubuntu3 in wily
  facter-customfacts-plugin 1.1-0ubuntu3 in wily amd64
  facter-customfacts-plugin 1.1-0ubuntu3 in wily arm64
  facter-customfacts-plugin 1.1-0ubuntu3 in wily armhf
  facter-customfacts-plugin 1.1-0ubuntu3 in wily i386
  facter-customfacts-plugin 1.1-0ubuntu3 in wily powerpc
  facter-customfacts-plugin 1.1-0ubuntu3 in wily ppc64el
Comment: unmaintained for years, not in Debian, depends on obsolete ruby1.9.1

summary: - libruby1.9.1 shouldn't install ruby or an alternative should be create
- who doesn't install ruby
+ libruby1.9.1 shouldn't install ruby - remove ruby1.9.1
Changed in ruby1.9.1 (Ubuntu):
status: New → Triaged
Changed in notmuch (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in ruby2.1 (Debian):
status: Unknown → Fix Released
Revision history for this message
Artur Rona (ari-tczew) wrote :

    Removal requested on 2015-08-20.
    Deleted on 2015-08-20 by Steve Langasek

    (From Debian) ROM; obsolete, replaced by ruby2.1, unsupported; Debian bug #747580
    Published on 2015-05-05
    Copied from ubuntu utopic in Primary Archive for Ubuntu

Changed in ruby1.9.1 (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Artur Rona (ari-tczew) wrote :

notmuch builds with ruby 2.2 already.

Changed in notmuch (Ubuntu):
status: Triaged → Invalid
Changed in ruby1.9.1 (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.