Zypper dup finds many problems doing online update to leap 15.6

I am trying online update from leap 15.5 → 15.6 using “releasever” methodology. I have extra repos such as: geo, education, electronics, games, graphics, and science.

When I keep all the extra repos enabled and run " sudo zypper dup" after repo refresh to leap 15.6, there are 91 problems requiring individual attention.

When I keep all the extra repos disabled and run “sudo zypper dup” after repo refresh to leap 15.6, there are 501 problems requiring individual attention.

Do I need to just wade through the 91 problems (or the 501 problems) or is there some automated way to treat this? I did not have this issue upgrading by “releasever” method to leap 15.5 that I can recall. I cannot see any consistent pattern of the problems.

Any advice.

tom kosvic

It is not quite clear to me what exactly you did.

My way of working thus far (up to 15.5, thus not to 15.6 already).

  1. Check if all repo URLs have the string $releasever in the proper place (by now they should, but you never know).
  2. Disable all non-official repos (for me that is only Packman, but I see you have a lot more, which BTW has it’s drawbacks as you experience right now).
  3. All users should log out and use Ctrl-Alt-F1 to switch to the virtual console.
  4. Login as root.
  5. systemctl isolate multi-user.target.
  6. zypper clean -a then zypper --releasever 15.6 ref then zypper --releasever 15.6 dup --allow-vendor-change.
  7. reboot.
  8. Maybe a check on your repos with zypper lr-d to see if those look fine.
  9. zypper up should not do much but you never know.
  10. Enable Packman (and you have more there).
  11. zypper dup --from packman because all switched back during the upgrade and now we will have a fresh multi-media “repair”.
  12. Ready, but you should now try to update/upgrade your non openSUSE packages from your extra repos. I am not sure, but a zypper up could do much here.

