There is 1 open security issue in forky.
There are 9 open security issues in bullseye.
There are 21 open security issues in buster.
commit 4865046d77c54e134dd6edc1105b8e6d01117af6
Author: dann frazier <dannf@debian.org>
Date: Mon Feb 16 19:59:13 2026 -0600
Add changelog entry for test flush() fix
Signed-off-by: dann frazier <dannf@debian.org>
commit 4dfefff3e2094c30127f9c37556cf2b958cf2b18
Merge: 8cb845be 73ec9e08
Author: dann frazier <dannf@debian.org>
Date: Tue Feb 17 01:57:10 2026 +0000
Merge branch 'dev-fix-tests' into 'debian/latest'
debian: python: fix caching issue with shutil.copyfileobj()
See merge request qemu-team/edk2!27
commit 73ec9e08398103b8ada31006f7e5f366943ac5a9
Author: Hector Cao <hector.cao@canonical.com>
Date: Mon Feb 16 13:07:55 2026 +0100
debian: python: fix caching issue with shutil.copyfileobj()
shutil.copyfileobj() does not guarantee to flush the data to
the dest file obj (see [1] and [2]. this behavior has been
revealed by a recent change [3] on the copefileobj() buffer
size in Python 3.14.
this behavior causes the tests to fail because recently
we add a new function (shell.p:init_shell_entry()) to add
a new boot entry for the tests (see [4]).
In Ubuntu, we are transitioning to Python 3.14 and this makes
the tests fail on EDK2 build. This will also happen in Debian
once it moves Python 3.14.
This commit makes sure we flush the data after the copefileobj
calls.
[1] https://github.com/python/cpython/issues/135648
[2] https://github.com/python/cpython/commit/34393cbdd46fd965de86f1e7bc89ab111f506723
[3] https://github.com/python/cpython/commit/6efd95c4650ec7c2fb5522b352c74a9d44370fe0
[4] https://salsa.debian.org/qemu-team/edk2/-/commit/b5a8cf7d7a26e40a068a5510c01b66c190ec5112
Among the 5 debian patches available in version 2025.11-4 of the package, we noticed the following issues:
There is 1 open security issue in trixie.
You can find information about how to handle this issue in the security team's documentation.
There are 9 open security issues in bookworm.
You can find information about how to handle these issues in the security team's documentation.