Request: Possible to move zzzFM to Stable Repo?

[timkb4cq]

That's puzzling. I just tried updating an existing zzzfm here and it switched to mx-pkexec.

Screenshot-47.png

[AVLinux]

What is the package version?

1.0.7-9 is the newest showing up here in Test Repo... *note yep that's it.

Let me clean the config folder and try again..

[AVLinux]

OK,

Something weird happening, I usually use MXPI and I crosschecked in Synaptic with the MX Test Repo temporarily enabled and it shows I have 1.0.7-8 installed with no upgrade available...?

ksnip_20220312-121215.png

When I rechecked in MXPI it shows the 1.0.7-9 Packages there... but the the zzzfm-gtk3 and zzzfm-common entry is not greyed out as it should be when a package is already installed...?

ksnip_20220312-121537.png

If I try and install from MXPI it goes through the motions but the data shows in 0 bytes so nothing actually gets installed...? weird!

Apt list tells me 1.0.7-8 is installed, so that is the problem, the question is why is it not getting upgraded when MXPI sees a newer package..?

[AVLinux]

OK as a last resort from MXPI I uninstalled zzzfm completely, ran apt clean, then opened the MX Test Repo in MXPI and reinstalled everything and it still installs 1.0.7-8... now I'm very confused..

[timkb4cq]

Could be the mirror you are set to for the Test repo hasn't updated yet.

Code: Select all

cat /etc/apt/sources.list.d/mx.list

[AVLinux]

Could be the mirror you are set to for the Test repo hasn't updated yet.

Code: Select all

cat /etc/apt/sources.list.d/mx.list

I'm on the default Rochester mirror and just had the Repo Manager select the fastest one but the result is the same, still showing a new version is available but nothing installs. It shouldn't make a difference but my LXDE system in development here is currently only 32bit, you did update both amd64 and i386 packages? What has confused me here is that if MXPI shows a new version available doesn't that mean the version is present?

[timkb4cq]

The rochester mirror updates every 6 hours, and it appears to have updated just before I uploaded the new version.
MXPI downloads the Test repo indexes directly from mxrepo.com, but installs from your configured mirror - thus the mismatch.
The *.mxrepo.com servers are all updated (mxrepo.com. la.mxrepo.com, it.mxrepo.com, nl.mxrepo.com, and the two that the third party mirrors sync from - thus not listed in repo manager, da.mxrepo.com & l3.mxrepo.com)

[AVLinux]

The rochester mirror updates every 6 hours, and it appears to have updated just before I uploaded the new version.
MXPI downloads the Test repo indexes directly from mxrepo.com, but installs from your configured mirror - thus the mismatch.
The *.mxrepo.com servers are all updated (mxrepo.com. la.mxrepo.com, it.mxrepo.com, nl.mxrepo.com, and the two that the third party mirrors sync from - thus not listed in repo manager, da.mxrepo.com & l3.mxrepo.com)

Thanks very much for explaining how this all works and of course thanks for your tireless work on the repos on all of our behalf! I guess I was to game to go on this and my enthusiasm got ahead of my mirror sync... story of my life!

I will leave it for a bit and try again this evening to confirm that it's good to go..

[timkb4cq]

The Rochester mirror has updated.

[AVLinux]

And Bingo we have a winner! Thank you!!

ksnip_20220312-151158.png

Interestingly it defaulted to Mousepad which is the default LXDE Text Editor so it correctly chose it over Featherpad.. Also did a few Root things and the mx-pkexec dialog shows up as expected!

*SIDE NOTE... I have very few complaints about MX Linux and certainly none with any weight but I do not like that it's Tools require Featherpad... Mousepad is the default Text Editor of both XFCE4 and LXDE and it is very capable for the Text Editing needs of your average User. Anyone doing serious coding will likely install a developers Text Editor like EMACs etc. anyway. Featherpad is clunky, kind of ugly, doesn't theme up with GTK themes very well and I don't enjoy having it installed by default only to appease the MX Tools when it isn't native to either XFCE4 or LXDE. This probably sounds much crabbier than I intend but I just wanted to go on record and write it down somewhere...