Package: guitarix
Version: 0.42.1+dfsg1-1
Severity: serious
Tags: patch
Justification: Policy 12.5
Dear Debian Multimedia Maintainers,
I noticed that the [debian/copyright] file for guitarix states that
two images ('data/Layout.svg' and 'data/stereo.svg') are under
CC-BY-1.0, which does not meet
Hi,
I just created a sid chroot with experimental repositories.
It compiles fine here with gcc-11
CC=gcc-11 CFLAGS="-march=x86-64-v2" ./configure && make -j20
... but I am going to try your compiler, too.
regards,
Joël
On Wed, Mar 3, 2021 at 5:27 PM Matthias Klose wrote:
>
> On 3/3/21 5:20
On 3/3/21 5:20 PM, Joël Krähemann wrote:
> Hi,
>
> I am not able to reproduce with debian sid gcc-10.
I'll update gcc-10 in experimental. The compiler used for the test rebuild was
deb [trusted=yes] http://people.debian.org/~doko/gcc/gcc10-v2 ./
deb [trusted=yes]
Hi,
I am not able to reproduce with debian sid gcc-10.
gcc-10/unstable,now 10.2.1-6 amd64 [installed]
GNU C compiler
just built successfully gsequencer-v3.7.38
CFLAGS="-march=x86-64-v2" ./configure && make -j20
regards,
Joël
On Wed, Mar 3, 2021 at 4:15 PM Matthias Klose wrote:
>
>
Package: src:vlc
Version: 3.0.12-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another
Package: src:synfigstudio
Version: 1.4.0+dfsg-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in
Package: src:synfig
Version: 1.4.0+dfsg-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another
Package: src:photoflow
Version: 0.2.8+git20200114-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix
Package: src:ocp
Version: 1:0.2.2+ds-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another
Package: src:faust
Version: 2.30.5~ds0-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another
Package: src:libebml
Version: 1.4.2-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another
Package: src:etl
Version: 1.4.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package
Package: src:drumgizmo
Version: 0.9.19-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another
Package: src:din
Version: 5.2.1-6
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package
Package: src:cheesecutter
Version: 2.9+git20191210-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix
Package: src:audacious
Version: 4.0.5-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another
Hi,
I just compiled gsequencer-3.7.38 and disabled hardening options.
I think it is duplicated of Bug#983868
--- Makefile.am.orig2021-03-03 16:57:30.680130313 +0100
+++ Makefile.am2021-03-03 16:57:38.428171218 +0100
@@ -21,7 +21,7 @@
if WITH_OSXAPI
AM_CPPFLAGS +=
Package: src:gsequencer
Version: 3.7.38-1
Severity: minor
User: debian-...@lists.debian.org
Usertags: ftbfs-x86-64-v2
Starting with LLVM 12 and GCC 11 (and backported to gcc-10 for Debian),
GCC introduces optimizations for new micro-architecture levels from
the x86-64 psABI. Filing these bug
Hi all,
There is a DEP3 patch in the repository.
https://salsa.debian.org/multimedia-team/gsequencer/-/blob/master/debian/patches/patch-ags_midi_buffer_util-c.diff
My opinion is you can pass NULL to these functions but actually you
shouldn't do this.
regards,
Joël
On Wed, Mar 3, 2021 at 10:45
On Wed, 3 Mar 2021, 10:30 am Joël Krähemann, wrote:
> I am going to provide another tarball including this fix.
>
There is no need to stage this for bullseye, it can be fixed later.
(Also because at this point it would require a release unblock...)
Hi,
I just tested with gcc-9, the patch should fix the problems with
ags_midi_buffer_util.c.
I would call it a false positive, it is good that GCC complains but it
doesn't actually
know how a MIDI parser is implemented.
If you need a higher-level API, I recommend you:
Well, that's not what the GCC developers think. The warning is there in GCC 9
and GCC 11 as well. The name of the option even implies that this is a "maybe".
Forcing it to become an error with -Werror might be wrong, so if you build with
-Werrer, build with -Wno-error=maybe-uninitialized as
22 matches
Mail list logo
