Processed: Extracting AutoPkgTest smoke test code to separate package

[Debian Bug Tracking System]

Processing control commands:

> block 1040846 by -1
Bug #1040846 [src:editorconfig-core-py] editorconfig-core-py autopkg test fail 
with setuptools 68
1040846 was not blocked by any bugs.
1040846 was not blocking any bugs.
Added blocking bug(s) of 1040846: 1041240
> block 1040848 by -1
Bug #1040848 [src:pyethash] pyethash autopkg test fail with setuptools 68
1040848 was not blocked by any bugs.
1040848 was not blocking any bugs.
Added blocking bug(s) of 1040848: 1041240
> block 1040849 by -1
Bug #1040849 [src:pyrlp] pyrlp autopkg test fail with setuptools 68
1040849 was not blocked by any bugs.
1040849 was not blocking any bugs.
Added blocking bug(s) of 1040849: 1041240
> block 1040850 by -1
Bug #1040850 [src:python-coverage] python-coverage autopkg test fail with 
setuptools 68
1040850 was not blocked by any bugs.
1040850 was not blocking any bugs.
Added blocking bug(s) of 1040850: 1041240
> block 1040851 by -1
Bug #1040851 [src:python-daemon] python-daemon autopkg test fail with 
setuptools 68
1040851 was not blocked by any bugs.
1040851 was not blocking any bugs.
Added blocking bug(s) of 1040851: 1041240
> block 1040852 by -1
Bug #1040852 [src:python-jsonext] python-jsonext autopkg test fail with 
setuptools 68
1040852 was not blocked by any bugs.
1040852 was not blocking any bugs.
Added blocking bug(s) of 1040852: 1041240
> block 1040853 by -1
Bug #1040853 [src:python-lockfile] python-lockfile autopkg test fail with 
setuptools 68
1040853 was not blocked by any bugs.
1040853 was not blocking any bugs.
Added blocking bug(s) of 1040853: 1041240
> block 1040854 by -1
Bug #1040854 [src:python-tinyrpc] tinyrpc autopkg test fail with setuptools 68
1040854 was not blocked by any bugs.
1040854 was not blocking any bugs.
Added blocking bug(s) of 1040854: 1041240

-- 
1040846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040846
1040848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040848
1040849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040849
1040850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040850
1040851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040851
1040852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040852
1040853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040853
1040854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040854
1041240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1037681

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1037681 + ftbfs
Bug #1037681 [src:gr-funcube] gr-funcube: ftbfs with GCC-13
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1037681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041454: naev: FTBFS on i386

[Sebastian Ramacher]

Source: naev
Version: 0.8.2-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=naev&arch=mips64el&ver=0.8.2-1%2Bb2&stamp=1689629171&raw=0

Configuring config.h using configuration
Has header "windows.h" : NO 
Library dl found: YES
Configuring naev.sh using configuration

../test/glcheck/meson.build:4:15: ERROR: Can not run test applications in this 
cross environment.

Cheers
-- 
Sebastian Ramacher

Processed: retitle 1041454 to naev: FTBFS on mips64el

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1041454 naev: FTBFS on mips64el
Bug #1041454 [src:naev] naev: FTBFS on i386
Changed Bug title to 'naev: FTBFS on mips64el' from 'naev: FTBFS on i386'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041456: gnuradio-dev depends on cruft libvolk2-dev

[Adrian Bunk]

Package: gnuradio-dev
Version: 3.10.7.0-1
Severity: serious
Control: affects -1 gnuradio

gnuradio-dev depends on cruft libvolk2-dev,
which installs an obsolete version of volk.

There is a similar problem with gnuradio
still depending on libvolk2-bin.

Processed: gnuradio-dev depends on cruft libvolk2-dev

[Debian Bug Tracking System]

Processing control commands:

> affects -1 gnuradio
Bug #1041456 [gnuradio-dev] gnuradio-dev depends on cruft libvolk2-dev
Added indication that 1041456 affects gnuradio

-- 
1041456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1037682

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1037682 + ftbfs
Bug #1037682 [src:gr-gsm] gr-gsm: ftbfs with GCC-13
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1037682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1037680

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1037680 + ftbfs
Bug #1037680 [src:gnss-sdr] gnss-sdr: ftbfs with GCC-13
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1037680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041457: python-escript: FTBFS on i386

[Sebastian Ramacher]

Source: python-escript
Version: 5.6-4
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=python-escript&arch=i386&ver=5.6-4%2Bb4&stamp=1689629735&raw=0

/usr/include/boost/bind.hpp:36:1: note: '#pragma message: The practice of 
declaring the Bind placeholders (_1, _2, ...) in the global namespace is 
deprecated. Please use  + using namespace 
boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the 
current behavior.'
   36 | BOOST_PRAGMA_MESSAGE(
  | ^~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: '#pragma message: This 
header is deprecated. Use  instead.'
   13 | BOOST_HEADER_DEPRECATED("")
  | ^~~

cc1plus: out of memory allocating 13288 bytes after a total of 774123520 bytes
scons: *** [debian/tmp3/posix/ripley/src/DefaultAssembler3D.os] Error 1
scons: building terminated because of errors.


Cheers
-- 
Sebastian Ramacher

Bug#1041458: colmap: FTBFS on i386

[Sebastian Ramacher]

Source: colmap
Version: 3.8-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=colmap&arch=i386&ver=3.8-1%2Bb1&stamp=1689694063&raw=0

[ 92%] Building CXX object 
src/CMakeFiles/colmap.dir/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp.o
cd /<>/obj-i686-linux-gnu/src && /usr/bin/c++ -DBOOST_ALL_NO_LIB 
-DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT -DGUI_ENABLED -DOPENGL_ENABLED 
-DOPENMP_ENABLED -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -I/<>/lib -I/<>/src -isystem 
/usr/include/eigen3 -isystem /usr/include/i386-linux-gnu/qt5 -isystem 
/usr/include/i386-linux-gnu/qt5/QtCore -isystem 
/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/i386-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/i386-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/i386-linux-gnu/qt5/QtGui -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DDISABLE_CPU_NEON 
-Wno-maybe-uninitialized -fopenmp -Wall -std=c++14 -fPIC -fPIC -MD -MT 
src/CMakeFiles/colmap.dir/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp.o -MF 
CMakeFiles/colmap.dir/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp.o.d -o 
CMakeFiles/colmap.dir/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp.o -c 
/<>/obj-i686-linux-gnu/src/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp

cc1plus: out of memory allocating 72 bytes after a total of 89124864 bytes
make[3]: *** [src/CMakeFiles/colmap.dir/build.make:657: 
src/CMakeFiles/colmap.dir/estimators/generalized_absolute_pose_coeffs.cc.o] 
Error 1

Cheers
-- 
Sebastian Ramacher

Processed: tagging 1041442

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1041442 + ftbfs
Bug #1041442 [src:python-fabio] python-fabio_2023.6.0-1_ppc64el-buildd.changes 
REJECTED
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1037622

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1037622 + ftbfs
Bug #1037622 [src:dolfin] dolfin: ftbfs with GCC-13
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1037622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041459: openturns: FTBFS everwhere

[Sebastian Ramacher]

Source: openturns
Version: 1.20-9
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=openturns&arch=amd64&ver=1.20-9%2Bb1&stamp=1689716922&raw=0

The following tests FAILED:
103 - cppcheck_Bonmin_std (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/<>/builddir'

Cheers
-- 
Sebastian Ramacher

Bug#1041460: octave: FTBFS on 32 bit architectures

[Sebastian Ramacher]

Source: octave
Version: 8.2.0-4
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=octave&arch=armel&ver=8.2.0-4&stamp=1689713418&raw=0


  libinterp/corefcn/psi.cc-tst ... pass   30/30 
 
  libinterp/corefcn/qr.cc-tst fatal: caught 
signal Segmentation fault -- stopping myself...
/bin/bash: line 1: 1484498 Segmentation fault  ( /bin/bash ../run-octave 
--no-init-file --silent --no-history -p /<>/test/mex 
/<>/test/fntests.m /<>/test )
make[6]: *** [Makefile:2882: check-local] Error 139
make[6]: Leaving directory '/<>/test'

Cheers
-- 
Sebastian Ramacher

Processed: bug 1000005 is forwarded to https://forums.passwordmaker.org/index.php?topic=1834.0

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 105 https://forums.passwordmaker.org/index.php?topic=1834.0
Bug #105 [src:passwordmaker-cli] passwordmaker-cli: depends on obsolete 
pcre3 library
Set Bug forwarded-to-address to 
'https://forums.passwordmaker.org/index.php?topic=1834.0'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037906: marked as done (yambar: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 08:37:38 +
with message-id 
and subject line Bug#1037906: fixed in yambar 1.10.0-1
has caused the Debian Bug report #1037906,
regarding yambar: ftbfs with GCC-13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:yambar
Version: 1.9.0-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/yambar_1.9.0-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

[...]
[24/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-cpu.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-cpu.5.scd'
[25/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-disk-io.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-disk-io.5.scd'
[26/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-dwl.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-dwl.5.scd'
[27/96] /usr/bin/meson --internal exe --capture 
doc/yambar-modules-foreign-toplevel.5 -- /bin/sh -c '/usr/bin/scdoc < 
../doc/yambar-modules-foreign-toplevel.5.scd'
[28/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-mpd.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-mpd.5.scd'
[29/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-mem.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-mem.5.scd'
[30/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-label.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-label.5.scd'
[31/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-pipewire.5 
-- /bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-pipewire.5.scd'
[32/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-i3.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-i3.5.scd'
[33/96] /usr/bin/env LC_ALL=C ../generate-version.sh 1.9.0 ../ version.h
[34/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-network.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-network.5.scd'
[35/96] /usr/bin/flex -o yambar.p/map.yy.c ../particles/map.l
[36/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-pulse.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-pulse.5.scd'
[37/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-removables.5 
-- /bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-removables.5.scd'
[38/96] /usr/bin/bison -Wall -Wcounterexamples --defines=yambar.p/map.tab.h 
--output=yambar.p/map.tab.c ../particles/map.y
[39/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-script.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-script.5.scd'
[40/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-river.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-river.5.scd'
[41/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-sway-xkb.5 
-- /bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-sway-xkb.5.scd'
[42/96] /usr/bin/meson --internal exe --capture doc/yambar-modules-xkb.5 -- 
/bin/sh -c '/usr/bin/scdoc < ../doc/yambar-modules-xkb.5.scd'
[43/96] cc -Iyambar.p -I. -I.. -Iparticles -I../particles -Ibar -Imodules 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/harfbuzz -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/json-c 
-I/usr/include/pipewire-0.3 -I/usr/include/spa-0.2 -fdiagnostics-color=always 
-DNDE

Processed: affects 1041211

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1041211 = src:sdl12-compat
Bug #1041211 [src:libsdl-perl] libsdl-perl: FTBFS and autopkgtest failure with 
sdl12-compat, especially on 32-bit
Removed indication that 1041211 affects src:libsdl-perl
Added indication that 1041211 affects src:sdl12-compat
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041443: [Debian-pan-maintainers] Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED

[PICCA Frederic-Emmanuel]

ok, it seems that I generated an orig.tag.gz with this (Thu Jan  1 00:00:00 
1970).

I can not remember which tool I used to generate this file.

gbp import-orig --uscan

or

deb-new-upstream

Nevertheless, why is it a serious bug ?

thanks

Frederic

Bug#1041443: [Debian-pan-maintainers] Bug#1041443: Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED

[PICCA Frederic-Emmanuel]

I just check this date is in the upstream tar file

https://files.pythonhosted.org/packages/54/84/ea12e176489b35c4610625ce56aa2a1d91ab235b0caa71846317bfd1192f/pyfai-2023.5.0.tar.gz

Processed: Bug#1041412 marked as pending in golang

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041412 [golang-1.21-src] golang-1.21-src: missing Breaks+Replaces: 
golang-1.21-go (<< 1.21~rc3)
Added tag(s) pending.

-- 
1041412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041412: marked as pending in golang

[Shengjing Zhu]

Control: tag -1 pending

Hello,

Bug #1041412 in golang reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/compiler/golang/-/commit/91c4555c1feb87c7139ce8e848d936a49b4177d9


Add Breaks+Replaces golang-1.21-go (<< 1.21~rc3) on golang-1.21-src

src/internal/platform/zosarch.go move from golang-1.21-go to golang-1.21-src
(Closes: #1041412)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041412

Bug#852964: marked as pending in golang-github-hashicorp-yamux

[Shengjing Zhu]

Control: tag -1 pending

Hello,

Bug #852964 in golang-github-hashicorp-yamux reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-hashicorp-yamux/-/commit/aa3d5db16338f635ea6d7f14b4f70b9a6b893fd5


Add patch to increase timeout in TestSendData_VeryLarge

Closes: #852964


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/852964

Processed: Bug#852964 marked as pending in golang-github-hashicorp-yamux

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #852964 [src:golang-github-hashicorp-yamux] golang-github-hashicorp-yamux: 
FTBFS randomly (failing tests)
Added tag(s) pending.

-- 
852964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1040473: marked as done (python-click: FTBFS after new pytest)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 10:35:40 +
with message-id 
and subject line Bug#1040473: fixed in python-click 8.1.6-1
has caused the Debian Bug report #1040473,
regarding python-click: FTBFS after new pytest
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1040473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: python-click
Version: 8.1.3-2
Severity: serious

Hello, after new pytest went in sid (or some other python updates), the package 
started FTBFS

I: Logging to /home/pbuilder/sid_result/python-click_8.1.3-2_amd64.build
D: cmdline: build --distribution sid --buildresult /home/pbuilder/sid_result 
--basetgz /home/pbuilder/sid-base.tgz --logfile 
/home/pbuilder/sid_result/python-click_8.1.3-2_amd64.build --mirror 
http://deb.debian.org/debian --debootstrapopts 
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg --aptcache 
/home/pbuilder/aptcache/debian --components main contrib non-free 
../python-click_8.1.3-2.dsc
W: cgroups are not available on the host, not using them.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Jul  6 12:17:33 CEST 2023
I: pbuilder-time-stamp: 1688638653
I: Building the build Environment
I: extracting base tarball [/home/pbuilder/sid-base.tgz]
I: copying local configuration
W: No local /etc/mailname to copy, relying on /tmp/build/356573/etc/mailname to 
be correct
W: --override-config is not set; not updating apt.conf Read the manpage for 
details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
D: no hooks of type H found -- ignoring
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [../python-click_8.1.3-2.dsc]
I: copying [../python-click_8.1.3.orig.tar.gz]
I: copying [../python-click_8.1.3-2.debian.tar.xz]
I: Extracting source
gpgv: Signature made Tue Jan 10 06:12:58 2023 UTC
gpgv:using RSA key B9FAD3192AF3E4A5309D9D39879F3C993801A94F
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for 
./python-click_8.1.3-2.dsc: no acceptable signature found
dpkg-source: info: extracting python-click in python-click-8.1.3
dpkg-source: info: unpacking python-click_8.1.3.orig.tar.gz
dpkg-source: info: unpacking python-click_8.1.3-2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying docs-Use-local-Python-intersphinx-inventary.patch
I: Not using root during the build.
I: Installing the build-deps
I: user script /tmp/build/356573/tmp/hooks/D20update starting
Hit:1 http://deb.debian.org/debian sid InRelease
Reading package lists...
I: user script /tmp/build/356573/tmp/hooks/D20update finished
 -> Attempting to parse the build-deps
 -> Considering build-depdebhelper-compat (= 13)
   -> Trying to add debhelper-compat=13
 -> Considering build-dep dh-sequence-python3
   -> Trying to add dh-sequence-python3
 -> Considering build-dep python3-all
   -> Trying to add python3-all
 -> Considering build-dep python3-doc 
   -> Trying to add python3-doc
 -> Considering build-dep python3-colorama
   -> Trying to add python3-colorama
 -> Considering build-dep python3-docutils
   -> Trying to add python3-docutils
 -> Considering build-dep python3-pallets-sphinx-themes (>= 2.0.1) 
   -> Trying to add python3-pallets-sphinx-themes
 -> Considering build-dep python3-pytest 
   -> Trying to add python3-pytest
 -> Considering build-dep python3-requests
   -> Trying to add python3-requests
 -> Considering build-dep python3-setuptools
   -> Trying to add python3-setuptools
 -> Considering build-dep python3-sphinx 
   -> Trying to add python3-sphinx
 -> Considering build-dep python3-sphinx-issues 
   -> Trying to add python3-sphinx-issues
 -> Considering build-dep python3-sphinx-tabs 
   -> Trying to add python3-sphinx-tabs
 -> Considering build-dep python3-sphinxcontrib-log-cabinet 
   -> Trying to add python3-sphinxcontrib-log-cabinet
 -> Installing  debhelper-compat=13 dh-sequence-python3 python3-all python3-doc 
python3-colorama python3-docutils python3-pallets-sphinx-themes python3-pytest 
python3-requests python3-setuptools python3-sphinx python3-sphinx-issues 
python3-sphinx-tabs python3-sphinxcontrib-log-cabinet
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  autoconf automake autopoint autotools-dev bsdextraut

Bug#852964: marked as done (golang-github-hashicorp-yamux: FTBFS randomly (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 10:35:30 +
with message-id 
and subject line Bug#852964: fixed in golang-github-hashicorp-yamux 0.1.1-1
has caused the Debian Bug report #852964,
regarding golang-github-hashicorp-yamux: FTBFS randomly (failing tests)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-hashicorp-yamux
Version: 0.0~git20151129.0.df94978-1
Severity: important

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_testdir -i -O--buildsystem=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
go install -v -p 1 github.com/hashicorp/yamux
github.com/hashicorp/yamux
   dh_auto_test -i -O--buildsystem=golang
go test -v -p 1 github.com/hashicorp/yamux
=== RUN   TestConst
--- PASS: TestConst (0.00s)
=== RUN   TestEncodeDecode
--- PASS: TestEncodeDecode (0.00s)

[... snipped ...]

=== RUN   TestGoAway
--- PASS: TestGoAway (0.00s)
=== RUN   TestManyStreams
--- PASS: TestManyStreams (0.60s)
=== RUN   TestManyStreams_PingPong
--- PASS: TestManyStreams_PingPong (1.30s)
=== RUN   TestHalfClose
--- PASS: TestHalfClose (0.00s)
=== RUN   TestReadDeadline
--- PASS: TestReadDeadline (0.01s)
=== RUN   TestWriteDeadline
--- PASS: TestWriteDeadline (0.05s)
=== RUN   TestBacklogExceeded
--- PASS: TestBacklogExceeded (0.02s)
=== RUN   TestKeepAlive
--- PASS: TestKeepAlive (0.20s)
=== RUN   TestKeepAlive_Timeout
--- PASS: TestKeepAlive_Timeout (0.35s)
=== RUN   TestLargeWindow
--- PASS: TestLargeWindow (0.01s)
=== RUN   TestSendData_VeryLarge
2017/01/28 00:54:09 [ERR] yamux: keepalive failed: session shutdown
--- FAIL: TestSendData_VeryLarge (20.00s)
panic: timeout [recovered]
panic: timeout

goroutine 376 [running]:
panic(0x516d80, 0xc4201eb130)
/usr/lib/go-1.7/src/runtime/panic.go:500 +0x1a1
testing.tRunner.func1(0xc420018900)
/usr/lib/go-1.7/src/testing/testing.go:579 +0x25d
panic(0x516d80, 0xc4201eb130)
/usr/lib/go-1.7/src/runtime/panic.go:458 +0x243
github.com/hashicorp/yamux.TestSendData_VeryLarge(0xc420018900)

/<>/obj-x86_64-linux-gnu/src/github.com/hashicorp/yamux/session_test.go:900
 +0x2f2
testing.tRunner(0xc420018900, 0x558898)
/usr/lib/go-1.7/src/testing/testing.go:610 +0x81
created by testing.(*T).Run
/usr/lib/go-1.7/src/testing/testing.go:646 +0x2ec
exit status 2
FAILgithub.com/hashicorp/yamux  22.833s
dh_auto_test: go test -v -p 1 github.com/hashicorp/yamux returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/golang-github-hashicorp-yamux/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough times (as the failure happens randomly).

Thanks.
--- End Message ---
--- Begin Message ---
Source: golang-github-hashicorp-yamux
Source-Version: 0.1.1-1
Done: Shengjing Zhu 

We believe that the bug you reported is fixed in the latest version of
golang-github-hashicorp-yamux, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated 
golang-github-hashicorp-yamux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Jul 2023 18:27:45 +0

Bug#1041412: marked as done (golang-1.21-src: missing Breaks+Replaces: golang-1.21-go (<< 1.21~rc3))

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 10:35:21 +
with message-id 
and subject line Bug#1041412: fixed in golang-1.21 1.21~rc3-2
has caused the Debian Bug report #1041412,
regarding golang-1.21-src: missing Breaks+Replaces: golang-1.21-go (<< 1.21~rc3)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-1.21-src
Version: 1.21~rc3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../golang-1.21-src_1.21~rc3-1_all.deb ...
  Unpacking golang-1.21-src (1.21~rc3-1) over (1.21~rc2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-1.21-src_1.21~rc3-1_all.deb (--unpack):
   trying to overwrite '/usr/share/go-1.21/src/internal/platform/zosarch.go', 
which is also in package golang-1.21-go 1.21~rc2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/golang-1.21-src_1.21~rc3-1_all.deb


cheers,

Andreas


golang-1.21-go=1.21~rc2-2_golang-1.21-src=1.21~rc3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: golang-1.21
Source-Version: 1.21~rc3-2
Done: Shengjing Zhu 

We believe that the bug you reported is fixed in the latest version of
golang-1.21, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated golang-1.21 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Jul 2023 16:12:19 +0800
Source: golang-1.21
Architecture: source
Version: 1.21~rc3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Compiler Team 
Changed-By: Shengjing Zhu 
Closes: 1041412
Changes:
 golang-1.21 (1.21~rc3-2) unstable; urgency=medium
 .
   * Team upload
   * Add Breaks+Replaces golang-1.21-go (<< 1.21~rc3) on golang-1.21-src
 src/internal/platform/zosarch.go move from golang-1.21-go to
 golang-1.21-src (Closes: #1041412)
Checksums-Sha1:
 6efa93c14b440f479de5810d61579cdc07eae2cd 2313 golang-1.21_1.21~rc3-2.dsc
 adfb0a85fd7669617e0e1fd088ca46bd2eac5174 36252 
golang-1.21_1.21~rc3-2.debian.tar.xz
 b8b08949f472b19cf9635bf91caee7c219d5be7d 6371 
golang-1.21_1.21~rc3-2_amd64.buildinfo
Checksums-Sha256:
 e1913a86753fcb3a63570a6132791ffe56804a3b0ddbac58c96ba91ddaf832e6 2313 
golang-1.21_1.21~rc3-2.dsc
 2279b4f8d4f37c792df61618114ed71e6569b24cf85177e4e3f72a962131e5ee 36252 
golang-1.21_1.21~rc3-2.debian.tar.xz
 fdb6223262e13b9c2d5fa27b3174d26c55d56fb7af00dae94f96cf3e6694134f 6371 
golang-1.21_1.21~rc3-2_amd64.buildinfo
Files:
 81753eb896ddfa29f0bd8f41120cdd64 2313 golang optional 
golang-1.21_1.21~rc3-2.dsc
 5919ae18bc92b21f4aff0f49bbd8c429 36252 golang optional 
golang-1.21_1.21~rc3-2.debian.tar.xz
 4cabf9ce2a20c2f12864e40a65e94150 6371 golang optional 
golang-1.21_1.21~rc3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCZLe1kgAKCRB/RPol6lUU
y6IMAQCdTND7V+4fct9kNNodVQmUOks5heOp0bSv5IhbgOJSLQEAukMeIvgcp8D3
VUapzAuoGQsZYSbFruwiuFAT2EBCTg8=
=t1D+
-END PGP SIGNATURE End Message ---

Bug#1041471: src:isa-support: fails to migrate to testing for too long: new autopkgtest fails on armel

[Paul Gevers]

Source: isa-support
Version: 15.1
Severity: serious
Control: close -1 19
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:isa-support has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable added 
an autopkgtest that segfaults on armel. (Just for your info in case it's 
relevant, the ci.debian.net armel VM's run on arm64 hardware.)


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=isa-support


OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:isa-support: fails to migrate to testing for too long: new autopkgtest fails on armel

[Debian Bug Tracking System]

Processing control commands:

> close -1 19
Bug #1041471 [src:isa-support] src:isa-support: fails to migrate to testing for 
too long: new autopkgtest fails on armel
Marked as fixed in versions isa-support/19.
Bug #1041471 [src:isa-support] src:isa-support: fails to migrate to testing for 
too long: new autopkgtest fails on armel
Marked Bug as done

-- 
1041471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: src:lmfit-py: fails to migrate to testing for too long: autopkgtest regression on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.2.1-1
Bug #1041472 [src:lmfit-py] src:lmfit-py: fails to migrate to testing for too 
long: autopkgtest regression on i386
Marked as fixed in versions lmfit-py/1.2.1-1.
Bug #1041472 [src:lmfit-py] src:lmfit-py: fails to migrate to testing for too 
long: autopkgtest regression on i386
Marked Bug as done

-- 
1041472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041472: src:lmfit-py: fails to migrate to testing for too long: autopkgtest regression on i386

[Paul Gevers]

Source: lmfit-py
Version: 1.1.0-1
Severity: serious
Control: close -1 1.2.1-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:lmfit-py has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The autopkgtest of the version in 
unstable fails on i386, where it passed in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=lmfit-py



OpenPGP_signature
Description: OpenPGP digital signature

Processed: closing 1000034

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 134
Bug #134 [src:cyrus-imapd] cyrus-imapd: depends on obsolete pcre3 library
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037856: marked as done (seqan-raptor: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 11:06:11 +
with message-id 
and subject line Bug#1037856: fixed in seqan-raptor 3.0.0+ds-2
has caused the Debian Bug report #1037856,
regarding seqan-raptor: ftbfs with GCC-13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:seqan-raptor
Version: 2.0.0.0.git.fecfbca+ds-3
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/seqan-raptor_2.0.0.0.git.fecfbca+ds-3_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

[...]
  int main() {}

Performing C++ SOURCE FILE Test CONCEPTS_FLAG_BUILTIN failed with the following 
output:
Change Dir: 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-gAVnUn

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_fd778/fast && gmake[2]: 
Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-gAVnUn'
/usr/bin/gmake  -f CMakeFiles/cmTC_fd778.dir/build.make 
CMakeFiles/cmTC_fd778.dir/build
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-gAVnUn'
Building CXX object CMakeFiles/cmTC_fd778.dir/src.cxx.o
/usr/bin/c++ -DCONCEPTS_FLAG_BUILTIN  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/seqan3/submodules/sdsl-lite/include/ -I/usr/include/simde 
-I/<>/lib/submodules/sharg-parser/include/ 
-I/<>/lib/submodules/lemon/include/ -mpopcnt -fopenmp 
-fopenmp-simd -DSIMDE_ENABLE_OPENMP -Wno-psabi -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/seqan3/submodules/sdsl-lite/include/ -I/usr/include/simde 
-I/<>/lib/submodules/sharg-parser/include/ 
-I/<>/lib/submodules/lemon/include/ -mpopcnt -fopenmp 
-fopenmp-simd -DSIMDE_ENABLE_OPENMP -Wno-psabi -o 
CMakeFiles/cmTC_fd778.dir/src.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-gAVnUn/src.cxx
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-gAVnUn/src.cxx:1:16:
 error: ‘__cpp_concepts’ was not declared in this scope
1 | static_assert (__cpp_concepts >= 201507); int 
main() {}
  |^~
gmake[3]: *** [CMakeFiles/cmTC_fd778.dir/build.make:78: 
CMakeFiles/cmTC_fd778.dir/src.cxx.o] Error 1
gmake[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-gAVnUn'
gmake[2]: *** [Makefile:127: cmTC_fd778/fast] Error 2
gmake[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-gAVnUn'


Source file was:
static_assert (__cpp_concepts >= 201507); int main() {}

Determining if the include file sdsl/version.hpp exists failed with the 
following output:
Change Dir: 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-ktDVva

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_5241a/fast && gmake[2]: 
Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-ktDVva'
/usr/bin/gmake  -f CMakeFiles/cmTC_5241a.dir/build.make 
CMakeFiles/cmTC_5241a.dir/build
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-ktDVva'
Building CXX object CMakeFiles/cmTC_5241a.dir/CheckIncludeFile.cxx.o
/usr/bin/c++   -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -W

Bug#1041371: marked as done (seqan3 autopkg test fails)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 11:06:26 +
with message-id 
and subject line Bug#1041371: fixed in seqan3 3.3.0~rc.1+ds-3
has caused the Debian Bug report #1041371,
regarding seqan3 autopkg test fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:seqan3
Version: 3.2.0+ds-7
Severity: serious
Tags: sid trixie

this blocks the otherwise unrelated migration of gcc-defaults.

see 
https://ci.debian.net/data/autopkgtest/testing/amd64/s/seqan3/35917949/log.gz

[...]
 35s + export CXX=g++
 35s + export CC=gcc
 35s + dpkg-buildflags --get CFLAGS
 35s + dpkg-buildflags --get CPPFLAGS
 35s + export CFLAGS=-g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.li5aisvz/downtmp/autopkgtest_tmp/build_unit=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -fuse-ld=gold

 35s + dpkg-buildflags --get CXXFLAGS
 35s + dpkg-buildflags --get CPPFLAGS
 35s + export CXXFLAGS=-g -O2 
-ffile-prefix-map=/tmp/autopkgtest-lxc.li5aisvz/downtmp/autopkgtest_tmp/build_unit=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -O3 -fuse-ld=gold

 35s + dpkg-buildflags --get LDFLAGS
 35s + export LDFLAGS=-Wl,-z,relro -Wl,-z,now
 35s + CMAKE_PREFIX_PATH=/usr/share/cmake cmake ../unit 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON

 35s -- The CXX compiler identification is GNU 13.1.0
 35s -- Detecting CXX compiler ABI info
 35s -- Detecting CXX compiler ABI info - done
 35s -- Check for working CXX compiler: /usr/bin/g++ - skipped
 35s -- Detecting CXX compile features
 35s -- Detecting CXX compile features - done
 35s -- Finding SeqAn3 and checking requirements:
 35s --   SeqAn3 include dir found:   /usr/include
 35s -- …adding submodule include: 
/usr/include/seqan3/submodules/sdsl-lite/include

 35s --   C++ Standard-20 support:via -std=c++20
 35s --   C++ Concepts support:   via -std=c++20
 36s --   Thread support: builtin.
 36s CMake Error at /usr/share/cmake/seqan3/seqan3-config.cmake:113 (message):
 36s   The SDSL library is required, but wasn't found.  Get it from
 36s   https://github.com/xxsds/sdsl-lite
 36s Call Stack (most recent call first):
 36s   /usr/share/cmake/seqan3/seqan3-config.cmake:319 (seqan3_config_error)
 36s 
/tmp/autopkgtest-lxc.li5aisvz/downtmp/autopkgtest_tmp/seqan3-test.cmake:15 
(find_package)

 36s   CMakeLists.txt:11 (include)
 36s
 36s
 36s -- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: seqan3
Source-Version: 3.3.0~rc.1+ds-3
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
seqan3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated seqan3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jul 2023 12:49:27 +0200
Source: seqan3
Architecture: source
Version: 3.3.0~rc.1+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 1041371
Changes:
 seqan3 (3.3.0~rc.1+ds-3) unstable; urgency=medium
 .
   * Release 3.3.0 RC1 to unstable with GCC 13 fixes. Closes: #1041371
Checksums-Sha1:
 ea7923d3220523ef3c55720dbaa91f578ec273e3 2547 seqan3_3.3.0~rc.1+ds-3.dsc
 90d9a81123235160f698489ea4205d5ef7f37b0a 10620 
seqan3_3.3.0~rc.1+ds-3.debian.tar.xz
 9e992d96491c281d3748c6cab92db9cb9ecf989a 15027 
seqan3_3.3.0~rc.1+ds-3_source.buildinfo
Checksums-Sha256:
 6fee903fc1a5cc97a00ae40e341718f611802e0e0ad436592e27d355773febf5 2547 
seqan3_3.3.0~rc.1+ds-3.dsc
 94eeca87c7802c6112c04ab9112567297a76a3746f16681f7e14bffb219dae1b 10620 
seqan3_3.3.0~rc.1+ds-3.debian.tar.xz
 94333dfe943ba24974b6f8e12d452beb88960d96ab2f076914d4d8e11fe6fc08 15027 
seqan3_3.3.0~rc.1+ds-3_source.buildinfo
Files:
 72d76fbb19ff6bd1cedf60ec03b87cfe 2547 science optional 
seqan3_3.3.0~rc.1

Bug#1041456: marked as done (gnuradio-dev depends on cruft libvolk2-dev)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 11:05:19 +
with message-id 
and subject line Bug#1041456: fixed in gnuradio 3.10.7.0-2
has caused the Debian Bug report #1041456,
regarding gnuradio-dev depends on cruft libvolk2-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnuradio-dev
Version: 3.10.7.0-1
Severity: serious
Control: affects -1 gnuradio

gnuradio-dev depends on cruft libvolk2-dev,
which installs an obsolete version of volk.

There is a similar problem with gnuradio
still depending on libvolk2-bin.
--- End Message ---
--- Begin Message ---
Source: gnuradio
Source-Version: 3.10.7.0-2
Done: A. Maitland Bottoms 

We believe that the bug you reported is fixed in the latest version of
gnuradio, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gnuradio package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Jul 2023 06:19:08 -0400
Source: gnuradio
Architecture: source
Version: 3.10.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 1041456
Changes:
 gnuradio (3.10.7.0-2) unstable; urgency=medium
 .
   * remove old volk dependencies (Closes: #1041456)
Checksums-Sha1:
 5a6215641fffe29b14e693a05d85ce0e7b55dafd 5210 gnuradio_3.10.7.0-2.dsc
 fbcbc4946142ee454c22d25e1a033302dbef590f 37908 
gnuradio_3.10.7.0-2.debian.tar.xz
 fcf4edb423f8d8021119db779d26cf12a9ad0370 38784 
gnuradio_3.10.7.0-2_amd64.buildinfo
Checksums-Sha256:
 bcaa8983deee310ff4e1d0303611c86619fcccbcc44936b9f2ffb673bdc600bb 5210 
gnuradio_3.10.7.0-2.dsc
 d58ae07106a2dfc5601be0a20feaa507f951a9efb17cd9a1cbd0419fcb39c78e 37908 
gnuradio_3.10.7.0-2.debian.tar.xz
 15dcc276f37c092c2d1eda07c71d0904927d50733d4ea504cb0a0b62ba17c1f1 38784 
gnuradio_3.10.7.0-2_amd64.buildinfo
Files:
 77ed9c6f91236dcbbb444d9e386e200f 5210 comm optional gnuradio_3.10.7.0-2.dsc
 35d82a80596e089cddbfa9a7b8fcd89d 37908 comm optional 
gnuradio_3.10.7.0-2.debian.tar.xz
 8741ecf0a7287208d8a9a84f8716bc8a 38784 comm optional 
gnuradio_3.10.7.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmS3vfYACgkQUEHxiR9E
4JBtdA//TknzFsjNOErZBTaJZ8SZjjjHxj6QSjCcpGTAId8iLHxx7rM7652unAH+
7sRWll9fumd7dpxixli1a2aKWRdMZejCwLFAtD4KpotNCbgLTTia/x9nLd13U/3f
N+Qn009eHYDYsSPwBPPcjcLGTLWCd3OZ35NG6rsrUQpyYHOadBjKpiE+i+7AO6bg
41UNl1PyfpHccseCsPQi+tPgBQpWg48WkS/r6aBPsle2+PiQHUJleTOYnTqd3EuN
up3X+5BOZSFKG+bnQhINjRCrgG0l2J+WehdyCi/4naV09WmBf2xjVgi1tP1aN12J
BW2MLx+LWu7aWh/RShXhXIXmhDDIkqfUcpzJEVoLCKbCOyyapJVPRR/9vtpQSnu9
ajegQXVuCnHAumYroY6BwfJNNvpusMAjkgk7YaKuDBM4ycYs1r04qh/3JRpZDltg
rzfCbaiNU3EnQD46N3b8lJs40J2H+UKNBSEqHW72xBq7QlXMs6KzgP1tWX64gzti
D9UlvkO8kq2VV8z5RxZM4OBgFafPhFYyJu86b8jOA2fbxScuPDaJC55aK5lTRHaG
XkLwE9oV2VV3MvCJYrmUUOHN8+zeMMaqmAgf114d0JgBAuTU4N5Utr2oirczD2cF
FXQdYnkszb7FJ7nqvWvPDeDBqLYl+M4ShXkifVlIoS3eSHxpPR0=
=Kuuh
-END PGP SIGNATURE End Message ---

Bug#1041474: intel-gmmlib: FTBFS on i386: error: ambiguating new declaration of ‘GMM_STATUS GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()’

[Andreas Beckmann]

Source: intel-gmmlib
Version: 22.3.7+ds1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=intel-gmmlib&arch=i386&ver=22.3.7%2Bds1-1&stamp=1688230619&raw=0

[ 53%] Building CXX object 
Source/GmmLib/CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o
cd /<>/obj-i686-linux-gnu/Source/GmmLib && /usr/bin/c++ 
-DGMM_LIB_DLL -DGMM_LIB_DLL_EXPORTS -DGMM_UNIFIED_LIB -DGMM_UNIFY_DAF_API 
-DISTDLIB_UMD -DSMALL_POOL_ALLOC -DUNUSED_ISTDLIB_MT -D_ATL_NO_WIN_SUPPORT 
-D__GFX_MACRO_C__ -D__GMM -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
-D__UMD -Digfx_gmmumd_dll_EXPORTS -I/<>/Source/GmmLib 
-I/<>/Source/GmmLib/Utility/GmmLog 
-I/<>/Source/GmmLib/inc -I/<>/Source/GmmLib/Utility 
-I/<>/Source/GmmLib/GlobalInfo 
-I/<>/Source/GmmLib/Texture 
-I/<>/Source/GmmLib/Resource 
-I/<>/Source/GmmLib/Platform -I/<>/Source/util 
-I/<>/Source/inc -I/<>/Source/inc/common 
-I/<>/Source/inc/umKmInc -I/<>/Source/install -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-reorder 
-Wsign-promo -Wnon-virtual-dtor -Wno-invalid-offsetof 
-fvisibility-inlines-hidden -fno-use-cxa-atexit -fno-rtti -fexceptions 
-fcheck-new -std=c++11 -pthread -Werror=non-virtual-dtor -O3 -DNDEBUG -fPIC 
-Wall -Winit-self -Winvalid-pch -Wpointer-arith -Wno-unused 
-Wno-unknown-pragmas -Wno-comments -Wno-narrowing -Wno-overflow 
-Wno-parentheses -Wno-missing-braces -Wno-sign-compare -Wno-enum-compare 
-Werror=address -Werror=format-security -Werror=return-type -march=corei7 
-mpopcnt -msse -msse2 -msse3 -mssse3 -msse4 -msse4.1 -msse4.2 -mfpmath=sse 
-finline-functions -fno-short-enums -Wa,--noexecstack -fno-strict-aliasing 
-DUSE_MMX -DUSE_SSE -DUSE_SSE2 -DUSE_SSE3 -DUSE_SSSE3 -fstack-protector 
-fdata-sections -ffunction-sections -fmessage-length=0 -fvisibility=hidden 
-fPIC -g -m32 -funswitch-loops -Wl,--no-undefined -Wl,--no-as-needed 
-Wl,--gc-sections -O2 -fno-omit-frame-pointer -finline-limit=100 -MD -MT 
Source/GmmLib/CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o -MF 
CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o.d -o 
CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o -c 
/<>/Source/GmmLib/GlobalInfo/GmmInfo.cpp
/<>/Source/GmmLib/GlobalInfo/GmmInfo.cpp:628:24: error: 
ambiguating new declaration of ‘GMM_STATUS 
GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()’
  628 | GMM_STATUS GMM_STDCALL 
GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()
  |^~
In file included from 
/<>/Source/GmmLib/inc/External/Common/GmmInfoExt.h:25,
 from 
/<>/Source/GmmLib/inc/../Texture/GmmTexture.h:27,
 from 
/<>/Source/GmmLib/inc/Internal/Common/GmmLibInc.h:52,
 from /<>/Source/GmmLib/GlobalInfo/GmmInfo.cpp:23:
/<>/Source/GmmLib/inc/External/Common/GmmInfo.h:630:41: note: old 
declaration ‘GMM_STATUS 
GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()’
  630 | GMM_STATUS  LockMAContextSyncMutex();
  | ^~
/<>/Source/GmmLib/GlobalInfo/GmmInfo.cpp:639:24: error: 
ambiguating new declaration of ‘GMM_STATUS 
GmmLib::GmmMultiAdapterContext::UnLockMAContextSyncMutex()’
  639 | GMM_STATUS GMM_STDCALL 
GmmLib::GmmMultiAdapterContext::UnLockMAContextSyncMutex()
  |^~
/<>/Source/GmmLib/inc/External/Common/GmmInfo.h:631:41: note: old 
declaration ‘GMM_STATUS 
GmmLib::GmmMultiAdapterContext::UnLockMAContextSyncMutex()’
  631 | GMM_STATUS  UnLockMAContextSyncMutex();
  | ^~~~
make[3]: *** [Source/GmmLib/CMakeFiles/igfx_gmmumd_dll.dir/build.make:527: 
Source/GmmLib/CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o] Error 1


Andreas

Bug#1041443: [Debian-pan-maintainers] Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED

[Aurelien Jarno]

Hi,

On 2023-07-19 11:24, PICCA Frederic-Emmanuel wrote:
> ok, it seems that I generated an orig.tag.gz with this (Thu Jan  1 00:00:00 
> 1970).
> 
> I can not remember which tool I used to generate this file.
> 
> gbp import-orig --uscan
> 
> or
> 
> deb-new-upstream

I am just the messenger here, if you disagree, please feel free to
contact ftpmasters or lintian maintainers.

> Nevertheless, why is it a serious bug ?

Your package has been built successfully on (some) buildds, but then the
binaries upload got rejected by dak, that's why they are still in
"Uploaded" state. Overall it's just like if pyfai hasn't been built or
fails to build from source.

Regards
Aurelien

[1] https://buildd.debian.org/status/package.php?p=pyfai

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1041471: src:isa-support: fails to migrate to testing for too long: new autopkgtest fails on armel

[roucaries bastien]

Hi Paul,

It is a regression on qemu. I will disable the test but I will prefer
qemu fixed.

I could not reproduce on porter box, I get another qemu bug...

Who is the specialist of qemu ?

Bastien

Le mer. 19 juil. 2023 à 10:45, Paul Gevers  a écrit :
>
> Source: isa-support
> Version: 15.1
> Severity: serious
> Control: close -1 19
> Tags: sid trixie
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
> Dear maintainer(s),
>
> The Release Team considers packages that are out-of-sync between testing
> and unstable for more than 30 days as having a Release Critical bug in
> testing [1]. Your package src:isa-support has been trying to migrate for
> 31 days [2]. Hence, I am filing this bug. The version in unstable added
> an autopkgtest that segfaults on armel. (Just for your info in case it's
> relevant, the ci.debian.net armel VM's run on arm64 hardware.)
>
> If a package is out of sync between unstable and testing for a longer
> period, this usually means that bugs in the package in testing cannot be
> fixed via unstable. Additionally, blocked packages can have impact on
> other packages, which makes preparing for the release more difficult.
> Finally, it often exposes issues with the package and/or
> its (reverse-)dependencies. We expect maintainers to fix issues that
> hamper the migration of their package in a timely manner.
>
> This bug will trigger auto-removal when appropriate. As with all new
> bugs, there will be at least 30 days before the package is auto-removed.
>
> I have immediately closed this bug with the version in unstable, so if
> that version or a later version migrates, this bug will no longer affect
> testing. I have also tagged this bug to only affect sid and trixie, so
> it doesn't affect (old-)stable.
>
> If you believe your package is unable to migrate to testing due to
> issues beyond your control, don't hesitate to contact the Release Team.
>
> Paul
>
> [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
> [2] https://qa.debian.org/excuses.php?package=isa-support

Bug#1041476: systemd: keep 254-rcX out of testing

[Luca Boccassi]

Source: systemd
Version: 254~rc2-3
Severity: grave

Let's avoid having release candidates reach testing, even after
autopkgtest is happy. Apparently setting the urgency in the changelog
entry does not work anymore...

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Processed: bug 1041460 is forwarded to https://savannah.gnu.org/bugs/index.php?64446

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1041460 https://savannah.gnu.org/bugs/index.php?64446
Bug #1041460 [src:octave] octave: FTBFS on 32 bit architectures
Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/index.php?64446'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037510: marked as done (texlive-lang-japanese: dangling symlinks due to missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 11:27:58 +
with message-id 
and subject line Bug#1037510: fixed in texlive-lang 2023.20230613-1
has caused the Debian Bug report #1037510,
regarding texlive-lang-japanese: dangling symlinks due to missing dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-lang-japanese
Version: 2022.20230122-1
Severity: serious

There is a dangling symlink on my machine:
/usr/share/texlive/texmf-dist/fonts/truetype/public/ipaex/ipaexm.ttf -> 
../../../../../../fonts/opentype/ipaexfont-mincho/ipaexm.ttf

This seems to be due to a missing dependency on fonts-ipaexfont-mincho.

Since texlive-lang-japanese provides the following symlinks:

lrwxrwxrwx 1 root root 60 2023-01-24 23:31:57 ipaexg.ttf -> 
../../../../../../fonts/opentype/ipaexfont-gothic/ipaexg.ttf
lrwxrwxrwx 1 root root 60 2023-01-24 23:31:57 ipaexm.ttf -> 
../../../../../../fonts/opentype/ipaexfont-mincho/ipaexm.ttf
lrwxrwxrwx 1 root root 56 2023-01-24 23:31:57 ipag.ttf -> 
../../../../../../fonts/opentype/ipafont-gothic/ipag.ttf
lrwxrwxrwx 1 root root 57 2023-01-24 23:31:57 ipagp.ttf -> 
../../../../../../fonts/opentype/ipafont-gothic/ipagp.ttf
lrwxrwxrwx 1 root root 56 2023-01-24 23:31:57 ipam.ttf -> 
../../../../../../fonts/opentype/ipafont-mincho/ipam.ttf
lrwxrwxrwx 1 root root 57 2023-01-24 23:31:57 ipamp.ttf -> 
../../../../../../fonts/opentype/ipafont-mincho/ipamp.ttf

it should also depend on fonts-ipaexfont-gothic, fonts-ipafont-gothic
and fonts-ipafont-mincho.

-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 3539 2023-06-13 11:22:32 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 23:25:33 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2023-04-09 11:54:45 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2023-04-09 11:54:45 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2022-10-13 13:39:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2023-04-09 11:54:45 
/usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2023-04-09 11:54:45 /usr/share/texmf/web2c/updmap.cfg 
-> /var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5130 2023-05-22 11:27:35 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2015-09-03 02:24:29 mktex.cnf
-rw-r--r-- 1 root root 475 2022-10-13 13:39:43 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

--

Bug#1041443: [Debian-pan-maintainers] Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED

[PICCA Frederic-Emmanuel]

> I am just the messenger here, if you disagree, please feel free to
> contact ftpmasters or lintian maintainers.

This was not a rant about this, I just wanted to understand what is going on :).

> Your package has been built successfully on (some) buildds, but then the
> binaries upload got rejected by dak, that's why they are still in
> "Uploaded" state. Overall it's just like if pyfai hasn't been built or
> fails to build from source.

So until a new upstream source is available with other timestamp, it will not 
be uploadable.

In you opinion, can we discuss about this on debian-devel ?


Cheers

Fred

Bug#1004770: marked as done (octave-video: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 13:48:50 +0200
with message-id 
and subject line Re: Bug#1004770: FTBFS with ffmpeg 5.0
has caused the Debian Bug report #1004770,
regarding octave-video: FTBFS with ffmpeg 5.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1004770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-video
Version: 2.0.2-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

octave-video FTBFS with ffmpeg 5.0 in experimental:
| g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/octave-6.4.0/octave/.. -I/usr/include/octave-6.4.0/octave  
-pthread -fopenmp -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g  -Wall -Wdate-time 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -I/usr/include/x86_64-linux-gnu  
-DPACKAGE_NAME="Octave-Forge video package" 
-DPACKAGE_TARNAME="octave-forge-video-package" -DPACKAGE_VERSION="2.0.2" 
-DPACKAGE_STRING="Octave-Forge video package 2.0.2" -DPACKAGE_BUGREPORT="" 
-DPACKAGE_URL="" -D_FORTIFY_SOURCE=2 cap_ffmpeg_wrapper.cc -o /tmp/oct-eKTjwQ.o
| In file included from cap_ffmpeg_wrapper.cc:18:
| cap_ffmpeg_impl_ov.hpp: In member function ‘const char* 
CvCapture_FFMPEG::get_video_codec_name() const’:
| cap_ffmpeg_impl_ov.hpp:529:51: error: ‘AVStream’ {aka ‘struct AVStream’} has 
no member named ‘codec’
|   529 | return _opencv_avcodec_get_name(video_st->codec->codec_id);
|   |   ^
| cap_ffmpeg_impl_ov.hpp: In member function ‘void CvCapture_FFMPEG::init()’:
| cap_ffmpeg_impl_ov.hpp:607:5: error: ‘av_register_all’ was not declared in 
this scope
|   607 | av_register_all();
|   | ^~~
| cap_ffmpeg_impl_ov.hpp: In member function ‘void CvCapture_FFMPEG::close()’:
| cap_ffmpeg_impl_ov.hpp:655:34: error: ‘AVStream’ {aka ‘struct AVStream’} has 
no member named ‘codec’
|   655 | avcodec_close( video_st->codec );
|   |  ^
| cap_ffmpeg_impl_ov.hpp: At global scope:
| cap_ffmpeg_impl_ov.hpp:845:39: error: ‘AVLockOp’ has not been declared
|   845 | static int LockCallBack(void **mutex, AVLockOp op)
|   |   ^~~~
| cap_ffmpeg_impl_ov.hpp: In function ‘int LockCallBack(void**, int)’:
| cap_ffmpeg_impl_ov.hpp:850:14: error: ‘AV_LOCK_CREATE’ was not declared in 
this scope; did you mean ‘AV_LOG_TRACE’?
|   850 | case AV_LOCK_CREATE:
|   |  ^~
|   |  AV_LOG_TRACE
| cap_ffmpeg_impl_ov.hpp:859:14: error: ‘AV_LOCK_OBTAIN’ was not declared in 
this scope
|   859 | case AV_LOCK_OBTAIN:
|   |  ^~
| cap_ffmpeg_impl_ov.hpp:863:14: error: ‘AV_LOCK_RELEASE’ was not declared in 
this scope
|   863 | case AV_LOCK_RELEASE:
|   |  ^~~
| cap_ffmpeg_impl_ov.hpp:867:14: error: ‘AV_LOCK_DESTROY’ was not declared in 
this scope
|   867 | case AV_LOCK_DESTROY:
|   |  ^~~
| cap_ffmpeg_impl_ov.hpp: In constructor 
‘InternalFFMpegRegister::InternalFFMpegRegister()’:
| cap_ffmpeg_impl_ov.hpp:904:9: error: ‘av_register_all’ was not declared in 
this scope
|   904 | av_register_all();
|   | ^~~
| cap_ffmpeg_impl_ov.hpp:907:9: error: ‘av_lockmgr_register’ was not declared 
in this scope
|   907 | av_lockmgr_register(&LockCallBack);
|   | ^~~
| cap_ffmpeg_impl_ov.hpp: In destructor 
‘InternalFFMpegRegister::~InternalFFMpegRegister()’:
| cap_ffmpeg_impl_ov.hpp:924:9: error: ‘av_lockmgr_register’ was not declared 
in this scope
|   924 | av_lockmgr_register(NULL);
|   | ^~~
| cap_ffmpeg_impl_ov.hpp: In member function ‘bool CvCapture_FFMPEG::open(const 
char*)’:
| cap_ffmpeg_impl_ov.hpp:969:42: error: invalid conversion from ‘const 
AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
|   969 |   input_format = av_find_input_format(entry->value);
|   |  ^~
|   |  |
|   |  const AVInputFormat*
| cap_ffmpeg_impl_ov.hpp:997:47: error: ‘AVStream’ {aka ‘struct AVStream’} has 
no member named ‘codec’
|   997 | AVCodecContext *enc = ic->streams[i]->codec;
|   |   

Bug#1041478: pymca: depends on python2

[Andreas Beckmann]

Package: pymca
Version: 5.8.7+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

  The following packages have unmet dependencies:
   pymca : Depends: python2:any but it is not installable


Cheers,

Andreas

Bug#1041260: wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)

[Jeremy Bícha]

On Sun, Jul 16, 2023 at 1:33 PM Sebastian Ramacher  wrote:
 Yes, sure. But all this sounds like nobody actually tested the uploaded
> wike version. The uploads should have gone to experimental …

I believe it was tested on a system that had libadwaita from
Experimental installed. Anyway, we're uploading libadwaita-1 to
Unstable now.

Thank you,
Jeremy Bícha

Processed (with 2 errors): Re: Bug#1041260: wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1041260 src:libadwaita-1 1.2.4-1
Bug #1041260 [src:wike] wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)
Bug reassigned from package 'src:wike' to 'src:libadwaita-1'.
No longer marked as found in versions wike/2.0.1-3.
Ignoring request to alter fixed versions of bug #1041260 to the same values 
previously set
Bug #1041260 [src:libadwaita-1] wike: BD-Uninstallable: libadwaita-1-dev:amd64 
(>= 1.3)
Marked as found in versions libadwaita-1/1.2.4-1.
> affects 1041260 src:wike
Bug #1041260 [src:libadwaita-1] wike: BD-Uninstallable: libadwaita-1-dev:amd64 
(>= 1.3)
Added indication that 1041260 affects src:wike
> Thank you,
Unknown command or malformed arguments to command.
> Jeremy Bícha
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1041260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041271: marked as done (maildir-utils: public shared library shipped in maildir-utils binary package)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 12:01:08 +
with message-id 
and subject line Bug#1041271: fixed in maildir-utils 1.8.14-3
has caused the Debian Bug report #1041271,
regarding maildir-utils: public shared library shipped in maildir-utils binary 
package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maildir-utils
Version: 1.8.14-2
Severity: serious
Justification: violates policy 8.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I think that libguile-mu.* need to be either moved to a private
directory or to their own packages. I don't know enough about guile to
say which is better.

- -- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages maildir-utils depends on:
ii  guile-3.0-libs  3.0.8-2
ii  libc6   2.37-3
ii  libgcc-s1   13.1.0-6
ii  libglib2.0-02.74.6-2
ii  libgmime-3.0-0  3.2.13+dfsg-2
ii  libreadline88.2-1.3
ii  libstdc++6  13.1.0-6
ii  libxapian30 1.4.22-1

maildir-utils recommends no packages.

maildir-utils suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmS0If4ACgkQA0U5G1Wq
FSFdlw//drvAFftKxrrn1Hk+A1wYL0ATPOgwI/61u3sC4P/uQRcTbC6zfJcO/uca
GJVFWaUHIFsmPr3lwQf6KkZweBtdnm38MXsXbxw7uBH5abEKoLPZCEr0FzArfZe/
CaPFMHgCl6/k25BNigIXUcx5rgvoLCjRYrh8RVvrIN/NWfEioYDYqYs4+ZEmswP3
fMOdoqfohtXlisfKrrI/ysK00gJpI0vWYJzdEcapirDy7eMtSBXOqjUz2a3kGJ/h
Oxtg1J1GCSp/pAb3lJvAojxITQI69ZAkX2T6xGqXUhGbRCKjVUulovI0iSQGbwM4
mKDMs5oH6kn8gM9z/HTUpoxhLE85KbMQjtsTx6MoXXZKPat02ipzloc3NqWQyBDj
pL8BEpnU6Hc0MtZLI6Q+gUG1akq5BmB24pKxrcEfAVRSdFXbOjfGIHjyH6achfcn
QwOz6R5kNte4VLfCOvWXhnsDvCeiOfePC/gaVqvvzJR5/iWMovDOdBTshK9uXWkl
3hgwYqRIYRtnKobz8QcOnqTbVxFiJv8gyaOm7cbhzKGfWeMFwv38mhmJXaRj7Znv
zb8MqG2eK89v8ZkD7RxsfVVOGOU94102QwlmQ6QOuB4etVyfuUkjjnRsjJgwSRE1
TtlYcHfIj8M2EgMPWEB2mjcFb/TKlx48+Br53YNk3z6mErYJtZk=
=HGuU
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: maildir-utils
Source-Version: 1.8.14-3
Done: David Bremner 

We believe that the bug you reported is fixed in the latest version of
maildir-utils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated maildir-utils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Jul 2023 08:11:03 -0300
Source: maildir-utils
Architecture: source
Version: 1.8.14-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: David Bremner 
Closes: 1041271
Changes:
 maildir-utils (1.8.14-3) unstable; urgency=medium
 .
   * Team upload
   * Bug fix: "public shared library shipped in maildir-utils binary
 package", thanks to Jeremy Sowden (Closes: #1041271).
Checksums-Sha1:
 78ae4f46489686896faedc18b921e739d9bc 2267 maildir-utils_1.8.14-3.dsc
 dc3a7de9828bfd0455dd10af29dd2ecc7dd59677 11532 
maildir-utils_1.8.14-3.debian.tar.xz
Checksums-Sha256:
 98dd1a04408f2005dec2e1eddc04c88362941fcd8b3125eb0a4949614c08c0e4 2267 
maildir-utils_1.8.14-3.dsc
 185d3c454fb577fd9cf0a13d4ae81660d3a11e36a94bea1d8b0218583c971917 11532 
maildir-utils_1.8.14-3.debian.tar.xz
Files:
 be23ef1758163709ed192ef649904d77 2267 mail optional maildir-utils_1.8.14-3.dsc
 13915ddec83905f0f0c9d6c7c5f320fd 11532 mail optional 
maildir-utils_1.8.14-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmS3x+0ACgkQA0U5G1Wq
FSGDAA/9FCyNGGyN9cksz61W+PxSsuhBlngBTVRnlKMM9Z0u0gC+mi9AjlISn6Fe
dDaBAtUQObMMxx6KciqyPBar3Vrrl3Ig4/ZPVJobMoMGQ926eBABV7Q41Xwp4WeY
WBkWOvr6D55V1s7XH2O1k8r9nr+ByLiSDaKjVbOv6U0Z4Fr3Zi/D/GwMrzarvktm
l9mqk4ImI1zz7wLkIVD+K5H

Bug#1034433: marked as done (libsdl3-doc: missing Breaks+Replaces: libsdl1.2-dev (<< 3))

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 12:20:06 +
with message-id 
and subject line Bug#1034433: fixed in libsdl3 3~git20230719~e413457+dfsg-1
has caused the Debian Bug report #1034433,
regarding libsdl3-doc: missing Breaks+Replaces: libsdl1.2-dev (<< 3)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1034433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsdl3-doc
Version: 3~git20230412+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libsdl3-doc_3~git20230412+dfsg-2_all.deb ...
  Unpacking libsdl3-doc (3~git20230412+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libsdl3-doc_3~git20230412+dfsg-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/SDL_AddTimer.3.gz', which is also 
in package libsdl1.2-dev 1.2.15+dfsg2-8
  Errors were encountered while processing:
   /var/cache/apt/archives/libsdl3-doc_3~git20230412+dfsg-2_all.deb


cheers,

Andreas


libsdl1.2-dev=1.2.15+dfsg2-8_libsdl3-doc=3~git20230412+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libsdl3
Source-Version: 3~git20230719~e413457+dfsg-1
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
libsdl3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1034...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated libsdl3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Jul 2023 10:13:01 +0100
Source: libsdl3
Architecture: source
Version: 3~git20230719~e413457+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Simon McVittie 
Closes: 1034433
Changes:
 libsdl3 (3~git20230719~e413457+dfsg-1) experimental; urgency=medium
 .
   * New upstream snapshot prerelease-3.0.0-2002-ge413457a7
   * libsdl3-doc Breaks/Replaces older versions of libsdl1.2-dev.
 libsdl1.2-dev from src:libsdl1.2 contained man pages, some of which are
 for functions with the same name as those in libsdl3-doc. libsdl1.2-dev
 from src:sdl12-compat no longer has those. (Closes: #1034433)
   * d/watch: Add the abbreviated sha1 to the version number, to make it
 easier to keep track of which snapshot corresponds to which commit
Checksums-Sha1:
 a1640c6e91595f78e5b3583b5906eb121702fec7 3270 
libsdl3_3~git20230719~e413457+dfsg-1.dsc
 62e75662c9aab0085bded09331f527f745b6350a 4273024 
libsdl3_3~git20230719~e413457+dfsg.orig.tar.gz
 1b3c85eeac96cfb67e6eaf94862bb82211d6a73e 29872 
libsdl3_3~git20230719~e413457+dfsg-1.debian.tar.xz
 43488e20466a4b5746bb7a2bf5e7dd32b42cf7e1 11334 
libsdl3_3~git20230719~e413457+dfsg-1_source.buildinfo
Checksums-Sha256:
 fe46e0203dc4287dbb9c87432c399363fdd0bba06f4179e399aa6586f98cf80f 3270 
libsdl3_3~git20230719~e413457+dfsg-1.dsc
 310228aa76f958275d7c94652d864afde528e6ce4dd71c603f848fe45271b9fa 4273024 
libsdl3_3~git20230719~e413457+dfsg.orig.tar.gz
 6b5e2424e58e12be290c0b976ce5c6da76cd7c2d239f7ca25d1675f0e3f5e643 29872 
libsdl3_3~git20230719~e413457+dfsg-1.debian.tar.xz
 cd3f8847348ee9eaa7d9432d2d3f2aa61e383f09e596961de909c046caf11186 11334 
libsdl3_3~git20230719~e413457+dfsg-1_source.buildinfo
Files:
 f6e7c1bb5e89a2325c521af3a1c08674 3270 libs optional 
libsdl3_3~git20230719~e413457+dfsg-1.dsc
 a09a2e1313f6ec024267c56d8bf9da0f 4273024 libs optional 
libsdl3_3~git20230719~e413457+dfsg.orig.tar.gz
 0b470fe9a364dbff7d8b

Bug#1041260: marked as done (wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3))

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 12:19:49 +
with message-id 
and subject line Bug#1041260: fixed in libadwaita-1 1.3.3-2
has caused the Debian Bug report #1041260,
regarding wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wike
Version: 2.0.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/package.php?p=wike&suite=sid

Dependency installability problem for wike on amd64:

wike build-depends on missing:
- libadwaita-1-dev:amd64 (>= 1.3)


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libadwaita-1
Source-Version: 1.3.3-2
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
libadwaita-1, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated libadwaita-1 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jul 2023 07:55:29 -0400
Source: libadwaita-1
Built-For-Profiles: noudeb
Architecture: source
Version: 1.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1041260
Launchpad-Bugs-Fixed: 2023411
Changes:
 libadwaita-1 (1.3.3-2) unstable; urgency=medium
 .
   * Release to unstable (Closes: #1041260)
 .
 libadwaita-1 (1.3.3-1) experimental; urgency=medium
 .
   * New upstream release (LP: #2023411)
 .
 libadwaita-1 (1.3.2-1) experimental; urgency=medium
 .
   * New upstream release
   * autopkgtest: Run python test through xvfb, required by GTK 4.10.2
 .
 libadwaita-1 (1.3.1-1) experimental; urgency=medium
 .
   * New upstream release
   * debian/patches: Use semi-transparent icons and pictures when disabled
 .
 libadwaita-1 (1.3~rc-1) experimental; urgency=medium
 .
   * New upstream release
   * debian/control.in: Bump minimum gtk4 to 4.9.5
 .
 libadwaita-1 (1.3~beta-1) experimental; urgency=medium
 .
   * New upstream release
   * debian/control.in: Bump minimum GTK4 to 4.9.3
   * debian/libadwaita-1.0.symbols: Add new symbols
   * Revert branching for bookworm
Checksums-Sha1:
 2152f8e72593bdacce75d7bb7c1a659f59a76bd5 2687 libadwaita-1_1.3.3-2.dsc
 b2d870c01f4fdca7f49ae4ebafacb9c4b6cac48c 15408 
libadwaita-1_1.3.3-2.debian.tar.xz
 3cf0bdcd7b3611b3727599662f6e5050a024b6af 19315 
libadwaita-1_1.3.3-2_source.buildinfo
Checksums-Sha256:
 b02e5770adfe3f61058a0a1bf0b1378b43bffcecca339aea5697aaf4c7eee101 2687 
libadwaita-1_1.3.3-2.dsc
 5ac6faae790bd63eaa08fef78e7c2d24b4a6989e71456b04a59e4956752f1469 15408 
libadwaita-1_1.3.3-2.debian.tar.xz
 03a5c50e925780fc545949a300debe12764f4f167465e6adb8afed52ebcc99b4 19315 
libadwaita-1_1.3.3-2_source.buildinfo
Files:
 6d2a11feda7d6f616d5839f8bf28fd08 2687 libs optional libadwaita-1_1.3.3-2.dsc
 4339046e69005525482be5ee247e3331 15408 libs optional 
libadwaita-1_1.3.3-2.debian.tar.xz
 5216f3cf1ffed1e48ba5d8ef4e20002d 19315 libs optional 
libadwaita-1_1.3.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmS3z3gACgkQ5mx3Wuv+
bH2yRg//bvlCOQOcOrm2en4zxsmdMBm+Y8uFEjgeQKvRUc8a7FZmjt6ZF/1vsjZD
rove37Dj2/RfKYX98ghiMWUjEioxW3t3wrAoKZvvpJ0hidXA/dllmJ8FN6Lhw036
vSWbwAdtubTAueluMSTtPYdp5cqyIB3t+Z23ZX7PfHMWAdiZHiN8j/s55KiEprxQ
P9XTqt4567tNX+F7AUkOhWmG6GrPnXlgV53nRS9BiUYElziU0tq12Aw+Tu3mqiNb
FQqfZguH8Tsh+iGRd7nMkzkJEgJBba7z7ayhbdxjHLzL118BKkP4lXiRBafvqlos
TIDgvkEvO/ylW/WRyc8lmeRmYSvPby2vC99ha/Vj9utcltyow5sPuHDsjloqN9YM
e13GAbFKAUdAd4oBR5/G9w0b/yEfyoz6JrV8lbio8q/r/5LIxWJt+WRupHr7o+/v
EQkvrKUHrL4mfGSM1/qRYv/JqztNwfFuWTSAablVFmySXo9VIOYQpDphcOp5oO33
Z6Z/2R6YWgZ4/gkFzAB0CGc/+DDuFH+Ryi27dAb4QpKe/Dl2NROnLOVqc7qz5xc1
A1qgbwml2BjbuPqe+OtTRPg7eecsu6VN3N0geTqBFBdfkKv7hJDGwr2eMkI0pCZF
Jh7GgorwXhx58y6p175C+y5kVBj7kEpc+Hvgy8X/C3d738OKoIU=
=yyE+
-END PGP SIGNATURE End Message ---

Processed: Bug#1041460 marked as pending in octave

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041460 [src:octave] octave: FTBFS on 32 bit architectures
Added tag(s) pending.

-- 
1041460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041460: marked as pending in octave

[Sébastien Villemot]

Control: tag -1 pending

Hello,

Bug #1041460 in octave reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/pkg-octave-team/octave/-/commit/91bfe75f2babba0c0c37b9e2ff4083fc3c3c4b2c


Disable SPQR on 32-bit architectures

This is a (hopefully temporary) workaround for the breakage of suitesparse 7 on
those architectures.

Also add a new suitesparse7-patch2.patch.

Closes: #1041460
Gbp-Dch: Full


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041460

Bug#1041460: marked as done (octave: FTBFS on 32 bit architectures)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 13:28:47 +
with message-id 
and subject line Bug#1041460: fixed in octave 8.2.0-5
has caused the Debian Bug report #1041460,
regarding octave: FTBFS on 32 bit architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave
Version: 8.2.0-4
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=octave&arch=armel&ver=8.2.0-4&stamp=1689713418&raw=0


  libinterp/corefcn/psi.cc-tst ... pass   30/30 
 
  libinterp/corefcn/qr.cc-tst fatal: caught 
signal Segmentation fault -- stopping myself...
/bin/bash: line 1: 1484498 Segmentation fault  ( /bin/bash ../run-octave 
--no-init-file --silent --no-history -p /<>/test/mex 
/<>/test/fntests.m /<>/test )
make[6]: *** [Makefile:2882: check-local] Error 139
make[6]: Leaving directory '/<>/test'

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: octave
Source-Version: 8.2.0-5
Done: Sébastien Villemot 

We believe that the bug you reported is fixed in the latest version of
octave, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated octave package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jul 2023 14:02:56 +0200
Source: octave
Architecture: source
Version: 8.2.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Sébastien Villemot 
Closes: 1041460
Changes:
 octave (8.2.0-5) unstable; urgency=medium
 .
   * Disable SPQR on 32-bit architectures.
 This is a (hopefully temporary) workaround for the breakage of suitesparse 
7
 on those architectures.
 Also add a new suitesparse7-patch2.patch. (Closes: #1041460)
Checksums-Sha1:
 5563a843d4d4699517a749deec05be8013585005 3315 octave_8.2.0-5.dsc
 74ae43960fbb0dd7257bdbca3f0e9850abdedb60 63516 octave_8.2.0-5.debian.tar.xz
 5db05d67b8abfb3a6a68b071e5635c2ec88e582a 26960 octave_8.2.0-5_amd64.buildinfo
Checksums-Sha256:
 c73125f497ddd3eea32c0c8b89ea0c761f13d7b52a08e533412dab04be10de05 3315 
octave_8.2.0-5.dsc
 7f7b572e1054a7320477860ddc0cad322ea9e621a90cd7a6ad1020d7aa1303e3 63516 
octave_8.2.0-5.debian.tar.xz
 61df3737c48ef8271160a183cb5c7798c5755c73b0203c60aa3cc3e1621bd315 26960 
octave_8.2.0-5_amd64.buildinfo
Files:
 dfa1a961968a4a022fa5806bab943600 3315 math optional octave_8.2.0-5.dsc
 b1568cccee4cfe2e3c52f5f59403437d 63516 math optional 
octave_8.2.0-5.debian.tar.xz
 bebac7d859ba5af50f845225d29467fc 26960 math optional 
octave_8.2.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmS335gACgkQLOzpNQ7O
vkphtw/8D9eS3amYY52uGwVet5MrUlFmlhSMsU9yIzaIeJuWsv/kBHBFcmh4LPIm
ss2CzrenzlLaBh5zcdnjLXnl4rvk8DYLloHrQrKfIpNpwZgWGmf+jxvfGqwtOJdm
JQ3/EYkrw6ePtGt39+d2Ez32gAZ9xR2+u28ELJ5RRCMFv3kTXzpVpNzqe0bc3JBl
IVnCVMvc2eJIVloAm6X3sz4E345gJgnM3qpvaBSLfsXP13BChaz1mJ3YDV1zgLUT
TmuSjwhuBk0iYKdnD7Q514iMv0a/B2KbbjSpqqC6WemjDXjBq8xB0NOZCOXlCmtY
nr0RIaOXKZgzn7ViNwoEEj9/FDT7YPYLyx4eTbCspWJooJU/C0qmcowvC9imgurV
HLohaRnTuAgB4voLCb+IhiUCSmuJ3KGeEWUxVDjdMJgopqgjqCjzlf07h4ZHjQKt
MippytJ2KUJtCJUL7H7C3ncKyxW/3ihsNiPEZTNt2Ntiv5JQpiCJDMGUS/D2GUzK
R9uNOly5vWhUwvmJ2ZevGhTDj731T1U+Q9hzwVxT1qSMUxioIec2iZOuO/ZW6yCN
nZSYn3/E2zRei8PwcrAjbAv5DpQGvIKieL7S096rAaKSnrrFVSgTbl0brtwgi9c8
PqY8LQHwxxF4p5fGgaThBH0WXQPr3rM/ZyvkJ+nljXIx4cZigsc=
=2LKO
-END PGP SIGNATURE End Message ---

Bug#1041080: marked as done (deepin-calculator FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 13:51:12 +
with message-id 
and subject line Bug#1041080: fixed in deepin-calculator 5.7.21-2
has caused the Debian Bug report #1041080,
regarding deepin-calculator FTBFS with googletest 1.13.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-calculator
Version: 5.7.21-1
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/deepin-calculator.html

...
In file included from /usr/include/gtest/gtest-message.h:57,
 from /usr/include/gtest/gtest-assertion-result.h:46,
 from /usr/include/gtest/gtest.h:64,
 from 
/build/1st/deepin-calculator-5.7.21/tests/src/control/ut_basickeypad.h:4,
 from 
/build/1st/deepin-calculator-5.7.21/tests/src/control/ut_basickeypad.cpp:1:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less 
than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


This can be fixed by setting CMAKE_CXX_STANDARD to 14
in both CMakeLists.txt and tests/CMakeLists.txt
--- End Message ---
--- Begin Message ---
Source: deepin-calculator
Source-Version: 5.7.21-2
Done: Nisha Pariyar 

We believe that the bug you reported is fixed in the latest version of
deepin-calculator, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nisha Pariyar  (supplier of updated deepin-calculator 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jul 2023 00:58:39 +0545
Source: deepin-calculator
Architecture: source
Version: 5.7.21-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Nisha Pariyar 
Closes: 1041080
Changes:
 deepin-calculator (5.7.21-2) unstable; urgency=medium
 .
   * debian/patches: Fix ftbfs by removing
 explicit cxx11. (Closes: #1041080)
   * debian/control:
 + Bump standard version to 4.6.2.
 + Add myself to uploaders list.
Checksums-Sha1:
 af09fd31838629804eb14571e2aca8c52c650d97 2457 deepin-calculator_5.7.21-2.dsc
 0531c66f6afc36eae67c6ea98929185e212d3585 4992 
deepin-calculator_5.7.21-2.debian.tar.xz
 134d72818e91aaca282146fe82c2769f0d3d453e 14386 
deepin-calculator_5.7.21-2_amd64.buildinfo
Checksums-Sha256:
 2265b64632fc9d18ffb4a3f8d3daf752ad3b1dfdae9dfd65b9e27e876afc7674 2457 
deepin-calculator_5.7.21-2.dsc
 3f90d62760ef0456a1585935944a3a9eb74630469e1e31097d487af3626f60f8 4992 
deepin-calculator_5.7.21-2.debian.tar.xz
 2fb85731738b96db4bb4cf003710cc3630fa26eb2b41a6012c20cad234fe80bc 14386 
deepin-calculator_5.7.21-2_amd64.buildinfo
Files:
 44c0411f6ea7f66f52c457fd7b9afbd8 2457 math optional 
deepin-calculator_5.7.21-2.dsc
 9faf941ce198d9def47b278b0b0823fb 4992 math optional 
deepin-calculator_5.7.21-2.debian.tar.xz
 2db668cb7f08e4bc821d3c451b408309 14386 math optional 
deepin-calculator_5.7.21-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2lMFjb4VS9/L8WutS1Qq9wT3RRYFAmS35SQACgkQS1Qq9wT3
RRbCcxAApRfauKqVY49EFQXqynjs4/afqGhTMcyftkr9K/yCCBCF8UyN8jfhIxhV
/4ky8NdmmDcqfyXWMah9kjtn6qN4O7czAM/FFM0A1AI3Cl58CvdUu+P8dY+2e/wE
Ty3UreSPWZsYhOQajw6zaI0an+oZRMLbEV241qFx4FNBEKXMOjfc4fu0PAzWLRMU
u3YrSyG+4SmlfUMyGtL9QFxppQmknQqgnqSzZXha7Rq7uINH5CKaMX0i07/8rh0q
v9e5gMJoYu5bDKn14QTH65VTneSxxWE+9XXmw+MW+gOczGRH1y0hMaSuK/+d3rJ4
eiJCRfj8w6eJaN45AlazSCu2rgfY2RZSeRltYwLLOCExHc4GAct3a6lznBdVHdlj
svaaGRy273pxyi5UIN4g6fWHLbUwCXIdoTwQ7heNkj4cY0oHjEUKio+KyGg4Tedv
akn++s/nXteEj6HILX4b0uoiNsa6DxV9+zHzFiQYx0gwQmhBynWswxtZ9tSt/hiU
E72cF9QRiDvtM2q62eKUlYBL3O5KpVCffZN4QGlnfR7rrJ4QVqWVTuNsoCAuiVhe
po6wfEdJTo1W5i0XUYCnJkCVYvdQJnO7xteVf+/n4re+WTdFnlmrtI2A3cB/jo0G
vxx8T2g6gupDmZsaIZm0jZIiCkj4mtT9ElK0Rqk6U0Cdkt/GgLo=
=aKKF
-END PGP SIGNATURE End Message ---

Bug#1039642: marked as done (r-cran-arsenal: autopkgtest failure with r-base (4.3.1-1))

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 13:53:33 +
with message-id 
and subject line Bug#1039642: fixed in r-cran-arsenal 3.6.3-2
has caused the Debian Bug report #1039642,
regarding r-cran-arsenal: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1039642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-arsenal
Version: 3.6.3-1
Severity: serious
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with r-base (4.3.1-1):

 48s [ FAIL 6 | WARN 0 | SKIP 12 | PASS 471 ]
 48s 
 48s ══ Skipped tests 
═══
 48s • On CRAN (12)
 48s 
 48s ══ Failed tests 

 48s ── Failure ('test_modelsum.R:125'): offset() works 
─
 48s `summary(...)` threw an error.
 48s Message: DLL requires the use of native symbols
 48s Class:   simpleError/error/condition
 48s Backtrace:
 48s  ▆
 48s   1. ├─testthat::expect_error(...) at test_modelsum.R:125:2
 48s   2. │ └─testthat:::quasi_capture(...)
 48s   3. │   ├─testthat (local) .capture(...)
 48s   4. │   │ └─base::withCallingHandlers(...)
 48s   5. │   └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
 48s   6. ├─base::summary(...)
 48s   7. └─arsenal::modelsum(...)
 48s   8.   └─arsenal:::modelsum_guts(...)
 48s   9. ├─base::`[<-`(`*tmp*`, coeffRRTidy$term == "Intercept", -1, value 
= ``)
 48s  10. └─tibble:::`[<-.tbl_df`(...)
 48s  11.   └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg, 
substitute(value))
 48s  12. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
 48s  13.   ├─base::withCallingHandlers(...)
 48s  14.   └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
 48s ── Error ('test_modelsum.R:240'): ordinal works 

 48s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the 
use of native symbols
 48s Backtrace:
 48s  ▆
 48s   1. ├─testthat::expect_identical(...) at test_modelsum.R:240:4
 48s   2. │ └─testthat::quasi_label(enquo(object), label, arg = "object")
 48s   3. │   └─rlang::eval_bare(expr, quo_get_env(quo))
 48s   4. ├─arsenal:::capture.kable(...)
 48s   5. │ └─utils::capture.output(x) at tests/testthat/helper-script.R:4:2
 48s   6. │   └─base::withVisible(...elt(i))
 48s   7. ├─base::summary(...)
 48s   8. └─arsenal::modelsum(...)
 48s   9.   └─arsenal:::modelsum_guts(...)
 48s  10. ├─base::`[<-`(...)
 48s  11. └─tibble:::`[<-.tbl_df`(...)
 48s  12.   └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg, 
substitute(value))
 48s  13. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
 48s  14.   ├─base::withCallingHandlers(...)
 48s  15.   └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
 48s ── Error ('test_modelsum.R:286'): negbin works 
─
 48s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the 
use of native symbols
 48s Backtrace:
 48s  ▆
 48s   1. ├─testthat::expect_identical(...) at test_modelsum.R:286:4
 48s   2. │ └─testthat::quasi_label(enquo(object), label, arg = "object")
 48s   3. │   └─rlang::eval_bare(expr, quo_get_env(quo))
 48s   4. ├─arsenal:::capture.kable(...)
 48s   5. │ └─utils::capture.output(x) at tests/testthat/helper-script.R:4:2
 48s   6. │   └─base::withVisible(...elt(i))
 48s   7. ├─base::summary(...)
 48s   8. └─arsenal::modelsum(...)
 48s   9.   └─arsenal:::modelsum_guts(...)
 48s  10. ├─base::`[<-`(`*tmp*`, coeffRRTidy$term == "Intercept", -1, value 
= ``)
 48s  11. └─tibble:::`[<-.tbl_df`(...)
 48s  12.   └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg, 
substitute(value))
 48s  13. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
 48s  14.   ├─base::withCallingHandlers(...)
 48s  15.   └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
 48s ── Error ('test_modelsum.R:386'): 08/01/2017: Beth Atkinson's subset 
problem ───
 48s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the 
use of native symbols
 48s Backtrace:
 48s  ▆
 48s   1. ├─testthat::expect_identical(...) at test_modelsum.R:386:2
 48s   2. │ └─testthat::quasi_label(enquo(object), label, arg = "object")
 48s   3. │   └─rlang::eval_bare(expr, quo_get_env(quo))
 48s   4. ├─arsenal:::capture.kable(...)
 48s   5. │ └─utils::capture.outp

Bug#1039643: marked as done (r-cran-av: autopkgtest failure with r-base (4.3.1-1))

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 13:53:40 +
with message-id 
and subject line Bug#1039643: fixed in r-cran-av 0.8.3+dfsg-2
has caused the Debian Bug report #1039643,
regarding r-cran-av: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1039643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-av
Version: 0.8.3+dfsg-1
Severity: serious
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with r-base (4.3.1-1):

 58s [ FAIL 4 | WARN 0 | SKIP 0 | PASS 0 ]
 58s 
 58s ══ Failed tests 

 58s ── Error ('test-audio.R:5'): (code run outside of `test_that()`) 
───
 58s Error in `not_null(.Call("psll_connections", p))`: DLL requires the use of 
native symbols
 58s Backtrace:
 58s  ▆
 58s   1. └─testthat::test_that(...) at test-audio.R:5:0
 58s   2.   └─testthat:::test_code(desc, code, env = parent.frame(), reporter = 
reporter)
 58s   3. └─reporter$start_test(context = reporter$.context, test = test)
 58s   4.   └─testthat:::o_apply(self$reporters, "start_test", context, 
test)
 58s   5. └─base::lapply(objects, f)
 58s   6.   └─testthat (local) FUN(X[[i]], ...)
 58s   7. └─x$start_test(...)
 58s   8.   └─ps::ps_connections(ps_handle())
 58s   9. └─ps:::psl_connections(p)
 58s  10.   └─ps:::not_null(.Call("psll_connections", p))
 58s ── Error ('test-fft.R:5'): (code run outside of `test_that()`) 
─
 58s Error in `not_null(.Call("psll_connections", p))`: DLL requires the use of 
native symbols
 58s Backtrace:
 58s  ▆
 58s   1. └─testthat::test_that(...) at test-fft.R:5:0
 58s   2.   └─testthat:::test_code(desc, code, env = parent.frame(), reporter = 
reporter)
 58s   3. └─reporter$start_test(context = reporter$.context, test = test)
 58s   4.   └─testthat:::o_apply(self$reporters, "start_test", context, 
test)
 58s   5. └─base::lapply(objects, f)
 58s   6.   └─testthat (local) FUN(X[[i]], ...)
 58s   7. └─x$start_test(...)
 58s   8.   └─ps::ps_connections(ps_handle())
 58s   9. └─ps:::psl_connections(p)
 58s  10.   └─ps:::not_null(.Call("psll_connections", p))
 58s ── Error ('test-formats.R:3'): (code run outside of `test_that()`) 
─
 58s Error in `not_null(.Call("psll_connections", p))`: DLL requires the use of 
native symbols
 58s Backtrace:
 58s  ▆
 58s   1. └─testthat::test_that(...) at test-formats.R:3:0
 58s   2.   └─testthat:::test_code(desc, code, env = parent.frame(), reporter = 
reporter)
 58s   3. └─reporter$start_test(context = reporter$.context, test = test)
 58s   4.   └─testthat:::o_apply(self$reporters, "start_test", context, 
test)
 58s   5. └─base::lapply(objects, f)
 58s   6.   └─testthat (local) FUN(X[[i]], ...)
 58s   7. └─x$start_test(...)
 58s   8.   └─ps::ps_connections(ps_handle())
 58s   9. └─ps:::psl_connections(p)
 58s  10.   └─ps:::not_null(.Call("psll_connections", p))
 58s ── Error ('test-video.R:3'): (code run outside of `test_that()`) 
───
 58s Error in `not_null(.Call("psll_connections", p))`: DLL requires the use of 
native symbols
 58s Backtrace:
 58s  ▆
 58s   1. └─testthat::test_that(...) at test-video.R:3:0
 58s   2.   └─testthat:::test_code(desc, code, env = parent.frame(), reporter = 
reporter)
 58s   3. └─reporter$start_test(context = reporter$.context, test = test)
 58s   4.   └─testthat:::o_apply(self$reporters, "start_test", context, 
test)
 58s   5. └─base::lapply(objects, f)
 58s   6.   └─testthat (local) FUN(X[[i]], ...)
 58s   7. └─x$start_test(...)
 58s   8.   └─ps::ps_connections(ps_handle())
 58s   9. └─ps:::psl_connections(p)
 58s  10.   └─ps:::not_null(.Call("psll_connections", p))
 58s 
 58s [ FAIL 4 | WARN 0 | SKIP 0 | PASS 0 ]

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-av/34918107/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-av
Source-Version: 0.8.3+dfsg-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
r-cran-av, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you f

Bug#1037577: antpm: 1.21-1 to fix ftbfs with GCC-13

[Ralovich Kristóf]

Version 1.21-1 is supposed to fix the gcc 13 build failure. Could someone 
please upload it from master/HEAD of https://salsa.debian.org/debian/antpm ?

Thank you,
Kristof

Bug#1037538: marked as done (gerbera: FTBFS with libupnp17)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 15:10:11 +
with message-id 
and subject line Bug#1037538: fixed in gerbera 1.12.1+dfsg-0.1
has caused the Debian Bug report #1037538,
regarding gerbera: FTBFS with libupnp17
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gerbera
Version: 1.1.0+dfsg-3.1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=gerbera&arch=amd64&ver=1.1.0%2Bdfsg-3.1%2Bb2&stamp=1686649192&raw=0

-- Found LFS: TRUE  
CMake Warning (dev) at 
/usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (UPnP) does
  not match the name of the calling package (LibUpnp).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindLibUpnp.cmake:39 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:372 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found UPnP: /usr/lib/x86_64-linux-gnu/libupnp.so (found version "17.1.8") 
CMake Error at CMakeLists.txt:389 (message):
  

  !! You are using a very old 1.8 snapshot.  Please upgrade to a 1.8.x
  release from upstream (https://github.com/mrjimenez/pupnp) !!



-- Configuring incomplete, errors occurred!

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gerbera
Source-Version: 1.12.1+dfsg-0.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
gerbera, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1037...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated gerbera package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Jul 2023 21:28:33 +0200
Source: gerbera
Binary: gerbera gerbera-dbgsym gerbera-doc
Architecture: source amd64 all
Version: 1.12.1+dfsg-0.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Bastian Germann 
Description:
 gerbera- UPnP MediaServer
 gerbera-doc - UPnP MediaServer - documentation
Closes: 925465 960927 1037538 1037675
Changes:
 gerbera (1.12.1+dfsg-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * New upstream version 1.12.1 (Closes: #1037538, #1037675, #960927, #925465)
   * d/watch: Scan new official GitHub repo
   * Add new build dependencies
   * Remove min build dependency versions
   * Update runtime dependencies
   * Fix lintian: unused-override
   * d/copyright: Drop non-existing files
   * d/copyright: Add new info
 .
   [ James Cowgill ]
   * Use debhelper compat 13
   * Set Rules-Requires-Root: no
   * Install all files within gerbera.install
   * Add gerbera-doc package and install sphinx documentation
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
Checksums-Sha1:
 3d5a8e2c37efbc2335a10d3de19ad2db98ad6aa9 2250 gerbera_1.12.1+dfsg-0.1.dsc
 5ff30ff038cf3153be216f8dc98794c8f0183a0f 2642788 
gerbera_1.12.1+dfsg.orig.tar.xz
 ea43bbe56f749fcde39a054f0afb7bf8de2ab934 18132 
gerbera_1.12.1+dfsg-0.1.debian.tar.xz
 9487c0167b5388f9203b6dbcfc91d14f0292fbe2 48943828 
gerbera-dbgsym_1.12.1+dfsg-0.1_amd64.deb
 3f70485c351eb470cd54f37443bd60da26f1f54f 2004468 
gerbera-doc_1.12.1+dfsg-0.1_all.deb
 40277313a5e9f67f8d1e6e4ed3810bbacd660f8e 13931 
gerbera_1.12.1+dfsg-0.1_amd64.buildinfo
 66ac18f6039b216e8a0e75257521ececa52d60aa 1406544 
gerbera_1.12.1+dfsg-0.1_amd64.deb
Checksums-Sha256:
 13cde682e1dd7230a200e38bed61776803e41b3b4ab27b843270602e5791ee44 2250 
gerbera_1.12.1+dfsg-0.1.dsc
 062fd1954d4e3794bec4ddc145bc5692feec35541c6f867caa280038374a45e5 2642788 
gerbera_1.12.1+dfsg.orig.tar.xz
 e8a549fa090b86eab8d6c480cc2

Bug#1037675: marked as done (gerbera: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 15:10:11 +
with message-id 
and subject line Bug#1037675: fixed in gerbera 1.12.1+dfsg-0.1
has caused the Debian Bug report #1037675,
regarding gerbera: ftbfs with GCC-13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gerbera
Version: 1.1.0+dfsg-3.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/gerbera_1.1.0+dfsg-3.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

[...]
  |  ^~
  |  exp
/<>/src/autoscan_inotify.cc: In member function ‘int 
AutoscanInotify::monitorDirectory(zmm::String, zmm::Ref, 
zmm::String, bool, zmm::Ref >)’:
/<>/src/autoscan_inotify.cc:532:24: error: ISO C++ forbids 
declaration of ‘out_of_range’ with no type [-fpermissive]
  532 | } catch (const out_of_range& ex) {
  |^~~~
/<>/src/autoscan_inotify.cc:532:36: error: expected ‘)’ before ‘&’ 
token
  532 | } catch (const out_of_range& ex) {
  | ~  ^
  |)
/<>/src/autoscan_inotify.cc:532:36: error: expected ‘{’ before ‘&’ 
token
/<>/src/autoscan_inotify.cc:532:38: error: ‘ex’ was not declared 
in this scope; did you mean ‘exp’?
  532 | } catch (const out_of_range& ex) {
  |  ^~
  |  exp
[ 11%] Building C object CMakeFiles/libgerbera.dir/src/contrib/md5.c.o
/usr/bin/cc -DAUTO_CREATE_DATABASE -DEXTEND_PROTOCOLINFO -DEXTERNAL_TRANSCODING 
-DHAVE_AVSTREAM_CODECPAR -DHAVE_CURL -DHAVE_EXIV2 -DHAVE_FFMPEG 
-DHAVE_FFMPEGTHUMBNAILER -DHAVE_INOTIFY -DHAVE_JS -DHAVE_LIBEXIF -DHAVE_MAGIC 
-DHAVE_MYSQL -DHAVE_NL_LANGINFO -DHAVE_SETLOCALE -DHAVE_SQLITE3 -DHAVE_TAGLIB 
-DONLINE_SERVICES -DPACKAGE_DATADIR=\"/usr/share/gerbera\" 
-DPACKAGE_NAME=\"gerbera\" -DTOMBDEBUG -DVERSION=\"1.1.0\" -DYOUTUBE 
-D__FILENAME__=\"src/contrib/md5.c\" -I/<>/src -I/usr/include/upnp 
-I/usr/include/mysql -I/usr/include/libexif -I/usr/include/exiv2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT 
CMakeFiles/libgerbera.dir/src/contrib/md5.c.o -MF 
CMakeFiles/libgerbera.dir/src/contrib/md5.c.o.d -o 
CMakeFiles/libgerbera.dir/src/contrib/md5.c.o -c 
/<>/src/contrib/md5.c
/<>/src/autoscan_inotify.cc: In member function ‘void 
AutoscanInotify::removeWatchMoves(int)’:
/<>/src/autoscan_inotify.cc:654:24: error: ISO C++ forbids 
declaration of ‘out_of_range’ with no type [-fpermissive]
  654 | } catch (const out_of_range& ex) {
  |^~~~
/<>/src/autoscan_inotify.cc:654:36: error: expected ‘)’ before ‘&’ 
token
  654 | } catch (const out_of_range& ex) {
  | ~  ^
  |)
/<>/src/autoscan_inotify.cc:654:36: error: expected ‘{’ before ‘&’ 
token
/<>/src/autoscan_inotify.cc:654:38: error: ‘ex’ was not declared 
in this scope; did you mean ‘exp’?
  654 | } catch (const out_of_range& ex) {
  |  ^~
  |  exp
/<>/src/autoscan_inotify.cc: In member function ‘void 
AutoscanInotify::addDescendant(int, int, zmm::Ref)’:

Processed: block 1041459 with 1040694

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 1041459 with 1040694
Bug #1041459 [src:openturns] openturns: FTBFS everwhere
1041459 was not blocked by any bugs.
1041459 was not blocking any bugs.
Added blocking bug(s) of 1041459: 1040694
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041459: marked as done (openturns: FTBFS everwhere)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 17:57:19 +0200
with message-id <9eb0dced-1afa-e84c-a2f1-99e378096...@debian.org>
and subject line openturns now builds correctly
has caused the Debian Bug report #1041459,
regarding openturns: FTBFS everwhere
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openturns
Version: 1.20-9
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=openturns&arch=amd64&ver=1.20-9%2Bb1&stamp=1689716922&raw=0

The following tests FAILED:
103 - cppcheck_Bonmin_std (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/<>/builddir'

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

Version: 1.20-9

Hi,

This was due to an unadvertised ABI break in coinoc-cbc: a rebuild of 
coinor-bonmin is needed, which will be done during an upcoming library 
transition.


For now, coinoc-cbc has been restored to its previous version and 
openturns can be built wherever it built before.


Cheers,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Processed: notfound 1041459 in 1.20-9

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 1041459 1.20-9
Bug #1041459 {Done: Pierre Gruet } [src:openturns] openturns: 
FTBFS everwhere
No longer marked as found in versions openturns/1.20-9.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041443: [Debian-pan-maintainers] Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED

[Aurelien Jarno]

On 2023-07-19 13:38, PICCA Frederic-Emmanuel wrote:
> > I am just the messenger here, if you disagree, please feel free to
> > contact ftpmasters or lintian maintainers.
> 
> This was not a rant about this, I just wanted to understand what is going on 
> :).
> 
> > Your package has been built successfully on (some) buildds, but then the
> > binaries upload got rejected by dak, that's why they are still in
> > "Uploaded" state. Overall it's just like if pyfai hasn't been built or
> > fails to build from source.
> 
> So until a new upstream source is available with other timestamp, it will not 
> be uploadable.

The problem is not in the upstream source tarball (the source got
accepted), but rather in the binary packages produced during the build.
The debian/rules file can somehow change the timestamp after copying the
file into the debian/tmp hierarchy.

> In you opinion, can we discuss about this on debian-devel ?
> 

Yes, I don't see why it couldn't be discussed there.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1041491: yuzu: FTBFS: Unmet build dependencies: glslang-tools:native

[Sebastian Ramacher]

Source: yuzu
Version: 0-1335+ds-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=yuzu&arch=amd64&ver=0-1335%2Bds-1%2Bb1&stamp=1689519069&raw=0

dpkg-buildpackage: info: host architecture amd64
dpkg-checkbuilddeps: error: Unmet build dependencies: glslang-tools:native
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting

Cheers
-- 
Sebastian Ramacher

Bug#1037828: marked as done (qt6-webengine: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 17:38:36 +
with message-id 
and subject line Bug#1037828: fixed in qt6-webengine 6.4.2-final+dfsg-6
has caused the Debian Bug report #1037828,
regarding qt6-webengine: ftbfs with GCC-13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qt6-webengine
Version: 6.4.2-final+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/qt6-webengine_6.4.2-final+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

[...]
  |  ^~~
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:1023:59:
 error: ‘absl::str_format_internal::FormatConversionCharIsUpper’ cannot be used 
as a function
 1023 | FormatConversionCharIsUpper(conv.conversion_char()) ? "NAN" : 
"nan", 3,
  |   ^
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:1027:42:
 error: ‘const class absl::str_format_internal::FormatConversionSpecImpl’ has 
no member named ‘conversion_char’
 1027 | FormatConversionCharIsUpper(conv.conversion_char()) ? "INF" : 
"inf", 3,
  |  ^~~
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:1027:59:
 error: ‘absl::str_format_internal::FormatConversionCharIsUpper’ cannot be used 
as a function
 1027 | FormatConversionCharIsUpper(conv.conversion_char()) ? "INF" : 
"inf", 3,
  |   ^
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:
 In function ‘bool absl::str_format_internal::{anonymous}::FloatToSink(Float, 
const absl::str_format_internal::FormatConversionSpecImpl&, 
absl::str_format_internal::FormatSinkImpl*)’:
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:1332:3:
 error: ‘FormatConversionChar’ was not declared in this scope; did you mean 
‘ToFormatConversionCharSet’?
 1332 |   FormatConversionChar c = conv.conversion_char();
  |   ^~~~
  |   ToFormatConversionCharSet
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:1334:7:
 error: ‘c’ was not declared in this scope
 1334 |   if (c == FormatConversionCharInternal::f ||
  |   ^
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:1334:42:
 error: ‘f’ is not a member of 
‘absl::str_format_internal::FormatConversionCharInternal’
 1334 |   if (c == FormatConversionCharInternal::f ||
  |  ^
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:1335:42:
 error: ‘F’ is not a member of 
‘absl::str_format_internal::FormatConversionCharInternal’
 1335 |   c == FormatConversionCharInternal::F) {
  |  ^
../../../../../src/3rdparty/chromium/third_party/abseil-cpp/absl/strings/internal/str_format/float_conversion.cc:1339:49:
 error: ‘e’ is not a 

Bug#1041497: vmm: fails to run with python3 >= 3.10

[Bernd Zeimetz]

Package: vmm
Version: 0.7.0-0.1
Severity: grave
X-Debbugs-Cc: b...@debian.org

Hi Bastian,

uploading a broken 0.1 version and keeping the maintainer who actually
orphaned the package intact is probably not the best way, I would
suggest that you either adopt the package or at least set the QA Group
as maintainer.

# vmm ld
Traceback (most recent call last):
  File "/usr/sbin/vmm", line 18, in 
sys.exit(run(sys.argv))
 ^
  File "/usr/lib/python3/dist-packages/VirtualMailManager/cli/main.py", line 
43, in run
handler = _get_handler()
  ^^
  File "/usr/lib/python3/dist-packages/VirtualMailManager/cli/main.py", line 
27, in _get_handler
handler = CliHandler()
  
  File "/usr/lib/python3/dist-packages/VirtualMailManager/cli/handler.py", line 
44, in __init__
super(CliHandler, self).__init__(skip_some_checks)
  File "/usr/lib/python3/dist-packages/VirtualMailManager/handler.py", line 87, 
in __init__
self._cfg = Cfg(self._cfg_fname)

  File "/usr/lib/python3/dist-packages/VirtualMailManager/config.py", line 292, 
in __init__
LazyConfig.__init__(self)
  File "/usr/lib/python3/dist-packages/VirtualMailManager/config.py", line 73, 
in __init__
'optionname': LazyConfigOption(int, 1, self.getint),
  ^
  File "/usr/lib/python3/dist-packages/VirtualMailManager/config.py", line 251, 
in __init__
if not isinstance(getter, collections.Callable):
  
AttributeError: module 'collections' has no attribute 'Callable'


collections.Callable is collections.abs.Callable since Python 3.10 



Cheers,

Bernd

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Processed: meson: glib2.0 FTBFS on mips64el: "native build" but then "Can not run test applications in this cross environment"

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:glib2.0
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Added indication that 1041499 affects src:glib2.0

-- 
1041499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041499: meson: glib2.0 FTBFS on mips64el: "native build" but then "Can not run test applications in this cross environment"

[Simon McVittie]

Package: meson
Version: 1.2.0-1
Severity: serious
Tags: ftbfs
Justification: causing FTBFS regression in another package
X-Debbugs-Cc: glib...@packages.debian.org
Control: affects -1 + src:glib2.0

glib2.0's meson.build has several calls to 'cc.run(...)' guarded by
a check for 'cc_can_run = meson.can_run_host_binaries()'.

On mips64el, Meson seems confused about whether this is a native or
cross build. At first, it correctly reports that this is a native build:


> The Meson build system
> Version: 1.2.0
> Source dir: /<>
> Build dir: /<>/debian/build/deb
> Build type: native build
> Project name: glib
> Project version: 2.76.4

but then later, cc.run() fails:

> ../../../meson.build:1127:14: ERROR: Can not run test applications in this 
> cross environment.

(Line 1127 is the first call to cc.run().)

With a minimal reproducer:

project('foo', 'c')
if meson.can_run_host_binaries()
meson.get_compiler('c').run('whatever')
endif

I can run `meson setup _build` successfully on amd64, or on the mips64el
porterbox eller in a trixie_mips64el-dchroot session with meson 1.1.1-2,
but not on eller in a sid_mips64el-dchroot session with meson 1.2.0-1.

I attach meson-log.txt from the minimal reproducer failing in
sid_mips64el-dchroot. It correctly reports

> Is cross compiler: False.

and

> Build machine cpu family: mips64
> Build machine cpu: mips64
> Host machine cpu family: mips64
> Host machine cpu: mips64
> Target machine cpu family: mips64
> Target machine cpu: mips64

as I would expect.

Thanks,
smcv
Build started at 2023-07-19T19:02:54.288530
Main binary: /usr/bin/python3
Build Options: 
Python system: Linux
The Meson build system
Version: 1.2.0
Source dir: /home/smcv
Build dir: /home/smcv/_build
Build type: native build
Project name: foo
Project version: undefined
---
Detecting compiler via: `cc --version` -> 0
stdout:
cc (Debian 13.1.0-7) 13.1.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
---
Running command: cc -E -dM -
-
---
Detecting linker via: `cc -Wl,--version` -> 0
stdout:
GNU ld (GNU Binutils for Debian) 2.40.90.20230714
Copyright (C) 2023 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.
---
stderr:
collect2 version 13.1.0
/usr/bin/ld -plugin 
/usr/libexec/gcc/mips64el-linux-gnuabi64/13/liblto_plugin.so 
-plugin-opt=/usr/libexec/gcc/mips64el-linux-gnuabi64/13/lto-wrapper 
-plugin-opt=-fresolution=/tmp/cc9MBOmq.res -plugin-opt=-pass-through=-lgcc 
-plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc 
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id 
--eh-frame-hdr -EL -mips64r2 --as-needed -dynamic-linker /lib64/ld.so.1 
-melf64ltsmip -pie 
/usr/lib/gcc/mips64el-linux-gnuabi64/13/../../../mips64el-linux-gnuabi64/Scrt1.o
 
/usr/lib/gcc/mips64el-linux-gnuabi64/13/../../../mips64el-linux-gnuabi64/crti.o 
/usr/lib/gcc/mips64el-linux-gnuabi64/13/crtbeginS.o 
-L/usr/lib/gcc/mips64el-linux-gnuabi64/13 
-L/usr/lib/gcc/mips64el-linux-gnuabi64/13/../../../mips64el-linux-gnuabi64 
-L/usr/lib/gcc/mips64el-linux-gnuabi64/13/../../../../lib 
-L/lib/mips64el-linux-gnuabi64 -L/lib/../lib -L/usr/lib/mips64el-linux-gnuabi64 
-L/usr/lib/../lib -L/usr/lib/gcc/mips64el-linux-gnuabi64/13/../../.. --version 
-lgcc --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state 
--as-needed -lgcc_s --pop-state 
/usr/lib/gcc/mips64el-linux-gnuabi64/13/crtendS.o 
/usr/lib/gcc/mips64el-linux-gnuabi64/13/../../../mips64el-linux-gnuabi64/crtn.o
---
Sanity testing C compiler: ccache cc
Is cross compiler: False.
Sanity check compiler command line: ccache cc sanitycheckc.c -o 
sanitycheckc.exe -D_FILE_OFFSET_BITS=64
Sanity check compile stdout:

-
Sanity check compile stderr:

-
Running test binary command:  /home/smcv/_build/meson-private/sanitycheckc.exe
C compiler for the host machine: ccache cc (gcc 13.1.0 "cc (Debian 13.1.0-7) 
13.1.0")
C linker for the host machine: cc ld.bfd 2.40.90.20230714
---
Detecting linker via: `gcc-ar --version` -> 0
stdout:
GNU ar (GNU Binutils for Debian) 2.40.90.20230714
Copyright (C) 2023 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.
---
---
Detecting compiler via: `cc --version` -> 0
stdout:
cc (Debian 13.1.0-7) 13.1.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warrant

Bug#1041497: Aw: Bug#1041497: vmm: fails to run with python3 >= 3.10

[Bastian Germann]

> uploading a broken 0.1 version and keeping the maintainer who actually
> orphaned the package intact is probably not the best way, I would
> suggest that you either adopt the package or at least set the QA Group
> as maintainer.

Can you please reference the orphaning bug report?
I cannot find one and that is why the upload was a NMU and not a QA upload.

Processed (with 2 errors): Re: Bug#1041454: naev: FTBFS on i386

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 meson/1.2.0-1
Unknown command or malformed arguments to command.

> forcemerge 1041499 -1
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Unable to merge bugs because:
package of #1041454 is 'src:naev' not 'meson'
Failed to forcibly merge 1041499: Did not alter merged bugs.

> affects -1 src:naev
Bug #1041454 [src:naev] naev: FTBFS on mips64el
Added indication that 1041454 affects src:naev

-- 
1041454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041454
1041499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041454: naev: FTBFS on i386

[Sebastian Ramacher]

Control: reassign -1 meson/1.2.0-1
Control: forcemerge 1041499 -1
Control: affects -1 src:naev

On 2023-07-19 09:32:25 +0200, Sebastian Ramacher wrote:
> Source: naev
> Version: 0.8.2-1
> Severity: serious
> Tags: ftbfs sid trixie
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/fetch.php?pkg=naev&arch=mips64el&ver=0.8.2-1%2Bb2&stamp=1689629171&raw=0
> 
> Configuring config.h using configuration
> Has header "windows.h" : NO 
> Library dl found: YES
> Configuring naev.sh using configuration
> 
> ../test/glcheck/meson.build:4:15: ERROR: Can not run test applications in 
> this cross environment.

That's #1041499 in meson.

Cheers
-- 
Sebastian Ramacher

Processed: tagging 1037814

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1037814 + ftbfs
Bug #1037814 [src:paraview] paraview: ftbfs with GCC-13
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1037814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1041454 to meson, forcibly merging 1041499 1041454

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1041454 meson 1.2.0-1
Bug #1041454 [src:naev] naev: FTBFS on mips64el
Bug reassigned from package 'src:naev' to 'meson'.
No longer marked as found in versions naev/0.8.2-1.
Ignoring request to alter fixed versions of bug #1041454 to the same values 
previously set
Bug #1041454 [meson] naev: FTBFS on mips64el
Marked as found in versions meson/1.2.0-1.
> forcemerge 1041499 1041454
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Bug #1041454 [meson] naev: FTBFS on mips64el
Removed indication that 1041454 affects src:naev
Added indication that 1041454 affects src:glib2.0
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Added tag(s) trixie and sid.
Merged 1041454 1041499
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041454
1041499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 1041499 is forwarded to https://github.com/mesonbuild/meson/issues/12017, tagging 1041499

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1041499 https://github.com/mesonbuild/meson/issues/12017
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Bug #1041454 [meson] naev: FTBFS on mips64el
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/12017'.
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/12017'.
> tags 1041499 + upstream
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Bug #1041454 [meson] naev: FTBFS on mips64el
Added tag(s) upstream.
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1041454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041454
1041499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037772: marked as pending in mash

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1037772 in mash reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/med-team/mash/-/commit/4089b1a5a5c39201145ae812b269376cf37e70bd


gcc-13.patch: new: fix ftbfs with gcc-13.

Closes: #1037772


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037772

Processed: Bug#1037772 marked as pending in mash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037772 [src:mash] mash: ftbfs with GCC-13
Added tag(s) pending.

-- 
1037772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1036878 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1036878 serious
Bug #1036878 [src:horizon-eda] horizon-eda: Please migrate from oce to occt
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1036878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1036878

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1036878 + trixie sid
Bug #1036878 [src:horizon-eda] horizon-eda: Please migrate from oce to occt
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1036878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041497: vmm: fails to run with python3 >= 3.10

[Bernd Zeimetz]

19.07.2023 21:36:39 Bastian Germann :

>> uploading a broken 0.1 version and keeping the maintainer who actually
>> orphaned the package intact is probably not the best way, I would
>> suggest that you either adopt the package or at least set the QA Group
>> as maintainer.
> 
> Can you please reference the orphaning bug report?
> I cannot find one and that is why the upload was a NMU and not a QA upload.

Oh well sorry, seems there was no otphaning bug, I was sure there was one.
Probably because I once said that I might take over the maintenance of the 
package. That's why I actually started to prepare it, but didn't find the time 
to finish it. If necessary I can look through my email archives, but if you 
want to maintain it, nobody will have anything against it.

Bug#1037772: marked as done (mash: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2023 22:35:36 +
with message-id 
and subject line Bug#1037772: fixed in mash 2.3+dfsg-4
has caused the Debian Bug report #1037772,
regarding mash: ftbfs with GCC-13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mash
Version: 2.3+dfsg-3
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/mash_2.3+dfsg-3_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

[...]
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for zlib.h... yes
checking for capnp... yes
checking for capnp/common.h... yes
checking for gsl/gsl_cdf.h... yes
configure: creating ./config.status
config.status: creating Makefile
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j8
make[1]: Entering directory '/<>'
cd src/mash/capnp;export 
PATH=/usr/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;capnp
 compile -I /usr/include -oc++ MinHash.capnp
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -std=c++14 -Isrc -I/usr/include 
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -o src/mash/Command.o 
src/mash/Command.cpp
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -std=c++14 -Isrc -I/usr/include 
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -o src/mash/CommandBounds.o 
src/mash/CommandBounds.cpp
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -std=c++14 -Isrc -I/usr/include 
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -o src/mash/CommandContain.o 
src/mash/CommandContain.cpp
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -std=c++14 -Isrc -I/usr/include 
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -o src/mash/CommandDistance.o 
src/mash/CommandDistance.cpp
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -std=c++14 -Isrc -I/usr/include 
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -o src/mash/CommandTaxScreen.o 
src/mash/CommandTaxScreen.cpp
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -std=c++14 -Isrc -I/usr/include 
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -o src/mash/CommandScreen.o 
src/mash/CommandScreen.cpp
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -std=c++14 -Isrc -I/usr/include 
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -o src/mash/CommandTriangle.o 
src/mash/CommandTriangle.cpp
g++ -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -std=c++14 -Isrc -I/usr/include 
-I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2  -o src/mash/CommandFind.o 
src/mash/CommandFind.cpp
src/mash/Command.cpp: In member function ‘void 
mash::Command::Option::setArgument(std::string)’:
src/mash/Command.cpp:70:42: error: ‘uint64_t’ was not declared in this scope
   70 | else if ( type == Integer && uint64_t(argumentAsNumber) != 
argumentAsNumber )
  | 

Bug#1040629: Additional information

[Vladimir Petko]

The original failure could be due to the network issue, as the tests
attempt to access the internet.

Processed: severity of 1040718 is serious, severity of 1040723 is serious, severity of 1040728 is serious ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1040718 serious
Bug #1040718 [src:fclib] fclib: autopkgtest failure due to new CMake 
deprecation warning
Severity set to 'serious' from 'important'
> severity 1040723 serious
Bug #1040723 [src:cppzmq] cppzmq: autopkgtest failure due to new CMake 
deprecation warning
Severity set to 'serious' from 'important'
> severity 1040728 serious
Bug #1040728 [src:glm] glm: autopkgtest failure due to new CMake deprecation 
warning
Severity set to 'serious' from 'important'
> severity 1040729 serious
Bug #1040729 [src:oce] oce: autopkgtest failure due to new CMake deprecation 
warning
Severity set to 'serious' from 'important'
> severity 1040730 serious
Bug #1040730 [src:khronos-opencl-clhpp] khronos-opencl-clhpp: autopkgtest 
failure due to new CMake deprecation warning
Severity set to 'serious' from 'important'
> severity 1040731 serious
Bug #1040731 [src:wslay] wslay: autopkgtest failure due to new CMake 
deprecation warning
Severity set to 'serious' from 'important'
> severity 1040733 serious
Bug #1040733 [src:docopt.cpp] docopt.cpp: autopkgtest failure due to new CMake 
deprecation warning
Severity set to 'serious' from 'important'
> severity 1040735 serious
Bug #1040735 [src:ms-gsl] ms-gsl: autopkgtest failure due to new CMake 
deprecation warning
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1040718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040718
1040723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040723
1040728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040728
1040729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040729
1040730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040730
1040731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040731
1040733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040733
1040735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041432: box64: unsatisfiable dependencies

[Adrian Bunk]

On Tue, Jul 18, 2023 at 10:55:53PM +0200, Johannes Schauer Marin Rodrigues 
wrote:
>...
> $ apt-cache show crossbuild-essential-mips64el  | grep Depends:
> Depends: gcc-mips64el-linux-gnuabi64 (>= 4:10.2) | gcc:mips64el, 
> g++-mips64el-linux-gnuabi64 (>= 4:10.2) | g++:mips64el, dpkg-cross
> 
> But other packages use the same thing. Why does it work there?

An alternative dependency might be in non-free or might not exist at all.

Package: box64
Architecture: amd64 arm64 ppc64el riscv64
Depends:
 libgcc-s1:amd64,
 libstdc++6:amd64,

A package must not assume that the user has other architectures enabled.

There is a general issue around such dependencies, and also the more 
specific problem that permitting cross-architecture dependencies would
also require checking that migrating a package for one architecture does
not break dependencies on other architectures.

For box64, using libgcc-s1-amd64-cross and libstdc++6-amd64-cross might 
be an option (untested).

cu
Adrian

Bug#1041317: marked as done (dgit: table too wide in man page, trashes autopkgtests)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jul 2023 00:35:30 +
with message-id 
and subject line Bug#1041317: fixed in dgit 11.1
has caused the Debian Bug report #1041317,
regarding dgit: table too wide in man page, trashes autopkgtests
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dgit
Version: 9.13
Severity: Important
Justification: causes problems for everybody's autopkgtests

I noticed that groff 1.23.0-2 (and -1 before it) will be blocked from
ever migrating to testing due to an autopkgtest failure on EVERY
architecture.

https://tracker.debian.org/pkg/groff

So I downloaded the 2.4MB compressed autopkgtest log for groff 1.23.0-2
on amd64 and trawled through the 325,000+ lines of output looking for
the problem.  On the one hand, that is an obnoxiously huge amount of
information.  On the other, the log is annotated well enough that I was
able to quickly locate the problem.

Here are the juicy bits.

[...]
941s + for roff in $manpages
941s + section=1
941s + page=dgit
[...]
941s + cmd='man --warnings "$@" $section $page'
941s + eval 'man --warnings "$@" $section $page 2>&1 >/dev/null |tee 
/tmp/autopkgtest-lxc.3j70k01o/downtmp/autopkgtest_
tmp/dgit.1.txt-errs'
941s ++ man --warnings 1 dgit
941s ++ tee 
/tmp/autopkgtest-lxc.3j70k01o/downtmp/autopkgtest_tmp/dgit.1.txt-errs
941s :46: warning: table wider than line length minus 
indentation
[...]
941s RE (?^:^(?:(?^:^(?=a)b))$)|(?^:^(?:ERROR.*)$)|(?^:^(?:.* # table wider 
than line width)$)
941s unexpected: :46: warning: table wider than line length 
minus indentation
941s unexpected errors
941s END failed--call queue aborted, <> line 1.
[...]
941s  EXITING 22 
[...]
941s TEST FAILED
[...]
2435s manpages-format  FAIL non-zero exit status 16

That regex is sufficiently complex that I can't tell if it's trying to
filter the diagnostic message "table wider than line width" or not.  If
it is, the fact that I have recast the language of the diagnostic
message in groff 1.23.0 has fooled it.

It is a bad idea to rely on the exact wording of diagnostic messages.
That is one reason error conditions in many software systems are given
an unintelligible identifier.

https://git.savannah.gnu.org/cgit/groff.git/commit/?id=7111d3378f0c2ceab891d66ae815d393ff87dae5

Yes, the language in the regex could be updated if it's doing what I
think it is, but that just kicks the can down the road.  It is better
for groff to have the freedom to continue to improve its diagnostic
messages for the comprehension of the user.

So let's the fix the problem in the dgit man page.

Man pages are formatted for a width of 78n if the terminal width is 80
columns.  This origin of this practice is not well documented but
experience with groff upstream leads me to believe that it is a
workaround for bugs in GNU tbl(1).  (In AT&T Unix Version 7, they were
formatted for a line length of 65n, with a page offset of one tenth of
an inch.  On Western Electric Teletype Model 37 printing terminals.)

How wide is dgit's man page?

$ MANPAGER=cat MANWIDTH=80 command man --warnings dgit |wc -L
:46: warning: table wider than line length minus indentation
79

Hence the warning.

groff 1.22.4 didn't used to throw this warning in this circumstance.

That was a bug.

https://savannah.gnu.org/bugs/index.php?61854

Now it does.

The diagnostic is wholly legitimate.

Let's have a look:

$ MANPAGER=cat MANWIDTH=80 command man --warnings -Tascii dgit | sed -n 
'/DESCRIPTION/,/OPERATIONS/p'
:46: warning: table wider than line length minus indentation
DESCRIPTION
   dgit allows you to treat the Debian archive as if it were a git reposi-
   tory.   Conversely, it allows Debian to publish the source of its pack-
   ages as git branches, in a format which is directly useable by ordinary
   people.

   This is the command line reference.  Please read the tutorial(s):
   dgit-user(7)  for users: edit, build and share packages
   dgit-nmu-simple(7)for DDs: do a straightforward NMU
   dgit-maint-native(7)  for maintainers of Debian-native packages
   dgit-maint-debrebase(7)   for maintainers: a pure-git rebasish workflow
   dgit-maint-merge(7)   for maintainers: a pure-git merging workflow
   dgit-maint-gbp(7) for maintainers already using git-buildpackage
   dgit-sponsorship(7)   for sponsors and sponsored contributors
   dgit-downstream-dsc(7)setting up d

Bug#1041511: ntfs-3g: Undocumented dependency on libbrotli-dev

[Theodoric Stier]

Source: ntfs-3g
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: kerd...@gmail.com

Dear Maintainer,

This package build fails during the configure step if libbrotli-dev is not 
installed.
It appears to be missing from BuildDep.

I'm gonna try to use reportbug to attach a build log.

Thanks,
Ted Stier

-- System Information:
Debian Release: 12.0
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
 dpkg-buildpackage -us -uc -ui -aamd64 -sa
dpkg-buildpackage: info: source package ntfs-3g
dpkg-buildpackage: info: source version 1:2022.10.3-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Theodoric Stier 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_clean
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building ntfs-3g using existing 
./ntfs-3g_2022.10.3.orig.tar.gz
dpkg-source: info: building ntfs-3g in ntfs-3g_2022.10.3-2.debian.tar.xz
dpkg-source: info: building ntfs-3g in ntfs-3g_2022.10.3-2.dsc
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Remember to add 'LT_INIT' to configure.ac.
configure.ac:189: warning: The macro `AC_GNU_SOURCE' is obsolete.
configure.ac:189: You should run autoupdate.
./lib/autoconf/specific.m4:312: AC_GNU_SOURCE is expanded from...
configure.ac:189: the top level
configure.ac:475: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:475: You should run autoupdate.
./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
configure.ac:475: the top level
configure.ac:189: installing './compile'
configure.ac:32: installing './config.guess'
configure.ac:32: installing './config.sub'
configure.ac:36: installing './install-sh'
configure.ac:36: installing './missing'
Makefile.am: installing './INSTALL'
libfuse-lite/Makefile.am: installing './depcomp'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/home/ted/deb/pkg/ntfs-3g/ntfs-3g-2022.10.3'
dh_auto_configure -- --exec-prefix=/ --enable-crypto \
--enable-extras --enable-xattr-mappings \
--enable-quarantined --disable-ldconfig \
--enable-mount-helper --with-fuse=internal \
--enable-posix-acls
./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 --exec-prefix=/ 
--enable-crypto --enable-extras --enable-xattr-mappings --enable-quarantined 
--disable-ldconfig --enable-mount-helper --with-fuse=internal 
--enable-posix-acls
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for wchar.h... yes
checking for minix/config.h... no
checking for utime.h..

Bug#1037661: marked as pending in flrig

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #1037661 in flrig reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-hamradio-team/flrig/-/commit/055308b778550579c8f570584efddf6606f3fa56


Add patch for FTBFS on GCC-13 (Closes: #1037661)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037661

Processed: Bug#1037661 marked as pending in flrig

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037661 [src:flrig] flrig: ftbfs with GCC-13
Added tag(s) pending.

-- 
1037661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: hdrmerge: ftbfs with GCC-13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #1037686 [src:hdrmerge] hdrmerge: ftbfs with GCC-13
Added tag(s) patch and pending.

-- 
1037686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1037686: hdrmerge: ftbfs with GCC-13

[Gianfranco Costamagna]

control: tags -1 patch pending

Uploaded the one line patch

diff -Nru hdrmerge-0.5+git20200117/debian/changelog 
hdrmerge-0.5+git20200117/debian/changelog
--- hdrmerge-0.5+git20200117/debian/changelog   2023-07-07 22:22:08.0 
+0200
+++ hdrmerge-0.5+git20200117/debian/changelog   2023-07-16 21:12:40.0 
+0200
@@ -1,3 +1,12 @@
+hdrmerge (0.5+git20200117-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/221.patch:
+- cherry-pick upstream proposed patch to fix gcc-13 build failure (Closes:
+  #1037686)
+
+ -- Gianfranco Costamagna   Sun, 16 Jul 2023 
21:12:40 +0200
+
 hdrmerge (0.5+git20200117-3) unstable; urgency=medium
 
   * Team upload.

diff -Nru hdrmerge-0.5+git20200117/debian/patches/221.patch 
hdrmerge-0.5+git20200117/debian/patches/221.patch
--- hdrmerge-0.5+git20200117/debian/patches/221.patch   1970-01-01 
01:00:00.0 +0100
+++ hdrmerge-0.5+git20200117/debian/patches/221.patch   2023-07-16 
21:12:40.0 +0200
@@ -0,0 +1,21 @@
+From 7a799d5c3adee9865f9956be51ec9d4955a087b7 Mon Sep 17 00:00:00 2001
+From: jdeluyck <5451787+jdelu...@users.noreply.github.com>
+Date: Thu, 29 Jun 2023 13:53:55 +0200
+Subject: [PATCH] fix compilation by including cstdlib
+
+---
+ src/TiffDirectory.hpp | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/TiffDirectory.hpp b/src/TiffDirectory.hpp
+index de989a4..dd9668d 100644
+--- a/src/TiffDirectory.hpp
 b/src/TiffDirectory.hpp
+@@ -22,6 +22,7 @@
+
+ #include 
+ #include 
++#include 
+
+ #ifndef _TIFFDIRECTORY_HPP_
+ #define _TIFFDIRECTORY_HPP_
diff -Nru hdrmerge-0.5+git20200117/debian/patches/series 
hdrmerge-0.5+git20200117/debian/patches/series
--- hdrmerge-0.5+git20200117/debian/patches/series  2023-07-07 
22:22:08.0 +0200
+++ hdrmerge-0.5+git20200117/debian/patches/series  2023-07-16 
21:12:40.0 +0200
@@ -1 +1,2 @@
 0001-Fix-LibRaw-0.21-API-change.patch
+221.patch


On Wed, 14 Jun 2023 09:25:26 + Matthias Klose  wrote:

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_auto

Bug#1037661: marked as done (flrig: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jul 2023 05:04:05 +
with message-id 
and subject line Bug#1037661: fixed in flrig 1.4.7-2
has caused the Debian Bug report #1037661,
regarding flrig: ftbfs with GCC-13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flrig
Version: 1.4.7-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/flrig_1.4.7-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 rigs/yaesu/FTdx9000.cxx:26:
./include/kenwood/KENWOOD.h:101:22: warning: ‘virtual void 
KENWOOD::tune_rig(int)’ was hidden [-Woverloaded-virtual=]
  101 | virtual void tune_rig(int);
  |  ^~~~
In file included from ./include/rigs.h:69:
./include/kenwood/TS940S.h:67:14: note:   by ‘void RIG_TS940S::tune_rig()’
   67 | void tune_rig();
  |  ^~~~
g++ -DHAVE_CONFIG_H -I.  -I. -I./include -I./xmlrpcpp -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./xmlrpcpp -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/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-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. 
-I./include   -pipe -Wall -fexceptions -O2   -DNDEBUG -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o support/flrig-dialogs.o `test -f 
'support/dialogs.cxx' || echo './'`support/dialogs.cxx
g++ -DHAVE_CONFIG_H -I.  -I. -I./include -I./xmlrpcpp -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./xmlrpcpp -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/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-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. 
-I./include   -pipe -Wall -fexceptions -O2   -DNDEBUG -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o support/flrig-gpio_ptt.o `test -f 
'support/gpio_ptt.cxx' || echo './'`support/gpio_ptt.cxx
g++ -DHAVE_CONFIG_H -I.  -I. -I./include -I./xmlrpcpp -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./xmlrpcpp -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/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-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. 
-I./include   -pipe -Wall -fexceptions -O2   -DNDEBUG -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o support/flrig-ptt.o `test -f 'support/ptt.cxx' || 
echo './'`support/ptt.cxx
g++ -DHAVE_CONFIG_H -I.  -I. -I./include -I./xmlrpcpp -Wdate-time 
-D_FORTIFY_SOURCE=2 -I./xmlrpcpp -I/usr/include/cairo -I/usr/include/glib-2.0 
-

Bug#1041075: marked as done (libphonenumber FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jul 2023 05:04:44 +
with message-id 
and subject line Bug#1041075: fixed in libphonenumber 8.12.57+ds-4
has caused the Debian Bug report #1041075,
regarding libphonenumber FTBFS with googletest 1.13.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libphonenumber
Version: 8.12.57+ds-3
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libphonenumber.html

...
In file included from /usr/include/gtest/gtest-message.h:57,
 from /usr/include/gtest/gtest-assertion-result.h:46,
 from /usr/include/gtest/gtest.h:64,
 from 
/build/1st/libphonenumber-8.12.57+ds/cpp/test/phonenumbers/asyoutypeformatter_test.cc:23:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less 
than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


This can be fixed by setting CMAKE_CXX_STANDARD to 14
in both cpp/CMakeLists.txt and tools/cpp/CMakeLists.txt
--- End Message ---
--- Begin Message ---
Source: libphonenumber
Source-Version: 8.12.57+ds-4
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
libphonenumber, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated libphonenumber package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Jul 2023 21:36:41 -0700
Source: libphonenumber
Architecture: source
Version: 8.12.57+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1041075
Changes:
 libphonenumber (8.12.57+ds-4) unstable; urgency=medium
 .
   * Team upload.
   * Use C++14 to resolve FTBFS with googletest 1.13.0 (Closes: #1041075)
 Thank you to Adrian Bunk for the patch
Checksums-Sha1:
 4c0ae52eb9361a7b86ff0aee97deee67016d5488 2928 libphonenumber_8.12.57+ds-4.dsc
 864ca5ca01b5ca1f935668b2fef1b1296993f240 12528 
libphonenumber_8.12.57+ds-4.debian.tar.xz
 1ef25242c62162f013a510a2b3c0c31438dc7d24 19992 
libphonenumber_8.12.57+ds-4_amd64.buildinfo
Checksums-Sha256:
 bed825a6815476c781efcaee62dfd53ee3ff252aa5626229f9148bb1e0cf8cf6 2928 
libphonenumber_8.12.57+ds-4.dsc
 c53e294927773592a02ded5512cbe2f3517ae1f62ada804f16c9b979b6d3b56a 12528 
libphonenumber_8.12.57+ds-4.debian.tar.xz
 7d570e42862602b991bf0f96fa1403a6d552015832be42ad9b85a7b65fa984f3 19992 
libphonenumber_8.12.57+ds-4_amd64.buildinfo
Files:
 f7645e2b618223e0317a0508a28e5c73 2928 libs optional 
libphonenumber_8.12.57+ds-4.dsc
 242850b98a211572d2be07e55ea47a03 12528 libs optional 
libphonenumber_8.12.57+ds-4.debian.tar.xz
 52f0f849a6ffcc43363262b0f15a818b 19992 libs optional 
libphonenumber_8.12.57+ds-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmS4vTYUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpb4dBAAsBILdQCYj1m8qn/dQPqxUBddadOh
HLfL+LvXLbnBESZaJVw0FhHaCRRwK4v1UanVuxkBBdS1qjydXUEdyJ5/V/1nQN/w
0/Reat+KDEPE9uAy3Q4jXT47DEC3XcNC+B4QUSz2vhHzpccDtw/VJL4pmdL1U5aG
IEiLT35NDxcMFOs69+ucyi8/gFW+EZNdaBSrzZIVpBORK7IE9SdsYfVr6Nhj7pvZ
Cj2+gOjRvxQFgNwgSahLy9dOZLdWGP9LoSTyAF8rX3xFfTwlQHr3rdeipHThlqIf
Zsm4iq1by/9GSc9U00M1LSP6GoKqcZGqkWvV299hDLmXiCEPIBYuRDju7HA0x6Eb
BrCsIl+iFka3/sF5q3P/9cDwjdLGWUqu4orlHx8almRxz2BiJvID+79K7Aot4e37
FkKZlT3Etn143OVtnXv9fURCRLLjFG5K+rmntgIPxzUWGjMh2b1ASIQ0cmYdVnNL
IT8tzYJU+3TqvbY5/7g3dTyfsfrzXXbsHdXNgclOPogGXu65fLYmYmWlgCiq98ZF
qRfIKI+RL7WAjkFJdCiZnJsY7px7Ztws8fjbzR6cm5of+zQk2znydAiGqafcZZbj
NutvBTfGWXWdoXcdWnKvtOBj+wHE7K0x7ua2aJvqgiJERx/4wzqqawkMWf0dhEwU
bjLSgq7L75Y15DY=
=uqo5
-END PGP SIGNATURE End Message ---

Bug#1037686: marked as done (hdrmerge: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jul 2023 05:04:14 +
with message-id 
and subject line Bug#1037686: fixed in hdrmerge 0.5+git20200117-3.1
has caused the Debian Bug report #1037686,
regarding hdrmerge: ftbfs with GCC-13
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 con

Bug#1041432: box64: unsatisfiable dependencies

[Johannes Schauer Marin Rodrigues]

Hi Adrian,

thank you for weighing in!

Quoting Adrian Bunk (2023-07-20 01:27:10)
> 
> Package: box64
> Architecture: amd64 arm64 ppc64el riscv64
> Depends:
>  libgcc-s1:amd64,
>  libstdc++6:amd64,
> 
> A package must not assume that the user has other architectures enabled.

why not? Is this codified in a policy somewhere? If foreign architectures are
not enabled, box64 would just not be installable but there are tons of packages
I cannot install on my system without the package itself being buggy (for
example due to Conflicts).

If I just drop these dependencies, that would make the package have an RC bug
because box64 cannot function without amd64 shared libraries.

> There is a general issue around such dependencies, and also the more specific
> problem that permitting cross-architecture dependencies would also require
> checking that migrating a package for one architecture does not break
> dependencies on other architectures.
> 
> For box64, using libgcc-s1-amd64-cross and libstdc++6-amd64-cross might be an
> option (untested).

Those packages install their libraries into /usr/ which is not
searched by the dynamic linker. Maybe some LD_LIBRARY_PATH trickery can make it
work but those shared libraries are not meant for running actual binaries.

Originally, box64 upstream shipped their own binary blobs of libstdc++.so.6 and
libgcc_s.so.1 and installed them into /usr/lib/x86_64-linux-gnu/. This is of
course not an option either as that would conflict with users who do have amd64
packages installed and would also make the package violate DFSG for shipping
binaries without source.

It seems that the correct way forward would be to teach britney about foreign
architecture dependencies? I had a look at the britney source and it seems to
ship with its own dependency resolver instead of relying on dose3, for example.
Teaching it about foreign architectures looks like a massive change...

Thanks!

cheers, josch

signature.asc
Description: signature