#10082 fedora 33/34 updates for shim-unsigned-x64-15.4-2.fc32
Closed: Fixed by humaton. Opened by kevin.

shim-unsigned-x64-15.4-2.fc32 is the package we want to use in f33/f34 as well as f32. However, bodhi doesn't really support this workflow.

https://bodhi.fedoraproject.org/updates/FEDORA-2021-aa625caed1 is a f32 update, but bodhi won't allow adding the same build to multiple updates.

So, proposal:

  • QA tests as much as they can
  • Since I think this fixes a approved blocker, we can land it in f34.
  • When we get the go ahead, just tag the shim-unsigned-x64-15.4-2.fc32 package into f34 and f33-updates and f32-updates (we could stagger them if desired)

This means no place to provide feedback with bodhi, but that seems the easiest way around this issue.

Thoughts?

CC @adamwill @pjones


I agree with the proposal.

Metadata Update from @mohanboddu:
- Issue tagged with: low-gain, low-trouble, ops

Is there a reason the unsigned package can't be built for all Fedora releases? It doesn't have the same constraint as regular shim does, as far as I know.

Is there a reason the unsigned package can't be built for all Fedora releases? It doesn't have the same constraint as regular shim does, as far as I know.

I think you've swapped them? The "signed" one is built from the binaries+signatures, so we can build it anywhere and get the same result, so long as the inputs are always the same. But the inputs being the same means they all need the same "unsigned" build, because our toolchain isn't able to give us the same reproducible binary across different gcc/binutils versions.

Ah, okay. Thanks for that info. :100:

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata