Debian Patches
Status for efibootguard/0.21-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 | [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 | ||
| Adapt-to-objcopy-stricter-target-checking.patch | [PATCH] Adapt to objcopy stricter target checking This fixes an build error due to: * Internal changes to plugin support, and stricter target checking may result in some errors being exposed in user options passed to the various binutils. For example objcopy --target=TARGET now will only work if the input file is for TARGET whereas prior versions of objcopy accepted other target input files and produced a TARGET output. If you do in fact want the old behaviour the correct usage is objcopy --output-target=TARGET. See also Debian bug #1122406. |
Quirin Gylstorff <quirin.gylstorff@siemens.com> | invalid | 2026-01-07 |
All known versions for source package 'efibootguard'
- 0.21-2 (sid)
- 0.21-1 (forky)
- 0.19-1 (trixie)
- 0.13-2+deb12u1 (bookworm)
