you should never actually delete an update, so no.

Well, if you think the current broken state is OK and the "500 Internal error" is normal expected behaviour and you are also OK with wasting testers resources by allowing them to test and give positive karma to something that is obsoleted for a long time and cannot be pushed to stable due to:

Broken update path: gr-air-modes-0-0.13.20130409gitf25d21f5.fc18 is already released, and is newer than gr-air-modes-0-0.10.20120905git6c7a7370.fc18

I can also ignore it.

you can unpush and not delete

Replying to [comment:3 ausil]:

you can unpush and not delete
How? It ends with:
500 Internal error

The server encountered an unexpected condition which prevented it from fulfilling the request.

This is the bodhi exception that is thrown when trying to unpush:
{{{
File "/usr/lib/python2.6/site-packages/bodhi/model.py", line 448, in set_request
self.unpush()
File "/usr/lib/python2.6/site-packages/bodhi/model.py", line 994, in unpush
task = koji.tagBuild(self.release.candidate_tag,build.nvr,force=True)
File "/usr/lib/python2.6/site-packages/koji/init.py", line 1552, in call
return self.func(self.__name,args,opts)
File "/usr/lib/python2.6/site-packages/koji/__init.py", line 1914, in _callMethod
raise err
TagError: build gr-air-modes-0-0.10.20120905git6c7a7370.fc18 not complete: state DELETED

}}}

I went ahead an marked the update as being 'obsolete' by hand.