On 24. 04. 19 11:14, Martin Gansser wrote:
I see:
Obsoletes: python2-mlt < 6.12.0-8
Obsoletes: mlt-python < 6.12.0-8
%package -n python3-mlt
Obsoletes: %{name}-python2 < 6.12.0-8
I believe you should only obsolete from one place.
Had mlt-python2 ever existed?
mlt-python2 had existed in old f27 packages and was then renamed to python-mlt. I have
removed: Obsoletes: mlt-python <6.12.0-8
Note that the sections in the specfile are really weirdly sorted
(description > of python3 package is ebllow the devel package etc.).
I have sorted the package section
As a result, the python3 package can obsolete mlt-ruby if the package
is build
--without ruby.
what does that mean exactly?
Regards
Martin