On Tue, Jul 30, 2019 at 11:11:34AM -0700, Kevin Fenzi wrote:
In this case it's koji.
For every package in the mass rebuild (f31-pending tag) robosign asks
koji "hey, is foobar-1.0.1-1.fc31 signed' ? koji checks... "yes, it
is".
robosign: "great, then I ask you to write out the signed rpms now"
koji: "ok, writing them out to disk again"
it's mostly this last step thats slow. I am not sure if koji is just
seeing if they were written out and returning, or actually re-writing
them out. It seems like it might be the latter, which makes me suspect
koji could optimize this somewhat.
It's still taking a long time today to get builds through Koji and
into Rawhide. Is there a reason we need to sign builds in Rawhide?
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/