Bug#1041899: libreoffice-uiconfig-report-builder: undeclared file conflicts with libreoffice-report-builder/unstable

[Helmut Grohne]

Package: libreoffice-uiconfig-report-builder
Version: 4:7.6.0~rc1-1
Severity: serious

Hi Rene,

thanks for the fixes to the other file conflict issues. Unfortunately,
your upload also introduces new problems.

libreoffice-uiconfig-report-builder now contains a lot of files below
/usr/lib/libreoffice/share/config/soffice.cfg/modules/dbreport that also
happen to be contained in libreoffice-report-builder (from
bullseye-backports to unstable). Are you missing replaces here?

Helmut

Bug#1041855: linux-image-6.4.0-1-amd64: IO wait regression

[Ben Hutchings]

Control: severity -1 important

On Mon, 2023-07-24 at 15:40 +0200, Christian Göttsche wrote:
> Package: src:linux
> Version: 6.4.4-1
> Severity: serious
> 
> Dear Maintainer,
> 
> Kernel 6.4.4 is affected by a regression causing one core be report
> high IO wait utilization.
> 
> See https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/

There is no such thing as a CPU having "high IO wait utilization". 
When tasks are in I/O wait state, they are not using a CPU.

Unfortunately, for historical reasons Linux includes such tasks in the
load average and reports a CPU as being in I/O wait state when it's
idle and the last task running on it went into I/O wait state (at least
I think that's what the rule is).

So this bug is about an unwanted change in task/CPU state reporting,
not tasks suddenly using much more CPU time.  For that reason, I don't
think it should "serious", i.e. a blocker for testing propagation.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.



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

Processed: Re: Bug#1041855: linux-image-6.4.0-1-amd64: IO wait regression

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1041855 [src:linux] linux-image-6.4.0-1-amd64: IO wait regression
Severity set to 'important' from 'serious'

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

Bug#1037892: marked as done (wayfire: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 22:41:11 +
with message-id 
and subject line Bug#1037892: fixed in wayfire 0.7.5-1
has caused the Debian Bug report #1037892,
regarding wayfire: 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.)


-- 
1037892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wayfire
Version: 0.7.4-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/wayfire_0.7.4-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

[...]
Message: 

wayfire 0.7.4

system wfconfig: true
 system wlroots: true
   xwayland: true
x11-backend: true
imageio: true
 gles32: true
print trace: true


Build targets in project: 38
NOTICE: Future-deprecated features used:
 * 0.56.0: {'meson.source_root', 'dependency.get_pkgconfig_variable'}

wayfire 0.7.4

  Subprojects
wf-touch : YES
wf-utils : YES

  User defined options
buildtype: plain
libdir   : lib/x86_64-linux-gnu
localstatedir: /var
prefix   : /usr
sysconfdir   : /etc
wrap_mode: nodownload

Found ninja-1.11.1 at /usr/bin/ninja
   dh_auto_build
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
[1/220] c++ -Isubprojects/wf-utils/libwf-utils.so.0.4.0.p 
-Isubprojects/wf-utils -I../subprojects/wf-utils -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++17 
-Wno-deprecated-declarations -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_condition_condition.cpp.o 
-MF 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_condition_condition.cpp.o.d 
-o 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_condition_condition.cpp.o 
-c ../subprojects/wf-utils/wayfire/condition/condition.cpp
[2/220] c++ -Isubprojects/wf-utils/libwf-utils.so.0.4.0.p 
-Isubprojects/wf-utils -I../subprojects/wf-utils -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++17 
-Wno-deprecated-declarations -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_condition_logic_condition.cpp.o
 -MF 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_condition_logic_condition.cpp.o.d
 -o 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_condition_logic_condition.cpp.o
 -c ../subprojects/wf-utils/wayfire/condition/logic_condition.cpp
[3/220] c++ -Isubprojects/wf-utils/libwf-utils.so.0.4.0.p 
-Isubprojects/wf-utils -I../subprojects/wf-utils -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++17 
-Wno-deprecated-declarations -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_lexer_literal.cpp.o -MF 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_lexer_literal.cpp.o.d -o 
subprojects/wf-utils/libwf-utils.so.0.4.0.p/wayfire_lexer_literal.cpp.o -c 
../subprojects/wf-utils/wayfire/lexer/literal.cpp
[4/220] c++ -Isubprojects/wf-utils/libwf-utils.so.0.4.0.p 
-Isubprojects/wf-utils -I../subprojects/wf-utils -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall 

Processed: bug 1041853 is forwarded to https://gitlab.kitware.com/cmake/cmake/-/issues/25123

[Debian Bug Tracking System]

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

> forwarded 1041853 https://gitlab.kitware.com/cmake/cmake/-/issues/25123
Bug #1041853 [cmake] cmake 3.27.0-1 causes sundials FTBFS
Set Bug forwarded-to-address to 
'https://gitlab.kitware.com/cmake/cmake/-/issues/25123'.
> thanks
Stopping processing here.

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

Bug#1041837: marked as done (libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= trixie: /usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 22:22:27 +
with message-id 
and subject line Bug#1041837: fixed in libreoffice 4:7.5.5-3
has caused the Debian Bug report #1041837,
regarding libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
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.)


-- 
1041837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-draw
Version: 4:7.5.5-2
Severity: serious

libreoffice-draw installs
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/layoutlist.xml
and
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/objectlist.xml
which are also contained in libreoffice-impress-nogui from bullseye to
trixie. Trying to install libreoffice-draw may result in an unpack
error. Please add the necessary Breaks and Replaces.

Helmut
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 4:7.5.5-3
Done: Rene Engelhard 

