From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] chrome vs. wayland wierdness
Date: Fri, 5 Aug 2022 00:12:02 +0100 [thread overview]
Message-ID: <20220805001202.3e646fca@digimed.co.uk> (raw)
In-Reply-To: <tcheu6$hn8$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Thu, 4 Aug 2022 21:49:59 -0000 (UTC), Grant Edwards wrote:
> verything seemed to be fine (IIRC, it upgraded chrome).
>
> emerge --depeclean --ask
>
> That removed a couple wayland packages (yay! I didn't really want
> wayland). Then it warned me
>
> !!! existing preserved libs:
> >>> package: dev-libs/wayland-1.21.0
> * - /usr/lib64/libwayland-client.so.0
> * - /usr/lib64/libwayland-client.so.0.21.0
> * used by /opt/google/chrome/libGLESv2.so
> (www-client/google-chrome-104.0.5112.79) Use emerge @preserved-rebuild
> to rebuild packages using these libraries
>
> I do as instructed and run 'emerge @preserved-rebuild' and it
> reinstalls chrome.
>
> But a subsequent emerge --depeclean --ask again produces the same
> warnings about wayland libraries that have been preserved.
>
> Are the dependencies for chrome broken?
chrome is a binary package, unlike chromium, so rebuilding will not change
the libraries it depends on. It sounds like those wayland packages should
not have been depcleaned and are a requirement for chrome.
--
Neil Bothwick
Zmodem has bigger bits, softer blocks, and tighter ASCII
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-04 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 21:49 [gentoo-user] chrome vs. wayland wierdness Grant Edwards
2022-08-04 23:12 ` Neil Bothwick [this message]
2022-08-05 0:35 ` [gentoo-user] " Grant Edwards
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=20220805001202.3e646fca@digimed.co.uk \
--to=neil@digimed.co.uk \
--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