RFC: enhance cgi-bin/pakfire.cgi to revert to "Stable"

[Paul Simmons <mbatranch@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]

Hello, @list.

 From time to time, the https://nightly.ipfire.org/master/latest/*/ is 
rebuilt, due to unforeseen (but show-stopping) revision(s) of the final 
Core ??? impending release.  I think test Core 154 has been rebuilt 
twice since its initial announcement.

If a user has switched into "Testing", and a rebuild occurs, the user 
must edit /opt/pakfire/db/core/mine and decrement the content to 
reinstall the updated Testing package(s).  I assume the same is true for 
the "Unstable" build.  When leaving Testing for Stable after an 
announced Release, one must make the same change to be certain of 
receiving the "complete" release.

In addition, I assume that if one should revert from Unstable to Stable, 
Testing to Stable, or Unstable to Testing, an edit would be required to 
ensure receiving and running the correct (and latest) "*" build.

Can anyone think of a way to change/automate "revisions" in 
cgi-bin/pakfire.cgi , or must one continue to be aware of (and manually 
correct) this anomaly?

I ask because some of us (lowly users) don't have a "non-production" 
machine, but become anxious to test releases (and resolve problems).  
Recently, I made a post on the forum to help a tester install a revised 
Core 154 test build.

I understand that your time and resources are limited, and that you make 
huge sacrifices for the community.  Please advise.

Many, many thanks for your efforts.  I am humbled by your efforts and 
expertise.

Paul