Please next time you want to show a list of your repositories use
zypper lr -d
As it is now, the list is almost worthless because it only shows the repos sequence number (#), Aliases and Names as they are on your system, which at the most hints to what they are. The real things are the URIs.
Looking at the names of the affected packages, the updated versions are probably in your graphics repo. But, of course, I am guessing since we don’t have enough information (as hcvv has already told you).
Whether this is actually a problem, if for you to decide. Perhaps you want the packman version with unrestricted codecs, rather than the graphics version which is limited by license requirements. And I think you already have the packman version. So maybe this isn’t a problem at all.
I disabled the graphics repo. It got installed by software.opensuse.org when I installed the current version of hugin. I’ll watch for it next time.
sudo zypper ref;zypper lu
[sudo] password for root:
Repository 'packman' is up to date.
Repository 'Non-OSS Repository' is up to date.
Repository 'Main Repository' is up to date.
Repository 'Main Update Repository' is up to date.
Repository 'Update Repository (Non-Oss)' is up to date.
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
S | Repository | Name | Current Version | Available Version | Arch
--+------------------------+---------------+--------------------+--------------------+-------
v | Main Update Repository | libidn2-0 | 2.2.0-lp152.1.3 | 2.2.0-lp152.2.3.1 | x86_64
v | Main Update Repository | libidn2-lang | 2.2.0-lp152.1.3 | 2.2.0-lp152.2.3.1 | noarch
v | Main Update Repository | libxml2-2 | 2.9.7-lp152.10.3.1 | 2.9.7-lp152.10.6.1 | x86_64
v | Main Update Repository | libxml2-tools | 2.9.7-lp152.10.3.1 | 2.9.7-lp152.10.6.1 | x86_64
Not sure why you thought it didn’t work the first time???
If zypper sees newer package in a repo that is not the vendor for that package it informs you that it won’t update since the vendor is set to a repo with lower numbers
Sorry, I don’t know. Most likely some setting (which I don’t know about) that I have set inadvertently. But for me, now it works and more importantly, I know what to watch for, the next time around.
Basically it is common to see package not to be updated if you have multiple repos that contain the same packages. It is not an error it is just info that some packages in some repo not your current vendor has a higher number. This may be as simple as a build number since packages get rebuilt all the time which increments the build number but does not really mean any change to the code.
I don’t have any packages not to be upgraded, so I can’t fully test this. Remove the “-D” if you want it to actually update instead of just telling you what it will do.