We believe that the bug you reported is fixed in the latest version of
libreoffice, 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.
Rene Engelhard  (supplier of updated libreoffice 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: Mon, 24 Jul 2023 22:17:40 +0200
Source: libreoffice
Architecture: source
Version: 4:7.5.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 1041837
Changes:
 libreoffice (4:7.5.5-3) unstable; urgency=medium
 .
   * debian/control.in:
 - add/update Replaces: in -draw/-draw-nogui:
   libreoffice-impress (<< 4:7.5.4~rc1-1), libreoffice-impress-nogui (<< 
4:7.5.4~rc1-1)
   (closes: #1041837)
Checksums-Sha1:
 0639b4790655cbed5047cdb3b692cdee2b893ff7 34576 libreoffice_7.5.5-3.dsc
 70ec86c4d2dfb2c1c0a01abfcb6a002e1a102ea8 24503324 
libreoffice_7.5.5-3.debian.tar.xz
 0d6c398a726776cd302e5371fbf7e386daf14330 35633 
libreoffice_7.5.5-3_source.buildinfo
Checksums-Sha256:
 f9cf03630e5c66265f3826531f078c40d35a561ea53ac0423e29b8da95c0df00 34576 
libreoffice_7.5.5-3.dsc
 1d9f8b67d711436c0df6e6abe51b7dbd58916a3ebc7a38932331d9bcd4802c5b 24503324 
libreoffice_7.5.5-3.debian.tar.xz
 32591960051f2ae139d7e76c559f0a7540a0279fe5a7bfe7cf7b096a30c6394c 35633 
libreoffice_7.5.5-3_source.buildinfo
Files:
 ca5dc4f57a9509f8a1d4823890059923 34576 editors optional libreoffice_7.5.5-3.dsc
 fa965efedd0ecc923fb8d5eed672e933 24503324 editors optional 
libreoffice_7.5.5-3.debian.tar.xz
 3b508c1ad9ba0d28d8453d71f704c41f 35633 editors optional 
libreoffice_7.5.5-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAmS+4OAQHHJlbmVAZGVi
aWFuLm9yZwAKCRAKoEVx0D4+cARxD/9nq3EGEIn2norB9sIMjnEbDJvaebYggOSQ
LLer5K2B3PHpiXgPAexMWddGpBbHfy7rbGk6+h4qOOMS4/2b1dIsu4oiAjTCrWiH
FMPYc+T0uEN7OcwH6ovznLw03z7+e8ETdlLjG5M+KNppz3YZ2ZDi3ZdKPLztydzr
gYVTrYq+ns6ewdZdEJLIxOgj+e+u6RxcuYkaFGR8CS6thEMXLVQuufG7U3J//OcB
DOif3QQ7FUp+XkKjlbxPlFJ7hCa6Wkeo36EyHk6IrXJ9VGrjN7SDBc2a2K1cKX7v
NaC42RN1U15yHpyY6j0XEzYxyLm138GgrBGDOYpjkPpma1EGdqC9+TJmp9BgwzrW
la2brtMtx6q5cRC+jy7HZVYpENAQwQVaSAfELewlm3XmmVvANNk0GujBkGVGcV0D
QUDc5yFjIbc2qhxR3fYcwXRqgS/2QvnZxwAQNEWT3f0wsyXnPHKCNUrauiSuq9Zq
0vB1a51Ob/6QeeqQTIo5RPz+qNYw0KjAFrAzecyBjWQNjtVvw4tQzXHy980Q0ojh
gEb9HjUswlqURkAk6JAwRXSIX9uA/Hqsc9o3XppHOlniF+LVm1hoMX3J21Qm298y
movO1P90WDKkRoRrM/f/r6EBkX9nleMwSZ0N1R5vV5U81Eyp2zRJebmwo4xeTZtm
04cPWCIMQg==
=hIIe
-END PGP SIGNATURE End Message ---

Bug#1041870: [3dprinter-general] Bug#1041870: slic3r-prusa FTBFS on i386

[Christoph Berg]

Re: Adrian Bunk
> 2. the following change:
> 
> --- debian/rules.old  2023-07-24 15:36:20.941771419 +
> +++ debian/rules  2023-07-24 15:36:43.133759741 +
> @@ -5,7 +5,7 @@
>  # less debug info to avoid running out of address space
>  ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
>   export DEB_CXXFLAGS_MAINT_APPEND += --param ggc-min-expand=5 -g0
> -else ifneq (,$(filter $(DEB_HOST_ARCH), armhf))

The old command was wrong anyway, the pattern list comes first:

ifneq (,$(filter armhf, $(DEB_HOST_ARCH)))

Doesn't matter when it's a single item without % wildcards, but will
explode when adding more architectures.

Christoph

Processed: affects 1040246

[Debian Bug Tracking System]

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

> affects 1040246 librust-sha3-0.9-dev librust-multihash-dev
Bug #1040246 [librust-block-buffer-0.9+block-padding-dev] 
librust-block-buffer-0.9+block-padding-dev: uninstallable after upgrade of 
rust-block-padding.
Added indication that 1040246 affects librust-sha3-0.9-dev and 
librust-multihash-dev
> thanks
Stopping processing here.

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

Bug#1037614: marked as done (cura-engine: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 20:40:33 +
with message-id 
and subject line Bug#1037614: fixed in cura-engine 1:5.0.0-4
has caused the Debian Bug report #1037614,
regarding cura-engine: 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.)


-- 
1037614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cura-engine
Version: 1:4.13.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/cura-engine_4.13.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

[...]
   27 | inline uint64_t ceil_divide_signed(const int64_t dividend, const 
int64_t divisor) //!< Return dividend divided by divisor rounded up towards 
positive infinity.
  |^~~~
/<>/src/settings/types/../../utils/math.h:27:8: note: ‘uint64_t’ 
is defined in header ‘’; did you forget to ‘#include ’?
/<>/src/settings/types/../../utils/math.h:31:8: error: ‘uint64_t’ 
does not name a type
   31 | inline uint64_t floor_divide_signed(const int64_t dividend, const 
int64_t divisor) //!< Return dividend divided by divisor rounded down towards 
negative infinity.
  |^~~~
/<>/src/settings/types/../../utils/math.h:31:8: note: ‘uint64_t’ 
is defined in header ‘’; did you forget to ‘#include ’?
/<>/src/settings/types/../../utils/math.h:35:8: error: ‘uint64_t’ 
does not name a type
   35 | inline uint64_t round_divide(const uint64_t dividend, const uint64_t 
divisor) //!< Return dividend divided by divisor rounded to the nearest integer
  |^~~~
/<>/src/settings/types/../../utils/math.h:35:8: note: ‘uint64_t’ 
is defined in header ‘’; did you forget to ‘#include ’?
/<>/src/settings/types/../../utils/math.h:39:8: error: ‘uint64_t’ 
does not name a type
   39 | inline uint64_t round_up_divide(const uint64_t dividend, const uint64_t 
divisor) //!< Return dividend divided by divisor rounded to the nearest integer
  |^~~~
/<>/src/settings/types/../../utils/math.h:39:8: note: ‘uint64_t’ 
is defined in header ‘’; did you forget to ‘#include ’?
make[3]: *** [CMakeFiles/_CuraEngine.dir/build.make:955: 
CMakeFiles/_CuraEngine.dir/src/settings/AdaptiveLayerHeights.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from /<>/src/settings/types/Angle.h:8,
 from /<>/src/settings/Settings.cpp:14:
/<>/src/settings/types/../../utils/math.h:22:8: error: ‘uint64_t’ 
does not name a type
   22 | inline uint64_t round_divide_signed(const int64_t dividend, const 
int64_t divisor) //!< Return dividend divided by divisor rounded to the nearest 
integer
  |^~~~
/<>/src/settings/types/../../utils/math.h:8:1: note: ‘uint64_t’ is 
defined in header ‘’; did you forget to ‘#include ’?
7 | #include 
  +++ |+#include 
8 | 
/<>/src/settings/types/../../utils/math.h:27:8: error: ‘uint64_t’ 
does not name a type
   27 | inline uint64_t ceil_divide_signed(const int64_t dividend, const 
int64_t divisor) //!< Return dividend divided by divisor rounded up towards 
positive infinity.
  |^~~~
/<>/src/settings/types/../../utils/math.h:27:8: note: ‘uint64_t’ 
is defined in header ‘’; did you forget to ‘#include ’?
/<>/src/settings/types/../../utils/math.h:31:8: error: ‘uint64_t’ 
does not name a type
   31 | inline uint64_t floor_divide_signed(const int64_t dividend, const 
int64_t divisor) //!< Return dividend divided by divisor rounded down towards 
negative 

Bug#1041808: marked as done (cura-engine: Several unit test failures on i686)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 20:40:33 +
with message-id 
and subject line Bug#1041808: fixed in cura-engine 1:5.0.0-4
has caused the Debian Bug report #1041808,
regarding cura-engine: Several unit test failures on i686
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.)


-- 
1041808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cura-engine
Version: 5.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Usertags: i686
Forwarded: https://github.com/Ultimaker/CuraEngine/issues/1192
X-Debbugs-Cc: onit...@gmail.com

On i686, CuraEngine 5.x fails to build due to failing unit tests.

This is a longstanding issue, going back to 4.4, where it was fixed by adding a
larger tolerance to test values.
However, the issue was not investigated thoroughly and returns in 5.0 with more
failing unit tests.

The root cause of these failures are rounding errors on i686, where the x87 FPU
produces different results than floating point units in other processors. These
differences are tiny, and usually not more than a few ULPs.

CuraEngine uses integer math in most places, but resorts to double-precision
floating-point calculations in certain cases. Afterwards, the results are
truncated to 64-bit integers (C type long long), and subsequent calculation is
done on the integer values. Truncation (aka round-toward-zero) is often ok and
works fine on amd64 (SSE2 floating-point math) and other CPUs, but produces
different results on the x87 FPU. When truncating, these produce off-by-one
errors in many cases, and the these errors can accumulate and lead to huge
differences in the unit tests.

By strategically adding explicit rounding (round-to-nearest) in the right
places, these errors can be eliminated. While this will produce subtly
different results in some cases, it is arguably more correct than always
truncating.

And at least on amd64, there is no performance difference between truncation
and rounding: The SSE2 CVTTSD2SI and CVTSD2SI instructions have the same
performance.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cura-engine
Source-Version: 1:5.0.0-4
Done: Gregor Riepl 

We believe that the bug you reported is fixed in the latest version of
cura-engine, 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.
Gregor Riepl  (supplier of updated cura-engine 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: Mon, 24 Jul 2023 22:09:39 +0200
Source: cura-engine
Architecture: source
Version: 1:5.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Gregor Riepl 
Closes: 1037614 1040252 1040806 1041808
Changes:
 cura-engine (1:5.0.0-4) unstable; urgency=medium
 .
   * Fix failing unit test. Closes: #1040252
   * Fix gcc-13 compatibility. Closes: #1037614
   * Fix errors with obsolete adhesion_extruder_nr parameter.
 Thanks to Dan Bungert (Canonical) for reporting this.
 Closes: #1040806
   * Fix rounding errors on i686. Closes: #1041808
   * Drop previous patch for rounding errors.
 It's covered by the round error fix.
Checksums-Sha1:
 466bf7c7a944b02c7373af4afd2fab004e56305c 2202 cura-engine_5.0.0-4.dsc
 1315c9fb0c2bda3ccbb8f8801a75a4b3cb2e3a08 67960 
cura-engine_5.0.0-4.debian.tar.xz
Checksums-Sha256:
 c7d26645d858ecb59241911c5e4e9818530bdac88e3825e837c51da5236637c7 2202 
cura-engine_5.0.0-4.dsc
 

Bug#1040252: marked as done (cura-engine FTBFS on some 32bit architectures)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 20:40:33 +
with message-id 
and subject line Bug#1040252: fixed in cura-engine 1:5.0.0-4
has caused the Debian Bug report #1040252,
regarding cura-engine FTBFS on some 32bit 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.)


-- 
1040252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cura-engine
Version: 1:5.0.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cura-engine=1%3A5.0.0-1
https://buildd.debian.org/status/logs.php?pkg=cura-engine=1%3A5.0.0-3

...
5: 
5: [ FATAL ] /usr/include/gtest/internal/gtest-param-util.h:585:: Condition 
IsValidParamName(param_name) failed. Parameterized test name 
'InfillTestParameters_P2_Z0_C0_L350__-4294967296' is invalid, in 
./tests/InfillTest.cpp line 241
5: 
...
96% tests passed, 1 tests failed out of 26

Total Test time (real) =  10.85 sec

The following tests FAILED:
  5 - InfillTest (Subprocess aborted)
Errors while running CTest
make[1]: *** [Makefile:94: test] Error 8
--- End Message ---
--- Begin Message ---
Source: cura-engine
Source-Version: 1:5.0.0-4
Done: Gregor Riepl 

We believe that the bug you reported is fixed in the latest version of
cura-engine, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gregor Riepl  (supplier of updated cura-engine 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: Mon, 24 Jul 2023 22:09:39 +0200
Source: cura-engine
Architecture: source
Version: 1:5.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Gregor Riepl 
Closes: 1037614 1040252 1040806 1041808
Changes:
 cura-engine (1:5.0.0-4) unstable; urgency=medium
 .
   * Fix failing unit test. Closes: #1040252
   * Fix gcc-13 compatibility. Closes: #1037614
   * Fix errors with obsolete adhesion_extruder_nr parameter.
 Thanks to Dan Bungert (Canonical) for reporting this.
 Closes: #1040806
   * Fix rounding errors on i686. Closes: #1041808
   * Drop previous patch for rounding errors.
 It's covered by the round error fix.
Checksums-Sha1:
 466bf7c7a944b02c7373af4afd2fab004e56305c 2202 cura-engine_5.0.0-4.dsc
 1315c9fb0c2bda3ccbb8f8801a75a4b3cb2e3a08 67960 
cura-engine_5.0.0-4.debian.tar.xz
Checksums-Sha256:
 c7d26645d858ecb59241911c5e4e9818530bdac88e3825e837c51da5236637c7 2202 
cura-engine_5.0.0-4.dsc
 def98284108caf71f50403cd9c8c9aedee22012f859c0c35bda5d771a003e5e8 67960 
cura-engine_5.0.0-4.debian.tar.xz
Files:
 7440b8e4397b19b37a18d98dacdf3b88 2202 utils optional cura-engine_5.0.0-4.dsc
 443631b854047125c2ed074e24980a9a 67960 utils optional 
cura-engine_5.0.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmS+2+YACgkQTFprqxLS
p64kLxAApgPNHf4TkeVxxS2XpURBv8q4XqFMzh4hpOFsplreZ7nq71HUAnfjR0Sj
PTq1gl+KakTud+4t+1OjRzMl8GTeqWGKP4hOxYzmMyK3iEdzFuA7f3Js0pwNpFIu
0OQduU63kG2W1WjXpPNEWsog+sTWVdpALvXx77S2P4VXFZ++nYBgqROjQA2vpzIt
wXiDXAHXYPfFRCHT3kGjOYZQwlaENQt5TR0mb2Y4Ht2Vl/iQJtSO6gF9m+dehSd7
yzam//urohzdNM824yxWZxa6KKEiwCX/ybGOD1dx2DcfG7wcxijcIK3kgiQeZfoH
oTsm3d/5NgRvilCyHxgWquC8bgmwtYS5VuRAilJ1m+d36x8TbJLEsJaCdt8MBMZD
3e33jcYZctcXtdxBDF8klGLZ9UfEfJnsWTlRZJCpUSWz4D6go126TFQxhdr25/af
Xd1kHr9PfJHjMbuVFlqBIWtdRsABrd41VdHH+A5XDEpgNzP/ICUGVm4s58mTwFfG
e6qFfY/XhjSLMPmIBH0buqvRNymT1JzsopZcZ6j4spR1/vlALWRJWaKVOpIZmW5r
SO+E3n6HhKeYFpFLXtn9vyZVgVyCZTcDiIRbjECXxdyPqLRxJ0s9VzG8zEB5FXZp
bwfo223J3Xm155eWi9R+Zm1PytSbNqMy+SLfXFvJoOPv9H7JQIo=
=IRhX
-END PGP SIGNATURE End Message ---

Processed: closing 1041837

[Debian Bug Tracking System]

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

> close 1041837 4:7.6.0~rc1-1
Bug #1041837 [libreoffice-draw] libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Marked as fixed in versions libreoffice/4:7.6.0~rc1-1.
Bug #1041837 [libreoffice-draw] libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Bug#1041837 marked as pending in libreoffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041837 [libreoffice-draw] libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Ignoring request to alter tags of bug #1041837 to the same tags previously set

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

Bug#1041837: marked as pending in libreoffice

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #1041837 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/3693fc16ba810d9e48a51ac21a3ad84579ad883d


add/update Replaces: in -draw/-draw-nogui: libreoffice-impress (<< 
4:7.5.4~rc1-1), libreoffice-impress-nogui (<< 4:7.5.4~rc1-1) (closes: #1041837)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041837

Bug#1041837: marked as pending in libreoffice

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #1041837 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/3693fc16ba810d9e48a51ac21a3ad84579ad883d


add/update Replaces: in -draw/-draw-nogui: libreoffice-impress (<< 
4:7.5.4~rc1-1), libreoffice-impress-nogui (<< 4:7.5.4~rc1-1) (closes: #1041837)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041837

Processed: Bug#1041837 marked as pending in libreoffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041837 [libreoffice-draw] libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Added tag(s) pending.

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

Bug#1041884: Acknowledgement (sct: segfault at e0)

[Alejandro Colomar]

Never mind.  My filesystem was full.  That was my problem.  I wrote
a program with an accidental infinite loop, and while debugging it,
a printf line started writing lines to somewhere in /opt, and I
forgot to kill it before writing 1 TB of garbage. :-)

Cheers,
Alex

On 2023-07-24 22:21, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 1041884: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041884.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   alx.manpa...@gmail.com
> (after having been given a Bug report number, if it did not have one).
> 
> Your message has been sent to the package maintainer(s):
>  Jacob Adams 
> 
> If you wish to submit further information on this problem, please
> send it to 1041...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

-- 

GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1041837: closed by René Engelhard (Re: Bug#1041837: libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= trixie: /usr/lib/libreoffic

[Debian Bug Tracking System]

Processing control commands:

> found -1 4:7.5.4~rc1-1
Bug #1041837 [libreoffice-draw] libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
There is no source info for the package 'libreoffice-draw' at version 
'4:7.5.4~rc1-1' with architecture ''
Unable to make a source version for version '4:7.5.4~rc1-1'
Marked as found in versions 4:7.5.4~rc1-1.

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

Bug#1041837: closed by René Engelhard (Re: Bug#1041837: libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= trixie: /usr/lib/libreoffice/share/config/

[Rene Engelhard]

Control: found -1 4:7.5.4~rc1-1

Control: fixed -1 4:7.6.0~rc1-1


Am 24.07.23 um 19:27 schrieb Helmut Grohne:

Control: reopen -1
Control: found -1 4:7.5.5-2
Control: found -1 4:7.5.5~rc1-2

On Mon, Jul 24, 2023 at 08:09:07AM +, Debian Bug Tracking System wrote:

08:26 < helmut> _rene_: re libreoffice (short on time atm): seems like I messed 
something up, please close my report. (...)

Further context here. On IRC you also said that this was fixed in
experimental. 20:51  * _rene_ lost hope


What? I didn't say anything on IRC about this.

And I said experimental (NEW). I even pointed to libreoffice-uiconfig-* 
of 7.6 (-> NEW)



Also note that experimentals version is LOWER than sids.

So obviously "fixed in experimental" does not make any sense here otherwise.


In contrast *YOU* said it could be closed. I followed.



/usr/lib/libreoffice/share/config/soffice.cfg/modules/simpress/ui/sidebarslidebackground.ui
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/layoutlist.xml
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/objectlist.xml
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/styles.xml


All of those are in -draw *and* draw-nogui (and those two conflict, so OK).

That's where they belong (well, probably not needed in -nogui but anyway.)


What looks missing indeed is some Replaces, I bumped them to go sure 
hopefully.


And as said in 7.6 it's fixed since the uiconfig-impress package should 
have the correct Replaces:



Regards,


Rene

Bug#1041884: sct: segfault at e0

[Alejandro Colomar]

Package: sct
Version: 1.3-1+b1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: alx.manpa...@gmail.com


Hi!

I'm not sure if this is a problem with sct(1), but I got an error that
mentions sct, so I'm reporting here in case it's related to sct(1).

Here's the error message as reported by dmesg:

$ sudo dmesg | tail -n2
[  432.416640] sct[3477]: segfault at e0 ip 555a975ee0fd sp 
7ffe887af340 error 4 in sct[555a975ee000+1000] likely on CPU 1 (core 1, 
socket 0)
[  432.416669] Code: 2f 00 00 66 90 00 00 00 00 00 00 00 00 41 57 41 56 41 55 
49 89 f5 41 54 55 53 89 fb 31 ff 48 83 ec 28 e8 86 ff ff ff 48 89 c5 <48> 63 80 
e0 00 00 00 48 89 ef 48 c1 e0 07 48 03 85 e8 00 00 00 48

My computer got a black screen where the only thing I could do is
REISUB.  It had a few problems booting after that for a few times.  I'm
still unsure about the cause, but this is the most notable error report
I've seen.

I have `sct 3000` in my .bash_aliases, so that just by opening a
terminal I get a nice screen temperature.  It has worked for a long
time...

Cheers,
Alex


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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

Versions of packages sct depends on:
ii  libc6   2.37-6
ii  libx11-62:1.8.6-1
ii  libxrandr2  2:1.5.2-2+b1

sct recommends no packages.

sct suggests no packages.

-- no debconf information

Bug#1041881: RM: winwrangler -- RoQA; depends on gtk2; low popcon

[Bastian Germann]

Source: winwrangler
Severity: serious

Please consider removing winwrangler. I guess there is no real use for it 
anymore.
I am going to reassign this to the FTP Masters if nobody reacts within a month.

Processed: bug 1041855 is forwarded to https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/ https://lore.kernel.org/lkml/11ded843-ac08-2306-ad0f-586978d03...@kernel.dk/raw

[Debian Bug Tracking System]

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

> forwarded 1041855 
> https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/ 
> https://lore.kernel.org/lkml/11ded843-ac08-2306-ad0f-586978d03...@kernel.dk/raw
Bug #1041855 [src:linux] linux-image-6.4.0-1-amd64: IO wait regression
Changed Bug forwarded-to-address to 
'https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/ 
https://lore.kernel.org/lkml/11ded843-ac08-2306-ad0f-586978d03...@kernel.dk/raw'
 from 'https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/'.
> thanks
Stopping processing here.

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

Processed: tagging 1041855

[Debian Bug Tracking System]

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

> tags 1041855 + upstream
Bug #1041855 [src:linux] linux-image-6.4.0-1-amd64: IO wait regression
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 1041855 is forwarded to https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/

[Debian Bug Tracking System]

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

> forwarded 1041855 
> https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/
Bug #1041855 [src:linux] linux-image-6.4.0-1-amd64: IO wait regression
Set Bug forwarded-to-address to 
'https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/'.
> thanks
Stopping processing here.

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

Processed: Bug#1041162 marked as pending in autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041162 [autopkgtest] autopkgtest should ignore ESO entries for pinning
Added tag(s) pending.

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

Bug#1041162: marked as pending in autopkgtest

[Paul Gevers]

Control: tag -1 pending

Hello,

Bug #1041162 in autopkgtest 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/ci-team/autopkgtest/-/commit/258d33bb820405cbe5897f2546d398eeb5337c13


adt_testbed: use dumpavail for pinning call to apt-cache

$(apt-cache showsrc $pkg) shows all packages available in the source,
including Extra-Source-Only entries. This can lead to unintended
failures.

Closes: #1041162


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041162

Bug#1041722: steam is incompatible with libgudev 238-2

[Simon McVittie]

On Sat, 22 Jul 2023 at 20:21:22 +0200, Felix Zielcke wrote:
> As soon as it enters testing more people are affected

steam-installer is at the same version in testing and unstable, and even
if it wasn't, holding back its migration with a RC bug wouldn't prevent
this crash, because the important parts of Steam auto-update themselves.

I'm surprised that you're seeing this crash, because it seems you already
have the factors that were mentioned in the upstream bug as potential
workarounds: libnm0:i386 is installed, and so is libudev0:i386.

Are these things that you installed as a (successful) workaround, but were
not present at the time that you saw the crash you're reporting?

If those have not been successful workarounds, some other packages you
could try installing (most likely solution first) are:

- libusb-1.0-0:i386
- libudev0:amd64
- libnm0:amd64
- libusb-1.0-0:amd64

Thanks,
smcv

Bug#1041876: nix FTBFS on !amd64

[Adrian Bunk]

Source: nix
Version: 2.16.1+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=nix=2.16.1%2Bdfsg-1

...
src/libcmd/repl.cc:18:10: fatal error: editline.h: No such file or directory
   18 | #include 
  |  ^~~~
compilation terminated.

Bug#1037624: marked as done (dpuser: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 18:34:37 +
with message-id 
and subject line Bug#1037624: fixed in dpuser 4.1+dfsg-2
has caused the Debian Bug report #1037624,
regarding dpuser: 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.)


-- 
1037624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dpuser
Version: 4.1+dfsg-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
../dpuser/dpuserAST.h:272:13: warning: ‘statementNode::id’ will be initialized 
after [-Wreorder]
  272 | int id;
  | ^~
../dpuser/dpuserAST.h:271:18: warning:   ‘ASTNode* statementNode::stmt’ 
[-Wreorder]
  271 | ASTNode *stmt = NULL;
  |  ^~~~
../dpuser/dpuserAST.h:273:9: warning:   when initialized here [-Wreorder]
  273 | statementNode(ASTNode *s) : id(0), stmt(s) { }
  | ^
../dpuser/dpuserAST.h: In destructor ‘virtual listNode::~listNode()’:
../dpuser/dpuserAST.h:284:49: warning: comparison of integer expressions of 
different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long 
unsigned int’} [-Wsign-compare]
  284 | virtual ~listNode() { for (int i = 0; i < list.size(); i++) 
delete list.at(i); }
  |   ~~^
../dpuser/dpuserAST.h: In destructor ‘virtual rangeNode::~rangeNode()’:
../dpuser/dpuserAST.h:295:46: warning: comparison of integer expressions of 
different signedness: ‘int’ and ‘std::vector::size_type’ {aka ‘long 
unsigned int’} [-Wsign-compare]
  295 | virtual ~rangeNode() { for (int i = 0; i < list.size(); i++) delete 
list.at(i); }
  |~~^
../dpuser/dpuserAST.h: In constructor 
‘extractrangeNode::extractrangeNode(ASTNode*, ASTNode*)’:
../dpuser/dpuserAST.h:310:14: warning: ‘extractrangeNode::argument’ will be 
initialized after [-Wreorder]
  310 | ASTNode *argument;
  |  ^~~~
../dpuser/dpuserAST.h:309:14: warning:   ‘ASTNode* extractrangeNode::range’ 
[-Wreorder]
  309 | ASTNode *range;
  |  ^
../dpuser/dpuserAST.h:311:5: warning:   when initialized here [-Wreorder]
  311 | extractrangeNode(ASTNode *arg, ASTNode *newrange) : argument(arg), 
range(newrange) { }
  | ^~~~
../dpuser/dpuserAST.h: In constructor ‘forloopNode::forloopNode(ASTNode*, 
ASTNode*, ASTNode*, ASTNode*)’:
../dpuser/dpuserAST.h:374:52: warning: ‘forloopNode::change’ will be 
initialized after [-Wreorder]
  374 | ASTNode *start, *check = NULL, *commands, *change = NULL, 
*limit = NULL;
  |^~
../dpuser/dpuserAST.h:374:41: warning:   ‘ASTNode* forloopNode::commands’ 
[-Wreorder]
  374 | ASTNode *start, *check = NULL, *commands, *change = NULL, 
*limit = NULL;
  | ^~~~
../dpuser/dpuserAST.h:375:9: warning:   when initialized here [-Wreorder]
  375 | forloopNode(ASTNode *s, ASTNode *c, ASTNode *e, ASTNode *co) : 
start(s), check(c), change(e), commands(co) { }
  | ^~~
../dpuser/dpuserAST.h: In constructor ‘forloopNode::forloopNode(ASTNode*, 
ASTNode*, ASTNode*)’:
../dpuser/dpuserAST.h:374:68: warning: ‘forloopNode::limit’ will be initialized 
after 

Bug#1037600: marked as done (casacore: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 18:34:28 +
with message-id 
and subject line Bug#1037600: fixed in casacore 3.5.0-3
has caused the Debian Bug report #1037600,
regarding casacore: 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.)


-- 
1037600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:casacore
Version: 3.5.0-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
  721 | reinterpret_cast(dest)[i] = symbolBuffer[i];
  |^
/<>/tables/Dysco/tests/../bytepacker.h:721:60: error: expected ‘)’ 
before ‘;’ token
  721 | reinterpret_cast(dest)[i] = symbolBuffer[i];
  |^
  |)
/<>/tables/Dysco/tests/../bytepacker.h: In static member function 
‘static void dyscostman::BytePacker::unpack16(unsigned int*, unsigned char*, 
size_t)’:
/<>/tables/Dysco/tests/../bytepacker.h:728:40: error: ‘uint16_t’ 
does not name a type
  728 | symbolBuffer[i] = reinterpret_cast(packedBuffer)[i];
  |^~~~
/<>/tables/Dysco/tests/../bytepacker.h:728:40: note: ‘uint16_t’ is 
defined in header ‘’; did you forget to ‘#include ’?
/<>/tables/Dysco/tests/../bytepacker.h:728:49: error: expected ‘>’ 
before ‘*’ token
  728 | symbolBuffer[i] = reinterpret_cast(packedBuffer)[i];
  | ^
/<>/tables/Dysco/tests/../bytepacker.h:728:49: error: expected ‘(’ 
before ‘*’ token
  728 | symbolBuffer[i] = reinterpret_cast(packedBuffer)[i];
  | ^
  | (
/<>/tables/Dysco/tests/../bytepacker.h:728:50: error: expected 
primary-expression before ‘>’ token
  728 | symbolBuffer[i] = reinterpret_cast(packedBuffer)[i];
  |  ^
/<>/tables/Dysco/tests/../bytepacker.h:728:68: error: expected ‘)’ 
before ‘;’ token
  728 | symbolBuffer[i] = reinterpret_cast(packedBuffer)[i];
  |^
  |)
