Re: [gentoo-user] install under centos606

[R0b0t1]

On Mon, Aug 21, 2017 at 6:49 AM,   wrote:
> Any likely problems if i install the stage3 tarball etc. under centos6.6?
> tried the live dvd but it has problems with my current graphics card
> (framebuffer driver).

Sir, I would be extremely careful with that release: both the major
and minor version are the number of the beast. If anything goes wrong
I do not doubt it is possible to spend time troubleshooting it, but in
general I would chalk the existence of most problems up to Satan's
involvement.

I will be sure to pray for you so that you might get Gentoo installed.
I have found my Gentoo usership to be a very rewarding experience.

Respectfully,
 R0b0t1

Re: [gentoo-user] install under centos606

[R0b0t1]

On Mon, Aug 21, 2017 at 7:08 AM, Ralph Seichter
 wrote:
> On 21.08.2017 13:49, mad.scientist.at.la...@tutanota.com wrote:
>
>> I'm excited about using gentoo, though the online instructions could
>> really use more structuring, i.e. it's hard to avoid reading the parts
>> you don't need to and the "flow" is rather lost. It's an extremely
>> verbose document which makes it very hard to get the gist of the install
>> procedure. it's not a bad document, merely poorly organized. [...]
>
> I completely disagree. I consider the Gentoo installation documentation
> well structured, easy to follow and precise, and I don't know what your
> statements like "most newbies would be helplessly confused" are supposed
> to be based on. Please don't try to pass on your personal opinions as
> facts without providing any proof. Show us a control group of newbies,
> most of them helplessly confused, if you can. ;-)
>

I think most of the problem is all the handbook does is give you a
working system in the technical sense. Everything else is up to you to
discover, which can be very hard if you are lacking terminology or
very specific experience.

