#50130 Building RPMs on RHEL8 fails
Closed: wontfix 3 years ago by spichugi. Opened 3 years ago by mmuehlfeldrh.

Issue Description

Building the RPMs on RHEL8 beta fails.

Package Version and Platform

git master

Steps to reproduce

  1. make -f rpm.mk rpms

Actual results

...
+ mv -f /usr/src/389-ds-base/rpmbuild/BUILDROOT/389-ds-base-1.4.0.20-20190108gitf574332fc.el8.x86_64/usr/share/cockpit/389-console/src/rhds-banner.html /usr/src/389-ds-base/rpmbuild/BUILDROOT/389-ds-base-1.4.0.20-20190108gitf574332fc.el8.x86_64/usr/share/cockpit/389-console/src/banner.html
mv: cannot stat '/usr/src/389-ds-base/rpmbuild/BUILDROOT/389-ds-base-1.4.0.20-20190108gitf574332fc.el8.x86_64/usr/share/cockpit/389-console/src/rhds-banner.html': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.CZw2KO (%install)

Expected results

Building RPMs should succeed.

Additional information

To fix the problem, change line 412 in rpm/389-ds-base.spec.in from

mv -f %{buildroot}%{_datadir}/cockpit/389-console/src/rhds-banner.html %{buildroot}%{_datadir}/cockpit/389-console/src/banner.html

to

mv -f %{buildroot}%{_datadir}/cockpit/389-console/rhds-banner.html %{buildroot}%{_datadir}/cockpit/389-console/banner.html

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue assigned to mmuehlfeldrh
- Issue set to the milestone: 1.4.0

3 years ago

@mreynolds I feel like this is an internal rh issue? I'd assume you would have resolved this already too?

Metadata Update from @spichugi:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3189

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

2 years ago

Login to comment on this ticket.

Metadata