Debian Patches
Status for efibootguard/0.22-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Do-not-use-ld-fatal-warnings.patch | Do not use ld fatal-warnings fatal-warnings are almost guaranteed to break the build when using a more recent linker than the upstream developers. Get rid of them so the package can be built with some warnings and be maintained sanely in the long run. |
Bastian Germann <bage@debian.org> | not-needed | 2024-05-07 | ||
| Prevent-reading-version-from-git.patch | Prevent reading version from git | Bastian Germann <bage@debian.org> | not-needed | 2021-12-07 | ||
| always-override-stack-protector-variables-in-EFI-bui.patch | always override stack-protector variables in EFI build These flags require libc support which we do not have in the EFI part. As distro builders inject the hardening flags into CFLAGS, which is fine for the userspace part, but for EFI we need to override it. |
Felix Moessbauer <felix.moessbauer@siemens.com> | not-needed | 2023-11-13 | ||
| multi-arch.patch | add option to use pkg-config instead of hardcode path to /usr/lib This fixes debian bug #1125737. |
Quirin Gylstorff <quirin.gylstorff@siemens.com> | invalid | |||
| use-objcopy-for-riscv64-with-gnu-efi-4.0.patch | use objcopy for riscv64 with gnu-efi >= 4.0 With gnu-efi >= 4.0 the binary copy no longer works as it leads to non working efi binaries. The binaries are from type data instead of PE32+ executable for EFI. This can be check with the command `file <path to the efibootguard binary>` This fixes Debian bug 1130324 [1]. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1130324 |
Quirin Gylstorff <quirin.gylstorff@siemens.com> | no | 2026-06-08 |
All known versions for source package 'efibootguard'
- 0.22-2 (sid, forky)
- 0.19-1 (trixie)
- 0.13-2+deb12u1 (bookworm)
