Package: sensord
Version: 1:3.1.2-2
Severity: minor

root:~$ apt-get install sensord; uname -s
[...]
Setting up librrd4 (1.3.8-1) ...
Setting up fancontrol (1:3.1.2-2) ...
Setting up lm-sensors (1:3.1.2-2) ...
Setting up sensord (1:3.1.2-2) ...
Starting sensor daemon: sensordError loading default configuration file: Kernel 
interface error
 failed!
GNU/kFreeBSD

This is obviously a candidate for "don't do that then", given the
clue buried in the name "Linux Monitoring sensors"... but then again
note the presence of "lsb-base" in the dependencies below.

The Architecture: fields of one or more of the packages in the
family need to be adjusted to mark sensord as Linux-only; you'll
have a better idea than I do of what the approved method is when
they're a mix of "any" and "all".  But by the way, while you're
adjusting that control file, would you mind changing the short
description for fancontrol?  At present it claims to have exactly
the same functionality as lm-sensors, and in this case I can easily
see how you'd fix it - something like this:

-Description: utilities to read temperature/voltage/fan sensors
+Description: fan speed control daemon

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: kfreebsd-i386 (i686)

Kernel: kFreeBSD 8.0-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sensord depends on:
ii  libc0.1                       2.10.2-2   GNU C Library: Shared libraries
ii  librrd4                       1.3.8-1    Time-series data storage and displ
ii  libsensors4                   1:3.1.2-2  library to read temperature/voltag
ii  lm-sensors                    1:3.1.2-2  utilities to read temperature/volt
ii  lsb-base                      3.2-23     Linux Standard Base 3.2 init scrip

sensord recommends no packages.

sensord suggests no packages.

-- no debconf information
-- 
JBR
Ankh kak! (Ancient Egyptian blessing)



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

Reply via email to