On Thu, Jun 21, 2007 at 04:23:50PM -0400, Jesse Keating wrote:
On Thursday 21 June 2007 16:17:09 Axel Thimm wrote:
> I created a new update which was a security relevant update and was
> marked as such. bodhi offered me the possibility to push into testing
> or stable. I think the push into stable was offered only because it
> was maerked a security sensitive, so updates-testing could be
> shortcutted. I also know that the default policy was for security
> updates to bypass updates-testing entirely.
> Still, the system offered my to go testing or stable, and I chose
> testing. The update later was simply saying that a request was made to
> move it, but not whereto. A while later the package made it into
> I'm not saying to change the policy, just noting a discrepancy in
> the application's workflow. Thanks!
Axel, can you file a ticket in bodhi's trac? That may be a bug.
I tried to, but
| TICKET_CREATE privileges are required to perform this operation
And trac munges the back operation in the browser.
Looks like the login timeouts are insanely short and trac has no
recovery mechanism for that.
Axel.Thimm at ATrpms.net