Description of problem: The updated httpd rpm fails to build. Version-Release number of selected component (if applicable): 2.0.40-21.3 How reproducible: Very Steps to Reproduce: 1. Try rebuilding the httpd-2.0.40-21.3.src.rpm with 'rpmbuild --rebuild httpd-2.0.40-21.3.src.rpm' 2. 3. Actual results: Bad exit status from /var/tmp/rpm-tmp.52254 (%install) Expected results: Binary httpd rpm(s) Additional info: Also failed using 'rpmbuild --rebuild httpd-2.0.40-21.3.src.rpm --target i386'
+ install -m 644 /usr/src/redhat/SOURCES/httpd.conf /var/tmp/httpd-root/usr/etc/httpd/conf/httpd.conf + mkdir /var/tmp/httpd-root/usr/etc/httpd/conf/ssl.crl + mkdir /var/tmp/httpd-root/usr/etc/httpd/conf/ssl.crt + mkdir /var/tmp/httpd-root/usr/etc/httpd/conf/ssl.csr + mkdir /var/tmp/httpd-root/usr/etc/httpd/conf/ssl.key + mkdir /var/tmp/httpd-root/usr/etc/httpd/conf/ssl.prm + install -m 644 /usr/src/redhat/SOURCES/mod_ssl-Makefile.crt /var/tmp/httpd-root/usr/etc/httpd/conf/ssl.crt/Makefile.crt + install -m 644 /usr/src/redhat/SOURCES/mod_ssl-Makefile.crl /var/tmp/httpd-root/usr/etc/httpd/conf/ssl.crl/Makefile.crl + ln -s ../../../usr/share/ssl/certs/Makefile /var/tmp/httpd-root/etc/httpd/conf ln: creating symbolic link `/var/tmp/httpd-root/etc/httpd/conf' to `../../../usr/share/ssl/certs/Makefile': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.52254 (%install)
I couldn't reproduce this. Are you using a fully updated RHL9 installation?
It's been fully patched. I noticed that the httpd.spec file calls for $RPM_BUILD_ROOT (which I thought was deprecated), I don't have this variable set anywhere. Could that be the cause of the build problem?
What version of RPM are you using? RPM_BUILD_ROOT has been correctly expanded to /var/tmp/httpd-root in the output you give above. Are you running rpmbuild as root or as a user?
Thanks for the report. This is a mass bug update; since this release of Red Hat Linux is no longer supported, please either: a) try and reproduce the bug with a supported version of Red Hat Enterprise Linux or Fedora Core, and re-open this bug as appropriate after changing the Product field, or, b) if relevant, try and reproduce this bug using the current version of the upstream package, and report the bug upstream. c) report the bug to the Fedora Legacy project who may wish to continue maintenance of this package.