Bug 1248040 - %python3_pkgversion not recognized?
Summary: %python3_pkgversion not recognized?
Alias: None
Product: Fedora
Classification: Fedora
Component: python3-pkgversion-macros
Version: 24
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Python Maintainers
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-07-29 13:32 UTC by Antonio
Modified: 2016-03-09 17:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-03-09 17:31:26 UTC

Attachments (Terms of Use)

Description Antonio 2015-07-29 13:32:48 UTC
Description of problem:
%python3_pkgversion macro is not recognized on F23/F24 (on koji builds).

See http://koji.fedoraproject.org/koji/getfile?taskID=10525890&name=root.log&offset=-4000

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

Comment 1 Orion Poplawski 2015-09-03 17:36:41 UTC
Has python3-pkgversion-macros not been added to the Fedora buildroots?

Comment 2 Robert Kuska 2015-09-04 07:19:11 UTC
It wasn't. As far as I know it is needed to have packaging guidelines for EPEL approved by FPC first.

There is some discussion at the end of the 2015/08/27 fpc meeting:

Comment 3 Matej Stuchlik 2015-09-07 09:15:15 UTC
To expand on that: Fedora relengs were not comfortable with adding a new package to buildroot at all, especially not when the guidelines were not yet approved by FESCO at that point.

Comment 4 Oliver Haessler 2015-12-04 09:50:31 UTC
so how do i use the %python3_pkgversion macro for builds that go to Fedora and EPEL? If i use:

BuildRequires:  python%{python3_pkgversion}-devel

it works on EPEL7 but on Fedora 24 I get:
Error: No Package found for python%{python3_pkgversion}-devel

I tried to include:
BuildRequires:  python3-pkgversion-macros

with no success.

Comment 6 Jan Kurik 2016-02-24 13:29:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:

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