http://bugzilla.opensuse.org/show_bug.cgi?id=925659
Edgar Aichinger changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |edogawa@aon.at
--- Comment #3 from Edgar Aichinger ---
I see the same behaviour for other OBS projects, since months, I'm not quite
sure for how long now but it could be since installing 13.2 short after its
release last November... asking on IRC about this yielded no reaction so far...
anyway, for me the key accept dialog in yast, or the respective zypper question
comes up for several OBS projects, whenever their repositories get an update
and need a zypper refresh. I'll try to list them from memory, in case it helps
to narrow the issue down:
Emulators: wine CVS builds
Graphics project
mozilla
home:ecsos
home:AndreasSchwab and one of his subprojects
devel:languages:ruby
here's an example from running "zypper ref", right now:
Neuen Signierungsschlüssel für Repository oder Paket erhalten:
Repository: Ruby Extensions (openSUSE_13.2)
Name des Schlüssels: devel:languages:ruby OBS Project
devel:languages:ruby@build.opensuse.org
Schlüsselfingerabdruck: A9EA39C4 9B6B9E93 B6863F84 9AF0C9A2 0E9AF123
Schlüssel erstellt: Mi 04 Jun 2014 06:10:54 CEST
Schlüssel läuft ab: Fr 12 Aug 2016 06:10:54 CEST
RPM-Name: gpg-pubkey-0e9af123-538e9c4e
Wollen Sie den Schlüssel (a)bweisen, ihm (t)emporär oder (i)mmer vertrauen?
[a/t/i/? zeigt alle Optionen] (a):
I always answer "i" (german for "trust permanently"), then it accepts and
continues normally, and still the next time a cache refresh is due, i'm
presented the same dialog/question again...
--
You are receiving this mail because:
You are on the CC list for the bug.