Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #163197 > unrolled thread
| Started by | Aldo Maggi <aldomaggi@katamail.com> |
|---|---|
| First post | 2016-01-17 12:00 +0100 |
| Last post | 2016-01-20 15:40 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.user
dselect, init and systemd-sysv Aldo Maggi <aldomaggi@katamail.com> - 2016-01-17 12:00 +0100
Re: dselect, init and systemd-sysv koanhead <koanhead@riseup.net> - 2016-01-20 08:10 +0100
Re: dselect, init and systemd-sysv Adam Wilson <moxalt@riseup.net> - 2016-01-20 15:40 +0100
| From | Aldo Maggi <aldomaggi@katamail.com> |
|---|---|
| Date | 2016-01-17 12:00 +0100 |
| Subject | dselect, init and systemd-sysv |
| Message-ID | <qRTdU-1nb-3@gated-at.bofh.it> |
Yesterday while updating my system via dselect (I'm using testing) I've received the warning that "init and systemd-sysv" were going to be uninstalled and I had to approve or deny that action. I've thought that as in previous cases (to be frank not recently but many years ago) there was a mistake, since looking at the packages which were going to be installed it didn't seem that a replacement was present, therefore I've stopped the updating. This morning I've tried again but got the same warning. So I've used apt-get update && apt-get upgrade, in this case no warning appears and systemd-sysv appears among the pkgs to be upgraded. Is dselect still working safely or should I give up and change package mgr? Many thanks Aldo
[toc] | [next] | [standalone]
| From | koanhead <koanhead@riseup.net> |
|---|---|
| Date | 2016-01-20 08:10 +0100 |
| Message-ID | <qSV3X-35h-1@gated-at.bofh.it> |
| In reply to | #163197 |
On Sun, 17 Jan 2016 12:00:02 +0100, Aldo Maggi wrote: > Yesterday while updating my system via dselect (I'm using testing) I've > received the warning that "init and systemd-sysv" were going to be > uninstalled and I had to approve or deny that action. > I've thought that as in previous cases (to be frank not recently but > many years ago) there was a mistake, since looking at the packages which > were going to be installed it didn't seem that a replacement was > present, therefore I've stopped the updating. > This morning I've tried again but got the same warning. > So I've used apt-get update && apt-get upgrade, in this case no warning > appears and systemd-sysv appears among the pkgs to be upgraded. > > Is dselect still working safely or should I give up and change package > mgr? > > Many thanks > > Aldo Without seeing the specific message output by dselect it isn't possible to say for sure- but I would guess that your testing system is trying to do a dist-upgrade, and in the process switching your init to the new default, systemd. If you don't want this to happen then it might be prevented by installing the systemd-shim package IIRC. If you're confused by the behavior of dselect I recommend using the `apt` tool instead, or one of `aptitude` or `apt-get`. Again, without the specific output messages you are seeing it's not possible to properly diagnose the situation- so everything I'm saying here could be entirely wrong!
[toc] | [prev] | [next] | [standalone]
| From | Adam Wilson <moxalt@riseup.net> |
|---|---|
| Date | 2016-01-20 15:40 +0100 |
| Message-ID | <qT25u-7Pe-55@gated-at.bofh.it> |
| In reply to | #163197 |
On Sun, 17 Jan 2016 11:26:54 +0100 Aldo Maggi <aldomaggi@katamail.com> wrote: > Yesterday while updating my system via dselect (I'm using testing) > I've received the warning that "init and systemd-sysv" were going to > be uninstalled and I had to approve or deny that action. You have to be prepared to face things like this if you're using testing. If you want everything to work peachy-perfect, use stable. I had the same problem a few days ago, back when I was still using testing. A whole host of issues and buggy packages led me to learn from my folly and switch to stable, of which I am a proud user once more. If you must continue using testing for some reason, be prepared to put up with problems such as these; they are manifold (occasionally). > I've thought that as in previous cases (to be frank not recently but > many years ago) there was a mistake, since looking at the packages > which were going to be installed it didn't seem that a replacement > was present, therefore I've stopped the updating. > This morning I've tried again but got the same warning. > So I've used apt-get update && apt-get upgrade, in this case no > warning appears and systemd-sysv appears among the pkgs to be > upgraded. This should already be a sign that apt-get and aptitude are vastly superior to dselect. dselect hasn't been the preferred dpkg frontend since woody. > Is dselect still working safely or should I give up and change > package mgr? Use apt-get. Seriously. The latest documentation for dselect is from woody, and 14 years old (2002): https://www.debian.org/releases/woody/i386/ch-main.en.html
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web