zypper up question

This morning I did a zypper up and I got the following:

sudo zypper up
[sudo] password for root: 
Loading repository data...
Reading installed packages...

The following 13 package updates will NOT be installed:
  libavcodec57 libavfilter6 libavformat57 libavresample3 libavutil55 libgstgl-1_0-0 libgstphotography-1_0-0 libpostproc54 libquicktime0 libsox3 libswresample2
  libswscale4 sox

The following 15 packages are going to be upgraded:
  cpp7 gcc7 gcc7-c++ gcc7-info libasan4 libcilkrts5 libgfortran4 libsensors4 libsensors4-32bit libstdc++6-devel-gcc7 libubsan0 libwicked-0-6 MozillaFirefox
  wicked wicked-service

15 packages to upgrade.
Overall download size: 88.8 MiB. Already cached: 0 B. After the operation, additional 379.8 KiB will be used.
Continue? [y/n/...? shows all options] (y): n

What is:

The following 13 package updates will NOT be installed:
   libavcodec57 libavfilter6 libavformat57 libavresample3 libavutil55  libgstgl-1_0-0 libgstphotography-1_0-0 libpostproc54 libquicktime0  libsox3 libswresample2
  libswscale4 sox

Is this something I should worry about and/or do something about it?

Thanks

No.
These are supplied by packman and opensuse repos. If you’ve chosen, say, packman then system has higher version number in the opensuse repo but will leave it with packman (or vice-versa).

If you check these in Yast2 software management you’ll see the 2 different versions.

If you do “zypper ref; zypper lu” you’ll probably find all those are Packman versions of installed packages that came from standard repos. Zypper up will not switch those packages to another repo. If you wish to make the switch, you can do “zypper dup --from Packman”, or pick and choose using YaST.

Say not Packman or OSS Repo, say in “different Repositories” “different Versions”.

The following 24 package updates will NOT be installed:
..........virtualbox virtualbox-qt
zypper se -s virtualbox-qt
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                    | Typ   | Version             | Arch   | Repository               
---+-------------------------+-------+---------------------+--------+--------------------------
v  | virtualbox-qt           | Paket | 6.0.6-5.15          | x86_64 | Sauerland-kernel         
i+ | virtualbox-qt           | Paket | 6.0.6-lp150.5.3     | x86_64 | Sauerland-Leap15.0       
v  | virtualbox-qt           | Paket | 6.0.6-2.21          | x86_64 | kernel-stable-kmp        
v  | virtualbox-qt           | Paket | 6.0.6-2.22          | i586   | kernel-stable-kmp        
v  | virtualbox-qt           | Paket | 5.2.22-lp150.4.24.1 | x86_64 | openSUSE-Leap-15.0-Update
v  | virtualbox-qt           | Paket | 5.2.20-lp150.4.20.1 | x86_64 | openSUSE-Leap-15.0-Update
v  | virtualbox-qt           | Paket | 5.2.18-lp150.4.17.1 | x86_64 | openSUSE-Leap-15.0-Update
v  | virtualbox-qt           | Paket | 5.2.18-lp150.4.14.1 | x86_64 | openSUSE-Leap-15.0-Update
v  | virtualbox-qt           | Paket | 5.2.16-lp150.4.11.1 | x86_64 | openSUSE-Leap-15.0-Update
v  | virtualbox-qt           | Paket | 5.2.16-lp150.4.9.1  | x86_64 | openSUSE-Leap-15.0-Update
v  | virtualbox-qt           | Paket | 5.2.14-lp150.4.6.1  | x86_64 | openSUSE-Leap-15.0-Update
v  | virtualbox-qt           | Paket | 5.2.12-lp150.4.3.1  | x86_64 | openSUSE-Leap-15.0-Update
v  | virtualbox-qt           | Paket | 5.2.10-lp150.3.6    | x86_64 | openSUSE-Leap-15.0-Oss

Are you implying that I should also upgrade the Packman too?

Thanks

No, he isn’t.

When you did a zypper up, you will have

  • the patches from the Update repos belonging to the standard openSUSE repos;
  • the newest versions of all repos your are subscribed to (and that is in your case including Packman).

The warning(s) you see are because there are packages from repo A, that have higher version numbers on repo B. zypper dup will NOT switch vendors, and thus does NOT install those newer versions, but instead in warns you about the fact. As you did not decide to have those packages from repo A without a reason, you will most probably take this warning as it is, a warning.

Take the case of Packman. You decided that you want to have the non-crippled multi-media packages from Packman. Thus, even when a version number of the same package is higher in the OSS repo, you do not want it because it is crippled.