lm-sensors-2.7.0 is dependent of i2c-2.7.0 Reproducible: Always Steps to Reproduce: 1. 2. 3.
That's correct and the ebuid already handles it. # emerge -upv lm-sensors These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-apps/i2c-2.7.0 [ebuild N ] sys-apps/lm-sensors-2.7.0-r1
Yes, the dependency is in the ebuild file, but something has to be broken. Or how can you explain this? ============================================================ # emerge -p i2c These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-apps/i2c-2.7.0 # emerge -p lm-sensors These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-apps/lm-sensors-2.7.0-r1 ============================================================ The first time I tried to emerge lm-sensors I got an error message saying that i2c was needed to compile something, so I emerged i2c and it worked. Then I wanted to reproduce the whole problem. I unmerged lm-sensors and i2c and tried to emerge lm-sensors again. This time it worked *without* having i2c installed at all...
What does emerge -up lm-sensors think of i2c?
emerge -Dp lm-sensors which portage version ?
============================ # emerge -up lm-sensors These are the packages that I would merge, in order: Calculating dependencies ...done! # emerge -Dp lm-sensors These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-apps/lm-sensors-2.7.0-r1 ============================ portage version: 2.0.49-r3
do you use kernel 2.4 or 2.6 ?
2.4.20
I assume you're using gentoo-sources. The lm_sensors ebuild depends on i2c OR gentoo-sources (or lolo_sources or xfs-sources). I can't tell if that's correct or not. But it's not a portage bug, so I'm re-assigning it to bug-wranglers.
closing since working as expected