In data domenica 5 febbraio 2023 11:49:35 CET, Carlos E. R. ha scritto:
On Sunday, 2023-02-05 at 10:37 +0100, Stakanov wrote:
Problem with zypper dup that sometimes have hick-ups with two conflicting Mesa versions available.
Why is there a MESA version in the packman repos if opensuse provides one too? To be clear I am talking about the Tumbleweed repos.
I recall some graphic card reason, but it is a recall that comes remotely and long time ago. So since this recently caused me some trouble because of shifting repo here and there I wanted to understand. Someone can maybe educate me on this. I do not think that patent rights can be an issue here. I just have to decide which Mesa should I use and I do not have any base for discrimination between the two.
Thank you in advance.
There have been posts about Mesa in the packman mail list recently:
X N 5243 23-01-14 13:15 Nicolas Formichella packman@links2linux (11K) [packman] Mesa-32bit out of sync to Mesa X N 5307 23-01-15 22:04 llyyr packman@links2linux (7456) [packman] [PM] Mesa 22.3.3-338.2 (openSUSE Tumbleweed/x86_64) X N 5343 23-01-16 18:41 mikey packman@links2linux (7461) > [packman] Mesa-32bit X N 5542 23-01-21 20:35 Robert Ahlskog packman@links2linux (6301) [packman] [PM] Mesa-drivers 22.3.3-338.5 (openSUSE Tumbleweed/x86_64) X N 5927 23-01-29 14:19 kit packman@links2linux (6876) [packman] [PM] Mesa-drivers 22.3.4-341.1 (openSUSE Tumbleweed/x86_64) X N 5938 23-01-29 13:57 Bruce Cadieux packman@links2linux (8545) [packman] [PM] Mesa-drivers 22.3.4-341.1 (openSUSE Tumbleweed/x86_64)
<http://lists.links2linux.de/pipermail/packman/>
-- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) In fact the issue comes up when there is a mismatch between the speed certain dependencies are requested, hence first I was asked to "change vendor" so I did, only to find out that the very files then were offered a few days after...requesting "change vendor" again.
Hence the need for discrimination about what to do, since the packages are seemingly(!) the same, but if you dig into that discussion you see, yes the issue is there (as usually). It is a bit sad that even mesa is now hit by this.