A good example of a more fully featured guide is Sakaki's EFI
Installation Guide
(https://wiki.gentoo.org/wiki/Sakaki's_EFI_Install_Guide). I have
proposed the handbook be updated, at least on an architecture-specific
basis, to reflect common installation options (as was it seems was
originally intended). However, the Handbook team seems very
conservative and hard to contact.

Among my suggestions were transferring the Handbook to Gollum, so the
pages could be managed from Git. Porting the whole Wiki to Gollum
might make it hard for normal users to contribute, but I suspect only
particularly adept users would have good contributions to the
Handbook.

R0b0t1.

Re: [gentoo-user] mount: Permission Denied in CHROOT

[symack]

Hello Everyone,

I did try that as well however when I do a grub install I am getting:

 grub-install /dev/sda
Installing for i386-pc platform.
grub-install: warning: disk does not exist, so falling back to partition
device /dev/sda2.
grub-install: warning: disk does not exist, so falling back to partition
device /dev/sda2.
grub-install: warning: disk does not exist, so falling back to partition
device /dev/sda2.
grub-install: error: disk `hostdisk//dev/sda2' not found.

/boot ls -la lists:

-rw-r--r--  1 root root  106617 Aug 22 20:51 config-4.9.34-gentoo
drwxr-xr-x  6 root root1024 Aug 22 20:52 grub
-rw-r--r--  1 root root 3609869 Aug 22 20:51 System.map-4.9.34-gentoo
-rw-r--r--  1 root root 6852592 Aug 22 20:51 vmlinuz-4.9.34-gentoo

​I am really not sure why we are getting the error. I can write to the
partition just fine as you can see.

Kind Regards,

Mike

Re: [gentoo-user] Re: downgrading glibc

[Daniel Frey]

On 08/22/2017 07:18 AM, Rich Freeman wrote:
> On Tue, Aug 22, 2017 at 6:34 AM, Nils Freydank  
> wrote:
>>
>> BTW, mythtv has no maintainer, might you be interested in a proxied
>> maintainership?
>>
> 
> I'd encourage somebody to step up and do this - I no longer use it and
> MythTV is one of those packages that you really need to use if you
> want to maintain it (hardware/etc, plus a fair bit of work).
> 
> If somebody steps up and wants tips please do feel free to ping me,
> and I suspect cardoe would also be willing.
> 
> In general though upstream maintains git branches for each of their
> releases under fixes/ that track stuff like this.  This commit was in
> fixes/0.28.  These are stable branches and very unlikely to break
> anything - and this was the basis of all the updates within a release
> on Gentoo previously.  The minor releases like 0.28.1 are just tagged
> versions off of these branches - 0.28 plus all the fixes up to that
> point in time is basically the same as 0.28.1.  The ebuild is designed
> to make it easy to pull these in - I see that cardoe pointed it at
> github so in theory you can just change the hash to the new head and
> it will probably pull in all the fixes.
> 
> They're up to 0.29 now.  That isn't in the 0.28 fixes branch, and
> might need a bit more testing.
> 


I use mythtv on a daily basis, have multiple frontends connecting to a
remote backend, but I do not know if the skills I have are enough to
even proxy-maintain them, or I'd offer in a heartbeat.

The only times I've delved into ebuilds is when they don't work, and my
knowledge is quite limited there.

Dan

Re: [gentoo-user] Is this working correctly??

[Dale]

Mick wrote:
> On Tuesday, 22 August 2017 16:41:54 BST Dale wrote:
>> Alan McKinnon wrote:
>>> On 22/08/2017 15:01, Dale wrote:
 Howdy,

 I have this 
> You have not defined what "this" is.  The word "this" is being used here as a 
> determinant (I think), but it is not preceded by a sentence defining it.  So, 
> we are left hanging in anticipation of you revealing what "this" refers to, 
> meanwhile engaging in wild a** guessing as to what it might have been you had 
> in your mind, but never wrote down.
>

This would be Seamonkey, that I use to compose and send emails with,
even tho I'm less happy with it than I once was.  ;-) 

 set to send text only for gentoo.org and kde.org.  Someone
 replied making me think it 
> Hmm ... same deal here.  You have not defined "it".

Same it.

>
 is not doing as instructed, even tho 
> By "tho" I assume your mean "though" if you have used a spelling variant of 
> the late 19th early 20th century, which in 2017 may appear an oddity.  
> Nevertheless, your preference is respected.

Yea, it's shorter spelled that way and sometimes my o and u fingers get
crossed up.  Those keys on the keyboard are wearing thin too.  lol 


 settings says it is.
> Well, "settings" in plural form are more than one and therefore the verb must 
> "say" it is.  Of course, settings say nothing, as they are not a person to 
> utter words.  Settings define, specify, set, show, indicate, and so on.
>
  Can someone tell me for sure and certain that this is
 sending as it should?  Text only I hope.
> "this" and "it" still require defining.
>

Done.  lol 


>>> I see 3 problems with your mail, but content-type is not one of them :-)
>>> That is set to text only, exactly as you intended
>> What would those be?  Maybe I can change a setting and fix it.
> Here we go again:  Alan explained he spotted three (3) things wrong with your 
> mail.  He did not say your mail is wrong.  Therefore, "it" is inappropriate 
> in 
> form.  It should be in plural.
>
> In addition, I am not sure what setting you may need to change.  I hope it 
> will not be painful for either party.

Me to because it may require changing email programs.  O_o 

>> Dale
>>
>> :-)  :-)
> LOL!  I'm only pulling your leg Dale! Wot U wrote was good and proper!  :-)
>
> PS.  I think Peter may be around the corner any minute now, to correct my 
> English too!  Ha, ha, ha!

Well, most old timers know I have this occasional hiccup with my email
program.  I upgrade and it starts sending HTML and all sorts of crazy
things.  Sometimes, I want to shoot the thing, stick some dynamite in it
and blow it up and then bury it, 10 feet deep.  I can put that leg you
are pulling in the hole if needed.  lol 

Dale

:-)  :-) 

Re: [gentoo-user] Is this working correctly??

[Mick]

On Tuesday, 22 August 2017 16:41:54 BST Dale wrote:
> Alan McKinnon wrote:
> > On 22/08/2017 15:01, Dale wrote:
> >> Howdy,
> >> 
> >> I have this 

You have not defined what "this" is.  The word "this" is being used here as a 
determinant (I think), but it is not preceded by a sentence defining it.  So, 
we are left hanging in anticipation of you revealing what "this" refers to, 
meanwhile engaging in wild a** guessing as to what it might have been you had 
in your mind, but never wrote down.


> >> set to send text only for gentoo.org and kde.org.  Someone
> >> replied making me think it 

Hmm ... same deal here.  You have not defined "it".

> >> is not doing as instructed, even tho 

By "tho" I assume your mean "though" if you have used a spelling variant of 
the late 19th early 20th century, which in 2017 may appear an oddity.  
Nevertheless, your preference is respected.

> >> settings says it is.

Well, "settings" in plural form are more than one and therefore the verb must 
"say" it is.  Of course, settings say nothing, as they are not a person to 
utter words.  Settings define, specify, set, show, indicate, and so on.

> >>  Can someone tell me for sure and certain that this is
> >> sending as it should?  Text only I hope.

"this" and "it" still require defining.


> > I see 3 problems with your mail, but content-type is not one of them :-)
> > That is set to text only, exactly as you intended
> 
> What would those be?  Maybe I can change a setting and fix it.

Here we go again:  Alan explained he spotted three (3) things wrong with your 
mail.  He did not say your mail is wrong.  Therefore, "it" is inappropriate in 
form.  It should be in plural.

In addition, I am not sure what setting you may need to change.  I hope it 
will not be painful for either party.

> Dale
> 
> :-)  :-)

LOL!  I'm only pulling your leg Dale! Wot U wrote was good and proper!  :-)

PS.  I think Peter may be around the corner any minute now, to correct my 
English too!  Ha, ha, ha!
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Is this working correctly??

[Dale]

Alan McKinnon wrote:
> On 22/08/2017 15:01, Dale wrote:
>> Howdy,
>>
>> I have this set to send text only for gentoo.org and kde.org.  Someone
>> replied making me think it is not doing as instructed, even tho settings
>> says it is.  Can someone tell me for sure and certain that this is
>> sending as it should?  Text only I hope. 
> I see 3 problems with your mail, but content-type is not one of them :-)
> That is set to text only, exactly as you intended
>
>

What would those be?  Maybe I can change a setting and fix it. 

Dale

:-)  :-) 

Re: [gentoo-user] Is this working correctly??

[Dale]

Dale wrote:
> Howdy,
>
> I have this set to send text only for gentoo.org and kde.org.  Someone
> replied making me think it is not doing as instructed, even tho settings
> says it is.  Can someone tell me for sure and certain that this is
> sending as it should?  Text only I hope. 
>
> Thanks.
>
> Dale
>
> :-)  :-) 
>

Thanks to all who replied.  It seems my settings are working but may
have replied with HTML when I replied to a HTML message. 

For future reference, if my messages are not list friendly, let me
know.  Sometimes a upgrade throws a curve ball. 

Dale

:-)  :-) 

Re: [gentoo-user] Is this working correctly??

[Alan McKinnon]

On 22/08/2017 15:01, Dale wrote:
> Howdy,
> 
> I have this set to send text only for gentoo.org and kde.org.  Someone
> replied making me think it is not doing as instructed, even tho settings
> says it is.  Can someone tell me for sure and certain that this is
> sending as it should?  Text only I hope. 

I see 3 problems with your mail, but content-type is not one of them :-)
That is set to text only, exactly as you intended


-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Re: downgrading glibc

[Neil Bothwick]

On 22 August 2017 14:09:39 EEST, Dale  wrote:
>It may have been you but I was thinking either Walter or Duncan but not
>sure.  It could be, I read it on -dev too.  I'm just not sure who it
>was
>just know it is gentoo related, since Gentoo is all I'm subscribed to. 
>
>One would think there would be some method to downgrade that is known
>to
>work and documented.  It can be done for lots of other very important
>packages but this one, not so much.  To me, it's just odd. 
>
>At least the OP found a fix tho.  < whew >
>
>Dale
>
>:-)  :-) 
>
>P. S. Top posting since Neil seems to be on some device that started
>it.  :-D 
>
>
>Neil Bothwick wrote:
>> I did it once, some years ago. AFAIR I commented out the version che
>k
>> in, i think, the glibc-toolchain eclass then emerged the older
>> version. Just make sire you have a binary package of the current
>> version that you can unpack in / if things go wrong.
>>
>> On 22 August 2017 13:53:35 EEST, Dale  wrote:
>>
>> Raffaele Belardi wrote:
>>
>> On Fri, 2017-08-18 at 09:00 +0200, Raffaele Belardi wrote:
>>
>> I hava a build problem upgrading Mythtv to 0.28.1-r1 [1]
>> on an ~amd64 system. The problem is related to a glibc
>API
>> change [2] introduced in glibc-2.24 and still present in
>> glibc-2.25. So I'm thinking to try the build with an
>older
>> glibc version. Downgrading the system to glibc to 2.23-r3
>> means trouble? If not, an emerge @preserved-rebuild after
>> the downgrade will be sufficient to not break the rest of
>> the system? I suppose a quickpkg of the whole world
>before
>> the downgrade would be a good idea, just in case...
>> thanks, raffaele [1]
>> https://bugs.gentoo.org/show_bug.cgi?id=604430 [2]
>> https://bugs.gentoo.org/show_bug.cgi?id=575232 
>>
>> Just as follow up, inspired by [2] I fixed the mythtv build
>> issue by adding #include  to videosource.cpp
>> and continuing the build with ebuild instead of emerge.
>raffaele
>>
>>
>>
>>
>> Just a FYI, some have been able to downgrade and it work. 
>However, you
>> have to be prepared for that beforehand I think.  I've seen it
>posted
>> before but can't recall WHO it was.  I was hoping they would
>reply but
>> either they didn't see your post or they are no longer
>subscribed. 
>>
>> While it may be possible, it is risky and not recommended.  It's
>one
>> thing that I wish they had a known path to downgrade for.  It's
>one of
>> those, you don't know it's going to break something until it does
>and
>> you have little or no options. 
>>
>> Glad you got a workaround tho. Maybe some more info will pop up
>later.
>>
>> Dale
>>
>> :-)  :-) 
>>
>>
>> -- 
>> Sent from my Android device with K-9 Mail. Please excuse my brevity. 

:P
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Re: downgrading glibc

[Rich Freeman]

On Tue, Aug 22, 2017 at 6:34 AM, Nils Freydank  wrote:
> Am Dienstag, 22. August 2017, 09:01:07 CEST schrieb Raffaele Belardi:
>> […]
>> > [1] https://bugs.gentoo.org/show_bug.cgi?id=604430
>> > [2] https://bugs.gentoo.org/show_bug.cgi?id=575232
>>
>> Just as follow up, inspired by [2] I fixed the mythtv build issue by
>> adding #include  to videosource.cpp and continuing the
>> build with ebuild instead of emerge.
> Great! In general, to improve Gentoo a bit further, you could create a patch
> at this point, test applying it via /etc/portage/patches/ and add it to the
> bugtracker (or paste it here or in IRC asking someone to paste it in your
> name) ;-)
>

Per the comment I made in the bug, if you're going to patch, I'd use
upstream's patch - the commit for 0.28 is:
https://github.com/MythTV/mythtv/commit/b012ff0f6b284969183863d42a6a14eb77ed0a1d

In general it is ALWAYS better to use the upstream patch.  Plus if you
need to get a Gentoo dev to commit it for you you'll get less
push-back that way if you reference it in a bug.

>
> BTW, mythtv has no maintainer, might you be interested in a proxied
> maintainership?
>

I'd encourage somebody to step up and do this - I no longer use it and
MythTV is one of those packages that you really need to use if you
want to maintain it (hardware/etc, plus a fair bit of work).

If somebody steps up and wants tips please do feel free to ping me,
and I suspect cardoe would also be willing.

In general though upstream maintains git branches for each of their
releases under fixes/ that track stuff like this.  This commit was in
fixes/0.28.  These are stable branches and very unlikely to break
anything - and this was the basis of all the updates within a release
on Gentoo previously.  The minor releases like 0.28.1 are just tagged
versions off of these branches - 0.28 plus all the fixes up to that
point in time is basically the same as 0.28.1.  The ebuild is designed
to make it easy to pull these in - I see that cardoe pointed it at
github so in theory you can just change the hash to the new head and
it will probably pull in all the fixes.

They're up to 0.29 now.  That isn't in the 0.28 fixes branch, and
might need a bit more testing.

-- 
Rich

Re: [gentoo-user] Re: downgrading glibc

[Raffaele Belardi]

On Tue, 2017-08-22 at 15:34 +0200, Nils Freydank wrote:
> Am Dienstag, 22. August 2017, 09:01:07 CEST schrieb Raffaele Belardi:
> > […]
> > > [1] https://bugs.gentoo.org/show_bug.cgi?id=604430
> > > [2] https://bugs.gentoo.org/show_bug.cgi?id=575232
> > 
> > Just as follow up, inspired by [2] I fixed the mythtv build issue
> > by
> > adding #include  to videosource.cpp and continuing
> > the
> > build with ebuild instead of emerge.
> 
> Great! In general, to improve Gentoo a bit further, you could create
> a patch 
> at this point, test applying it via /etc/portage/patches/ and add it
> to the 
> bugtracker (or paste it here or in IRC asking someone to paste it in
> your 
> name) ;-)

I agree that would be the correct way. My intention was to add a
comment in the bugtracker stating the above but things have already
evolved as you noticed.

> (I guess you can avoid that in this case as another dev said that bug
> is fixed 
> upstream now.)
> 
> BTW, mythtv has no maintainer, might you be interested in a proxied 
> maintainership?

Not sure about the implications (read: effort), mythtv is a huge
beast...

raffaele

Re: [gentoo-user] Re: downgrading glibc

[Nils Freydank]

Am Dienstag, 22. August 2017, 09:01:07 CEST schrieb Raffaele Belardi:
> […]
> > [1] https://bugs.gentoo.org/show_bug.cgi?id=604430
> > [2] https://bugs.gentoo.org/show_bug.cgi?id=575232
> 
> Just as follow up, inspired by [2] I fixed the mythtv build issue by
> adding #include  to videosource.cpp and continuing the
> build with ebuild instead of emerge.
Great! In general, to improve Gentoo a bit further, you could create a patch 
at this point, test applying it via /etc/portage/patches/ and add it to the 
bugtracker (or paste it here or in IRC asking someone to paste it in your 
name) ;-)

(I guess you can avoid that in this case as another dev said that bug is fixed 
upstream now.)

BTW, mythtv has no maintainer, might you be interested in a proxied 
maintainership?


Greetings,
Nils
-- 
GPG fingerprint: '00EF D31F 1B60 D5DB ADB8  31C1 C0EC E696 0E54 475B'
Nils Freydank

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Is this working correctly??

[Tom H]

On Tue, Aug 22, 2017 at 4:01 PM, Dale  wrote:
>
> I have this set to send text only for gentoo.org and kde.org. Someone
> replied making me think it is not doing as instructed, even tho settings
> says it is. Can someone tell me for sure and certain that this is
> sending as it should?  Text only I hope.

Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Re: [gentoo-user] Is this working correctly??

[Todd Goodman]

I only see content-type text/plain.

So it seems to be working from my POV.

Todd


On 8/22/2017 9:01 AM, Dale wrote:

Howdy,

I have this set to send text only for gentoo.org and kde.org.  Someone
replied making me think it is not doing as instructed, even tho settings
says it is.  Can someone tell me for sure and certain that this is
sending as it should?  Text only I hope.

Thanks.

Dale

:-)  :-)

[gentoo-user] Is this working correctly??

[Dale]

Howdy,

I have this set to send text only for gentoo.org and kde.org.  Someone
replied making me think it is not doing as instructed, even tho settings
says it is.  Can someone tell me for sure and certain that this is
sending as it should?  Text only I hope. 

Thanks.

Dale

:-)  :-) 

Re: [gentoo-user] Re: ruby 22

[Dale]

John Covici wrote:
> On Tue, 22 Aug 2017 05:16:55 -0400,
> Neil Bothwick wrote:
>> [1  ]
>> [2  ]
>> RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - - 
>> newuse @world to apply the change. The depclean should work, 
>> Just check for stray ruby settings in /etc/portage. 
>>
>> On 22 August 2017 05:21:23 EEST, John Covici  wrote:
>>
>>  On Mon, 21 Aug 2017 21:20:04 -0400,
>> Alec Ten Harmsel wrote:
>>
>>   
>>
>>  On 08/21/2017 10:13 AM, allan gottlieb wrote:
>>
>>   
>>  I issued emerge --pretend --verbose --depclean =ruby-2.1.9
>>  and the response was
>>
>>dev-lang/ruby
>>   selected: 2.1.9
>>  protected: none
>>omitted: 2.2.6
>>
>>  Am I correct in believing it is now safe to issue
>>
>> emerge --depclean =ruby-2.1.9
>>
>>  thanks,
>>  allan
>>
>>  
>>  Yes, that should be fine. I rarely look at portage output and
>>  just run `emerge -uDN @world' and `emerge --depclean' right after
>>  one another, and it always works fine for ruby/python upgrades.
>>
>>  The devs have done such a good job in general that I haven't had
>>  any problems just running these commands the past couple years.
>>
>> I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
>> default, but when I ran emerge --depclean I still have packages
>> pulling ruby21 as follows:
>>
>> Calculating dependencies  .. . done!
>>   dev-lang/ruby-2.1.10 pulled in by:
>>   dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
>>   dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1
>>   dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1
>>   dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1
>>   dev-ruby/maruku-0.7.3 requires dev-lang/ruby:2.1
>>   dev-ruby/minitest-5.10.3 requires
>>   dev-lang/ruby:2.1
>>   dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
>>   dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
>>   dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
>>   dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
>>   dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1
>>   dev-ruby/rubygems-2.6.12 requires
>>   dev-lang/ruby:2.1
>>   dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1
>>   dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1
>>   virtual/rubygems-13 requires dev-lang/ruby:2.1
>>   virtual/rubygems-7 requires dev-lang/ruby:2.1
>>
>> I tried a word ld update, but it didn't update any of those packages
>> -- any ideas of how to fix?
>>
> I use the following arguments when I run updates:
> --update --deep --with-bdeps=y --changed-use --backtrack=120
> --keep-goingworld
>
> Do I need to use new-use instead?
>

Over the years, I've updated my update process to what causes the least
issues, for me at least.  This is what I type in:

eix-sync && emerge -uaDN world

This is the settings I have in make.conf:

EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j8
--quiet-build=n -1 --unordered-display"

Obviously some may need to be set differently, like the -j8 part, for
your system but some of that helps no matter what system you use.  The
-1 for example keeps the world file clean since you have to put effort
into adding something to it.  One could add it to the world file
directly or use the --select y option.  Either way, nothing gets added
to the world file because you forgot to use the -1 option.  The
backtrack, so far 100 has worked.  If I start to have issues that a
higher number fixes, it will be upped to that number.  Over time, some
things have been removed since they were no longer needed. 

Your mileage may vary but could give you a good starting point.  Took me
years to get to that simple line.  ;-)  If anyone is interested, I could
post some other things from make.conf I've picked up over the years. 

