Bug#838931: repro: logrotate script fails if repro is not running

[Gard Spreemann]

Package: repro
Version: 1:1.9.7-5
Severity: normal

Dear Maintainer,

The logrotate script for repro uses start-stop-daemon in its
postrotate in a way that makes it exit with status 1 if repro is not
running. This can cause needless e-mails to be sent to the
administrator of the system if repro is installed but deliberately not
running, or if the package has been removed with configuration files
kept in place.

I do not know what the most appropriate way to fix this is, but it
seems that adding --oknodo to start-stop-daemon in repro's logrotate
script will work.

Best,
Gard Spreemann

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)