Automatic updates for single builds are not pushed to pending, they go directly to testing. So I guess this was created manually. But I sill think that we have some logic in place to move the update in testing in such case so I ll have a look at what is going on there.

For some reason the build did not get signed. The build is correctly tagged as f32-updates-candidate so it should be picked up by robosignatory and signed.

I am not sure how to check if something went wrong in robosignatory. Maybe @kevin can help here.

See https://bodhi.fedoraproject.org/updates/FEDORA-2019-875ceb5baa
I don't know what @sagitter edited, but this update is in pending for a while. Is suggest there was some confusion with automatic rawhide updates vs. regular updates and now this wants to be pushed to testing, but there is no testing?

Using that release (1.74-8) should be forced because it overrides the current (bad) higher released build (1.74-7) created when Python 3.7 was used on Rawhide branch (see the Changelog of python-biopython).
Currently, dependent packages (like ProDy) build fails on Fedora 32 because uses python(37)-biopython.

Automatic updates for single builds are not pushed to pending, they go directly to testing. So I guess this was created manually. But I sill think that we have some logic in place to move the update in testing in such case so I ll have a look at what is going on there.

Yes, I myself have created FEDORA-2019-875ceb5baa manually.

I've retagged the package and that got it going. I'm not sure why it was stuck...

Thanks.