Package: systemd
Version: 37-1.1
Severity: minor
Tags: patch
Dear Maintainer,
Found a few typos in '/usr/share/man/man5/systemd.path.5.gz'
& '/usr/share/man/man5/systemd.unit.5.gz',
see attached '.diff' files.
Hope this helps...
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii initscripts 2.88dsf-22.1
ii libacl1 2.2.51-5
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-27
ii libcap2 1:2.22-1
ii libcryptsetup4 2:1.4.1-2
ii libdbus-1-3 1.5.12-1
ii libpam0g 1.1.3-7
ii libselinux1 2.1.9-4
ii libsystemd-daemon0 44-1
ii libsystemd-login0 44-1
ii libudev0 175-3.1
ii libwrap0 7.6.q-23
ii udev 175-3.1
ii util-linux 2.20.1-4
Versions of packages systemd recommends:
ii libpam-systemd 37-1.1
Versions of packages systemd suggests:
pn python 2.7.2-10
pn systemd-gui <none>
-- no debconf information
--- systemd.path.5 2012-03-03 14:35:06.000000000 -0500
+++ /tmp/systemd.path.5 2012-04-11 03:34:53.365433806 -0400
@@ -74,7 +74,7 @@
\fIPathExists=\fR
may be used to watch the mere existence of a file or directory\&. If the file specified exists the configured unit is activated\&.
\fIPathExistsGlob=\fR
-works similar, but checks for the existance of at least one file matching the globbing pattern specified\&.
+works similar, but checks for the existence of at least one file matching the globbing pattern specified\&.
\fIPathChanged=\fR
may be used to watch a file or directory and activate the configured unit whenever it changes or is modified\&.
\fIDirectoryNotEmpty=\fR
--- systemd.unit.5 2012-03-03 14:35:06.000000000 -0500
+++ /tmp/systemd.unit.5 2012-04-11 03:37:26.539115257 -0400
@@ -79,7 +79,7 @@
.PP
If a line starts with
\fB\&.include\fR
-followed by a file name, the specified file will be parsed at this point\&. Make sure that the file that is included has the appropiate section headers before any directives\&.
+followed by a file name, the specified file will be parsed at this point\&. Make sure that the file that is included has the appropriate section headers before any directives\&.
.PP
Along with a unit file
foo\&.service
