Bug#1093365: vulkan-tools: FTBFS: error: â??VK_DRIVER_ID_RESERVED_27â?? was not declared in this scope
Simon McVittie kirjoitti 23.1.2025 klo 13.11: Control: tags -1 + fixed-upstream pending On Fri, 17 Jan 2025 at 18:54:30 +, Santiago Vila wrote: /<>/vulkaninfo/generated/vulkaninfo.hpp: In function ‘std::string VkDriverIdString(VkDriverId)’: /<>/vulkaninfo/generated/vulkaninfo.hpp:103:15: error: ‘VK_DRIVER_ID_RESERVED_27’ was not declared in this scope; did you mean ‘VK_DRIVER_ID_MESA_VENUS’? It looks like this has been fixed in the upstream 1.4.304.0 release, which is staged in the packaging git repository but has not yet been uploaded. Is there something blocking upload of that version? vulkan-volk needs an update, but it doesn't follow the workflow of other xorg-team packages, so I don't touch it. -- t
Bug#1093365: vulkan-tools: FTBFS: error: â??VK_DRIVER_ID_RESERVED_27â?? was not declared in this scope
Control: tags -1 + fixed-upstream pending On Fri, 17 Jan 2025 at 18:54:30 +, Santiago Vila wrote: > /<>/vulkaninfo/generated/vulkaninfo.hpp: In function > ‘std::string VkDriverIdString(VkDriverId)’: > /<>/vulkaninfo/generated/vulkaninfo.hpp:103:15: error: > ‘VK_DRIVER_ID_RESERVED_27’ was not declared in this scope; did you mean > ‘VK_DRIVER_ID_MESA_VENUS’? It looks like this has been fixed in the upstream 1.4.304.0 release, which is staged in the packaging git repository but has not yet been uploaded. Is there something blocking upload of that version? Thanks, smcv
Processed: Re: Bug#1093365: vulkan-tools: FTBFS: error: â??VK_DRIVER_ID_RESERVED_27â?? was not declared in this scope
Processing control commands: > tags -1 + fixed-upstream pending Bug #1093365 [src:vulkan-tools] vulkan-tools: FTBFS: error: âVK_DRIVER_ID_RESERVED_27â was not declared in this scope Added tag(s) fixed-upstream and pending. -- 1093365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: vulkan-volk: new upstream release, required by updated vulkan-tools
Processing control commands: > block 1093365 by -1 Bug #1093365 [src:vulkan-tools] vulkan-tools: FTBFS: error: âVK_DRIVER_ID_RESERVED_27â was not declared in this scope 1093365 was not blocked by any bugs. 1093365 was not blocking any bugs. Added blocking bug(s) of 1093365: 1093844 > affects -1 src:vulkan-tools Bug #1093844 [src:vulkan-volk] vulkan-volk: new upstream release, required by updated vulkan-tools Added indication that 1093844 affects src:vulkan-tools -- 1093365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093365 1093844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1093844: vulkan-volk: new upstream release, required by updated vulkan-tools
Source: vulkan-volk Version: 1.3.290.0-1 Severity: important Control: block 1093365 by -1 Control: affects -1 src:vulkan-tools X-Debbugs-Cc: vulkan-to...@packages.debian.org The new upstream release 1.4.304.0 is required by an updated version of vulkan-tools, which as far as I can see would fix RC bug #1093365. Timo Aaltonen writes: > Simon McVittie kirjoitti 23.1.2025 klo 13.11: > > Is there something blocking upload of that version? > > vulkan-volk needs an update, but it doesn't follow the workflow of other > xorg-team packages, so I don't touch it. Please could another team member take a look at updating vulkan-volk? (Perhaps new upstream releases of the Vulkan stack should go to experimental until all parts are ready, since it seems they often need to go together?) Thanks, smcv
Processed: glslang-dev: autopkgtest regression in unstable: libraries from spirv.pc no longer sufficient to link a test program
Processing control commands:
> found -1 15.1.0-1
Bug #1093845 [glslang-dev] glslang-dev: autopkgtest regression in unstable:
libraries from spirv.pc no longer sufficient to link a test program
Marked as found in versions glslang/15.1.0-1.
> block 1088554 by -1
Bug #1088554 {Done: Paul Gevers } [src:glslang] src:glslang:
fails to migrate to testing for too long: fails its own autopkgtest
1088554 was not blocked by any bugs.
1088554 was not blocking any bugs.
Added blocking bug(s) of 1088554: 1093845
--
1088554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088554
1093845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1093845: glslang-dev: autopkgtest regression in unstable: libraries from spirv.pc no longer sufficient to link a test program
Package: glslang-dev Version: 15.0.0-1 Severity: serious Justification: https://release.debian.org/testing/rc_policy.txt §6a X-Debbugs-Cc: spirv-to...@packages.debian.org Control: found -1 15.1.0-1 Control: block 1088554 by -1 It looks as though new versions of glslang and/or spirv-tools have caused linking using spirv.pc to regress, similar to #951988. The test I contributed in #951988 was previously successful, but is now failing. Linking a simple test program to libglslang with glslang.pc is still successful: 64s + pkg-config --cflags --libs glslang 64s + g++ -std=c++17 -o trivial trivial.cpp -lglslang -lMachineIndependent -lGenericCodeGen -lOSDependent -lSPVRemapper -lpthread 65s + test -x trivial but linking a slightly less simple test program with spirv.pc is not: 65s + g++ -std=c++17 -o spirv spirv.cpp -lSPIRV -lSPIRV-Tools-opt -lSPIRV-Tools -lSPIRV-Tools-link -lglslang -lMachineIndependent -lGenericCodeGen -lOSDependent -lSPVRemapper -lpthread 65s /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/14/../../../x86_64-linux-gnu/libglslang.a(SpvTools.cpp.o): in function `glslang::SpirvToolsDisassemble(std::ostream&, std::vector > const&, spv_target_env)': 65s (.text+0x423): undefined reference to `spvContextCreate' 65s /usr/bin/ld: (.text+0x455): undefined reference to `spvBinaryToText' 65s /usr/bin/ld: (.text+0x464): undefined reference to `spvDiagnosticPrint' (etc.) The .pc files are a Debian-specific addition, so presumably the patches that add them need updating to reflect how upstream would link programs to these libraries? Has libglslang.a perhaps grown a dependency on SPIRV-Tools, which is not detected by the glslang.pc test-case because it's too simple? If that's the case then it might need "Requires: SPIRV-Tools", like spirv.pc already has. (I don't know much about the internal structure of these libraries, so I don't know how their upstream developer intends them to fit together.) Resolving this will be a prerequisite for src:glslang migrating to testing (#1088554). smcv
[Git][xorg-team/vulkan/vulkan-volk][pristine-tar] pristine-tar data for vulkan-volk_1.4.304.0.orig.tar.gz
Dylan Aïssi pushed to branch pristine-tar at X Strike Force / vulkan / vulkan-volk Commits: a32f1a80 by Dylan Aïssi at 2025-01-23T15:02:51+01:00 pristine-tar data for vulkan-volk_1.4.304.0.orig.tar.gz - - - - - 2 changed files: - + vulkan-volk_1.4.304.0.orig.tar.gz.delta - + vulkan-volk_1.4.304.0.orig.tar.gz.id Changes: = vulkan-volk_1.4.304.0.orig.tar.gz.delta = Binary files /dev/null and b/vulkan-volk_1.4.304.0.orig.tar.gz.delta differ = vulkan-volk_1.4.304.0.orig.tar.gz.id = @@ -0,0 +1 @@ +5d33af6ce9814e1ff816e2bb191b7486577818cb View it on GitLab: https://salsa.debian.org/xorg-team/vulkan/vulkan-volk/-/commit/a32f1a802d9f011dc6cc168f45bb2ef659335b48 -- View it on GitLab: https://salsa.debian.org/xorg-team/vulkan/vulkan-volk/-/commit/a32f1a802d9f011dc6cc168f45bb2ef659335b48 You're receiving this email because of your account on salsa.debian.org.
[Git][xorg-team/vulkan/vulkan-volk] Pushed new tag debian/1.4.304.0-1
Dylan Aïssi pushed new tag debian/1.4.304.0-1 at X Strike Force / vulkan / vulkan-volk -- View it on GitLab: https://salsa.debian.org/xorg-team/vulkan/vulkan-volk/-/tree/debian/1.4.304.0-1 You're receiving this email because of your account on salsa.debian.org.
[Git][xorg-team/vulkan/vulkan-volk] Pushed new tag upstream/1.4.304.0
Dylan Aïssi pushed new tag upstream/1.4.304.0 at X Strike Force / vulkan / vulkan-volk -- View it on GitLab: https://salsa.debian.org/xorg-team/vulkan/vulkan-volk/-/tree/upstream/1.4.304.0 You're receiving this email because of your account on salsa.debian.org.
Processing of mesa_24.3.4-1_source.changes
mesa_24.3.4-1_source.changes uploaded successfully to localhost along with the files: mesa_24.3.4-1.dsc mesa_24.3.4.orig.tar.xz mesa_24.3.4.orig.tar.xz.asc mesa_24.3.4-1.debian.tar.xz mesa_24.3.4-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
[Git][xorg-team/lib/mesa] Pushed new tag debian/24.3.4-1
Timo Aaltonen pushed new tag debian/24.3.4-1 at X Strike Force / lib / mesa -- View it on GitLab: https://salsa.debian.org/xorg-team/lib/mesa/-/tree/debian/24.3.4-1 You're receiving this email because of your account on salsa.debian.org.
mesa_24.3.4-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, 23 Jan 2025 19:48:02 +0200 Source: mesa Built-For-Profiles: noudeb Architecture: source Version: 24.3.4-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Changes: mesa (24.3.4-1) unstable; urgency=medium . * New upstream release. * control: Make libgl1-mesa-dri depend on the same version of libgbm1. Checksums-Sha1: d2587bc4eab684474227b0d5c890871f996a8277 6648 mesa_24.3.4-1.dsc 957ed67271cd7e2f42a8c1d10c0d2c38043ae84a 30691532 mesa_24.3.4.orig.tar.xz c1e41f2076d649c042ee84ff1daec93f1b97d952 488 mesa_24.3.4.orig.tar.xz.asc 32ce824f2064c81a8e296d8ab1cd7c3b79c45a4f 105780 mesa_24.3.4-1.debian.tar.xz e8135a8d51d77b6bf73c378a61b052b96e348953 10658 mesa_24.3.4-1_source.buildinfo Checksums-Sha256: 985e51b1ba32c786c09380cf7f652f821be457aec2838b238d9983f69ccd7c46 6648 mesa_24.3.4-1.dsc e641ae27191d387599219694560d221b7feaa91c900bcec46bf444218ed66025 30691532 mesa_24.3.4.orig.tar.xz 20a9b5658e28e467a6cf3f0aa086d1f3cec98af646af572d2db9cb27825fbc87 488 mesa_24.3.4.orig.tar.xz.asc c435107efc9d12c20a900d1739d6ae1ca9aa3f7847e60378470f818abf727177 105780 mesa_24.3.4-1.debian.tar.xz 8b469f04872561bcddce9f8627dea11ba7bcccb4ff39713193b53d81bedb2c3c 10658 mesa_24.3.4-1_source.buildinfo Files: b2ff5b3c99cac408a7e643e063e022e8 6648 graphics optional mesa_24.3.4-1.dsc c64b7e2b4f1c7782c41bf022edbb365c 30691532 graphics optional mesa_24.3.4.orig.tar.xz 85baa10280c8519ef8693849115fecb6 488 graphics optional mesa_24.3.4.orig.tar.xz.asc d8081812a1b68ccc62aba158db8cdff8 105780 graphics optional mesa_24.3.4-1.debian.tar.xz c173bcd1349359b2501ace2f8ce716f9 10658 graphics optional mesa_24.3.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmeSgN4ACgkQy3AxZaiJ hNyOaw//RTHg1vMVXD5gix20o7Cs21X6yBSjTFvKUmd+SdSM0DPlrdQanmaDgNlg wEnBAkMq5h57uUxkBlbWkKGu/q58x3UaiEvHFQ+N7BtB6cETMJSKxPW7FmneAPeu HjopzL9xcJddhb+O7DBEADFCy8PQ941kVYV3vBJAUMOpcmYC06hj7jKIsGdUVwtX SPw1MLlitLg/Fr0qi6GlhlUnQMaCyLn3nD7RsypL/7k7ALKOw8FKTss8nn/xgQaF xfoZFCV/zpaPGyHTU3ZBKVQdeO7tVXY+o3vUp5p6ec/0AeFqCYbRnRzfYj96lPvY CCJcoraHFBoRih5435FPEVcpc1JSQPcjuFT2zv8zR8OXB+1udW0BTDH9mcGYgij9 9ERJYXU9Nh2wcNqZ3sACxljEuLGhsGIqibbMecRwo2A8xbHV0Am8Fl8F+tdz1Ziy H5EdUgvD8PMCJo6INfK8wDu/3vj+54OYQgLVuh2AzBlKZfXE8mnZR/1516OTrpG5 hk0wPBRfyP2AKT3agTdXWs+3DitxP+5saBHGNI7R02ybUj1y4tq6I9HEoRtc3Qnc 9akymgTuJC6SQlXXiJmYhIRQTYbduy5HGgmYNZ/DrCB+6nkGIJWmcK5NBbm2Mr76 GTiTuKg0NV0N/D9yzRC4snZ8GjSnaHrrefAwun/uzV4nLPNWwsM= =0oGJ -END PGP SIGNATURE- pgpDgf13l9SiD.pgp Description: PGP signature
Bug#1093844: marked as done (vulkan-volk: new upstream release, required by updated vulkan-tools)
Your message dated Thu, 23 Jan 2025 14:41:30 + with message-id and subject line Bug#1093844: fixed in vulkan-volk 1.4.304.0-1 has caused the Debian Bug report #1093844, regarding vulkan-volk: new upstream release, required by updated vulkan-tools 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.) -- 1093844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vulkan-volk Version: 1.3.290.0-1 Severity: important Control: block 1093365 by -1 Control: affects -1 src:vulkan-tools X-Debbugs-Cc: vulkan-to...@packages.debian.org The new upstream release 1.4.304.0 is required by an updated version of vulkan-tools, which as far as I can see would fix RC bug #1093365. Timo Aaltonen writes: > Simon McVittie kirjoitti 23.1.2025 klo 13.11: > > Is there something blocking upload of that version? > > vulkan-volk needs an update, but it doesn't follow the workflow of other > xorg-team packages, so I don't touch it. Please could another team member take a look at updating vulkan-volk? (Perhaps new upstream releases of the Vulkan stack should go to experimental until all parts are ready, since it seems they often need to go together?) Thanks, smcv --- End Message --- --- Begin Message --- Source: vulkan-volk Source-Version: 1.4.304.0-1 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of vulkan-volk, 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 1093...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated vulkan-volk 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, 23 Jan 2025 15:07:00 +0100 Source: vulkan-volk Architecture: source Version: 1.4.304.0-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Dylan Aïssi Closes: 1093844 Changes: vulkan-volk (1.4.304.0-1) unstable; urgency=medium . * New upstream version 1.4.304.0 (Closes: #1093844) * Bump version of libvulkan-dev to >= 1.4.304 Checksums-Sha1: 97392fa1931a80298f02355e3d344e11d9b5c016 2007 vulkan-volk_1.4.304.0-1.dsc 7fdc54442149808778ebecdf97a41fb37bf88dbe 65511 vulkan-volk_1.4.304.0.orig.tar.gz f78ba0d80c4cae257f4d3bec85ea4a524e028796 2640 vulkan-volk_1.4.304.0-1.debian.tar.xz 6311cb740d7058d3600718501c4a4b847b4f7b6b 7413 vulkan-volk_1.4.304.0-1_amd64.buildinfo Checksums-Sha256: a368b597a2c8f6a684612826bde7381045696a5044356898c972ec61e4e1 2007 vulkan-volk_1.4.304.0-1.dsc 2a563c9dd926c804d91d7b84c59516678ccb32d039038049fc20eb22547c88fb 65511 vulkan-volk_1.4.304.0.orig.tar.gz 385e93208f32207b81a3344f6f9509b99a331b4b849d13d4822862066c661719 2640 vulkan-volk_1.4.304.0-1.debian.tar.xz 6b9ac9170390c958d66d53c665965c85fee11b89020880d87b68ed050e227d10 7413 vulkan-volk_1.4.304.0-1_amd64.buildinfo Files: 77466f9d9eb45b87ac0b521da8c8166d 2007 graphics optional vulkan-volk_1.4.304.0-1.dsc b3a038a08223f7393334a610aeea3330 65511 graphics optional vulkan-volk_1.4.304.0.orig.tar.gz a7c0b0c1bd725bd4e75575ffece228fa 2640 graphics optional vulkan-volk_1.4.304.0-1.debian.tar.xz 5de1a0ef59b9d33081af3c5eb926b452 7413 graphics optional vulkan-volk_1.4.304.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmeSTWkACgkQYS7xYT4F D1Q9dxAAnpWS/gVa38TSQYS2WD3zl/ajsRK0F+w8dNqbG3+pb6b+aEtfb7xZwaZ0 4mBTsplgiHEcv7UkXgFKMZjGn5FrdB9J90peE//GFYPeOqlva8fahtlXlfaM+MyM rMXzxawLWeuAUb8TuEcsRhxNu7KguhRLUKx0VTUlfdbL1r4rwE2quOybLjU/XXmA O31gaUKf2maWgbttl3S2bxoUw1B3cdGFIrl4kKUgbyIyT0OUrzv2Dx7VfFX3wh6z wFX9VW7B7YINmoXYTL3ai8xl4+SnEz7sOxv4SrNmHetGcF/0w9HgKGe0BNiBH/XF hocjZyLNRRy1KXLc2tmHG0Z9eUZtyScf+HLV+QRQ6XROklvwrgidda6lDMmSZqg1 WuXMfGFPcmB5AoCIg74JXKxqIWe5HEPUWw3XP6UCBgLuOkEFR3u7icJBWZtbagFG iCa5E3J1ArojLFZp/N0oRmVqJ+EZ46r7Od5YXsIKKQkHaj7+oj+RSzZApxzDWcsl Pm51kS0bk1WCLt9tjErL+cMk4yObQt5G8iUzlyp5DOiewiglWywrBsfo66+BqeOH LiwGoCLEMKB0vTTkjIDBJrt4aQWrB3PWIdLoEDGcF8IBOivC6+qr7BBMl9ndFG8K tne50iweDDyxM1dk1AFVCyyJEDyXse1URv+/wWPrNYbLa6yKVzQ= =lxSx -END PGP SIGNATURE- pgpUYSGM_PXUf.pgp Description: PGP signature --- End Message ---
Bug#1078735: xserver-xorg-video-vesa: fix FTBFS on multiple platforms with newer GCC
On 15/08/2024 06:14, Zixing Liu wrote: * d/p/fix-implicit-declarations.patch: add a patch to fix FTBFS on multiple platforms (LP: #2062159). That's the most interesting bit, which would fix #1087279. However, as I have stated in the upstream MR [1], I think the patch is wrong. We should use libpciaccess instead, as inb/outb don't exist on some architectures, including arm64. Cheers, Emilio [1] https://gitlab.freedesktop.org/xorg/driver/xf86-video-vesa/-/merge_requests/12
Bug#1093365: vulkan-tools: FTBFS: error: â??VK_DRIVER_ID_RESERVED_27â?? was not declared in this scope
On Thu, 23 Jan 2025 at 13:22:20 +0200, Timo Aaltonen wrote: > Simon McVittie kirjoitti 23.1.2025 klo 13.11: > > Is there something blocking upload of that version? > > vulkan-volk needs an update I opened a bug asking for the new version to be packaged, and it has now been closed by an upload to unstable. smcv
Processing of vulkan-volk_1.4.304.0-1_source.changes
vulkan-volk_1.4.304.0-1_source.changes uploaded successfully to localhost along with the files: vulkan-volk_1.4.304.0-1.dsc vulkan-volk_1.4.304.0.orig.tar.gz vulkan-volk_1.4.304.0-1.debian.tar.xz vulkan-volk_1.4.304.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
vulkan-volk_1.4.304.0-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, 23 Jan 2025 15:07:00 +0100 Source: vulkan-volk Architecture: source Version: 1.4.304.0-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Dylan Aïssi Closes: 1093844 Changes: vulkan-volk (1.4.304.0-1) unstable; urgency=medium . * New upstream version 1.4.304.0 (Closes: #1093844) * Bump version of libvulkan-dev to >= 1.4.304 Checksums-Sha1: 97392fa1931a80298f02355e3d344e11d9b5c016 2007 vulkan-volk_1.4.304.0-1.dsc 7fdc54442149808778ebecdf97a41fb37bf88dbe 65511 vulkan-volk_1.4.304.0.orig.tar.gz f78ba0d80c4cae257f4d3bec85ea4a524e028796 2640 vulkan-volk_1.4.304.0-1.debian.tar.xz 6311cb740d7058d3600718501c4a4b847b4f7b6b 7413 vulkan-volk_1.4.304.0-1_amd64.buildinfo Checksums-Sha256: a368b597a2c8f6a684612826bde7381045696a5044356898c972ec61e4e1 2007 vulkan-volk_1.4.304.0-1.dsc 2a563c9dd926c804d91d7b84c59516678ccb32d039038049fc20eb22547c88fb 65511 vulkan-volk_1.4.304.0.orig.tar.gz 385e93208f32207b81a3344f6f9509b99a331b4b849d13d4822862066c661719 2640 vulkan-volk_1.4.304.0-1.debian.tar.xz 6b9ac9170390c958d66d53c665965c85fee11b89020880d87b68ed050e227d10 7413 vulkan-volk_1.4.304.0-1_amd64.buildinfo Files: 77466f9d9eb45b87ac0b521da8c8166d 2007 graphics optional vulkan-volk_1.4.304.0-1.dsc b3a038a08223f7393334a610aeea3330 65511 graphics optional vulkan-volk_1.4.304.0.orig.tar.gz a7c0b0c1bd725bd4e75575ffece228fa 2640 graphics optional vulkan-volk_1.4.304.0-1.debian.tar.xz 5de1a0ef59b9d33081af3c5eb926b452 7413 graphics optional vulkan-volk_1.4.304.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmeSTWkACgkQYS7xYT4F D1Q9dxAAnpWS/gVa38TSQYS2WD3zl/ajsRK0F+w8dNqbG3+pb6b+aEtfb7xZwaZ0 4mBTsplgiHEcv7UkXgFKMZjGn5FrdB9J90peE//GFYPeOqlva8fahtlXlfaM+MyM rMXzxawLWeuAUb8TuEcsRhxNu7KguhRLUKx0VTUlfdbL1r4rwE2quOybLjU/XXmA O31gaUKf2maWgbttl3S2bxoUw1B3cdGFIrl4kKUgbyIyT0OUrzv2Dx7VfFX3wh6z wFX9VW7B7YINmoXYTL3ai8xl4+SnEz7sOxv4SrNmHetGcF/0w9HgKGe0BNiBH/XF hocjZyLNRRy1KXLc2tmHG0Z9eUZtyScf+HLV+QRQ6XROklvwrgidda6lDMmSZqg1 WuXMfGFPcmB5AoCIg74JXKxqIWe5HEPUWw3XP6UCBgLuOkEFR3u7icJBWZtbagFG iCa5E3J1ArojLFZp/N0oRmVqJ+EZ46r7Od5YXsIKKQkHaj7+oj+RSzZApxzDWcsl Pm51kS0bk1WCLt9tjErL+cMk4yObQt5G8iUzlyp5DOiewiglWywrBsfo66+BqeOH LiwGoCLEMKB0vTTkjIDBJrt4aQWrB3PWIdLoEDGcF8IBOivC6+qr7BBMl9ndFG8K tne50iweDDyxM1dk1AFVCyyJEDyXse1URv+/wWPrNYbLa6yKVzQ= =lxSx -END PGP SIGNATURE- pgp0zd8CrZs4x.pgp Description: PGP signature
Bug#1066263: marked as done (xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])
Your message dated Thu, 23 Jan 2025 18:50:34 +0100
with message-id <2507d119-da17-4651-bb82-9da239434...@debian.org>
and subject line Re: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error:
implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’?
[-Werror=implicit-function-declaration]
has caused the Debian Bug report #1066263,
regarding xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit
declaration of function ‘vasprintf’; did you mean ‘vsprintf’?
[-Werror=implicit-function-declaration]
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.)
--
1066263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfonts-utils
Version: 1:7.7+6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../fonttosfnt -Wdate-time -D_FORTIFY_SOURCE=2
> -DXVENDORNAME=\"X.Org\ Foundation\" -I/usr/include/freetype2
> -I/usr/include/libpng16 -DXVENDORNAMESHORT=\"X.Org\" -D_BSD_SOURCE -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c ../fonttosfnt/write.c
> sed -e 's|__vendorversion__|"fonttosfnt 1.0.4" "X Version 11"|' -e
> 's|__xorgversion__|"fonttosfnt 1.0.4" "X Version 11"|' -e
> 's|__xservername__|Xorg|g' -e 's|__xconfigfile__|xorg.conf|g' -e
> 's|__projectroot__|/usr|g' -e 's|__apploaddir__||' -e
> 's|__appmansuffix__|1|g' -e 's|__libmansuffix__|3|g' -e
> 's|__adminmansuffix__|8|g' -e 's|__miscmansuffix__|7|g' -e
> 's|__filemansuffix__|5|g' < ../fonttosfnt/fonttosfnt.man > fonttosfnt.1
> In file included from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/stdlib.h:26,
> from ../fonttosfnt/struct.c:24:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> _DEFAULT_SOURCE"
> | ^~~
> In file included from /usr/include/time.h:25,
> from ../fonttosfnt/util.c:25:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> _DEFAULT_SOURCE"
> | ^~~
> In file included from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/stdio.h:27,
> from ../fonttosfnt/read.c:26:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> _DEFAULT_SOURCE"
> | ^~~
> In file included from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/stdio.h:27,
> from ../fonttosfnt/fonttosfnt.c:25:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> _DEFAULT_SOURCE"
> | ^~~
> In file included from
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> from /usr/include/stdio.h:27,
> from ../fonttosfnt/write.c:29:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
> _DEFAULT_SOURCE"
> | ^~~
> ../fonttosfnt/read.c: In function ‘readFile’:
> ../fonttosfnt/read.c:239:40: warning: format ‘%d’ expects argument of type
> ‘int’, but argument 4 has type ‘FT_Pos’ {aka ‘long int’} [-Wformat=]
> 239 | fprintf(stderr, "size %d: %dx%d\n",
> | ~^
> ||
> |int
> |
Bug#297003: startx: use Debian alternatives instead of hardcoded paths
On Sun, Mar 06, 2011 at 02:03:58AM +0100, Cyril Brulebois wrote: > just for reference, nowadays, your patch mostly boils down to updating > the default client, from xterm to x-terminal-emulator. That could be > done at build-time: > | Makefile.am:-DXTERM=@XTERM@ \ > | configure.ac:DEFAULT_XTERM=xterm > | configure.ac:AS_HELP_STRING([--with-xterm=XTERM], [Path to xterm]), This is still true. Since #557138 was fixed, d/rules even passes --with-xterm=/usr/bin/xterm.
Processed: Re: Bug#1077893: xserver-xorg-video-qxl: Add Appstream metainfo announcing HW support
Processing control commands: > forwarded -1 > https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/merge_requests/21 Bug #1077893 [xserver-xorg-video-qxl] xserver-xorg-video-qxl: Add Appstream metainfo announcing HW support Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/merge_requests/21'. -- 1077893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1077893: xserver-xorg-video-qxl: Add Appstream metainfo announcing HW support
Control: forwarded -1 https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/merge_requests/21 It is now sent upstream. -- Happy hacking Petter Reinholdtsen
Processed: Re: Bug#840881: xserver-xorg-video-vmware: Please announce supported hardware using AppStream
Processing control commands: > forwarded -1 > https://gitlab.freedesktop.org/xorg/driver/xf86-video-vmware/-/merge_requests/15 Bug #840881 [xserver-xorg-video-vmware] xserver-xorg-video-vmware: Please announce supported hardware using AppStream Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/xorg/driver/xf86-video-vmware/-/merge_requests/15'. -- 840881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840881: xserver-xorg-video-vmware: Please announce supported hardware using AppStream
Control: forwarded -1 https://gitlab.freedesktop.org/xorg/driver/xf86-video-vmware/-/merge_requests/15 The patch is now sent upstream. -- Happy hacking Petter Reinholdtsen