Hope that helps.

Dale

:-)  :-) 

Re: [gentoo-user] Re: ruby 22

[Alec Ten Harmsel]

On Tue, Aug 22, 2017 at 07:57:39AM -0400, John Covici wrote:
> > 
> > I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
> > default, but when I ran emerge --depclean I still have packages
> > pulling ruby21 as follows:
> > 
> > Calculating dependencies  .. . done!
> >   dev-lang/ruby-2.1.10 pulled in by:
> >   dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
> >   dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1
> >   dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1
> >   dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1
> >   dev-ruby/maruku-0.7.3 requires dev-lang/ruby:2.1
> >   dev-ruby/minitest-5.10.3 requires
> >   dev-lang/ruby:2.1
> >   dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
> >   dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
> >   dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
> >   dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
> >   dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1
> >   dev-ruby/rubygems-2.6.12 requires
> >   dev-lang/ruby:2.1
> >   dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1
> >   dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1
> >   virtual/rubygems-13 requires dev-lang/ruby:2.1
> >   virtual/rubygems-7 requires dev-lang/ruby:2.1
> > 
> > I tried a word ld update, but it didn't update any of those packages
> > -- any ideas of how to fix?
> > 
> 
> I use the following arguments when I run updates:
> --update --deep --with-bdeps=y --changed-use --backtrack=120
> --keep-goingworld
> 
> Do I need to use new-use instead?

