Package: systemd
Version: 44-2
Severity: minor

Dear Maintainer,

I think this is just a cosmetic bug. I'm not sure from reading LSB whether "+" is allowed in LSB headers or not. If it's not, feel free to reassign to the package tacacs_plus.

After installing tacacs_plus the following message appears in syslog on
every daemon-reload. I'm not seeing any other problems so it might be
just a cosmetic issue, but one side is not adhering to LSB specs
apparently.

Jun 11 12:45:39 ops02 systemd[1]: Reloading.
Jun 11 12:45:39 ops02 systemd[1]: [/etc/init.d/tacacs_plus:3] Failed to add LSB Provides name tacacs+.service, ignoring: Invalid argument

root@ops02:/# grep Provides /etc/init.d/tacacs_plus
# Provides:          tacacs+

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  dpkg                 1.16.3
ii  initscripts          2.88dsf-22.1
ii  libacl1              2.2.51-7
ii  libaudit0            1:1.7.18-1.1
ii  libc6                2.13-33
ii  libcap2              1:2.22-1
ii  libcryptsetup4       2:1.4.3-1
ii  libdbus-1-3          1.6.0-1
ii  libkmod2             8-2
ii  liblzma5             5.1.1alpha+20110809-3
ii  libpam0g             1.1.3-7.1
ii  libselinux1          2.1.9-2
ii  libsystemd-daemon0   44-2
ii  libsystemd-id128-0   44-2
ii  libsystemd-journal0  44-2
ii  libsystemd-login0    44-2
ii  libudev0             175-3.1
ii  libwrap0             7.6.q-23
ii  udev                 175-3.1
ii  util-linux           2.20.1-5

Versions of packages systemd recommends:
ii  libpam-systemd  44-2

Versions of packages systemd suggests:
ii  python        2.7.2-10
pn  python-cairo  <none>
pn  python-dbus   <none>
pn  systemd-gui   <none>

-- no debconf information



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to