Red Hat Bugzilla – Bug 1259883
Avoiding ifdefs in specs
Last modified: 2017-08-05 18:17:23 EDT
Description of problem:
From FPC discussion, we think the following would be helpful to avoid some %ifdef usage in specs:
diff --git a/macros.python3-pkgversion.epel b/macros.python3-pkgversion.epel
index d78af0c..7c2dfb9 100644
@@ -1,2 +1,6 @@
+# Set to /bin/true when not active to avoid %ifdefs in specfiles
diff --git a/macros.python3-pkgversion.fedora b/macros.python3-pkgversion.fedora
index ecf71b4..4bfe0e1 100644
@@ -1 +1,5 @@
+# Set to /bin/true to avoid %ifdefs in specfiles
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:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This is now in place with python-srpm-macros. I think we can now drop this package.
What's the story with this package in EPEL7? This fix has been made in git but never built. Without it, specs to build multiple python3 runtimes as described in https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3 don't work.
This package is obsolete - replaced by python-rpm-macros/python-srpm-macros. We have lots of python3 (python34) packages now in EPEL7 and coming to EPEL6, so the EPEL7 Python3 process is well underway.
I wonder then why Patrick Uiterwijk added it as a buildreq to python-crypto in EPEL-7 earlier today.
Does python-srpm-macros support the python3_other stuff too? I got a build failure when trying this out in a local EPEL-7 build.
(In reply to Paul Howarth from comment #7)
> I wonder then why Patrick Uiterwijk added it as a buildreq to python-crypto
> in EPEL-7 earlier today.
> Does python-srpm-macros support the python3_other stuff too? I got a build
> failure when trying this out in a local EPEL-7 build.
We don't yet support the python3_other stuff. Hopefully soon, but it also may change.
Where, if anywhere, is the python3_other stuff being tracked/discussed?
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.