> sudo zypper dup
[sudo] password for root:
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Looking for gpg keys in repository GNOME:Apps.
gpgkey=https://download.opensuse.org/repositories/GNOME:/Apps/openSUSE_Factory+GNOME_Factory/repodata/repomd.xml.key
Retrieving repository 'GNOME:Apps' metadata ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[|]
Warning: Digest verification failed for file 'ea9e9390c09fb52ea6e0a263e518944852b9cfaf829c797375d90f7ad915aafe-primary.xml.gz'
[/var/tmp/AP_0xvu8iln/repodata/ea9e9390c09fb52ea6e0a263e518944852b9cfaf829c797375d90f7ad915aafe-primary.xml.gz]
expected ea9e9390c09fb52ea6e0a263e518944852b9cfaf829c797375d90f7ad915aafe
but got 5a40910e270f3e6b5047f8ae3d9960bb93c60364b26f25e7cd889d7a3200d52a
Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.
However if you made certain that the file with checksum '5a40..' is secure, correct
and should be used within this operation, enter the first 4 characters of the checksum
to unblock using this file on your own risk. Empty input will discard the file.
Unblock or discard? [5a40/...? shows all options] (discard):
Retrieving repository 'GNOME:Apps' metadata ..........................................................................................................................................................................[error]
Repository 'GNOME:Apps' is invalid.
[GNOME_Apps|https://download.opensuse.org/repositories/GNOME:/Apps/openSUSE_Factory+GNOME_Factory/] Failed to retrieve new repository metadata.
History:
- ea9e9390c09fb52ea6e0a263e518944852b9cfaf829c797375d90f7ad915aafe-primary.xml.gz has wrong checksum
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'GNOME:Apps' because of the above error.
Some of the repositories have not been refreshed because of an error.
dist-upgrade: Due to the treatment of orphaned packages dist-upgrade depends on a proper
repository setup more than any other command. It must not continue if enabled repositories fail
to refresh. This may severely damage the system. If a failing repository is actually not needed,
it must be disabled. See 'man zypper' for more information about this command.
[13:20:25] myuser@ostw-kde /home/myuser [4]
>
Users of Factory repos should know at least some repository and zypper basics. The use of developement/home/factory repos can cause serious package conflicts up to not properly working apps. So at least some basic troubleshooting knowledge is required when using them.
This repo is marked as beta testing for the next release (see SDB). Use it on your own risk.
Clean your cache and try again. If it still occurs, wait some time until the mirrors are synced
I do not know that repo (and we have only the name, thus not the URL (thus you could post it e.g. with zypper lr -d), but it says that when you trust that repo, you can type those four characters as answer to the question and then it will proceed.