Bug 1585753 - dbus-c++-devel will not build for EPEL 7.
Summary: dbus-c++-devel will not build for EPEL 7.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: dbus-c++
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-04 15:44 UTC by Richard Grainger
Modified: 2024-07-09 02:23 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-09 02:23:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
rpm build log (1.94 MB, text/plain)
2018-06-04 15:44 UTC, Richard Grainger
no flags Details

Description Richard Grainger 2018-06-04 15:44:53 UTC
Created attachment 1447542 [details]
rpm build log

Description of problem:

Using RHEL 7.5/CentOS 7.5 (1804), dbus-c++-devel will not build using SRPM currently in EPEL.


Version-Release number of selected component (if applicable):

dbus-c++-0.5.0-0.16.20090203git13281b3.el7.src.rpm 

How reproducible:

Attempt to rebuild SRPM.

Steps to Reproduce:

1. Create a clean CentOS 7.5 (1804) RPM build environment with all build requirements installed and download src rpm to "RPMBUILD/SRPMS"
2. Run: rpmbuild --rebuild --define "_topdir $PWD/RPMBUILD" RPMBUILD/SRPMS/dbus-c++-0.5.0-0.16.20090203git13281b3.el7.src.rpm

Actual results:

A whole bunch of C++ errors (see attached log).

Expected results:

RPM rebuilds successfully.

Additional info:

Comment 1 Anssi Johansson 2018-06-07 18:00:16 UTC
EPEL's dbus-c++ was built in 2014. This package builds fine with CentOS 7.0.1406, which was released at around the same time.

Perhaps the dependencies have changed in the meantime, causing the build breakage.

Comment 2 Troy Dawson 2024-07-09 02:23:59 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.


Note You need to log in before you can comment on or make changes to this bug.