Bug#1069382: libxcb: FTBFS on arm64: KeyError: 'xcb_redirect_t'
Is there any way to fix or work around this? It's been blocking new version of obs-studio from entering testing for a while. Thanks! Shmerl.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Mon, 6 May 2024 01:28:47 +0300 Jussi Pakkanen wrote: > Filed: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070470 > Thanks! Do you think it's worth it it to file the bug to rust upstream too: https://github.com/rust-lang/rust/issues May be wider Rust developers can have an insight. Or it's something very Debian specific? Shmerl.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Sat, 4 May 2024 21:10:10 +0300 Jussi Pakkanen wrote: > The script runs fine on x64_64 but fails on arm64 (and probably also > x86, but I did not test it). This would imply something wonky going on > in the toolchain. The question then becomes where this should be > reported to. May be for rustc? It's worth filing the bug if it's not clear what the root cause is. If it's not really rustc, developers will point that out. Regards, Shmerl.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Thu, 2 May 2024 19:05:22 +0300 Jussi Pakkanen wrote: > > Along the way I found other bugs, such as bindgen not working at all > out of the box. I filed > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070241 for that. > > All in all this is getting into very deep Debian toolchain magic, of > which I have little knowledge. :( > If real solution for this requires upstream involvement, may be it's worth disabling these tests, until upstream is actually not broken? That would at least move things forward, otherwise it might be stuck for who knows how long? I don't know what's the usual recommended approach for handling such cases. Regards, Shmerl.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Mon, 26 Feb 2024 19:53:49 +0100 Fabio Pedretti wrote: > Ubuntu fixed it with this patch: > https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz > Can this fix be added to Debian? Meson has been stuck without moving to testing for a very long time and now it seems to be stalling Mesa in result too. Shmerl.
Bug#1042050: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4:(.text.startup+0x3): undefined reference to `hidden_function'
On Tue, 1 Aug 2023 22:55:02 +0300 Jussi Pakkanen wrote: > On Wed, 26 Jul 2023 at 00:16, Lucas Nussbaum wrote: > > This is actually a bug in gobject-introspection. It has already been > fixed upstream. Dunno what the schedule is for getting that into a > release and on to Debian. > Can this be applied for now as a patch until upstream makes a new tag (which can be a while)? https://gitlab.gnome.org/GNOME/gobject-introspection/-/commit/bf96a92ef263820d40e233814a46932cae00db41 Stuck Meson is blocking a bunch of packages from being updated in testing. Regards, Shmerl.
Bug#1025659: libgl1-mesa-dri: mesa causes xorg segfault; regression against 22.2.0-1
On Fri, 23 Dec 2022 14:53:02 +0100 Fabio Pedretti wrote: > Is this still an issue with 22.3.1-1? If that helps, I have one Intel laptop with Haswell GPU and it works fine with Mesa 22.3.1 (KDE Plasma). Shmerl.
Bug#1002872: Can this be unblocked now?
Looks like it should be just a build time config switch fix. Shmerl.
Bug#943623: Latest llvm10 snapshot still fails with Mesa master
On Tue, 12 Nov 2019 18:11:10 +0100 Sylvestre Ledru wrote: > > https://github.com/llvm/llvm-project/commit/343597789eba1e6482e130b0c1b0818b1432d311 > This is unrelated. Thanks for the clarification, I followed one of the links you posted above, and thought it was related. > I am aware of the issue. No resend the same content as the bug. > It was a long week end here and I have a $$$ job. > > Don't hesitate to step in to help, this is opensource ;) Thanks! Do you have any hints about what to experiment with to address it? I'm quite a loss at what could be the source of this. Best regards, Shmerl.
Bug#943623: Latest llvm10 snapshot still fails with Mesa master
To follow up. According to https://bugs.llvm.org/show_bug.cgi?id=43722#c5, the issue was fixed 5 days ago in https://github.com/llvm/llvm-project/commit/343597789eba1e6482e130b0c1b0818b1432d311 But latest snapshot from http://apt.llvm.org/unstable/pool/main/l/llvm-toolchain-snapshot/ (from 2019-11-11), still fails to work with Mesa master / gcc 9 like this: /usr/bin/ld: /usr/lib/llvm-10/lib/libLLVMAMDGPUDisassembler.a: error adding symbols: archive has no index; run ranlib to add one collect2: error: ld returned 1 exit status Is there something still missing?
Bug#943623: Any idea how to fix this?
This issue currently breaks building Mesa master with llvm10 snapshot from http://apt.llvm.org/unstable (in Debian testing).
