Hi, again I get some errors/problems when trying to update my Tumbleweed system via zypper dup. That is the initial message:
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...
4 Problems:
Problem: the to be installed python310-jupyter-events-0.6.3-3.1.noarch requires '(python310-jsonschema-format-nongpl >= 3.2.0 with python310-jsonschema-format-nongpl < 4.18)', but this requirement cannot be provided
Problem: the to be installed python310-nbformat-5.9.0-2.1.noarch requires '(python310-jsonschema > 2.6 with python310-jsonschema < 4.18)', but this requirement cannot be provided
Problem: the to be installed python311-jupyter-events-0.6.3-3.1.noarch requires '(python311-jsonschema-format-nongpl >= 3.2.0 with python311-jsonschema-format-nongpl < 4.18)', but this requirement cannot be provided
Problem: the to be installed python311-nbformat-5.9.0-2.1.noarch requires '(python311-jsonschema > 2.6 with python311-jsonschema < 4.18)', but this requirement cannot be provided
Problem: the to be installed python310-jupyter-events-0.6.3-3.1.noarch requires '(python310-jsonschema-format-nongpl >= 3.2.0 with python310-jsonschema-format-nongpl < 4.18)', but this requirement cannot be provided
not installable providers: python310-jsonschema417-format-nongpl-4.17.3-1.1.noarch[repo-oss]
Solution 1: Following actions will be done:
deinstallation of python310-jupyter-events-0.6.3-2.3.noarch
deinstallation of python310-jupyter-server-fileid-0.9.0-1.2.noarch
deinstallation of python310-jupyter-server-2.6.0-1.2.noarch
deinstallation of python310-jupyterlab-4.0.2-1.2.noarch
deinstallation of python310-jupyterlab-server-2.23.0-1.1.noarch
deinstallation of python310-notebook-shim-0.2.3-1.2.noarch
deinstallation of python310-jupyter-lsp-2.2.0-1.2.noarch
deinstallation of python310-nbclassic-1.0.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: deinstallation of python310-jsonschema-format-nongpl-4.18.3-1.1.noarch
Solution 3: keep obsolete python310-jupyter-events-0.6.3-2.3.noarch
Solution 4: break python310-jupyter-events-0.6.3-3.1.noarch by ignoring some of its dependencies
is that something that resolve itself in a while or do i have to do something?
What is the full output from your zypper dup before starting the upgrade? In particular, I’d look to see what says it needs to change repositories (but the full output will generally be helpful).
That’s very odd, because when I run it, I see (for example):
$ sudo zypper dup
[sudo] password for root:
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...
The following item is locked and will not be changed by any action:
Available:
PackageKit
The following 140 packages are going to be upgraded:
alacarte audit autofs bind-utils colord colord-color-profiles cpupower cpupower-bash-completion cryptsetup cryptsetup-doc docker-buildx docker-compose fipscheck freetype2-devel fuse3 google-chrome-stable harfbuzz-devel i2c-tools inkscape
inkscape-extensions-extra inkscape-extensions-gimp iproute2 iproute2-bash-completion kernel-macros krb5 krb5-32bit libaudit1 libauparse0 libblkid1 libblkid1-32bit libblkid-devel libbpf1 libbsd0 libcap-ng0 libcolord2 libcolorhug2 libcpupower0
libcryptsetup12 libfdisk1 libfipscheck1 libfreetype6 libfreetype6-32bit libfuse3-3 libgudev-1_0-0 libharfbuzz0 libharfbuzz0-32bit libharfbuzz-gobject0 libharfbuzz-icu0 libharfbuzz-subset0 libi2c0 libi2c0-devel libmount1 libmount1-32bit libmount-devel
libply5 libply-splash-core5 libply-splash-graphics5 libpoppler-cpp0 libpoppler-glib8 libpskc0 libqpdf29 libreoffice libreoffice-base libreoffice-calc libreoffice-draw libreoffice-filters-optional libreoffice-gnome libreoffice-gtk3
libreoffice-icon-themes libreoffice-impress libreofficekit libreoffice-l10n-en libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-writer libseccomp2 libsmartcols1 libsynctex2 libtomcrypt1 libtpms0 libuuid1 libuuid1-32bit libuuid-devel
libwireshark16 libwiretap13 libwsutil14 libzimg2 MozillaFirefox nvidia-compute-G06 nvidia-compute-G06-32bit nvidia-compute-utils-G06 nvidia-driver-G06-kmp-default nvidia-gl-G06 nvidia-gl-G06-32bit nvidia-utils-G06 nvidia-video-G06
nvidia-video-G06-32bit openSUSE-release openSUSE-release-appliance-custom perl-Cpanel-JSON-XS plymouth plymouth-dracut plymouth-lang plymouth-plugin-label plymouth-plugin-two-step plymouth-scripts plymouth-theme-bgrt plymouth-theme-spinner
poppler-tools python310-black python310-boto3 python310-botocore python310-charset-normalizer python310-docutils python310-importlib-metadata python310-lxml python310-pycodestyle python311-charset-normalizer python311-lxml rpm-config-SUSE smartmontools
sysstat system-group-audit tcsh tcsh-lang telegram-desktop typelib-1_0-HarfBuzz-0_0 util-linux util-linux-systemd util-linux-tty-tools v4l2loopback-autoload v4l2loopback-utils veracrypt veracrypt-lang wireshark wireshark-ui-qt xterm xterm-bin
xterm-resize
The following product is going to be upgraded:
openSUSE Tumbleweed 20230714-0 -> 20230718-0
The following 9 NEW packages are going to be installed:
kernel-default-6.4.3-1.1 kernel-default-devel-6.4.3-1.1 kernel-devel-6.4.3-1.1 kernel-source-6.4.3-1.1 kernel-syms-6.4.3-1.1 libfstrm0 libpoppler130 v4l2loopback-kmp-default-0.12.7_k6.4.3_1-1.44 virtualbox-kmp-default-7.0.8_k6.4.3_1-6.2
The following package is going to be REMOVED:
libpoppler129
The following package requires a system reboot:
kernel-default-6.4.3-1.1
140 packages to upgrade, 9 new, 1 to remove.
Overall download size: 1.14 GiB. Already cached: 0 B. After the operation, additional 1.5 GiB will be used.
Note: System reboot required.
Continue? [y/n/v/...? shows all options] (y):
I don’t have packages that would change repositories, but as I recall, if something was going to change repos, that would be indicated in this summary.
Sounds like you got to a resolution, though, which is perfect.
Yes you are right, those two lines regarding loading repository data and reading installed packages where there too. But no repo change or anything like that.
