I have a fully updated leap 42.3 installation. When examining zypper dup it says there are
24 new packages
7 to be removed packages (including my nvida drivers)
64 packages to be upgraded
64 packages to change vender.
Is this advisable to do? What am I upgrading to?
I see no replacement for the nvida drivers. That worries me.
Thanks for any advice,
Tom Kosvic
Post the complete output here in Code-Tags.
Also
zypper lr -d
hello 
Why should you dup a fully updated 42.3 install? dup is good to upgrade (to 15?) or for tumbleweed
the difference is probably related to vendor changes. If you have packman may be it could be useful to use yast repo view, “upadate all packages to this repo” (link on the upper part of the window)
jdd
No. On Leap “zypper dup” will by default install newest version of each package found across all enabled repositories. Meaning it can replace packages with incompatible versions that happen to be present somewhere, even if you did not intend to do it. Normally there is no need to use “dup” when updating Leap installation; in exceptional cases always run it with “–no-allow-vendor-change”.
No, it isn’t.
What am I upgrading to?
You would be upgrading from 42.3 to 42.3. In principle, that should be okay.
I see no replacement for the nvida drivers. That worries me.
That’s one of the reasons that the change is not advisable. Strictly speaking, the nvidia drivers are not part of 42.3. You chose to add them. By “zypper dup” cannot read your mind.
Anyway, just for the heck of it, I tried “zypper dup” (but said “no” to actually making the changes).
It showed 7 vendor-changes. They were all from “packman” to “opensuse”. Since I have “packman” at a better priority (98 instead of 99), it should not do that unless there’s a good reason. So perhaps those packages are no longer in packman. This could be due to the expiry of the patent restrictions on MP3 codecs. So I might look into manually making those changes anyway. The first on the list is “lame”, and it seems to have disappeared from packman, but shown up in the update repo.
It also wanted to install “lifecycle-data-openSUSE”. I’ll have to look into what that is, though it is probably a list of end-of-support dates.
Personally, I would be cautious of blindly using “zypper dup” on a standard release (not counting Tumbleweed). But if you use it just as a dry run, to review packages that you should examine, then that can make sense .
I run “zypper dup” on non-TW openSUSE if I find the system is suffering from some kind of internal inconsistency… really basic stuff that should work but isn’t, and in particular if the kernel and kernel-devel won’t match, and if “zypper up” does not solve those problems.
Those situations are few and far in between, so I do this very rarely.
And, of course I run that command if I’m truly migrating from one major openSUSE version or release to another.
TSU
zypper dup on LEAP should be run only when doing a full vendor change to a particular repo using the --from switch for example
zypper dup --from packman
or when doing an OS upgrade with a minimal amount of installed repo’s (only the default 4 repos: OSS, non-OSS, update-OSS, update-non-OSS) running zypper dup when having a lot of enabled repo’s will install the newest versions of packages from any repo they’re found and if you have extra repositories will most certainly break your OS
unlike LEAP TW uses repo stickiness and running zypper dup will not change package vendors the equivalent LEAP command would be
zypper dup --no-allow-vendor-change
which would be more or less the same as running
zypper up