On Tue, Jun 4, 2019 at 3:26 AM Nico Kadel-Garcia <nkadel(a)gmail.com> wrote:
On Mon, Jun 3, 2019 at 10:51 AM Sérgio Basto <sergio(a)serjux.com> wrote:
>
> Hi,
> These removed python2 packages are breaking upgrade path
>
> 1- when you remove python2-foo , you should add to main package
> Obsoletes: python2-foo
If I may suggest, *absolutely not*. "Obsoletes: python2-foo"
specifically means that it includes and provides "python2-foo"
functionality, and "python3-foo" packages *do not* provide this. There
are a very few tools that put things in "/usr/bin" for typical use,
such as the "rpm" package itself which might benefit from such
options. But I think it's quite dangerous to replace them willy-nilly
due to compatibility for old packages which would have their
requirements replaced with something quite incompatible without
notification.
I think you misunderstand here. Obsoletes does not specifically
indicate it is equivalent. It is saying that you're replacing it. You
will still get a broken dep chain if something Requires something that
was obsoleted.
It is absolutely the correct strategy to do Obsoletes (without Provides) here.
--
真実はいつも一つ!/ Always, there's only one truth!