Bug#1044072: marked as done (python-anndata: FTBFS with pandas 2.0)

[Debian Bug Tracking System]

Your message dated Fri, 29 Mar 2024 03:06:13 +
with message-id 
and subject line Bug#1044072: fixed in python-anndata 0.10.6-1
has caused the Debian Bug report #1044072,
regarding python-anndata: FTBFS with pandas 2.0
to be marked as done.

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

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


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

Package: src:python-anndata
Version: 0.8.0-4
Control: block 1043240 by -1

python-anndata fails to build with pandas 2.0, currently in experimental.

Build log:
https://launchpadlibrarian.net/680701368/buildlog_ubuntu-mantic-amd64.python-anndata_0.8.0-4_BUILDING.txt.gz

Autopkgtest log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-anndata/36575847/log.gz

A common source of failures is that pandas.util.testing has been renamed 
to pandas.testing.  Both names were available in all 1.x versions (and 
hence in Debian stable and oldstable), so Debian packages that were 
using this can immediately switch unconditionally.
--- End Message ---
--- Begin Message ---
Source: python-anndata
Source-Version: 0.10.6-1
Done: Diane Trout 

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated python-anndata 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, 28 Mar 2024 18:36:47 -0700
Source: python-anndata
Architecture: source
Version: 0.10.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Diane Trout 
Closes: 1044072
Changes:
 python-anndata (0.10.6-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * New upstream version (Closes: #1044072)
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * Set upstream metadata fields: Repository.
   * Build-Depends: python3-hatchling, python3-hatch-vcs, python3-httpx
   * Patch out the need for scanpy for documentation example
 .
   [ Diane Trout ]
   * Add python3-distributed as a build and autopkgtest dependency
   * Add skip-awkward.patch to tell pytest to skip tests that depend on
 awkward.
   * Add skip-cupy-tests.patch to skip cupy dependent tests.
   * New upstream release 0.10.6-1
   * Refresh patches
   * Add python3-pytest-mock as test and autopkgtest dependency
Checksums-Sha1:
 131360fcaa1d66a5f1bcca96315392c67c365032 2983 python-anndata_0.10.6-1.dsc
 9b2f78f923a02750f0ff97c7c3029ab3d46fb1f9 509188 
python-anndata_0.10.6.orig.tar.gz
 d5d88f6e35ad732ef6ed35452053b6909dbe7baf 7852 
python-anndata_0.10.6-1.debian.tar.xz
 1f463b79c3b2bb2cbb03af96e87466e02260c97a 11303 
python-anndata_0.10.6-1_amd64.buildinfo
Checksums-Sha256:
 5f2ea2cfe17c5f014a8fb5981e188d6eace6bc60eab0473dcde994fe50fd0259 2983 
python-anndata_0.10.6-1.dsc
 4cd8eebfaebc93bb88e9b1df07d658ad97766226fc480100f2162bec1f64599d 509188 
python-anndata_0.10.6.orig.tar.gz
 ac60bd5cf94473cea9fbce1ba8da562d055a35bac58c4dc07e447da0129746f5 7852 
python-anndata_0.10.6-1.debian.tar.xz
 d546254494d8cf3594e35015d50cce7a889b78301cf10bb4cf05dd2f7e5202d2 11303 
python-anndata_0.10.6-1_amd64.buildinfo
Files:
 be8bfa50ed6f7b2fe4a906ca0412c06d 2983 python optional 
python-anndata_0.10.6-1.dsc
 debd5a08277b7de55547c981fa94b27e 509188 python optional 
python-anndata_0.10.6.orig.tar.gz
 7965c6289c611f1e77a5fe7c1ba65b64 7852 python optional 
python-anndata_0.10.6-1.debian.tar.xz
 b8693f795f02f082cc153f47079d6b4a 11303 python optional 
python-anndata_0.10.6-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQVcMeSBIEX5AQ11mQ04NnM013AFAmYGI3YACgkQmQ04NnM0
13AuoA/9G61g8kAELim0hnVtEx6HLuDE2vNEmUntnk1gYQPGp/r6kzk+2cpb7FjF
xf9atM4WQFECG5byqVFHu3zwJIMZ0TOKnv7Z15BLRFec4Xbq7c6tC10tiRclU1mJ
frtpqXMi6XEXTrxvJbL727SiXWJyZHQHido1AHAej0jL3EeYH8JjZpven6gjBIeo
TQSib4EPxC5RlUQLOx4KEyxAeODmqP50J82xTKhZ89bK/Jjewv1L96kuskPV9bsQ
eHIeBuaX4a/ZsN29yYyx43wEIf8sb1EHhHF5lVcnsQPc48C9h+bb7KSwxd8EWvoM
MI+k7iga66DxcENZyvHsy3VleJ7msl1c5KRC66Zj4qzuABY3ENjg5PyGxs66gfFG

Bug#1067875: marked as done (howm: fails to install: Error: Cannot open load file: No such file or directory, iigrep)

[Debian Bug Tracking System]

Your message dated Fri, 29 Mar 2024 03:01:40 +
with message-id 
and subject line Bug#1067875: fixed in howm 1.5.1-2
has caused the Debian Bug report #1067875,
regarding howm: fails to install: Error: Cannot open load file: No such file or 
directory, iigrep
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.)


-- 
1067875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: howm
Version: 1.5.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up howm (1.5.1-1) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install howm for emacs
  install/howm-1.5.1: Handling install of emacsen flavor emacs
  install/howm-1.5.1: byte-compiling for emacs
  
  In gfunc-define-function:
  gfunc.el:71:2: Warning: docstring has wrong usage of unescaped single quotes 
(use \= or different quoting)
  
  In toplevel form:
  howm-backend.el:22:2: Error: Cannot open load file: No such file or 
directory, iigrep
  
  In howm-map-with-index:
  howm-common.el:160:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-first-n:
  howm-common.el:235:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-classify:
  howm-common.el:361:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-with-coding-system:
  howm-common.el:441:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-with-schedule-interval:
  howm-common.el:526:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In toplevel form:
  howm-date.el:22:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm-menu.el:22:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm-misc.el:22:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm-mkmenu.el:71:2: Warning: `mapcar' called for effect; use `mapc' or 
`dolist' instead
  
  In toplevel form:
  howm-mode.el:38:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm-reminder.el:22:2: Error: Cannot open load file: No such file or 
directory, iigrep
  
  In howm-dont-warn-free-variable:
  howm-vars.el:78:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-funcall-if-defined:
  howm-vars.el:85:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  howm-vars.el:125:2: Warning: defvar `howm-compatible-to-ver1dot3' docstring 
has wrong usage of unescaped single quotes (use \= or different quoting)
  howm-vars.el:600:2: Warning: custom-declare-variable `howm-list-title' 
docstring has wrong usage of unescaped single quotes (use \= or different 
quoting)
  howm-vars.el:814:2: Warning: custom-declare-variable 
`howm-process-coding-system' docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  howm-vars.el:839:2: Warning: custom-declare-variable 
`howm-iigrep-preview-items' docstring wider than 80 characters
  howm-vars.el:941:2: Warning: custom-declare-variable 
`howm-view-external-viewer-assoc' docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  howm-vars.el:984:2: Warning: custom-declare-variable `howm-auto-narrow' 
docstring has wrong usage of unescaped single quotes (use \= or different 
quoting)
  
  In toplevel form:
  howm-view.el:22:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm.el:65:2: Error: Cannot open load file: No such file or directory, iigrep
  
  In riffle-summary-name-format:
  riffle.el:115:2: Warning: docstring wider than 80 characters
  
  In riffle-contents-name-format:
  riffle.el:115:2: Warning: docstring wider than 80 characters
  ERROR: install script from howm package failed
  dpkg: error processing package howm (--configure):
   installed howm package post-installation script subprocess returned error 
exit status 1


cheers,

Andreas


howm_1.5.1-1.log.gz
Description: 

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

[Emmanuel Arias]

Hi Lucas,

Sorry, I cannot reproduce this error. I tried running the package 
locally and in the salsa-ci [0]


[0] https://salsa.debian.org/python-team/packages/cachy/-/pipelines/658758

--
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1 


 ⠈⠳⣄


OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: severity of 1059183 is normal

[Debian Bug Tracking System]

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

> severity 1059183 normal
Bug #1059183 [ftp.debian.org] RM: loadlin -- ROM; uploads are stuck
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 1059183 is serious

[Debian Bug Tracking System]

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

> severity 1059183 serious
Bug #1059183 [ftp.debian.org] RM: loadlin -- ROM; uploads are stuck
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1067923: alsa-ucm-conf: should depend on libasound2t64 instead of libasound2

[Daniel Serpell]

Package: alsa-ucm-conf
Version: 1.2.11-1
Severity: serious
Justification: depends on missing package after time_t transition

Dear maintainer,

After the time_t transition, the libasound2 was renamed to libasound2t64, so
the dependencies should be updated.

Regards,


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

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

Versions of packages alsa-ucm-conf depends on:
ii  libasound2t64 [libasound2]  1.2.11-1+b1

alsa-ucm-conf recommends no packages.

alsa-ucm-conf suggests no packages.

-- no debconf information

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Santiago Vila]

Version: 2.45.3+ds-3

El 28/3/24 a las 23:38, Daniel Swarbrick escribió:

On 28.03.24 23:33, Santiago Vila wrote:

If you prefer I could report this build failure in a new report
(or you can also use the clone command so that the bug has a new number,
then close the old bug).


Please report a new bug, with just the relevant info regarding the new build 
failure.


Ok, will do. Closing this one, then.


We already override the default test timeout for arm, mips64el and riscv64 to 60 minutes, 
as well as set "-short", because otherwise those archs simply take too long to 
grind through all the tests.

If you expect these tests to pass on a host with only one or two cores, we will 
certainly need to raise the test timeout, even for fast amd64 hosts.


Yes, I expect it to work on all systems on which prometheus itself works.
(And as a prometheus user myself, I've used it in all sort of systems, big or 
small).

Thanks.

Bug#1067467: closing 1067467

[Samuel Thibault]

close 1067467 
thanks

Processed: closing 1067467

[Debian Bug Tracking System]

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

> close 1067467
Bug #1067467 [src:eztrace] eztrace fails tests during the build on almost all 
architectures
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1066735: marked as done (mpich: fails to connect processes and report ranks)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 22:56:50 +
with message-id 
and subject line Bug#1066735: fixed in mpich 4.2.0-5.1
has caused the Debian Bug report #1066735,
regarding mpich: fails to connect processes and report ranks
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.)


-- 
1066735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eztrace
Version: 2.1-6
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[3]: Entering directory '/<>/test/mpi'
> make[3]: Nothing to be done for 'all'.
> make[3]: Leaving directory '/<>/test/mpi'
>  [OK] 
> > Running /<>/test/mpi/test_mpi_ping.sh...
> > Running mpirun.mpich -np 2 /<>/build-mpich/src/eztrace -p -t 
> > mpich ./mpi_ping
> Eztrace test Mode
> Eztrace test Mode
> dir: mpi_ping_trace
> [P0T0] Starting EZTrace (pid: 878489)...
> [P0T0] MPI mode selected
> This program requires 2 MPI processes, aborting...
> dir: mpi_ping_trace
> /bin/rm: cannot remove 'mpi_ping_trace': Directory not empty
> [P0T0] Stopping EZTrace (pid:878489)...
> [P0T0] Starting EZTrace (pid: 878488)...
> [P0T0] MPI mode selected
> This program requires 2 MPI processes, aborting...
> [P0T0] Stopping EZTrace (pid:878488)...
>  [OK] 
> otf2-print: warning: out of order Group definition: "MPI_COMM_4_group" <4>
> otf2-print: warning: out of order Comm/InterComm definition: "MPI_COMM_4" <4>
>  > Checking for ENTER/LEAVE parity
>  [OK] 0 event of each type
>  > Checking the number of MPI_SEND events
>   [ERROR] 0 events (expected: 20200)
>  > Checking the number of MPI_RECV events
>   [ERROR] 0 events (expected: 20200)
>  > Checking the number of ENTER MPI_Send events
>   [ERROR] 0 events (expected: 20200)
>  > Checking the number of LEAVE MPI_Send events
>   [ERROR] 0 events (expected: 20200)
>  > Checking the number of ENTER MPI_Recv events
>   [ERROR] 0 events (expected: 20200)
>  > Checking the number of LEAVE MPI_Recv events
>   [ERROR] 0 events (expected: 20200)
> PASS: 2, FAILED:6, TOTAL: 8
>   [ERROR] Test /<>/test/mpi/test_mpi_ping.sh 
> failed
> > Running /<>/test/mpi/test_mpi_waitall.sh...
> > Running mpirun.mpich -np 4 /<>/build-mpich/src/eztrace -p -t 
> > mpich ./waitall
> Eztrace test Mode
> Eztrace test Mode
> Eztrace test Mode
> Eztrace test Mode
> dir: waitall_trace
> dir: waitall_trace
> [P0T0] Starting EZTrace (pid: 878563)...
> [P0T0] MPI mode selected
> Please run with 4 processes.
> [P0T0] Starting EZTrace (pid: 878567)...
> [P0T0] MPI mode selected
> Please run with 4 processes.
> dir: waitall_trace
> [P0T0] Starting EZTrace (pid: 878558)...
> [P0T0] MPI mode selected
> Please run with 4 processes.
> [P0T0] Stopping EZTrace (pid:878563)...
> [P0T0] Stopping EZTrace (pid:878567)...
> dir: waitall_trace
> [P0T0] Starting EZTrace (pid: 878566)...
> [P0T0] MPI mode selected
> Please run with 4 processes.
> [P0T0] Stopping EZTrace (pid:878566)...
> [P0T0] Stopping EZTrace (pid:878558)...
>   [ERROR] command 'mpirun.mpich -np 4 
> /<>/build-mpich/src/eztrace -p -t mpich ./waitall' failed
> otf2-print: warning: out of order Group definition: "MPI_COMM_4_group" <4>
> otf2-print: warning: out of order Comm/InterComm definition: "MPI_COMM_4" <4>
>  > Checking for ENTER/LEAVE parity
>  [OK] 0 event of each type
>  > Checking the number of MPI_ISEND events
>   [ERROR] 0 events (expected: 3)
>  > Checking the number of MPI_ISEND_COMPLETE events
>   [ERROR] 0 events (expected: 3)
>  > Checking the number of MPI_IRECV events
>   [ERROR] 0 events (expected: 3)
>  > Checking the number of MPI_IRECV_REQUEST events
>   [ERROR] 0 events (expected: 3)
>  > Checking the number of ENTER MPI_Isend events
>   [ERROR] 0 events (expected: 3)
>  > Checking the number of LEAVE MPI_Isend events
>   [ERROR] 0 events (expected: 3)
>  > Checking the number of ENTER MPI_Irecv events
>   [ERROR] 0 events (expected: 3)
>  > Checking the number of LEAVE MPI_Irecv events
>   [ERROR] 0 events (expected: 3)
>  > Checking the number of ENTER MPI_Waitall events
>   [ERROR] 0 events (expected: 4)
>  > Checking the number of LEAVE 

Bug#1067281: marked as done (eztrace: FTBFS: 9: [OTF2] src/otf2_file_posix.c:163: error: File or directory does not exist: POSIX: 'waitall_trace/eztrace_log/0.evt')

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 22:56:50 +
with message-id 
and subject line Bug#1066735: fixed in mpich 4.2.0-5.1
has caused the Debian Bug report #1066735,
regarding eztrace: FTBFS: 9: [OTF2] src/otf2_file_posix.c:163: error: File or 
directory does not exist: POSIX: 'waitall_trace/eztrace_log/0.evt'
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.)


-- 
1066735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eztrace
Version: 2.1-7
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[3]: Entering directory '/<>/test/mpi'
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  mpi_ring.c   -o 
> mpi_ring
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  mpi_multiring.c   -o 
> mpi_multiring
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  mpi_spawn.c   -o 
> mpi_spawn
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  test_mpi.c   -o 
> test_mpi
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  waitall.c   -o 
> waitall
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  waitany.c   -o 
> waitany
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  persistent.c   -o 
> persistent
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  mpi_ping.c   -o 
> mpi_ping
> mpicc.mpich -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 -Wl,-z,relro -Wl,-z,now  allgather.c   -o 
> allgather
> make[3]: Leaving directory '/<>/test/mpi'
>  [OK] 
> > Running /<>/test/mpi/test_mpi_ping.sh...
> > Running mpirun.mpich -np 2 /<>/build-mpich/src/eztrace -p -t 
> > mpich ./mpi_ping
> Eztrace test Mode
> Eztrace test Mode
> dir: mpi_ping_trace
> dir: mpi_ping_trace
> [P0T0] Starting EZTrace (pid: 2348798)...
> [P0T0] MPI mode selected
> This program requires 2 MPI processes, aborting...
> [P0T0] Starting EZTrace (pid: 2348797)...
> [P0T0] MPI mode selected
> This program requires 2 MPI processes, aborting...
> [P0T0] Stopping EZTrace (pid:2348798)...
> [P0T0] Stopping EZTrace (pid:2348797)...
>  [OK] 
> otf2-print: warning: out of order Group definition: "MPI_COMM_4_group" <4>
> otf2-print: warning: out of order Comm/InterComm definition: "MPI_COMM_4" <4>
>  > Checking for ENTER/LEAVE parity
>  [OK] 0 event of each type
>  > Checking the number of MPI_SEND events
>   [ERROR] 0 events (expected: 20200)
>  > Checking the number of MPI_RECV events
>   [ERROR] 0 events (expected: 20200)
>  > Checking the number of ENTER MPI_Send events
>   [ERROR] 0 events (expected: 20200)
>  > Checking the number of LEAVE MPI_Send events
>   [ERROR] 0 events (expected: 

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Daniel Swarbrick]

