Python troubles on update - TW

English Install/Boot/Login
1

I’m updating my system and I’m getting the usual python problems (should have listened to those who cleaned up their python installs).

4 Problems:
Problem: problem with the installed libopencore-amrnb0-0.1.6-1699.1.pm.9.x86_64
Problem: problem with the installed libopencore-amrwb0-0.1.6-1699.1.pm.9.x86_64
Problem: the to be installed python310-jupyter-events-0.6.3-4.1.noarch requires 'python310-jsonschema-format-nongpl >= 4.18', but this requirement cannot be provided
Problem: the to be installed python311-jupyter-events-0.6.3-4.1.noarch requires 'python311-jsonschema-format-nongpl >= 4.18', but this requirement cannot be provided

Problem: problem with the installed libopencore-amrnb0-0.1.6-1699.1.pm.9.x86_64
 Solution 1: install libopencore-amrnb0-0.1.6-1.3.x86_64 from vendor openSUSE
  replacing libopencore-amrnb0-0.1.6-1699.1.pm.9.x86_64 from vendor http://packman.links2linux.de
 Solution 2: keep obsolete libopencore-amrnb0-0.1.6-1699.1.pm.9.x86_64

Select 1.

Then:

Problem: problem with the installed libopencore-amrwb0-0.1.6-1699.1.pm.9.x86_64
 Solution 1: install libopencore-amrwb0-0.1.6-1.3.x86_64 from vendor openSUSE
  replacing libopencore-amrwb0-0.1.6-1699.1.pm.9.x86_64 from vendor http://packman.links2linux.de
 Solution 2: keep obsolete libopencore-amrwb0-0.1.6-1699.1.pm.9.x86_64

Select 1.

Then:

Problem: the to be installed python310-jupyter-events-0.6.3-4.1.noarch requires 'python310-jsonschema-format-nongpl >= 4.18', but this requirement cannot be provided
  not installable providers: python310-jsonschema-format-nongpl-4.18.4-1.1.noarch[download.opensuse.org-oss]
 Solution 1: Following actions will be done:
  deinstallation of python310-jupyter-events-0.6.3-3.1.noarch
  deinstallation of python310-jupyter-server-fileid-0.9.0-1.2.noarch
  deinstallation of python310-notebook-shim-0.2.3-1.2.noarch
  deinstallation of python310-jupyterlab-4.0.2-1.2.noarch
  deinstallation of python310-jupyter-lsp-2.2.0-1.2.noarch
  deinstallation of python310-notebook-6.5.4-1.2.noarch
  deinstallation of python310-jupyter-1.0.0-12.2.noarch
 Solution 2: Following actions will be done:
  deinstallation of python310-jsonschema417-format-nongpl-4.17.3-1.1.noarch
  deinstallation of python310-jsonschema417-4.17.3-1.1.noarch
  deinstallation of python310-nbformat-5.9.0-2.1.noarch
  deinstallation of python310-nbconvert-7.6.0-1.1.noarch
  deinstallation of python310-nbclient-0.8.0-1.2.noarch
  deinstallation of python310-notebook-6.5.4-1.2.noarch
  deinstallation of python310-jupyter-1.0.0-12.2.noarch
  deinstallation of python310-notebook-shim-0.2.3-1.2.noarch
  deinstallation of python310-jupyterlab-4.0.2-1.2.noarch
  deinstallation of python310-jupyter-server-fileid-0.9.0-1.2.noarch
  deinstallation of python310-jupyter-lsp-2.2.0-1.2.noarch
 Solution 3: keep obsolete python310-jupyter-events-0.6.3-3.1.noarch
 Solution 4: break python310-jupyter-events-0.6.3-4.1.noarch by ignoring some of its dependencies

Afterwards a series of “problems” to select from.

Just skip all the python stuff? If I don’t, it will remove Jupyter and will not let me reinstall it. I don’t use it, but as soon as it’s not available, I’ll need it.

I already selected de-install on the remaining issues with Jupyter but python wouldn’t work at all afterwards so I did a system rollback.

This is all on a fresh install from last week with only one update between then and now. All I’ve done on this machine is work on some C projects with a terminal and a browser. I’m pretty sure I didn’t mess it up - this time.

2

I would use Solution 2 because the Update wants python310-jsonschema-format-nongpl-4.18.4-1.1 and therfore I would delete python310-jsonschema417-format-nongpl-4.17.3-1.1

But post also:
zypper lr -d

3

OK, thanks.

# | Alias                            | Name                                   | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                  | Service
--+----------------------------------+----------------------------------------+---------+-----------+---------+----------+--------+----------------------------------------------------------------------+--------
1 | code                             | Visual Studio Code                     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://packages.microsoft.com/yumrepos/vscode                       | 
2 | download.opensuse.org-non-oss    | Main Repository (NON-OSS)              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/                | 
3 | download.opensuse.org-oss        | Main Repository (OSS)                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/                    | 
4 | download.opensuse.org-tumbleweed | Main Update Repository                 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/                      | 
5 | packman                          | Packman                                | Yes     | (r ) Yes  | Yes     |   90     | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ | 
6 | repo-debug                       | openSUSE-Tumbleweed-Debug              | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/              | 
7 | repo-openh264                    | Open H.264 Codec (openSUSE Tumbleweed) | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed              | 
8 | repo-source                      | openSUSE-Tumbleweed-Source             | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/             | 
9 | skype-stable                     | skype (stable)                         | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://repo.skype.com/rpm/stable/
4

Your Repo list is ok.

5

Error after error after error. I reinstalled TW (again). I say this almost flippantly, but I think it’s more practical to reinstall TW once a month instead of dealing with all of the errors on zypper dup. It only takes 20 mins to get up and running. Problem solving always takes longer. Must be my hardware/network because I know many of you here have very few problems. I have an update problem at least every two weeks.

I think it’s time for me to divorce susie. She doesn’t like me and has slapped me in the face one too many times. Thanks for all of your help everyone here.

6

It’s rare I have conflicts on the two TW desktops and two TW laptops. It’s all about configuration (my opinion, of course).

Rolling distro’s aren’t for everyone’s use case. You should consider Leap or maybe MicroOS Aeon / Kalpa.

7

FWIW, I encounter these often as there’s an overlap between the Packman and openSUSE repos/packages.

My rule is to zypper dup only if the Main repos have had changes after a zypper ref, otherwise it’s a constant juggle between the two vendors.

8

Honestly I recommend everyone on TW who wants to use a fixed version of python to use pyenv and also get familiar with update-alternatives. Especially in the OP’s case, you can lock your python version to within pyenv then use pip of respective python evironment to install things like jupyter and so far I haven’t had any serious conflicts.

9

That’s interesting. Please tell me more about your process (if you wouldn’t mind).

Ironically, I rarely use python. But I want it to be available for the day I do need it. Great suggestion.

Susie, “I just can’t quit you…”

10

By the way; can I not just skip over the python flubs?

11

A couple of other things I should have put in my last post:

Should I simply wait to update when things iron themselves out in the repos? Also, is there a way to avoid using Packman altogether and still have a usable media enabled system?

12

I’m having the same issue on dup.

These errors are confusing for me, because if I answer 1 (which to me seems like it’s updating to a newer version because it says option 2 is the obsolete one) - then when I get to the summary it says that those packages will be downgraded.

So really I just don’t know what’s going on. So I choose to do nothing and wait a week. Retry zypper dup. This almost always solves these types of issues.

13

It’s unclear to me what a “usable media system” is … what exactly constitutes that?

14

Play a video if I need to (which is rare).

15

Good advice - just be patient. Hard on a rolling release, a doddle on Debian. The irony…

16

So, after a fresh install the python 2.7 terminal app is gone, as are the 3.10 and the jupyter whatevers -which I wanted anyway. But, you cannot install Jupyter notbook or anything related to Jupyter. Bit silly - lots of p-devs out there using notebooks.

17

I thought I was having a bout with déjà-vu, but I remembered this from not long ago:

Maybe a clean-up is in order (?)

18

I did as you did. I think Calibre dependencies were also causing all kinds of problems - removed that and manually installed it. No issues accept I still can’t install jupyter notebooks using zypper (of course I can use containers - or even VS Code, but I don’t need too). The things we fret about, eh?

Thanks for the reminder of that older post @aggie.

1 Like
19

You know, you nailed it @aggie. I just removed my manually installed Calbre and boom, jupyter notbooks can now be installed as well as all the other issues have gone. :+1:

1 Like
20

To wrap this up:

As of 7/31, the installer no longer installs Jupyter and the Python 3.10 & 3.11 QT Consoles by default. Good things!