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 to testing due to a blocking bug in glslang (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062799). This bug in glslang is now fixed with the last upload. I'm a beginner regarding this kind transition / blocking bug / CI, so I don't know how this bug can be solved... I don't know if it helps, but I have a RFS (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072181) for a new version of shaderc (which changes nothing about this bug). You can see on Salsa that autopkgtests pass with the version of glslang available in unstable: https://salsa.debian.org/debian/shaderc/-/pipelines/683648. Philippe.
