commit 1fb00ac1c97fe3f021613dd606d2194707f73481 Author: Mo Zhou <firstname.lastname@example.org> Date: Sat Nov 25 16:00:42 2023 -0500 Remove patches merged upstream, and quilt refresh the remaining ones. commit 683991dcbe002295c3ecfef05a465d0ce8ff4841 Author: Mo Zhou <email@example.com> Date: Sat Nov 25 15:52:29 2023 -0500 gbp-dch: update commit a2cf4616ad1030c868958d961d86ccd259135eac Merge: 514cbbaf 9810de80 Author: Mo Zhou <firstname.lastname@example.org> Date: Sat Nov 25 15:51:48 2023 -0500 Update upstream source from tag 'upstream/3.12.0' Update to upstream version '3.12.0' with Debian dir 8c01cae00ad7f07221e559ebd889d9351ff22d25 commit 9810de808b386df2cac04b89fbdd425436ac394a Author: Mo Zhou <email@example.com> Date: Sat Nov 25 15:51:26 2023 -0500 New upstream version 3.12.0 commit 514cbbaf5724a53a319c94e92d58bb977f1a261d Author: Sébastien Villemot <firstname.lastname@example.org> Date: Sun Nov 27 17:27:54 2022 +0100 Mark patch as applied upstream Gbp-Dch: Ignore
There is 1 open security issue in bullseye.
You can find information about how to handle this issue in the security team's documentation.
Among the 5 debian patches available in version 3.11.0-2 of the package, we noticed the following issues: