Your message dated Thu, 05 Sep 2024 09:21:07 +0000
with message-id <e1sm8fr-006wm7...@fasolo.debian.org>
and subject line Bug#1080475: fixed in mesa 24.2.1-4
has caused the Debian Bug report #1080475,
regarding mesa: please re-enable softpipe, at least on architectures where 
llvmpipe is not yet mature
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1080475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mesa
Severity: important
Justification: causes FTBFS in at least src:gtk4
Tags: ftbfs
X-Debbugs-Cc: g...@packages.debian.org, debian-ri...@packages.debian.org, 
debian-loonga...@packages.debian.org, debian-m...@packages.debian.org
User: debian-m...@packages.debian.org
Usertags: mips64el
User: debian-ri...@packages.debian.org
Usertags: riscv64

Historically, Mesa's llvmpipe used LLVM MCJIT, which supports a limited
range of architectures and will not add more, and this resulted in
several architectures having either a broken llvmpipe or no llvmpipe
support at all.

With the recent upload of Mesa 24.2.x to unstable, llvmpipe now uses
ORCJIT for architectures where MCJIT is unavailable. However, the ORCJIT
version of llvmpipe doesn't seem to be particularly mature yet (perhaps
unsurprisingly, it's very new!) and is crashing under some circumstances
on at least riscv64: #1080435.

If softpipe was still enabled on at least the affected architectures,
then packages' test suites would be able to force its use via
GALLIUM_DRIVER=softpipe in the environment if necessary. At the
moment src:gtk4 does this on mips*, plus the powerpc and sparc* -ports
architectures, to avoid #1010838; the removal of the softpipe driver
means that this makes GL initialization fail, causing test failures and
a FTBFS (I'll report this as a separate RC bug in src:gtk4). I had hoped
to do the same for riscv64 to work around #1080435, but in fact this is
not possible for the same reason.

While it's more important on the ORCJIT architectures, also enabling
softpipe on more mainstream architectures like x86 would make it easier
for maintainers to compare llvmpipe with softpipe (without having to
build their package on porterboxes that are often very slow), and easier
to get a consistent test result for all architectures.

For what it's worth, the upstream default (with -Dgallium-drivers=auto)
is to enable softpipe on all architectures. In the Debian
packaging, I believe this would be most easily done by reverting
1ba4b2499e875266f6fbd7ba20068fb569986286 "rules: Build softpipe or
llvmpipe depending on the arch, not both.".

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: mesa
Source-Version: 24.2.1-4
Done: Timo Aaltonen <tjaal...@debian.org>

We believe that the bug you reported is fixed in the latest version of
mesa, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1080...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen <tjaal...@debian.org> (supplier of updated mesa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 05 Sep 2024 11:49:34 +0300
Source: mesa
Built-For-Profiles: noudeb
Architecture: source
Version: 24.2.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Timo Aaltonen <tjaal...@debian.org>
Closes: 1080475
Changes:
 mesa (24.2.1-4) unstable; urgency=medium
 .
   * patches: Add patches to fix autopkgtest regressions in dril.
   * rules: Enable softpipe everywhere again. (Closes: #1080475)
Checksums-Sha1:
 943b44b8fc882f6158f1ed4f516130c89b83d3e6 6648 mesa_24.2.1-4.dsc
 c0f164bccabed29a8e1ac4293286cd5f43153d25 106336 mesa_24.2.1-4.debian.tar.xz
 29370705c1447c71cbeb42b2b3ed1e732a165cb1 10738 mesa_24.2.1-4_source.buildinfo
Checksums-Sha256:
 afca0da5f25c620fd1768c0153b789ed0b0bd55aa4146b5ed93d0567714e67c7 6648 
mesa_24.2.1-4.dsc
 98ad3ccf93b278e8b467ebf96d82c28261484dc28d8eeef85682bb20a052e1a2 106336 
mesa_24.2.1-4.debian.tar.xz
 6a3180198707ab452621d5659962bcd9b1c8ad65acbefae6b3ba7e8a60d227f0 10738 
mesa_24.2.1-4_source.buildinfo
Files:
 2bc126183e9ee46ef14a03e5602b49d7 6648 graphics optional mesa_24.2.1-4.dsc
 2534027599420bb2edab1e8378de8da9 106336 graphics optional 
mesa_24.2.1-4.debian.tar.xz
 a0d4efe588ccdfbb2242c643b28e281e 10738 graphics optional 
mesa_24.2.1-4_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmbZcK8ACgkQy3AxZaiJ
hNzqJxAAgLbyN6IFFNFqVBv8IkfYrOutrwLwwrAt+Q24CysP2Oco9Lt0aQmgCTUO
uR9LTpLsiXY2mp8hHKtHKUxOb0U4lXChKtBynmxhe9dp9K1eIl13N9ELOSJf6c+E
kzVw99Es0LRJJuQxXE7bVhZkTgvf7VApLg//5V705gZ+C2tlu87gNKdI6SCIPute
7cVKNubta7PbJAZXLu9AYFtNIk8BrolDD8S8p/U3p+VluL9EgPlzmjuj2xyusGJ7
1Pxy6Ey1HUln/jofpj5D/sppAeF+GlBsfpnXa3+n2u7liwZlixCYtAFk07yg34yY
P1jvBYdUUz4utG8nDJR4xfdv6x6jbusfVa0zPmlcV8GVHtan89X2BUwQMBlbo2q0
L+5hPmQiZcXTqs7qtPQvqzGOvRQgIuRw4lI/qygyvUzudapUSNQmLSqYrI9Yoj3U
SxSKfTSPlyDQlAA907B3sEDY5j+GZtu/GbsGcwdWVCfqVE8IrsxFHoJPbJZ0yUAU
eUMmTOvffwnQPl7HkVh0U+xJrIn7f+vaR8kAK5lcvaGudoeRAvrpS6QZySDWO3gz
Fei3KjiDk6SDCgnvvSrXUz2PQElqF6pWbk0fUaYRs4kdw3KWG1eB61t413hiX/MJ
TsJwg6jh7dvDRa7JYZ7i33lXkfT7tPYUvOGsFdUJHEOlLAqYtPU=
=CX/b
-----END PGP SIGNATURE-----

Attachment: pgpYeEz9DD_Xc.pgp
Description: PGP signature


--- End Message ---

Reply via email to