----- Original Message -----
From: "Vít Ondruch" <vondruch(a)redhat.com>
Sent: Wednesday, May 13, 2020 6:11:16 PM
Subject: Re: Retired "rubygems" package
Resurrecting this thread after long time.
I have unretired the package indeed. But it was lying around without
actual fixes. But fear not, this is about to change. Here is my PR:
and scratch build:
But be careful, I have not tested this at all, except that it builds.
I've started rebuild on top of it:
So far it seems all've build fine (actionview failure is unrelated).
Dne 13. 08. 19 v 11:31 Jun Aruga napsal(a):
>> Obviously if I was convinced we really need it, I'd did that without
> I do not think that someone is using the independent "rubygems" package.
> It's a legacy of old Ruby that does not bundle rubygem in it.
> But I like that if you want to retire this kind of key package, just
> share us what you will do on this mailing-list, before your work to
> Then I am fine.
> On Mon, Aug 12, 2019 at 12:09 PM Vít Ondruch <vondruch(a)redhat.com> wrote:
>> Hi all,
>> The independent "rubygems" package was retired, because it FTBFS
>> for some while:
>> Now I wonder, do we care? Should I unretire it while there is a chance
>> to do it without review or we don't care and we are fine with the
>> bundled version shipped in Ruby? Obviously if I was convinced we really
>> need it, I'd did that without asking. So what are your opinions?