1 |
I'm helping support a web site hosted at Heroku and written in Ruby on |
2 |
Rails. Following some tool upgrades there, I upgraded my local rails |
3 |
to 3.1, uninstalling the previous version 2.7. I now have |
4 |
RUBY_TARGETS="ruby31" in make.conf. and several specific dev-ruby |
5 |
package versions in package.accept_keywords. Most of them upgraded |
6 |
fine, or at least reinstalled (using a version supporting ruby31 after |
7 |
unmerging the old version) but some are giving me grief. |
8 |
|
9 |
For example, "emerge -1 dev-ruby/thor" gives me |
10 |
|
11 |
!!! Problem resolving dependencies for dev-ruby/thor |
12 |
... done! |
13 |
|
14 |
!!! The ebuild selected to satisfy "dev-ruby/thor" has unmet |
15 |
requirements. |
16 |
- dev-ruby/thor-1.2.1::gentoo USE="-doc -test" ABI_X86="(64)" |
17 |
RUBY_TARGETS="-ruby27 (-ruby30) (-ruby31)" |
18 |
|
19 |
The following REQUIRED_USE flag constraints are unsatisfied: |
20 |
any-of ( ruby_targets_ruby27 ruby_targets_ruby30 |
21 |
ruby_targets_ruby31 ) |
22 |
|
23 |
I would expect USE_RUBY="ruby31" to translate into ruby_targets_ruby31, |
24 |
but even explicitly adding that to package.use has no effect. Is there |
25 |
something I'm missing turning off ruby31, specifically for just a small |
26 |
number of packages? (so far the only other one with this problem is |
27 |
dev-ruby/mini_mime). |
28 |
|
29 |
Portage has two versions of thor: 1.1.0 and 1.1.2, both marked stable |
30 |
for amd64, and 1.2.1 has USE_RUBY="ruby26 ruby27 ruby30 ruby31" so I |
31 |
don't see any reason it's not working. |
32 |
|
33 |
I already have railties installed (using -O) with ruby31, and it |
34 |
depends on thor via ruby_add_redepend, which I read as requiring thor |
35 |
with ruby31. thor is not mentioned in any file under /etc/portage. |
36 |
|
37 |
Does anybody see what I'm missing? |
38 |
|
39 |
Jack |