make[3]: *** [tables/Dysco/CMakeFiles/tDysco.dir/build.make:93: 
tables/Dysco/CMakeFiles/tDysco.dir/tests/testbytepacking.cc.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:5890: 
tables/Dysco/CMakeFiles/tDysco.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs
[ 44%] Linking CXX executable tTable_3
cd /<>/obj-x86_64-linux-gnu/tables/Tables/test && /usr/bin/cmake 
-E cmake_link_script CMakeFiles/tTable_3.dir/link.txt --verbose=1
/usr/bin/c++ -fcx-fortran-rules -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11 -pthread -Wl,-z,relro -Wl,--as-needed -rdynamic 
CMakeFiles/tTable_3.dir/tTable_3.cc.o -o tTable_3  
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/tables:/<>/obj-x86_64-linux-gnu/casa
 ../../libcasa_tables.so.7 ../../../casa/libcasa_casa.so.7 
/usr/lib/x86_64-linux-gnu/libreadline.so -lncurses -lm -ldl 
-L/usr/lib/x86_64-linux-gnu -lgsl -lgslcblas -lm 
[ 44%] Linking CXX executable tVeryBigTable
cd 

Bug#1041871: bolt: collision with the former bolt package

[Daniel Vacek]

Package: bolt
Version: 1:16.0-57~exp2
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: neel...@gmail.com

The new dependency package from llvm-defaults steals the name from the old
thunderbolt package.

Bug#1041870: slic3r-prusa FTBFS on i386

[Adrian Bunk]

Source: slic3r-prusa
Version: 2.6.0+dfsg-1
Severity: serious
Tags: ftbfs patch
Forwarded: https://github.com/prusa3d/PrusaSlicer/pull/11036

https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=i386=2.6.0%2Bdfsg-1=1690032193=0

...
/<>/src/libslic3r/Format/AnycubicSLA.cpp:327:15: error: no 
matching function for call to ‘crop_value(float_t&, float, float)’
  327 | crop_value(h.delay_before_exposure_s, 0.0f, 1000.0f);
  | ~~^~
/<>/src/libslic3r/Format/AnycubicSLA.cpp:219:24: note: candidate: 
‘template void Slic3r::{anonymous}::crop_value(T&, T, T)’
...


Two fixes are required for fixing the build on i386
(and likely also some non-release 32bit architectures).

1. The patch from the pull request above, and

2. the following change:

--- debian/rules.old2023-07-24 15:36:20.941771419 +
+++ debian/rules2023-07-24 15:36:43.133759741 +
@@ -5,7 +5,7 @@
 # less debug info to avoid running out of address space
 ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
export DEB_CXXFLAGS_MAINT_APPEND += --param ggc-min-expand=5 -g0
-else ifneq (,$(filter $(DEB_HOST_ARCH), armhf))
+else ifeq ($(DEB_HOST_ARCH_BITS), 32)
export DEB_CXXFLAGS_MAINT_APPEND += -g1
 endif
 

Processed: [bts-link] source package src:libatomic-queue

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:libatomic-queue
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1037715 (http://bugs.debian.org/1037715)
> # Bug title: libatomic-queue: ftbfs with GCC-13
> #  * https://github.com/max0x7ba/atomic_queue/issues/55
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1037715 + fixed-upstream
Bug #1037715 [src:libatomic-queue] libatomic-queue: ftbfs with GCC-13
Added tag(s) fixed-upstream.
> usertags 1037715 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:syslog-ng

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:syslog-ng
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #46 (http://bugs.debian.org/46)
> # Bug title: syslog-ng: depends on obsolete pcre3 library
> #  * https://github.com/syslog-ng/syslog-ng/issues/4140
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 46 + fixed-upstream
Bug #46 [src:syslog-ng] syslog-ng: depends on obsolete pcre3 library
Added tag(s) fixed-upstream.
> usertags 46 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 46 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1041837 closed by René Engelhard (Re: Bug#1041837: libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= trixie: /usr/lib/libreoffice

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1041837 {Done: René Engelhard } [libreoffice-draw] 
libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= 
trixie: /usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Bug reopened
Ignoring request to alter fixed versions of bug #1041837 to the same values 
previously set
> found -1 4:7.5.5-2
Bug #1041837 [libreoffice-draw] libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Marked as found in versions libreoffice/4:7.5.5-2.
> found -1 4:7.5.5~rc1-2
Bug #1041837 [libreoffice-draw] libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Marked as found in versions libreoffice/4:7.5.5~rc1-2.

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

Bug#1041837: closed by René Engelhard (Re: Bug#1041837: libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= trixie: /usr/lib/libreoffice/share/config/

[Helmut Grohne]

Control: reopen -1
Control: found -1 4:7.5.5-2
Control: found -1 4:7.5.5~rc1-2

On Mon, Jul 24, 2023 at 08:09:07AM +, Debian Bug Tracking System wrote:
> 08:26 < helmut> _rene_: re libreoffice (short on time atm): seems like I 
> messed something up, please close my report. (...)

Further context here. On IRC you also said that this was fixed in
experimental. In reality, it is not.

libreoffice-draw version 4:7.5.5-2 (unstable) and 4:7.5.5~rc1-2
(experimental) contain the following files.

/usr/lib/libreoffice/share/config/soffice.cfg/simpress/layoutlist.xml
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/objectlist.xml

These are also contained in libreoffice-impress-nogui version 4:7.4.7-1
(bookworm and trixie). There is no Conflicts nor Replaces relation nor
is there any diversion.

As such, this is a serious bug.

Do you see any mistake in this analysis?

There is another conflict. libreoffice-draw-nogui version 4:7.5.5-2
(unstable) and 4:7.5.5~rc1-2 (experimental) contain the following files.

/usr/lib/libreoffice/share/config/soffice.cfg/modules/simpress/ui/sidebarslidebackground.ui
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/layoutlist.xml
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/objectlist.xml

These are also contained in libreoffice-impress version 4:7.4.7-1
(bookworm and trixie).

Furthermore, the latter two are also contained in
libreoffice-impress-nogui versoin 4:7.4.7-1 (bookworm and trixie).
Again, there is no Conflicts nor Replaces relation nor any diversion
that would prevent an unpack error.

Again, is there any mistake in this analysis?

Helmut

Bug#1041851: marked as done (cage: FTBFS with wlroots 0.16)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 17:20:30 +
with message-id 
and subject line Bug#1041851: fixed in cage 0.1.4+20230724-1
has caused the Debian Bug report #1041851,
regarding cage: FTBFS with wlroots 0.16
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=cage=amd64=0.1.4-4%2Bb1=1690184836=0

[3/12] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-Wpedantic -std=c11 -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/cage.c.o 
-MF cage.p/cage.c.o.d -o cage.p/cage.c.o -c ../cage.c
FAILED: cage.p/cage.c.o 
cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-Wpedantic -std=c11 -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/cage.c.o 
-MF cage.p/cage.c.o.d -o cage.p/cage.c.o -c ../cage.c
In file included from ../view.h:8,
 from ../seat.h:12,
 from ../server.h:16,
 from ../output.h:8,
 from ../cage.c:45:
/usr/include/wlr/types/wlr_surface.h:1:2: warning: #warning 
"wlr/types/wlr_surface.h has been deprecated and will be removed in the future. 
Use wlr/types/wlr_compositor.h and wlr/types/wlr_subcompositor.h." [-Wcpp]
1 | #warning "wlr/types/wlr_surface.h has been deprecated and will be 
removed in the future. Use wlr/types/wlr_compositor.h and 
wlr/types/wlr_subcompositor.h."
  |  ^~~
../cage.c: In function ‘main’:
../cage.c:389:21: error: too few arguments to function ‘wlr_xdg_shell_create’
  389 | xdg_shell = wlr_xdg_shell_create(server.wl_display);
  | ^~~~
In file included from /usr/include/wlr/types/wlr_xdg_decoration_v1.h:5,
 from ../cage.c:36:
/usr/include/wlr/types/wlr_xdg_shell.h:315:23: note: declared here
  315 | struct wlr_xdg_shell *wlr_xdg_shell_create(struct wl_display *display,
  |   ^~~~
../cage.c:508:38: error: too few arguments to function 
‘wlr_output_layout_get_box’
  508 | struct wlr_box *layout_box = 
wlr_output_layout_get_box(server.output_layout, NULL);
  |  ^
In file included from ../cage.c:30:
/usr/include/wlr/types/wlr_output_layout.h:110:6: note: declared here
  110 | void wlr_output_layout_get_box(struct wlr_output_layout *layout,
  |  ^
[4/12] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-Wpedantic -std=c11 -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
cage.p/idle_inhibit_v1.c.o -MF cage.p/idle_inhibit_v1.c.o.d -o 
cage.p/idle_inhibit_v1.c.o -c ../idle_inhibit_v1.c
In file included from ../view.h:8,
 from ../output.h:9,
 from ../server.h:15,
 from ../idle_inhibit_v1.c:15:
/usr/include/wlr/types/wlr_surface.h:1:2: warning: #warning 
"wlr/types/wlr_surface.h has been deprecated and will be removed in the future. 
Use wlr/types/wlr_compositor.h and wlr/types/wlr_subcompositor.h." [-Wcpp]
1 | #warning "wlr/types/wlr_surface.h has been deprecated and will be 
removed in the future. Use wlr/types/wlr_compositor.h and 
wlr/types/wlr_subcompositor.h."
  |  ^~~
[5/12] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-Wpedantic -std=c11 -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
cage.p/render.c.o -MF cage.p/render

Bug#1041863: marked as done (amd64-microcode: CVE-2023-20593: use-after-free in AMD Zen2 processors)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 16:49:02 +
with message-id 
and subject line Bug#1041863: fixed in amd64-microcode 3.20230719.1
has caused the Debian Bug report #1041863,
regarding amd64-microcode: CVE-2023-20593: use-after-free in AMD Zen2 processors
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.)


-- 
1041863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: amd64-microcode
Version: 3.20230414.1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1  3.20191218.1

Hi,

The following vulnerability was published for amd64-microcode.

CVE-2023-20593[0]:
| use-after-free in AMD Zen2 processors

Merge request at [2].

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-20593
https://www.cve.org/CVERecord?id=CVE-2023-20593
[1] https://lock.cmpxchg8b.com/zenbleed.html
[2] https://salsa.debian.org/hmh/amd64-microcode/-/merge_requests/5

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: amd64-microcode
Source-Version: 3.20230719.1
Done: Henrique de Moraes Holschuh 

We believe that the bug you reported is fixed in the latest version of
amd64-microcode, 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.
Henrique de Moraes Holschuh  (supplier of updated 
amd64-microcode 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: Mon, 24 Jul 2023 13:07:34 -0300
Source: amd64-microcode
Architecture: source
Version: 3.20230719.1
Distribution: unstable
Urgency: high
Maintainer: Henrique de Moraes Holschuh 
Changed-By: Henrique de Moraes Holschuh 
Closes: 1041863
Changes:
 amd64-microcode (3.20230719.1) unstable; urgency=high
 .
   * Update package data from linux-firmware 20230625-39-g59fbffa9:
 * Fixes for CVE-2023-20593 "Zenbleed" on AMD Zen2 processors
   (closes: #1041863)
 * New Microcode patches:
   + Family=0x17 Model=0xa0 Stepping=0x00: Patch=0x08a8
 * Updated Microcode patches:
   + Family=0x17 Model=0x31 Stepping=0x00: Patch=0x0830107a
   + Family=0x19 Model=0x01 Stepping=0x00: Patch=0x0a001079
   + Family=0x19 Model=0x01 Stepping=0x01: Patch=0x0a0011d1
   + Family=0x19 Model=0x01 Stepping=0x02: Patch=0x0a001234
   * README: update for new release
Checksums-Sha1:
 1263b79d06590da1853024c4a00e3766336fb0a8 1695 amd64-microcode_3.20230719.1.dsc
 72c9fa45ac3882c8804e72a7f8f2c5ffee48e840 120676 
amd64-microcode_3.20230719.1.tar.xz
 b4e617ab310d5f633e0c486f7a5cf48fbed49e48 6680 
amd64-microcode_3.20230719.1_amd64.buildinfo
Checksums-Sha256:
 7038054ec4fe57add514dd3b4683617bd5781b24d3a6a1ce144035e47d147fec 1695 
amd64-microcode_3.20230719.1.dsc
 c6942f14f798056f26ec9eeae93e03f57975e513ef07f4173366f0cb519d2a30 120676 
amd64-microcode_3.20230719.1.tar.xz
 485421994a42d167e3201cac193f21161afa82bc8e6f7f4f495dd2821f8bebe2 6680 
amd64-microcode_3.20230719.1_amd64.buildinfo
Files:
 62073b5eca489f0bab7984f88aad24ef 1695 non-free-firmware/admin standard 
amd64-microcode_3.20230719.1.dsc
 026554c25951d0f410933e1a67d43a5c 120676 non-free-firmware/admin standard 
amd64-microcode_3.20230719.1.tar.xz
 41f75b81b241f5969459b919c8b44450 6680 non-free-firmware/admin standard 
amd64-microcode_3.20230719.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIXEYtQeAQUHyKjs9TkVcVzAplOQFAmS+prMACgkQTkVcVzAp
lOQHTw/+K8avtXUHKXH/f7VvF8g65sd1BCKrEWHb2snJcrhulAlnOB7y9xrlf25T
H0vLlJVUAqc7MVf5PJpJJS6EC3MXznXaZlJElpcGIQWt1J/CoU+GjfCxyegxo3G9
LFRin4/zZJmP7R4XlKZ7OTYo0sMO1Wc+8rCFAmgRQnvKiTwCyCcp7nkaVMOP0BO3
oiJNh0q6JJajRV4Tv18kaRq28MwtxN4kFa0LgoUowlsz4dmmz4xuQv/zuYx+U40z
l+MxqTLiNIPt/VAxwyuwXPsZyCcJ7f2jO9q55y0+HxDy0wU5cH6tCsLskNocdNZF
fGebiIKk+1VI6yM+WWCmFtUMd1Tk/R1BQalDs3rFFpOQIj0mSRFzX//1WrYqu75i
ttu9rvhQZAJAE89aC4WuBkG3THMvjBKavRlpjyIp81wq5t98/hKhDjMB47hwKT+y

Processed: libcoq-paramcoq no longer depends on libcoq-stdlib-*

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:coqeal
Bug #1041869 [libcoq-paramcoq] libcoq-paramcoq no longer depends on 
libcoq-stdlib-*
Added indication that 1041869 affects src:coqeal

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

Bug#1041869: libcoq-paramcoq no longer depends on libcoq-stdlib-*

[Adrian Bunk]

Package: libcoq-paramcoq
Version: 1.1.3+coq8.17-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:coqeal

Package: libcoq-paramcoq
Version: 1.1.3+coq8.17-1+b1
Depends: libcoq-stdlib (>= 8.17)

Package: libcoq-paramcoq
Version: 1.1.3+coq8.16-3+b1
Depends: libcoq-stdlib-ewsr6


This was likely the root cause of
https://buildd.debian.org/status/fetch.php?pkg=coqeal=amd64=1.1.3-1%2Bb1=1690189656=0

Bug#1041867: tests fail blocking migration

[Jonathan Wiltshire]

Source: node-dottie
Version: 2.0.6+~2.0.5-1
Severity: serious
X-Debbugs-Cc: j...@debian.org

Hi,

The version of node-dottie in sid does not migrate because of a
regression in its tests:

| 91s   46 passing (25ms)
| 91s   2 failing
| 91s 
| 91s   1) dottie.set
| 91sshould not attempt to set __proto__:
| 91s  Error: Accessing Object.prototype.__proto__ has been disallowed with 
--disable-proto=throw
| 91s   at Context. (test/set.test.js:74:17)
| 91s   at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21)
| 91s   at Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5)
| 91s   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:666:10)
| 91s   at /usr/share/nodejs/mocha/lib/runner.js:789:12
| 91s   at next (/usr/share/nodejs/mocha/lib/runner.js:581:14)
| 91s   at /usr/share/nodejs/mocha/lib/runner.js:591:7
| 91s   at next (/usr/share/nodejs/mocha/lib/runner.js:474:14)
| 91s   at Immediate._onImmediate 
(/usr/share/nodejs/mocha/lib/runner.js:559:5)
| 91s   at process.processImmediate (node:internal/timers:471:21)
| 91s 
| 91s   2) dottie.transform
| 91sshould guard against prototype pollution:
| 91s  Error: Accessing Object.prototype.__proto__ has been disallowed with 
--disable-proto=throw
| 91s   at Context. (test/transform.test.js:158:24)
| 91s   at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21)
| 91s   at Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5)
| 91s   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:666:10)
| 91s   at /usr/share/nodejs/mocha/lib/runner.js:789:12
| 91s   at next (/usr/share/nodejs/mocha/lib/runner.js:581:14)
| 91s   at /usr/share/nodejs/mocha/lib/runner.js:591:7
| 91s   at next (/usr/share/nodejs/mocha/lib/runner.js:474:14)
| 91s   at Immediate._onImmediate 
(/usr/share/nodejs/mocha/lib/runner.js:559:5)
| 91s   at process.processImmediate (node:internal/timers:471:21)
| 91s 
| 91s 
| 91s 
| 91s autopkgtest [15:29:22]: test pkg-js-autopkgtest: ---]
| 91s autopkgtest [15:29:22]: test pkg-js-autopkgtest:  - - - - - - - - - - 
results - - - - - - - - - -
| 91s pkg-js-autopkgtest   FAIL non-zero exit status 2
| 91s autopkgtest [15:29:22]:  summary
| 91s pkg-js-autopkgtest-require PASS (superficial)
| 91s pkg-js-autopkgtest   FAIL non-zero exit status 2

