"The ruby1.9.1 in 14.04 LTS is in main and is supported by the Ubuntu
security team for the life of the LTS."
Is the Ubuntu security team providing out-of-band updates for Ruby
1.9.x? Because if not, it clearly is *not* being supported for the life
of LTS -- 1.9.x is obsolete and isn't receiving
This really is a bug and baffling that it won't be fixed. We used 14.04
for the stability not the brokenness and having to go to 15.10 to get
working ruby version that I don't have to manually symlink is not a
great solution.
--
You received this bug notification because you are a member of
The ruby1.9.1 in 14.04 LTS is in main and is supported by the Ubuntu
security team for the life of the LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310292
Title:
installing `ruby2.0` results
BTW, this is actually maybe a security problem too -- people who think
they are installing a supported version are actually silently getting an
unsupported version that no longer receives upstream security fixes:
https://www.ruby-lang.org/en/news/2014/01/10/ruby-1-9-3-will-end-
on-2015/
--
You
Here is our workaround which should be better than the ones proposed
above (doesn't get wiped out by package upgrade / reinstall)
# Rename original out of the way, so updates / reinstalls don't squash our hack
fix
dpkg-divert --add --rename --divert /usr/bin/ruby.divert /usr/bin/ruby
dpkg-divert
I just stumbled on this, and if the Ubuntu team will close such obvious
problems with Won't fix for a LTS release, they should IMO just be up
front that it is not supported and remove Ruby packaging entirely.
Leaving totally broken packages in doesn't help anyone.
--
You received this bug
Link to SRU proposal: https://bugs.launchpad.net/ubuntu/+source/ruby-
defaults/+bug/1315143
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310292
Title:
installing `ruby2.0` results in ruby
+1 for fixing this as a Trusty SRU. Keeping it broken for the next two
years is completely ridiculous. Please PLEASE fix the ruby2.0 dependency
error on Trusty.
The least-surprising thing to do is to change the package dependency
error so that installing ruby2.0 does not pull in ruby1.9.1. People
I ran into this today. I was surprised that the update-alternatives
support for ruby had been yanked. Here's how to set ruby2.0 to be the
default:
sudo ln -sf /usr/bin/ruby2.0 /usr/bin/ruby
sudo ln -sf /usr/bin/gem2.0 /usr/bin/gem
No promises this will work 100% or not cause problems with other
That Ruby2.0 depends on Ruby1.9.1 isn't as much the problem as the fact
that when Ruby2.0 is installed, it is not the default ruby; ruby1.9 is.
That, to me, is completely baffling.
On Mon, May 12, 2014 at 12:10 AM, Daniel Muller
1310...@bugs.launchpad.netwrote:
The problem seems to be in the
What does Won't Fix mean for this LTS release?
Does it mean, there will not be, for lifetime of LTS, anyway 'ruby'
would call version 2.0? If you want that to occur, you need to mangle
symlinks yourself?
Isn't this regression? As 'ruby-switch' package did this in 13.10?
Could solution be, to
The problem seems to be in the fact that ruby2.0 depends on ruby, which
depends on ruby1.9.1.
I rebundled the package without the dependencies to ruby and
rubygems-integration: https://launchpad.net/~spuul/+archive/ruby2.0
I removed the dependency to libjs-jquery too (I am unclear why this
I don't know if Ubuntu has dedicated resources to ruby or not,
but I doubt they can still change this for 14.04.
no, we don't have, and it won't be changed for trusty. fixed in utopic.
if you are interested in getting ruby to a recent version for future
releases please consider working with
won't fix for trusty
** Changed in: ruby2.0 (Ubuntu Trusty)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310292
Title:
installing `ruby2.0` results in ruby
fixed in utopic
** Also affects: ruby2.0 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ruby2.0 (Ubuntu Utopic)
Importance: Undecided
Status: Confirmed
** Changed in: ruby2.0 (Ubuntu Utopic)
Status: Confirmed = Fix Released
--
You received this
Sorry, could you dumb this down a notch for me?
I get that when I request ruby2.0 you have $REASONS for also
installing 1.9.fuckingancientwhocares
What I fail to understand is how not making THE THING I REQUESTED the
default.
--
You received this bug notification because you are a member of
I understand quite well how package management works in Ubuntu and
Debian. Over the past 5 years I've packed a number of Ruby projects
(such as Chef and its dependencies) for Debian and Ubuntu. I guess
that's why this problem irritates me so much: I thought we were finally
having progress to get
You're probably misunderstanding how this works in Debian, let me
explain:
Installing ruby1.9.1 gives you /usr/bin/ruby1.9.1.
Installing ruby2.0 gives you /usr/bin/ruby2.0.
Installing ruby2.1 gives you /usr/bin/ruby2.1.
The ruby package is merely a package that points /usr/bin/ruby to one of
From the Debian POV, this is working as designed.
If you install ruby2.0, it is available as ruby2.0.
** Changed in: ruby2.0 (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Furthermore, this is fixed in the Debian package! Ubuntu 14.04 was past
import freeze when the package was fixed. It should be implemented.
Seriously.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Are you kidding me?
In what possible scenario would you NOT expect apt-get install ruby2.0
to give you ANYTHING but ruby version 2.0(dot whatever) as the default
Ruby interpreter?
This is broken.
** Changed in: ruby2.0 (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug
To clarify: it should make the default `ruby` point at Ruby 2.0. If this
is a bug in update-alternatives, then so be it. It is absurd to me that
this was closed invalid when it doesn't do the thing that a user would
expect.
--
You received this bug notification because you are a member of Ubuntu
Expected behavior is not delivered.
If I ran 'apt-get install apache2' and found that apache1.x was
installed instead, I'd be upset.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310292
Title:
From the Debian POV, this is working as designed.
If that's the case, why did Debian consider it a bug and fix it
upstream? You've got me very confused.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree that I expect ruby2.0 to be the only version installed and at
the least the default version.
It appears update-alternatives no longer supports ruby out of the box as
well.
# update-alternatives --config ruby
update-alternatives: error: no alternatives for ruby
It also seems strange to
It appears upstream (Debian) Ruby package changed this during the Trusty
freeze:
ruby-defaults (1:2.0.0.1~exp3) experimental; urgency=medium
* ruby-all-dev: migrate from Ruby 1.9.1 and 2.0 to Ruby 2.0 and 2.1
* ruby: remove Breaks/Conflicts/Replaces against old interpreter packages
as
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ruby2.0 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310292
Title:
Truth is spoken here. If I install Ruby2.0, that's what I expect to have
readily available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310292
Title:
installing `ruby2.0` results in ruby
28 matches
Mail list logo
