Gentoo Archives: gentoo-user

From: Dale <rdalek1967@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] dev-lang/ruby and dev-ruby/xmlrpc-0.3.0[ruby_targets_ruby25] error
Date: Mon, 22 Jul 2019 11:37:44
Message-Id: c85b6d83-b213-7e9b-f7f4-4f3cf5d2d54a@gmail.com
In Reply to: Re: [gentoo-user] dev-lang/ruby and dev-ruby/xmlrpc-0.3.0[ruby_targets_ruby25] error by Mick
1 Mick wrote:
2 > On Monday, 22 July 2019 11:12:55 BST Dale wrote:
3 >> Howdy,
4 >>
5 >> I did my usual sync and ran into a slight problem. Given the minimal
6 >> output, I can't quite figure out if there is a way around this.
7 >> Sometimes I can emerge a few packages individually and get around this
8 >> sort of thing. On this one tho, I just can't quite figure out how to
9 >> get around the problem. Things I've tried so far. Made sure nothing in
10 >> package.use is ruby related and made sure no packages in the list are in
11 >> there either. I updated @system successfully and tried again, same
12 >> error. I've tried unmasking next up packages with no change. I
13 >> reversed that and tried to mask some packages, same thing or it
14 >> complains about the masked packages one. I've tried to emerge the
15 >> packages listed individually, in different order even, with no change.
16 >> This is what I get.
17 >>
18 >>
19 >>
20 >> root@fireball / # emerge -uvaDN world
21 >>
22 >> These are the packages that would be merged, in order:
23 >>
24 >> Calculating dependencies... done!
25 >>
26 >> emerge: there are no ebuilds to satisfy
27 >> ">=dev-ruby/xmlrpc-0.3.0[ruby_targets_ruby25]".
28 >> (dependency required by "dev-lang/ruby-2.5.5::gentoo" [ebuild])
29 >> (dependency required by
30 >> "dev-ruby/rake-12.3.2::gentoo[ruby_targets_ruby25]" [ebuild])
31 >> (dependency required by "media-video/mkvtoolnix-35.0.0::gentoo" [installed])
32 >> (dependency required by "@selected" [set])
33 >> (dependency required by "@world" [argument])
34 >> root@fireball / #
35 >
36 > Have you specified ruby target 2.5 anywhere in your /etc/portage and, or
37 > uninstalled/masked ruby 2.4? The above packages are installed with the
38 > default ruby 2.4 here:
39 >
40 > ~ $ equery u dev-ruby/xmlrpc
41 > [ Legend : U - final flag setting for installation]
42 > [ : I - package is installed with flag ]
43 > [ Colors : set, unset ]
44 > * Found these USE flags for dev-ruby/xmlrpc-0.3.0:
45 > U I
46 > - - doc : Add extra documentation (API, Javadoc, etc). It is
47 > recommended to
48 > enable per package instead of globally
49 > + + ruby_targets_ruby24 : Build with MRI Ruby 2.4.x
50 > - - test : Enable dependencies and/or preparations necessary
51 > to run tests (usually
52 > controlled by FEATURES=test but can be toggled
53 > independently)
54 >
55 > ~ $ equery u dev-ruby/rake
56 > [ Legend : U - final flag setting for installation]
57 > [ : I - package is installed with flag ]
58 > [ Colors : set, unset ]
59 > * Found these USE flags for dev-ruby/rake-12.3.1:
60 > U I
61 > - - doc : Add extra documentation (API, Javadoc, etc). It is
62 > recommended to
63 > enable per package instead of globally
64 > + + ruby_targets_ruby24 : Build with MRI Ruby 2.4.x
65 > - - test : Enable dependencies and/or preparations necessary
66 > to run tests (usually
67 > controlled by FEATURES=test but can be toggled
68 > independently)
69 >
70
71
72 I have ruby 2.4 here as well.
73
74
75 root@fireball / # equery list -p ruby
76  * Searching for ruby ...
77 [-P-] [  ] dev-lang/ruby-2.4.5:2.4
78 [IP-] [  ] dev-lang/ruby-2.4.6:2.4
79 [-P-] [  ] dev-lang/ruby-2.5.5:2.5
80 [-P-] [ ~] dev-lang/ruby-2.6.2:2.6
81 [-P-] [ ~] dev-lang/ruby-2.6.3:2.6
82 root@fireball / #
83
84
85 It appears something is pulling in 2.5 but for some reason, even tho it
86 isn't masked, it won't emerge it because of some other problem, that I
87 can't figure out yet. 
88
89 I looked in /etc/portage for anything ruby and didn't find much but
90 commented out the little I did find.  It made no difference since they
91 were specific to older versions anyway.  It gives the same error.
92
93 I did manage to get it to update the other KDE packages tho.  I did a
94 --exclude for the packages listed in the error.  It still complains but
95 it does emerge everything else.  Maybe when that is done, it will share
96 some more details and give us a clue. 
97
98 Usually we have the opposite problem, emerge spitting out to much info,
99 most of it useless or confusing at that.  This is the first time that
100 I've got so little and not be able to figure out a workaround. 
101
102 When the KDE packages get done, I'll try again and post what it spits
103 out.  Maybe it will give us more info or emerge will find a way to solve
104 it. 
105
106 Thanks for the info. 
107
108 Dale
109
110 :-)  :-) 

Replies