Bug#1134244: debsecan: dpkg-reconfigure debsecan error

mark <[email protected]> Fri, 17 Apr 2026 23:19:50 -0600
Newsgroups gmane.linux.debian.ports.amd64
Message-ID <177648959074.36243.3075070628228076122.reportbug__12174.0080810682$1776489690$gmane$org@abeja.emsquirt.com>
Package: debsecan
Version: 0.4.20.2
Severity: important
Tags: d-i
X-Debbugs-Cc: [email protected], [email protected], [email protected]
User: [email protected]
Usertags: amd64
User: [email protected]
Usertags: amd64

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

used debsecan to identify unstable security updates for installation on testing when trixie was testing. now that forky is testing, I receive error messages


-- System Information:
Debian Release: forky/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.19.11+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debsecan depends on:
ii  ca-certificates        20260223
ii  debconf [debconf-2.0]  1.5.92
ii  python3                3.13.9-3
ii  python3-apt            3.1.0

Versions of packages debsecan recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.99.1-1
ii  systemd-cron [cron-daemon]                 2.6.0-1

debsecan suggests no packages.

-- debconf information:
* debsecan/report: true
* debsecan/mailto: [email protected]
* debsecan/source:
* debsecan/suite: GENERIC