This release: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4da598e74b has been stuck waiting to get moved to stable. Is some error going on that isn't evident?

This was a release that I did to hopefully correct what is discussed here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...

Kevin Fenzi wrote: > We are in Beta freeze. Only packages that fix accepted blocker bugs > or > freeze break exceptions can go stable. > > https://fedoraproject.org/wiki/Milestone_freezes Would it be possible for Bodhi to say so, so people don't need to ask here on the mailing list? Kevin's wording is perfect. It just needs to be visible in the web interface, with the words "Beta freeze" as a link.

On Fri, Sep 11, 2020 at 04:35:03PM -0500, Tony Asleson wrote: > This release: > > https://bodhi.fedoraproject.org/updates/FEDORA-2020-4da598e74b > > has been stuck waiting to get moved to stable. Is some error going on > that isn't evident? We are in Beta freeze. Only packages that fix accepted blocker bugs or freeze break exceptions can go stable. https://fedoraproject.org/wiki/Milestone_freezes > > This was a release that I did to hopefully correct what is discussed here: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... You can request a freeze break if you like: https://fedoraproject.org/wiki/Milestone_freezes#How_are_freeze_exception... or just wait until after Beta is signed off on and updates will start flowing to stable again (until final freeze).

The older build was tagged over the new one because Kevin ran a fixup script to find packages where Bodhi accidentally pushed an older version on top of a new one (it's a long standing Bodhi issue during freezes). Your build was caught in the fixup. However, before you go and ask releng to undo this, I believe what they did was actually correct. The EVR of a package should not go backwards like you pushed an older build there. Instead, you need to bump Epoch to 1 (in both F33 and master) and then do new builds and submit that to bodhi. This should make the downgrade correctly happen.

On 9/30/20 1:05 PM, Kalev Lember wrote: > On Wed, Sep 30, 2020 at 7:48 PM Tony Asleson <tasleson(a)redhat.com&gt; wrote: > >> On 9/11/20 5:07 PM, Kevin Fenzi wrote: >>> On Fri, Sep 11, 2020 at 04:35:03PM -0500, Tony Asleson wrote: >>>> This release: >>>> >>>> https://bodhi.fedoraproject.org/updates/FEDORA-2020-4da598e74b >>>> >>>> has been stuck waiting to get moved to stable. Is some error going on >>>> that isn't evident? >>> >>> We are in Beta freeze. Only packages that fix accepted blocker bugs or >>> freeze break exceptions can go stable. >>> >>> https://fedoraproject.org/wiki/Milestone_freezes >>> >>>> >>>> This was a release that I did to hopefully correct what is discussed >> here: >>>> >>>> >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... >>> >>> You can request a freeze break if you like: >>> >> https://fedoraproject.org/wiki/Milestone_freezes#How_are_freeze_exception... >>> or just wait until after Beta is signed off on and updates will start >>> flowing to stable again (until final freeze). >> >> I got an email on 9/25 that this issue was moved to stable. As of right >> now it's still appears to be in updates-testing. >> >> >> Using the following: >> >> https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html >> >> >> I would have thought that 9/29 this package would be in stable, but >> maybe beta has not been signed off? >> > > Hi Tony, Hi Kalev, > Looks like your update briefly made it stable, but then the older build > (pywbem-1.0.1-1.fc33) was tagged back over the new one > (pywbem-0.14.6-6.fc33): > > $ koji list-history --tag f33 --package pywbem > Tue Feb 11 18:46:20 2020 package owner releng set for pywbem in f33 by > mohanboddu [still active] > Tue Feb 11 18:46:20 2020 package list entry created: pywbem in f33 by > mohanboddu [still active] > Tue Feb 11 19:20:52 2020 pywbem-0.14.6-2.fc32 tagged into f33 by mohanboddu > Fri May 29 14:27:13 2020 pywbem-0.14.6-3.fc33 tagged into f33 by autopen > Sat Aug 1 20:48:49 2020 pywbem-0.14.6-4.fc33 tagged into f33 by mohanboddu > [still active] > Mon Aug 10 07:14:46 2020 pywbem-1.0.1-1.fc33 tagged into f33 by bodhi > Tue Aug 11 17:38:36 2020 pywbem-0.14.6-2.fc32 untagged from f33 by oscar > Fri Sep 25 18:23:13 2020 pywbem-0.14.6-6.fc33 tagged into f33 by bodhi > [still active] > Sat Sep 26 20:14:34 2020 pywbem-1.0.1-1.fc33 re-tagged into f33 by kevin > Sat Sep 26 20:21:02 2020 pywbem-0.14.6-3.fc33 untagged from f33 by oscar > > The older build was tagged over the new one because Kevin ran a fixup > script to find packages where Bodhi accidentally pushed an older version on > top of a new one (it's a long standing Bodhi issue during freezes). Your > build was caught in the fixup. > > However, before you go and ask releng to undo this, I believe what they did > was actually correct. The EVR of a package should not go backwards like you > pushed an older build there. Instead, you need to bump Epoch to 1 (in both > F33 and master) and then do new builds and submit that to bodhi. This > should make the downgrade correctly happen. > I specifically asked about this: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... and was told to not bump the epoch and that all would be fine if I got this done before final freeze, which is what I'm trying to do. So what's the correct answer, because I'm running out of time?

Ahh, sure, if the previous package was uninstallable then it should be fine to not use epoch.

So two options here: a) file a releng ticket ( https://pagure.io/releng/issues) and ask them to re-tag the other build, or b) just bump release and rebuild and submit it to bodhi once more.

I posed the question on IRC if this fix-up script gets run after freeze and the answer was it could. I don't want to get caught with this again, so I'm in the process of adding epoch and rolling new releases across the board as it seems like the safest approach. Just wish I had done this as I had planned 4+ weeks ago.