Package: munin-async
Version: 2.0.25-1
Severity: normal
Tags: patch

Dear Maintainer,

Not sure if this changed recently of if I missed that in my previous report but
the same line in munin-async.README.Debian contains another couple of typos.

 * The /usr/sbin/munin-async path is wrong, it should be 
/usr/share/munin/munin-async.

 * The second typo is more vicious. First there's two spaces before the 
'--spooldir'
   option. I'm not actually sure if that's a problem. However one of these is 
not a
   regular space! If you copy-paste the line, and even if you remove the first 
extraneous
   space you find, it does not work despite being 'obviously' correct.

I have attached a patch.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages munin-async depends on:
ii  adduser              3.113+nmu3
ii  init-system-helpers  1.23
ii  munin-common         2.0.25-1
ii  munin-node           2.0.25-1
ii  perl                 5.20.2-6
ii  perl-modules         5.20.2-6

munin-async recommends no packages.

munin-async suggests no packages.

-- no debconf information
--- debian/munin-async.README.Debian.orig	2015-09-10 23:42:19.389006958 +0200
+++ debian/munin-async.README.Debian	2015-09-10 23:43:29.744841811 +0200
@@ -83,7 +83,7 @@
 into your munin collection server, you should edit the /var/lib/munin-
 async/.ssh/authorized_keys file and add
 
-no-port-forwarding,no-agent-forwarding,no-X11-forwarding,no-pty,no-user-rc,command="/usr/sbin/munin-async  --spooldir /var/lib/munin/spool --spoolfetch"
+no-port-forwarding,no-agent-forwarding,no-X11-forwarding,no-pty,no-user-rc,command="/usr/share/munin/munin-async --spooldir /var/lib/munin/spool --spoolfetch"
 
 to the beginning of the relevant line. Additionally consider from="(remote machine IPs)".
 

Reply via email to