Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-15 Thread Diederik de Haas
On Mon Aug 12, 2024 at 1:05 PM CEST, Faidon Liambotis wrote: > On Sun, Aug 11, 2024 at 12:31:21PM -0400, Reinhard Tartler wrote: > > But you are right, ultimately this decision is up to the maintainer to make. > > Maintainer here :) > > For this particular case, I think removing -Werror made sense

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-12 Thread Faidon Liambotis
On Sun, Aug 11, 2024 at 12:31:21PM -0400, Reinhard Tartler wrote: > But you are right, ultimately this decision is up to the maintainer to make. Maintainer here :) First of all, thanks to the both of you for caring enough about this package to file bugs, NMU and argue about its bugs! It's helpful

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-12 Thread Diederik de Haas
On Sun Aug 11, 2024 at 6:31 PM CEST, Reinhard Tartler wrote: > I'm afraid we'll have to agree to disagree Agreed signature.asc Description: PGP signature

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-11 Thread Reinhard Tartler
On 2024-08-11 11:50, Diederik de Haas wrote: For Debian, I do think that this workaround is acceptable, at least for the purposes of allowing further testing in the "testing" Distribution, so that we get additional datapoints whether there actually are runtime issues that stem from unitialized

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-11 Thread Reinhard Tartler
On 2024-08-11 11:50, Diederik de Haas wrote: If you can make the argument that a specific warning can be ignored, you could override that specific warning with a clear explanation why that's OK in this particular case. This patch OTOH essentially says to ignore ALL warnings. Please find an

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-11 Thread Diederik de Haas
On Sun Aug 11, 2024 at 4:56 PM CEST, Reinhard Tartler wrote: > On 2024-08-11 08:55, Diederik de Haas wrote: > > On 03 Aug 2024 11:08:58 -0400 Reinhard Tartler > > wrote: > >> I noticed this package is listed as low-NMU. As such, I'm taking the > >> liberty of uploading the following patch as NMU t

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-11 Thread Reinhard Tartler
On 2024-08-11 08:55, Diederik de Haas wrote: On 03 Aug 2024 11:08:58 -0400 Reinhard Tartler wrote: I noticed this package is listed as low-NMU. As such, I'm taking the liberty of uploading the following patch as NMU to sid: ... new file debian/patches/don-t-fail-on-unknown-gcc-warnings.patch

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-11 Thread Diederik de Haas
On 03 Aug 2024 11:08:58 -0400 Reinhard Tartler wrote: > I noticed this package is listed as low-NMU. As such, I'm taking the > liberty of uploading the following patch as NMU to sid: > ... > new file debian/patches/don-t-fail-on-unknown-gcc-warnings.patch > @@ -0,0 +1,20 @@ > +From: Reinhard Tar

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-08-03 Thread Reinhard Tartler
I noticed this package is listed as low-NMU. As such, I'm taking the liberty of uploading the following patch as NMU to sid: 3 files changed, 28 insertions(+) debian/changelog | 7 +++ .../patches/don-t-fail-on-unknown-gcc-warnings.patch | 20

Bug#1075633: wasmedge: ftbfs with GCC-14

2024-07-27 Thread Diederik de Haas
On Wed, 03 Jul 2024 12:47:52 + Matthias Klose wrote: > Package: src:wasmedge > Version: 0.13.5+dfsg-1 > Usertags: ftbfs-gcc-14 > > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The > severity of this report will