Your message dated Sun, 12 Jul 2026 17:22:04 +0000
with message-id <[email protected]>
and subject line Bug#1137728: fixed in linux-vulnerability-mitigation 20260629-2
has caused the Debian Bug report #1137728,
regarding linux-vulnerability-mitigation: fails to cleanly install, if manual
mode is chosen
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1137728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137728
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-vulnerability-mitigation
Version: 20260519.1-1
Severity: important
Tags: security
X-Debbugs-Cc: [email protected], Debian Security Team
<[email protected]>
Hello there!
Firstoff, thanks for creating and maintaining this useful package.
Really appreciated.
I installed it on one box some versions ago and I decided to test it on other
boxes, as well.
However, I have just found that linux-vulnerability-mitigation/20260519.1-1
(currently in Debian unstable) fails to cleanly install, if I choose the
manual mode to select mitigations:
# aptitude install linux-vulnerability-mitigation
The following NEW packages will be installed:
linux-vulnerability-mitigation
[...]
Preconfiguring packages ...
find: ‘/usr/share/linux-vulnerability-mitigation/mitigations’: No such file
or directory
Selecting previously unselected package linux-vulnerability-mitigation.
[...]
A debconf dialog appears and asks the user to choose a method to select
mitigations. If I choose "manual", the following happens:
Usage: linux-vulnerability-mitigation install
-m|--mitigation={MITIGATION|MITIGATION1,MITIGATION2,...|ALL}
See linux-vulnerability-mitigation-install(1),
linux-vulnerability-mitigation(1) and linux-vulnerability-mitigation(7) for
more information.
dpkg: error processing package linux-vulnerability-mitigation (--configure):
old linux-vulnerability-mitigation package postinst maintainer script
subprocess failed with exit status 1
Processing triggers for man-db (2.13.1-1)…
Errors were encountered while processing:
linux-vulnerability-mitigation
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up linux-vulnerability-mitigation (20260519.1-1)…
Usage: linux-vulnerability-mitigation install
-m|--mitigation={MITIGATION|MITIGATION1,MITIGATION2,...|ALL}
See linux-vulnerability-mitigation-install(1),
linux-vulnerability-mitigation(1) and linux-vulnerability-mitigation(7) for
more information.
dpkg: error processing package linux-vulnerability-mitigation (--configure):
old linux-vulnerability-mitigation package postinst maintainer script
subprocess failed with exit status 1
Errors were encountered while processing:
linux-vulnerability-mitigation
After purging the package, I tried to install it again, but this time I chose
"none".
The installation succeeded.
But, needless to say, there was no debconf dialog to manually select the
mitigations.
I could however manually install the mitigations I needed with:
$ linux-vulnerability-mitigation check
$ linux-vulnerability-mitigation status
# linux-vulnerability-mitigation install -m CVE-2026-43494
Maybe I will stick to the "none" mode and manage mitigations with the
above commands.
But I think the "manual" mode should be fixed (or dropped entirely).
Please fix this bug.
Thanks for your time and dedication!
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 7.0.9+deb14-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-vulnerability-mitigation depends on:
ii debconf [debconf-2.0] 1.5.92
linux-vulnerability-mitigation recommends no packages.
Versions of packages linux-vulnerability-mitigation suggests:
ii bash-completion 1:2.16.0-8
-- debconf information:
* linux-vulnerability-mitigation/mitigations:
linux-vulnerability-mitigation/title:
* linux-vulnerability-mitigation/mode: none
--- End Message ---
--- Begin Message ---
Source: linux-vulnerability-mitigation
Source-Version: 20260629-2
Done: Daniel Baumann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
linux-vulnerability-mitigation, which is due to be installed in the Debian FTP
archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Baumann <[email protected]> (supplier of updated
linux-vulnerability-mitigation package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 12 Jul 2026 18:55:08 +0200
Source: linux-vulnerability-mitigation
Architecture: source
Version: 20260629-2
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <[email protected]>
Changed-By: Daniel Baumann <[email protected]>
Closes: 1137728 1139678 1139708 1140684
Changes:
linux-vulnerability-mitigation (20260629-2) sid; urgency=medium
.
* Adding updated Catalan debconf translations from Carles Pina i Estany
<[email protected]> (Closes: #1139678).
* Adding updated German debconf translations from Helge Kreutzmann
<[email protected]> (Closes: #1139708).
* Adding updated Dutch debconf translations from Frans Spiesschaert
<[email protected]> (Closes: #1140684).
* Don't fail on empty manual mitigations, thanks to Francesco Poli
(wintermute) <[email protected]> for reporting (Closes:
#1137728).
Checksums-Sha1:
ccc2710ef787b5667e3f7f40a3dd03346dff9e4e 1491
linux-vulnerability-mitigation_20260629-2.dsc
2b60d589c7e5dd7a68c6686e26baa6b2f3f9662f 7260
linux-vulnerability-mitigation_20260629-2.debian.tar.xz
f73083212be494ee51da4271fcd6b7555f9422c9 5812
linux-vulnerability-mitigation_20260629-2_amd64.buildinfo
Checksums-Sha256:
ab91dcc4c9c79a0821857b2aa492adf76565a307166dec5f7d80fe532c286336 1491
linux-vulnerability-mitigation_20260629-2.dsc
b2eb53f2c315978961123c542cb0ed9f90a1aed6f4f1ab5e51cadbb33c853b50 7260
linux-vulnerability-mitigation_20260629-2.debian.tar.xz
4cc82ccc27402580b0792163147415315c690cb1f0baf1b7bf69f9c0ce560a7f 5812
linux-vulnerability-mitigation_20260629-2_amd64.buildinfo
Files:
8a8415c7a83bcba7d3ca9e9d08d197e9 1491 admin optional
linux-vulnerability-mitigation_20260629-2.dsc
23cad085f9204e76b6bc966d22a46dbf 7260 admin optional
linux-vulnerability-mitigation_20260629-2.debian.tar.xz
39673316249b00b5d3fe39f25d3861cf 5812 admin optional
linux-vulnerability-mitigation_20260629-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQQmmGg4gLaoSj0ERgL7tPDoCoAiLwUCalPHLwAKCRD7tPDoCoAi
LwA2AP9/vXdgVcKQC9YnJu3Sx4FF6yh0nvrUiUFSIrMtQTC1ygEAmflNYb3BZEs6
5tke/KxWSKeHQxRnRMzmARCMxOH8GAA=
=N6FQ
-----END PGP SIGNATURE-----
pgpUxrD_qQ0m5.pgp
Description: PGP signature
--- End Message ---
