There is still an issue that the update want delete the steam package because of a broken dependency.
2 Problems:
Problem: 1: the installed calibre-7.4.0-2.3.x86_64 requires 'libQt6Gui.so.6(Qt_6.7.0_PRIVATE_API)(64bit)', but this requirement cannot be provided
deleted providers: libQt6Gui6-6.7.0-2.2.x86_64
Problem: 2: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided
deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64
Problem: 1: the installed calibre-7.4.0-2.3.x86_64 requires 'libQt6Gui.so.6(Qt_6.7.0_PRIVATE_API)(64bit)', but this requirement cannot be provided
deleted providers: libQt6Gui6-6.7.0-2.2.x86_64
Solution 1: Following actions will be done:
keep obsolete libQt6Gui6-6.7.0-2.2.x86_64
keep obsolete libQt6Core6-6.7.0-2.2.x86_64
keep obsolete libQt6DBus6-6.7.0-2.2.x86_64
keep obsolete libQt6OpenGL6-6.7.0-2.2.x86_64
keep obsolete libQt6Widgets6-6.7.0-2.2.x86_64
Solution 2: deinstallation of calibre-7.4.0-2.3.x86_64
Solution 3: break calibre-7.4.0-2.3.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): 2
Problem: 2: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided
deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64
Solution 1: deinstallation of steam-1.0.0.79-1.4.x86_64
Solution 2: keep obsolete glibc-locale-base-32bit-2.39-7.1.x86_64
Solution 3: break steam-1.0.0.79-1.4.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):
Excellent news about Aeon and the development of an own installer. The last time I installed Aeon it didn't allow automatic user login, is this possible anymore? Thanks
I'm excited for this one. It seems to be the last 15.X release until whatever openSUSE ALP does. I'm probably going to switch my servers to MicroOS, but I'm happy that I get another year or so with 15.6.
Congrats on the hard work everyone! I'm out of town for the release, but I might upgrade my VPN server remotely to join in a little.
A brand new network namespace doesn’t have any network interfaces. When you start a process in a namespace, all its child processes will start there too. It’s like a little network jail, and the functionality is baked into the kernel / is kernel enforced.
I use this to keep certain processes on a vpn, with no need for interface-binding support from the process, or a vpn-killswitch.
Another fun fact, this is the functionality that enables containerization, like docker/podman
openSUSE
Oldest