I'm not sure; I always use new-use. If you haven't synced and updated recently,
you may have issues as the default profiles still had ruby-2.1 listed in
them.

Alec

Re: [gentoo-user] Re: ruby 22

[John Covici]

On Tue, 22 Aug 2017 05:16:55 -0400,
Neil Bothwick wrote:
> 
> [1  ]
> [2  ]
> RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - - 
> newuse @world to apply the change. The depclean should work, 
> Just check for stray ruby settings in /etc/portage. 
> 
> On 22 August 2017 05:21:23 EEST, John Covici  wrote:
> 
>  On Mon, 21 Aug 2017 21:20:04 -0400,
> Alec Ten Harmsel wrote:
> 
>   
> 
>  On 08/21/2017 10:13 AM, allan gottlieb wrote:
> 
>   
>  I issued emerge --pretend --verbose --depclean =ruby-2.1.9
>  and the response was
> 
>dev-lang/ruby
>   selected: 2.1.9
>  protected: none
>omitted: 2.2.6
> 
>  Am I correct in believing it is now safe to issue
> 
> emerge --depclean =ruby-2.1.9
> 
>  thanks,
>  allan
> 
>  
>  Yes, that should be fine. I rarely look at portage output and
>  just run `emerge -uDN @world' and `emerge --depclean' right after
>  one another, and it always works fine for ruby/python upgrades.
> 
>  The devs have done such a good job in general that I haven't had
>  any problems just running these commands the past couple years.
> 
> I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
> default, but when I ran emerge --depclean I still have packages
> pulling ruby21 as follows:
> 
> Calculating dependencies  .. . done!
>   dev-lang/ruby-2.1.10 pulled in by:
>   dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
>   dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1
>   dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1
>   dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1
>   dev-ruby/maruku-0.7.3 requires dev-lang/ruby:2.1
>   dev-ruby/minitest-5.10.3 requires
>   dev-lang/ruby:2.1
>   dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
>   dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
>   dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
>   dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
>   dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1
>   dev-ruby/rubygems-2.6.12 requires
>   dev-lang/ruby:2.1
>   dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1
>   dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1
>   virtual/rubygems-13 requires dev-lang/ruby:2.1
>   virtual/rubygems-7 requires dev-lang/ruby:2.1
> 
> I tried a word ld update, but it didn't update any of those packages
> -- any ideas of how to fix?
> 

