Hi Erez, Erez Zilber wrote:
Thanks. I will try to use the rpm from Todd's build. BTW - if I want to create such a build on Fedora that will create el6 packages (e.g. git-220.127.116.11-2.el6.x86_64.rpm), what's the procedure?
Something like this (this is from memory): # Install fedpkg $ yum install fedpkg # Checkout the fedora git package (anonymously) $ fedpkg clone -a git && cd gitVerify the git tarball. This is optional, but I would be remiss to suggest you skip it. We used to include the tarball .asc file in the fedora git repo, but that is no longer available for download. Instead, it must be copied and pasted from Google Code (I'd love to see the .asc files return, FWIW).
# To verify the tarball, have fedpkg download the sources first -- if # you don't want to verify the tarball, you can skip this command and # the gpg/sha1sum commands that follow
$ fedpkg sources# Copy and paste the gpg signature from # http://code.google.com/p/git-core/downloads/detail?name=git-18.104.22.168.tar.gz&can=2&q= # to a local file and use gpg to verify it, then sha1sum to check the # tarballs
$ gpg --verify sha1.asc ... $ sha1sum -c sha1.asc # Create an el6 srpm $ fedpkg --dist el6 srpm# Build that package in mock, adding yourself or your build user to # the mock group first
$ sudo useradd -a -G mock $USER $ mock -r epel-6-x86_64 git-22.214.171.124-2.el6.src.rpmThe first time you build for a given release in mock will take longer than subsequent builds, because mock needs to download a lot of packages for the build root. These packages will be cached for future runs builds.
In the end, you should end up with a set of packages and build logs under /var/lib/mock/epel-6-x86_64/result/.
Hope this helps, -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
Description: PGP signature