On Sun, 2015-03-08 at 21:43 +0100, Michael Biebl wrote: > Did you deliberate add jessie entries instead of replacing the wheezy > entries? Does it change if you remove the wheezy entries?
I've always done it that way. Just s/wheezy/jessie/ instead of both gives sysvinit-core. > apt should properly install systemd-sysv on upgrades and afaik is the > recommended method. That is the case. > I don't see, how this is a bug in init and what we should do about this. > Can you elaborate why you filed this against init? I wasn't sure which package was the cause of it and where the fix should be. I probably should have filed it against the whole set of packages involved until the location for the fix is found. Please feel free to reassign as appropriate. > From my POV, this should either be reassigned to aptitude (maybe they > can do something about this) or to release-notes, documenting that > aptitude should not be used on dist-upgrades in the way you did. The issue doesn't happen with aptitude dist-upgrade, it only happens with aptitude upgrade. > Is "aptitude upgrade" actually supposed to be used on dist-upgrades? Whether or not one should use aptitude flips around between releases so I believe people will be using it whether or not we recommend it for a particular release. > Again, from my POV the best we can do is to document in the release > notes how to do a proper dist upgrade (and how not to). Incidentally, > the release notes already recommend *not* to use aptitude [1]. I expect people will just use the tool they prefer and won't read the release notes. I note that one problematic command is 'aptitude upgrade' and the "Minimal system upgrade" section doesn't mention not using aptitude. I've filed #780076 about that. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
