Source: systemd Version: 204-1 Severity: normal In Debian we install systemd/udev to /, not /usr. The references in the man pages (man/*.xml) all point to locations in /usr/lib where the actual location is in /lib, e.g. systemd-timedated.service.xml: <para><filename>/usr/lib/systemd/systemd-timedated</filename></para>
This is confusing for users reading the documentation. Unfortunately, we can't just simply run a sed over the man pages as a post processing step, as some ressources are actually also in /usr under Debian, e.g. tmpfiles.d.xml: <para><filename>/usr/lib/tmpfiles.d/*.conf</filename></para> I think the fix for this is to not use hard-coded locations but use the one defined in configure. My initial idea was to use xml.in and pre-process them via Makefile.am / sed. But since we already do XSL transformations, we can just use xslt to do the processing for us. I forgot the details, so I'm CCing Zbyszek here, our documentation wizard, hoping he can chime in and provide more details how to do it properly. Michael -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii initscripts 2.88dsf-43 ii libacl1 2.2.52-1 ii libaudit0 1:1.7.18-1.1 ii libc6 2.17-7 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.6.1-1 ii libdbus-1-3 1.6.12-1 ii libgcrypt11 1.5.2-3 ii libkmod2 9-3 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.3-9 ii libselinux1 2.1.13-2 ii libsystemd-daemon0 204-1 ii libsystemd-journal0 204-1 ii libudev1 204-1 ii libwrap0 7.6.q-24 ii udev 204-1 ii util-linux 2.20.1-5.5 Versions of packages systemd recommends: ii libpam-systemd 204-1 Versions of packages systemd suggests: ii systemd-ui 2-2 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
