Bug#1116965: dlocate relies on /var/lib/dpkg/available, unavailable on trixie and newer systems

Source: dlocate
Version: 1.17
Severity: grave
X-Debbugs-Cc: [email protected]

Hi,

on a fresh trixie install, /etc/cron.daily/dlocate will fail every day with
following email:

/etc/cron.daily/dlocate:
grep-available: /var/lib/dpkg/available: No such file or directory

The call chain is:
/etc/cron.daily/dlocate -> /usr/sbin/update-dlocatedb -> /usr/share/dlocate/update-dpkg-list

This file doesn't seem to be created on trixie systems, and on my upgraded
systems /var/lib/dpkg/available seems to be at least 5 years old. It seems to
have been created in the past with `dpkg --update-avail`, dlocate should ensure
this is being called and the file is current before depending on the existence
of the file.

I've set the severity to grave, since AFAICS this will cause dlocate to either
not work or work with several years old stale data.

Greets,
Lee

-- System Information:
Debian Release: 13.1
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'proposed-updates'), (990, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.43+deb13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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