1 |
On 2022.10.11 17:43, Neil Bothwick wrote: |
2 |
> On Tue, 11 Oct 2022 16:02:52 -0400, Jack wrote: |
3 |
> |
4 |
> > For example, "emerge -1 dev-ruby/thor" gives me |
5 |
> > |
6 |
>> !!! Problem resolving dependencies for dev-ruby/thor ... done! |
7 |
> > |
8 |
>> !!! The ebuild selected to satisfy "dev-ruby/thor" has unmet |
9 |
>> requirements. |
10 |
>> - dev-ruby/thor-1.2.1::gentoo USE="-doc -test" ABI_X86="(64)" |
11 |
>> RUBY_TARGETS="-ruby27 (-ruby30) (-ruby31)" |
12 |
> |
13 |
> ruby30 and ruby31 are in parentheses, which means they are not |
14 |
> available. |
15 |
Given everything below - what other reasons might there be for this? |
16 |
I've yet to find any pattern of the difference between the ebuilds for |
17 |
the small number of dev-ruby packages that show this problem, and those |
18 |
for the the thirty plus which have installed just fine. |
19 |
> > |
20 |
> > The following REQUIRED_USE flag constraints are unsatisfied: |
21 |
> > any-of ( ruby_targets_ruby27 ruby_targets_ruby30 |
22 |
> ruby_targets_ruby31 ) |
23 |
> > |
24 |
>> I would expect USE_RUBY="ruby31" to translate into |
25 |
>> ruby_targets_ruby31, but even explicitly adding that to package.use |
26 |
>> has no effect. |
27 |
> |
28 |
> The ebuild contains USE_RUBY="ruby26 ruby27" ruby_add_bdepend " |
29 |
Hmm. It looks to me that line should probably be 'USE_RUBY="ruby26 |
30 |
ruby27 ruby30 ruby31" ruby_add_bdepend "' However, as it only affects |
31 |
the required ruby version for two depedencies only if the test use flag |
32 |
is set (it is not) I'm not sure why it would matter. |
33 |
|
34 |
I suppose it is likely just a typo in the ebuild. They removed ruby25 |
35 |
from 1.1.0 but didn't add the newer ruby versions. Actually even 1.1.0 |
36 |
may be broken as it includes ruby30 in USE_RUBY but not on the |
37 |
ruby_add_bdepend line. However, I just made an -r1 in my local |
38 |
overlay, adding the new ruby versions to that line, and I still get the |
39 |
same error. So I'm actually still stuck figuring out why this ebuild |
40 |
won't take ruby31. |
41 |
> |
42 |
> Have you tried setting RUBY_TARGETS to ruby27 for this package? |
43 |
Why would I do that if I don't have ruby-2.7 installed, nor do I want |
44 |
to? |
45 |
> |
46 |
> I must say I find the whole RUBY_* thing even more troublesome than |
47 |
> the PYTHON_* stuff, and that's saying something! |
48 |
That I agree with. If I knew then what I know now, I would have argued |
49 |
much more vigorously against using Ruby on Rails for this web site. |
50 |
But that's fodder another entire thread. |
51 |
> |
52 |
> |
53 |
> -- |
54 |
> Neil Bothwick |
55 |
Jack |