On Sat, 9 Jul 2022 18:12:51 +0100, Wols Lists wrote:
> > Could disabling a USE flag remove that dependency? It may not be
> > google-chrome itself but something else it depends on. Using the
> > --tree option may help here. Masking the keyring package may force
> > emerge to shine some light
Wols Lists wrote:
> So why am I glad my USE= includes "-gnome" :-)
>
> Although I don't use Chrome, so I wouldn't notice anyways :-)
You are wrong: The dependency is unconditional, so USE=-gnome won't help.
What helps is to put a version of virtual/secret-service in your local
repository which
On 08/07/2022 07:44, Dale wrote:
the...@sys-concept.com wrote:
On 7/7/22 21:50, Dale wrote:
You found a solution that works. That's great. Now you can get back to
doing more important things. ;-)
Dale
:-) :-)
By upgrading one of my system, I've just noticed this behaviour is
enforced
Thelma,
On Friday, 2022-07-08 10:20:12 -0600, you wrote:
> ...
> app-crypt/libsecret-0.20.5-r3 pulled in by:
> app-crypt/gcr-3.41.0 requires >=app-crypt/libsecret-0.20
>
> And "app-crypt/gcr" was an upgrade.
This does not happen with the stable version 3.40.0 of "app-crypt/gcr",
only
4 matches
Mail list logo
