public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arve Barsnes <arve.barsnes@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Klayout and ruby target problem.
Date: Sun, 25 Jun 2023 18:32:32 +0200	[thread overview]
Message-ID: <CAJjrzcWJ7WC-2_r0ynpVmB_HeVMvNdbyMVw=jnJf-G9XAO64Uw@mail.gmail.com> (raw)
In-Reply-To: <41ac1a54-6b1d-c03d-76bb-12c79b659b9d@gmail.com>

On Sun, 25 Jun 2023 at 18:19, Dale <rdalek1967@gmail.com> wrote:
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     ruby_targets_ruby30
>
>   The above constraints are a subset of the following complete expression:
>     exactly-one-of ( python_single_target_python3_10
> python_single_target_python3_11 ) any-of ( ruby_targets_ruby30 )
>
> By default, it has no ruby target it seems, although it used to.  The
> on/off status changes.  Setting to match the old way made it worse, as
> mentioned above.  I can't figure out how to make this work.

This might be a bug from the recent move to ruby31 as the default
target, but the easy solution as I see it now is installing the
unstable version klayout-0.28.9, which has the ruby31 target
available.

I found this bug, https://bugs.gentoo.org/903497, which was about
stabilising 0.28.5 "because needed by ruby30", so I assume a similar
action is needed now.

Regards,
Arve


  reply	other threads:[~2023-06-25 16:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25 16:19 [gentoo-user] Klayout and ruby target problem Dale
2023-06-25 16:32 ` Arve Barsnes [this message]
2023-06-25 17:24   ` Dale
2023-06-25 17:34     ` Arve Barsnes
2023-06-25 20:11       ` Dale
2023-06-25 17:10 ` Matt Connell
2023-06-25 17:34   ` Dale
2023-06-25 20:21 ` Andreas K. Huettel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJjrzcWJ7WC-2_r0ynpVmB_HeVMvNdbyMVw=jnJf-G9XAO64Uw@mail.gmail.com' \
    --to=arve.barsnes@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox