Online Upgrade to 15.4 -- retain and update OBS repo installed packages

English Install/Boot/Login
1

I am still working on online upgrade. I wish to try to retain and upgrade packages that have been installed from the OBS repos such as science, games, geo, education, electronics, etc. Much time was spent installing these packages and configuring them. I’d like to avoid a redo. I manually edited the urls for the OBS repos as the naming convention is changed.I would like suggestions as to what to do on “problem” messages I am getting doing a “dry run”. Initially there were 5 problems denoted. I took solution 1 on each. Then a second set of 4 problems were stated. After I selected option 1 on each, a thrd set of 3 problem as denoted. Then there was a set of 2 problems. I cancelled after that.
I know it is not possible to say which option to select but I need a general philosophy as to what to do to give the best chances of keeping these apps operational.
I hope this is not too lengthy. Code output is below:

(base) tom@mydesktop:~> sudo zypper --releasever=15.4 dup  --dry-run   --download-onl
y  --auto-agree-with-licenses  --allow-vendor-change
[sudo] password for root:  
Warning: Enforced setting: $releasever=15.4
Retrieving repository 'nVidia Graphics Drivers' metadata ......................[done]
Building repository 'nVidia Graphics Drivers' cache ...........................[done]
Retrieving repository 'Packman Repository' metadata ...........................[done]
Building repository 'Packman Repository' cache ................................[done]
Retrieving repository 'leap 15.4 -- games' metadata ...........................[done]
Building repository 'leap 15.4 -- games' cache ................................[done]
Retrieving repository 'leap 15.4 -- science' metadata .........................[done]
Building repository 'leap 15.4 -- science' cache ..............................[done]
Retrieving repository 'leap 15.4 -- education' metadata .....................................................................................................[done]
Building repository 'leap 15.4 -- education' cache ..........................................................................................................[done]
Retrieving repository 'leap 15.4 -- geo' metadata ...........................................................................................................[done]
Building repository 'leap 15.4 -- geo' cache ................................................................................................................[done]
Retrieving repository 'leap 15.4 -- electronics' metadata ...................................................................................................[done]
Building repository 'leap 15.4 -- electronics' cache ........................................................................................................[done]
Retrieving repository 'leap 15.4 -- graphics' metadata ......................................................................................................[done]
Building repository 'leap 15.4 -- graphics' cache ...........................................................................................................[done]
Retrieving repository 'Update Repository of openSUSE Backports' metadata ....................................................................................[done]
Building repository 'Update Repository of openSUSE Backports' cache .........................................................................................[done]
Retrieving repository 'Non-OSS Repository' metadata .........................................................................................................[done]
Building repository 'Non-OSS Repository' cache ..............................................................................................................[done]
Retrieving repository 'Main Repository' metadata ............................................................................................................[done]
Building repository 'Main Repository' cache .................................................................................................................[done]
Retrieving repository 'Update Repository with updates from SUSE Linux Enterprise 15' metadata ...............................................................[done]
Building repository 'Update Repository with updates from SUSE Linux Enterprise 15' cache ....................................................................[done]
Retrieving repository 'Update Repository (OSS)' metadata ....................................................................................................[done]
Building repository 'Update Repository (OSS)' cache .........................................................................................................[done]
Retrieving repository 'Update Repository (Non-Oss)' metadata ................................................................................................[done]
Building repository 'Update Repository (Non-Oss)' cache .....................................................................................................[done]
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...
**5 Problems**:
Problem: the installed python3-Sphinx-doc-man-1.8.5-1.30.noarch requires 'python3-Sphinx = 1.8.5', but this requirement cannot be provided
Problem: the to be installed pipewire-libjack-0_3-0.3.49-150400.1.5.x86_64 conflicts with 'libjackserver0' provided by the installed libjackserver0-1.9.12-1.33.x86
_64
Problem: the to be installed libpoppler-devel-22.01.0-150400.1.5.x86_64 requires 'libboost_headers-devel >= 1.58', but this requirement cannot be provided
Problem: the installed libboost_thread1_75_0-devel-1.75.0-2.5.x86_64 requires 'libboost_headers1_75_0-devel = 1.75.0', but this requirement cannot be provided
Problem: the installed libpoppler-glib-devel-0.79.0-3.5.1.x86_64 requires 'libpoppler-glib8 = 0.79.0', but this requirement cannot be provided

Problem: the installed python3-Sphinx-doc-man-1.8.5-1.30.noarch requires 'python3-Sphinx = 1.8.5', but this requirement cannot be provided
  deleted providers: python3-Sphinx-1.8.5-1.24.noarch
 Solution 1: deinstallation of python3-Sphinx-doc-man-1.8.5-1.30.noarch
 Solution 2: keep obsolete python3-Sphinx-1.8.5-1.24.noarch
 Solution 3: break python3-Sphinx-doc-man-1.8.5-1.30.noarch by ignoring some of its dependencies

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

