Re: Is there something going on with dev-ruby packages?

On 4/6/26 11:24 AM, Christopher Fore wrote:
> Hello,
>
> We're just trying to add Ruby 3.3 to packages that are still on 3.2
> since 3.2 is EOL now[0] and didn't expect the dependency issues.
>
> A fix got committed today[1] that will hopefully fix said dependency
> issues. We're hoping to get Ruby 3.4 going as the default in the near
> future with 4.0 as a sort of reach goal just to have some timeline
> padding since 3.3 is only getting security updates now.
>
> Hopefully the next update is smoother! :)
>
>
> Thanks,
> Christopher
>
> [0]: https://www.ruby-lang.org/en/downloads/branches/#ruby-32
> [1]: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f4acf7c20ae9ea8c0fbd03cd7414f9200bbd42b
>


Good to know.  I figured it was some change that was going on that maybe 
had a few kinks to work out.  I did start to wonder when my backup/old 
rig updated smoothly tho.

I was mostly making sure it was not some error on my part. Sometimes I 
can have a entry in a /etc/portage/<file> that throws things off and it 
is not obvious from the error.  I don't have a ruby entry there but I 
thought it might be something pulling in something ruby related and 
starting a chain reaction.  That can happen and may not change until I 
find the entry that causes it. Since this is not the case, next weekend 
will likely go smoothly.  I may even try again later tonight/early 
morning and see if things go smoothly.  I can do it in my chroot.

One thing I like about emerge, if it can't figure out a sane upgrade 
path, it just skips that and updates what it thinks is safe to upgrade.  
It updated a lot of KDE stuff and everything is working fine.  So emerge 
updated the packages it could resolve and skipped everything else.

Oh, my previous post should have read 'other packages that are *not* 
needed for booting'.  Funny how that one word changes so much.  o_O It's 
rare, very rare, that I keyword a package that involves the booting of 
my OS.  I like being able to boot.  I hate having to boot some other 
image, mount and chroot and all that stuff.

Thanks for the info.  At least I know it is likely not me and something 
I need to fix but just some major changes that has a little hiccup at 
the moment.

Dale

:-)  :-)