Le 30/05/2024 à 22:25, Paul Gevers a écrit :
Currently, shaderc 2023.2-1 is in testing. This version suffers from an
"undefined symbol" bug
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070983). This bug is
fixed in version 2023.8-1 which is now in unstable.
Can you please elaborate
Hello,
Well, this issue is "normal".
Currently, shaderc 2023.2-1 is in testing. This version suffers from an
"undefined symbol" bug
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070983). This bug is
fixed in version 2023.8-1 which is now in unstable. However, this
version never migrated
Hello,
I realized this bug prevents shaderc from migrating to testing.
Please have a look on my MR
(https://salsa.debian.org/xorg-team/vulkan/glslang/-/merge_requests/6),
which (among other things) fixes this bug.
Thanks,
Philippe.
Hello,
I think this is fixed in glslang/14.0.0-2:
pkg-config --libs glslang
-lglslang -lMachineIndependent -lOSDependent -lSPVRemapper -lpthread
Also based on what is in changelog of this last version of glslang-dev.
Philippe.
Sorry, I didn’t notice it was already reported in bugs 1011739 and 1010421
against ldc...
Source: gir-to-d
Version: 0.22.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: phil.sw...@gmx.fr
Dear Maintainer,
On an up-to-date Sid, gir-to-d fails to build from source:
% apt source gir-to-d
...
% sudo apt
Package: ruby-net-sftp
Version: 1:3.0.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Control: affects -1 vagrant
Dear Maintainer,
I cannot use Vagrant anymore, and it turns out it comes from the ugprade
of ruby-net-ssh to version 7.0.1 which doesn't satisfy the
7 matches
Mail list logo