On 25. 04. 19 18:38, Nico Kadel-Garcia wrote:
On Thu, Apr 25, 2019 at 10:27 AM Miro Hrončok mhroncok@redhat.com wrote:
On 25. 04. 19 9:22, Miroslav Suchý wrote:
Dne 24. 04. 19 v 23:04 Ben Cotton napsal(a):
Removed packages that would block the upgrades to Fedora 32 will be obsoleted from {{package|fedora-obsolete-packages}}.
Which effectively means all python2-* packages. Right?
Almost. The ones that stop requiring the automatic provides and get FESCo exception to use python27 won't be obsoleted.
Note that only "problematic on upgrade" packages should be obsoleted, but anything that would require python(abi) = 2.7 or similar jumps to this category, so yes, probably all of them.
(I've previously forgot to reply to the list.)
How much is going to be needed for "mock" to still work for older operating systems?
I'm confused. How is the change relevant for mock? I think I'm missing some pieces of the thought process here, could you please elaborate on that?
And for .spec files that may be backported to older Fedora or EPEL, do we want to have "with_python2" as a designated option to disable for Fedora > 31, but leave enabled for EPEL and older Fedora?
%bcond_with python2 https://docs.fedoraproject.org/en-US/packaging-guidelines/Python_Appendix/#_...
I realize it's work similar to that of using "with_python3" up until now, but I'm not convinced we can gracefully abandon that altogether.
Abandon what exactly? with_python3? That of course depends on what operating systems you want the package to be built and the amount of your dependencies and their availability on EPEL7 for example. Msot "normal" stuff should be EPEL7-python3 compatible, for example mock (since you've mentioned it):
https://src.fedoraproject.org/rpms/mock/pull-request/6