Normally, incorrect.
I have seen that “zypper update” will update to the latest version from any configured repository unless you specified the app should come from only a specific repository or vendor.
TSU
It looks OK and should not be touched.
I only mentioned looking at this to know why a system shouldn’t ordinarily be left running “xhost -local” nothing else.
TSU
I thought that’s what the option “–allow-vendor-change” is for? That’s what I found in /etc/zypp/zypp.conf:
##
## EXPERTS ONLY: TUNE DISTRIBUTION UPGRADE (DUP)
## Set whether to allow changing the packages vendor upon DUP. If you
## are following a continuous distribution like Tumbleweed or Factory
## where you use 'zypper dup --no-allow-vendor-change' quite frequently,
## you may indeed benefit from disabling the VendorChange. Packages from
## OBS repos will then be kept rather than being overwritten by Tumbleweeds
## version.
##
## Valid values: boolean
## Default value: true
##
solver.dupAllowVendorChange = false
Could that possibly have been set to “true”? The conf-file says that’s the default - hm? I didn’t change that AFAIK - but I’m on Leap, anyway.
Thats not true.
zypper up will not change the Repository for an installed package.
But if there are some dependencies, zypper will ask if it should change the Repo.
But zypper will not change without asking.
And zypper dup has also the –allow-vendor-change not set.
You can set this behavior in the /etc/zypp/zypp.conf.
There is some misinformation about zypper update and dist-upgrade in this thread.
Unlike most distros, openSUSE differentiates between an update which advances the package version in small steps and an upgrade which does much more and usually refers to the distribution upgrade which replaces entire subsystems, often advancing (or installing a previous) to a major version and subsystems.
So openSUSE users have to be very careful when describing either an update or an upgrade, we distinctly refer to very different things and there are different commands for each.
zypper update (or zypper up) is typically used to update a normal release distro like LEAP. When you’re running a version 15.2 or a 15.3 for example, for purposes of stability you choose LEAP because changes are incremental so in theory has fewer issues both with itself and supporting applications.
zypper distribution-upgrade (or zypper dup) is used most often to move from one major version to another, like moving from 15.2 to 15.3. It can also be used for other major system changes like moving from LEAP to Tumbleweed or vice versa. If you’re running Tumbleweed, because it’s a rolling release every change is a major re-installation so there is no such thing as incremental updating, you only have distribution upgrades.
Whenever you run either of these two commands, as you might expect there is always a check for currency, so refreshing is always invoked if needed. You can refresh separately or simply skip it as an unneeded separate command when updating or distribution-upgrading although because of the very major action of an upgrade a prior refresh is generally recommended anyway.
zypper update has often been described in these forums as updating packages only from the same repository as the original. I have not seen this to be the case and the zypper man pages (link follows below) also does not say this. So, for example if you’re running a version of an app from the OSS and add a special repository that has a newer version, “zypper up” should automatically update to the newest minor version of that application no matter what repository the newer version comes from. If there is a new major version of the application, you will likely need to explicitly install that new major version explicitly.
You can also see this behavior installing unintentional packages from repos when people make the mistake of configuring a Tumbleweed repo on a LEAP system. You don’t need to do a “dup” all it takes is an “up” to pull in all those Tumbleweed packages into your LEAP system, severely damaging your system and that is because the TW packages are more recent. If the situation was the other way where a Tumbleweed system was configured with LEAP repos, although there might be some damage, it’s not nearly as extensive because it’s unlikely very many LEAP packages would have a more recent version than Tumbleweed packages.
You can find this also in the carefully worded zypper MAN pages…
https://www.unix.com/man-page/suse/8/zypper/
TSU
I think we can agree we’re talking about default behaviors without any special flags…
From the zypper MAN pages, note that “vendor” is the only parameter mentioned that would block a package from installing… No mention of repo.
And, I’ve updated systems as I described… Just added a repo (eg a KDE Frameworks repo) and updated the system with a “zypper up.” In no way did I specify that default packages in my system were to be replaced by packages from the new repo… I just added the repo and updated.
update (up) [options] [packagename] ... Update installed packages with newer versions, where possible.
This command will not update packages which would require change of package vendor unless the vendor is specified in /etc/zypp/ven-
dors.d, or which would require manual resolution of problems with dependencies. Such non-installable updates will then be listed in
separate section of the summary as "The following package updates will NOT be installed:".
To update individual packages, specify one or more package names. You can use the '*' and '?' wildcard characters in the package names to specify multiple packages matching the pattern.
Just because an option is made available doesn’t mean that the option has to be explicitly set.
Depends on the default behavior.
If you don’t know what the default behavior is, then go ahead and explicitly set whatever you want to be safe.
In many cases the flag is explicitly available because when you’re scripting you might want to set one way, and later in the same script set it back to the original way without exiting the script so defaults are reset.
TSU
Hi Tsu,
Well, I didn’t mess with the settings. I have just been looking what permanent setting is available. The config file was change on 18th March. Don’t know what has triggered that. I might well have stepped into that trap “up vs. dup”. I have noticed the setting was just referring to the -dup option and wondered what is the default for -up. Alway happy to learn! 
@tsu
hp-laptop:/home/stephan # LANG=C zypper se -s Ausweis
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-------------+------------+--------------------+--------+-----------------------
v | AusweisApp2 | package | 1.22.1-lp152.2.9.1 | x86_64 | Main Update Repository
v | AusweisApp2 | package | 1.22.0-lp152.2.6.1 | x86_64 | Main Update Repository
i+ | AusweisApp2 | package | 1.22.0-lp152.1.2 | x86_64 | Sauerland-15.2
v | AusweisApp2 | package | 1.20.2-lp152.2.3.1 | x86_64 | Main Update Repository
v | AusweisApp2 | package | 1.20.0-lp152.1.6 | x86_64 | Main Repository
| AusweisApp2 | srcpackage | 1.22.1-lp152.2.9.1 | noarch | Main Update Repository
| AusweisApp2 | srcpackage | 1.22.0-lp152.2.6.1 | noarch | Main Update Repository
| AusweisApp2 | srcpackage | 1.22.0-lp152.1.2 | noarch | Sauerland-15.2
| AusweisApp2 | srcpackage | 1.20.2-lp152.2.3.1 | noarch | Main Update Repository
hp-laptop:/home/stephan # LANG=C zypper up
Loading repository data...
Reading installed packages...
The following 4 items are locked and will not be changed by any action:
Available:
broadcom-wl broadcom-wl-kmp-default libqt5-qtvirtualkeyboard r8168-blacklist-r8169
The following 25 package updates will NOT be installed:
AusweisApp2 cpio cpio-lang cpio-mt curl fontconfig kernel-default-devel-5.11.11-1.1.gdbc4a02 kernel-devel-5.11.11-1.1.gdbc4a02 kernel-macros libcurl4 libfaad2 libfdk-aac2 liblilv-0-0 libpcsclite1 libSDL2-2_0-0
libserd-0-0 libsord-0-0 libsratom-0-0 libva-glx2 libva-wayland2 pcsc-lite perl-Glib-Object-Introspection rtl8821ce-kmp-default rtw88-kmp-default-git20210323_k5.11.10_2.gfa5dcf1-2.6 ucode-intel
Nothing to do.
hp-laptop:/home/stephan # LANG=C zypper lr -d | grep -Ei 'oss|Sauerl'
2 | Sauerland-Kernel-Stable | Sauerland-Kernel-Stable | Yes | (r ) Yes | Yes | 10 | rpm-md | https://download.opensuse.org/repositories/home:/Sauerland/Kernel_stable/ |
3 | openSUSE_Leap_15.2 | Sauerland-15.2 | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15.2/ |
4 | openSUSE_Leap_15.2_Update | Sauerland-15.2-Update | Yes | (r ) Yes | Yes | 15 | rpm-md | https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15.2_Update/ |
7 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.2/repo/non-oss/ |
8 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.2/repo/oss/ |
9 | repo-source | Source Repository | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.2/repo/oss/ |
10 | repo-source-non-oss | Source Repository (Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.2/repo/non-oss/ |
11 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.2/oss/ |
12 | repo-update-non-oss | Update Repository (Non-Oss) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/update/leap/15.2/non-oss/ |
hp-laptop:/home/stephan #
No update when executing zypper up.
Only:
The following 25 package updates will NOT be installed:
AusweisApp2…
And that is the meaning of:
zypper up will not update this package because this package is in another Repo. But this package has a higher number or the Repo has a higher priority (not in this cause, it has 99).
So please do not tell it wrong.
First,
I’m not sure what you are testing… Perhaps your private Saurland repo’s contents compared to what is already on your system? (Am guessing)
In any case, zypper is at least saying that it has discovered multiple possibilities that are for some reason are decided one way and is informing you that there are options not enacted.
Some possible reasons for zypper to not update packages found somewhere and not installed…
- The package is the same version, so there is no reason to install the newly discovered package in the new repository
- The package is explicitly locked in some way
- There is a dependency on an existing installed package
- The Maintenance people have made a specific decision that over-rides others, like specifying a standard version of the kernel.
That’s just off the top of my head, I don’t know if there are other reasons that don’t come to mind immediately.
TSU
I just ran **zypper up **and got this
The following 46 package updates will NOT be installed:
clementine cmus cmus-plugin-cue cmus-plugin-ffmpeg cmus-plugin-flac cmus-plugin-mpc cmus-plugin-pulse cmus-plugin-wavpack conky ffmpegthumbnailer graphviz graphviz-gd graphviz-gnome
graphviz-plugins-core icoutils ImageMagick ImageMagick-config-7-SUSE imlib2-loaders libdjvulibre21 libdmtx0 libffmpegthumbnailer4 libgd3 libgphoto2-6 libgphoto2-6-lang libgraphviz6
libimagequant0 libImlib2-1 libjbig2 libjpeg8 libmpv1 libopenjp2-7 libopenjpeg1 libpodofo0_9_6 libprojectM3 libtiff5 libwebp7 libwebpdemux2 libwebpmux3 libzvbi0 mozilla-nss-certs mpv
mpv-bash-completion mpv-mpris optipng pngquant podofo
A few days back I think they were like 25, now it says they’re 46. When I first installed openSUSE, I installed vlc and when tried playing some video it wouldn’t play it, so I search and found that I needed to add packman repo, so I did. Some other day, I discovered kawaii-player, which I use in Debian, is availbale in the repos, so I installed, but it didn’t work, I thought the reason might be the version which quite old, 2 something while current one is 5, after some digging, I found the multimedia repo, it has kawaii-player 5, so I added it too and install it, sadly it doesn’t work either. So far, I added 4 repos, including graphics.
| Alias | Name | Enabled | GPG Check | Refresh
—±--------------------------±-------------------------------------------------±-----------±-----------------±----------
1 | MEGAsync | MEGAsync | Yes | (r ) Yes |Yes
2 | dvd | dvd | Sí | (r ) Yes |Yes
3 | graphics | graphics | Yes | (r )Yes | Yes
4 | home_benoit_monin | benoit_monin’s Home Project (openSUSE_Leap_15.2) | Yes | (r ) Yes | No
5 | mozilla-x86_64 | mozilla-x86_64 | Yes | (r ) Yes | No
6 | multimedia-apps-x86_64 | multimedia-apps-x86_64 | Yes | (r )Yes | No
7 | openSUSE-Leap-15.2-1 | openSUSE-Leap-15.2-1 | No | ---- | ----
8 | packman | packman | Yes | (r ) Yes | Yes
9 | repo-debug | Debug Repository | No | ---- | ----
10 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ----
11 | repo-debug-update | Update Repository (Debug) | No | ---- | ----
12 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ----
13 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes
14 | repo-oss | Main Repository | Yes | (r )Yes |Yes
15 | repo-source | Source Repository | No | ---- | ----
16 | repo-source-non-oss | Source Repository (Non-OSS) | No | ---- | ----
17 | repo-update | Main Update Repository |Yes | (r ) Yes | Yes
18 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) [FONT=monospace]Yes | Yes
[/FONT]
I was thinking of opening a thread to ask for some advice in this, but since we’re at it, I just took the opportunity to do it here. Is there something wrong with this? And if so, what should I do to fix it?
Please, your repo list is of no use.
- It is not between CODE tags.
- It does not include the line with the command, so we have only output, but not what you asked for.
- We need the URLs to know what the repos are, thus use
zypper lr -d
Ok, I think I solved it 
I took a second look at that list and saw ImageMagick there, since I know this is a graphics pkg, I wondered whether since I had added the graphics repo, that would be the reason for it to show, and indeed it was. I launched yast and checked that list, and the new pkgs came from graphics repo, so I installed them. I also removed kawaii-player and the multimedia repo since there was some missed dependencies not provided by any repo, and that’s probably the reason it didn’t work, the missing pkg is libavcoded58 something. I ran **zypper up **again and now I get this
The following 8 package updates will NOT be installed::
conky libdjvulibre21 libjbig2 libopenjp2-7 libopenjpeg1 libwebp7 libwebpdemux2 pngquant
Nothing to do
That looks to me like an improvement from the previous output. Anything else I should be doing? Thank you all for all the input and helpful replies. I’m still learning the inner workings of this great distro, so I do appreciate getting so much info from experienced users like you
Yeah, I just noticed that, I probably hit “quote” button instead of “code”. Sorry about that. Here’s what you asked for
moltke ~ zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+---------------------------+--------------------------------------------------+------------+------------------+------------+-----------+--------+----------------------------------------------------------------------------------------------+---------
1 | MEGAsync | MEGAsync | Yes | (r ) Yes | Yes | 99 | rpm-md | https://mega.nz/linux/MEGAsync/openSUSE_Leap_15.0/ |
2 | dvd | dvd | Yes | (r ) Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_15.2/ |
3 | graphics | graphics | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/graphics/openSUSE_Leap_15.2 |
4 | home_benoit_monin | benoit_monin's Home Project (openSUSE_Leap_15.2) | Yes | (r ) Yes | No | 99 | rpm-md | https://download.opensuse.org/repositories/home:/benoit_monin/openSUSE_Leap_15.2/ |
5 | mozilla-x86_64 | mozilla-x86_64 | Yes | (r ) Yes | No | 99 | rpm-md | https://ftp.lysator.liu.se/pub/opensuse/repositories/mozilla/openSUSE_Leap_15.2/ |
6 | openSUSE-Leap-15.2-1 | openSUSE-Leap-15.2-1 | No | ---- | ---- | 99 | rpm-md | hd:/?device=/dev/disk/by-id/usb-Kingston_DataTraveler_2.0_0014780F99555B8B190F000B-0:0-part2 |
7 | packman | packman | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.2/ |
8 | repo-debug | Debug Repository | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.2/repo/oss/ |
9 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.2/repo/non-oss/ |
10 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.2/oss/ |
11 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.2/non-oss/ |
12 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.2/repo/non-oss/ |
13 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.2/repo/oss/ |
14 | repo-source | Source Repository | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.2/repo/oss/ |
15 | repo-source-non-oss | Source Repository (Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.2/repo/non-oss/ |
16 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.2/oss/ |
17 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.2/non-oss/ |
moltke ~
Thanks for your reply. Note that it is a bit diffrent since I just removed/disabled the multimedia repo.
- Please if you add and enable a Repo. also enable the refresh. That will prevent you for some complications on update with unsynchronized package-versions in that Repo.
- Please do not use Packman Repo and multimedia:libs Repo at the same time, that will brake your multimedia packages at some time. multimedia:apps Repo has nothing to do with this.
Ok, got it. Thank you. Actually, I did search about whether there could be some conflicting issues by adding those two repos at the same time, but didn’t find anything that told me there was. I was a bit reluctant to do it because I had some bad experience with deb-multimedia in Debian and was afraid of going to a similar situation here. I tried anyway, didn’t work for what I wanted, so I removed it. Thanks again for all your help. Much appreciated.