LANG=C zypper ref && LANG=C zypper patch && LANG=C zypper up
Retrieving repository 'openSUSE:Leap:15.1:Update' metadata ................................................................[done]
Building repository 'openSUSE:Leap:15.1:Update' cache .....................................................................[done]
Repository 'libdvdcss repository' is up to date.
Retrieving repository 'Packman Repository' metadata .......................................................................[done]
Building repository 'Packman Repository' cache ............................................................................[done]
Repository 'openSUSE-leap/15.1-Non-Oss' is up to date.
Repository 'openSUSE-leap/15.1-Oss' is up to date.
Retrieving repository 'openSUSE-15.1-Update' metadata .....................................................................[done]
Building repository 'openSUSE-15.1-Update' cache ..........................................................................[done]
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Nothing to do.
Loading repository data...
Reading installed packages...
The following 3 package updates will NOT be installed:
vlc-vdpau youtube-dl-bash-completion youtube-dl-zsh-completion
Nothing to do.
Is this please some error which should be corrected ?
There are newer version of those files in other repos other than the one that installed the packages
you can do
zypper in -f vlc-vdpau youtube-dl-bash-completion youtube-dl-zsh-completion
to force the updates
or
zypper up --allow-vendor-change
to change where they come from.
Yes, you probably have them from OSS instead of Packman (and you have youtube-dl itself from Packman, a bit inconsistent). Means you didn’t do or (or repeat) the vendor change to Packman.
If you wish you can disable vendor stickyness completely - in this case the package manager will not ask permission to change vendor for packages, and updating will just install whatever package has the highest version number, regardless of where it comes from.
I always use “zypper update --allow-vendor-change”, but you may want to carefully read what changes zypper is going to make.
If you want to allow vendor change, then it is important that you carefully set repo priorities. I know that you do that. And I do that. But most users find it confusing.
Here’s my practice:
For the default repos (part of a standard install), I leave the priority=99 (the default).
For the packman repo, I set a lower priority. I’m currently using 97. Note that with zypper, a lower priority number really means a higher priority. A lower priority number makes the repo more preferred.
For other repos, I usually set priority to 100 or higher. I want the standard repos to be preferred over those in most cases. But then I usually disable other repos except when I am explicitly using them.
For updates: I use “zypper update”. I do not allow vendor change.
Occasionally, after an update: I do
zypper dup -D --allow-vendor-change
With that “-D”, it doesn’t actually do anything, It tells me what it would do, if this were not a dry run. Most of the time, it says “nothing to do”. Occasionally, it wants to move a package from one repo to another. This is usually moving a package from the standard openSUSE repos to packman. And in that case, I will probably repeat the command, but without the “-D”, – because I usually do want to move packages to packman.
Again, I described my personal practice. People need to decide on their own practices. Someone new to openSUSE might just want to stick to the defaults.
Which would be rather stupid if you want to keep your Packman installed packages to stick to Packman. Which is what most people want (as long as they want their multi-media to function).
erlangen:~ # zypper dist-upgrade --auto-agree-with-licenses --allow-vendor-change --allow-downgrade
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
The following item is locked and will not be changed by any action:
Available:
plymouth
Nothing to do.
erlangen:~ #
The above minimizes number of questions asked by “zypper dist-upgrade” and sticks to packman whenever possible.
Why are you bringing zypper dup at all in this thread? This is about Leap 15.1 and the OP just wants to keep up-to-date. That means we are talking about zypper patch and/or zypper up. but never about zypper dup!
localhost:~ # zypper update --auto-agree-with-licenses --allow-vendor-change --allow-downgrade
Loading repository data...
Warning: Repository 'Aktualisierungs-Repository (Nicht-Open-Source-Software)' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...
The following 2 packages are going to be upgraded:
curl libcurl4
2 packages to upgrade.
Overall download size: 669.8 KiB. Already cached: 0 B. No additional space will be used or freed after the operation.
Continue? [y/n/v/...? shows all options] (y):
Retrieving package libcurl4-7.66.0-lp152.3.3.1.x86_64 (1/2), 340.8 KiB (559.5 KiB unpacked)
Retrieving delta: ./x86_64/libcurl4-7.66.0-lp152.2.6_lp152.3.3.1.x86_64.drpm, 116.9 KiB
Retrieving: libcurl4-7.66.0-lp152.2.6_lp152.3.3.1.x86_64.drpm ...................................................[done]
Applying delta: ./libcurl4-7.66.0-lp152.2.6_lp152.3.3.1.x86_64.drpm .............................................[done]
Retrieving package curl-7.66.0-lp152.3.3.1.x86_64 (2/2), 329.0 KiB (479.2 KiB unpacked)
Retrieving delta: ./x86_64/curl-7.66.0-lp152.2.6_lp152.3.3.1.x86_64.drpm, 126.6 KiB
Retrieving: curl-7.66.0-lp152.2.6_lp152.3.3.1.x86_64.drpm .......................................................[done]
Applying delta: ./curl-7.66.0-lp152.2.6_lp152.3.3.1.x86_64.drpm .................................................[done]
Checking for file conflicts: ....................................................................................[done]
(1/2) Installing: libcurl4-7.66.0-lp152.3.3.1.x86_64 ............................................................[done]
(2/2) Installing: curl-7.66.0-lp152.3.3.1.x86_64 ................................................................[done]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.
localhost:~ #
update for Leap takes the same parameters as dist-upgrade for Tumbleweed.The same procedure applies to both distributions.
I see that there is a repository called Education https://download.opensuse.org/repositories/Education/openSUSE_Leap_15.3/ with the version of 6.19 for wine but the Main Repository for openSUSE has it as wine 6.0. Is that why it is not updating?
Have I by accident added the Education repo, or is it part of openSUSE?
There is no Update for wine in openSUSE Leap 15.3.
The policy of openSUSE is not to upgrade to a newer Version of any Software in the lifetime of a openSUSE Version. Only patches and updates were done.
So wine will be stayed in Version 6.0 in Leap 15.3.