On 28.03.24 23:33, Santiago Vila wrote:

If you prefer I could report this build failure in a new report
(or you can also use the clone command so that the bug has a new number,
then close the old bug).


Please report a new bug, with just the relevant info regarding the new 
build failure.


We already override the default test timeout for arm, mips64el and 
riscv64 to 60 minutes, as well as set "-short", because otherwise those 
archs simply take too long to grind through all the tests.


If you expect these tests to pass on a host with only one or two cores, 
we will certainly need to raise the test timeout, even for fast amd64 hosts.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Santiago Vila]

El 28/3/24 a las 22:42, Daniel Swarbrick escribió:

I think you are taking the "FAILED" out of context and misinterpreting the test 
output.


This is very likely, yes, and I'm sorry for that.

If you prefer I could report this build failure in a new report
(or you can also use the clone command so that the bug has a new number,
then close the old bug).

Thanks.

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Daniel Swarbrick]

As expected:

=== RUN   TestQuerierIndexQueriesRace/[m!="0"___name__="metric"]
panic: test timed out after 20m0s
...
FAILgithub.com/prometheus/prometheus/tsdb   1200.016s

On 28.03.24 23:13, Santiago Vila wrote:

Ok, I'm attaching one of my build logs for version 2.45.3+ds-3.
This one was tried on a m6a.large instance from AWS, which has 2 CPUs.

Thanks.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Santiago Vila]

El 28/3/24 a las 22:42, Daniel Swarbrick escribió:

Please can you find in your logs the _actual_ failing test or tests, because it 
is not TestRulesUnitTest.


Ok, I'm attaching one of my build logs for version 2.45.3+ds-3.
This one was tried on a m6a.large instance from AWS, which has 2 CPUs.

Thanks.

prometheus_2.45.3+ds-3_amd64-20240325T141933.921Z.gz
Description: application/gzip

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Daniel Swarbrick]

On 28.03.24 15:00, Santiago Vila wrote:

In either case, this is still happening for me in the current version:

Lucas Nussbaum  wrote:

   FAILED:
1:48: parse error: unexpected character inside braces: '0'


I think you are taking the "FAILED" out of context and misinterpreting 
the test output. Those are TestRulesUnitTest/* subtests, which are 
expected to fail. The summary at the end shows the expected results:


=== RUN   TestRulesUnitTest
...
=== RUN   TestRulesUnitTest/Bad_input_series
Unit Testing:  ./testdata/bad-input-series.yml
  FAILED:
1:48: parse error: unexpected character inside braces: '0'
...
--- PASS: TestRulesUnitTest (0.38s)
--- PASS: TestRulesUnitTest/Passing_Unit_Tests (0.22s)
--- PASS: TestRulesUnitTest/Long_evaluation_interval (0.13s)
--- PASS: TestRulesUnitTest/Bad_input_series (0.00s)
--- PASS: TestRulesUnitTest/Bad_PromQL (0.00s)
--- PASS: TestRulesUnitTest/Bad_rules_(syntax_error) (0.00s)
--- PASS: TestRulesUnitTest/Bad_rules_(error_evaluating) (0.00s)
--- PASS: TestRulesUnitTest/Simple_failing_test (0.01s)
--- PASS: TestRulesUnitTest/Disabled_feature_(@_modifier) (0.00s)
--- PASS: TestRulesUnitTest/Enabled_feature_(@_modifier) (0.00s)
--- PASS: TestRulesUnitTest/Disabled_feature_(negative_offset) (0.00s)
--- PASS: TestRulesUnitTest/Enabled_feature_(negative_offset) (0.00s)

You will see this in the output of _passing_ debci test runs.

Please can you find in your logs the _actual_ failing test or tests, 
because it is not TestRulesUnitTest.


If you are running tests on a VM with a single core, it's quite likely 
that you're hitting the test timeout, which I would find a more 
reasonable explanation for the dh_auto_test_error, since the Prometheus 
tests are quite extensive. They will take more than an hour on an 11th 
gen Intel Core i7 if I set GOMAXPROCS=1. Since debian/rules is setting a 
test timeout of 20m by default, this would fail.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066649: marked as done (libtritonus-java: FTBFS: org_tritonus_lowlevel_pogg_Buffer.c:224:16: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 21:15:52 +
with message-id 
and subject line Bug#1066649: fixed in libtritonus-java 20070428-14.2
has caused the Debian Bug report #1066649,
regarding libtritonus-java: FTBFS: org_tritonus_lowlevel_pogg_Buffer.c:224:16: 
error: implicit declaration of function ‘memcpy’ 
[-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.)


-- 
1066649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtritonus-java
Version: 20070428-14.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 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g 
> -Wall -I. -I/usr/lib/jvm/default-java/include 
> -I/usr/lib/jvm/default-java/include/linux -I../../../jni/ -fPIC -D_REENTRANT  
>  -c -o org_tritonus_lowlevel_pogg_Buffer.o org_tritonus_lowlevel_pogg_Buffer.c
> In file included from common.h:24,
>  from org_tritonus_lowlevel_pogg_Buffer.c:27:
> org_tritonus_lowlevel_pogg_Buffer.c: In function ‘setHandle’:
> ../common/HandleFieldHandler.h:59:57: warning: cast from pointer to integer 
> of different size [-Wpointer-to-int-cast]
>59 | (*env)->SetLongField(env, obj, fieldID, (jlong) (int) 
> handle);   \
>   | ^
> org_tritonus_lowlevel_pogg_Buffer.c:30:1: note: in expansion of macro 
> ‘HandleFieldHandlerDeclaration’
>30 | HandleFieldHandlerDeclaration(handler, oggpack_buffer*)
>   | ^
> org_tritonus_lowlevel_pogg_Buffer.c: In function ‘getHandle’:
> ../common/HandleFieldHandler.h:66:26: warning: cast to pointer from integer 
> of different size [-Wint-to-pointer-cast]
>66 | _type   handle = (_type) (int) (*env)->GetLongField(env, obj, 
> fieldID); \
>   |  ^
> org_tritonus_lowlevel_pogg_Buffer.c:30:1: note: in expansion of macro 
> ‘HandleFieldHandlerDeclaration’
>30 | HandleFieldHandlerDeclaration(handler, oggpack_buffer*)
>   | ^
> org_tritonus_lowlevel_pogg_Buffer.c: In function 
> ‘Java_org_tritonus_lowlevel_pogg_Buffer_readInit’:
> org_tritonus_lowlevel_pogg_Buffer.c:224:16: error: implicit declaration of 
> function ‘memcpy’ [-Werror=implicit-function-declaration]
>   224 | (void) memcpy(buffer2, buffer, nBytes);
>   |^~
> org_tritonus_lowlevel_pogg_Buffer.c:29:1: note: include ‘’ or 
> provide a declaration of ‘memcpy’
>28 | #include "org_tritonus_lowlevel_pogg_Buffer.h"
>   +++ |+#include 
>29 | 
> org_tritonus_lowlevel_pogg_Buffer.c:224:16: warning: incompatible implicit 
> declaration of built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   224 | (void) memcpy(buffer2, buffer, nBytes);
>   |^~
> org_tritonus_lowlevel_pogg_Buffer.c:224:16: note: include ‘’ or 
> provide a declaration of ‘memcpy’
> org_tritonus_lowlevel_pogg_Buffer.c: In function 
> ‘Java_org_tritonus_lowlevel_pogg_Buffer_getBuffer’:
> org_tritonus_lowlevel_pogg_Buffer.c:439:61: warning: pointer targets in 
> passing argument 5 of ‘(*env)->SetByteArrayRegion’ differ in signedness 
> [-Wpointer-sign]
>   439 | (*env)->SetByteArrayRegion(env, abBuffer, 0, bytes, buffer);
>   | ^~
>   | |
>   | unsigned 
> char *
> org_tritonus_lowlevel_pogg_Buffer.c:439:61: note: expected ‘const jbyte *’ 
> {aka ‘const signed char *’} but argument is of type ‘unsigned char *’
> cc1: some warnings being treated as errors
> make[2]: *** [: org_tritonus_lowlevel_pogg_Buffer.o] Error 1


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

All bugs filed during this archive rebuild are listed at:

Processed (with 1 error): tagging 1043127, reassign 1059415 to libntfs-3g89t64,ntfs-3g, fixed 1059415 in 1:2022.10.3-2 ...

[Debian Bug Tracking System]

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

> tags 1043127 + sid trixie
Bug #1043127 {Done: Matthias Klose } [src:creduce] creduce: 
switch to current llvm default version
Added tag(s) sid and trixie.
> reassign 1059415 libntfs-3g89t64,ntfs-3g 1:2022.10.3-1.2
Unknown command or malformed arguments to command.
> fixed 1059415 1:2022.10.3-2
Bug #1059415 {Done: Laszlo Boszormenyi (GCS) } 
[ntfs-3,libntfs-3g89t64] ntfs-3g: install files into /usr (instead of /)
Warning: Unknown package 'ntfs-3'
There is no source info for the package 'ntfs-3' at version '1:2022.10.3-2' 
with architecture ''
Ignoring request to alter fixed versions of bug #1059415 to the same values 
previously set
Warning: Unknown package 'ntfs-3'
> tags 1067915 + sid trixie
Bug #1067915 [src:veusz] Update Build-Depends for the time64 library renames
Added tag(s) trixie and sid.
> tags 1067912 + sid trixie
Bug #1067912 [src:nitrokey-app] Update Build-Depends for the time64 library 
renames
Added tag(s) sid and trixie.
> tags 1067913 + sid trixie
Bug #1067913 [src:linssid] FTBFS: error: cannot convert ‘long int*’ to ‘const 
time_t*’ {aka ‘const long long int*’}
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1066204: marked as done (kbuild: FTBFS: utils.c:107:75: error: implicit declaration of function ‘strerror’; did you mean ‘perror’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 21:12:16 +
with message-id 
and subject line Bug#1066204: fixed in kbuild 1:0.1.9998svn3589+dfsg-2
has caused the Debian Bug report #1066204,
regarding kbuild: FTBFS: utils.c:107:75: error: implicit declaration of 
function ‘strerror’; did you mean ‘perror’? 
[-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.)


-- 
1066204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kbuild
Version: 1:0.1.9998svn3589+dfsg-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 -DHAVE_CONFIG_H -I. -I/<>/src/sed/lib -I..  
> -I/<>/src/sed/lib -I/<>/src/sed/intl 
> -I/<>/src/sed -I../lib -I../intl -Wdate-time -D_FORTIFY_SOURCE=2 
>  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT 
> utils.o -MD -MP -MF .deps/utils.Tpo -c -o utils.o 
> /<>/src/sed/lib/utils.c
> /<>/src/sed/lib/utils.c: In function ‘panic’:
> /<>/src/sed/lib/utils.c:107:75: error: implicit declaration of 
> function ‘strerror’; did you mean ‘perror’? 
> [-Werror=implicit-function-declaration]
>   107 | fprintf (stderr, _("cannot remove %s: %s"), 
> open_files->name, strerror (errno));
>   |   
> ^~~~
>   |   
> perror
> In file included from /<>/src/sed/lib/utils.h:21,
>  from /<>/src/sed/lib/utils.c:42:
> /<>/src/sed/basicdefs.h:70:25: warning: format ‘%s’ expects 
> argument of type ‘char *’, but argument 4 has type ‘int’ [-Wformat=]
>70 | # define gettext(msgid) (msgid)
>   | ^~~
> /<>/src/sed/basicdefs.h:73:19: note: in expansion of macro 
> ‘gettext’
>73 | #define _(String) gettext(String)
>   |   ^~~
> /<>/src/sed/lib/utils.c:107:30: note: in expansion of macro ‘_’
>   107 | fprintf (stderr, _("cannot remove %s: %s"), 
> open_files->name, strerror (errno));
>   |  ^
> /<>/src/sed/lib/utils.c: In function ‘ck_mkstemp’:
> /<>/src/sed/lib/utils.c:200:23: error: implicit declaration of 
> function ‘strlen’ [-Werror=implicit-function-declaration]
>   200 |   template = xmalloc (strlen (tmpdir) + strlen (base) + 8);
>   |   ^~
> /<>/src/sed/lib/utils.c:76:1: note: include ‘’ or 
> provide a declaration of ‘strlen’
>75 | # include 
>   +++ |+#include 
>76 | # define VSTART(l,a)va_start(l, a)
> /<>/src/sed/lib/utils.c:200:23: warning: incompatible implicit 
> declaration of built-in function ‘strlen’ [-Wbuiltin-declaration-mismatch]
>   200 |   template = xmalloc (strlen (tmpdir) + strlen (base) + 8);
>   |   ^~
> /<>/src/sed/lib/utils.c:200:23: note: include ‘’ or 
> provide a declaration of ‘strlen’
> /<>/src/sed/lib/utils.c: In function ‘ck_strdup’:
> /<>/src/sed/lib/utils.c:401:22: warning: incompatible implicit 
> declaration of built-in function ‘strlen’ [-Wbuiltin-declaration-mismatch]
>   401 |   char *ret = MALLOC(strlen(str)+1, char);
>   |  ^~
> /<>/src/sed/basicdefs.h:123:48: note: in definition of macro 
> ‘MALLOC’
>   123 | #define MALLOC(n,t)  (VCAST(t *)ck_malloc((n)*sizeof(t)))
>   |^
> /<>/src/sed/lib/utils.c:401:22: note: include ‘’ or 
> provide a declaration of ‘strlen’
>   401 |   char *ret = MALLOC(strlen(str)+1, char);
>   |  ^~
> /<>/src/sed/basicdefs.h:123:48: note: in definition of macro 
> ‘MALLOC’
>   123 | #define MALLOC(n,t)  (VCAST(t *)ck_malloc((n)*sizeof(t)))
>   |^
> /<>/src/sed/lib/utils.c:402:10: error: implicit declaration of 
> function ‘strcpy’ [-Werror=implicit-function-declaration]
>   402 |   return strcpy(ret, str);
>   |  ^~
> /<>/src/sed/lib/utils.c:402:10: note: 

Processed: block 1036884 with 1066328

[Debian Bug Tracking System]

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

> block 1036884 with 1066328
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1067508 1067676 1067189 1067193 1067069 1067171 1055530 
1067677 1066049 1067190 1065787 1067509 1065973 1066794 1055352 1067192 1065816 
1067458 1067170 1067175 1067288 1062847
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1066328
> thanks
Stopping processing here.

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

Bug#1067921: FTBFS: error: call of overloaded ‘MSString(const time_t&)’ is ambiguous

[Andrey Rakhmatullin]

Source: aplus-fsf
Version: 4.22.1-13
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=aplus-
fsf=armhf=4.22.1-13=1711588996=0

MSTime.C: In member function ‘virtual MSString MSTime::asDebugInfo() const’:
MSTime.C:53:25: error: call of overloaded ‘MSString(const time_t&)’ is
ambiguous
   53 |   result+=MSString(_time);
  | ^
In file included from ../MSTypes/MSScalarModel.H:37,
 from ../MSTypes/MSTime.H:15,
 from MSTime.C:10:


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067829: nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]

[Thorsten Glaser]

Emanuele Rocca dixit:

>The attached patch by Vladimir Petko was sent upstream and fixes the
>FTBFS on armhf/armel.

The patch is catastrophically wrong.

+-  snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
++  snprintf(flushtime, sizeof(flushtime), "%lld\n", now);

Change that to:

++  snprintf(flushtime, sizeof(flushtime), "%lld\n", (long long)now);

time_t is not guaranteed to be 64-bit (or even integer, by ISO C),
it must always be coerced into the expected type for printf.

Please forward this upstream as well.

Might as well want to check that flushtime is large enough, too.

bye,
//mirabilos
-- 
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival

Processed: fixed 1060768 in 0.0.8.81.gaa63a79-1

[Debian Bug Tracking System]

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

> fixed 1060768 0.0.8.81.gaa63a79-1
Bug #1060768 [pdudaemon] pdudaemon: Missing dependency on python3-aiohttp
Marked as fixed in versions pdudaemon/0.0.8.81.gaa63a79-1.
> thanks
Stopping processing here.

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

Processed: tagging 1067494

[Debian Bug Tracking System]

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

> tags 1067494 + ftbfs
Bug #1067494 [obs-studio] obs-studio: FTBFS on time64_t archs
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1067920: FTBFS: error: no matching function for call to ‘max(saidx64_t&, long int)

[Andrey Rakhmatullin]

Source: phylonium
Version: 1.7-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=phylonium=armhf=1.7-2=1711651088=0

process.cxx: In lambda function:
process.cxx:222:39: error: no matching function for call to ‘max(saidx64_t&,
long int)’
  222 | this_length = std::max(inter.l, 0l);
  |   ^
In file included from /usr/include/c++/13/vector:62,
 from process.h:8,
 from process.cxx:6:
/usr/include/c++/13/bits/stl_algobase.h:257:5: note: candidate: ‘template constexpr const _Tp& std::max(const _Tp&, const _Tp&)’
  257 | max(const _Tp& __a, const _Tp& __b)
  | ^~~


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1066649: libtritonus-java: diff for NMU version 20070428-14.2

[Andrey Rakhmatullin]

Control: tags 1066649 + patch
Control: tags 1066649 + pending

Dear maintainer,

I've prepared an NMU for libtritonus-java (versioned as 20070428-14.2) and
uploaded it to unstable.

Regards.


-- 
WBR, wRAR
diff -Nru libtritonus-java-20070428/debian/changelog libtritonus-java-20070428/debian/changelog
--- libtritonus-java-20070428/debian/changelog	2020-01-27 04:28:23.0 +0500
+++ libtritonus-java-20070428/debian/changelog	2024-03-29 00:44:52.0 +0500
@@ -1,3 +1,10 @@
+libtritonus-java (20070428-14.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066649).
+
+ -- Andrey Rakhmatullin   Fri, 29 Mar 2024 00:44:52 +0500
+
 libtritonus-java (20070428-14.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libtritonus-java-20070428/debian/patches/fix-implicit-function-declaration.patch libtritonus-java-20070428/debian/patches/fix-implicit-function-declaration.patch
--- libtritonus-java-20070428/debian/patches/fix-implicit-function-declaration.patch	1970-01-01 05:00:00.0 +0500
+++ libtritonus-java-20070428/debian/patches/fix-implicit-function-declaration.patch	2024-03-29 00:44:52.0 +0500
@@ -0,0 +1,29 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin 
+Bug-Debian: https://bugs.debian.org/1066649
+Last-Update: 2024-03-28
+
+Index: libtritonus-java-20070428/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Buffer.c
+===
+--- libtritonus-java-20070428.orig/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Buffer.c
 libtritonus-java-20070428/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Buffer.c
+@@ -24,6 +24,7 @@
+ |<---this code is formatted to fit into 80 columns --->|
+ */
+ 
++#include 
+ #include "common.h"
+ #include "org_tritonus_lowlevel_pogg_Buffer.h"
+ 
+Index: libtritonus-java-20070428/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Packet.c
+===
+--- libtritonus-java-20070428.orig/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Packet.c
 libtritonus-java-20070428/src/lib/pvorbis/org_tritonus_lowlevel_pogg_Packet.c
