Signature Verification Failure for repo NON OSS

English Applications
1

I got yhr following error"

**Signature verification failed for file 'content' from repository 'Main Repository (NON-OSS)'.**
**Warning: This might be caused by a malicious change in the file!**

Who would I contact to take care of this?

Output of zypper lr -u

# | Alias                            | Name                       | Enabled | GPG Check | Refresh | URI                                                       
          
--+----------------------------------+----------------------------+---------+-----------+---------+-----------------------------------------------------------
---------
1 | download.opensuse.org-non-oss    | Main Repository (NON-OSS)  | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/tumbleweed/repo/non-oss/     
          
2 | download.opensuse.org-oss        | Main Repository (OSS)      | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/tumbleweed/repo/oss/         
          
3 | download.opensuse.org-tumbleweed | Main Update Repository     | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/tumbleweed/           
          
4 | openSUSE-20160417-0              | openSUSE-20160417-0        | No      | ----      | No      | http://download.opensuse.org/tumbleweed/repo/oss/         
          
5 | packman                          | packman                    | Yes     | (r ) Yes  | Yes     | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tu
mbleweed/
6 | repo-debug                       | openSUSE-Tumbleweed-Debug  | No      | ----      | No      | http://download.opensuse.org/debug/tumbleweed/repo/oss/   
          
7 | repo-source                      | openSUSE-Tumbleweed-Source | No      | ----      | No      | http://download.opensuse.org/source/tumbleweed/repo/oss/
2

That seems like a problem that I ran into, maybe a year ago.

I aborted that update, waited a few hours, then tried again. And all was fine.

You possibly were using a mirror that was not completely updated.

3

In YaST: Software: Software Repositories: select the main NON-OSS repository and then (bottom-right) “refresh selected repository”.
If it still errors, wait (until the maintainers have addressed the issue).
If you’re lucky, you’ll be prompted to accept a new key for the repository.

4

I still get the error, but I can wait. :slight_smile: