Additional mirrors Packman


I have had a problem with the Yast desktop app for updating. I often get the message that says some of the repos isn’t reachable. I have tried to change to another mirror for Packman and the problem goes away for some time, then it reemerges. Is it possible to set up different Packman sources so the app looks to another mirror when one isn’t available?

Dag R

Maybe we should have a look at your repo sources.

zypper lr -u

will show us from the terminal if the Packman repo is the correct one.

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

# | Alias               | Navn                        | aktivert | GPG-kontroll | Oppdater | URI                                                     
1 | openSUSE-20160826-0 | openSUSE-20160826-0         | Ja       | (r ) Ja      | Ja       |       
2 | packman             | packman                     | Ja       | (r ) Ja      | Ja       |       
3 | repo-debug          | openSUSE-Tumbleweed-Debug   | Nei      | ----         | ----     | 
4 | repo-non-oss        | openSUSE-Tumbleweed-Non-Oss | Ja       | (r ) Ja      | Ja       |   
5 | repo-source         | openSUSE-Tumbleweed-Source  | Nei      | ----         | ----     |
6 | repo-update         | openSUSE-Tumbleweed-Update  | Ja       | (r ) Ja      | Ja       |     

I normally use

(you go for the Tumbleweed path of course).
It is normally very stable. But remind that a few months ago, when the Austrian one had some intermittent problems (any many thus switched to GWDG) within a week, GWDG was down for one for a weekend. So you never know, but in general they are very stable for a costless service. :wink:

You could add GWDG to your list, but I would always only have one of them Enabled at a time. When the fallback one is already in the list, it is easy to switch without you having to search for the exact URL.

And yes, everything looks OK. I use the same source but for Leap. Though I had no downtime at least not that I noticed.