after sync the i2c package shows up as NEW package. Since im using a 2.6.x kernel - im using the kernel supplied modules. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Do you have lm_sensors installed?
Yes, I have had version 2.9.0 installed for some time - never had to install the i2c package.
(In reply to comment #2) > Yes, I have had version 2.9.0 installed for some time - never had to install > the i2c package. You did because it was a "dependency" - though i2c actually installed nothing when kernel 2.6 was detected. Just run emerge -Cav i2c and you'll see (and fix it). I will assign this bug to maintainer since now portage installs lm_sensors-2.9.1 slotted (why?) and i2c "upgrade" now actually fails with 2.6 kernels. I think this should be handled better.
cool, that worked nice. Thanks for helping me.
Just some more feedback: einfo in 2.9.1 ebuild should IMHO say more explicitly that you really need to run sensors-detect even if you are just upgrading. Previous /etc/conf.d/lm_sensors configuration won
Just some more feedback: einfo in 2.9.1 ebuild should IMHO say more explicitly that you really need to run sensors-detect even if you are just upgrading. Previous /etc/conf.d/lm_sensors configuration won´t work due to missing LOADMODULES and INITSENSORS lines. Maybe the init script should say this instead of exiting silently if those lines are missing, it is a little confusing. Oh, and thanks for the new sensord use flag, really nifty feature. ;-)
I have removed the SLOT from the earlier versions as well, and added instructions about running sensors-detect even if upgrading now. Jakub: how, in your opinion, could this have been handled better? The old behavior was broken, and there was really no easy way to make the migration to a non-broken setup... at least as I see it. Closing as INVALID since the original issue was not a bug.
(In reply to comment #6) > I have removed the SLOT from the earlier versions as well, and added > instructions about running sensors-detect even if upgrading now. Thanks. > Jakub: how, in your opinion, could this have been handled better? Well, I
(In reply to comment #6) > I have removed the SLOT from the earlier versions as well, and added > instructions about running sensors-detect even if upgrading now. Thanks. > Jakub: how, in your opinion, could this have been handled better? Well, I´m not sure. Maybe the ebuild should force the users to unmerge i2c first when upgrading (which would prevent i2c upgrade to fail later on) but it depends on your opinion. No easy solution here.
That would an ugly hack - and it would be an unnecessary evil for people still running kernel 2.4.x. I'd hate to introduce another ugly hack just to get rid of the old 'install nothing for kernel 2.6.x hack' - the good news is, that this time it was done 'right'. Should you, or anybody else, come up with a better solution for migrating from <=2.9.0 to 2.9.1, please do not hessitate to contact me - we can still get that into the package before it is marked stable.
