Re: [gentoo-user] problems emerging some ruby packages (almost solved)
On 2022.10.12 01:18, Arve Barsnes wrote: On Wed, 12 Oct 2022 at 02:12, Jack wrote: As I said in my reply to Neil, why would this happen in just a handful of packages, but not in over thirty others? mini_mime is the other problem package, and it does not use ruby_add_bdepend so there is only one line with USE_RUBY: 'USE_RUBY="ruby26 ruby27 ruby30 ruby31"'. > So - why is ruby31 disabled for (so far) only these two packages? (The other packages which are failing depend on one of these two.) Maybe these two are just written more strict? I'm unable to read the eclass to determine how it masks these flags on a stable system on these packages, it will happily install it with ruby31 on my unstable system, but you can try to unmask the flag in /etc/portage/package.use.mask dev-ruby/thor -ruby_targets_ruby31 Well, this almost did the trick. That file has to be in /etc/portage/profile. Just having it in /etc/portage did not work. It turns out the masking of ruby_targets_ruby30 and ruby_targets_ruby31 is in /usr/portage/profiles/base/use.stable.mask. I still have no idea why ruby31 was masked for these two packages (thor and mini_mime) but not for over thirty other dev-ruby packages I have installed. My next issue is that I installed several packages with -O (skip dependencies) so now I have to work my way through finding all the uninstalled dependencies I skipped, many of which will need to be unmasked as they are testing. Thanks for all the suggestions and support, and I'll report back either when it's all done or if I find another blockage. Jack
Re: [gentoo-user] problems emerging some ruby packages
On Wednesday, 12 October 2022 01:12:00 BST Jack wrote: > On 2022.10.11 19:41, Michael wrote: > > NOTE: ruby 3.0 and 3.1 are marked as testing. > > I explicitly have ruby-3.1 unmasked with "=dev-lang/ruby-3.1.2-r1 > ~amd64" in package.accept_keyword, and USE_RUBY="ruby31" in make.conf. Try setting in your /etc/make.conf this expression instead: RUBY_TARGETS="ruby31" as per https://wiki.gentoo.org/wiki/Ruby and if you have not yet switched to using it, run: eselect ruby set ruby31 > I do not see any reference to ruby in the profile. Is there somewhere > else I need to unmask something? emerge --info also says > 'RUBY_TARGETS="ruby31"' as its only reference to a specific ruby > version. That's what you'd add in your make.conf, for this ruby slot to be used globally. > As I said in my reply to Neil, why would this happen in just a handful > of packages, but not in over thirty others? mini_mime is the other > problem package, and it does not use ruby_add_bdepend so there is only > one line with USE_RUBY: 'USE_RUBY="ruby26 ruby27 ruby30 ruby31"'. I think it is relevant to how these USE variables are parsed and their syntax. If you specify the ruby version via a USE flag, then this should be: USE="ruby31" emerge -pv blah-blah You need to specify it as above and since you want to use ruby31 wholesale on your system, set it in make.conf as the wiki page explains. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] problems emerging some ruby packages
On Tue, 11 Oct 2022 19:52:44 -0400, Jack wrote: > > Have you tried setting RUBY_TARGETS to ruby27 for this package? > Why would I do that if I don't have ruby-2.7 installed, nor do I want > to? We don't always get what we want. If thor currently needs 2.7 then you have to have it if you want thor. Try it with an emerge -p. Whether it works or not, you will have further clues as to the source of the issue. -- Neil Bothwick Anything worth fighting for is worth fighting dirty for. pgpIVcOyHaWde.pgp Description: OpenPGP digital signature
