It's great to be able to switch from Stable to Testing from Web GUI.
However, when the Stable version is released after Testing, switching the repository back does not trigger stable download. Firewall stuck on Testing version.
Would be good for Pakfire to recognise Stable version as newer so that it updates. A finer granularity of version recognition I guess.
I am not sure what you are suggestion, but when you change back to "stable", the last Core Update is reinstalled again which should bring you back to where you want to be.
Is this what you are expecting?
Say you are testing IPFire 2.25 Core Update 151 Development Build: master:abcdef
When 2.25 Core Update 151 Stable is released, you should be able to switch from Testing to Stable and have it download/install. Not wait for 2.25 Update 152 or later.
What is stopping you from changing back to the stable branch? As mentioned, the final update will be installed again on your system.
I have tried that on several firewalls and on different testing versions. Never worked. Have always had to backup and manually install Stable version. Maybe a Pakfire bug?
Can you provide log files?
Does the logic in pakfire.cgi decrement /opt/pakfire/db/core/mine when switching the repo from testing to stable? If not, I think it should.
It should kick in and reinstall the previous update. It is enabled for any repository apart from stable.
Closing this, since no sufficient log data has been provided. Please reopen, if necessary.