Code: Select all

# /etc/apt/sources.list
deb http://nl.mxrepo.com/antix/testing testing dev main nosystemd
deb https://archive.neon.kde.org/unstable bionic main
deb http://security-cdn.debian.org/ testing/updates main contrib
deb-src http://nl.mxrepo.com/antix/testing testing dev main nosystemd
deb-src https://archive.neon.kde.org/unstable bionic main
deb-src http://security-cdn.debian.org/ testing/updates main contrib

When mixing up the Neon and the antiX repo (i wanna try Neon on an env outside systemd), there’re very much error showing up plenties of KF libs aren’t going to be installed, few even aren’t found on my repo at all. Any stuff needed to be done for tidying up the antiX/Neon env thanks?

There's bound to be errors. You've got Antix repo's based on Debian Testing & Neon repo's based on Ubuntu Bionic.
I don't know how you'll tidy that up as many packages would now need downgrading.
In my opinion, a clean install of Neon, would be the way to go.
But wait & see if anyone else has any other ideas first.

I see: Your antix-repository has 'nosystemd'.

Ubuntu 18.04 LTS (and KDE neon on top of it)
is systemd-based.

And even if both were the same:

What You did was wrong. This will never work.

You could try to remove all KDE neon packages,
if You know, how deb-package management works.

But I don't think You know. And I wouldn't enjoy
explaining it on forum-pages.

Therefore:
1)
Reinstall Your Antix. You destroyed it.
It could maybe be repaired, but most probably
not by You.

2)
Read about, what a distribution is. Because You don't
seem to know this.

Only because it's mentioned on Distrowatch
doesn't mean it can all be wildly mixed together.
The same package-format is not enough.

This will never work. Neither GNU/Linux nor BSD.

Edit:

To make it clearly understood,
all this problem has absolutely nothing
to do with software-quality of Antix, Ubuntu,
and KDE neon.

It's System-Administration by someone not knowing
what an operating-system is.

It could be compared to someone manually copying
system-files from Windows7 into Windows10, and
afterwards wondering why the Microsoft-stuff won't boot.

Just a Tip for you hd_scania.
It's often good practise before you do anything drastic to your system, (which we've probably all done at some point) to take a back up of your system first. FSarchiver, Timeshift, or even Clonezilla are good for this. Then when all goes wrong you can restore a working system.
But as NoNameNoBlame says, the easiest way forward now would probably be a reinstall.