@rjschwei, are you sure we don't want to provide python2-gflags in this package? I think it wouldn't hurt to keep that provides directive even if it's just for "compatibility" with RH, Arch and probably others...

So the Provides: Obsoletes: are only necessary because the package was renamed to reflect our naming policy. If you leave the file as is then the the python3 package will also provide python-gflags which then would create an install conflict between python2-python-gflags and python3-python-gflags.

Antonio Larrosa (alarrosa) - about 7 years ago

author source maintainer target maintainer

Not really, you can have a look at the Provides section in https://build.opensuse.org/package/binary/home:alarrosa:branches:devel:languages:python/python-python-gflags?arch=x86_64&filename=python2-python-gflags-3.1.1-29.1.noarch.rpm&repository=openSUSE_Tumbleweed and https://build.opensuse.org/package/binary/home:alarrosa:branches:devel:languages:python/python-python-gflags?arch=x86_64&filename=python3-python-gflags-3.1.1-29.1.noarch.rpm&repository=openSUSE_Tumbleweed

The singlespec macros modify the Provides/Obsoletes directives (as well as Requires) so they substitute the python prefix with python2/python3 depending on the package being generated. That way, python2-python-gflags provides: python-gflags = 3.1.1 python-python-gflags = 3.1.1-29.1 python2-gflags = 3.1.1
python2-python-gflags = 3.1.1-29.1

while python3-python-gflags provides: python3-gflags = 3.1.1
python3-python-gflags = 3.1.1-29.1