@rjschwei, should I remove also the existing Provides/Obsoletes here as you requested in https://build.opensuse.org/request/show/491278 ? Note that in this case, it's providing python-m2crypto which gets transformed to python2-m2crypto and the automatic provides will add python2-M2Crypto, so I think it makes sense here to keep both (python-m2crypto and %{oldpython}-m2crypto).
Thus when the Python3 package is built, it will provide and obsolete as stated, so will the Python2 package. Therefore the Python3 and Python2 package will conflict.
@rjschwei, should I remove also the existing Provides/Obsoletes here as you requested in https://build.opensuse.org/request/show/491278 ? Note that in this case, it's providing python-m2crypto which gets transformed to python2-m2crypto and the automatic provides will add python2-M2Crypto, so I think it makes sense here to keep both (python-m2crypto and %{oldpython}-m2crypto).
Nothing touches:
Provides: python-m2crypto = %{version} Obsoletes: python-m2crypto < %{version}
Thus when the Python3 package is built, it will provide and obsolete as stated, so will the Python2 package. Therefore the Python3 and Python2 package will conflict.
OK, this is not correct. Although not documented the macros do fiddle with Provides: and Obsoletes: directives. Thus no conflict is generated.