New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/53434#issuecomment-2648187246

Comment:
> > Was wondering what was causing us to be so far behind on Mesa updates!
> > 
> > Looks like description links 3 mesa reports as segfaults in 24.3.1:
> > 
> > https://gitlab.freedesktop.org/mesa/mesa/-/issues/12253 (Segfault on AMD Polaris)
> > 
> > The issue that has reports by Void users, reported as fixed in 24.3.2, seems to be corroborated by Void users that have done the testing.
> > 
> > https://gitlab.freedesktop.org/mesa/mesa/-/issues/12275 (Segfault on Nvidia Quadro)
> > 
> > Isn't a segfault. Report indicates the user had segfaults in 24.2.7, but those went away in 24.3.1 and instead has different issue.
> > 
> > https://gitlab.freedesktop.org/mesa/mesa/-/issues/12283 (Segfault with Gnome-Shell on Intel Integrated Graphics)
> > 
> > Lodged against the 25.0.0-devel branch of mesa, not an actual release branch.
> > 
> > Since this issue is actually just one specific crash type that has been fixed for a while, could we get Mesa updates back on track?
> 
> We were in fact awaiting for testing by the userbase. When the issue was opened, `mesa 23.3.1` was riddled with segfault reports everywhere in their gitlab repo. I just indicized some as examples to demonstrate this was a multi-architecture concern, to justify the title, and a version reverse, that's all. But there were tens of segfaults reports on gitlab, although it was impossible to tell exactly which were related or not. So far, we've only got positive feedback about testing with AMDGPU, and the lack of reporting on other architectures was holding back an update. 
> 
> @SpidFightFR I suppose we could attempt an update to a Mesa 24.3.2+ version, since it doesn't seem we're getting more tests from here. We've only had two users actually reporting positive results with `mesa-24.3.2`, that should hopefully be enough. Let's just be careful the first 24-48 hours after the update. I will keep this issue open in the meantime just in case. 
> 
> @classabbyamp I also bring this to the attention of a more experienced void maintainer (Yourself), in case they want to chime in on what it should be done. 
> 

Hey there, i won't be able to do this myself, unfortunately.

I've changed distro, i am no longer on voidlinux. 

I won't be able to test things myself.