<div class="gmail_quote">2009/4/4 Kai Schaetzl <span dir="ltr"><<a href="mailto:maillists@conactive.com">maillists@conactive.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I found that lm_sensors got installed because of a dependency on my first<br>
Xen VM that I updated to 5.3. lm_sensors doesn't make sense in a VM. I<br>
thought, ok let's check after the update who wants it. However:<br>
<br>
rpm -q --whatrequires lm_sensors<br>
no package requires lm_sensors<br>
<br>
(same for --triggeredby with lm_sensors or the packages below)<br>
<br>
Trying to remove lm_sensors reveals these packages:<br>
<br>
Removing:<br>
lm_sensors i386 2.10.7-4.el5 installed<br>
1.8 M<br>
Removing for dependencies:<br>
cacti noarch 0.8.7d-1.el5.rf installed<br>
5.1 M<br>
net-snmp i386 1:5.3.2.2-5.el5 installed<br>
2.8 M<br>
net-snmp-utils i386 1:5.3.2.2-5.el5 installed<br>
342 k<br>
php-snmp i386 5.1.6-23.el5 installed<br>
24 k<br>
<br>
But trying to remove any of them doesn't show a dependency on lm_sensors.<br>
<br>
How can I find out what triggered the installation of lm_sensors in the<br>
upgrade?<br>
</blockquote><div><br>rpm -q --provides lm_sensors<br>config(lm_sensors) = 2.10.7-4.el5<br>libsensors.so.3()(64bit)<br>lm_sensors = 2.10.7-4.el5<br><br>rpm -q --requires net-snmp<br><snip><br>libsensors.so.3()(64bit)<br>
<snip><br><br>requires are not always a package name...<br><br>d <br></div></div><br>