Re: i2c and lm-sensors mess (it works)
I have made some test yesterday, and since then I am using my computer
with a 2.4 kernel, 2.7.0 i2c and lm-sensors modules, and applications
using libsensors2 or libsensors3. So the solution works !
I have made some packages, splitting lm-sensors:
- i2c, version 2.7.0 building:
- lm-sensors, version 2.8.4 (with sysfs support) building:
- lm-sensors-old, version 2.7.0 building:
Both i2c and lm-sensors-old doesn't build modules for 2.6 kernels, as
the modules are already included in the kernel.
The packages are available on http://people.debian.org/~aurel32/i2c-lmsensors
So here is my proposal for the next days:
1) Get the approval of David Maze to upload such modules. David, please
don't hesitate to refuse such packages. You're maintaining
i2c/lm-sensors for years, you better know them than me.
2) Upload i2c, lm-sensors and lm-sensors-old. Both lm-sensors and
lm-sensors-old need manual override. Maybe we could have the help of
ftpmasters to get higher priority on this packages, as we need to
have i2c/lm-sensors support in Sarge.
3) Ask for removal of old packages:
i2c-2.4.20-3-386, i2c-2.4.20-3-586tsc, i2c-2.4.20-3-686,
i2c-2.4.20-3-686-smp, i2c-2.4.20-3-k6, i2c-2.4.20-3-k7,
4) File bugs to get all applications linked to libsensors2 to be rebuilt
against latest version of lm-sensors, so they will depends on
* kdebase ??? (reenable support of sensors in ksysguard)
5) Ask for removal of libsensors2 from Sid
6) When all packages have moved to Sarge, ask for removal of libsensors1
Please give me your opinions about all of that.
.''`. Aurelien Jarno GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineering Student
`. `' firstname.lastname@example.org | email@example.com
`- people.debian.org/~aurel32 | www.aurel32.net