Hi.
I’m going to do a live update from 42.2 to 42.3.
I have some repos disabled. I will change them to the 42.3.
Some of them I am not sure if I want to use them anymore or not (that’s why I have them disabled)
Can I let them disabled while doing zypper dup or I have to delete them before zypper dup?
regards
You show no information at all. What are others supposed to understand when you say “some repos” and “some of them”?
Please show
zypper lr -d
and explain what you think of those.
Maybe I did not express correctly myself.
The question is if I run a zypper dup with some repos disabled, zypper ignore these repos when upgrading or it uses them?
I think I have read somewhere that zypper dup use the most recent version in any repository you have without taking in account repository priority or if the respository is enabled or not. That is my concern.
About my list of repos, here it is.
andromeda:/home/fernando # zypper lr -d
Repository priorities in effect: (See 'zypper lr -P' for details)
90 (raised priority) : 4 repositories
94 (raised priority) : 1 repository
97 (raised priority) : 2 repositories
98 (raised priority) : 2 repositories
99 (default priority) : 6 repositories
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+-------------------------------------+-----------------------------------+---------+-----------+---------+----------+--------+------------------------------------------------------------------------------------------------+--------
1 | AVR | AVR | No | ---- | ---- | 105 | rpm-md | http://download.opensuse.org/repositories/CrossToolchain:/avr/openSUSE_Leap_42.2/ |
2 | Application:Geo | Application:Geo | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/Application:/Geo/openSUSE_Leap_42.2/ |
3 | Documentation:Tools | Documentation:Tools | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/Documentation:/Tools/openSUSE_Leap_42.2/ |
4 | Ham_Radio | Ham Radio | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/hamradio/openSUSE_Leap_42.2/ |
5 | KDE:Extra | KDE:Extra | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.2/ |
6 | KDE:KDE3 | KDE:KDE3 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Leap_42.2/ |
7 | M17N_fonts | M17N fonts | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Leap_42.2/ |
8 | Packman Repository | Packman Repository | Yes | (r ) Yes | Yes | 98 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_42.2/ |
9 | Publishing | Publishing | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/Publishing/openSUSE_Leap_42.2/ |
10 | Virtualization | Virtualization | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/Virtualization/openSUSE_Leap_42.2/ |
11 | X11:RemoteDesktop:x2go | X11:RemoteDesktop:x2go | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/X11:/RemoteDesktop:/x2go/openSUSE_Leap_42.2/ |
12 | devel:languages:ocaml | devel:languages:ocaml | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/ocaml/openSUSE_Leap_42.2/ |
13 | devel:languages:perl | devel:languages:perl | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_Leap_42.2/ |
14 | devel:languages:python | devel:languages:python | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE_Leap_42.2/ |
15 | filesystems | filesystems | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/filesystems/openSUSE_Leap_42.2/ |
16 | hardware | hardware | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/hardware/openSUSE_Leap_42.2/ |
17 | home:Kenzu:3d-print | home:Kenzu:3d-print | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/home:/Kenzu:/3d-print/openSUSE_Leap_42.2/ |
18 | home:dl8fcl:branches:hamradio | home:dl8fcl:branches:hamradio | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/home:/dl8fcl:/branches:/hamradio/openSUSE_Leap_42.2/ |
19 | home:mnhauke:sdr | home:mnhauke:sdr | No | ---- | ---- | 103 | rpm-md | http://download.opensuse.org/repositories/home:/mnhauke:/sdr/openSUSE_Leap_42.2/ |
20 | home:wkazubski | home:wkazubski | No | ---- | ---- | 104 | rpm-md | http://download.opensuse.org/repositories/home:/wkazubski/openSUSE_Leap_42.2/ |
21 | http-download.opensuse.org-2a34e86b | Education | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/Education/openSUSE_Leap_42.2/ |
22 | http-download.opensuse.org-31545117 | openSUSE:Leap:42.2:Update | Yes | (r ) Yes | Yes | 97 | rpm-md | http://download.opensuse.org/update/leap/42.2/oss/ |
23 | http-download.opensuse.org-a0801dc4 | hardware:sdr | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/hardware:/sdr/openSUSE_Leap_42.2/ |
24 | nVidia Graphics Drivers | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 94 | rpm-md | http://download.nvidia.com/opensuse/leap/42.2/ |
25 | openSUSE BuildService - Education | openSUSE BuildService - Education | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/Education/openSUSE_Leap_42.2/ |
26 | openSUSE-Leap-42.1-Update-Non-Oss | openSUSE-Leap-42.1-Update-Non-Oss | Yes | (r ) Yes | Yes | 97 | rpm-md | http://download.opensuse.org/update/leap/42.2/non-oss/ |
27 | repo-debug | openSUSE-leap/42.2-Debug | Yes | (r ) Yes | No | 90 | yast2 | http://download.opensuse.org/debug/distribution/leap/42.2/repo/oss/ |
28 | repo-non-oss | openSUSE-leap/42.2-Non-Oss | Yes | (r ) Yes | Yes | 90 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/non-oss/ |
29 | repo-oss | openSUSE-leap/42.2-Oss | Yes | (r ) Yes | Yes | 90 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/oss/ |
30 | repo-source | openSUSE-leap/42.2-Source | Yes | (r ) Yes | Yes | 90 | yast2 | http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/ |
31 | science | science | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/science/openSUSE_Leap_42.2/ |
32 | security | security | Yes | (r ) Yes | Yes | 98 | rpm-md | http://download.opensuse.org/repositories/security/openSUSE_Leap_42.2/ |
andromeda:/home/fernando #
Disabled should be fine.
The difference between disabled and deleted, is that cached information is not removed for disabled repos. But, otherwise, the work the same (at least in my experience).
Disabled vs. deleted means that in the first case it is very easy to enable again when needed, easier that adding it again.
And a quick look at your repo list.
Apart from the priorities (not many use them, so they stand out), I see at least one 42.1 repo as an left over from am eralier version. Do not mix repos of different openSUSE versions.
I do not know where you read about how to upgrade using the online method, but you should disable all non standard repos, changing the 42.2 in 42.3 in the official ones (OSS, non-OSS, Update, Update-non=OSS) and do the zypper dup.
You should of course also change the 42.2 to 42.3 in all the normally disabled standard repos like Source and Debug, this to avoid problems whenever you want to use them in the future.
After that you can change the other repos one by one to 42.3 URLs, Packman first, and install what you need from them (for Packman by doing the Vendor switch). As only you know why and how you use all those “home” repos, it is you thatt should now know what to do.
why do people not use priorities?
I see at least one 42.1 repo as an left over from am eralier version. Do not mix repos of different openSUSE versions.
26 | openSUSE-Leap-42.1-Update-Non-Oss | openSUSE-Leap-42.1-Update-Non-Oss | Yes | (r ) Yes | Yes | 97 | rpm-md | http://download.opensuse.org/update/leap/42.2/non-oss/
I forgot to change the description of the repo, but the url is the correct 42,2
I do not know where you read about how to upgrade using the online method, but you should disable all non standard repos, changing the 42.2 in 42.3 in the official ones (OSS, non-OSS, Update, Update-non=OSS) and do the zypper dup.
You should of course also change the 42.2 to 42.3 in all the normally disabled standard repos like Source and Debug, this to avoid problems whenever you want to use them in the future.
I read it in the SDB:System_upgrade, but they say “remove all third party/OBS repos you no longer need” so I wasn’t sure if disabling them will be enough.
After that you can change the other repos one by one to 42.3 URLs, Packman first, and install what you need from them (for Packman by doing the Vendor switch). As only you know why and how you use all those “home” repos, it is you thatt should now know what to do.
Better upgrading only with standar repos and then vendor switch to packam than doing the upgrade with packman enabled? why?
regards
Long ago they were often used, but since zypper up is by default vendor sticky, the main reason to use them is gone. Once you have a package from a specific repo, it will only be replaced by newer version from the same repo. Thus once you have chosen to install a package from a repo, there is no danger of reverting.
So they may not hurt, but their usage is limited.
Remark the “you no longer need”. That is different from needing the same repo, but for the newer openSUSE version. Often, an upgrade, in what form, is a good time to clean up things. Removing left overs you do not need any more.
Well, I imagine you could do it with the new Packman, but you then still need the “Vendor switch to Packman” to be sure because the version numbering on the Packman repo vs. the OSS repo might not give you the Packman one. I think that priority might help here, but doing the Vendor switch is more sure.
Remind that you asked advice on how to do it with the most chance to success. And people here will tell you how they succeeded in most cases already since several (may more then 10) upgrades during the years. Other pathes are possible and maybe even quicker (when you omit the time spend on designing the quicker path). So you may do different and that might lead to a good upgrade without doubt. You are of course welcome to test. And people here would love to read your report about your experiences.