Processed: reopen the bug -- 1067410

[Debian Bug Tracking System]

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

> reopen 1067410
Bug #1067410 {Done: Bo YU } 
[golang-github-go-jose-go-jose-dev] golang-github-go-jose-go-jose-dev: ftbfs on 
i386 and mips64el due to timeout of test case
'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 golang-github-go-jose-go-jose/4.0.1-3.
>
End of message, stopping processing here.

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

Processed: severity of 1067059 is important, user release.debian....@packages.debian.org, usertagging 1067059

[Debian Bug Tracking System]

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

> severity 1067059 important
Bug #1067059 {Done: Youhei SASAKI } [src:ruby-hdfeos5] 
ruby-hdfeos5: FTBFS with gcc-14 (-Werror=implicit-function-declaration)
Severity set to 'important' from 'serious'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
sebas...@debian.org).
> usertags 1067059 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> thanks
Stopping processing here.

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

Bug#1067474: gxr-openvr: package Build-Depends on libgxr-0.15-0 whic is no longer built

[Michael Hudson-Doyle]

Package: gxr-openvr
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * s/libgxr-0.15-0/libgxr-dev/ in Build-Depends.

Thanks for considering the patch.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gxr-openvr-0.15.1/debian/control gxr-openvr-0.15.1/debian/control
--- gxr-openvr-0.15.1/debian/control2024-03-08 18:00:00.0 +1300
+++ gxr-openvr-0.15.1/debian/control2024-03-22 18:20:57.0 +1300
@@ -1,8 +1,7 @@
 Source: gxr-openvr
 Section: contrib/libs
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Andrew Lee (李健秋) 
+Maintainer: Andrew Lee (李健秋) 
 Uploaders: Héctor Orón Martínez 
 Build-Depends:
  debhelper (>= 11),
@@ -12,7 +11,7 @@
  gtk-doc-tools,
  libgtk-3-dev (>= 3.22),
  libgulkan-dev (>= 0.15.0),
- libgxr-0.15-0,
+ libgxr-dev,
  libjson-glib-dev,
  libopenvr-dev,
  mesa-common-dev,

Bug#1012975: marked as done (libcypher-parser: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Fri, 22 Mar 2024 05:08:31 +
with message-id 
and subject line Bug#1012975: fixed in libcypher-parser 0.6.2-0.1
has caused the Debian Bug report #1012975,
regarding libcypher-parser: ftbfs with GCC-12
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.)


-- 
1012975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcypher-parser
Version: 0.6.0-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -pthread  -Wpedantic -Wvla -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11 -fvisibility=hidden -pipe -Wall -W -Werror   
  -Wno-unused-parameter -Wno-missing-field-initializers -Wpointer-arith 
-Wstrict-prototypes -Wcast-qual -Wcast-align -Wno-error=unused-function 
-Wno-error=unused-variable -Wno-error=deprecated-declarations -c -o 
libcypher_parser_la-ast_expression.lo `test -f 'ast_expression.c' || echo 
'./'`ast_expression.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -Wpedantic -Wvla -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11 -fvisibility=hidden -pipe -Wall -W -Werror 
-Wno-unused-parameter -Wno-missing-field-initializers -Wpointer-arith 
-Wstrict-prototypes -Wcast-qual -Wcast-align -Wno-error=unused-function 
-Wno-error=unused-variable -Wno-error=deprecated-declarations -c 
ast_expression.c  -fPIC -DPIC -o .libs/libcypher_parser_la-ast_expression.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -Wpedantic -Wvla -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11 -fvisibility=hidden -pipe -Wall -W -Werror 
-Wno-unused-parameter -Wno-missing-field-initializers -Wpointer-arith 
-Wstrict-prototypes -Wcast-qual -Wcast-align -Wno-error=unused-function 
-Wno-error=unused-variable -Wno-error=deprecated-declarations -c 
ast_expression.c -o libcypher_parser_la-ast_expression.o >/dev/null 2>&1
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -pthread  -Wpedantic -Wvla -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11 -fvisibility=hidden -pipe -Wall -W -Werror   
  -Wno-unused-parameter -Wno-missing-field-initializers -Wpointer-arith 
-Wstrict-prototypes -Wcast-qual -Wcast-align -Wno-error=unused-function 
-Wno-error=unused-variable -Wno-error=deprecated-declarations -c -o 
libcypher_parser_la-ast_extract.lo `test -f 'ast_extract.c' || echo 
'./'`ast_extract.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -Wpedantic -Wvla -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11 -fvisibility=hidden -pipe -Wall -W -Werror 
-Wno-unused-parameter -Wno-missing-field-initializers -Wpointer-arith 

Processed: unarchiving 1061899, severity of 1061899 is important, user release.debian....@packages.debian.org ...

[Debian Bug Tracking System]

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

> unarchive 1061899
Bug #1061899 {Done: Michael Hudson-Doyle } 
[src:comedilib] comedilib: NMU diff for 64-bit time_t transition
Unarchived Bug 1061899
> severity 1061899 important
Bug #1061899 {Done: Michael Hudson-Doyle } 
[src:comedilib] comedilib: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
sebas...@debian.org).
> usertags 1061899 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1061928
Bug #1061928 {Done: Steve Langasek } [src:avro-c] avro-c: 
NMU diff for 64-bit time_t transition
Unarchived Bug 1061928
> severity 1061928 important
Bug #1061928 {Done: Steve Langasek } [src:avro-c] avro-c: 
NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1061928 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1062051
Bug #1062051 {Done: Steve Langasek } [src:cglm] cglm: NMU 
diff for 64-bit time_t transition
Unarchived Bug 1062051
> severity 1062051 important
Bug #1062051 {Done: Steve Langasek } [src:cglm] cglm: NMU 
diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1062051 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1062184
Bug #1062184 {Done: Steve Langasek } [src:gnucap] gnucap: 
NMU diff for 64-bit time_t transition
Unarchived Bug 1062184
> severity 1062184 important
Bug #1062184 {Done: Steve Langasek } [src:gnucap] gnucap: 
NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1062184 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1062277
Bug #1062277 {Done: Steve Langasek } [src:libdvbpsi] 
libdvbpsi: NMU diff for 64-bit time_t transition
Unarchived Bug 1062277
> severity 1062277 important
Bug #1062277 {Done: Steve Langasek } [src:libdvbpsi] 
libdvbpsi: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1062277 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1062291
Bug #1062291 {Done: Steve Langasek } [src:libfido2] 
libfido2: NMU diff for 64-bit time_t transition
Unarchived Bug 1062291
> severity 1062291 important
Bug #1062291 {Done: Steve Langasek } [src:libfido2] 
libfido2: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1062291 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1062333
Bug #1062333 {Done: Steve Langasek } [src:discover] 
discover: NMU diff for 64-bit time_t transition
Unarchived Bug 1062333
> severity 1062333 important
Bug #1062333 {Done: Steve Langasek } [src:discover] 
discover: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1062333 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1062632
Bug #1062632 {Done: Luca Boccassi } [src:libsolv] libsolv: 
NMU diff for 64-bit time_t transition
Unarchived Bug 1062632
> severity 1062632 important
Bug #1062632 {Done: Luca Boccassi } [src:libsolv] libsolv: 
NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1062632 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1062865
Bug #1062865 {Done: Jochen Sprickerhof } 
[src:ros-bond-core] ros-bond-core: NMU diff for 64-bit time_t transition
Unarchived Bug 1062865
> severity 1062865 important
Bug #1062865 {Done: Jochen Sprickerhof } 
[src:ros-bond-core] ros-bond-core: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1062865 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1063105
Bug #1063105 {Done: Steve Langasek } [src:alsa-oss] 
alsa-oss: NMU diff for 64-bit time_t transition
Unarchived Bug 1063105
> severity 1063105 important
Bug #1063105 {Done: Steve Langasek } [src:alsa-oss] 
alsa-oss: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1063105 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1063140
Bug #1063140 {Done: Steve Langasek } [src:mpg123] mpg123: 
NMU diff for 64-bit time_t transition
Unarchived Bug 1063140
> severity 1063140 important
Bug #1063140 {Done: Steve Langasek } [src:mpg123] mpg123: 
NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1063140 time-t-downgrade
Usertags were: time-t-downgrade.
Usertags are now: time-t-downgrade.
> unarchive 1063888
Bug #1063888 {Done: Steve Langasek } [src:zfs-linux] 
zfs-linux: NMU diff for 64-bit time_t transition
Unarchived Bug 1063888
> severity 1063888 important

Bug#1067399: marked as done (openjdk-17-jre: uninstallable (depends on wrong libraries))

[Debian Bug Tracking System]

Your message dated Fri, 22 Mar 2024 04:41:39 + (UTC)
with message-id 
and subject line Re: openjdk-17-jre: uninstallable (depends on wrong libraries)
has caused the Debian Bug report #1067399,
regarding openjdk-17-jre: uninstallable (depends on wrong libraries)
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.)


-- 
1067399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-17-jre
Version: 17.0.11~6ea-1
Severity: serious
Justification: uninstallable

Depends: openjdk-17-jre-headless (= 17.0.11~6ea-1),
 libglib2.0-0t64 (>= 2.24), […], libcups2, […]

This must of course be libcups2t64.
--- End Message ---
--- Begin Message ---
Version: 17.0.11~7ea-1

This appears fixed now.--- End Message ---

Bug#1067059: marked as done (ruby-hdfeos5: FTBFS with gcc-14 (-Werror=implicit-function-declaration))

[Debian Bug Tracking System]

Your message dated Fri, 22 Mar 2024 04:06:57 +
with message-id 
and subject line Bug#1067059: fixed in ruby-hdfeos5 1.2-12
has caused the Debian Bug report #1067059,
regarding ruby-hdfeos5: FTBFS with gcc-14 
(-Werror=implicit-function-declaration)
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.)


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

Dear Maintainer,

Your package FTBFS in unstable:

 hdfeos5pt_wrap.c: In function ‘sort_data_byte’:
 hdfeos5pt_wrap.c:329:14: error: implicit declaration of function 
‘HE5_PTreadlevelF’; did you mean ‘HE5_PTreadlevel’? 
[-Werror=implicit-function-declaration]
   329 | status = HE5_PTreadlevelF(i_ptid, i_level, o_linkfield, 
H5T_NATIVE_CHAR, o_data_parent);
   |  ^~~~
   |  HE5_PTreadlevel

 
https://buildd.debian.org/status/fetch.php?pkg=ruby-hdfeos5=amd64=1.2-11%2Bb4=1710703222=log

See also: 
https://gcc.gnu.org/gcc-14/porting_to.html#implicit-function-declaration

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: ruby-hdfeos5
Source-Version: 1.2-12
Done: Youhei SASAKI 

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

