Bug#849312: apt: dist-upgrade removes pkgs instead of upgrading them
2017-01-04 11:33 GMT+01:00 David Kalnischkies <david@kalnischkies.de>:
> On Tue, Jan 03, 2017 at 10:29:19AM +0100, Olaf van der Spek wrote:
>> 2016-12-25 13:12 GMT+01:00 David Kalnischkies <david@kalnischkies.de>:
>> >> Can't it detect mariadb-server-10.1 being a proper upgrade of
>> >> mariadb-server-10.0 and hence scoring this as neutral or positive?
>> >
>> > In general no, because that isn't a positive upgrade: It involves the
>>
>> 10.1 declares replaces on 10.0 doesn't it?
>> Doesn't apt use this information?
>
> It doesn't because the 'Replaces' is only there to tell dpkg that it is
> okay that this package overrides some files of another package. That
> frequently happens then a single package is split into a bunch (like
> foo, foo-data, foo-plugins-extra). It does also happen then two packages
In this case it'd be fine to use the info right?
> 'fight' over a particalur path in the filesystem and that fight was
> resolved: like in the git, chromium or node cases just to name a few big
> and popular ones. I somehow doubt you consider a spaceshooter an upgrade
> to a browser (or well, actually the other way around – which was the
> chromium case).
So exactly what are we trying to prevent here?
Apparently apt is already happy to propose the removal of packages..
> See Debian policy §7.6.1 for details. See also §7.6.2 – but don't get
> your hopes up in terms of upgrades: You wouldn't like apt to constantly
> flip between postfix and exim4 either…
Do exim and postfix declare Replaces on each other?
--
Olaf
Reply to: