Bug#1061795: csound fails its autopkg tests with Python 3.12

[Matthias Klose]

Package: src:csound
Version: 1:6.18.1+dfsg-1
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

With python3-defaults from experimental, the package fails its autopkg 
tests:


[...]

3648s autopkgtest [14:30:36]: test command5:  - - - - - - - - - - 
results - - - - - - - - - -

3648s autopkgtest [14:30:36]:  summary
3648s python3-csound   PASS (superficial)
3648s upstream-testsuite   FAIL stderr: 
/tmp/autopkgtest.TOrCP4/build.Mx9/src/tests/commandline/test.py:196: 
SyntaxWarning: invalid escape sequence '\c'

3648s command1 PASS

Bug#1061422: add patch

[Matthias Klose]

Control: tags -1 + patch

https://launchpadlibrarian.net/711104605/blender_4.0.2+dfsg-1ubuntu3_4.0.2+dfsg-1ubuntu4.diff.gz

Bug#1061422: blender ftbfs with Python 3.12 as the default

[Matthias Klose]

Package: src:blender
Version: 4.0.2+dfsg-1
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

blender ftbfs with Python 3.12 as the default, Debian doesn't have yet 
all dependencies built for 3.12, so here is the log from Ubuntu for now.


complete build logs at
https://launchpad.net/ubuntu/+source/blender/4.0.2+dfsg-1ubuntu3


/<>/source/blender/freestyle/intern/python/BPy_IntegrationType.cpp:192:58: 
error: too many initializers for ‘_object::’

  192 | PyVarObject_HEAD_INIT(_Type, 1){MEAN}};
  |  ^
/<>/source/blender/freestyle/intern/python/BPy_IntegrationType.cpp:193:97: 
error: too many initializers for ‘_object::’
  193 | static PyLongObject _IntegrationType_MIN = 
{PyVarObject_HEAD_INIT(_Type, 1){MIN}};
  | 
^
/<>/source/blender/freestyle/intern/python/BPy_IntegrationType.cpp:194:97: 
error: too many initializers for ‘_object::’
  194 | static PyLongObject _IntegrationType_MAX = 
{PyVarObject_HEAD_INIT(_Type, 1){MAX}};
  | 
^
/<>/source/blender/freestyle/intern/python/BPy_IntegrationType.cpp:196:59: 
error: too many initializers for ‘_object::’

  196 | PyVarObject_HEAD_INIT(_Type, 1){FIRST}};
  |   ^
/<>/source/blender/freestyle/intern/python/BPy_IntegrationType.cpp:198:58: 
error: too many initializers for ‘_object::’

  198 | PyVarObject_HEAD_INIT(_Type, 1){LAST}};
  |  ^
make[3]: *** 
[source/blender/freestyle/CMakeFiles/bf_freestyle.dir/build.make:560: 
source/blender/freestyle/CMakeFiles/bf_freestyle.dir/intern/python/BPy_IntegrationType.cpp.o] 
Error 1

make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:7778: 
source/blender/freestyle/CMakeFiles/bf_freestyle.dir/all] Error 2

make[2]: *** Waiting for unfinished jobs

Bug#1061420: obs-studio won't migrate, missing build on ppc64el

[Matthias Klose]

Package: src:obs-studio
Version: 30.0.2+dfsg-2
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

obs-studio won't migrate, missing build on ppc64el, because luajit isn't 
built anymore on ppc64el.


This will block python3-defaults, when making 3.12 the default Python 
version.

Bug#1056839: pyliblo: ftbfs with cython 3.0.x

[Matthias Klose]

Package: src:pyliblo
Version: 0.10.0-5.1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython3

[This bug is targeted to the upcoming trixie release]

The package fails to build in a test rebuild on at least arm64 with
cython 3.0.5, but succeeds to build with cython 0.29.36.  Please
update the package to build with cython 3.0.5 (available in experimental).

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.

Build logs building with cython 3.0.5 can be found at
https://people.debian.org/~stefanor/cython3/cython-3.0.5/

See also https://lists.debian.org/debian-python/2023/11/msg00034.html

Bug#1056496: python-pyknon's autopkg tests fail with Python 3.12

[Matthias Klose]

Package: src:python-pyknon
Version: 1.2-5
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

python-pyknon's autopkg tests fail with Python 3.12:

[...]
151s === FAILURES 
===
151s __ TestMIDIUtils.testAddNote 
___

151s
151s self = 
151s
151s def testAddNote(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addNote(0, 0, 100,0,1,100)
151s >   self.assertEquals(MyMIDI.tracks[0].eventList[0].type, "note")
151s E   AttributeError: 'TestMIDIUtils' object has no attribute 
'assertEquals'. Did you mean: 'assertEqual'?

151s
151s test_midi.py:45: AttributeError
151s _ TestMIDIUtils.testDeinterleaveNotes 
__

151s
151s self = 
151s
151s def testDeinterleaveNotes(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addNote(0, 0, 100, 0, 2, 100)
151s MyMIDI.addNote(0, 0, 100, 1, 2, 100)
151s MyMIDI.close()
151s >   self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type, 
'NoteOn')
151s E   AttributeError: 'TestMIDIUtils' object has no attribute 
'assertEquals'. Did you mean: 'assertEqual'?

151s
151s test_midi.py:56: AttributeError
151s _ TestMIDIUtils.testFrequency 
__

151s
151s self = 
151s
151s def testFrequency(self):
151s freq = frequencyTransform(8.1758)
151s >   self.assertEquals(freq[0],  0x00)
151s E   AttributeError: 'TestMIDIUtils' object has no attribute 
'assertEquals'. Did you mean: 'assertEqual'?

151s
151s test_midi.py:116: AttributeError
151s ___ TestMIDIUtils.testSysEx 


151s
151s self = 
151s
151s def testSysEx(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addSysEx(0,0, 0, struct.pack('>B', 0x01))
151s MyMIDI.close()
151s >   self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type, 
'SysEx')
151s E   AttributeError: 'TestMIDIUtils' object has no attribute 
'assertEquals'. Did you mean: 'assertEqual'?

151s
151s test_midi.py:192: AttributeError
151s _ TestMIDIUtils.testTimeShift 
__

151s
151s self = 
151s
151s def testTimeShift(self):
151s
151s # With one track
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addNote(0, 0, 100, 5, 1, 100)
151s MyMIDI.close()
151s >   self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type, 
'NoteOn')
151s E   AttributeError: 'TestMIDIUtils' object has no attribute 
'assertEquals'. Did you mean: 'assertEqual'?

151s
151s test_midi.py:71: AttributeError
151s ___ TestMIDIUtils.testTuning 
___

151s
151s self = 
151s
151s def testTuning(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.changeNoteTuning(0, [(1, 440), (2, 880)])
151s MyMIDI.close()
151s >   self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type, 
'UniversalSysEx')
151s E   AttributeError: 'TestMIDIUtils' object has no attribute 
'assertEquals'. Did you mean: 'assertEqual'?

151s
151s test_midi.py:219: AttributeError
151s ___ TestMIDIUtils.testUniversalSysEx 
___

151s
151s self = 
151s
151s def testUniversalSysEx(self):
151s MyMIDI = MIDIFile(1)
151s MyMIDI.addUniversalSysEx(0,0, 1, 2, struct.pack('>B', 0x01))
151s MyMIDI.close()
151s >   self.assertEquals(MyMIDI.tracks[0].MIDIEventList[0].type, 
'UniversalSysEx')
151s E   AttributeError: 'TestMIDIUtils' object has no attribute 
'assertEquals'. Did you mean: 'assertEqual'?

151s
151s test_midi.py:204: AttributeError
151s ___ TestMIDIUtils.testWriteVarLength 
___

151s
151s self = 
151s
151s def testWriteVarLength(self):
151s >   self.assertEquals(writeVarLength(0x70), [0x70])
151s E   AttributeError: 'TestMIDIUtils' object has no attribute 
'assertEquals'. Did you mean: 'assertEqual'?

151s
151s test_midi.py:37: AttributeError
151s === warnings summary 
===

151s test_genmidi.py::TestWriteMidi::test_write_midifile
151s   /tmp/autopkgtest.tzc68l/autopkgtest_tmp/test/test_genmidi.py:41: 
ResourceWarning: unclosed file <_io.BufferedRandom name=11>

151s midi.write(tempfile.TemporaryFile())
151s   Enable tracemalloc to get traceback where the object was allocated.
151s   See 
https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings 
for more info.

151s
151s -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
151s === 8 failed, 101 passed, 1 warning in 0.23s 
===

Bug#1037910: zynaddsubfx: ftbfs with GCC-13

[Matthias Klose]

Package: src:zynaddsubfx
Version: 3.0.6-5
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/zynaddsubfx_3.0.6-5_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
  |  ~^~~
   55 |__glibc_objsize (__s), __fmt,
  |~
   56 |__va_arg_pack ());
  |~
[ 21%] Building CXX object src/UI/CMakeFiles/zynaddsubfx_gui.dir/NioUI.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/UI && /usr/bin/c++ -DALSA=1 
-DASM_F2I_YES -DFLTK_GUI -DHAS_X11=1 -DHAVE_ASYNC=1 -DHAVE_CPP_STD_COMPLEX=1 
-DHAVE_SCHEDULER=1 -DJACK=1 -DOSS=1 -DUSE_NSM=1 -DVERSION=\"\" 
-I/<>/rtosc/include -I/<>/obj-x86_64-linux-gnu/src 
-I/usr/lib/fltk -I/<>/src/UI 
-I/<>/obj-x86_64-linux-gnu/src/UI -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-Wno-unused-parameter -O3 -ffast-math -fomit-frame-pointer  -msse -msse2 
-mfpmath=sse   -Wall -Wextra -fPIC -MD -MT 
src/UI/CMakeFiles/zynaddsubfx_gui.dir/NioUI.cpp.o -MF 
CMakeFiles/zynaddsubfx_gui.dir/NioUI.cpp.o.d -o 
CMakeFiles/zynaddsubfx_gui.dir/NioUI.cpp.o -c /<>/src/UI/NioUI.cpp
[ 21%] Building CXX object src/UI/CMakeFiles/zynaddsubfx_gui.dir/TipWin.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/UI && /usr/bin/c++ -DALSA=1 
-DASM_F2I_YES -DFLTK_GUI -DHAS_X11=1 -DHAVE_ASYNC=1 -DHAVE_CPP_STD_COMPLEX=1 
-DHAVE_SCHEDULER=1 -DJACK=1 -DOSS=1 -DUSE_NSM=1 -DVERSION=\"\" 
-I/<>/rtosc/include -I/<>/obj-x86_64-linux-gnu/src 
-I/usr/lib/fltk -I/<>/src/UI 
-I/<>/obj-x86_64-linux-gnu/src/UI -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-Wno-unused-parameter -O3 -ffast-math -fomit-frame-pointer  -msse -msse2 
-mfpmath=sse   -Wall -Wextra -fPIC -MD -MT 
src/UI/CMakeFiles/zynaddsubfx_gui.dir/TipWin.cpp.o -MF 
CMakeFiles/zynaddsubfx_gui.dir/TipWin.cpp.o.d -o 
CMakeFiles/zynaddsubfx_gui.dir/TipWin.cpp.o -c 
/<>/src/UI/TipWin.cpp
[ 22%] Building CXX object 
src/UI/CMakeFiles/zynaddsubfx_gui.dir/WidgetPDial.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/UI && /usr/bin/c++ -DALSA=1 
-DASM_F2I_YES -DFLTK_GUI -DHAS_X11=1 -DHAVE_ASYNC=1 -DHAVE_CPP_STD_COMPLEX=1 
-DHAVE_SCHEDULER=1 -DJACK=1 -DOSS=1 -DUSE_NSM=1 -DVERSION=\"\" 
-I/<>/rtosc/include -I/<>/obj-x86_64-linux-gnu/src 
-I/usr/lib/fltk -I/<>/src/UI 
-I/<>/obj-x86_64-linux-gnu/src/UI -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-Wno-unused-parameter -O3 -ffast-math -fomit-frame-pointer  -msse -msse2 
-mfpmath=sse   -Wall -Wextra -fPIC -MD -MT 
src/UI/CMakeFiles/zynaddsubfx_gui.dir/WidgetPDial.cpp.o -MF 
CMakeFiles/zynaddsubfx_gui.dir/WidgetPDial.cpp.o.d -o 
CMakeFiles/zynaddsubfx_gui.dir/WidgetPDial.cpp.o -c 
/<>/src/UI/WidgetPDial.cpp
[ 22%] Building CXX object 
src/UI/CMakeFiles/zynaddsubfx_gui.dir/PartNameButton.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/UI && /usr/bin/c++ -DALSA=1 
-DASM_F2I_YES -DFLTK_GUI -DHAS_X11=1 -DHAVE_ASYNC=1 -DHAVE_CPP_STD_COMPLEX=1 
-DHAVE_SCHEDULER=1 -DJACK=1 -DOSS=1 -DUSE_NSM=1 -DVERSION=\"\" 
-I/<>/rtosc/include -I/<>/obj-x86_64-linux-gnu/src 
-I/usr/lib/fltk -I/<>/src/UI 
-I/<>/obj-x86_64-linux-gnu/src/UI -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-Wno-unused-parameter -O3 -ffast-math -fomit-frame-pointer  -msse -msse2 
-mfpmath=sse   -Wall -Wextra -fPIC -MD -MT 
src/UI/CMakeFiles/zynaddsubfx_gui.dir/PartNameButton.cpp.o -MF 
CMakeFiles/zynaddsubfx_gui.dir/PartNameButton.cpp.o.d -o 
CMakeFiles/zynaddsubfx_gui.dir/PartNameButton.cpp.o -c 

Bug#1037913: zytrax: ftbfs with GCC-13

[Matthias Klose]

Package: src:zytrax
Version: 0+git20201215-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/zytrax_0+git20201215-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
globals/base64.cpp:21:9: note: ‘uint8_t’ is defined in header ‘’; did 
you forget to ‘#include ’?
globals/base64.cpp:22:16: error: expected ‘;’ before ‘char_array_4’
   22 | uint8_t char_array_4[4];
  |^
  |;
globals/base64.cpp:25:17: error: ‘char_array_3’ was not declared in this scope
   25 | char_array_3[i++] = *(buf++);
  | ^~~~
globals/base64.cpp:25:39: error: ‘buf’ was not declared in this scope
   25 | char_array_3[i++] = *(buf++);
  |   ^~~
globals/base64.cpp:27:25: error: ‘char_array_4’ was not declared in this scope
   27 | char_array_4[0] = (char_array_3[0] & 0xfc) >> 2;
  | ^~~~
globals/base64.cpp:40:25: error: ‘char_array_3’ was not declared in this scope
   40 | char_array_3[j] = '\0';
  | ^~~~
globals/base64.cpp:42:17: error: ‘char_array_4’ was not declared in this scope
   42 | char_array_4[0] = (char_array_3[0] & 0xfc) >> 2;
  | ^~~~
globals/base64.cpp:42:36: error: ‘char_array_3’ was not declared in this scope
   42 | char_array_4[0] = (char_array_3[0] & 0xfc) >> 2;
  |^~~~
globals/base64.cpp: At global scope:
globals/base64.cpp:57:8: error: ‘uint8_t’ was not declared in this scope
   57 | Vector base64_decode(std::string const _string) {
  |^~~
globals/base64.cpp:57:8: note: ‘uint8_t’ is defined in header ‘’; did 
you forget to ‘#include ’?
globals/base64.cpp:57:15: error: template argument 1 is invalid
   57 | Vector base64_decode(std::string const _string) {
  |   ^
globals/base64.cpp: In function ‘int base64_decode(const std::string&)’:
globals/base64.cpp:62:9: error: ‘uint8_t’ was not declared in this scope
   62 | uint8_t char_array_4[4], char_array_3[3];
  | ^~~
globals/base64.cpp:62:9: note: ‘uint8_t’ is defined in header ‘’; did 
you forget to ‘#include ’?
globals/base64.cpp:65:69: error: ‘is_base64’ cannot be used as a function
   65 | while (in_len-- && (encoded_string[in_] != '=') && 
is_base64(encoded_string[in_])) {
  |
~^
globals/base64.cpp:66:17: error: ‘char_array_4’ was not declared in this scope
   66 | char_array_4[i++] = encoded_string[in_];
  | ^~~~
globals/base64.cpp:72:25: error: ‘char_array_3’ was not declared in this scope
   72 | char_array_3[0] = (char_array_4[0] << 2) + 
((char_array_4[1] & 0x30) >> 4);
  | ^~~~
globals/base64.cpp:77:37: error: request for member ‘push_back’ in ‘ret’, which 
is of non-class type ‘int’
   77 | ret.push_back(char_array_3[i]);
  | ^
globals/base64.cpp:84:25: error: ‘char_array_4’ was not declared in this scope
   84 | char_array_4[j] = 0;
  | ^~~~
globals/base64.cpp:87:25: error: ‘char_array_4’ was not declared in this scope
   87 | char_array_4[j] = 
base64_chars.find(char_array_4[j]);
  | ^~~~
globals/base64.cpp:89:17: error: ‘char_array_3’ was not declared in this scope
   89 | char_array_3[0] = (char_array_4[0] << 2) + 
((char_array_4[1] & 0x30) >> 4);
  | ^~~~

Bug#1037900: wxsvg: ftbfs with GCC-13

[Matthias Klose]

Package: src:wxsvg
Version: 2:1.5.24+dfsg-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/wxsvg_1.5.24+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
config.status: creating include/Makefile
config.status: creating include/wxSVGXML/Makefile
config.status: creating include/wxSVG/Makefile
config.status: creating src/svgxml/Makefile
config.status: creating src/Makefile
config.status: creating src/cairo/Makefile
config.status: creating src/skia/Makefile
config.status: creating svgview/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j8
make[1]: Entering directory '/<>'
Making all in src
make[2]: Entering directory '/<>/src'
Making all in svgxml
make[3]: Entering directory '/<>/src/svgxml'
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ 
-DPACKAGE_NAME=\"wxsvg\" -DPACKAGE_TARNAME=\"wxsvg\" 
-DPACKAGE_VERSION=\"1.5.24\" -DPACKAGE_STRING=\"wxsvg\ 1.5.24\" 
-DPACKAGE_BUGREPORT=\"http://wxsvg.sourceforge.net/\; -DPACKAGE_URL=\"\" 
-DPACKAGE=\"wxsvg\" -DVERSION=\"1.5.24\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I.  -I../../include/wxSVGXML 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16  
-DUSE_RENDER_CAIRO -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
-I/usr/include/free
 type2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -pthread   
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -I/usr/include/wx-3.2 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread   -DUSE_LIBAV 
-I/usr/include/x86_64-linux-gnu  -c -o svgxml.lo svgxml.cpp
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ 
-DPACKAGE_NAME=\"wxsvg\" -DPACKAGE_TARNAME=\"wxsvg\" 
-DPACKAGE_VERSION=\"1.5.24\" -DPACKAGE_STRING=\"wxsvg\ 1.5.24\" 
-DPACKAGE_BUGREPORT=\"http://wxsvg.sourceforge.net/\; -DPACKAGE_URL=\"\" 
-DPACKAGE=\"wxsvg\" -DVERSION=\"1.5.24\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I.  -I../../include/wxSVGXML 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16  
-DUSE_RENDER_CAIRO -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
-I/usr/include/free
 type2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -pthread   
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -I/usr/include/wx-3.2 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread   -DUSE_LIBAV 
-I/usr/include/x86_64-linux-gnu  -c -o svgxmlhelpr.lo svgxmlhelpr.cpp
libtool: compile:  g++ -DPACKAGE_NAME=\"wxsvg\" -DPACKAGE_TARNAME=\"wxsvg\" 
-DPACKAGE_VERSION=\"1.5.24\" "-DPACKAGE_STRING=\"wxsvg 1.5.24\"" 
-DPACKAGE_BUGREPORT=\"http://wxsvg.sourceforge.net/\; -DPACKAGE_URL=\"\" 
-DPACKAGE=\"wxsvg\" -DVERSION=\"1.5.24\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 

Bug#1037883: vimix: ftbfs with GCC-13

[Matthias Klose]

Package: src:vimix
Version: 0.7.2+git20221123+ds-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/vimix_0.7.2+git20221123+ds-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
 from /<>/src/main.cpp:27:
/<>/src/Scene.h:135:27: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations]
  135 | struct hasId: public std::unary_function
  |   ^~
In file included from /usr/include/c++/13/string:49,
 from /<>/src/Settings.h:5,
 from /<>/src/main.cpp:26:
/usr/include/c++/13/bits/stl_function.h:117:12: note: declared here
  117 | struct unary_function
  |^~
In file included from /<>/src/Primitives.h:6,
 from /<>/src/Scene.cpp:31:
/<>/src/Scene.h:135:27: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations]
  135 | struct hasId: public std::unary_function
  |   ^~
In file included from /usr/include/c++/13/bits/refwrap.h:39,
 from /usr/include/c++/13/bits/shared_ptr_base.h:57,
 from /usr/include/c++/13/bits/shared_ptr.h:53,
 from /usr/include/c++/13/condition_variable:45,
 from /usr/include/c++/13/future:41,
 from /<>/src/Shader.h:4,
 from /<>/src/Scene.cpp:30:
/usr/include/c++/13/bits/stl_function.h:117:12: note: declared here
  117 | struct unary_function
  |^~
In file included from /<>/src/GarbageVisitor.h:6,
 from /<>/src/Scene.cpp:33:
/<>/src/Source.h:203:33: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations]
  203 | struct hasNode: public std::unary_function
  | ^~
/usr/include/c++/13/bits/stl_function.h:117:12: note: declared here
  117 | struct unary_function
  |^~
/<>/src/Source.h:211:33: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations]
  211 | struct hasName: public std::unary_function
  | ^~
/usr/include/c++/13/bits/stl_function.h:117:12: note: declared here
  117 | struct unary_function
  |^~
/<>/src/Source.h:221:31: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations]
  221 | struct hasId: public std::unary_function
  |   ^~
/usr/include/c++/13/bits/stl_function.h:117:12: note: declared here
  117 | struct unary_function
  |^~
/<>/src/Source.h:231:34: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations]
  231 | struct hasDepth: public std::unary_function
  |  ^~
/usr/include/c++/13/bits/stl_function.h:117:12: note: declared here
  117 | struct unary_function
  |^~
In file included from /<>/src/Primitives.h:6,
 from /<>/src/Primitives.cpp:38:
/<>/src/Scene.h:135:27: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations]
  135 | struct hasId: public std::unary_function
  |   ^~
In file included from /usr/include/c++/13/string:49,
 from /<>/src/ImageShader.h:4,
 from /<>/src/Primitives.cpp:31:
/usr/include/c++/13/bits/stl_function.h:117:12: note: declared here
  117 | struct unary_function
  |^~
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:245: src/CMakeFiles/vimix.dir/all] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[1]: *** 

Bug#1037799: opencollada: ftbfs with GCC-13

[Matthias Klose]

Package: src:opencollada
Version: 0.1.0~20180719.619d942+dfsg0-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/opencollada_0.1.0~20180719.619d942+dfsg0-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
[ 20%] Building CXX object 
Externals/MathMLSolver/CMakeFiles/MathMLSolver_static.dir/src/AST/MathMLASTConstantExpression.cpp.o
cd "/<>/debian/cmake/Externals/MathMLSolver" && /usr/bin/c++ 
-DGENERATEDSAXPARSER_XMLPARSER_LIBXML -DXMLPARSER_LIBXML 
-I"/<>/Externals/MathMLSolver/include" 
-I"/<>/Externals/MathMLSolver/include/AST" -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra 
-Wno-unknown-pragmas -Wno-switch -Wno-reorder -Wno-unused-parameter 
-Wno-ignored-qualifiers -fPIC -O3 -DNDEBUG -MD -MT 
Externals/MathMLSolver/CMakeFiles/MathMLSolver_static.dir/src/AST/MathMLASTConstantExpression.cpp.o
 -MF 
CMakeFiles/MathMLSolver_static.dir/src/AST/MathMLASTConstantExpression.cpp.o.d 
-o CMakeFiles/MathMLSolver_static.dir/src/AST/MathMLASTConstantExpression.cpp.o 
-c 
"/<>/Externals/MathMLSolver/src/AST/MathMLASTConstantExpression.cpp"
[ 20%] Building CXX object 
GeneratedSaxParser/CMakeFiles/GeneratedSaxParser_static.dir/src/GeneratedSaxParserParserError.cpp.o
cd "/<>/debian/cmake/GeneratedSaxParser" && /usr/bin/c++ 
-DGENERATEDSAXPARSER_XMLPARSER_LIBXML -DXMLPARSER_LIBXML 
-I"/<>/GeneratedSaxParser/include" -I/usr/include/libxml2 
-I"/<>/COLLADABaseUtils/include" 
-I"/<>/COLLADABaseUtils/include/Math" -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra 
-Wno-unknown-pragmas -Wno-switch -Wno-reorder -Wno-unused-parameter 
-Wno-ignored-qualifiers -fPIC -O3 -DNDEBUG -MD -MT 
GeneratedSaxParser/CMakeFiles/GeneratedSaxParser_static.dir/src/GeneratedSaxParserParserError.cpp.o
 -MF 
CMakeFiles/GeneratedSaxParser_static.dir/src/GeneratedSaxParserParserError.cpp.o.d
 -o 
CMakeFiles/GeneratedSaxParser_static.dir/src/GeneratedSaxParserParserError.cpp.o
 -c "/<>/GeneratedSaxParser/src/GeneratedSaxParserParserError.cpp"
[ 20%] Building CXX object 
Externals/MathMLSolver/CMakeFiles/MathMLSolver_static.dir/src/AST/MathMLASTArithmeticExpression.cpp.o
cd "/<>/debian/cmake/Externals/MathMLSolver" && /usr/bin/c++ 
-DGENERATEDSAXPARSER_XMLPARSER_LIBXML -DXMLPARSER_LIBXML 
-I"/<>/Externals/MathMLSolver/include" 
-I"/<>/Externals/MathMLSolver/include/AST" -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -Wextra 
-Wno-unknown-pragmas -Wno-switch -Wno-reorder -Wno-unused-parameter 
-Wno-ignored-qualifiers -fPIC -O3 -DNDEBUG -MD -MT 
Externals/MathMLSolver/CMakeFiles/MathMLSolver_static.dir/src/AST/MathMLASTArithmeticExpression.cpp.o
 -MF 
CMakeFiles/MathMLSolver_static.dir/src/AST/MathMLASTArithmeticExpression.cpp.o.d
 -o 
CMakeFiles/MathMLSolver_static.dir/src/AST/MathMLASTArithmeticExpression.cpp.o 
-c 
"/<>/Externals/MathMLSolver/src/AST/MathMLASTArithmeticExpression.cpp"
/<>/Externals/MathMLSolver/src/AST/MathMLASTConstantExpression.cpp:
 In copy constructor ‘MathML::AST::ConstantExpression::ConstantExpression(const 
MathML::AST::ConstantExpression&)’:
/<>/Externals/MathMLSolver/src/AST/MathMLASTConstantExpression.cpp:28:9:
 warning: base class ‘class MathML::AST::INode’ should be explicitly 
initialized in the copy constructor [-Wextra]
   28 | ConstantExpression::ConstantExpression( const 
ConstantExpression& ref )
  | ^~
[ 21%] Building CXX object 
GeneratedSaxParser/CMakeFiles/GeneratedSaxParser_static.dir/src/GeneratedSaxParserParserTemplateBase.cpp.o
cd "/<>/debian/cmake/GeneratedSaxParser" && /usr/bin/c++ 
-DGENERATEDSAXPARSER_XMLPARSER_LIBXML -DXMLPARSER_LIBXML 
-I"/<>/GeneratedSaxParser/include" -I/usr/include/libxml2 

Bug#1037730: libheif: ftbfs with GCC-13

[Matthias Klose]

Package: src:libheif
Version: 1.15.1-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/libheif_1.15.1-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f libheif/CMakeFiles/heif.dir/build.make 
libheif/CMakeFiles/heif.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/libheif 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/libheif 
/<>/obj-x86_64-linux-gnu/libheif/CMakeFiles/heif.dir/DependInfo.cmake
 --color=
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f libheif/CMakeFiles/heif.dir/build.make 
libheif/CMakeFiles/heif.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  2%] Building CXX object libheif/CMakeFiles/heif.dir/heif_context.cc.o
cd /<>/obj-x86_64-linux-gnu/libheif && /usr/bin/c++ 
-DENABLE_MULTITHREADING_SUPPORT=1 -DENABLE_PARALLEL_TILE_DECODING=1 
-DENABLE_PLUGIN_LOADING=1 -DHAVE_AOM_DECODER=1 -DHAVE_AOM_ENCODER=1 
-DHAVE_DAV1D=1 -DHAVE_LIBDE265=1 -DHAVE_UNISTD_H -DHAVE_VISIBILITY 
-DHAVE_X265=1 -DLIBHEIF_EXPORTS -DWITH_DEFLATE_HEADER_COMPRESSION=1 
-Dheif_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> 
-I/<>/include/libheif -I/<>/include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -fvisibility-inlines-hidden   -Wall -Werror -Wsign-compare 
-Wconversion -Wno-sign-conversion -Wno-error=conversion 
-Wno-error=unused-parameter -Wno-error=deprecated-declarations -std=c++11 -MD 
-MT libheif/CMakeFiles/heif.dir/heif_context.cc.o -MF 
CMakeFiles/heif.dir/heif_context.cc.o.d -o 
CMakeFiles/heif.dir/heif_context.cc.o -c /<>/libheif/heif_conte
 xt.cc
[  4%] Building CXX object libheif/CMakeFiles/heif.dir/box.cc.o
[  6%] Building CXX object libheif/CMakeFiles/heif.dir/bitstream.cc.o
[  8%] Building CXX object libheif/CMakeFiles/heif.dir/heif.cc.o
[ 10%] Building CXX object libheif/CMakeFiles/heif.dir/error.cc.o
[ 13%] Building CXX object libheif/CMakeFiles/heif.dir/heif_file.cc.o
cd /<>/obj-x86_64-linux-gnu/libheif && /usr/bin/c++ 
-DENABLE_MULTITHREADING_SUPPORT=1 -DENABLE_PARALLEL_TILE_DECODING=1 
-DENABLE_PLUGIN_LOADING=1 -DHAVE_AOM_DECODER=1 -DHAVE_AOM_ENCODER=1 
-DHAVE_DAV1D=1 -DHAVE_LIBDE265=1 -DHAVE_UNISTD_H -DHAVE_VISIBILITY 
-DHAVE_X265=1 -DLIBHEIF_EXPORTS -DWITH_DEFLATE_HEADER_COMPRESSION=1 
-Dheif_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> 
-I/<>/include/libheif -I/<>/include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -fvisibility-inlines-hidden   -Wall -Werror -Wsign-compare 
-Wconversion -Wno-sign-conversion -Wno-error=conversion 
-Wno-error=unused-parameter -Wno-error=deprecated-declarations -std=c++11 -MD 
-MT libheif/CMakeFiles/heif.dir/box.cc.o -MF CMakeFiles/heif.dir/box.cc.o.d -o 
CMakeFiles/heif.dir/box.cc.o -c /<>/libheif/box.cc
cd /<>/obj-x86_64-linux-gnu/libheif && /usr/bin/c++ 
-DENABLE_MULTITHREADING_SUPPORT=1 -DENABLE_PARALLEL_TILE_DECODING=1 
-DENABLE_PLUGIN_LOADING=1 -DHAVE_AOM_DECODER=1 -DHAVE_AOM_ENCODER=1 
-DHAVE_DAV1D=1 -DHAVE_LIBDE265=1 -DHAVE_UNISTD_H -DHAVE_VISIBILITY 
-DHAVE_X265=1 -DLIBHEIF_EXPORTS -DWITH_DEFLATE_HEADER_COMPRESSION=1 
-Dheif_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> 
-I/<>/include/libheif -I/<>/include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -fvisibility-inlines-hidden   -Wall -Werror -Wsign-compare 
-Wconversion -Wno-sign-conversion -Wno-error=conversion 
-Wno-error=unused-parameter -Wno-error=deprecated-declarations -std=c++11 -MD 
-MT libheif/CMakeFiles/heif.dir/bitstream.cc.o -MF 

Bug#1037748: libwebm: ftbfs with GCC-13

[Matthias Klose]

Package: src:libwebm
Version: 1.0.0.29-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/libwebm_1.0.0.29-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
[ 50%] Building CXX object CMakeFiles/mkvparser_tests.dir/testing/test_util.cc.o
/usr/bin/c++  -I/<> -I/<>/webm_parser 
-I/<>/webm_parser/include -I/googlemock/include -std=c++11 -g 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -fPIC -pie -Wdate-time -D_FORTIFY_SOURCE=2 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Wall 
-Wextra -Wnarrowing -Wno-deprecated -MD -MT 
CMakeFiles/mkvparser_tests.dir/testing/test_util.cc.o -MF 
CMakeFiles/mkvparser_tests.dir/testing/test_util.cc.o.d -o 
CMakeFiles/mkvparser_tests.dir/testing/test_util.cc.o -c 
/<>/testing/test_util.cc
In file included from /<>/testing/test_util.cc:8:
/<>/testing/test_util.h:35:12: error: ‘uint64_t’ in namespace 
‘std’ does not name a type; did you mean ‘wint_t’?
   35 | const std::uint64_t kOpusCodecDelay = 650;
  |^~~~
  |wint_t
/<>/testing/test_util.h:37:12: error: ‘uint64_t’ in namespace 
‘std’ does not name a type; did you mean ‘wint_t’?
   37 | const std::uint64_t kOpusSeekPreroll = 8000;
  |^~~~
  |wint_t
/<>/testing/test_util.h:63:59: error: ‘std::int64_t’ has not been 
declared
   63 | bool HasCuePoints(const mkvparser::Segment* segment, std::int64_t* 
cues_offset);
  |   ^~~
In file included from /<>/testing/test_util.cc:8:
/<>/testing/test_util.h:35:12: error: ‘uint64_t’ in namespace 
‘std’ does not name a type; did you mean ‘wint_t’?
   35 | const std::uint64_t kOpusCodecDelay = 650;
  |^~~~
  |wint_t
/<>/testing/test_util.h:37:12: error: ‘uint64_t’ in namespace 
‘std’ does not name a type; did you mean ‘wint_t’?
   37 | const std::uint64_t kOpusSeekPreroll = 8000;
  |^~~~
  |wint_t
/<>/testing/test_util.h:63:59: error: ‘std::int64_t’ has not been 
declared
   63 | bool HasCuePoints(const mkvparser::Segment* segment, std::int64_t* 
cues_offset);
  |   ^~~
make[3]: *** [CMakeFiles/vp9_level_stats_tests.dir/build.make:121: 
CMakeFiles/vp9_level_stats_tests.dir/testing/test_util.cc.o] Error 1
make[3]: *** Waiting for unfinished jobs
[ 51%] Building CXX object CMakeFiles/mkvmuxer_tests.dir/testing/test_util.cc.o
/usr/bin/c++  -I/<> -I/<>/webm_parser 
-I/<>/webm_parser/include -I/googlemock/include -std=c++11 -g 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -fPIC -pie -Wdate-time -D_FORTIFY_SOURCE=2 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Wall 
-Wextra -Wnarrowing -Wno-deprecated -MD -MT 
CMakeFiles/mkvmuxer_tests.dir/testing/test_util.cc.o -MF 
CMakeFiles/mkvmuxer_tests.dir/testing/test_util.cc.o.d -o 
CMakeFiles/mkvmuxer_tests.dir/testing/test_util.cc.o -c 
/<>/testing/test_util.cc
make[3]: *** [CMakeFiles/mkvparser_tests.dir/build.make:93: 
CMakeFiles/mkvparser_tests.dir/testing/test_util.cc.o] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from /<>/testing/test_util.cc:8:
/<>/testing/test_util.h:35:12: error: ‘uint64_t’ in namespace 
‘std’ does not name a type; did you mean ‘wint_t’?
   35 | const std::uint64_t kOpusCodecDelay = 650;
  |^~~~
  |wint_t
/<>/testing/test_util.h:37:12: error: ‘uint64_t’ in namespace 
‘std’ does not name a type; did you mean ‘wint_t’?
   37 | const std::uint64_t kOpusSeekPreroll = 8000;
  |^~~~
  |wint_t
/<>/testing/test_util.h:63:59: error: ‘std::int64_t’ has not been 
declared
   63 | bool HasCuePoints(const 

Bug#1037710: kodi: ftbfs with GCC-13

[Matthias Klose]

Package: src:kodi
Version: 2:20.1+dfsg-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/kodi_20.1+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
In file included from /<>/xbmc/windowing/X11/WinSystemX11.cpp:20:
/<>/xbmc/settings/DisplaySettings.h:147:21: note:   by 
‘CDisplaySettings& CDisplaySettings::operator=(const CDisplaySettings&)’
  147 |   CDisplaySettings& operator=(CDisplaySettings const&) = delete;
  | ^~~~
In file included from /<>/xbmc/input/InputManager.h:19,
 from /<>/xbmc/windowing/X11/WinEventsX11.cpp:17:
/<>/xbmc/utils/Observer.h:51:23: warning: ‘virtual Observable& 
Observable::operator=(const Observable&)’ was hidden [-Woverloaded-virtual=]
   51 |   virtual Observable =(const Observable );
  |   ^~~~
/<>/xbmc/input/InputManager.h:68:24: note:   by ‘const 
CInputManager& CInputManager::operator=(const CInputManager&)’
   68 |   CInputManager const& operator=(CInputManager const&) = delete;
  |^~~~
[  8%] Building CXX object 
build/windowing/gbm/drm/CMakeFiles/windowing_gbm_drm.dir/DRMCrtc.cpp.o
cd /<>/obj-x86_64-linux-gnu/build/windowing/gbm/drm && 
/usr/bin/c++  -I/<>/obj-x86_64-linux-gnu -I/<> 
-I/<>/lib -I/<>/xbmc 
-I/<>/xbmc/platform/linux 
-I/<>/xbmc/cores/VideoPlayer 
-I/<>/obj-x86_64-linux-gnu/build 
-I/<>/xbmc/platform/posix -isystem 
/<>/obj-x86_64-linux-gnu/build/include -isystem 
/usr/include/dbus-1.0 -isystem /usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-isystem /usr/include/pipewire-0.3 -isystem /usr/include/spa-0.2 -isystem 
/usr/include/python3.11 -isystem /usr/include/samba-4.0 -isystem 
/usr/include/libxml2 -isystem 
/<>/obj-x86_64-linux-gnu/build/cores/RetroPlayer/messages -isystem 
/usr/include/freetype2 -isystem /usr/include/fribidi -isystem /usr/include/lzo 
-isystem /usr/include/libdrm -g -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_XBMC -
 DDEB_VERSION=\"2:20.1+dfsg-1\" -Wall -Wdouble-promotion 
-Wmissing-field-initializers -Wsign-compare -Wextra -Wno-unused-parameter 
-Wno-cast-function-type -Wnon-virtual-dtor -O2 -g -DNDEBUG -DTARGET_POSIX 
-DTARGET_LINUX -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 
-DHAVE_LINUX_DMA_BUF=1 -DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 
-DHAVE_SSE=1 -DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 
-D__STDC_CONSTANT_MACROS -D_FILE_OFFSET_BITS=64 -DHAS_POSIX_NETWORK 
-DHAS_LINUX_NETWORK -DHAS_BUILTIN_SYNC_ADD_AND_FETCH=1 
-DHAS_BUILTIN_SYNC_SUB_AND_FETCH=1 -DHAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP=1 
-DHAVE_INOTIFY=1 -DHAVE_POSIX_FADVISE=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 
-DHAVE_INTTYPES_H=1 -DHAS_ALSA=1 -DHAS_AVAHI=1 -DHAS_ZEROCONF=1 
-DHAVE_LIBBLURAY=1 -DHAVE_LIBBLURAY_BDJ=1 -DHAVE_LIBCEC=1 -DHAS_DBUS=1 
-DHAS_ISO9660PP=1 -DHAVE_LCMS2=1 -DCMS_NO_REGISTER_KEYWORD=1 -DHAS_LIRC=1 
-DHAS_WEB_SERVER=1 -DHAS_WEB_INTERFACE=1 -DHAS_FILESYSTEM_NFS=1 -DHAS_NFS_SET_TI
 MEOUT -DHAS_PIPEWIRE=1 -DHAS_AIRPLAY=1 -DHAS_PULSEAUDIO=1 -DHAS_PYTHON=1 
-DHAS_FILESYSTEM_SMB=1 -DHAS_SNDIO=1 -DHAVE_LIBUDEV=1 -DHAS_UDFREAD=1 
-DHAVE_LIBXSLT=1 -DHAVE_LIBVA=1 -DHAS_GLX=1 -DHAVE_LIBVDPAU=1 
-DDATE_HAS_STRINGVIEW -DFFMPEG_VER_SHA=\"4.4.1\" -DHAVE_GCRYPT=1 
-DSPDLOG_FMT_EXTERNAL -DSPDLOG_DEBUG_ON -DSPDLOG_NO_ATOMIC_LEVELS 
-DSPDLOG_ENABLE_PATTERN_PADDING -DSPDLOG_COMPILED_LIB -DSPDLOG_SHARED_LIB 
-DHAS_EGL=1 -DHAVE_EGLEXTANGLE=1 -DHAVE_X11=1 -DHAVE_LIBXRANDR=1 
-DHAVE_HDR_OUTPUT_METADATA=1 -DHAVE_DRM_MODIFIER_NAME=1 -DHAS_GL=1 
-DHAVE_WAYLAND=1 -DHAVE_GBM=1 -DHAS_GBM_BO_MAP=1 -DHAS_GBM_MODIFIERS=1 
-DHAS_MYSQL=1 -DHAS_UPNP=1 -DHAS_DVD_DRIVE -DHAS_CDDA_RIPPER -DHAS_AIRTUNES=1 
-DBIN_INSTALL_PATH=\"/usr/lib/x86_64-linux-gnu/kodi\" 
-DINSTALL_PATH=\"/usr/share/kodi\" -Werror=double-promotion 
-Werror=missing-field-initializers 

Bug#1037714: kodi-inputstream-ffmpegdirect: ftbfs with GCC-13

[Matthias Klose]

Package: src:kodi-inputstream-ffmpegdirect
Version: 20.5.0+ds1-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/kodi-inputstream-ffmpegdirect_20.5.0+ds1-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
[ 56%] Building CXX object 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftSegment.cpp.o
/usr/bin/c++ -DADDON_GLOBAL_VERSION_FILESYSTEM_USED 
-DADDON_GLOBAL_VERSION_GENERAL_USED -DADDON_GLOBAL_VERSION_MAIN_USED 
-DADDON_GLOBAL_VERSION_NETWORK_USED -DADDON_GLOBAL_VERSION_TOOLS_USED 
-DADDON_INSTANCE_VERSION_INPUTSTREAM_USED -DBUILD_KODI_ADDON 
-DFFMPEGDIRECT_VERSION=20.5.0 -Dinputstream_ffmpegdirect_EXPORTS  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -DTARGET_POSIX 
-DTARGET_LINUX -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 
-DHAVE_LINUX_DMA_BUF=1 -DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 
-DHAVE_SSE=1 -DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 
-std=c++17 -MD -MT 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftSegment.cpp.o -MF 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftSegment.cpp.o.d -o 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftSegment.cpp.o -c 
/<>/src/stream/TimeshiftSegment.
 cpp
[ 62%] Building CXX object 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o
/usr/bin/c++ -DADDON_GLOBAL_VERSION_FILESYSTEM_USED 
-DADDON_GLOBAL_VERSION_GENERAL_USED -DADDON_GLOBAL_VERSION_MAIN_USED 
-DADDON_GLOBAL_VERSION_NETWORK_USED -DADDON_GLOBAL_VERSION_TOOLS_USED 
-DADDON_INSTANCE_VERSION_INPUTSTREAM_USED -DBUILD_KODI_ADDON 
-DFFMPEGDIRECT_VERSION=20.5.0 -Dinputstream_ffmpegdirect_EXPORTS  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -DTARGET_POSIX 
-DTARGET_LINUX -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 
-DHAVE_LINUX_DMA_BUF=1 -DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 
-DHAVE_SSE=1 -DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 
-std=c++17 -MD -MT 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o -MF 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o.d -o 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o -c 
/<>/src/stream/TimeshiftStream.cpp
[ 68%] Building CXX object 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/url/URL.cpp.o
/usr/bin/c++ -DADDON_GLOBAL_VERSION_FILESYSTEM_USED 
-DADDON_GLOBAL_VERSION_GENERAL_USED -DADDON_GLOBAL_VERSION_MAIN_USED 
-DADDON_GLOBAL_VERSION_NETWORK_USED -DADDON_GLOBAL_VERSION_TOOLS_USED 
-DADDON_INSTANCE_VERSION_INPUTSTREAM_USED -DBUILD_KODI_ADDON 
-DFFMPEGDIRECT_VERSION=20.5.0 -Dinputstream_ffmpegdirect_EXPORTS  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -DTARGET_POSIX 
-DTARGET_LINUX -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 
-DHAVE_LINUX_DMA_BUF=1 -DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 
-DHAVE_SSE=1 -DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 
-std=c++17 -MD -MT 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/url/URL.cpp.o -MF 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/url/URL.cpp.o.d -o 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/url/URL.cpp.o -c 
/<>/src/stream/url/URL.cpp
[ 75%] Building CXX object 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/url/UrlOptions.cpp.o
/usr/bin/c++ -DADDON_GLOBAL_VERSION_FILESYSTEM_USED 
-DADDON_GLOBAL_VERSION_GENERAL_USED -DADDON_GLOBAL_VERSION_MAIN_USED 
-DADDON_GLOBAL_VERSION_NETWORK_USED -DADDON_GLOBAL_VERSION_TOOLS_USED 
-DADDON_INSTANCE_VERSION_INPUTSTREAM_USED -DBUILD_KODI_ADDON 
-DFFMPEGDIRECT_VERSION=20.5.0 -Dinputstream_ffmpegdirect_EXPORTS  -g -O2 

Bug#1037712: kodi-inputstream-adaptive: ftbfs with GCC-13

[Matthias Klose]

Package: src:kodi-inputstream-adaptive
Version: 20.3.2+ds-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/kodi-inputstream-adaptive_20.3.2+ds-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
cd /<>/obj-x86_64-linux-gnu/lib/mpegts && /usr/bin/c++ 
-DBUILD_KODI_ADDON -DUNICODE -D_UNICODE -D__STDC_FORMAT_MACROS 
-I/<>/lib/mpegts/. -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fPIC   -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 -DHAVE_SSE=1 
-DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -std=c++17 -MD -MT 
lib/mpegts/CMakeFiles/mpegts.dir/ES_MPEGAudio.cpp.o -MF 
CMakeFiles/mpegts.dir/ES_MPEGAudio.cpp.o.d -o 
CMakeFiles/mpegts.dir/ES_MPEGAudio.cpp.o -c 
/<>/lib/mpegts/ES_MPEGAudio.cpp
[ 19%] Building CXX object lib/mpegts/CMakeFiles/mpegts.dir/ES_Subtitle.cpp.o
cd /<>/obj-x86_64-linux-gnu/lib/mpegts && /usr/bin/c++ 
-DBUILD_KODI_ADDON -DUNICODE -D_UNICODE -D__STDC_FORMAT_MACROS 
-I/<>/lib/mpegts/. -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fPIC   -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 -DHAVE_SSE=1 
-DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -std=c++17 -MD -MT 
lib/mpegts/CMakeFiles/mpegts.dir/ES_Subtitle.cpp.o -MF 
CMakeFiles/mpegts.dir/ES_Subtitle.cpp.o.d -o 
CMakeFiles/mpegts.dir/ES_Subtitle.cpp.o -c 
/<>/lib/mpegts/ES_Subtitle.cpp
[ 20%] Building CXX object lib/mpegts/CMakeFiles/mpegts.dir/ES_AAC.cpp.o
cd /<>/obj-x86_64-linux-gnu/lib/mpegts && /usr/bin/c++ 
-DBUILD_KODI_ADDON -DUNICODE -D_UNICODE -D__STDC_FORMAT_MACROS 
-I/<>/lib/mpegts/. -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fPIC   -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 -DHAVE_SSE=1 
-DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -std=c++17 -MD -MT 
lib/mpegts/CMakeFiles/mpegts.dir/ES_AAC.cpp.o -MF 
CMakeFiles/mpegts.dir/ES_AAC.cpp.o.d -o CMakeFiles/mpegts.dir/ES_AAC.cpp.o -c 
/<>/lib/mpegts/ES_AAC.cpp
/<>/src/test/TestHelper.cpp: In constructor 
‘HLSTestTree::HLSTestTree(UTILS::PROPERTIES::KodiProperties, 
CHOOSER::IRepresentationChooser*)’:
/<>/src/test/TestHelper.cpp:142:74: error: invalid cast to 
abstract class type ‘AESDecrypter’
  142 |   m_decrypter = 
std::make_unique(AESDecrypter(std::string()));
  | 
 ^
/<>/src/test/TestHelper.h:69:7: note:   because the following 
virtual functions are pure within ‘AESDecrypter’:
   69 | class AESDecrypter : public IAESDecrypter
  |   ^~~~
/<>/src/test/../Iaes_decrypter.h:28:16: note: ‘virtual void 
IAESDecrypter::ivFromSequence(int*, int)’
   28 |   virtual void ivFromSequence(uint8_t* buffer, uint64_t sid) = 0;
  |^~
[ 21%] Building CXX object lib/mpegts/CMakeFiles/mpegts.dir/ES_h264.cpp.o
cd /<>/obj-x86_64-linux-gnu/lib/mpegts && /usr/bin/c++ 
-DBUILD_KODI_ADDON -DUNICODE -D_UNICODE -D__STDC_FORMAT_MACROS 
-I/<>/lib/mpegts/. -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fPIC   -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 -DHAVE_SSE=1 
-DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 

Bug#1037711: kodi-imagedecoder-heif: ftbfs with GCC-13

[Matthias Klose]

Package: src:kodi-imagedecoder-heif
Version: 20.1.0+ds1-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/kodi-imagedecoder-heif_20.1.0+ds1-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
/<>/lib/TinyEXIF/TinyEXIF.cpp:1238:9: error: ‘RelatedImageWidth’ 
was not declared in this scope
 1238 | RelatedImageWidth = 0;
  | ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1239:9: error: ‘RelatedImageHeight’ 
was not declared in this scope
 1239 | RelatedImageHeight= 0;
  | ^~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1240:9: error: ‘Orientation’ was not 
declared in this scope
 1240 | Orientation   = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1243:9: error: ‘ResolutionUnit’ was 
not declared in this scope; did you mean ‘XResolution’?
 1243 | ResolutionUnit= 0;
  | ^~
  | XResolution
/<>/lib/TinyEXIF/TinyEXIF.cpp:1244:9: error: ‘BitsPerSample’ was 
not declared in this scope
 1244 | BitsPerSample = 0;
  | ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1247:9: error: ‘ExposureProgram’ was 
not declared in this scope
 1247 | ExposureProgram   = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1248:9: error: ‘ISOSpeedRatings’ was 
not declared in this scope
 1248 | ISOSpeedRatings   = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1255:9: error: ‘Flash’ was not 
declared in this scope
 1255 | Flash = 0;
  | ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1256:9: error: ‘MeteringMode’ was 
not declared in this scope
 1256 | MeteringMode  = 0;
  | ^~~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1257:9: error: ‘LightSource’ was not 
declared in this scope
 1257 | LightSource   = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1258:9: error: ‘ProjectionType’ was 
not declared in this scope
 1258 | ProjectionType= 0;
  | ^~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1259:21: error: request for member 
‘clear’ in ‘((TinyEXIF::EXIFInfo*)this)->TinyEXIF::EXIFInfo::SubjectArea’, 
which is of non-class type ‘int’
 1259 | SubjectArea.clear();
  | ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1275:18: error: ‘struct 
TinyEXIF::EXIFInfo::LensInfo_t’ has no member named ‘FocalPlaneResolutionUnit’; 
did you mean ‘FocalPlaneXResolution’?
 1275 | LensInfo.FocalPlaneResolutionUnit = 0;
  |  ^~~~
  |  FocalPlaneXResolution
/<>/lib/TinyEXIF/TinyEXIF.cpp:1294:21: error: ‘struct 
TinyEXIF::EXIFInfo::Geolocation_t’ has no member named ‘GPSDifferential’
 1294 | GeoLocation.GPSDifferential = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1301:35: error: ‘struct 
TinyEXIF::EXIFInfo::Geolocation_t::Coord_t’ has no member named ‘direction’
 1301 | GeoLocation.LatComponents.direction = 0;
  |   ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1305:35: error: ‘struct 
TinyEXIF::EXIFInfo::Geolocation_t::Coord_t’ has no member named ‘direction’
 1305 | GeoLocation.LonComponents.direction = 0;
  |   ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1312:20: error: ‘struct 
TinyEXIF::EXIFInfo::MicroVideo_t’ has no member named ‘HasMicroVideo’
 1312 | MicroVideo.HasMicroVideo = 0;
  |^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1313:20: error: ‘struct 
TinyEXIF::EXIFInfo::MicroVideo_t’ has no member named ‘MicroVideoVersion’
 1313 | MicroVideo.MicroVideoVersion = 0;
  |^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1314:20: error: ‘struct 
TinyEXIF::EXIFInfo::MicroVideo_t’ has no member named 

Bug#1037685: guitarix: ftbfs with GCC-13

[Matthias Klose]

Package: src:guitarix
Version: 0.44.1+dfsg1-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/guitarix_0.44.1+dfsg1-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
../src/LV2/DSP/gx_common.h:36:1: note: ‘uint32_t’ is defined in header 
‘’; did you forget to ‘#include ’?
   35 | #include 
  +++ |+#include 
   36 | #ifndef _IMMINTRIN_H_INCLUDED
../src/LV2/DSP/gx_common.h:69:5: error: ‘uint32_t’ does not name a type
   69 | uint32_t  mxcsr;
  | ^~~~
../src/LV2/DSP/gx_common.h:69:5: note: ‘uint32_t’ is defined in header 
‘’; did you forget to ‘#include ’?
../src/LV2/DSP/gx_common.h:70:5: error: ‘uint32_t’ does not name a type
   70 | uint32_t  old_mxcsr;
  | ^~~~
../src/LV2/DSP/gx_common.h:70:5: note: ‘uint32_t’ is defined in header 
‘’; did you forget to ‘#include ’?
../src/LV2/DSP/gx_common.h: In member function ‘void 
DenormalProtection::set_()’:
../src/LV2/DSP/gx_common.h:76:9: error: ‘old_mxcsr’ was not declared in this 
scope
   76 | old_mxcsr = _mm_getcsr();
  | ^
../src/LV2/DSP/gx_common.h:77:9: error: ‘mxcsr’ was not declared in this scope
   77 | mxcsr = old_mxcsr;
  | ^
../src/LV2/DSP/gx_common.h:78:78: error: ‘mxcsr_mask’ was not declared in this 
scope
   78 | _mm_setcsr((mxcsr | _MM_DENORMALS_ZERO_MASK | 
_MM_FLUSH_ZERO_MASK) & mxcsr_mask);
  | 
 ^~
../src/LV2/DSP/gx_common.h: In member function ‘void 
DenormalProtection::reset_()’:
../src/LV2/DSP/gx_common.h:83:20: error: ‘old_mxcsr’ was not declared in this 
scope
   83 | _mm_setcsr(old_mxcsr);
  |^
../src/LV2/DSP/gx_common.h: In constructor 
‘DenormalProtection::DenormalProtection()’:
../src/LV2/DSP/gx_common.h:89:9: error: ‘mxcsr_mask’ was not declared in this 
scope
   89 | mxcsr_mask = 0xffbf; // Default MXCSR mask
  | ^~
../src/LV2/DSP/gx_common.h:90:9: error: ‘mxcsr’ was not declared in this scope
   90 | mxcsr  = 0;
  | ^
../src/LV2/DSP/gx_common.h:91:9: error: ‘uint8_t’ was not declared in this scope
   91 | uint8_t fxsave[512] __attribute__ ((aligned (16))); // 
Structure for storing FPU state with FXSAVE command
  | ^~~
../src/LV2/DSP/gx_common.h:91:9: note: ‘uint8_t’ is defined in header 
‘’; did you forget to ‘#include ’?
../src/LV2/DSP/gx_common.h:93:16: error: ‘fxsave’ was not declared in this 
scope; did you mean ‘_xsave’?
   93 | memset(fxsave, 0, sizeof(fxsave));
  |^~
  |_xsave
../src/LV2/DSP/gx_common.h:95:9: error: ‘uint32_t’ was not declared in this 
scope
   95 | uint32_t mask = *(reinterpret_cast([0x1c])); 
// Obtain the MXCSR mask from FXSAVE structure
  | ^~~~
../src/LV2/DSP/gx_common.h:95:9: note: ‘uint32_t’ is defined in header 
‘’; did you forget to ‘#include ’?
../src/LV2/DSP/gx_common.h:96:13: error: ‘mask’ was not declared in this scope
   96 | if (mask != 0)
  | ^~~~

Waf: Leaving directory `/<>/build'
Build failed
 -> task in 'gx_amp' failed with exit status 1: 
{task 140143352578912: cxx gx_tonestack.cc -> gx_tonestack.cc.1.o}
['/usr/bin/g++', '-g', '-O2', '-ffile-prefix-map=/<>=.', 
'-fstack-protector-strong', '-Wformat', '-Werror=format-security', '-g', '-O2', 
'-ffile-prefix-map=/<>=.', '-fstack-protector-strong', '-Wformat', 
'-Werror=format-security', '-Wdate-time', '-D_FORTIFY_SOURCE=2', '-O3', 
'-DNDEBUG', '-D_FILE_OFFSET_BITS=64', '-std=c++11', '-fvisibility=hidden', 
'-fno-lto', '-Wl,-z,noexecstack', '-Wl,-z,relro,-z,now', 
'-Wl,--exclude-libs,ALL', '-fvisibility=hidden', '-Wl,-z,relro,-z,now', 
'-Wl,--exclude-libs,ALL', '-fPIC', '-Isrc/LV2/faust', '-I../src/LV2/faust', 

Bug#1037686: hdrmerge: ftbfs with GCC-13

[Matthias Klose]

Package: src:hdrmerge
Version: 0.5+git20200117-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/hdrmerge_0.5+git20200117-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
   57 | void IFD::write(uint8_t * buffer, size_t & pos, bool hasNext) {
  |  ^
/<>/src/TiffDirectory.cpp:57:44: error: ‘pos’ was not declared in 
this scope
   57 | void IFD::write(uint8_t * buffer, size_t & pos, bool hasNext) {
  |^~~
/<>/src/TiffDirectory.cpp:57:49: error: expected 
primary-expression before ‘bool’
   57 | void IFD::write(uint8_t * buffer, size_t & pos, bool hasNext) {
  | ^~~~
/<>/src/TiffDirectory.cpp: In member function ‘size_t 
hdrmerge::IFD::length() const’:
/<>/src/TiffDirectory.cpp:77:46: error: request for member ‘size’ 
in ‘((const hdrmerge::IFD*)this)->hdrmerge::IFD::entryData’, which is of 
non-class type ‘const int’
   77 | return 6 + 12*entries.size() + entryData.size();
  |  ^~~~
/<>/src/TiffDirectory.cpp: At global scope:
/<>/src/TiffDirectory.cpp:81:17: error: ‘hdrmerge::IFD::DirEntry* 
hdrmerge::IFD::getEntry’ is not a static data member of ‘class hdrmerge::IFD’
   81 | IFD::DirEntry * IFD::getEntry(uint16_t tag) {
  | ^~~
/<>/src/TiffDirectory.cpp:81:31: error: ‘uint16_t’ was not 
declared in this scope
   81 | IFD::DirEntry * IFD::getEntry(uint16_t tag) {
  |   ^~~~
/<>/src/TiffDirectory.cpp:81:31: note: ‘uint16_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
make[3]: *** [CMakeFiles/hdrmerge.dir/build.make:216: 
CMakeFiles/hdrmerge.dir/src/TiffDirectory.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from 
/<>/obj-x86_64-linux-gnu/hdrmerge_autogen/UVLADIE3JM/moc_AboutDialog.cpp:10,
 from 
/<>/obj-x86_64-linux-gnu/hdrmerge_autogen/mocs_compilation.cpp:2:
/<>/obj-x86_64-linux-gnu/hdrmerge_autogen/UVLADIE3JM/../../../src/AboutDialog.hpp:32:68:
 warning: ‘constexpr QFlags::QFlags(Zero) [with Enum = Qt::WindowType; Zero 
= int QFlags::Private::*]’ is deprecated: Use default 
constructor instead [-Wdeprecated-declarations]
   32 | explicit AboutDialog(QWidget * parent = 0, Qt::WindowFlags f = 0);
  |^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1305,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/qtguiglobal.h:43,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtwidgetsglobal.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialog.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QDialog:1,
 from 
/<>/obj-x86_64-linux-gnu/hdrmerge_autogen/UVLADIE3JM/../../../src/AboutDialog.hpp:26:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:123:80: note: declared here
  123 | QT_DEPRECATED_X("Use default constructor instead") Q_DECL_CONSTEXPR 
inline QFlags(Zero) noexcept : i(0) {}
  | 
   ^~
In file included from 
/<>/obj-x86_64-linux-gnu/hdrmerge_autogen/UVLADIE3JM/moc_DngPropertiesDialog.cpp:10,
 from 
/<>/obj-x86_64-linux-gnu/hdrmerge_autogen/mocs_compilation.cpp:3:
/<>/obj-x86_64-linux-gnu/hdrmerge_autogen/UVLADIE3JM/../../../src/DngPropertiesDialog.hpp:35:67:
 warning: ‘constexpr QFlags::QFlags(Zero) [with Enum = Qt::WindowType; Zero 
= int QFlags::Private::*]’ is deprecated: Use default 
constructor instead [-Wdeprecated-declarations]
   35 | DngPropertiesDialog(QWidget * parent = 0, Qt::WindowFlags f = 0);
  |   ^

Bug#1037676: giada: ftbfs with GCC-13

[Matthias Klose]

Package: src:giada
Version: 0.22.0-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/giada_0.22.0-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
/usr/bin/c++ -DFMT_SHARED -DJUCE_DEBUG=0 
-DJUCE_GLOBAL_MODULE_SETTINGS_INCLUDED=1 -DJUCE_MODAL_LOOPS_PERMITTED=1 
-DJUCE_MODULE_AVAILABLE_juce_gui_basics=1 -DJUCE_PLUGINHOST_AU=0 
-DJUCE_PLUGINHOST_VST=1 -DJUCE_STANDALONE_APPLICATION=1 -DJUCE_USE_CURL=0 
-DJUCE_WEB_BROWSER=0 -DNDEBUG -DWITH_AUDIO_JACK -DWITH_VST -DWITH_VST2 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -I/<> 
-I/<>/src -I/<>/src/deps/juce/modules 
-I/<>/src/deps/vst3sdk -I/usr/include/freetype2 -isystem 
/usr/include/rtmidi -isystem /usr/include/opus -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++17 -Wno-error -Wno-error=format-security 
-I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -pthread 
-I/usr/include/rtaudio -D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ 
-D_REENTRANT  -Wdate-time -D_FORTIFY_SOURCE=2 -D_fstEffect=AEffect 
-DBUILD_DATE='"2023-01-11"' -DTEST_RESOURCES_DIR='"tests/resources/
 "' -Wall -Wextra -Wpedantic -pthread -D__UNIX_JACK__ -D__LINUX_ALSA__ 
-D__LINUX_PULSE__ -D_REENTRANT -MD -MT 
CMakeFiles/giada.dir/src/gui/dialogs/midiIO/midiInputChannel.cpp.o -MF 
CMakeFiles/giada.dir/src/gui/dialogs/midiIO/midiInputChannel.cpp.o.d -o 
CMakeFiles/giada.dir/src/gui/dialogs/midiIO/midiInputChannel.cpp.o -c 
/<>/src/gui/dialogs/midiIO/midiInputChannel.cpp
[ 53%] Building CXX object 
CMakeFiles/giada.dir/src/gui/dialogs/midiIO/midiInputMaster.cpp.o
/usr/bin/c++ -DFMT_SHARED -DJUCE_DEBUG=0 
-DJUCE_GLOBAL_MODULE_SETTINGS_INCLUDED=1 -DJUCE_MODAL_LOOPS_PERMITTED=1 
-DJUCE_MODULE_AVAILABLE_juce_gui_basics=1 -DJUCE_PLUGINHOST_AU=0 
-DJUCE_PLUGINHOST_VST=1 -DJUCE_STANDALONE_APPLICATION=1 -DJUCE_USE_CURL=0 
-DJUCE_WEB_BROWSER=0 -DNDEBUG -DWITH_AUDIO_JACK -DWITH_VST -DWITH_VST2 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -I/<> 
-I/<>/src -I/<>/src/deps/juce/modules 
-I/<>/src/deps/vst3sdk -I/usr/include/freetype2 -isystem 
/usr/include/rtmidi -isystem /usr/include/opus -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++17 -Wno-error -Wno-error=format-security 
-I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -pthread 
-I/usr/include/rtaudio -D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ 
-D_REENTRANT  -Wdate-time -D_FORTIFY_SOURCE=2 -D_fstEffect=AEffect 
-DBUILD_DATE='"2023-01-11"' -DTEST_RESOURCES_DIR='"tests/resources/
 "' -Wall -Wextra -Wpedantic -pthread -D__UNIX_JACK__ -D__LINUX_ALSA__ 
-D__LINUX_PULSE__ -D_REENTRANT -MD -MT 
CMakeFiles/giada.dir/src/gui/dialogs/midiIO/midiInputMaster.cpp.o -MF 
CMakeFiles/giada.dir/src/gui/dialogs/midiIO/midiInputMaster.cpp.o.d -o 
CMakeFiles/giada.dir/src/gui/dialogs/midiIO/midiInputMaster.cpp.o -c 
/<>/src/gui/dialogs/midiIO/midiInputMaster.cpp
[ 54%] Building CXX object 
CMakeFiles/giada.dir/src/gui/elems/midiIO/midiLearner.cpp.o
/usr/bin/c++ -DFMT_SHARED -DJUCE_DEBUG=0 
-DJUCE_GLOBAL_MODULE_SETTINGS_INCLUDED=1 -DJUCE_MODAL_LOOPS_PERMITTED=1 
-DJUCE_MODULE_AVAILABLE_juce_gui_basics=1 -DJUCE_PLUGINHOST_AU=0 
-DJUCE_PLUGINHOST_VST=1 -DJUCE_STANDALONE_APPLICATION=1 -DJUCE_USE_CURL=0 
-DJUCE_WEB_BROWSER=0 -DNDEBUG -DWITH_AUDIO_JACK -DWITH_VST -DWITH_VST2 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -I/<> 
-I/<>/src -I/<>/src/deps/juce/modules 
-I/<>/src/deps/vst3sdk -I/usr/include/freetype2 -isystem 
/usr/include/rtmidi -isystem /usr/include/opus -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++17 -Wno-error -Wno-error=format-security 
-I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -pthread 
-I/usr/include/rtaudio -D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ 
-D_REENTRANT  -Wdate-time -D_FORTIFY_SOURCE=2 -D_fstEffect=AEffect 

Bug#1037648: faust: ftbfs with GCC-13

[Matthias Klose]

Package: src:faust
Version: 2.54.9+ds0-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/faust_2.54.9+ds0-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
 3036 | int  v1 = popInt();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh: In member 
function ‘void FBCInterpreter::ExecuteBlock(FBCBlockInstruction*, bool) [with REAL = double; int 
TRACE = 4]’:
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3037:14: 
warning: array subscript ‘double[0]’ is partly outside array bounds of ‘int 
[1]’ [-Warray-bounds=]
 3037 | REAL v2 = *reinterpret_cast();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3036:14: 
note: object ‘v1’ of size 4
 3036 | int  v1 = popInt();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh: In member 
function ‘void FBCInterpreter::ExecuteBlock(FBCBlockInstruction*, bool) [with REAL = double; int 
TRACE = 5]’:
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3037:14: 
warning: array subscript ‘double[0]’ is partly outside array bounds of ‘int 
[1]’ [-Warray-bounds=]
 3037 | REAL v2 = *reinterpret_cast();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3036:14: 
note: object ‘v1’ of size 4
 3036 | int  v1 = popInt();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh: In member 
function ‘void FBCInterpreter::ExecuteBlock(FBCBlockInstruction*, bool) [with REAL = double; int 
TRACE = 6]’:
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3037:14: 
warning: array subscript ‘double[0]’ is partly outside array bounds of ‘int 
[1]’ [-Warray-bounds=]
 3037 | REAL v2 = *reinterpret_cast();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3036:14: 
note: object ‘v1’ of size 4
 3036 | int  v1 = popInt();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh: In member 
function ‘void FBCInterpreter::ExecuteBlock(FBCBlockInstruction*, bool) [with REAL = double; int 
TRACE = 7]’:
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3037:14: 
warning: array subscript ‘double[0]’ is partly outside array bounds of ‘int 
[1]’ [-Warray-bounds=]
 3037 | REAL v2 = *reinterpret_cast();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3036:14: 
note: object ‘v1’ of size 4
 3036 | int  v1 = popInt();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh: In member 
function ‘void FBCInterpreter::ExecuteBlock(FBCBlockInstruction*, bool) [with REAL = double; int 
TRACE = 0]’:
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3037:14: 
warning: array subscript ‘double[0]’ is partly outside array bounds of ‘int 
[1]’ [-Warray-bounds=]
 3037 | REAL v2 = *reinterpret_cast();
  |  ^~
/<>/compiler/generator/interpreter/fbc_interpreter.hh:3036:14: 
note: object ‘v1’ of size 4
 3036 | int  v1 = popInt();
  |  ^~
[ 13%] Building CXX object 
CMakeFiles/faust.dir/<>/compiler/lock_api.cpp.o
/usr/bin/g++ -DCMAJOR_BUILD -DCPP_BUILD -DCSHARP_BUILD -DC_BUILD -DDLANG_BUILD 
-DFIR_BUILD -DINTERP_BUILD -DJAVA_BUILD -DJAX_BUILD -DJULIA_BUILD 
-DLIBDIR=\"lib\" -DLLVM_140 -DLLVM_BUILD -DLLVM_VERSION=\"14.0.6\" -DOCPP_BUILD 
-DRUST_BUILD -DWASM_BUILD -I/<>/compiler 
-I/<>/compiler/boxes -I/<>/compiler/documentator 
-I/<>/compiler/draw -I/<>/compiler/errors 
-I/<>/compiler/evaluate -I/<>/compiler/extended 
-I/<>/compiler/generator 
-I/<>/compiler/generator/dlang 
-I/<>/compiler/generator/csharp 
-I/<>/compiler/generator/fir 
-I/<>/compiler/generator/julia 
-I/<>/compiler/generator/interpreter 
-I/<>/compiler/generator/rust 
-I/<>/compiler/generator/cmajor 
-I/<>/compiler/normalize -I/<>/compiler/parallelize 
-I/<>/compiler/parser 

Bug#1037628: drumgizmo: ftbfs with GCC-13

[Matthias Klose]

Package: src:drumgizmo
Version: 0.9.20-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/drumgizmo_0.9.20-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
libtool: link: g++ -DUI_X11 -I.. -I../src -I../hugin -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o plugingui plugingui-testmain.o plugingui-hugin.o  
./.libs/libplugingui.a -lX11 -lXext ../src/.libs/libdg.a -lsndfile -lpthread 
../src/.libs/libnls.a -latomic -lrt
make[5]: Leaving directory '/<>/plugingui'
make[4]: Leaving directory '/<>/plugingui'
make[3]: Leaving directory '/<>/plugingui'
Making all in plugin
make[3]: Entering directory '/<>/plugin'
Making all in vst
make[4]: Entering directory '/<>/plugin/vst'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/<>/plugin/vst'
make[4]: Entering directory '/<>/plugin'
g++ -DHAVE_CONFIG_H -I. -I..-I../plugin/plugingizmo -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffast-math 
-std=c++11 -DDISABLE_HUGIN -c -o ttlgen-ttlgen.o `test -f 
'../plugin/plugingizmo/ttlgen.cc' || echo './'`../plugin/plugingizmo/ttlgen.cc
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -c -o drumgizmo_la-hugin.lo `test -f 
'../hugin/hugin.c' || echo './'`../hugin/hugin.c
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -DLV2 
-DLV2_PLUGIN_URI=\"http://drumgizmo.org/lv2\;  -fvisibility=hidden 
-I../zita-resampler/libs  -I/usr/include/opus -I/usr/include/x86_64-linux-gnu  
-I../plugin/plugingizmo -I../ -I../plugingui -I../src -I../hugin -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c -o 
drumgizmo_la-midievent.lo `test -f '../plugin/plugingizmo/midievent.cc' || echo 
'./'`../plugin/plugingizmo/midievent.cc
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -DLV2 
-DLV2_PLUGIN_URI=\"http://drumgizmo.org/lv2\;  -fvisibility=hidden 
-I../zita-resampler/libs  -I/usr/include/opus -I/usr/include/x86_64-linux-gnu  
-I../plugin/plugingizmo -I../ -I../plugingui -I../src -I../hugin -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c -o 
drumgizmo_la-pluginlv2.lo `test -f '../plugin/plugingizmo/pluginlv2.cc' || echo 
'./'`../plugin/plugingizmo/pluginlv2.cc
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -DLV2 
-DLV2_PLUGIN_URI=\"http://drumgizmo.org/lv2\;  -fvisibility=hidden 
-I../zita-resampler/libs  -I/usr/include/opus -I/usr/include/x86_64-linux-gnu  
-I../plugin/plugingizmo -I../ -I../plugingui -I../src -I../hugin -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c -o 
drumgizmo_la-drumgizmo_plugin.lo `test -f 'drumgizmo_plugin.cc' || echo 
'./'`drumgizmo_plugin.cc
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffast-math -c 
../hugin/hugin.c  -fPIC -DPIC -o .libs/drumgizmo_la-hugin.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-DLV2 -DLV2_PLUGIN_URI=\"http://drumgizmo.org/lv2\; -fvisibility=hidden 
-I../zita-resampler/libs -I/usr/include/opus -I/usr/include/x86_64-linux-gnu 
-I../plugin/plugingizmo -I../ -I../plugingui 

Bug#1037594: blender: ftbfs with GCC-13

[Matthias Klose]

Package: src:blender
Version: 3.4.1+dfsg-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/blender_3.4.1+dfsg-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:171:29:
 note: object ‘emission_sd_storage’ of size 736
  171 |   ShaderDataCausticsStorage emission_sd_storage;
  | ^~~
In function ‘int ccl::kernel_path_mnee_sample(KernelGlobals, IntegratorState, 
ShaderData*, ShaderData*, const RNGState*, LightSample*, BsdfEval*)’,
inlined from ‘void ccl::integrate_surface_direct_light(KernelGlobals, 
IntegratorState, ShaderData*, const RNGState*) [with unsigned int 
node_feature_mask = 33554879]’ at 
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:194:54,
inlined from ‘bool ccl::integrate_surface(KernelGlobals, IntegratorState, 
float*) [with unsigned int node_feature_mask = 33554879]’ at 
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:670:54:
/<>/intern/cycles/kernel/../kernel/integrator/mnee.h:1024:19: 
warning: array subscript ‘ccl::ShaderData[0]’ is partly outside array bounds of 
‘ccl::ShaderDataCausticsStorage [1]’ [-Warray-bounds=]
 1024 | if (bsdf->type == 
CLOSURE_BSDF_MICROFACET_BECKMANN_REFRACTION_ID ||
  | ~~^~~~
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h: In 
function ‘bool ccl::integrate_surface(KernelGlobals, IntegratorState, float*) 
[with unsigned int node_feature_mask = 33554879]’:
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:171:29:
 note: object ‘emission_sd_storage’ of size 736
  171 |   ShaderDataCausticsStorage emission_sd_storage;
  | ^~~
In file included from 
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:10,
 from 
/<>/intern/cycles/kernel/../kernel/device/cpu/kernel_arch_impl.h:32:
In function ‘int ccl::kernel_path_mnee_sample(KernelGlobals, IntegratorState, 
ShaderData*, ShaderData*, const RNGState*, LightSample*, BsdfEval*)’,
inlined from ‘void ccl::integrate_surface_direct_light(KernelGlobals, 
IntegratorState, ShaderData*, const RNGState*) [with unsigned int 
node_feature_mask = 33554879]’ at 
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:194:54,
inlined from ‘bool ccl::integrate_surface(KernelGlobals, IntegratorState, 
float*) [with unsigned int node_feature_mask = 33554879]’ at 
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:670:54:
/<>/intern/cycles/kernel/../kernel/integrator/mnee.h:1023:43: 
warning: array subscript ‘ccl::ShaderData[0]’ is partly outside array bounds of 
‘ccl::ShaderDataCausticsStorage [1]’ [-Warray-bounds=]
 1023 | ccl_private ShaderClosure *bsdf = _mnee->closure[ci];
  |   ^
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h: In 
function ‘bool ccl::integrate_surface(KernelGlobals, IntegratorState, float*) 
[with unsigned int node_feature_mask = 33554879]’:
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:171:29:
 note: object ‘emission_sd_storage’ of size 736
  171 |   ShaderDataCausticsStorage emission_sd_storage;
  | ^~~
In function ‘int ccl::kernel_path_mnee_sample(KernelGlobals, IntegratorState, 
ShaderData*, ShaderData*, const RNGState*, LightSample*, BsdfEval*)’,
inlined from ‘void ccl::integrate_surface_direct_light(KernelGlobals, 
IntegratorState, ShaderData*, const RNGState*) [with unsigned int 
node_feature_mask = 33554879]’ at 
/<>/intern/cycles/kernel/../kernel/integrator/shade_surface.h:194:54,
inlined from ‘bool ccl::integrate_surface(KernelGlobals, IntegratorState, 
float*) [with unsigned int node_feature_mask = 33554879]’ at 

Bug#1037584: audacity: ftbfs with GCC-13

[Matthias Klose]

Package: src:audacity
Version: 3.2.4+dfsg-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/audacity_3.2.4+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
cd /<>/obj-x86_64-linux-gnu/lib-src/libnyquist && /usr/bin/cc 
-DCMTSTUFF -DEXPERIMENTAL_CRASH_REPORT -DEXPERIMENTAL_DRAGGABLE_PLAY_HEAD 
-DEXPERIMENTAL_FULL_WASAPI -DEXPERIMENTAL_HALF_WAVE -DEXPERIMENTAL_KEY_VIEW 
-DEXPERIMENTAL_MIDI_OUT -DEXPERIMENTAL_MODULE_PREFS 
-DEXPERIMENTAL_NOISE_REDUCTION -DEXPERIMENTAL_NOTETRACK_OVERLAY 
-DEXPERIMENTAL_NYQUIST_SPLIT_CONTROL -DEXPERIMENTAL_PUNCH_AND_ROLL 
-DEXPERIMENTAL_SCIENCE_FILTERS -DEXPERIMENTAL_SCROLLING_LIMITS 
-DEXPERIMENTAL_SCRUBBING_SCROLL_WHEEL -DEXPERIMENTAL_SCRUBBING_SUPPORT 
-DEXPERIMENTAL_SPECTRAL_EDITING -DEXPERIMENTAL_SYNC_LOCK -DEXPERIMENTAL_THEMING 
-DEXPERIMENTAL_TWO_TONE_TIME_RULER -DEXPERIMENTAL_ZOOM_TOGGLE_BUTTON -DEXT 
-DUSE_NYQUIST=1 -I/<>/lib-src/libnyquist/nyquist/cmt 
-I/<>/lib-src/libnyquist/nyquist/cmupv/src 
-I/<>/lib-src/libnyquist/nyquist/ffts/src 
-I/<>/lib-src/libnyquist/nyquist/nyqsrc 
-I/<>/lib-src/libnyquist/nyquist/nyqstk -I/<>
 /lib-src/libnyquist/nyquist/nyqstk/include 
-I/<>/lib-src/libnyquist/nyquist/tran 
-I/<>/lib-src/libnyquist/nyquist/xlisp 
-I/<>/lib-src/libnyquist/nyquist/sys/unix 
-I/<>/lib-src/libnyquist -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -MD -MT 
lib-src/libnyquist/CMakeFiles/libnyquist.dir/nyquist/nyqsrc/sndfnint.c.o -MF 
CMakeFiles/libnyquist.dir/nyquist/nyqsrc/sndfnint.c.o.d -o 
CMakeFiles/libnyquist.dir/nyquist/nyqsrc/sndfnint.c.o -c 
/<>/lib-src/libnyquist/nyquist/nyqsrc/sndfnint.c
[ 23%] Building C object 
lib-src/libnyquist/CMakeFiles/libnyquist.dir/nyquist/nyqsrc/sndmax.c.o
cd /<>/obj-x86_64-linux-gnu/lib-src/libnyquist && /usr/bin/cc 
-DCMTSTUFF -DEXPERIMENTAL_CRASH_REPORT -DEXPERIMENTAL_DRAGGABLE_PLAY_HEAD 
-DEXPERIMENTAL_FULL_WASAPI -DEXPERIMENTAL_HALF_WAVE -DEXPERIMENTAL_KEY_VIEW 
-DEXPERIMENTAL_MIDI_OUT -DEXPERIMENTAL_MODULE_PREFS 
-DEXPERIMENTAL_NOISE_REDUCTION -DEXPERIMENTAL_NOTETRACK_OVERLAY 
-DEXPERIMENTAL_NYQUIST_SPLIT_CONTROL -DEXPERIMENTAL_PUNCH_AND_ROLL 
-DEXPERIMENTAL_SCIENCE_FILTERS -DEXPERIMENTAL_SCROLLING_LIMITS 
-DEXPERIMENTAL_SCRUBBING_SCROLL_WHEEL -DEXPERIMENTAL_SCRUBBING_SUPPORT 
-DEXPERIMENTAL_SPECTRAL_EDITING -DEXPERIMENTAL_SYNC_LOCK -DEXPERIMENTAL_THEMING 
-DEXPERIMENTAL_TWO_TONE_TIME_RULER -DEXPERIMENTAL_ZOOM_TOGGLE_BUTTON -DEXT 
-DUSE_NYQUIST=1 -I/<>/lib-src/libnyquist/nyquist/cmt 
-I/<>/lib-src/libnyquist/nyquist/cmupv/src 
-I/<>/lib-src/libnyquist/nyquist/ffts/src 
-I/<>/lib-src/libnyquist/nyquist/nyqsrc 
-I/<>/lib-src/libnyquist/nyquist/nyqstk -I/<>
 /lib-src/libnyquist/nyquist/nyqstk/include 
-I/<>/lib-src/libnyquist/nyquist/tran 
-I/<>/lib-src/libnyquist/nyquist/xlisp 
-I/<>/lib-src/libnyquist/nyquist/sys/unix 
-I/<>/lib-src/libnyquist -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -MD -MT 
lib-src/libnyquist/CMakeFiles/libnyquist.dir/nyquist/nyqsrc/sndmax.c.o -MF 
CMakeFiles/libnyquist.dir/nyquist/nyqsrc/sndmax.c.o.d -o 
CMakeFiles/libnyquist.dir/nyquist/nyqsrc/sndmax.c.o -c 
/<>/lib-src/libnyquist/nyquist/nyqsrc/sndmax.c
[ 23%] Building C object 
lib-src/libnyquist/CMakeFiles/libnyquist.dir/nyquist/nyqsrc/sndread.c.o
cd /<>/obj-x86_64-linux-gnu/lib-src/libnyquist && /usr/bin/cc 
-DCMTSTUFF -DEXPERIMENTAL_CRASH_REPORT -DEXPERIMENTAL_DRAGGABLE_PLAY_HEAD 
-DEXPERIMENTAL_FULL_WASAPI -DEXPERIMENTAL_HALF_WAVE -DEXPERIMENTAL_KEY_VIEW 
-DEXPERIMENTAL_MIDI_OUT -DEXPERIMENTAL_MODULE_PREFS 
-DEXPERIMENTAL_NOISE_REDUCTION -DEXPERIMENTAL_NOTETRACK_OVERLAY 
-DEXPERIMENTAL_NYQUIST_SPLIT_CONTROL -DEXPERIMENTAL_PUNCH_AND_ROLL 
-DEXPERIMENTAL_SCIENCE_FILTERS -DEXPERIMENTAL_SCROLLING_LIMITS 
-DEXPERIMENTAL_SCRUBBING_SCROLL_WHEEL 

Bug#1037583: audmes: ftbfs with GCC-13

[Matthias Klose]

Package: src:audmes
Version: 2022.10.09-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/audmes_2022.10.09-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
wxWidgets lib settings: 
-L/usr/lib/x86_64-linux-gnu;-pthread;;;-lwx_gtk3u_core-3.2;-lwx_baseu-3.2
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_RUNSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
FETCHCONTENT_FULLY_DISCONNECTED


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
   dh_auto_build
cd obj-x86_64-linux-gnu && make -j8 "INSTALL=install 
--strip-program=true" VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/AudMeS.dir/build.make CMakeFiles/AudMeS.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/AudMeS.dir/DependInfo.cmake 
--color=
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/AudMeS.dir/build.make CMakeFiles/AudMeS.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 14%] Building CXX object CMakeFiles/AudMeS.dir/dlg_audiointerface.cpp.o
[ 28%] Building C object CMakeFiles/AudMeS.dir/fourier.c.o
/usr/bin/c++ -DHAVE_GETTIMEOFDAY -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__LINUX__ -D__WXGTK__ -I/<>/. 
-isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -Wall -Wextra -std=gnu++11 -MD -MT 
CMakeFiles/AudMeS.dir/dlg_audiointerface.cpp.o -MF 
CMakeFiles/AudMeS.dir/dlg_audiointerface.cpp.o.d -o 
CMakeFiles/AudMeS.dir/dlg_audiointerface.cpp.o -c 
/<>/dlg_audiointerface.cpp
/usr/bin/cc -DHAVE_GETTIMEOFDAY -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__LINUX__ -D__WXGTK__ -I/<>/. 
-isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -MD -MT CMakeFiles/AudMeS.dir/fourier.c.o -MF 
CMakeFiles/AudMeS.dir/fourier.c.o.d -o CMakeFiles/AudMeS.dir/fourier.c.o -c 
/<>/fourier.c
[ 57%] Building CXX object CMakeFiles/AudMeS.dir/CtrlOScope.cpp.o
[ 57%] Building CXX object CMakeFiles/AudMeS.dir/AudMeS.cpp.o
[ 71%] Building CXX object CMakeFiles/AudMeS.dir/RWAudio_IO.cpp.o
/usr/bin/c++ -DHAVE_GETTIMEOFDAY -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__LINUX__ -D__WXGTK__ -I/<>/. 
-isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -Wall -Wextra -std=gnu++11 -MD -MT 
CMakeFiles/AudMeS.dir/CtrlOScope.cpp.o -MF 
CMakeFiles/AudMeS.dir/CtrlOScope.cpp.o.d -o 
CMakeFiles/AudMeS.dir/CtrlOScope.cpp.o -c /<>/CtrlOScope.cpp
[ 85%] Building CXX object CMakeFiles/AudMeS.dir/rtaudio/RtAudio.cpp.o
/usr/bin/c++ -DHAVE_GETTIMEOFDAY -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__LINUX__ -D__WXGTK__ -I/<>/. 
-isystem 

Bug#1015713: zam-plugins: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:zam-plugins
Version: 3.14~repack3-1
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/zam-plugins_3.14~repack3-1_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
dh clean
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make \
PREFIX=/usr \
NOOPT=false
make[2]: Entering directory '/<>'
/usr/bin/make -C dpf/dgl
make[3]: Entering directory '/<>/dpf/dgl'
Compiling src/Application.cpp
Compiling src/Color.cpp
Compiling src/Geometry.cpp
Compiling src/ImageBase.cpp
Compiling src/Resources.cpp
Compiling src/Widget.cpp
Compiling src/OpenGL.cpp (OpenGL variant)
Compiling src/Image.cpp (OpenGL variant)
Compiling src/ImageWidgets.cpp (OpenGL variant)
Compiling src/NanoVG.cpp (OpenGL variant)
Compiling src/WidgetPrivateData.cpp (OpenGL variant)
Compiling src/Window.cpp (OpenGL variant)
Creating libdgl-opengl.a
Symlinking libdgl.a
make[3]: Leaving directory '/<>/dpf/dgl'
/usr/bin/make -C plugins/ZamComp
make[3]: Entering directory '/<>/plugins/ZamComp'
Compiling ZamCompPlugin.cpp
Compiling ZamCompArtwork.cpp
Compiling ZamCompUI.cpp
ZamCompUI.cpp: In member function ‘virtual void 
DISTRHO::ZamCompUI::onDisplay()’:
ZamCompUI.cpp:278:5: warning: this ‘for’ clause does not guard... 
[-Wmisleading-indentation]
  278 | for (int i=numRedLeds; i>0; --i)
  | ^~~
ZamCompUI.cpp:281:9: note: ...this statement, but the latter is misleadingly 
indented as if it were guarded by the ‘for’
  281 | if (fLedYellowValue >= 20.f)
  | ^~
Compiling DistrhoPluginMain.cpp (JACK)
Compiling DistrhoUIMain.cpp (JACK)
Creating JACK standalone for ZamComp
In function ‘fons__freeFont’,
inlined from ‘fonsAddFontMem’ at 
../../dpf/dgl/src/nanovg/fontstash.h:919:16,
inlined from ‘nvgCreateFontMem’ at 
../../dpf/dgl/src/nanovg/nanovg.c:2164:23,
inlined from ‘loadSharedResources’ at ../../dpf/dgl/src/NanoVG.cpp:925:21:
../../dpf/dgl/src/nanovg/fontstash.h:821:47: warning: ‘free’ called on 
unallocated object ‘temp1’ [-Wfree-nonheap-object]
  821 | if (font->freeData && font->data) free((void*)font->data);
  |   ^
../../dpf/dgl/src/nanovg/fontstash.h: In member function ‘loadSharedResources’:
../../dpf/dgl/src/Resources.cpp:5:28: note: declared here
5 | static const unsigned char temp1[] = 
{0,1,0,0,0,19,1,0,0,4,0,48,70,70,84,77,102,9,29,176,0,0,1,60,0,0,0,28,71,68,69,70,144,48,138,184,0,0,1,88,
  |^
/usr/bin/ld: /tmp/cc99AiZl.ltrans0.ltrans.o: in function 
`DGL::ZamKnob::onDisplay()':
./plugins/ZamComp/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
/usr/bin/ld: ./plugins/ZamComp/../../dpf/dgl/src/Geometry.cpp:906: undefined 
reference to `DGL::Rectangle::_draw(bool)'
/usr/bin/ld: /tmp/cc99AiZl.ltrans1.ltrans.o: in function 
`DGL::Image::_drawAt(DGL::Point const&)':
./plugins/ZamComp/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
collect2: error: ld returned 1 exit status
make[3]: *** [../../dpf/Makefile.plugins.mk:174: ../../bin/ZamComp] Error 1
make[3]: Leaving directory '/<>/plugins/ZamComp'
make[2]: *** [Makefile:32: ZamComp] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Bug#1015678: taglib: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:taglib
Version: 1.12-1
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/taglib_1.12-1_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
  _ZTIN6TagLib4MPEG6HeaderE@Base 1.9.1-2.2~
  _ZTIN6TagLib4RIFF3WAV10PropertiesE@Base 1.9.1-2.2~
  _ZTIN6TagLib4RIFF3WAV4FileE@Base 1.9.1-2.2~
@@ -2379,11 +2379,11 @@
  _ZTIN6TagLib5ID3v25FrameE@Base 1.9.1-2.2~
  _ZTIN6TagLib5ID3v26FooterE@Base 1.9.1-2.2~
  _ZTIN6TagLib5ID3v26HeaderE@Base 1.9.1-2.2~
- (optional=lto)_ZTIN6TagLib6String13StringPrivateE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# (optional=lto)_ZTIN6TagLib6String13StringPrivateE@Base 
1.9.1-2.2~
  _ZTIN6TagLib6StringE@Base 1.9.1-2.2~
  _ZTIN6TagLib6Vorbis10PropertiesE@Base 1.9.1-2.2~
  _ZTIN6TagLib6Vorbis4FileE@Base 1.9.1-2.2~
- (optional=lto)_ZTIN6TagLib7FileRef14FileRefPrivateE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# (optional=lto)_ZTIN6TagLib7FileRef14FileRefPrivateE@Base 
1.9.1-2.2~
  _ZTIN6TagLib7FileRefE@Base 1.9.1-2.2~
  _ZTIN6TagLib7WavPack10PropertiesE@Base 1.9.1-2.2~
  _ZTIN6TagLib7WavPack4FileE@Base 1.9.1-2.2~
@@ -2538,21 +2538,21 @@
  _ZTVN6TagLib3ASF4File11FilePrivate24ContentDescriptionObjectE@Base 1.11
  _ZTVN6TagLib3ASF4File11FilePrivate32ExtendedContentDescriptionObjectE@Base 
1.11
  _ZTVN6TagLib3ASF4FileE@Base 1.9.1-2.2~
- (optional=lto)_ZTVN6TagLib3ASF7Picture14PicturePrivateE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# (optional=lto)_ZTVN6TagLib3ASF7Picture14PicturePrivateE@Base 
1.9.1-2.2~
  _ZTVN6TagLib3ASF7PictureE@Base 1.9.1-2.2~
- (optional=lto)_ZTVN6TagLib3ASF9Attribute16AttributePrivateE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# 
(optional=lto)_ZTVN6TagLib3ASF9Attribute16AttributePrivateE@Base 1.9.1-2.2~
  _ZTVN6TagLib3ASF9AttributeE@Base 1.9.1-2.2~
  _ZTVN6TagLib3MP410PropertiesE@Base 1.9.1-2.2~
  _ZTVN6TagLib3MP43TagE@Base 1.9.1-2.2~
  _ZTVN6TagLib3MP44FileE@Base 1.9.1-2.2~
- (optional=lto)_ZTVN6TagLib3MP44Item11ItemPrivateE@Base 1.9.1-2.2~
- (optional=lto)_ZTVN6TagLib3MP48CoverArt15CoverArtPrivateE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# (optional=lto)_ZTVN6TagLib3MP44Item11ItemPrivateE@Base 
1.9.1-2.2~
+#MISSING: 1.12-1# 
(optional=lto)_ZTVN6TagLib3MP48CoverArt15CoverArtPrivateE@Base 1.9.1-2.2~
  _ZTVN6TagLib3MPC10PropertiesE@Base 1.9.1-2.2~
  _ZTVN6TagLib3MPC4FileE@Base 1.9.1-2.2~
  _ZTVN6TagLib3Mod10PropertiesE@Base 1.9.1-2.2~
  _ZTVN6TagLib3Mod3TagE@Base 1.9.1-2.2~
  _ZTVN6TagLib3Mod4FileE@Base 1.9.1-2.2~
- (optional=lto)_ZTVN6TagLib3Mod8FileBaseE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# (optional=lto)_ZTVN6TagLib3Mod8FileBaseE@Base 1.9.1-2.2~
  _ZTVN6TagLib3Ogg10PageHeaderE@Base 1.9.1-2.2~
  _ZTVN6TagLib3Ogg11XiphCommentE@Base 1.9.1-2.2~
  _ZTVN6TagLib3Ogg4FLAC4FileE@Base 1.9.1-2.2~
@@ -2574,7 +2574,7 @@
  _ZTVN6TagLib4MPEG10PropertiesE@Base 1.9.1-2.2~
  _ZTVN6TagLib4MPEG10XingHeaderE@Base 1.9.1-2.2~
  _ZTVN6TagLib4MPEG4FileE@Base 1.9.1-2.2~
- (optional=lto)_ZTVN6TagLib4MPEG6Header13HeaderPrivateE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# (optional=lto)_ZTVN6TagLib4MPEG6Header13HeaderPrivateE@Base 
1.9.1-2.2~
  _ZTVN6TagLib4MPEG6HeaderE@Base 1.9.1-2.2~
  _ZTVN6TagLib4RIFF3WAV10PropertiesE@Base 1.9.1-2.2~
  _ZTVN6TagLib4RIFF3WAV4FileE@Base 1.9.1-2.2~
@@ -2613,11 +2613,11 @@
  _ZTVN6TagLib5ID3v25FrameE@Base 1.9.1-2.2~
  _ZTVN6TagLib5ID3v26FooterE@Base 1.9.1-2.2~
  _ZTVN6TagLib5ID3v26HeaderE@Base 1.9.1-2.2~
- (optional=lto)_ZTVN6TagLib6String13StringPrivateE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# (optional=lto)_ZTVN6TagLib6String13StringPrivateE@Base 
1.9.1-2.2~
  _ZTVN6TagLib6StringE@Base 1.9.1-2.2~
  _ZTVN6TagLib6Vorbis10PropertiesE@Base 1.9.1-2.2~
  _ZTVN6TagLib6Vorbis4FileE@Base 1.9.1-2.2~
- (optional=lto)_ZTVN6TagLib7FileRef14FileRefPrivateE@Base 1.9.1-2.2~
+#MISSING: 1.12-1# (optional=lto)_ZTVN6TagLib7FileRef14FileRefPrivateE@Base 
1.9.1-2.2~
  _ZTVN6TagLib7FileRefE@Base 1.9.1-2.2~
  _ZTVN6TagLib7WavPack10PropertiesE@Base 

Bug#1015549: mpeg2dec: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:mpeg2dec
Version: 0.5.1-9
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/mpeg2dec_0.5.1-9_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
Making check in test
make[2]: Entering directory '/<>/test'
make  check-TESTS
make[3]: Entering directory '/<>/test'
make[4]: Entering directory '/<>/test'
SKIP: compile
SKIP: regression
FAIL: globals
=
   libmpeg2 0.5.1: test/test-suite.log
=

# TOTAL: 3
# PASS:  0
# SKIP:  2
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

SKIP: regression


SKIP regression (exit status: 77)

SKIP: compile
=

SKIP compile (exit status: 77)

FAIL: globals
=

BAD GLOBAL SYMBOLS in /<>/test/../libmpeg2/.libs/libmpeg2.so:
idct_alpha.c.0f630beb
idct_altivec.c.86e8576d
motion_comp_alpha.c.86adf087
motion_comp_altivec.c.8092a501
motion_comp_arm.c.9d6ac4b9
motion_comp_vis.c.f5289281
BAD GLOBAL SYMBOLS in 
/<>/test/../libmpeg2/convert/.libs/libmpeg2convert.so:
rgb_vis.c.42fa1640
FAIL globals (exit status: 1)


Testsuite summary for libmpeg2 0.5.1

# TOTAL: 3
# PASS:  0
# SKIP:  2
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log

make[4]: *** [Makefile:535: test-suite.log] Error 1
make[4]: Leaving directory '/<>/test'
make[3]: *** [Makefile:643: check-TESTS] Error 2
make[3]: Leaving directory '/<>/test'
make[2]: *** [Makefile:729: check-am] Error 2
make[2]: Leaving directory '/<>/test'
make[1]: *** [Makefile:408: check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
returned exit code 2
make: *** [debian/rules:32: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Bug#1015532: libvpx: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:libvpx
Version: 1.11.0-2
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/libvpx_1.11.0-2_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
a - vp9/encoder/vp9_mbgraph.c.o
a - vp9/encoder/x86/temporal_filter_sse4.c.o
a - vp9/encoder/x86/vp9_quantize_sse2.c.o
a - vp9/encoder/x86/vp9_quantize_avx2.c.o
a - vp9/encoder/x86/vp9_diamond_search_sad_avx.c.o
a - vp9/encoder/x86/vp9_highbd_block_error_intrin_sse2.c.o
a - vp9/encoder/x86/highbd_temporal_filter_sse4.c.o
a - vp9/encoder/x86/vp9_dct_intrin_sse2.c.o
a - vp9/encoder/x86/vp9_frame_scale_ssse3.c.o
a - vp9/encoder/x86/vp9_denoiser_sse2.c.o
a - vp9/encoder/x86/vp9_error_avx2.c.o
a - vp9/common/x86/vp9_mfqe_sse2.asm.o
a - vp9/encoder/x86/vp9_dct_sse2.asm.o
a - vp9/encoder/x86/vp9_error_sse2.asm.o
a - vp9/encoder/x86/vp9_quantize_ssse3_x86_64.asm.o
a - vp9/ratectrl_rtc.cc.o
ar -crsv libgtest_g.a third_party/googletest/src/src/gtest-all.cc.o
strip --strip-debug \
  -o libvpx.a libvpx_g.a
a - third_party/googletest/src/src/gtest-all.cc.o
strip --strip-debug \
  -o libvp9rc.a libvp9rc_g.a
strip --strip-debug \
  -o libgtest.a libgtest_g.a
mkdir -p vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/
cp -p libvpx.a vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/libvpx.a
./vp9/encoder/vp9_bitstream.c: In function ‘encode_tile_worker’:
./vp9/encoder/vp9_bitstream.c:948:3: warning: ‘write_modes’ accessing 64 bytes 
in a region of size 16 [-Wstringop-overflow=]
./vp9/encoder/vp9_bitstream.c:948:3: note: referencing argument 8 of type 
‘int[4] *’
./vp9/encoder/vp9_bitstream.c:488:13: note: in a call to function ‘write_modes’
./vp8/decoder/threading.c: In function ‘vp8mt_alloc_temp_buffers.part.0’:
./vp8/decoder/threading.c:768:7: warning: ‘memset’ specified bound between 
18446744071562068032 and 18446744073709551592 exceeds maximum object size 
9223372036854775807 [-Wstringop-overflow=]
./vp8/decoder/threading.c:776:7: warning: ‘memset’ specified bound between 
18446744072635809824 and 18446744073709551592 exceeds maximum object size 
9223372036854775807 [-Wstringop-overflow=]
./vp8/decoder/threading.c:784:7: warning: ‘memset’ specified bound between 
18446744072635809824 and 18446744073709551592 exceeds maximum object size 
9223372036854775807 [-Wstringop-overflow=]
[LN]  libvpx.so.7.0.0 libvpx.so
[LN]  libvpx.so.7.0.0 libvpx.so.7
mkdir -p ./
[LN]  libvpx.so.7.0.0 libvpx.so.7.0
mkdir -p ./
mkdir -p ./
[LN]  libvpx.so.7.0.0 vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/libvpx.so
mkdir -p vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/
ln -sf  libvpx.so.7.0.0 libvpx.so
ln -sf  libvpx.so.7.0.0 libvpx.so.7
ln -sf  libvpx.so.7.0.0 libvpx.so.7.0
ln -sf  libvpx.so.7.0.0 vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/libvpx.so
[LN]  libvpx.so.7.0.0 vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/libvpx.so.7
mkdir -p vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/
mkdir -p vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/
[LN]  libvpx.so.7.0.0 vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/libvpx.so.7.0
mkdir -p vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/
ln -sf  libvpx.so.7.0.0 vpx-vp8-vp9-x86_64-linux-v1.11.0/lib/libvpx.so.7
g++ -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -m64 -o test_libvpx 
ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o 

Bug#1015530: libva: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:libva
Version: 2.14.0-1
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/libva_2.14.0-1_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libva-x11.so.2.1400.0 libva-x11.so.2 || { rm -f libva-x11.so.2 && ln 
-s libva-x11.so.2.1400.0 libva-x11.so.2; }; })
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libva-x11.so.2.1400.0 libva-x11.so || { rm -f libva-x11.so && ln -s 
libva-x11.so.2.1400.0 libva-x11.so; }; })
libtool: install: /usr/bin/install -c .libs/libva-x11.lai 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libva-x11.la
libtool: warning: relinking 'libva-glx.la'
libtool: install: (cd /<>/va; /bin/bash "/<>/libtool" 
 --tag CC --mode=relink gcc -Wall -fstack-protector -g -O2 
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -fstack-protector 
-version-info 1402:0:1400 -flto=auto -ffat-lto-objects -Wl,-z,relro -o 
libva-glx.la -rpath /usr/lib/x86_64-linux-gnu libva.la glx/libva_glx.la 
libva-x11.la -lGL -lX11 -ldl -inst-prefix-dir /<>/debian/tmp)
libtool: relink: gcc -shared  -fPIC -DPIC  -Wl,--whole-archive 
glx/.libs/libva_glx.a -Wl,--no-whole-archive  
-L/<>/debian/tmp/usr/lib/x86_64-linux-gnu 
-L/usr/lib/x86_64-linux-gnu -lva -lva-x11 -lGL -lX11 -ldl  -fstack-protector -g 
-O2 -flto=auto -fstack-protector-strong -fstack-protector -flto=auto -Wl,-z 
-Wl,relro   -Wl,-soname -Wl,libva-glx.so.2 -o .libs/libva-glx.so.2.1400.0
libtool: install: /usr/bin/install -c .libs/libva-glx.so.2.1400.0T 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libva-glx.so.2.1400.0
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libva-glx.so.2.1400.0 libva-glx.so.2 || { rm -f libva-glx.so.2 && ln 
-s libva-glx.so.2.1400.0 libva-glx.so.2; }; })
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libva-glx.so.2.1400.0 libva-glx.so || { rm -f libva-glx.so && ln -s 
libva-glx.so.2.1400.0 libva-glx.so; }; })
libtool: install: /usr/bin/install -c .libs/libva-glx.lai 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libva-glx.la
libtool: warning: relinking 'libva-wayland.la'
libtool: install: (cd /<>/va; /bin/bash "/<>/libtool" 
 --tag CC --mode=relink gcc -Wall -fstack-protector -g -O2 
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -fstack-protector 
-version-info 1402:0:1400 -flto=auto -ffat-lto-objects -Wl,-z,relro -o 
libva-wayland.la -rpath /usr/lib/x86_64-linux-gnu libva.la 
wayland/libva_wayland.la -lwayland-client -ldrm -ldl -inst-prefix-dir 
/<>/debian/tmp)
libtool: relink: gcc -shared  -fPIC -DPIC  -Wl,--whole-archive 
wayland/.libs/libva_wayland.a -Wl,--no-whole-archive  
-L/<>/debian/tmp/usr/lib/x86_64-linux-gnu 
-L/usr/lib/x86_64-linux-gnu -lva -lwayland-client -ldrm -ldl  -fstack-protector 
-g -O2 -flto=auto -fstack-protector-strong -fstack-protector -flto=auto -Wl,-z 
-Wl,relro   -Wl,-soname -Wl,libva-wayland.so.2 -o 
.libs/libva-wayland.so.2.1400.0
libtool: install: /usr/bin/install -c .libs/libva-wayland.so.2.1400.0T 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libva-wayland.so.2.1400.0
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libva-wayland.so.2.1400.0 libva-wayland.so.2 || { rm -f 
libva-wayland.so.2 && ln -s libva-wayland.so.2.1400.0 libva-wayland.so.2; }; })
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libva-wayland.so.2.1400.0 libva-wayland.so || { rm -f libva-wayland.so 
&& ln -s libva-wayland.so.2.1400.0 libva-wayland.so; }; })
libtool: install: /usr/bin/install -c .libs/libva-wayland.lai 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libva-wayland.la
libtool: warning: remember to run 

Bug#1015402: ffmpeg: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:ffmpeg
Version: 7:4.4.2-1
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/ffmpeg_4.4.2-1_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/ffmpeg-bitstream-filters.texi 
doc/ffmpeg-bitstream-filters.pod
perl /<>/doc/texidep.pl /<> 
/<>/doc/ffmpeg-formats.texi doc/ffmpeg-formats.pod 
>doc/ffmpeg-formats.pod.d
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/ffmpeg-formats.texi doc/ffmpeg-formats.pod
perl /<>/doc/texidep.pl /<> 
/<>/doc/ffmpeg-protocols.texi doc/ffmpeg-protocols.pod 
>doc/ffmpeg-protocols.pod.d
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/ffmpeg-protocols.texi doc/ffmpeg-protocols.pod
perl /<>/doc/texidep.pl /<> 
/<>/doc/ffmpeg-devices.texi doc/ffmpeg-devices.pod 
>doc/ffmpeg-devices.pod.d
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/ffmpeg-devices.texi doc/ffmpeg-devices.pod
perl /<>/doc/texidep.pl /<> 
/<>/doc/ffmpeg-filters.texi doc/ffmpeg-filters.pod 
>doc/ffmpeg-filters.pod.d
perl /<>/doc/texidep.pl /<> 
/<>/doc/libavutil.texi doc/libavutil.pod >doc/libavutil.pod.d
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/libavutil.texi doc/libavutil.pod
perl /<>/doc/texidep.pl /<> 
/<>/doc/libswscale.texi doc/libswscale.pod >doc/libswscale.pod.d
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/ffmpeg-filters.texi doc/ffmpeg-filters.pod
perl /<>/doc/texidep.pl /<> 
/<>/doc/libswresample.texi doc/libswresample.pod 
>doc/libswresample.pod.d
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/libswscale.texi doc/libswscale.pod
perl /<>/doc/texidep.pl /<> 
/<>/doc/libavcodec.texi doc/libavcodec.pod >doc/libavcodec.pod.d
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/libswresample.texi doc/libswresample.pod
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/libavcodec.texi doc/libavcodec.pod
perl /<>/doc/texidep.pl /<> 
/<>/doc/libavformat.texi doc/libavformat.pod >doc/libavformat.pod.d
perl /<>/doc/texidep.pl /<> 
/<>/doc/libavdevice.texi doc/libavdevice.pod >doc/libavdevice.pod.d
perl /<>/doc/texidep.pl /<> 
/<>/doc/libavfilter.texi doc/libavfilter.pod >doc/libavfilter.pod.d
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/libavformat.texi doc/libavformat.pod
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffmpeg.pod > 
doc/ffmpeg.1
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/libavdevice.texi doc/libavdevice.pod
perl /<>/doc/texi2pod.pl -Dconfig-not-all=yes -Idoc 
/<>/doc/libavfilter.texi doc/libavfilter.pod
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffplay.pod > 
doc/ffplay.1
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffprobe.pod > 
doc/ffprobe.1
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffmpeg-all.pod > 
doc/ffmpeg-all.1
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffplay-all.pod > 
doc/ffplay-all.1
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffprobe-all.pod > 
doc/ffprobe-all.1
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffmpeg-utils.pod 
> doc/ffmpeg-utils.1
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffmpeg-scaler.pod 
> doc/ffmpeg-scaler.1
pod2man --section=1 --center=" " --release=" " --date=" " 
doc/ffmpeg-resampler.pod > doc/ffmpeg-resampler.1
pod2man --section=1 --center=" " --release=" " --date=" " doc/ffmpeg-codecs.pod 
> doc/ffmpeg-codecs.1
pod2man --section=1 --center=" " --release=" " --date=" " 
doc/ffmpeg-bitstream-filters.pod > doc/ffmpeg-bitstream-filters.1
pod2man --section=1 --center=" " --release=" " --date=" " 
doc/ffmpeg-formats.pod > doc/ffmpeg-formats.1
pod2man --section=1 --center=" " --release=" " --date=" " 
doc/ffmpeg-protocols.pod > 

Bug#1015389: dpf-plugins: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:dpf-plugins
Version: 1.4-1
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/dpf-plugins_1.4-1_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
# Kars
make all -C plugins/Kars
make[2]: Entering directory '/<>/plugins/Kars'
Compiling DistrhoPluginKars.cpp
Compiling DistrhoPluginMain.cpp (JACK)
Compiling DistrhoPluginMain.cpp (DSSI)
Compiling DistrhoPluginMain.cpp (LV2)
Compiling DistrhoPluginMain.cpp (VST)
Creating DSSI plugin library for Kars
Creating JACK standalone for Kars
Creating VST plugin for Kars
Creating LV2 plugin library for Kars
make[2]: Leaving directory '/<>/plugins/Kars'
# Mini-Series
make all -C plugins/3BandEQ
make[2]: Entering directory '/<>/plugins/3BandEQ'
Compiling DistrhoPlugin3BandEQ.cpp
Compiling DistrhoArtwork3BandEQ.cpp
Compiling DistrhoUI3BandEQ.cpp
Compiling DistrhoPluginMain.cpp (JACK)
Compiling DistrhoUIMain.cpp (JACK)
Compiling DistrhoPluginMain.cpp (LADSPA)
Compiling DistrhoPluginMain.cpp (VST)
Compiling DistrhoUIMain.cpp (VST)
Compiling DistrhoPluginMain.cpp (DSSI)
Compiling DistrhoUIMain.cpp (DSSI)
Compiling DistrhoPluginMain.cpp (LV2)
Compiling DistrhoUIMain.cpp (LV2)
Creating LADSPA plugin for 3BandEQ
Creating DSSI plugin library for 3BandEQ
Creating DSSI UI for 3BandEQ
Creating JACK standalone for 3BandEQ
Creating LV2 plugin UI for 3BandEQ
Creating VST plugin for 3BandEQ
Creating LV2 plugin library for 3BandEQ
/usr/bin/ld: /usr/bin/ld: /tmp/ccTzHHPu.ltrans0.ltrans.o: in function 
`DGL::Image::_drawAt(DGL::Point const&)':
./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
/usr/bin/ld: /tmp/ccTzHHPu.ltrans0.ltrans.o: in function 
`DGL::ImageKnob::onDisplay()':
./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
/usr/bin/ld: ./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined 
reference to `DGL::Rectangle::_draw(bool)'
/tmp/cclIavR2.ltrans0.ltrans.o: in function 
`DGL::Image::_drawAt(DGL::Point const&)':
./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
/usr/bin/ld: /tmp/cclIavR2.ltrans0.ltrans.o: in function 
`DGL::ImageKnob::onDisplay()':
./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
/usr/bin/ld: ./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined 
reference to `DGL::Rectangle::_draw(bool)'
collect2: error: ld returned 1 exit status
make[2]: *** [../../dpf/Makefile.plugins.mk:201: 
../../bin/3BandEQ-dssi/3BandEQ_ui] Error 1
make[2]: *** Waiting for unfinished jobs
collect2: error: ld returned 1 exit status
make[2]: *** [../../dpf/Makefile.plugins.mk:174: ../../bin/3BandEQ] Error 1
/usr/bin/ld: /tmp/ccPCnjbX.ltrans0.ltrans.o: in function 
`DGL::Image::_drawAt(DGL::Point const&)':
./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
/usr/bin/ld: /tmp/ccPCnjbX.ltrans0.ltrans.o: in function 
`DGL::ImageKnob::onDisplay()':
./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
/usr/bin/ld: ./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined 
reference to `DGL::Rectangle::_draw(bool)'
collect2: error: ld returned 1 exit status
make[2]: *** [../../dpf/Makefile.plugins.mk:223: 
../../bin/3BandEQ.lv2/3BandEQ_ui.so] Error 1
/usr/bin/ld: /tmp/cc1zxJra.ltrans0.ltrans.o: in function 
`DGL::Image::_drawAt(DGL::Point const&)':
./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 
`DGL::Rectangle::_draw(bool)'
/usr/bin/ld: /tmp/cc1zxJra.ltrans0.ltrans.o: in function 
`DGL::ImageKnob::onDisplay()':
./plugins/3BandEQ/../../dpf/dgl/src/Geometry.cpp:906: undefined reference to 

Bug#1015371: cmt: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:cmt
Version: 1.18-1
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/cmt_1.18-1_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
   dh_auto_build -O--sourcedirectory=src
cd src && make -j8 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>/src'
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o am.o am.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o ambisonic.o ambisonic.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o amp.o amp.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o analogue.o analogue.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o canyondelay.o canyondelay.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o cmt.o cmt.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o descriptor.o descriptor.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o delay.o delay.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dynamic.o dynamic.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o filter.o filter.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o freeverb/Components/allpass.o 
freeverb/Components/allpass.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o freeverb/Components/comb.o 
freeverb/Components/comb.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o freeverb/Components/revmodel.o 
freeverb/Components/revmodel.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o freeverb/freeverb.o 
freeverb/freeverb.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o grain.o grain.cpp
g++ -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security  -Wall -Werror -O2 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2  -c -o init.o init.cpp
g++ -g -O2 

Bug#1015366: cheesecutter: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:cheesecutter
Version: 2.9+git20211011-1
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/cheesecutter_2.9+git20211011-1_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/derelict/sdl/macinit/NSZone.o 
src/derelict/sdl/macinit/NSZone.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/derelict/sdl/macinit/runtime.o 
src/derelict/sdl/macinit/runtime.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/derelict/sdl/macinit/SDLMain.o 
src/derelict/sdl/macinit/SDLMain.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/derelict/sdl/macinit/selectors.o 
src/derelict/sdl/macinit/selectors.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/derelict/sdl/macinit/string.o 
src/derelict/sdl/macinit/string.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/audio/audio.o src/audio/audio.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/audio/player.o src/audio/player.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/audio/timer.o src/audio/timer.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/audio/callback.o src/audio/callback.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/com/fb.o src/com/fb.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/com/kbd.o src/com/kbd.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/com/session.o src/com/session.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/main.o src/main.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/ui/tables.o src/ui/tables.d
src/ui/tables.d:226:44: warning: module ct.base is not accessible here, perhaps 
add 'static import ct.base;' [-Wdeprecated]
  226 | song.tableIterator((ct.base.Song.Table t) {
  |^
src/ui/tables.d:259:44: warning: module ct.base is not accessible here, perhaps 
add 'static import ct.base;' [-Wdeprecated]
  259 | song.tableIterator((ct.base.Song.Table t) {
  |^
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/ui/dialogs.o src/ui/dialogs.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/ui/help.o src/ui/help.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/ui/ui.o src/ui/ui.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/ui/input.o src/ui/input.d
gdc -O2 -g -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-I./src -J./src/c64 -J./src/font -c -o src/seq/seqtable.o src/seq/seqtable.d
gdc -O2 -g 

Bug#1015356: audacious: ftbfs with LTO (link time optimization) enabled

[Matthias Klose]

Package: src:audacious
Version: 4.1-2
Severity: minor
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-lto

This package currently fails to build (at least on the amd64
architecture) with link time optimizations enabled.  For a background
for LTO please see

https://wiki.debian.org/ToolChain/LTO

The goal is to enable this optimization by default in an upcoming
Debian release in dpkg-buildflags for 64bit architectures.  The goal
is to get this package to build with link time optimizations, or to
explicitly disable link time optimizations for this package build.

To reproduce the build failure, enable the lto optimization in
testing/unstable by adding "optimize=+lto" to DEB_BUILD_MAINT_OPTIONS
in the debian/rules file, or if this macro is unset, just set it:

export DEB_BUILD_MAINT_OPTIONS = optimize=+lto

Please try to fix the build with lto enabled, fixing the packaging or
forwarding the issue upstream. If the issue cannot be fixed,
explicitly disallow building the package with lto by adding to your
rules file:

export DEB_BUILD_MAINT_OPTIONS = optimize=-lto

or adding that string to your existing setting of DEB_BUILD_MAINT_OPTIONS.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/dpkglto/audacious_4.1-2_unstable_dpkglto.log
The last lines of the build log are at the end of this report.

[...]
  (c++)"std::_Function_handler 
>::_M_manager(std::_Any_data&, std::_Any_data const&, 
std::_Manager_operation)@Base" 4.1
  (c++)"std::_Function_handler::_M_invoke(std::_Any_data 
const&)@Base" 4.1
  (c++)"std::_Function_handler::_M_manager(std::_Any_data&, std::_Any_data const&, 
std::_Manager_operation)@Base" 4.1
  (c++|optional|regex)"std::once_flag::.*@Base" 4.0.5
- (c++)"std::thread::_State_impl > 
>::_M_run()@Base" 4.0
- (c++)"std::thread::_State_impl > 
>::~_State_impl()@Base" 4.0
- (c++)"std::thread::_State_impl > >::_M_run()@Base" 4.0
- (c++)"std::thread::_State_impl > >::~_State_impl()@Base" 4.0
- (c++)"std::thread::~thread()@Base" 4.0
- (c++|optional)"std::unique_lock::unlock()@Base" 4.0.5
+#MISSING: 4.1-2# 
(c++)"std::thread::_State_impl > 
>::_M_run()@Base" 4.0
+#MISSING: 4.1-2# 
(c++)"std::thread::_State_impl > 
>::~_State_impl()@Base" 4.0
+#MISSING: 4.1-2# 
(c++)"std::thread::_State_impl > >::_M_run()@Base" 4.0
+#MISSING: 4.1-2# 
(c++)"std::thread::_State_impl > >::~_State_impl()@Base" 4.0
+#MISSING: 4.1-2# (c++)"std::thread::~thread()@Base" 4.0
+#MISSING: 4.1-2# (c++|optional)"std::unique_lock::unlock()@Base" 
4.0.5
  (c++)"str_append_printf(StringBuf&, char const*, ...)@Base" 4.0
  (c++)"str_calc_hash(char const*)@Base" 3.8
  (c++)"str_compare(char const*, char const*)@Base" 3.8
@@ -439,8 +439,8 @@
  (c++)"typeinfo for std::_Weak_result_type@Base" 4.1
  (c++)"typeinfo for std::_Weak_result_type_impl@Base" 4.1
  (c++)"typeinfo for std::_Weak_result_type_memfun@Base" 4.1
- (c++)"typeinfo for 
std::thread::_State_impl > >@Base" 
4.0
- (c++)"typeinfo for 
std::thread::_State_impl > >@Base" 4.0
+#MISSING: 4.1-2# (c++)"typeinfo for 
std::thread::_State_impl > >@Base" 
4.0
+#MISSING: 4.1-2# (c++)"typeinfo for 
std::thread::_State_impl > >@Base" 4.0
  (c++)"typeinfo for void ()@Base" 4.1
  (c++)"typeinfo for void (*)()@Base" 4.1
  (c++)"typeinfo name for IniParser@Base" 3.8
@@ -465,5 +465,5 @@
  (c++)"uri_to_filename(char const*, bool)@Base" 3.8
  (c++)"vfs_async_file_get_contents(char const*, std::function const&)>)@Base" 4.0
  (c++)"vfs_async_file_get_contents(char const*, void (*)(char const*, 
Index const&, void*), void*)@Base" 3.8
- (c++)"vtable for 
std::thread::_State_impl > >@Base" 
4.0
- (c++)"vtable for 
std::thread::_State_impl > >@Base" 4.0
+#MISSING: 4.1-2# (c++)"vtable for 
std::thread::_State_impl > >@Base" 
4.0
+#MISSING: 4.1-2# (c++)"vtable for 
std::thread::_State_impl > >@Base" 4.0
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libaudqt2/DEBIAN/symbols doesn't match 
completely debian/libaudqt2.symbols
--- debian/libaudqt2.symbols (libaudqt2_4.1-2_amd64)
+++ dpkg-gensymbols8DDllo   2022-06-10 08:59:44.131613021 +
@@ -1,11 +1,11 @@
 libaudqt.so.2 libaudqt2 #MINVER#
- (c++)"QByteArray::~QByteArray()@Base" 3.7.1
- (c++)"QString::~QString()@Base" 3.7.1
+#MISSING: 4.1-2# (c++)"QByteArray::~QByteArray()@Base" 3.7.1
+#MISSING: 4.1-2# (c++)"QString::~QString()@Base" 3.7.1
  (c++)"audqt::ColorButton::ColorButton(QWidget*)@Base" 4.0
- (c++)"audqt::ColorButton::onColorChanged()@Base" 4.0
+#MISSING: 4.1-2# (c++)"audqt::ColorButton::onColorChanged()@Base" 4.0
  (c++)"audqt::ColorButton::paintEvent(QPaintEvent*)@Base" 4.0
  (c++)"audqt::ColorButton::setColor(QColor const&)@Base" 4.0
- (c++)"audqt::ColorButton::~ColorButton()@Base" 4.0
+#MISSING: 4.1-2# (c++)"audqt::ColorButton::~ColorButton()@Base" 4.0
  (c++)"audqt::DockItem::DockItem(char const*, char const*, QWidget*)@Base" 4.1
  (c++)"audqt::DockItem::find_by_plugin(PluginHandle*)@Base" 4.1
  

Bug#1012977: libffado: ftbfs with GCC-12

[Matthias Klose]

Package: src:libffado
Version: 2.4.5-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/libffado_2.4.5-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
/usr/include/dbus-c++-1/dbus-c++/types.h:332:77: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const bool&’
  332 | inline DBus::MessageIter  << (DBus::MessageIter , const 
bool )
  | 
^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:338:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const int16_t&)’
  338 | inline DBus::MessageIter  << (DBus::MessageIter , const 
int16_t )
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:338:80: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const int16_t&’ {aka ‘const short int&’}
  338 | inline DBus::MessageIter  << (DBus::MessageIter , const 
int16_t )
  | 
~~~^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:344:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const uint16_t&)’
  344 | inline DBus::MessageIter  << (DBus::MessageIter , const 
uint16_t )
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:344:81: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const uint16_t&’ {aka ‘const short unsigned int&’}
  344 | inline DBus::MessageIter  << (DBus::MessageIter , const 
uint16_t )
  | 
^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:350:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const int32_t&)’
  350 | inline DBus::MessageIter  << (DBus::MessageIter , const 
int32_t )
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:350:80: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const int32_t&’ {aka ‘const int&’}
  350 | inline DBus::MessageIter  << (DBus::MessageIter , const 
int32_t )
  | 
~~~^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:356:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const uint32_t&)’
  356 | inline DBus::MessageIter  << (DBus::MessageIter , const 
uint32_t )
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:356:81: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const uint32_t&’ {aka ‘const unsigned int&’}
  356 | inline DBus::MessageIter  << (DBus::MessageIter , const 
uint32_t )
  | 
^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:362:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const int64_t&)’
  362 | inline DBus::MessageIter  << (DBus::MessageIter , const 
int64_t )
  |   ^~~~
/usr/include/dbus-c++-1/dbus-c++/types.h:362:80: note:   no known conversion 
for argument 2 from ‘const DBus::Struct, 
double>’ to ‘const int64_t&’ {aka ‘const long int&’}
  362 | inline DBus::MessageIter  << (DBus::MessageIter , const 
int64_t )
  | 
~~~^~~
/usr/include/dbus-c++-1/dbus-c++/types.h:368:27: note: candidate: 
‘DBus::MessageIter& operator<<(DBus::MessageIter&, const uint64_t&)’
  368 | inline DBus::MessageIter  

Bug#1012954: juce: ftbfs with GCC-12

[Matthias Klose]

Package: src:juce
Version: 6.1.6~ds0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/juce_6.1.6~ds0-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  ignore line: 
[COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/12/:/usr/lib/gcc/x86_64-linux-gnu/12/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/12/:/usr/lib/gcc/x86_64-linux-gnu/]
  ignore line: 
[LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/12/:/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/12/../../../:/lib/:/usr/lib/]
  ignore line: [COLLECT_GCC_OPTIONS='-g' '-O2' 
'-ffile-prefix-map=/<>=.' '-fstack-protector-strong' '-Wformat=1' 
'-Wdate-time' '-D' '_FORTIFY_SOURCE=2' '-D' 'JUCER_ENABLE_GPL_MODE=1' '-v' '-o' 
'cmTC_2d782' '-shared-libgcc' '-mtune=generic' '-march=x86-64' '-dumpdir' 
'cmTC_2d782.']
  link line: [ /usr/lib/gcc/x86_64-linux-gnu/12/collect2 -plugin 
/usr/lib/gcc/x86_64-linux-gnu/12/liblto_plugin.so 
-plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper 
-plugin-opt=-fresolution=/tmp/ccT3SnLT.res -plugin-opt=-pass-through=-lgcc_s 
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc 
-plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --build-id 
--eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker 
/lib64/ld-linux-x86-64.so.2 -pie -o cmTC_2d782 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o 
/usr/lib/gcc/x86_64-linux-gnu/12/crtbeginS.o -L/usr/lib/gcc/x86_64-linux-gnu/12 
-L/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu 
-L/usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib -L/lib/x86_64-linux-gnu 
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
-L/usr/lib/gcc/x86_64-linux-gnu/12/../../.. -z relro -z now CMakeFiles/cmTC_2d78
 2.dir/CMakeCXXCompilerABI.cpp.o -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc 
/usr/lib/gcc/x86_64-linux-gnu/12/crtendS.o 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crtn.o]
arg [/usr/lib/gcc/x86_64-linux-gnu/12/collect2] ==> ignore
arg [-plugin] ==> ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/12/liblto_plugin.so] ==> ignore
arg [-plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper] ==> ignore
arg [-plugin-opt=-fresolution=/tmp/ccT3SnLT.res] ==> ignore
arg [-plugin-opt=-pass-through=-lgcc_s] ==> ignore
arg [-plugin-opt=-pass-through=-lgcc] ==> ignore
arg [-plugin-opt=-pass-through=-lc] ==> ignore
arg [-plugin-opt=-pass-through=-lgcc_s] ==> ignore
arg [-plugin-opt=-pass-through=-lgcc] ==> ignore
arg [--build-id] ==> ignore
arg [--eh-frame-hdr] ==> ignore
arg [-m] ==> ignore
arg [elf_x86_64] ==> ignore
arg [--hash-style=gnu] ==> ignore
arg [--as-needed] ==> ignore
arg [-dynamic-linker] ==> ignore
arg [/lib64/ld-linux-x86-64.so.2] ==> ignore
arg [-pie] ==> ignore
arg [-o] ==> ignore
arg [cmTC_2d782] ==> ignore
arg [/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o] 
==> obj [/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o]
arg [/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o] ==> 
obj [/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o]
arg [/usr/lib/gcc/x86_64-linux-gnu/12/crtbeginS.o] ==> obj 
[/usr/lib/gcc/x86_64-linux-gnu/12/crtbeginS.o]
arg [-L/usr/lib/gcc/x86_64-linux-gnu/12] ==> dir 
[/usr/lib/gcc/x86_64-linux-gnu/12]
arg 

Bug#1012947: iem-plugin-suite: ftbfs with GCC-12

[Matthias Klose]

Package: src:iem-plugin-suite
Version: 1.13.0-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/iem-plugin-suite_1.13.0-2_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
/usr/share/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:504:18: 
error: ‘exchange’ is not a member of ‘std’
  504 | if (std::exchange (style, s) != style)
  |  ^~~~
In file included from 
/usr/share/juce/modules/juce_gui_basics/juce_gui_basics.h:271,
 from 
/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.h:57,
 from 
/<>/obj-x86_64-linux-gnu/DirectivityShaper/DirectivityShaper_artefacts/JuceLibraryCode/../JuceLibraryCode/JuceHeader.h:14,
 from 
/<>/resources/OSC/../customComponents/SimpleLabel.h:24,
 from /<>/resources/OSC/OSCStatus.h:25,
 from /<>/resources/OSC/OSCStatus.cpp:24:
/usr/share/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h: In member 
function ‘void juce::ComponentPeer::setAppStyle(Style)’:
/usr/share/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:504:18: 
error: ‘exchange’ is not a member of ‘std’
  504 | if (std::exchange (style, s) != style)
  |  ^~~~
In file included from 
/usr/share/juce/modules/juce_gui_basics/juce_gui_basics.h:271,
 from 
/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.h:57,
 from 
/<>/obj-x86_64-linux-gnu/DirectivityShaper/DirectivityShaper_artefacts/JuceLibraryCode/JuceHeader.h:14,
 from 
/<>/resources/Standalone/StandaloneApp.cpp:53:
/usr/share/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h: In member 
function ‘void juce::ComponentPeer::setAppStyle(Style)’:
/usr/share/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:504:18: 
error: ‘exchange’ is not a member of ‘std’
  504 | if (std::exchange (style, s) != style)
  |  ^~~~
In file included from 
/<>/resources/Standalone/StandaloneApp.cpp:58:
/<>/resources/Standalone/MyStandaloneFilterWindow.h: In member 
function ‘void MyStandalonePluginHolder::setupAudioDevices(bool, const 
juce::String&, const juce::AudioDeviceManager::AudioDeviceSetup*)’:
/<>/resources/Standalone/MyStandaloneFilterWindow.h:588:44: 
warning: ‘void juce::AudioDeviceManager::addMidiInputCallback(const 
juce::String&, juce::MidiInputCallback*)’ is deprecated: Use 
addMidiInputDeviceCallback instead. [-Wdeprecated-declarations]
  588 | deviceManager.addMidiInputCallback ({}, );
  | ~~~^
In file included from 
/usr/share/juce/modules/juce_audio_devices/juce_audio_devices.h:186,
 from 
/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.h:58:
/usr/share/juce/modules/juce_audio_devices/audio_io/juce_AudioDeviceManager.h:480:10:
 note: declared here
  480 | void addMidiInputCallback (const String&, MidiInputCallback*);
  |  ^~~~
/<>/resources/Standalone/MyStandaloneFilterWindow.h: In member 
function ‘void MyStandalonePluginHolder::shutDownAudioDevices()’:
/<>/resources/Standalone/MyStandaloneFilterWindow.h:597:47: 
warning: ‘void juce::AudioDeviceManager::removeMidiInputCallback(const 
juce::String&, juce::MidiInputCallback*)’ is deprecated: Use 
removeMidiInputDeviceCallback instead. [-Wdeprecated-declarations]
  597 | deviceManager.removeMidiInputCallback ({}, );
  | ~~^

Bug#1012936: giada: ftbfs with GCC-12

[Matthias Klose]

Package: src:giada
Version: 0.21.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/giada_0.21.0-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
 from /<>/src/core/engine.h:32,
 from /<>/src/core/engine.cpp:27:
/<>/src/deps/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:
 In member function ‘void juce::ComponentPeer::setAppStyle(Style)’:
/<>/src/deps/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:504:18:
 error: ‘exchange’ is not a member of ‘std’
  504 | if (std::exchange (style, s) != style)
  |  ^~~~
In file included from 
/<>/src/deps/juce/modules/juce_gui_basics/juce_gui_basics.h:271,
 from 
/<>/src/deps/juce/modules/juce_audio_processors/juce_audio_processors.h:57,
 from /<>/src/deps/juce-config.h:6,
 from /<>/src/core/plugins/pluginManager.h:34,
 from /<>/src/core/mixerHandler.h:30,
 from /<>/src/core/mixerHandler.cpp:27:
/<>/src/deps/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:
 In member function ‘void juce::ComponentPeer::setAppStyle(Style)’:
/<>/src/deps/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:504:18:
 error: ‘exchange’ is not a member of ‘std’
  504 | if (std::exchange (style, s) != style)
  |  ^~~~
In file included from 
/<>/src/deps/juce/modules/juce_gui_basics/juce_gui_basics.h:271,
 from 
/<>/src/deps/juce/modules/juce_audio_processors/juce_audio_processors.h:57,
 from /<>/src/deps/juce-config.h:6,
 from /<>/src/core/channels/channel.h:32,
 from /<>/src/core/model/model.h:30,
 from /<>/src/core/sequencer.cpp:32:
/<>/src/deps/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:
 In member function ‘void juce::ComponentPeer::setAppStyle(Style)’:
/<>/src/deps/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:504:18:
 error: ‘exchange’ is not a member of ‘std’
  504 | if (std::exchange (style, s) != style)
  |  ^~~~
In file included from /<>/src/core/engine.cpp:31:
/<>/src/utils/log.h: In instantiation of ‘void 
giada::u::log::print(const char*, Args&& ...) [with Args = {}]’:
/<>/src/core/engine.cpp:167:16:   required from here
/<>/src/utils/log.h:84:29: warning: format not a string literal 
and no format arguments [-Wformat-security]
   84 | std::fprintf(f, format, 
string_to_c_str(std::forward(args))...);
  | 
^
/<>/src/utils/log.h:90:28: warning: format not a string literal 
and no format arguments [-Wformat-security]
   90 | std::printf(format, 
string_to_c_str(std::forward(args))...);
  | 
~~~^~
In file included from 
/<>/src/deps/juce/modules/juce_gui_basics/juce_gui_basics.h:271,
 from 
/<>/src/deps/juce/modules/juce_audio_processors/juce_audio_processors.h:57,
 from /<>/src/deps/juce-config.h:6,
 from /<>/src/core/channels/channel.h:32,
 from /<>/src/core/channels/channelManager.h:30,
 from /<>/src/core/engine.h:32,
 from /<>/src/core/init.cpp:30:
/<>/src/deps/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:
 In member function ‘void juce::ComponentPeer::setAppStyle(Style)’:
/<>/src/deps/juce/modules/juce_gui_basics/windows/juce_ComponentPeer.h:504:18:
 error: ‘exchange’ is 

Bug#1012899: bambootracker: ftbfs with GCC-12

[Matthias Klose]

Package: src:bambootracker
Version: 0.5.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/bambootracker_0.5.0-1_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra 
-Werror -pedantic -pedantic-errors -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -D_REENTRANT -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iinstrument -Imodule 
-I../submodules/emu2149/src -I/usr/include/rtaudio -I/usr/include/rtmidi 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
order_list_common_qt_command.o 
gui/command/order/order_list_common_qt_command.cpp
g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra 
-Werror -pedantic -pedantic-errors -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -D_REENTRANT -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iinstrument -Imodule 
-I../submodules/emu2149/src -I/usr/include/rtaudio -I/usr/include/rtmidi 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
pattern_editor_common_qt_command.o 
gui/command/pattern/pattern_editor_common_qt_command.cpp
g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra 
-Werror -pedantic -pedantic-errors -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -D_REENTRANT -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iinstrument -Imodule 
-I../submodules/emu2149/src -I/usr/include/rtaudio -I/usr/include/rtmidi 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o drop_detect_list_widget.o 
gui/drop_detect_list_widget.cpp
g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra 
-Werror -pedantic -pedantic-errors -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS 
-D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -D_REENTRANT -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iinstrument -Imodule 
-I../submodules/emu2149/src -I/usr/include/rtaudio -I/usr/include/rtmidi 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o effect_description.o 
gui/effect_description.cpp
g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra 
-Werror -pedantic -pedantic-errors 

Bug#989206: fix ftbfs with glib2.0 from experimental

[Matthias Klose]

Package: src:guitarix
Version: 0.42.1+dfsg1-2
Tags: patch

this is upstream issue
https://sourceforge.net/p/guitarix/patches/12/

but it's not GCC 11 causing the issue, but glib2.0 from experimental.

package patch at
http://launchpadlibrarian.net/540849775/guitarix_0.42.1+dfsg1-2_0.42.1+dfsg1-2ubuntu1.diff.gz

Bug#983927: gsequencer: ftbfs with -march=x86-64-v2

[Matthias Klose]

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] http://people.debian.org/~doko/gcc/gcc10-v3 ./

Bug#984394: vlc: ftbfs with GCC-11

