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.
Description of problem:
I would like to release a package to EPEL7 which depends on boost-python3 and boost-python3-devel as i did already for Fedora29.
However that package is not available on EPEL7 nor on RHEL7.
Would it be possible to include it either in RHEL7 or EPEL7?
thanks
regards
Andrea
There is no python3 package in RHEL 7, so it is impossible to add boost-python3 to RHEL 7.
If you need it in EPEL you'd have to add a new boost-python3 package yourself. It's an unusual case, because it wouldn't just be adding a new branch of the Fedora 'boost' package (as that would clash with the base RHEL 7 boost). You'd need a new EPEL-specific package that only builds boost-python3.
Comment 3Red Hat Bugzilla Rules Engine
2018-08-29 09:18:43 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
ok i see, since python34 is in EPEL7 i may try to add boost-python34 and boost-python34-devel then, would you be available to help and review the packages?
thanks
Andrea
ok thanks!
the spec file is cleaner now, but i still kept the 70 patches to apply, ( some of them related to python). Do you know if i can safely remove some of them?
Comment 10Robert-André Mauchin 🐧
2018-10-19 17:00:39 UTC
- Use %{python3_pkgversion} instead of hardcoded 34
- Not needed:
rm -rf $RPM_BUILD_ROOT
%clean
rm -rf $RPM_BUILD_ROOT
%defattr(-, root, root, -)
- License must be installed with %license, not %doc
- Add %ldconfig_scriptlets for the library
- This is not used by your package, I think you can remove it too
%ifnarch %{ix86} x86_64
# Avoid using Boost.Context on non-x86 arches. s390 is not
# supported at all and there were _syntax errors_ in PPC code. This
# should be enabled on a case-by-case basis as the arches are tested
# and fixed.
%bcond_with context
%else
%bcond_without context
%endif
Comment 11Robert-André Mauchin 🐧
2018-10-19 17:01:01 UTC