Metadata Update from @james: - Issue tagged with: medium-gain, medium-trouble
Sorry, this is a bad week or two to get weird issues issues fixed ... so it might take a bit before someone can work out what went wrong and fix it.
Likely it's bodhi not doing what it should with the sidetag creation... but not obvious why.
Possible it's due to none of the packages being signed, but also not sure why.
Yes, I know the datacenter move is underway and everybody is super busy. I can be patient. I did try editing the update (without actually changing anything) to see if that would shake something loose, but no luck.
Metadata Update from @patrikp: - Issue assigned to patrikp
Hello, apologies for the delay. I have manually re-tagged all of the builds into f43-updates-testing-pending, let's see if Bodhi wakes up.
f43-updates-testing-pending
Thanks for the attempt Patrik, but a full day has passed without Bodhi moving things along, I'm afraid.
I see the packages are all signed now (padlock next to them on the builds tab).
I edited it and refreshed from the side tag and it moved ahead, but now it's mad that there's some newer builds. ;(
So, I guess you need to rebuild those again and refresh the side tag?
I can do that. Thank you, Patrik and Kevin! I appreciate the help.
Well ... I built polymake overnight, then refreshed the update a couple of hours ago. It is still sitting there in the pending state. :-(
So, the builds were erroneously tagged, I've manually ran the process to apply the correct tags and the update was moved to testing, but then: This update cannot be pushed to stable. These builds python-symengine-0.14.1-4.fc43 have a more recent build in koji's f43 tag.
This update cannot be pushed to stable. These builds python-symengine-0.14.1-4.fc43 have a more recent build in koji's f43 tag.
Tarnation. This side tag has been open too long. Okay, I have built python-symengine yet again and edited the update. Fingers crossed...
Yay! That worked! Many thanks to all of you for your unfailing patience and excellent help.
Metadata Update from @patrikp: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)