Thelma
On 7/8/22 08:02, Arve Barsnes wrote:
On Fri, 8 Jul 2022 at 15:34, Matt Connell <[email protected]> wrote:
Should not this instruction say emerge --pretend --depclean rather
than --unmerge ?
Since its pretended, the result is the same, ultimately.
Actually, none of them gives you any info about why a package is
installed, and --unmerge doesn't even try to check. Without --pretend
it's perfectly happy to let you shoot yourself in the foot. What you
actually need to get portage to tell you what requires the package in
question is
# emerge --pretend --depclean --verbose gnome-keyring
Regards,
Arve
OK I think I got to the bottom of this, it is caused by package upgrade:
[ebuild U ] app-crypt/gcr-3.41.0 [3.40.0] USE="gtk introspection vala -gtk-doc
-systemd% -test"
All other packages are new and pull-in as a dependency:
gnome-base/gnome-keyring-42.1 pulled in by:
virtual/secret-service-0 requires gnome-base/gnome-keyring
grep secret-service upgrade_07-07-22.txt
[ebuild N ] virtual/secret-service-0
virtual/secret-service-0 pulled in by:
app-crypt/libsecret-0.20.5-r3 requires =virtual/secret-service-0,
virtual/secret-service
grep app-crypt/libsecret upgrade_07-07-22.txt
[ebuild N ] app-crypt/libsecret-0.20.5-r3 USE="crypt introspection vala -gtk-doc -test
-tpm" ABI_X86="(64) -32 (-x32)"
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.
So maybe it is better to leave it as it is, instead of fighting the system :-)
But it would be nice if there were some notes about it during emerge.
All of a sudden when starting chrome, a message box pops up "choose password for new
keyring" (without any explanation) and all screen is frozen, only option is to enter a
password or "cancel it".
Thelma
