systemd and systemd-sysv

Started by melmarker, 2014/01/10, 23:55:52

Previous topic - Next topic

melmarker

There was a upgrade for systemd after our release:

Changes:
* hold systemd-sysvrc is now obsolete
* sysvinit must not be removed any longer and can stay installed
* the pinning of sysvinit -1 can be removed
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

clubex

Which version of systemd is this?

melmarker

Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

pjnsmb


quote:
* sysvinit must not be removed any longer and can stay installed


I am running December 2013.2
I have checked that I have not purged sysvinit since install.
I have systemd and systemd-sysv  : Installed: 204-6


If I do :
apt-get install  sysvinit


I get :
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package sysvinit is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
systemd-sysv upstart sysvinit-utils sysvinit-core file-rc


E: Package 'sysvinit' has no installation candidate
regards
pjnsmb

dibl

#4
Quote from: pjnsmb on 2014/01/11, 09:09:32

E: Package 'sysvinit' has no installation candidate


That is odd -- like your networking was not running or something.  This is a "Desperado" installation, fully updated:


root@tosh205:/# apt-cache policy systemd
systemd:
  Installed: 204-6
  Candidate: 204-6
  Version table:
*** 204-6 0
        500 http://ftp.us.debian.org/debian/ unstable/main i386 Packages
        100 /var/lib/dpkg/status
     204-5.2 0
        500 http://packages.siduction.org/fixes/ unstable/main i386 Packages
root@tosh205:/# apt-cache policy sysvinit
sysvinit:
  Installed: 2.88dsf-45
  Candidate: 2.88dsf-45
  Version table:
*** 2.88dsf-45 0
        500 http://ftp.us.debian.org/debian/ unstable/main i386 Packages
        100 /var/lib/dpkg/status
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

pjnsmb

just double checked that I have network access and I do have.................


but this is the new December 2013.2 I am talking about.?
regards
pjnsmb

ayla

#6
cal@neskaya:~cal: apt-cache policy sysvinit
sysvinit:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Paket-Pinning: 2.88dsf-45
  Versionstabelle:
     2.88dsf-45 -1
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
cal@neskaya:~cal: apt-cache policy systemd
systemd:
  Installiert:           204-6
  Installationskandidat: 204-6
  Versionstabelle:
*** 204-6 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     204-5.2 0
        500 http://ftp.uni-stuttgart.de/siduction/fixes/ unstable/main amd64 Packages


This is a 2013.2 installation.

AFAIK the suggestion from melmaker is only needed for pre 2013.2, including 2013.2rc1

greets
ayla

melmarker

#7
no, that fit for rc and the regular release. The reason for that:
S. Langasek (vorlon) has fixed some issues with sysvinit, sysvinit stay essential, but is an empty metapackage now, that depends on sysvinit-core or systemd-sysv. These changes solve the problem with removing sysvinit, it can and should stay installed.


Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

ayla

Thanks for clarification. So I should do an apt-get install sysvinit I guess?

pjnsmb

that is what I tried  look at my first post

regards
pjnsmb

ayla

Have a look at /etc/apt/preferences.d.
There is a file 999-finalize:

QuotePackage: sysvinit
Pin: release a=unstable
Pin-Priority: -1
remove it or comment the lines with a #

Then apt-get update && apt-get install sysvinit

greets
ayla

pjnsmb

thanks ayla


that worked for me


glad somebody knows what they are doing................
regards
pjnsmb

melmarker

systeminit is empty and will stay empty - it makes no difference if it is installed or not :P

but if one remove the -1 pinning it will be installed automagically within the next d-u because it is essential :)
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

ayla

Have to confess: I know nothing and what I thought clear now is heavy fog.  :o

Oder in deutsch: Alle Klarheiten restlos beseitigt.  :D

greets
ayla