What does this apt/synaptic error mean?
 

I've just been updating my 32-bit AntiX. dbus would not update and was described as broken. The message is:
"dbus depends on libsystemd0 but it is not installable".

I checked for this library and got:
"libsystemd0 has no available version but exists in the database".

AntiX doesn't actually use systemd but it gets most of its software directly from the Debian repository. So is this a glitch in the business of getting systemd out of AntiX? Should I just wait and hope it gets cleared up or is there something I should be doing?

As far it's me: Yes, pretty sure this is related to antiX avoiding systemd.
If it was me i would ask in the antiX forum.
A websearch gives for example this:
http://antix.freeforums.org/post50440.html#p50440
(which would mean: you have to wait)

I don't know if antiX uses pinning to make sure neither systemd nor libsystemd0 gets installed as a dependencies. You have to check that, and if libsystemd0 doesn't bother you, remove the pinning for it.

But, like said, to be sure, i would ask at the antiX forum (or wait if one who knows for sure answers here)

Well, I'm not in a hurry. I just wanted to check that there isn't something wrong at my end.

Because you had a message describing a package as broken, I personally would run the following 2 commands just to check that all is right at your end:

dpkg --audit

sudo apt-get check

Hazel.

Hopefully you don't have Debian Multi Media sources enabled.

When ever I grabbed something from there. And later on forget to comment that sources.list out. Breakage was sure to occur.

Have you repaired the GPG key error yet that came up recently from Daves repo server?

https://forum.mxlinux.org/viewtopic.php?f=108&t=41849

Does your version match mine?

is your /etc/apt/preferences.d/00systemd match mine?

Because dbus updated fine on my install with no errors and I am still on AntiX 15.

The link to Anti's post in the forum thread is for folks running Alpha 2 with Debian Stretch Repos. I am still on Jessie on mine.

Hence why I want to see your sources.list in your inxi report.

I just upgraded a fresh antiX-16.1 with default repos without issue. No libsystemd0 got installed.

So there seems to be something wrong at your end.

It didn't get installed at my end either! The problem is that dbus seemed to require it. I am tied up this morning, but I shall try again in the afternoon with all the helpful suggestions I have received in this thread and then report back.

btw I did notice the failure to connect to daveserver and I suspect that that's where the problem lies. I gather that this is the repo that contains all the AntiX-specific packages.

OK. I ran inxi and the result is one of the two attached files. The only Debian repos that I am using are the main Jessie ones. Multimedia is not activated, so that's one more thing we can forget about.

The commands suggested by hydrurga ran without error. Then I ran apt-get update again because I wanted to see the daveserver error more clearly. That's the second attachment.

@Rokytnj. My systemd pin file is the same as yours, but my AntiX keyring is older, 2015 rather than 2017. That's probably the cause of the problem. But when I tried to update it with apt-get as per your link, apt-get said it was up to date!

What do I do next?

How I fixed my GPG error was to install the newer dave deb manually from here

http://antix.daveserver.info/stable/...chive-keyring/

Just run the dpkg -i install command or use Gdebi or Synaptic <point it to the deb>.

say yes to overwrite and install poackage maintainers version. Then run apt-get update again and see if that fixes it.

That worked for me.

Edit. me cheating for later on. I hope you don't mind hazel.

Thanks, Roky! That did it. When I ran apt-get update again, there were no errors. Then I ran apt-get upgrade and a whole load of AntiX-specific stuff came down from daveserver. I hope I'm clear now.

Now can anyone point me to a simple non-technical explanation of what I just did? Because I hate working blind, even when I'm following guidance from trusted friends.

PS: Synaptic is OK too. No broken packages reported and dbus is no longer waiting for an update.

My biker simple explanation. Which can be wrong. But I get by even when mistaken.

Daves repo has a bunch of libs and apps specific to /usr/local/bin and other places.

Since the gpg error kicks in. Synaptic and apt think you are trying to install stuff from a malware repo sight.

So it says no to downloading during a apt-get update && apt-get dist-upgrade process started by you.

Badda Bing, Badda Boom. Error city. Because Daves nosystemd repo and Jessie update start arguing kinda sorta and Jessie starts to complain about needing systemd stuff. Because systemd stuff is the default now in Jessie upgrades.

I hope my neanderthal type of Linux user explanation is correct and easy to understand. Maybe Anti can explain better and correct me if I am wrong.

Edit: forgot my manners. Glad you got it all sorted.

@nd edit: Ha ha. Now to use this thread to fix my shop media center computer gpg errors. I dual boot this with MX and AntiX.

So let me see if I understand this. This key ring is a list of public key certificates for trusted repository servers and some of them were out of date. As a result, daveserver was seen as a dodgy site and apt wouldn't download anything from it. Instead I got the standard Debian versions, which are dependent on systemd.

But why couldn't I update the key ring via apt? Or does that come from daveserver too, creating a closed loop?

The keyring does come from daveserver. Some people have had issues updating, others not. The first question asked (to upgrade) is something like 'do you want to install from an untrusted server?'. If user answers the default No, then I assume that 'locks' the daveserver/antiX repo.

I didn't see that message. Maybe I wasn't looking carefully enough.

I've been for a walk since my previous post and I think I now understand what happened. I assume a new keyring comes out before the certificates expire, and gets picked up by people who do a weekly or monthly update. But I use oldboy only as an occasional print server because it runs painfully slow even with AntiX. I update it when I remember to. In the mean time, the certificates must have run out, trapping me in this loop.