Bug ID | 1063164 |
---|---|
Summary | Zypper --gpg-auto-import-keys does not work |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 42.3 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Installation |
Assignee | yast2-maintainers@suse.de |
Reporter | marco.varlese@suse.com |
QA Contact | jsrain@suse.com |
Found By | --- |
Blocker | --- |
First of all, I am not sure if this is a bug or I'm doing something wrong (or not doing enough). I'm adding a new repo via the command: sudo zypper --non-interactive --gpg-auto-import-keys ar --refresh -n CloudRepo http://download.opensuse.org/repositories/Cloud:/Tools/openSUSE_Leap_42.3/Cloud:Tools.repo All looks good, however when I later on invoke the command: sudo zypper refresh I get the following issue Retrieving repository 'CloudRepo' metadata ---------------------------------------------------------------------------------------------------------------------------------------------------------------------[\] New repository or package signing key received: Repository: CloudRepo Key Name: Cloud OBS Project <Cloud@build.opensuse.org> Key Fingerprint: ACE2204F 418CFEB8 BF02ABF5 9338BC79 29DD7D91 Key Created: Wed 20 Sep 2017 05:28:52 PM CEST Key Expires: Fri 29 Nov 2019 04:28:52 PM CET Rpm Name: gpg-pubkey-29dd7d91-59c28934 Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r) I would have expected the --gpg-auto-import-keys to import the key and trust them?