Package: command-not-found Version: 23.04.0-2 Severity: normal Dear Maintainer,
If obsolete package lists are present in /var/lib/apt/lists, as happens after upgrading from one release to the next, command-not-found still considers packages present in those lists as candidates. Thus on a system running Debian 13 after an upgrade from Debian 12, command-not-found neofetch points to the neofetch package even though it’s not available from any configured repository (as confirmed by apt policy). Removing the obsolete lists fixes the issue, but it would be better if command-not-found ignored them (or if apt update removed them, but that’s perhaps a tougher problem). Regards, Stephen -- System Information: Debian Release: 13.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (90, 'unstable-debug'), (90, 'testing-debug'), (90, 'unstable'), (90, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.12.63+deb13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 command-not-found depends on: ii apt-file 3.3 ii lsb-release 12.1-1 ii python3 3.13.5-1 ii python3-apt 3.0.0 command-not-found recommends no packages. Versions of packages command-not-found suggests: pn snapd <none> -- no debconf information