[Matthias Klose]

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 is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/vlc_3.0.12-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
libtool: link: echo "{ global:" > .libs/libmpgv_plugin.ver
libtool: link:  cat .libs/libmpgv_plugin.exp | sed -e "s/\(.*\)/\1;/" >> 
.libs/libmpgv_plugin.ver
libtool: link:  echo "local: *; };" >> .libs/libmpgv_plugin.ver
libtool: link:  gcc -shared  -fPIC -DPIC  demux/mpeg/.libs/mpgv.o   -Wl,-rpath 
-Wl,/<>/src/.libs ../compat/.libs/libcompat.a 
../src/.libs/libvlccore.so  -g -O2 -fstack-protector-strong -O3 -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,defs   -Wl,-soname -Wl,libmpgv_plugin.so 
-Wl,-version-script -Wl,.libs/libmpgv_plugin.ver -o .libs/libmpgv_plugin.so
libtool: link: ( cd ".libs" && rm -f "libmpgv_plugin.la" && ln -s 
"../libmpgv_plugin.la" "libmpgv_plugin.la" )
../doltcompile gcc -DHAVE_CONFIG_H -I. -I..  
-DMODULE_STRING=\"$(p="demux/playlist/b4s.lo"; p="${p##*/}"; p="${p#lib}"; 
p="${p%_plugin*}"; p=$(echo "$p"|sed 's/-/_/g'); p="${p%.lo}"; echo "$p")\" 
-D__PLUGIN__  -I./access -I./codec -I../include -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Wextra 
-Wsign-compare -Wundef -Wpointer-arith -Wvolatile-register-var 
-Wformat-security -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes 
-Werror-implicit-function-declaration -Winit-self -Wlogical-op -Wshadow=local 
-pipe -fvisibility=hidden -O3 -fno-math-errno -funsafe-math-optimizations 
-fno-rounding-math -fno-signaling-nans -fcx-limited-range -funroll-loops 
-fomit-frame-pointer -c -o demux/playlist/b4s.lo demux/playlist/b4s.c
../doltcompile gcc -DHAVE_CONFIG_H -I. -I..  
-DMODULE_STRING=\"$(p="demux/playlist/dvb.lo"; p="${p##*/}"; p="${p#lib}"; 
p="${p%_plugin*}"; p=$(echo "$p"|sed 's/-/_/g'); p="${p%.lo}"; echo "$p")\" 
-D__PLUGIN__  -I./access -I./codec -I../include -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Wextra 
-Wsign-compare -Wundef -Wpointer-arith -Wvolatile-register-var 
-Wformat-security -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes 
-Werror-implicit-function-declaration -Winit-self -Wlogical-op -Wshadow=local 
-pipe -fvisibility=hidden -O3 -fno-math-errno -funsafe-math-optimizations 
-fno-rounding-math -fno-signaling-nans -fcx-limited-range -funroll-loops 
-fomit-frame-pointer -c -o demux/playlist/dvb.lo demux/playlist/dvb.c
../doltcompile gcc -DHAVE_CONFIG_H -I. -I..  
-DMODULE_STRING=\"$(p="demux/playlist/ifo.lo"; p="${p##*/}"; p="${p#lib}"; 
p="${p%_plugin*}"; p=$(echo "$p"|sed 's/-/_/g'); p="${p%.lo}"; echo "$p")\" 
-D__PLUGIN__  -I./access -I./codec -I../include -I../include -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security   -Wall -Wextra 
-Wsign-compare -Wundef -Wpointer-arith -Wvolatile-register-var 
-Wformat-security -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes 
-Werror-implicit-function-declaration -Winit-self -Wlogical-op -Wshadow=local 
-pipe -fvisibility=hidden -O3 -fno-math-errno -funsafe-math-optimizations 
-fno-rounding-math -fno-signaling-nans -fcx-limited-range -funroll-loops 
-fomit-frame-pointer -c -o demux/playlist/ifo.lo demux/playlist/ifo.c
../doltcompile gcc -DHAVE_CONFIG_H -I. -I..  
-DMODULE_STRING=\"$(p="demux/playlist/itml.lo"; p="${p##*/}"; p="${p#lib}"; 
p="${p%_plugin*}"; p=$(echo "$p"|sed 's/-/_/g'); p="${p%.lo}"; echo 

Bug#984357: synfigstudio: ftbfs with GCC-11

[Matthias Klose]

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 another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/synfigstudio_1.4.0+dfsg-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
/usr/include/c++/11/chrono:3366:28: error: expected ‘;’ before ‘{’ token
 3366 |   return __sys_time{__t.time_since_epoch()} + _S_epoch_diff;
  |^
/usr/include/c++/11/chrono:3366:51: error: expected ‘;’ before ‘}’ token
 3366 |   return __sys_time{__t.time_since_epoch()} + _S_epoch_diff;
  |   ^
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../..  -I../../src -I../../libltdl -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -pthread -D_REENTRANT 
-I/usr/include/synfig-1.0 -I/usr/include/x86_64-linux-gnu//ImageMagick-6 
-I/usr/include/ImageMagick-6 -I/usr/include/x86_64-linux-gnu//ImageMagick-6 
-I/usr/include/ImageMagick-6 -I/usr/include/x86_64-linux-gnu//ImageMagick-6 
-I/usr/include/ImageMagick-6 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/OpenEXR -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/libxml++-2.6 
-I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include -I/usr/include/libxml2 
-I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
-I/usr/include/pango-1.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/inc
 lude/fribidi -I/usr/include/harfbuzz -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/mlt++ -I/usr/include/mlt 
-I/usr/include/ETL -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -DLOCALEDIR=\"/usr//locale\" 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -DNDEBUG -W -Wall -c -o 
libsynfigapp_la-inputdevice.lo `test -f 'inputdevice.cpp' || echo 
'./'`inputdevice.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../libltdl 
-Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 
-DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 
-DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 
-DMAGICKCORE_QUANTUM_DEPTH=16 -pthread -D_REENTRANT -I/usr/include/synfig-1.0 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu -I/usr/include/OpenEXR -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/libxml++-2.6 
-I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include -I/usr/include/libxml2 
-I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
-I/usr/include/pango-1.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/fribidi -I/usr/include/harfbu
 zz -I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/mlt++ -I/usr/include/mlt -I/usr/include/ETL 
-I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-DLOCALEDIR=\"/usr//locale\" 

Bug#984355: synfig: ftbfs with GCC-11

[Matthias Klose]

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 is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/synfig_1.4.0+dfsg-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
In file included from /usr/include/ETL/ETL/clock:56,
 from target_tile.cpp:37:
/usr/include/ETL/ETL/_clock_system.h:34:27: error: using-declaration for 
non-member at class scope
   34 | # define __sys_clock::clock
  |   ^
In file included from /usr/include/c++/11/mutex:39,
 from node.h:40,
 from valuenode.h:39,
 from canvas.h:40,
 from target.h:39,
 from target_tile.h:32,
 from target_tile.cpp:39:
/usr/include/c++/11/chrono:3341:25: error: expected ‘;’ before ‘=’ token
 3341 |   using __sys_clock = chrono::system_clock;
  | ^
/usr/include/c++/11/chrono:3341:25: error: expected unqualified-id before ‘=’ 
token
/usr/include/c++/11/chrono:3353:63: error: type/value mismatch at argument 1 in 
template parameter list for ‘template struct 
std::chrono::time_point’
 3353 | _S_from_sys(const chrono::time_point<__sys_clock, _Dur>& __t) 
noexcept
  |   ^
/usr/include/c++/11/chrono:3353:63: note:   expected a type, got ‘clock’
/usr/include/c++/11/chrono:3362:45: error: type/value mismatch at argument 1 in 
template parameter list for ‘template struct 
std::chrono::time_point’
 3362 | chrono::time_point<__sys_clock, _Dur>
  | ^
/usr/include/c++/11/chrono:3362:45: note:   expected a type, got ‘clock’
/usr/include/c++/11/chrono: In static member function ‘static 
std::filesystem::__file_clock::time_point std::filesystem::__file_clock::now()’:
/usr/include/c++/11/chrono:3323:55: error: no matching function for call to 
‘std::filesystem::__file_clock::_S_from_sys(std::chrono::_V2::system_clock::time_point)’
 3323 |   { return _S_from_sys(chrono::system_clock::now()); }
  |   ^
/usr/include/c++/11/chrono:3353:9: note: candidate: ‘template 
static std::chrono::time_point 
std::filesystem::__file_clock::_S_from_sys(const int&)’
 3353 | _S_from_sys(const chrono::time_point<__sys_clock, _Dur>& __t) 
noexcept
  | ^~~
/usr/include/c++/11/chrono:3353:9: note:   template argument 
deduction/substitution failed:
/usr/include/c++/11/chrono:3323:55: note:   couldn’t deduce template parameter 
‘_Dur’
 3323 |   { return _S_from_sys(chrono::system_clock::now()); }
  |   ^
/usr/include/c++/11/chrono: In static member function ‘static 
std::chrono::time_point 
std::filesystem::__file_clock::_S_from_sys(const int&)’:
/usr/include/c++/11/chrono:3356:34: error: request for member 
‘time_since_epoch’ in ‘__t’, which is of non-class type ‘const int’
 3356 |   return __file_time{__t.time_since_epoch()} - _S_epoch_diff;
  |  ^~~~
/usr/include/c++/11/chrono: In static member function ‘static int 
std::filesystem::__file_clock::_S_to_sys(const 
std::chrono::time_point&)’:
/usr/include/c++/11/chrono:3365:28: error: expected ‘;’ before ‘=’ token
 3365 |   using __sys_time = chrono::time_point<__sys_clock, _Dur>;
  |^
/usr/include/c++/11/chrono:3365:28: error: expected primary-expression before 
‘=’ token

Bug#984294: photoflow: ftbfs with GCC-11

[Matthias Klose]

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 in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/photoflow_0.2.8+git20200114-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
[ 45%] Building CXX object src/CMakeFiles/pfgui.dir/gui/widgets/layerlist.cc.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DLENSFUN_HAS_OVERLOADED_FIND_LENSES=1 
-DVIPS_GET_BLOB_REQUIRES_CONST_VOID_POINTER=1 -I/usr/include/gtkmm-3.0 
-I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 
-I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 
-I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
-I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 
-I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freet
 ype2 -I/usr/include/libpng16 -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/<>/src/external 
-I/usr/include/OpenEXR -I/usr/include/libxml2 -I/usr/include/orc-0.4 
-I/usr/include/libgsf-1 -I/usr/include/x86_64-linux-gnu/ImageMagick-6 
-I/usr/include/ImageMagick-6 -I/usr/include/poppler/glib -I/usr/include/poppler 
-I/usr/include/librsvg-2.0 -I/usr/include/openslide 
-I/usr/lib/x86_64-linux-gnu/hdf5/serial/include -I/<>/src 
-I/<>/src/external/rawspeed/src/librawspeed 
-I/<>/src/external/rawspeed/src/external 
-I/<>/obj-x86_64-linux-gnu/src/external/rawspeed/src 
-I/usr/include/lensfun -I/<>/src/external/librtprocess/src/include 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FOR
 TIFY_SOURCE=2 -DPF_HAS_LENSFUN   -O3 -ftree-vectorize -funroll-loops 
-fomit-frame-pointer -DNDEBUG  -Dgmic_build -Dcimg_use_vt100 -Dcimg_use_fftw3 
-Dcimg_use_tiff -Dcimg_use_zlib -Dcimg_display=0 -fpermissive -std=gnu++14 
-Wno-error=narrowing -Dgmic_is_parallel -fno-ipa-sra -march=nocona 
-mtune=generic -I/<>/src/dt -DLIBRAW_NODLL 
-DINSTALL_PREFIX='"/usr"'  -Wno-deprecated-register 
-Wno-deprecated-declarations -DLOCALEDIR="/usr/share/locale" -DGTKMM_3  
-Wno-unused-parameter -fPIC -o CMakeFiles/pfgui.dir/gui/widgets/layerlist.cc.o 
-c /<>/src/gui/widgets/layerlist.cc
[ 45%] Building CXX object 
src/CMakeFiles/pfgui.dir/gui/widgets/lensfun_selector.cc.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DLENSFUN_HAS_OVERLOADED_FIND_LENSES=1 
-DVIPS_GET_BLOB_REQUIRES_CONST_VOID_POINTER=1 -I/usr/include/gtkmm-3.0 
-I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 
-I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 
-I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
-I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 

Bug#984263: ocp: ftbfs with GCC-11

[Matthias Klose]

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 is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/ocp_0.2.2+ds-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
ac_ct_CC='gcc'
ac_ct_CC_FOR_BUILD='gcc'
ac_ct_CXX='g++'
bindir='${prefix}/bin'
build='x86_64-pc-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='pc'
datadir='${prefix}/share/ocp'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='/usr'
host='x86_64-pc-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
libdir='${prefix}/lib'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "ocp"
#define PACKAGE_TARNAME "ocp"
#define PACKAGE_VERSION "0.2.2"
#define PACKAGE_STRING "ocp 0.2.2"
#define PACKAGE_BUGREPORT "stian.skjels...@gmail.com"
#define PACKAGE_URL ""
#define DLLVERSION 0x0202
#define TIME_WITH_SYS_TIME 1
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define LIB_SUFFIX ".so"
#define DIR_SUFFIX ""

configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --prefix=/usr 
--exec-prefix=/usr --mandir=\${prefix}/share/man --sysconfdir=/etc 
--datadir=\${prefix}/share/ocp --libdir=\${prefix}/lib --bindir=\${prefix}/bin 
--infodir=\${prefix}/share/info --without-x11 --with-dir-suffix= --with-ncurses 
--with-adplug returned exit code 1
make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Bug#984117: faust: ftbfs with GCC-11

[Matthias Klose]

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 is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/faust_2.30.5~ds0-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
/<>/compiler/../architecture/faust/gui/JSONUI.h:176:69: error: 
‘::max_digits10’ has not been declared
  176 | fUI << 
std::setprecision(std::numeric_limits::max_digits10);
  | 
^~~~
/<>/compiler/../architecture/faust/gui/JSONUI.h:177:49: error: 
‘numeric_limits’ is not a member of ‘std’
  177 | fMeta << 
std::setprecision(std::numeric_limits::max_digits10);
  | ^~
/<>/compiler/../architecture/faust/gui/JSONUI.h:177:68: error: 
expected primary-expression before ‘>’ token
  177 | fMeta << 
std::setprecision(std::numeric_limits::max_digits10);
  |^
/<>/compiler/../architecture/faust/gui/JSONUI.h:177:71: error: 
‘::max_digits10’ has not been declared
  177 | fMeta << 
std::setprecision(std::numeric_limits::max_digits10);
  |   
^~~~
/<>/compiler/../architecture/faust/gui/JSONUI.h: In member 
function ‘std::string JSONUIReal::JSON(bool)’:
/<>/compiler/../architecture/faust/gui/JSONUI.h:394:48: error: 
‘numeric_limits’ is not a member of ‘std’
  394 | JSON << 
std::setprecision(std::numeric_limits::max_digits10);
  |^~
/<>/compiler/../architecture/faust/gui/JSONUI.h:394:67: error: 
expected primary-expression before ‘>’ token
  394 | JSON << 
std::setprecision(std::numeric_limits::max_digits10);
  |   ^
/<>/compiler/../architecture/faust/gui/JSONUI.h:394:70: error: 
‘::max_digits10’ has not been declared
  394 | JSON << 
std::setprecision(std::numeric_limits::max_digits10);
  |  
^~~~
In file included from /<>/compiler/generator/compile.hh:35,
 from /<>/compiler/generator/compile.cpp:38:
/<>/compiler/../architecture/faust/gui/JSONUI.h: In member 
function ‘void JSONUIReal::init(const string&, const string&, int, int, 
int, const string&, const string&, const string&, const string&, const 
std::vector >&, const 
std::vector >&, int, const 
std::map, int>&, bool)’:
/<>/compiler/../architecture/faust/gui/JSONUI.h:176:47: error: 
‘numeric_limits’ is not a member of ‘std’
  176 | fUI << 
std::setprecision(std::numeric_limits::max_digits10);
  |   ^~
/<>/compiler/../architecture/faust/gui/JSONUI.h:176:66: error: 
expected primary-expression before ‘>’ token
  176 | fUI << 
std::setprecision(std::numeric_limits::max_digits10);
  |  ^
/<>/compiler/../architecture/faust/gui/JSONUI.h:176:69: error: 
‘::max_digits10’ has not been declared
  176 | fUI << 
std::setprecision(std::numeric_limits::max_digits10);
  | 
^~~~
/<>/compiler/../architecture/faust/gui/JSONUI.h:177:49: error: 
‘numeric_limits’ is not a member of ‘std’
  177 | fMeta << 

Bug#984099: libebml: ftbfs with GCC-11

[Matthias Klose]

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 is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libebml_1.4.2-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/ebml.dir/build.make CMakeFiles/ebml.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/ebml.dir/DependInfo.cmake 
--color=
Dependee 
"/<>/obj-x86_64-linux-gnu/CMakeFiles/ebml.dir/DependInfo.cmake" is 
newer than depender 
"/<>/obj-x86_64-linux-gnu/CMakeFiles/ebml.dir/depend.internal".
Dependee 
"/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeDirectoryInformation.cmake"
 is newer than depender 
"/<>/obj-x86_64-linux-gnu/CMakeFiles/ebml.dir/depend.internal".
Scanning dependencies of target ebml
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f CMakeFiles/ebml.dir/build.make CMakeFiles/ebml.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  4%] Building CXX object CMakeFiles/ebml.dir/src/EbmlContexts.cpp.o
/usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<> -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden 
-std=gnu++11 -o CMakeFiles/ebml.dir/src/EbmlContexts.cpp.o -c 
/<>/src/EbmlContexts.cpp
[ 12%] Building CXX object CMakeFiles/ebml.dir/src/EbmlBinary.cpp.o
[ 12%] Building CXX object CMakeFiles/ebml.dir/src/Debug.cpp.o
/usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<> -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden 
-std=gnu++11 -o CMakeFiles/ebml.dir/src/Debug.cpp.o -c 
/<>/src/Debug.cpp
/usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<> -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden 
-std=gnu++11 -o CMakeFiles/ebml.dir/src/EbmlBinary.cpp.o -c 
/<>/src/EbmlBinary.cpp
[ 16%] Building CXX object CMakeFiles/ebml.dir/src/EbmlCrc32.cpp.o
/usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<> -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden 
-std=gnu++11 -o CMakeFiles/ebml.dir/src/EbmlCrc32.cpp.o -c 
/<>/src/EbmlCrc32.cpp
[ 20%] Building CXX object CMakeFiles/ebml.dir/src/EbmlDate.cpp.o
/usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<> -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden 
-std=gnu++11 -o CMakeFiles/ebml.dir/src/EbmlDate.cpp.o -c 
/<>/src/EbmlDate.cpp
[ 25%] Building CXX object CMakeFiles/ebml.dir/src/EbmlDummy.cpp.o
/usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<> -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden 
-std=gnu++11 -o CMakeFiles/ebml.dir/src/EbmlDummy.cpp.o -c 
/<>/src/EbmlDummy.cpp
[ 29%] Building CXX object CMakeFiles/ebml.dir/src/EbmlElement.cpp.o
/usr/bin/c++ -Debml_EXPORTS -I/<>/obj-x86_64-linux-gnu 

Bug#984053: etl: ftbfs with GCC-11

[Matthias Klose]

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 is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/etl_1.4.0-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
g++ -DHAVE_CONFIG_H -I. -I../ETL  -I.. -I../ETL -Wdate-time -D_FORTIFY_SOURCE=2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall -O2 -DNDEBUG -I.. -I../ETL 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall -O2 -DNDEBUG -c -o hermite.o hermite.cpp
angle.cpp: In function ‘int angle_test()’:
angle.cpp:205:17: error: reference to ‘hermite’ is ambiguous
  205 | hermite hermie(a,b,b.dist(a),b.dist(a));
  | ^~~
In file included from ../ETL/hermite:32,
 from angle.cpp:29:
../ETL/_hermite.h:135:7: note: candidates are: ‘template 
class etl::hermite’
  135 | class hermite : public bezier
  |   ^~~
In file included from /usr/include/c++/11/cmath:1927,
 from ../ETL/_fixed.h:33,
 from ../ETL/_curve_func.h:33,
 from ../ETL/angle:31,
 from angle.cpp:26:
/usr/include/c++/11/bits/specfun.h:918:5: note: ‘template typename __gnu_cxx::__promote<_Tp>::__type std::hermite(unsigned int, _Tp)’
  918 | hermite(unsigned int __n, _Tp __x)
  | ^~~
angle.cpp:205:30: error: expected primary-expression before ‘>’ token
  205 | hermite hermie(a,b,b.dist(a),b.dist(a));
  |  ^
angle.cpp:205:32: error: ‘hermie’ was not declared in this scope
  205 | hermite hermie(a,b,b.dist(a),b.dist(a));
  |^~
make[3]: *** [Makefile:677: angle.o] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from ../ETL/bezier:32,
 from ../ETL/_hermite.h:32,
 from ../ETL/hermite:32,
 from hermite.cpp:25:
../ETL/_bezier.h: In instantiation of ‘etl::bezier_base::value_type 
etl::bezier_base::operator()(etl::bezier_base::time_type) const 
[with V = float; T = etl::fixed_base; etl::bezier_base::value_type = float; etl::bezier_base::time_type = 
etl::fixed_base]’:
hermite.cpp:151:14:   required from here
../ETL/_bezier.h:98:18: warning: implicitly-declared ‘constexpr 
etl::fixed_base& etl::fixed_base::operator=(const 
etl::fixed_base&)’ is deprecated [-Wdeprecated-copy]
   98 | t=(t-r)/(s-r);
  | ~^~~~
In file included from ../ETL/_curve_func.h:33,
 from ../ETL/_bezier.h:33,
 from ../ETL/bezier:32,
 from ../ETL/_hermite.h:32,
 from ../ETL/hermite:32,
 from hermite.cpp:25:
../ETL/_fixed.h:181:1: note: because ‘etl::fixed_base’ has 
user-provided ‘etl::fixed_base::fixed_base(const _fixed&) [with 
T = int; unsigned int FIXED_BITS = 12; etl::fixed_base::_fixed = 
etl::fixed_base]’
  181 | fixed_base::fixed_base(const _fixed ):_data(x._data)
  | ^~~~
In file included from ../ETL/bezier:32,
 from ../ETL/_hermite.h:32,
 from ../ETL/hermite:32,
 from hermite.cpp:25:
../ETL/_bezier.h: In instantiation of ‘etl::bezier_base::value_type 
etl::bezier_base::operator()(etl::bezier_base::time_type) const 
[with V = etl::angle; T = etl::fixed_base; etl::bezier_base::value_type = etl::angle; etl::bezier_base::time_type = 
etl::fixed_base]’:
hermite.cpp:192:16:   required from here
../ETL/_bezier.h:98:18: warning: 

Bug#984040: drumgizmo: ftbfs with GCC-11

[Matthias Klose]

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 is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/drumgizmo_0.9.19-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../hugin -I../pugixml/src 
-DSSE -msse -msse2 -I../zita-resampler/libs -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c sample.cc -o 
libdg_la-sample.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-I../hugin -I../pugixml/src -DSSE -msse -msse2 -I../zita-resampler/libs 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffast-math 
-std=c++11 -DDISABLE_HUGIN -c -o libdg_la-staminafilter.lo `test -f 
'staminafilter.cc' || echo './'`staminafilter.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../hugin -I../pugixml/src 
-DSSE -msse -msse2 -I../zita-resampler/libs -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c 
staminafilter.cc  -fPIC -DPIC -o .libs/libdg_la-staminafilter.o
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-I../hugin -I../pugixml/src -DSSE -msse -msse2 -I../zita-resampler/libs 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffast-math 
-std=c++11 -DDISABLE_HUGIN -c -o libdg_la-thread.lo `test -f 'thread.cc' || 
echo './'`thread.cc
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-I../hugin -I../pugixml/src -DSSE -msse -msse2 -I../zita-resampler/libs 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffast-math 
-std=c++11 -DDISABLE_HUGIN -c -o libdg_la-velocityfilter.lo `test -f 
'velocityfilter.cc' || echo './'`velocityfilter.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../hugin -I../pugixml/src 
-DSSE -msse -msse2 -I../zita-resampler/libs -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c thread.cc  
-fPIC -DPIC -o .libs/libdg_la-thread.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../hugin -I../pugixml/src 
-DSSE -msse -msse2 -I../zita-resampler/libs -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c 
velocityfilter.cc  -fPIC -DPIC -o .libs/libdg_la-velocityfilter.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../hugin -I../pugixml/src 
-DSSE -msse -msse2 -I../zita-resampler/libs -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ffast-math -std=c++11 -DDISABLE_HUGIN -c thread.cc -o 
libdg_la-thread.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..   
-I../hugin -I../pugixml/src -DSSE -msse -msse2 -I../zita-resampler/libs 
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffast-math 
-std=c++11 -DDISABLE_HUGIN -c -o libdg_la-versionstr.lo `test -f 
'versionstr.cc' || echo './'`versionstr.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../hugin 

Bug#984033: din: ftbfs with GCC-11

[Matthias Klose]

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 is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/din_5.2.1-6_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
checking for libircclient.h... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for liblo... yes
checking for jack... yes
checking for fftw3f... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating include/Makefile
config.status: creating data/Makefile
config.status: executing depfiles commands
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
docbook-to-man debian/din.1.sgml > debian/din.1
dh_auto_build
make -j4
make[2]: Entering directory '/<>'
Making all in include
make[3]: Entering directory '/<>/include'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/include'
Making all in src
make[3]: Entering directory '/<>/src'
g++ -DPACKAGE_NAME=\"din\" -DPACKAGE_TARNAME=\"din\" 
-DPACKAGE_VERSION=\"5.2.1\" -DPACKAGE_STRING=\"din\ 5.2.1\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"din\" 
-DVERSION=\"5.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GL_GL_H=1 
-DHAVE_TCL8_6_TCL_H=1 -DHAVE_LIBIRCCLIENT_H=1 -I.   -Wdate-time 
-D_FORTIFY_SOURCE=2-I /usr/include -I /usr/local/include -I /opt/include 
-I/usr/include/tcl8.6 -I/usr/local/include/tcl8.6 -I /opt/include/tcl8.6 -I 
../include  -Wall -O3 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o main.o main.cc
g++ -DPACKAGE_NAME=\"din\" -DPACKAGE_TARNAME=\"din\" 
-DPACKAGE_VERSION=\"5.2.1\" -DPACKAGE_STRING=\"din\ 5.2.1\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"din\" 
-DVERSION=\"5.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GL_GL_H=1 
-DHAVE_TCL8_6_TCL_H=1 -DHAVE_LIBIRCCLIENT_H=1 -I.   -Wdate-time 
-D_FORTIFY_SOURCE=2-I /usr/include -I /usr/local/include -I /opt/include 
-I/usr/include/tcl8.6 -I/usr/local/include/tcl8.6 -I /opt/include/tcl8.6 -I 
../include  -Wall -O3 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o din.o din.cc
g++ -DPACKAGE_NAME=\"din\" -DPACKAGE_TARNAME=\"din\" 
-DPACKAGE_VERSION=\"5.2.1\" -DPACKAGE_STRING=\"din\ 5.2.1\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"din\" 
-DVERSION=\"5.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GL_GL_H=1 
-DHAVE_TCL8_6_TCL_H=1 -DHAVE_LIBIRCCLIENT_H=1 -I.   -Wdate-time 
-D_FORTIFY_SOURCE=2-I /usr/include -I /usr/local/include -I /opt/include 
-I/usr/include/tcl8.6 -I/usr/local/include/tcl8.6 -I /opt/include/tcl8.6 -I 
../include  -Wall -O3 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o audio.o audio.cc
g++ -DPACKAGE_NAME=\"din\" -DPACKAGE_TARNAME=\"din\" 
-DPACKAGE_VERSION=\"5.2.1\" -DPACKAGE_STRING=\"din\ 5.2.1\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"din\" 
-DVERSION=\"5.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 

Bug#984009: cheesecutter: ftbfs with GCC-11