I use the following arguments when I run updates:
--update --deep --with-bdeps=y --changed-use --backtrack=120
--keep-goingworld

Do I need to use new-use instead?

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

Re: [gentoo-user] Re: downgrading glibc

[Dale]

It may have been you but I was thinking either Walter or Duncan but not
sure.  It could be, I read it on -dev too.  I'm just not sure who it was
just know it is gentoo related, since Gentoo is all I'm subscribed to. 

One would think there would be some method to downgrade that is known to
work and documented.  It can be done for lots of other very important
packages but this one, not so much.  To me, it's just odd. 

At least the OP found a fix tho.  < whew >

Dale

:-)  :-) 

P. S. Top posting since Neil seems to be on some device that started
it.  :-D 


Neil Bothwick wrote:
> I did it once, some years ago. AFAIR I commented out the version che k
> in, i think, the glibc-toolchain eclass then emerged the older
> version. Just make sire you have a binary package of the current
> version that you can unpack in / if things go wrong.
>
> On 22 August 2017 13:53:35 EEST, Dale  wrote:
>
> Raffaele Belardi wrote:
>
> On Fri, 2017-08-18 at 09:00 +0200, Raffaele Belardi wrote:
>
> I hava a build problem upgrading Mythtv to 0.28.1-r1 [1]
> on an ~amd64 system. The problem is related to a glibc API
> change [2] introduced in glibc-2.24 and still present in
> glibc-2.25. So I'm thinking to try the build with an older
> glibc version. Downgrading the system to glibc to 2.23-r3
> means trouble? If not, an emerge @preserved-rebuild after
> the downgrade will be sufficient to not break the rest of
> the system? I suppose a quickpkg of the whole world before
> the downgrade would be a good idea, just in case...
> thanks, raffaele [1]
> https://bugs.gentoo.org/show_bug.cgi?id=604430 [2]
> https://bugs.gentoo.org/show_bug.cgi?id=575232 
>
> Just as follow up, inspired by [2] I fixed the mythtv build
> issue by adding #include  to videosource.cpp
> and continuing the build with ebuild instead of emerge. raffaele
>
>
>
>
> Just a FYI, some have been able to downgrade and it work.  However, you
> have to be prepared for that beforehand I think.  I've seen it posted
> before but can't recall WHO it was.  I was hoping they would reply but
> either they didn't see your post or they are no longer subscribed. 
>
> While it may be possible, it is risky and not recommended.  It's one
> thing that I wish they had a known path to downgrade for.  It's one of
> those, you don't know it's going to break something until it does and
> you have little or no options. 
>
> Glad you got a workaround tho. Maybe some more info will pop up later.
>
> Dale
>
> :-)  :-) 
>
>
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity. 

Re: [gentoo-user] Re: downgrading glibc

[Neil Bothwick]

I did it once, some years ago. AFAIR I commented out the version che k in, i 
think, the glibc-toolchain eclass then emerged the older version. Just make 
sire you have a binary package of the current version that you can unpack in / 
if things go wrong. 

On 22 August 2017 13:53:35 EEST, Dale  wrote:
>Raffaele Belardi wrote:
>> On Fri, 2017-08-18 at 09:00 +0200, Raffaele Belardi wrote:
>>> I hava a build problem upgrading Mythtv to 0.28.1-r1 [1] on an
>~amd64
>>> system. The problem is related to a glibc API change [2] introduced
>>> in
>>> glibc-2.24 and still present in glibc-2.25. So I'm thinking to try
>>> the
>>> build with an older glibc version.
>>>
>>> Downgrading the system to glibc to 2.23-r3 means trouble?
>>> If not, an emerge @preserved-rebuild after the downgrade will be
>>> sufficient to not break the rest of the system?
>>> I suppose a quickpkg of the whole world before the downgrade would
>be
>>> a
>>> good idea, just in case...
>>>
>>> thanks,
>>>
>>> raffaele
>>>
>>>
>>> [1] https://bugs.gentoo.org/show_bug.cgi?id=604430
>>> [2] https://bugs.gentoo.org/show_bug.cgi?id=575232
>> Just as follow up, inspired by [2] I fixed the mythtv build issue by
>> adding #include  to videosource.cpp and continuing
>the
>> build with ebuild instead of emerge.
>>
>> raffaele
>>
>>
>
>Just a FYI, some have been able to downgrade and it work.  However, you
>have to be prepared for that beforehand I think.  I've seen it posted
>before but can't recall WHO it was.  I was hoping they would reply but
>either they didn't see your post or they are no longer subscribed. 
>
>While it may be possible, it is risky and not recommended.  It's one
>thing that I wish they had a known path to downgrade for.  It's one of
>those, you don't know it's going to break something until it does and
>you have little or no options. 
>
>Glad you got a workaround tho. Maybe some more info will pop up later.
>
>Dale
>
>:-)  :-) 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Re: downgrading glibc

[Dale]

Raffaele Belardi wrote:
> On Fri, 2017-08-18 at 09:00 +0200, Raffaele Belardi wrote:
>> I hava a build problem upgrading Mythtv to 0.28.1-r1 [1] on an ~amd64
>> system. The problem is related to a glibc API change [2] introduced
>> in
>> glibc-2.24 and still present in glibc-2.25. So I'm thinking to try
>> the
>> build with an older glibc version.
>>
>> Downgrading the system to glibc to 2.23-r3 means trouble?
>> If not, an emerge @preserved-rebuild after the downgrade will be
>> sufficient to not break the rest of the system?
>> I suppose a quickpkg of the whole world before the downgrade would be
>> a
>> good idea, just in case...
>>
>> thanks,
>>
>> raffaele
>>
>>
>> [1] https://bugs.gentoo.org/show_bug.cgi?id=604430
>> [2] https://bugs.gentoo.org/show_bug.cgi?id=575232
> Just as follow up, inspired by [2] I fixed the mythtv build issue by
> adding #include  to videosource.cpp and continuing the
> build with ebuild instead of emerge.
>
> raffaele
>
>

Just a FYI, some have been able to downgrade and it work.  However, you
have to be prepared for that beforehand I think.  I've seen it posted
before but can't recall WHO it was.  I was hoping they would reply but
either they didn't see your post or they are no longer subscribed. 

While it may be possible, it is risky and not recommended.  It's one
thing that I wish they had a known path to downgrade for.  It's one of
those, you don't know it's going to break something until it does and
you have little or no options. 

Glad you got a workaround tho. Maybe some more info will pop up later.

Dale

:-)  :-) 

Re: [gentoo-user] Question on install

[Dale]

