Dev1 Galaxy Forum / Update for libsystemd0

Re: Update for libsystemd0

dummy@example.com (ChuangTzu) — Tue, 15 Jan 2019 21:17:32 +0000

Yup, fairly harmless, just a reminder of how long those tentacles are. Good news is that without the body, the tentacles are just a sticky reminder.

Re: Update for libsystemd0

dummy@example.com (Ogis1975) — Tue, 15 Jan 2019 18:24:54 +0000

xinomilo wrote:

we don't have systemd installed, but all these packages are hard coded to look for it anyway?
this doesn't seem like a good practice at all. !?!?!?

Quote from sticky thread:

Most of those "alarming" files are just systemd units files, put there by daemons/packages/utilities who "also" support systemd in a way or another. So they are not alarming but just *totally* *harmless* if you don't have a running systemd as PID 1, since only systemd understands and can run them. It would be *totally* *useless* (and utterly *stupid* IMHO) to fork, rebuild, and maintain a few more hundred packages only because they happen to provide a systemd unit file for
those systems where systemd is used.

Re: Update for libsystemd0

dummy@example.com (golinux) — Tue, 15 Jan 2019 17:46:54 +0000

xinomilo wrote:

we don't have systemd installed, but all these packages are hard coded to look for it anyway?
this doesn't seem like a good practice at all. !?!?!?

So far, that connection is "harmless" (according to those who know better than I). If that ever changes, we'll be scrambling. It's similar to libpulse0. Even though I don't have pulseaudio installed some apps still look for it so it needs to be there. Feel free to join the libsystemd0 decontamination team.

Re: Update for libsystemd0

dummy@example.com (xinomilo) — Tue, 15 Jan 2019 17:21:45 +0000

we don't have systemd installed, but all these packages are hard coded to look for it anyway?
this doesn't seem like a good practice at all. !?!?!?

Re: Update for libsystemd0

dummy@example.com (golinux) — Tue, 15 Jan 2019 16:11:55 +0000

The other option would be to remove the hook in all the packages that call it. Unless we have many more devs to remove these, we're going to have to live with it. We actually did a pretty good job in jessie but the list is growing with each new release.

Re: Update for libsystemd0

dummy@example.com (Geoff 42) — Tue, 15 Jan 2019 10:44:31 +0000

Some software wants to know whether systemd is running or not and it calls libsystemd0 to find out and can then behave correctly. If you delete libsystemd0 then such software will not be able to find out.

Geoff

Re: Update for libsystemd0

dummy@example.com (Ron) — Mon, 14 Jan 2019 22:37:06 +0000

Thanks for that link. I have read that in the past. I forgot it was a sticky. So I gather from the sticky that libsystemd0 does nothing. So in that case I guess it doesn't matter if I update it or not? Is that correct?

Is it okay to delete this file? (Sorry if this is a thick-headed question)

Re: Update for libsystemd0

dummy@example.com (golinux) — Mon, 14 Jan 2019 18:10:17 +0000

You might want to look at this sticky thread.

Update for libsystemd0

dummy@example.com (Ron) — Mon, 14 Jan 2019 17:41:43 +0000

I just noticed there is an update for libsystemd0. Does Devuan use this app/file/whatever? Would it break the OS if I deleted it? Or should I just update it? Thanks.