(https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-dottie/36116500/log.gz)

Because of the migration blockage, updates for bullseye and bookworm are
also blocked because of version constraints.

-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#1041836: Version Correction

[Mike Bird]

Please note that the bug is in version 2.36-9+deb12u1 i.e. the
new version just released to Stable.

reportbug saw 2.36-9 because I had to revert to the previous
version before anything but static executables would work.

--Mike

Bug#1035732: marked as done (libkscreenlocker5: Endless loop when using PAM)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 16:32:24 +
with message-id 
and subject line Bug#1035732: fixed in kscreenlocker 5.20.5-1+deb11u1
has caused the Debian Bug report #1035732,
regarding libkscreenlocker5: Endless loop when using PAM
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.)


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

Package: libkscreenlocker5
Version: 5.20.5-1
Severity: critical
Tags: patch upstream
Justification: breaks the whole system

Dear Maintainer,

* What led up to the situation?

A variation of upstream bug report https://bugs.kde.org/show_bug.cgi?id=438099

pam-configuration with
auth[success=2 default=ignore]  pam_krb5.so minimum_uid=1000
auth[success=1 default=ignore]  pam_unix.so nullok 
try_first_pass
authrequisite   pam_deny.so
and
pressing "enter" to unlock the screen without entering a password.

   * What was the outcome of this action?

Endless loop of

kcheckpass[74114]: pam_krb5(kde:auth): pam_sm_authenticate: entry
kcheckpass[74114]: pam_krb5(kde:auth): (user ) error getting password: 
Conversation error
kcheckpass[74114]: pam_krb5(kde:auth): authentication failure; logname= 
uid= euid= tty=:1 ruser= rhost=
kcheckpass[74114]: pam_krb5(kde:auth): pam_sm_authenticate: exit (failure)
kcheckpass[74114]: pam_unix(kde:auth): conversation failed
kcheckpass[74114]: pam_unix(kde:auth): auth could not identify password for 
[]

(here more than 250 times / second)
till next unlock attempt with a password.
Flooding /var/log/auth.log and central authentication services.
(Thus an unintentional "enter" on a locked screen can result in at least  
completely filled disks.)


* What outcome did you expect instead?

Authentication failure.

Please include the short patch
https://invent.kde.org/plasma/kscreenlocker/-/commit/fca315cf72826f93eda7a026016b33818b9d1f39
to kscreenlocker-5.20.5 in bullseye.

The critical part has been completely rewritten in kscreenlocker-5.27.2
(testing) and the problem probably doesn't apply there.

Best regards,
Andreas Poenicke

BTW:
Hotfix:

Separate /etc/pam.d/kde configuration with "use_first_pass" instead of
"try_first_pass", like

auth[success=2 default=ignore]  pam_krb5.so minimum_uid=1000
auth[success=1 default=ignore]  pam_unix.so use_first_pass
authrequisite   pam_deny.so

Which should be ok for kscreenlocker in most cases.





-- System Information:
Debian Release: 11.7
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-22-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:de
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libkscreenlocker5 depends on:
ii  kpackagetool5  5.78.0-3
ii  libc6  2.31-13+deb11u6
ii  libkf5configcore5  5.78.0-4
ii  libkf5configgui5   5.78.0-4
ii  libkf5coreaddons5  5.78.0-4
ii  libkf5crash5   5.78.0-3
ii  libkf5declarative5 5.78.0-2
ii  libkf5globalaccel-bin  5.78.0-3
ii  libkf5globalaccel5 5.78.0-3
ii  libkf5i18n55.78.0-2
ii  libkf5idletime55.78.0-2
ii  libkf5notifications5   5.78.0-2
ii  libkf5package5 5.78.0-3
ii  libkf5quickaddons5 5.78.0-2
ii  libkf5waylandclient5   4:5.78.0-2
ii  libkf5waylandserver5   4:5.78.0-2
ii  libkf5windowsystem55.78.0-2
ii  libkf5xmlgui5  5.78.0-2
ii  libpam0g   1.4.0-9+deb11u1
ii  libqt5core5a   5.15.2+dfsg-9
ii  libqt5dbus55.15.2+dfsg-9
ii  libqt5gui5 5.15.2+dfsg-9
ii  libqt5network5 5.15.2+dfsg-9
ii  libqt5qml5 5.15.2+dfsg-6
ii  libqt5quick5   5.15.2+dfsg-6
ii  libqt5widgets5 5.15.2+dfsg-9
ii  libqt5x11extras5   5.15.2-2
ii  libstdc++6 10.2.1-6
ii  libwayland-client0 1.18.0-2~exp1.1
ii  libwayland-server0 1.18.0-2~exp1.1
ii  libx11-6   2:1.7.2-1
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb11.14-3
ii  libxi6 2:1.7.10-1
ii  psmisc 23.4-2

Versions of packages libkscreenlocker5 recommends:
ii  kde-config-screenlocker  5.20.5-1

libkscreenlocker5 suggests no packages.

-- no debconf information

--
Karlsruher Institut für Technologie
Institut für Theoretische Festkörperphysik

Processed: Re: Bug#1041435: fixed in bitsnpicas 2.0+ds-2

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1041435 {Done: Gürkan Myczko } [bitsnpicas] bitsnpicas: 
unusable, chokes with nullptr exception
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions bitsnpicas/2.0+ds-2.
> retitle -1 bitsnpicas: Contains potentially non-free binary unicode data
Bug #1041435 [bitsnpicas] bitsnpicas: unusable, chokes with nullptr exception
Changed Bug title to 'bitsnpicas: Contains potentially non-free binary unicode 
data' from 'bitsnpicas: unusable, chokes with nullptr exception'.
> found -1 2.0+ds-2
Bug #1041435 [bitsnpicas] bitsnpicas: Contains potentially non-free binary 
unicode data
Marked as found in versions bitsnpicas/2.0+ds-2.

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

Bug#1041435: fixed in bitsnpicas 2.0+ds-2

[Nilesh Patra]

Control: reopen -1
Control: retitle -1 bitsnpicas: Contains potentially non-free binary unicode 
data
Control: found -1 2.0+ds-2

On Mon, 24 Jul 2023 13:20:33 + Debian FTP Masters 
 wrote:
