public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problems with world update and chromium and maybe something else
Date: Tue, 10 Dec 2024 10:43:04 -0500	[thread overview]
Message-ID: <00808d43-5bfc-464c-8053-f1644040299e@gentoo.org> (raw)
In-Reply-To: <m1o71jftgl.wl-covici@ccs.covici.com>


[-- Attachment #1.1: Type: text/plain, Size: 2564 bytes --]

On 12/10/24 10:28 AM, covici@ccs.covici.com wrote:
> Hi.  So, in my attempt at the recent world update, I would like not to
> use  wayland because of accessibility problems and yet I see:
>
> Script started on 2024-12-10 10:09:20-05:00 [COMMAND="emerge --update --deep --changed-use --with-bdeps=y --keep-going world" TERM="xterm-256color" TTY="/dev/pts/0" COLUMNS="80" LINES="24"]
> ^[]0;emerge\a
> These are the packages that would be merged, in order:
> 
> Calculating dependencies  
> 
> !!! Problem resolving dependencies for www-client/chromium from @selected
> ... done!
> Dependency resolution took 5.70 s (backtrack: 0/200).
> 
> 
> !!! The ebuild selected to satisfy "www-client/chromium" has unmet requirements.
> - www-client/chromium-132.0.6834.32::gentoo USE="X cups hangouts official proprietary-codecs qt5 qt6 screencast system-harfbuzz system-zstd vaapi widevine -bindist -custom-cflags -debug -ffmpeg-chromium -gtk4 (-headless) -kerberos -pax-kernel (-pgo) -pulseaudio (-selinux) (-system-icu) -system-png -test -wayland" ABI_X86="(64)" L10N="af am ar bg bn ca cs da de el en-GB es es-419 et fa fi fil fr gu he hi hr hu id it ja kn ko lt lv ml mr ms nb nl pl pt-BR pt-PT ro ru sk sl sr sv sw ta te th tr uk ur vi zh-CN zh-TW" LLVM_SLOT="19"
> 
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     screencast? ( wayland )


You see portage telling you that the "screencast" USE flag is enabled by
default, and that it depends on the "wayland" USE flag, and you cannot
disable wayland unless you also disable screencast.

You can just disable screencast. It is enabled as a default by some
desktop profiles, but nothing requires you to use those defaults.


>   The above constraints are a subset of the following complete expression:
>     !headless? ( any-of ( X wayland ) ) pgo? ( X !wayland ) qt6? ( qt5 ) screencast? ( wayland ) ffmpeg-chromium? ( bindist proprietary-codecs ) exactly-one-of ( llvm_slot_19 )
> 
> (dependency required by "@selected" [set])
> (dependency required by "@world" [argument])
> ^[]0;root@:/usr/src\a
> Script done on 2024-12-10 10:09:26-05:00 [COMMAND_EXIT_CODE="1"]
> 
> Also, where do I put lvm19 --what is portage looking for?


Portage isn't asking you to do anything with llvm19. "A subset of the
following complete expression" just means that portage is providing
additional full diagnostic information about the *entire* package
details. The screencast part is the only issue.

llvm19 is enabled and forced by default anyway.

-- 
Eli Schwartz

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2024-12-10 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 15:28 [gentoo-user] problems with world update and chromium and maybe something else covici
2024-12-10 15:43 ` Eli Schwartz [this message]
2024-12-10 17:58   ` covici

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=00808d43-5bfc-464c-8053-f1644040299e@gentoo.org \
    --to=eschwartz@gentoo.org \
    --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