Thomas Mueller wrote:
>> Content-Type: multipart/alternative;
>> boundary="5A3B7F546928893D6B2B7B3A"
>> X-Authority-Analysis: v=2.2 cv=HvEGIwbS c=1 sm=1 tr=0 
>> a=ZNQZ+YIiQ1SmzuxDAKl+CA==:117 a=ZNQZ+YIiQ1SmzuxDAKl+CA==:17 
>> a=x7bEGLp0ZPQA:10 a=ISoD08LcTzsA:10 a=xqWC_Br6kY4A:10 a=KeKAF7QvOSUA:10 
>> a=r77TgQKjGQsHNAKrUKIA:9 a=mlNn8-T5:8
>> a=pGLkceIS:8 a=3Tx8IGE4dgYU5_1tCPoA:9 a=QEXdDO2ut3YA:10 
>> a=B-9MPiEJO1CQoaZW8noA:9 a=UUooY5TJg16SgZ0K:21 a=_W_S_7VecoQA:10 
>> a=_4ER54FGBOWlvg8qisjz:22 a=6kGIvZw6iX1k4Y-7sg4_:22
>> X-Cloudmark-Score: 0
>> X-RR-Connecting-IP: 107.14.168.212:25
>> Content-Type: text/plain; charset=UTF-8
>> Content-Transfer-Encoding: 7bit
> 
>> mad.scientist.at.la...@tutanota.com wrote:
>>> precisely what happened, sorry i didn't realize that chainging the
>>> "subject" line causes confusion.  now i know, now i can avoid that
>>> mistake.
>> --
>>> Securely sent with Tutanota. Claim your encrypted mailbox today!
>>> https://tutanota.com
>>> 21. Aug 2017 09:37 by rdalek1...@gmail.com :
>
>> No problem.  By the way, top posting is sort of frowned on.  However, we
>> also realize some devices don't play well with bottom posting.  If
>> possible, set it to bottom post.  If not possible, oh well.  ;-)
> Multipart/alternative is much worse than top-posting!
>
> Dale
>
>
>

I have mine set to send text only.  It is supposed to do this for
anything related to gentoo.org and kde.org.  Is it not sending text
only?  I'm showing the setting is still active here, although I've had
it disappear in the past after a upgrade. 

I might add, it also no longer defaults to 'reply to list' like it
should either.  It's not a bug, it's a nifty new annoying feature that
the Seamonkey devs decided to install.  When replying to a list, I
either have to use the pull down or take out the personal email addy and
replace it with the list addy.  At some point, I could see me no longer
using Seamonkey after many many years of using it. 

Dale

:-)  :-) 

Re: [gentoo-user] Re: ruby 22

[Neil Bothwick]

RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - - 
newuse @world to apply the change. The depclean should work, 
Just check for stray ruby settings in /etc/portage. 

On 22 August 2017 05:21:23 EEST, John Covici  wrote:
>On Mon, 21 Aug 2017 21:20:04 -0400,
>Alec Ten Harmsel wrote:
>> 
>> 
>> On 08/21/2017 10:13 AM, allan gottlieb wrote:
>> > 
>> > I issued emerge --pretend --verbose --depclean =ruby-2.1.9
>> > and the response was
>> > 
>> >   dev-lang/ruby
>> >  selected: 2.1.9
>> > protected: none
>> >   omitted: 2.2.6
>> > 
>> > Am I correct in believing it is now safe to issue
>> > 
>> >emerge --depclean =ruby-2.1.9
>> > 
>> > thanks,
>> > allan
>> > 
>> 
>> Yes, that should be fine. I rarely look at portage output and
>> just run `emerge -uDN @world' and `emerge --depclean' right after
>> one another, and it always works fine for ruby/python upgrades.
>> 
>> The devs have done such a good job in general that I haven't had
>> any problems just running these commands the past couple years.
>
>I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
>default, but when I ran emerge --depclean I still have packages
>pulling ruby21 as follows:
>
>Calculating dependencies  .. . done!
>  dev-lang/ruby-2.1.10 pulled in by:
>  dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
>dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1
>   dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1
>   dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1
>  dev-ruby/maruku-0.7.3 requires dev-lang/ruby:2.1
> dev-ruby/minitest-5.10.3 requires
>  dev-lang/ruby:2.1
>  dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
>dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
>   dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
>   dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
>  dev-ruby/rdoc-5.1.0 requires dev-lang/ruby:2.1
> dev-ruby/rubygems-2.6.12 requires
>  dev-lang/ruby:2.1
>  dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1
>dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1
>   virtual/rubygems-13 requires dev-lang/ruby:2.1
>   virtual/rubygems-7 requires dev-lang/ruby:2.1
>
>I tried a word ld update, but it didn't update any of those packages
>-- any ideas of how to fix?
>
>-- 
>Your life is like a penny.  You're going to lose it.  The question is:
>How do
>you spend it?
>
> John Covici
> cov...@ccs.covici.com


In -- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Re: ruby 22

[John Covici]

On Tue, 22 Aug 2017 02:58:31 -0400,
Raffaele Belardi wrote:
> 
> On Mon, 2017-08-21 at 22:21 -0400, John Covici wrote:
> > On Mon, 21 Aug 2017 21:20:04 -0400,
> > Alec Ten Harmsel wrote:
> > > 
> > I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
> > default, but when I ran emerge --depclean I still have packages
> > pulling ruby21 as follows:
> > 
> > Calculating dependencies  .. . done!
> >   dev-lang/ruby-2.1.10 pulled in by:
> >   dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
> >  dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1
> > dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1
> > dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1
> >dev-ruby/maruku-0.7.3 requires dev-
> > lang/ruby:2.1
> >   dev-ruby/minitest-5.10.3 requires
> >   dev-lang/ruby:2.1
> >   dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
> >  dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
> > dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
> > dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
> >dev-ruby/rdoc-5.1.0 requires dev-
> > lang/ruby:2.1
> >   dev-ruby/rubygems-2.6.12 requires
> >   dev-lang/ruby:2.1
> >   dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1
> >  dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1
> > virtual/rubygems-13 requires dev-lang/ruby:2.1
> > virtual/rubygems-7 requires dev-lang/ruby:2.1
> > 
> > I tried a word ld update, but it didn't update any of those packages
> > -- any ideas of how to fix?
> 
> Did you do an emerge @preserved-rebuild? I had the a similar problem
> but only for a couple of packages (racc and another one), it was
> quickly fixed that way. But I never had RUBY_TARGETS set so maybe YMMV.
There are no libraries listed for rebuilding, emerge
@preserved-rebuild says 0 packages.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

