MX Linux Forum

anticapitalista wrote: Sun Jul 26, 2020 3:52 pm Just to point out that MX Test repo (it is not called MX testing) is buster based.
If you are using sid repos, you should probably not use MX test repo.

Good point, and so far I don't see any packages in MX test that give a significant version advantage over the packages in Sid, so it's probably not worth the effort. It was a bit of fun trying it though.

andyprough wrote: Sun Jul 26, 2020 4:05 pm

anticapitalista wrote: Sun Jul 26, 2020 3:52 pm Just to point out that MX Test repo (it is not called MX testing) is buster based.
If you are using sid repos, you should probably not use MX test repo.

Good point, and so far I don't see any packages in MX test that give a significant version advantage over the packages in Sid, so it's probably not worth the effort. It was a bit of fun trying it though.

anti is right about that for sure.

But like I said, some of the packages we backport from Bullseye or Sid are actually versions ahead of or modified to be better OOTB for users than what is in Bullseye or Sid. Chromium, MystiQ, Ranger, vokoscreen-ng just to name a few examples really quick. Our versions are superior to anything Debian has IMHO.

We try to make sure our versions of anything in our Stable or Test repo do not trump anything that may come down from Debian... unless we don't want their versions overriding ours. So that can answer why some of our versions may not be "higher" than Debian Bullseye or Sid. One example of this was the intel-microcode recently. It was backported by us shortly before it came down as a forced update from Debian. We don't want to not allow Debian to push security updates to us if they move quickly from Sid > Bullseye > Buster.

But its just not stuff in the MX Test Repo, its many things in stable, but you do miss out I think by not being able to use the MX Test Repo. For your experiments... not really a big deal.

I have a small issue in system settings. According to what I have read there should be a selection called Desktop Behavior.
I don't seem to have it.
What I need to do is change the timing on the when the lock screen activates. That should be in that section.
Here is what I have:

MAYBL8 wrote: Sun Jul 26, 2020 7:06 pm I have a small issue in system settings. According to what I have read there should be a selection called Desktop Behavior.
I don't seem to have it.
What I need to do is change the timing on the when the lock screen activates. That should be in that section.

You need to install the kde-config-screenlocker package. There's no Desktop Behavior section anymore I don't think, but once you install kde-config-screenlocker you'll get a 'Screen Locking' module under the Workspace Behavior section. That's the module with options for changing the screen lock timing.

SwampRabbit wrote: Sun Jul 26, 2020 6:19 pmBut like I said, some of the packages we backport from Bullseye or Sid are actually versions ahead of or modified to be better OOTB for users than what is in Bullseye or Sid. Chromium, MystiQ, Ranger, vokoscreen-ng just to name a few examples really quick. Our versions are superior to anything Debian has IMHO.

Of those four packages, my franken-antiX-Sid-MX-KDE system ( ) was willing to try to install Ranger and vokoscreen-ng from MX Test, but threw up errors when I selected the Chromium and MystiQ MX Test packages. I did not really install any of them, as I don't want to destroy this unstable beast any faster than necessary.

Thanks,
Now I have to figure out what else I am missing so I can stop asking these kinds of questions.

MAYBL8 wrote: Sun Jul 26, 2020 7:43 pm Thanks,
Now I have to figure out what else I am missing so I can stop asking these kinds of questions.

Questions are fine, not a problem, I've been asking you a few too. That's what this whole endeavor is about. It is worth spending a good bit of time searching through all the packages in Synaptic that come up with a 'kde' search, or when searching 'plasma', or 'qt', to see what you could still use. For settings, search 'kde-config' and look at all the modules.

Also, I meant to tell you, I found that Debian has a 'kde-full' package that seems to install quite a few useful things after you've first installed task-kde-desktop. Unfortunately, task-kde-desktop just isn't a great all-encompassing meta-package.

andyprough wrote: Sun Jul 26, 2020 7:43 pm Of those four packages, my franken-antiX-Sid-MX-KDE system ( ) was willing to try to install Ranger and vokoscreen-ng from MX Test, but threw up errors when I selected the Chromium and MystiQ MX Test packages. I did not really install any of them, as I don't want to destroy this unstable beast any faster than necessary.

Probably because of a dependency or dependency of a dependency that isn’t in your available repos OR conflicts.. hard to say Without seeing the output.

This is the problem with mashing up multiple base OS versions.

When we build packages, they are built against a base OS version like anti was talking about (Buster vs Sid). Now this may or may not cause issues, most of the time what you are probably seeing isn’t what “build depends” are used to create the package but the specifically defined runtime “depends” needed to use the package.
Sometimes packages have specific versions as dependencies, sometimes not.

Edit: this isn’t just us that do this, it’s Debian, Ubuntu, etc, etc. which is why we tell people not to mix and match. Especially with Ubuntu PPAs.

Would both of you be interested in learning more about that sort of stuff? I mentioned it to Stevo already, but I can bring it up again.

Sure I will give it a go. I take you need help packaging ?
I guess I would have to set up a different system than this one for doing that?
I have several systems so that is no problem or I could just partition out something on this system.
Just let me know. I will be glad to help in any way I can.

MAYBL8 wrote: Sun Jul 26, 2020 8:38 pm Sure I will give it a go. I take you need help packaging ?
I guess I would have to set up a different system than this one for doing that?
I have several systems so that is no problem or I could just partition out something on this system.
Just let me know. I will be glad to help in any way I can.

One thing at a time, let me talk to Stevo again... he’s the boss.