Hello,
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: https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
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: https://gist.github.com/pvalena/dd00dafa1bf37b8f74312b57e650d8b0 + means addition - means removal
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.
Currently failing (dependent) packages: https://gist.github.com/pvalena/f9b40fdebed1b9864ea1e1c7fedcb14a
_ _ _ _
Additionaly, Ruby on Rails was updated to 6.0.3.3 in Rawhide and F33 has update pending: https://bodhi.fedoraproject.org/updates/FEDORA-2020-83a4999b7c https://bodhi.fedoraproject.org/updates/FEDORA-2020-4dd34860a3
Please let me know if this breaks something for you. You can see my test passing here: https://gist.github.com/pvalena/350309be47258e9bdb0e01f7e04fde12
Regards,
Hello,
nice work! From a swift look on the list any `simplecov` might not be needed IMO.
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 `cucumber-cucumber-expressions`.
Regards, Jarek
On 30/09/2020 21:33, Pavel Valena wrote:
Hello,
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: https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
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: https://gist.github.com/pvalena/dd00dafa1bf37b8f74312b57e650d8b0
- means addition
- means removal
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.
Currently failing (dependent) packages: https://gist.github.com/pvalena/f9b40fdebed1b9864ea1e1c7fedcb14a
Additionaly, Ruby on Rails was updated to 6.0.3.3 in Rawhide and F33 has update pending: https://bodhi.fedoraproject.org/updates/FEDORA-2020-83a4999b7c https://bodhi.fedoraproject.org/updates/FEDORA-2020-4dd34860a3
Please let me know if this breaks something for you. You can see my test passing here: https://gist.github.com/pvalena/350309be47258e9bdb0e01f7e04fde12
Regards,
The list of packages `ruby-rails` group in Koschei is useful to manage the packages related to Ruby on Rails. https://koschei.fedoraproject.org/groups/ruby-rails Thanks for the work.
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 seems rubygem-rspec2 was removed from the list.
From a swift look on the list any `simplecov` might not be needed IMO.
it seems rubygem-simplecov does not exist on the list.
It would be nice to know what cucumber version will be required for this to build
it seems cucumber also does not exist on the list.
----- Original Message -----
From: "Jun Aruga" jaruga@redhat.com To: "Ruby SIG mailing list" ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 10:01:44 AM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
The list of packages `ruby-rails` group in Koschei is useful to manage the packages related to Ruby on Rails. https://koschei.fedoraproject.org/groups/ruby-rails Thanks for the work.
Yes, that's what I intend to update, like my email said, hopefully clearly enough. The proposed and the changes are in comparison with current ruby-rails group list.
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 seems rubygem-rspec2 was removed from the list.
From a swift look on the list any `simplecov` might not be needed IMO.
it seems rubygem-simplecov does not exist on the list.
It would be nice to know what cucumber version will be required for this to build
it seems cucumber also does not exist on the list.
I'll investigate, and let you know why they're on the list (but obviously, they're in BuildRequires of some package). There could be also an option of creating "ignorelist" for my script. The packages that wouldn't be allowed in `ruby-rails` list, and therefore their build dependencies wouldn't be resolved (and included therefore).
Thanks for the feedback!
Pavel
-- Jun | He - His - Him
Pavel
Dne 30. 09. 20 v 22:16 Jaroslav Prokop napsal(a):
Hello,
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.
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 `cucumber-cucumber-expressions`.
Yes, there were huge reorganization in upstream cucumber. Any help with getting recent cucumber into Fedora would be appreciated.
Regards, Jarek
On 30/09/2020 21:33, Pavel Valena wrote:
Hello,
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: https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
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.
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: https://gist.github.com/pvalena/dd00dafa1bf37b8f74312b57e650d8b0 + 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?
And ruby itself should definitely be on the list.
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.
Vít
Currently failing (dependent) packages: https://gist.github.com/pvalena/f9b40fdebed1b9864ea1e1c7fedcb14a
Additionaly, Ruby on Rails was updated to 6.0.3.3 in Rawhide and F33 has update pending: https://bodhi.fedoraproject.org/updates/FEDORA-2020-83a4999b7c https://bodhi.fedoraproject.org/updates/FEDORA-2020-4dd34860a3
Please let me know if this breaks something for you. You can see my test passing here: https://gist.github.com/pvalena/350309be47258e9bdb0e01f7e04fde12
Regards,
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.o...
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 11:31:10 AM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 30. 09. 20 v 22:16 Jaroslav Prokop napsal(a):
Hello,
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 `cucumber-cucumber-expressions`.
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.
Regards, Jarek
On 30/09/2020 21:33, Pavel Valena wrote:
Hello,
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: https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
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: https://gist.github.com/pvalena/dd00dafa1bf37b8f74312b57e650d8b0 + 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!
Pavel
Vít
Currently failing (dependent) packages: https://gist.github.com/pvalena/f9b40fdebed1b9864ea1e1c7fedcb14a
Additionaly, Ruby on Rails was updated to 6.0.3.3 in Rawhide and F33 has update pending: https://bodhi.fedoraproject.org/updates/FEDORA-2020-83a4999b7c https://bodhi.fedoraproject.org/updates/FEDORA-2020-4dd34860a3
Please let me know if this breaks something for you. You can see my test passing here: https://gist.github.com/pvalena/350309be47258e9bdb0e01f7e04fde12
Regards,
Dne 01. 10. 20 v 11:47 Pavel Valena napsal(a):
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 11:31:10 AM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 30. 09. 20 v 22:16 Jaroslav Prokop napsal(a):
On 30/09/2020 21:33, Pavel Valena wrote:
Hello,
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: https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
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 think there should be some initial list of packages we do care about, this should be probably:
ruby
rubygem-rails and actually everything what appears in the Gemfile of fresh RoR app
and some DB adapters:
rubygem-mysql2
rubygem-mongo
rubygem-pg (mongo got somehow pulled in, but it is just by coincidence I'd say).
And ruby itself should definitely be on the list.
Well, isn't `ruby` other group? I've opted for `rubygems-` packages only.
I think we were talking about RoR group, which might not be just about rubygems. Actually, we might be missing js-jquery for example. There used to be also some other js- dependencies required by RoR app.
V.
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 12:02:02 PM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 01. 10. 20 v 11:47 Pavel Valena napsal(a):
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 11:31:10 AM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 30. 09. 20 v 22:16 Jaroslav Prokop napsal(a):
On 30/09/2020 21:33, Pavel Valena wrote:
Hello,
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: https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
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 think there should be some initial list of packages we do care about, this should be probably:
ruby
Not sure about ruby itself. Rails could theoretically run on any ruby runtime, right? Anyway there's not much harm to have it there, if you insist. I'm simply missing the point, ... now I realized. We don't have a `ruby` Koschei group. Maybe that's something we want instead?
rubygem-rails and actually everything what appears in the Gemfile of fresh RoR app
Ok, good idea. Although we currently don't have the asset pipeline (webpacker).
and some DB adapters:
rubygem-mysql2
rubygem-mongo
rubygem-pg (mongo got somehow pulled in, but it is just by coincidence I'd say).
Yes, I think this corresponds to comps group. I'll take all packages from there.
And ruby itself should definitely be on the list.
Well, isn't `ruby` other group? I've opted for `rubygems-` packages only.
I think we were talking about RoR group, which might not be just about rubygems. Actually, we might be missing js-jquery for example. There used to be also some other js- dependencies required by RoR app.
Right, let me check other runtime packages installed freshly with 'Ruby on Rails', or @rubyonrails (that might cover all usecases above).
V.
Pavel
Dne 01. 10. 20 v 20:21 Pavel Valena napsal(a):
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 12:02:02 PM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 01. 10. 20 v 11:47 Pavel Valena napsal(a):
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 11:31:10 AM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 30. 09. 20 v 22:16 Jaroslav Prokop napsal(a):
On 30/09/2020 21:33, Pavel Valena wrote:
Hello,
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: https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
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 think there should be some initial list of packages we do care about, this should be probably:
ruby
Not sure about ruby itself. Rails could theoretically run on any ruby runtime, right?
We don't have any other runtime ...
Anyway there's not much harm to have it there, if you insist. I'm simply missing the point, ... now I realized. We don't have a `ruby` Koschei group. Maybe that's something we want instead?
It is probably easier to search for "ruby". I don't want to create some dump groups, which will nobody care about. "rails" group would deserve more attention on itself.
rubygem-rails and actually everything what appears in the Gemfile of fresh RoR app
Ok, good idea. Although we currently don't have the asset pipeline (webpacker).
Please don't add on the list any packages we don't have (sorry, couldn't resist :D)
and some DB adapters:
rubygem-mysql2
rubygem-mongo
rubygem-pg (mongo got somehow pulled in, but it is just by coincidence I'd say).
Yes, I think this corresponds to comps group. I'll take all packages from there.
Good idea.
V.
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Friday, October 2, 2020 10:28:42 AM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 01. 10. 20 v 20:21 Pavel Valena napsal(a):
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 12:02:02 PM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 01. 10. 20 v 11:47 Pavel Valena napsal(a):
----- Original Message -----
From: "Vít Ondruch" vondruch@redhat.com To: ruby-sig@lists.fedoraproject.org Sent: Thursday, October 1, 2020 11:31:10 AM Subject: Re: ruby-rails group in Koschei & RoR 6.0.3.3
Dne 30. 09. 20 v 22:16 Jaroslav Prokop napsal(a):
On 30/09/2020 21:33, Pavel Valena wrote: > Hello, > > 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: > https://gist.github.com/pvalena/ccdd482ace158bc55c891528e2be22ce
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 think there should be some initial list of packages we do care about, this should be probably:
ruby
Not sure about ruby itself. Rails could theoretically run on any ruby runtime, right?
We don't have any other runtime ...
Yes, not now. I was just making a point on Ruby on Rails not being tied to one.
Anyway there's not much harm to have it there, if you insist. I'm simply missing the point, ... now I realized. We don't have a `ruby` Koschei group. Maybe that's something we want instead?
It is probably easier to search for "ruby". I don't want to create some dump groups, which will nobody care about. "rails" group would deserve more attention on itself.
Right. `ruby` is probably sufficient to build ruby (no bootstrap package atm.).
That doesn't explain why it should be in ruby-rails group (apart from `ruby` in the name), but like I said before, there's no strong argument against, so I'll keep it on "includelist".
rubygem-rails and actually everything what appears in the Gemfile of fresh RoR app
Ok, good idea. Although we currently don't have the asset pipeline (webpacker).
Please don't add on the list any packages we don't have (sorry, couldn't resist :D)
Sure, I didn't mean to. What I wanted to point out, is that the fresh RoR Gemfile needs to be modified, to be usable in our Fedora.
and some DB adapters:
rubygem-mysql2
rubygem-mongo
rubygem-pg (mongo got somehow pulled in, but it is just by coincidence I'd say).
Yes, I think this corresponds to comps group. I'll take all packages from there.
Good idea.
V.
Pavel
# Note to self: investigate rubygem-mongo.
ruby-sig@lists.fedoraproject.org