A new error message from sudo zypper dup - what to do!

Just had an error message today when running update. Here is what I have:–

alastair@IBMW530:~> sudo zypper dup 
[sudo] password for root:  
Retrieving repository 'Main Update Repository' metadata ----------------------------------\] 
Warning: Digest verification failed for file 'f4fba37aa004f93b3b9f72917e4621a69964f902184252d
9cfce7f49399cb2fe-primary.xml.gz' 
[/var/tmp/AP_0xpRfikR/repodata/f4fba37aa004f93b3b9f72917e4621a69964f902184252d9cfce7f49399cb2
fe-primary.xml.gz] 

  expected f4fba37aa004f93b3b9f72917e4621a69964f902184252d9cfce7f49399cb2fe 
  but got  01c466b6218bb4b8f10b81b3dfcd3496233525bda6db49a4af52051311689a29 

Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases e
ven to a system compromise.

However if you made certain that the file with checksum '01c4..' 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? [01c4/...? shows all options] (discard): **

I assume the checksum has been scrambled but am not sure if the fault is on my system or at the repo site.
Please could I have some advice on what to do.
Budge

Hi
Could have hit an out of sync mirror, wait a bit and try again, or run zypper -vvv ref -f to force a refresh and see what happens

Hi Malcolm,
Tried your suggested forced refresh but still getting problem. Will leave it till tomorrow.
Thanks,
Alastair

This shouldn’t be a problem/question for an experienced user at all. Did you try another mirror?

Experienced? Clearly not enough. I had trouble finding what i was looking for which was TW update. Here is what I have at present.

Repository 'Main Update Repository' is invalid.

So I am looking for TW Main Update Repo but cannot see that offered yet. Quite a few sites are grey and not up to date and I cannot find an update site for TW, only oss and non-oss.
For example at uni-erlangen.de I am offered /opensuse/Tumbleweed/… which does not offer an update repo or /opensuse/Update/… which does not offer a TW repo.
Sorry to be thick but uncertain which to select. Guidance would be appreciated.

Some mirrors are not following the “upstream” way of providing an explicit update directory. They only provide the main oss/non-oss/source/debug directorys but incorperate all the actual Tumbleweed snapshots into it. So they are also up to date and this is no problem if you do a “zypper dup”.

You miss to tell the URI. All of these are up to date:

**erlangen:~ #** repos 
#  | Alias         | Enabled | GPG Check | Refresh | Priority | URI 
---+---------------+---------+-----------+---------+----------+------------------------------------------------------- 
 7 | Packman       | Yes     | (r ) Yes  | Yes     |   90     | https://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/ 
21 | non-oss       | Yes     | (r ) Yes  | Yes     |   99     | https://download.opensuse.org/tumbleweed/repo/non-oss/ 
23 | oss           | Yes     | (r ) Yes  | Yes     |   99     | https://download.opensuse.org/tumbleweed/repo/oss/ 
30 | update        | Yes     | (r ) Yes  | Yes     |   99     | https://download.opensuse.org/update/tumbleweed/ 
11 | google-chrome | Yes     | (r ) Yes  | Yes     |  100     | https://dl.google.com/linux/chrome/rpm/stable/x86_64 
**erlangen:~ #**

So I am looking for TW Main Update Repo but cannot see that offered yet. Quite a few sites are grey and not up to date and I cannot find an update site for TW, only oss and non-oss.
For example at uni-erlangen.de I am offered /opensuse/Tumbleweed/… which does not offer an update repo or /opensuse/Update/… which does not offer a TW repo.
Sorry to be thick but uncertain which to select. Guidance would be appreciated.

Update is currently empty. I haven’t seen packages here since a long time:

