The difference between the two follow below. We can see multiple packages don't 
have a sysvinit file anymore, like buildd. But there is a new package, though: 
mlat-client-adsbfi. This package wasn't in Oracular, but it's in Plucky. The 
problem is: It just has a sysvinit script. As I said before, systemd will 
remove support for sysvinit scripts. Usually, everything works because systemd 
generates a unit for the sysvinit services, but this is no more. I am not sure 
about what version, though. So maybe this is a valid concern for Plucky or 
perhaps just for QQ.
-+android-androresolvd
-+babeld
-+buildd
-+camo
-+cvsd
-+darkstat
-+dibbler-client
-+dibbler-relay
-+dibbler-server
-+didiwiki
-+distcc
-+fair
-+farpd
-+ftp-proxy
-+git-daemon-sysvinit
-+ifplugd
-+ipfm
-+ircd-ircu
-+libvirt-daemon-system-sysv
-+llmnrd
-+lnpd
-+mbmon
-+mgetty-fax
-+minicoredumper
++mlat-client-adsbfi
-+nslcd
-+pandorafms-agent
-+pcaputils
-+policyd-weight
-+portsentry
-+pynslcd
-+pyro4
-+reniced
-+rng-tools-debian
-+sagan
-+samhain
-+vtun
-+webfs
-+whereami
-+xen-utils-common
-+xringd

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1681993

Title:
  Systemd service for packages without support

Status in systemd package in Ubuntu:
  New

Bug description:
  This bug is a little (just a little!?) crazy: First I done some shell-
  fu:

  apt-file search /lib/systemd/system/|grep service|cut -d: -f1|uniq > 
systemd_service.txt
  apt-file search /etc/init.d/|cut -d: -f1|uniq  > sysvinit_service.txt
  diff systemd_service.txt sysvinit_service.txt|grep  '^\+' >just_sysvinit.txt


  The first command created a list with the packages with systemd
  services. I considered as systemd service any package with a .service
  file under /lib/systemd/system/.

  The second command created a list with the packages with sysvinit
  services. I considered a sysvinit service any package with a file
  under /etc/init.d/.

  The third command compares the two files and only select the packages
  with sysvinit service, but without a correspondent systemd service.
  This packages should have support for systemd too because systemd is
  now native on new Ubuntu releases. I don't think need hurry to change
  all packages because sysvinit support on systemd is solid, but I think
  we need to think about this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681993/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to