Howdy, I ran into this last week and I just skipped this package. I thought maybe I caught the tree in the middle of some update or something that would be corrected by this week. Well, it's still here so it's me, not the tree. I tried setting the ruby target like it suggests but then I get a long error message about a lot of other conflicts. It seems to make the problem worse not better. Anyone know how to get around this problem??
root@fireball / # emerge -auDN world These are the packages that would be merged, in order: Calculating dependencies | !!! Problem resolving dependencies for sci-electronics/klayout from @selected ... done! Dependency resolution took 4.79 s. !!! The ebuild selected to satisfy "sci-electronics/klayout" has unmet requirements. - sci-electronics/klayout-0.28.5::gentoo USE="" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_11 -python3_10" RUBY_TARGETS="-ruby30" The following REQUIRED_USE flag constraints are unsatisfied: ruby_targets_ruby30 The above constraints are a subset of the following complete expression: exactly-one-of ( python_single_target_python3_10 python_single_target_python3_11 ) any-of ( ruby_targets_ruby30 ) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) root@fireball / # equery u sci-electronics/klayout [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for sci-electronics/klayout-0.28.5: U I - - python_single_target_python3_10 : Build for Python 3.10 only + + python_single_target_python3_11 : Build for Python 3.11 only - + ruby_targets_ruby30 : Build with MRI Ruby 3.0.x root@fireball / # By default, it has no ruby target it seems, although it used to. The on/off status changes. Setting to match the old way made it worse, as mentioned above. I can't figure out how to make this work. Any ideas? Thoughts? Dale :-) :-)
