From: Luis Lavena <luislavena@...>
Date: 2010-10-25T03:50:18+09:00
Subject: Re: Workaround for gem push

On Oct 24, 8:49 am, Brian Candler <b.cand...@pobox.com> wrote:
> I've got an updated gem to push out, but I've got a problem.
>
> * gemcutter appears to have removed 'gem push', because it has been
> merged into rubygems 1.3.6
> * my Ubuntu 10.4 box has rubygems 1.3.5
> * Debian intentionally disabled "gem update --system"
>
> Is there an older version of gemcutter which would work acceptably with
> rubygems 1.3.5? I've tried both 0.6.1 and 0.5.0 but not gone back any
> earlier than that.
>
> I know I could just toss out the Debian ruby and/or rubygems, but I'd
> rather not right now.
>

The only workaround I can think of right now is remove ubuntu managed
rubygems and manually install 1.3.7 on top of it.

The problem with that approach is that operation might bork your
existing gem installation due the /var/ vs /usr/lib installation
changes done by Debian concept of LFS (Linux Filesystem) structure.

The saner and zero compromise approach will be use RVM to have a newer
and system-independent Ruby installation, but that goes against your
first point.

There is always a compromise.

--
Luis Lavena