Debian distribution maintenance software
pp.
Youhei SASAKI  (supplier of updated ruby-hdfeos5 
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: Tue, 19 Mar 2024 15:28:16 +0900
Source: ruby-hdfeos5
Architecture: source
Version: 1.2-12
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Youhei SASAKI 
Closes: 1067059
Changes:
 ruby-hdfeos5 (1.2-12) unstable; urgency=medium
 .
   [ Bas Couwenberg ]
   * Rename salsa-ci.yml to .gitlab-ci.yml.
   * Bump Standards-Version to 4.6.2, no changes.
   * Drop obsolete ruby-interpreter dependency alternative.
   * Bump debhelper compat to 13.
   * Remove generated files in clean target.
   * Switch to dh-sequence-*.
   * Add patch to fix FTBFS with GCC 14.
 (closes: #1067059)
 .
   [ Youhei SASAKI ]
   * Remove X?-Ruby-Versions fields from d/control
   * d/watch: Update URI, https
   * d/patches/gcc-14.patch: Add Patch Tag, Forwarded: not-needed
Checksums-Sha1:
 78a0649851b0e8875a2d5f60a38614192493c18a 2178 ruby-hdfeos5_1.2-12.dsc
 8217012ef58c5cfbc7ba4a9e2c57fb0cb82f8ea8 22460 
ruby-hdfeos5_1.2-12.debian.tar.xz
 ead272441c4f25bffce8546a87b94f8021d64bc0 10507 
ruby-hdfeos5_1.2-12_amd64.buildinfo
Checksums-Sha256:
 d83cb03486ad1a7a19464b3a54f5a29395bb389d290d2fac867928ff509febc1 2178 
ruby-hdfeos5_1.2-12.dsc
 5b2503e365ad5949eb513adfde86f944ce6bcdb7271bff7ef8aa0ccdf7279188 22460 
ruby-hdfeos5_1.2-12.debian.tar.xz
 9b2ef7e4522cd1ad5f2afbaa79796beda0e0963e9a08d6294d2952a9aea5c0a9 10507 
ruby-hdfeos5_1.2-12_amd64.buildinfo
Files:
 760751d91343052571a2ae628c3a8aba 2178 ruby optional ruby-hdfeos5_1.2-12.dsc
 5c7185a4fbde331e5727801328bcffc4 22460 ruby optional 
ruby-hdfeos5_1.2-12.debian.tar.xz
 896f4e483c8d3ed18f334d1a9f0af74f 10507 ruby optional 
ruby-hdfeos5_1.2-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZqTqcE/iQFWNasLmk5TzVIkdfgcFAmX89aMACgkQk5TzVIkd
fgcdDw/+OVro2JV8PNjt0LmxAsHUcEyaoI2pl0P+3fxhWuyi3s/RGI6lP7/N+4Se
LmQdM/xAef7qm/9U5X52dRMqUzD/pYs4OgutZSzOhxj/VAL6nRHMqOiv0k3GjAp2
eN/m+ufId/Dr739EY3vGxmuIHo7IIvrvKzAS0LAm1HBVtV3rtILxHw5DRy3WoSbF
mvI5jLHp1Vqpz9Qya/9rOTIPFWpn93ciOEnefD+0bU54RPoMW3wZ2lSia85BB0k0
UwmMeohBvfWGF+EpgyhWcDNMxYakBi92422Y3+LolAqYYHxgvMFPzzSeBsHKJrkR
dHN/c4rSvUTzO6DC8sph//z776ERw4MZQzCci4tQwiyMTdYRvR8kEg/fXWxFClGK
Bv/bBZ0KX0CN/LJENXLIRzgQ5JG17HC+gJDZ6WVtCNj4r2YhqCjiUXPtp3qNLCOX
yz3IScFqghO4LyhWvFL1Kw5uNUoFZBkl6qXc4YeOBxQM/x8AZYsYchVp22BZAN2S
c2E3OYOp1xrrHMjPKkqm5T1U7VyOJbBv3tWI7PqKzMo9FSj3vSL35CioYbAE5TWF
AvCTRbOJE4jWIRRGNpdBTzCN54A1BshBmE8vTatM6vJGQsVJnd9GsBoslviyxWbZ
qn60TIXzS3BGCq1bzEsJu1tesdjgX0WIUWBck8gQ5G+NAd1IUaA=
=/g/x
-END PGP SIGNATURE-

Bug#1065779: marked as done (libcdk5: FTBFS on arm{el,hf}: configure:7804:12: error: implicit declaration of function 'tgoto' [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Fri, 22 Mar 2024 03:56:35 +
with message-id 
and subject line Bug#1065779: fixed in libcdk5 5.0.20230201-2
has caused the Debian Bug report #1065779,
regarding libcdk5: FTBFS on arm{el,hf}: configure:7804:12: error: implicit 
declaration of function 'tgoto' [-Werror=implicit-function-declaration]
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=libcdk5=armel=5.0.20180306-3.1=1709540851=0

configure:7811: gcc -c -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fPIE 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_DEFAULT_SOURCE conftest.c >&5
configure: In function 'main':
configure:7804:12: error: implicit declaration of function 'tgoto' 
[-Werror=implicit-function-declaration]
 7804 | {
  |^
cc1: some warnings being treated as errors
configure:7814: $? = 1
configure: failed program was:
#line 7799 "configure"
#include "confdefs.h"
#include 
int
main (void)
{
initscr(); tgoto("?", 0,0)
  ;
  return 0;
}
configure:7811: gcc -c -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fPIE 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_DEFAULT_SOURCE conftest.c >&5
configure: In function 'main':
configure:7804:12: error: implicit declaration of function 'tgoto' 
[-Werror=implicit-function-declaration]
 7804 | {
  |^
cc1: some warnings being treated as errors
configure:7814: $? = 1
configure: failed program was:
#line 7799 "configure"
#include "confdefs.h"
#include 
int
main (void)
{
initscr(); tgoto("?", 0,0)
  ;
  return 0;
}
configure:7811: gcc -c -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fPIE 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_DEFAULT_SOURCE conftest.c >&5
configure:7800:10: fatal error: ncurses/ncurses.h: No such file or directory
 7800 | #include "confdefs.h"
  |  ^~~~   
compilation terminated.
configure:7814: $? = 1
configure: failed program was:
#line 7799 "configure"
#include "confdefs.h"
#include 
int
main (void)
{
initscr(); tgoto("?", 0,0)
  ;
  return 0;
}
configure:7811: gcc -c -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fPIE 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_DEFAULT_SOURCE conftest.c >&5
configure:7800:10: fatal error: ncurses/curses.h: No such file or directory
 7800 | #include "confdefs.h"
  |  ^~~~  
compilation terminated.
configure:7814: $? = 1
configure: failed program was:
#line 7799 "configure"
#include "confdefs.h"
#include 
int
main (void)
{
initscr(); tgoto("?", 0,0)
  ;
  return 0;
}
configure:7831: result: none
configure:7835: error: No curses header-files found

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libcdk5
Source-Version: 5.0.20230201-2
Done: Steve M. Robbins 

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated libcdk5 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: Thu, 21 Mar 2024 22:10:54 -0500
Source: libcdk5

Bug#1066702: marked as done (libcdk5: FTBFS: configure: error: No curses header-files found)

[Debian Bug Tracking System]

Your message dated Fri, 22 Mar 2024 03:56:35 +
with message-id 
and subject line Bug#1066702: fixed in libcdk5 5.0.20230201-2
has caused the Debian Bug report #1066702,
regarding libcdk5: FTBFS: configure: error: No curses header-files found
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.)


-- 
1066702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcdk5
Version: 5.0.20180306-3.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> checking for unistd.h... (cached) yes
> checking for mode_t... yes
> checking whether struct tm is in sys/time.h or time.h... time.h
> checking for extra include directories... no
> checking if we have identified curses headers... none
> configure: error: No curses header-files found
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/libcdk5_5.0.20180306-3.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libcdk5
Source-Version: 5.0.20230201-2
Done: Steve M. Robbins 

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated libcdk5 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: Thu, 21 Mar 2024 22:10:54 -0500
Source: libcdk5
Architecture: source
Version: 5.0.20230201-2
Distribution: unstable
Urgency: medium
Maintainer: Steve M. Robbins 
Changed-By: Steve M. Robbins 
Closes: 1065779 1066702
Changes:
 libcdk5 (5.0.20230201-2) unstable; urgency=medium
 .
   * Upload to unstable.  Closes: #1065779, #1066702.
Checksums-Sha1:
 f1836fcd99bc29f2c1fb8446ae27e3de0a2b78d9 2345 libcdk5_5.0.20230201-2.dsc
 69df57d45bc72577cda14aee2bb357c3263a8fa7 15496 
libcdk5_5.0.20230201-2.debian.tar.xz
 d3460b92361a4219f201fe5c3de9368c4485802e 6821 
libcdk5_5.0.20230201-2_source.buildinfo
Checksums-Sha256:
 5c5d1a4a6fec4d9f63db5e6cd5349af3c2bfec13a8b6799f6371a4e724fdbe63 2345 
libcdk5_5.0.20230201-2.dsc
 4caa732a71276ff38d40794ffca48230ddc1b044ba8e47648d8f9ad017c91d05 15496 
libcdk5_5.0.20230201-2.debian.tar.xz
 fcf7042d0bca9f2e917d9e57e10c691c8753010689e91f30887cd832736d6102 6821 
libcdk5_5.0.20230201-2_source.buildinfo
Files:
 b9fb5bb656c906658b6ec4183224262a 2345 libs optional libcdk5_5.0.20230201-2.dsc
 e9c3e45ffe8af358cc0e5e448d4ea76b 15496 libs optional 
libcdk5_5.0.20230201-2.debian.tar.xz
 2359a8606283f0ba0f094de4afc46af0 6821 libs optional 
libcdk5_5.0.20230201-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEy89k8fa3rclNjyokyeVeL63I9LkFAmX890wPHHNtckBkZWJp
YW4ub3JnAAoJEMnlXi+tyPS5jSEP/AlKzahfChHs8TZ2RhTjyq3Vn+rzFhGSKr+K
LLIoRHewcKOCUieCvf4J0Ffo5du9qDkFwgpCIa8E+b5UfYhJpXEINqPNmjicaDjf
5QgeSekwH7ehbpe0AhrVYqQ5V07KvSIrym1HFk71qz6lfjRLDWs1O6k8HeyXKAEG
KSyqT+GUoNmoUVe2pJoLDUJaJyq+O2BWLLXioaAvn/NX4v/mTv4+Xe5pb27Qxel2
vQ0SP6lcJDg+lVCKiaS8D06W3pD9524tdhAr2hSZ2eXeXI4o7SRnfWOdhKfuD5nI
f8NVyz5fxuigLY2snU8Nz9hCCnvun0GEtxDDbGHHKstSrz8axELp+FZsj8QQ0Bt1
eOCSpHmD13gf+lcigYhfl2SK1iH/u3c589AaXGGPR2AlM3zHELHDRbsJBlDkNvRD
pejYEesQVHltuT64klrpS4XcUIe1vu+5h9Yiz+U0rLC61lhjY1lEFaclIQ77kU+S

Bug#1067473: gambas3: ftbfs on time64 arches

[Michael Hudson-Doyle]

Package: gambas3
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com

Dear Maintainer,


In Ubuntu, the attached patch was applied to achieve the following:


  * s/libdumb1/libdump1t64/ in Build-Depends.


Thanks for considering the patch.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gambas3-3.19.0/debian/control gambas3-3.19.0/debian/control
--- gambas3-3.19.0/debian/control   2024-01-05 12:31:10.0 +1300
+++ gambas3-3.19.0/debian/control   2024-03-22 16:46:35.0 +1300
@@ -17,7 +16,7 @@
libcrypt-dev,
libcurl4-gnutls-dev | libcurl-ssl-dev,
libdbus-1-dev,
-   libdumb1,
+   libdumb1t64,
libffi-dev,
libglew-dev,
libgmime-3.0-dev,

Processed: Re: createrepo-c: FTBFS: xml_file.c:338:36: error: implicit declaration of function ‘rasprintf’; did you mean ‘g_sprintf’? [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066292 [src:createrepo-c] createrepo-c: FTBFS: xml_file.c:338:36: error: 
implicit declaration of function ‘rasprintf’; did you mean ‘g_sprintf’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066292: createrepo-c: FTBFS: xml_file.c:338:36: error: implicit declaration of function ‘rasprintf’; did you mean ‘g_sprintf’? [-Werror=implicit-function-declaration]

[Michael Hudson-Doyle]

Package: createrepo-c
Followup-For: Bug #1066292
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Control: tags -1 patch

Dear Maintainer,


In Ubuntu, the attached patch was applied to achieve the following:


  * Fix printing time_t and missing prototypes.


Thanks for considering the patch.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru createrepo-c-0.17.3/debian/patches/ftbfs.patch 
createrepo-c-0.17.3/debian/patches/ftbfs.patch
--- createrepo-c-0.17.3/debian/patches/ftbfs.patch  1970-01-01 
12:00:00.0 +1200
+++ createrepo-c-0.17.3/debian/patches/ftbfs.patch  2024-03-22 
15:53:53.0 +1300
@@ -0,0 +1,21 @@
+--- a/src/xml_dump_repomd.c
 b/src/xml_dump_repomd.c
+@@ -143,7 +143,7 @@
+BAD_CAST repomd->revision);
+ } else {
+ // Use the current time if no revision was explicitly specified
+-gchar *rev = g_strdup_printf("%ld", time(NULL));
++gchar *rev = g_strdup_printf("%lld", (long long)time(NULL));
+ xmlNewChild(root, NULL, BAD_CAST "revision", BAD_CAST rev);
+ g_free(rev);
+ }
+--- a/src/xml_file.c
 b/src/xml_file.c
+@@ -20,6 +20,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include "xml_file.h"
+ #include 
+ #include "error.h"
diff -Nru createrepo-c-0.17.3/debian/patches/series 
createrepo-c-0.17.3/debian/patches/series
--- createrepo-c-0.17.3/debian/patches/series   2023-01-06 11:16:32.0 
+1300
+++ createrepo-c-0.17.3/debian/patches/series   2024-03-22 15:52:17.0 
+1300
@@ -1,3 +1,4 @@
 python-path.patch
 python-skbuild-path.patch
 python-platlib-debian.patch
+ftbfs.patch

Bug#1066776: marked as done (responses: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 22 Mar 2024 01:42:55 +
with message-id 
and subject line Bug#1066776: fixed in responses 0.24.1-2
has caused the Debian Bug report #1066776,
regarding responses: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.12 3.11" returned exit code 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.)


-- 
1066776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: responses
Version: 0.24.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # The tests require local network (but not internet) access.
> # pybuild's setting of http_proxy=http://127.0.0.1:9/ breaks it.
> http_proxy= dh_auto_test
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_responses/build; python3.12 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.12.2, pytest-8.0.2, pluggy-1.4.0
> rootdir: /<>
> configfile: tox.ini
> plugins: pytest_httpserver-1.0.10, asyncio-0.20.3
> asyncio: mode=Mode.STRICT
> collected 211 items
> 
> responses/tests/test_matchers.py .   [ 
> 15%]
> responses/tests/test_multithreading.py ..[ 
> 20%]
> responses/tests/test_recorder.py [ 
> 22%]
> responses/tests/test_registries.py ...F. [ 
> 26%]
> responses/tests/test_responses.py .. [ 
> 44%]
>  [ 
> 78%]
> F
> [100%]
> 
> === FAILURES 
> ===
> _ test_registry_async 
> __
> 
> cls = 
> func = . at 0x7fd2dcdfbc40>
> when = 'call'
> reraise = (, )
> 
> @classmethod
> def from_call(
> cls,
> func: Callable[[], TResult],
> when: Literal["collect", "setup", "call", "teardown"],
> reraise: Optional[
> Union[Type[BaseException], Tuple[Type[BaseException], ...]]
> ] = None,
> ) -> "CallInfo[TResult]":
> """Call func, wrapping the result in a CallInfo.
> 
> :param func:
> The function to call. Called without arguments.
> :param when:
> The phase in which the function is called.
> :param reraise:
> Exception or exceptions that shall propagate if raised by the
> function, instead of being wrapped in the CallInfo.
> """
> excinfo = None
> start = timing.time()
> precise_start = timing.perf_counter()
> try:
> >   result: Optional[TResult] = func()
> 
> /usr/lib/python3/dist-packages/_pytest/runner.py:342: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/_pytest/runner.py:263: in 
> lambda: ihook(item=item, **kwds), when=when, reraise=reraise
> /usr/lib/python3/dist-packages/pluggy/_hooks.py:501: in __call__
> return self._hookexec(self.name, self._hookimpls.copy(), kwargs, 
> firstresult)
> /usr/lib/python3/dist-packages/pluggy/_manager.py:119: in _hookexec
> return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
> /usr/lib/python3/dist-packages/_pytest/threadexception.py:87: in 
> pytest_runtest_call
> yield from thread_exception_runtest_hook()
> /usr/lib/python3/dist-packages/_pytest/threadexception.py:63: in 
> thread_exception_runtest_hook
> yield
> /usr/lib/python3/dist-packages/_pytest/unraisableexception.py:90: in 
> pytest_runtest_call
> yield from unraisable_exception_runtest_hook()
> /usr/lib/python3/dist-packages/_pytest/unraisableexception.py:65: in 
> unraisable_exception_runtest_hook
> yield
> /usr/lib/python3/dist-packages/_pytest/logging.py:839: in pytest_runtest_call
> yield from self._runtest_for(item, "call")
> /usr/lib/python3/dist-packages/_pytest/logging.py:822: in _runtest_for
> yield
> /usr/lib/python3/dist-packages/_pytest/capture.py:882: in pytest_runtest_call
> return (yield)
> /usr/lib/python3/dist-packages/_pytest/skipping.py:256: in pytest_runtest_call
> return (yield)

Bug#1067468: these tests also fail with openmpi on amd64 and ppc64el

[Samuel Thibault]

Matthias Klose, le ven. 22 mars 2024 01:11:09 +0100, a ecrit:
> these tests also fail with openmpi on amd64 and ppc64el

? I can't reproduce this.

Samuel

Processed: these tests also fail with openmpi on amd64 and ppc64el

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 eztrace fails openmpi tests on arm64, amd64, ppc64el
Bug #1067468 [src:eztrace] eztrace fails openmpi tests on arm64
Changed Bug title to 'eztrace fails openmpi tests on arm64, amd64, ppc64el' 
from 'eztrace fails openmpi tests on arm64'.

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

Bug#1067468: these tests also fail with openmpi on amd64 and ppc64el

[Matthias Klose]

Control: retitle -1 eztrace fails openmpi tests on arm64, amd64, ppc64el

these tests also fail with openmpi on amd64 and ppc64el

Bug#1067368: marked as done (ngspetsc: FTBFS: unsatisfiable build-dependencies (purely virtual?): libocct-data-exchange-7.6 (>= 7.6.3+dfsg1), libocct-ocaf-7.6 (>= 7.6.3+dfsg1))

[Debian Bug Tracking System]

Your message dated Fri, 22 Mar 2024 00:37:00 +0100
with message-id <5b236d764ee2e61bf38dbb58a560c...@debian.org>
and subject line Re: Bug#1067368 ngspetsc: FTBFS: unsatisfiable 
build-dependencies (purely virtual?): libocct-data-exchange-7.6
has caused the Debian Bug report #1067368,
regarding ngspetsc: FTBFS: unsatisfiable build-dependencies (purely virtual?): 
libocct-data-exchange-7.6 (>= 7.6.3+dfsg1), libocct-ocaf-7.6 (>= 7.6.3+dfsg1)
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.)


-- 
1067368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ngspetsc
Version: 0.0~git20240130.0c8a05b-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-python3, fenicsx, 
> libpetsc-real-dev, pybuild-plugin-pyproject, python3-setuptools, python3, 
> python3-petsc4py, python3-mpi4py, python3-netgen, python3-numpy, 
> python3-pytest, python3-sphinx, python3-sphinx-autodoc-typehints, pandoc, 
> python3-ipython, python3-nbsphinx, python3-sphinx-rtd-theme, build-essential, 
> fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-python3, 
> fenicsx, libpetsc-real-dev, pybuild-plugin-pyproject, python3-setuptools, 
> python3, python3-petsc4py, python3-mpi4py, python3-netgen, python3-numpy, 
> python3-pytest, python3-sphinx, python3-sphinx-autodoc-typehints, pandoc, 
> python3-ipython, python3-nbsphinx, python3-sphinx-rtd-theme, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [977 B]
> Get:5 copy:/<>/apt_archive ./ Packages [954 B]
> Fetched 2540 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libnglib-6.2t64 : Depends: libocct-data-exchange-7.6 (>= 7.6.3+dfsg1)
>Depends: libocct-ocaf-7.6 (>= 7.6.3+dfsg1)
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/ngspetsc_0.0~git20240130.0c8a05b-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---

You got caught in the middle of the 64-bit time_t t64 transition.--- End Message ---

Bug#1066490: marked as done (motif: FTBFS: XpmCrBufFrI.c:155:5: error: implicit declaration of function ‘strcpy’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 23:46:22 +
with message-id 
and subject line Bug#1066490: fixed in motif 2.3.8-3.1
has caused the Debian Bug report #1066490,
regarding motif: FTBFS: XpmCrBufFrI.c:155:5: error: implicit declaration of 
function ‘strcpy’ [-Werror=implicit-function-declaration]
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.)


-- 
1066490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: motif
Version: 2.3.8-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../../include -I.. -I./.. -DXMBINDDIR_FALLBACK=\"/usr/share/X11/bindings\" 
> -DINCDIR=\"/usr/include/X11\" -DLIBDIR=\"/usr/lib/x86_64-linux-gnu/X11\" 
> -DX11RGBPATH=\"/etc/X11/rgb.txt\"   -Wdate-time -D_FORTIFY_SOURCE=2  
> -I/usr/include/freetype2 -I/usr/include/libpng16   -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -D_FILE_OFFSET_BITS=64 -Wall -g 
> -fno-strict-aliasing -Wno-unused -Wno-comment -I/usr/include/freetype2 
> -I/usr/include/libpng16-c -o XpmCrBufFrP.lo XpmCrBufFrP.c
> XpmCrBufFrI.c: In function ‘XmeXpmCreateBufferFromXpmImage’:
> XpmCrBufFrI.c:155:5: error: implicit declaration of function ‘strcpy’ 
> [-Werror=implicit-function-declaration]
>   155 | strcpy(ptr, buf);
>   | ^~
> XpmCrBufFrI.c:47:1: note: include ‘’ or provide a declaration of 
> ‘strcpy’
>46 | #include "XpmI.h"
>   +++ |+#include 
>47 | 
> XpmCrBufFrI.c:155:5: warning: incompatible implicit declaration of built-in 
> function ‘strcpy’ [-Wbuiltin-declaration-mismatch]
>   155 | strcpy(ptr, buf);
>   | ^~
> XpmCrBufFrI.c:155:5: note: include ‘’ or provide a declaration of 
> ‘strcpy’
> XpmCrBufFrI.c: In function ‘WriteColors’:
> XpmCrBufFrI.c:292:9: error: implicit declaration of function ‘strncpy’ 
> [-Werror=implicit-function-declaration]
>   292 | strncpy(s, *defaults++, cpp);
>   | ^~~
> XpmCrBufFrI.c:292:9: note: include ‘’ or provide a declaration of 
> ‘strncpy’
> XpmCrBufFrI.c:292:9: warning: incompatible implicit declaration of built-in 
> function ‘strncpy’ [-Wbuiltin-declaration-mismatch]
> XpmCrBufFrI.c:292:9: note: include ‘’ or provide a declaration of 
> ‘strncpy’
> XpmCrBufFrI.c:312:9: warning: incompatible implicit declaration of built-in 
> function ‘strcpy’ [-Wbuiltin-declaration-mismatch]
>   312 | strcpy(s, "\",\n");
>   | ^~
> XpmCrBufFrI.c:312:9: note: include ‘’ or provide a declaration of 
> ‘strcpy’
> XpmCrBufFrI.c:316:45: error: implicit declaration of function ‘strlen’ 
> [-Werror=implicit-function-declaration]
>   316 |(*data_size + l - *used_size) <= strlen(buf))
>   | ^~
> XpmCrBufFrI.c:316:45: note: include ‘’ or provide a declaration of 
> ‘strlen’
> XpmCrBufFrI.c:316:45: warning: incompatible implicit declaration of built-in 
> function ‘strlen’ [-Wbuiltin-declaration-mismatch]
> XpmCrBufFrI.c:316:45: note: include ‘’ or provide a declaration of 
> ‘strlen’
> XpmCrBufFrI.c: In function ‘WritePixels’:
> XpmCrBufFrI.c:352:13: warning: incompatible implicit declaration of built-in 
> function ‘strncpy’ [-Wbuiltin-declaration-mismatch]
>   352 | strncpy(s, colors[*pixels].string, cpp); /* how can we 
> trust *pixels? :-\ */
>   | ^~~
> XpmCrBufFrI.c:352:13: note: include ‘’ or provide a declaration of 
> ‘strncpy’
> XpmCrBufFrI.c:357:9: warning: incompatible implicit declaration of built-in 
> function ‘strcpy’ [-Wbuiltin-declaration-mismatch]
>   357 | strcpy(s, "\",\n");
>   | ^~
> XpmCrBufFrI.c:357:9: note: include ‘’ or provide a declaration of 
> ‘strcpy’
> XpmCrBufFrI.c:365:9: warning: incompatible implicit declaration of built-in 
> function ‘strncpy’ [-Wbuiltin-declaration-mismatch]
>   365 | strncpy(s, colors[*pixels].string, cpp); /* how can we trust 
> *pixels? */
>   |

Bug#1067468: eztrace fails openmpi tests on arm64

[Matthias Klose]

Package: src:eztrace
Version: 2.1-7
Severity: serious
Tags: sid trixie ftbfs

eztrace fails openmpi tests on arm64:

67% tests passed, 2 tests failed out of 6

Total Test time (real) =  22.42 sec

The following tests FAILED:
  2 - mpi_tests (Failed)
  6 - mpi_tests (Failed)
Errors while running CTest
make[2]: *** [Makefile:74: test] Error 8
make[2]: Leaving directory '/<>/build-openmpi'


maybe you could try to run all test suites before failing, if one of the 
test suites fails?

Bug#1067459: marked as done (connectgram: Please update or drop qt6 dependencies)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 22:51:04 +
with message-id 
and subject line Bug#1067459: fixed in connectagram 1.3.5-2
has caused the Debian Bug report #1067459,
regarding connectgram: Please update or drop qt6 dependencies
to be marked as done.

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

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


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

Package: connectagram
Version: 1.3.5-1
Severity: serious

Dear Maintainer,


Looks like you are adding some runtime dependencies as build-dependencies

Thanks for considering the patch.

--- connectagram-1.3.5/debian/control   2024-03-12 02:50:36.0 +0100
+++ connectagram-1.3.5/debian/control   2024-03-21 21:36:00.0 +0100
@@ -10,9 +9,6 @@
   qt6-l10n-tools,
   qt6-tools-dev-tools,
   qt6-base-dev-tools,
-  libqt6widgets6,
-  libqt6gui6,
-  libqt6core6,
   mesa-common-dev,
   debhelper-compat (= 13)
 Standards-Version: 4.6.2


