Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Some tests contained in the Subversion source code failed if executed as root. Consequently, the source RPM for the subversion package could be rebuilt only by non-root users. With this update, the tests which fail as root are disabled if running as root. As a result, the subversion source RPM can be rebuilt by both non-root or root users.
Description of problem:
The subversion testsuite which is being run during rebuild fails if the package is being rebuilt by the root user.
The testsuite should either be fixed or rebuild as root discouraged and the testsuite problem workarounded.
Version-Release number of selected component (if applicable):
subversion-1.7.14-1.el7.src.rpm
How reproducible:
always
Steps to Reproduce:
1. su -
2. yumdownloader --source subversion
3. (install the missing dependencies)
4. rpmbuild --rebuild subversion*src.rpm
Actual results:
There was 1 failure:
1) testBasicLocking(org.apache.subversion.javahl.BasicTests)junit.framework.AssertionFailedError: file should be read only now expected:<false> but was:<true>
at org.apache.subversion.javahl.BasicTests.testBasicLocking(BasicTests.java:2027)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.apache.subversion.javahl.RunTests.main(RunTests.java:116)
FAILURES!!!
Tests run: 54, Failures: 1, Errors: 0
make: *** [check-javahl] Error 1
Expected results:
the build fails more gracefully and suggests a way to workaround (to disable the tests)
Additional info:
for example, the mariadb spec has this:
# fail quickly and obviously if user tries to build as root
%if %runselftest
if [ x"`id -u`" = x0 ]; then
echo "The mariadb's regression tests may fail if run as root."
echo "If you really need to build the RPM as root, use"
echo "--define='runselftest 0' to skip the regression tests."
exit 1
fi
%endif
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2425.html
Description of problem: The subversion testsuite which is being run during rebuild fails if the package is being rebuilt by the root user. The testsuite should either be fixed or rebuild as root discouraged and the testsuite problem workarounded. Version-Release number of selected component (if applicable): subversion-1.7.14-1.el7.src.rpm How reproducible: always Steps to Reproduce: 1. su - 2. yumdownloader --source subversion 3. (install the missing dependencies) 4. rpmbuild --rebuild subversion*src.rpm Actual results: There was 1 failure: 1) testBasicLocking(org.apache.subversion.javahl.BasicTests)junit.framework.AssertionFailedError: file should be read only now expected:<false> but was:<true> at org.apache.subversion.javahl.BasicTests.testBasicLocking(BasicTests.java:2027) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at org.apache.subversion.javahl.RunTests.main(RunTests.java:116) FAILURES!!! Tests run: 54, Failures: 1, Errors: 0 make: *** [check-javahl] Error 1 Expected results: the build fails more gracefully and suggests a way to workaround (to disable the tests) Additional info: for example, the mariadb spec has this: # fail quickly and obviously if user tries to build as root %if %runselftest if [ x"`id -u`" = x0 ]; then echo "The mariadb's regression tests may fail if run as root." echo "If you really need to build the RPM as root, use" echo "--define='runselftest 0' to skip the regression tests." exit 1 fi %endif