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
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.
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
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
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
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
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
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
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
Ubuntu fixed it with this patch:
https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz
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
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
12 matches
Mail list logo