G.
--- End Message ---
--- Begin Message ---
Source: connectagram
Source-Version: 1.3.5-2
Done: Alexandre Detiste 

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

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated connectagram 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: Thu, 21 Mar 2024 23:07:00 +0100
Source: connectagram
Architecture: source
Version: 1.3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Alexandre Detiste 
Closes: 1067459
Changes:
 connectagram (1.3.5-2) unstable; urgency=medium
 .
   * Team Upload
   * do not add runtime dependencies as build-dependencies (Closes: #1067459)
Checksums-Sha1:
 35286fa63b4eec2209073af0942db1bf43b5dbb0 2141 connectagram_1.3.5-2.dsc
 840b88e3dfdfe0ca497e95c334457940adf9f1d7 6448 
connectagram_1.3.5-2.debian.tar.xz
 cddc77d522c86f5c3268d4087c61a4c95c171a4b 12277 
connectagram_1.3.5-2_source.buildinfo
Checksums-Sha256:
 103c1d476205cb0304aecc5a3eae5a771d33378fb9ccdd2f46a160877471125b 2141 
connectagram_1.3.5-2.dsc
 2c894adee6bd8b8a784322920f86ce47612ce9bf3b2b2cdb6c9be46617ced206 6448 
connectagram_1.3.5-2.debian.tar.xz
 1103313fc1e1ad810a2ad85c746d523a6dbe0c6ff0ea3d0de965a729489d7dfd 12277 
connectagram_1.3.5-2_source.buildinfo
Files:
 fa9b7c8ec22e69ed09e91b16e13d3dd8 2141 games optional connectagram_1.3.5-2.dsc
 1098aa3c2ff9dc43a3db11a88e48cd75 6448 games optional 
connectagram_1.3.5-2.debian.tar.xz
 9f4d6b1e74e74081a7baeadba8964ad4 12277 games optional 
connectagram_1.3.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmX8sRcRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBo1iQ//ZDzaeQB1yoZvh2ghUN3U8OqE3uQgQYpC
s6YZ/Nc/tfW4p5Q7UhoHQ5aF3GaXx6uIfbHDTBNyZDlio11QOeJ4EdE5BjGKSD8k
szbg9cAL5pSZT4VV3Hom2zadA6o6cCJefYTwbdjuK37r8QajNsaqz2/LwgJ7uImj
n3gNSQVBFVaL2KPGjVNiiKumLaNuencSiviXRE1+n6K/XZybmbN3ImLkKyhmp9JV
VS9HC90HvOCa8N5fLn/nwVvOltUAeGXHgJgiMRNUnBWe4vjqdVe1l2sTFtY6Qrnn
gbzfoiI/gjtPfVcRuMFqx3CVQ0gcXP/sUCQ/pQxYPd5in0LHfeOM6H6Z4QjuTa9e
1tt0U+KeoQiuqS4LObHhp8Rnc6/3+MNX6x0J6iH0cRsYL8vTo3s6ltDDGDGyl4Oq
0YnZivQKRv4Pbw2UUHE591Aj47tsiAjamh6nB8A/py4s8fVkH/OqX9Iu4eLb58Y8
adO75mxdKyhNujm7DHXaiBA0r2Q/sNsSU162WvMKckLWaR5TEyUmS+GcNS33wcs1
Lg+NdqNeQXH7Dmh/nGk+Pt3t1i7JJL2uWfXq0x0zqJG8YdXKU+FKZDyld+lqiDjk
tecWAJy3ziG/sXSM3Tx7ing+o8d3zEQ8pQIEt8Yzhu/Pw8/YJ92Gg764jHmyRuuW
kC/wB5yl0oI=
=8hgK
-END PGP SIGNATURE-



pgp_x8g31AUv9.pgp
Description: PGP signature
--- End Message ---

Processed: tagging 1066490

[Debian Bug Tracking System]

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

> tags 1066490 + pending
Bug #1066490 [src:motif] motif: FTBFS: XpmCrBufFrI.c:155:5: error: implicit 
declaration of function ‘strcpy’ [-Werror=implicit-function-declaration]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 1066490

[Debian Bug Tracking System]

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

> tags 1066490 + patch
Bug #1066490 [src:motif] motif: FTBFS: XpmCrBufFrI.c:155:5: error: implicit 
declaration of function ‘strcpy’ [-Werror=implicit-function-declaration]
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1066490: motif: FTBFS: XpmCrBufFrI.c:155:5: error: implicit declaration of function ‘strcpy’ [-Werror=implicit-function-declaration]

[Samuel Thibault]

Hello,

Lucas Nussbaum, le mer. 13 mars 2024 12:53:39 +0100, a ecrit:
> > XpmCrBufFrI.c:155:5: error: implicit declaration of function ‘strcpy’ 
> > [-Werror=implicit-function-declaration]
> >   155 | strcpy(ptr, buf);
> >   | ^~

Given the severity, the importance of the package, the time_t rebuild
issues, and the simplicity of a fix, I have uploaded the attached
changes to DELAYED/0.

Samuel
diff -Nru motif-2.3.8/debian/changelog motif-2.3.8/debian/changelog
--- motif-2.3.8/debian/changelog2020-07-02 11:30:19.0 +0200
+++ motif-2.3.8/debian/changelog2024-03-21 23:42:09.0 +0100
@@ -1,3 +1,10 @@
+motif (2.3.8-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * patches/implicit: Fix build with qa=+bug-implicit-func (Closes: #1066490)
+
+ -- Samuel Thibault   Thu, 21 Mar 2024 23:42:09 +0100
+
 motif (2.3.8-3) unstable; urgency=medium
 
   [ Graham Inggs ]
diff -Nru motif-2.3.8/debian/patches/implicit 
motif-2.3.8/debian/patches/implicit
--- motif-2.3.8/debian/patches/implicit 1970-01-01 01:00:00.0 +0100
+++ motif-2.3.8/debian/patches/implicit 2024-03-21 23:38:08.0 +0100
@@ -0,0 +1,26 @@
+---
+ demos/unsupported/xmform/xmform.c |1 +
+ lib/Xm/XpmI.h |2 +-
+ 2 files changed, 2 insertions(+), 1 deletion(-)
+
+--- a/lib/Xm/XpmI.h
 b/lib/Xm/XpmI.h
+@@ -129,7 +129,7 @@ extern "C" {
+ extern FILE *popen();
+ #endif
+ 
+-#if defined(SYSV) || defined(SVR4) || defined(VMS) || defined(WIN32) || 
defined (_SVID_SOURCE)
++#if defined(SYSV) || defined(SVR4) || defined(VMS) || defined(WIN32) || 
defined (_SVID_SOURCE) || defined (_POSIX_SOURCE)
+ #include 
+ 
+ #ifndef index
+--- a/demos/unsupported/xmform/xmform.c
 b/demos/unsupported/xmform/xmform.c
+@@ -50,6 +50,7 @@ xmform*topShadowColor:   white
+ xmform*bottomShadowColor:black
+ ***---*/
+ 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru motif-2.3.8/debian/patches/series motif-2.3.8/debian/patches/series
--- motif-2.3.8/debian/patches/series   2020-07-02 10:59:29.0 +0200
+++ motif-2.3.8/debian/patches/series   2024-03-21 23:37:12.0 +0100
@@ -17,3 +17,4 @@
 pass-hardening-flags.patch
 revert-fix-1617.patch
 cross.patch
+implicit

Processed: Re: Bug#1067467: eztrace fails tests during the build on almost all architectures

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1066735
Bug #1067467 [src:eztrace] eztrace fails tests during the build on almost all 
architectures
1067467 was not blocked by any bugs.
1067467 was not blocking any bugs.
Added blocking bug(s) of 1067467: 1067281 and 1066735

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

Bug#1067467: eztrace fails tests during the build on almost all architectures

[Samuel Thibault]

Control: block -1 by 1066735

Ok, it's the third one, I'll just add a block instead of merging again.

Samuel

Matthias Klose, le jeu. 21 mars 2024 23:23:21 +0100, a ecrit:
> Package: src:eztrace
> Version: 2.1-7
> Severity: serious
> Tags: sid trixie ftbfs
> 
> eztrace fails tests during the build on almost all architectures, e.g.
> 
> 
> 90% tests passed, 2 tests failed out of 21
> 
> Total Test time (real) =  42.52 sec
> 
> The following tests FAILED:
> 2 - mpi_tests (Failed)
> 9 - mpi_tests (Failed)
> Errors while running CTest
> make[2]: *** [Makefile:74: test] Error 8
> make[2]: Leaving directory '/<>/build-mpich'

Bug#1067467: eztrace fails tests during the build on almost all architectures

[Matthias Klose]

Package: src:eztrace
Version: 2.1-7
Severity: serious
Tags: sid trixie ftbfs

eztrace fails tests during the build on almost all architectures, e.g.


90% tests passed, 2 tests failed out of 21

Total Test time (real) =  42.52 sec

The following tests FAILED:
  2 - mpi_tests (Failed)
  9 - mpi_tests (Failed)
Errors while running CTest
make[2]: *** [Makefile:74: test] Error 8
make[2]: Leaving directory '/<>/build-mpich'

Bug#1067465: yosys-plugin-ghdl builds on x86 only, but built on other architectures before

[Matthias Klose]

Package: src:yosys-plugin-ghdl
Version: 0.0~git20230419.5b64ccf-1
Severity: serious
Tags: sid trixie ftbfs

yosys-plugin-ghdl builds on x86 only, but built on other architectures 
before


Caused by

* Use ghdl-mcode instead of ghdl-gcc as it's more portable

but ghdl-mcode is only available on amd64 and i386.  With this choice 
you're making things worse.

Processed: Bug#1067459 marked as pending in connectagram

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067459 [connectagram] connectgram: Please update or drop qt6 dependencies
Added tag(s) pending.

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

Bug#1067459: marked as pending in connectagram

[Alexandre Detiste]

Control: tag -1 pending

Hello,

Bug #1067459 in connectagram 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/games-team/connectagram/-/commit/5020b40697f449084163bf05096ddbf5ebb03f65


do not add runtime dependencies as build-dependencies (Closes: #1067459)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067459

Processed: Re: Bug#1066967: dh_sphinxdoc: replaces files provided by read-the-doc theme by empty symlinks

[Debian Bug Tracking System]

Processing control commands:

> tags 1066967 +unreproducible
Bug #1066967 [sphinx-common] dh_sphinxdoc: replaces files provided by 
read-the-doc theme by empty symlinks
Ignoring request to alter tags of bug #1066967 to the same tags previously set

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

Bug#1066967: dh_sphinxdoc: replaces files provided by read-the-doc theme by empty symlinks

[Dmitry Shachnev]

Control: tags 1066967 +unreproducible

Hi Holger!

On Sat, Mar 16, 2024 at 09:52:54AM +0100, Holger Wansing wrote:
> Package: sphinx-common
> Severity: serious
> 
> Hi,
> 
> dh_sphinxdoc does not work well with read-the-doc theme, apparently.
> Debian policy document has switched to sphinx_rtd_theme recently (see
> https://salsa.debian.org/dbnpolicy/policy/-/commit/686622814018b5a121252b189d99c1968f332b78
>  )
> 
> However, the built document has a completely broken html layout, because
> many files under _static/ are empty (0B size), most noteably 
> _static/css/theme.css.
> 
> If I replace 
>   dh $@ --with sphinxdoc
> by
>   dh $@
> (so do not use dh_sphinxdoc), I get a valid html file with the theme
> in use.

I cannot reproduce this. I downloaded debian-policy source package and built
it in an up-to-date sid chroot. And the built package has this:

  $ dpkg-deb -c debian-policy_4.6.2.1_all.deb | grep theme.css
  lrwxrwxrwx root/root 0 2024-02-24 15:39 
./usr/share/doc/debian-policy/policy.html/_static/css/theme.css -> 
../../../../../sphinx_rtd_theme/static/css/theme.css

So, it is a symlink, not an empty file. When resolving the relative path,
I get /usr/share/sphinx_rtd_theme/static/css/theme.css, and that file
exists in sphinx-rtd-theme-common and is non-empty.

The only issue I see is that sphinx-rtd-theme-common is in Recommends of
debian-policy, not in Depends. But that is because ${sphinxdoc:Depends}
was put there.

Am I doing something wrong?

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Re: Bug#1066967: dh_sphinxdoc: replaces files provided by read-the-doc theme by empty symlinks

[Debian Bug Tracking System]

Processing control commands:

> tags 1066967 +unreproducible
Bug #1066967 [sphinx-common] dh_sphinxdoc: replaces files provided by 
read-the-doc theme by empty symlinks
Added tag(s) unreproducible.

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

Bug#1067462: ERROR: Failed to create organization

[Tj]

Package: taskd
Version: 1.1.0+dfsg-4+b2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: deb...@iam.tj

Dear Maintainer,

After installation and following the instructions in README.Debian I
found that adding an organisation fails. It is due to two
things:

1. The package fails to create /var/lib/taskd/orgs/

see https://github.com/GothenburgBitFactory/taskserver/issues/82

2. Permissions on /var/lib/taskd/ are incorrect; since taskd uses
Debian-taskd user that user needs write permissions to everything under
/var/lib/taskd/  . Additionally Others should not have access.

-- System Information:
Debian Release: 12.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.7+debian+tj (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 taskd depends on:
ii  adduser3.134
ii  gnutls-bin 3.7.9-2+deb12u2
ii  init-system-helpers1.65.2
ii  libc6  2.36-9+deb12u4
ii  libgcc-s1  12.2.0-14
ii  libgnutls303.7.9-2+deb12u2
ii  libstdc++6 12.2.0-14
ii  libuuid1   2.38.1-5+b1
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.06-4

taskd recommends no packages.

Versions of packages taskd suggests:
pn  taskwarrior  

-- Configuration Files:
/etc/taskd/config changed [not included]

-- no debconf information

Processed: Re: Bug#1067458: pulseaudio: FTBFS cpu-volume-test fails

[Debian Bug Tracking System]

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

> affects 1067458 src:pulseaudio
Bug #1067458 [src:orc] pulseaudio: FTBFS cpu-volume-test fails
Ignoring request to set affects of bug 1067458 to the same value previously set
>
End of message, stopping processing here.

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

Bug#1067459: connectgram: Please update or drop qt6 dependencies

[Gianfranco Costamagna]

Package: connectagram
Version: 1.3.5-1
Severity: serious

Dear Maintainer,


Looks like you are adding some runtime dependencies as build-dependencies

Thanks for considering the patch.

--- connectagram-1.3.5/debian/control   2024-03-12 02:50:36.0 +0100
+++ connectagram-1.3.5/debian/control   2024-03-21 21:36:00.0 +0100
@@ -10,9 +9,6 @@
   qt6-l10n-tools,
   qt6-tools-dev-tools,
   qt6-base-dev-tools,
-  libqt6widgets6,
-  libqt6gui6,
-  libqt6core6,
   mesa-common-dev,
   debhelper-compat (= 13)
 Standards-Version: 4.6.2


G.

Bug#1067460: entropybroker: please fix libpng-dev build dependency

[Gianfranco Costamagna]

Package: entropybroker
Version: 2.9-7
Severity: serious
Tags: patch

Dear Maintainer,

  * Update dependency to libpng-dev


Thanks for considering the patch.

diff -Nru entropybroker-2.9/debian/control entropybroker-2.9/debian/control
--- entropybroker-2.9/debian/control2022-07-31 22:25:00.0 +0200
+++ entropybroker-2.9/debian/control2024-03-21 21:41:18.0 +0100
@@ -7,7 +7,7 @@
 , libgd-dev
, libasound2-dev
, libusb-1.0-0-dev
-   , libpng16-16
+   , libpng-dev
, zlib1g-dev
, libpcsclite-dev
, libftdi-dev


G.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1067458: pulseaudio: FTBFS cpu-volume-test fails

[Jeremy Bícha]

Source: orc
Severity: serious
Version: 1:0.4.38-1
Forwarded: https://gitlab.freedesktop.org/gstreamer/orc/-/issues/66
X-Debbugs-CC: pulseau...@packages.debian.org
User: debian-...@lists.debian.org
Usertags: time-t
Control: affects -1 src:pulseaudio
Control: block 1036884 by -1

pulseaudio fails to build from source on a few architectures but it
built successfully recently. The build log suggests that the new
version of orc might have triggered this regression in pulseaudio's
build tests so I filed an upstream bug and am reporting this Debian
bug against orc.

Here's an excerpt from the build log.

test: cpu-volume-test
start time:   20:02:32
duration: 2.06s
result:   exit status 1
command:  src/tests/cpu-volume-test
--- stdout ---
Running suite(s): CPU
66%: Checks: 3, Failures: 0, Errors: 1
../src/tests/cpu-volume-test.c:188:E:svolume:svolume_orc_test:0:
(after this point) Received signal 11 (Segmentation fault)

https://buildd.debian.org/status/package.php?p=pulseaudio

Thank you,
Jeremy Bícha

Processed: pulseaudio: FTBFS cpu-volume-test fails

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:pulseaudio
Bug #1067458 [src:orc] pulseaudio: FTBFS cpu-volume-test fails
Added indication that 1067458 affects src:pulseaudio
> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1067069 1067193 1065787 1067171 1062847 1065973 1067189 
1067192 1067190 1066794 1066049 1055530 1065816 1067170 1067175 1055352
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067458

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

Bug#1064003: Bug#1065416: [Cross-toolchain-base-devs] Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Helmut Grohne]

Hi Bastian and Matthias,

I was recently working on gcc builds and this disagreement currently
makes stuff unbuildable. Hence I looked into solutions and/or
workarounds.

On Tue, Mar 05, 2024 at 09:50:27AM +0100, Helmut Grohne wrote:
> > You just said that the search path used during the build of the
> > toolchain and the one for everything else are unrelated.  So you are
> > free to create $BUILD/tmp-include with symlinks for asm, asm-generic,
> > linux.
> > 
> > The toolchain as installed already finds all headers.  So I still don't
> > see why we need this in the final system.
> 
> I find this argument fairly convincing and hope Matthias also does.

As a result, I implemented the proposed change and am attaching it for
discussion here. I've implemented it in a way that if there is a sysroot
linux header installation, it'll be preferred. Do you see any downsides
of this approach?

Helmut
linux-libc-dev now provides linux-libc-dev-$arch-cross without actually
providing /usr//include. Thus we symlink it to where we need it.

See also #1064003.

diff --git a/debian/rules2 b/debian/rules2
index 651d14af..6a486ffe 100644
--- a/debian/rules2
+++ b/debian/rules2
@@ -1266,6 +1266,13 @@ endif
 	  ln -sf /usr/include/$(DEB_HOST_MULTIARCH)/crypt.h \
 	$(builddir)/sys-include/crypt.h; \
 	fi
+	: # Import headers from Multi-Arch:foreign linux-libc-dev
+	set -e; for d in asm-generic linux; do \
+	  if [ -d "/usr/include/$$d" ] && ! [ -d "/usr/$(DEB_TARGET_GNU_TYPE)/include/$$d" ]; then \
+	mkdir -p '$(builddir)/sys-include'; \
+	ln -sf "/usr/include/$$d" "$(builddir)/sys-include/$$d"; \
+	  fi; \
+	done
 
 	touch $(configure_stamp)
 

Bug#1066995: marked as done (pulseaudio: FTBFS with _TIME_BITS=64 on 32-bit systems)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 19:51:16 +
with message-id 
and subject line Bug#1067247: fixed in pulseaudio 16.1+dfsg1-4
has caused the Debian Bug report #1067247,
regarding pulseaudio: FTBFS with _TIME_BITS=64 on 32-bit systems
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.)


-- 
1067247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pulseaudio
Version: 16.1+dfsg1-3
Severity: serious
Tags: upstream
Justification: ftbfs
User: debian-powe...@lists.debian.org
Usertags: powerpc
X-Debbugs-Cc: debian-powe...@lists.debian.org

Hi,

pulseaudio fails to built from source with _TIME_BITS=64 [1]:

[632/648] cc -Isrc/utils/libpulsedsp.so.p -Isrc/utils -I../src/utils -I. -I.. 
-Isrc -I../src -fdiagnostics-color=always -Wall -Winvalid-pch -std=gnu11 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-pthread -DHAVE_CONFIG_H -D_GNU_SOURCE -Wno-nonnull-compare -MD -MQ 
src/utils/libpulsedsp.so.p/padsp.c.o -MF src/utils/libpulsedsp.so.p/padsp.c.o.d 
-o src/utils/libpulsedsp.so.p/padsp.c.o -c ../src/utils/padsp.c
FAILED: src/utils/libpulsedsp.so.p/padsp.c.o 
cc -Isrc/utils/libpulsedsp.so.p -Isrc/utils -I../src/utils -I. -I.. -Isrc 
-I../src -fdiagnostics-color=always -Wall -Winvalid-pch -std=gnu11 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-pthread -DHAVE_CONFIG_H -D_GNU_SOURCE -Wno-nonnull-compare -MD -MQ 
src/utils/libpulsedsp.so.p/padsp.c.o -MF src/utils/libpulsedsp.so.p/padsp.c.o.d 
-o src/utils/libpulsedsp.so.p/padsp.c.o -c ../src/utils/padsp.c
In file included from /usr/include/features.h:393,
 from /usr/include/endian.h:21,
 from /usr/include/linux/soundcard.h:43,
 from /usr/include/powerpc-linux-gnu/sys/soundcard.h:1,
 from ../src/utils/padsp.c:33:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
only with _FILE_OFFSET_BITS=64"
   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^

This needs to be fixed for the time_t transition [2].

Thanks,
Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=pulseaudio=powerpc=16.1%2Bdfsg1-3%2Bb1=1710500596=0
> [2] https://wiki.debian.org/ReleaseGoals/64bit-time

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along 

Bug#1067247: marked as done (pulseaudio: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64")

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 19:51:16 +
with message-id 
and subject line Bug#1067247: fixed in pulseaudio 16.1+dfsg1-4
has caused the Debian Bug report #1067247,
regarding pulseaudio: #error "_TIME_BITS=64 is allowed only with 
_FILE_OFFSET_BITS=64"
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.)


-- 
1067247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pulseaudio
Version: 16.1+dfsg1-3
Severity: serious
Justification: FTBFS
Tags: ftbfs
X-Debbugs-Cc: t...@mirbsd.de

Unfortunately, as with umockdev, I have no idea what is going on
here… does it #undef _FILE_OFFSET_BITS or something?
--- End Message ---
--- Begin Message ---
Source: pulseaudio
Source-Version: 16.1+dfsg1-4
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated pulseaudio 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: Thu, 21 Mar 2024 15:35:29 -0400
Source: pulseaudio
Built-For-Profiles: noudeb
Architecture: source
Version: 16.1+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Pulseaudio maintenance team 

Changed-By: Jeremy Bícha 
Closes: 1067247
Changes:
 pulseaudio (16.1+dfsg1-4) unstable; urgency=medium
 .
   * Team upload
   * Selectively disable libpulsedsp & padsp on 32-bit non-i386 architectures.
 Thanks to Simon McVittie, Steve Langasek (Closes: #1067247)
Checksums-Sha1:
 89960442f5681ad8c31c494975ff3291140755aa 3766 pulseaudio_16.1+dfsg1-4.dsc
 3e22725e00ba1788951eba0a1c0de954df5ee612 38556 
pulseaudio_16.1+dfsg1-4.debian.tar.xz
 e66abd27affaf3c190535cc433c1a935e391452d 18905 
pulseaudio_16.1+dfsg1-4_source.buildinfo
Checksums-Sha256:
 97d847ad79fc36e745bbd28aa34dbb61b8b1825f5939d117164f47d036f560da 3766 
pulseaudio_16.1+dfsg1-4.dsc
 b0ae3d8f85b62e64e3f59319886f9c7bc36a16040a11d78820c6bf9fb00a 38556 
pulseaudio_16.1+dfsg1-4.debian.tar.xz
 c137479e2ca93f018b6765c3025a600122dbbfae701c928876e43a54f65423a8 18905 
pulseaudio_16.1+dfsg1-4_source.buildinfo
Files:
 8877bf3a3f99d445fd49ce83fa044163 3766 sound optional 
pulseaudio_16.1+dfsg1-4.dsc
 4b78d0f975f93834a1f6ff62c6172cac 38556 sound optional 
pulseaudio_16.1+dfsg1-4.debian.tar.xz
 07eea26fbc97420e47d3755385e21965 18905 sound optional 
pulseaudio_16.1+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmX8jCwACgkQ5mx3Wuv+
bH3TMA/+PVwt8znh5SGjvBSzEPDn1ubcl5dSQQpeZEp2cMXf1OS70OJ/JaNwdapm
yTlqdccYizDajt59BB0xmhoFllM6cSIauZJr51lFFUq0k8hdESTAwZNi6rzXpjmG
fx1vb1e4wuMzmK199DT80YtAcTPlJBq4BT0uayUej6rM0LlVYBGD9UXt5P+TVpRs
jS75uivilBUjBGtQVl/uwh8jjRiYa9/HltIbXcVPJ8K8p4boNs1zeThevBNR4j//
MhRjbCIuAIGbZ8r96fdXiYvDM466/wKYEflWAhFAfoHwIOiWtyQIdTyQ/hM3nhwa
UQ7HH5GRWTbsy1KswkiZ49LeEviCxRbzFBkzQJZIQkCk9GZGa/Ep6wuKbwucsX/c
VeTW/kz1X/pQfpGIOzfeWmIChF+Wq7soSWGpfeqNziFz0IvE0VCSIKBU5xPOKF1P
DpaC8YouUUc7bleRuyKm7ktoPT3C8zEqiry4l07lcvJQXi9Feno/vK0sNz37GeFy
+oKIkpwoE2kbGZ0goAigGWnWa/IaIlnKEAEDXQrOH0vSXRbXlITv0C5UHPny/u4h
/MiYPpJd8m+ACXSdYEoSgNkqVDP/izRCXjS0SxadXDd/B7e736H95fskWCr+VQFq
oqX2rYGETCnveMNo38++qR9kSgvbvIz8ZVUzOMm78OmZ9N7axjk=
=3Tff
-END PGP SIGNATURE-



pgprG0tAGoNMc.pgp
Description: PGP signature
--- End Message ---

Bug#1066754: sentry-python: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Gregor Riepl]

Hi,

I believe this issue can be addressed by my proposed fix for #1063986:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063986#12

Regards,
Gregor

Bug#1067247: marked as pending in pulseaudio

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1067247 in pulseaudio 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/pulseaudio-team/pulseaudio/-/commit/5209c2fc46630722f1aaa3c0bbf88a9f843cd27c


Selectively disable libpulsedsp & padsp on 32-bit non-i386 architectures

Thanks: Simon McVittie, Steve Langasek

Closes: #1067247


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067247

Processed: Bug#1067247 marked as pending in pulseaudio

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067247 [src:pulseaudio] pulseaudio: #error "_TIME_BITS=64 is allowed only 
with _FILE_OFFSET_BITS=64"
Bug #1066995 [src:pulseaudio] pulseaudio: FTBFS with _TIME_BITS=64 on 32-bit 
systems
Added tag(s) pending.
Added tag(s) pending.

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

Processed: Re: Bug#1066314: regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #1066314 [src:regina-rexx] regina-rexx: FTBFS: ./rexxext.c:95:7: error: 
implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066314: regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration]

[Agustin Martin]

Control: tags -1 +pending

El dom, 17 mar 2024 a las 21:41, Agustin Martin
() escribió:
>
> El vie, 15 mar 2024 a las 18:57, Agustin Martin
> () escribió:
> >
> > Hi, Lucas and Alen.
> >
> > While it is easy to fix this particular error (see attached patch,
> > from upstream repo), other similar error happens afterwards in my
> > tests. The problem is that this package is way behind upstream and I
> > think priority is to upgrade to a recent upstream version and then fix
> > whatever is left.
>
> Hi, Alen,
>
> Some time ago I played a bit with upgrading regina-rexx to a recent
> upstream version. I think I can find that stuff and try again with
> last upstream version. In case of success, I would like to push
> changes to regina-rexx salsa repo for further inspection. Let me know
> your POV.

Hi, Lucas and Alen

I have been working on upgrading upstream version from 3.6 to 3.9.5.
There have been a lot of upstream changes between both versions and I
have tried to quickly look at them in case I find something I do not
like. It was a quick look, so something may have gone unnoticed,
better if maintainer can look better at it. I have upgraded all the
Debian stuff to work with that new version, added some other changes I
found interesting, and verified that everything builds in a recent
pbuilder sid box, so I think package as I have it fixes this problem,
thus the "pending" tag.

I have committed everything to
https://salsa.debian.org/debian/regina-rexx.git, including upstream
and pristine-tar branches. I will leave some time for inspection and,
if no one else uploads before and there are no objections, will upload
NMU myself. In the meantime I would like to look at [#1027405:
regina-rexx FTCBFS: builds for the build architecture] and see how to
adjust supplied patch and deal with this problem. Note that
regina-rexx package is marked for autoremoval from testing on 26
April.

Regards,

-- 
Agustin

Bug#1063986: sentry-python: autopkgtest regression with pytest 8

[Gregor Riepl]

Hi,

I think this issue can be fixed by pulling in the latest sentry-sdk 
version (1.43 at this point) and applying the following patch:



diff --git a/debian/rules b/debian/rules
index 206ab22..27d6911 100755
--- a/debian/rules
+++ b/debian/rules
@@ -43,6 +43,7 @@ PYBUILD_TEST_ARGS_PYTEST7_IGNORE=\
and not test_circular_references \
and not test_has_tracestate_enabled \
and not test_default_release \
+   and not test_uwsgi_warnings \

 export PYBUILD_NAME=sentry_sdk
 # Disable tests failing mostly because of internet access (httpbin.org)


The test "test_uwsgi_warnings" is flaky and doesn't clean up properly 
after itself, which leads to an error further down the line.


Please release a new version as soon as possible.
Thank you very much.

Regards,
Gregor

Processed: Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 tech-ctte
Bug #1065416 [linux-libc-dev] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Bug reassigned from package 'linux-libc-dev' to 'tech-ctte'.
No longer marked as found in versions linux/6.7.7-1.
Ignoring request to alter fixed versions of bug #1065416 to the same values 
previously set
> severity -1 normal
Bug #1065416 [tech-ctte] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Severity set to 'normal' from 'serious'

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

Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Bastian Blank]

Control: reassign -1 tech-ctte
Control: severity -1 normal

Hi

I don't see any way to solve this issue right now.  Please decide this
matter according to 6.1 nr 2 Debian Constitution.

Background:  linux-libc-dev provides the Linux API for consumption by
all userspace stuff.

This package was arch-any for as long as I remember and provided only
the headers for this single architecture.  Since a short while this
package is now arch-all and provides headers for all known Debian
architectures in one swoop.  This change was done when the Ubuntu
maintainers asked if we wanted to follow.

This now means that new architectures will need to get added to
linux-libc-dev first and it is not longer required to push hand crafted
packages somewhere in the ports archive.

However the package now contains everything that is also contained in
the uncoordinated linux-libc-dev-*-cross packages.  The only difference
is the physical location of the files (/usr/include instead of the
policy violating /usr/*/include).  This API proofed to be compatible
with all tested packages available in the archive.

Because of this (from my side unnecessary) code duplication, I opened
the plan to replace linux-libc-dev-*-cross, see #1059786.  Two months
later the following bug report comes in:

On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote:
> linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't
> do that completely
> 
> Provides: linux-libc-dev-amd64-cross (= 6.7.7-1), ...
> 
> However the links in /usr/DEB_HOST_GNU_TYPE/include are missing.
> 
> Please stop providing the cross-packages, you don't even need a breaks,
> because the current cross packages continue to work.
> 
> Once that is done, I'll reduce the cross packages to some symlinks.

Even after several e-mails, the OP was unable or unwilling to show where
the problem actually lies.

Please decide who is going to provide linux-libc-dev and all the
associated cross stuff and how it should look like.

Regards,
Bastian

-- 
Vulcans never bluff.
-- Spock, "The Doomsday Machine", stardate 4202.1

Bug#1067410: golang-github-go-jose-go-jose-dev: ftbfs on i386 and mips64el due to timeout of test case

[Nilesh Patra]

> The 4.0.1-2 still has timeout on test issue, see:
> https://buildd.debian.org/status/logs.php?pkg=golang-github-go-jose-go-jose=i386
>
> https://buildd.debian.org/status/logs.php?pkg=golang-github-go-jose-go-jose=mips64el
>
> So open this to trace it again.
> ...
> golang-github-go-jose-go-jose (4.0.1-3) unstable; urgency=medium
> .
>   * Skip one test on some architectures accurately. (Closes: #1067410)

You could instead increase the timeout too with:

override_dh_auto_test:
dh_auto_test -- -timeout=1h

Unless the tests run on those archs forever.

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1067444: FileNotFoundError: [Errno 2] ... /usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst

[Jochen Sprickerhof]

Hi Tj,

* Tj  [2024-03-21 16:08]:

Severity: grave
Justification: renders package unusable


I disagree here. Any reason why you did it?


With a fresh install and manually creating the user's configuration file
I hit this error. The path reported seems to indicate the package is not
shipping the file mentioned. I tried moving the user config directory and
saw the error caused by it being missing, put it back, and hit this package
config file issue agian.

$ bugwarrior-pull
CRITICAL:bugwarrior.command:Could not load configuration. Maybe you have not 
created a configuration file.
FileNotFoundError: [Errno 2] No such file or directory: 
'/home/tj/.config/bugwarrior/bugwarriorrc'

$ mv ~/.config/bugwarrior{.bak,}

$ bugwarrior-pull
CRITICAL:bugwarrior.command:Could not load configuration. Maybe you have not 
created a configuration file.
FileNotFoundError: [Errno 2] No such file or directory: 
'/usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst'

$ cat ~/.config/bugwarrior/bugwarriorrc
[general]
targets = debianbts my_github


Delete my_github here, as you don't have a section on it.


[debianbts]
service = bts
bts.email = deb...@iam.tj


Add bts.udd = True to get your bugs ;).


$ dpkg -S docs/configuration.rst
dpkg-query: no path found matching pattern *docs/configuration.rst*
$ apt-file search  docs/configuration.rst
$


dpkg -S configuration.rst
bugwarrior: /usr/share/doc/bugwarrior/html/_sources/common_configuration.rst.txt
bugwarrior: /usr/share/doc/bugwarrior/html/_sources/configuration.rst.txt

The second one is the same file. I will push new version with a fixed 
path.


Cheers Jochen


signature.asc
Description: PGP signature

Bug#1067450: ttyd: does not start

[Daniel]

Package: ttyd
Version: 1.7.4-1+b2
Severity: grave
Justification: renders package unusable

Output of systemctl status ttyd

Mar 21 17:59:09 zone-s ttyd[1039170]: [2024/03/21 17:59:09:4449] E: 
lws_create_context: failed to load evlib_uv
Mar 21 17:59:09 zone-s ttyd[1039170]: [2024/03/21 17:59:09:4449] E: 
libwebsockets context creation failed
Mar 21 17:59:09 zone-s systemd[1]: ttyd.service: Main process exited, 
code=exited, status=1/FAILURE
Mar 21 17:59:09 zone-s systemd[1]: ttyd.service: Failed with result 'exit-code'.



-- System Information:
Debian Release: trixie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages ttyd depends on:
ii  libc6   2.36-9+deb12u4
ii  libcap2 1:2.66-4
ii  libjson-c5  0.16-2
ii  libssl3t64  3.1.5-1.1
ii  libuv1t64   1.48.0-1.1
ii  libwebsockets-evlib-uv  4.1.6-3
ii  zlib1g  1:1.2.13.dfsg-1

ttyd recommends no packages.

Versions of packages ttyd suggests:
ii  apache2  2.4.57-2

-- no debconf information

Bug#1066245: marked as done (gnucash: FTBFS: sqlite3test.c:30:5: error: implicit declaration of function ‘qof_log_init’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 17:07:33 +
with message-id 
and subject line Bug#1066245: fixed in gnucash 1:5.5-1.2
has caused the Debian Bug report #1066245,
regarding gnucash: FTBFS: sqlite3test.c:30:5: error: implicit declaration of 
function ‘qof_log_init’ [-Werror=implicit-function-declaration]
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.)


-- 
1066245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnucash
Version: 1:5.5-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> cd /<>/.build/bindings/python && /usr/bin/cc 
> -DBOOST_ATOMIC_DYN_LINK -DBOOST_ATOMIC_NO_LIB -DBOOST_CHRONO_DYN_LINK 
> -DBOOST_CHRONO_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_DATE_TIME_NO_LIB 
> -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_FILESYSTEM_NO_LIB -DBOOST_LOCALE_DYN_LINK 
> -DBOOST_LOCALE_NO_LIB -DBOOST_REGEX_DYN_LINK -DBOOST_REGEX_NO_LIB 
> -DBOOST_THREAD_DYN_LINK -DBOOST_THREAD_NO_LIB 
> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 
> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DHAVE_CONFIG_H -DHAVE_GUILE30 
> -D_GNU_SOURCE -I/<>/libgnucash 
> -I/<>/libgnucash/engine -I/<>/gnucash/gnome-utils 
> -I/<>/libgnucash/app-utils -I/<>/gnucash/gnome 
> -I/<>/libgnucash/core-utils -I/usr/include/python3.11 
> -I/<>/.build/common -I/<>/common 
> -I/<>/borrowed/libc 
> -I/<>/.build/libgnucash/core-utils -isystem 
> /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -Wall -Wmissing-prototypes -Wmissing-declarations -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -O3 
> -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -Wmissing-prototypes 
> -Wmissing-declarations -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu11 -Wno-implicit 
> -Wno-missing-prototypes -Wno-declaration-after-statement 
> -Wno-missing-declarations -Wno-error=stringop-truncation -MD -MT 
> bindings/python/CMakeFiles/sqlite3test.dir/sqlite3test.c.o -MF 
> CMakeFiles/sqlite3test.dir/sqlite3test.c.o.d -o 
> CMakeFiles/sqlite3test.dir/sqlite3test.c.o -c 
> /<>/bindings/python/sqlite3test.c
> /<>/bindings/python/sqlite3test.c: In function ‘main’:
> /<>/bindings/python/sqlite3test.c:30:5: error: implicit 
> declaration of function ‘qof_log_init’ [-Werror=implicit-function-declaration]
>30 | qof_log_init();
>   | ^~~~
> /<>/bindings/python/sqlite3test.c:31:5: error: implicit 
> declaration of function ‘qof_init’ [-Werror=implicit-function-declaration]
>31 | qof_init();
>   | ^~~~
> /<>/bindings/python/sqlite3test.c:32:5: error: implicit 
> declaration of function ‘gnc_engine_init’ 
> [-Werror=implicit-function-declaration]
>32 | gnc_engine_init(0, no_args);
>   | ^~~
> cc1: some warnings being treated as errors
> make[5]: *** [bindings/python/CMakeFiles/sqlite3test.dir/build.make:118: 
> bindings/python/CMakeFiles/sqlite3test.dir/sqlite3test.c.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/gnucash_5.5-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gnucash
Source-Version: 1:5.5-1.2

Bug#1067446: ghdl fails to build with gnat-13

[Matthias Klose]

Package: src:ghdl
Version: 3.0.0+dfsg2-1
Severity: serious
Tags: sid trixie ftbfs

ghdl still uses gcc-12/gnat-12 for the build, a package that will not be 
shipped with the next Debian release (these will be gcc-13 and gcc-14).


Replacing the -12 b-d's with -13, and fixing the version check in 
Makefile.in let's the package build, but with some tsts failing.


There's also a new upstream release.

Bug#1067445: whitakers-words ftbfs with gnat-13

[Matthias Klose]

Package: src:whitakers-words
Version: 0.2020.10.27-1.3
Severity: serious
Tags: sid trixie ftbfs

[...]
makeinfl.adb:22:06: warning: renamed predefined unit is an obsolescent 
feature (RM J.1) [-gnatwj]
/home/packages/tmp/x/whitakers-words-0.2020.10.27/src/latin_utils/latin_utils-general.adb: 
In function 'latin_utils__general__load_dictionary':
/home/packages/tmp/x/whitakers-words-0.2020.10.27/src/latin_utils/latin_utils-general.adb:49:8: 
warning: 'd_k' may be used uninitialized [-Wmaybe-uninitialized]
/home/packages/tmp/x/whitakers-words-0.2020.10.27/src/latin_utils/latin_utils-general.ads:33:8: 
note: 'd_k' was declared here


   compilation of makeinfl.adb failed

gprbuild: *** compilation phase failed
make[2]: *** [Makefile:40: commands] Error 4
make[2]: Leaving directory 
'/home/packages/tmp/x/whitakers-words-0.2020.10.27'

Bug#1064128: marked as done (liquidsoap: FTBFS: Error: Unbound module Pcre)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 16:42:20 +
with message-id 
and subject line Bug#1064128: fixed in liquidsoap 2.2.4-1
has caused the Debian Bug report #1064128,
regarding liquidsoap: FTBFS: Error: Unbound module Pcre
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.)


-- 
1064128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liquidsoap
Version: 2.2.3-1
Severity: serious

Dear Maintainer,

The package has one ftbfs issue due to:

```
299 | let key = Pcre.get_substring sub 1 in
^^
Error: Unbound module Pcre
(cd _build/default && /usr/bin/ocamlc.opt -w -40 -g -bin-annot -I 
src/core/.liquidsoap_core.objs/byte -I /usr/lib/ocaml/angstrom -I 
/usr/lib/ocaml/bigstringaf -I /usr/lib/ocaml/bytes -I 
/usr/lib/ocaml/camlp-streams -I /usr/lib/ocaml/camomile/lib -I 
/usr/lib/ocaml/cry -I /usr/lib/ocaml/curl -I /usr/lib/ocaml/dtools -I 
/usr/lib/ocaml/dune-build-info -I /usr/lib/ocaml/dune-private-libs/dune-section 
-I /usr/lib/ocaml/dune-site -I /usr/lib/ocaml/dune-site/private -I 
/usr/lib/ocaml/duppy -I /usr/lib/ocaml/fileutils -I /usr/lib/ocaml/gen -I 
/usr/lib/ocaml/inotify -I /usr/lib/ocaml/magic -I /usr/lib/ocaml/menhirLib -I 
/usr/lib/ocaml/metadata -I /usr/lib/ocaml/mm -I /usr/lib/ocaml/mm/audio -I 
/usr/lib/ocaml/mm/base -I /usr/lib/ocaml/mm/image -I /usr/lib/ocaml/mm/midi -I 
/usr/lib/ocaml/mm/video -I /usr/lib/ocaml/re -I /usr/lib/ocaml/sedlex -I 
/usr/lib/ocaml/seq -I /usr/lib/ocaml/stdlib-shims -I /usr/lib/ocaml/stringext 
-I /usr/lib/ocaml/syslog -I /usr/lib/ocaml/threads -I /usr/lib/ocaml/uri -I 
src/console/.console.objs/byte -I src/lang/.liquidsoap_lang.objs/byte 
-no-alias-deps -o src/core/.liquidsoap_core.objs/byte/ffmpeg_format.cmo -c 
-impl src/core/encoder/formats/ffmpeg_format.pp.ml)
File "src/core/encoder/formats/ffmpeg_format.ml", line 136, characters 20-31:
136 | (if Pcre.pmatch ~pat:"video" name then "" else 
"video_content,")
  ^^^
Error: Unbound module Pcre
(cd _build/default && /usr/bin/ocamlopt.opt -w -40 -g -w -9 -alert --deprecated 
-O2 -I src/core/.liquidsoap_core.objs/byte -I 
src/core/.liquidsoap_core.objs/native -I /usr/lib/ocaml/angstrom -I 
/usr/lib/ocaml/bigstringaf -I /usr/lib/ocaml/bytes -I 
/usr/lib/ocaml/camlp-streams -I /usr/lib/ocaml/camomile/lib -I 
/usr/lib/ocaml/cry -I /usr/lib/ocaml/curl -I /usr/lib/ocaml/dtools -I 
/usr/lib/ocaml/dune-build-info -I /usr/lib/ocaml/dune-private-libs/dune-section 
-I /usr/lib/ocaml/dune-site -I /usr/lib/ocaml/dune-site/private -I 
/usr/lib/ocaml/duppy -I /usr/lib/ocaml/fileutils -I /usr/lib/ocaml/gen -I 
/usr/lib/ocaml/inotify -I /usr/lib/ocaml/magic -I /usr/lib/ocaml/menhirLib -I 
/usr/lib/ocaml/metadata -I /usr/lib/ocaml/mm -I /usr/lib/ocaml/mm/audio -I 
/usr/lib/ocaml/mm/base -I /usr/lib/ocaml/mm/image -I /usr/lib/ocaml/mm/midi -I 
/usr/lib/ocaml/mm/video -I /usr/lib/ocaml/re -I /usr/lib/ocaml/sedlex -I 
/usr/lib/ocaml/seq -I /usr/lib/ocaml/stdlib-shims -I /usr/lib/ocaml/stringext 
-I /usr/lib/ocaml/syslog -I /usr/lib/ocaml/threads -I /usr/lib/ocaml/uri -I 
src/console/.console.objs/byte -I src/console/.console.objs/native -I 
src/lang/.liquidsoap_lang.objs/byte -I src/lang/.liquidsoap_lang.objs/native 
-intf-suffix .ml -no-alias-deps -o 
src/core/.liquidsoap_core.objs/native/http.cmx -c -impl 
src/core/tools/http.pp.ml)
File "src/core/tools/http.ml", line 69, characters 10-20:
69 | match Pcre.split ~pat:"=" arg with
   ^^
Error: Unbound module Pcre
dh_auto_build: error: dune build -j 4 -p 
liquidsoap,liquidsoap-core,liquidsoap-lang,liquidsoap-js,liquidsoap-libs,liquidsoap-libs-extra,liquidsoap-mode,tls-liquidsoap,sdl-liquidsoap
 returned exit code 1
make: *** [debian/rules:7: binary-arch] Error 25

```

Although it was failed with -b1 version on buildd[0], but it is reproduced on 
my local build for amd64 and riscv64 also.


[0]: 
https://buildd.debian.org/status/fetch.php?pkg=liquidsoap=amd64=2.2.3-1%2Bb1=1708087445=0


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: liquidsoap
Source-Version: 2.2.4-1
Done: Kyle Robbertze 

We believe that the bug you reported is fixed in the latest version of
liquidsoap, 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 

Bug#1067444: FileNotFoundError: [Errno 2] ... /usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst

[Tj]

Package: bugwarrior
Version: 1.8.0-7
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With a fresh install and manually creating the user's configuration file
I hit this error. The path reported seems to indicate the package is not
shipping the file mentioned. I tried moving the user config directory and
saw the error caused by it being missing, put it back, and hit this package
config file issue agian.

$ bugwarrior-pull
CRITICAL:bugwarrior.command:Could not load configuration. Maybe you have not 
created a configuration file.
FileNotFoundError: [Errno 2] No such file or directory: 
'/home/tj/.config/bugwarrior/bugwarriorrc'

$ mv ~/.config/bugwarrior{.bak,}

$ bugwarrior-pull
CRITICAL:bugwarrior.command:Could not load configuration. Maybe you have not 
created a configuration file.
FileNotFoundError: [Errno 2] No such file or directory: 
'/usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst'

$ cat ~/.config/bugwarrior/bugwarriorrc
[general]
targets = debianbts my_github

[debianbts]
service = bts
bts.email = deb...@iam.tj

$ dpkg -S docs/configuration.rst
dpkg-query: no path found matching pattern *docs/configuration.rst*
$ apt-file search  docs/configuration.rst
$

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

Versions of packages bugwarrior depends on:
ii  libjs-sphinxdoc5.3.0-4
ii  python33.11.2-1+b1
ii  python3-click  8.1.3-2
ii  python3-dateutil   2.8.2-2
ii  python3-dogpile.cache  1.1.8-2
ii  python3-future 0.18.2-6
ii  python3-jinja2 3.1.2-1
ii  python3-lockfile   1:0.12.2-2.2
ii  python3-requests   2.28.1+dfsg-1
ii  python3-six1.16.0-4
ii  python3-taskw  2.0.0-1
ii  python3-tz 2022.7.1-4

Versions of packages bugwarrior recommends:
ii  python3-google-auth-oauthlib  0.4.2-1
ii  python3-googleapi 1.7.12-1
ii  python3-jira  3.4.1-1
ii  python3-keyring   23.9.3-2
ii  python3-phabricator   0.7.0-1.1
ii  python3-pypandoc  1.7.4+ds0-2

bugwarrior suggests no packages.

-- no debconf information

Bug#1067410: marked as done (golang-github-go-jose-go-jose-dev: ftbfs on i386 and mips64el due to timeout of test case)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 16:38:08 +
with message-id 
and subject line Bug#1067410: fixed in golang-github-go-jose-go-jose 4.0.1-3
has caused the Debian Bug report #1067410,
regarding golang-github-go-jose-go-jose-dev: ftbfs on i386 and mips64el due to 
timeout of test case
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.)


-- 
1067410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-go-jose-go-jose-dev
Version: 4.0.1-2
Severity: serious

The 4.0.1-2 still has timeout on test issue, see:
https://buildd.debian.org/status/logs.php?pkg=golang-github-go-jose-go-jose=i386

https://buildd.debian.org/status/logs.php?pkg=golang-github-go-jose-go-jose=mips64el

So open this to trace it again.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: golang-github-go-jose-go-jose
Source-Version: 4.0.1-3
Done: Bo YU 

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

Debian distribution maintenance software
pp.
Bo YU  (supplier of updated golang-github-go-jose-go-jose 
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: Thu, 21 Mar 2024 22:43:58 +0800
Source: golang-github-go-jose-go-jose
Architecture: source
Version: 4.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Bo YU 
Closes: 1067410
Changes:
 golang-github-go-jose-go-jose (4.0.1-3) unstable; urgency=medium
 .
   * Skip one test on some architectures accurately. (Closes: #1067410)
Checksums-Sha1:
 9846776c0534966e3abd6f16bfd0304265285e62 2450 
golang-github-go-jose-go-jose_4.0.1-3.dsc
 076dfa45ff61aca7abea29260e99587f687e3f11 4276 
golang-github-go-jose-go-jose_4.0.1-3.debian.tar.xz
 83080482355ea5886f9728cbb1a02ade8fb4c2c7 7609 
golang-github-go-jose-go-jose_4.0.1-3_amd64.buildinfo
Checksums-Sha256:
 ae5afd6cb0c87898a0b6b850d0c37c29e1cf82ad9b07be5628e38f1e8cd466d6 2450 
golang-github-go-jose-go-jose_4.0.1-3.dsc
 dbce1531557e15985347b212b7d093baeb6d9eeabf52329ca328f035a3b88b8f 4276 
golang-github-go-jose-go-jose_4.0.1-3.debian.tar.xz
 fcf7192074967a4abaf1b067fdb54d7c1347f183daedaf1ad0e98691006e6c53 7609 
golang-github-go-jose-go-jose_4.0.1-3_amd64.buildinfo
Files:
 a808cb87961c33b6738153ba5cf67b19 2450 golang optional 
golang-github-go-jose-go-jose_4.0.1-3.dsc
 6d2739357ea75217a05b1bc8682fd65e 4276 golang optional 
golang-github-go-jose-go-jose_4.0.1-3.debian.tar.xz
 caa3966f4a9501705396c03b6af6d62d 7609 golang optional 
golang-github-go-jose-go-jose_4.0.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIcmhjYVTlmab0tjp+RVP3hQ+S68FAmX8XzoACgkQ+RVP3hQ+
S68eXw/+OLoQpkkgYoHaWvyXXPTJFcJKeWxtPD4OtNUtIR8C6uG3yhZwoZykHtAA
w7bqmAFI5QPbTS5QhV4UYsyDLaNgl7zlxjLsjYNukMfWaTnqReBQCDMk7xGjtnrI
+MCmZEXLmHUnqOY0kR5IA8VelWVzoSO/uVH5X3ohYsKErhfm54ZMpFewHn+1NXEA
ud8JBFUs6FrILJb9U3t0vFfTCXdVdHPbluVNf4MzC2GrfF39ljK16IGwPEXoz7WC
Ov6l2as34rPVsVBg15fTzhYERUOmbkBMitcOgCGQgW+YbwPH7Y/tZYpS3o42JJYY
ippqlYO4wE17nDRBJ6YO2yfuEjEGeu/9iOt4dzldxuzLfPcF3S0X+//KpE+1UKod
DZ2GFMPWHnON+mHBW+XQ4tvXT2571CwH84BJqh2btlA7RgLssCVKe+5RZkenIvVN
G87KDHgPTIt24Pr1ZdLW0kkwhXSfMUb14xf2NwDAEQ0+hBpNiJtcKR4vaNDXrdgY
yrDMuSC/8ACuMYXzWlg0amf5GZAAb9kQYx8MSZPmDXvCw75pqkDVDLM/lnMKXRl+
Z4x/pmYE+PcwPk971W+u4DyEK3CqU0OboHolmCb+ZgCtdCdKVOjAhO5aZ39cIo4D
6l2BADdZY8GeAqfIE7mPcetDQ3d8fe+Bxt1L0jb6AfsGzS6fF1I=
=H6On
-END PGP SIGNATURE-



pgpoZfKMWQape.pgp
Description: PGP signature
--- End Message ---

Bug#1067442: marked as done (contains files for different architecture)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 17:25:35 +0100
with message-id <20240321162535.eo3ebgnohaq5o...@mraw.org>
and subject line Re: Bug#1067442: contains files for different architecture
has caused the Debian Bug report #1067442,
regarding contains files for different architecture
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.)


-- 
1067442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: syslinux-efi
Version: 3:6.04~git20190206.bf6db5b4+dfsg1-3
Severity: grave
X-Debbugs-Cc: dbarysh...@gmail.com

The ARM64 syslinux-efi package binaries for x86 instead instead of ARM
binaries:

$ uname -m
aarch64

$ file /usr/lib/SYSLINUX.EFI/efi*/syslinux.efi
/usr/lib/SYSLINUX.EFI/efi32/syslinux.efi: PE32 executable (EFI application) 
Intel 80386 (stripped to external PDB), for MS Windows
/usr/lib/SYSLINUX.EFI/efi64/syslinux.efi: PE32+ executable (EFI application) 
x86-64 (stripped to external PDB), for MS Windows

As such these binaries are unusable on ARM64 hosts.

-- System Information:
Debian Release: 12.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 6.6.9-qcomlt-arm64-00188-g31f49428dc7d (SMP w/4 CPU threads; 
PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

syslinux-efi depends on no packages.

Versions of packages syslinux-efi recommends:
ii  syslinux-common  3:6.04~git20190206.bf6db5b4+dfsg1-3

Versions of packages syslinux-efi suggests:
ii  dosfstools  4.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

Dmitry Baryshkov  (2024-03-21):
> Package: syslinux-efi
> Version: 3:6.04~git20190206.bf6db5b4+dfsg1-3
> Severity: grave
> X-Debbugs-Cc: dbarysh...@gmail.com
> 
> The ARM64 syslinux-efi package binaries for x86 instead instead of ARM
> binaries:
> 
> $ uname -m
> aarch64
> 
> $ file /usr/lib/SYSLINUX.EFI/efi*/syslinux.efi
> /usr/lib/SYSLINUX.EFI/efi32/syslinux.efi: PE32 executable (EFI application) 
> Intel 80386 (stripped to external PDB), for MS Windows
> /usr/lib/SYSLINUX.EFI/efi64/syslinux.efi: PE32+ executable (EFI application) 
> x86-64 (stripped to external PDB), for MS Windows
> 
> As such these binaries are unusable on ARM64 hosts.

There's a single `Architecture: all` package, there are no
architecture-specific builds for this package…

https://repo.or.cz/syslinux.git/tree/HEAD:/efi knows about efi32 and
efi64, not about ARM.

And I can't find any information about ARM anywhere anyway…

 extlinux arch=amd64,i386,x32
 isolinux arch=all
 pxelinux arch=all
 syslinux arch=amd64,i386,x32
 syslinux-common arch=all
 syslinux-efi arch=all
 syslinux-utils arch=amd64,i386,x32

Sounds like not a bug, instead of a grave bug…


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---

Processed: Re: Bug#1067407: graphviz: diff for NMU version 2.42.2-8.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo
Bug #1067407 [graphviz] graphviz: FTBFS due to -Wimplicit-declaration gcc flag
Added tag(s) moreinfo.

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

Bug#1067407: graphviz: diff for NMU version 2.42.2-8.1

[GCS]

Control: tags -1 +moreinfo

On Thu, Mar 21, 2024 at 12:39 PM Gianfranco Costamagna
 wrote:
> I've prepared an NMU for graphviz (versioned as 2.42.2-8.1) and
> uploaded it to DELAYED/2. Please feel free to cancel it directly if you want 
> to do a maintainer upload.
 I do not see the point of this. Can you please recheck the current
graphviz package state and report back to me?

Regards,
Laszlo/GCS

Bug#1067407: graphviz: FTBFS due to -Wimplicit-declaration gcc flag

[GCS]

Hi Gianfranco,

On Thu, Mar 21, 2024 at 9:09 AM Gianfranco Costamagna
 wrote:
> Hello, looks like the package will FTBFS due to newly introduced 
> implicit-declaration flag
> I did cherry-pick two upstream patches and the package now build successfully.
 When that '-Wimplicit-declaration' is going to be set? I'm a bit
confused, you may mix it with '-Werror=implicit-function-declaration'
which was already patched five days ago.
Can you recheck your findings and add more information?

Thanks,
Laszlo/GCS

Bug#1067387: marked as done (prometheus-homeplug-exporter: FTBFS: make[1]: *** [debian/rules:31: override_dh_auto_build] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 16:13:06 +
with message-id 
and subject line Bug#1067387: fixed in prometheus-homeplug-exporter 0.3.0-5
has caused the Debian Bug report #1067387,
regarding prometheus-homeplug-exporter: FTBFS: make[1]: *** [debian/rules:31: 
override_dh_auto_build] Error 25
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.)


-- 
1067387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-homeplug-exporter
Version: 0.3.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- -tags "" -ldflags " -X 
> github.com/prometheus/common/version.Version=0.3.0 -X 
> github.com/prometheus/common/version.Revision=0.3.0-4 -X 
> github.com/prometheus/common/version.Branch=debian/sid -X 
> github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
>  -X github.com/prometheus/common/version.BuildDate=20221008-13:15:02 -X 
> github.com/prometheus/common/version.GoVersion=go1.22.1"
>   cd build && go version
> go version go1.22.1 linux/amd64
>   cd build && go env
> GO111MODULE='off'
> GOARCH='amd64'
> GOBIN=''
> GOCACHE='/<>/build/go-build'
> GOENV='/<>/debian/.debhelper/generated/_source/home/.config/go/env'
> GOEXE=''
> GOEXPERIMENT=''
> GOFLAGS=''
> GOHOSTARCH='amd64'
> GOHOSTOS='linux'
> GOINSECURE=''
> GOMODCACHE='/<>/build/pkg/mod'
> GONOPROXY=''
> GONOSUMDB=''
> GOOS='linux'
> GOPATH='/<>/build'
> GOPRIVATE=''
> GOPROXY='off'
> GOROOT='/usr/lib/go-1.22'
> GOSUMDB='sum.golang.org'
> GOTMPDIR=''
> GOTOOLCHAIN='local'
> GOTOOLDIR='/usr/lib/go-1.22/pkg/tool/linux_amd64'
> GOVCS=''
> GOVERSION='go1.22.1'
> GCCGO='gccgo'
> GOAMD64='v1'
> AR='ar'
> CC='gcc'
> CXX='g++'
> CGO_ENABLED='1'
> GOMOD=''
> GOWORK=''
> CGO_CFLAGS='-g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection'
> CGO_CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2'
> CGO_CXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection'
> CGO_FFLAGS='-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-clash-protection -fcf-protection'
> CGO_LDFLAGS='-Wl,-z,relro'
> PKG_CONFIG='pkg-config'
> GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 
> -ffile-prefix-map=/tmp/go-build3746614504=/tmp/go-build 
> -gno-record-gcc-switches'
>   cd build && go install -trimpath -v -p 8 -tags  -ldflags " -X 
> github.com/prometheus/common/version.Version=0.3.0 -X 
> github.com/prometheus/common/version.Revision=0.3.0-4 -X 
> github.com/prometheus/common/version.Branch=debian/sid -X 
> github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
>  -X github.com/prometheus/common/version.BuildDate=20221008-13:15:02 -X 
> github.com/prometheus/common/version.GoVersion=go1.22.1" 
> github.com/brandond/homeplug_exporter
> internal/goexperiment
> internal/goos
> internal/godebugs
> internal/cpu
> runtime/internal/atomic
> internal/unsafeheader
> internal/coverage/rtcov
> internal/goarch
> runtime/internal/syscall
> internal/itoa
> math/bits
> unicode/utf8
> internal/race
> internal/abi
> internal/chacha8rand
> runtime/internal/math
> runtime/internal/sys
> sync/atomic
> unicode
> internal/bytealg
> cmp
> math
> encoding
> slices
> unicode/utf16
> log/internal
> internal/nettrace
> container/list
> crypto/internal/alias
> crypto/subtle
> crypto/internal/boring/sig
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/alias
> google.golang.org/protobuf/internal/flags
> google.golang.org/protobuf/internal/set
> runtime
> internal/reflectlite
> runtime/metrics
> sync
> internal/singleflight
> internal/bisect
> internal/testlog
> google.golang.org/protobuf/internal/pragma
> runtime/cgo
> errors
> sort
> internal/godebug
> internal/oserror
> io
> internal/safefilepath
> path
> strconv
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> internal/intern
> math/rand
> crypto/internal/nistec/fiat
> strings
> bytes
> hash
> reflect
> hash/crc32
> net/netip
> crypto
> crypto/internal/randutil
> bufio
> regexp/syntax
> crypto/rc4
> vendor/golang.org/x/text/transform
> net/http/internal/ascii
> internal/syscall/unix
> time
> internal/syscall/execenv
> github.com/beorn7/perks/quantile
> hash/fnv
> 

Bug#1067275: marked as done (prometheus-process-exporter: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 16:13:15 +
with message-id 
and subject line Bug#1067275: fixed in prometheus-process-exporter 0.7.10-4
has caused the Debian Bug report #1067275,
regarding prometheus-process-exporter: FTBFS: make[1]: *** [debian/rules:28: 
override_dh_auto_build] Error 25
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.)


-- 
1067275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-process-exporter
Version: 0.7.10-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- -tags "" -ldflags " -X 
> github.com/prometheus/common/version.Version=0.7.10 -X 
> github.com/prometheus/common/version.Revision=0.7.10-3 -X 
> github.com/prometheus/common/version.Branch=debian/sid -X 
> github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org 
> -X github.com/prometheus/common/version.BuildDate=20221215-03:41:28 -X 
> github.com/prometheus/common/version.GoVersion=go1.22.1"
>   cd build && go install -trimpath -v -p 8 -tags  -ldflags " -X 
> github.com/prometheus/common/version.Version=0.7.10 -X 
> github.com/prometheus/common/version.Revision=0.7.10-3 -X 
> github.com/prometheus/common/version.Branch=debian/sid -X 
> github.com/prometheus/common/version.BuildUser=team+pkg...@tracker.debian.org 
> -X github.com/prometheus/common/version.BuildDate=20221215-03:41:28 -X 
> github.com/prometheus/common/version.GoVersion=go1.22.1" 
> github.com/ncabatoff/process-exporter 
> github.com/ncabatoff/process-exporter/cmd/process-exporter 
> github.com/ncabatoff/process-exporter/collector 
> github.com/ncabatoff/process-exporter/config 
> github.com/ncabatoff/process-exporter/proc
> internal/coverage/rtcov
> internal/goarch
> internal/godebugs
> internal/goos
> internal/unsafeheader
> internal/goexperiment
> runtime/internal/atomic
> runtime/internal/syscall
> internal/cpu
> internal/abi
> internal/chacha8rand
> runtime/internal/math
> runtime/internal/sys
> internal/itoa
> math/bits
> unicode/utf8
> internal/race
> sync/atomic
> unicode
> cmp
> encoding
> slices
> internal/nettrace
> log/internal
> unicode/utf16
> container/list
> crypto/internal/alias
> internal/bytealg
> math
> crypto/subtle
> crypto/internal/boring/sig
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/alias
> google.golang.org/protobuf/internal/flags
> google.golang.org/protobuf/internal/set
> runtime
> internal/reflectlite
> runtime/metrics
> sync
> internal/testlog
> internal/bisect
> google.golang.org/protobuf/internal/pragma
> internal/singleflight
> runtime/cgo
> errors
> internal/godebug
> sort
> io
> internal/oserror
> internal/safefilepath
> strconv
> internal/intern
> vendor/golang.org/x/net/dns/dnsmessage
> path
> syscall
> strings
> bytes
> hash
> crypto/internal/randutil
> hash/crc32
> math/rand
> crypto/internal/nistec/fiat
> bufio
> reflect
> net/netip
> regexp/syntax
> crypto
> crypto/rc4
> vendor/golang.org/x/text/transform
> net/http/internal/ascii
> github.com/beorn7/perks/quantile
> hash/fnv
> github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
> html
> text/tabwriter
> golang.org/x/text/transform
> golang.org/x/crypto/blowfish
> regexp
> time
> internal/syscall/execenv
> internal/syscall/unix
> github.com/jpillora/backoff
> context
> io/fs
> internal/poll
> internal/fmtsort
> encoding/binary
> embed
> os
> encoding/base64
> crypto/cipher
> crypto/internal/edwards25519/field
> vendor/golang.org/x/crypto/internal/poly1305
> crypto/md5
> crypto/internal/nistec
> golang.org/x/sys/unix
> github.com/cespare/xxhash
> crypto/internal/boring
> crypto/des
> encoding/pem
> crypto/aes
> crypto/sha512
> crypto/internal/edwards25519
> crypto/hmac
> crypto/sha1
> crypto/sha256
> vendor/golang.org/x/crypto/chacha20
> vendor/golang.org/x/crypto/hkdf
> fmt
> path/filepath
> github.com/prometheus/procfs/internal/util
> net
> vendor/golang.org/x/sys/cpu
> crypto/ecdh
> google.golang.org/protobuf/internal/detrand
> io/ioutil
> internal/lazyregexp
> vendor/golang.org/x/crypto/chacha20poly1305
> github.com/ncabatoff/process-exporter
> encoding/hex
> flag
> github.com/prometheus/procfs/internal/fs
> github.com/ncabatoff/go-seq/seq
> log
> os/user
> encoding/json
> compress/flate
> math/big
> net/url
> vendor/golang.org/x/text/unicode/bidi
> 

Bug#1000001: marked as done (pgpcre: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 16:12:47 +
with message-id 
and subject line Bug#101: fixed in pgpcre 0.20190509-7
has caused the Debian Bug report #101,
regarding pgpcre: 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.)


-- 
101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgpcre
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: pgpcre
Source-Version: 0.20190509-7
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pgpcre 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: Thu, 21 Mar 2024 16:32:43 +0100
Source: pgpcre
Architecture: source
Version: 0.20190509-7
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Closes: 101
Changes:
 pgpcre (0.20190509-7) unstable; urgency=medium
 .
   [ Yavor Doganov ]
   * Port to PCRE2 (Closes: #101).
 .
   [ Christoph Berg ]
   * B-D on pkconf.
Checksums-Sha1:
 32bb5c1860daef2f2dc868122406389e382995cd 2042 pgpcre_0.20190509-7.dsc
 533d35f9fb52a2231ac7b9967579de66450f04b0 4688 pgpcre_0.20190509-7.debian.tar.xz
Checksums-Sha256:
 bb92168bc6ce589cd011256d554028eec591b07a605fdb755aace519df73c054 2042 
pgpcre_0.20190509-7.dsc
 7da0f583b6f52ad8ae9a20393fc06cbd64c163f5adf64599d5affb5cd40ee5a3 4688 
pgpcre_0.20190509-7.debian.tar.xz
Files:
 2424cae2c93ffb00b49144d46dd805b8 2042 database optional pgpcre_0.20190509-7.dsc
 cf47f11bc628f4890ce48dfffb4e28bf 4688 database optional 
pgpcre_0.20190509-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmX8VU4ACgkQTFprqxLS
p65L/g//RItAuqAUBIZM/n5JKR+S4VcZ0ZZrU5jqpW7xrsJvjK+Qfq55bOBBlq3U
Ve9tXdX2zJft8/CtkEyPzm3gDfG1upF2UFcMUgp4vQF9OHyIVDd/gYiY1A08J7D2
4MbU7aW9Al55JAbPQyFvHJ9dTZN3KwO828ET9CaDh/BMw3EzR7G+MZPtVKghukG7
ECTwfjH+w3z4v8fVpxhgRXfyV93MhUCD33crC+i4MGD1whQlDXsrU2cPaJ2JxBBy
KfdrfUT25xaKeX1V+vpI/1xLPUmXiY6QWQfINynVYucEuzocp9X+Z8Sp6xJUO0Op
QapBDSS5Xn3zwhm/UDV80d6dhoELj7Bkj2tdNTjllmiHi5fdW3lcfq/GFzmr7Jlx
XqWEi0bu8wr6xcw1vw59TAaehsg+J3lVkNs3DwQSsvyFLev4qqYbTQZd6Cd97Vua
oO4aryKXM3JwsIUAIvs7tyB4hxdbgP5Dwg+jvJkMSXvxDME1H/UlBOIJ0n5qgOV1
OCYgRg15+tyd7DvXpqe/Pbim0Br1Q4DnEVTxQ65Ehg//N6NcaUPQrl6YLDyFjrAz
SQsft/O9MkgutusIv+VU4WxhRDxNQuEf75FLkFvA463Wk99vCrTOJVrZsHlhIE2I
31AWrIx3bl99ZToN9RpJvcKVek6uiw4JwqiYn0xQgJg2rROa7QA=
=72BA
-END PGP SIGNATURE-



pgpT_eEQHxeLA.pgp
Description: PGP signature
--- End Message ---

Processed: severity of 1063118 is important, user release.debian....@packages.debian.org, usertagging 1063118 ...

[Debian Bug Tracking System]

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

> severity 1063118 important
Bug #1063118 {Done: Benjamin Drung } [src:hdf-eos5] 
hdf-eos5: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
sebas...@debian.org).
> usertags 1063118 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> severity 1063134 important
Bug #1063134 {Done: Benjamin Drung } [src:libquazip] 
libquazip: NMU diff for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1063134 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> severity 1063294 important
Bug #1063294 {Done: Benjamin Drung } [src:pth] pth: NMU diff 
for 64-bit time_t transition
Severity set to 'important' from 'serious'
> usertags 1063294 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> severity 1066395 important
Bug #1066395 {Done: Bas Couwenberg } [src:python-hdf4] 
python-hdf4: FTBFS: ld: cannot find -lmfhdf: No such file or directory
Severity set to 'important' from 'serious'
> usertags 1066395 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> severity 1066442 important
Bug #1066442 {Done: Bas Couwenberg } [src:merkaartor] 
merkaartor: FTBFS: Preferences/MerkaartorPreferences.h:28:10: fatal error: 
proxy.h: No such file or directory
Severity set to 'important' from 'serious'
> usertags 1066442 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> severity 1066747 important
Bug #1066747 {Done: Bas Couwenberg } [src:rasterio] 
rasterio: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 
"3.12 3.11" returned exit code 13
Severity set to 'important' from 'serious'
> usertags 1066747 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> thanks
Stopping processing here.

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

Processed: severity of 1066716 is important, user release.debian....@packages.debian.org, usertagging 1066716 ...

[Debian Bug Tracking System]

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

> severity 1066716 important
Bug #1066716 {Done: Bas Couwenberg } [src:libtfbs-perl] 
libtfbs-perl: FTBFS: ./lib/pwm_searchPFF.c:55:7: error: implicit declaration of 
function ‘announce’ [-Werror=implicit-function-declaration]
Severity set to 'important' from 'serious'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
sebas...@debian.org).
> usertags 1066716 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> severity 1065759 important
Bug #1065759 {Done: Andreas Tille } 
[src:libbio-samtools-perl] libbio-samtools-perl: FTBFS: 
lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function 
‘bam_sort_core’; did you mean ‘bam_format1_core’? 
[-Werror=implicit-function-declaration]
Severity set to 'important' from 'serious'
> usertags 1065759 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> thanks
Stopping processing here.

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

Bug#1067317: scons: FTBFS: Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so: libharfbuzz.so.0: cannot open shared object file: No suc

[Mats Wichmann]

On Wed, 20 Mar 2024 22:04:03 +0100 Lucas Nussbaum  wrote:

Source: scons
Version: 4.5.2+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


This is unfortunate.  The docbook toolchain seems to have always 
generated a lot of spew from fop, which to the SCons project has seemed 
"out of our control". Now it seems something has changed so where the 
java used to throw SEVERE it is now throwing ERROR, thus failing the 
build - which really has nothing to do with the operation of SCons, 
which is just a Python package, after all.  This is a failure to 
generate the pdf versions of the docs, which are unused by the deb 
package, afaict.



Relevant part (hopefully):



> [ERROR] FOUserAgent - Invalid property value encountered in margin-left="": org.apache.fop.fo.expr.PropertyException: 
file:/<>/doc/man/scons-scons-time.fo:3:6: No conversion defined ; property:'margin-left' (See position 147:8) 
>/doc/man/scons-scons-time.fo:3:6: No conversion defined 
; property:'margin-left'>org.apache.fop.fo.expr.PropertyException: 
file:/<>/doc/man/scons-scons-time.fo:3:6: No conversion defined ; property:'margin-left'

...

> [ERROR] FOUserAgent - Invalid property value encountered in margin-right="": org.apache.fop.fo.expr.PropertyException: 
file:/<>/doc/man/scons-scons-time.fo:3:6: No conversion defined ; property:'margin-right' (See position 
147:8) >/doc/man/scons-scons-time.fo:3:6: No conversion 
defined ; property:'margin-right'>org.apache.fop.fo.expr.PropertyException: 
file:/<>/doc/man/scons-scons-time.fo:3:6: No conversion defined ; property:'margin-right'
>at org.apache.fop.fo.properties.PropertyMaker.make(PropertyMaker.java:446)
>at 
org.apache.fop.fo.PropertyList.convertAttributeToProperty(PropertyList.java:499)


The latest upstream release (4.7.0) tried to provide a way to avoid 
doing the pdf and Sphinx builds, but it turns out it doesn't do that in 
a place that the Debian packaging uses anyway.  Will make a note to 
revisit that on our end.


Didn't realize the deb directly used the build files in doc/man and 
doc/user.  The quickest way to patch around this would seem to be to 
comment out or remove the check in


doc/man/SConstruct
doc/user/SConstrcut

which checks for the presence of the 'fop' or 'xep' commands, so that 
'has_pdf' remains false, and the pdf build thus isn't attempted at all. 
I assume you don't need the pdf files, just the scons.1 etc. files? 
that's all I see copied in 
https://salsa.debian.org/debian/scons/-/blob/master/debian/rules?ref_type=heads

Bug#1067442: contains files for different architecture

[Dmitry Baryshkov]

Package: syslinux-efi
Version: 3:6.04~git20190206.bf6db5b4+dfsg1-3
Severity: grave
X-Debbugs-Cc: dbarysh...@gmail.com

The ARM64 syslinux-efi package binaries for x86 instead instead of ARM
binaries:

$ uname -m
aarch64

$ file /usr/lib/SYSLINUX.EFI/efi*/syslinux.efi
/usr/lib/SYSLINUX.EFI/efi32/syslinux.efi: PE32 executable (EFI application) 
Intel 80386 (stripped to external PDB), for MS Windows
/usr/lib/SYSLINUX.EFI/efi64/syslinux.efi: PE32+ executable (EFI application) 
x86-64 (stripped to external PDB), for MS Windows

As such these binaries are unusable on ARM64 hosts.

-- System Information:
Debian Release: 12.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 6.6.9-qcomlt-arm64-00188-g31f49428dc7d (SMP w/4 CPU threads; 
PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

syslinux-efi depends on no packages.

Versions of packages syslinux-efi recommends:
ii  syslinux-common  3:6.04~git20190206.bf6db5b4+dfsg1-3

Versions of packages syslinux-efi suggests:
ii  dosfstools  4.2-1

-- no debconf information

Processed: severity of 1065108 is important, user release.debian....@packages.debian.org, usertagging 1065108

[Debian Bug Tracking System]

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

> severity 1065108 important
Bug #1065108 {Done: tony mancill } [src:java3d] java3d: 
FTBFS: missing build-dep on libnsl-dev
Severity set to 'important' from 'serious'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
sebas...@debian.org).
> usertags 1065108 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> thanks
Stopping processing here.

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

Processed: severity of 1066067 is important

[Debian Bug Tracking System]

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

> severity 1066067 important
Bug #1066067 [src:cl-plus-ssl] cl-plus-ssl: hardcoded libssl3 dependency
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1066067: cl-plus-ssl: hardcoded libssl3 dependency

[Christoph Berg]

Re: Sebastian Ramacher
> Source: cl-plus-ssl
> Version: 20220328.git8b91648-4
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> 
> cl-plus-ssl hardcodeds a dependency on libssl3. Due to the time_t
> transition, the package name changed and the dependency needs to be
> updated.

It actually doesn't hard-code the dependency but correctly extracts it
from libssl-dev. But since we don't have arch:all binnmus, a new
upload was needed anyway. Just did that.

Once cl-plus-ssl is installed, please binnmu pgloader to have it pick
up the changed dependency.

Christoph

Bug#1067427: dpkg-dev: Fail to generate a substitution variable ${t64:Provides} (time_t transition)

[Christian Marillat]

On 21 mars 2024 15:41, Simon McVittie  wrote:


[...]

>  4. armel, armhf are the two 32-bit release architectures which are
> not in any of the previous categories, so they are genuinely changing
> their ABIs.
> Non-release architectures in the same category: hppa m68k powerpc sh4.
>
> On these architectures, libopenshot-audio9t64 must not have a Provides
> on libopenshot-audio9, because its ABI has changed, so the new library
> does not provide an interface that is compatible with the old library.
> (This is the reason why we're doing all this renaming!)

I did not know.

> So I think this is not a bug, and certainly not a RC bug. The warnings are
> a bit annoying, but do not indicate a genuine problem.

Yes of course, you can close this bug.

Christian

Bug#1000001: marked as pending in pgpcre

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #101 in pgpcre 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/postgresql/pgpcre/-/commit/b36dc6e2517979428bac0855fdc5578e3ef8006a


Port to PCRE2 (Closes: #101).

B-D on pkconf.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/101

Processed: Bug#1000001 marked as pending in pgpcre

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #101 [src:pgpcre] pgpcre: depends on obsolete pcre3 library
Added tag(s) pending.

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

Processed: Re: Bug#1067427: dpkg-dev: Fail to generate a substitution variable ${t64:Provides} (time_t transition)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1067427 [dpkg-dev] dpkg-dev: Fail to generate a substitution variable 
${t64:Provides} (time_t transition)
Added tag(s) moreinfo.

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

Bug#1067427: dpkg-dev: Fail to generate a substitution variable ${t64:Provides} (time_t transition)

[Simon McVittie]

Control: tags -1 + moreinfo

On Thu, 21 Mar 2024 at 15:00:52 +0100, Christian Marillat wrote:
> I noticed this bug with the libopenshot-audio source and with
> armel, armh and powerpc architectures from buildd logs and my rebuild.
> 
> I didn't pay attention for others sources, but I noticed that only
> after a second rebuild...
> 
> ,
> | pkg-gencontrol: warning: Provides field of package libopenshot-audio9t64: 
> substitution variable ${t64:Provides} used, but is not defined
> | dpkg-gencontrol: warning: Provides field of package libopenshot-audio9t64: 
> substitution variable ${t64:Provides} used, but is not defined
> `

This appears to be working as designed (cc'ing the instigator of this
transition for confirmation). It is correct that no ${t64:Provides}
is generated on armel, armhf and powerpc (and other 32-bit non-i386
architectures, like hppa).

There are four categories of architectures for this transition (text
adapted from https://wiki.debian.org/ReleaseGoals/64bit-time, which was
itself adapted from a recent message from me to -devel):

 1. amd64, arm64, mips64el, ppc64el, riscv64, s390x are all 64-bit, so they
already had 64-bit time_t.
Non-release architectures in the same category: alpha hurd-amd64 ia64
loong64 ppc64 sparc64.

On these architectures, libopenshot-audio9t64 can safely have
Provides: libopenshot-audio9, because the ABI has not actually changed.

 2. i386 is 32-bit but has been excluded from the 64-bit time_t transition
because its major purpose this decade is running legacy 32-bit
binaries, a purpose that would no longer be possible if it broke ABI.
Non-release architectures in the same category: hurd-i386.

On i386, libopenshot-audio9t64 can have the Provides, as above.

 3. There is currently no release architecture that is 32-bit but already
had a 64-bit time_t prior to 2024.
Non-release architectures in this category: x32.

On x32, libopenshot-audio9t64 should ideally have the Provides, as above
(I'm not sure whether it actually does, but given the status of x32,
I don't think this is actually harming anyone.)

 4. armel, armhf are the two 32-bit release architectures which are
not in any of the previous categories, so they are genuinely changing
their ABIs.
Non-release architectures in the same category: hppa m68k powerpc sh4.

On these architectures, libopenshot-audio9t64 must not have a Provides
on libopenshot-audio9, because its ABI has changed, so the new library
does not provide an interface that is compatible with the old library.
(This is the reason why we're doing all this renaming!)

So I think this is not a bug, and certainly not a RC bug. The warnings are
a bit annoying, but do not indicate a genuine problem.

smcv

Bug#1067439: cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 12

[Simone Piccardi]

Package: cpu
Version: 1.4.3-13+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

It was working on Debian 11, but after upgrading to Debian 12 just calling the 
program make it crash:

root@davis:~# cpu
CPU_loadLibrary: dlopen(libcpu_ldap.so, RTLD_NOW) failed.
CPU_loadLibrary: /lib/x86_64-linux-gnu/libcpu_ldap.so: undefined symbol: 
globalLdap
There was an error loading the ldap library. Exiting.

Regards
Simone

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 cpu depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libc6  2.36-9+deb12u4
ii  libcrack2  2.9.6-5+b1
ii  libcrypt1  1:4.4.33-2
ii  libldap-2.5-0  2.5.13+dfsg-5
ii  ucf3.0043+nmu1

cpu recommends no packages.

cpu suggests no packages.

-- debconf information:
  cpu/ldap/BIND_PASS: (password omitted)
  cpu/ldap/USER_BASE: ou=People,dc=truelite,dc=it
  cpu/ldap/BIND_DN: cn=admin,dc=truelite,dc=it
  cpu/ldap/GROUP_BASE: ou=Group,dc=truelite,dc=it
  cpu/ldap/LDAP_URI: ldap://localhost
  cpu/do_debconf: true

Bug#1066943: marked as done (ntirpc: FTBFS: missing dependency on libnsl-dev)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 15:20:29 +
with message-id 
and subject line Bug#1066943: fixed in ntirpc 4.3-4
has caused the Debian Bug report #1066943,
regarding ntirpc: FTBFS: missing dependency on libnsl-dev
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=ntirpc=armel=4.3-3.1=1710521344=0

-- Looking for epoll_create
-- Looking for epoll_create - found
-- Found EPOLL: 1  
-- Could NOT find NSL (missing: NSL_LIBRARY) 
-- 
-- ---
-- TIRPC_EPOLL = TRUE
-- USE_RPC_RDMA = OFF
-- USE_GSS = ON
-- USE_PROFILE = OFF
-- USE_LTTNG_NTIRPC = OFF
-- Configuring done (5.2s)
CMake Error: The following variables are used in this project, but they are set 
to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake 
files:
NSL_LIBRARY (ADVANCED)
linked by target "ntirpc" in directory /<>/src

-- Generating done (0.1s)
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_RUNSTATEDIR
CMAKE_INSTALL_SYSCONFDIR
FETCHCONTENT_FULLY_DISCONNECTED


CMake Generate step failed.  Build files cannot be regenerated correctly.

Cheers> 
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ntirpc
Source-Version: 4.3-4
Done: Christoph Martin 

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated ntirpc 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: Thu, 21 Mar 2024 16:01:05 +0100
Source: ntirpc
Architecture: source
Version: 4.3-4
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Christoph Martin 
Closes: 1066943
Changes:
 ntirpc (4.3-4) unstable; urgency=medium
 .
   * add Build-Depends on libnsl-dev (closes: #1066943)
   * fix clean target
   * wrap-and-sort debian/control
Checksums-Sha1:
 afad88a3d5a6c4e5189dc2911ca5bb42b4d3bcd5 1994 ntirpc_4.3-4.dsc
 adc494c0ce915e7195f6521cb5dcf94b782723bb 385720 ntirpc_4.3.orig.tar.gz
 d4198253e7d255077904dbed7453ce5151b1e56f 8488 ntirpc_4.3-4.debian.tar.xz
 e25dfa55fca372c61b6ac0f5dce127e74f916d84 9219 ntirpc_4.3-4_amd64.buildinfo
Checksums-Sha256:
 638a9fc15cd86cd8170c55c0ee02768e5e95a8f9f00e6cd783fee3fbdca7b81d 1994 
ntirpc_4.3-4.dsc
 f139a6972de50c1bd7ac18abfc966a996820a43855fccfe18611c34326a7c6b9 385720 
ntirpc_4.3.orig.tar.gz
 f3efbc5c1cf6d8f3b8b86ae2b3848f494a113d557fc4e9bc621a1b4a53ec00f3 8488 
ntirpc_4.3-4.debian.tar.xz
 2f8ff8fe71bef6a8a80a1ad96b3f85a175c739ca113c87253677023269c9e20f 9219 
ntirpc_4.3-4_amd64.buildinfo
Files:
 b6cae6e564c0b06854de5f29787d2d35 1994 net optional ntirpc_4.3-4.dsc
 a47fae13d0ddc024a02ddac21a61c479 385720 net optional ntirpc_4.3.orig.tar.gz
 1bee2d862f9f6edb2fc6bd6c65a03d5f 8488 net optional ntirpc_4.3-4.debian.tar.xz
 5b2a2b4841bcb6425be22ae99cd5c44c 9219 net optional ntirpc_4.3-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdDnWZeAGEWiqWy6hesz1la2n0EoFAmX8TmkACgkQesz1la2n
0ErfwRAArTYVtv3ExL0D8N367Tj2dVbIQSNcs6dZigD0BotiHhBukIOJaY5W6/If
1ayKP7lMeMavBJ4SxhuHlHMK4voC/Sv+TbeBihhJnyu+OKG6pc+MNHR9zub4alMO
1s5k46ugkpu0IY7uvGsq5wGHw38SPyPMMl7UoIt9VkTprPas3ep1wXRgvR1UL4V9
9SlRek9rgTtBKDpSJDqwvQELko/LELEk9ET7cv/DQ25fTHxiywcpogdf5BLIjaEC
suHSUj63BYFIbugECnjFAyDCemnz+Bk0HImG5EmZTTfpIl/V/SwwNELcgxHLiaqP
K0AbtGp8Sh7HJuuTbMPyL6ySU1yaIi65gvni/GIE2gHq6QB9Bu40RA+iSuA59wQb
1OQ93Hb4KLCi4NsUfLgQCIw/6hi3cdg16SPO5B95hJjMpxjonIAomGx+2s1ypnUe
MxkC6KHbr8X8HhUtuiHQ4UDVMsEn3dlSXpMOLua10m45omKQvvJmczEclnU/DMyB

Bug#1066717: marked as done (k2pdfopt: FTBFS: ocrtess.c:180:9: error: implicit declaration of function ‘ocrtess_lang_default’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 15:06:43 +
with message-id 
and subject line Bug#1066717: fixed in k2pdfopt 2.55+ds-2
has caused the Debian Bug report #1066717,
regarding k2pdfopt: FTBFS: ocrtess.c:180:9: error: implicit declaration of 
function ‘ocrtess_lang_default’ [-Werror=implicit-function-declaration]
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.)


-- 
1066717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: k2pdfopt
Version: 2.55+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/willuslib && /usr/bin/cc  
> -I/<>/. -I/<>/obj-x86_64-linux-gnu 
> -I/<>/willuslib -I/<>/k2pdfoptlib 
> -I/<>/willuslib/.. -isystem /usr/include/leptonica -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wall -pedantic -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DUSE_CMAKE -Wall -MD -MT 
> willuslib/CMakeFiles/willuslib.dir/ocrwords.c.o -MF 
> CMakeFiles/willuslib.dir/ocrwords.c.o.d -o 
> CMakeFiles/willuslib.dir/ocrwords.c.o -c /<>/willuslib/ocrwords.c
> /<>/willuslib/ocrtess.c: In function ‘ocrtess_lang_by_index’:
> /<>/willuslib/ocrtess.c:180:9: error: implicit declaration of 
> function ‘ocrtess_lang_default’ [-Werror=implicit-function-declaration]
>   180 | ocrtess_lang_default(NULL,NULL,0,langdef,31,NULL,0,0);
>   | ^~~~
> /<>/willuslib/ocrtess.c: In function ‘ocrtess_set_logfile’:
> /<>/willuslib/ocrtess.c:226:5: error: implicit declaration of 
> function ‘tess_capi_set_logfile’ [-Werror=implicit-function-declaration]
>   226 | tess_capi_set_logfile(filename);
>   | ^
> /<>/willuslib/ocrtess.c: In function ‘ocrtess_debug_message’:
> /<>/willuslib/ocrtess.c:233:5: error: implicit declaration of 
> function ‘tess_capi_debug_message’; did you mean ‘ocrtess_debug_message’? 
> [-Werror=implicit-function-declaration]
>   233 | tess_capi_debug_message(message);
>   | ^~~
>   | ocrtess_debug_message
> /<>/willuslib/ocrtess.c: In function ‘ocrtess_lang_exists’:
> /<>/willuslib/ocrtess.c:244:5: error: implicit declaration of 
> function ‘ocrtess_datapath’ [-Werror=implicit-function-declaration]
>   244 | ocrtess_datapath(tesspath0,datadir,MAXFILENAMELEN-1);
>   | ^~~~
> /<>/willuslib/ocrtess.c: In function 
> ‘ocrtess_lang_get_from_github’:
> /<>/willuslib/ocrtess.c:263:5: error: implicit declaration of 
> function ‘ocrtess_url’ [-Werror=implicit-function-declaration]
>   263 | ocrtess_url(url,255,fast);
>   | ^~~
> [ 60%] Linking C static library libk2pdfoptlib.a
> cd /<>/obj-x86_64-linux-gnu/k2pdfoptlib && /usr/bin/cmake -P 
> CMakeFiles/k2pdfoptlib.dir/cmake_clean_target.cmake
> /<>/willuslib/ocrtess.c:265:5: error: implicit declaration of 
> function ‘ocrtess_baselang’ [-Werror=implicit-function-declaration]
>   265 | ocrtess_baselang(urlbasename,lang,127);
>   | ^~~~
> /<>/willuslib/ocrtess.c: At top level:
> /<>/willuslib/ocrtess.c:300:6: warning: conflicting types for 
> ‘ocrtess_baselang’; have ‘void(char *, char *, int)’
>   300 | void ocrtess_baselang(char *dst,char *src,int maxlen)
>   |  ^~~~
> /<>/willuslib/ocrtess.c:265:5: note: previous implicit 
> declaration of ‘ocrtess_baselang’ with type ‘void(char *, char *, int)’
>   265 | ocrtess_baselang(urlbasename,lang,127);
>   | ^~~~
> /<>/willuslib/ocrtess.c:315:6: warning: conflicting types for 
> ‘ocrtess_url’; have ‘void(char *, int,  int)’
>   315 | void ocrtess_url(char *url0,int maxlen,int fast)
>   |  ^~~
> /<>/willuslib/ocrtess.c:263:5: note: previous implicit 
> declaration of ‘ocrtess_url’ with type ‘void(char *, int,  int)’
>   263 | ocrtess_url(url,255,fast);
>   | ^~~
> /<>/willuslib/ocrtess.c: In function ‘ocrtess_init’:
> /<>/willuslib/ocrtess.c:365:9: error: implicit declaration of 
> function ‘tess_capi_init’ 

Bug#1067170: zeroinstall-injector: diff for NMU version 2.18-2.1

[Boyuan Yang]

Control: tags 1067170 + patch
Control: tags 1067170 + pending
X-Debbugs-CC: tal...@gmail.com

Dear maintainer,

I've prepared an NMU for zeroinstall-injector (versioned as 2.18-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru zeroinstall-injector-2.18/debian/changelog 
zeroinstall-injector-2.18/debian/changelog
--- zeroinstall-injector-2.18/debian/changelog  2022-10-24 09:25:32.0 
-0400
+++ zeroinstall-injector-2.18/debian/changelog  2024-03-21 10:43:37.0 
-0400
@@ -1,3 +1,12 @@
+zeroinstall-injector (2.18-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Drop explicit dependency on libgtk-3-0. The dependency
+will be implicitly listed automatically. This helps to solve issues
+with time_64 transition. (Closes: #1067170)
+
+ -- Boyuan Yang   Thu, 21 Mar 2024 10:43:37 -0400
+
 zeroinstall-injector (2.18-2) unstable; urgency=medium
 
   * Fix build on bytecode-only platforms. Closes: #1022235.
diff -Nru zeroinstall-injector-2.18/debian/control 
zeroinstall-injector-2.18/debian/control
--- zeroinstall-injector-2.18/debian/control2022-10-24 09:25:32.0 
-0400
+++ zeroinstall-injector-2.18/debian/control2024-03-21 10:39:06.0 
-0400
@@ -30,7 +30,6 @@
 Package: 0install
 Architecture: any
 Depends: 0install-core (>= ${source:Version}),
- libgtk-3-0,
  ${misc:Depends},
  ${shlibs:Depends}
 Replaces: 0install-core (<< 2.10-1)


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

Processed: zeroinstall-injector: diff for NMU version 2.18-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1067170 + patch
Bug #1067170 [0install] 0install: hard-coded dependency on libgtk-3-0 will 
become uninstallable on armel/armhf
Added tag(s) patch.
> tags 1067170 + pending
Bug #1067170 [0install] 0install: hard-coded dependency on libgtk-3-0 will 
become uninstallable on armel/armhf
Added tag(s) pending.

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

Bug#1066256: marked as done (mcrypt: FTBFS: mcrypt.gaa:109:3: error: implicit declaration of function ‘mcrypt_license’; did you mean ‘mcrypt_free’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 14:41:09 +
with message-id 
and subject line Bug#1066256: fixed in mcrypt 2.6.8-7
has caused the Debian Bug report #1066256,
regarding mcrypt: FTBFS: mcrypt.gaa:109:3: error: implicit declaration of 
function ‘mcrypt_license’; did you mean ‘mcrypt_free’? 
[-Werror=implicit-function-declaration]
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.)


-- 
1066256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mcrypt
Version: 2.6.8-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -o gaaout.o -c gaaout.c -DLOCALEDIR=\"/usr/share/locale\" -I../intl -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -I/usr/include -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I..
> getpass.c: In function ‘readpass’:
> getpass.c:98:18: warning: the comparison will always evaluate as ‘false’ for 
> the address of ‘input’ will never be NULL [-Waddress]
>98 | if (input==NULL) return NULL;
>   |  ^~
> getpass.c:93:21: note: ‘input’ declared here
>93 | static char input[MAXLEN + 1];
>   | ^
> getpass.c:104:12: warning: pointer targets in assignment from ‘char *’ to 
> ‘unsigned char *’ differ in signedness [-Wpointer-sign]
>   104 | ap = asterix;
>   |^
> rfc2440.c: In function ‘dek_load’:
> rfc2440.c:566:42: warning: pointer targets in passing argument 5 of 
> ‘mhash_keygen_ext’ differ in signedness [-Wpointer-sign]
>   566 |DIM (d->key), pass, strlen(pass));
>   |  ^~~~
>   |  |
>   |  char *
> In file included from /usr/include/mhash.h:10,
>  from ./defines.h:8,
>  from rfc2440.c:18:
> /usr/include/mutils/mhash.h:108:45: note: expected ‘uint8_t *’ {aka ‘unsigned 
> char *’} but argument is of type ‘char *’
>   108 |   mutils_word8 *password, mutils_word32 
> passwordlen);
>   | ^
> rfc2440.c: In function ‘dek_create’:
> rfc2440.c:617:42: warning: pointer targets in passing argument 5 of 
> ‘mhash_keygen_ext’ differ in signedness [-Wpointer-sign]
>   617 |DIM (d->key), pass, strlen(pass));
>   |  ^~~~
>   |  |
>   |  char *
> /usr/include/mutils/mhash.h:108:45: note: expected ‘uint8_t *’ {aka ‘unsigned 
> char *’} but argument is of type ‘char *’
>   108 |   mutils_word8 *password, mutils_word32 
> passwordlen);
>   | ^
> rfc2440.c: In function ‘symkey_enc_decode’:
> rfc2440.c:635:27: warning: pointer targets in passing argument 2 of 
> ‘header_decode’ differ in signedness [-Wpointer-sign]
>   635 | header_decode(dat->d, , , , NULL);
>   |   ^~~~
>   |   |
>   |   int *
> rfc2440.c:426:41: note: expected ‘uint32 *’ {aka ‘unsigned int *’} but 
> argument is of type ‘int *’
>   426 | header_decode(const uchar *buf, uint32 *tag, uint32 *len,
>   | ^~~
> rfc2440.c:635:33: warning: pointer targets in passing argument 3 of 
> ‘header_decode’ differ in signedness [-Wpointer-sign]
>   635 | header_decode(dat->d, , , , NULL);
>   | ^~~~
>   | |
>   | int *
> rfc2440.c:426:54: note: expected ‘uint32 *’ {aka ‘unsigned int *’} but 
> argument is of type ‘int *’
>   426 | header_decode(const uchar *buf, uint32 *tag, uint32 *len,
>   |  ^~~
> rfc2440.c:635:43: warning: pointer targets 

Bug#1067418: Tests fail on 32-bit t64 arches

[Jérémy Lal]

Source: tpm2-tss
Followup-For: Bug #1067418

Upstream will just skip those tests on 32-bit:
https://github.com/tpm2-software/tpm2-tss/commit/932b1e78047ed0ddc09fcb06bff2e7cf96406976


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

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

Processed: Update GNOME Shell extension bugs for GNOME Shell 46

[Debian Bug Tracking System]

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

> user pkg-gnome-maintain...@lists.alioth.debian.org
Setting user to pkg-gnome-maintain...@lists.alioth.debian.org (was 
jeremy.bi...@canonical.com).
> usertags 1052089 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-45 gnome-shell-46.
> usertags 1052090 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-45 gnome-shell-46.
> usertags 1052096 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-45 gnome-shell-46.
> usertags 1052098 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-46 gnome-shell-45.
> usertags 1052101 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-45 gnome-shell-46.
> usertags 1052105 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-46 gnome-shell-45.
> usertags 1052108 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-46 gnome-shell-45.
> usertags 1052110 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-46 gnome-shell-45.
> usertags 1052111 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-46 gnome-shell-45.
> usertags 1052115 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-45 gnome-shell-46.
> usertags 1052556 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-45 gnome-shell-46.
> usertags 1054511 gnome-shell-46
Usertags were: gnome-shell-45.
Usertags are now: gnome-shell-46 gnome-shell-45.
> retitle 1052089 gnome-shell-extension-autohidetopbar: needs update for GNOME 
> Shell 46
Bug #1052089 [gnome-shell-extension-autohidetopbar] 
gnome-shell-extension-autohidetopbar: needs update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-autohidetopbar: needs update for 
GNOME Shell 46' from 'gnome-shell-extension-autohidetopbar: needs update for 
GNOME Shell 45'.
> retitle 1052090 gnome-shell-extension-bluetooth-quick-connect: needs update 
> for GNOME Shell 46
Bug #1052090 [gnome-shell-extension-bluetooth-quick-connect] 
gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-bluetooth-quick-connect: needs 
update for GNOME Shell 46' from 'gnome-shell-extension-bluetooth-quick-connect: 
needs update for GNOME Shell 45'.
> retitle 1052096 gnome-shell-extension-flypie: needs update for GNOME Shell 46
Bug #1052096 [gnome-shell-extension-flypie] gnome-shell-extension-flypie: needs 
update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-flypie: needs update for GNOME 
Shell 46' from 'gnome-shell-extension-flypie: needs update for GNOME Shell 45'.
> retitle 1052098 gnome-shell-extension-gamemode: needs update for GNOME Shell 
> 46
Bug #1052098 [gnome-shell-extension-gamemode] gnome-shell-extension-gamemode: 
needs update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-gamemode: needs update for GNOME 
Shell 46' from 'gnome-shell-extension-gamemode: needs update for GNOME Shell 
45'.
> retitle 1052101 gnome-shell-extension-hamster: needs update for GNOME Shell 46
Bug #1052101 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: 
needs update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-hamster: needs update for GNOME 
Shell 46' from 'gnome-shell-extension-hamster: needs update for GNOME Shell 45'.
> retitle 1052105 gnome-shell-extension-no-annoyance: needs update for GNOME 
> Shell 46
Bug #1052105 [gnome-shell-extension-no-annoyance] 
gnome-shell-extension-no-annoyance: needs update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-no-annoyance: needs update for 
GNOME Shell 46' from 'gnome-shell-extension-no-annoyance: needs update for 
GNOME Shell 45'.
> retitle 1052108 gnome-shell-extension-system-monitor: needs update for GNOME 
> Shell 46
Bug #1052108 [gnome-shell-extension-system-monitor] 
gnome-shell-extension-system-monitor: needs update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-system-monitor: needs update for 
GNOME Shell 46' from 'gnome-shell-extension-system-monitor: needs update for 
GNOME Shell 45'.
> retitle 1052110 gnome-shell-extension-vertical-overview: needs update for 
> GNOME Shell 46
Bug #1052110 [gnome-shell-extension-vertical-overview] 
gnome-shell-extension-vertical-overview: needs update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-vertical-overview: needs update for 
GNOME Shell 46' from 'gnome-shell-extension-vertical-overview: needs update for 
GNOME Shell 45'.
> retitle 1052111 gnome-shell-extension-weather: needs update for GNOME Shell 46
Bug #1052111 [gnome-shell-extension-weather] gnome-shell-extension-weather: 
needs update for GNOME Shell 45
Changed Bug title to 'gnome-shell-extension-weather: needs update for GNOME 
Shell 46' from 'gnome-shell-extension-weather: needs update for GNOME Shell 45'.
> retitle 1052115 workrave-gnome: needs update 

Processed: forcibly merging 1065375 1066272

[Debian Bug Tracking System]

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

> forcemerge 1065375 1066272
Bug #1065375 {Done: Ryan Kavanagh } [src:bc] bc fails to build 
with abi=time64
Bug #1066272 [src:bc] bc: FTBFS: stack.c:40:5: error: implicit declaration of 
function ‘checkferror_output’ [-Werror=implicit-function-declaration]
Marked Bug as done
Marked as fixed in versions bc/1.07.1-4.
Added tag(s) patch.
Bug #1065375 {Done: Ryan Kavanagh } [src:bc] bc fails to build 
with abi=time64
Marked as found in versions bc/1.07.1-3.
Added tag(s) ftbfs.
Merged 1065375 1066272
> thanks
Stopping processing here.

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

Processed: reassign 1067333 to src:python-sphinxcontrib.plantuml, affects 1067333

[Debian Bug Tracking System]

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

> reassign 1067333 src:python-sphinxcontrib.plantuml
Bug #1067333 [src:autosuspend] autosuspend: FTBFS: TypeError: can only 
concatenate str (not "bytes") to str
Bug reassigned from package 'src:autosuspend' to 
'src:python-sphinxcontrib.plantuml'.
No longer marked as found in versions autosuspend/6.0.0-1.
Ignoring request to alter fixed versions of bug #1067333 to the same values 
previously set
> affects 1067333 src:autosuspend
Bug #1067333 [src:python-sphinxcontrib.plantuml] autosuspend: FTBFS: TypeError: 
can only concatenate str (not "bytes") to str
Added indication that 1067333 affects src:autosuspend
> thanks
Stopping processing here.

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

Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Matthias Klose]

On 21.03.24 07:58, Bastian Blank wrote:

On Wed, Mar 20, 2024 at 09:59:31PM +0100, Matthias Klose wrote:

Independent of any technical issues, this is a hijacking of a package name.
Please revert that change.


Okay.  Please prepare to take over linux-libc-dev alltogether then,
there can be only one copy.


please drop the provides:

linux-libc-dev-alpha-cross (= 6.7.9-2), linux-libc-dev-amd64-cross (= 
6.7.9-2), linux-libc-dev-arm64-cross (= 6.7.9-2), 
linux-libc-dev-armel-cross (= 6.7.9-2), linux-libc-dev-armhf-cross (= 
6.7.9-2), linux-libc-dev-hppa-cross (= 6.7.9-2), 
linux-libc-dev-i386-cross (= 6.7.9-2), linux-libc-dev-loong64-cross (= 
6.7.9-2), linux-libc-dev-m68k-cross (= 6.7.9-2), 
linux-libc-dev-mips-cross (= 6.7.9-2), linux-libc-dev-mips64-cross (= 
6.7.9-2), linux-libc-dev-mips64el-cross (= 6.7.9-2), 
linux-libc-dev-mips64r6el-cross (= 6.7.9-2), linux-libc-dev-mipsel-cross 
(= 6.7.9-2), linux-libc-dev-powerpc-cross (= 6.7.9-2), 
linux-libc-dev-ppc64-cross (= 6.7.9-2), linux-libc-dev-ppc64el-cross (= 
6.7.9-2), linux-libc-dev-riscv64-cross (= 6.7.9-2), 
linux-libc-dev-s390x-cross (= 6.7.9-2), linux-libc-dev-sh4-cross (= 
6.7.9-2), linux-libc-dev-sparc64-cross (= 6.7.9-2), 
linux-libc-dev-x32-cross (= 6.7.9-2)

Processed: forcibly merging 1065947 1066458

[Debian Bug Tracking System]

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

> forcemerge 1065947 1066458
Bug #1065947 [src:rmlint] rmlint: FTBFS on arm{el,hf}: undefined reference to 
`rm_xattr_is_deduplicated'
Bug #1066458 [src:rmlint] rmlint: FTBFS: ./lib/session.c:227:(.text+0x701): 
undefined reference to `rm_xattr_is_deduplicated'
Merged 1065947 1066458
> thanks
Stopping processing here.

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

Processed: forcibly merging 1065942 1066273

[Debian Bug Tracking System]

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

> forcemerge 1065942 1066273
Bug #1065942 [src:lcmaps-plugins-jobrep] lcmaps-plugins-jobrep: FTBFS on 
arm{el,hf}: jobrep_data_handling.c:1282:17: error: implicit declaration of 
function ‘i2c_ASN1_INTEGER’; did you mean ‘i2s_ASN1_INTEGER’? 
[-Werror=implicit-function-declaration]
Bug #1066273 [src:lcmaps-plugins-jobrep] lcmaps-plugins-jobrep: FTBFS: 
jobrep_data_handling.c:1282:17: error: implicit declaration of function 
‘i2c_ASN1_INTEGER’; did you mean ‘i2s_ASN1_INTEGER’? 
[-Werror=implicit-function-declaration]
Merged 1065942 1066273
> thanks
Stopping processing here.

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

Processed: bug 1067247 is forwarded to https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/3770

[Debian Bug Tracking System]

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

> forwarded 1067247 
> https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/3770
Bug #1067247 [src:pulseaudio] pulseaudio: #error "_TIME_BITS=64 is allowed only 
with _FILE_OFFSET_BITS=64"
Bug #1066995 [src:pulseaudio] pulseaudio: FTBFS with _TIME_BITS=64 on 32-bit 
systems
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/3770'.
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/3770'.
> thanks
Stopping processing here.

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

Bug#1067428: contextfree: diff for NMU version 3.4+dfsg-1.1

[Gianfranco Costamagna]

Package: contextfree
Version: 3.4+dfsg-1
Severity: serious
Tags: patch  pending


Dear maintainer,

I've prepared an NMU for contextfree (versioned as 3.4+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru contextfree-3.4+dfsg/debian/changelog 
contextfree-3.4+dfsg/debian/changelog
--- contextfree-3.4+dfsg/debian/changelog   2023-01-19 00:52:13.0 
+0100
+++ contextfree-3.4+dfsg/debian/changelog   2024-03-21 15:00:29.0 
+0100
@@ -1,3 +1,10 @@
+contextfree (3.4+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop libagg2 runtime dependency (Closes: #-1)
+
+ -- Gianfranco Costamagna   Thu, 21 Mar 2024 
15:00:29 +0100
+
 contextfree (3.4+dfsg-1) unstable; urgency=medium

   * New upstream release
diff -Nru contextfree-3.4+dfsg/debian/control 
contextfree-3.4+dfsg/debian/control
--- contextfree-3.4+dfsg/debian/control 2023-01-19 00:52:13.0 +0100
+++ contextfree-3.4+dfsg/debian/control 2024-03-21 15:00:19.0 +0100
@@ -21,7 +21,7 @@

 Package: contextfree
 Architecture: any
-Depends: libagg2 (>= 1:2.6.1), ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: image generator based on context-free grammars
  Context Free is a program that produces images based on context-free grammars.
  These grammars are sets of non-deterministic rules that determine what an


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1067427: dpkg-dev: Fail to generate a substitution variable ${t64:Provides} (time_t transition)

[Christian Marillat]

Package: dpkg-dev
Version: 1.22.6
Severity: serious

Dear Maintainer,

Feel free to reassign.

I noticed this bug with the libopenshot-audio source and with
armel, armh and powerpc architectures from buildd logs and my rebuild.

I didn't pay attention for others sources, but I noticed that only
after a second rebuild...

,
| pkg-gencontrol: warning: Provides field of package libopenshot-audio9t64: 
substitution variable ${t64:Provides} used, but is not defined
| dpkg-gencontrol: warning: Provides field of package libopenshot-audio9t64: 
substitution variable ${t64:Provides} used, but is not defined
`

https://buildd.debian.org/status/fetch.php?pkg=libopenshot-audio=powerpc=0.3.2%2Bdfsg1-2.1=1709343482=0

https://buildd.debian.org/status/fetch.php?pkg=libopenshot-audio=armhf=0.3.2%2Bdfsg1-2.1=1709142395=0

Chirstian


-- Package-specific info:

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

Kernel: Linux 6.8.1-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dpkg-dev depends on:
ii  binutils  2.42-4
ii  bzip2 1.0.8-5.1
ii  libdpkg-perl  1.22.6
ii  make  4.3-4.1
ii  patch 2.7.6-7
ii  perl  5.38.2-3.2
ii  tar   1.35+dfsg-3
ii  xz-utils  5.6.0-0.2

Versions of packages dpkg-dev recommends:
ii  build-essential  12.10
ii  clang-16 [c-compiler]1:16.0.6-23
ii  fakeroot 1.34-1
ii  gcc [c-compiler] 4:13.2.0-7
ii  gcc-13 [c-compiler]  13.2.0-19
ii  gnupg2.2.40-3
ii  gpgv 2.2.40-3
pn  libalgorithm-merge-perl  

Versions of packages dpkg-dev suggests:
pn  debian-keyring  

-- no debconf information

Bug#1066589: marked as done (quisk: FTBFS: charleston/chas_rx2.c:968:3: error: implicit declaration of function ‘Py_InitModule’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 14:37:32 +0100
with message-id 
and subject line Re: Bug#1066589: quisk: FTBFS: charleston/chas_rx2.c:968:3: 
error: implicit declaration of function ‘Py_InitModule’ 
[-Werror=implicit-function-declaration]
has caused the Debian Bug report #1066589,
regarding quisk: FTBFS: charleston/chas_rx2.c:968:3: error: implicit 
declaration of function ‘Py_InitModule’ [-Werror=implicit-function-declaration]
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.)


-- 
1066589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quisk
Version: 4.2.24-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I. -I.. -I/usr/include/libusb-1.0 -I/usr/include/python3.11 -c 
> charleston/chas_rx2.c -o 
> build/temp.linux-x86_64-cpython-311/charleston/chas_rx2.o
> charleston/chas_rx2.c: In function ‘initchas_rx1’:
> charleston/chas_rx2.c:968:3: error: implicit declaration of function 
> ‘Py_InitModule’ [-Werror=implicit-function-declaration]
>   968 |   Py_InitModule ("chas_rx1", QuiskMethods);
>   |   ^
> charleston/chas_rx2.c:973:5: warning: ‘return’ with no value, in function 
> returning non-void [-Wreturn-type]
>   973 | return; //Error
>   | ^~
> charleston/chas_rx2.c:966:16: note: declared here
>   966 | PyMODINIT_FUNC initchas_rx1 (void)
>   |^~~~
> cc1: some warnings being treated as errors
> error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
> E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned 
> exit code 13
> make: *** [debian/rules:3: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/quisk_4.2.24-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: quisk
Source-Version: 4.2.30-1
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated quisk 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: Thu, 21 Mar 2024 12:31:12 +
Source: quisk
Architecture: source
Version: 4.2.30-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 1063085
Changes:
 quisk (4.2.30-1) unstable; urgency=medium
 .
   * New 

Bug#1066593: marked as done (libnbcompat: FTBFS: lchflags.c:49:17: error: implicit declaration of function ‘chflags’; did you mean ‘lchflags’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 13:20:52 +
with message-id 
and subject line Bug#1066593: fixed in libnbcompat 20180822-6
has caused the Debian Bug report #1066593,
regarding libnbcompat: FTBFS: lchflags.c:49:17: error: implicit declaration of 
function ‘chflags’; did you mean ‘lchflags’? 
[-Werror=implicit-function-declaration]
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.)


-- 
1066593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnbcompat
Version: 20180822-5.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D__DBINTERFACE_PRIVATE -I. 
> -I.  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -DHAVE_CONFIG_H -c lchflags.c
> lchflags.c: In function ‘lchflags’:
> lchflags.c:49:17: error: implicit declaration of function ‘chflags’; did you 
> mean ‘lchflags’? [-Werror=implicit-function-declaration]
>49 | return (chflags(path, flags));
>   | ^~~
>   | lchflags
> cc1: some warnings being treated as errors
> *** [lchflags.o] Error code 1
> 
> bmake[1]: stopped in /<>
> 1 error
> 
> bmake[1]: stopped in /<>
> dh_auto_build: error: bmake -j1 returned exit code 2
> make: *** [debian/rules:19: build] Error 255


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/libnbcompat_20180822-5.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libnbcompat
Source-Version: 20180822-6
Done: John Goerzen 

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

Debian distribution maintenance software
pp.
John Goerzen  (supplier of updated libnbcompat 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: Thu, 21 Mar 2024 07:12:25 -0500
Source: libnbcompat
Architecture: source
Version: 20180822-6
Distribution: unstable
Urgency: medium
Maintainer: John Goerzen 
Changed-By: John Goerzen 
Closes: 1066593
Changes:
 libnbcompat (20180822-6) unstable; urgency=medium
 .
   * Remove lchflags, which wasn't working anyway and which called chflags,
 which had no prototype.  Closes: #1066593.
Checksums-Sha1:
 5b45ca1db2780a7c44ac11f67d509bdf63558b79 1966 libnbcompat_20180822-6.dsc
 4fee2a4737d9f8a83ad36a226d49ab2013a8651b 5176 libnbcompat_20180822-6.diff.gz
 7773c537d172d1b5e084f95d44eb2c83e73dc1a8 6660 
libnbcompat_20180822-6_source.buildinfo
Checksums-Sha256:
 7b4d011d32031bfb106b3e20781c3b0c4f6a17322699a77ced57b4df48032ab2 1966 
libnbcompat_20180822-6.dsc
 1f978d2f4efe9d44a752e7f4eb0bc96655f4a41e8d1b7cdc1a5cbac8f3d3d2f8 5176 
libnbcompat_20180822-6.diff.gz
 599b580c77df9235432798e80ece9d0176a79eb055df1da209ac2962767aabe3 6660 
libnbcompat_20180822-6_source.buildinfo
Files:
 

Bug#1062010: marked as done (dar: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Thu, 21 Mar 2024 13:04:28 +
with message-id 
and subject line Bug#1062010: fixed in dar 2.7.13-6
has caused the Debian Bug report #1062010,
regarding dar: NMU diff for 64-bit time_t transition
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.)


-- 
1062010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dar
Version: 2.7.13-2
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
dar as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for dar
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-15-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru dar-2.7.13/debian/changelog dar-2.7.13/debian/changelog
--- dar-2.7.13/debian/changelog 2023-11-08 12:07:15.0 +
+++ dar-2.7.13/debian/changelog 2024-01-30 21:43:50.0 +
@@ -1,3 +1,10 @@
+dar (2.7.13-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle   Tue, 30 Jan 2024 21:43:50 +
+
 dar (2.7.13-2) unstable; urgency=medium
 
   * Change build-dep on python3-all-dev to python3-dev.  Closes: #1055500.
diff -Nru dar-2.7.13/debian/control dar-2.7.13/debian/control
--- dar-2.7.13/debian/control   2023-11-08 12:07:15.0 +
+++ dar-2.7.13/debian/control   2024-01-30 21:43:50.0 +
@@ -19,7 +19,7 @@
 Package: libdar-dev
 Section: libdevel
 Architecture: any
-Depends: libdar64-6000 (= ${binary:Version}), ${misc:Depends}, zlib1g-dev,
+Depends: libdar64-6000t64 (= ${binary:Version}), ${misc:Depends}, zlib1g-dev,
  libbz2-dev, libzstd-dev, liblzo2-dev, liblzma-dev, liblz4-dev,
  libgcrypt20-dev, libgpg-error-dev, libassuan-dev, libargon2-dev
 Description: Disk ARchive: Development files for shared library
@@ -36,7 +36,10 @@
  compression, ATTR/ACL support. DAR also supports Pipes for remote
  operations, including with ssh.
 
-Package: libdar64-6000
+Package: libdar64-6000t64
+Provides: ${t64:Provides}
+Replaces: libdar64-6000
+Breaks: libdar64-6000 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -61,7 +64,7 @@
 
 Package: dar
 Architecture: any
-Depends: libdar64-6000 (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}
+Depends: libdar64-6000t64 (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}
 Suggests: par2, dar-docs
 Description: Disk ARchive: Backup directory tree and files
  Full featured archiver with support for differential backups, slices,
diff -Nru dar-2.7.13/debian/libdar64-6000.dirs 
dar-2.7.13/debian/libdar64-6000.dirs
--- dar-2.7.13/debian/libdar64-6000.dirs2023-09-11 12:53:53.0 
+
+++ dar-2.7.13/debian/libdar64-6000.dirs1970-01-01 00:00:00.0 

Bug#1067247: pulseaudio: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

[Simon McVittie]

On Wed, 20 Mar 2024 at 20:00:32 +, Thorsten Glaser wrote:
> Unfortunately, as with umockdev, I have no idea what is going on
> here… does it #undef _FILE_OFFSET_BITS or something?

Yes it does. padsp(1) is based on a LD_PRELOAD module similar to those
used in fakeroot, fakechroot, umockdev and so on, which works by
interposing a bunch of glibc functions including stat(). As currently
implemented, it achieves this by #undef'ing the _FILE_OFFSET_BITS feature
test so that it can interpose all flavours of stat(), including
stat64() and so on.

Since glibc 2.34, on 32-bit architectures all such LD_PRELOAD modules
need updating to also interpose __lstat64_time64(), __stat64_time64(),
__fstat64_time64() and __fstatat64_time64() on architectures where they
exist - otherwise, programs and libraries compiled with 64-bit time_t
will bypass the wrapped stat(), stat64() etc. and call __stat64_time64()
instead, and therefore the wrapping will be ineffective and padsp will
not work as intended.

Because padsp is not core functionality for pulseaudio, a brute-force
approach to unblocking this could be to disable it on 32-bit non-i386
architectures. Untested pseudocode:

--- meson.build
+++ meson.build
 if cc.has_header('sys/soundcard.h', required: get_option('oss-output'))
   # OSS output via daemon module-detect
   cdata.set('HAVE_OSS_OUTPUT', 1)
   # OSS wrapper
-  cdata.set('HAVE_OSS_WRAPPER', 1)
+  if cc.sizeof('void *') >= 8 or host_machine.cpu_family() == 'x86'
+cdata.set('HAVE_OSS_WRAPPER', 1)
+  endif
   cdata.set('PULSEDSP_LOCATION', pulsedsp_location)
 endif

(and then change the packaging to tolerate it not being installed)

In practice padsp is mainly useful for legacy i386 binaries and maybe
a few very early legacy amd64 binaries (late 90s/early 00s era games,
especially ported by Loki Games) which might assume OSS audio, and not
support ALSA or PulseAudio directly. Since we're breaking the platform ABI
on armel/armhf/etc. *anyway*, we can't rely on the ability to run legacy
binaries even if they exist, so it's probably no longer interesting to
provide padsp on those architectures.

smcv

Bug#1067208: umockdev: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

[Simon McVittie]

On Thu, 21 Mar 2024 at 14:13:38 +0500, Andrey Rakhmatullin wrote:
> On Wed, Mar 20, 2024 at 03:05:34AM +, Thorsten Glaser wrote:
> > cc -Ilibumockdev-preload.so.0.0.0.p -I. -I.. -fdiagnostics-color=always 
> > -Wall -Winvalid-pch -std=gnu11 -Werror=missing-prototypes 
> > -Werror=strict-prototypes -Werror=nested-externs -Werror=pointer-arith 
> > -Werror=implicit-function-declaration -Werror=implicit-int 
> > -Werror=int-conversion -Werror=old-style-definition -Werror=pointer-arith 
> > -Werror=init-self -Werror=format-security -Werror=format=2 
> > -Werror=return-type -Werror=uninitialized -Wcast-align -Wno-error=pragmas 
> > -Wno-error=discarded-qualifiers -Wno-error=incompatible-pointer-types 
> > -Wno-error=pointer-sign -Wno-unused-but-set-variable -Wno-unused-function 
> > -Wno-unused-label -Wno-unused-value -Wno-unused-variable -g -O2 
> > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> > -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
> > -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> > -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=default 
> > -MD -MQ libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o -MF 
> > libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o.d -o 
> > libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o -c 
> > ../src/libumockdev-preload.c
> > In file included from /usr/include/features.h:393,
> >  from /usr/include/assert.h:35,
> >  from ../src/libumockdev-preload.c:31:
> > /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is 
> > allowed only with _FILE_OFFSET_BITS=64"
> >26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
> >   | ^
> > 
> > 
> > I admit I don’t exactly see what’s going on here. Does it
> > maybe #unset _FILE_OFFSET_BITS or something?
> It does. src/libumockdev-preload.c:
> 
> /* override -D_FILE_OFFSET_BITS, it breaks us */
> #undef _FILE_OFFSET_BITS
> 
> This has the same roots as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065973 as this file
> says "The initial code for intercepting function calls was inspired and
> partially copied from kmod's testsuite". Maybe it can also have the same
> fix (but that bug isn't fixed yet, though it has a proposed fix).

This appears to be because umockdev is based on a LD_PRELOAD module that
interposes wrapped or mock versions of glibc functions like stat() that
are sensitive to the sizes of off_t and time_t.

I don't think the proposed fix in kmod is correct, and I don't think
an equivalent in umockdev would be correct either. Since glibc 2.34,
on 32-bit architectures all such LD_PRELOAD modules will need updating
to also wrap __lstat64_time64(), __stat64_time64(), __fstat64_time64()
and __fstatat64_time64() on architectures where they exist - otherwise,
programs and libraries compiled with 64-bit time_t will bypass the
wrapped stat(), stat64() etc. and call __stat64_time64() instead, and
therefore the wrapping will be ineffective and umockdev's mock devices
will not be seen.

fakeroot, fakechroot and other LD_PRELOAD modules that interpose stat()
will already be doing something similar, and might provide a useful
reference for what is needed. Here's the equivalent in fakechroot:
https://github.com/dex4er/fakechroot/pull/104/commits/dac74cd68cfb6eeaae9cd13bdc48737a44980df9

smcv

Bug#1065973: kmod: FTBFS due to time64 transition

[Simon McVittie]

On Thu, 21 Mar 2024 at 15:45:13 +0500, Andrey Rakhmatullin wrote:
> On Wed, Mar 13, 2024 at 08:23:07AM +0100, Helge Deller wrote:
> > The patch below builds for me on the hppa platform.
> Unfortunately tests fail here with it in an armhf chroot, I don't know if
> it's generic or because the chroot is a qemu-based one on amd64.

I think the root cause (both for needing to unset _FILE_OFFSET_BITS, and
for the tests failing) is that kmod's test suite is interposing
mock/wrapped versions of the stat() family.

With the transition to 64-bit time_t, there are new members of the stat()
family that will also need interposing on 32-bit architectures:
__lstat64_time64() is the replacement for lstat(), and __stat64_time64()
for stat().

There are also __fstat64_time64() and __fstatat64_time64(), but kmod
doesn't seem to interpose fstat() or fstatat(), so those are probably
unnecessary in this case.

fakeroot, fakechroot and other LD_PRELOAD modules that interpose stat()
will already be doing something similar, and might provide a useful
reference for what is needed. Here's the equivalent in fakechroot:
https://github.com/dex4er/fakechroot/pull/104/commits/dac74cd68cfb6eeaae9cd13bdc48737a44980df9

smcv

Processed: Re: Bug#1067386: anymarkup-core: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:python-flexmock
Bug #1067386 [src:anymarkup-core] anymarkup-core: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Bug reassigned from package 'src:anymarkup-core' to 'src:python-flexmock'.
No longer marked as found in versions anymarkup-core/0.8.1-3.
Ignoring request to alter fixed versions of bug #1067386 to the same values 
previously set
> merge -1 1067358
Bug #1067386 [src:python-flexmock] anymarkup-core: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Bug #1067386 [src:python-flexmock] anymarkup-core: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Marked as found in versions python-flexmock/0.11.3-3.
Bug #1067358 [src:python-flexmock] python-flexmock: FTBFS: AttributeError: 
module '_pytest.runner' has no attribute 'call_runtest_hook'
Merged 1067358 1067386

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