That message is only because your zypper thinks that for a long time no updates were done to the Main OSS repo. And that is logical, because in Leap all updates come from the several Update repos and the Main repo is not changed.
Most people will not see that because when you do an update regular on a not too long time schedule (let us say weekly), zypper sees that it was used and OK one week ago. But you have apparently not done an upgrade for a considerable long time, thus zypper warns you.
Then my description is not 100% true, sorry for that. But the main idea is still that the Main repos (OSS and non-OSS) do not change after release. zypper is afraid that you have a stale mirror or so.
I remember the same message reported to people using Tumbleweed, but then about the Update repo. Only because TWQ does not use the Update repo (well, very seldom).
I also do regular updates, and have also only recently started seeing this message.
If it is due to a repository not changing, and Zypper therefore thinking it’s outdated, then why does the warning not show for other unchanging repositories (e.g. Main Repository)?
Also, if I force a rebuild of all of the caches using
sudo zypper ref -f
then shouldn’t Zypper no longer know that the repo is outdated? And yet when I ran this command, I still received the warning when I did sudo zypper up.
Could it be a problem with the repo itself, perhaps a preparations are made for 15.4?
But if mirror redirection is dynamic, is there no safeguard to prevent being redirected to an outdated mirror? Is the redirection random every time?
And assuming there’s no critical update that I’m after (in which case I could specify the mirror I want to use on a temporary/permanent basis), is it best to simply ignore the warning given that it should disappear when zypper eventually gets redirected to a different mirror?
Hi Paul & Henk,
In my case it is the Update repo that gives me the suggested use of a different mirror. Strange that an update repo is not updated itself, particularly if the redirection is automatic, as you suggest.
Whatever, all I want to know is should I ignore the warning and if I wish to use a different mirror how do I do that please?
Budge
Personally, on the very rare occasion I’ve seen the "Outdate Repository warning I’ve simply left the update for a few hours and then tried again. I would only consider specifying a specific mirror if I was consistently seeing the warning.
Do consider though:
Quote from: https://mirrors.opensuse.org/*
Under normal circumstances, there should be no need to use mirrors directly, and look at this table for that purpose. If you do see the need, there might be something wrong and it would be appreciated if you notify the admins about it, so it can be fixed for the benefit of yourself, and possibly many other users.*
As an afterthought I should add that the URL of your chosen mirror may not necessarily be in the form shown for mirrors.coreix.net - You may need to visit the mirror in a web browser first to establish the exact path to use in the URL prior to “distribution/leap/15.3/repo/oss/”