Bug 1451710 - 0001-Disable-python3-builds-on-pure-RHEL-7-without-EPEL-7.patch
Summary: 0001-Disable-python3-builds-on-pure-RHEL-7-without-EPEL-7.patch
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-pytest-runner
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Wright
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-17 10:48 UTC by Pavol Babinčák
Modified: 2024-07-09 02:06 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
Disable python3 builds on pure RHEL 7 without EPEL 7 (2.87 KB, patch)
2017-05-17 10:48 UTC, Pavol Babinčák
no flags Details | Diff

Description Pavol Babinčák 2017-05-17 10:48:31 UTC
Created attachment 1279645 [details]
Disable python3 builds on pure RHEL 7 without EPEL 7

Description of problem:
Package cannot be built in pure RHEL 7 without EPEL 7. Build environment there is missing python3 packages and couple of macros available in EPEL 7 only.

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

How reproducible:
Always

Steps to Reproduce:
1. run fedpkg local on RHEL 7 machine
2.
3.

Actual results:
Fails with Error: No Package found for python%{python3_pkgversion}-devel

Expected results:
Package built successfully at least for python2.


Additional info:

Comment 1 Fedora Admin user for bugzilla script actions 2023-04-26 00:33:15 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 2 Fedora Admin user for bugzilla script actions 2023-04-28 12:12:03 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 3 Troy Dawson 2024-07-09 02:06:49 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.