Re: [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring
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 on what needs the package as well. It > > should grumble about it being masked along with what needs it. > > > > Sort of odd that something like this pops up all of a sudden with no > > notice of the change. > > > So why am I glad my USE= includes "-gnome" :-) > > Although I don't use Chrome, so I wouldn't notice anyways :-) google-chrome is a binary package, so USE flags won't make any difference to its dependencies. -- Neil Bothwick We are from the planet Taglinis. Take us to your reader! pgpOm9UMqrzR7.pgp Description: OpenPGP digital signature
[gentoo-user] Re: google-chrome-103.0.5060 - choose password for new keyring
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 does not actually pull in anything. That's not very elegent, though: If suddenly the dependency is real, things will break “silently”.
Re: [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring
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 (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. 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 on what needs the package as well. It should grumble about it being masked along with what needs it. Sort of odd that something like this pops up all of a sudden with no notice of the change. So why am I glad my USE= includes "-gnome" :-) Although I don't use Chrome, so I wouldn't notice anyways :-) Cheers, Wol
Re: [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring
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 with the non-stable version 3.41.0 which has this additional dep- endency. But then, as soon as 3.41.0 will become stable you'd have the same problem. Sincerely, Rainer
