Mick wrote: > On Monday, 22 July 2019 11:12:55 BST Dale wrote: >> Howdy, >> >> I did my usual sync and ran into a slight problem. Given the minimal >> output, I can't quite figure out if there is a way around this. >> Sometimes I can emerge a few packages individually and get around this >> sort of thing. On this one tho, I just can't quite figure out how to >> get around the problem. Things I've tried so far. Made sure nothing in >> package.use is ruby related and made sure no packages in the list are in >> there either. I updated @system successfully and tried again, same >> error. I've tried unmasking next up packages with no change. I >> reversed that and tried to mask some packages, same thing or it >> complains about the masked packages one. I've tried to emerge the >> packages listed individually, in different order even, with no change. >> This is what I get. >> >> >> >> root@fireball / # emerge -uvaDN world >> >> These are the packages that would be merged, in order: >> >> Calculating dependencies... done! >> >> emerge: there are no ebuilds to satisfy >> ">=dev-ruby/xmlrpc-0.3.0[ruby_targets_ruby25]". >> (dependency required by "dev-lang/ruby-2.5.5::gentoo" [ebuild]) >> (dependency required by >> "dev-ruby/rake-12.3.2::gentoo[ruby_targets_ruby25]" [ebuild]) >> (dependency required by "media-video/mkvtoolnix-35.0.0::gentoo" [installed]) >> (dependency required by "@selected" [set]) >> (dependency required by "@world" [argument]) >> root@fireball / # > > Have you specified ruby target 2.5 anywhere in your /etc/portage and, or > uninstalled/masked ruby 2.4? The above packages are installed with the > default ruby 2.4 here: > > ~ $ equery u dev-ruby/xmlrpc > [ Legend : U - final flag setting for installation] > [ : I - package is installed with flag ] > [ Colors : set, unset ] > * Found these USE flags for dev-ruby/xmlrpc-0.3.0: > U I > - - doc : Add extra documentation (API, Javadoc, etc). It is > recommended to > enable per package instead of globally > + + ruby_targets_ruby24 : Build with MRI Ruby 2.4.x > - - test : Enable dependencies and/or preparations necessary > to run tests (usually > controlled by FEATURES=test but can be toggled > independently) > > ~ $ equery u dev-ruby/rake > [ Legend : U - final flag setting for installation] > [ : I - package is installed with flag ] > [ Colors : set, unset ] > * Found these USE flags for dev-ruby/rake-12.3.1: > U I > - - doc : Add extra documentation (API, Javadoc, etc). It is > recommended to > enable per package instead of globally > + + ruby_targets_ruby24 : Build with MRI Ruby 2.4.x > - - test : Enable dependencies and/or preparations necessary > to run tests (usually > controlled by FEATURES=test but can be toggled > independently) >
I have ruby 2.4 here as well. root@fireball / # equery list -p ruby * Searching for ruby ... [-P-] [ ] dev-lang/ruby-2.4.5:2.4 [IP-] [ ] dev-lang/ruby-2.4.6:2.4 [-P-] [ ] dev-lang/ruby-2.5.5:2.5 [-P-] [ ~] dev-lang/ruby-2.6.2:2.6 [-P-] [ ~] dev-lang/ruby-2.6.3:2.6 root@fireball / # It appears something is pulling in 2.5 but for some reason, even tho it isn't masked, it won't emerge it because of some other problem, that I can't figure out yet. I looked in /etc/portage for anything ruby and didn't find much but commented out the little I did find. It made no difference since they were specific to older versions anyway. It gives the same error. I did manage to get it to update the other KDE packages tho. I did a --exclude for the packages listed in the error. It still complains but it does emerge everything else. Maybe when that is done, it will share some more details and give us a clue. Usually we have the opposite problem, emerge spitting out to much info, most of it useless or confusing at that. This is the first time that I've got so little and not be able to figure out a workaround. When the KDE packages get done, I'll try again and post what it spits out. Maybe it will give us more info or emerge will find a way to solve it. Thanks for the info. Dale :-) :-)
