From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: gentoo-user@lists.gentoo.org, thelma@sys-concept.com
Subject: Re: [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring
Date: Fri, 8 Jul 2022 11:01:17 +0200 [thread overview]
Message-ID: <25287.62045.200260.80162@tux.local> (raw)
In-Reply-To: Msg <f9d15101-1101-b52c-7c27-1438672e06d5@sys-concept.com> of 2022-07-07 23:13:47 -0600 from thelma@sys-concept.com
Thelma,
On Thursday, 2022-07-07 23:13:47 -0600, thelma@sys-concept.com wrote:
> ...
> By upgrading one of my system, I've just noticed this behaviour is enforced (I think) by new package that was pulled by emerge:
> [ebuild N ] gnome-base/gnome-keyring-42.1 USE="pam ssh-agent (-selinux) -systemd -test"
> Upgrading just "chrome" did not ask me for any keyring password.
>
> I don't use gnome, I use XFCE but I guess one of the package pull this as a dependency.
Run
$ emerge --pretend --unmerge gnome-base/gnome-keyring
to get the list of packages depending on "gnome-base/gnome-keyring".
Then check each of these packages for a set USE flag causing "gnome-
base/gnome-keyring" to be pulled in. At least in many cases such a USE
flag will be named just "gnome-keyring".
Sincerely,
Rainer
next prev parent reply other threads:[~2022-07-08 9:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 2:11 [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring thelma
2022-07-08 2:23 ` Dale
2022-07-08 3:20 ` thelma
2022-07-08 3:28 ` Dale
2022-07-08 3:43 ` thelma
2022-07-08 3:50 ` Dale
2022-07-08 5:13 ` thelma
2022-07-08 6:44 ` Dale
2022-07-09 17:12 ` Wols Lists
2022-07-09 18:06 ` [gentoo-user] " Martin Vaeth
2022-07-09 21:34 ` [gentoo-user] " Neil Bothwick
2022-07-08 9:01 ` Dr Rainer Woitok [this message]
2022-07-08 9:48 ` John Covici
2022-07-08 13:34 ` Matt Connell
2022-07-08 14:02 ` Arve Barsnes
2022-07-08 16:20 ` thelma
2022-07-08 17:12 ` Neil Bothwick
2022-07-08 17:26 ` thelma
2022-07-08 18:07 ` Matt Connell
2022-07-09 17:02 ` Dr Rainer Woitok
2022-07-08 14:02 ` Matt Connell
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=25287.62045.200260.80162@tux.local \
--to=rainer.woitok@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=thelma@sys-concept.com \
/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