#5174: F-17 update cannot be pushed despite qualifying for stable -----------------------------+------------------------ Reporter: pghmcfc | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 17 Final | Component: other Keywords: bodhi | Blocked By: Blocking: | -----------------------------+------------------------ I have a critical path update that has been in updates-testing for over two weeks and has no negative karma, yet I still can't push it to stable:
https://admin.fedoraproject.org/updates/FEDORA-2012-6165/perl-IO-Socket- SSL-1.66-1.fc17
Yesterday I received an email telling me it had been in updates-testing for 14 days and I could push it to stable - but I couldn't.
Today I received an "old testing" reminder that I was able to push the update. I still can't.
There is no "Mark as stable" link, editing the update and putting "Stable" for "Request" has no effect, and using the bodhi command-line client tells me that the update has not yet met the stable update criteria.
What's going on?
#5174: F-17 update cannot be pushed despite qualifying for stable ------------------------------+----------------------- Reporter: pghmcfc | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 17 Final | Component: other Resolution: | Keywords: bodhi Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by pghmcfc):
Same problem now with https://admin.fedoraproject.org/updates/FEDORA-2012-6698/perl-Net- SSLeay-1.48-1.fc17
#5174: F-17 update cannot be pushed despite qualifying for stable ------------------------------+----------------------- Reporter: pghmcfc | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 17 Final | Component: other Resolution: | Keywords: bodhi Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by pghmcfc):
And another one: https://admin.fedoraproject.org/updates/FEDORA-2012-6930
I'm getting spammed with emails telling me I can push these every day, but I can't, well not unless I give my own update the extra karma point it needs to actually get pushed.
#5174: F-17 update cannot be pushed despite qualifying for stable ------------------------------+----------------------- Reporter: pghmcfc | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 17 Final | Component: other Resolution: | Keywords: bodhi Blocked By: | Blocking: ------------------------------+-----------------------
Comment (by pghmcfc):
Whatever switch has just been flicked to start releasing updates for F-17 has resolved this issue - Bodhi now presents a "Mark Critical Path Update as Stable" link and I am able to mark ones that have been in testing for two weeks as stable now.
It would be nice to know what the cause of this was though, so that it won't be an issue as F-18 release approaches.
#5174: F-17 update cannot be pushed despite qualifying for stable ------------------------------+----------------------- Reporter: pghmcfc | Owner: rel-eng@… Type: task | Status: closed Milestone: Fedora 17 Final | Component: other Resolution: fixed | Keywords: bodhi Blocked By: | Blocking: ------------------------------+----------------------- Changes (by kevin):
* resolution: => fixed * status: new => closed
Comment:
I'd suggest refiling this against bodhi next time you see it appear?
Not sure what would have happened here. ;(
rel-eng@lists.fedoraproject.org
-
Fedora Release Engineering