On Tue, Mar 17, 2009 at 12:02:47PM -0700, Ross Boylan wrote: > On Tue, 2009-03-17 at 09:32 +0100, Aurelien Jarno wrote: > > Ross Boylan a écrit : > ... > > > Would it be possible not to create sensor.conf for new installs? I have > > > a brand new Lenny system and added lm-sensors and sensord (and > > > dependencies and suggestions). If this was all v3, why did it create > > > sensors.conf? Actually, I'm assuming they created it; maybe it was > > > already there. > > > > /etc/sensor.conf is created because you have installed an application > > still using the old version 2 of the library, that is libsensors3 (as > > opposed to version 3 called libsensors4). Doing an install of the Lenny > > without those applications does not create /etc/sensors.conf. > > > The reverse dependencies on libsensors3 indicate libsnmp15 is the package > pulling > the old stuff in on my machine. > > Should I (or you) file a wish against that package to switch > dependencies? Quite a few other packages also depend on the old lib.
The problem is that the API is not compatible, so it's more than just switching the dependencies. Most of the packages depending on the old library and with a patch available already have a bug open. The goal is to get rid of libsensors3 in squeeze, I plan to do NMU of the remaining packages a few months before the freeze. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
