Build CentOS RPM for current git release, unsuccessful rebuild with alternate prefix2019 Community Moderator Electionhow to patch PKGBUILD to lib32Centos 7 boot up with custom kernel problemInstalling Docker on CentOSCentOS 7 Install: Error populating transactionCentOS 7 Custom Install: Error populating transactionstartx fails fedora 23How do you use rpmbuild to make an rpm package when there are file not found or permission errors?./configure cannot find GCC but whereis is able to?Issue with elrepo-kernel: packages are not availableFedora 29 VirtualBox possible conflict
How do I color the graph in datavisualization?
How much character growth crosses the line into breaking the character
How did Rebekah know that Esau was planning to kill his brother in Genesis 27:42?
Which one is correct as adjective “protruding” or “protruded”?
What are the purposes of autoencoders?
Is aluminum electrical wire used on aircraft?
dpdt switch to spst switch
The screen of my macbook suddenly broken down how can I do to recover
If infinitesimal transformations commute why dont the generators of the Lorentz group commute?
Problem with TransformedDistribution
Why should universal income be universal?
Rising and falling intonation
Creepy dinosaur pc game identification
What does chmod -u do?
height map for normal input sharp edges
How to indicate a cut out for a product window
What is the evidence for the "tyranny of the majority problem" in a direct democracy context?
Symbol used to indicate indivisibility
Multiplicative persistence
Why electric field inside a cavity of a non-conducting sphere not zero?
Has any country ever had 2 former presidents in jail simultaneously?
What percentage of fillings performed today are done with mercury amalgam?
It grows, but water kills it
How do you make your own symbol when Detexify fails?
Build CentOS RPM for current git release, unsuccessful rebuild with alternate prefix
2019 Community Moderator Electionhow to patch PKGBUILD to lib32Centos 7 boot up with custom kernel problemInstalling Docker on CentOSCentOS 7 Install: Error populating transactionCentOS 7 Custom Install: Error populating transactionstartx fails fedora 23How do you use rpmbuild to make an rpm package when there are file not found or permission errors?./configure cannot find GCC but whereis is able to?Issue with elrepo-kernel: packages are not availableFedora 29 VirtualBox possible conflict
I am stuck in an effort to provide an maintain an up-to-date git release for a collection of CentOS Linux servers. I was hoping to be able to create binary RPMs that I could just have published to a local yum mirror - in order to simply installs, and to easily keep everything up-to-date as part of regular maintenance along with the rest of the OS.
It is a common recommendation to simply install the git binaries from the OS's package manager (yum). However, even under the latest CentOS / RHEL 7, the latest provided packages are stuck at a relatively ancient 1.8.3.1 - compared to the latest 2.7.1. It seems that RPMForge used to provide some updated git packages, but not since EL 6. So it seems that building from source is really the only remaining option here - but using a custom RPM package here to maintain this would be a good idea.
- References:
- https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
- https://stackoverflow.com/questions/21820715/how-to-install-latest-version-of-git-on-centos-6-x-7-x
- https://stackoverflow.com/questions/28365026/update-to-latest-git-version-2-2-x-in-centos
- https://www.digitalocean.com/community/tutorials/how-to-install-git-on-centos-7
- https://serverfault.com/questions/709433/install-a-newer-version-of-git-on-centos-7
It looks like using Fedora's "mock" for RPM packaging will be the best way of handling this. It seems that the worst of this would be obtaining / creating / maintaining a SPEC file. Fortunately, it seems that Fedora Rawhide will be invaluable for this - as available at https://rpmfind.net/linux/RPM/fedora/devel/rawhide/src/g/git-2.7.0-1.fc24.src.html .
I had success doing a simple rebuild from the SRPM:
$ mock -r epel-7-x86_64 rebuild /tmp/git-2.7.0-1.fc24.src.rpm
However, installation fails due to many conflicts from the existing OS-provided git installation. I wouldn't want to remove / replace the OS-provided versions anyway, at risk of running into compatibility or dependency issues down the road with other OS-provided packages that may expect the older git version. I'd prefer a custom RPM that uses a /usr/local prefix.
Using rpm -qpi against any of native RPMs report that they are (not relocatable) - meaning I can't run rpm with a --prefix flag to install in such an alternate location. However, I don't believe I'd want to depend upon using this anyway, as it would complicate being able to run default installs from yum. I would think that this could be easily customized into the source RPM build, so that the resulting RPMs don't conflict.
I thought this would be as simple as defining an alternate value for the _prefix macro in the SPEC file, as such:
$ mock -r epel-7-x86_64 -D "_prefix /usr/local" rebuild /tmp/git-2.7.0-1.fc24.src.rpm
This looked like it was progressing nicely, until it failed spectacularly - ending with the following errors:
+ sed -e 's@^/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64@@'
find: '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl': No such file or directory
+ find /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl -mindepth 1 -type d
+ sed -e 's@^/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64@%dir @'
find: '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl': No such file or directory
+ grep Git/SVN perl-git-files
error: Bad exit status from /var/tmp/rpm-tmp.sw2Kfy (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.sw2Kfy (%install)
ERROR: Exception(/tmp/git-2.7.0-1.fc24.src.rpm) Config(epel-7-x86_64) 2 minutes 39 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
# bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/git.spec
Alternatively, if I first extract the SPECS and SOURCES, change prefix to /usr/local (from %_prefix) in SPECS/git.spec, then rebuild, things still fail - but at a different spot:
+ install -pm 644 contrib/emacs/git.el /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/emacs/site-lisp/git
+ install -Dpm 644 /builddir/build/SOURCES/git-init.el /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/emacs/site-lisp/site-start.d/git-init.el
+ install -pm 755 contrib/credential/gnome-keyring/git-credential-gnome-keyring /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/libexec/git-core
install: cannot create regular file '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/libexec/git-core': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.CJFTef (%install)
Bad exit status from /var/tmp/rpm-tmp.CJFTef (%install)
RPM build errors:
ERROR: Exception(git-build/2/git-2.7.0-1.el7.centos.src.rpm) Config(epel-7-x86_64) 1 minutes 37 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
# bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/git.spec
(I'm guessing the former attempt with defining the _prefix macro was closer to success than forcefully changing prefix in the SPEC file - as there may now be other usages of _prefix that are still using the default value.)
- References:
- https://fedoraproject.org/wiki/How_to_create_an_RPM_package
- https://wiki.centos.org/HowTos/SetupRpmBuildEnvironment
- https://wiki.centos.org/HowTos/RebuildSRPM
http://www.thegeekstuff.com/2015/02/rpm-build-package-example/- (Disqualified, builds source RPMs as root!)
- http://blog.packagecloud.io/eng/2015/05/11/building-rpm-packages-with-mock/
I'm not exactly sure how to proceed. Is there a different way I should be specifying an alternate installation prefix, or is there something else I can try?
centos fedora package-management rpm git
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am stuck in an effort to provide an maintain an up-to-date git release for a collection of CentOS Linux servers. I was hoping to be able to create binary RPMs that I could just have published to a local yum mirror - in order to simply installs, and to easily keep everything up-to-date as part of regular maintenance along with the rest of the OS.
It is a common recommendation to simply install the git binaries from the OS's package manager (yum). However, even under the latest CentOS / RHEL 7, the latest provided packages are stuck at a relatively ancient 1.8.3.1 - compared to the latest 2.7.1. It seems that RPMForge used to provide some updated git packages, but not since EL 6. So it seems that building from source is really the only remaining option here - but using a custom RPM package here to maintain this would be a good idea.
- References:
- https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
- https://stackoverflow.com/questions/21820715/how-to-install-latest-version-of-git-on-centos-6-x-7-x
- https://stackoverflow.com/questions/28365026/update-to-latest-git-version-2-2-x-in-centos
- https://www.digitalocean.com/community/tutorials/how-to-install-git-on-centos-7
- https://serverfault.com/questions/709433/install-a-newer-version-of-git-on-centos-7
It looks like using Fedora's "mock" for RPM packaging will be the best way of handling this. It seems that the worst of this would be obtaining / creating / maintaining a SPEC file. Fortunately, it seems that Fedora Rawhide will be invaluable for this - as available at https://rpmfind.net/linux/RPM/fedora/devel/rawhide/src/g/git-2.7.0-1.fc24.src.html .
I had success doing a simple rebuild from the SRPM:
$ mock -r epel-7-x86_64 rebuild /tmp/git-2.7.0-1.fc24.src.rpm
However, installation fails due to many conflicts from the existing OS-provided git installation. I wouldn't want to remove / replace the OS-provided versions anyway, at risk of running into compatibility or dependency issues down the road with other OS-provided packages that may expect the older git version. I'd prefer a custom RPM that uses a /usr/local prefix.
Using rpm -qpi against any of native RPMs report that they are (not relocatable) - meaning I can't run rpm with a --prefix flag to install in such an alternate location. However, I don't believe I'd want to depend upon using this anyway, as it would complicate being able to run default installs from yum. I would think that this could be easily customized into the source RPM build, so that the resulting RPMs don't conflict.
I thought this would be as simple as defining an alternate value for the _prefix macro in the SPEC file, as such:
$ mock -r epel-7-x86_64 -D "_prefix /usr/local" rebuild /tmp/git-2.7.0-1.fc24.src.rpm
This looked like it was progressing nicely, until it failed spectacularly - ending with the following errors:
+ sed -e 's@^/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64@@'
find: '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl': No such file or directory
+ find /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl -mindepth 1 -type d
+ sed -e 's@^/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64@%dir @'
find: '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl': No such file or directory
+ grep Git/SVN perl-git-files
error: Bad exit status from /var/tmp/rpm-tmp.sw2Kfy (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.sw2Kfy (%install)
ERROR: Exception(/tmp/git-2.7.0-1.fc24.src.rpm) Config(epel-7-x86_64) 2 minutes 39 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
# bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/git.spec
Alternatively, if I first extract the SPECS and SOURCES, change prefix to /usr/local (from %_prefix) in SPECS/git.spec, then rebuild, things still fail - but at a different spot:
+ install -pm 644 contrib/emacs/git.el /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/emacs/site-lisp/git
+ install -Dpm 644 /builddir/build/SOURCES/git-init.el /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/emacs/site-lisp/site-start.d/git-init.el
+ install -pm 755 contrib/credential/gnome-keyring/git-credential-gnome-keyring /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/libexec/git-core
install: cannot create regular file '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/libexec/git-core': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.CJFTef (%install)
Bad exit status from /var/tmp/rpm-tmp.CJFTef (%install)
RPM build errors:
ERROR: Exception(git-build/2/git-2.7.0-1.el7.centos.src.rpm) Config(epel-7-x86_64) 1 minutes 37 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
# bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/git.spec
(I'm guessing the former attempt with defining the _prefix macro was closer to success than forcefully changing prefix in the SPEC file - as there may now be other usages of _prefix that are still using the default value.)
- References:
- https://fedoraproject.org/wiki/How_to_create_an_RPM_package
- https://wiki.centos.org/HowTos/SetupRpmBuildEnvironment
- https://wiki.centos.org/HowTos/RebuildSRPM
http://www.thegeekstuff.com/2015/02/rpm-build-package-example/- (Disqualified, builds source RPMs as root!)
- http://blog.packagecloud.io/eng/2015/05/11/building-rpm-packages-with-mock/
I'm not exactly sure how to proceed. Is there a different way I should be specifying an alternate installation prefix, or is there something else I can try?
centos fedora package-management rpm git
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am stuck in an effort to provide an maintain an up-to-date git release for a collection of CentOS Linux servers. I was hoping to be able to create binary RPMs that I could just have published to a local yum mirror - in order to simply installs, and to easily keep everything up-to-date as part of regular maintenance along with the rest of the OS.
It is a common recommendation to simply install the git binaries from the OS's package manager (yum). However, even under the latest CentOS / RHEL 7, the latest provided packages are stuck at a relatively ancient 1.8.3.1 - compared to the latest 2.7.1. It seems that RPMForge used to provide some updated git packages, but not since EL 6. So it seems that building from source is really the only remaining option here - but using a custom RPM package here to maintain this would be a good idea.
- References:
- https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
- https://stackoverflow.com/questions/21820715/how-to-install-latest-version-of-git-on-centos-6-x-7-x
- https://stackoverflow.com/questions/28365026/update-to-latest-git-version-2-2-x-in-centos
- https://www.digitalocean.com/community/tutorials/how-to-install-git-on-centos-7
- https://serverfault.com/questions/709433/install-a-newer-version-of-git-on-centos-7
It looks like using Fedora's "mock" for RPM packaging will be the best way of handling this. It seems that the worst of this would be obtaining / creating / maintaining a SPEC file. Fortunately, it seems that Fedora Rawhide will be invaluable for this - as available at https://rpmfind.net/linux/RPM/fedora/devel/rawhide/src/g/git-2.7.0-1.fc24.src.html .
I had success doing a simple rebuild from the SRPM:
$ mock -r epel-7-x86_64 rebuild /tmp/git-2.7.0-1.fc24.src.rpm
However, installation fails due to many conflicts from the existing OS-provided git installation. I wouldn't want to remove / replace the OS-provided versions anyway, at risk of running into compatibility or dependency issues down the road with other OS-provided packages that may expect the older git version. I'd prefer a custom RPM that uses a /usr/local prefix.
Using rpm -qpi against any of native RPMs report that they are (not relocatable) - meaning I can't run rpm with a --prefix flag to install in such an alternate location. However, I don't believe I'd want to depend upon using this anyway, as it would complicate being able to run default installs from yum. I would think that this could be easily customized into the source RPM build, so that the resulting RPMs don't conflict.
I thought this would be as simple as defining an alternate value for the _prefix macro in the SPEC file, as such:
$ mock -r epel-7-x86_64 -D "_prefix /usr/local" rebuild /tmp/git-2.7.0-1.fc24.src.rpm
This looked like it was progressing nicely, until it failed spectacularly - ending with the following errors:
+ sed -e 's@^/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64@@'
find: '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl': No such file or directory
+ find /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl -mindepth 1 -type d
+ sed -e 's@^/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64@%dir @'
find: '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl': No such file or directory
+ grep Git/SVN perl-git-files
error: Bad exit status from /var/tmp/rpm-tmp.sw2Kfy (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.sw2Kfy (%install)
ERROR: Exception(/tmp/git-2.7.0-1.fc24.src.rpm) Config(epel-7-x86_64) 2 minutes 39 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
# bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/git.spec
Alternatively, if I first extract the SPECS and SOURCES, change prefix to /usr/local (from %_prefix) in SPECS/git.spec, then rebuild, things still fail - but at a different spot:
+ install -pm 644 contrib/emacs/git.el /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/emacs/site-lisp/git
+ install -Dpm 644 /builddir/build/SOURCES/git-init.el /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/emacs/site-lisp/site-start.d/git-init.el
+ install -pm 755 contrib/credential/gnome-keyring/git-credential-gnome-keyring /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/libexec/git-core
install: cannot create regular file '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/libexec/git-core': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.CJFTef (%install)
Bad exit status from /var/tmp/rpm-tmp.CJFTef (%install)
RPM build errors:
ERROR: Exception(git-build/2/git-2.7.0-1.el7.centos.src.rpm) Config(epel-7-x86_64) 1 minutes 37 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
# bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/git.spec
(I'm guessing the former attempt with defining the _prefix macro was closer to success than forcefully changing prefix in the SPEC file - as there may now be other usages of _prefix that are still using the default value.)
- References:
- https://fedoraproject.org/wiki/How_to_create_an_RPM_package
- https://wiki.centos.org/HowTos/SetupRpmBuildEnvironment
- https://wiki.centos.org/HowTos/RebuildSRPM
http://www.thegeekstuff.com/2015/02/rpm-build-package-example/- (Disqualified, builds source RPMs as root!)
- http://blog.packagecloud.io/eng/2015/05/11/building-rpm-packages-with-mock/
I'm not exactly sure how to proceed. Is there a different way I should be specifying an alternate installation prefix, or is there something else I can try?
centos fedora package-management rpm git
I am stuck in an effort to provide an maintain an up-to-date git release for a collection of CentOS Linux servers. I was hoping to be able to create binary RPMs that I could just have published to a local yum mirror - in order to simply installs, and to easily keep everything up-to-date as part of regular maintenance along with the rest of the OS.
It is a common recommendation to simply install the git binaries from the OS's package manager (yum). However, even under the latest CentOS / RHEL 7, the latest provided packages are stuck at a relatively ancient 1.8.3.1 - compared to the latest 2.7.1. It seems that RPMForge used to provide some updated git packages, but not since EL 6. So it seems that building from source is really the only remaining option here - but using a custom RPM package here to maintain this would be a good idea.
- References:
- https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
- https://stackoverflow.com/questions/21820715/how-to-install-latest-version-of-git-on-centos-6-x-7-x
- https://stackoverflow.com/questions/28365026/update-to-latest-git-version-2-2-x-in-centos
- https://www.digitalocean.com/community/tutorials/how-to-install-git-on-centos-7
- https://serverfault.com/questions/709433/install-a-newer-version-of-git-on-centos-7
It looks like using Fedora's "mock" for RPM packaging will be the best way of handling this. It seems that the worst of this would be obtaining / creating / maintaining a SPEC file. Fortunately, it seems that Fedora Rawhide will be invaluable for this - as available at https://rpmfind.net/linux/RPM/fedora/devel/rawhide/src/g/git-2.7.0-1.fc24.src.html .
I had success doing a simple rebuild from the SRPM:
$ mock -r epel-7-x86_64 rebuild /tmp/git-2.7.0-1.fc24.src.rpm
However, installation fails due to many conflicts from the existing OS-provided git installation. I wouldn't want to remove / replace the OS-provided versions anyway, at risk of running into compatibility or dependency issues down the road with other OS-provided packages that may expect the older git version. I'd prefer a custom RPM that uses a /usr/local prefix.
Using rpm -qpi against any of native RPMs report that they are (not relocatable) - meaning I can't run rpm with a --prefix flag to install in such an alternate location. However, I don't believe I'd want to depend upon using this anyway, as it would complicate being able to run default installs from yum. I would think that this could be easily customized into the source RPM build, so that the resulting RPMs don't conflict.
I thought this would be as simple as defining an alternate value for the _prefix macro in the SPEC file, as such:
$ mock -r epel-7-x86_64 -D "_prefix /usr/local" rebuild /tmp/git-2.7.0-1.fc24.src.rpm
This looked like it was progressing nicely, until it failed spectacularly - ending with the following errors:
+ sed -e 's@^/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64@@'
find: '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl': No such file or directory
+ find /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl -mindepth 1 -type d
+ sed -e 's@^/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64@%dir @'
find: '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/perl5/vendor_perl': No such file or directory
+ grep Git/SVN perl-git-files
error: Bad exit status from /var/tmp/rpm-tmp.sw2Kfy (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.sw2Kfy (%install)
ERROR: Exception(/tmp/git-2.7.0-1.fc24.src.rpm) Config(epel-7-x86_64) 2 minutes 39 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
# bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/git.spec
Alternatively, if I first extract the SPECS and SOURCES, change prefix to /usr/local (from %_prefix) in SPECS/git.spec, then rebuild, things still fail - but at a different spot:
+ install -pm 644 contrib/emacs/git.el /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/emacs/site-lisp/git
+ install -Dpm 644 /builddir/build/SOURCES/git-init.el /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/share/emacs/site-lisp/site-start.d/git-init.el
+ install -pm 755 contrib/credential/gnome-keyring/git-credential-gnome-keyring /builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/libexec/git-core
install: cannot create regular file '/builddir/build/BUILDROOT/git-2.7.0-1.el7.centos.x86_64/usr/libexec/git-core': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.CJFTef (%install)
Bad exit status from /var/tmp/rpm-tmp.CJFTef (%install)
RPM build errors:
ERROR: Exception(git-build/2/git-2.7.0-1.el7.centos.src.rpm) Config(epel-7-x86_64) 1 minutes 37 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed. See logs for output.
# bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/git.spec
(I'm guessing the former attempt with defining the _prefix macro was closer to success than forcefully changing prefix in the SPEC file - as there may now be other usages of _prefix that are still using the default value.)
- References:
- https://fedoraproject.org/wiki/How_to_create_an_RPM_package
- https://wiki.centos.org/HowTos/SetupRpmBuildEnvironment
- https://wiki.centos.org/HowTos/RebuildSRPM
http://www.thegeekstuff.com/2015/02/rpm-build-package-example/- (Disqualified, builds source RPMs as root!)
- http://blog.packagecloud.io/eng/2015/05/11/building-rpm-packages-with-mock/
I'm not exactly sure how to proceed. Is there a different way I should be specifying an alternate installation prefix, or is there something else I can try?
centos fedora package-management rpm git
centos fedora package-management rpm git
edited May 23 '17 at 12:40
Community♦
1
1
asked Feb 7 '16 at 1:35
ziesemerziesemer
19618
19618
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I found some guys git repo who had SRPM for git 2.7.2
If that is new enough for you.
I successfully build that on Centos 6.
https://github.com/nkadel/git27-srpm
It creates all the packages and dependencies for me, and I was able to add it to my private repo to install git.
I'm guessing from the changelogs on 2.9.3 that you could just bump the version number in the spec file to get 2.9.3. (latest version at time of this writing)
Thanks. I was able to build under CentOS 7 "as-is", but again - I seem to be unable to successfully set a/usr/localprefix (with repeated concerns of replacing the OS-provided versions, running into compatibility or dependency issues down the road with other OS-provided packages, etc.)
– ziesemer
Aug 21 '16 at 18:37
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f260465%2fbuild-centos-rpm-for-current-git-release-unsuccessful-rebuild-with-alternate-pr%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found some guys git repo who had SRPM for git 2.7.2
If that is new enough for you.
I successfully build that on Centos 6.
https://github.com/nkadel/git27-srpm
It creates all the packages and dependencies for me, and I was able to add it to my private repo to install git.
I'm guessing from the changelogs on 2.9.3 that you could just bump the version number in the spec file to get 2.9.3. (latest version at time of this writing)
Thanks. I was able to build under CentOS 7 "as-is", but again - I seem to be unable to successfully set a/usr/localprefix (with repeated concerns of replacing the OS-provided versions, running into compatibility or dependency issues down the road with other OS-provided packages, etc.)
– ziesemer
Aug 21 '16 at 18:37
add a comment |
I found some guys git repo who had SRPM for git 2.7.2
If that is new enough for you.
I successfully build that on Centos 6.
https://github.com/nkadel/git27-srpm
It creates all the packages and dependencies for me, and I was able to add it to my private repo to install git.
I'm guessing from the changelogs on 2.9.3 that you could just bump the version number in the spec file to get 2.9.3. (latest version at time of this writing)
Thanks. I was able to build under CentOS 7 "as-is", but again - I seem to be unable to successfully set a/usr/localprefix (with repeated concerns of replacing the OS-provided versions, running into compatibility or dependency issues down the road with other OS-provided packages, etc.)
– ziesemer
Aug 21 '16 at 18:37
add a comment |
I found some guys git repo who had SRPM for git 2.7.2
If that is new enough for you.
I successfully build that on Centos 6.
https://github.com/nkadel/git27-srpm
It creates all the packages and dependencies for me, and I was able to add it to my private repo to install git.
I'm guessing from the changelogs on 2.9.3 that you could just bump the version number in the spec file to get 2.9.3. (latest version at time of this writing)
I found some guys git repo who had SRPM for git 2.7.2
If that is new enough for you.
I successfully build that on Centos 6.
https://github.com/nkadel/git27-srpm
It creates all the packages and dependencies for me, and I was able to add it to my private repo to install git.
I'm guessing from the changelogs on 2.9.3 that you could just bump the version number in the spec file to get 2.9.3. (latest version at time of this writing)
answered Aug 19 '16 at 11:50
Alex RAlex R
1012
1012
Thanks. I was able to build under CentOS 7 "as-is", but again - I seem to be unable to successfully set a/usr/localprefix (with repeated concerns of replacing the OS-provided versions, running into compatibility or dependency issues down the road with other OS-provided packages, etc.)
– ziesemer
Aug 21 '16 at 18:37
add a comment |
Thanks. I was able to build under CentOS 7 "as-is", but again - I seem to be unable to successfully set a/usr/localprefix (with repeated concerns of replacing the OS-provided versions, running into compatibility or dependency issues down the road with other OS-provided packages, etc.)
– ziesemer
Aug 21 '16 at 18:37
Thanks. I was able to build under CentOS 7 "as-is", but again - I seem to be unable to successfully set a
/usr/local prefix (with repeated concerns of replacing the OS-provided versions, running into compatibility or dependency issues down the road with other OS-provided packages, etc.)– ziesemer
Aug 21 '16 at 18:37
Thanks. I was able to build under CentOS 7 "as-is", but again - I seem to be unable to successfully set a
/usr/local prefix (with repeated concerns of replacing the OS-provided versions, running into compatibility or dependency issues down the road with other OS-provided packages, etc.)– ziesemer
Aug 21 '16 at 18:37
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f260465%2fbuild-centos-rpm-for-current-git-release-unsuccessful-rebuild-with-alternate-pr%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown