They are attempting (not necessarily successfully) to prevent shutdowns/reboots while package manager is running

Ah, interesting. Thanks!

It probably won't. AFAIUI the developers have made the decision to stub out most of the (unwanted) extra functionality offered by systemd.

Devuan is based on Debian. The goal of Devuan is to be free of systemd in order to let people decide which init system to use. That is why libsystemd0 is an empty package. The other goal is to keep things simple (it means not to maintain to many packages). It is in the mind of the developers of apt (which of course is from debian and ubuntu) that the decisions of what apt should depend upon is taking place. I am sure you can find more information on debians apt-devel mailing list. It will be a lot of work with no practical benefit to remove the empty systemd0 package. If it easy to do without removing a lot of packages I am sure it was already done.

I hope this answer was helpfull

Have a nice day
Lars H

bgstack15 wrote:

would you know any of the motivations of the apt maintainers who made the choice to link apt to libsystemd0?

No but I would hazard a guess that it is related to the systemd timers now supplied with the package (or perhaps the new sandboxing feature).

They are attempting (not necessarily successfully) to prevent shutdowns/reboots while package manager is running, but that code depends on systemd-logind (or maybe elogind) and doesn't work if, for example, dbus isn't running or something else went wrong. Also i don't know how elogind is going to prevent shutdown/reboot if init system isn't systemd.

The code is here: https://github.com/Debian/apt/blob/cb60 … l.cc#L3444

Another thing they do with systemd is that they track if package manager was invoked in interactive mode/shell or not and include that info into HTTP requests to repo servers. That code is also completely depends on systemd and won't work if you are not running systemd.

https://github.com/Debian/apt/blob/cb60 … tp.cc#L981

Besides that i didn't find any more systemd call in apt.

would you know any of the motivations of the apt maintainers who made the choice to link apt to libsystemd0?

No but I would hazard a guess that it is related to the systemd timers now supplied with the package (or perhaps the new sandboxing feature).

Would anyone well-versed in the subject try to explain it to me?

Not sure about "well versed" but I can tell you that the apt binary is linked to /lib/x86_64-linux-gnu/libsystemd.so.0 during compilation — this is because GNU/Linux uses dynamic linking.

In Devuan's case /lib/x86_64-linux-gnu/libsystemd.so.0 is symlinked to /usr/lib/x86_64-linux-gnu/libelogind.so.0 so at no point is systemd invoked in any way.

EDIT: better link.

I am concerned that apt has been modified to use systemd. Would anyone well-versed in the subject try to explain it to me? I will also at some point to try to look at the source, but if anybody could summarize, that would help everyone else out!

Apt has not been modified to use systemd. I have no trace of sysemd on my computer (running beowulf), not even libsystemd0, and apt works just fine. I really don't know what else to say.

Does it link to libsystemd0 because apt in Devuan is build from older source code or is that because apt in Devuan is built on Debian that has systemd?

The apt package in Devuan comes directly from Debian; it is an unmodified Debian package.

Phil

It's installed by libelogind0.

$ ldd $(which apt) | grep -i systemd
$ dpkg -S /usr/lib/x86_64-linux-gnu/libsystemd.so.0

That's not a problem. It's essentially a "fake" systemd component -- libelogind0 put that there because some software expects libsystemd0 to be present. The software "thinks" it's "talking" to libsystemd0, but it's really "talking" to libelogind0.

Phil

Isn't it a symbolic link to libelogind.so.0?

Yes, you are correct.

Phil

I dont think there is any way of getting around this as devuan is a fork of debian. I believe it would require a rewrite of the code and a massive downgrade of binaries in the repos.

No, it appears to be just a matter of recompiling apt with `HAVE_SYSTEMD` unset. It is unset when systemd isn't present. I have compiled apt from source code on Devuan (Beowulf) and apt doesn't link to libsystemd0 anymore.

You can try it yourself, source code is here: https://github.com/Debian/apt

You will need `triehash` somewhere in your path, utility itself is here: https://github.com/julian-klode/triehash, then `ln -sf /path/triehash.pl /otherpath/bin/triehash` and `/otherpath/bin` has to be in $PATH so cmake can see it when configuring apt build. The rest of the packages needed for build can be installed from Devuan repos.