On Wed, 2019-04-24 at 13:34 +0000, Martin Gansser wrote:
> > 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
These packages renames, which we use provides i.e. we rename mlt-python
to python2-mlt and we add Provides: mlt-python , give a lot of
confusions for example in dnf query --whatrequires, we may miss some
packages etc .
So IMO these "Provides" should be cleaned in next one or two releases
and all dependent packages should be adjust.
I.e. we shouldn't have any package requiring foo-python , they should
already require the correct name, python2-foo and python3-foo .
Thanks.
> > 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
> _______________________________________________
> devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
--
Sérgio M. B.
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]