On 05/14/2018 04:38 PM, Carlos O'Donell wrote:
The process you describe is largely mechanical, and easy enough to
automate.
If everything is mechanical and easy to automate, why is it that the
only person regularly releasing Fedora updates is me?
Today my process is like this:
(1) Do the merge.
(2) Scratch build.
(3) Verify scratch build.
(4) Commit.
(5) Do the final build.
The ABI baseline update and merge commit both happen at (4).
Do you do a scratch build on all architectures? I don't think this is
feasible because it turns every update into a multi-day effort.
If you poll the rest of the glibc team I'd argue you find the
rest of us
are doing something very similar. I never omit (2) and (3), and if you're
going to do a scratch build, then you just do this:
(1) Do the merge.
(2) Scratch build + ABI verify mode.
(3) Verify scratch build + Verify and update ABI.
(4) Commit.
(5) Do the final build.
The number of steps are the same.
This would need something that dumps out the ABI differences in a base64
blob (similar to what we use to exfiltrate coredumps). Is this included
in your patches? I didn't see it there.
I think what you suggests requires local builds, not scratch builds in
Koji. This means that one needs to reserve a machine capable of
building the relevant Fedora branch. This is currently difficult to
automate for various reasons.
Thanks,
Florian