setting status before setting importance causes traceback

[Jelmer Vernooij]

Attempting to set a bug status to triaged or fixreleased before its importance has been set to something other than undecided causes a traceback. It would be nice if hydrazine (or launchpadlib) could print a saner error:

hydrazine(edge) #524843 in bzr-git> status fixreleased
changing status New => Fix Released
HTTP Error 412: Precondition Failed
Response headers:
---
content-length: 0
content-type: text/plain
date: Wed, 10 Mar 2010 00:39:51 GMT
server: zope.server.http (HTTP)
status: 412
vary: Cookie,Authorization,Accept
via: 1.1 wildcard.edge.launchpad.net
x-content-type-warning: guessed from content
x-powered-by: Zope (www.zope.org), Python (www.python.org)
---
Response body:
---

---

hydrazine(edge) #524843 in bzr-git> status fixreleased
changing status New => Fix Released
HTTP Error 412: Precondition Failed
Response headers:
---
content-length: 0
content-type: text/plain
date: Wed, 10 Mar 2010 00:39:52 GMT
server: zope.server.http (HTTP)
status: 412
vary: Cookie,Authorization,Accept
via: 1.1 wildcard.edge.launchpad.net
x-content-type-warning: guessed from content
x-powered-by: Zope (www.zope.org), Python (www.python.org)
---
Response body:
---

---

hydrazine(edge) #524843 in bzr-git> importance low
changing importance Undecided => Low
**** before save
**** got error
hydrazine(edge) #524843 in bzr-git> status fixreleased
changing status New => Fix Released

[Jelmer Vernooij (jelmer)]

Actually, this doesn't appear to be the full problem. In some cases I am actually able to set status to triaged before setting an importance.