Processing of mesa_25.0.2-1_source.changes
mesa_25.0.2-1_source.changes uploaded successfully to localhost along with the files: mesa_25.0.2-1.dsc mesa_25.0.2.orig.tar.xz mesa_25.0.2-1.debian.tar.xz mesa_25.0.2-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: x11-xkb-utils: Please backport xkbcomp patch to avoid Xwayland warnings
Processing control commands: > affects -1 sway Bug #1100957 [libx11-6] x11-xkb-utils: Please backport xkbcomp patch to avoid Xwayland warnings Added indication that 1100957 affects sway -- 1100957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1100957: x11-xkb-utils: Please backport xkbcomp patch to avoid Xwayland warnings
Package: libx11-6 Version: 7.7+9 Control: affects -1 sway X-debbugs-cc: s...@packages.debian.org Dear maintainer, With Sway on Debian with Xwayland turned on, one's logs get filled with The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Unsupported maximum keycode 708, clipping. > X11 cannot support keycodes above 255. Errors from xkbcomp are not fatal to the X server over and over again. Bug reports: https://github.com/swaywm/sway/issues/6476 https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/137 This is reported to fix the problem: https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/79 It would be great if this patch could make it into trixie. Thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#1081943: libgl1-mesa-dri: llvmpipe exists but does not work on sparc64
On Thu, 20 Mar 2025 at 15:50:44 +0100, John Paul Adrian Glaubitz wrote: On Mon, 2024-09-16 at 11:43 +0100, Simon McVittie wrote: Expected result: either of these: - llvmpipe exists, is used, and works - llvmpipe doesn't exist and softpipe is automatically used instead ... I would suggest special-casing llvmpipe (and anything else requiring LLVM JIT: lavapipe?) to be built on most of the $(LLVM_ARCHS), but not sparc64. I just ran into this issue while looking at libadwaita-1. I'm not 100% sure yet what would need to be done to enable full JIT support on sparc64. I assume that the missing component is liborc, isn't it? I don't know, I'm not a compiler or Mesa expert. I know that one blocker for LLVM JIT on less mainstream architectures in the past has been that LLVM upstream deprecated their old JIT implementation (MC JIT?) in favour of a new implementation (ORC JIT?), and as part of that they would no longer accept patches to expand the old JIT to new architectures; but for a while Mesa only knew how to use the old JIT, and could not use the new JIT, which meant no JIT on riscv64 for example. I believe that limitation has now been resolved, with Mesa using the new JIT on at least the architectures that are not supported by the old one. I don't think LLVM ORC JIT has anything to do with the liborc used by e.g. GStreamer (src:orc in Debian), but I could be wrong about that. If it isn't obvious how to make the JIT work on sparc64, the next best thing (probably considerably easier to achieve) would be for the Mesa packaging to disable llvmpipe (and any other feature that needs it, like perhaps lavapipe) on sparc64, so that the only features that are enabled on each architecture are the ones that we can expect will actually work in practice. From GTK's point of view, I think that not having llvmpipe at all would be better than llvmpipe existing but crashing out at runtime. If I understand correctly, the result of that would be that in the absence of a supported GPU, everything that uses OpenGL (such as GTK) would automatically fall back to softpipe, which is slow and sometimes misrenders things (so we'd still need architecture-specific workarounds to ignore known test failures) but does generally work (so GTK apps would have a reasonably normal level of functionality, even if they're slow or have visual glitches). smcv
Bug#1081943: libgl1-mesa-dri: llvmpipe exists but does not work on sparc64
Hello Simon, On Mon, 2024-09-16 at 11:43 +0100, Simon McVittie wrote: > To reproduce: > - install gtk4 build-dependencies on sparc64 porterbox with no access to a > real GPU > - get gtk4 source > - edit debian/rules to remove the special case that forces use of softpipe > on sparc64 > - build and run tests > > Expected result: either of these: > - llvmpipe exists, is used, and works > - llvmpipe doesn't exist and softpipe is automatically used instead > > Actual result: > - all tests that use OpenGL fail with message "Target has no JIT support" > > I would suggest special-casing llvmpipe (and anything else requiring LLVM > JIT: lavapipe?) to be built on most of the $(LLVM_ARCHS), but not sparc64. I just ran into this issue while looking at libadwaita-1. I'm not 100% sure yet what would need to be done to enable full JIT support on sparc64. I assume that the missing component is liborc, isn't it? Looking at the LLVM upstream sources, I see no obvious reason why liborc should not be supported on sparc64. But I'm not an expert on liborc, so I might be missing something. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
mesa_25.0.2-1_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 20 Mar 2025 16:52:21 +0200 Source: mesa Built-For-Profiles: noudeb Architecture: source Version: 25.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1100360 Changes: mesa (25.0.2-1) unstable; urgency=medium . * New upstream release. * patches: Fix spam from gfxstream. (Closes: #1100360) * rules: Update gentarball target to use xz and the current tree. Checksums-Sha1: 1af46c5f60943a393d0c0093ea39cd09228172ee 6331 mesa_25.0.2-1.dsc d599e0300a7ccc40cca3ce98ddc661d32594f848 49714228 mesa_25.0.2.orig.tar.xz 6576a46ef6e97d7e38cae624bd9ee23eeb1cc4dc 111608 mesa_25.0.2-1.debian.tar.xz 033e1371ebd256d18617deb4e3de51b4a32acd41 10707 mesa_25.0.2-1_source.buildinfo Checksums-Sha256: a42c50b84ba2b0a99a015155828d406058e9a587ef3a0ad5a4b01bf6fa152e3b 6331 mesa_25.0.2-1.dsc 262a44efda321f492e5019be3439d27f44107d7e4dca1b8cce7304d48474e422 49714228 mesa_25.0.2.orig.tar.xz f1df6066f4d0c0846804e2e28b8224a8078f3f2eadfa910f54a2bea7511ce820 111608 mesa_25.0.2-1.debian.tar.xz 9ee9c10a124fb724c13098db9f050909a34dd3d2cb5c7fffdd58ecab130253ce 10707 mesa_25.0.2-1_source.buildinfo Files: 16f003421129e26eed0b18d63ed6cea6 6331 graphics optional mesa_25.0.2-1.dsc 4f9eb34b49d5d93e990d2c3660f39fc9 49714228 graphics optional mesa_25.0.2.orig.tar.xz 7e54eb2117a0e2df39f9e37883d991bd 111608 graphics optional mesa_25.0.2-1.debian.tar.xz 2ef0a46752c071013d51d71cf7f1a9de 10707 graphics optional mesa_25.0.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmfcK8MACgkQy3AxZaiJ hNwBoA//bvTvvabBGdcxe3uvV/nCNgsN9miUeqO+1T+6wmeS1bMGiq7LLV3mch5i 3KUhxN64pOoUPiORoGZq3f/cL7ht6yHH4TerJHjidxg97vZ/+YpQqeBrCWA7STbS hTXs7BY6a108PsUtJjwi4FdszaEYpgz+45Anf1zQ4WapacWb4VvO6qeEvQwp2YJP bkFRRaMT51H55efoY9XbFuvXGOJ5hqS2y0qqLA1TKfMvRLtQkvEoszvguGGj2RMY r4ux8H1NNZJ9xTKQT4+JGhGmgRakLvOAkkpPNl4cb78cyps9k5r/nH49ptiiAoCP T+3mOzABjme5oirCahRiRRrrAUKGGaeDNd91faJxlkMfZxM247bHd5oVnprKuRjv NGtbIhUUAC4NKF1gRCzXujIZ5b2QWxl45V8qMa7WBDNI73YEYyuRiJPR5S7KPTSg axT5JGDs7z7vJ9GnSzsPSrXUwldHQsqWtQrgQl/OMCLOT07AM4k4fwCfZ2mRjfcL mZig8t63LLysqgBzQsOi7k6Lz1/tUlW9PthGEpBphsbYWevEBIUvk+NyIUUclqE6 JXPSfz7BZt6/MT5VlhOVEb0OvRk2FRyThHVUB8dLMJuKdYrjEuk/6qbptrUc2Rod Wij6+2AZGIaR+mosEJtRY7DeSs4nd0K/pi2loHLJ8ILueLhapNc= =0Byi -END PGP SIGNATURE- pgpJptpBzwQ2s.pgp Description: PGP signature
[Git][xorg-team/lib/mesa] Pushed new tag debian/25.0.2-1
Timo Aaltonen pushed new tag debian/25.0.2-1 at X Strike Force / lib / mesa -- View it on GitLab: https://salsa.debian.org/xorg-team/lib/mesa/-/tree/debian/25.0.2-1 You're receiving this email because of your account on salsa.debian.org.
