X-Debbugs-Cc: raph...@offensive-security.com Package: lintian-brush Version: 0.101 Severity: minor
Raphael writes: > I noticed a case where lintian-brush drops a > .maintscript file: > https://janitor.kali.org/cupboard/pkg/hashcat-utils/059988c9-7de0-454a-9ed5-99381ae399a6/ >* > The commit message just says that it's "obsolete". How does it decide > that it's obsolete? Does it link the version with a date through the > changelog? In any case, it would be great if the commit message explained > how the tool came to this conclusion... Ideally, ancient-maintscript-entry should list when the last version was for which the maintscript entry was relevant and when it was uploaded. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-4-amd64 (SMP w/2 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian-brush depends on: ii devscripts 2.21.1 ii python3 3.9.2-2 ii python3-breezy 3.1.0-8 ii python3-debian 0.1.39 ii python3-debmutate 0.27 ii python3-distro-info 1.0 ii python3-dulwich 0.20.15-1 ii python3-iniparse 0.4-3 ii python3-ruamel.yaml 0.16.12-2 ii python3-upstream-ontologist 0.1.14-1 Versions of packages lintian-brush recommends: ii decopy 0.2.4.4-0.1 ii dos2unix 7.4.1-1 ii gpg 2.2.27-1 ii libdebhelper-perl 13.3.4 ii lintian 2.104.0 ii ognibuild 0.0.2-1 ii python3-asyncpg 0.21.0-1+b2 ii python3-bs4 4.9.3-1 ii python3-docutils 0.16+dfsg-3 ii python3-levenshtein 0.12.2-1 ii python3-lxml 4.6.3-1 ii python3-markdown 3.3.4-1 ii python3-pyinotify 0.9.6-1.3 Versions of packages lintian-brush suggests: pn breezy-debian <none> pn gnome-pkg-tools <none> ii po-debconf 1.0.21+nmu1 ii postgresql-common 225 -- no debconf information
