----- Original Message -----
From: "Vít Ondruch" <vondruch(a)redhat.com>
Sent: Thursday, October 1, 2020 11:31:10 AM
Subject: Re: ruby-rails group in Koschei & RoR 184.108.40.206
Dne 30. 09. 20 v 22:16 Jaroslav Prokop napsal(a):
> nice work!
> From a swift look on the list any `simplecov` might not be needed IMO.
There might be some package pulling in simplecov, but we typically
remove this dependency, so it would probably make sense to identify how
simplecov gets on the list and remove the dependency.
Yes, correct, that's what I intend to do.
> It would be nice to know what cucumber version will be required for
> this to build
> since there were renames of multiple packages that cucumber depends on,
> for example the gem `cucumber-expressions` was renamed to
Yes, there were huge reorganization in upstream cucumber. Any help with
getting recent cucumber into Fedora would be appreciated.
Ok, let me check what requires the older one.
> On 30/09/2020 21:33, Pavel Valena wrote:
>> following on my previous email (bellow), I'm working on regenerating
>> the list of packages `ruby-rails` group in Koschei.
>> I've done some fixes to package resolving in my script (I'm left with
>> 3 unresolved /ambiguous/ packages as well), and got current list:
I think there is missing rubygem-mysql2, which might not appear
anywhere, because it is just optional, but we should not forget to
include it in the list. For the similar reason, it would be nice to keep
rubygem-mongo on the list.
Hmm, but if it's not in the buildroot, should we concern ourselves with it? Or do we
care for weak dependencies the same? I could add those explicitly (Recommends ->
Require for those builds), or could be just on some "Includelist" WDYT?
>> I'm also thinking of a way to get list of packages that are requiring
>> the dependency (let me know if you want to see that).
>> Proposed (generated) changes:
>> + means addition
>> - means removal
Removed rubygem-web-console? I think it is one of the debug dependencies
of default RoR app. Or was this changed? rubygem-debug_inspector might
be the same case.
And removed rubygem-sass-rails? That also is surprising to me.
Also, what happened to sdoc?
Let me investigate, as with the rest.
And ruby itself should definitely be on the list.
Well, isn't `ruby` other group? I've opted for `rubygems-` packages only.
>> There are some suspicious entries, like `+rubygem-rspec2`, which will
>> need further investigation. I'll welcome any additional feedback on
>> packages that are missing, or should not be in this group.
It would be nice to get rid of RSpec2, but last time I checked, it did
not seems to be really easy.
Hopefully it'll be better now. I'll check.
Thanks for the feedback!
>> Currently failing (dependent) packages:
>> _ _ _ _
>> Additionaly, Ruby on Rails was updated to 220.127.116.11 in Rawhide and F33
>> has update pending:
>> Please let me know if this breaks something for you. You can see my
>> test passing here: