Describe the issue librsync-2.3.2-4.fc37 built successfully, but hangs at f37-updates-candidate. No Bodhi update was created automatically for some reason (and I also did not receive the notification e-mail about the successful build, which I normally do).
When do you need this? (YYYY/MM/DD) ASAP, but not urgent.
When is this no longer needed or useful? (YYYY/MM/DD) n/a
If we cannot complete your request, what is the impact? n/a
Fixed. This happened during our rabbitmq cluster doom. ;(
i just retagged it now and bodhi picked it up.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)