https://bugzilla.redhat.com/show_bug.cgi?id=1387873 --- Comment #13 from Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> --- (In reply to Michal Ambroz from comment #12) > BTW Zbysek please can you make your mind - is or is not that Provides > necessary? > I have removed it on your request, now you want it back in form of macro. I did not request %python_provide to be removed. Comment c#10 was the first place where I mentioned it. > Please note this will build only with python2 so in my opinion having there > just "Provides: python2-pyx" is the right thing. Using %python_provide is a > must only in case building for multiple pythons. We do not want to end-up > having there "Provides: python-pyx", because that would suggest python3, by > default in f25. The goal of having %python_provide is that *now* we get Provides:python-%{name} on all python2 binary packages, and at some point in the *future*, when we want python3 packages to be installed when you ask for python-%{name}, we can do that switch automatically, just by adjusting the definition of that macro and doing a mass rebuild. Having a single or multiple subpackages doesn't really matter here. That switch hasn't happened yet, and will never happen in F25. Currently, when you ask for python-%{name}, you should get python2 version (either python2-%{name} subpackage for the ones that did the rename, or python-%{name} subpackage for the rest). So, python2-pyx should have the (automatically generated) Provides:python-pyx tag. (In reply to Michal Ambroz from comment #11) > It looked much easier when José Matos <jamatos@xxxxxxxx> claimed in 1286341 : > > Michael if you want to submit this file for review I will approve it immediately. > > :D Yeah, it's taking longer than expected ;) As a consolation, look at the this way: after the initial build you're unlikely to ever touch the package again. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx