There is 1 open security issue in sid.
There is 1 open security issue in forky.
Among the 71 debian patches available in version 2.14-3 of the package, we noticed the following issues:
commit b7018e4c539bc8520beedc29957180a11fbddc86
Author: Steve McIntyre <93sam@debian.org>
Date: Sun Aug 16 19:00:33 2026 +0100
Add changelog entry
commit e9af4173b6a42ceb0cf70805b96df07fd29c26b7
Merge: dbb269fc 2f3b5590
Author: Steve McIntyre <93sam@debian.org>
Date: Sun Aug 16 17:59:48 2026 +0000
Merge branch 'debian-test' into 'master'
debian/rules: serialize package build targets
See merge request grub-team/grub!91
commit 2f3b5590da1e2f809e746d5e4f6071d3bc28ed31
Author: youwan Wang <wangyouwan@hygon.com>
Date: Mon Aug 3 11:59:50 2026 +0800
debian/rules: serialize package build targets
Build package targets one at a time from override_dh_auto_build instead of letting make schedule all build/<package> prerequisites in parallel.
Several platform builds write generated po/ and documentation files under shared source-tree directories. When those builds run concurrently, they can race and fail intermittently during dh_auto_build.
Example failure:
dh_auto_build: error: cd obj/grub-xen-i386 && make -j24 returned exit code 2
make[1]: *** [debian/rules:262: debian/stamps/build-grub-xen-i386] Error 255
commit dbb269fcfb546b516ccb9050ce9979a387909ff9
Author: Steve McIntyre <93sam@debian.org>
Date: Sun Aug 16 18:56:41 2026 +0100
Fix up changelog after accepting MR
commit 969992b177c7fab8730fb738c48af53836a77d2a
Merge: e86eb68f 189fbc7d
Author: Steve McIntyre <93sam@debian.org>
Date: Sun Aug 16 17:55:25 2026 +0000
Merge branch 'fix/powerpc-grub-emu-pks-ftbfs' into 'master'
Fix grub-emu FTBFS on 32-bit powerpc due to PKS support (Closes: #1127348)
See merge request grub-team/grub!93
commit 189fbc7da34f185db7fba1475fcd3ce2cb245f96
Author: Trupti Shirsat <trupti@linux.ibm.com>
Date: Wed Aug 5 13:10:36 2026 -0500
debian/patches: Fix grub-emu FTBFS on 32-bit powerpc due to PKS support (Closes: #1127348)
There are 8 open security issues in trixie.
You can find information about how to handle these issues in the security team's documentation.
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.