[opensuse] Zypper forgets trusted repo keys every 24 hours
Hi, I know that there is a similar thread that has this issue. I don't know why, but this happens every day if I request a repo refresh from zypper: zypper shell zypper> refresh Retrieving repository 'Editors' metadata .............................................................................................................................[done] Building repository 'Editors' cache ..................................................................................................................................[done] Repository 'Emu' is up to date. Repository 'Graphics' is up to date. Repository 'Node.js' is up to date. Repository 'Python3' is up to date. Repository 'nVidia Graphics Drivers' is up to date. Repository 'openSUSE BuildService - Mono:Community' is up to date. Repository 'openSUSE BuildService - Education' is up to date. Retrieving repository 'openSUSE BuildService - KDE:Extra' metadata ------------------------------------------------------------------------------------------------------[/] New repository or package signing key received: Key ID: 27C070176F88BB2F Key Name: KDE OBS Project <KDE@build.opensuse.org> Key Fingerprint: 4E8E6DE2961F3083EAC5008627C070176F88BB2F Key Created: Sun 31 Aug 2014 05:06:11 PM IDT Key Expires: Tue 08 Nov 2016 04:06:11 PM IST Repository: openSUSE BuildService - KDE:Extra Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a <-- Retrieving repository 'openSUSE BuildService - KDE:Extra' metadata ...................................................................................................[done] Building repository 'openSUSE BuildService - KDE:Extra' cache ........................................................................................................[done] Repository 'openSUSE BuildService - LibreOffice' is up to date. Retrieving repository 'openSUSE BuildService - filesystems' metadata .................................................................................................[done] Building repository 'openSUSE BuildService - filesystems' cache ......................................................................................................[done] Retrieving repository 'openSUSE BuildService - Games' metadata .......................................................................................................[done] Building repository 'openSUSE BuildService - Games' cache ............................................................................................................[done] Repository 'openSUSE BuildService - LXDE' is up to date. Repository 'openSUSE BuildService - Mozilla' is up to date. Repository 'openSUSE BuildService - Java:packages' is up to date. Retrieving repository 'openSUSE BuildService - devel:languages:perl' metadata ........................................................................................[done] Building repository 'openSUSE BuildService - devel:languages:perl' cache .............................................................................................[done] Retrieving repository 'openSUSE BuildService - devel:languages:python' metadata ......................................................................................[done] Building repository 'openSUSE BuildService - devel:languages:python' cache ...........................................................................................[done] Retrieving repository 'Packman Repository' metadata ---------------------------------------------------------------------------------------------------------------------[-] New repository or package signing key received: Key ID: 45A1D0671ABD1AFB Key Name: PackMan Project (signing key) <packman@links2linux.de> Key Fingerprint: F8875B880D518B6B8C530D1345A1D0671ABD1AFB Key Created: Tue 16 Sep 2014 01:18:00 AM IDT Key Expires: Fri 13 Sep 2024 01:17:21 AM IDT Repository: Packman Repository Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a <-- Retrieving repository 'Packman Repository' metadata ..................................................................................................................[done] Building repository 'Packman Repository' cache .......................................................................................................................[done] Repository 'games:tools' is up to date. Repository 'google-chrome' is up to date. Repository 'Multimedia - Apps' is up to date. Repository 'libdvdcss repository' is up to date. Repository 'ownCloud' is up to date. Repository 'openSUSE-13.1-Non-Oss' is up to date. Repository 'openSUSE-13.1-Oss' is up to date. Retrieving repository 'openSUSE-13.1-Update' metadata -------------------------------------------------------------------------------------------------------------------[-] New repository or package signing key received: Key ID: B88B2FD43DBDC284 Key Name: openSUSE Project Signing Key <opensuse@opensuse.org> Key Fingerprint: 22C07BA534178CD02EFE22AAB88B2FD43DBDC284 Key Created: Mon 05 May 2014 11:37:40 AM IDT Key Expires: Thu 02 May 2024 11:37:40 AM IDT Repository: openSUSE-13.1-Update Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a <-- Retrieving repository 'openSUSE-13.1-Update' metadata ................................................................................................................[done] Building repository 'openSUSE-13.1-Update' cache .....................................................................................................................[done] Repository 'openSUSE-13.1-Update-Non-Oss' is up to date. All repositories have been refreshed. Why is it that zypper forgets that I trusted the repo keys? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Yevgeny wrote:
Hi, I know that there is a similar thread that has this issue.
I don't know why, but this happens every day if I request a repo refresh from zypper:
zypper shell zypper> refresh Retrieving repository 'Editors' metadata .............................................................................................................................[done] Building repository 'Editors' cache ..................................................................................................................................[done] Repository 'Emu' is up to date. Repository 'Graphics' is up to date. Repository 'Node.js' is up to date. Repository 'Python3' is up to date. Repository 'nVidia Graphics Drivers' is up to date. Repository 'openSUSE BuildService - Mono:Community' is up to date. Repository 'openSUSE BuildService - Education' is up to date. Retrieving repository 'openSUSE BuildService - KDE:Extra' metadata ------------------------------------------------------------------------------------------------------[/]
New repository or package signing key received: Key ID: 27C070176F88BB2F Key Name: KDE OBS Project <KDE@build.opensuse.org> Key Fingerprint: 4E8E6DE2961F3083EAC5008627C070176F88BB2F Key Created: Sun 31 Aug 2014 05:06:11 PM IDT Key Expires: Tue 08 Nov 2016 04:06:11 PM IST Repository: openSUSE BuildService - KDE:Extra
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a <-- Retrieving repository 'openSUSE BuildService - KDE:Extra' metadata ...................................................................................................[done] Building repository 'openSUSE BuildService - KDE:Extra' cache ........................................................................................................[done] Repository 'openSUSE BuildService - LibreOffice' is up to date. Retrieving repository 'openSUSE BuildService - filesystems' metadata .................................................................................................[done] Building repository 'openSUSE BuildService - filesystems' cache ......................................................................................................[done] Retrieving repository 'openSUSE BuildService - Games' metadata .......................................................................................................[done] Building repository 'openSUSE BuildService - Games' cache ............................................................................................................[done] Repository 'openSUSE BuildService - LXDE' is up to date. Repository 'openSUSE BuildService - Mozilla' is up to date. Repository 'openSUSE BuildService - Java:packages' is up to date. Retrieving repository 'openSUSE BuildService - devel:languages:perl' metadata ........................................................................................[done] Building repository 'openSUSE BuildService - devel:languages:perl' cache .............................................................................................[done] Retrieving repository 'openSUSE BuildService - devel:languages:python' metadata ......................................................................................[done] Building repository 'openSUSE BuildService - devel:languages:python' cache ...........................................................................................[done] Retrieving repository 'Packman Repository' metadata ---------------------------------------------------------------------------------------------------------------------[-]
New repository or package signing key received: Key ID: 45A1D0671ABD1AFB Key Name: PackMan Project (signing key) <packman@links2linux.de> Key Fingerprint: F8875B880D518B6B8C530D1345A1D0671ABD1AFB Key Created: Tue 16 Sep 2014 01:18:00 AM IDT Key Expires: Fri 13 Sep 2024 01:17:21 AM IDT Repository: Packman Repository
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a <-- Retrieving repository 'Packman Repository' metadata ..................................................................................................................[done] Building repository 'Packman Repository' cache .......................................................................................................................[done] Repository 'games:tools' is up to date. Repository 'google-chrome' is up to date. Repository 'Multimedia - Apps' is up to date. Repository 'libdvdcss repository' is up to date. Repository 'ownCloud' is up to date. Repository 'openSUSE-13.1-Non-Oss' is up to date. Repository 'openSUSE-13.1-Oss' is up to date. Retrieving repository 'openSUSE-13.1-Update' metadata -------------------------------------------------------------------------------------------------------------------[-]
New repository or package signing key received: Key ID: B88B2FD43DBDC284 Key Name: openSUSE Project Signing Key <opensuse@opensuse.org> Key Fingerprint: 22C07BA534178CD02EFE22AAB88B2FD43DBDC284 Key Created: Mon 05 May 2014 11:37:40 AM IDT Key Expires: Thu 02 May 2024 11:37:40 AM IDT Repository: openSUSE-13.1-Update
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a <-- Retrieving repository 'openSUSE-13.1-Update' metadata ................................................................................................................[done] Building repository 'openSUSE-13.1-Update' cache .....................................................................................................................[done] Repository 'openSUSE-13.1-Update-Non-Oss' is up to date. All repositories have been refreshed.
Why is it that zypper forgets that I trusted the repo keys?
Why don't you try doing the same thing from YaST2 and see what happens.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Dirk Gently -
Yevgeny