I have been trying to ‘zypper dup’ and am getting a large number of dependency errors stating that packages cannot be provided. I could not find anything in forums or internet search that made sense.
i then re-ran the sudo zypper dist-upgrade --allow-vendor-change --allow-downgrade --from "packman" and it appears to be running the distribution update.
Why is this? Do I need to issue the dis-upgrade -allow-vendor-change every time and prior to the zypper dup?
TasP
Whithout that you showed us your repos including priorities, and without any console output from “failed” upgrade…how should anybody be able to tell you reasons for that?
If I had added the PackMan repo (for codecs and multimedia), and had already issued the ‘—allow-vendor-change” why would a future zypper dup fail with non-resolvable dependencies.
I have seen this issue reported multiple times, but without an answer.
Re-issuing —allow_vendor-change and —allow-downgrade from packman, and by the way running zypper dup twice, seems to have fixed the issue, until I do more multimedia testing.
The only thing I can think of, is, I read on one of the forums I could run zypper up…. I think I may have…. Can anyone think if that would cause it?
Also, if more information is required, what would it be?
TasP
See my last comment. Repo list with URL and a log of failed zypper dup.
If you failed to set higher priorities to the packman repo (as described in the SDB:Installing_codecs_from_Packman_repositories) something like what you describe can happen…
@70tas As asked by @hui show some output, I suspect the Mesa update as that looks like it failed on the drivers… Show Essentials / A_tw-Mesa - Packman Build Service PMBS
You may be a magician…
Here are the last few updates I tried:
twkde:/home/papadopoulosa # sudo zypper dist-upgrade --allow-vendor-change
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…
Nothing to do.
twkde:/home/papadopoulosa # zypper in vlc
Loading repository data…
Reading installed packages…
‘vlc’ is already installed.
There is an update candidate for ‘vlc’ from vendor ‘obs://build.opensuse.org/multimedia’, while the current vendor is ‘http://packman.links2linux.de’. Use ‘zypper install vlc-3.0.18-338.6.x86_64’ to install this candidate.
There is an update candidate for ‘vlc’, but it comes from a repository with a lower priority. Use ‘zypper install vlc-3.0.18-338.6.x86_64’ to install this candidate.
Resolving package dependencies…
Nothing to do.
twkde:/home/papadopoulosa # sudo zypper dup --from packman --allow-vendor-change
Loading repository data…
Reading installed packages…
Computing distribution upgrade…
3 Problems:
Problem: nothing provides ‘Mesa-dri = 22.3.4’ needed by the to be installed Mesa-22.3.4-341.1.x86_64
Problem: nothing provides ‘Mesa-dri = 22.3.4’ needed by the to be installed Mesa-22.3.4-341.1.x86_64
Problem: nothing provides ‘Mesa-dri = 22.3.4’ needed by the to be installed Mesa-22.3.4-341.1.x86_64
Problem: nothing provides ‘Mesa-dri = 22.3.4’ needed by the to be installed Mesa-22.3.4-341.1.x86_64
Solution 1: Following actions will be done:
deinstallation of Mesa-22.3.3-339.1.x86_64
deinstallation of xorg-x11-server-21.1.6-2.1.x86_64
deinstallation of xorg-x11-server-Xvfb-21.1.6-2.1.x86_64
deinstallation of patterns-base-x11-20200505-38.1.x86_64
deinstallation of xf86-input-evdev-2.10.6-3.9.x86_64
deinstallation of xf86-input-joystick-1.6.4-1.1.x86_64
deinstallation of xf86-input-libinput-1.2.1-1.4.x86_64
deinstallation of xf86-input-vmmouse-13.2.0-1.1.x86_64
deinstallation of xf86-input-wacom-0.40.0-2.5.x86_64
deinstallation of xf86-video-fbdev-0.5.0-3.3.x86_64
deinstallation of xf86-video-vesa-2.6.0-1.1.x86_64
deinstallation of xf86-video-vmware-13.3.0+12-2.3.x86_64
deinstallation of xorg-x11-driver-video-7.6_1-19.9.x86_64
deinstallation of xf86-input-keyboard-1.9.0-2.7.x86_64
deinstallation of python310-opengl-3.1.6-1.4.noarch
downgrade of libglvnd-1.6.0-1.1.x86_64 to libglvnd-1.4.0-4.2.x86_64
deinstallation of xorgxrdp-0.9.19-1.1.x86_64
deinstallation of plasma5-session-wayland-5.26.5-1.3.x86_64
deinstallation of kcm_tablet-3.2.0-5.5.x86_64
deinstallation of python310-opengl-accelerate-3.1.6-1.4.x86_64
deinstallation of vidcutter-6.0.5.1-27.17.x86_64
deinstallation of patterns-kde-kde_plasma-20221001-1.1.noarch
deinstallation of patterns-games-games-20220126-1.4.x86_64
deinstallation of patterns-base-x11_enhanced-20200505-38.1.x86_64
deinstallation of patterns-kde-kde-20221001-1.1.noarch
Solution 2: install Mesa-22.3.3-340.1.i586 despite the inferior architecture
Solution 3: keep obsolete Mesa-22.3.3-339.1.x86_64
Solution 4: break Mesa-22.3.4-341.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): ^Ctwkde:/home/papadopoulosa # sudo zypper dup --from packman --allow-vendor-change
Retrieving repository ‘Main Repository (NON-OSS)’ metadata …[done]
Retrieving repository ‘Main Repository (OSS)’ metadata …[done]
Retrieving repository ‘multimedia:apps’ metadata …[done]
Retrieving repository ‘openSUSE:Tumbleweed’ metadata …[done]
Loading repository data…
Reading installed packages…
Computing distribution upgrade…
2 Problems:
Problem: the to be installed Mesa-22.3.4-341.1.x86_64 requires ‘Mesa-dri = 22.3.4’, but this requirement cannot be provided
Problem: the to be installed Mesa-libGL1-22.3.4-341.1.x86_64 requires ‘Mesa = 22.3.4’, but this requirement cannot be provided
Problem: the to be installed Mesa-22.3.4-341.1.x86_64 requires ‘Mesa-dri = 22.3.4’, but this requirement cannot be provided
not installable providers: Mesa-dri-22.3.4-340.1.i586[download.opensuse.org-oss]
Mesa-dri-22.3.4-340.1.x86_64[download.opensuse.org-oss]
Mesa-dri-22.3.4-340.1.i586[https-download.opensuse.org-6a18dd4d]
Mesa-dri-22.3.4-340.1.x86_64[https-download.opensuse.org-6a18dd4d]
Mesa-dri-22.3.4-341.1.i586[packman]
Solution 1: Following actions will be done:
keep obsolete Mesa-22.3.3-339.1.x86_64
keep obsolete Mesa-libEGL1-22.3.3-339.1.x86_64
Solution 2: Following actions will be done:
deinstallation of Mesa-22.3.3-339.1.x86_64
deinstallation of Mesa-dri-22.3.3-340.1.x86_64
deinstallation of Mesa-gallium-22.3.3-340.1.x86_64
deinstallation of xorg-x11-server-21.1.6-2.1.x86_64
deinstallation of xorg-x11-server-Xvfb-21.1.6-2.1.x86_64
deinstallation of xorg-x11-server-extra-21.1.6-2.1.x86_64
deinstallation of python310-opengl-3.1.6-1.4.noarch
downgrade of libglvnd-1.6.0-1.1.x86_64 to libglvnd-1.4.0-4.2.x86_64
deinstallation of xf86-input-evdev-2.10.6-3.9.x86_64
deinstallation of xf86-input-joystick-1.6.4-1.1.x86_64
deinstallation of xf86-input-libinput-1.2.1-1.4.x86_64
deinstallation of xf86-input-vmmouse-13.2.0-1.1.x86_64
deinstallation of xf86-input-wacom-0.40.0-2.5.x86_64
deinstallation of xf86-video-fbdev-0.5.0-3.3.x86_64
deinstallation of xf86-video-vesa-2.6.0-1.1.x86_64
deinstallation of xf86-video-vmware-13.3.0+12-2.3.x86_64
deinstallation of xorg-x11-driver-video-7.6_1-19.9.x86_64
deinstallation of xf86-input-keyboard-1.9.0-2.7.x86_64
deinstallation of xorgxrdp-0.9.19-1.1.x86_64
deinstallation of python310-opengl-accelerate-3.1.6-1.4.x86_64
deinstallation of vidcutter-6.0.5.1-27.17.x86_64
deinstallation of plasma5-session-wayland-5.26.5-1.3.x86_64
deinstallation of kcm_tablet-3.2.0-5.5.x86_64
deinstallation of patterns-kde-kde_plasma-20221001-1.1.noarch
deinstallation of patterns-games-games-20220126-1.4.x86_64
deinstallation of patterns-base-x11_enhanced-20200505-38.1.x86_64
deinstallation of patterns-kde-kde-20221001-1.1.noarch
Solution 3: install Mesa-dri-22.3.4-341.1.i586 despite the inferior architecture
Solution 4: install Mesa-dri-22.3.4-340.1.x86_64 from excluded repository
Solution 5: break Mesa-22.3.4-341.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): 3
Problem: the to be installed Mesa-libGL1-22.3.4-341.1.x86_64 requires ‘Mesa = 22.3.4’, but this requirement cannot be provided
not installable providers: Mesa-22.3.4-340.1.i586[download.opensuse.org-oss]
Mesa-22.3.4-340.1.x86_64[download.opensuse.org-oss]
Mesa-22.3.4-340.1.i586[https-download.opensuse.org-6a18dd4d]
Mesa-22.3.4-340.1.x86_64[https-download.opensuse.org-6a18dd4d]
Mesa-22.3.4-341.1.i586[packman]
Mesa-22.3.4-341.1.x86_64[packman]
Solution 1: Following actions will be done:
deinstallation of Mesa-libGL1-22.3.3-339.1.x86_64
deinstallation of xorg-x11-server-Xvfb-21.1.6-2.1.x86_64
deinstallation of xorg-x11-server-extra-21.1.6-2.1.x86_64
deinstallation of Mesa-dri-22.3.3-340.1.x86_64
deinstallation of Mesa-gallium-22.3.3-340.1.x86_64
deinstallation of xf86-input-evdev-2.10.6-3.9.x86_64
deinstallation of xf86-input-joystick-1.6.4-1.1.x86_64
deinstallation of xf86-input-libinput-1.2.1-1.4.x86_64
deinstallation of xf86-input-vmmouse-13.2.0-1.1.x86_64
deinstallation of xf86-input-wacom-0.40.0-2.5.x86_64
deinstallation of xf86-video-fbdev-0.5.0-3.3.x86_64
deinstallation of xf86-video-vesa-2.6.0-1.1.x86_64
deinstallation of xf86-video-vmware-13.3.0+12-2.3.x86_64
deinstallation of xorg-x11-driver-video-7.6_1-19.9.x86_64
deinstallation of xf86-input-keyboard-1.9.0-2.7.x86_64
deinstallation of xorgxrdp-0.9.19-1.1.x86_64
downgrade of libglvnd-1.6.0-1.1.x86_64 to libglvnd-1.4.0-4.2.x86_64
deinstallation of python310-opengl-3.1.6-1.4.noarch
deinstallation of plasma5-session-wayland-5.26.5-1.3.x86_64
deinstallation of kcm_tablet-3.2.0-5.5.x86_64
deinstallation of patterns-kde-kde_plasma-20221001-1.1.noarch
deinstallation of patterns-games-games-20220126-1.4.x86_64
deinstallation of patterns-base-x11_enhanced-20200505-38.1.x86_64
deinstallation of python310-opengl-accelerate-3.1.6-1.4.x86_64
deinstallation of vidcutter-6.0.5.1-27.17.x86_64
deinstallation of patterns-kde-kde-20221001-1.1.noarch
Solution 2: install Mesa-gallium-22.3.4-341.1.i586 despite the inferior architecture
Solution 3: install Mesa-gallium-22.3.4-340.1.x86_64 from excluded repository
Solution 4: keep obsolete Mesa-libGL1-22.3.3-339.1.x86_64
Solution 5: break Mesa-libGL1-22.3.4-341.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): 3
Resolving dependencies…
Computing distribution upgrade…
The following 8 packages are going to be upgraded:
Mesa Mesa-dri Mesa-gallium Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0-32bit libOSMesa8-32bit pipewire-aptx
The following package is going to change architecture:
Mesa-dri x86_64 → i586
The following 4 packages are going to change vendor:
Mesa openSUSE → http://packman.links2linux.de
Mesa-gallium http://packman.links2linux.de → openSUSE
Mesa-libEGL1 openSUSE → http://packman.links2linux.de
Mesa-libGL1 openSUSE → http://packman.links2linux.de
The following 10 NEW packages are going to be installed:
libLLVM15-32bit libdrm2-32bit libdrm_amdgpu1-32bit libdrm_intel1-32bit libdrm_nouveau2-32bit libdrm_radeon1-32bit libedit0-32bit libncurses6-32bit libpciaccess0-32bit
libxcb-dri3-0-32bit
8 packages to upgrade, 10 new, 4 to change vendor, 1 to change arch.
Overall download size: 49.1 MiB. Already cached: 0 B. After the operation, additional 121.5 MiB will be used.
Continue? [y/n/v/…? shows all options] (y):
Retrieving: libdrm2-32bit-2.4.114-3.1.x86_64 (Main Repository (OSS)) (1/18), 55.7 KiB
Retrieving: libdrm2-32bit-2.4.114-3.1.x86_64.rpm …[done (253.6 KiB/s)]
Retrieving: libncurses6-32bit-6.4.20230114-2.2.x86_64 (Main Repository (OSS)) (2/18), 467.3 KiB
Retrieving: libncurses6-32bit-6.4.20230114-2.2.x86_64.rpm …[done (1.0 MiB/s)]
Retrieving: libpciaccess0-32bit-0.17-1.1.x86_64 (Main Repository (OSS)) (3/18), 29.8 KiB
Retrieving: libpciaccess0-32bit-0.17-1.1.x86_64.rpm …[done (22.7 KiB/s)]
Retrieving: libxcb-dri3-0-32bit-1.15-2.1.x86_64 (Main Repository (OSS)) (4/18), 15.1 KiB
Retrieving: libxcb-dri3-0-32bit-1.15-2.1.x86_64.rpm …[done (2.5 KiB/s)]
Retrieving: libdrm_radeon1-32bit-2.4.114-3.1.x86_64 (Main Repository (OSS)) (5/18), 37.0 KiB
Retrieving: libdrm_radeon1-32bit-2.4.114-3.1.x86_64.rpm …[done (342.7 KiB/s)]
Retrieving: libdrm_nouveau2-32bit-2.4.114-3.1.x86_64 (Main Repository (OSS)) (6/18), 34.2 KiB
Retrieving: libdrm_nouveau2-32bit-2.4.114-3.1.x86_64.rpm …[done (114.5 KiB/s)]
Retrieving: libdrm_amdgpu1-32bit-2.4.114-3.1.x86_64 (Main Repository (OSS)) (7/18), 38.2 KiB
Retrieving: libdrm_amdgpu1-32bit-2.4.114-3.1.x86_64.rpm …[done (231.5 KiB/s)]
Retrieving: libedit0-32bit-20210910.3.1-1.11.x86_64 (Main Repository (OSS)) (8/18), 95.2 KiB
Retrieving: libedit0-32bit-20210910.3.1-1.11.x86_64.rpm …[done (293.1 KiB/s)]
Retrieving: libdrm_intel1-32bit-2.4.114-3.1.x86_64 (Main Repository (OSS)) (9/18), 84.7 KiB
Retrieving: libdrm_intel1-32bit-2.4.114-3.1.x86_64.rpm …[done (10.2 KiB/s)]
Retrieving: libLLVM15-32bit-15.0.7-1.1.x86_64 (Main Repository (OSS)) (10/18), 27.6 MiB
Retrieving: libLLVM15-32bit-15.0.7-1.1.x86_64.rpm …[done (4.6 MiB/s)]
Retrieving: pipewire-aptx-0.3.65-1.1.x86_64 (Packman) (11/18), 23.5 KiB
Retrieving: pipewire-aptx-0.3.65-1.1.x86_64.rpm …[done (15.6 KiB/s)]
Retrieving: Mesa-libglapi0-32bit-22.3.4-341.1.x86_64 (Packman) (12/18), 67.5 KiB
Retrieving: Mesa-libglapi0-32bit-22.3.4-341.1.x86_64.rpm …[done (31.6 KiB/s)]
Retrieving: Mesa-libEGL1-22.3.4-341.1.x86_64 (Packman) (13/18), 165.9 KiB
Retrieving: Mesa-libEGL1-22.3.4-341.1.x86_64.rpm …[done (95.6 KiB/s)]
Retrieving: libOSMesa8-32bit-22.3.4-341.1.x86_64 (Packman) (14/18), 2.8 MiB
Retrieving: libOSMesa8-32bit-22.3.4-341.1.x86_64.rpm …[done (2.2 MiB/s)]
Retrieving: Mesa-gallium-22.3.4-340.1.x86_64 (Main Repository (OSS)) (15/18), 9.5 MiB
Retrieving: Mesa-gallium-22.3.4-340.1.x86_64.rpm …[done (3.4 MiB/s)]
Retrieving: Mesa-dri-22.3.4-341.1.i586 (Packman) (16/18), 7.9 MiB
Retrieving: Mesa-dri-22.3.4-341.1.i586.rpm …[done (6.4 MiB/s)]
Retrieving: Mesa-libGL1-22.3.4-341.1.x86_64 (Packman) (17/18), 204.5 KiB
Retrieving: Mesa-libGL1-22.3.4-341.1.x86_64.rpm …[done]
Retrieving: Mesa-22.3.4-341.1.x86_64 (Packman) (18/18), 60.2 KiB
Retrieving: Mesa-22.3.4-341.1.x86_64.rpm …[done]
Checking for file conflicts: …[done]
( 1/18) Installing: libdrm2-32bit-2.4.114-3.1.x86_64 …[done]
( 2/18) Installing: libncurses6-32bit-6.4.20230114-2.2.x86_64 …[done]
( 3/18) Installing: libpciaccess0-32bit-0.17-1.1.x86_64 …[done]
( 4/18) Installing: libxcb-dri3-0-32bit-1.15-2.1.x86_64 …[done]
( 5/18) Installing: libdrm_radeon1-32bit-2.4.114-3.1.x86_64 …[done]
( 6/18) Installing: libdrm_nouveau2-32bit-2.4.114-3.1.x86_64 …[done]
( 7/18) Installing: libdrm_amdgpu1-32bit-2.4.114-3.1.x86_64 …[done]
( 8/18) Installing: libedit0-32bit-20210910.3.1-1.11.x86_64 …[done]
( 9/18) Installing: libdrm_intel1-32bit-2.4.114-3.1.x86_64 …[done]
(10/18) Installing: libLLVM15-32bit-15.0.7-1.1.x86_64 …[done]
(11/18) Installing: pipewire-aptx-0.3.65-1.1.x86_64 …[done]
(12/18) Installing: Mesa-libglapi0-32bit-22.3.4-341.1.x86_64 …[done]
(13/18) Installing: Mesa-libEGL1-22.3.4-341.1.x86_64 …[done]
(14/18) Installing: libOSMesa8-32bit-22.3.4-341.1.x86_64 …[done]
(15/18) Installing: Mesa-gallium-22.3.4-340.1.x86_64 …[done]
(16/18) Installing: Mesa-dri-22.3.4-341.1.i586 …[done]
(17/18) Installing: Mesa-libGL1-22.3.4-341.1.x86_64 …[done]
(18/18) Installing: Mesa-22.3.4-341.1.x86_64 …[done]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run ‘zypper ps -s’ to list these programs.
Nice mess…
As Tumbleweed user it is advised to follow factory Mailing list, forums and channels for additional repos.
You could have found already by searching the forum, that Mesa atm fails building on packman repo. The same applies for VLC on packman repo.
And you didn’t chose that wisely when you got asked for solution by zypper…so now you have a nice mess…
So every user is supposed to go searching instead of depending on the dependencies within the update tool?
Yes it is a nice mess…
@70tas don’t use third party repositories… rebuild the mesa drivers locally… both options work 
Remember the openSUSE project has no control of what happens outside of the project, not sure what your expectations are?
Well, like other users, I am more concerned on having a stable system than trying to figure out the inner workings. I understand why OpenSUSE took out the codecs; but there has to be some documentation on how to add them back in. I did what someone suggested, by using Packman…
No one suggested I not use it, and I’m not sure where and how to build MESA.
I love OSS when it is working… but it is painful when it is not, and especially with losing LEAP.
@70tas not sure what you mean about loosing Leap, still a few more years to go… Have you looked at MicroOS, aside from a transactional system (and running tumbleweed, so lots of updates at present), flatpaks come bundled with everything needed for an end user.
When I read about it going away, I went Tumbleweed. But as far as codecs are concerned, I’m sure I’d end up in the same ‘fine mess’ I am today.
So I am trying to read up on your suggestion about MicroOS, but I am not sure what that would buy me. I’d still need my DE, and applications. I’ve checked the Wiki, but I can’t see a whole lot of information on it. What exactly will it do for the end user?
Tas
@70tas most of the flatpaks pull in required things to run, like patented encumbered items…
At present flathub is used, but going forward as far as I know rpms and flatpaks will be built/distributed…
So I have a test setup here;
flatpak list
Name Application ID Version Branch Installation
Flatseal com.github.tchx84.Flatseal 1.8.1 stable user
Extension Manager com.mattjakeman.ExtensionManager 0.4.0 stable user
VSCodium com.vscodium.codium 1.74.3.23010 stable user
Freedesktop Platform org.freedesktop.Platform 22.08.5 22.08 user
Mesa org.freedesktop.Platform.GL.default 21.3.9 21.08 user
Mesa org.freedesktop.Platform.GL.default 22.3.2 22.08 user
Mesa (Extra) org.freedesktop.Platform.GL.default 22.3.2 22.08-extra user
Intel org.freedesktop.Platform.VAAPI.Intel 21.08 user
Intel org.freedesktop.Platform.VAAPI.Intel 22.08 user
Freedesktop SDK org.freedesktop.Sdk 22.08.5 22.08 user
Calculator org.gnome.Calculator 43.0.1 stable user
Web org.gnome.Epiphany 43.0 stable user
GNOME Application Platform version 43 org.gnome.Platform 43 user
Text Editor org.gnome.TextEditor 43.1 stable user
KDE Application Platform org.kde.Platform 5.15-22.08 user
KDE Application Platform org.kde.Platform 6.3 user
Strawberry Music Player org.strawberrymusicplayer.strawberry 1.0.0 stable user
I usually when I see there is a lot of dependencies , I cancel the upgrade and wait a few days , usually they get fixed .
Third option, available for Intel or NVIDIA GPU users: keep using Mesa from official OSS repository, as the Mesa from Packman enables features for AMD GPU users.
I’d also recommend flatpaks for most users as well… codecs from additional repos are more likely to require maintenance.
Just to recap, my boxes are all VMs running on AMD GPU.
2. I’ve waited two weeks, no love.
3. Parkman is recommended on the wiki and subject matter pages
4. I am not going to microOS and flatpaks at this time.
Which leaves me with either a forced update or a rebuild.
I am running a forced update now, we’ll see. But I have another point to make. I am a die hard OSS devotee. But I see a lot of users, many of which I’ve recommended go with OSS, who have these kind of of issues.
What can we do to make Tumbleweed a more mainstream and more robust environment. I am willing to help, but microOS and flatpaks are not the answer, yet. To paraphrase, teach me how to fish and I can eat, and teach others as well.
TasP
That’s unusually long, but I don’t use Mesa from packman.
Must have been another wiki. Ours states explicitly on third-party repositories “no guarantee”, “not supported”, “may not be tested”, and recommends the official repos.
If you can share the pages that recommend packman it would be appreciated – they must be fixed.
Flatpak is not exclusive to MicroOS, many use them on TW.
Force updates are not a reasonable option if you prioritize stability.
Flatpaks avoids many issues originating from third-party repos, and is FOSS. It’s just a different distribution model.
Packman might use a hand to catch and fixes those issues sooner. Also, if you find any issues with the alternative model flatpaks, also help solving them. Hopefully you understand the issue arises from distributing binaries, you can also help rebuilding packages locally.
@70tas wait a bit more the system was only fixed a few hours ago, it’s just finished building, another couple of hours and should be good to go.