**erlangen:~ #** zypper packages --repo update  
Loading repository data... 
Reading installed packages... 
S | Repository                      | Name                                | Version | Arch 
--+---------------------------------+-------------------------------------+---------+------- 
  | Hauptaktualisierungs-Repository | update-test-32bit-pkg               | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-32bit-pkg               | 3-2.1   | x86_64 
  | Hauptaktualisierungs-Repository | update-test-32bit-pkg               | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-32bit-pkg               | 3-2.1   | i586 
  | Hauptaktualisierungs-Repository | update-test-32bit-pkg-32bit         | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-affects-package-manager | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-affects-package-manager | 3-2.1   | x86_64 
  | Hauptaktualisierungs-Repository | update-test-affects-package-manager | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-affects-package-manager | 3-2.1   | i586 
  | Hauptaktualisierungs-Repository | update-test-broken                  | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-broken                  | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-feature                 | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-feature                 | 3-2.1   | x86_64 
  | Hauptaktualisierungs-Repository | update-test-feature                 | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-feature                 | 3-2.1   | i586 
  | Hauptaktualisierungs-Repository | update-test-interactive             | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-interactive             | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-optional                | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-optional                | 3-2.1   | x86_64 
  | Hauptaktualisierungs-Repository | update-test-optional                | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-optional                | 3-2.1   | i586 
  | Hauptaktualisierungs-Repository | update-test-reboot-needed           | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-reboot-needed           | 3-2.1   | x86_64 
  | Hauptaktualisierungs-Repository | update-test-reboot-needed           | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-reboot-needed           | 3-2.1   | i586 
  | Hauptaktualisierungs-Repository | update-test-relogin-suggested       | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-relogin-suggested       | 3-2.1   | x86_64 
  | Hauptaktualisierungs-Repository | update-test-relogin-suggested       | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-relogin-suggested       | 3-2.1   | i586 
  | Hauptaktualisierungs-Repository | update-test-retracted               | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-retracted               | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-security                | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-security                | 3-2.1   | x86_64 
  | Hauptaktualisierungs-Repository | update-test-security                | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-security                | 3-2.1   | i586 
  | Hauptaktualisierungs-Repository | update-test-trivial                 | 5.1-2.1 | x86_64 
  | Hauptaktualisierungs-Repository | update-test-trivial                 | 5-4.1   | x86_64 
  | Hauptaktualisierungs-Repository | update-test-trivial                 | 5.1-2.1 | i586 
  | Hauptaktualisierungs-Repository | update-test-trivial                 | 5-4.1   | i586 
**erlangen:~ #**

Detailed status of opensuse: Mirror-Status ftp.fau.de (ftp.uni-erlangen.de)

Taking hui’s information and now that of karlmistelberger I have just deleted the update repo from my list. Clearly now redundant.
No further problems with zypper dup.
Will call for help if anything changes but so far so good!
Many thanks,
Budge.

Hi
The update repository was used the other week when there was the qcom firmware issue, no doubt it will be required again.

Anything present in Tumbleweed update repository will appear in regular oss/non-oss, just a bit later. So it is “required” only if you insist on following each and every Tumbleweed snapshot and refuse to benefit from rollback possibility offered by SUSE. Otherwise you can just wait a couple of days until new version is published in standard repository.

But anyone who wants to follow each Tumbleweed snapshot should be prepared to deal with all sorts of breakage. Bad mirror is just a minor nuisance.

OK I get the picture and am happy to use rollback more now I understand. I tried adding update to my system again but this failed again. I am happy to wait but wonder if I should just overwrite the checksum. Just a thought.

After having first removed TW Update repository I was able to add it back OK here…

paul@Orion-22:~> sudo zypper ar http://download.opensuse.org/update/tumbleweed/ TW-Update
[sudo] password for root: 
Adding repository 'TW-Update' ....................................................................................................................[done]
Repository 'TW-Update' successfully added

URI         : http://download.opensuse.org/update/tumbleweed/
Enabled     : Yes
GPG Check   : Yes
Autorefresh : No
Priority    : 99 (default priority)

Repository priorities are without effect. All enabled repositories share the same priority.
paul@Orion-22:~>

The mirror software should take care of finding a suitable mirror server, looks like my closest/best is “ftp.gwdg.de

paul@Orion-22:~/Global/Downloads> wget http://download.opensuse.org/update/tumbleweed/x86_64/update-test-trivial-5.1-2.1.x86_64.rpm
--2022-10-17 11:21:11--  http://download.opensuse.org/update/tumbleweed/x86_64/update-test-trivial-5.1-2.1.x86_64.rpm
Resolving download.opensuse.org (download.opensuse.org)... 195.135.221.134, 2001:67c:2178:8::13
Connecting to download.opensuse.org (download.opensuse.org)|195.135.221.134|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://ftp.gwdg.de/pub/opensuse/update/tumbleweed/x86_64/update-test-trivial-5.1-2.1.x86_64.rpm [following]
--2022-10-17 11:21:12--  http://ftp.gwdg.de/pub/opensuse/update/tumbleweed/x86_64/update-test-trivial-5.1-2.1.x86_64.rpm
Resolving ftp.gwdg.de (ftp.gwdg.de)... 134.76.12.6, 2001:638:60f:110::1:2
Connecting to ftp.gwdg.de (ftp.gwdg.de)|134.76.12.6|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9020 (8.8K) [application/x-redhat-package-manager]
Saving to: ‘update-test-trivial-5.1-2.1.x86_64.rpm’

update-test-trivial-5.1-2.1.x86_64.rpm 100%===========================================================================>]   8.81K  --.-KB/s    in 0.001s  

2022-10-17 11:21:12 (6.55 MB/s) - ‘update-test-trivial-5.1-2.1.x86_64.rpm’ saved [9020/9020]

paul@Orion-22:~>

or maybe I’ve misunderstood what your problem is :\ …