When I tried to install sys-apps/lm_sensors-2.10.7 with "sensord" use flag, emerge wants to install net-analyzer/rrdtool too, which in turn wants to install x11-libs/cairo. Installing any x11-libs on a server is unnecessary risk! # echo "sys-apps/lm_sensors sensord" >> /etc/portage/package.use # emerge --pretend lm_sensors These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds built with USE flags to satisfy ">=x11-libs/cairo-1.4.6[svg]". !!! One of the following packages is required to complete your request: - x11-libs/cairo-1.8.6-r1 (Change USE: +svg) (dependency required by "net-analyzer/rrdtool-1.3.8" [ebuild]) (dependency required by "sys-apps/lm_sensors-2.10.7" [ebuild]) (dependency required by "lm_sensors" [argument]) -------- # man sensord DESCRIPTION Sensord is a daemon that can be used to periodically log sensor readings from hardware health-monitoring chips to syslog(3) or a round-robin database (RRD) and to alert when a sensor alarm is signalled; for example, if a fan fails, a temperature limit is exceeded, etc. -------- If someone wants to store output from sensord in syslog, there is no reason to install rrdtool. I think in such a case rrdtool (as well as cairo) is not necessary. Reproducible: Always Steps to Reproduce: 1. # echo "sys-apps/lm_sensors sensord" >> /etc/portage/package.use 2. # emerge --pretend lm_sensors Actual Results: with sys-apps/lm_sensors, net-analyzer/rrdtool and x11-libs/cairo as dependency want to be installed Expected Results: sys-apps/lm_sensors should install without net-analyzer/rrdtool
fixed for 3.1.1 which just now has hit the tree. thanks for the report.
(In reply to comment #1) > fixed for 3.1.1 which just now has hit the tree. > thanks for the report. Not fixed in 3.1.1, still the same: obelix ~ # echo "sys-apps/lm_sensors ~amd64" >> /etc/portage/package.keywords obelix ~ # echo "sys-apps/lm_sensors sensord" >> /etc/portage/package.use obelix ~ # emerge --pretend lm_sensors These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds built with USE flags to satisfy ">=x11-libs/cairo-1.4.6[svg]". !!! One of the following packages is required to complete your request: - x11-libs/cairo-1.8.8 (Change USE: +svg) (dependency required by "net-analyzer/rrdtool-1.3.8" [ebuild]) (dependency required by "sys-apps/lm_sensors-3.1.1" [ebuild]) (dependency required by "lm_sensors" [argument]) When I remove that sensord flag, all seems to be OK, and nothing wants to be emerged with lm_sensors as dependency. But I definitely need "sensord" (what is lm_sensor good for without monitoring?) and it should NOT be obligatory to have round-robin database or cairo vector graphics library installed, as sensord can send output to syslog too... I suggest adding "rrdtool" use flag to lm_sensors (this use flag is already used with other packages): If someone wants to have output from sensord in RRD, he can emerge it. But if someone wants just to have output written to syslog, there is no need to have RRD (or X11/Cairo)...
ahh - sorry. i misread the bug. sensord's README explicitly states that rrdtool is required. i have no plans of ripping that out. you are, of course, free to supply a patch to upstream. you could also bug the rrdtool maintainer, and ask for a rrdtool version which can only log data and not draw anything, however i dont know if that is a reasonable request. sorry!
man sensord: ----------------- OPTIONS: -r, --rrd-file file: Specify a round-robin database into which to log all sensor readings; e.g., `/var/log/sensord.rrd'. This database will be created if it does not exist. By default, no round-robin database is used. ----------------- As manual page says redirecting output to RRD is just an option, which is not even used in default installation. But you are right, /prog/sensord/README says rrdtool development headers and libraries are required (maybe just for compilation)... But when I add that svg-flag for cairo, I get this long list of packages which want to be installed with lm_sensors (just because I selected "sensord" use flag): obelix portage # emerge --pretend lm_sensors These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] media-libs/freetype-2.3.9-r1 USE="-X -bindist -debug -doc -fontforge -utils" [ebuild NS ] sys-devel/automake-1.9.6-r2 [1.10.2] [ebuild N ] media-libs/libpng-1.2.40 [ebuild N ] dev-perl/XML-Parser-2.36 [ebuild N ] x11-misc/util-macros-1.3.0 [ebuild N ] dev-util/intltool-0.40.5 [ebuild N ] x11-libs/pixman-0.17.2 USE="mmx sse2 (-altivec) -debug" [ebuild N ] media-libs/fontconfig-2.6.0-r2 USE="-doc" [ebuild N ] app-admin/eselect-fontconfig-1.0 [ebuild N ] x11-libs/cairo-1.8.8 USE="svg -X (-aqua) -cleartype -debug -directfb -doc -glitz -opengl -xcb" [ebuild N ] x11-libs/pango-1.24.5-r1 USE="-X -debug -doc -test" [ebuild N ] net-analyzer/rrdtool-1.3.8 USE="nls perl python -doc -rrdcgi -ruby -tcl" [ebuild N ] sys-apps/lm_sensors-3.1.1 USE="sensord" It is unacceptable to have all this X-stuff installed on server just because I want to monitor sensors with daemon. This makes lm_sensors actually unusable on servers...
i do agree with you. the current situation is not very nice.
(In reply to comment #4) > man sensord: > ----------------- > OPTIONS: > -r, --rrd-file file: Specify a round-robin database into which to log all > sensor readings; e.g., `/var/log/sensord.rrd'. This database will be created if > it does not exist. By default, no round-robin database is used. > ----------------- > > As manual page says redirecting output to RRD is just an option, which is not > even used in default installation. But you are right, /prog/sensord/README says > rrdtool development headers and libraries are required (maybe just for > compilation)... > > But when I add that svg-flag for cairo, I get this long list of packages which > want to be installed with lm_sensors (just because I selected "sensord" use > flag): > > obelix portage # emerge --pretend lm_sensors > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild N ] media-libs/freetype-2.3.9-r1 USE="-X -bindist -debug -doc > -fontforge -utils" > [ebuild NS ] sys-devel/automake-1.9.6-r2 [1.10.2] > [ebuild N ] media-libs/libpng-1.2.40 > [ebuild N ] dev-perl/XML-Parser-2.36 > [ebuild N ] x11-misc/util-macros-1.3.0 > [ebuild N ] dev-util/intltool-0.40.5 > [ebuild N ] x11-libs/pixman-0.17.2 USE="mmx sse2 (-altivec) -debug" > [ebuild N ] media-libs/fontconfig-2.6.0-r2 USE="-doc" > [ebuild N ] app-admin/eselect-fontconfig-1.0 > [ebuild N ] x11-libs/cairo-1.8.8 USE="svg -X (-aqua) -cleartype -debug > -directfb -doc -glitz -opengl -xcb" > [ebuild N ] x11-libs/pango-1.24.5-r1 USE="-X -debug -doc -test" > [ebuild N ] net-analyzer/rrdtool-1.3.8 USE="nls perl python -doc -rrdcgi > -ruby -tcl" > [ebuild N ] sys-apps/lm_sensors-3.1.1 USE="sensord" > > It is unacceptable to have all this X-stuff installed on server just because I > want to monitor sensors with daemon. This makes lm_sensors actually unusable on > servers... What X-stuff? I don't see a single package in that list that is X11, except util-macros which just bunch of .m4 files for running autotools on some of the above packages.
Also from upstream file prog/sensord/Module.mk: # The round robin database (RRD) development headers and libraries are # REQUIRED. Get this package from: # http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/ So closed as WONTFIX for now while waiting for patch, that has also been accepted into upstream: http://www.lm-sensors.org/report