>  bitsnpicas (2.0+ds-2) unstable; urgency=medium
>  .
>* Apply patch to fix usability. (Closes: #1041435)
>  Thank you Nilesh Patra.

Thanks for applying my patch, it is atleast usable now. However, this
part of the bug still remains un-fixed, which would mean potentially
pushing non-free software into main.

I've thus retitled the bug and reopened it.

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: amd64-microcode: CVE-2023-20593: use-after-free in AMD Zen2 processors

[Debian Bug Tracking System]

Processing control commands:

> found -1  3.20191218.1
Bug #1041863 [src:amd64-microcode] amd64-microcode: CVE-2023-20593: 
use-after-free in AMD Zen2 processors
Marked as found in versions amd64-microcode/3.20191218.1.

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

Bug#1041863: amd64-microcode: CVE-2023-20593: use-after-free in AMD Zen2 processors

[Salvatore Bonaccorso]

Source: amd64-microcode
Version: 3.20230414.1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1  3.20191218.1

Hi,

The following vulnerability was published for amd64-microcode.

CVE-2023-20593[0]:
| use-after-free in AMD Zen2 processors

Merge request at [2].

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-20593
https://www.cve.org/CVERecord?id=CVE-2023-20593
[1] https://lock.cmpxchg8b.com/zenbleed.html
[2] https://salsa.debian.org/hmh/amd64-microcode/-/merge_requests/5

Regards,
Salvatore

Bug#999966: Pending fix

[Sylvestre Ledru]

Le 24/07/2023 à 15:45, Pierre Gruet a écrit :

Hi again,

Le 24/07/2023 à 14:15, Sylvestre Ledru a écrit :

Le 24/07/2023 à 14:07, Pierre Gruet a écrit :

Hi Sylvestre,


[...]


As it is changing the behavior of the language, I feel that it is a 
bit risky to do such changes this way.
It might break scilab script between the upstream implementation and 
the Debian/Ubuntu packages.


For example:
-[Mss, comments] = csvRead(filename, ";" , [] , "string" , [] ,"/foo 
bar/");
+[Mss, comments] = csvRead(filename, ";" , [] , "string" , [] ,"foo 
bar");


Maybe you could automatically remove the trailing and ending "/" 
before passing them to PCRE, no?


Thanks again for looking at the patch.

What you suggest is to write some handle_pattern function taking 
patterns with delimiters and returning them without the delimiters and 
possibly without the backslashes escaping the delimiter character 
inside the pattern, right?


Also, logically following would be looking at modifiers after the 
final delimiter and translating them into the right options for 
compiling the pattern?
yeah, in the gateway, removing / / on the fly  when processing the input 
arguments


Do you think one needs to account for modifiers othen than "imx"?


Dunno, I don't know how often they are used and how :(

Cheers

S

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Andrea Pappacoda]

Il giorno lun 24 lug 2023 alle 09:05:30 +02:00:00, Sebastian Ramacher 
 ha scritto:
Please prepare transitions in experimental first. This would avoid 
such

issues.

If there are no news regarding a fix for this bug, please revert
cpp-httplib 0.11.4 to get back to a good state.


Hi, I'll be sure to do it next time. I've looked into this, but I 
couldn't find any change which would cause test failures on s390x 
specifically. cpp-httplib's test suite is a bit flaky though, so it may 
have been just an unlucky run (this is an issue in itself, but I have 
already reported it upstream and it didn't get much attention). Is it 
possible to re-try the build?


Thanks :)

--
OpenPGP key: 66DE F152 8299 0C21 99EF  A801 A8A1 28A8 AB1C EE49

Bug#999966: Pending fix

[Pierre Gruet]

Hi again,

Le 24/07/2023 à 14:15, Sylvestre Ledru a écrit :

Le 24/07/2023 à 14:07, Pierre Gruet a écrit :

Hi Sylvestre,


[...]


As it is changing the behavior of the language, I feel that it is a bit 
risky to do such changes this way.
It might break scilab script between the upstream implementation and the 
Debian/Ubuntu packages.


For example:
-[Mss, comments] = csvRead(filename, ";" , [] , "string" , [] ,"/foo 
bar/");

+[Mss, comments] = csvRead(filename, ";" , [] , "string" , [] ,"foo bar");

Maybe you could automatically remove the trailing and ending "/" before 
passing them to PCRE, no?


Thanks again for looking at the patch.

What you suggest is to write some handle_pattern function taking 
patterns with delimiters and returning them without the delimiters and 
possibly without the backslashes escaping the delimiter character inside 
the pattern, right?


Also, logically following would be looking at modifiers after the final 
delimiter and translating them into the right options for compiling the 
pattern?


Do you think one needs to account for modifiers othen than "imx"?



Cheers,
Sylvestre




Best,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041855: linux-image-6.4.0-1-amd64: IO wait regression

[Christian Göttsche]

Package: src:linux
Version: 6.4.4-1
Severity: serious

Dear Maintainer,

Kernel 6.4.4 is affected by a regression causing one core be report
high IO wait utilization.

See https://lore.kernel.org/lkml/12251678.o9o76zd...@natalenko.name/

Processed: Re: naev: FTBFS on mips64el

[Debian Bug Tracking System]

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

> affects 1041454 src:evince src:glibmm2.68 src:gnome-builder src:gjs
Bug #1041454 [meson] naev: FTBFS on mips64el
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 1041454 affects src:evince, src:glibmm2.68, 
src:gnome-builder, and src:gjs
Added indication that 1041499 affects src:evince, src:glibmm2.68, 
src:gnome-builder, and src:gjs
> affects 1041454 src:gobject-introspection
Bug #1041454 [meson] naev: FTBFS on mips64el
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 1041454 affects src:gobject-introspection
Added indication that 1041499 affects src:gobject-introspection
>
End of message, 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#1041435: marked as done (bitsnpicas: unusable, chokes with nullptr exception)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 13:20:33 +
with message-id 
and subject line Bug#1041435: fixed in bitsnpicas 2.0+ds-2
has caused the Debian Bug report #1041435,
regarding bitsnpicas: unusable, chokes with nullptr exception
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.)


-- 
1041435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bitsnpicas
Version: 2.0+ds-1
Severity: serious
X-Debbugs-Cc: t...@debian.org

Dear Maintainer,

bitsnpicas is currently unusable and chokes with:

$ bitsnpicas
Exception in thread "main" java.lang.NullPointerException
at java.base/java.io.Reader.(Reader.java:168)
at java.base/java.io.InputStreamReader.(InputStreamReader.java:76)
at java.base/java.util.Scanner.(Scanner.java:566)
at com.kreative.unicode.data.Encoding.(Encoding.java:26)
at com.kreative.unicode.data.EncodingList.(EncodingList.java:58)
at com.kreative.unicode.data.EncodingList.instance(EncodingList.java:20)
at 
com.kreative.bitsnpicas.edit.GlyphListModelList$GlyphListModelRootNode.(GlyphListModelList.java:93)
at 
com.kreative.bitsnpicas.edit.GlyphListModelList.(GlyphListModelList.java:29)
at 
com.kreative.bitsnpicas.edit.GlyphListPanel.(GlyphListPanel.java:34)
at 
com.kreative.bitsnpicas.edit.BitmapListFrame.(BitmapListFrame.java:19)
at com.kreative.bitsnpicas.edit.Main.openFont(Main.java:158)
at com.kreative.bitsnpicas.edit.Main.newBitmapFont(Main.java:71)
at com.kreative.bitsnpicas.edit.Main.main(Main.java:55)
at com.kreative.bitsnpicas.main.Main.main(Main.java:12)

This is because of the exclusion of following files w/o patching the
code properly

 main/java/BitsNPicas/src/com/kreative/unicode/mappings/Mac*.txt
 main/java/BitsNPicas/src/com/kreative/unicode/mappings/Windows*.txt
 main/java/BitsNPicas/src/com/kreative/unicode/mappings/IBM*.txt

I applied a patch trying to exclude unicodes and can get it to a usable state. 
The patch is
attached with this bug report. However, even after being able to launch
the menu, I see windows and IBM related unicode options in the menu. I
did not dive deep into the code, but it could be stemming from

main/java/BitsNPicas/src/com/kreative/unicode/data/unidata.ucd

In which case the unicode bin itself contains non-free content and needs
fixing accordingly.

Thanks,
Nilesh

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages bitsnpicas depends on:
ii  xdg-utils  1.1.3-4.1

bitsnpicas recommends no packages.

bitsnpicas suggests no packages.

-- no debconf information
diff --git a/main/java/BitsNPicas/Makefile b/main/java/BitsNPicas/Makefile
index d339248..3955afc 100644
--- a/main/java/BitsNPicas/Makefile
+++ b/main/java/BitsNPicas/Makefile
@@ -48,47 +48,16 @@ BitsNPicas.jar: bin
 	jar cmf dep/MANIFEST.MF BitsNPicas.jar -C bin com/kreative/unicode -C bin com/kreative/bitsnpicas
 	chmod +x BitsNPicas.jar
 
-BitsNPicas.app: BitsNPicas-Pre10.15.app BitsNPicas-MacOS10.15.app BitsNPicas-MacOS11.0.app
+BitsNPicas.app: BitsNPicas-Pre10.15.app
 
 BitsNPicas-Pre10.15.app: dep BitsNPicas.jar
-	mkdir -p BitsNPicas-Pre10.15.app/Contents/MacOS
 	mkdir -p BitsNPicas-Pre10.15.app/Contents/Resources/Java
 	cp -f dep/PkgInfo BitsNPicas-Pre10.15.app/Contents
 	cp -f dep/Info.plist BitsNPicas-Pre10.15.app/Contents
-	cp -f dep/universalJavaApplicationStub-Pre10.15 BitsNPicas-Pre10.15.app/Contents/MacOS/BitsNPicas
 	cp -f dep/kbnp*.icns dep/dmov*.icns dep/movr*.icns BitsNPicas-Pre10.15.app/Contents/Resources
 	cp -f dep/*.jar BitsNPicas-Pre10.15.app/Contents/Resources/Java
 	cp -f BitsNPicas.jar BitsNPicas-Pre10.15.app/Contents/Resources/Java
 
-BitsNPicas-MacOS10.15.app: dep BitsNPicas.jar
-	mkdir -p BitsNPicas-MacOS10.15.app/Contents/MacOS
-	mkdir -p BitsNPicas-MacOS10.15.app/Contents/Resources/Java
-	cp -f dep/PkgInfo BitsNPicas-MacOS10.15.app/Contents
-	cp -f dep/Info.plist BitsNPicas-MacOS10.15.app/Contents
-	cp -f dep/universalJavaApplicationStub-MacOS10.15 BitsNPicas-MacOS10.15.app/Contents/MacOS/BitsNPicas
-	cp -f dep/kbnp*.icns dep/dmov*.icns dep/movr*.icns BitsNPicas-MacOS10.15.app/Contents/Resources
-	cp -f dep/*.jar 

Processed: cmake 3.27.0-1 causes sundials FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:sundials
Bug #1041853 [cmake] cmake 3.27.0-1 causes sundials FTBFS
Added indication that 1041853 affects src:sundials

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

Bug#1037663: foma: ftbfs with GCC-13

[Gunnar Hjalmarsson]

Control: affects -1 ibus-typing-booster

Thanks for the upstream PR with a fix, Tino. Considering that upstream 
is not so alert, do you plan to add the fix as a patch? I suspect the 
autoremoval 'threat' affects several other packages.


--
Cheers,

Gunnar Hjalmarsson

Processed: Re: Bug#1037663: foma: ftbfs with GCC-13

[Debian Bug Tracking System]

Processing control commands:

> affects -1 ibus-typing-booster
Bug #1037663 [src:foma] foma: ftbfs with GCC-13
Added indication that 1037663 affects ibus-typing-booster

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

Bug#1041853: cmake 3.27.0-1 causes sundials FTBFS

[Adrian Bunk]

Package: cmake
Version: 3.27.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:sundials

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

...
Fatal Error: Cannot open module file 'fsundials_profiler_mod.mod' for reading 
at (1): No such file or directory
compilation terminated.
make[3]: *** 
[src/sundials/fmod/CMakeFiles/sundials_fgeneric_mod_obj_shared.dir/build.make:267:
 
src/sundials/fmod/CMakeFiles/sundials_fgeneric_mod_obj_shared.dir/fsundials_context_mod.f90.o]
 Error 1



Downgrading cmake to 3.26.4-4 fixes the build.

Bug#1041851: cage: FTBFS with wlroots 0.16

[Sebastian Ramacher]

Source: cage
Version: 0.1.4-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=cage=amd64=0.1.4-4%2Bb1=1690184836=0

[3/12] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-Wpedantic -std=c11 -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/cage.c.o 
-MF cage.p/cage.c.o.d -o cage.p/cage.c.o -c ../cage.c
FAILED: cage.p/cage.c.o 
cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-Wpedantic -std=c11 -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ cage.p/cage.c.o 
-MF cage.p/cage.c.o.d -o cage.p/cage.c.o -c ../cage.c
In file included from ../view.h:8,
 from ../seat.h:12,
 from ../server.h:16,
 from ../output.h:8,
 from ../cage.c:45:
/usr/include/wlr/types/wlr_surface.h:1:2: warning: #warning 
"wlr/types/wlr_surface.h has been deprecated and will be removed in the future. 
Use wlr/types/wlr_compositor.h and wlr/types/wlr_subcompositor.h." [-Wcpp]
1 | #warning "wlr/types/wlr_surface.h has been deprecated and will be 
removed in the future. Use wlr/types/wlr_compositor.h and 
wlr/types/wlr_subcompositor.h."
  |  ^~~
../cage.c: In function ‘main’:
../cage.c:389:21: error: too few arguments to function ‘wlr_xdg_shell_create’
  389 | xdg_shell = wlr_xdg_shell_create(server.wl_display);
  | ^~~~
In file included from /usr/include/wlr/types/wlr_xdg_decoration_v1.h:5,
 from ../cage.c:36:
/usr/include/wlr/types/wlr_xdg_shell.h:315:23: note: declared here
  315 | struct wlr_xdg_shell *wlr_xdg_shell_create(struct wl_display *display,
  |   ^~~~
../cage.c:508:38: error: too few arguments to function 
‘wlr_output_layout_get_box’
  508 | struct wlr_box *layout_box = 
wlr_output_layout_get_box(server.output_layout, NULL);
  |  ^
In file included from ../cage.c:30:
/usr/include/wlr/types/wlr_output_layout.h:110:6: note: declared here
  110 | void wlr_output_layout_get_box(struct wlr_output_layout *layout,
  |  ^
[4/12] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-Wpedantic -std=c11 -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
cage.p/idle_inhibit_v1.c.o -MF cage.p/idle_inhibit_v1.c.o.d -o 
cage.p/idle_inhibit_v1.c.o -c ../idle_inhibit_v1.c
In file included from ../view.h:8,
 from ../output.h:9,
 from ../server.h:15,
 from ../idle_inhibit_v1.c:15:
/usr/include/wlr/types/wlr_surface.h:1:2: warning: #warning 
"wlr/types/wlr_surface.h has been deprecated and will be removed in the future. 
Use wlr/types/wlr_compositor.h and wlr/types/wlr_subcompositor.h." [-Wcpp]
1 | #warning "wlr/types/wlr_surface.h has been deprecated and will be 
removed in the future. Use wlr/types/wlr_compositor.h and 
wlr/types/wlr_subcompositor.h."
  |  ^~~
[5/12] cc -Icage.p -I. -I.. -I/usr/include/libdrm -I/usr/include/pixman-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-Wpedantic -std=c11 -DWLR_USE_UNSTABLE -Wall -Wundef -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
cage.p/render.c.o -MF cage.p/render.c.o.d -o cage.p/render.c.o -c ../render.c
In file included from ../render.c:16:
/usr/include/wlr/types/wlr_surface.h:1:2: warning: #warning 
"wlr/types/wlr_surface.h has been deprecated and will be removed in the future. 
Use wlr/types/wlr_compositor.h and wlr/types/wlr_subcompositor.h." [-Wcpp]
1 | #warning "wlr/types/wlr_surface.h has been deprecated and will be 
removed in the future. Use wlr/types/wlr_compositor.h and 
wlr/types/wlr_subcompositor.h."
  |  ^~~
In file included from ../view.h:8,
 from ../seat.h:12,
 from ../server.h:16,
 from ../output.h:8,
 from ../render.c:21:
/usr/include/wlr/types/wlr_surface.h:1:2: warning: #warning 
"wlr/types/wlr_surface.h has been deprecated and will be removed in the future. 
Use wlr/types/wlr_compositor.h and wlr/types/wlr_subcompositor.h." 

Bug#1041850: phoc: FTBFS with wlroots 0.16.

[Sebastian Ramacher]

Source: phoc
Version: 0.29.0+ds-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=phoc=amd64=0.29.0%2Bds-1%2Bb1=1690184504=0

Dependency wlroots found: NO found 0.16.2 but need: '== 0.15.1'
Dependency lookup for wlroots with method 'pkgconfig' failed: Invalid version, 
need 'wlroots' ['== 0.15.1'] found '0.16.2'.
CMake binary for 1 is not cached
CMake binary missing from cross or native file, or env var undefined.
Trying a default CMake fallback at cmake
Did not find CMake 'cmake'
Found CMake: NO
Dependency lookup for wlroots with method 'cmake' failed: CMake binary for 
machine 1 not found. Giving up.
Run-time dependency wlroots found: NO 

../meson.build:72:18: ERROR: Dependency lookup for wlroots with method 
'pkgconfig' failed: Invalid version, need 'wlroots' ['== 0.15.1'] found 
'0.16.2'.
dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup 
.. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dembed-wlroots=disabled 
-Dman=true returned exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-arch] Error 2


Cheers
-- 
Sebastian Ramacher

Bug#999966: Pending fix

[Sylvestre Ledru]

Le 24/07/2023 à 14:07, Pierre Gruet a écrit :

Hi Sylvestre,

Le 24/07/2023 à 13:54, Sylvestre Ledru a écrit :

Cool stuff. Could you please push your change to the repo ? :)
thanks
S


Sure, done! 

Thanks

> Any opinion from you on that matter will be appreciated :)

As it is changing the behavior of the language, I feel that it is a bit risky 
to do such changes this way.
It might break scilab script between the upstream implementation and the 
Debian/Ubuntu packages.

For example:
-[Mss, comments] = csvRead(filename, ";" , [] , "string" , [] ,"/foo bar/");
+[Mss, comments] = csvRead(filename, ";" , [] , "string" , [] ,"foo bar");

Maybe you could automatically remove the trailing and ending "/" before passing 
them to PCRE, no?

Cheers,
Sylvestre

Bug#1037910: marked as done (zynaddsubfx: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 12:12:34 +
with message-id 
and subject line Bug#1037910: fixed in zynaddsubfx 3.0.6-6
has caused the Debian Bug report #1037910,
regarding zynaddsubfx: 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.)


-- 
1037910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zynaddsubfx
Version: 3.0.6-5
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

Bug#1037707: marked as done (keyman: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 12:05:34 +
with message-id 
and subject line Bug#1037707: fixed in keyman 16.0.140-1
has caused the Debian Bug report #1037707,
regarding keyman: 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.)


-- 
1037707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:keyman
Version: 16.0.139-4
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/keyman_16.0.139-4_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/kmx/kmx_processevent.h:58:27: error: ‘PKMX_BYTE’ has not been 
declared
   58 |   KMX_BOOL VerifyKeyboard(PKMX_BYTE filebase, size_t sz);
  |   ^
../../../src/kmx/kmx_processevent.h:59:27: error: ‘PKMX_BYTE’ has not been 
declared
   59 |   KMX_BOOL VerifyChecksum(PKMX_BYTE buf,  size_t sz);
  |   ^
../../../src/kmx/kmx_processevent.h:60:27: error: ‘PKMX_BYTE’ has not been 
declared
   60 |   PKMX_WCHAR StringOffset(PKMX_BYTE base, KMX_DWORD offset);
  |   ^
../../../src/kmx/kmx_processevent.h:60:43: error: ‘KMX_DWORD’ has not been 
declared
   60 |   PKMX_WCHAR StringOffset(PKMX_BYTE base, KMX_DWORD offset);
  |   ^
../../../src/kmx/kmx_processevent.h:62:27: error: ‘PKMX_BYTE’ has not been 
declared
   62 |   LPKEYBOARD CopyKeyboard(PKMX_BYTE bufp, PKMX_BYTE base);
  |   ^
../../../src/kmx/kmx_processevent.h:62:43: error: ‘PKMX_BYTE’ has not been 
declared
   62 |   LPKEYBOARD CopyKeyboard(PKMX_BYTE bufp, PKMX_BYTE base);
  |   ^
../../../src/kmx/kmx_processevent.h:85:45: error: ‘KMX_DWORD’ has not been 
declared
   85 |   PKMX_WCHAR  GetSystemStore(LPKEYBOARD kb, KMX_DWORD SystemID);
  | ^
../../../src/kmx/kmx_processevent.h:89:25: error: ‘KMX_DWORD’ has not been 
declared
   89 |   KMX_BOOL IsCapsLockOn(KMX_DWORD modifiers);
  | ^
../../../src/kmx/kmx_processevent.h:90:20: error: ‘KMX_DWORD’ has not been 
declared
   90 |   void SetCapsLock(KMX_DWORD , KMX_BOOL capsLockOn, KMX_BOOL 
force = FALSE);
  |^
../../../src/kmx/kmx_processevent.h:91:22: error: ‘KMX_DWORD’ has not been 
declared
   91 |   void ResetCapsLock(KMX_DWORD , KMX_BOOL isKeyDown);
  |  ^
../../../src/kmx/kmx_processevent.h:92:29: error: ‘KMX_DWORD’ has not been 
declared
   92 |   KMX_BOOL KeyCapsLockPress(KMX_DWORD , KMX_BOOL isKeyDown);
  | ^
../../../src/kmx/kmx_processevent.h:93:22: error: ‘KMX_DWORD’ has not been 
declared
   93 |   void KeyShiftPress(KMX_DWORD , KMX_BOOL isKeyDown);
  |  ^
../../../src/kmx/kmx_processevent.h:95:30: error: ‘KMX_UINT’ has not been 
declared
   95 |   KMX_BOOL IsEquivalentShift(KMX_UINT rshift, KMX_UINT kshift);
  |  ^~~~
../../../src/kmx/kmx_processevent.h:95:47: error: ‘KMX_UINT’ has not been 
declared
   95 |   KMX_BOOL IsEquivalentShift(KMX_UINT rshift, KMX_UINT kshift);
  |   ^~~~
../../../src/kmx/kmx_processevent.h:102:46: error: ‘KMX_UINT’ has not been 
declared
  102 |   KMX_BOOL 

Bug#999966: Pending fix

[Pierre Gruet]

Hi Sylvestre,

Le 24/07/2023 à 13:54, Sylvestre Ledru a écrit :

Cool stuff. Could you please push your change to the repo ? :)
thanks
S


Sure, done! Any opinion from you on that matter will be appreciated :)

I should mention my changes were tested, to some extent: all the 
examples in the help pages of the affected scilab functions work and 
give the same results as with pcre3.


Cheers,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#999966: Pending fix

[Sylvestre Ledru]

Cool stuff. Could you please push your change to the repo ? :)
thanks
S

Le 23/07/2023 à 23:42, Pierre Gruet a écrit :

Control: tags -1 pending

Hi,

I intend to upload a fix shortly, after some days reworking the package to get 
rid of pcre3.

I post the contents of the header of the patch I wrote for further reference.


  This consists in:
  1. making changes in the following files:
   - scilab/modules/spreadsheet/src/c/csvRead.c
   - scilab/modules/string/src/c/strsubst.c
   - scilab/modules/string/sci_gateway/cpp/sci_strsubst.cpp
   - scilab/modules/string/sci_gateway/cpp/sci_grep.cpp
   - scilab/modules/string/sci_gateway/cpp/sci_strindex.cpp
   - scilab/modules/string/sci_gateway/cpp/sci_regexp.cpp
   - scilab/modules/slint/includes/PCREException.hxx
   - scilab/modules/slint/includes/PCREMatcher.hxx
   - scilab/modules/slint/src/cpp/PCREException.cpp
   - scilab/modules/slint/src/cpp/PCREMatcher.cpp
  in which one needs to use the pcre2 functions. This is somewhat
  difficult because the upstream codes contains files like
  scilab/modules/string/src/c/pcre_(internal|private).c which perform the
  regex matches and are highly dependent on the contents of the pcre
  library. To avoid rewriting them, I skipped them and put all the
  pattern compiling and matching stuff in the above .(c|cpp|hxx) files.

  2. updating the following files:
   - scilab/m4/pcre.m4
   - scilab/configure.ac
   - scilab/modules/string/Makefile.am
   - scilab/modules/slint/Makefile.am
  so that the flags and libraries of pcre2 are used, not the ones of
  pcre3.

  3. updating all the remaining files in this patch so that delimiters
  are not provided to the scilab functions working with regular
  expression patterns and modifiers like "i", "m" or "x" are not provided
  either, as they are not handled by the modifications I made. This
  implied also modifying a large part of the unit tests of these
  functions using the "imx" modifiers and I hope this was done well, as
  currently the build-time tests are not run during a Debian build.


Also I plan to insert a debian/NEWS file to warn about 3. above.


Best,

Bug#1041040: Fwd: Bug#1041040: aspectc++ autopkg tests fail with GCC 13

[Reinhard Tartler]

On 7/23/23 9:13 AM, Reinhard Tartler wrote:


Turns out, the fix only works on amd64/i386, but not for instance on Arm, 
Matthias, our GCC maintainer has filed 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041040 for this.

I looked over the patch and couldn't find anything architecture specific. Can 
you make any rhyme or reason for why it might fail on arm64?

Here are some more test logs:
https://ci.debian.net/packages/a/aspectc++/unstable/arm64/


This issue also occurs during a regular package build, not only during 
autopkgtest. I could reproduce it on the amdhal.debian.org in a sid chroot and 
got this:

Weaving aspects into PreFileIncluder.cc...
  
Weaving aspects into PreprocessorParser.cc...

Weaving aspects into UnitManager.cc...
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/src/PreFileIncluder.cc:19:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/TokenStream.h:25:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/Array.h:27:
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/Array.h_0_virt:66:9:
 error: __float128 is not supported on this target
typedef __float128 _Float128;
^
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/src/PrePrintVisitor.cc:19:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/PreSemIterator.h:24:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/PreTreeIterator.h:24:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/PreTree.h:25:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/PreVisitor.h:24:
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/PreVisitor.h_0_virt:66:9:
 error: __float128 is not supported on this target
typedef __float128 _Float128;
^
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/src/PreprocessorParser.cc:19:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/Token.h:25:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/LanguageID.h:25:
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/LanguageID.h_0_virt:66:9:
 error: __float128 is not supported on this target
typedef __float128 _Float128;
^
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/src/UnitManager.cc:19:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/Unit.h:25:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/List.h:25:
In file included from 
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/ListElement.h:27:
/tmp/autopkgtest.sSXQhw/build.5EQ/src/Puma/gen-release/step1/inc/Puma/ListElement.h_0_virt:66:9:
 error: __float128 is not supported on this target
typedef __float128 _Float128;
^

Bug#999966: marked as done (scilab: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 11:32:35 +
with message-id 
and subject line Bug#66: fixed in scilab 6.1.1+dfsg2-8
has caused the Debian Bug report #66,
regarding scilab: depends on obsolete pcre3 library
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.)


-- 
66: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=66
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scilab
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: scilab
Source-Version: 6.1.1+dfsg2-8
Done: Pierre Gruet 

We believe that the bug you reported is fixed in the latest version of
scilab, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pierre Gruet  (supplier of updated scilab 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: Mon, 24 Jul 2023 10:27:50 +0200
Source: scilab
Architecture: source
Version: 6.1.1+dfsg2-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Pierre Gruet 
Closes: 66
Changes:
 scilab (6.1.1+dfsg2-8) unstable; urgency=medium
 .
   * Using pcre2 instead of obsolete pcre3 (Closes: #66)
   * Providing a debian/NEWS file to let users know about the changes in regex
 handling in scilab.
   * Correcting some unmatched/obsolete Lintian overrides
   * Trim trailing whitespace.
Checksums-Sha1:
 43e7506819eb1782731e020a835dc2b467685c88 3460 scilab_6.1.1+dfsg2-8.dsc
 a8db5a00f146680dfac85045073a34aae155ad08 100888 
scilab_6.1.1+dfsg2-8.debian.tar.xz
 36d4be955ba72fe9a52865f7f083e991a8b52980 23911 
scilab_6.1.1+dfsg2-8_amd64.buildinfo
Checksums-Sha256:
 27929bdb089ef22f8d995e98d38ef18d8ac1e447ffc5241a766832c06768e478 3460 
scilab_6.1.1+dfsg2-8.dsc
 4df286d0b73a7977535ebcc2914efd3462e488fefd1779dca5b629e4707c3a74 100888 
scilab_6.1.1+dfsg2-8.debian.tar.xz
 907d20b19a3fa7b23f4f9918e402990cacdbe7f680b41edaa13f330362b85589 23911 
scilab_6.1.1+dfsg2-8_amd64.buildinfo
Files:
 96d4c1f90d87780ccfbc4e023215 3460 math optional scilab_6.1.1+dfsg2-8.dsc
 2786ec2419354ddd03e85e5a49b60199 100888 math optional 
scilab_6.1.1+dfsg2-8.debian.tar.xz
 7ae4d80b60e0e1a8b08dc2d49de8d613 23911 math optional 
scilab_6.1.1+dfsg2-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmS+VhkACgkQYAMWptwn
dHYxNBAAqiyPcjBGqYWoOHk7Sj5usBg/9K2MERi79PxCBvkdHDam8FXgCxtuWtDN
YaNI4NJwxgMx95brfBJkSRRIvVkpScHFO0KiyXSOIOYj9BUZAAgEi9xOWHuof4E5
R6l11eqiHzyBpEVaNXNi4ixGb3o4IxfJ4vW9eIP++MCJmGHgPNd3/BmaT7cgirJR
zTvWENp6Iz3UY72oH9096+8Wzv6X0l4T3tAzPfo1tea9Yc7vFKw/+9IRKoPlmt02
LL/My/ZbpQcebUQqQU28Q87O87G3urkPfpMPRU5v6JWIDl1TbnGz6pZPPFA4/9N1
1ghBv8s1VVhoacbBbm2Wj6rMR1rHOjOLPtUzMrGK8MRd1L2dabCatDIMYBKMWSdO
f6U9cFNxJTO8BfvLpzB5CFNTXDeKp+AxndUm8HWfUjwUSnTY184w8jU/+WNNnSAi
beXQWe5UX69TKFGJgpED6XmodM6CApEDHmDDK17LgVZuMJ8L5vfOWJ0xPKFMEpaj
pts6CNGx0spjYRjDHc89l2MIp5lAPF2+4L5JvMO7W8iM+i/OqOe5j0vM91Ot1prS
mczCZ+ocdq0sOILB7PWeYwxADZtxc2j9QTxVOgDXy7NZaAvr1XrXhDYXujO0aGtr
PLrB1fcVX26Cm6y2AYYFiUO0F/OP3/ru+TnzlnuZuNbTARKptNo=
=eUli
-END PGP SIGNATURE End Message ---

Bug#1041834: marked as done (libclang-rt-16-dev: undeclared file conflict with libclang-rt-16-dev-wasm{32,64} on /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 11:19:39 +
with message-id 
and subject line Bug#1041834: fixed in llvm-toolchain-16 1:16.0.6-6
has caused the Debian Bug report #1041834,
regarding libclang-rt-16-dev: undeclared file conflict with 
libclang-rt-16-dev-wasm{32,64} on 
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a
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.)


-- 
1041834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclang-rt-16-dev
Version: 1:16.0.6-5
Severity: serious

libclang-rt-16-dev installs
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm{32,64}.a,
which are also installed by libclang-rt-16-dev-wasm{32,64} respectively.
Trying to coinstall these packages in unstable results in an unpack
error. I guess that these files should only be contained in the
respective wasm packages. Don't forget to include the necessary
Breaks+Replaces when fixing this.

Helmut
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-16
Source-Version: 1:16.0.6-6
Done: Sylvestre Ledru 

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-16, 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.
Sylvestre Ledru  (supplier of updated llvm-toolchain-16 
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: Mon, 24 Jul 2023 08:29:14 +0200
Source: llvm-toolchain-16
Architecture: source
Version: 1:16.0.6-6
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1041834
Changes:
 llvm-toolchain-16 (1:16.0.6-6) unstable; urgency=medium
 .
   * Do the delete of wasi in libclang-rt regardless (Closes: #1041834)
Checksums-Sha1:
 c5a240f741d7eb5c5f14772f09e1744cf8dd3dee 8089 llvm-toolchain-16_16.0.6-6.dsc
 f04d768715d0c034d6162fe2f41d10601d06acf1 168456 
llvm-toolchain-16_16.0.6-6.debian.tar.xz
 5d15b799bd90082e3baf728783a40b672f6c5a84 34347 
llvm-toolchain-16_16.0.6-6_amd64.buildinfo
Checksums-Sha256:
 51b2e0153ce0a534d02bb5a260569941179d880171401009def54e8f1f6f08f9 8089 
llvm-toolchain-16_16.0.6-6.dsc
 0e3304d6a582b7d2aabac6ed8580dce6d41b62b3516ab9f6a8ed844330a89ec2 168456 
llvm-toolchain-16_16.0.6-6.debian.tar.xz
 c4d07afc394fd09050138ae82278876438b1172ed874a0a4171dae1f0296 34347 
llvm-toolchain-16_16.0.6-6_amd64.buildinfo
Files:
 3b69053a5a678f7eceaa80d8f61e 8089 devel optional 
llvm-toolchain-16_16.0.6-6.dsc
 61122aabc149ca62a9508d9ef735f659 168456 devel optional 
llvm-toolchain-16_16.0.6-6.debian.tar.xz
 6e75eb5ef44424ac19321b7a749e4e3c 34347 devel optional 
llvm-toolchain-16_16.0.6-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmS+UckACgkQfmUo2nUv
G+EkIA/+PCjJTm3c3iPpLndArESS65yzZspd70JK4Ze4S9A6FDjNtxxEhQgxmtID
UoKZMnHAAghjsJ+eGSkb27zVh9TQp1RoCb2EmQ7OKDOAObdC93kIHB540AEYWzZ/
/oyqGxSG5GwfRw64Za4f7qS+N11fPJfSuIRnA8f3hmG4RCQ1/4nCgQAo3WMmdTWZ
W9et9PvNrH+eGa5yFR7u/0b5p+OA2gNXeXTd05xkuFwxvaVOdL8BGMKt0TY6rhxg
AaNbM3XV+kainkNy/9GbC48VfQfsFuOjtM2Sw4fkw89ZxZihTSX2d6uSmx541Hlz
r42QT45x6y8WM6EXF9NaaxvM7tR7mc+TrKqs3ieGRZvNl0M9oahz7yz4gnHv0zKh
OavH5qIZ/VqXjlBSo/5hU5nmX7JtUn3UUkDJiXVd08ojk6cvWRQASKEefwyrf0zB
JOlSOUQ0KYvW3i2DsiVVsqinaK0taMaso0VriVVCiwuhoR0podcKyhN7BAQ4m8Ot
XHdNHjWAIUswtw1b/QqjYa7jqTGq49A4wCKQ52gUOiQS/RjqqKkYNDGLprRpCSJ8
rHqibl4lwhO7Be0fKWasEJidJcPAJgFsduDYd6tdX/ad1gscKdBqOg2Ix6wnyf3l
5L6kozCFsCViA+HyZ7dUblPMh5MnBsN8X/PJvsqmHu3bmL69M1s=
=4A0Q
-END PGP SIGNATURE End Message ---

Bug#1041302: svt-av1: breaks ABI without SONAME bump

[Dylan Aïssi]

Hi Sebastian,

On Mon, 17 Jul 2023 08:51:00 +0200 Sebastian Ramacher
 wrote:
> Version 1.6.0 removed compressed_ten_bit_format from the middle of
> EbSvtAv1EncConfiguration, hence changing the memory layout of that
> struct. This means that the ABI changed requiring a SONAME bump.

I reported this issue upstream.

But , now the question is: what is the best way to deal with that on our side?
Should I artificially bump the soname? If so, what soname can I use?
How do we handle these cases in Debian usually?

Best regards,
Dylan

Processed: found 1037541 in 1:1.50.1-3

[Debian Bug Tracking System]

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

> found 1037541 1:1.50.1-3
Bug #1037541 {Done: Hilko Bengen } [src:libguestfs] 
libguestfs: FTBFS: supermin: error: lstat: Value too large for defined data 
type: /var/tmp/supermin2b73c8.tmpdir/base.d/init
Marked as found in versions libguestfs/1:1.50.1-3 and reopened.
> thanks
Stopping processing here.

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

Processed: svt-av1: breaks ABI without SONAME bump

[Debian Bug Tracking System]

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

> forwarded 1041302 https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/2095
Bug #1041302 [src:svt-av1] svt-av1: breaks ABI without SONAME bump
Set Bug forwarded-to-address to 
'https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/2095'.
>
End of message, stopping processing here.

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

Bug#1037707: keyman: ftbfs with GCC-13

[Eberhard Beilharz]

I just uploaded 16.0.140-1 to mentors which contains a fix.


Eberhard Beilharz wrote on 2023-07-24 09:13:
Yes, I already fixed it in the upstream repo. I'll push a new package 
soon.


Thanks,
    Eberhard

Boyuan Yang wrote on 2023-07-22 01:49:

Hi Eberhard,

Are you going to work on this issue?

Thanks,
Boyuan Yang


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

Package: src:keyman
Version: 16.0.139-4
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/keyman_16.0.139-4_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/kmx/kmx_processevent.h:58:27: error: ‘PKMX_BYTE’ has 
not been

declared

 58 |   KMX_BOOL VerifyKeyboard(PKMX_BYTE filebase, size_t sz);
    |   ^
../../../src/kmx/kmx_processevent.h:59:27: error: ‘PKMX_BYTE’ has 
not been

declared

 59 |   KMX_BOOL VerifyChecksum(PKMX_BYTE buf,  size_t sz);
    |   ^
../../../src/kmx/kmx_processevent.h:60:27: error: ‘PKMX_BYTE’ has 
not been

declared

 60 |   PKMX_WCHAR StringOffset(PKMX_BYTE base, KMX_DWORD offset);
    |   ^
../../../src/kmx/kmx_processevent.h:60:43: error: ‘KMX_DWORD’ has 
not been

declared

 60 |   PKMX_WCHAR StringOffset(PKMX_BYTE base, KMX_DWORD offset);
    |   ^
../../../src/kmx/kmx_processevent.h:62:27: error: ‘PKMX_BYTE’ has 
not been

declared

 62 |   LPKEYBOARD CopyKeyboard(PKMX_BYTE bufp, PKMX_BYTE base);
    |   ^
../../../src/kmx/kmx_processevent.h:62:43: error: ‘PKMX_BYTE’ has 
not been

declared

 62 |   LPKEYBOARD CopyKeyboard(PKMX_BYTE bufp, PKMX_BYTE base);
    |   ^
../../../src/kmx/kmx_processevent.h:85:45: error: ‘KMX_DWORD’ has 
not been

declared
 85 |   PKMX_WCHAR GetSystemStore(LPKEYBOARD kb, KMX_DWORD 
SystemID);

    | ^
../../../src/kmx/kmx_processevent.h:89:25: error: ‘KMX_DWORD’ has 
not been

declared

 89 |   KMX_BOOL IsCapsLockOn(KMX_DWORD modifiers);
    | ^
../../../src/kmx/kmx_processevent.h:90:20: error: ‘KMX_DWORD’ has 
not been

declared

 90 |   void SetCapsLock(KMX_DWORD , KMX_BOOL capsLockOn,

KMX_BOOL force = FALSE);



OpenPGP_0xE9140597606020D3.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: reassign 1041338 to linux-kbuild-6.3, forcibly merging 1040178 1041338

[Debian Bug Tracking System]

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

> reassign 1041338 linux-kbuild-6.3
Bug #1041338 [src:linux] linux autopkg test blocks gcc-12 migration
Bug reassigned from package 'src:linux' to 'linux-kbuild-6.3'.
No longer marked as found in versions linux/6.3.7-1.
Ignoring request to alter fixed versions of bug #1041338 to the same values 
previously set
> forcemerge 1040178 1041338
Bug #1040178 {Done: Salvatore Bonaccorso } 
[linux-kbuild-6.3] linux-kbuild-6.3: missing Breaks: 
linux-headers-6.3.0-1-common, ...
Bug #1040178 {Done: Salvatore Bonaccorso } 
[linux-kbuild-6.3] linux-kbuild-6.3: missing Breaks: 
linux-headers-6.3.0-1-common, ...
Added tag(s) sid and trixie.
Bug #1041338 [linux-kbuild-6.3] linux autopkg test blocks gcc-12 migration
Marked Bug as done
Added indication that 1041338 affects nvidia-kernel-dkms
Marked as fixed in versions linux/6.4.4-1.
Marked as found in versions linux/6.3.11-1.
Merged 1040178 1041338
> thanks
Stopping processing here.

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

Processed: Re: Bug#1039883: The issue impacts SSD disks as well

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1039883 [src:linux] linux-image-6.3.0-1-amd64: ext4 corruption with 
symlinks
Ignoring request to alter tags of bug #1039883 to the same tags previously set

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

Bug#1039883: The issue impacts SSD disks as well

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi,

[Ted, Andreas, context in https://bugs.debian.org/1039883]

On Sun, Jul 02, 2023 at 09:14:50PM +, Hervé Werner wrote:
> I've just faced this issue on the SSD disk as well, so it seems that
> the probability is just lower on a speedier disk.

Are you able to reliably preoeduce the issue and can bisect it to the
introducing commit? 

Can you retest please with recent kernel, 6.3.11-1 and ideally 6.4.4-1
as recently uploaded to unstable?

Regards,
Salvatore

Processed: tagging 1039883

[Debian Bug Tracking System]

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

> tags 1039883 + moreinfo
Bug #1039883 [src:linux] linux-image-6.3.0-1-amd64: ext4 corruption with 
symlinks
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#1041338: linux autopkg test blocks gcc-12 migration

[Salvatore Bonaccorso]

Hi Matthias,

On Mon, Jul 17, 2023 at 06:07:59PM +0200, Matthias Klose wrote:
> Package: src:linux
> Version: 6.3.7-1
> Severity: serious
> Tags: sid trixie
> 
> seen on amd64, the issue doesn't look related to gcc-12.
> 
> see
> https://ci.debian.net/data/autopkgtest/testing/amd64/l/linux/35917919/log.gz
> 
> [...]
> 56sgcc-12 
> -Wp,-MMD,/tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/.foo.mod.o.d
> -nostdinc -I/usr/src/linux-headers-6.3.0-1-common/arch/x86/include
> -I./arch/x86/include/generated
> -I/usr/src/linux-headers-6.3.0-1-common/include -I./include
> -I/usr/src/linux-headers-6.3.0-1-common/arch/x86/include/uapi
> -I./arch/x86/include/generated/uapi
> -I/usr/src/linux-headers-6.3.0-1-common/include/uapi
> -I./include/generated/uapi -include
> /usr/src/linux-headers-6.3.0-1-common/include/linux/compiler-version.h
> -include /usr/src/linux-headers-6.3.0-1-common/include/linux/kconfig.h
> -include
> /usr/src/linux-headers-6.3.0-1-common/include/linux/compiler_types.h
> -D__KERNEL__ -fmacro-prefix-map=/usr/src/linux-headers-6.3.0-1-common/=
> -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing
> -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration
> -Werror=implicit-int -Werror=return-type -Wno-format-security
> -funsigned-char -std=gnu11 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
> -fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1
> -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup
> -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare
> -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern
> -mindirect-branch-register -mindirect-branch-cs-prefix
> -mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
> -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks
> -Wno-frame-address -Wno-format-truncation -Wno-format-overflow
> -Wno-address-of-packed-member -O2 -fno-allow-store-data-races
> -Wframe-larger-than=2048 -fstack-protector-strong -Wno-main
> -Wno-unused-but-set-variable -Wno-unused-const-variable
> -Wno-dangling-pointer -ftrivial-auto-var-init=zero
> -fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
> -falign-functions=16 -Wdeclaration-after-statement -Wvla -Wno-pointer-sign
> -Wcast-function-type -Wno-stringop-truncation -Wno-stringop-overflow
> -Wno-restrict -Wno-maybe-uninitialized -Wno-array-bounds
> -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -fno-strict-overflow
> -fno-stack-check -fconserve-stack -Werror=date-time
> -Werror=incompatible-pointer-types -Werror=designated-init
> -Wno-packed-not-aligned -g -DMODULE -DKBUILD_BASENAME='"foo.mod"'
> -DKBUILD_MODNAME='"foo"' -D__KBUILD_MODNAME=kmod_foo -c -o
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/foo.mod.o
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/foo.mod.c
>  57s
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/foo.mod.c:10:10:
> fatal error: asm/orc_header.h: No such file or directory
>  57s10 | #include 
>  57s   |  ^~
>  57s compilation terminated.
>  57s make[1]: ***
> [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.modfinal:29:
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/foo.mod.o] Error 1
>  57s make: Leaving directory '/usr/src/linux-headers-6.3.0-1-cloud-amd64'
>  57s make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:1967:
> modules] Error 2
>  57s I: Clean
>  57s E: Unexpected warning/error messages
>  57s make: Entering directory '/usr/src/linux-headers-6.3.0-1-cloud-amd64'
>  57s make -f /usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.clean
> obj=/tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo
>  57s # CLEAN
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/Module.symvers
>  57s   rm -rf
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/Module.symvers
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/modules.nsdeps 
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/compile_commands.json
> /tmp/autopkgtest-lxc.f52ni744/downtmp/autopkgtest_tmp/foo/.thinlto-cache
>  57s make: Leaving directory '/usr/src/linux-headers-6.3.0-1-cloud-amd64'
>  57s autopkgtest [03:20:42]: test kbuild: ---]
>  57s autopkgtest [03:20:42]: test kbuild:  - - - - - - - - - - results - - -
> - - - - - - -
>  57s kbuild   FAIL stderr: E: Unexpected warning/error messages

That should be the same root cause as #1040178. Merging both.

The upload 6.4.4-1 to unstable should address this now.

Regards,
Salvatore

Processed (with 1 error): forcibly merging 1040178 1041338

[Debian Bug Tracking System]

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

> forcemerge 1040178 1041338
Bug #1040178 {Done: Salvatore Bonaccorso } 
[linux-kbuild-6.3] linux-kbuild-6.3: missing Breaks: 
linux-headers-6.3.0-1-common, ...
Unable to merge bugs because:
package of #1041338 is 'src:linux' not 'linux-kbuild-6.3'
Failed to forcibly merge 1040178: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: tagging 1040682

[Debian Bug Tracking System]

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

> tags 1040682 + trixie sid
Bug #1040682 [src:colord] FTBFS in colord with meson 1.2.0 rc2
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1037790: marked as done (nix: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 08:39:17 +
with message-id 
and subject line Bug#1037790: fixed in nix 2.16.1+dfsg-1
has caused the Debian Bug report #1037790,
regarding nix: 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.)


-- 
1037790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nix
Version: 2.8.0-1.1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
checking for boostlib >= 1.66 (106600)... yes
checking whether -latomic is needed... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libcrypto... yes
checking for libarchive >= 3.1.2... yes
checking for sqlite3 >= 3.6.19... yes
checking for libcurl... yes
checking for libeditline... yes
checking for libsodium... yes
checking for libbrotlienc libbrotlidec... yes
checking for libcpuid... yes
checking for libseccomp... yes
checking for aws/s3/S3Client.h... no
checking for bdw-gc... yes
checking for gtest_main... yes
checking for nlohmann_json >= 3.9... yes
checking for lowdown >= 0.9.0... yes
checking for setresuid... yes
checking for setreuid... yes
checking for lchown... yes
checking for strsignal... yes
checking for posix_fallocate... yes
checking for sysconf... yes
configure: creating ./config.status
config.status: creating config.h
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j8
make[1]: Entering directory '/<>'
rm -f Makefile.config && ./config.status --quiet --file=Makefile.config
bison -v -o src/libexpr/parser-tab.cc src/libexpr/parser.y -d
bison -v -o src/libexpr/parser-tab.cc src/libexpr/parser.y -d
flex --outfile src/libexpr/lexer-tab.cc --header-file=src/libexpr/lexer-tab.hh 
src/libexpr/lexer.l
flex --outfile src/libexpr/lexer-tab.cc --header-file=src/libexpr/lexer-tab.hh 
src/libexpr/lexer.l
src/libexpr/lexer.l:314: warning, -s option given but default rule can be 
matched
cat src/nix-channel/unpack-channel.nix >> 
src/nix-channel/unpack-channel.nix.gen.hh.tmp
cat src/nix-env/buildenv.nix >> src/nix-env/buildenv.nix.gen.hh.tmp
cat src/nix/get-env.sh >> src/nix/get-env.sh.gen.hh.tmp
src/libexpr/lexer.l:314: warning, -s option given but default rule can be 
matched
cat doc/manual/generate-manpage.nix >> 
doc/manual/generate-manpage.nix.gen.hh.tmp
cat doc/manual/utils.nix >> doc/manual/utils.nix.gen.hh.tmp
cat src/libexpr/flake/call-flake.nix >> 
src/libexpr/flake/call-flake.nix.gen.hh.tmp
cat src/libexpr/imported-drv-to-derivation.nix >> 
src/libexpr/imported-drv-to-derivation.nix.gen.hh.tmp
cat src/libexpr/primops/derivation.nix >> 
src/libexpr/primops/derivation.nix.gen.hh.tmp
cat src/libexpr/fetchurl.nix >> src/libexpr/fetchurl.nix.gen.hh.tmp
g++ -o src/libutil/archive.o -c src/libutil/archive.cc -Wdate-time 
-D_FORTIFY_SOURCE=2  -fstack-protector-strong -Wformat -Werror=format-security 
-ffile-prefix-map=/<>=. -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-g -Wno-deprecated-declarations -g -Wall -include config.h -std=c++17 -I src 
-I/usr/include/libcpuid -DREADLINE -I/usr/include/x86_64-linux-gnu 
-I/usr/include  -MMD -MF src/libutil/.archive.o.dep -MP
g++ -o src/libutil/args.o -c src/libutil/args.cc -Wdate-time 
-D_FORTIFY_SOURCE=2  -fstack-protector-strong -Wformat -Werror=format-security 
-ffile-prefix-map=/<>=. -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-g 

Bug#1037859: marked as done (skimage: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 10:27:04 +0200
with message-id 
and subject line Re-closing accidentally reopened bug
has caused the Debian Bug report #1037823,
regarding skimage: 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.)


-- 
1037823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:skimage
Version: 0.19.3-8
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/skimage_0.19.3-8_unstable_gccexp.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:312:1:
 note: in expansion of macro ‘SCALAR_COMBINER’
  312 | SCALAR_COMBINER(uint32_t)
  | ^~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:31:
 error: template argument 2 is invalid
  304 |   struct __combined {   
   \
  |   ^
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:312:1:
 note: in expansion of macro ‘SCALAR_COMBINER’
  312 | SCALAR_COMBINER(uint32_t)
  | ^~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:17:
 error: ‘uint64_t’ was not declared in this scope
  314 | SCALAR_COMBINER(uint64_t)
  | ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:21:
 note: in definition of macro ‘SCALAR_COMBINER’
  304 |   struct __combined {   
   \
  | ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:17:
 note: ‘uint64_t’ is defined in header ‘’; did you forget to ‘#include 
’?
  314 | SCALAR_COMBINER(uint64_t)
  | ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:21:
 note: in definition of macro ‘SCALAR_COMBINER’
  304 |   struct __combined {   
   \
  | ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:17:
 error: ‘uint64_t’ was not declared in this scope
  314 | SCALAR_COMBINER(uint64_t)
  | ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:27:
 note: in definition of macro ‘SCALAR_COMBINER’
  304 |   struct __combined {   
   \
  |   ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:17:
 note: ‘uint64_t’ is defined in header ‘’; did you forget to ‘#include 
’?
  314 | SCALAR_COMBINER(uint64_t)
  | ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:27:
 note: in definition of macro ‘SCALAR_COMBINER’
  304 |   struct __combined {   
   \
  |   ^~~~
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:304:31:
 error: template argument 1 is invalid
  304 |   struct __combined {   
   \
  |   ^
/usr/lib/python3/dist-packages/pythran/pythonic/include/types/combined.hpp:314:1:
 note: in expansion of macro ‘SCALAR_COMBINER’
  314 | SCALAR_COMBINER(uint64_t)
  | ^~~

Bug#1037823: marked as done (pythran: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 10:27:04 +0200
with message-id 
and subject line Re-closing accidentally reopened bug
has caused the Debian Bug report #1037823,
regarding pythran: 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.)


-- 
1037823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pythran
Version: 0.11.0+ds-7
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/pythran_0.11.0+ds-7_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

[...]
FAILED pythran/tests/test_base.py::TestBase::test_pow - distutils.errors.Comp...
FAILED pythran/tests/test_base.py::TestBase::test_pow_op0 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_pow_op1 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_pow_op2 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_print - distutils.errors.Co...
FAILED pythran/tests/test_base.py::TestBase::test_print_tuple - distutils.err...
FAILED pythran/tests/test_base.py::TestBase::test_raise - distutils.errors.Co...
FAILED pythran/tests/test_base.py::TestBase::test_range1 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range2 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range3 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range4 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range5 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range6 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range7 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range_negative_step - distu...
FAILED pythran/tests/test_base.py::TestBase::test_raw_set - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_recursion1 - distutils.erro...
FAILED pythran/tests/test_base.py::TestBase::test_recursion2 - distutils.erro...
FAILED pythran/tests/test_base.py::TestBase::test_recursive_attr - distutils
FAILED pythran/tests/test_base.py::TestBase::test_reduce - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_return_empty_list - distuti...
FAILED pythran/tests/test_base.py::TestBase::test_return_set - distutils.erro...
FAILED pythran/tests/test_base.py::TestBase::test_reversed - distutils.errors...
FAILED pythran/tests/test_base.py::TestBase::test_reversed_range_negative_step
FAILED pythran/tests/test_base.py::TestBase::test_reversed_slice - distutils
FAILED pythran/tests/test_base.py::TestBase::test_round - distutils.errors.Co...
FAILED pythran/tests/test_base.py::TestBase::test_rrange1 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange2 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange3 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange4 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange5 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange6 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange7 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_set - distutils.errors.Comp...
FAILED pythran/tests/test_base.py::TestBase::test_set_comprehension - distuti...
FAILED pythran/tests/test_base.py::TestBase::test_shadow_parameters - distuti...

Bug#1041844: geary FTBFS with vala 0.56.9

[Adrian Bunk]

Source: geary
Version: 43.0-1
Severity: serious
Tags: ftbfs trixie sid patch
Forwarded: 
https://gitlab.gnome.org/GNOME/geary/-/commit/4a7ca820b1d3d6130fedf254dc5b4cd7efb58f2c

https://buildd.debian.org/status/fetch.php?pkg=geary=alpha=43.0-1=1690173311=0

...
../src/client/accounts/accounts-editor-row.vala:388.45-388.53: error: too few 
type arguments for `Accounts.EditorRow'
  388 | internal interface Accounts.ValidatingRow : EditorRow {
  | ^
...

Processed: Re-assign (and close) skimage bug

[Debian Bug Tracking System]

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

> reassign 1037859 src:pythran 0.11.0+ds-7
Bug #1037859 [src:skimage] skimage: ftbfs with GCC-13
Bug reassigned from package 'src:skimage' to 'src:pythran'.
No longer marked as found in versions skimage/0.19.3-8.
Ignoring request to alter fixed versions of bug #1037859 to the same values 
previously set
Bug #1037859 [src:pythran] skimage: ftbfs with GCC-13
Marked as found in versions pythran/0.11.0+ds-7.
> affects 1037859 src:skimage
Bug #1037859 [src:pythran] skimage: ftbfs with GCC-13
Added indication that 1037859 affects src:skimage
> fixed 1037859 0.11.0+ds-8
Bug #1037859 [src:pythran] skimage: ftbfs with GCC-13
Marked as fixed in versions pythran/0.11.0+ds-8.
> forcemerge 1037859 1037823
Bug #1037859 [src:pythran] skimage: ftbfs with GCC-13
Bug #1037823 {Done: Drew Parsons } [src:pythran] pythran: 
ftbfs with GCC-13
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pythran/0.11.0+ds-8.
Added indication that 1037823 affects src:skimage
Bug #1037823 [src:pythran] pythran: ftbfs with GCC-13
Marked as fixed in versions pythran/0.11.0+ds-8.
Merged 1037823 1037859
> thanks
Stopping processing here.

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

Bug#1037642: encfs: ftbfs with GCC-13

[Agustin Martin]

> 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/encfs_1.9.5-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.

Hi, Mathias,

I have tried to triage this bug report by adding to debian/rules

export CC  = gcc-13
export CXX = g++-13

in a plain sid cowbuilder chroot and could not reproduce this problem
(log shows that g++-13 is indeed used).

I have also created a sid+experimental cowbuilder chroot and followed
guidelines, and also did not succeed (by the way, g++ in experimental
seems to have reached sid).

Regards,

-- 
Agustin

Processed: your mail

[Debian Bug Tracking System]

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

> notfound 1041837 4:7.5.5-2
Bug #1041837 {Done: René Engelhard } [libreoffice-draw] 
libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= 
trixie: /usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
No longer marked as found in versions libreoffice/4:7.5.5-2.
>
End of message, stopping processing here.

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

Bug#1041837: marked as done (libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= trixie: /usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 10:06:29 +0200
with message-id <5362375f-bc7c-4753-ac9d-8b78d308f...@rene-engelhard.de>
and subject line Re: Bug#1041837: libreoffice-draw: undeclared file conflict 
with libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
has caused the Debian Bug report #1041837,
regarding libreoffice-draw: undeclared file conflict with 
libreoffice-impress-nogui <= trixie: 
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
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.)


-- 
1041837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-draw
Version: 4:7.5.5-2
Severity: serious

libreoffice-draw installs
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/layoutlist.xml
and
/usr/lib/libreoffice/share/config/soffice.cfg/simpress/objectlist.xml
which are also contained in libreoffice-impress-nogui from bullseye to
trixie. Trying to install libreoffice-draw may result in an unpack
error. Please add the necessary Breaks and Replaces.

Helmut
--- End Message ---
--- Begin Message ---
Control: notfound 1041837 4:7.5.5-2

08:26 < helmut> _rene_: re libreoffice (short on time atm): seems like I messed 
something up, please close my report. (...)

Am 24. Juli 2023 06:52:51 MESZ schrieb Helmut Grohne :
>Package: libreoffice-draw
>Version: 4:7.5.5-2
>Severity: serious
>
>libreoffice-draw installs
>/usr/lib/libreoffice/share/config/soffice.cfg/simpress/layoutlist.xml
>and
>/usr/lib/libreoffice/share/config/soffice.cfg/simpress/objectlist.xml
>which are also contained in libreoffice-impress-nogui from bullseye to
>trixie. Trying to install libreoffice-draw may result in an unpack
>error. Please add the necessary Breaks and Replaces.
>
>Helmut
>
--- End Message ---

Processed: gcc-13 FTBFS bug housekeeping

[Debian Bug Tracking System]

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

> found 1037573 13.0.0+r63-1~exp2
Bug #1037573 {Done: Roger Shimizu } [src:android-platform-art] 
android-platform-art: ftbfs with GCC-13
Marked as found in versions android-platform-art/13.0.0+r63-1~exp2.
> tags 1037573 experimental
Bug #1037573 {Done: Roger Shimizu } [src:android-platform-art] 
android-platform-art: ftbfs with GCC-13
Added tag(s) experimental.
> close 1037578
Bug #1037578 [src:apparmor] apparmor: ftbfs with GCC-13
Marked Bug as done
> close 1037583 2023.04.09-1
Bug #1037583 [src:audmes] audmes: ftbfs with GCC-13
Marked as fixed in versions audmes/2023.04.09-1.
Bug #1037583 [src:audmes] audmes: ftbfs with GCC-13
Marked Bug as done
> close 1037584 3.3.3+dfsg-1
Bug #1037584 [src:audacity] audacity: ftbfs with GCC-13
Marked as fixed in versions audacity/3.3.3+dfsg-1.
Bug #1037584 [src:audacity] audacity: ftbfs with GCC-13
Marked Bug as done
> close 1037599
Bug #1037599 [src:bustools] bustools: ftbfs with GCC-13
Marked Bug as done
> close 1037642
Bug #1037642 [src:encfs] encfs: ftbfs with GCC-13
Marked Bug as done
> close 1037657 115.0.2esr-1
Bug #1037657 [src:firefox-esr] firefox-esr: ftbfs with GCC-13
Marked as fixed in versions firefox-esr/115.0.2esr-1.
Bug #1037657 [src:firefox-esr] firefox-esr: ftbfs with GCC-13
Marked Bug as done
> close 1037681 3.10.0~rc3-3
Bug #1037681 [src:gr-funcube] gr-funcube: ftbfs with GCC-13
Marked as fixed in versions gr-funcube/3.10.0~rc3-3.
Bug #1037681 [src:gr-funcube] gr-funcube: ftbfs with GCC-13
Marked Bug as done
> close 1037695 2.22.0-1
Bug #1037695 [src:iminuit] iminuit: ftbfs with GCC-13
Ignoring request to alter fixed versions of bug #1037695 to the same values 
previously set
Bug #1037695 [src:iminuit] iminuit: ftbfs with GCC-13
Marked Bug as done
> close 1037743 0~git20230615.a45d8b8+dfsg-1
Bug #1037743 [src:libtgowt] libtgowt: ftbfs with GCC-13
Marked as fixed in versions libtgowt/0~git20230615.a45d8b8+dfsg-1.
Bug #1037743 [src:libtgowt] libtgowt: ftbfs with GCC-13
Marked Bug as done
> close 1037770 1:10.11.4-1
Bug #1037770 [src:mariadb] mariadb: ftbfs with GCC-13
Marked as fixed in versions mariadb/1:10.11.4-1.
Bug #1037770 [src:mariadb] mariadb: ftbfs with GCC-13
Marked Bug as done
> close 1037766 0.255+dfsg.1-1
Bug #1037766 [src:mame] mame: ftbfs with GCC-13
Marked as fixed in versions mame/0.255+dfsg.1-1.
Bug #1037766 [src:mame] mame: ftbfs with GCC-13
Marked Bug as done
> close 1037774 1.5.109-1
Bug #1037774 [src:mfgtools] mfgtools: ftbfs with GCC-13
Marked as fixed in versions mfgtools/1.5.109-1.
Bug #1037774 [src:mfgtools] mfgtools: ftbfs with GCC-13
Marked Bug as done
> reassign 1037776 src:mia
Bug #1037776 [src:miaviewit] miaviewit: ftbfs with GCC-13
Bug reassigned from package 'src:miaviewit' to 'src:mia'.
No longer marked as found in versions miaviewit/1.0.5-3.
Ignoring request to alter fixed versions of bug #1037776 to the same values 
previously set
> forcemerge 1037775 1037776
Bug #1037775 [src:mia] mia: ftbfs with GCC-13
Bug #1037776 [src:mia] miaviewit: ftbfs with GCC-13
Marked as found in versions mia/2.4.7-11.
Merged 1037775 1037776
> affects 1037775 src:miaviewit
Bug #1037775 [src:mia] mia: ftbfs with GCC-13
Bug #1037776 [src:mia] miaviewit: ftbfs with GCC-13
Added indication that 1037775 affects src:miaviewit
Added indication that 1037776 affects src:miaviewit
> close 1037784 3.4.2+dfsg-1
Bug #1037784 [src:mygui] mygui: ftbfs with GCC-13
Marked as fixed in versions mygui/3.4.2+dfsg-1.
Bug #1037784 [src:mygui] mygui: ftbfs with GCC-13
Marked Bug as done
> close 1037789
Bug #1037789 [src:nheko] nheko: ftbfs with GCC-13
Marked Bug as done
> close 1037793 2:3.91-1
Bug #1037793 [src:nss] nss: ftbfs with GCC-13
Marked as fixed in versions nss/2:3.91-1.
Bug #1037793 [src:nss] nss: ftbfs with GCC-13
Marked Bug as done
> close 1037797 2.7.4-1
Bug #1037797 [src:onednn] onednn: ftbfs with GCC-13
Marked as fixed in versions onednn/2.7.4-1.
Bug #1037797 [src:onednn] onednn: ftbfs with GCC-13
Marked Bug as done
> reassign 1037629 src:libtins
Bug #1037629 [src:dublin-traceroute] dublin-traceroute: ftbfs with GCC-13
Bug reassigned from package 'src:dublin-traceroute' to 'src:libtins'.
No longer marked as found in versions dublin-traceroute/0.4.2-2.
Ignoring request to alter fixed versions of bug #1037629 to the same values 
previously set
> forcemerge 1037744 1037629
Bug #1037744 [src:libtins] libtins: ftbfs with GCC-13
Bug #1037629 [src:libtins] dublin-traceroute: ftbfs with GCC-13
Marked as found in versions libtins/4.0-1.
Merged 1037629 1037744
> affects 1037744 src:dublin-traceroute
Bug #1037744 [src:libtins] libtins: ftbfs with GCC-13
Bug #1037629 [src:libtins] dublin-traceroute: ftbfs with GCC-13
Added indication that 1037744 affects src:dublin-traceroute
Added indication that 1037629 affects src:dublin-traceroute
> close 1037897 2.40.4-1
Bug #1037897 [src:wpewebkit] wpewebkit: ftbfs with GCC-13
Marked as fixed in versions wpewebkit/2.40.4-1.
Bug #1037897 [src:wpewebkit] wpewebkit: 

Bug#1041834: libclang-rt-16-dev: undeclared file conflict with libclang-rt-16-dev-wasm{32, 64} on /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a

[Sylvestre Ledru]

OK, I think i found the issue

Le 24/07/2023 à 06:45, Helmut Grohne a écrit :

Package: libclang-rt-16-dev
Version: 1:16.0.6-5
Severity: serious

libclang-rt-16-dev installs
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm{32,64}.a,
which are also installed by libclang-rt-16-dev-wasm{32,64} respectively.
Trying to coinstall these packages in unstable results in an unpack
error. I guess that these files should only be contained in the
respective wasm packages. Don't forget to include the necessary
Breaks+Replaces when fixing this.

Helmut

___
Pkg-llvm-team mailing list
pkg-llvm-t...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-llvm-team

Bug#1041833: marked as done (libafl-persistent-ocaml: undeclared file conflict with libafl-persistent-ocaml-dev/bookworm)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 07:19:00 +
with message-id 
and subject line Bug#1041833: fixed in ocaml-afl-persistent 1.4-3
has caused the Debian Bug report #1041833,
regarding libafl-persistent-ocaml: undeclared file conflict with 
libafl-persistent-ocaml-dev/bookworm
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.)


-- 
1041833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libafl-persistent-ocaml
Version: 1.4-2
Severity: serious

libafl-persistent-ocaml installs /usr/lib/ocaml/afl-persistent/META,
which is also installed by libafl-persistent-ocaml-dev/bookworm. As
such, upgrades may result in an unpack error. If this is an intentional
move, please add corresponding Breaks+Replaces.

Helmut
--- End Message ---
--- Begin Message ---
Source: ocaml-afl-persistent
Source-Version: 1.4-3
Done: Stéphane Glondu 

We believe that the bug you reported is fixed in the latest version of
ocaml-afl-persistent, 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.
Stéphane Glondu  (supplier of updated ocaml-afl-persistent 
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: Mon, 24 Jul 2023 08:53:03 +0200
Source: ocaml-afl-persistent
Architecture: source
Version: 1.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1041833
Changes:
 ocaml-afl-persistent (1.4-3) unstable; urgency=medium
 .
   * Team upload
   * Add Breaks+Replaces to cope with move of META (Closes: #1041833)
Checksums-Sha1:
 02cf372c28746a15dcded8fe2d1a94690b9ca0a1 2027 ocaml-afl-persistent_1.4-3.dsc
 5ba78b64fd99d49add3617d4f763fe9bf29fa0ec 2392 
ocaml-afl-persistent_1.4-3.debian.tar.xz
Checksums-Sha256:
 8063c8d69b5e9271edf81a5ba19def2a55b9adc9484e20fd873cc01d33d94f2b 2027 
ocaml-afl-persistent_1.4-3.dsc
 bd805078cfebe128b744a0dec6688574d5651eec7d7f21b4a93b0d7b6b00d7e1 2392 
ocaml-afl-persistent_1.4-3.debian.tar.xz
Files:
 01e307847aef866dc41e7fbb7b0c2408 2027 ocaml optional 
ocaml-afl-persistent_1.4-3.dsc
 c048523048e6c427aefe1799470f1f49 2392 ocaml optional 
ocaml-afl-persistent_1.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmS+IEoSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBpcAH/04gB2cJX37RFXAWJS2WyZACONtOpAM7
046H0dkrsahB6LVTrkFhMxQpclrZ79CnuFfhGFepC4+Cb5epPLrerUrL1Kqc9KMh
RGU+umC8cAOsa5P+eymC9FOCU1srNc92cVyLWHXoyEV2BBMq57asbSz4Df8EPKT5
hVW9r+IYyqywasR+bKsaQZ6A5EIkZaQ8QmFqxIoyHBbnc8yFFqi2helW6aGizRSJ
QQieC6Lzpp6ZNoQ6ppdvgtCQmJ+lOxq8R3OP4CJ+rqPjLYX5X93/b7QTya8phQDv
Pm0QEYg6kOYx1v8fEg9gPhbI1I1hY76Sz0imoz2b60epquwJKKG96HI=
=D4AA
-END PGP SIGNATURE End Message ---

Bug#1037707: keyman: ftbfs with GCC-13

[Eberhard Beilharz]

Yes, I already fixed it in the upstream repo. I'll push a new package soon.

Thanks,
    Eberhard

Boyuan Yang wrote on 2023-07-22 01:49:

Hi Eberhard,

Are you going to work on this issue?

Thanks,
Boyuan Yang


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

Package: src:keyman
Version: 16.0.139-4
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/keyman_16.0.139-4_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/kmx/kmx_processevent.h:58:27: error: ‘PKMX_BYTE’ has not been

declared

     58 |   KMX_BOOL VerifyKeyboard(PKMX_BYTE filebase, size_t sz);
    |   ^
../../../src/kmx/kmx_processevent.h:59:27: error: ‘PKMX_BYTE’ has not been

declared

     59 |   KMX_BOOL VerifyChecksum(PKMX_BYTE buf,  size_t sz);
    |   ^
../../../src/kmx/kmx_processevent.h:60:27: error: ‘PKMX_BYTE’ has not been

declared

     60 |   PKMX_WCHAR StringOffset(PKMX_BYTE base, KMX_DWORD offset);
    |   ^
../../../src/kmx/kmx_processevent.h:60:43: error: ‘KMX_DWORD’ has not been

declared

     60 |   PKMX_WCHAR StringOffset(PKMX_BYTE base, KMX_DWORD offset);
    |   ^
../../../src/kmx/kmx_processevent.h:62:27: error: ‘PKMX_BYTE’ has not been

declared

     62 |   LPKEYBOARD CopyKeyboard(PKMX_BYTE bufp, PKMX_BYTE base);
    |   ^
../../../src/kmx/kmx_processevent.h:62:43: error: ‘PKMX_BYTE’ has not been

declared

     62 |   LPKEYBOARD CopyKeyboard(PKMX_BYTE bufp, PKMX_BYTE base);
    |   ^
../../../src/kmx/kmx_processevent.h:85:45: error: ‘KMX_DWORD’ has not been

declared

     85 |   PKMX_WCHAR  GetSystemStore(LPKEYBOARD kb, KMX_DWORD SystemID);
    | ^
../../../src/kmx/kmx_processevent.h:89:25: error: ‘KMX_DWORD’ has not been

declared

     89 |   KMX_BOOL IsCapsLockOn(KMX_DWORD modifiers);
    | ^
../../../src/kmx/kmx_processevent.h:90:20: error: ‘KMX_DWORD’ has not been

declared

     90 |   void SetCapsLock(KMX_DWORD , KMX_BOOL capsLockOn,

KMX_BOOL force = FALSE);



OpenPGP_0xE9140597606020D3.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1037580: marked as done (ares: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 07:05:48 +
with message-id 
and subject line Bug#1037580: fixed in ares 132-1
has caused the Debian Bug report #1037580,
regarding ares: 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.)


-- 
1037580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ares
Version: 126-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/ares_126-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

[...]
  239 |   if(!rhs) throw std::runtime_error("division by zero");
  |   ^
../nall/arithmetic/natural.hpp:239:23: note: ‘std::runtime_error’ is defined in 
header ‘’; did you forget to ‘#include ’?
In file included from ../nall/arithmetic.hpp:77:
../nall/arithmetic/natural.hpp: In function ‘void nall::div(const u8192&, const 
u8192&, u8192&, u8192&)’:
../nall/arithmetic/natural.hpp:239:23: error: ‘runtime_error’ is not a member 
of ‘std’
  239 |   if(!rhs) throw std::runtime_error("division by zero");
  |   ^
../nall/arithmetic/natural.hpp:239:23: note: ‘std::runtime_error’ is defined in 
header ‘’; did you forget to ‘#include ’?
In file included from ../nall/arithmetic.hpp:37,
 from ../nall/hash/hash.hpp:3,
 from ../nall/hash/sha256.hpp:3,
 from ../nall/file-buffer.hpp:12,
 from ../nall/file.hpp:3,
 from ../nall/directory.hpp:3,
 from ../hiro/core/core.hpp:4,
 from ../hiro/core/core.cpp:13,
 from ../hiro/hiro.cpp:5:
../nall/arithmetic/natural.hpp: In function ‘void nall::div(const u256&, const 
u256&, u256&, u256&)’:
../nall/arithmetic/natural.hpp:239:23: error: ‘runtime_error’ is not a member 
of ‘std’
  239 |   if(!rhs) throw std::runtime_error("division by zero");
  |   ^
../nall/arithmetic/natural.hpp:1:1: note: ‘std::runtime_error’ is defined in 
header ‘’; did you forget to ‘#include ’?
  +++ |+#include 
1 | #define ConcatenateType(Size) u##Size
In file included from ../nall/arithmetic.hpp:45:
../nall/arithmetic/natural.hpp: In function ‘void nall::div(const u512&, const 
u512&, u512&, u512&)’:
../nall/arithmetic/natural.hpp:239:23: error: ‘runtime_error’ is not a member 
of ‘std’
  239 |   if(!rhs) throw std::runtime_error("division by zero");
  |   ^
../nall/arithmetic/natural.hpp:239:23: note: ‘std::runtime_error’ is defined in 
header ‘’; did you forget to ‘#include ’?
In file included from ../nall/arithmetic.hpp:53:
../nall/arithmetic/natural.hpp: In function ‘void nall::div(const u1024&, const 
u1024&, u1024&, u1024&)’:
../nall/arithmetic/natural.hpp:239:23: error: ‘runtime_error’ is not a member 
of ‘std’
  239 |   if(!rhs) throw std::runtime_error("division by zero");
  |   ^
../nall/arithmetic/natural.hpp:239:23: note: ‘std::runtime_error’ is defined in 
header ‘’; did you forget to ‘#include ’?
make[2]: *** [../nall/GNUmakefile:201: obj/ares-fixed-allocator.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: *** [../ruby/GNUmakefile:94: obj/ruby.o] Error 1
In file included from ../nall/arithmetic.hpp:61:
../nall/arithmetic/natural.hpp: In function ‘void nall::div(const u2048&, const 
u2048&, u2048&, u2048&)’:
../nall/arithmetic/natural.hpp:239:23: error: 

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Sebastian Ramacher]

On 2023-07-20 18:25:05 +0200, Andrea Pappacoda wrote:
> On Sun, 16 Jul 2023 16:07:00 +0200 Sebastian Ramacher 
> wrote:
> > Source: cpp-httplib
> > Version: 0.13.1+ds-1
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the
> past)
> >
> > When starting an uncoordinated transition, please at least ensure that
> > the package at least builds on all suported platforms.
> 
> Hi Sebastian, thanks for the report. It isn't easy for me to test that
> cpp-httplib's test suite passes on all architectures, since I only have
> access to amd64 machines. Nonetheless, I'll look into this as soon as
> possible.

Please prepare transitions in experimental first. This would avoid such
issues.

If there are no news regarding a fix for this bug, please revert
cpp-httplib 0.11.4 to get back to a good state.

Cheers
-- 
Sebastian Ramacher

Bug#1040053: gjs: autopkgtest regression: free(): invalid pointer

[Paul Gevers]

Hi Jeremy,

On 24-07-2023 02:14, Jeremy Bícha wrote:

But I am surprised that this RC bug did not block the
migration of gjs 1.76.2-3 to Testing today.


That's because the bts infers which suites are affected by "reading" the 
changelog. I filed the bug against 1.74.3-1, but that's not an ancestor 
of 1.76.2-3, so it considered the bug as not affecting the uploads after 
1.74.3-1. If you look at the affected versions plot in the bts, you even 
see that it's completely missing, the bts doesn't know that 1.74.3-1 
even existed. The migration software (britney) gets it's information 
from the bts of course.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041633: marked as done (qgis: needs DEB_PYTHON_INSTALL_LAYOUT=deb to build)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jul 2023 06:22:39 +
with message-id 
and subject line Bug#1041633: fixed in qgis 3.28.9+dfsg-1
has caused the Debian Bug report #1041633,
regarding qgis: needs DEB_PYTHON_INSTALL_LAYOUT=deb to build
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.)


-- 
1041633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cmake
Version: 3.27.0-1
Severity: serious
Tags: upstream
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

FindPython.cmake in 3.27 returns the wrong Python_SITEARCH path which breaks 
the qgis build:

 -- Python site-packages: /usr/local/lib/python3.11/dist-packages

This was:

 -- Python site-packages: /usr/lib/python3/dist-packages

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: qgis
Source-Version: 3.28.9+dfsg-1
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
qgis, 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.
Bas Couwenberg  (supplier of updated qgis 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: Mon, 24 Jul 2023 06:19:51 +0200
Source: qgis
Architecture: source
Version: 3.28.9+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1041633
Changes:
 qgis (3.28.9+dfsg-1) unstable; urgency=medium
 .
   * Export DEB_PYTHON_INSTALL_LAYOUT=deb_system to fix FTBFS with CMake 3.27.0
 instead of a patch.
 (closes: #1041633)
   * Update symbols for other architectures.
   * Move from experimental to unstable.
Checksums-Sha1:
 b69fab22b8ce21913e12f3bd93da64bdecbf20a0 5384 qgis_3.28.9+dfsg-1.dsc
 0951514ce2a5a2368bc7f285f69ff0d0a89f36ad 435176 
qgis_3.28.9+dfsg-1.debian.tar.xz
 0d2f97d79f979674eb9e1d7e09fd8c3dc519fa50 41203 
qgis_3.28.9+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 c428a35e9987c524b9b532216ea2dc38f41058e78981ade80f0df4f4efa69bc9 5384 
qgis_3.28.9+dfsg-1.dsc
 3f33dbc98e406dae8843ed5c77ca1c737d048a9418dfba30d6cecc27ff2f8f42 435176 
qgis_3.28.9+dfsg-1.debian.tar.xz
 7e6d6994183ade18cb3936fb23de5d93c53bb8fe6e607df29ac4905cb41e9729 41203 
qgis_3.28.9+dfsg-1_amd64.buildinfo
Files:
 cbcfda236682e504dbe04253694bd1d9 5384 science optional qgis_3.28.9+dfsg-1.dsc
 5992e4b80902956c6b34501d6abc6941 435176 science optional 
qgis_3.28.9+dfsg-1.debian.tar.xz
 277e0a57ad8a63e3c5840431101ee57c 41203 science optional 
qgis_3.28.9+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmS+E38ACgkQZ1DxCuiN
SvE6ig/8DVWKl6BpCHKz8GRmzCS2wVDhI6V7FID5JDvgsvFD2QxUYX1TtUhnkQeK
9ATcASaL/xemDTvOZQ/BNi//wznT9D9kcfm3Fak3SpX6AhhXuNQyoPnu+LnYb6qw
hcBKNY3Zo3ARrst1pQ9DUL9S7Fjf5aiYxRm777Fd6LYCFL4ARBegK52AJHlA/8X8
mghBfe+BoNSZJ8wj5wTqsndn/WRgqTDJ6ojgMMorTqOuIzCFJeEo/6twTUiBYl5Q
3VQl8zELj64TnE5dzzTKSYimgkvGaROIKc88uEMYniAj1z70LsJLk/53dUvD070U
Qj8WOmV9XuW54aF+Imssuo1YX/BDP5RlZPYzMR/djv3V1W2tW/drOxwFleMrsvqj
w/dtvKKzwys/rIPIblNwDaOOlT/s3yNSTXDdFiiYwJgZk2iKTusOIuH9CeKKSFqt
2aWl5wRZU8XEMkZqg1wPa8qmXUt0zf5iw1P3aJv8P5bGHQISGay0YsXYjqZih4wD
egxL8GhNhldlhy1zYrkSRBIoIY2/QoKP+QTUb2cKEKFrT9lBseAJGoOLvON7GU5X
9A9zTJiSNHLuw0r/VP4MZ87V2AW8K5ikuPWrx8HxLvaLn8V3ozl/t8++a2LLMtMd
GSMqp/M13sJ20NQKkoP0PG2b/2or5qLGB/0nYurLj2SzBlN7fHk=
=sGoR
-END PGP SIGNATURE End Message ---

Bug#1034348: at: autopkgtest regression on arm64

[Paul Gevers]

Hi,

For the record.

On 24-07-2023 04:21, Debian Bug Tracking System wrote:

Another happy at user here.

Jose M Calhariz  wrote:

Hi, I believe my last update fixed the problem can someone double check?

That was at 3.2.5-2, right?  Closing this bug: afaik nobody has been able to
reproduce the issue.  Therefore better to close and see what happens next.

Please reopen if you feel this is not appropriate.


When I look at the history of the failures, it seems that something else 
fixed the issue. E.g on arm64 [1], we can see the test started to pass 
between 2023-04-13 and 2023-05-12. I first thought this aligned with me 
updating the host systems, but that happened earlier IIRC.


Paul

[1] https://ci.debian.net/packages/a/at/testing/arm64/


OpenPGP_signature
Description: OpenPGP digital signature