From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6754F158020 for ; Tue, 11 Oct 2022 23:52:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E2C92E0920; Tue, 11 Oct 2022 23:52:47 +0000 (UTC) Received: from mail-qk1-f172.google.com (mail-qk1-f172.google.com [209.85.222.172]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9F1F8E08EC for ; Tue, 11 Oct 2022 23:52:47 +0000 (UTC) Received: by mail-qk1-f172.google.com with SMTP id 8so2091332qka.1 for ; Tue, 11 Oct 2022 16:52:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:content-disposition:message-id :in-reply-to:mime-version:to:subject:from:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=cl6ergrC8KWtlgAoMG4FwSWeIR9XZPrxIKBXdApsYBo=; b=ABOFTKAr5jK0ETgd0YraLXZ1WzbVxqNhBxxTewAJameHqsFlLXUJPr9Dgy78qBdisc KI+wMA8euImiMC+psxlV/4cG/f34BOpxMRgUZJbzQ9iOX7HwdlmF7wHLpU9kek9NtkMn 5O9NurVnxR+mK3+Yi4vqUOJhUXZa/WtECkvtnw4G+sxhQDvqN81sBTDSNkRFTtquWwIo 426fQzOaQeKmdtXN3N4WnFZAi50TShPM5fQD8kkXnLa1ibh5hSAtVUBYt7WjJn5tnAU+ L8oAKWbj+NXXa7YqeC4yR8zt9tjFNvrfGvAjG3iJEFVM9vy7fJw+C52oXN+2xiXC8D86 uMoA== X-Gm-Message-State: ACrzQf3Rt41rP3eQ2Oi8OHweKKA2Do0OHNDr6yprnnSJ/zw/3p7sOT8A r/MAUEWIzjWoyuz/X5+QbjfhOI9LqrbHmsQv X-Google-Smtp-Source: AMsMyM5C8M39fmQV+PG5U71bcuH1A9CwF/4ykb+Vg6kGTbwJx+3rxouiCOvzBstYZUuyrg3HXaJFqg== X-Received: by 2002:a37:9ac8:0:b0:6ea:a959:3eb5 with SMTP id c191-20020a379ac8000000b006eaa9593eb5mr13767385qke.551.1665532366538; Tue, 11 Oct 2022 16:52:46 -0700 (PDT) Received: from ffortso9 (c-73-238-129-126.hsd1.ct.comcast.net. [73.238.129.126]) by smtp.gmail.com with ESMTPSA id bk19-20020a05620a1a1300b006ec771d8f89sm7744808qkb.112.2022.10.11.16.52.45 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Oct 2022 16:52:46 -0700 (PDT) Date: Tue, 11 Oct 2022 19:52:44 -0400 From: Jack Subject: Re: [gentoo-user] problems emerging some ruby packages To: gentoo-user@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: <20221011224302.577a9db5@digimed.co.uk> X-Mailer: Balsa 2.6.4 Message-Id: Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 4f66c56e-4ba1-47e9-bee3-cc9a4c21bd9c X-Archives-Hash: 4d701f10d09581d7b585c4850764621c On 2022.10.11 17:43, Neil Bothwick wrote: > On Tue, 11 Oct 2022 16:02:52 -0400, Jack wrote: >=20 > > For example, "emerge -1 dev-ruby/thor" gives me > > >> !!! Problem resolving dependencies for dev-ruby/thor ... done! > > >> !!! The ebuild selected to satisfy "dev-ruby/thor" has unmet =20 >> requirements. >> - dev-ruby/thor-1.2.1::gentoo USE=3D"-doc -test" ABI_X86=3D"(64)" =20 >> RUBY_TARGETS=3D"-ruby27 (-ruby30) (-ruby31)" >=20 > ruby30 and ruby31 are in parentheses, which means they are not =20 > available. Given everything below - what other reasons might there be for this? =20 I've yet to find any pattern of the difference between the ebuilds for =20 the small number of dev-ruby packages that show this problem, and those =20 for the the thirty plus which have installed just fine. > > > > The following REQUIRED_USE flag constraints are unsatisfied: > > any-of ( ruby_targets_ruby27 ruby_targets_ruby30 =20 > ruby_targets_ruby31 ) > > >> I would expect USE_RUBY=3D"ruby31" to translate into =20 >> ruby_targets_ruby31, but even explicitly adding that to package.use =20 >> has no effect. >=20 > The ebuild contains USE_RUBY=3D"ruby26 ruby27" ruby_add_bdepend " Hmm. It looks to me that line should probably be 'USE_RUBY=3D"ruby26 =20 ruby27 ruby30 ruby31" ruby_add_bdepend "' However, as it only affects =20 the required ruby version for two depedencies only if the test use flag =20 is set (it is not) I'm not sure why it would matter. I suppose it is likely just a typo in the ebuild. They removed ruby25 =20 from 1.1.0 but didn't add the newer ruby versions. Actually even 1.1.0 =20 may be broken as it includes ruby30 in USE_RUBY but not on the =20 ruby_add_bdepend line. However, I just made an -r1 in my local =20 overlay, adding the new ruby versions to that line, and I still get the =20 same error. So I'm actually still stuck figuring out why this ebuild =20 won't take ruby31. >=20 > 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 =20 to? >=20 > I must say I find the whole RUBY_* thing even more troublesome than =20 > the PYTHON_* stuff, and that's saying something! That I agree with. If I knew then what I know now, I would have argued =20 much more vigorously against using Ruby on Rails for this web site. =20 But that's fodder another entire thread. >=20 >=20 > -- > Neil Bothwick Jack