Your message dated Thu, 20 Oct 2022 18:16:45 +0000 with message-id <e1ola61-003wc7...@fasolo.debian.org> and subject line Bug#1021861: fixed in virglrenderer 0.10.3-2 has caused the Debian Bug report #1021861, regarding virglrenderer FTBFS on armel 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.) -- 1021861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: virglrenderer Version: 0.10.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=virglrenderer&arch=armel&ver=0.10.3-1&stamp=1664582880&raw=0 ... FAILED: src/libvirgl.a.p/venus_vkr_context.c.o cc -Isrc/libvirgl.a.p -Isrc -I../src -I../src/gallium/include -I../src/gallium/auxiliary -I../src/gallium/auxiliary/util -I. -I.. -I../src/venus -I../src/drm -I../src/drm/drm-uapi -Isrc/mesa -I../src/mesa -I../src/mesa/compat -I../src/mesa/pipe -I../src/mesa/util -I/usr/include/libdrm -fdiagnostics-color=always -DNDEBUG -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -O0 -Werror=implicit-function-declaration -Werror=missing-prototypes -Wmissing-prototypes -Werror=incompatible-pointer-types -Werror=int-to-pointer-cast -Wno-overlength-strings -fvisibility=hidden -imacros /<<PKGBUILDDIR>>/obj-arm-linux-gnueabi/config.h -DHAVE_CONFIG_H=1 -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ src/libvirgl.a.p/venus_vkr_context.c.o -MF src/libvirgl.a.p/venus_vkr_context.c.o.d -o src/libvirgl.a.p/venus_vkr_context.c.o -c ../src/venus/vkr_context.c In file included from ../src/mesa/util/compiler.h:37, from ../src/mesa/util/xxhash.h:81, from ../src/venus/vkr_context.c:17: ../src/venus/vkr_ring.h:33:1: error: static assertion failed: "vkr_ring_control requires lock-free 32-bit atomic_uint" 33 | static_assert(ATOMIC_INT_LOCK_FREE == 2 && sizeof(atomic_uint) == 4, | ^~~~~~~~~~~~~ ... Do src/venus/vkr_ring.h and src/proxy/proxy_context.h really require ATOMIC_INT_LOCK_FREE == 2? Atomics on armel being implemented with a kernel helper, which gives only ATOMIC_INT_LOCK_FREE == 1. If ATOMIC_INT_LOCK_FREE == 2 is really required, then disabling venus and renderserver on armel should workaround it for now.
--- End Message ---
--- Begin Message ---Source: virglrenderer Source-Version: 0.10.3-2 Done: Michael Tokarev <m...@tls.msk.ru> We believe that the bug you reported is fixed in the latest version of virglrenderer, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev <m...@tls.msk.ru> (supplier of updated virglrenderer 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: SHA256 Format: 1.8 Date: Thu, 20 Oct 2022 20:19:02 +0300 Source: virglrenderer Architecture: source Version: 0.10.3-2 Distribution: unstable Urgency: medium Maintainer: Gert Wollny <g...@debian.org> Changed-By: Michael Tokarev <m...@tls.msk.ru> Closes: 1021861 Changes: virglrenderer (0.10.3-2) unstable; urgency=medium . * Another non-maintainer upload. * d/rules: disable render-server on armel since it requires (not enabled) venus (Really closes: #1021861) * install the newly usr/libexec/virgl_render_server into virgl-server (on !armel) * d/rules: show testlog.txt (to stderr) in case of selftest failure * d/rules: ignore selftest failures on all 32bit arches too, for now * d/control: build-depend on dh-exec (for arch filtering of virgl-server) * d/control: switch to debhelper-compat=13 * d/control: bump Standards-Version to 4.6.1 (no changes) Checksums-Sha1: 12735c1218cf6d034461d24e56d215b335725c1c 1845 virglrenderer_0.10.3-2.dsc 2436f7af65e7f12bb7498d2fcaa62291b954f0c3 7692 virglrenderer_0.10.3-2.debian.tar.xz f6e3398de099aa7972bab688a424cb7a05981de2 8388 virglrenderer_0.10.3-2_source.buildinfo Checksums-Sha256: 1c4af44a20dd9da214be581a6b4d80195f49d80e21e296d613d35da0b3681a27 1845 virglrenderer_0.10.3-2.dsc abf63e9f12cd33c3c48da7d2af99702f1821b7ac7b3105e6a4699a73310df91c 7692 virglrenderer_0.10.3-2.debian.tar.xz d2c93c59872d40b96bdc2f0743961ccc54a887028042112acacc1fd617813346 8388 virglrenderer_0.10.3-2_source.buildinfo Files: 67a7965e42915c348568f54b95fbd232 1845 libs optional virglrenderer_0.10.3-2.dsc d0dd63815c1758e5983fee87cdd2bf8c 7692 libs optional virglrenderer_0.10.3-2.debian.tar.xz 04e1f09d025564383d5de51fa7ab68cb 8388 libs optional virglrenderer_0.10.3-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAmNRhQoPHG1qdEB0bHMu bXNrLnJ1AAoJEHAbT2saaT5ZVAIH/3M87JnG5/zkHgcjdOwJKB5Z6LW6vnWhYled jH++Sa3U8oICZCcJDS28LBBK6lviHsGT1yL5M6GKJFkyGn3jtJnNTNAmmuByOwK4 FuT4cDUuoGMeUtlyzYt/4NHsgxnWvnTlusTu0ZA3ctYtixxLktNqOR8U1jigjtR0 BIegMEAPr3tZsuMVeRo2DX7sxYKeRCuhBgO+U6tskvfgfS8aviMu2YIwDX82qKPA RItFj+SslYYkCVOAzkpNJnQzlzrnxTeiB/rRxWMffNKbreXCHciJ/d2O7/FvbRjv tCwU4xtbuV4u6uEQbnNHaixf5YMSqZjNC+FT9c1BL42g0xsflp4= =WzGI -----END PGP SIGNATURE-----
--- End Message ---
