Discussion is rather wishy-washy regarding removing or updating 3rd party repos. Discussion refers ro “removing” some 3rd party repos.
Question 1 – Does the term removal as used in the wiki mean to “disable (unenable)” the repo or to completely “delete” the repo from the repo list? In other words, will zypper upgrade an unenabled repo?
Question 2 - Should nvidia proprietary driver repos be left enabled and retained (with releasever variable added to url) during the update? Can’t be left with unusable graphics. Wiki does not specifically address nvidia repo suggested actions. Past problems with nvida make me very nervous about this. Don’t want a rcomplete reinstall to be necessary. That’s a week of work getting all the installed stuff back running.
Question 3 - In the wiki, it is recommended to [size=1]“disable all OBS repositories first, perform the upgrade, then reenable them.”. What are OBS repositories? Are openSUSE “science”, “graphics”, “education”, electronics", and other repos that I have activated considered as OBS directories? And again, as per above, does disable mean unenable or delete?
thanks for insights from more knowledgeable people. Perhpas answers will help others avoid issues. tom kosvic
[/size]
Are openSUSE “science”, “graphics”, “education”, electronics", and other repos that I have activated considered as OBS directories?
[/size]
a) openSUSE does not have “science” etc
b) it is impossible to answer your question because anyone can name anything “science”. OBS repository usually refers to packages that are developed on build.opensuse.org and made available in download.opensuse.org/repositories. So if repository URL starts with this string, it is most likely OBS repository.
When you post your list as it is now, people might be able to advice on each one of the repos you have now.
My personal path is to disable all non-standard repos, including Packman during the zypper dup. I only switch again to Packman (of course the new one, but when you have $releasever in it’s URL that goes automatic after the first and great zypper dup is completed) after the whole (including an extra zypper up) is finished. I haven’t other ones, but I think my basic approach is clear.
That’s funny because the upgrade wikiutilizing zypper suggests that leaving packman enabled would work better with zypper dup. Wiki says:
“Removing a repository causes the problem that every package that was installed from it will revert to another repository (if found), or deleted, or left at the old version, depending on the administrator choices. It may be a better method to leave the repository active.”
Like Malcolm said, check if all repo definitions have $releasever. There is another way to do this:
zypper --releasever FOOBAR lr -d
. When an URL in that repo list still has 15.3 instead of FOOBAR, it does not have $releasever.
I only told what I did in earlier upgrades (and what I will do again). I assume that quote is about other repos in general, my remark is based on Packman. I do not care if during the zypper dup packages are reverted to OSS. A new switch to Packman at the end will cure that. IMHO it has the advantage that when something is no more offered from Packman, but now from OSS (e.g. because it is no longer restricted by patents), that package will now be from OSS and notr missing.
Actually this is a tiny problem. On my machine 56 packages come from packman out of 3663 packages total. Keeping additional repos active during upgrade can cause big issues.
BTW: “Only a fool learns from his own mistakes. The wise man learns from the mistakes of others.” ― Otto von Bismarck
I already ran the sed command. Your command shows “releasever” inplace of “15.3” in all the names and urls that are displayed in repo configuration… Quite lengthy so I did not post.
How do you display the current “releasever” variable value? Is it in zypper somewhere?
Well, as it is used as default in all zypper commands when you do not specify it different with the global option --releasever, the repo list you posted above, with no --relesaever specified, either shows 15.3 where hard-coded, or it shows what is the default in those place where you have $releasever coded.