Hi Rubyists,
Today, I have built Ruby 2.1 [1]! It is built in the f21-ruby side tag [2]. Now it is time for your action. Please check the updated Ruby guidelines [3] and start rebuilding packages using command:
fedpkg build --target=f21-ruby
For help with migration and build, you can use fermig [4]. Single file can be migrated by update.rb script [5]:
$ ~/projects/fermig/update.rb rubygem-foo.spec
This is the list of package which must be rebuild:
$ repoquery --disablerepo=* --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel'
But I'd like to encourage you to check all your packages, if they are compatible with Ruby 2.1 (for example yesterday, I had to update rubygem-introspection to be compatible with Ruby 2.1).
Also note the update of Minitest 4.x to Minitest 5.x which may cause some troubles.
Anyway, together with jstribny, we will go through every package and try to rebuild if you'll not be faster then us ;) Any help is appreciated as well as feedback.
Thanks
Vít
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=509933 [2] https://fedorahosted.org/rel-eng/ticket/5882 [3] https://fedorahosted.org/fpc/ticket/409 [4] https://github.com/voxik/fermig [5] https://github.com/voxik/fermig/blob/master/update.rb [6] https://lists.fedoraproject.org/pipermail/ruby-sig/2014-April/001534.html
And I forgot about gem2rpm. I have already prepared changes for F21, but did not push them nor released new version. I'll do it soon. Please put some pressure on me if you need it sooner ;)
Vít
Dne 9.4.2014 12:26, Vít Ondruch napsal(a):
Hi Rubyists,
Today, I have built Ruby 2.1 [1]! It is built in the f21-ruby side tag [2]. Now it is time for your action. Please check the updated Ruby guidelines [3] and start rebuilding packages using command:
fedpkg build --target=f21-ruby
For help with migration and build, you can use fermig [4]. Single file can be migrated by update.rb script [5]:
$ ~/projects/fermig/update.rb rubygem-foo.spec
This is the list of package which must be rebuild:
$ repoquery --disablerepo=* --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel'
But I'd like to encourage you to check all your packages, if they are compatible with Ruby 2.1 (for example yesterday, I had to update rubygem-introspection to be compatible with Ruby 2.1).
Also note the update of Minitest 4.x to Minitest 5.x which may cause some troubles.
Anyway, together with jstribny, we will go through every package and try to rebuild if you'll not be faster then us ;) Any help is appreciated as well as feedback.
Thanks
Vít
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=509933 [2] https://fedorahosted.org/rel-eng/ticket/5882 [3] https://fedorahosted.org/fpc/ticket/409 [4] https://github.com/voxik/fermig [5] https://github.com/voxik/fermig/blob/master/update.rb [6] https://lists.fedoraproject.org/pipermail/ruby-sig/2014-April/001534.html _______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
On 04/09/2014 01:29 PM, Vít Ondruch wrote:
And I forgot about gem2rpm. I have already prepared changes for F21, but did not push them nor released new version. I'll do it soon. Please put some pressure on me if you need it sooner ;)
Can you at least push these changes, even at a different branch?
I was thinking to also include in the template the %check macro:
``` %check pushd .%{gem_instdir}
popd ```
That way we could add more "pressure" for packagers to use test suites. I can submit a PR :)
Dne 10.4.2014 13:51, Achilleas Pipinellis napsal(a):
On 04/09/2014 01:29 PM, Vít Ondruch wrote:
And I forgot about gem2rpm. I have already prepared changes for F21, but did not push them nor released new version. I'll do it soon. Please put some pressure on me if you need it sooner ;)
Can you at least push these changes, even at a different branch?
I pushed it into master.
I was thinking to also include in the template the %check macro:
%check pushd .%{gem_instdir} popdThat way we could add more "pressure" for packagers to use test suites. I can submit a PR :)
Feel free to send PR (or open issue at minimum :).
Thanks.
Vít
Hi Vit,
Anyway, together with jstribny, we will go through every package and try to rebuild if you'll not be faster then us ;) Any help is appreciated as well as feedback.
I'd like to help. How does one do that? What does one need to be able to help? Get a running Rawhide install and use mock/rpmbuild?
/allen
________________________________
Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.
Dne 9.4.2014 20:17, Allen Hewes napsal(a):
Hi Vit,
Anyway, together with jstribny, we will go through every package and try to rebuild if you'll not be faster then us ;) Any help is appreciated as well as feedback.
I'd like to help. How does one do that? What does one need to be able to help? Get a running Rawhide install and use mock/rpmbuild?
/allen
Hi Allen,
Thanks for your offer.
mock is enough. It doesn't matter what Fedora you run ... in theory, you can work just with koji, but it would be hard to debug the problems you might encounter.
You can start with rebuild of binary packages you own, for that case is everything easy (just don't forget to specify the target). If you'd like to rebuild packages you don't own but you care about, you can ask for permissions in pkgdb and see if you'll get approved. Otherwise, please update the .spec file and store the SRPM somewhere, where I can pick it up and rebuild using my povenpackager privileges.
HTH
Vít
Hi,
I'd like to help. How does one do that? What does one need to be able to help? Get a running Rawhide install and use mock/rpmbuild?
We created an etherpad for the f21 rebuild[1], please assign yourself to the packages you are going to rebuild.
Apart from mock, you can use scratch build:
~/projects/fermig/update.rb rubygem-name.spec fedpkg scratch-build --srpm --target=f21-ruby
This will change the obvious + try to build it in Koji with f21-ruby target. Then you can commit to master and run the build (also with the target).
Thank you for offering your help.
Josef
I'd like to help. How does one do that? What does one need to be able to
help? Get a running Rawhide install and use mock/rpmbuild?
We created an etherpad for the f21 rebuild[1], please assign yourself to the packages you are going to rebuild.
Apart from mock, you can use scratch build:
~/projects/fermig/update.rb rubygem-name.spec fedpkg scratch-build --srpm --target=f21-ruby
This will change the obvious + try to build it in Koji with f21-ruby target. Then you can commit to master and run the build (also with the target).
Thank you for offering your help.
Well, you guys are light-years ahead of me. I am a beginner at this Fedora stuff. I've only done this for my own repo and koji cooker. My koji is older and runs on RHEL 5. So I will be asking what seem like dumb questions, but it's really I have no idea of what you guys are talking about.
I don't own any packages of anything. I have never used the Fedora Koji system for anything but I am versed in Koji usage b/c I have my own. Is account perms and creation synced with the FeSCO account I created a while back? i.e. can I do scratch builds? But if the build works in mock, there's a high probability it will work in Koji but every now and then, that's not true. I don't know what fermig is. I have never heard of etherpad. Would I be able to do what you've asked without accounts and whatnot? I don't know what pkgdb is.
I thought I was signing up getting all the Fedora "gems" (i.e. rubygem-*) built/confirmed with Ruby 2.1.1 and RubyGems 2.2.2. Is that not what I signed up for? ;-) There's a lot in that list I am familiar with: typhoeus, nokogiri, therubyracer, ffi, hpricot, thin, syck, gherkin. Some of these look like they might be deprecated...
Also, you are missing my favorite: bundler. You'll need updated Thor and rpsec 3.0.0.beta2 for it to pass its tests.
I do most of my work in mock but every now and then I do have use rpmbuild --rebuild on an install of the target OS to solve issues. So I should have a rawhide VM installed, right? Just in case...
Is there somewhere you guys can send complete Fedora n00bies?
/allen
________________________________
Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.
Dne 11.4.2014 17:32, Allen Hewes napsal(a):
I'd like to help. How does one do that? What does one need to be able to
help? Get a running Rawhide install and use mock/rpmbuild?
We created an etherpad for the f21 rebuild[1], please assign yourself to the packages you are going to rebuild.
Apart from mock, you can use scratch build:
~/projects/fermig/update.rb rubygem-name.spec fedpkg scratch-build --srpm --target=f21-ruby
This will change the obvious + try to build it in Koji with f21-ruby target. Then you can commit to master and run the build (also with the target).
Thank you for offering your help.
Well, you guys are light-years ahead of me. I am a beginner at this Fedora stuff.
Sorry, it is always hard to explain everything in one email ;) I would suggest you to go through [1] or [2] and filter out irrelevant stuff such as reviews, bugzilla etc.
I've only done this for my own repo and koji cooker. My koji is older and runs on RHEL 5. So I will be asking what seem like dumb questions, but it's really I have no idea of what you guys are talking about.
I don't own any packages of anything. I have never used the Fedora Koji system for anything but I am versed in Koji usage b/c I have my own. Is account perms and creation synced with the FeSCO account I created a while back? i.e. can I do scratch builds? But if the build works in mock, there's a high probability it will work in Koji but every now and then, that's not true.
Hmm, not 100% sure if you can do scratch builds without being sponsored as a package. Nevertheless, I am attaching my mock config I am using.
I don't know what fermig is.
Bunch of scripts which will do the basic conversion, but nothing fancy. Not much documented. You should read the code or search this ML and ask for clarification.
https://github.com/voxik/fermig
I have never heard of etherpad. Would I be able to do what you've asked without accounts and whatnot?
Just open the page, write there your name and when you pick some interesting gem, write your name behind to let us know that you are working on it to prevent duplicated work.
http://piratepad.net/NWw7WqbvTb
I don't know what pkgdb is.
https://admin.fedoraproject.org/pkgdb/
Allows to assign packagers to packages and their rights.
I thought I was signing up getting all the Fedora "gems" (i.e. rubygem-*) built/confirmed with Ruby 2.1.1 and RubyGems 2.2.2. Is that not what I signed up for? ;-)
Yes, that was my understanding :)
There's a lot in that list I am familiar with: typhoeus, nokogiri, therubyracer, ffi, hpricot, thin, syck, gherkin. Some of these look like they might be deprecated...
Also, you are missing my favorite: bundler. You'll need updated Thor and rpsec 3.0.0.beta2 for it to pass its tests.
Bundler has no binary extension, therefore it is not on the list. But there might be some updates needed.
I do most of my work in mock but every now and then I do have use rpmbuild --rebuild on an install of the target OS to solve issues. So I should have a rawhide VM installed, right? Just in case...
No, you should not need any VM, mock should be alright.
Is there somewhere you guys can send complete Fedora n00bies?
Se above.
I'll try to sum my workflow in several bulletpoints
1) fedpkg co rubygem-foo 2) cd rubygem-foo 3) fermig/update.rb rubygem-foo.spec 4) fedpkg srpm 5) mock -r fedora-f21-ruby-x86_64 rubygem-foo-1.2.3-1.fc21.src.rpm [--no-clean] 6) fix any issues and repeat from 4)
If the package is ready and tested, please upload the SRPM somewhere and note the link into etherpad, or send the link here, ping me via IRC, whatever works for you :)
HTH
Vít
[1] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers [2] http://axilleas.me/en/blog/2013/i-got-approved-as-a-packager-now-what/
Vit,
I don't own any packages of anything. I have never used the Fedora Koji system for anything but I am versed in
Koji usage b/c I have my own. Is account perms and creation synced with the FeSCO account I created a while back? i.e. can I do scratch builds? But if the build works in mock, there's a high probability it will work in Koji but every now and then, that's not true.
Hmm, not 100% sure if you can do scratch builds without being sponsored as a package. Nevertheless, I am attaching my mock config I am using.
The mock config is a good start but how would I feed dependencies into those repositories without creating my own repository somewhere? I have been playing around with COPR of late to build GNOME 3.12 for Fedora 19. Do you think COPR be used for this process? Also, I could put off worrying about this until I come across packages which have these dependencies.
Also, you are missing my favorite: bundler. You'll need updated Thor and
rpsec 3.0.0.beta2 for it to pass its tests.
Bundler has no binary extension, therefore it is not on the list. But there might be some updates needed.
Ah, OK that explains a lot, ext's only in the etherpad/PiratePad list.
Let's take JSON for instance. You have JSON 1.7.7 listed in etherpad/PiratePad but there's newer versions (1.8.1). As part of this process, do want updates? Or just updates to make things (test suites) run for the combination of Ruby/RubyGems/gem targeting Fedora 21? If you'd update JSON, you'd update json_pure and multi_json. Are those included in this process? Or is the goal to get what's in that list built against Ruby 2.1.1 / RubyGems 2.2.2?
/allen
________________________________
Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.
On 04/11/2014 08:23 PM, Allen Hewes wrote:
Vit,
I don't own any packages of anything. I have never used the Fedora Koji system for anything but I am versed in
Koji usage b/c I have my own. Is account perms and creation synced with the FeSCO account I created a while back? i.e. can I do scratch builds? But if the build works in mock, there's a high probability it will work in Koji but every now and then, that's not true.
Hmm, not 100% sure if you can do scratch builds without being sponsored as a package. Nevertheless, I am attaching my mock config I am using.
The mock config is a good start but how would I feed dependencies into those repositories without creating my own repository somewhere? I have been playing around with COPR of late to build GNOME 3.12 for Fedora 19. Do you think COPR be used for this process? Also, I could put off worrying about this until I come across packages which have these dependencies.
Since this is just a rebuild (using the same version as is), all dependencies will be in rawhide and already met.
Also, you are missing my favorite: bundler. You'll need updated Thor and
rpsec 3.0.0.beta2 for it to pass its tests.
Bundler has no binary extension, therefore it is not on the list. But there might be some updates needed.
Ah, OK that explains a lot, ext's only in the etherpad/PiratePad list.
Let's take JSON for instance. You have JSON 1.7.7 listed in etherpad/PiratePad but there's newer versions (1.8.1). As part of this process, do want updates? Or just updates to make things (test suites) run for the combination of Ruby/RubyGems/gem targeting Fedora 21? If you'd update JSON, you'd update json_pure and multi_json. Are those included in this process? Or is the goal to get what's in that list built against Ruby 2.1.1 / RubyGems 2.2.2?
I guess we go first with the rebuild and then with any updates.
Dne 11.4.2014 19:54, Achilleas Pipinellis napsal(a):
On 04/11/2014 08:23 PM, Allen Hewes wrote:
Vit,
I don't own any packages of anything. I have never used the Fedora Koji system for anything but I am versed in
Koji usage b/c I have my own. Is account perms and creation synced with the FeSCO account I created a while back? i.e. can I do scratch builds? But if the build works in mock, there's a high probability it will work in Koji but every now and then, that's not true.
Hmm, not 100% sure if you can do scratch builds without being sponsored as a package. Nevertheless, I am attaching my mock config I am using.
The mock config is a good start but how would I feed dependencies into those repositories without creating my own repository somewhere? I have been playing around with COPR of late to build GNOME 3.12 for Fedora 19. Do you think COPR be used for this process? Also, I could put off worrying about this until I come across packages which have these dependencies.
Since this is just a rebuild (using the same version as is), all dependencies will be in rawhide and already met.
Yes, dependencies are met.
But to answer your question, you have two options how to install additional dependencies into mock:
1) You can update the config file and add there some local repository. 2) If there is not much dependencies, you can install them into mock manually (mock --install mydependency.rpm), but then you have to always use --no-clean option, otherwise the buildroot will be recreated from scratch and the dependency lost.
Also, you are missing my favorite: bundler. You'll need updated Thor and
rpsec 3.0.0.beta2 for it to pass its tests.
Bundler has no binary extension, therefore it is not on the list. But there might be some updates needed.
Ah, OK that explains a lot, ext's only in the etherpad/PiratePad list.
Let's take JSON for instance. You have JSON 1.7.7 listed in etherpad/PiratePad but there's newer versions (1.8.1).
json is not that good example, since Ruby ships json as a subpackage. They are overlapped with the standalone version.
As part of this process, do want updates? Or just updates to make things (test suites) run for the combination of Ruby/RubyGems/gem targeting Fedora 21? If you'd update JSON, you'd update json_pure and multi_json. Are those included in this process? Or is the goal to get what's in that list built against Ruby 2.1.1 / RubyGems 2.2.2?
I guess we go first with the rebuild and then with any updates.
Well, less changes is better, but otherwise there is no general answer. But here it is how I see it:
1) When I am rebuilding my package, I might consider update to the latest version, since I am maintainer and I'd need to do it anyway. 2) I update the package, if I know that there were some compatibility fixes and I know I don't break any dependency. I might decide to backport the patch otherwise, if the changes were not too invasive. 3) Otherwise, I try to not change too much, since it is maintainers decision, what version is in Fedora.
Vít
Dne 10.4.2014 09:09, Vít Ondruch napsal(a):
Dne 9.4.2014 20:17, Allen Hewes napsal(a):
Hi Vit,
Anyway, together with jstribny, we will go through every package and try to rebuild if you'll not be faster then us ;) Any help is appreciated as well as feedback.
I'd like to help. How does one do that? What does one need to be able to help? Get a running Rawhide install and use mock/rpmbuild?
/allen
Hi Allen,
Thanks for your offer.
mock is enough. It doesn't matter what Fedora you run
I should mention, that you should enable the [local] configuration and replace the rawhide repo with f21-ruby repo.
... in theory, you can work just with koji, but it would be hard to debug the problems you might encounter.
You can start with rebuild of binary packages you own, for that case is everything easy (just don't forget to specify the target). If you'd like to rebuild packages you don't own but you care about, you can ask for permissions in pkgdb and see if you'll get approved. Otherwise, please update the .spec file and store the SRPM somewhere, where I can pick it up and rebuild using my povenpackager privileges.
HTH
Vít _______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
You can check the status using:
$ koji list-tagged f21-ruby
or at web:
http://koji.fedoraproject.org/koji/builds?inherited=0&tagID=266&orde...
Vít
Dne 9.4.2014 12:26, Vít Ondruch napsal(a):
Hi Rubyists,
Today, I have built Ruby 2.1 [1]! It is built in the f21-ruby side tag [2]. Now it is time for your action. Please check the updated Ruby guidelines [3] and start rebuilding packages using command:
fedpkg build --target=f21-ruby
For help with migration and build, you can use fermig [4]. Single file can be migrated by update.rb script [5]:
$ ~/projects/fermig/update.rb rubygem-foo.spec
This is the list of package which must be rebuild:
$ repoquery --disablerepo=* --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel'
But I'd like to encourage you to check all your packages, if they are compatible with Ruby 2.1 (for example yesterday, I had to update rubygem-introspection to be compatible with Ruby 2.1).
Also note the update of Minitest 4.x to Minitest 5.x which may cause some troubles.
Anyway, together with jstribny, we will go through every package and try to rebuild if you'll not be faster then us ;) Any help is appreciated as well as feedback.
Thanks
Vít
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=509933 [2] https://fedorahosted.org/rel-eng/ticket/5882 [3] https://fedorahosted.org/fpc/ticket/409 [4] https://github.com/voxik/fermig [5] https://github.com/voxik/fermig/blob/master/update.rb [6] https://lists.fedoraproject.org/pipermail/ruby-sig/2014-April/001534.html _______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
On 04/10/2014 02:55 PM, Vít Ondruch wrote:
You can check the status using:
$ koji list-tagged f21-ruby
or at web:
http://koji.fedoraproject.org/koji/builds?inherited=0&tagID=266&orde...
Thanks for this, I was just looking into koji commands :)
And actually I could mention again Josef's ehterpad. This could be helpful to prevent stepping on each others toes :)
http://piratepad.net/NWw7WqbvTb
Vít
Dne 10.4.2014 13:55, Vít Ondruch napsal(a):
You can check the status using:
$ koji list-tagged f21-ruby
or at web:
http://koji.fedoraproject.org/koji/builds?inherited=0&tagID=266&orde...
Vít
Dne 9.4.2014 12:26, Vít Ondruch napsal(a):
Hi Rubyists,
Today, I have built Ruby 2.1 [1]! It is built in the f21-ruby side tag [2]. Now it is time for your action. Please check the updated Ruby guidelines [3] and start rebuilding packages using command:
fedpkg build --target=f21-ruby
For help with migration and build, you can use fermig [4]. Single file can be migrated by update.rb script [5]:
$ ~/projects/fermig/update.rb rubygem-foo.spec
This is the list of package which must be rebuild:
$ repoquery --disablerepo=* --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel'
But I'd like to encourage you to check all your packages, if they are compatible with Ruby 2.1 (for example yesterday, I had to update rubygem-introspection to be compatible with Ruby 2.1).
Also note the update of Minitest 4.x to Minitest 5.x which may cause some troubles.
Anyway, together with jstribny, we will go through every package and try to rebuild if you'll not be faster then us ;) Any help is appreciated as well as feedback.
Thanks
Vít
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=509933 [2] https://fedorahosted.org/rel-eng/ticket/5882 [3] https://fedorahosted.org/fpc/ticket/409 [4] https://github.com/voxik/fermig [5] https://github.com/voxik/fermig/blob/master/update.rb [6] https://lists.fedoraproject.org/pipermail/ruby-sig/2014-April/001534.html
ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
On 04/09/2014 01:26 PM, Vít Ondruch wrote:
Hi Rubyists,
Today, I have built Ruby 2.1 [1]! It is built in the f21-ruby side tag [2]. Now it is time for your action. Please check the updated Ruby guidelines [3] and start rebuilding packages using command:
fedpkg build --target=f21-ruby
For help with migration and build, you can use fermig [4]. Single file can be migrated by update.rb script [5]:
$ ~/projects/fermig/update.rb rubygem-foo.spec
This is the list of package which must be rebuild:
$ repoquery --disablerepo=* --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel'
Just to make sure I understood the whole update thing correctly. All points below are for f21/rawhide only.
1. The new guidelines say that Requires/Provides should not be listed in spec. This is for ALL gems right? If so, shouldn't all gems be rebuilt? Not only those that require ruby-devel.
2. ruby 2.1 isn't yet in rawhide so we must use `--target=f21-ruby` when pushing an update. I'm not too familiar with koji tags, does that mean that koji uses a special repo where ruby2.1 is in? What about moving to rawhide repos, I mean will it be done automatically at some point?
3. When running a test suite of rubygems that require ruby-devel, we must from now on point to LOAD_PATH explicitly (-I%{buildroot}%{gem_extdir_mri}). gems with no C extensions should not require this, right?
Hope I didn't leave anything out :)
Dne 10.4.2014 14:39, Achilleas Pipinellis napsal(a):
On 04/09/2014 01:26 PM, Vít Ondruch wrote:
Hi Rubyists,
Today, I have built Ruby 2.1 [1]! It is built in the f21-ruby side tag [2]. Now it is time for your action. Please check the updated Ruby guidelines [3] and start rebuilding packages using command:
fedpkg build --target=f21-ruby
For help with migration and build, you can use fermig [4]. Single file can be migrated by update.rb script [5]:
$ ~/projects/fermig/update.rb rubygem-foo.spec
This is the list of package which must be rebuild:
$ repoquery --disablerepo=* --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel'
Just to make sure I understood the whole update thing correctly. All points below are for f21/rawhide only.
- The new guidelines say that Requires/Provides should not be listed in
spec. This is for ALL gems right? If so, shouldn't all gems be rebuilt? Not only those that require ruby-devel.
New guidelines are not retrospectively enforced, so it is not needed.
- ruby 2.1 isn't yet in rawhide so we must use `--target=f21-ruby` when
pushing an update. I'm not too familiar with koji tags, does that mean that koji uses a special repo where ruby2.1 is in? What about moving to rawhide repos, I mean will it be done automatically at some point?
Yes, you have to use the '--target' otherwise you'll be building against Rawhides Ruby. Once we rebuild everything (or most of the packages), the tag will get merged into the main rawhide tag by rel-engs.
- When running a test suite of rubygems that require ruby-devel, we
must from now on point to LOAD_PATH explicitly (-I%{buildroot}%{gem_extdir_mri}). gems with no C extensions should not require this, right?
Unfortunately, that is right. Or better
-I$(dirs +1)%{gem_extdir_mri}
since you are testing under %{_builddir}, not under %{buildroot}. But I am open for better suggestions. Actually, there would be possible to modify RubyGem's operating_system.rb to add this path on the $LOAD_PATH, but it would be too much magic in background, so I don't like the idea.
Vít
ruby-sig@lists.fedoraproject.org
-
Achilleas Pipinellis -
Allen Hewes -
Josef Stribny -
Vít Ondruch