[Matthias Klose]

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 in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/cheesecutter_2.9+git20191210-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-4ce1bd09-ae7e-4b24-ab9c-7341d373cc36
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package cheesecutter
dpkg-buildpackage: info: source version 2.9+git20191210-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Gürkan Myczko 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_auto_clean
make -j4 clean
make[1]: Entering directory '/<>'
Makefile:29: warning: ignoring prerequisites on suffix rule definition
Makefile:26: warning: ignoring prerequisites on suffix rule definition
rm -f *.o *~ resid/*.o resid-fp/*.o ccutter ct2util \
src/c64/player.bin src/derelict/util/compat.o 
src/derelict/util/sharedlib.o src/derelict/util/exception.o 
src/derelict/util/loader.o src/derelict/util/wintypes.o 
src/derelict/util/xtypes.o src/derelict/sdl/sdl.o src/derelict/sdl/net.o 
src/derelict/sdl/ttf.o src/derelict/sdl/mixer.o src/derelict/sdl/image.o 
src/derelict/sdl/sdlfuncs.o src/derelict/sdl/sdltypes.o 
src/derelict/sdl/macinit/CoreFoundation.o 
src/derelict/sdl/macinit/DerelictSDLMacLoader.o src/derelict/sdl/macinit/ID.o 
src/derelict/sdl/macinit/MacTypes.o src/derelict/sdl/macinit/NSApplication.o 
src/derelict/sdl/macinit/NSArray.o src/derelict/sdl/macinit/NSAutoreleasePool.o 
src/derelict/sdl/macinit/NSDictionary.o src/derelict/sdl/macinit/NSEnumerator.o 
src/derelict/sdl/macinit/NSEvent.o src/derelict/sdl/macinit/NSGeometry.o 
src/derelict/sdl/macinit/NSMenu.o src/derelict/sdl/macinit/NSMenuItem.o 
src/derelict/sdl/macinit/NSNotification.o src/derelict/sdl/macinit/NSObject.o 
src/derelict/sdl/macinit/NSProcessInfo.o src/derelict
 /sdl/macinit/NSString.o src/derelict/sdl/macinit/NSZone.o 
src/derelict/sdl/macinit/runtime.o src/derelict/sdl/macinit/SDLMain.o 
src/derelict/sdl/macinit/selectors.o src/derelict/sdl/macinit/string.o 
src/audio/audio.o src/audio/player.o src/audio/timer.o src/audio/callback.o 
src/ct/purge.o src/ct/base.o src/ct/dump.o src/com/fb.o src/com/cpu.o 
src/com/kbd.o src/com/session.o src/com/util.o src/main.o src/ui/tables.o 
src/ui/dialogs.o src/ui/ui.o src/ui/input.o src/ui/help.o src/seq/seqtable.o 
src/seq/tracktable.o src/seq/trackmap.o src/seq/fplay.o src/seq/sequencer.o 
src/audio/resid/filter.o  src/audio/resid/residctrl.o src/resid/envelope.o 
src/resid/extfilt.o src/resid/filter.o src/resid/w6_ps_.o src/resid/w6_pst.o 
src/resid/w6_p_t.o src/resid/w6__st.o src/resid/w8_ps_.o src/resid/w8_pst.o 
src/resid/w8_p_t.o src/resid/w8__st.o src/resid/pot.o src/resid/sid.o 
src/resid/voice.o src/resid/wave.o src/resid-fp/envelopefp.o 
src/resid-fp/extfiltfp.o src/resid-fp/filterfp.o src/resid-fp/potf
 p.o src/resid-fp/sidfp.o src/resid-fp/versionfp.o src/resid-fp/voicefp.o 
src/resid-fp/wavefp.o src/ct2util.o src/ct/base.o src/com/cpu.o src/com/util.o 
src/ct/purge.o src/ct/dump.o src/ct/build.o src/asm/acme.o src/asm/alu.o 
src/asm/basics.o src/asm/cpu.o src/asm/dynabuf.o 

Bug#983974: audacious: ftbfs with GCC-11

[Matthias Klose]

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 package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/audacious_4.0.5-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
Normalized 
debian/audacious/usr/share/locale/en_GB/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/ca/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/gl/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/bg/LC_MESSAGES/audacious.mo
Normalized 
debian/audacious/usr/share/locale/ml_IN/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/ru/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/nl/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/be/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/pl/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/fr/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/ko/LC_MESSAGES/audacious.mo
Normalized 
debian/audacious/usr/share/locale/id_ID/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/sv/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/sr/LC_MESSAGES/audacious.mo
Normalized debian/audacious/usr/share/locale/lv/LC_MESSAGES/audacious.mo
   dh_compress
   dh_fixperms
   dh_missing
   dh_dwz
   dh_strip
   dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libaudcore5/DEBIAN/symbols doesn't match 
completely debian/libaudcore5.symbols
--- debian/libaudcore5.symbols (libaudcore5_4.0.5-1_amd64)
+++ dpkg-gensymbolsO8k0qu   2021-03-01 21:01:33.472887325 +
@@ -211,6 +211,9 @@
  (c++|regex)"^str_append_vprintf\(StringBuf&, char const\*, 
(__va_list_tag\*?|char\*|std::__va_list|void\*)\)@Base" 4.0
  (c++|regex)"^str_format_time\((long|long long)\)@Base$" 3.8
  (c++|regex)"^str_vprintf\(char const\*, 
(__va_list_tag\*?|char\*|std::__va_list|void\*)\)@Base$" 3.9
+ _ZNSt11unique_lockISt5mutexE6unlockEv@Base 4.0.5-1
+ _ZNSt14_Function_baseD1Ev@Base 4.0.5-1
+ _ZNSt14_Function_baseD2Ev@Base 4.0.5-1
  (c++)"aud_art_data(AudArtItem const*)@Base" 3.9
  (c++)"aud_art_file(AudArtItem const*)@Base" 3.9
  (c++)"aud_art_request(char const*, int, bool*)@Base" 3.9
@@ -363,7 +366,7 @@
  (c++)"int_to_str(int)@Base" 3.8
  (c++)"mainloop_quit()@Base" 3.8
  (c++)"mainloop_run()@Base" 3.8
- (c++)"std::call_once(std::once_flag&, void 
(&)())::{lambda()#2}::_FUN()@Base" 4.0
+#MISSING: 4.0.5-1# (c++)"std::call_once(std::once_flag&, void 
(&)())::{lambda()#2}::_FUN()@Base" 4.0
  (c++)"std::thread::_State_impl > 
>::_M_run()@Base" 4.0
  (c++)"std::thread::_State_impl > 
>::~_State_impl()@Base" 4.0
  (c++)"std::thread::_State_impl > >::_M_run()@Base" 4.0
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libaudgui5/DEBIAN/symbols doesn't match 
completely debian/libaudgui5.symbols
--- debian/libaudgui5.symbols (libaudgui5_4.0.5-1_amd64)
+++ dpkg-gensymbolsfrpBiM   2021-03-01 21:01:33.596887372 +
@@ -75,3 +75,4 @@
  (c++)"audgui_urilist_insert(Playlist, int, char const*)@Base" 3.9
  (c++)"audgui_urilist_open(char const*)@Base" 3.8
  (c++)"audgui_vis_bar_color(_GdkColor const&, int, int, float&, float&, 

Bug#983927: gsequencer: ftbfs with -march=x86-64-v2

[Matthias Klose]

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 reports for packages building with
the current level (x86-64), but not with x86-64-v2.

To reproduce these issues, append -march=x86-64-v2 to the compiler
flags (CFLAGS, CXXFLAGS, ...).  You also need hardware supporting these.
The easiest way is to call the dynamic linker in glibc 2.33 like
  /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 --help
Otherwise look at the flags in /proc/cpuinfo and compare these with
those from table 3.1 in the System V Application Binary Interface doc:
https://gitlab.com/x86-psABIs/x86-64-ABI/-/wikis/x86-64-psABI

Please don't upload a package setting these flags by default.  The
x86-64 baseline is still unchanged.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc10-v2/gsequencer_3.7.38-1_unstable_gcc10-v2.log
The last lines of the build log are at the end of this report.

[...]
  |char *
In file included from ./ags/audio/midi/ags_midi_parser.h:26,
 from ags/audio/midi/ags_midi_parser.c:20:
/usr/include/libxml2/libxml/tree.h:791:22: note: expected ‘const xmlChar *’ 
{aka ‘const unsigned char *’} but argument is of type ‘char *’
  791 |   const xmlChar *name,
  |   ~~~^~~~
ags/audio/midi/ags_midi_parser.c:2854:4: warning: pointer targets in passing 
argument 3 of ‘xmlNewProp’ differ in signedness [-Wpointer-sign]
 2854 |text);
  |^~~~
  ||
  |gchar * {aka char *}
In file included from ./ags/audio/midi/ags_midi_parser.h:26,
 from ags/audio/midi/ags_midi_parser.c:20:
/usr/include/libxml2/libxml/tree.h:792:22: note: expected ‘const xmlChar *’ 
{aka ‘const unsigned char *’} but argument is of type ‘gchar *’ {aka ‘char *’}
  792 |   const xmlChar *value);
  |   ~~~^
ags/audio/midi/ags_midi_parser.c:2861:4: warning: pointer targets in passing 
argument 2 of ‘xmlNewProp’ differ in signedness [-Wpointer-sign]
 2861 |"sequence-name",
  |^~~
  ||
  |char *
In file included from ./ags/audio/midi/ags_midi_parser.h:26,
 from ags/audio/midi/ags_midi_parser.c:20:
/usr/include/libxml2/libxml/tree.h:791:22: note: expected ‘const xmlChar *’ 
{aka ‘const unsigned char *’} but argument is of type ‘char *’
  791 |   const xmlChar *name,
  |   ~~~^~~~
ags/audio/midi/ags_midi_parser.c:2862:4: warning: pointer targets in passing 
argument 3 of ‘xmlNewProp’ differ in signedness [-Wpointer-sign]
 2862 |text);
  |^~~~
  ||
  |gchar * {aka char *}
In file included from ./ags/audio/midi/ags_midi_parser.h:26,
 from ags/audio/midi/ags_midi_parser.c:20:
/usr/include/libxml2/libxml/tree.h:792:22: note: expected ‘const xmlChar *’ 
{aka ‘const unsigned char *’} but argument is of type ‘gchar *’ {aka ‘char *’}
  792 |   const xmlChar *value);
  |   ~~~^
ags/audio/midi/ags_midi_parser.c:2869:4: warning: pointer targets in passing 
argument 2 of ‘xmlNewProp’ differ in signedness [-Wpointer-sign]
 2869 |"instrument-name",
  |^
  ||
  |char *
In file included from ./ags/audio/midi/ags_midi_parser.h:26,
 from ags/audio/midi/ags_midi_parser.c:20:
/usr/include/libxml2/libxml/tree.h:791:22: note: expected ‘const xmlChar *’ 
{aka ‘const unsigned char *’} but argument is of type ‘char *’
  791 |   const xmlChar *name,
  |   ~~~^~~~
ags/audio/midi/ags_midi_parser.c:2870:4: warning: pointer targets in passing 
argument 3 of ‘xmlNewProp’ differ in signedness [-Wpointer-sign]
 2870 |text);
  |^~~~
  ||
  |gchar * {aka char *}
In file included from ./ags/audio/midi/ags_midi_parser.h:26,
 from ags/audio/midi/ags_midi_parser.c:20:
/usr/include/libxml2/libxml/tree.h:792:22: note: expected ‘const xmlChar *’ 
{aka ‘const unsigned char *’} but argument is of type ‘gchar *’ {aka ‘char *’}
  792 |   const xmlChar *value);
  |   ~~~^
ags/audio/midi/ags_midi_parser.c: In function ‘ags_midi_parser_set_property’:
ags/audio/midi/ags_midi_parser.c:792:2: warning: ignoring return value of 
‘fread’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  792 |  fread(midi_parser->buffer, sizeof(guchar), file_length, f);
  |  ^~
libtool: compile:  gcc -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. 
-I./ags -std=gnu99 -include errno.h -DAGS_VECTORIZED_BUILTIN_FUNCTIONS=1 
-I/usr/include -DAGS_LIBRARY_SUFFIX=\".so\" -Werror=return-type 
-Werror=uninitialized -Werror=maybe-uninitialized -DSRCDIR=\".\" 

Bug#983868: gsequencer ftbfs with -Werror=maybe-uninitialized

[Matthias Klose]

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 well.

On 3/2/21 3:46 PM, Joël Krähemann wrote:
> Hi,
> 
> This is not a GSequencer bug!
> 
> This behavior is wanted.
> 
> delta_time was properly initialized in ags_midi_buffer_util_seek_message().
> 
> it would be wrong if delta_time was overridden by
> ags_midi_buffer_util_get_varlength().
> it does only return 0 length so varlength shall not be set.
> 
> If you output 0 length, this means you can't use return location, so why
> should I set it?
> 
> regards,
> Joël
> 
> On Tue, Mar 2, 2021 at 1:45 PM Matthias Klose  wrote:
>>
>> Package: src:gsequencer
>> Version: 3.7.38-1
>> Severity: important
>> Tags: sid bullseye
>> X-Debbugs-CC: Joël Krähemann 
>>
>> gsequencer ftbfs with -Werror=maybe-uninitialized, with gcc-10 and gcc-11 
>> from
>> experimental.
>>
>> ags/audio/midi/ags_midi_buffer_util.c:2606:17: error: ‘current_delta_time’ 
>> may
>> be used uninitialized in this function [-Werror=maybe-uninitialized]
>>  2606 | *delta_time = current_delta_time;
>>   | ^~~~
>> cc1: some warnings being treated as errors
>>
>> You don't see the error in a build log, because the libtool output is 
>> redirected
>> to /dev/null.
>>
>> Forwarded to https://gcc.gnu.org/PR99340
>>
>> The warning is only seen with -fPIE, not -fPIC, which is a bug in GCC.
>>
>> The warning itself is correct, ags_midi_buffer_util_get_varlength doesn't 
>> always
>> return a value in varlength.

Bug#983868: gsequencer ftbfs with -Werror=maybe-uninitialized

[Matthias Klose]

Package: src:gsequencer
Version: 3.7.38-1
Severity: important
Tags: sid bullseye
X-Debbugs-CC: Joël Krähemann 

gsequencer ftbfs with -Werror=maybe-uninitialized, with gcc-10 and gcc-11 from
experimental.

ags/audio/midi/ags_midi_buffer_util.c:2606:17: error: ‘current_delta_time’ may
be used uninitialized in this function [-Werror=maybe-uninitialized]
 2606 | *delta_time = current_delta_time;
  | ^~~~
cc1: some warnings being treated as errors

You don't see the error in a build log, because the libtool output is redirected
to /dev/null.

Forwarded to https://gcc.gnu.org/PR99340

The warning is only seen with -fPIE, not -fPIC, which is a bug in GCC.

The warning itself is correct, ags_midi_buffer_util_get_varlength doesn't always
return a value in varlength.

Bug#982068: sonic-pi autopkg tests fail with stderr output

[Matthias Klose]

Package: src:sonic-pi
Version: 3.2.2~repack-7

sonic-pi autopkg tests fail with stderr output. I only see that on the Ubuntu
autopkg testers as:

server:

Booting on Linux
Jackd already running. Not starting another server...
Boot - Starting the SuperCollider server...
Boot - scsynth -u 4556 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B
127.0.0.1
JackTimedDriver::Process XRun = 12 usec
JackTimedDriver::Process XRun = 12 usec
JackTimedDriver::Process XRun = 11 usec
JackTimedDriver::Process XRun = 12 usec
JackTimedDriver::Process XRun = 12 usec
JackTimedDriver::Process XRun = 11 usec
JackTimedDriver::Process XRun = 12 usec
JackTimedDriver::Process XRun = 10 usec
Creating pids store: /tmp/sonic-pi-pids


the ui test is marked as flaky, but also shows the stderr output, but hiding the
failure because of the flaky restriction set.

full test logs at
https://autopkgtest.ubuntu.com/packages/s/sonic-pi/hirsute/amd64

Bug#978854: libmypaint: ftbfs with autoconf 2.70

[Matthias Klose]

Package: src:libmypaint
Version: 1.6.0-1
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/libmypaint_1.6.0-1_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
configure.ac:240: the top level
configure.ac:240: warning: The macro `AC_OUTPUT_COMMANDS' is obsolete.
configure.ac:240: You should run autoupdate.
./lib/autoconf/status.m4:1025: AC_OUTPUT_COMMANDS is expanded from...
/usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from...
/usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from...
/usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from...
configure.ac:240: the top level
configure.ac:83: warning: The macro `AC_PROG_CC_C99' is obsolete.
configure.ac:83: You should run autoupdate.
./lib/autoconf/c.m4:1476: AC_PROG_CC_C99 is expanded from...
configure.ac:83: the top level
configure.ac:240: warning: The macro `GLIB_GNU_GETTEXT' is obsolete.
configure.ac:240: You should run autoupdate.
/usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from...
/usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from...
configure.ac:240: the top level
configure.ac:240: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:240: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:673: AS_IF is expanded from...
./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from...
/usr/share/aclocal/glib-gettext.m4:51: GLIB_LC_MESSAGES is expanded from...
/usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from...
/usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from...
configure.ac:240: the top level
configure.ac:240: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:240: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:673: AS_IF is expanded from...
./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from...
lib/m4sugar/m4sh.m4:673: AS_IF is expanded from...
./lib/autoconf/headers.m4:89: _AC_CHECK_HEADER_COMPILE is expanded from...
./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from...
/usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from...
/usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from...
/usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from...
configure.ac:240: the top level
configure.ac:240: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:240: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:673: AS_IF is expanded from...
./lib/autoconf/headers.m4:89: _AC_CHECK_HEADER_COMPILE is expanded from...
./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from...
/usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from...
/usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from...
/usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from...
configure.ac:240: the top level
configure.ac:240: warning: The macro `AC_OUTPUT_COMMANDS' is obsolete.
configure.ac:240: You should run autoupdate.
./lib/autoconf/status.m4:1025: AC_OUTPUT_COMMANDS is expanded from...
/usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from...
/usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from...
/usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from...
configure.ac:240: the top level
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4macros'.
libtoolize: copying file 'm4macros/libtool.m4'
libtoolize: copying file 'm4macros/ltoptions.m4'
libtoolize: copying file 'm4macros/ltsugar.m4'
libtoolize: copying file 'm4macros/ltversion.m4'
libtoolize: copying file 'm4macros/lt~obsolete.m4'
ERROR: 'IT_PROG_INTLTOOL' must appear in configure.ac for intltool to work.
autoreconf: error: intltoolize failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:13: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Bug#978818: gem: ftbfs with autoconf 2.70

[Matthias Klose]

Package: src:gem
Version: 0.94-3
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/gem_0.94-3_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
  record-support
use QuickTime: yes
use v4l  : no
use v4l2 : yes (libv4l)
  model-support
use OBJ  : YES (local)
use ASSIMP2  : no
use ASSIMP3  : no

Now run make ...
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j4
make[1]: Entering directory '/<>'
Making all in src
make[2]: Entering directory '/<>/src'
make  all-recursive
make[3]: Entering directory '/<>/src'
Making all in Gem
make[4]: Entering directory '/<>/src/Gem'
make  all-am
make[5]: Entering directory '/<>/src/Gem'
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src  -I../../src -DGEM_INTERNAL  -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME='""Debian/1:0.94-3""' -DPD -I/usr/include/pd-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o libGem_la-glew.lo `test -f 'glew.c' || echo 
'./'`glew.c
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../src  -I../../src -DGEM_INTERNAL  -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME='""Debian/1:0.94-3""' -DPD -I/usr/include/pd-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions 
-falign-jumps -funroll-loops -ffast-math -mmmx -msse2 -c -o libGem_la-Cache.lo 
`test -f 'Cache.cpp' || echo './'`Cache.cpp
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../src  -I../../src -DGEM_INTERNAL  -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME='""Debian/1:0.94-3""' -DPD -I/usr/include/pd-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions 
-falign-jumps -funroll-loops -ffast-math -mmmx -msse2 -c -o 
libGem_la-ContextData.lo `test -f 'ContextData.cpp' || echo './'`ContextData.cpp
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../src  -I../../src -DGEM_INTERNAL  -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME='""Debian/1:0.94-3""' -DPD -I/usr/include/pd-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions 
-falign-jumps -funroll-loops -ffast-math -mmmx -msse2 -c -o libGem_la-Dylib.lo 
`test -f 'Dylib.cpp' || echo './'`Dylib.cpp
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I../../src 
-DGEM_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME=\"\"Debian/1:0.94-3\"\" -DPD -I/usr/include/pd -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c glew.c  -fPIC -DPIC -o .libs/libGem_la-glew.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src 
-DGEM_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME=\"\"Debian/1:0.94-3\"\" -DPD -I/usr/include/pd -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions 
-falign-jumps -funroll-loops -ffast-math -mmmx -msse2 -c Dylib.cpp  -fPIC -DPIC 
-o .libs/libGem_la-Dylib.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src 
-DGEM_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME=\"\"Debian/1:0.94-3\"\" -DPD -I/usr/include/pd -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions 
-falign-jumps -funroll-loops -ffast-math -mmmx -msse2 -c ContextData.cpp  -fPIC 
-DPIC -o .libs/libGem_la-ContextData.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src 
-DGEM_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2 
-DGEM_VERSION_CODENAME=\"\"Debian/1:0.94-3\"\" -DPD -I/usr/include/pd -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -freg-struct-return -O3 -falign-loops -falign-functions 
-falign-jumps -funroll-loops -ffast-math -mmmx -msse2 -c Cache.cpp  -fPIC -DPIC 
-o .libs/libGem_la-Cache.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../src -I../../src 
-DGEM_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2 

Bug#978762: abcmidi: ftbfs with autoconf 2.70

[Matthias Klose]

Package: src:abcmidi
Version: 20200809-1
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/abcmidi_20200809-1_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
PACKAGE_STRING='abcmidi 2011-08-03'
PACKAGE_TARNAME='abcmidi'
PACKAGE_URL=''
PACKAGE_VERSION='2011-08-03'
PATH_SEPARATOR=':'
SHELL='/bin/bash'
ac_ct_CC='gcc'
bindir='${exec_prefix}/bin'
build='x86_64-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu=''
build_os=''
build_vendor=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "abcmidi"
#define PACKAGE_TARNAME "abcmidi"
#define PACKAGE_VERSION "2011-08-03"
#define PACKAGE_STRING "abcmidi 2011-08-03"
#define PACKAGE_BUGREPORT "seymour.shl...@crc.ca"
#define PACKAGE_URL ""
#define HAVE_LIBM 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define STDC_HEADERS 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1

configure: exit 127
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking returned exit code 127
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Bug#973292: blender ftbfs with python3.9

[Matthias Klose]

Package: src:blender
Version: 2.83.5+dfsg-3
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

to reproduce, you can use the repositories found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

https://people.debian.org/~ginggs/python3.9-default/blender_2.83.5+dfsg-3+build1_amd64-2020-10-26T09:00:19Z.build


[...]
/<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1948:33:
error: ‘PyNoArgsFunction’ undeclared (first use in this function); did you mean
‘PyCFunction’?
 1948 |   return matrix__apply_to_copy((PyNoArgsFunction)Matrix_transpose, 
self);
  | ^~~~
  | PyCFunction
/<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1948:50:
error: expected ‘)’ before ‘Matrix_transpose’
 1948 |   return matrix__apply_to_copy((PyNoArgsFunction)Matrix_transpose, 
self);
  |  ^~~~
  |  )
/<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1946:50:
warning: unused parameter ‘self’ [-Wunused-parameter]
 1946 | static PyObject *Matrix_transposed(MatrixObject *self)
  |~~^~~~
/<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:
In function ‘Matrix_normalized’:
/<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1994:33:
error: ‘PyNoArgsFunction’ undeclared (first use in this function); did you mean
‘PyCFunction’?
 1994 |   return matrix__apply_to_copy((PyNoArgsFunction)Matrix_normalize, 
self);
  | ^~~~
  | PyCFunction
/<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1994:50:
error: expected ‘)’ before ‘Matrix_normalize’
 1994 |   return matrix__apply_to_copy((PyNoArgsFunction)Matrix_normalize, 
self);
  |  ^~~~
  |  )
/<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1992:50:
warning: unused parameter ‘self’ [-Wunused-parameter]
 1992 | static PyObject *Matrix_normalized(MatrixObject *self)
  |~~^~~~

Bug#972026: add patch

[Matthias Klose]

Control: tags -1 + patch

patch at
https://github.com/belangeo/pyo/commit/274ed61d6664d44d23416957e781b8afbb559589

there's also a new upstream version 1.0.3.

Bug#972026: python-pyo ftbfs with python3.9 as supported python version

[Matthias Klose]

Package: src:python-pyo
Version: 1.0.2-1
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -DUSE_PORTAUDIO -DUSE_PORTMIDI -DUSE_OSC -DUSE_JACK
-DJACK_OLD_API -Iinclude -I/usr/include -I/usr/local/include
-I/usr/include/python3.9 -c src/objects/bandsplitmodule.c -o
build/temp.linux-x86_64-3.9/src/objects/bandsplitmodule.o -Wno-strict-prototypes
-Wno-strict-aliasing -O3 -g0 -DNDEBUG
In file included from /usr/include/python3.9/pytime.h:6,
 from /usr/include/python3.9/Python.h:85,
 from src/objects/bandsplitmodule.c:21:
src/objects/bandsplitmodule.c: In function ‘MultiBandMain_setFrequencies’:
/usr/include/python3.9/object.h:633:41: error: expected ‘(’ before
‘PyType_HasFeature’
  633 | #define PyType_FastSubclass(type, flag) PyType_HasFeature(type, flag)
  | ^
/usr/include/python3.9/listobject.h:25:5: note: in expansion of macro
‘PyType_FastSubclass’
   25 | PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_LIST_SUBCLASS)
  | ^~~
src/objects/bandsplitmodule.c:1639:8: note: in expansion of macro ‘PyList_Check’
 1639 | if PyList_Check(arg) {
  |^~~~
src/objects/bandsplitmodule.c:1639:26: error: expected ‘;’ before ‘{’ token
 1639 | if PyList_Check(arg) {
  |  ^
src/objects/bandsplitmodule.c:1638:12: warning: unused variable ‘bounds’
[-Wunused-variable]
 1638 | int i, bounds = self->nbands - 1;
  |^~
src/objects/bandsplitmodule.c:1638:9: warning: unused variable ‘i’
[-Wunused-variable]
 1638 | int i, bounds = self->nbands - 1;
  | ^
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.9 setup.py build

Bug#967211: swami: Unversioned Python removal in sid/bullseye

[Matthias Klose]

Package: src:swami
Version: 2.2.1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#967186: ogmrip: Unversioned Python removal in sid/bullseye

[Matthias Klose]

Package: src:ogmrip
Version: 1.0.1-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#966248: don't depend on a specific gdc version

[Matthias Klose]

Package: src:cheesecutter
Version: 2.9+git20191210-1
Severity: serious
Tags: sid bullseye patch

don't depend on a specific gdc version. GCC 9 will be removed most likely for
the next Debian release.

patch at
http://launchpadlibrarian.net/490078513/cheesecutter_2.9+git20191210-1build2_2.9+git20191210-1ubuntu1.diff.gz

Bug#963064: faust ftbfs with LLVM 10

[Matthias Klose]

Package: src:faust
Version: 2.20.2~ds0-1
Severity: important
Tags: sid bullseye patch

faust ftbfs with LLVM 10, not detecting LLVM 10. Fixed with the attached patch.

--- faust-2.20.2~ds0.orig/build/CMakeLists.txt
+++ faust-2.20.2~ds0/build/CMakeLists.txt
@@ -80,7 +80,7 @@ if (INCLUDE_LLVM )
llvm_cmake()
endif()

-   string (REGEX REPLACE "([0-9])\\.([0-9]).*" "LLVM_\\1\\2" LLVM_VERSION
${LLVM_PACKAGE_VERSION})
+   string (REGEX REPLACE "([0-9][0-9]*)\\.([0-9][0-9]*).*" "LLVM_\\1\\2"
LLVM_VERSION ${LLVM_PACKAGE_VERSION})

# the declarations below are redundant but necessary to cope with
different cmake behaviors on different platforms
set (TMP ${SRCDIR}/generator/llvm)

However it later shows more build errors with LLVM, so maybe it's better to
explicitly build with a fixed LLVM version?

Bug#957967: xawtv: ftbfs with GCC-10

[Matthias Klose]

Package: src:xawtv
Version: 3.106-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/xawtv_3.106-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  | ^
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I/usr/include/ncursesw -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wstrict-prototypes 
-Wpointer-arith -Wno-pointer-sign -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_FILE_OFFSET_BITS=64 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/X11/fonts -I. -I./vbistuff -I./x11 
-I./jwz -I./common -I./console -I./x11 -I./structs -I./libng -I/usr/include/lqt 
-DCONFIGFILE="/etc/X11/xawtvrc" -DLIBDIR="/usr/lib/x86_64-linux-gnu/xawtv" 
-DDATADIR="/usr/share/xawtv" -DVERSION="3.106" -Wp,-MD,mk/console_matrox.tmp -c 
-o console/matrox.o console/matrox.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I/usr/include/ncursesw -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wstrict-prototypes 
-Wpointer-arith -Wno-pointer-sign -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_FILE_OFFSET_BITS=64 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/X11/fonts -I. -I./vbistuff -I./x11 
-I./jwz -I./common -I./console -I./x11 -I./structs -I./libng -I/usr/include/lqt 
-DCONFIGFILE="/etc/X11/xawtvrc" -DLIBDIR="/usr/lib/x86_64-linux-gnu/xawtv" 
-DDATADIR="/usr/share/xawtv" -DVERSION="3.106" -Wp,-MD,mk/common_lirc.tmp -c -o 
common/lirc.o common/lirc.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I/usr/include/ncursesw -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wstrict-prototypes 
-Wpointer-arith -Wno-pointer-sign -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_FILE_OFFSET_BITS=64 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/X11/fonts -I. -I./vbistuff -I./x11 
-I./jwz -I./common -I./console -I./x11 -I./structs -I./libng -I/usr/include/lqt 
-DCONFIGFILE="/etc/X11/xawtvrc" -DLIBDIR="/usr/lib/x86_64-linux-gnu/xawtv" 
-DDATADIR="/usr/share/xawtv" -DVERSION="3.106" -Wp,-MD,mk/common_joystick.tmp 
-c -o common/joystick.o common/joystick.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I/usr/include/ncursesw -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wstrict-prototypes 
-Wpointer-arith -Wno-pointer-sign -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_FILE_OFFSET_BITS=64 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/X11/fonts -I. -I./vbistuff -I./x11 
-I./jwz -I./common -I./console -I./x11 -I./structs -I./libng -I/usr/include/lqt 
-DCONFIGFILE="/etc/X11/xawtvrc" -DLIBDIR="/usr/lib/x86_64-linux-gnu/xawtv" 
-DDATADIR="/usr/share/xawtv" -DVERSION="3.106" -Wp,-MD,mk/common_midictrl.tmp 
-c -o common/midictrl.o common/midictrl.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I/usr/include/ncursesw -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes -Wstrict-prototypes 
-Wpointer-arith -Wno-pointer-sign -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_FILE_OFFSET_BITS=64 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/X11/fonts -I. -I./vbistuff -I./x11 
-I./jwz -I./common -I./console -I./x11 -I./structs -I./libng -I/usr/include/lqt 
-DCONFIGFILE="/etc/X11/xawtvrc" -DLIBDIR="/usr/lib/x86_64-linux-gnu/xawtv" 
-DDATADIR="/usr/share/xawtv" -DVERSION="3.106" -Wp,-MD,mk/console_v4l-info.tmp 
-c -o console/v4l-info.o console/v4l-info.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I/usr/include/ncursesw -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes 

Bug#957915: vlc: ftbfs with GCC-10

[Matthias Klose]

Package: src:vlc
Version: 3.0.8-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/vlc_3.0.8-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
libtool: link: /usr/bin/nm -B  codec/omxil/.libs/libomxil_plugin_la-utils.o 
packetizer/.libs/libomxil_plugin_la-h264_nal.o 
packetizer/.libs/libomxil_plugin_la-hevc_nal.o 
codec/omxil/.libs/libomxil_plugin_la-qcom.o 
codec/omxil/.libs/libomxil_plugin_la-omxil.o 
codec/omxil/.libs/libomxil_plugin_la-omxil_core.o   ./.libs/libchroma_copy.a | 
sed -n -e 's/^.*[  ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' | /bin/sed 
's/.* //' | sort | uniq > .libs/libomxil_plugin.exp
libtool: link: echo "{ global:" > .libs/libvaapi_drm_plugin.ver
libtool: link: mv -f ".libs/libavcodec_plugin.expT" 
".libs/libavcodec_plugin.exp"
libtool: link:  cat .libs/libvaapi_drm_plugin.exp | sed -e "s/\(.*\)/\1;/" >> 
.libs/libvaapi_drm_plugin.ver
libtool: link:  echo "local: *; };" >> .libs/libvaapi_drm_plugin.ver
libtool: link:  gcc -shared  -fPIC -DPIC  
codec/avcodec/.libs/libvaapi_drm_plugin_la-vaapi.o 
hw/vaapi/.libs/libvaapi_drm_plugin_la-vlc_vaapi.o   -Wl,-rpath 
-Wl,/<>/src/.libs ../compat/.libs/libcompat.a 
../src/.libs/libvlccore.so -Wl,--as-needed -lva-drm -lva  -g -O2 
-fstack-protector-strong -O3 -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,defs   
-Wl,-soname -Wl,libvaapi_drm_plugin.so -Wl,-version-script 
-Wl,.libs/libvaapi_drm_plugin.ver -o .libs/libvaapi_drm_plugin.so
libtool: link: echo "{ global:" > .libs/libavcodec_plugin.ver
libtool: link: /bin/grep -E -e "^vlc_entry" ".libs/libomxil_plugin.exp" > 
".libs/libomxil_plugin.expT"
libtool: link:  cat .libs/libavcodec_plugin.exp | sed -e "s/\(.*\)/\1;/" >> 
.libs/libavcodec_plugin.ver
libtool: link: mv -f ".libs/libomxil_plugin.expT" ".libs/libomxil_plugin.exp"
libtool: link: echo "{ global:" > .libs/libomxil_plugin.ver
libtool: link:  echo "local: *; };" >> .libs/libavcodec_plugin.ver
libtool: link:  gcc -shared  -fPIC -DPIC  
codec/avcodec/.libs/libavcodec_plugin_la-video.o 
codec/avcodec/.libs/libavcodec_plugin_la-subtitle.o 
codec/avcodec/.libs/libavcodec_plugin_la-audio.o 
codec/avcodec/.libs/libavcodec_plugin_la-va.o 
codec/avcodec/.libs/libavcodec_plugin_la-avcodec.o 
codec/avcodec/.libs/libavcodec_plugin_la-encoder.o  -Wl,--whole-archive 
./.libs/libavcodec_common.a -Wl,--no-whole-archive  -Wl,-rpath 
-Wl,/<>/src/.libs ../compat/.libs/libcompat.a 
../src/.libs/libvlccore.so -Wl,--as-needed -lavcodec -lavutil -lm  -g -O2 
-fstack-protector-strong -O3 -Wl,-Bsymbolic -Wl,-z -Wl,relro -Wl,-z -Wl,now 
-Wl,-z -Wl,defs   -Wl,-soname -Wl,libavcodec_plugin.so -Wl,-version-script 
-Wl,.libs/libavcodec_plugin.ver -o .libs/libavcodec_plugin.so
libtool: link:  cat .libs/libomxil_plugin.exp | sed -e "s/\(.*\)/\1;/" >> 
.libs/libomxil_plugin.ver
libtool: link:  echo "local: *; };" >> .libs/libomxil_plugin.ver
libtool: link:  gcc -shared  -fPIC -DPIC  
codec/omxil/.libs/libomxil_plugin_la-utils.o 
packetizer/.libs/libomxil_plugin_la-h264_nal.o 
packetizer/.libs/libomxil_plugin_la-hevc_nal.o 
codec/omxil/.libs/libomxil_plugin_la-qcom.o 
codec/omxil/.libs/libomxil_plugin_la-omxil.o 
codec/omxil/.libs/libomxil_plugin_la-omxil_core.o  -Wl,--whole-archive 
./.libs/libchroma_copy.a -Wl,--no-whole-archive  -Wl,-rpath 
-Wl,/<>/src/.libs ../compat/.libs/libcompat.a 
../src/.libs/libvlccore.so -Wl,--as-needed -ldl  -g -O2 
-fstack-protector-strong -O3 -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,defs   
-Wl,-soname -Wl,libomxil_plugin.so -Wl,-version-script 
-Wl,.libs/libomxil_plugin.ver -o .libs/libomxil_plugin.so
/usr/bin/ld: 
codec/omxil/.libs/libomxil_plugin_la-omxil.o:./modules/codec/omxil/omxil_core.h:32:
 multiple definition of `pf_free_handle'; 
codec/omxil/.libs/libomxil_plugin_la-utils.o:./modules/codec/omxil/omxil_core.h:32:
 first defined here

Bug#957886: tutka: ftbfs with GCC-10

[Matthias Klose]

Package: src:tutka
Version: 1.1.3-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/tutka_1.1.3-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
/usr/lib/qt5/bin/uic messagelistdialog.ui -o ui_messagelistdialog.h
/usr/lib/qt5/bin/uic helpdialog.ui -o ui_helpdialog.h
g++ -c -pipe -g -Werror -fsigned-char -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W 
-Wno-strict-overflow -Wno-sign-compare -D_REENTRANT -fPIC -DQT_NO_DEBUG_OUTPUT 
-DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/main.o main.cpp
g++ -c -pipe -g -Werror -fsigned-char -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W 
-Wno-strict-overflow -Wno-sign-compare -D_REENTRANT -fPIC -DQT_NO_DEBUG_OUTPUT 
-DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/block.o block.cpp
g++ -c -pipe -g -Werror -fsigned-char -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W 
-Wno-strict-overflow -Wno-sign-compare -D_REENTRANT -fPIC -DQT_NO_DEBUG_OUTPUT 
-DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/instrument.o 
instrument.cpp
g++ -c -pipe -g -Werror -fsigned-char -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W 
-Wno-strict-overflow -Wno-sign-compare -D_REENTRANT -fPIC -DQT_NO_DEBUG_OUTPUT 
-DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/message.o message.cpp
g++ -c -pipe -g -Werror -fsigned-char -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W 
-Wno-strict-overflow -Wno-sign-compare -D_REENTRANT -fPIC -DQT_NO_DEBUG_OUTPUT 
-DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. 
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o .obj/playseq.o playseq.cpp
g++ -c -pipe -g -Werror -fsigned-char -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W 
-Wno-strict-overflow -Wno-sign-compare -D_REENTRANT -fPIC -DQT_NO_DEBUG_OUTPUT 

Bug#957718: pt2-clone: ftbfs with GCC-10

[Matthias Klose]

Package: src:pt2-clone
Version: 1.06-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/pt2-clone_1.06-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_keyboard.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:456:
 multiple definition of `editor'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:456:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_keyboard.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:320:
 multiple definition of `input'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:320:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_keyboard.c.o:./obj-x86_64-linux-gnu/./src/pt2_config.h:15:
 multiple definition of `ptConfig'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_config.h:15:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_keyboard.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:298:
 multiple definition of `audio'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:298:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_keyboard.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:291:
 multiple definition of `cpu'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:291:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_main.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:456:
 multiple definition of `editor'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:456:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_main.c.o:./obj-x86_64-linux-gnu/./src/pt2_config.h:15:
 multiple definition of `ptConfig'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_config.h:15:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_main.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:291:
 multiple definition of `cpu'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:291:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_main.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:320:
 multiple definition of `input'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:320:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_main.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:298:
 multiple definition of `audio'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:298:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_modloader.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:456:
 multiple definition of `editor'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:456:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_modloader.c.o:./obj-x86_64-linux-gnu/./src/pt2_config.h:15:
 multiple definition of `ptConfig'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_config.h:15:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_modloader.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:320:
 multiple definition of `input'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:320:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_modloader.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:298:
 multiple definition of `audio'; 
CMakeFiles/pt2-clone.dir/src/pt2_audio.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:298:
 first defined here
/usr/bin/ld: 
CMakeFiles/pt2-clone.dir/src/pt2_modloader.c.o:./obj-x86_64-linux-gnu/./src/pt2_header.h:291:
 multiple definition of `cpu'; 

Bug#957626: ocp: ftbfs with GCC-10

[Matthias Klose]

Package: src:ocp
Version: 1:0.2.0-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ocp_0.2.0-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url.c -o timidity-git/libarc/url.o -c -DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_b64decode.c -o timidity-git/libarc/url_b64decode.o -c 
-DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_cache.c -o timidity-git/libarc/url_cache.o -c 
-DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_dir.c -o timidity-git/libarc/url_dir.o -c -DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_file.c -o timidity-git/libarc/url_file.o -c -DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_hqxdecode.c -o timidity-git/libarc/url_hqxdecode.o -c 
-DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_inflate.c -o timidity-git/libarc/url_inflate.o -c 
-DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_mem.c -o timidity-git/libarc/url_mem.o -c -DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_pipe.c -o timidity-git/libarc/url_pipe.o -c -DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc -Itimidity-git/libunimod 
-Itimidity-git/timidity -Itimidity-git/utils -I. -DHAVE_CONFIG_H -I.././ 
timidity-git/libarc/url_qsdecode.c -o timidity-git/libarc/url_qsdecode.o -c 
-DNO_CURSES
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall 
-Itimidity-git/interface -Itimidity-git/libarc 

Bug#957495: lives: ftbfs with GCC-10

[Matthias Klose]

Package: src:lives
Version: 3.0.2-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/lives_3.0.2-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
/usr/bin/ld: giw/giwled.o:./src/./paramspecial.h:77: multiple definition of 
`mergealign'; widget-helper.o:./src/paramspecial.h:77: first defined here
/usr/bin/ld: giw/giwled.o:./src/./events.h:198: multiple definition of `rdet'; 
widget-helper.o:./src/events.h:198: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper.h:1136: multiple definition of 
`widget_opts'; widget-helper.o:./src/widget-helper.h:1136: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:975: multiple definition 
of `LIVES_STOCK_LABEL_MEDIA_RECORD'; 
widget-helper.o:./src/widget-helper-gtk.h:975: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:974: multiple definition 
of `LIVES_STOCK_LABEL_MEDIA_PAUSE'; 
widget-helper.o:./src/widget-helper-gtk.h:974: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:973: multiple definition 
of `LIVES_STOCK_LABEL_MEDIA_PLAY'; 
widget-helper.o:./src/widget-helper-gtk.h:973: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:972: multiple definition 
of `LIVES_STOCK_LABEL_MEDIA_STOP'; 
widget-helper.o:./src/widget-helper-gtk.h:972: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:971: multiple definition 
of `LIVES_STOCK_LABEL_MEDIA_REWIND'; 
widget-helper.o:./src/widget-helper-gtk.h:971: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:970: multiple definition 
of `LIVES_STOCK_LABEL_MEDIA_FORWARD'; 
widget-helper.o:./src/widget-helper-gtk.h:970: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:968: multiple definition 
of `LIVES_STOCK_LABEL_GO_FORWARD'; 
widget-helper.o:./src/widget-helper-gtk.h:968: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:967: multiple definition 
of `LIVES_STOCK_LABEL_SELECT_ALL'; 
widget-helper.o:./src/widget-helper-gtk.h:967: first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:966: multiple definition 
of `LIVES_STOCK_LABEL_DELETE'; widget-helper.o:./src/widget-helper-gtk.h:966: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:965: multiple definition 
of `LIVES_STOCK_LABEL_REFRESH'; widget-helper.o:./src/widget-helper-gtk.h:965: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:964: multiple definition 
of `LIVES_STOCK_LABEL_REVERT'; widget-helper.o:./src/widget-helper-gtk.h:964: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:963: multiple definition 
of `LIVES_STOCK_LABEL_CLOSE'; widget-helper.o:./src/widget-helper-gtk.h:963: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:962: multiple definition 
of `LIVES_STOCK_LABEL_APPLY'; widget-helper.o:./src/widget-helper-gtk.h:962: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:961: multiple definition 
of `LIVES_STOCK_LABEL_QUIT'; widget-helper.o:./src/widget-helper-gtk.h:961: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:960: multiple definition 
of `LIVES_STOCK_LABEL_OPEN'; widget-helper.o:./src/widget-helper-gtk.h:960: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:959: multiple definition 
of `LIVES_STOCK_LABEL_SAVE_AS'; widget-helper.o:./src/widget-helper-gtk.h:959: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:958: multiple definition 
of `LIVES_STOCK_LABEL_SAVE'; widget-helper.o:./src/widget-helper-gtk.h:958: 
first defined here
/usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:957: multiple definition 
of `LIVES_STOCK_LABEL_NO'; widget-helper.o:./src/widget-helper-gtk.h:957: first 
defined here
/usr/bin/ld: 

Bug#957382: jackeq: ftbfs with GCC-10

[Matthias Klose]

Package: src:jackeq
Version: 0.5.9-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/jackeq_0.5.9-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from support.c:15:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/share"\" 
-DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16  -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -ffast-math -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security  
-I/usr/include/libxml2 -Wall -c -o jackeq-help.o `test -f 'help.c' || echo 
'./'`help.c
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from help.c:31:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from help.c:31:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from help.c:31:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from 

Bug#957326: gwc: ftbfs with GCC-10

[Matthias Klose]

Package: src:gwc
Version: 0.22.04-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/gwc_0.22.04-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
biquad.c: In function ‘filter_dialog’:
biquad.c:343:9: warning: variable ‘dclose’ set but not used 
[-Wunused-but-set-variable]
  343 | int dclose = 0 ;
  | ^~
gcc tap_reverb_file_io.o tap_reverb.o reverb.o dialog.o gwc.o audio_device.o 
audio_edit.o audio_util.o gtkled.o gtkledbar.o preferences.o drawing.o 
amplify.o denoise.o undo.o declick.o sample_block.o decrackle.o stat.o 
dethunk.o i0.o i1.o chbevl.o markers.o encode.o soundfile.o pinknoise.o 
biquad.o  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed meschach.a -lgtk-x11-2.0 
-lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 
-lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lfontconfig -lfreetype -lglib-2.0 
-lsndfile -lasound  -lfftw3-lm -o gtk-wave-cleaner
/usr/bin/ld: dialog.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: dialog.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; 
reverb.o:./gwc.h:189: first defined here
/usr/bin/ld: dialog.o:./gwc.h:188: multiple definition of `tmpdir'; 
reverb.o:./gwc.h:188: first defined here
/usr/bin/ld: gwc.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: gwc.o:./gwc.h:188: multiple definition of `tmpdir'; 
reverb.o:./gwc.h:188: first defined here
/usr/bin/ld: gwc.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; 
reverb.o:./gwc.h:189: first defined here
/usr/bin/ld: audio_device.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: audio_device.o:./gwc.h:189: multiple definition of 
`CLIPBOARD_FILE'; reverb.o:./gwc.h:189: first defined here
/usr/bin/ld: audio_device.o:./gwc.h:188: multiple definition of `tmpdir'; 
reverb.o:./gwc.h:188: first defined here
/usr/bin/ld: audio_edit.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; 
reverb.o:./gwc.h:189: first defined here
/usr/bin/ld: audio_edit.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: audio_edit.o:./gwc.h:188: multiple definition of `tmpdir'; 
reverb.o:./gwc.h:188: first defined here
/usr/bin/ld: audio_util.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: audio_util.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; 
reverb.o:./gwc.h:189: first defined here
/usr/bin/ld: audio_util.o:./gwc.h:188: multiple definition of `tmpdir'; 
reverb.o:./gwc.h:188: first defined here
/usr/bin/ld: preferences.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: preferences.o:./gwc.h:189: multiple definition of 
`CLIPBOARD_FILE'; reverb.o:./gwc.h:189: first defined here
/usr/bin/ld: preferences.o:./gwc.h:188: multiple definition of `tmpdir'; 
reverb.o:./gwc.h:188: first defined here
/usr/bin/ld: drawing.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: drawing.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; 
reverb.o:./gwc.h:189: first defined here
/usr/bin/ld: drawing.o:./gwc.h:188: multiple definition of `tmpdir'; 
reverb.o:./gwc.h:188: first defined here
/usr/bin/ld: amplify.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: amplify.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; 
reverb.o:./gwc.h:189: first defined here
/usr/bin/ld: amplify.o:./gwc.h:188: multiple definition of `tmpdir'; 
reverb.o:./gwc.h:188: first defined here
/usr/bin/ld: denoise.o:./gwc.h:193: multiple definition of `main_window'; 
reverb.o:./gwc.h:193: first defined here
/usr/bin/ld: denoise.o:./gwc.h:189: 

Bug#957217: forked-daapd: ftbfs with GCC-10

[Matthias Klose]

Package: src:forked-daapd
Version: 26.4+dfsg1-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/forked-daapd_26.4+dfsg1-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: 
‘__builtin___snprintf_chk’ output between 17 and 26 bytes into a destination of 
size 21
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ^~~~
   68 |__bos (__s), __fmt, __va_arg_pack ());
  |~
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
library/filescanner_itunes.o library/filescanner_itunes.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
inputs/file_http.o inputs/file_http.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o inputs/pipe.o 
inputs/pipe.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o outputs/raop.o 
outputs/raop.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
outputs/raop_verification.o outputs/raop_verification.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 
-D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu  -D_GNU_SOURCE 
-DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" 
-DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
outputs/streaming.o outputs/streaming.c
gcc -DHAVE_CONFIG_H -I. -I..  -Wall -I/usr/include/x86_64-linux-gnu 
-I/usr/include/json-c -D_THREAD_SAFE -D_REENTRANT -I/usr/include/p11-kit-1 

Bug#957111: csound: ftbfs with GCC-10

[Matthias Klose]

Package: src:csound
Version: 1:6.13.0~dfsg-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/csound_6.13.0~dfsg-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
[582/708] /usr/bin/cc -DCS_DEFAULT_PLUGINDIR=\"/usr/lib/csound/plugins64-6.0\" 
-DCS_PACKAGE_DATE=\"2020-01-16\" -DHAVE_EXECINFO -DHAVE_SOCKETS -DHAVE_STRTOD_L 
-DHAVE_STRTOK_R -DLINUX -DNO_FLTK_THREADS -DPIPES -DUSE_LRINT 
-D_CSOUND_RELEASE_ -D_GNU_SOURCE -I/usr/include/lua5.1 -I.././H -I.././include 
-I.././Engine -I.././util -I../. -I. -Iinclude -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DBETA 
-fvisibility=hidden -std=gnu99 -DHAVE_ATOMIC_BUILTIN -DHAVE_PTHREAD   
-ftree-vectorize -ffast-math -O3 -fno-finite-math-only -mtune=generic -MD -MT 
Frontends/CMakeFiles/csound-bin.dir/csound/sched.c.o -MF 
Frontends/CMakeFiles/csound-bin.dir/csound/sched.c.o.d -o 
Frontends/CMakeFiles/csound-bin.dir/csound/sched.c.o   -c 
../Frontends/csound/sched.c
[583/708] : && /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DBETA -fvisibility=hidden -std=gnu99 -DHAVE_ATOMIC_BUILTIN 
-DHAVE_PTHREAD  -Wl,-z,relro -Wl,-z,now-rdynamic 
Frontends/CMakeFiles/csound-bin.dir/csound/csound_main.c.o 
Frontends/CMakeFiles/csound-bin.dir/csound/sched.c.o  -o csound  
-Wl,-rpath,"/<>/obj-x86_64-linux-gnu:"  libcsound64.so.6.0  
-lpthread  -lm && :
[584/708] cd "/<>/Frontends" && /usr/bin/bison -d -o 
"/<>/obj-x86_64-linux-gnu/Frontends/beats.tab.c" beats/beats.y
beats/beats.y: warning: 1 reduce/reduce conflict [-Wconflicts-rr]
[585/708] cd "/<>/Frontends" && /usr/bin/flex 
"-o/<>/obj-x86_64-linux-gnu/Frontends/beatslex.yy.c" beats/beats.l
[586/708] /usr/bin/cc -DCS_DEFAULT_PLUGINDIR=\"/usr/lib/csound/plugins64-6.0\" 
-DCS_PACKAGE_DATE=\"2020-01-16\" -DHAVE_EXECINFO -DHAVE_SOCKETS -DHAVE_STRTOD_L 
-DHAVE_STRTOK_R -DLINUX -DNO_FLTK_THREADS -DPIPES -DUSE_LRINT 
-D_CSOUND_RELEASE_ -D_GNU_SOURCE -I/usr/include/lua5.1 -I.././H -I.././include 
-I.././Engine -I.././util -I../. -I. -Iinclude -IFrontends -I../Frontends/beats 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DBETA 
-fvisibility=hidden -std=gnu99 -DHAVE_ATOMIC_BUILTIN -DHAVE_PTHREAD   
-ftree-vectorize -ffast-math -O3 -fno-finite-math-only -mtune=generic -MD -MT 
Frontends/CMakeFiles/csbeats.dir/beats/main.c.o -MF 
Frontends/CMakeFiles/csbeats.dir/beats/main.c.o.d -o 
Frontends/CMakeFiles/csbeats.dir/beats/main.c.o   -c ../Frontends/beats/main.c
[587/708] /usr/bin/cc -DCS_DEFAULT_PLUGINDIR=\"/usr/lib/csound/plugins64-6.0\" 
-DCS_PACKAGE_DATE=\"2020-01-16\" -DHAVE_EXECINFO -DHAVE_SOCKETS -DHAVE_STRTOD_L 
-DHAVE_STRTOK_R -DLINUX -DNO_FLTK_THREADS -DPIPES -DUSE_LRINT 
-D_CSOUND_RELEASE_ -D_GNU_SOURCE -I/usr/include/lua5.1 -I.././H -I.././include 
-I.././Engine -I.././util -I../. -I. -Iinclude -IFrontends -I../Frontends/beats 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DBETA 
-fvisibility=hidden -std=gnu99 -DHAVE_ATOMIC_BUILTIN -DHAVE_PTHREAD   
-ftree-vectorize -ffast-math -O3 -fno-finite-math-only -mtune=generic -MD -MT 
Frontends/CMakeFiles/csbeats.dir/beatslex.yy.c.o -MF 
Frontends/CMakeFiles/csbeats.dir/beatslex.yy.c.o.d -o 
Frontends/CMakeFiles/csbeats.dir/beatslex.yy.c.o   -c Frontends/beatslex.yy.c
[588/708] cd "/<>/obj-x86_64-linux-gnu/interfaces" && 
/usr/bin/cmake -E make_directory 
/<>/obj-x86_64-linux-gnu/interfaces 
/<>/obj-x86_64-linux-gnu/interfaces/CMakeFiles/_jcsound6.dir && 
/usr/bin/cmake -E env SWIG_LIB=/usr/share/swig4.0 /usr/bin/swig4.0 -java 
-D__BUILDING_LIBCSOUND -DHAVE_PTHREAD_SPIN_LOCK -DHAVE_PTHREAD_BARRIER_INIT 
-DPARCS -DGNU_GETTEXT -DHAVE_DIRENT_H 

Bug#957023: audacity: ftbfs with GCC-10

[Matthias Klose]

Package: src:audacity
Version: 2.3.3-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/audacity_2.3.3-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
widgets/Meter.cpp:980:31: warning: ‘void* memset(void*, int, size_t)’ clearing 
an object of non-trivial type ‘class MeterUpdateMsg’; use assignment or 
value-initialization instead [-Wclass-memaccess]
  980 |memset(, 0, sizeof(msg));
  |   ^
In file included from widgets/Meter.cpp:42:
widgets/Meter.h:50:7: note: ‘class MeterUpdateMsg’ declared here
   50 | class MeterUpdateMsg
  |   ^~
widgets/Meter.cpp: In member function ‘void 
MeterPanel::OnMeterUpdate(wxTimerEvent&)’:
widgets/Meter.cpp:1070:9: warning: unused variable ‘gAudioIO’ 
[-Wunused-variable]
 1070 |auto gAudioIO = AudioIO::Get();
  | ^~~~
g++ -DHAVE_CONFIG_H -I.  -std=c++11 -Wno-deprecated-declarations 
-D__STDC_CONSTANT_MACROS -DWXINTL_NO_GETTEXT_MACRO 
-DLIBDIR=\"/usr/lib/x86_64-linux-gnu\"   -pthread
-I../lib-src/lib-widget-extra 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread   
-I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu   -I../lib-src/libnyquist 
-I/usr/include/soundtouch   -I/usr/include/lilv-0 -I/usr/include/sratom-0 
-I/usr/include/sord-0 -I/usr/include/serd-0 -I/usr/include/suil-0 
-I/usr/include/portSMF -I../lib-src/portmidi  -I../lib-src/sbsms/include   
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/us
 r/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-Wno-unused-local-typedefs -I../lib-src/portmixer/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DwxDEBUG_LEVEL=0 --std=gnu++11  -Wall -I../include 
-I../lib-src/FileDialog-c -o 
widgets/audacity-NumericTextCtrl.o `test -f 'widgets/NumericTextCtrl.cpp' || 
echo './'`widgets/NumericTextCtrl.cpp
g++ -DHAVE_CONFIG_H -I.  -std=c++11 -Wno-deprecated-declarations 
-D__STDC_CONSTANT_MACROS -DWXINTL_NO_GETTEXT_MACRO 
-DLIBDIR=\"/usr/lib/x86_64-linux-gnu\"   -pthread
-I../lib-src/lib-widget-extra 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread   
-I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu   -I../lib-src/libnyquist 
-I/usr/include/soundtouch   -I/usr/include/lilv-0 -I/usr/include/sratom-0 
-I/usr/include/sord-0 -I/usr/include/serd-0 -I/usr/include/suil-0 
-I/usr/include/portSMF -I../lib-src/portmidi  -I../lib-src/sbsms/include   
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/us
 r/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/atk-1.0 -I/usr/include/cairo 

Bug#956972: abcmidi: ftbfs with GCC-10

[Matthias Klose]

Package: src:abcmidi
Version: 20200122-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/abcmidi_20200122-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  | ^
drawtune.c:3019:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 3019 |   printbarnumber(ft->x, (int)ft->item);
  | ^
drawtune.c:3042:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 3042 |   printbarnumber(ft->x, (int)ft->item);
  | ^
drawtune.c:3050:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 3050 |   printbarnumber(ft->x, (int)ft->item);
  | ^
drawtune.c:3243:16: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 3243 |   lineno = (int)(ft->item);
  |^
drawtune.c: In function ‘getlineheight’:
drawtune.c:3366:16: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 3366 |   lineno = (int)(v->place->item);
  |^
drawtune.c:3375:36: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
 3375 |   *height = *height + (double)((int)v->place->item);
  |^
gcc -DANSILIBS -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2   -DHAVE_CONFIG_H 
-Wdate-time -D_FORTIFY_SOURCE=2 -I.   -c -o debug.o debug.c
debug.c: In function ‘showfeature’:
debug.c:146:30: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  146 |   printf("LINENUM %d\n", (int)(ft->item));
  |  ^
In file included from /usr/include/stdio.h:867,
 from debug.c:5:
In function ‘printf’,
inlined from ‘showtune’ at debug.c:229:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:107:10: warning: ‘%s’ directive 
argument is null [-Wformat-overflow=]
  107 |   return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack 
());
  |  ^~~
gcc -DANSILIBS -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2   -DHAVE_CONFIG_H 
-Wdate-time -D_FORTIFY_SOURCE=2 -I.   -c -o pslib.o pslib.c
gcc -DANSILIBS -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2   -DHAVE_CONFIG_H 
-Wdate-time -D_FORTIFY_SOURCE=2 -I.   -c -o position.o position.c
gcc -DANSILIBS -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2   -DHAVE_CONFIG_H 
-Wdate-time -D_FORTIFY_SOURCE=2 -I.   -c -o midicopy.o midicopy.c
gcc -DANSILIBS -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2   -DHAVE_CONFIG_H 
-Wdate-time -D_FORTIFY_SOURCE=2 -I.   -c -o abcmatch.o abcmatch.c
gcc -DANSILIBS -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2   -DHAVE_CONFIG_H 
-Wdate-time -D_FORTIFY_SOURCE=2 -I.   -c -o matchsup.o matchsup.c
matchsup.c: In function ‘event_octave’:
matchsup.c:818:6: warning: type of ‘local’ defaults to ‘int’ [-Wimplicit-int]
  818 | void event_octave(num, local)
  |  ^~~~
matchsup.c: In function ‘dumpfeat’:
matchsup.c:2015:34: warning: format ‘%d’ expects a matching ‘int’ argument 
[-Wformat=]
 2015 |   else printf("%d %s   %d %d %d %d 
\n",i,featname[j],pitch[i],num[i],denom[i]);
  | ~^
  |  |
  |  int
drawtune.c: In function ‘printtune’:
drawtune.c:3504:30: warning: ‘.eps’ directive writing 4 bytes into a region of 
size between 0 and 255 [-Wformat-overflow=]
 3504 

Bug#956974: ableton-link: ftbfs with GCC-10

[Matthias Klose]

Package: src:ableton-link
Version: 3.0.2+dfsg-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ableton-link_3.0.2+dfsg-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
[  6%] Building CXX object 
src/CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_PeerGateway.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  
-DLINK_PLATFORM_LINUX=1 -DLINK_PLATFORM_UNIX=1 -isystem 
/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wno-multichar   -o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_PeerGateway.cpp.o -c 
/<>/src/ableton/discovery/tst_PeerGateway.cpp
[  8%] Building CXX object 
src/CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_PeerGateways.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  
-DLINK_PLATFORM_LINUX=1 -DLINK_PLATFORM_UNIX=1 -isystem 
/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wno-multichar   -o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_PeerGateways.cpp.o -c 
/<>/src/ableton/discovery/tst_PeerGateways.cpp
[ 10%] Building CXX object 
src/CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_UdpMessenger.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  
-DLINK_PLATFORM_LINUX=1 -DLINK_PLATFORM_UNIX=1 -isystem 
/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wno-multichar   -o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_UdpMessenger.cpp.o -c 
/<>/src/ableton/discovery/tst_UdpMessenger.cpp
[ 12%] Building CXX object 
src/CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/v1/tst_Messages.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  
-DLINK_PLATFORM_LINUX=1 -DLINK_PLATFORM_UNIX=1 -isystem 
/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wno-multichar   -o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/v1/tst_Messages.cpp.o -c 
/<>/src/ableton/discovery/v1/tst_Messages.cpp
[ 14%] Building CXX object 
src/CMakeFiles/LinkDiscoveryTest.dir/ableton/test/catch/CatchMain.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  
-DLINK_PLATFORM_LINUX=1 -DLINK_PLATFORM_UNIX=1 -isystem 
/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wno-multichar   -o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/test/catch/CatchMain.cpp.o -c 
/<>/src/ableton/test/catch/CatchMain.cpp
[ 17%] Building CXX object 
src/CMakeFiles/LinkDiscoveryTest.dir/ableton/test/serial_io/SchedulerTree.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  
-DLINK_PLATFORM_LINUX=1 -DLINK_PLATFORM_UNIX=1 -isystem 
/<>/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wno-multichar   -o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/test/serial_io/SchedulerTree.cpp.o -c 
/<>/src/ableton/test/serial_io/SchedulerTree.cpp
[ 19%] Linking CXX executable ../bin/LinkDiscoveryTest
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/LinkDiscoveryTest.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wno-multichar  -Wl,-z,relro -rdynamic 
CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_InterfaceScanner.cpp.o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_Payload.cpp.o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_PeerGateway.cpp.o 
CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_PeerGateways.cpp.o 

Bug#951829: don't explicitly request python 3.7 for the build

[Matthias Klose]

On 2/24/20 9:35 AM, Mathieu Malaterre wrote:
> Control: tags -1 patch
> 
> Patch does not work. debian/rules uses py3version to compute the
> target locations of files, it is expected to only return one python
> supported version.
> 
> See past buildds failures:
> 
> * 
> https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=6.2.1-7=1582278085=0

well, then your assumptions are wrong? The package b-d's on python3-all-dev, so
it expects all supported python3 versions.  But your rules file doesn't do so,
it only builds for one version.

Bug#951829: don't explicitly request python 3.7 for the build

[Matthias Klose]

Package: src:openvdb
Version: 6.2.1-8
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

Don't explicitly request python 3.7 for the build, the build then fails with
3.8. patch at
http://launchpadlibrarian.net/466083872/openvdb_6.2.1-8_6.2.1-8ubuntu1.diff.gz

Bug#925754: Fixed in newer release of libopenshot / libopenshot-audio

[Matthias Klose]

libopenshot-audio 0.1.8 still fails to build with:

In file included from
/packages/tmp/p/libopenshot-audio-0.1.8/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/juce_graphics.h:82,
 from
/packages/tmp/p/libopenshot-audio-0.1.8/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/juce_gui_basics.h:28,
 from
/packages/tmp/p/libopenshot-audio-0.1.8/JuceLibraryCode/modules/juce_audio_processors/juce_audio_processors.h:28,
 from
/packages/tmp/p/libopenshot-audio-0.1.8/JuceLibraryCode/modules/juce_audio_processors/juce_audio_processors.cpp:39:
/packages/tmp/p/libopenshot-audio-0.1.8/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/colour/juce_PixelFormats.h:
In member function ‘juce::uint8& juce::PixelARGB
::getAlpha()’:
/packages/tmp/p/libopenshot-audio-0.1.8/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/colour/juce_PixelFormats.h:113:77:
error: cannot bind packed field ‘((juce::
PixelARGB*)this)->juce::PixelARGB::.juce::PixelARGBcomps[3]’ to ‘juce::uint8&’ {aka ‘unsigned char&’}
  113 | forcedinline uint8& getAlpha() noexcept   { return comps
[indexA]; }
  |
~^

Bug#948977: kodi ftbfs in unstable (fontforge segfault)

[Matthias Klose]

Package: src:kodi
Version: 2:17.6+dfsg1-4
Severity: serious
Tags: sid bullseye

kodi ftbfs in unstable (fontforge segfault):

[...]
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:498: installing 'build-aux/compile'
configure.ac:16: installing 'build-aux/config.guess'
configure.ac:16: installing 'build-aux/config.sub'
configure.ac:15: installing 'build-aux/install-sh'
configure.ac:15: installing 'build-aux/missing'
configure.ac:2282: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or
'*_CPPFLAGS')
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/kodi-17.6+dfsg1'
cp -r /<>/kodi-17.6+dfsg1/webinterface-default
/<>/kodi-17.6+dfsg1/addons/webinterface.default
sed -i 's/DEB_VERSION/"'2:17.6+dfsg1-4ubuntu6'"/' xbmc/Application.cpp
xbmc/utils/SystemInfo.cpp
fontforge -script /<>/kodi-17.6+dfsg1/debian/mergefonts.ff \
/usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf \
/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf \
/<>/kodi-17.6+dfsg1/media/Fonts/arial.ttf
Copyright (c) 2000-2019. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later 
 with many parts BSD . Please read LICENSE.
 Version: 20190801
 Based on sources from 12:20 UTC 13-Nov-2019-ML-D-GDK3.
Cannot find your hotkey definition file!
This font contains both a 'kern' table and a 'GPOS' table.
  The 'kern' table will only be read if there is no 'kern' feature in 'GPOS'.
Use-my-metrics flag set on at least two components in glyph 685
The glyph named Omega is mapped to U+03A9.
  But its name indicates it should be mapped to U+2126.
Attempt to output -2027224918 into a 16-bit field. It will be truncated and the
file may not be useful.make[1]: *** [debian/rules:115:
override_dh_auto_configure] Segmentation fault (core dumped)
make[1]: Leaving directory '/<>/kodi-17.6+dfsg1'
make: *** [debian/rules:90: build] Error 2

Bug#938601: supercollider: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:supercollider
Version: 1:3.10.0+repack-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:supercollider

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#938081: python-pyo: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:python-pyo
Version: 0.9.1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-pyo

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#938072: python-pyknon: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:python-pyknon
Version: 1.0-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-pyknon

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#937917: python-midiutil: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:python-midiutil
Version: 1.2.1-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-midiutil

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#937540: pysoundfile: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:pysoundfile
Version: 0.10.1-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:pysoundfile

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#937266: pd-py: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:pd-py
Version: 0.2.2+git20170625.1.88fc77a-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:pd-py

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#937208: openni-sensor-primesense: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:openni-sensor-primesense
Version: 5.1.0.41-9
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:openni-sensor-primesense

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#937206: openni2: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:openni2
Version: 2.2.0.33+dfsg-11
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:openni2

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#937205: openni: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:openni
Version: 1.5.4.0+dfsg-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:openni

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#937207: openni-sensor-pointclouds: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:openni-sensor-pointclouds
Version: 5.1.0.41.9-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + 
src:openni-sensor-pointclouds

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#936883: libkate: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:libkate
Version: 0.4.1-9
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:libkate

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#936813: laditools: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:laditools
Version: 1.1.0-3.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:laditools

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#936805: kodi: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:kodi
Version: 2:17.6+dfsg1-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:kodi

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#936721: idjc: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:idjc
Version: 0.8.17-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:idjc

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

Bug#936693: handbrake: Python2 removal in sid/bullseye

[Matthias Klose]

Package: src:handbrake
Version: 1.2.2+ds1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:handbrake

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.