Pin: origin "iso.mxrepo.com"

these hooks you speak of, are you saying that if I install something it could pull a dependency from mxrepo? I don't want that to happen & mess up my system.

Thanks for pointing that out.

That's fine, my instruction won't cause a problem if all he wants is kernels, and pins low priority.

Also MXLinux uses sysv init not systemd, and keeping systemd-sysv pinned at -1 should help, also if you keep MX repositories at 100 they rarely will pull anything in unless specified, dependencies will come from Devuan repositories as a priority, and you can pin lower if you want, but I've not had anything odd pulled even at 250.

I don't know, I'm not that stubborn I guess as long as openrc or sysv init keeps working I'll continue to be happy...  But I can understand wanting to avoiding systemd creep.

Yes, it's the creep that is the real issue with systemd.  If it was just an init, there would have been no need for Devuan.

It is quite intentional.

Just FYI, packages coming from Debian via amprolla3 are banned but packages coming directly from Debian are not filtered.  That's why we advise against using Debian repos directly.

Cheers

That's fine, my instruction won't cause a problem if all he wants is kernels, and pins low priority.

Also MXLinux uses sysv init not systemd, and keeping sysdemd-sysv pinned at -1 should help, also if you keep MX repositories at 100 they rarely will pull anything in unless specified, dependencies will come from Devuan repositories as a priority, and you can pin lower if you want, but I've not had anything odd pulled even at 250.

I don't know, I'm not that stubborn I guess as long as openrc or sysv init keeps working I'll continue to be happy...  But I can understand wanting to avoiding systemd creep.

Is using elogind from devuan repositories a faux paux?

Oh also you could add this line to /etc/apt/preferences.d/avoid-systemd

Package: systemd-sysv
Pin: origin "mxrepo.com"
Pin-Priority: -1

Edit: I went back to my initial post and edited the pin-priority for mx repo to 100.  That's a relatively safer place to start.

Try adding the one you want to /etc/apt/sources.list.d/:

deb http://iso.mxrepo.com/mx/repo/ stretch main non-free
deb http://iso.mxrepo.com/mx/testrepo/ stretch test

then:

wget -qO -  http://teharris.net/mx17repo.asc | sudo apt-key add - 

Then pin in /etc/apt/preferences.d/:

Package: *
Pin: origin "mxrepo.com"
Pin-Priority: 100

I personally have the full mxrepos for all their tools, I pin the repository around 100, and usally have their testing commented out and use devuan backports...  If you want to use mx repos fully then you may also want to list antiX repos...  well good luck, I hope this helps.

So add mx17 repos and just install the packages you want

Edit: I edited pin priority to 100

http://mxrepo.com/mx/testrepo/pool/test … -liquorix/

these kernel + headers are backported for stable GCC, MX17 = Stretch-based distros. I do not want add all mxrepo.com repos, I just would like this folder.
Is this possible to do in some way? If not, is possible Devuan developers could perhaps add these backported Liquorix kernel to Devuan repos? I think would be great addition to Devuan for those that would like bleeding-edge kernel, is especially ideal for SSD's.