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,
> 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  or  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
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.
I don't know what pkgdb is.
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?
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
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 :)