Signature verification failed on tumbleweed

English Install/Boot/Login
1

When running zypper dup on Tumbleweed I get

sudo zypper dup                                                                                          
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Signature verification failed for file 'repomd.xml' from repository 'repo-non-oss'.

    Note: Signing data enables the recipient to verify that no modifications occurred after the data
    were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
    and in extreme cases even to a system compromise.

    Note: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the
    whole repo.

    Warning: This file was modified after it has been signed. This may have been a malicious change,
    so it might not be trustworthy anymore! You should not continue unless you know it's safe.

    Note: This might be a transient issue if the server is in the midst of receiving new data. The
    data file and its signature are two files which must fit together. In case the request hit the
    server in the midst of updating them, the signature verification might fail. After a few
    minutes, when the server has updated its data, it should work again.

Signature verification failed for file 'repomd.xml' from repository 'repo-non-oss'. Continue? [yes/no] (no):

My Repositories:

Repository priorities in effect:                                              (See 'zypper lr -P' for details)
      90 (raised priority)  :  1 repository
      99 (default priority) :  6 repositories

# | Alias                      | Name              | Enabled | GPG Check | Refresh
--+----------------------------+-------------------+---------+-----------+--------
1 | NVIDIA:repo-non-free       | repo-non-free     | Yes     | (r ) Yes  | Yes
2 | openSUSE:repo-non-oss      | repo-non-oss      | Yes     | (r ) Yes  | Yes
3 | openSUSE:repo-openh264     | repo-openh264     | Yes     | (r ) Yes  | Yes
4 | openSUSE:repo-oss          | repo-oss          | Yes     | (r ) Yes  | Yes
5 | openSUSE:repo-oss-debug    | repo-oss-debug    | No      | ----      | ----
6 | openSUSE:repo-oss-source   | repo-oss-source   | No      | ----      | ----
7 | openSUSE:update-tumbleweed | update-tumbleweed | Yes     | (r ) Yes  | Yes
8 | packman                    | Packman           | Yes     | (r ) Yes  | Yes
9 | vscode~                    | vscode~           | Yes     | (r ) Yes  | Yes
2

You should read the output and do what is suggested there:

Note: This might be a transient issue if the server is in the midst of receiving new data. The
data file and its signature are two files which must fit together. In case the request hit the
server in the midst of updating them, the signature verification might fail. After a few
minutes, when the server has updated its data, it should work again.

As a new Tumblweeed snapshot was published, some mirrors are still in the mid of syncing…simply wait some time and retry later.

3

I gave it about 1/2 hour between attempts so I guess it takes longer to update the mirror?

4

Yes. Because a mirror contains several GB of data also for other distributions and projects. This error is common. Yust search the forum and you will find that nearly everytime a new snapshots gets released, somebody ask the same question.

5

In that case I’ll try again tomorrow. It’s the first time I’ve seen that message in about seven years of running Tumbleweed, I must have been lucky.

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.