BTW, repositories #7 - #10 are duplicates of those above. 
Mind your tone. Consider this a warning.
You have only 2 serious options:
sudo zypper --releasever=15.6 dup --allow-vendor-changeto update to 15.6 . With your repo set ( and yes, we always want to see all of them ) is pretty stock, I’d give that a try- full reinstall.
Make a backup of /home before either one of them
Are you sure the $releasever is already present in those URLs? His system is way back in the past!
And of course he should first clean the list. Those double ones should be removed before he goes on.
@joepaule
The repository list in your post #18 does not show any occurrence of the $releasever variable. That might be OK but nevertheless check your repository definitions. Without that variable the command shown above might not work (see man zypper for more information).
If your current system is openSUSE Leap 15.3 then going to openSUSE Leap 15.6 directly (without installing 15.4 , then 15.5 and last but not least 15.6) is not recommended.
However all this is just my personal view others might know better …
I concur with all you say. However this is to be expected. When there is $releasever in a repo URL, it will show as 15.3 in a Leap 15.3 installation. No difference with hard-coded 15.3
One can test if it is there by e.g.
zypper --releasever FOOBAR lr -d
If you look it up, you’ll see it does. Not in the repo urls but that’s not needed. I’ve actually done this recently on 3 laptops (only basic repos) and it worked fine.
Sorry, but I am a bit at loss here.
What is “it” and what “does” it?
- Using the
--releaseverfeature when not coded into the URLs? - Upgrading (or doing other
zyppercommands with some repos configured twice?
I think releasever was introduced at 15.3 but may not be active if that version was upgraded from 15.2 or earlier.
You should be able to tell from Yast -software repositories all URLS must have “releasever” in the string
That might be correct. In any case, IMHO it is not a bad idea to advice the OP (which such an old system of which we do not know it’s history) to check if they are there if advising to use it.
That is one way to do it. And easy one is the one posted by me above. A third one
grep baseurl /etc/zypp/repos.d/*.repo
And one does not even have to “be root” to do that.
Using openSUSE Tumbleweed only I do not have any $releaserver in my repository URLs and do not know for sure how zypper lr handles this variable when displaying the repository list. So I added “… That might be OK …” to express my uncertainty.
I just want OP to make sure he has that variable in his URLs.
The duplicate repos were already addressesed.
releasever was already introduced in 15.1 . Having it in the repo URLs only happens since 15.5, when upgraded.
And, sorry to ask, did you actually miss this? And instead of looking it up you ask me to explain? I don’t post an opinion, but factual info.
Depends on what you upgraded from in the past. if previous versions did not have it it won’t there. I remember having to add it to my URL’s
May I ask you a question (or will that result in a further warning or even worse)?
Do you consider your recommendation to upgrade directly from Leap 15.3 to 15.6 a “factual info”?
Not used in Tumbleweed.
But the idea is very simple. When using zypper:
When the string $releasever is found in the baseurl= parameter of a repo definition, it is replaced by another string. That string is found in the system (forgotten where) as is the present version string (e.g. 15.5), or, when the global option --releasever <something> is used, it is replaced by the value of that global option.
It is only a string replacement. Just like used in bash . Only less sophisticated (because not needed). And that is why a list with --releasever FOOBAR will show all the URLs in the listing with FOOBAR somewhere if, and only if, $releasever is in the baseurl= definition.
There is no magic in computing.
Thank you for your detailed explanation.
Basically I had the same understanding. However I could not really verify how zypper lr would show the URL so I was just cautious …
Miss what?
I use the realesever feature since it was offered. I only can not remember exactly when it was introduced and I warn the OP to check it. What is wrong with that?
If you have read my posts, you’ve read I actually have done that. Proof is at my customer.
This was your post. An answer to my post. I never warned for the jump over 15.4 and 15.5, thus I can fully understand that others do not read in it that you did that out of this post.
I understand. In Tumbleweed you can not test this to see for yourself.