+@@ -24,6 +24,7 @@
+ |<---this code is formatted to fit into 80 columns --->|
+ */
+ 
++#include 
+ #include "common.h"
+ #include "org_tritonus_lowlevel_pogg_Packet.h"
+ 
diff -Nru libtritonus-java-20070428/debian/patches/series libtritonus-java-20070428/debian/patches/series
--- libtritonus-java-20070428/debian/patches/series	2020-01-27 04:28:02.0 +0500
+++ libtritonus-java-20070428/debian/patches/series	2024-03-29 00:44:52.0 +0500
@@ -9,3 +9,4 @@
 java10-compatibility.diff
 bump-java-to-1.6.patch
 fluidsynth2.patch
+fix-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Processed: libtritonus-java: diff for NMU version 20070428-14.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1066649 + patch
Bug #1066649 [src:libtritonus-java] libtritonus-java: FTBFS: 
org_tritonus_lowlevel_pogg_Buffer.c:224:16: error: implicit declaration of 
function ‘memcpy’ [-Werror=implicit-function-declaration]
Added tag(s) patch.
> tags 1066649 + pending
Bug #1066649 [src:libtritonus-java] libtritonus-java: FTBFS: 
org_tritonus_lowlevel_pogg_Buffer.c:224:16: error: implicit declaration of 
function ‘memcpy’ [-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1067919: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

Source: calindori
Version: 24.02.0-1
Severity: serious
Tags: ftbfs

The package explicitly Build-Depends: libqt5*, these need to be changed to
libqt5*t64 (where applicable) if these deps are needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067918: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 6 has type ‘time_t’ {aka ‘long long int’}

[Andrey Rakhmatullin]

Source: mmsd-tng
Version: 2.6.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=mmsd-
tng=armhf=2.6.0-2=1711644612=0

In file included from ../src/mms.h:27,
 from ../src/service.c:58:
../src/service.c: In function ‘time_to_str’:
../src/log.h:24:47: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 6 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
   24 |   g_log (G_LOG_DOMAIN, G_LOG_LEVEL_DEBUG, "%s:%s() " fmt, \
  |   ^~


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067916: FTBFS: tests failed

[Andrey Rakhmatullin]

Source: capnproto
Version: 1.0.1-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=capnproto=armhf=1.0.1-3%2Bb2=1711652087=0

[ TEST ] kj/mutex-test.c++:262: legacy test: Mutex/WhenWithTimeout
kj/mutex-test.c++:321: failed: expected t >= 10 * kj::MILLISECONDS [20.039μs >=
10ms]; t = 20.039μs
stack: 74ee05 74b4a9 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f
f76797d9 f767987d
kj/mutex-test.c++:329: failed: expected t >= 20 * kj::MILLISECONDS [92.405μs >=
20ms]; t = 92.405μs
stack: 74ee05 74b525 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f
f76797d9 f767987d
kj/mutex-test.c++:373: failed: expected clock.now() - start >= 10 *
kj::MILLISECONDS [12.208μs >= 10ms]
stack: 74eacb 74b5b9 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f
f76797d9 f767987d
[ FAIL ] kj/mutex-test.c++:262: legacy test: Mutex/WhenWithTimeout (47479 μs)
[ TEST ] kj/mutex-test.c++:391: legacy test: Mutex/WhenWithTimeoutPreciseTiming
kj/mutex-test.c++:412: failed: expected t >= 100 * kj::MILLISECONDS [11.64μs >=
100ms]
stack: 74a51d f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f f76797d9
f767987d
[ FAIL ] kj/mutex-test.c++:391: legacy test: Mutex/WhenWithTimeoutPreciseTiming
(40 μs)
[ TEST ] kj/mutex-test.c++:422: legacy test:
Mutex/WhenWithTimeoutPreciseTimingAfterInterrupt
kj/mutex-test.c++:446: failed: expected t >= 100 * kj::MILLISECONDS [12.647μs
>= 100ms]; t / kj::MILLISECONDS = 0
stack: 74eca3 74a27f f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f
f76797d9 f767987d
[ FAIL ] kj/mutex-test.c++:422: legacy test:
Mutex/WhenWithTimeoutPreciseTimingAfterInterrupt (10139 μs)


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067914: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

Source: collatinus
Version: 12.2-1
Severity: serious

The package explicitly Build-Depends: libqt5printsupport5, this needs to be
changed to
libqt5printsupport5t64 if it's needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067915: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

Source: veusz
Version: 3.6.2-1
Severity: serious

The package explicitly Build-Depends: libqt5*, these need to be changed to
libqt5*t64 (where applicable) if these deps are needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1066203: marked as done (recode: FTBFS: error.c:197:43: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 19:22:15 +
with message-id 
and subject line Bug#1066203: fixed in recode 3.6-26
has caused the Debian Bug report #1066203,
regarding recode: FTBFS: error.c:197:43: error: implicit declaration of 
function ‘strcmp’ [-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.)


-- 
1066203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: recode
Version: 3.6-25
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 -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.  -Wdate-time -D_FORTIFY_SOURCE=2  
> -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> realloc.c
> error.c: In function ‘error_at_line’:
> error.c:197:43: error: implicit declaration of function ‘strcmp’ 
> [-Werror=implicit-function-declaration]
>   197 |   (file_name == old_file_name || !strcmp (old_file_name, 
> file_name)))
>   |   ^~
> error.c:51:1: note: include ‘’ or provide a declaration of ‘strcmp’
>50 | #include "error.h"
>   +++ |+#include 
>51 | 
> realloc.c:28:7: warning: conflicting types for built-in function ‘realloc’; 
> expected ‘void *(void *, long unsigned int)’ [-Wbuiltin-declaration-mismatch]
>28 | char *realloc ();
>   |   ^~~
> realloc.c:26:1: note: ‘realloc’ is declared in header ‘’
>25 | #include 
>   +++ |+#include 
>26 | 
> malloc.c:27:7: warning: conflicting types for built-in function ‘malloc’; 
> expected ‘void *(long unsigned int)’ [-Wbuiltin-declaration-mismatch]
>27 | char *malloc ();
>   |   ^~
> malloc.c:26:1: note: ‘malloc’ is declared in header ‘’
>25 | #include 
>   +++ |+#include 
>26 | 
> cc1: some warnings being treated as errors
> make[4]: *** [Makefile:172: error.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/recode_3.6-25_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: recode
Source-Version: 3.6-26
Done: Santiago Vila 

We believe that the bug you reported is fixed in the latest version of
recode, 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.
Santiago Vila  (supplier of updated recode 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, 28 Mar 2024 19:50:00 +0100
Source: recode
Architecture: source
Version: 3.6-26
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Closes: 1066203
Changes:
 recode (3.6-26) unstable; urgency=medium
 .
   * Strip -Werror=implicit-function-declaration from CFLAGS. Closes: #1066203.
Checksums-Sha1:
 84ce6c7a7e404cb6731c4234f7ab6b5f57aab120 1489 recode_3.6-26.dsc
 ad7c248d7862b19be4de0197559bfd268d4ad6fd 171024 recode_3.6-26.debian.tar.xz
 

Bug#1066203: recode: FTBFS: error.c:197:43: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration]

[Santiago Vila]

Ok, the problem was that CFLAGS now contains 
-Werror=implicit-function-declaration
by default, set by dpkg-buildflags in unstable.

The minimal fix is to drop such option, by adding this line to debian/rules:

export DEB_CFLAGS_MAINT_STRIP = -Werror=implicit-function-declaration

I'm Cc:ing Andrey Rakhmatullin, who was kind enough to look at this
and try to diagnose it.

Thanks.

Bug#1067913: FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}

[Andrey Rakhmatullin]

Source: linssid
Version: 3.6-8
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=linssid=armhf=3.6-8%2Bb2=1711139760=0

MainForm.cpp: In member function ‘void MainForm::doLogData()’:
MainForm.cpp:1296:68: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka
‘const long long int*’}
 1296 | std::strftime(nowStr, 100, "%Y/%m/%d.%H:%M:%S",
std::localtime(::now));
  |
^~
  ||
  |long
int*


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067912: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

Source: nitrokey-app
Version: 1.4.2-1
Severity: serious

The package explicitly Build-Depends: libqt5concurrent5, this needs to be
changed to libqt5concurrent5t64 if it's needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067911: FTBFS: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror]

[Andrey Rakhmatullin]

Source: zeroc-ice
Version: 3.7.10-2.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=zeroc-
ice=armhf=3.7.10-2.1=1711639887=0

arm-linux-gnueabihf-g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-
protector-strong -fstack-clash-protection -Wformat -Werror=format-security -MT
modules/IcePy/build/arm-linux-gnueabihf/shared/pic/Grammar.o -MMD -MP -MF
modules/IcePy/build/arm-linux-gnueabihf/shared/pic/Grammar.Td -Wall -Wextra
-Wshadow -Wdeprecated -Werror -pthread -DNDEBUG -Imodules/IcePy
-I../cpp/include -I../cpp/include/generated -I../cpp/src
-I/usr/include/python3.11 -I/usr/include/python3.11 -Wsign-compare -g
-Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-
protection -Wformat -Werror=format-security -DNDEBUG -g -fwrapv -O2 -Wall -Wno-
missing-field-initializers -Wno-psabi -fPIC -fvisibility=hidden
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -c ../cpp/src/Slice/Grammar.cpp -o modules/IcePy/build/arm-
linux-gnueabihf/shared/pic/Grammar.o
cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is
not valid for C++ [-Werror]
cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is
not valid for C++ [-Werror]
cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is
not valid for C++ [-Werror]
cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is
not valid for C++ [-Werror]




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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067910: Update Build-Depends for the time64 library renames

[Andrey Rakhmatullin]

Source: ifcplusplus
Version: 0~git20190402.13744d5+dfsg-3
Severity: serious

The package explicitly Build-Depends: libqt5widgets5, this needs to be changed
to
libqt5widgets5t64 if it's needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1067439: marked as done (cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 12)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 18:17:09 +
with message-id 
and subject line Bug#1067439: fixed in cpu 1.4.3-14~deb12u1
has caused the Debian Bug report #1067439,
regarding cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 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.)


-- 
1067439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: cpu
Source-Version: 1.4.3-14~deb12u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
cpu, 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.
Andreas Beckmann  (supplier of updated cpu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Mar 2024 21:37:56 +0100
Source: cpu
Architecture: source
Version: 1.4.3-14~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1067439
Changes:
 cpu (1.4.3-14~deb12u1) bookworm; urgency=medium
 .
   * QA upload.
   * Rebuild or bookworm.
 .
 cpu (1.4.3-14) unstable; urgency=medium
 .
   * QA upload.
   * Actually provide a definition of globalLdap.  (Closes: #1067439)
   * Add smoke test.
Checksums-Sha1:
 9ffe5d4a3e00fa24700fe1b874bea028d212ba8e 1883 cpu_1.4.3-14~deb12u1.dsc
 ff306c91a4d6f47d23fe29dfa1baf80b6ddbae33 29824 
cpu_1.4.3-14~deb12u1.debian.tar.xz
 3541c0886dd913475f9d9b3b54c5b2443da111c2 6099 
cpu_1.4.3-14~deb12u1_source.buildinfo
Checksums-Sha256:
 25bf7ec1cb98cca7c39fa1d7bd6aafeafcb378ca451c24436f32670c46286d92 1883 
cpu_1.4.3-14~deb12u1.dsc
 f919f872baec6081b10c6068ea531463ec705abd8a736fd8dec6b030e6567a97 29824 
cpu_1.4.3-14~deb12u1.debian.tar.xz
 4f1a478f84059df83e703e499b2a947c008bde440c5775f52de30bce3839fde9 6099 
cpu_1.4.3-14~deb12u1_source.buildinfo
Files:
 065134c5719dbd06cc7d1bbd26dc5f7c 1883 admin optional cpu_1.4.3-14~deb12u1.dsc
 49a7ef578518b11eaf60e8b3aa1ca8b0 29824 admin optional 
cpu_1.4.3-14~deb12u1.debian.tar.xz
 a3a5fd84daf5e09ae3e781d1a409fe82 6099 admin optional 
cpu_1.4.3-14~deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYB4TsQHGFuYmVAZGVi

Bug#1043058: marked as done (libesmtp6: missing Breaks: libesmtp5)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 18:17:09 +
with message-id 
and subject line Bug#1043058: fixed in libesmtp 1.1.0-3.1~deb12u1
has caused the Debian Bug report #1043058,
regarding libesmtp6: missing Breaks: libesmtp5
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.)


-- 
1043058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libesmtp6
Version: 1.1.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

This leaves a crippled libesmtp5 package installed on certain upgrade
paths.

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The libesmtp6 package has the following relationships with libesmtp5:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libesmtp5

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

3m29.5s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/lib/esmtp/sasl-cram-md5.so (from libesmtp5 package)
  debsums: missing file /usr/lib/esmtp/sasl-login.so (from libesmtp5 package)
  debsums: missing file /usr/lib/esmtp/sasl-plain.so (from libesmtp5 package)

This wasn't noticed as long as libesmtp6 still provided the files, but
that no longer seems to be the case.


cheers,

Andreas


libesmtp-dev_1.1.0-3+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libesmtp
Source-Version: 1.1.0-3.1~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated libesmtp 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, 28 Mar 2024 13:08:06 +0100
Source: libesmtp
Architecture: source
Version: 1.1.0-3.1~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Jeremy T. Bouse 
Changed-By: Andreas Beckmann 
Closes: 1043058
Changes:
 libesmtp (1.1.0-3.1~deb12u1) bookworm; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for bookworm.
 .
 libesmtp (1.1.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * libesmtp6: Add versioned Replaces and Breaks against
 libesmtp5 (<< 1.0.6-1~) (Closes: #1043058)
Checksums-Sha1:
 9fd471502589cf876a7995a72f70f378674a4e01 2002 libesmtp_1.1.0-3.1~deb12u1.dsc
 aa1963d60442be4ab9209b642fdb7596071f0fdd 4984 
libesmtp_1.1.0-3.1~deb12u1.debian.tar.xz
 ac09837e0f9b528b1e47ab6042b8fe1fca8afe93 6485 
libesmtp_1.1.0-3.1~deb12u1_source.buildinfo
Checksums-Sha256:
 bf72ed06acf88c13fc2b889128850aa6861f3f84a836219b28246a0e7a4330b2 2002 
libesmtp_1.1.0-3.1~deb12u1.dsc
 e569810f660c70cbde5bd3d1cb685f8a5a15abea38ed4a049632b9371b0e1796 4984 
libesmtp_1.1.0-3.1~deb12u1.debian.tar.xz
 8cd16464348dcd1555c1ab6013eb259c946e565c598985b1748aa1de99584aa6 6485 
libesmtp_1.1.0-3.1~deb12u1_source.buildinfo
Files:
 84ea01336884f894f367617e77192125 2002 libs optional 
libesmtp_1.1.0-3.1~deb12u1.dsc
 4fca56d432f20d0b35f9a1a7881846d4 4984 libs optional 
libesmtp_1.1.0-3.1~deb12u1.debian.tar.xz
 a653ed810d3a6e18a5411d43944c6c0a 6485 libs optional 
libesmtp_1.1.0-3.1~deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYFXgEQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCNwmEACKYkbjQ4KID6b1FONqpMyPSFkBGR9DYpgo
H7SN3Y6U5NmWsXOQjAleDfe0+kBV+iMzvTgJU8c/V1w4CpZ9HBjpX1GjSW2Tx/vZ
LK39nkYf5jp7nlwQRbqzFrdAysehrlZmhbXoosjOjKWTv5rBohqhlMHd5HJHWVgU
E4sChtdqq7pmd6Y5nuajzuGWOliolUT+j/xiixRu6Yzkxw7sHD2RX80SCqJqY9v4
dWA2S9atu9Ao3oRUEMRIyCYZDYTTFOfTu57ra+5PiNkUOavAnKEc3GB7ltbIblVI

Bug#1025655: marked as done (hovercraft: requires python3-setuptools)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 18:17:09 +
with message-id 
and subject line Bug#1025655: fixed in hovercraft 2.7-6~deb12u1
has caused the Debian Bug report #1025655,
regarding hovercraft: requires python3-setuptools
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.)


-- 
1025655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hovercraft
Version: 2.7-2
Severity: important
X-Debbugs-Cc: bms.deb...@barwap.com

Dear Maintainer,


fresh install, running hovercraft 

$ hovercraft planning_presentation.rst html 
Traceback (most recent call last):
  File "/usr/bin/hovercraft", line 33, in 
sys.exit(load_entry_point('hovercraft==2.7', 'console_scripts', 
'console_script')())
  File "/usr/bin/hovercraft", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 680, in _load_unlocked
  File "", line 790, in exec_module
  File "", line 228, in _call_with_frames_removed
  File "/usr/share/hovercraft/hovercraft/__init__.py", line 6, in 
import pkg_resources
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3243, 
in 
def _initialize_master_working_set():
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3226, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3255, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 568, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 886, in 
require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 772, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'setuptools' distribution was not found 
and is required by hovercraft


   * What outcome did you expect instead?
$ hovercraft planning_presentation.rst html

(No errors - what did happen after apt-get install python3-setuptools)



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

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

Versions of packages hovercraft depends on:
ii  libjs-impress  1.0.0-1
ii  libjs-sphinxdoc3.4.3-2
ii  python33.9.2-3
ii  python3-docutils   0.16+dfsg-4
ii  python3-lxml   4.6.3+dfsg-0.1+deb11u1
ii  python3-pkg-resources  52.0.0-4
ii  python3-pygments   2.7.1+dfsg-2.1
ii  python3-svg.path   3.0-2
ii  python3-watchdog   1.0.2-2

hovercraft recommends no packages.

hovercraft suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: hovercraft
Source-Version: 2.7-6~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated hovercraft package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 25 Mar 2024 21:54:54 +0100
Source: hovercraft
Architecture: source
Version: 2.7-6~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1025655
Changes:
 

Bug#1067906: qtwebengine-opensource-src - FTBFS on armhf.

[Peter Green]

Package: qtwebengine-opensource-src
Version: 5.15.15+dfsg-2
Severity: serious

qtwebengine-opensource-src failed to build on armhf when binnmu'd for the time_t
transition due to symbol changes.
(qtwebengine does not support any of the other architectures affected by
the time64 transition.

grep MISSING qtwebengine-opensource-src.log | grep -v optional
+#MISSING: 5.15.15+dfsg-2+b3# 
_ZN15QtWebEngineCore14ProfileAdapter21determineDownloadPathERK7QStringS3_RKl@Qt_5
 5.14.1
+#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox18localtime_overrideEPKl@Qt_5 5.12.2
+#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox20localtime64_overrideEPKl@Qt_5 5.12.2
+#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox20localtime_r_overrideEPKlP2tm@Qt_5 
5.12.2
+#MISSING: 5.15.15+dfsg-2+b3# _ZN7sandbox22localtime64_r_overrideEPKlP2tm@Qt_5 
5.12.2

Bug#1067669: marked as done (FTBFS on 32-bit: test possible_underflow ... FAILED)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 17:53:15 +
with message-id 
and subject line Bug#1067669: fixed in rust-uutils-term-grid 0.6.0-2
has caused the Debian Bug report #1067669,
regarding FTBFS on 32-bit: test possible_underflow ... FAILED
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.)


-- 
1067669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-uutils-term-grid
Version: 0.6.0-1
Severity: serious
Tags: ftbfs

test uutils_ls::columns_width_30 ... ok
test possible_underflow ... FAILED

failures:

 possible_underflow stdout 
thread 'possible_underflow' panicked at 'attempt to multiply with overflow',
/usr/src/rustc-1.70.0/library/core/src/num/mod.rs:371:5


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: rust-uutils-term-grid
Source-Version: 0.6.0-2
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-uutils-term-grid, 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.
Peter Michael Green  (supplier of updated 
rust-uutils-term-grid 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, 28 Mar 2024 17:17:03 +
Source: rust-uutils-term-grid
Architecture: source
Version: 0.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1067669
Changes:
 rust-uutils-term-grid (0.6.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Package uutils_term_grid 0.6.0 from crates.io using debcargo 2.6.1
   * Fix tests on 32-bit architectures (Closes: #1067669)
Checksums-Sha1:
 0e7da64690a221d5d9c624bf0987baa36e1eea15 2292 rust-uutils-term-grid_0.6.0-2.dsc
 fc2ecdff301f601b90408de3e564110b430102bb 2964 
rust-uutils-term-grid_0.6.0-2.debian.tar.xz
 cb4fd4c99ea4396b2e2522ea1ab31f19f5131763 7790 
rust-uutils-term-grid_0.6.0-2_source.buildinfo
Checksums-Sha256:
 adb1e5dfef55c8215e4feb33e8666bab4fb3dab578e872270589d3d8136006d2 2292 
rust-uutils-term-grid_0.6.0-2.dsc
 a4aaba76294a3c4caa26c930e4e501f5ffdc44cd3cf397386e27c7712a60563b 2964 
rust-uutils-term-grid_0.6.0-2.debian.tar.xz
 0880a34be1bd840a2051b4aefd31074a33ffeb80c385d4c15daa23db0e64 7790 
rust-uutils-term-grid_0.6.0-2_source.buildinfo
Files:
 7a5526bb0dba618d789ce6892347aa57 2292 rust optional 
rust-uutils-term-grid_0.6.0-2.dsc
 d9a0ba3935d2db63ca8107a9abf9305b 2964 rust optional 
rust-uutils-term-grid_0.6.0-2.debian.tar.xz
 2c2ded1f4ddd59079a1c27d4bdefb173 7790 rust optional 
rust-uutils-term-grid_0.6.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmYFpsgUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsdmQ//SfKDsIO0nj0f2vR9+5qbNtTK2Ith
9s1BWNvdueJKXpBXzUgJ9Lh92Ml2dLAcbK5r3qUFZwQT0bgvVjcINYf8Y9Ey6KUx
uneAy0Tz05IU+6tZNjbr0rQmZyMci4Uqilu5LeCbAM7bJdXseil7fdjBSuVHSxtZ
yAUAP8HHqmDibWXyQ81XwZP/XC/J1IN3nzHMilo/YpUfvlv5PYHzTWkpizB5X3KF
DFYtMgGh6w8GJryKt212odeI+TquWv1gHlfRyiUkx9ONoeHuXXAu14BMrWLhQ1+2
oQktnX5oFY25HY25DrXYUMH6lY2sxlyoBf9jaPfFvKX36g98zy688ynWNXQT3FiA
UBdlyRpoGQY8y6UoPQcBF56ISB0ZK4zTCdGEVflw6mHWIfxKJhaAyEwE7z7+3cmd
M854TVznciika2aDC2SRX0kRVrJy52tI2NUGxlL584rkiKWosaGweYSPgHvRsJfF
Ao/eSNTPWuudoPNPmOGrelubASq5l/pikY6enBjeT8VX5Nk/1f36Bd6j2oLoTPdH
adwUpSsZ8X8vGDIAQuHWQMn73AxYAznU/3e09AvtGtg3J7TobeATN5QOdi9N2Sx4
FxDHBaMuiG9y+iPIRF5/Gn26bZASIAEel1fBiG0mhwG3Rfr008tu/6y+cMaA3eHm
YWIA04ZWxyQv8sU=
=l7V6
-END PGP SIGNATURE-



pgpaHMIgmTBcU.pgp
Description: PGP signature
--- End 

Bug#1063431: marked as done (src:r-cran-future.apply: fails to migrate to testing for too long: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 17:52:49 +
with message-id 
and subject line Bug#1063431: fixed in r-cran-future.apply 1.11.2+dfsg-1
has caused the Debian Bug report #1063431,
regarding src:r-cran-future.apply: fails to migrate to testing for too long: 
autopkgtest failure
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.)


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

Source: r-cran-future.apply
Version: 1.11.0+dfsg-1
Severity: serious
Control: close -1 1.11.1+dfsg-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-future.apply has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug. The version in 
unstable fails its own autopkgtest on armel, armhf and i386 (our 32 bits 
architectures).


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


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


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


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


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-future.apply
Source-Version: 1.11.2+dfsg-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
r-cran-future.apply, 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.
Andreas Tille  (supplier of updated r-cran-future.apply 
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, 28 Mar 2024 17:35:21 +0100
Source: r-cran-future.apply
Architecture: source
Version: 1.11.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1063431
Changes:
 r-cran-future.apply (1.11.2+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #1063431
Checksums-Sha1:
 b1253bc506a68b81edb4fbdbe611496c7f5acef2 2286 
r-cran-future.apply_1.11.2+dfsg-1.dsc
 1ad1c4a6daa56c790ef2e590bac49c8b42ed1524 46480 
r-cran-future.apply_1.11.2+dfsg.orig.tar.xz
 db620b1d75a319e9422cc8886737dab9c7651426 2892 
r-cran-future.apply_1.11.2+dfsg-1.debian.tar.xz
 60ed00b79a65327f554d76e6c9c0b8f8ed6ee435 24027 
r-cran-future.apply_1.11.2+dfsg-1_source.buildinfo
Checksums-Sha256:
 2626fc43779653576e5fe9191c6fca3dc9c580986141f1d2e4f764cae0d040fd 2286 
r-cran-future.apply_1.11.2+dfsg-1.dsc
 fe4f7144a2a7b7ee265b7a225c62b8454a0231c1458f3ee57b6c758f21796e80 46480 
r-cran-future.apply_1.11.2+dfsg.orig.tar.xz
 c2fde53f326c82e526c66bc4df35a30dc945e4c158c05cc320987acb53b97d0e 2892 
r-cran-future.apply_1.11.2+dfsg-1.debian.tar.xz
 da212603e00a712f403ed93eac5d8116fef11820a59c6490d788e1bf7cf08be2 24027 
r-cran-future.apply_1.11.2+dfsg-1_source.buildinfo
Files:
 fdf0ea831e6963372cfbebf90da469c5 2286 gnu-r optional 
r-cran-future.apply_1.11.2+dfsg-1.dsc
 8399b45bdb3b54c4c439b4e6ed742281 46480 

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Daniel Swarbrick]

On 28.03.24 15:00, Santiago Vila wrote:

Daniel Swarbrick  wrote:

* Add new 0022-Support-prometheus-common-0.47.0.patch (Closes: #1064765)


Hello. I don't quite understand how the above fix is related to
the bug itself (but maybe it's because I don't know prometheus internals).


As described in the patch:

This cherry-picks part of a commit relating to negotiation of the
"Accept" header, which became more complex with prometheus/common
0.47.0. See upstream commit a28d786.

This resolved the original FTBFS for which this bug was opened, as far 
as I could see, which was this test failure:


> === RUN   TestFederationWithNativeHistograms
> federate_test.go:417:
> 	Error Trace: 
/<>/.build/src/github.com/prometheus/prometheus/web/federate_test.go:417

>Error:  Not equal:
>expected: 4
>actual  : 1
>Test:   TestFederationWithNativeHistograms
> --- FAIL: TestFederationWithNativeHistograms (0.01s)

I was able to reliably reproduce that failure by rolling forward / back 
the prometheus/common dependency in go.mod on a local git clone.



In either case, this is still happening for me in the current version:

Lucas Nussbaum  wrote:

   FAILED:
1:48: parse error: unexpected character inside braces: '0'


This sounds like a _new_ bug.


Note: I'm currently using virtual machines with 1 CPU and with 2 CPUs
for archive rebuilds. On systems with 2 CPUs, the package FTBFS randomly.
On systems with 1 CPU, the package FTBFS always.

Therefore, to reproduce, please try GRUB_CMDLINE_LINUX="nr_cpus=1"
in /etc/default/grub first.


I'm struggling to see how a different number of CPU cores would elicit 
the aforementioned new bug. It doesn't seem to have the typical 
characteristics of a race condition. I'll have to try to find some time 
to setup a VM and try to reproduce it.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed (with 5 errors): Re: Bug#1051496: mailgraph: does not support the new syslog format

[Debian Bug Tracking System]

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

> severity 1051496 normal
Bug #1051496 [mailgraph] mailgraph: does not support the new syslog format
Severity set to 'normal' from 'grave'
> tags 1051496 + moreinfo
Bug #1051496 [mailgraph] mailgraph: does not support the new syslog format
Added tag(s) moreinfo.
> Hello Michael,
Unknown command or malformed arguments to command.
> thank you for spending your time helping to make Debian better with this bug
Unknown command or malformed arguments to command.
> report.
Unknown command or malformed arguments to command.
> We are using mailgraph one multiple server with Debian Bullseye, Bookworm and
Unknown command or malformed arguments to command.
> Trixie without any failure.
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#1067054: Debian 12 - Copy files on USB 3

[pham...@bluewin.ch]

After further testing, the crash issue when copying multiple files (total 
volume 150 GB) or a disk image (250 GB) is present when an SSD is formatted in 
GPT format. 
This works without problem if the SSD is formatted in MBR/MS-DOS.
Regards.

Bug#1067829: nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]

[Emanuele Rocca]

Control: tags -1 + patch

Hi,

On 2024-03-27 11:02, Sebastian Ramacher wrote:
> export-cache.c: In function ‘junction_flush_exports_cache’:
> export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long 
> int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
>   110 | snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
>   | ~~^ ~~~
>   |   | |
>   |   | time_t {aka 
> long long int}
>   |   long int
>   | %lld

The attached patch by Vladimir Petko was sent upstream and fixes the
FTBFS on armhf/armel.

  Emanuele
diff -Nru nfs-utils-2.6.4/debian/changelog nfs-utils-2.6.4/debian/changelog
--- nfs-utils-2.6.4/debian/changelog	2023-12-03 14:58:30.0 +0100
+++ nfs-utils-2.6.4/debian/changelog	2024-03-28 16:56:19.0 +0100
@@ -1,3 +1,10 @@
+nfs-utils (1:2.6.4-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply upstream patch to fix FTBFS on armhf/armel (Closes: #1067829) 
+
+ -- Emanuele Rocca   Thu, 28 Mar 2024 16:56:19 +0100
+
 nfs-utils (1:2.6.4-3) unstable; urgency=medium
 
   [ Salvatore Bonaccorso ]
diff -Nru nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch
--- nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch	1970-01-01 01:00:00.0 +0100
+++ nfs-utils-2.6.4/debian/patches/flushtime-long-long-int.patch	2024-03-28 16:56:19.0 +0100
@@ -0,0 +1,17 @@
+Author: Vladimir Petko
+Origin: https://bugzilla.kernel.org/show_bug.cgi?id=218540
+Bug-Debian: https://bugs.debian.org/1067829
+
+Index: nfs-utils-2.6.4/support/junction/export-cache.c
+===
+--- nfs-utils-2.6.4.orig/support/junction/export-cache.c
 nfs-utils-2.6.4/support/junction/export-cache.c
+@@ -107,7 +107,7 @@ junction_flush_exports_cache(void)
+ 		xlog(D_GENERAL, "%s: time(3) failed", __func__);
+ 		return FEDFS_ERR_SVRFAULT;
+ 	}
+-	snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
++	snprintf(flushtime, sizeof(flushtime), "%lld\n", now);
+ 
+ 	for (i = 0; junction_proc_files[i] != NULL; i++) {
+ 		retval = junction_write_time(junction_proc_files[i], flushtime);
diff -Nru nfs-utils-2.6.4/debian/patches/series nfs-utils-2.6.4/debian/patches/series
--- nfs-utils-2.6.4/debian/patches/series	2023-12-03 14:58:30.0 +0100
+++ nfs-utils-2.6.4/debian/patches/series	2024-03-28 16:56:19.0 +0100
@@ -1,3 +1,4 @@
 multiarch-kerberos-paths.patch
 always-run-generator.patch
 fsidd-call-anonymous-sockets-by-their-name-only-don-.patch
+flushtime-long-long-int.patch

Processed: Re: Bug#1067829: nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Wer

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}: 
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, 
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Added tag(s) patch.

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

Bug#1067293: singular: FTBFS: cfModGcd.cc:1809:37: error: cannot convert ‘fq_nmod_ctx_struct*’ to ‘const fq_nmod_mat_struct*’

[Jerome BENOIT]

Hello Lucas, thanks for the report.
The issue appeared to be fixed in version 4.3.2-p16.
I am on my way to bring this new version to experimental.
Best wishes, Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1067898: atril, dependencies unsatisfiable on 32-bit non-i386 architectures.

[Peter Green]

Package: atril
Version: 1.26.2-2
Severity: serious

The latest version of atril depends on both libatrildocument3 and
libatrildocument3t64. As a result it is uninstallable on
architectures that are undergoing the time64 transition
(armel, armhf and some debian-ports archictures).

Bug#1067897: rust-coreutils - FTBFS with new rust-uutils-term-grid.

[Peter Green]

Package: rust-coreutils
Version: 0.0.24-2
Severity: serious

rust-coreutils FTBFS with the new version of rust-uutils-term-grid.
The Debian build-dependency allows the new version, but the Cargo
dependency does not.

After bumping the cargo dependency, the code fails to build with a
bunch of errors.


error[E0432]: unresolved import `term_grid::Cell`
  --> src/uu/ls/src/ls.rs:37:17
   |
37 | use term_grid::{Cell, Direction, Filling, Grid, GridOptions};
   |  no `Cell` in the root
   |
   = help: consider importing one of these items instead:
   std::cell::Cell
   core::cell::Cell
error[E0063]: missing field `width` in initializer of `GridOptions`
--> src/uu/ls/src/ls.rs:2598:34
 |
2598 | let mut grid = Grid::new(GridOptions { filling, direction });
 |  ^^^ missing `width`

error[E0061]: this function takes 2 arguments but 1 argument was supplied
--> src/uu/ls/src/ls.rs:2598:24
 |
2598 | let mut grid = Grid::new(GridOptions { filling, direction });
 |^ -- an 
argument of type `Vec<_>` is missing
error[E0599]: no method named `add` found for struct `Grid` in the current scope
--> src/uu/ls/src/ls.rs:2609:18
 |
2609 | grid.add(formatted_name);
 |  ^^^ method not found in `Grid<_>`

error[E0599]: no method named `fit_into_width` found for struct `Grid` in the 
current scope
--> src/uu/ls/src/ls.rs:2612:20
 |
2612 | match grid.fit_into_width(width as usize) {
 |^^ method not found in `Grid<_>`

error[E0599]: no method named `fit_into_columns` found for struct `Grid` in the 
current scope
--> src/uu/ls/src/ls.rs:2618:40
 |
2618 | write!(out, "{}", grid.fit_into_columns(1))?;
 | method not found in 
`Grid<_>`

Processed: severity is normal

[Debian Bug Tracking System]

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

> severity 1066983 normal
Bug #1066983 {Done: Markus Koschany } [monopd] monopd: Fails 
to start monopd.service
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: bug 1067829 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=218540

[Debian Bug Tracking System]

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

> forwarded 1067829 https://bugzilla.kernel.org/show_bug.cgi?id=218540
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}: 
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, 
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=218540'.
> thanks
Stopping processing here.

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

Processed: Bug#1066525 marked as pending in mlv-smile

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066525 [src:mlv-smile] mlv-smile: FTBFS: src/allocateurs.c:45:39: error: 
implicit declaration of function ‘getpagesize’ 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066525: marked as pending in mlv-smile

[Lance Lin]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/mlv-smile/-/commit/6b710a1d21459678e69c79747b21f3eb6e4fbe63


d/patches: Replace getpagesize with sysconf (Closes: #1066525)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066525

Bug#1067776: marked as done (openrc: move files to /usr (DEP17) and revert unnecessary time64 transition)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 15:00:12 +
with message-id 
and subject line Bug#1067776: fixed in openrc 0.53-2
has caused the Debian Bug report #1067776,
regarding openrc: move files to /usr (DEP17) and revert unnecessary time64 
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.)


-- 
1067776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openrc,libeinfo1,libeinfo1t64,librc1t64
Version: 0.53-1.1
Severity: serious
Tags: patch
User: helm...@debian.org
Usertags: dep17p1 dep17m2
Control: affects -1 librc1

Hi,

I am sending you a patch for moving files to /usr for DEP17, because
doing so requires mitigations due to time64 having renamed libraries. In
particular, I verified that libeinfo did not actually break ABI.
Therefore, I am proposing to revert the time64 transition for libeinfo.
As a consequence of the reversion, we need fewer /usr-move mitigations.
We still need the mitigation for librc though. I have set the severity
of this bug to serious to prevent libeinfo1t64 from migrating to trixie.
It should either be reverted before migration or it should not be
reverted. If you disagree with the reversion, please lower the severity
of this bug and I'll send a patch that extends the mitigation to
libeinfo. That said, fewer library renames make upgrades less painful.

I've tested the patch using piuparts and with a manual test case
precisely triggering the DEP17 P1 file loss scenario:

mmdebstrap trixie /dev/null --variant=apt --include librc-dev 
--customize-hook='echo "deb http://deb.debian.org/debian sid main" > 
"$1/etc/apt/sources.list.d/sid.list"' --chrooted-customize-hook="apt-get 
update" --customize-hook="upload librc1t64_0.53-1.2_amd64.deb /l.deb" 
--customize-hook="upload librc-dev_0.53-1.2_amd64.deb /d.deb" 
--chrooted-customize-hook="dpkg --auto-deconfigure --unpack /l.deb /d.deb; 
apt-get -y install /l.deb /d.deb" --chrooted-customize-hook="dpkg --verify"

Do note that this patch must not be backported to bookworm-backports or
earlier. If you intend to backport, you must revert both this patch and
the time64 transition for your backport.

I recommend uploading this sooner rather than later, because the
reversion helps people who have not yet upgraded libeinfo to unstable.

Helmut
diff -Nru openrc-0.53/debian/changelog openrc-0.53/debian/changelog
--- openrc-0.53/debian/changelog2024-02-29 13:48:11.0 +0100
+++ openrc-0.53/debian/changelog2024-03-26 15:56:35.0 +0100
@@ -1,3 +1,11 @@
+openrc (0.53-1.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Revert unnecessary time64 transition for libeinfo
+  * Move files to /usr and mitigate file loss (DEP17) (Closes: #-1).
+
+ -- Helmut Grohne   Tue, 26 Mar 2024 15:56:35 +0100
+
 openrc (0.53-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru openrc-0.53/debian/control openrc-0.53/debian/control
--- openrc-0.53/debian/control  2024-02-29 13:48:11.0 +0100
+++ openrc-0.53/debian/control  2024-03-26 15:56:35.0 +0100
@@ -47,7 +47,7 @@
 Package: librc1t64
 Provides: ${t64:Provides}
 Replaces: librc1
-Breaks: librc1 (<< ${source:Version})
+Conflicts: librc1 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${misc:Depends},
@@ -84,10 +84,10 @@
  .
  This package provides development files for the runtime library.
 
-Package: libeinfo1t64
-Provides: ${t64:Provides}
-Replaces: libeinfo1
-Breaks: libeinfo1 (<< ${source:Version})
+Package: libeinfo1
+Provides: libeinfo1t64
+Replaces: libeinfo1t64
+Breaks: libeinfo1t64 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${misc:Depends},
@@ -110,7 +110,7 @@
 Package: libeinfo-dev
 Architecture: any
 Section: libdevel
-Depends: libeinfo1t64 (=${binary:Version}),
+Depends: libeinfo1 (=${binary:Version}),
  ${misc:Depends},
 Multi-Arch: same
 Description: dependency based service manager (pretty console display 
development)
diff -Nru openrc-0.53/debian/libeinfo-dev.links 
openrc-0.53/debian/libeinfo-dev.links
--- openrc-0.53/debian/libeinfo-dev.links   2024-01-22 18:18:38.0 
+0100
+++ openrc-0.53/debian/libeinfo-dev.links   2024-03-26 15:56:35.0 
+0100
@@ -1,3 +1,3 @@
 #! /usr/bin/dh-exec
 
-lib/${DEB_HOST_MULTIARCH}/libeinfo.so.1 
usr/lib/${DEB_HOST_MULTIARCH}/libeinfo.so
+usr/lib/${DEB_HOST_MULTIARCH}/libeinfo.so.1 
usr/lib/${DEB_HOST_MULTIARCH}/libeinfo.so
diff -Nru openrc-0.53/debian/libeinfo1.install 
openrc-0.53/debian/libeinfo1.install
--- 

Bug#1067363: marked as done (polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.1

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 15:00:10 +
with message-id 
and subject line Bug#1067226: fixed in flint 3.1.2-1~exp1
has caused the Debian Bug report #1067226,
regarding polymake: FTBFS: dpkg-shlibdeps: error: no dependency information 
found for /lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
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.)


-- 
1067226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: polymake
Version: 4.11-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):
> make[1]: Entering directory '/<>'
> dh_perl usr/lib/polymake/perlx
> make[1]: Leaving directory '/<>'
>dh_link -O--max-parallel=8
>dh_strip_nondeterminism -O--max-parallel=8
>dh_compress -O--max-parallel=8
>dh_fixperms -O--max-parallel=8
>dh_missing -O--max-parallel=8
>dh_strip -O--max-parallel=8
>dh_makeshlibs -O--max-parallel=8
>dh_shlibdeps -O--max-parallel=8
> dpkg-shlibdeps: error: no dependency information found for 
> /lib/x86_64-linux-gnu/libflint.so.19 (used by 
> debian/polymake/usr/lib/polymake/lib/matroid.so)
> Hint: check if the library actually comes from a package.
> dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/polymake.substvars 
> debian/polymake/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so
>  debian/polymake/usr/lib/polymake/lib/ideal.so 
> debian/polymake/usr/lib/polymake/lib/topaz.so 
> debian/polymake/usr/lib/polymake/lib/tropical.so 
> debian/polymake/usr/lib/polymake/lib/polytope.so 
> debian/polymake/usr/lib/polymake/lib/group.so 
> debian/polymake/usr/lib/polymake/lib/fan.so 
> debian/polymake/usr/lib/polymake/lib/graph.so 
> debian/polymake/usr/lib/polymake/lib/matroid.so 
> debian/polymake/usr/lib/polymake/lib/fulton.so 
> debian/polymake/usr/lib/polymake/lib/common.so returned exit code 25
> dpkg-shlibdeps: error: no dependency information found for 
> /lib/x86_64-linux-gnu/libflint.so.19 (used by 
> debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
> Hint: check if the library actually comes from a package.
> dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/libpolymake4.11.substvars 
> debian/libpolymake4.11/usr/lib/libpolymake.so.4.11 
> debian/libpolymake4.11/usr/lib/polymake/lib/libpolymake-apps-rt.so.4.11 
> debian/libpolymake4.11/usr/lib/polymake/lib/libpolymake-apps.so.4.11 returned 
> exit code 25
> dh_shlibdeps: error: Aborting due to earlier error
> make: *** [debian/rules:35: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/polymake_4.11-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 ---
Source: flint
Source-Version: 3.1.2-1~exp1
Done: Doug Torrance 

We believe that the bug you reported is fixed in the latest version of
flint, 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.
Doug Torrance  (supplier of updated flint 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, 26 Mar 2024 13:30:18 -0400
Source: flint
Binary: libflint-dev libflint-doc libflint19 libflint19-dbgsym
Architecture: source amd64 all
Version: 

Bug#1067226: marked as done (flint: libflint needs soversion bump to 19)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 15:00:10 +
with message-id 
and subject line Bug#1067226: fixed in flint 3.1.2-1~exp1
has caused the Debian Bug report #1067226,
regarding flint: libflint needs soversion bump to 19
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.)


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

Source: flint
X-Debbugs-Cc: dtorra...@piedmont.edu
Version: 3.1.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The binary package libflint18t64 ships libflint.so.19, so it should be
renamed to libflint19 and there should be a transition.  This is causing
a number of issues:

* Several Lintian warnings and errors:
 - mismatched-override
 - package-name-doesnt-match-sonames
 - shared-library-not-shipped
 - ships-undeclared-shared-library

* The normaliz autopkgtests are failing, e.g., [1]:
 /usr/bin/normaliz: error while loading shared libraries: libflint.so.18: 
cannot open shared object file: No such file or directory

* The macaulay2 builds are failing, e.g. [2]:
 checking whether the package normaliz is installed... /usr/bin/normaliz
 normaliz: error while loading shared libraries: libflint.so.18: cannot open 
shared object file: No such file or directory

[1] https://ci.debian.net/packages/n/normaliz/testing/amd64/44097859/
[2] 
https://buildd.debian.org/status/fetch.php?pkg=macaulay2=all=1.23%2Bds-1=1710934109=0



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: flint
Source-Version: 3.1.2-1~exp1
Done: Doug Torrance 

We believe that the bug you reported is fixed in the latest version of
flint, 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.
Doug Torrance  (supplier of updated flint 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, 26 Mar 2024 13:30:18 -0400
Source: flint
Binary: libflint-dev libflint-doc libflint19 libflint19-dbgsym
Architecture: source amd64 all
Version: 3.1.2-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Doug Torrance 
Description:
 libflint-dev - C library for number theory, development files
 libflint-doc - Documentation for the FLINT library
 libflint19 - C library for number theory, shared library
Closes: 1067226
Changes:
 flint (3.1.2-1~exp1) experimental; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * debian/control
 - Rename libflint18t64 -> libflint19 (Closes: #1067226).
 - Add Breaks/Replaces for libflint18t64, but only for version 3.1.0 or
   greater, where soversion 19 first appeared.
   * debian/libflint19.install
 - Rename from libflint18t64.install
   * debian/libflint18t64.lintian-overrides
 - Remove file; no longer necessary now that the package name matches
   the soname.
   * debian/libflint18t64.shlibs
 - Remove file; generated automatically by debhelper.
Checksums-Sha1:
 5483a1039898e9885330771e0fb73636e8d6a787 2240 flint_3.1.2-1~exp1.dsc
 b3e5d8a24710f23d8445b28f3414d9414fc2e8ca 7585361 flint_3.1.2.orig.tar.gz
 a513895e084255e8d186053b4e6de91a403308c7 8748 flint_3.1.2-1~exp1.debian.tar.xz
 41f569f88d4144050e9613d3acb768dfe66fdc0e 10682 
flint_3.1.2-1~exp1_amd64.buildinfo
 ded0e4f92405f864682ec58b575c6f8e86015fcd 221804 
libflint-dev_3.1.2-1~exp1_amd64.deb
 387f0119236460692889e909056163ad02369d27 7490332 
libflint-doc_3.1.2-1~exp1_all.deb
 fc03237a4231c2b2270e20238d3b9addf29d0efe 13933484 
libflint19-dbgsym_3.1.2-1~exp1_amd64.deb
 e98f0feb6195e01359e10bf79cb40042f0278f22 3779924 
libflint19_3.1.2-1~exp1_amd64.deb
Checksums-Sha256:
 59998279c13475a87a6295c2cabb9a2099da1e1cfd894bcfd586554799e4bf5d 2240 
flint_3.1.2-1~exp1.dsc
 b701d9f1ec9258944d0b8702bc77981637dc80f01dc3530fd86d6b6b75fbec63 7585361 
flint_3.1.2.orig.tar.gz
 b1e9d9c2167ef6b8ea8c08589ffe3fea05134c8f106214db5a04a3caaaef9536 8748 
flint_3.1.2-1~exp1.debian.tar.xz
 ffce6137559fee45bb051fc49831dcfac835cc0593238c150b2651e18a1552e2 10682 
flint_3.1.2-1~exp1_amd64.buildinfo
 

Bug#1066479: marked as done (opendnssec: FTBFS: ../../common/scheduler/task.c:137:25: error: implicit declaration of function ‘clamp’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 14:43:58 +
with message-id 
and subject line Bug#1066479: fixed in opendnssec 1:2.1.13-1.1
has caused the Debian Bug report #1066479,
regarding opendnssec: FTBFS: ../../common/scheduler/task.c:137:25: error: 
implicit declaration of function ‘clamp’ [-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.)


-- 
1066479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opendnssec
Version: 1:2.1.13-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 -DHAVE_CONFIG_H -I. -I../../common  -I/usr/include -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wall -pedantic -DSQLITE3_SONAME=\"libsqlite3.so.0\" -pedantic -rdynamic -c 
> -o scheduler/worker.o ../../common/scheduler/worker.c
> ../../common/cmdhandler.c: In function ‘cmdhandler_accept_client’:
> ../../common/cmdhandler.c:386:9: warning: unused variable ‘err’ 
> [-Wunused-variable]
>   386 | int err;
>   | ^~~
> ../../common/cmdhandler.c: In function ‘cmdhandler_start’:
> ../../common/cmdhandler.c:509:13: warning: unused variable ‘i’ 
> [-Wunused-variable]
>   509 | ssize_t i;
>   | ^
> ../../common/cmdhandler.c: In function ‘self_pipe_trick’:
> ../../common/cmdhandler.c:596:35: warning: zero-length gnu_printf format 
> string [-Wformat-zero-length]
>   596 | client_printf(sockfd, "");
>   |   ^~
> ../../common/cmdhandler.c: In function ‘cmdhandler_perform_command’:
> ../../common/cmdhandler.c:173:13: warning: ignoring return value of 
> ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   173 | asprintf(, "unknown generic arguments");
>   | ^
> ../../common/cmdhandler.c:202:17: warning: ignoring return value of 
> ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   202 | asprintf(, "memory error");
>   | ^~~~
> ../../common/cmdhandler.c:209:21: warning: ignoring return value of 
> ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   209 | asprintf(, "Error parsing arguments %s 
> command line %s", command->name, arg);
>   | 
> ^~
> ../../common/cmdhandler.c:232:25: warning: ignoring return value of 
> ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   232 | asprintf(, "no help for command  
> %s.", arg);
>   | 
> ^
> ../../common/cmdhandler.c:246:13: warning: ignoring return value of 
> ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   246 | asprintf(, "Unknown command %s.", arg);
>   | ^~~~
> ../../common/scheduler/schedule.c: In function ‘schedule_get_first_task’:
> ../../common/scheduler/schedule.c:81:20: warning: unused variable ‘node’ 
> [-Wunused-variable]
>81 | ldns_rbnode_t* node = LDNS_RBTREE_NULL;
>   |^~~~
> ../../common/scheduler/task.c: In function ‘task_perform’:
> ../../common/scheduler/task.c:137:25: error: implicit declaration of function 
> ‘clamp’ [-Werror=implicit-function-declaration]
>   137 | task->backoff = clamp(task->backoff * 2, 60, 
> ODS_SE_MAX_BACKOFF);
>   | ^
> cc1: some warnings being treated as errors
> make[4]: *** [Makefile:601: scheduler/task.o] Error 1


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

All bugs filed during this archive rebuild are listed at:

Bug#1061229: marked as done (numpydoc: Failing autopkgtest)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 14:43:47 +
with message-id 
and subject line Bug#1061229: fixed in numpydoc 1.6.0-2
has caused the Debian Bug report #1061229,
regarding numpydoc: Failing autopkgtest
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.)


-- 
1061229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numpydoc
Version: 1.6.0-1
Severity: serious
Tags: patch
X-Debbugs-CC: marmochia...@gmail.com

numpydoc's autopkgtest is failing. Matthias added a path to Ubuntu to
mark it as expected fail, but without further explanation. I am
attaching a version of his patch.

Thank you,
Jeremy Bícha
From f2558e7fc77f69ed00e8c1095c4b23cd3535a4d6 Mon Sep 17 00:00:00 2001
From: Matthias Klose 
Date: Sun, 14 Jan 2024 08:07:16 +0100
Subject: [PATCH] Add patch to mark one test as expected fail

---
 debian/patches/series   |  1 +
 debian/patches/xfail-one-test.patch | 21 +
 2 files changed, 22 insertions(+)
 create mode 100644 debian/patches/xfail-one-test.patch

diff --git a/debian/patches/series b/debian/patches/series
index 0a5f0c1..44ddc34 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 validateconstant.patch
 Use-system-inventory.patch
+xfail-one-test.patch
diff --git a/debian/patches/xfail-one-test.patch b/debian/patches/xfail-one-test.patch
new file mode 100644
index 000..f1b5ae8
--- /dev/null
+++ b/debian/patches/xfail-one-test.patch
@@ -0,0 +1,21 @@
+From: Matthias Klose 
+Date: Sun, 14 Jan 2024 08:07:16 +0100
+Subject: xfail-one-test
+
+---
+ numpydoc/tests/test_validate.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/numpydoc/tests/test_validate.py b/numpydoc/tests/test_validate.py
+index 68040ad..fdb395b 100644
+--- a/numpydoc/tests/test_validate.py
 b/numpydoc/tests/test_validate.py
+@@ -1470,7 +1470,7 @@ class TestValidator:
+ marks=pytest.mark.xfail,
+ ),
+ # Returns tests
+-("BadReturns", "return_not_documented", ("No Returns section found",)),
++pytest.param("BadReturns", "return_not_documented", ("No Returns section found",), marks=pytest.mark.xfail),
+ ("BadReturns", "yield_not_documented", ("No Yields section found",)),
+ pytest.param("BadReturns", "no_type", ("foo",), marks=pytest.mark.xfail),
+ ("BadReturns", "no_description", ("Return value has no description",)),
-- 
2.43.0

--- End Message ---
--- Begin Message ---
Source: numpydoc
Source-Version: 1.6.0-2
Done: Graham Inggs 

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated numpydoc 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, 28 Mar 2024 13:44:50 +
Source: numpydoc
Built-For-Profiles: noudeb
Architecture: source
Version: 1.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Graham Inggs 
Closes: 1061229
Changes:
 numpydoc (1.6.0-2) unstable; urgency=medium
 .
   * Team upload
   * Restore test dependency on python3-doc (Closes: #1061229)
Checksums-Sha1:
 6dda0593093b1c8f1789487caf633bbeba1b6734 2315 numpydoc_1.6.0-2.dsc
 670c395aae3c1be8b9a26385d4dfe8e855809297 4972 numpydoc_1.6.0-2.debian.tar.xz
Checksums-Sha256:
 ca2cee9b21079a1da5668129d17a2f3ec89a14d5567142310e1e8783c99f8bb5 2315 
numpydoc_1.6.0-2.dsc
 2a10ea7978624e7f807844627fa3a9103d8a018528b0c0ee355d681afbc53b0b 4972 
numpydoc_1.6.0-2.debian.tar.xz
Files:
 5cbc0b35a3afefd2f8dbc3f246e91357 2315 python optional numpydoc_1.6.0-2.dsc
 ad62d425275c879a51ed834db46317e1 4972 python optional 
numpydoc_1.6.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmYFdaUACgkQr8/sjmac
4cJMJQ/9F9G3+QiPvlnY7VXVpfS6fVN1FAemAluMvLXHiIz7q/N6TJ4rPp4mK9Qo
yx9NwUS6dl86d/VQauuQ3aWlsY/nJJFkKhfXefghumbTwsffD/qq8irMIbQt8V1U

Bug#1054249: (no subject)

[Johan Van de Wauw]

Can this solution be brought too bookworm, either through stable-updates 
(preferably) or otherwise backports?


The current package is not useable.

Processed: Re: prometheus: FTBFS: dh_auto_test error

[Debian Bug Tracking System]

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

> found 1064765 2.45.3+ds-3
Bug #1064765 {Done: Daniel Swarbrick } [src:prometheus] 
prometheus: FTBFS: dh_auto_test error
Marked as found in versions prometheus/2.45.3+ds-3 and reopened.
> thanks
Stopping processing here.

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

Bug#1064765: prometheus: FTBFS: dh_auto_test error

[Santiago Vila]

found 1064765 2.45.3+ds-3
thanks

Daniel Swarbrick  wrote:

* Add new 0022-Support-prometheus-common-0.47.0.patch (Closes: #1064765)


Hello. I don't quite understand how the above fix is related to
the bug itself (but maybe it's because I don't know prometheus internals).

In either case, this is still happening for me in the current version:

Lucas Nussbaum  wrote:

   FAILED:
1:48: parse error: unexpected character inside braces: '0'


Note: I'm currently using virtual machines with 1 CPU and with 2 CPUs
for archive rebuilds. On systems with 2 CPUs, the package FTBFS randomly.
On systems with 1 CPU, the package FTBFS always.

Therefore, to reproduce, please try GRUB_CMDLINE_LINUX="nr_cpus=1"
in /etc/default/grub first.

If that's still not enough to reproduce the build failure, please contact me
privately and I will gladly provide a machine to reproduce it.

Thanks.

Processed: Re: libpng1.6: hardcodes wrong udeb in shlibs, making udebs uninstallable

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.6.43-4
Bug #1066069 [src:libpng1.6] libpng1.6: hardcodes wrong udeb in shlibs, making 
udebs uninstallable
The source 'libpng1.6' and version '1.6.43-4' do not appear to match any binary 
packages
Marked as fixed in versions libpng1.6/1.6.43-4.
> close -1
Bug #1066069 [src:libpng1.6] libpng1.6: hardcodes wrong udeb in shlibs, making 
udebs uninstallable
Marked Bug as done

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

Bug#1066069: libpng1.6: hardcodes wrong udeb in shlibs, making udebs uninstallable

[Gianfranco Costamagna]

control: fixed -1 1.6.43-4
control: close -1
On Tue, 12 Mar 2024 01:13:08 +0100 Cyril Brulebois  wrote:

Source: libpng1.6
Version: 1.6.43-3
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-b...@lists.debian.org

Hi,

Your debian/rules includes this:

override_dh_makeshlibs:
dh_makeshlibs --add-udeb=libpng16-16-udeb -a

and that's indeed the package that's listed in debian/control.

However, debian/libpng16-16t64.shlibs has it wrong:

libpng16 16 libpng16-16t64 (>= 1.6.2)
udeb: libpng16 16 libpng16-udeb (>= 1.6.2)

At this point, that breaks at least:

The following packages have unmet dependencies:
 libcairo2-udeb : Depends: libpng16-16t64-udeb (>= 1.6.2) but it is not 
installable
 libfreetype6-udeb : Depends: libpng16-16t64-udeb (>= 1.6.2) but it is not 
installable
 libgdk-pixbuf-2.0-0-udeb : Depends: libpng16-16t64-udeb (>= 1.6.2) but it 
is not installable


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




OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064761: marked as pending in libsdl-perl

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #1064761 in libsdl-perl 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/perl-team/modules/packages/libsdl-perl/-/commit/d04367a8b11f83b5aead5fadcf2cff4a200dc714


Fix reference-counting in set_event_filter

Closes: #1064761


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064761

Processed: Bug#1064761 marked as pending in libsdl-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064761 [src:libsdl-perl] libsdl-perl: FTBFS: dh_auto_test: error: 
/usr/bin/perl Build test --verbose 1 returned exit code 255
Added tag(s) pending.

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

Processed: Bug#1067849 marked as pending in util-linux

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067849 [src:util-linux] util-linux: CVE-2024-28085: wall: escape sequence 
injection
Ignoring request to alter tags of bug #1067849 to the same tags previously set

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

Bug#1067849: marked as pending in util-linux

[Chris Hofstaedtler]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/util-linux/-/commit/95eb5918012e2db63a5808db53b1c8e6bada7fba


Add upstream patches to fix CVE-2024-28085

Closes: #1067849


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067849

Processed: #1067301 forwarded

[Debian Bug Tracking System]

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

> forwarded 1067301 https://github.com/pypr/compyle/issues/104
Bug #1067301 [src:compyle] compyle: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/pypr/compyle/issues/104'.
> thanks
Stopping processing here.

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

Processed: bookworm-pu: package libesmtp/1.1.0-3.1~deb12u1

[Debian Bug Tracking System]

Processing control commands:

> block 1043058 with -1
Bug #1043058 {Done: Salvatore Bonaccorso } [libesmtp6] 
libesmtp6: missing Breaks: libesmtp5
1043058 was not blocked by any bugs.
1043058 was not blocking any bugs.
Added blocking bug(s) of 1043058: 1067888
> affects -1 + src:libesmtp
Bug #1067888 [release.debian.org] bookworm-pu: package 
libesmtp/1.1.0-3.1~deb12u1
Added indication that 1067888 affects src:libesmtp

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

Bug#1065331: closing 1065331

[Michael R. Crusoe]

#confirmed by manual inspection
close 1065331 1.10.10+repack-3.2
thanks


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: closing 1065331

[Debian Bug Tracking System]

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

> #confirmed by manual inspection
> close 1065331 1.10.10+repack-3.2
Bug #1065331 [libhdf5-103-1t64] libhdf5-103-1t64: depends on libcurl4 instead 
of libcurl4t64
Marked as fixed in versions hdf5/1.10.10+repack-3.2.
Bug #1065331 [libhdf5-103-1t64] libhdf5-103-1t64: depends on libcurl4 instead 
of libcurl4t64
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1064814: marked as done (ironic-inspector: FTBFS: AttributeError: 'Flask' object has no attribute 'before_first_request'. Did you mean: '_got_first_request'?)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 10:49:30 +
with message-id 
and subject line Bug#1064814: fixed in ironic-inspector 12.1.0-2
has caused the Debian Bug report #1064814,
regarding ironic-inspector: FTBFS: AttributeError: 'Flask' object has no 
attribute 'before_first_request'. Did you mean: '_got_first_request'?
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.)


-- 
1064814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ironic-inspector
Version: 11.7.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> =
> Failures during discovery
> =
> --- import errors ---
> Failed to import test module: ironic_inspector.test.unit.test_acl
> Traceback (most recent call last):
>   File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path
> module = self._get_module_from_name(name)
>  
>   File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/ironic_inspector/test/unit/test_acl.py", line 29, in 
> 
> from ironic_inspector import main
>   File "/<>/ironic_inspector/main.py", line 199, in 
> @_app.before_first_request
>  ^
> AttributeError: 'Flask' object has no attribute 'before_first_request'. Did 
> you mean: '_got_first_request'?
> 
> Failed to import test module: ironic_inspector.test.unit.test_main
> Traceback (most recent call last):
>   File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path
> module = self._get_module_from_name(name)
>  
>   File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/ironic_inspector/test/unit/test_main.py", line 32, 
> in 
> from ironic_inspector import main
>   File "/<>/ironic_inspector/main.py", line 199, in 
> @_app.before_first_request
>  ^
> AttributeError: 'Flask' object has no attribute 'before_first_request'. Did 
> you mean: '_got_first_request'?
> 
> Failed to import test module: ironic_inspector.test.unit.test_wsgi_service
> Traceback (most recent call last):
>   File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path
> module = self._get_module_from_name(name)
>  
>   File "/usr/lib/python3.12/unittest/loader.py", line 337, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/ironic_inspector/test/unit/test_wsgi_service.py", 
> line 18, in 
> from ironic_inspector import main
>   File "/<>/ironic_inspector/main.py", line 199, in 
> @_app.before_first_request
>  ^
> AttributeError: 'Flask' object has no attribute 'before_first_request'. Did 
> you mean: '_got_first_request'?
> 
> 
> The above traceback was encountered during test discovery which imports all 
> the found test modules in the specified test_path.
> 
> --
> Ran 0 tests in 4.545s
> 
> OK
> + stestr slowest
> make[1]: *** [debian/rules:34: override_dh_install] Error 3


The full build log is available from:
http://qa-logs.debian.net/2024/02/26/ironic-inspector_11.7.0-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240226;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240226=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: ironic-inspector
Source-Version: 12.1.0-2
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
ironic-inspector, which is due to be installed 

Bug#1064815: marked as done (python-os-vif: FTBFS: failed test: os_vif.tests.unit.test_objects.TestObjectVersions.test_versions)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 10:49:40 +
with message-id 
and subject line Bug#1064815: fixed in python-os-vif 3.5.0-2
has caused the Debian Bug report #1064815,
regarding python-os-vif: FTBFS: failed test: 
os_vif.tests.unit.test_objects.TestObjectVersions.test_versions
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.)


-- 
1064815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-os-vif
Version: 3.2.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> ==
> FAIL: os_vif.tests.unit.test_objects.TestObjectVersions.test_versions
> os_vif.tests.unit.test_objects.TestObjectVersions.test_versions
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File "/<>/os_vif/tests/unit/test_objects.py", line 67, in 
> test_versions
> self.assertEqual(expected, actual,
>   File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 395, in 
> assertEqual
> self.assertThat(observed, matcher, message)
>   File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 482, in 
> assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: !=:
> reference = {'FixedIPList': '1.0-15ecf022a68ddbb8c2a6739cfc9f8f5e',
>  'RouteList': '1.0-15ecf022a68ddbb8c2a6739cfc9f8f5e',
>  'SubnetList': '1.0-15ecf022a68ddbb8c2a6739cfc9f8f5e'}
> actual= {'FixedIPList': '1.0-29387c5026a3ac4fe1048d7f4f658bec',
>  'RouteList': '1.0-29387c5026a3ac4fe1048d7f4f658bec',
>  'SubnetList': '1.0-29387c5026a3ac4fe1048d7f4f658bec'}
> : Some objects have changed; please make sure the versions have been bumped, 
> and then update their hashes here.
> 
> 
> --
> Ran 75 tests in 8.453s
> 
> FAILED (failures=1)
> + echo ==> STESTR TEST SUITE FAILED FOR python3.12: displaying pip3 
> freeze output...
> ==> STESTR TEST SUITE FAILED FOR python3.12: displaying pip3 freeze 
> output...
> + [ -x /usr/bin/pip3 ]
> + pip3 freeze
> alabaster==0.7.12
> amqp==5.2.0
> anyjson==0.3.3
> appdirs==1.4.4
> attrs==23.2.0
> autopage==0.4.0
> Babel==2.10.3
> bcrypt==3.2.2
> blinker==1.7.0
> cachetools==5.3.0
> certifi==2023.11.17
> cffi==1.16.0
> chardet==5.2.0
> charset-normalizer==3.3.2
> cliff==4.3.0
> cmd2==2.4.3+ds
> confluent-kafka==1.7.0
> coverage==7.2.7
> cryptography==41.0.7
> debtcollector==2.5.0
> decorator==5.1.1
> deprecation==2.0.7
> dnspython==2.6.1
> docutils==0.20.1
> dogpile.cache==1.1.8
> dulwich==0.21.6
> eventlet==0.0.0
> extras==1.0.0
> fasteners==0.18
> fixtures==4.0.1
> flake8==6.1.0
> futurist==2.4.1
> gevent==23.9.1
> greenlet==3.0.1
> hacking==4.1.0
> idna==3.6
> imagesize==1.4.1
> importlib-metadata==4.12.0
> iso8601==1.0.2
> Jinja2==3.1.2
> jmespath==1.0.1
> jsonpatch==1.32
> jsonpointer==2.3
> keystoneauth1==5.3.0
> kombu==5.3.5
> lxml==5.1.0
> Mako==1.3.2.dev0
> MarkupSafe==2.1.5
> mccabe==0.7.0
> monotonic==1.6
> more-itertools==10.2.0
> msgpack==1.0.3
> netaddr==0.8.0
> netifaces==0.11.0
> oauthlib==3.2.2
> openstackdocstheme==3.2.0
> openstacksdk==1.5.0
> os-client-config==2.1.0
> os-service-types==1.7.0
> oslo.concurrency==5.2.0
> oslo.config==9.2.0
> oslo.context==5.2.0
> oslo.i18n==6.1.0
> oslo.log==5.3.0
> oslo.messaging==14.4.1
> oslo.metrics==0.7.0
> oslo.middleware==5.2.0
> oslo.privsep==3.2.0
> oslo.serialization==5.2.0
> oslo.service==3.2.0
> oslo.utils==6.2.1
> oslo.versionedobjects==3.2.0
> oslosphinx==4.18.0
> oslotest==4.5.0
> ovs==3.3.0
> ovsdbapp==2.4.1
> packaging==23.2
> Paste==3.7.1
> PasteDeploy==3.1.0
> pbr==6.0.0
> ply==3.11
> prettytable==3.6.0
> prometheus-client==0.19.0
> psutil==5.9.8
> py==1.11.0
> pyasyncore==1.0.2
> pycodestyle==2.11.1
> pycparser==2.21
> pyflakes==3.1.0
> Pygments==2.17.2
> pyinotify==0.9.6
> PyJWT==2.7.0
> pyparsing==3.1.1
> pyperclip==1.8.2
> pyroute2==0.7.7
> python-dateutil==2.8.2
> python-subunit==1.4.2
> pytz==2024.1
> PyYAML==6.0.1
> pyzmq==24.0.1
> reno==2.11.2
> repoze.lru==0.7
> requests==2.31.0
> requestsexceptions==1.4.0
> rfc3986==2.0.0
> roman==3.3
> Routes==2.5.1
> six==1.16.0
> snowballstemmer==2.2.0
> sortedcontainers==2.4.0
> Sphinx==7.2.6
> statsd==4.0.1
> stestr==4.1.0
> stevedore==5.1.0
> Tempita==0.5.2
> 

Processed: Bug#1064814 marked as pending in ironic-inspector

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064814 [src:ironic-inspector] ironic-inspector: FTBFS: AttributeError: 
'Flask' object has no attribute 'before_first_request'. Did you mean: 
'_got_first_request'?
Added tag(s) pending.

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

Bug#1067260: marked as done (python-wsme: FTBFS: make[1]: pyversions: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 10:34:32 +
with message-id 
and subject line Bug#1067260: fixed in python-wsme 0.12.1-2
has caused the Debian Bug report #1067260,
regarding python-wsme: FTBFS: make[1]: pyversions: No such file or directory
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.)


-- 
1067260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wsme
Version: 0.11.0-5
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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> debian/rules:31: warning: overriding recipe for target 
> 'override_dh_gencontrol'
> /usr/share/openstack-pkg-tools/pkgos.make:132: warning: ignoring old recipe 
> for target 'override_dh_gencontrol'
> pkgos-dh_auto_install --no-py2
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-wsme
> + echo python-wsme
> + sed s/python-//
> + PY_MODULE_NAME=wsme
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ no = yes ]
> + TARGET_DIR=python3-wsme
> + pwd
> + python3.12 setup.py install --install-layout=deb --root 
> /<>/debian/python3-wsme
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'author-email' will not be supported in future
> versions. Please use the underscore name 'author_email' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> /usr/lib/python3/dist-packages/setuptools/command/develop.py:40: 
> EasyInstallDeprecationWarning: easy_install command is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` and ``easy_install``.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://github.com/pypa/setuptools/issues/917 for details.
> 
> 
> 
> !!
>   easy_install.initialize_options(self)
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> 

Processed: Bug#1064815 marked as pending in python-os-vif

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1064815 [src:python-os-vif] python-os-vif: FTBFS: failed test: 
os_vif.tests.unit.test_objects.TestObjectVersions.test_versions
Added tag(s) pending.

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

Processed: found 1051496 in 1.14-21

[Debian Bug Tracking System]

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

> found 1051496 1.14-21
Bug #1051496 {Done: Jörg Frings-Fürst } [mailgraph] 
mailgraph: does not support the new syslog format
Marked as found in versions mailgraph/1.14-21; no longer marked as fixed in 
versions mailgraph/1.14-21 and reopened.
> thanks
Stopping processing here.

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

Bug#1064815: marked as pending in python-os-vif

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1064815 in python-os-vif 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/openstack-team/libs/python-os-vif/-/commit/3ea0c1af8b771b55bccb61e1931530871f9acd26


Uploading to unstable, fixing FTBFS (Closes: #1064815).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064815

Bug#1064814: marked as pending in ironic-inspector

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1064814 in ironic-inspector 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/openstack-team/services/ironic-inspector/-/commit/82aa1a8fc60828e5b08dcc1240f31a9163ab2b71


Uploading to unstable, fixing FTBFS (Closes: #1064814).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1064814

Bug#1067798: marked as done (python-pykmip: FTBFS: failing tests)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 10:19:18 +
with message-id 
and subject line Bug#1067798: fixed in python-pykmip 0.10.0-7
has caused the Debian Bug report #1067798,
regarding python-pykmip: FTBFS: failing tests
to be marked as done.

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

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


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

Package: src:python-pykmip
Version: 0.10.0-6
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules build
make: pyversions: No such file or directory
py3versions: no X-Python3-Version in control file, using supported versions
dh build --buildsystem=python_distutils --with python3
   dh_update_autotools_config -O--buildsystem=python_distutils
   dh_autoreconf -O--buildsystem=python_distutils
   dh_auto_configure -O--buildsystem=python_distutils
dh_auto_configure: warning: Please use the third-party "pybuild" build system 
instead of python-distutils
dh_auto_configure: warning: This feature will be removed in compat 12.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
make[1]: pyversions: No such file or directory
py3versions: no X-Python3-Version in control file, using supported versions
echo "Do nothing..."
Do nothing...
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
make[1]: pyversions: No such file or directory
py3versions: no X-Python3-Version in control file, using supported versions
set -e ; for i in 3.12 3.11 ; do \
PYTHONPATH=. PYTHON=python$i python$i -m coverage run --source=kmip/ -m 
pytest --strict kmip/tests/unit ; \
done
= test session starts ==
platform linux -- Python 3.12.2, pytest-8.1.1, pluggy-1.4.0
rootdir: /<>
configfile: pytest.ini
collected 3394 items

kmip/tests/unit/core/attributes/test_application_specific_information.py . [  
0%]
..   [  0%]
kmip/tests/unit/core/attributes/test_attributes.py ......... [  1%]
 [  3%]
 [  3%]
kmip/tests/unit/core/attributes/test_digest.py   [  4%]
kmip/tests/unit/core/factories/payloads/test_payload.py  [  4%]
...  [  5%]
kmip/tests/unit/core/factories/payloads/test_request.py  [  6%]
..   [  6%]
kmip/tests/unit/core/factories/payloads/test_response.py ... [  7%]
...  [  8%]
kmip/tests/unit/core/factories/test_attribute.py .   [  8%]
kmip/tests/unit/core/factories/test_attribute_values.py ..ss.s.s [  8%]
s[  9%]
kmip/tests/unit/core/messages/contents/test_authentication.py .. [  9%]
..   [  9%]
kmip/tests/unit/core/messages/contents/test_protocol_version.py  [ 10%]
.[ 10%]
kmip/tests/unit/core/messages/payloads/test_activate.py ..   [ 11%]
kmip/tests/unit/core/messages/payloads/test_archive.py . [ 11%]
.[ 11%]
kmip/tests/unit/core/messages/payloads/test_cancel.py .. [ 12%]
...  [ 12%]
kmip/tests/unit/core/messages/payloads/test_check.py ... [ 13%]
.[ 14%]
kmip/tests/unit/core/messages/payloads/test_create.py .. [ 14%]
 [ 15%]
kmip/tests/unit/core/messages/payloads/test_create_key_pair.py . [ 16%]
...  [ 17%]
kmip/tests/unit/core/messages/payloads/test_decrypt.py . [ 18%]
.[ 19%]

Processed: Bug#1067260 marked as pending in python-wsme

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067260 [src:python-wsme] python-wsme: FTBFS: make[1]: pyversions: No such 
file or directory
Added tag(s) pending.

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

Bug#1067260: marked as pending in python-wsme

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1067260 in python-wsme 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/openstack-team/python/python-wsme/-/commit/b5e347a7567b2a6e22d7328795b5604b63545434


Uploading to unstable, fixing FTBFS (Closes: #1067260).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067260

Bug#1064664: marked as done (ukui-power-manager has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/ukui-control-center/libpower.so)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 09:35:57 +
with message-id 
and subject line Bug#1064664: fixed in ukui-power-manager 4.0.0.0-2
has caused the Debian Bug report #1064664,
regarding ukui-power-manager has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/ukui-control-center/libpower.so
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.)


-- 
1064664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ukui-power-manager
Version: 4.0.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + ukui-control-center

ukui-power-manager has an undeclared file conflict. This may result in
an unpack error from dpkg.

The file /usr/lib/x86_64-linux-gnu/ukui-control-center/libpower.so is
contained in the packages
 * ukui-control-center
   * 3.0.2-2 as present in bullseye
   * 3.0.5.1-2 as present in bookworm|trixie
 * ukui-power-manager/4.0.0.0-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: ukui-power-manager
Source-Version: 4.0.0.0-2
Done: handsome_feng 

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

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated 
ukui-power-manager 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, 28 Mar 2024 17:11:41 +0800
Source: ukui-power-manager
Architecture: source
Version: 4.0.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: kylin Team 
Changed-By: handsome_feng 
Closes: 1064664
Changes:
 ukui-power-manager (4.0.0.0-2) unstable; urgency=medium
 .
   * Fix the conflict with ukui-control-center. (Closes: #1064664)
Checksums-Sha1:
 3ab12b888676c6b287866e54322d685d13e7e498 2373 ukui-power-manager_4.0.0.0-2.dsc
 62ecf8102ac36afeae78bcab450e2f6ec4831f08 98628 
ukui-power-manager_4.0.0.0.orig.tar.gz
 b7154b204ae0a5396f670a0b46cf735464d147cc 2812 
ukui-power-manager_4.0.0.0-2.debian.tar.xz
 aadee349caedc91a274e92b583ea63ea5fa3fc00 18139 
ukui-power-manager_4.0.0.0-2_source.buildinfo
Checksums-Sha256:
 01e617845ff797e4693a5cf0eaad2105436eca891e37570e7c0ce887f63512fe 2373 
ukui-power-manager_4.0.0.0-2.dsc
 5fe69c864fcba39e5567566b432e6604be8d401011de4cc31d34bafe19c14991 98628 
ukui-power-manager_4.0.0.0.orig.tar.gz
 e10518d5954948ca1041e7773d106ddd7ad48f2aba22475c9fd10e72c8b01d0f 2812 
ukui-power-manager_4.0.0.0-2.debian.tar.xz
 03508b05785cfa922d8746add214c5ab38b4cae8a79fdc16b65fcfafeed5052e 18139 
ukui-power-manager_4.0.0.0-2_source.buildinfo
Files:
 28c13af6aba881e503339958f7ec9046 2373 x11 optional 
ukui-power-manager_4.0.0.0-2.dsc
 88f5b3e56e21a0c9e223ab5abb24b4b3 98628 x11 optional 
ukui-power-manager_4.0.0.0.orig.tar.gz
 bcda3bbc49f04d7b61b779f9d040bfe7 2812 x11 optional 
ukui-power-manager_4.0.0.0-2.debian.tar.xz
 d9a77d0c08930ecb709d36bce39da138 18139 x11 optional 
ukui-power-manager_4.0.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmYFNJgbHGppYW5mZW5n
bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8MsXcP/3wyoI3gAUWdAKC7MUSH
Me6qzDs12euMfQMF3UzMhrn3yQpJztsiqlH46NxZdzApn0zMsO5CNi7GPOWXd74m
iW/de2XXetwoh1bgM0tE1HKxrN2annydnmS47aVRv1fnerOntTdLIFSm7+eygQEu
JEoIbCz9nZWn63BEvP+UUp+Mu5w+nC31fJB1Av8lvXNZZzI1CNMWBF46wBINtImL
mVEHcqj4GpooJXKMv+7cYI6f01jloQYPTY/expum953olnhGx8YsDH9wst3J+fPk
hVoD09EpYvO+bHVp7cpx3ywwLwZJm8Lcpu24ZUOxug3YKw1i429p9FslNfJrkX5W

Bug#1063617: marked as done (sogo FTBFS on little endian)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 09:48:42 +0100
with message-id <6c433bef08397152da59e5e84bdb3fa63a8040c7.ca...@debian.org>
and subject line Bug closed in sogo 5.10.0-2 upload
has caused the Debian Bug report #1063617,
regarding sogo FTBFS on little endian
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.)


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

https://buildd.debian.org/status/logs.php?pkg=sogo=5.9.0-1
https://buildd.debian.org/status/logs.php?pkg=sogo=5.9.1-1

...
==
FAIL: test_recurrenceRangesWithinCalendarDateRange_ 
(TestiCalRecurrenceCalculator.m:381)
--
Invalid occurrence for recurrence rule 
FREQ=YEARLY;UNTIL=2131T09Z;BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA: Fri 
1999-01-01 09:00 (expected date was Sat 1998-01-31 09:00)

==
FAIL: test_NGInternetSocketAddressFromString (TestNGNetUtlilities.m:86)
--
isIpv4 mismatch. Expected: '1', result: '0'. Test url: 'localhost:1001'

==
FAIL: test_generateDataForHeaderFieldNamed_value_ 
(TestNGMimeAddressHeaderFieldGenerator.m:78)
--
received 'wolfg...@test.com,
   wolfg...@test.com' instead of '"" ' 
for '"" '

--
Ran 38 tests

FAILED (3 failures, 0 errors)
hash = 
$argon2id$v=19$m=65536,t=2,p=1$H1BrOTIX9XOi2WuD7zx+pw$Vvik3l21HkuRr5LhnJz0RBq35hxI8woG51F/gEuUt78
make[3]: *** [GNUmakefile:63: check] Error 1



debian/rules ignores test failures on big endian
--- End Message ---
--- Begin Message ---
This bug was closed by this upload, which was lacking a colon in the
bug closer:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Mar 2024 22:47:37 +0100
Source: sogo
Architecture: source
Version: 5.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian SOGo Maintainers

Changed-By: Jordi Mallach 
Changes:
 sogo (5.10.0-2) unstable; urgency=medium
 .
   * Revert number of expected test failures to 2 (closes #1063617).
   * Add bug closer to previous changelog entry.
   * Do not run testsuite if `nocheck` is part of DEB_BUILD_OPTIONS.
Checksums-Sha1:
 1ea55c2f0ab09ebc1f1f9935d94c702296362a17 2271 sogo_5.10.0-2.dsc
 de7410e3adf9b67613545fde027030ca6c38c108 18440 sogo_5.10.0-
2.debian.tar.xz
 a4d036768fa35279035c58c9b67cdf13df041e1e 11467 sogo_5.10.0-
2_amd64.buildinfo
Checksums-Sha256:
 4a57e1e1d97758ce94d369e9118a2b99ec3951afb2c2937787c64a29459319a4 2271
sogo_5.10.0-2.dsc
 7def40b5bc1459836729fb6e9bbd78b1c1c219092fab6a2150d7c090f3269e77 18440
sogo_5.10.0-2.debian.tar.xz
 96b02c63096ffdfbb5363de914f61b1ad4f75d89a2f95371969e834b8919b01c 11467
sogo_5.10.0-2_amd64.buildinfo
Files:
 d96e649bcc0c49d9288c59853b133e9d 2271 mail optional sogo_5.10.0-2.dsc
 be41b6eb545c802c8b0f041a1ebedc70 18440 mail optional sogo_5.10.0-
2.debian.tar.xz
 b6f21e538f4c3531e239ecb18aebb062 11467 mail optional sogo_5.10.0-
2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAmYDQ3sACgkQJVAvb8vj
ywReFg//YALCqsLzMpyuaFpUnPoQ+levT6j5Mm/Rz+Q1APMMNLdFHU8TayyJVvat
KKuV0WK6XNcr9N1VfcqcFpodSAx1gRYv/PVoj/3rtygEjHbRPwhI8tPIglt3+D4G
QQTlsqtY5gYHN1JWR0YLkgTfKMjRg+Q54UlquUAGYo7vzz9xRPXGK9KDXGx8F7kT
itXTFFoZAOqrhInHF5LjjTfSK3Fu/VIVgkdLqN1IsLhNOnArcwrFW+JveJ/t7i5G
OM4uu2jBDFAwba8Q6cN2KWJ7Fdd7MZmn5aIbf1K3McoRSuUOMTqrz09wBbm5DULg
L6Bzf8AdtJGbEzlPmifN5YXBFPgO+/2/LG9hvtLYlzaAcSgt4FFE5NbEvtkd2R8Q
bxPGQJASBwUtQQGt5/ugqocfOK5L3vSyPQpW6QtMHfIPBeYtVmE2DMMscLrR9uhs
CfTeK1fb5huh7RaSHsfAO4e4cpgAngP+3Yabh7fAwIRIxiE4T3aCMk5M7MhN+XtK
xuf/evonjWSNJo9mBoG14Z/3caW7FdfF7D5yNfNw8WKKo/qWKFPkX315e0B7gka5
3MN1Q3VdcbG2kaYRC91vOmE7VFevglSYCwrv+ZC7tEs8rZZr+xcmMpAt1/CezHuh
kBFTcyQYxuo1QlQjn8Ixez8doAFkBLr3GvneeqoZJS0JjbIwTbQ=
=d1l4
-END PGP SIGNATURE-



-- 
Jordi Mallach 
Debian Project


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

Bug#1067297: marked as done (taskw: 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 Thu, 28 Mar 2024 08:38:56 +
with message-id 
and subject line Bug#1067297: fixed in taskw 2.0.0-2
has caused the Debian Bug report #1067297,
regarding taskw: 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.)


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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config 
> running config
> I: pybuild base:305: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12/build/taskw
> copying taskw/utils.py -> /<>/.pybuild/cpython3_3.12/build/taskw
> copying taskw/taskrc.py -> /<>/.pybuild/cpython3_3.12/build/taskw
> copying taskw/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw
> copying taskw/exceptions.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw
> copying taskw/task.py -> /<>/.pybuild/cpython3_3.12/build/taskw
> copying taskw/warrior.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw
> creating /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/uuid.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/string.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/choice.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/base.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/duration.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/annotationarray.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/numeric.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/commaseparateduuid.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/date.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> copying taskw/fields/array.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/fields
> creating /<>/.pybuild/cpython3_3.12/build/taskw/test
> copying taskw/test/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/test
> copying taskw/test/test_warrior.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/test
> copying taskw/test/test_utils.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/test
> copying taskw/test/test_taskrc.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/test
> copying taskw/test/test_fields.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/test
> copying taskw/test/test_datas.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/test
> copying taskw/test/test_recursive.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/test
> copying taskw/test/test_task.py -> 
> /<>/.pybuild/cpython3_3.12/build/taskw/test
> running egg_info
> creating taskw.egg-info
> writing taskw.egg-info/PKG-INFO
> writing dependency_links to taskw.egg-info/dependency_links.txt
> writing requirements to taskw.egg-info/requires.txt
> writing top-level names to taskw.egg-info/top_level.txt
> writing manifest file 'taskw.egg-info/SOURCES.txt'
> reading manifest file 'taskw.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '.tox_tests.sh'
> adding license file 'LICENSE.txt'
> writing manifest file 'taskw.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: 
> Package 'taskw.test.data' is absent from the `packages` configuration.
> !!
> 
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'taskw.test.data' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
> 
> This leads to an ambiguous overall configuration. If you want to 
> 

Bug#1067330: marked as done (websockify: FTBFS: /usr/bin/pkgos-dh_auto_install: 37: python3.12: not found)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 08:39:05 +
with message-id 
and subject line Bug#1067330: fixed in websockify 0.10.0+dfsg1-6
has caused the Debian Bug report #1067330,
regarding websockify: FTBFS: /usr/bin/pkgos-dh_auto_install: 37: python3.12: 
not 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.)


-- 
1067330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: websockify
Version: 0.10.0+dfsg1-5
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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=websockify
> + echo websockify
> + sed s/python-//
> + PY_MODULE_NAME=websockify
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.12 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> /usr/bin/pkgos-dh_auto_install: 37: python3.12: not found
> make[1]: *** [debian/rules:25: override_dh_auto_install] Error 127


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/websockify_0.10.0+dfsg1-5_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 ---
Source: websockify
Source-Version: 0.10.0+dfsg1-6
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
websockify, 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.
Thomas Goirand  (supplier of updated websockify 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, 28 Mar 2024 08:39:58 +0100
Source: websockify
Architecture: source
Version: 0.10.0+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1067330
Changes:
 websockify (0.10.0+dfsg1-6) unstable; urgency=medium
 .
   * Fix d/control build-depends from python3-dev to python3-all-dev
 (Closes: #1067330).
Checksums-Sha1:
 9ec87d69499119ffbe7a193a58d82763463e763f 2245 websockify_0.10.0+dfsg1-6.dsc
 b6ff9d5c6a7b86feba4ecb8905f878673113f018 12432 
websockify_0.10.0+dfsg1-6.debian.tar.xz
 6498ab068d5e6f647f7cd2569ef2a801a850d712 8855 
websockify_0.10.0+dfsg1-6_amd64.buildinfo
Checksums-Sha256:
 9b52d9522747445dfc43634d15337ddf2c97482f33ae453ce772d7e38b426e4a 2245 
websockify_0.10.0+dfsg1-6.dsc
 aa0ab937bcca59b36f38eac8725f3f05090c44187155313f0f80f3db47c678b8 12432 
websockify_0.10.0+dfsg1-6.debian.tar.xz
 55592424ed8d3d969410f15f277e9e68beb559be89d41330865cd056dc30ebae 8855 
websockify_0.10.0+dfsg1-6_amd64.buildinfo
Files:
 3c54635a78751e9a18b19ff44014b25e 2245 python optional 
websockify_0.10.0+dfsg1-6.dsc
 a57d12d39b11a5c2f0db5c828dbba89d 12432 python optional 
websockify_0.10.0+dfsg1-6.debian.tar.xz
 9b54b84626357fde26b22667cc047695 8855 python optional 
websockify_0.10.0+dfsg1-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

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

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 08:34:57 +
with message-id 
and subject line Bug#1066781: fixed in hickle 5.0.2-9
has caused the Debian Bug report #1066781,
regarding hickle: FTBFS: dh_auto_test: error: pybuild --test -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.)


-- 
1066781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hickle
Version: 5.0.2-8
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):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> running config
> I: pybuild base:305: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_hickle/build/hickle
> copying hickle/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle
> copying hickle/hickle.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle
> copying hickle/fileio.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle
> copying hickle/lookup.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle
> copying hickle/helpers.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle
> copying hickle/__version__.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle
> creating /<>/.pybuild/cpython3_3.12_hickle/build/hickle/tests
> copying hickle/tests/generate_legacy_4_0_0.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle/tests
> copying hickle/tests/test_01_hickle_helpers.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle/tests
> copying hickle/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_hickle/build/hickle/tests
> copying hickle/tests/test_hickle.py -> 
> 

Bug#1067875: howm: fails to install: Error: Cannot open load file: No such file or directory, iigrep

[Andreas Beckmann]

Package: howm
Version: 1.5.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up howm (1.5.1-1) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install howm for emacs
  install/howm-1.5.1: Handling install of emacsen flavor emacs
  install/howm-1.5.1: byte-compiling for emacs
  
  In gfunc-define-function:
  gfunc.el:71:2: Warning: docstring has wrong usage of unescaped single quotes 
(use \= or different quoting)
  
  In toplevel form:
  howm-backend.el:22:2: Error: Cannot open load file: No such file or 
directory, iigrep
  
  In howm-map-with-index:
  howm-common.el:160:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-first-n:
  howm-common.el:235:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-classify:
  howm-common.el:361:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-with-coding-system:
  howm-common.el:441:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-with-schedule-interval:
  howm-common.el:526:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In toplevel form:
  howm-date.el:22:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm-menu.el:22:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm-misc.el:22:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm-mkmenu.el:71:2: Warning: `mapcar' called for effect; use `mapc' or 
`dolist' instead
  
  In toplevel form:
  howm-mode.el:38:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm-reminder.el:22:2: Error: Cannot open load file: No such file or 
directory, iigrep
  
  In howm-dont-warn-free-variable:
  howm-vars.el:78:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  
  In howm-funcall-if-defined:
  howm-vars.el:85:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  howm-vars.el:125:2: Warning: defvar `howm-compatible-to-ver1dot3' docstring 
has wrong usage of unescaped single quotes (use \= or different quoting)
  howm-vars.el:600:2: Warning: custom-declare-variable `howm-list-title' 
docstring has wrong usage of unescaped single quotes (use \= or different 
quoting)
  howm-vars.el:814:2: Warning: custom-declare-variable 
`howm-process-coding-system' docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  howm-vars.el:839:2: Warning: custom-declare-variable 
`howm-iigrep-preview-items' docstring wider than 80 characters
  howm-vars.el:941:2: Warning: custom-declare-variable 
`howm-view-external-viewer-assoc' docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)
  howm-vars.el:984:2: Warning: custom-declare-variable `howm-auto-narrow' 
docstring has wrong usage of unescaped single quotes (use \= or different 
quoting)
  
  In toplevel form:
  howm-view.el:22:2: Error: Cannot open load file: No such file or directory, 
iigrep
  
  In toplevel form:
  howm.el:65:2: Error: Cannot open load file: No such file or directory, iigrep
  
  In riffle-summary-name-format:
  riffle.el:115:2: Warning: docstring wider than 80 characters
  
  In riffle-contents-name-format:
  riffle.el:115:2: Warning: docstring wider than 80 characters
  ERROR: install script from howm package failed
  dpkg: error processing package howm (--configure):
   installed howm package post-installation script subprocess returned error 
exit status 1


cheers,

Andreas


howm_1.5.1-1.log.gz
Description: application/gzip

Bug#1064598: yagv: crashes with "module 'pyglet.graphics' has no attribute 'vertex_list'"

[Petter Reinholdtsen]

[Gregor Riepl 2024-02-26]
> Unfortunately, it appears that upstream project is dead.
> The last commit was in 2017, and any requests by @pere on their bug tracker
> fell on deaf ears: [2]
> 
> It's regrettable, but I don't think yagv can be kept with the current
> situation.

I agree.  Someone need to take over yagl upstream development for it to
be sustainable in Debian.  Time to file for removal?

See https://bugs.debian.org/877377 > for my tries to find a new upstream.

-- 
Happy hacking
Petter Reinholdtsen

Processed: Bug#1067297 marked as pending in taskw

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067297 [src:taskw] taskw: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.

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

Bug#1067297: marked as pending in taskw

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

Bug #1067297 in taskw 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/python-team/packages/taskw/-/commit/8a061fb95ba06d5abae05248efab04d2ebb70ed5


Fix tests with new pytest

Closes: #1067297


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067297

Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input

[Petter Reinholdtsen]

[James Valleroy 2024-02-12]
> Here is a patch that fixes the build:

Thank you.  Can you explain why changing the output from package.json to
mktemp and then moving the result to package.json will solve the build
problem?  I fail to understand how this could change anything.

Btw, did you mean TEMPFILE=$(shell mktemp) to get a random temp file
name?

-- 
Happy hacking
Petter Reinholdtsen

Processed: reassign 1067333 plantuml

[Debian Bug Tracking System]

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

> reassign 1067333 plantuml
Bug #1067333 [src:python-sphinxcontrib.plantuml] autosuspend: FTBFS: TypeError: 
can only concatenate str (not "bytes") to str
Bug reassigned from package 'src:python-sphinxcontrib.plantuml' to 'plantuml'.
Ignoring request to alter found versions of bug #1067333 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1067333 to the same values 
previously set
>
End of message, 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#1067333: Further investigation

[Thomas Goirand]

Hi,

I tried rebuilding autosuspend in Sid, and the build lead to this 
traceback in Java:


Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinxcontrib/plantuml.py", line 
223, in html_visit_plantuml

fnames = dict((e, render_plantuml(self, node, e))
 
  File "/usr/lib/python3/dist-packages/sphinxcontrib/plantuml.py", line 
223, in 

fnames = dict((e, render_plantuml(self, node, e))
  ^^
  File "/usr/lib/python3/dist-packages/sphinxcontrib/plantuml.py", line 
116, in render_plantuml
raise PlantUmlError('error while running plantuml\n\n' + 
serr.decode('utf-8'))

sphinxcontrib.plantuml.PlantUmlError: error while running plantuml

Exception in thread "main" java.lang.InternalError: 
java.lang.reflect.InvocationTargetException
	at 
java.desktop/sun.font.FontManagerFactory$1.run(FontManagerFactory.java:87)
	at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
	at 
java.desktop/sun.font.FontManagerFactory.getInstance(FontManagerFactory.java:75)
	at 
java.desktop/sun.font.SunFontManager.getInstance(SunFontManager.java:248)
	at 
java.desktop/sun.font.FontDesignMetrics.getMetrics(FontDesignMetrics.java:266)
	at 
java.desktop/sun.java2d.SunGraphics2D.getFontMetrics(SunGraphics2D.java:871)

at net.sourceforge.plantuml.Run.forceOpenJdkResourceLoad(Run.java:230)
at net.sourceforge.plantuml.Run.main(Run.java:137)
Caused by: java.lang.reflect.InvocationTargetException
	at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method)
	at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
	at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at 
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
	at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
	at 
java.desktop/sun.font.FontManagerFactory$1.run(FontManagerFactory.java:85)

... 7 more
Caused by: java.lang.RuntimeException: Fontconfig head is null, check 
your fonts or fonts configuration
	at 
java.desktop/sun.awt.FontConfiguration.getVersion(FontConfiguration.java:1271)
	at 
java.desktop/sun.awt.FontConfiguration.readFontConfigFile(FontConfiguration.java:224)

at 
java.desktop/sun.awt.FontConfiguration.init(FontConfiguration.java:106)
	at 
java.desktop/sun.awt.X11FontManager.createFontConfiguration(X11FontManager.java:706)

at java.desktop/sun.font.SunFontManager$2.run(SunFontManager.java:358)
at java.desktop/sun.font.SunFontManager$2.run(SunFontManager.java:315)
	at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:318)

at java.desktop/sun.font.SunFontManager.(SunFontManager.java:315)
at java.desktop/sun.awt.FcFontManager.(FcFontManager.java:35)
at java.desktop/sun.awt.X11FontManager.(X11FontManager.java:56)
... 13 more

so the issue seems to be in PlantUML rather than its sphinxcontrib 
wrapper in Python.


Please note that the part that raised the error in Python is probably 
broken, but when there's no error when starting PlantUML, the module 
should still be ok.


I'm reassigning the bug to PlantUML. Please deal between autosuspend and 
PlantUML.


Cheers,

Thomas Goirand (zigo)

Processed: Bug#1066781 marked as pending in hickle

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066781 [src:hickle] hickle: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.

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

Bug#1066781: marked as pending in hickle

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1066781 in hickle 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/python-team/packages/hickle/-/commit/8f016c484ff18c3e959d0df8cb54d5216f7c4a2f


Added patch to fix FTBFS with Pytest version 8. Closes: #1066781


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066781

Bug#1067145: marked as done (websockify: missing depend on python3-all for autopkgtest)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2024 08:44:47 +0100
with message-id <32e7c48b-4829-4abd-8fd4-98dad063f...@debian.org>
and subject line Duplicate
has caused the Debian Bug report #1067145,
regarding websockify: missing depend on python3-all for autopkgtest
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.)


-- 
1067145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: websockify
Version: 0.10.0+dfsg1-5
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package has an autopkgtest regression due to changes in NumPy.
The python3-numpy package no longer depends on all supported Python 
versions. You need to depend on python3-all if you want to run your 
tests against all supported Python releases.

Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmX5ZWMACgkQ+C8H+466
LVklSQwAy7kT48/933q/dYkim+duv/km7n1KV7tLw3GF5O8ctdOxu2X3KRJA63cI
T1TSrwjRstiWnLKaeRbKNPlC32f38OxCxMKejwnadBEpGYEcictC9T+x9GNtGL77
2tqtpNBksMSCcbF6nJHWTX0CnCqH8aIlbAQg56JiMuDhT3JpmJd4xgLYp0SHpZeF
LbD4KHLGfuyMjF76V07KTjOK7cpOW2tgVMwDLik+24doO85K/js4RsS0oN2gaI4T
ViHvDM+YTlB3sfPcfjpaZF+zSQB04Q2ntfFJcB+AijxVBnlDAZw/Ue8ONwSPVrXl
y8No1OtRGX0p2f3EmOAgrQjiql5fqN3g9t6isO+hdt1dsuYr6OupeZ2V9+8mVaOG
x6y2l7RgOjbCdpWTDeLBAsilSdU5adzdBWDTpGY7sjsSNSskDItSc103XAqmENGy
zDSDGHkpSQ7H76Nmdy9PQ0FOpndYKehXujUxjF67IEiSHa5aELeLgL8b3VICoh2V
k4N0zbUx
=J7Oc
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---

Hi,

This was fixed in websockify 0.10.0+dfsg1-6 and is a duplicate of #1067330.

Cheers,

Thomas Goirand (zigo)--- End Message ---