Bug#859640: debsums: make syslog messages more explicit

Thomas Chopitea tomchop at gmail.com
Wed Apr 5 13:08:24 UTC 2017


Package: debsums
Version: 2.0.52+nmu1
Severity: wishlist

Dear Maintainer,

The syslog messages generated by debsums are not explicit enough. It would
be nice to explicitly say why logs are being written instead of just logging
the path to the binary.

e.g.

Current log line:

  Mar 31 11:52:06 HOSTNAME debsums: /usr/bin/base64

Enhanced log line:
  
  Mar 31 11:52:06 HOSTNAME debsums: CHECKSUM FAILED: /usr/bin/base64

Thanks!


-- System Information:
Debian Release: jessie/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-112-generic (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: upstart (via init_is_upstart())

Versions of packages debsums depends on:
ii  dpkg                  1.17.5ubuntu5.7
ii  libdpkg-perl          1.17.5ubuntu5.7
ii  libfile-fnmatch-perl  0.02-1build3
ii  perl                  5.18.2-2ubuntu1.1
ii  ucf                   3.0027+nmu1

debsums recommends no packages.

debsums suggests no packages.

-- no debconf information



More information about the pkg-perl-maintainers mailing list