I tried the pin thing about a week ago and it did not catch systemD.
I sure must have misconfigured it if it really works, as granted I didnt understand how the pinning actually works, as I should understand it.
I had the same failure as many other users had where the package pinned just appeared again.
I will try it again, if I cannot Migrate the system as is to Antix.
It will be valuable to at least run this mission crytical server with MX18 without systemD ever darkening my doorstep if I can get pinning to work which will give me time if I have to do a hard migrate to antix or devuan. As I mention now, I have to use cron to notify me if it installed.
UPDATE: I created a partition on one of my machines I installed MX18 and will test the pinning there till it works.
MX works great if I can ban systemD permanently. I dont want to use any application that is systemD dependent. They are usually gnome apps so I dont bother with that anyway. At the moment I have no systemD dependencies and will see if I can get pinning to work on the test partition.
If I get trouble I will post it in a new thread. Better not to do any apt/dpkg commands on the existing system untill I understand pinning properly in my test partition.
Thanks a lot.