03:23:48 user@localhost ~ → sudo zypper dup
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...
2 Problems:
Problem: 1: the to be installed tack-1.11.20251210-911.1.x86_64 requires 'ncurses = 6.6.20260912', but this requirement cannot be provided
not installable providers: libncurses6-6.6.20260912-911.1.i586[Base_System]
libncurses6-6.6.20260912-911.1.x86_64[Base_System]
Problem: 2: the to be installed xz-devel-5.8.4-204.1.x86_64 requires 'liblzma5 = 5.8.4', but this requirement cannot be provided
not installable providers: liblzma5-5.8.4-204.1.i586[Base_System]
liblzma5-5.8.4-204.1.x86_64[Base_System]
Problem: 1: the to be installed tack-1.11.20251210-911.1.x86_64 requires 'ncurses = 6.6.20260912', but this requirement cannot be provided
not installable providers: libncurses6-6.6.20260912-911.1.i586[Base_System]
libncurses6-6.6.20260912-911.1.x86_64[Base_System]
Solution 1: Following actions will be done:
install libncurses6-6.6.20260912-911.1.x86_64 from vendor obs://build.opensuse.org/Base:System
replacing libncurses6-6.6.20260815-111.1.x86_64 from vendor openSUSE
install ncurses-devel-6.6.20260912-911.1.x86_64 from vendor obs://build.opensuse.org/Base:System
replacing ncurses-devel-6.6.20260815-111.1.x86_64 from vendor openSUSE
Solution 2: install tack-1.11.20251210-111.1.x86_64 from vendor openSUSE
replacing tack-1.11.20251210-909.4.x86_64 from vendor obs://build.opensuse.org/Base:System
Solution 3: keep obsolete tack-1.11.20251210-909.4.x86_64
Solution 4: break tack-1.11.20251210-911.1.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):
Please explain what to do, and how to tackle such issues in future by myself
The useful first step is to show us the configured repos zypper lr -u
and examine zypper se -si <package-mentioned-in-error>
You can always test the proposed upgrade first with sudo zypper dup --dry-run
This lets you see what zypper wants to change without actually changing anything.
It’s quite strange that, the not installable items are “.i586” …
Can you please post the output of your system’s “zypper repos --uri”?
The output of “lscpu --hierarchic | head -4” could also be useful.
On this Tumbleweed 20260912 system I’m not seeing your problem:
# LANG=C.UTF-8 zypper install --force --recommends tack
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Forcing installation of 'tack-1.11.20251210-111.1.x86_64' from repository 'repo-oss'.
Resolving package dependencies...
The following package is going to be reinstalled:
tack
1 package to reinstall.
Package download size: 162.5 KiB
Package install size change:
| 218.8 KiB required by packages that will be installed
0 B | - 218.8 KiB released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): n
#
> LANG=C.UTF-8 zypper info --requires tack
Loading repository data...
Reading installed packages...
Information for package tack:
-----------------------------
Repository : repo-oss
Name : tack
Version : 1.11.20251210-111.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 218.8 KiB
Installed : Yes (automatically)
Status : up-to-date
Source package : ncurses-6.6.20260815-111.1.src
Upstream URL : https://www.invisible-island.net/ncurses/ncurses.html
Summary : Terminfo action checker
Description :
This package contains the tack utility to help to build a new terminfo
entry describing an unknown terminal. It can also be used to test the
correctness of an existing entry, and to develop the correct pad
timings needed to ensure that screen updates do not fall behind the
incoming data stream.
Requires : [5]
libtinfo.so.6()(64bit)
libtinfo.so.6(NCURSES6_TINFO_5.0.19991023)(64bit)
libc.so.6(GLIBC_2.42)(64bit)
libtinfo.so.6(NCURSES6_TINFO_5.7.20081102)(64bit)
ncurses = 6.6.20260815
>
@hcvv@OrsoBruno
I added the Base:System repo for some package I installed a couple weeks ago. It’s installation guide redirected me to that repo since the package was unavailable in the default openSUSE repositories.
I’d agree. I have been thinking about getting rid of repos that might be simply eating up space and causing dependency confusions during updates. Perhaps I should make a separate topic for that?
Start Myrlyn. choose from the Views: Repositories.
Choose from the list of repos the one we are curious of and the the right you will see the packages installed from it.
BTW, when you are still using YaST, it has the same feature.
Apparently, every single one of the packages is also available in openSUSE Main Repository. I don’t even know anymore. I don’t know the relevance of this info, but it seems like the versions between the two repos are very different. E.g. powertop x64 package has 2.16-2.1 in openSUSE repo but in Base_System repo, it is of version 2.16-99.4. Have a look for yourself:
Those are the 3 packages you manually installed from the Base:System repo, the others are likely dependencies.
I see no real reason to prefer those versions, unless you are debugging one of those packages.
Consider disabling or removing that repo since it is going to cause conflicts as you can see and then performing a zypper dup --from download.opensuse.org-oss --allow-vendor change.
As a side note be aware that generally speaking having both Packman and VLC repos enabled is asking for trouble, so you might be better off disabling one or the other, or at least set priorities carefully to avoid packages from those two repos when not really needed.
Consider disabling or removing that repo since it is going to cause conflicts as you can see and then performing a zypper dup --from download.opensuse.org-oss --allow-vendor change .
Thanks. I’ll look into getting rid of it right away.
As a side note be aware that generally speaking having both Packman and VLC repos enabled is asking for trouble, so you might be better off disabling one or the other, or at least set priorities carefully to avoid packages from those two repos when not really needed.
I added the VLC repo as I was planning to switch away from Packman. Although I’ve put the switching on halt temporarily, as I think that it is still too early. I’ll disable VLC for the meantime.
