Re: Bug#709758: Replacing a binary package by another one(was: Communication issue?)
On Thu, Sep 5, 2013 at 11:34 PM, Philipp Kern <firstname.lastname@example.org> wrote:
> On 2013-09-05 11:15, David Kalnischkies wrote:
> [ Provides/Replaces up thread ]
>> The policy defines two uses of Replaces:
>> So my simple question is, which combination of relations should that
>> be that tells a smart package manager to upgrade pkgA to pkgB ?
> What about pkgB replacing and providing pkgA?
Because its usually an error to just replace a package without
breaking/conflicting against it in which case it looks suspiciously
like 7.6.2 – also just take the examples I mentioned and think
about what happens:
For example, you made mplayer2 now an upgrade for mplayer.
I am not sure that is what their maintainers/upstreams intend.
(maybe it is, but I am not keen on letting foo2/foo-ng maintainer
decide what is a good upgrade path for foo – that should really
be decided by foo maintainer).