On 01/19/2012 06:39 AM, Vít Ondruch wrote:
> Hi rubyists,
>
> yesterday evening, we finally obtained tag/target [1] for our Ruby 1.9.3 rebuild.
Following that, I immediately build Ruby 1.9.3 there and following with gems I own or
maintain. I would like to ask you to support me in this effort. I'd like to see to
majority of packages rebuild in this tag before F17 branch, which is 7th of February
according to Fedora 17 release schedule [2]. We would like to merge the target into the
f17 target right before the branch. After this milestone, we will need to do the rest,
however, Bodhi will slow us down.
>
> So here I'll try to list some tips how to proceed, although they are probably not
exhaustive and we will try to update the how to as we proceed.
>
>
> === Build ===
> $ fedpkg build --target=f17-ruby
>
> Please note that we are building with special target f17-ruby and that we are
building from master.
>
> === Updates needed for your package ===
> If you wonder what you should change in your package, it is very likely that you can
find updated .srpm in bkabrda's repository [3] as well as clone of original git repo
[4] if you prefer. There is also list of packages with potential issues [5].
>
> Please note that there was done mass rebuild in mean time, therefore the packages
needs to be updated. Pay special attention to release number. I am using currently
following procedure:
>
> 1) $ fedpkg co rubygem-foo
> 2) $ wget
http://bkabrda.fedorapeople.org/ruby-srpms/rubygem-foo-1.0-1.fc17.src.rpm
> 3) $ fedpkg import rubygem-foo-1.0-1.fc17.src.rpm
> 4) $ git reset HEAD rubygem-foo.spec
> 5) $ git checkout -p -- rubygem-foo.spec
> Note that you need this step to resurrect the changelog and revision changes due to
mass rebuild, but you can use also different methods if you like.
> 6) $ rpmdev-bumpspec rubygem-foo.spec
> 7) $ git commit -a
> 8) $ git push
> 9) $ fedpkg build --target=f17-ruby
Quick question, as these rpms get rebuilt / pushed, is there a repo we can point to
corresponding to the f17-ruby target? It would be alot easier to be able to pull updated
dependencies already built in via yum rather that having the manually install them in the
mock'd / local environment.
-Mo