Problem: the to be installed pipewire-libjack-0_3-0.3.49-150400.1.5.x86_64 conflicts with 'libjackserver0' provided by the installed libjackserver0-1.9.12-1.33.x86
_64
 Solution 1: Following actions will be done:
  deinstallation of libjackserver0-1.9.12-1.33.x86_64
  deinstallation of libjacknet0-1.9.12-1.33.x86_64
  deinstallation of libjack0-1.9.12-1.33.x86_64
  deinstallation of jack-1.9.12-1.33.x86_64
 Solution 2: deinstallation of pipewire-libjack-0_3-0.3.24-4.3.1.x86_64
 Solution 3: keep obsolete pipewire-libjack-0_3-0.3.24-4.3.1.x86_64

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

Problem: the to be installed libpoppler-devel-22.01.0-150400.1.5.x86_64 requires 'libboost_headers-devel >= 1.58', but this requirement cannot be provided
  not installable providers: libboost_headers1_66_0-devel-1.66.0-12.3.1.x86_64[repo-oss]
 Solution 1: Following actions will be done:
  deinstallation of libboost_headers1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_system1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_numpy-py3-1_75_0-devel-1.75.0-2.6.x86_64
  deinstallation of libboost_program_options1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_regex1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_filesystem1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_date_time1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_chrono1_75_0-devel-1.75.0-2.5.x86_64
 Solution 2: deinstallation of libpoppler-devel-0.79.0-3.5.1.x86_64
 Solution 3: keep obsolete libpoppler-devel-0.79.0-3.5.1.x86_64
 Solution 4: break libpoppler-devel-22.01.0-150400.1.5.x86_64 by ignoring some of its dependencies

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

Problem: the installed libboost_thread1_75_0-devel-1.75.0-2.5.x86_64 requires 'libboost_headers1_75_0-devel = 1.75.0', but this requirement cannot be provided
 Solution 1: Following actions will be done:
  deinstallation of libboost_thread1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_system1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_numpy-py3-1_75_0-devel-1.75.0-2.6.x86_64
  deinstallation of libboost_program_options1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_regex1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_filesystem1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_date_time1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_chrono1_75_0-devel-1.75.0-2.5.x86_64
 Solution 2: deinstallation of libpoppler-glib-devel-0.79.0-3.5.1.x86_64
 Solution 3: keep obsolete libpoppler-glib-devel-0.79.0-3.5.1.x86_64
 Solution 4: break libboost_thread1_75_0-devel-1.75.0-2.5.x86_64 by ignoring some of its dependencies

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

Problem: the installed libpoppler-glib-devel-0.79.0-3.5.1.x86_64 requires 'libpoppler-glib8 = 0.79.0', but this requirement cannot be provided
  deleted providers: libpoppler-glib8-0.79.0-3.5.1.x86_64
 Solution 1: Following actions will be done:
  keep obsolete libpoppler-glib8-0.79.0-3.5.1.x86_64
  keep obsolete typelib-1_0-Poppler-0_18-0.79.0-3.5.1.x86_64
  keep obsolete libpoppler-cpp0-0.79.0-3.5.1.x86_64
 Solution 2: Following actions will be done:
  deinstallation of libboost_test1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_system1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_numpy-py3-1_75_0-devel-1.75.0-2.6.x86_64
  deinstallation of libboost_program_options1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_regex1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_filesystem1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_date_time1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_chrono1_75_0-devel-1.75.0-2.5.x86_64
 Solution 3: deinstallation of libOpenSceneGraph-devel-3.6.5-lp153.60.2.x86_64
 Solution 4: keep obsolete libpoppler-glib8-0.79.0-3.5.1.x86_64
 Solution 5: break libpoppler-glib-devel-0.79.0-3.5.1.x86_64 by ignoring some of its dependencies

**Choose from above solutions by number or skip, retry or cancel [1/2/3/4/5/s/r/c/d/?] (c): **1
Resolving dependencies...
Computing distribution upgrade...
**4 Problems:**
Problem: the to be installed alsa-plugins-jack-1.2.6-150400.1.10.x86_64 requires 'jack', but this requirement cannot be provided
Problem: the installed libboost_test1_75_0-devel-1.75.0-2.5.x86_64 requires 'libboost_headers1_75_0-devel = 1.75.0', but this requirement cannot be provided
Problem: the to be installed libpoppler-devel-22.01.0-150400.1.5.x86_64 requires 'libpoppler-cpp0 = 22.01.0', but this requirement cannot be provided
Problem: the to be installed libpoppler-glib-devel-22.01.0-150400.1.5.x86_64 requires 'libpoppler-glib8 = 22.01.0', but this requirement cannot be provided

