New Bodhi, and odd error pushing a package update to testing

[Garrett Holmstrom]

On 9/20/2010 16:41, Michel Alexandre Salim wrote:
> On Mon, Sep 20, 2010 at 11:30 PM, Fedora Koji Build System
> <buildsys at fedoraproject.org>  wrote:
>> Package: Miro
>> NVR: Miro-3.0.3-2.fc13
>> User: bodhi
>> Status: failed
>> Tag Operation: untagged
>>  From Tag: dist-f13-updates-testing-pending
>>
>> Miro-3.0.3-2.fc13 unsuccessfully untagged from dist-f13-updates-testing-pending by bodhi
>> Operation failed with the error:
>>     koji.TagError: build Miro-3.0.3-2.fc13 not in tag dist-f13-updates-testing-pending
>>
>>
> Might this have to do with the deployment of the new Bodhi? Bodhi
> still thinks the update has not been pushed to testing:
>
> https://admin.fedoraproject.org/updates/Miro-3.0.3-2.fc13
>
> but Koji already has the package tagged dist-f13-updates-testing:
>
> http://koji.fedoraproject.org/koji/buildinfo?buildID=196032

I see something similar with my latest round of stable pushes:

Package: euca2ools
NVR: euca2ools-1.3.1-1.fc13
User: bodhi
Status: failed
Tag Operation: untagged
 From Tag: dist-f13-updates-pending

euca2ools-1.3.1-1.fc13 unsuccessfully untagged from 
dist-f13-updates-pending by bodhi
Operation failed with the error:
     koji.TagError: build euca2ools-1.3.1-1.fc13 not in tag 
dist-f13-updates-pending