To solve #282261 and #295029 we need sys-apps/lm_sensors-3.1.1 stabl ASAP. Those bugs are due to stabilisation of Linux 2.6.31. 3.1.1 is way older than 30 days, so please, stabilise it. And the only bug filled against it, #291326 have been closed 43 days ago.
I second the motion that this ebuild needs to be stabilized as soon as possible. lm_sensors has been neglected for some time and now that 2.6.31 is stable this issue needs attention more than ever.
*** Bug 279443 has been marked as a duplicate of this bug. ***
this is a complete listing of packages depending on lm_sensors, which need to be checked for compatibility with lm_sensors-3.1.x: app-admin/gkrellm-2.3.2:lm_sensors app-admin/gkrellm-2.3.2-r1:lm_sensors app-admin/gkrellm-2.3.4:lm_sensors gnome-extra/hardware-monitor-1.4.2:lm_sensors gnome-extra/hardware-monitor-1.4.2-r1:lm_sensors gnome-extra/sensors-applet-2.2.4:lm_sensors gnome-extra/sensors-applet-2.2.5:lm_sensors kde-base/ksysguard-4.3.3:lm_sensors kde-base/ksysguard-4.3.4:lm_sensors media-plugins/vdr-sysinfo-0.1.0a-r1 media-plugins/vdr-systeminfo-0.1.1 net-analyzer/net-snmp-5.4.2.1-r1:lm_sensors net-analyzer/net-snmp-5.4.2.1-r2:lm_sensors+kernel_linux net-analyzer/net-snmp-5.4.2.1-r3:lm_sensors+kernel_linux [B]sys-apps/i2c-tools-3.0.0 [B]sys-apps/i2c-tools-3.0.1 [B]sys-apps/i2c-tools-3.0.2 sys-apps/mondo-0.9 sys-apps/mondo-0.9a sys-power/cpufreqd-2.1.1:lm_sensors sys-power/cpufreqd-2.2.0-r2:lm_sensors sys-power/cpufreqd-2.2.1:lm_sensors sys-power/cpufreqd-2.3.4:lm_sensors sys-power/cpufreqd-2.3.4-r1:lm_sensors sys-power/cpufreqd-2.3.4-r2:lm_sensors x11-misc/xsensors-0.60 x11-plugins/wmalms-1.1.1-r1 x11-plugins/wmmsens-0.29.8 x11-plugins/wmgtemp-0.7 x11-plugins/wmsensormon-1.2.1 xfce-extra/xfce4-sensors-plugin-0.10.99.6:lm_sensors
(In reply to comment #3) > this is a complete listing of packages depending on lm_sensors, which need to > be checked for compatibility with lm_sensors-3.1.x: I would be concerned if you mean that all the packages you listed must be compatible with lm_sensors-3.1.x for it to be marked stable. Surely some responsible choices need to be made about which packages take precedence. But importantly, we are not removing 2.10.x, so if 3.1.x is incompatible with some utility, then nothing is lost, but that utility may need its dependencies updated to depend specifically on 2.10.x. Returning to my point about making responsible choices, mondo has not seen a code update since 2003, so I highly doubt (but do not rule out) its importance. media-plugins/vdr-sys* aren't quite as ancient, but I would still question their importance over lm_sensors itself. kernel-2.6.31 was marked stable even though it was incompatible with lm_sensors. ;) (I.e., we shouldn't let packages more trivial than lm_sensors itself block it from being marked stable.)
(In reply to comment #3) > this is a complete listing of packages depending on lm_sensors, which need to > be checked for compatibility with lm_sensors-3.1.x: Who shall check this ?
anybody can check this. report which versions work and which dont...
I'm pretty keen to see this stabilized, so here's a summary of the bugs it is depending on: 269057 - xsensors: New version (0.70) supports lm_sensors-3 but has not been added to the portage tree 289829 - wmalms: Masked pending removal from tree 291426 - wmgtemp: New version (in tree) reported working by Robert Cernansky 291429 - wmsensorsmon: Masked pending removal from tree 291432 - wmmsens: Masked pending removal from tree 299026 - lm_sensors: Script errors in sensors-detect? Works for me. I also tested that it works with kde-base/ksysguard and app-admin/gkrellm. From other bug reports, I see that it is supported by cpufreqd and net-snmp -- even though those bug reports are closed, maybe they should be added as blockers to this one so that they can easily be referred to? I would guess that the Gnome project are up-to-date. So the only stable package that doesn't support it is xsensors because, as I mentioned above, the maintainers haven't bumped it. Thilo, are there any other outstanding bugs or issues that are blocking this stabilization? All the documented blockers seem to be trivial or resolved.
Hallelujah! All bugs blocking this one are resolved! Can we expect to see it marked stable soon please? Thanks.
Test & stabilize: =sys-apps/lm_sensors-3.1.2: alpha amd64 ppc x86
Thanks for moving this along, Samuli!
amd64 stable
x86 stable
ppc stable
alpha stable, closing