Re: [gentoo-user] Question on install

[Thomas Mueller]

> Content-Type: multipart/alternative;
> boundary="5A3B7F546928893D6B2B7B3A"
> X-Authority-Analysis: v=2.2 cv=HvEGIwbS c=1 sm=1 tr=0 
> a=ZNQZ+YIiQ1SmzuxDAKl+CA==:117 a=ZNQZ+YIiQ1SmzuxDAKl+CA==:17 
> a=x7bEGLp0ZPQA:10 a=ISoD08LcTzsA:10 a=xqWC_Br6kY4A:10 a=KeKAF7QvOSUA:10 
> a=r77TgQKjGQsHNAKrUKIA:9 a=mlNn8-T5:8
> a=pGLkceIS:8 a=3Tx8IGE4dgYU5_1tCPoA:9 a=QEXdDO2ut3YA:10 
> a=B-9MPiEJO1CQoaZW8noA:9 a=UUooY5TJg16SgZ0K:21 a=_W_S_7VecoQA:10 
> a=_4ER54FGBOWlvg8qisjz:22 a=6kGIvZw6iX1k4Y-7sg4_:22
> X-Cloudmark-Score: 0
> X-RR-Connecting-IP: 107.14.168.212:25

> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 7bit

> mad.scientist.at.la...@tutanota.com wrote:
> > precisely what happened, sorry i didn't realize that chainging the
> > "subject" line causes confusion.  now i know, now i can avoid that
> > mistake.
>
> --
> > Securely sent with Tutanota. Claim your encrypted mailbox today!
> > https://tutanota.com
>
> > 21. Aug 2017 09:37 by rdalek1...@gmail.com :


> No problem.  By the way, top posting is sort of frowned on.  However, we
> also realize some devices don't play well with bottom posting.  If
> possible, set it to bottom post.  If not possible, oh well.  ;-)

Multipart/alternative is much worse than top-posting!

Dale

[gentoo-user] Re: downgrading glibc

[Raffaele Belardi]

On Fri, 2017-08-18 at 09:00 +0200, Raffaele Belardi wrote:
> I hava a build problem upgrading Mythtv to 0.28.1-r1 [1] on an ~amd64
> system. The problem is related to a glibc API change [2] introduced
> in
> glibc-2.24 and still present in glibc-2.25. So I'm thinking to try
> the
> build with an older glibc version.
> 
> Downgrading the system to glibc to 2.23-r3 means trouble?
> If not, an emerge @preserved-rebuild after the downgrade will be
> sufficient to not break the rest of the system?
> I suppose a quickpkg of the whole world before the downgrade would be
> a
> good idea, just in case...
> 
> thanks,
> 
> raffaele
> 
> 
> [1] https://bugs.gentoo.org/show_bug.cgi?id=604430
> [2] https://bugs.gentoo.org/show_bug.cgi?id=575232

Just as follow up, inspired by [2] I fixed the mythtv build issue by
adding #include  to videosource.cpp and continuing the
build with ebuild instead of emerge.

raffaele

Re: [gentoo-user] Re: ruby 22

[Raffaele Belardi]

On Mon, 2017-08-21 at 22:21 -0400, John Covici wrote:
> On Mon, 21 Aug 2017 21:20:04 -0400,
> Alec Ten Harmsel wrote:
> > 
> I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
> default, but when I ran emerge --depclean I still have packages
> pulling ruby21 as follows:
> 
> Calculating dependencies  .. . done!
>   dev-lang/ruby-2.1.10 pulled in by:
>   dev-ruby/hoe-3.13.0 requires dev-lang/ruby:2.1
>dev-ruby/json-1.8.3 requires dev-lang/ruby:2.1
>   dev-ruby/json-2.1.0 requires dev-lang/ruby:2.1
>   dev-ruby/kpeg-1.1.0 requires dev-lang/ruby:2.1
>  dev-ruby/maruku-0.7.3 requires dev-
> lang/ruby:2.1
> dev-ruby/minitest-5.10.3 requires
>   dev-lang/ruby:2.1
>   dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
>dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
>   dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
>   dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
>  dev-ruby/rdoc-5.1.0 requires dev-
> lang/ruby:2.1
> dev-ruby/rubygems-2.6.12 requires
>   dev-lang/ruby:2.1
>   dev-ruby/test-unit-3.2.5 requires dev-lang/ruby:2.1
>dev-ruby/yard-0.9.8 requires dev-lang/ruby:2.1
>   virtual/rubygems-13 requires dev-lang/ruby:2.1
>   virtual/rubygems-7 requires dev-lang/ruby:2.1
> 
> I tried a word ld update, but it didn't update any of those packages
> -- any ideas of how to fix?

Did you do an emerge @preserved-rebuild? I had the a similar problem
but only for a couple of packages (racc and another one), it was
quickly fixed that way. But I never had RUBY_TARGETS set so maybe YMMV.

raffaele