Am 06.04.2017 um 10:27 schrieb Fabian Vogt:

Hi,

Am Donnerstag, 6. April 2017, 10:12:52 CEST schrieb Freek de Kruijf:

...

Apparently after updating the repository KDE:Extra of Tumbleweed and refreshing the local storage using zypper, zypper asks again for acceptance of the gpg-pubkey, which I do using the always option. But the next time this is asked again.

I noticed this as well and I have no idea what's wrong. Any hints (or help) is appreciated...

Cheers, Fabian

-------------------------------------------------------------------------------- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

My main suspect is Packagekit. Look at /var/log/pk_backend_zypp. I have the same problem with my personal home repository for a couple of days now. Today I removed Packagekit from my system. Lets see, what happens on the next update from my home repo. Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 07.04.2017 um 10:21 schrieb Freek de Kruijf:

Op donderdag 6 april 2017 19:46:01 CEST schreef Hendrik Woltersdorf: [snip] I was triggered by the messages of Packagekit, and used zypper dup to perform the update. Using zypper I got this question, so I answered with always. But later, not with every update, the question shows up again with the same gpg- pubkey. Somehow this key is not stored in its proper place. The key is in "http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Tumbleweed/ repodata/repomd.xml.key" but I do not know how to store this key in its proper place.

You find the keys in the rpm database: rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}\n' After "zypper ref", and - if necessary - storing new keys you can find them there. I found that they disappear when Packagekit runs. Later I find traces of that in /var/log/pk_backend_zypp with: grep -C2 "has been removed" /var/log/pk_backend_zypp Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

There does seem to be *something* wrong with PackageKit since the last update or two. Trying to use zypper or YaST, I get the "PackageKit is already running" message every time now. And KDE Discover now reproducibly crashes every time I search for something. What's the easiest way to install all the debug symbols so I can analyze the coredump? Nate On 04/09/2017 12:50 PM, Hendrik Woltersdorf wrote:

Am 06.04.2017 um 19:46 schrieb Hendrik Woltersdorf:

...

Am 06.04.2017 um 10:27 schrieb Fabian Vogt:

...

Hi,

Am Donnerstag, 6. April 2017, 10:12:52 CEST schrieb Freek de Kruijf:

...

Apparently after updating the repository KDE:Extra of Tumbleweed and refreshing the local storage using zypper, zypper asks again for acceptance of the gpg-pubkey, which I do using the always option. But the next time this is asked again. I noticed this as well and I have no idea what's wrong. Any hints (or help) is appreciated...

Cheers, Fabian

-------------------------------------------------------------------------------- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

My main suspect is Packagekit. Look at /var/log/pk_backend_zypp.

I have the same problem with my personal home repository for a couple of days now. Today I removed Packagekit from my system. Lets see, what happens on the next update from my home repo.

Hendrik

In the meantime I got an update from my home repository and without any interfering from the removed Packagekit there are no more questions, to accept "new" keys. So I think, we found the culprit. The next question is, why does Packagekit remove these keys?

Some snippets from my logs:

2017-04-05 20:49:03 <1> schlepptop.site(2038) [zypp++] ExternalProgram.cc(start_program):249 Executing '/usr/bin/gpg2' '--list-public-keys' '--homedir' '/var/tmp/zypp.Qb8XuG/zypp-trusted-kr2KkfYV' '--no-default-keyring' '--quiet' '--with-colons' '--fixed-list-mode' '--with-fingerprint' '--with-sig-list' '--no-tty' '--no-greeting' '--batch' '--status-fd' '1' ... 2017-04-05 20:49:03 <1> schlepptop.site(2038) [zypp::KeyRing] KeyRing.cc(getData):169 [98E2444254139549-55a21502] [home:hendwolt OBS Project <home:hendwolt@build.opensuse.org>] [65BD0DE44DD8BE950CBC291A98E2444254139549] [TTL 166] ... 2017-04-05 20:49:03 <1> schlepptop.site(2038) [zypp++] RpmDb.cc(updateIf):909 Old key in Z: gpg-pubkey-54139549-55a21501 2017-04-05 20:49:03 <1> schlepptop.site(2038) [zypp++] RpmDb.cc(computeKeyRingSync):946 gpg-pubkey-54139549-55a21502 _Z ... 2017-04-05 20:49:03 <1> schlepptop.site(2038) [zypp++] ExternalProgram.cc(start_program):249 Executing '/usr/bin/gpg2' '--delete-keys' '--homedir' '/var/tmp/zypp.Qb8XuG/zypp-trusted-kr2KkfYV' '--no-default-keyring' '--yes' '--quiet' '--no-tty' '--batch' '--status-fd' '1' '98E2444254139549' ... 2017-04-05 20:49:03 <1> schlepptop.site(2038) [zypp::KeyRing] KeyRing.cc(deleteKey):568 Deleted key 98E2444254139549 from keyring /var/tmp/zypp.Qb8XuG/zypp-trusted-kr2KkfYV 2017-04-05 20:49:03 <1> schlepptop.site(2038) [zypp] RpmDb.cc(trustedKeyRemoved):140 Trusted key removed from zypp Keyring. Removing... ... 2017-04-05 20:49:04 <1> schlepptop.site(2038) [zypp] RpmDb.cc(removePubkey):1201 Key [98E2444254139549-55a21502] [home:hendwolt OBS Project <home:hendwolt@build.opensuse.org>] [65BD0DE44DD8BE950CBC291A98E2444254139549] [TTL 166] has been removed from RPM trusted keyring

Any ideas, why Packagekit "thinks" this key is too old?

Hendrik

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org