Problem: the to be installed alsa-plugins-jack-1.2.6-150400.1.10.x86_64 requires 'jack', but this requirement cannot be provided
 Solution 1: Following actions will be done:
  keep jack-1.9.12-1.33.x86_64
  keep libjacknet0-1.9.12-1.33.x86_64
  keep libjackserver0-1.9.12-1.33.x86_64
 Solution 2: deinstallation of alsa-plugins-jack-1.2.2-1.55.x86_64
 Solution 3: break alsa-plugins-jack-1.2.6-150400.1.10.x86_64 by ignoring some of its dependencies

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

Problem: the installed libboost_test1_75_0-devel-1.75.0-2.5.x86_64 requires 'libboost_headers1_75_0-devel = 1.75.0', but this requirement cannot be provided
 Solution 1: deinstallation of libboost_test1_75_0-devel-1.75.0-2.5.x86_64
 Solution 2: keep libboost_headers1_75_0-devel-1.75.0-2.5.x86_64
 Solution 3: break libboost_test1_75_0-devel-1.75.0-2.5.x86_64 by ignoring some of its dependencies

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

Problem: the to be installed libpoppler-devel-22.01.0-150400.1.5.x86_64 requires 'libpoppler-cpp0 = 22.01.0', but this requirement cannot be provided
  not installable providers: libpoppler-cpp0-22.01.0-150400.1.5.x86_64[repo-oss]
 Solution 1: deinstallation of libpoppler-devel-0.79.0-3.5.1.x86_64
 Solution 2: keep obsolete libpoppler-devel-0.79.0-3.5.1.x86_64
 Solution 3: remove lock to allow removal of libpoppler-cpp0-0.79.0-3.5.1.x86_64
 Solution 4: break libpoppler-devel-22.01.0-150400.1.5.x86_64 by ignoring some of its dependencies

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

Problem: the to be installed libpoppler-glib-devel-22.01.0-150400.1.5.x86_64 requires 'libpoppler-glib8 = 22.01.0', but this requirement cannot be provided
  not installable providers: libpoppler-glib8-22.01.0-150400.1.5.x86_64[repo-oss]
 Solution 1: deinstallation of libpoppler-glib-devel-0.79.0-3.5.1.x86_64
 Solution 2: keep obsolete libpoppler-glib-devel-0.79.0-3.5.1.x86_64
 Solution 3: remove lock to allow removal of libpoppler-glib8-0.79.0-3.5.1.x86_64
 Solution 4: break libpoppler-glib-devel-22.01.0-150400.1.5.x86_64 by ignoring some of its dependencies

**Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c): 1**
Resolving dependencies...
Computing distribution upgrade...
**3 Problems:**

**2 Problems:**

**Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): **c
(base) tom@mydesktop:~>

I had to cut text due to length. thanks, tom kosvic

2

Hi
You need to visit the problem repositories to see if the packages have been built for Leap 15.4…

Not sure where your Sphinx packages are coming from, that is a very old version…

Leap 15.4;


Repository     : Main Repository
Name           : python3-Sphinx
Version        : 2.3.1-150400.1.7
3

I have no records of what packages were installed from each of the OBS repos. Because of that, I ran a thread in this forum to get code to query with zypper each repo to find what is on my system that was installed from that OBS repo and send that to a text file. I can do that. Many items.

I guess then I need to review 15.4 versions of the OBS repos to see what is included there and compare with the generated list files. Then should I delete the packages from my system for which there are no 15.4 OBS equivalent or try to let them be and see if they run? Any opinion??

Additionally, the sphinx files are from the main repo but I have no recollection as to where or what uses them. I deleted them

thanks, tom kosvic

4

Hi
You should be able to query what packages are installed from which repo vi Repository Number…

Yes, but also be aware that some packages have moved to the SLE side (eg the Sphinx packages), but check and delete if required is probably the best plan…

5

Deleting packages from a system in order to upgrade without trouble, with intent to add them back after upgrade success, has no effect on your personal settings for those packages. You won’t lose anything except the time involved removing then adding back those packages, which may well be less than the time you would spend resolving conflict and/or repo issues using zypper or YaST.

6

This is yet another bug in how Leap is assembled. Leap blindly inherits all (at least, many) packages from all previous service packs of SLE15. The doc subpackage no more exists in SLE15 SP4 and should not be part of Leap 15.4 repository.