Now you report “problems”, but you do not tell in which step (I assume step #6 above), nor did you bother to show even one of those here. So I will not be surprised when people have not enough information at all to help you with those “problems”.

2 Likes

Here is more on the steps I did. I will follow your step list. Some of your steps are not on the upgrade pages of others.

  1. verify $releasever
(base) tom@mydesktop: ~ $ grep baseurl /etc/zypp/repos.d/*.repo
/etc/zypp/repos.d/download.nvidia.com-$releasever.repo:baseurl=http://download.nvidia.com/opensuse/leap/$releasever
/etc/zypp/repos.d/ftp.gwdg.de-openSUSE_Leap_$releasever_1.repo:baseurl=https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_$releasever/
/etc/zypp/repos.d/http-download.opensuse.org-1ca1690e.repo:baseurl=http://download.opensuse.org/update/leap/${releasever}/oss/
/etc/zypp/repos.d/http-download.opensuse.org-1f61c7be.repo:baseurl=http://download.opensuse.org/distribution/leap/${releasever}/repo/oss/
/etc/zypp/repos.d/opensuse-guide.org-openSUSE_Leap_$releasever.repo:baseurl=http://opensuse-guide.org/repo/openSUSE_Leap_$releasever/
/etc/zypp/repos.d/openSUSE_Leap_${releasever}_1.repo:baseurl=https://download.opensuse.org/repositories/science/${releasever}/
/etc/zypp/repos.d/openSUSE_Leap_${releasever}_2.repo:baseurl=https://download.opensuse.org/repositories/Education/${releasever}/
/etc/zypp/repos.d/openSUSE_Leap_${releasever}_3.repo:baseurl=https://download.opensuse.org/repositories/Application:/Geo/${releasever}/
/etc/zypp/repos.d/openSUSE_Leap_${releasever}_4.repo:baseurl=https://download.opensuse.org/repositories/electronics/${releasever}/
/etc/zypp/repos.d/openSUSE_Leap_${releasever}_5.repo:baseurl=https://download.opensuse.org/repositories/graphics/${releasever}/
/etc/zypp/repos.d/openSUSE_Leap_${releasever}.repo:baseurl=https://download.opensuse.org/repositories/games:/tools/${releasever}/
/etc/zypp/repos.d/repo-backports-update.repo:baseurl=https://download.opensuse.org/update/leap/$releasever/backports/
/etc/zypp/repos.d/repo-non-oss.repo:baseurl=https://download.opensuse.org/distribution/leap/$releasever/repo/non-oss/
/etc/zypp/repos.d/repo-sle-update.repo:baseurl=https://download.opensuse.org/update/leap/$releasever/sle/
/etc/zypp/repos.d/repo-update-non-oss.repo:baseurl=https://download.opensuse.org/update/leap/$releasever/non-oss/
/etc/zypp/repos.d/vivaldi.repo:baseurl=https://repo.vivaldi.com/archive/rpm/x86_64
(base) tom@
  1. I did twice: once with non-official repos enabled and once with non-official repos disabled. Official wiki (SDB:System upgrade - openSUSE Wiki) suggests to disable non-offical repos and then says it is not really necessary anymore; so I did both options

  2. Did not use virtual console. opensuse upgrade wiki does not reference that. Some others do.

4… did zypper commands using sudo not as root. But should be same.

5 Never saw this command referenced any where – “systemctl isolate multi-user.target”
What is purpose?

  1. ran – sudo zypper --releasever 15.6 ref, This completed error free
    ran – sudo zypper --releasever 15.6 dup With non-offical repos enabIed I got 91 problems to resolve. With non-official repos disabled I got 501 problems. I did not run with --allow-vendor-change option. No reference I have seen suggests that but I will try it. Might reduce problem list.
  2. Did not reboot, set repos back to 15.5

I will try again with non-official repos disabled and --allow-vendor-change activated.

thanks for assistance and suggestions

For additional info here is upgrade with all repos incl non-official repose) enabled:
``
(base) tom@mydesktop: ~ $ sudo zypper --releasever=15.6 dup
Warning: Enforced setting: $releasever=15.6
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…
91 Problems:
Problem: 1: problem with the installed bleachbit-4.6.0-1.1.noarch
Problem: 2: problem with the installed geos-devel-3.12.1-lp155.61.1.x86_64
Problem: 3: problem with the installed gflags-devel-2.2.2-lp155.3.4.x86_64
Problem: 4: problem with the installed gsl-2.8-lp155.59.1.x86_64
Problem: 5: problem with the installed gsl-devel-2.8-lp155.59.1.x86_64
Problem: 6: problem with the installed hdf5-gnu-hpc-devel-1.12.3-lp155.217.1.noarch
Problem: 7: problem with the installed hdf5-gnu-mvapich2-hpc-devel-1.12.3-lp155.217.1.noarch
Problem: 8: problem with the installed inkscape-1.2.2-lp155.117.2.x86_64
Problem: 9: problem with the installed inkscape-extensions-extra-1.2.2-lp155.117.2.x86_64
Problem: 10: problem with the installed inkscape-extensions-gimp-1.2.2-lp155.117.2.x86_64
Problem: 11: problem with the installed inkscape-lang-1.2.2-lp155.117.2.noarch
Problem: 12: problem with the installed libJudy1-1.0.5-lp155.15.1.x86_64
Problem: 13: problem with the installed libOpenCL1-2.3.1-lp155.51.1.x86_64
Problem: 14: problem with the installed libamd2-2.4.6-lp155.102.5.x86_64
Problem: 15: problem with the installed libarmadillo12-12.8.3-lp155.371.3.x86_64
Problem: 16: problem with the installed libbtf1-1.2.6-lp155.102.5.x86_64
Problem: 17: problem with the installed libcamd2-2.4.6-lp155.102.5.x86_64
Problem: 18: problem with the installed libccolamd2-2.9.6-lp155.102.5.x86_64
Problem: 19: problem with the installed libcgns4_3-4.3.0-lp155.17.5.x86_64
Problem: 20: problem with the installed libcholmod3-3.0.14-lp155.102.5.x86_64
Problem: 21: problem with the installed libcolamd2-2.9.6-lp155.102.5.x86_64
Problem: 22: problem with the installed libcxsparse3-3.2.0-lp155.102.5.x86_64
Problem: 23: problem with the installed libdca0-0.0.7-150500.1.pm.6.x86_64
Problem: 24: problem with the installed libespeak-ng1-1.51.1-lp155.25.5.x86_64
Problem: 25: problem with the installed libexiv2-27-0.27.6-lp155.207.3.x86_64
Problem: 26: problem with the installed libgd3-2.3.3-lp155.171.2.x86_64
Problem: 27: problem with the installed libgeos_c1-3.12.1-lp155.61.1.x86_64
Problem: 28: problem with the installed libgflags2_2-2.2.2-lp155.3.4.x86_64
Problem: 29: problem with the installed libgphoto2-6-2.5.30-lp155.248.1.x86_64
Problem: 30: problem with the installed libgphoto2-6-lang-2.5.30-lp155.248.1.noarch
Problem: 31: problem with the installed libgslcblas0-2.8-lp155.59.1.x86_64
Problem: 32: problem with the installed libhdf5-gnu-hpc-1.12.3-lp155.217.1.x86_64
Problem: 33: problem with the installed libhdf5-gnu-mpich-hpc-1.12.3-lp155.217.1.x86_64
Problem: 34: problem with the installed libhdf5-gnu-mvapich2-hpc-1.12.3-lp155.217.1.x86_64
Problem: 35: problem with the installed libhdf5_fortran-gnu-mvapich2-hpc-1.12.3-lp155.217.1.x86_64
Problem: 36: problem with the installed libhdf5_hl-gnu-hpc-1.12.3-lp155.217.1.x86_64
Problem: 37: problem with the installed libjxl0_8-0.8.2-lp155.37.3.x86_64
Problem: 38: problem with the installed libklu1-1.3.9-lp155.102.5.x86_64
Problem: 39: problem with the installed libmetis5-5.1.0-lp155.30.1.x86_64
Problem: 40: problem with the installed libopenblas-gnu-hpc-0.3.27-lp155.177.1.x86_64
Problem: 41: problem with the installed libopenblas-gnu-hpc-devel-0.3.27-lp155.177.1.x86_64
Problem: 42: problem with the installed libopenblas-pthreads-gnu-hpc-0.3.27-lp155.177.1.x86_64
Problem: 43: problem with the installed libopenblas-pthreads-gnu-hpc-devel-0.3.27-lp155.177.1.x86_64
Problem: 44: problem with the installed libopencascade-applicationframework7_7-7.7.0-lp155.40.11.x86_64
Problem: 45: problem with the installed libopencascade-foundationclasses7_7-7.7.0-lp155.40.11.x86_64
Problem: 46: problem with the installed libopencascade-modelingalgorithms7_7-7.7.0-lp155.40.11.x86_64
Problem: 47: problem with the installed libopencascade-modelingdata7_7-7.7.0-lp155.40.11.x86_64
Problem: 48: problem with the installed libopencascade-visualization7_7-7.7.0-lp155.40.11.x86_64
Problem: 49: problem with the installed libopencore-amrnb0-0.1.6-150500.1.pm.3.x86_64
Problem: 50: problem with the installed libopencore-amrwb0-0.1.6-150500.1.pm.3.x86_64
Problem: 51: problem with the installed libopencv3_4-3.4.19-lp155.35.7.x86_64
Problem: 52: problem with the installed libopencv409-4.9.0-lp155.1.1.x86_64
Problem: 53: problem with the installed libopencv_aruco409-4.9.0-lp155.1.1.x86_64
Problem: 54: problem with the installed libopencv_face409-4.9.0-lp155.1.1.x86_64
Problem: 55: problem with the installed libopencv_gapi409-4.9.0-lp155.1.1.x86_64
Problem: 56: problem with the installed libopencv_highgui409-4.9.0-lp155.1.1.x86_64
Problem: 57: problem with the installed libopencv_imgcodecs409-4.9.0-lp155.1.1.x86_64
Problem: 58: problem with the installed libopencv_objdetect409-4.9.0-lp155.1.1.x86_64
Problem: 59: problem with the installed libopencv_optflow409-4.9.0-lp155.1.1.x86_64
Problem: 60: problem with the installed libopencv_superres409-4.9.0-lp155.1.1.x86_64
Problem: 61: problem with the installed libopencv_videoio409-4.9.0-lp155.1.1.x86_64
Problem: 62: problem with the installed libopencv_videostab409-4.9.0-lp155.1.1.x86_64
Problem: 63: problem with the installed libopencv_ximgproc409-4.9.0-lp155.1.1.x86_64
Problem: 64: problem with the installed libosdCPU3_4_4-3.4.4-lp155.13.6.x86_64
Problem: 65: problem with the installed libpcre2-16-0-10.44-lp155.81.1.x86_64
Problem: 66: problem with the installed libpcre2-32-0-10.44-lp155.81.1.x86_64
Problem: 67: problem with the installed libpcre2-8-0-10.44-lp155.81.1.x86_64
Problem: 68: problem with the installed libsox3-14.4.2-150500.3.5.pm.2.x86_64
Problem: 69: problem with the installed libspatialite7-5.0.1-lp155.19.1.x86_64
Problem: 70: problem with the installed libspqr2-2.1.0-lp155.102.5.x86_64
Problem: 71: problem with the installed libsuitesparseconfig5-5.13.0-lp155.102.5.x86_64
Problem: 72: problem with the installed libumfpack5-5.7.9-lp155.102.5.x86_64
Problem: 73: problem with the installed libvo-amrwbenc0-0.1.3-150500.1.pm.3.x86_64
Problem: 74: problem with the installed libvo-amrwbenc0-32bit-0.1.3-150500.1.pm.3.x86_64
Problem: 75: problem with the installed libwcs7-7.12-lp155.27.5.x86_64
Problem: 76: problem with the installed metis-5.1.0-lp155.30.1.x86_64
Problem: 77: problem with the installed metis-devel-5.1.0-lp155.30.1.x86_64
Problem: 78: problem with the installed metis-doc-5.1.0-lp155.30.1.noarch
Problem: 79: problem with the installed opencv-4.9.0-lp155.1.1.x86_64
Problem: 80: problem with the installed opencv-devel-4.9.0-lp155.1.1.x86_64
Problem: 81: problem with the installed python3-Cycler-0.11.0-lp155.3.1.noarch
Problem: 82: problem with the installed python3-opencv-4.9.0-lp155.1.1.x86_64
Problem: 83: problem with the installed python3-opengl-accelerate-3.1.6-lp155.24.5.x86_64
Problem: 84: problem with the installed python3-service_identity-21.1.0-lp155.33.1.noarch
Problem: 85: problem with the installed rstudio-2023.06.2+561-1.x86_64
Problem: 86: problem with the installed sox-14.4.2-150500.3.5.pm.2.x86_64
Problem: 87: problem with the installed libgeos3_12_1-3.12.1-lp155.61.1.x86_64
Problem: 88: the to be installed ffmpeg-4-4.4.4-150600.18.pm.2.x86_64 conflicts with ‘ffmpeg-tools’ provided by the to be installed ffmpeg-3-3.4.13-150600.1.pm.8.x86_64
Problem: 89: the to be installed libjpeg62-devel-32bit-62.3.0-150600.22.3.x86_64 requires ‘libjpeg62-devel = 62.3.0’, but this requirement cannot be provided
deleted providers: libjpeg62-devel-62.3.0-lp155.222.1.x86_64
not installable providers: libjpeg62-devel-62.3.0-150600.22.3.x86_64[http-download.opensuse.org-1f61c7be]

Problem: 90: the to be installed python3-dbus-python-devel-1.2.16-150600.3.2.x86_64 requires ‘python3-dbus-python-common-devel = 1.2.16’, but this requirement cannot be provided
deleted providers: python-dbus-python-common-devel-1.2.16-6.3.1.x86_64
not installable providers: python3-dbus-python-common-devel-1.2.16-150600.3.2.x86_64[http-download.opensuse.org-1f61c7be]

Problem: 91: the to be installed libvtk1-9.1.0-bp156.5.65.x86_64 requires ‘libcgns.so.4.3()(64bit)’, but this requirement cannot be provided
deleted providers: libcgns4_3-4.3.0-lp155.17.5.x86_64
not installable providers: libcgns4_3-4.3.0-bp156.2.9.x86_64[http-download.opensuse.org-1f61c7be]

Problem: 1: problem with the installed bleachbit-4.6.0-1.1.noarch
Solution 1: install bleachbit-4.4.2-bp156.2.1.noarch from vendor openSUSE
replacing bleachbit-4.6.0-1.1.noarch from vendor obs://build.opensuse.org/home:andrew_z
Solution 2: keep obsolete bleachbit-4.6.0-1.1.noarch

Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c):


thanks for looking

Let only the below repositories enabled and don’t touch the ${releasever} variable.

#  | Alias                 | Name                                   | Enabled | GPG Check | Refresh | Priority | URI
---+-----------------------+----------------------------------------+---------+-----------+---------+----------+------------------------------------------------------------------
 3 | repo-backports-update | Update repository of openSUSE Backpo-> | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/leap/15.5/backports/
 8 | repo-non-oss          | Repositório Non-OSS                    | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/distribution/leap/15.5/repo/non-oss/
 9 | repo-openh264         | Open H.264 Codec (openSUSE Leap)       | Yes     | (r ) Yes  | Yes     |   99     | http://codecs.opensuse.org/openh264/openSUSE_Leap/
10 | repo-oss              | Repositório principal                  | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/distribution/leap/15.5/repo/oss/
12 | repo-sle-update       | Update repository with updates from -> | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/leap/15.5/sle/
14 | repo-update           | Repositório principal de atualização   | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/leap/15.5/oss
15 | repo-update-non-oss   | Repositório de atualização (Non-OSS)   | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/leap/15.5/non-oss/

Then, change to a virtual terminal (Ctrl+Alt+F1) and execute the following:

The “releasever” methodology is optional. I have 24 15.6 installations. about 25% were fresh installations. The rest were all online upgrades using the tried and true traditional practice of literal version numbers in all repo files, using the following basic procedure:

  1. update installation being upgraded from to latest 15.5 versions of all installed packages
  2. remove all but newest kernel
  3. disable all optional repos
  4. switch all repo file content from 15.5 to 15.6
  5. zypper clean
  6. zypper ref
  7. zypper dup
  8. reenable all optional repos required that have equivalent 15.6 repos
  9. zypper ref
  10. zypper up

If wishing to upgrade from 15.4 (or older), upgrade (to 15.4 first, then) to 15.5, but skip steps 8-10 until 7 is completed for 15.6.

Again, his is as I do it. And for reasons. Almost all software is to be replaced. Thus running the minimum is imminent (at least to me). Thus the login as root on the virtual console (normal users not involved), the multi-user level (no Display Manager running).

(As Leap user you may have missed it, but many Tumbleweed users were hit when they installed a new TW version from their KDE desktop where the whole of KDE was upgraded. Those that did it from the virtual console with no KDE user logged in, had no problems however).

And of course, when one is already rootone does not need the stupid sudo (which I never use BTW).

And you did not try the --allow-vendor-change on the zypper dup`. I assume that many of your “problems” will disappear when you do.

But again, this is how I do it. You are free to to do things otherwise. The most important thing is of course that you read all what I wrote (and all what you find anywhere else) as suggestions. And that you then understand what is suggested and why it is suggested. Read man pages, etc.

That is nowadays a very old-fashioned way to do things. I can understand that you want to stick to the old way of managing versioning, but it is now for years that all repos are preinstalled with the $releasver feature. I think your suggestion that people go and edit all their repo file to undo this and then for their future upgrates again update all their repo files, is very counterproductive. So IMHO you better do not advertise this anymore to new (since already some years) openSUSE users.

2 Likes

I successfully accomplished the update to 15.6 using the $releasver procedure. I continued with all the “non-official” repos enabled. When the "–allow-vendor-change’ was added to sudo zypper dup, the number of problems was greatly reduced from 91 down to 2 which was manageable. That was the problem I was seeking insights into.

4800+ files were replaced. The system properly reboooted into leap 15.6. Upon a cursory review all seems working; included some apps I installed to root by compiling and installing independently from the knowledge of zypper/yast.

Looks good as of now and I think “–allow-vendor-change” should be added to the upgrade wiki procedure to greatly simplify the process. As I recall the $releasever procedure was first introduced in going from 15.4 to 15.5. At least that is when I first saw and used it. It seems to be working fine.

Thanks for all the help.

tom kosvic

@tckosvic The issue is using third-party repositories for the upgrade process is not supported. Testing is only carried out with the default repositories, so whilst it can work if the repositories are present, that’s for the end user to resolve as you have done :wink:

Repo files with literal version strings remain supported, for good reason.

On my installations, all OEM files must be changed anyway to replace the idiotic, redundant, needlessly long-winded names supplied by the installer that induce zypper lr -d output wider than the screen, which among other things, obfuscates diagnosis of repo issues.

# ls -gGl /etc/zypp/repos.d/*repo
-rw-r--r-- 1 153 Jun 12 15:06 /etc/zypp/repos.d/NonOSS.repo
-rw-r--r-- 1 143 Jun 12 15:06 /etc/zypp/repos.d/OSS.repo
-rw-r--r-- 1 270 Jun 12 15:06 /etc/zypp/repos.d/PackmanE.repo
-rw-r--r-- 1 180 Jun 12 15:06 /etc/zypp/repos.d/TDE.repo
-rw-r--r-- 1 192 Jun 12 15:06 /etc/zypp/repos.d/TDEnoarch.repo
-rw-r--r-- 1 129 Jun 12 15:06 /etc/zypp/repos.d/Update.repo
-rw-r--r-- 1 239 Jun 12 15:06 /etc/zypp/repos.d/UpdateBP.repo
-rw-r--r-- 1 145 Jun 12 15:06 /etc/zypp/repos.d/UpdateNonOSS.repo
-rw-r--r-- 1 135 Jun 12 15:06 /etc/zypp/repos.d/UpdateSLE.repo
-rw-r--r-- 1   0 Jun 12 15:06 /etc/zypp/repos.d/repo-backports-debug-update.repo
-rw-r--r-- 1   0 Jun 12 15:06 /etc/zypp/repos.d/repo-backports-update.repo
-rw-r--r-- 1   0 Jun 12 15:06 /etc/zypp/repos.d/repo-sle-debug-update.repo
-rw-r--r-- 1   0 Jun 12 15:06 /etc/zypp/repos.d/repo-sle-update.repo
#

Old-fashioned can be a very good thing, especially when something is not broken and not in need of fixing, as is the case in Leap. Note that each has a timestamp equal to the release date. Each installation here uses files from the exact same file template set on the LAN server. Alterations in the timestamps are cause for investigation. Each file stands on its own, and can be completely understood without reference to some unspecified other file. Editing all those files to change to/from literal version string is a simple process of one sed command that takes mere seconds.

# ls -gGl /etc/zypp/repos.d/OSS.*
-rw-r--r-- 1 143 Jun 12 15:06 /etc/zypp/repos.d/OSS.repo
-rw-r--r-- 1 147 Jun 12 15:06 /etc/zypp/repos.d/OSS.repo-gwdg
-rw-r--r-- 1 143 Jun 12 15:06 /etc/zypp/repos.d/OSS.repo6
-rw-r--r-- 1 138 Jun 12 15:06 /etc/zypp/repos.d/OSS.repoC
-rw-r--r-- 1 143 Jun 12 15:06 /etc/zypp/repos.d/OSS.repoD
-rw-r--r-- 1 159 Jun 12 15:06 /etc/zypp/repos.d/OSS.repoLmia
#

When repo trouble is apparent, as is common with cdn.o.o & mirrorcache.o.o mirrors located in USA, it’s a simple process to over-copy a file with simple rename to switch to some other repo and continue, instead of wasting time waiting to try again later.

I do not think I denied that. After all $releasever is only a string replacement.

And for the rest of your long story, I do not deny that adapting e.g. Aliases is a bad thing. After all man zypper says

Alias serves as a shorthand for the long URI or name of the repository

And the alias I see often do definitely not fulfill that definition.

But this all has nothing to do with the use of $releasever and has also nothing to do with the OPs problem. Thus I do not understand why you post it here.

1 Like

deleted response