> Details of changes below, which included some more ungrafting: > >>> Here is a list of what has been on my radar and I'll be looking to >>> apply on the mesa-updates branch. If there's something I missed and >>> you think makes sense here (e.g. lower level graphical/X related >>> libraries) please let me know. And yes, I need to make a Mesa team. It >>> is on my list! >>> >>> 1. ungraft libx11 and libxpm >>> > > These are done. > > Also, since I didn't realize libx11 means building python, and rust, > and so on, I figured I would ungraft more that was being rebuilt > anyway. So nghttp2 and curl have been ungrafted. > > The only more involved change was in ungrafting curl (to keep another > test skip for Hurd), in > <https://git.savannah.gnu.org/cgit/guix.git/commit/?id=00442f15d46cd9d5d02499827946d23426aad0ba&h=mesa-updates> > and then running parallel tests (very nice speed up for building curl > I came across in the documentation!) in > <https://git.savannah.gnu.org/cgit/guix.git/commit/?id=d70f2b788e56545f93dc24238d2617e20fde7460&h=mesa-updates>. > Please do take a look in case I missed something here, but all built > fine locally on x86_64 at least. > >>> 2. update mesa (23.2.1) >>> >>> 3. <https://issues.guix.gnu.org/65375> (libepoxy fix for GTK, see >>> <https://issues.guix.gnu.org/64981>) >>> > > These are done. > >>> 4. <https://issues.guix.gnu.org/65155> (mesa vulkan search-paths) >>> > > I don't think this is a correct change as written (search-path should > be in vulkan-loader if I'm understanding what is supposed to happen > here). Anyway, will follow up on that issue and left it out for now. > >>> 5. <https://issues.guix.gnu.org/65153> (sdl2 vulkan-loader; and update >>> sdl2?) >>> >>> 6. <https://issues.guix.gnu.org/64637> (libdrm update; to even newer >>> version now) >>> >>> 7. <https://issues.guix.gnu.org/66727> (libxkbcommon update) >>> >>> 8. <https://issues.guix.gnu.org/64639> (pixman update) >>> > > All these done (sdl2 was also updated to latest version). > >>> 9. submit patch for mesa team >>> > > But not this one, the easy one :) It will be sent. > >>> Thanks everyone! And when you see the updates pushed on mesa-updates >>> and builds become available, please do test and let me know. Or if >>> you'd like to join this team of one, happy to have you on board. >> >> Sounds like a fine plan! Thank you for tackling this! > > Happy to! Substitutes will eventually become available, but there's > quite a few builds to be done. This takes care of some ungrafts and > updates with I hope minimal disruption. I'll be keeping an eye out and > using locally as well. Please test and report, thanks everyone! > > John
An issue was created to track merging the mesa-updates branch here: <https://issues.guix.gnu.org/66964>. Please use that bug number as needed (and cc me or use wide-reply in emacs debbugs).