I've untagged it and re-tagged it into f32-updates-candidate and it seems to be unstuck :)

https://bodhi.fedoraproject.org/updates/FEDORA-2019-560a7ecd09

Sorry for the inconvenience :(

Is that something I could do myself in future, or does it require more elevated privileges?

If I could have done it myself, what would be the koji commands to use?

Oh, and thanks for the quick response.

Is that something I could do myself in future, or does it require more elevated privileges?

I honestly do not know, afaik I am a regular packager/provenpackager in koji so it may work for you as well

If I could have done it myself, what would be the koji commands to use?

I checked the current status with: koji buildinfo perl-Path-Class-0.37-14.fc32. Since it was stuck in f32-updates-candidate I decided to remove it and adding it back to the tag which should kick robosignatory again.

So I untagged it using koji untag f32-updates-candidate perl-Path-Class-0.37-14.fc32 and retagged it using: koji tag f32-updates-candidate perl-Path-Class-0.37-14.fc32.
This then re-triggered robosignatory who signed the build and moved it into the next tag where bodhi picks it up.
If it had been in another tag, the problem/solution may have been different :)

Oh, and thanks for the quick response.

Sure thing :)

Thanks, I'm a provenpackager too so I'll give it a try if it happens again.

for reference, python2-setuptools-41.0.1-10.fc32 was stuck as well and I run:

$ koji untag f32-updates-candidate  python2-setuptools-41.0.1-10.fc32
$ koji tag f32-updates-candidate  python2-setuptools-41.0.1-10.fc32
Created task 37352387
Watching tasks (this may be safely interrupted)...
37352387 tagBuild (noarch): closed
37352387 tagBuild (noarch) completed successfully

And it indeed helped.