Your message dated Sat, 26 Apr 2014 19:54:05 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-systemd-maintainers] Bug#719634: Bug#719634:
Bug#719634: dh-systemd: Support of /usr/lib/systemd/system
has caused the Debian Bug report #719634,
regarding dh-systemd: Support of /usr/lib/systemd/system
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
719634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719634
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dh-systemd
Version: 1.8
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi!
I have already discussed this with Michael S. who told me that unit
files should be shipped in /lib/systemd/system. However, systemd also
accepts /usr/lib/systemd/system as a valid path. I don't find anything
saying that the use of /usr/lib/systemd/system is discouraged.
There is at least one package shipping systemd unit file in
/usr/lib/systemd/system (ExaBGP). This can be corrected if this
location is really discouraged (I would ask upstream to correct
that). Also, for an autotools package, it is easier to ship files in
/usr than outside.
What do you think?
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dh-systemd depends on:
ii debhelper 9.20130630
ii perl 5.14.2-21
dh-systemd recommends no packages.
dh-systemd suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQIcBAEBCAAGBQJSCoCLAAoJEJWkL+g1NSX5kFUP/1wgnw8PQezC8PDbv4MvKeEv
FdmVFClpjpAiC4lwfwEMtHzpo0zakE8f1rjCewtQRPJtHtBnh8FmatTsBu3dXRUz
R/MFHfw9JATaLKHDLPTWWf2FadAYAy7cAIgYQOJO/ty8H7Qfmg+GgXIH4ZN1is10
wzzkAls6Odvaw7Mhv6Q7faFeKVr808w+DIt8/TAq7mVVzJuV97+NLjkuK6sayrVQ
n/cvNOqE6ICbT0sSVL17soHFTOxqTO2n3i1kYE8ZE3My+a5ulZJpoLTX9g+QURQ0
J7orE++3rT+Iw6wdJaHFIuYnNqASJ9kzko2I6tm5+A42URnOLvoGenHhp3+yEbhD
VzUnNxAGUtIq5x34xW36NZgplCbrdhtuAnZS5JnupAGQfnrmdPx0XylfXHo/ZTbo
JhWO8GHjlTcw3CLK5Xn/Z9uU8ZRqXjq7+bR87iEhZe+v1AE9eYEauShcE/nABLVk
3x/cLgA+3Sr9NkcMeqU7T3d6JQwp5jeFu4J3XY3sHkVQBQ3XYkwUl/k2awgxo/OC
8Yv8UBZOfW6ihMZtsnk6lUNCSsej8L1503dDnjWX0qqA651LAE5t1TRalEOzCNg7
AUNLIhnQNdZah4q4zIfPrjokptwJijAFJPFAmN4IY3qDeWHTb1W7Z6epBzVDPjHy
u8t8HfElLyymxqrjz8zM
=WJ6T
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi Vincent,
Vincent Bernat <[email protected]> writes:
>> systemd even ships a configure.ac snippet for that, hoping to achieve
>> some consistency among projects
>
> Oh, good to know. Thanks for the pointer.
Sorry for replying late, but now we’re bug-scrubbing :).
I’m closing this one since nobody is going to work on the original
symptom and a clean fix was provided by Michael Biebl instead. I
consider this fixed.
--
Best regards,
Michael
--- End Message ---