Problem: the to be installed pipewire-libjack-0_3-0.3.49-150400.1.5.x86_64 conflicts with 'libjackserver0' provided by the installed libjackserver0-1.9.12-1.33.x86_64
 Solution 1: Following actions will be done:
  deinstallation of libjackserver0-1.9.12-1.33.x86_64
  deinstallation of libjacknet0-1.9.12-1.33.x86_64
  deinstallation of libjack0-1.9.12-1.33.x86_64
  deinstallation of jack-1.9.12-1.33.x86_64
 Solution 2: deinstallation of pipewire-libjack-0_3-0.3.24-4.3.1.x86_64
 Solution 3: keep obsolete pipewire-libjack-0_3-0.3.24-4.3.1.x86_64

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

pipewire provides server side functionality and client side emulation for Jack API. It is up to you to decide whether you want to use jack or whether you want to use pipewire. But removing pipewire-libjack will minimize changes to Leap 15.3 (I doubt very much you used pipewire there).

Problem: the to be installed alsa-plugins-jack-1.2.6-150400.1.10.x86_64 requires 'jack', but this requirement cannot be provided
 Solution 1: Following actions will be done:
  keep jack-1.9.12-1.33.x86_64
  keep libjacknet0-1.9.12-1.33.x86_64
  keep libjackserver0-1.9.12-1.33.x86_64
 Solution 2: deinstallation of alsa-plugins-jack-1.2.2-1.55.x86_64
 Solution 3: break alsa-plugins-jack-1.2.6-150400.1.10.x86_64 by ignoring some of its dependencies

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

You do not solve problems by blindly answering “1” to every question. You first told zypper to remove jack, and now you tell zypper to keep jack so you are back on square one. This should be obvious even if you do not know what “jack” is. At least be consistent in what you tell zypper to do.

Problem: the to be installed libpoppler-devel-22.01.0-150400.1.5.x86_64 requires 'libboost_headers-devel >= 1.58', but this requirement cannot be provided  not installable providers: libboost_headers1_66_0-devel-1.66.0-12.3.1.x86_64[repo-oss]
 Solution 1: Following actions will be done:
  deinstallation of libboost_headers1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_system1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_numpy-py3-1_75_0-devel-1.75.0-2.6.x86_64
  deinstallation of libboost_program_options1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_regex1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_filesystem1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_date_time1_75_0-devel-1.75.0-2.5.x86_64
  deinstallation of libboost_chrono1_75_0-devel-1.75.0-2.5.x86_64
 Solution 2: deinstallation of libpoppler-devel-0.79.0-3.5.1.x86_64
 Solution 3: keep obsolete libpoppler-devel-0.79.0-3.5.1.x86_64
 Solution 4: break libpoppler-devel-22.01.0-150400.1.5.x86_64 by ignoring some of its dependencies

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

Do you actually need development packages? Do you compile anything? Do you compile anything that requires poppler development packages?

In any case, I doubt you spent much time configuring any -devel package so just chose 2 and decide later if you actually need it.

There are two versions of boost development packages - 66 and 75 - but version 75 does not provide libboost_headers-devel, so libpoppler-devel tries to install version 66. If some other package requires version 75, you get conflict. I do not know whether these two versions are indeed incompatible or it just boost packaging bug.

Once again - do you really NEED -devel packages in the first place? Even if you do, you are better off removing them in advance and then installing only those packages that you actually need after upgrade.

P.S. Please stop applying fonts to computer text. It makes it far more difficult than necessary to answer normally.

7

Appreciate all the comments. Responses to a few of them below.

I just clicked “1” on all the solution choices just to step through the alternatives to see how many there really were and where it was going. Just for testing

I do compile many apps and use these development packages. I try to compile rather than use binaries in many cases. I guess the dev packages could be added back in later as the need arises. Basically they are mostly only used once.

I only added “bold font” to the beginning of each set of problems denoting number of problems. Other bold text concerned with the choices came from zypper and was pasted there.

A related question, will a compiled package that is installed into root become part of the zypper databases and be upgradeable or will that be lost in an upgrade? I think I will ask this in a separate thread.

thanks all, tom kosvic

8

Update ran successfully. 4900 packages were updated. System reboots and runs. Surprised that there were so many system installs that could be changed to OBS repo installs but all the changes to OBS repo packages went ok. Not yet sure about what I need to reinstall or recompile.

Thanks all for comments and assistance.

tom kosvic

9

No.

[noparse]

[FONT=monospace][/noparse]

This font tag will have rather weird effect when attempting to insert comments at relevant places.

10

It’s easy to make disappear. There’s a button just for the purpose. Left to right across the top button row, it’s #2, with a tiny red X. Select all. Click. Poof. All gone.