[Aptitude-devel] Bug#780028: init: aptitude upgrade from wheezy to jessie does not install systemd-sysv
david at kalnischkies.de
Sun Mar 8 21:04:05 GMT 2015
On Sun, Mar 08, 2015 at 07:35:37PM +0100, Axel Beckert wrote:
> Citing from the URL above:
> > apt-get update
> > apt-get -y upgrade
> > aptitude -y upgrade
> > apt-get -y dist-upgrade
> > aptitude -y dist-upgrade
> > apt-get -y autoremove
(I wondered about that as well…)
> Why in the world would someone use apt-get and aptitude alternately
> during a dist-upgrade? If you don't want to interfere with, you use
> apt-get (which should choose systemd-sysv) or you use aptitude because
> you want to interfere and interactively fine-tune aptitude's decisions
> anyway, so it shouldn't matter if aptitude chooses the one or the
> other because you're going to fine tune such stuff anyways.
I was speculating¹ that the sysvinit solution is preferred as it needs
less removes and Ansgar added that even then he eliminates the remove its
still the preferred solution, which gives the impression that less news
are preferred, while the fact that it is choosing a non-default or-group
member is ignored here (or at least less important).
Given that or-group order is a pretty common way of transporting default
choices I wonder if that is really a good idea.
Its kinda hard to imagine that there is even a single person left which
hasn't a set-in-stone opinion on init, but lets assume otherwise for
a minute anyway: Wouldn't such a person expect aptitude to give him our
new default overlord? I mean, aptitude makes it easy to explore other
solutions, but is that reason enough to make such an other solution the
first proposed solution?
(¹ on IRC as while I follow aptitude bugs, I don't really want to chirp
on them as as a non-user it isn't my business, but now that I am invited
via deity@ to comment I have a bit less qualms…)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: Digital signature
More information about the Aptitude-devel