Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Thu, 9 May 2024 at 19:51, Shmerl wrote: > 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? I don't use Rust, but I would imagine that if someone manages to replicate the issue with an up to date rustup or whatever it is that that people use to get their up to date toolchain, then it might make sense to for them to report it upstream.
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 Sun, 5 May 2024 at 04:33, Shmerl wrote: > 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. Filed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070470
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 Sat, 4 May 2024 at 13:27, Jussi Pakkanen wrote: > Disabling tests is also not a great because it just hides the bug. > Thus other packages that actually use this functionality are going to > hit this eventually and file more bugs on Meson. That is a waste of > everybody's time and energy. I managed to replicate this bug without Meson. Attached is sample code plus a build script that runs a few compilation commands in a shell script. 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. rustcmixbug.tar.gz Description: GNU Zip compressed data
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Fri, 3 May 2024 at 06:42, Shmerl wrote: > 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 am the upstream. All of this works in our CI and other distros meaning that the only person who can reasonably fix this is also me. Disabling tests is also not a great because it just hides the bug. Thus other packages that actually use this functionality are going to hit this eventually and file more bugs on Meson. That is a waste of everybody's time and energy.
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 Thu, 2 May 2024 at 01:48, Shmerl 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. I looked into this and the answer is sadly no. That patch explicitly adds -lc to every link which breaks other tests that depend on it not being there. These tests have been added after Ubuntu made that change, so they won't show up there. They will once they update Meson to a newer version. 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. :(
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#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
Ubuntu fixed it with this patch: https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Thu, 21 Dec 2023 at 14:57, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 30 days as having a Release Critical bug in > testing [1]. Your package src:meson has been trying to migrate for 31 > days [2]. Hence, I am filing this bug. The version in unstable fails its > own autopkgtest on arm64 and i386 (and armel, but that's not a regression). The reason for this is the following (on i86, but the same applies to arm64 too): 2428s = note: /usr/bin/ld: /usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inflate.o): in function `.L707': 2428s (.text+0x2c79): undefined reference to `__stack_chk_fail_local' 2428s /usr/bin/ld: /usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inflate.o): in function `inflateSync': 2428s (.text+0x3471): undefined reference to `__stack_chk_fail_local' 2428s /usr/bin/ld: /usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inftrees.o): in function `inflate_table': 2428s (.text+0xea7): undefined reference to `__stack_chk_fail_local' 2428s /usr/bin/ld: prog: hidden symbol `__stack_chk_fail_local' isn't defined 2428s /usr/bin/ld: final link failed: bad value 2428s collect2: error: ld returned 1 exit status This happens when mixing code compiled natively with code compiled with rustc. To the best of our knowledge, this is a Rust toolchain bug because the exact same compilation commands work on other platforms. The missing symbol has double leading underscores implying it is a compiler internal thing and the test we are using does not attempt to do anything magical, only compile and link C and Rust code together in the same binary.
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
Source: meson Version: 1.2.3-1 Severity: serious Control: close -1 1.3.0-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:meson has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest on arm64 and i386 (and armel, but that's not a regression). If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=meson OpenPGP_signature.asc Description: OpenPGP digital signature
