Learn more about these different git repos.
Other Git URLs
There was an issue with non-latest version of libuv-1.39.0-1.fc32 got tagged into f32-updates tag and I fixed it and the next compose failed due to missing signs due to koji gc, so I wrote the signed rpms back (koji write-signed-rpm) and ran the compose which successfully completed but it used the unsigned rpm of libuv-1.40.0-1.fc32 and caused problems for users.
libuv-1.39.0-1.fc32
(koji write-signed-rpm)
libuv-1.40.0-1.fc32
We ran next compose without doing anything and it seems to have fixed it.
At this point, that only thing that I can think of the 06.1 compose might have used somthing in 06.0 and caused this issue, but I am not sure.
This is a problem with reusing results from previous compose. There is a known issue when whitelists or inheritance changes, and apparently the signed packages are a similar case. On next run there will be different koji event, and that will block the reuse.
Alternatively Bodhi should add pkgset_allow_reuse = False to the config. The feature can't really help in there, as the builds are changing for every run. It's really only useful for modules (where builds in the same tag rarely change).
pkgset_allow_reuse = False
That being said, this is still something that should be fixed in Pungi.
ok. I am setting 'pkgset_allow_reuse = False' in the bodhi updates pushes config. :)
Commit 49a5661 fixes this issue
Metadata Update from @onosek: - Issue set to the milestone: 4.2.8
Login to comment on this ticket.