Bug#1066215: marked as done (soundmodem: FTBFS: kisspkt.c:762:9: error: implicit declaration of function ‘fchmod’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Mon, 25 Mar 2024 05:17:29 +
with message-id 
and subject line Bug#1066215: fixed in soundmodem 0.20-7
has caused the Debian Bug report #1066215,
regarding soundmodem: FTBFS: kisspkt.c:762:9: error: implicit declaration of 
function ‘fchmod’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/libxml2  -I../matlib 
> -I../libmisc -I../directx/include -I../directx/include/directx6  -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 -O2 -c -o audiofilein.o audiofilein.c
> kisspkt.c: In function ‘kiss_input’:
> kisspkt.c:505:14: warning: pointer targets in assignment from ‘unsigned char 
> *’ to ‘char *’ differ in signedness [-Wpointer-sign]
>   505 | endp = chan->pkt.kiss.ibuf + chan->pkt.kiss.ibufptr;
>   |  ^
> kisspkt.c:514:38: warning: pointer targets in passing argument 2 of 
> ‘kiss_decode’ differ in signedness [-Wpointer-sign]
>   514 | kiss_decode(chan, cp1+1, cp2-cp1-1);
>   |   ~~~^~
>   |  |
>   |  char *
> kisspkt.c:451:62: note: expected ‘u_int8_t *’ {aka ‘unsigned char *’} but 
> argument is of type ‘char *’
>   451 | static void kiss_decode(struct modemchannel *chan, u_int8_t *b, int 
> len)
>   |~~^
> kisspkt.c: In function ‘p3dreceive’:
> kisspkt.c:597:22: warning: unused variable ‘i’ [-Wunused-variable]
>   597 | unsigned int i;
>   |  ^
> kisspkt.c: In function ‘pktinit’:
> kisspkt.c:762:9: error: implicit declaration of function ‘fchmod’ 
> [-Werror=implicit-function-declaration]
>   762 | fchmod(slave, 0660);
>   | ^~
> gcc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/libxml2  -I../matlib 
> -I../libmisc -I../directx/include -I../directx/include/directx6  -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 -O2 -c -o chansim.o chansim.c
> gcc -DHAVE_CONFIG_H -I. -I..  -I/usr/include/libxml2  -I../matlib 
> -I../libmisc -I../directx/include -I../directx/include/directx6  -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 -O2 -c -o ptt.o ptt.c
> audioio.c: In function ‘iotransmitstop’:
> audioio.c:669:25: warning: unused variable ‘j’ [-Wunused-variable]
>   669 | unsigned int i, j;
>   | ^
> audioio.c:669:22: warning: unused variable ‘i’ [-Wunused-variable]
>   669 | unsigned int i, j;
>   |  ^
> audioio.c:668:15: warning: unused variable ‘sbuf’ [-Wunused-variable]
>   668 | short sbuf[256];
>   |   ^~~~
> alsaio.c: In function ‘open_alsa’:
> alsaio.c:256:9: warning: ‘snd_pcm_sw_params_set_xfer_align’ is deprecated 
> [-Wdeprecated-declarations]
>   256 | err = snd_pcm_sw_params_set_xfer_align(pcm_handle, swparams, 
> 1);
>   | ^~~
> In file included from /usr/include/alsa/asoundlib.h:56,
>  from alsaio.c:55:
> /usr/include/alsa/pcm.h:1389:5: note: declared here
>  1389 | int snd_pcm_sw_params_set_xfer_align(snd_pcm_t *pcm, 
> snd_pcm_sw_params_t *params, snd_pcm_uframes_t val) 
> __attribute__((deprecated));
>   | ^~~~
> audioio.c: In function ‘iotxend’:
> audioio.c:293:9: warning: ignoring return value of ‘read’ declared 

Processed: Bug#1066215 marked as pending in soundmodem

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066215 [src:soundmodem] soundmodem: FTBFS: kisspkt.c:762:9: error: 
implicit declaration of function ‘fchmod’ 
[-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066215: marked as pending in soundmodem

[Tony Mancill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-hamradio-team/soundmodem/-/commit/a90a68aa72b15f277f08fbef758c08fbbeed04e8


Add patch for implicit-declaration warning (Closes: #1066215)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066215

Bug#1067630: fixed in emacs 1:29.3+1-1

[Max Nikulin]

On Mon, 25 Mar 2024 01:13:54 + Debian FTP Masters wrote:

Source: emacs
Source-Version: 1:29.3+1-1
Done: Rob Browning


Should this issue be reopened or be cloned to backport fixes to Emacs-28 
in Debian stable?

Processed: Re: emacs: release 29.3 fixes "several security vulnerabilities"

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:28.2+1-15
Bug #1067630 {Done: Rob Browning } [src:emacs] emacs: 
release 29.3 fixes "several security vulnerabilities"
Marked as found in versions emacs/1:28.2+1-15.

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

Bug#1067630: emacs: release 29.3 fixes "several security vulnerabilities"

[Max Nikulin]

Control: found -1 1:28.2+1-15

On Sun, 24 Mar 2024 16:53:55 -0300 David Bremner wrote:

** Arbitrary Lisp code is no longer evaluated as part of turning on Org mode.
This is for security reasons, to avoid evaluating malicious Lisp code.


Emacs-28 in Debian 12 bookworm requires the fix as well.

Source: org-mode
versions 9.5 and 9.6 till 9.6.23 are affected as well.


** LaTeX preview is now by default disabled for email attachments.
To get back previous insecure behavior, set the variable
'org--latex-preview-when-risky' to a non-nil value.


This one is rather old, so almost certainly even Emacs-26 is affected.
On the other hand its severity is not so high and only users having 
latex packages installed are affected.


See also
Ihor Radchenko to emacs-orgmode… [ANN] Emergency bugfix release: Org 
mode 9.6.23. Sun, 24 Mar 2024 17:16:50 +. 
https://list.orgmode.org/871q7zbldp.fsf@localhost



The fix for LaTeX evaluation requires Emacs 29.3 and will not work for
the earlier Emacs versions. If upgrading Emacs is not viable, as a
workaround, you can set `org-preview-latex-default-process' to 'verbatim
- this will disable LaTeX previews and avoid the vulnerability.

Bug#1067630: marked as done (emacs: release 29.3 fixes "several security vulnerabilities")

[Debian Bug Tracking System]

Your message dated Mon, 25 Mar 2024 01:13:54 +
with message-id 
and subject line Bug#1067630: fixed in emacs 1:29.3+1-1
has caused the Debian Bug report #1067630,
regarding emacs: release 29.3 fixes "several security vulnerabilities"
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.)


-- 
1067630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs
Version: 29.2+1-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team , 
debian-emac...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


According to the 29.3 release notes

* Changes in Emacs 29.3
Emacs 29.3 is an emergency bugfix release intended to fix several
security vulnerabilities described below.

** Arbitrary Lisp code is no longer evaluated as part of turning on Org mode.
This is for security reasons, to avoid evaluating malicious Lisp code.

** New buffer-local variable 'untrusted-content'.
When this is non-nil, Lisp programs should treat buffer contents with
extra caution.

** Gnus now treats inline MIME contents as untrusted.
To get back previous insecure behavior, 'untrusted-content' should be
reset to nil in the buffer.

** LaTeX preview is now by default disabled for email attachments.
To get back previous insecure behavior, set the variable
'org--latex-preview-when-risky' to a non-nil value.

** Org mode now considers contents of remote files to be untrusted.
Remote files are recognized by calling 'file-remote-p'.

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

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

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmYAhNIACgkQA0U5G1Wq
FSEANg//cukjqohXxNRpkxbutqHHvOB1aAr3d78jowjP3Yb9ozAArNxUjuJHEdSZ
5HCASm269atf5753maZILjyx3VmF/qUihyGjbbWjqMwNrQkkQiuXBfYn1F4R76/V
tyFile5NZVXIgYMykLb+rSHap6KMBnhjvLWSwNsDMuD8WB7OPH7KOI2xYqkUb7ue
SIgkCr0GJ+LaHOAYlRKkAYok4qwIfijLBw41Bt7t9Tawh+5d5nDkNPDphFOB+bG+
1hOQD8KVYWIceRK83wcDictSxbeTSo/cp6cEtVZX3yrDvBRbj3VKjKWL+0UIKfWO
iGWQYn622B7WbBIwEddQMmla+nxa5rxEN9VMEE8N5xcpI1lnL0lVSxw0jbT0FopJ
PmwFYmz1+pxB2fhRTv1T7ZTSAJS3BKQ9u2R8tuKO5ilSYp1zJrBBIazGPZ3Q+UBS
EoPh4hy5G4IZ3X3yaE9cX76fdDMMGPQ7HIinkw5A7KWb8zHse5m3+WG+iPNuveHU
GRwOB9pDDRTQrQVG8of2YVS0kLb9eu2jUD0sbi8As3P5Mr/gXHlrSgs5t1qg3HuA
Kkg7m7PAONZu0LBZNZsItm/V0weDqBdE+LZsa/1LUk3H+zvswhctlNLuZ7Y4mKqh
YpuwmZ2+cv1To2M/DKbBx2ngl5EiojF8hk5pGezcZ811NRFAQKc=
=BxE4
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: emacs
Source-Version: 1:29.3+1-1
Done: Rob Browning 

We believe that the bug you reported is fixed in the latest version of
emacs, 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.
Rob Browning  (supplier of updated emacs 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: Sun, 24 Mar 2024 16:30:50 -0500
Source: emacs
Architecture: source
Version: 1:29.3+1-1
Distribution: unstable
Urgency: high
Maintainer: Rob Browning 
Changed-By: Rob Browning 
Closes: 1067630
Changes:
 emacs (1:29.3+1-1) unstable; urgency=high
 .
   * Merge upstream version 29.3.  Thanks to David Bremner for the
 report. (Closes: 1067630)
 .
   * Update debian/copyright for 29.3
Checksums-Sha1:
 5c895babdcf06d88afcb131a7be36d4578b98aef 3018 emacs_29.3+1-1.dsc
 c5910d788335c197bd5fa6abbc6d5e6086df5487 29289064 emacs_29.3+1.orig.tar.xz
 6d2520132138fdd71b76241d07d80b3c7bc14877 63228 emacs_29.3+1-1.debian.tar.xz
 e7dc6c1f3bcd127805d028ea5e0a0f5762df5007 21743 emacs_29.3+1-1_amd64.buildinfo
Checksums-Sha256:
 6ef3ba5a9c23b37680d5dcef827cc85ebacec9fa839fefec5bc57d7c8e0ea9cc 3018 
emacs_29.3+1-1.dsc
 

Bug#1067359: marked as done (rbldnsd: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_configure] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 25 Mar 2024 01:55:52 +
with message-id 
and subject line Bug#1067359: fixed in rbldnsd 1.0~20210120-3
has caused the Debian Bug report #1067359,
regarding rbldnsd: FTBFS: make[1]: *** [debian/rules:8: 
override_dh_auto_configure] Error 1
to be marked as done.

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

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


-- 
1067359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rbldnsd
Version: 1.0~20210120-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 '/<>'
> CFLAGS="-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" LDFLAGS="-Wl,-z,relro -Wl,-z,now" \
>./configure --enable-systemd --enable-zlib
> configure: rbldnsd... 1.0pre (snapshot 20210120)
> checking for C compiler... gcc
> checking whether the C compiler (gcc -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)
>can produce executables... yes
> checking for ranlib... ranlib
> checking for stdint.h... yes
> checking whether C compiler defines __SIZEOF_POINTER__... yes
> checking byte order... little-endian
> checking for inline... yes
> checking for socklen_t... yes
> checking for libraries needed for connect()... not found
> configure: fatal: cannot find libraries needed for sockets
> make[1]: *** [debian/rules:8: override_dh_auto_configure] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/rbldnsd_1.0~20210120-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: rbldnsd
Source-Version: 1.0~20210120-3
Done: Marco d'Itri 

We believe that the bug you reported is fixed in the latest version of
rbldnsd, 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.
Marco d'Itri  (supplier of updated rbldnsd 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 00:13:30 +0100
Source: rbldnsd
Architecture: source
Version: 1.0~20210120-3
Distribution: unstable
Urgency: medium
Maintainer: Marco d'Itri 
Changed-By: Marco d'Itri 
Closes: 1067359
Changes:
 rbldnsd (1.0~20210120-3) unstable; urgency=medium
 .
   * Add the Debian patch configure_fix to disable some useless tests in
 the configure script which fail with modern gcc. (Closes: #1067359)
Checksums-Sha1:
 03316f11b94f0eca4d39c84cd33137cd4f3c70b6 1332 rbldnsd_1.0~20210120-3.dsc
 07b94c16de91ad62bba132f1292b848e2c9f1a09 18036 
rbldnsd_1.0~20210120-3.debian.tar.xz
 d527cb32ecb32776ba7f0be5dd7a9e06bb8220a4 6267 
rbldnsd_1.0~20210120-3_amd64.buildinfo
Checksums-Sha256:
 9d13c1732f3a3bd64b25034f588e31977b216a760f7d0f978f7079ad66069971 1332 
rbldnsd_1.0~20210120-3.dsc
 b70194a4a24634f4737738ac7b81396e9ccc7f90f41466c42ea5f0ef4f3bab6e 18036 
rbldnsd_1.0~20210120-3.debian.tar.xz
 8091852003c9b7f955bbce47f5e929ac9b16766dea64e3d62d41a4b93102d883 6267 

Bug#1063971: marked as done (python-dateutil: autopkgtest regression with pytest 8)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 23:14:52 +
with message-id 
and subject line Bug#1063971: fixed in python-dateutil 2.9.0-1
has caused the Debian Bug report #1063971,
regarding python-dateutil: autopkgtest regression with pytest 8
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.)


-- 
1063971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-dateutil
Version: 2.8.2-3
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pytest-8

Dear maintainer,

your package has a autopkgtest regression with pytest 8.

Typically, packages will start failing if they

- have deprecation warnings of type PytestRemovedIn8Warning, or

- assume a particular pytest stdout/stderr output which might have
changed, or

- rely on implementation details of the pytest test collector, in
particular the pytest.Package class, which has been redesigned for
pytest 8.

Please refer to the upstream changelog [1] for a complete list of
breaking changes and the pytest (pseudo-)excuses [2] related to your
package for details of the regression.

It is possible that the autopkgtest regression is not directly caused
by python-dateutil, but by one of its dependencies. In that case,
feel free to reassign the bug and mark your package as affected, but
do not close the bug until the autopkgtest passes.

Cheers Timo

[1]
https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023-
12-30 [2]
https://qa.debian.org/excuses.php?experimental=1=pytest
--- End Message ---
--- Begin Message ---
Source: python-dateutil
Source-Version: 2.9.0-1
Done: Julian Gilbey 

We believe that the bug you reported is fixed in the latest version of
python-dateutil, 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.
Julian Gilbey  (supplier of updated python-dateutil 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: Sun, 24 Mar 2024 21:28:04 +
Source: python-dateutil
Architecture: source
Version: 2.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julian Gilbey 
Closes: 1063971
Changes:
 python-dateutil (2.9.0-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Add patch that should solve some DeprecationWarning in Python3.12
 which affects: #1058414 (of package python-itsdangerous)
 The patch is *not* applied since it is not sufficient and breaks several
 other tests in dateutil
   * Test all supported Python3 versions in autopkgtest (to show the
 DeprecationWarning for Python3.12)
 .
   [ Julian Gilbey ]
   * New upstream version (closes: #1063971)
   * Refresh patches
   * Remove ancient Breaks field from d/control and update
 Standards-Version
   * Remove unused upstream signing-key (no longer appears to be signed
 upstream)
   * Add d/upstream/metadata file
Checksums-Sha1:
 3ae76fd4f68735d846c01c450765c434c6ace411 2282 python-dateutil_2.9.0-1.dsc
 44229ab0040a8cdd7baaa81de8d3a42e6c4af5f9 342990 
python-dateutil_2.9.0.orig.tar.gz
 6bed6bec9869f307877a66146e5c2a988dd9225b 6860 
python-dateutil_2.9.0-1.debian.tar.xz
 225409d9b66be81f8cb9a4570d40d124102dfa59 8013 
python-dateutil_2.9.0-1_amd64.buildinfo
Checksums-Sha256:
 d323e0ee2b04cce8f8e82636d5890e8ae89442f57462a1f1d5e5f7820983e19b 2282 
python-dateutil_2.9.0-1.dsc
 78e73e19c63f5b20ffa567001531680d939dc042bf7850431877645523c66709 342990 
python-dateutil_2.9.0.orig.tar.gz
 aace3c970c3243288cd5ac29050c2f0de751282023a1dd12cc0f6d5783c40703 6860 
python-dateutil_2.9.0-1.debian.tar.xz
 498d279d2866723ad6fd6bb07049e3a9741d4d811c941cc8e67b350be9ba02f5 8013 
python-dateutil_2.9.0-1_amd64.buildinfo
Files:
 9ef680947691871ebc6cc39cea34d0a6 2282 python optional 
python-dateutil_2.9.0-1.dsc
 f4888298c0f2d5239c85c6457455a975 342990 python optional 
python-dateutil_2.9.0.orig.tar.gz
 4b32f425ad2934be47b4a58890343704 6860 python optional 
python-dateutil_2.9.0-1.debian.tar.xz
 ea5dddb59441214dd88e7cc58f2c1e23 8013 python optional 
python-dateutil_2.9.0-1_amd64.buildinfo

-BEGIN PGP 

Bug#1067604: marked as done (src:libcdk5: autopkgtest regression, tests the old version and more issues)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 22:47:35 +
with message-id 
and subject line Bug#1067604: fixed in libcdk5 5.0.20230201-3
has caused the Debian Bug report #1067604,
regarding src:libcdk5: autopkgtest regression, tests the old version and more 
issues
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.)


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

Source: libcdk5
Version: 5.0.20230201-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report. I note that the version it tests against 
is the previous version.


On top of that, this test is really, really superficial, please mark it 
as such [2]. Also, autopkgtest is supposed to be tested against the 
*installed* packages. It doesn't look like your test needs a build, can 
you please remove the "build-needed" restriction (it's probably what's 
causing the migration test to fail in view of the time_t)?


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
[2] https://release.debian.org/testing/rc_policy.txt section 6(a) (bottom)

https://ci.debian.net/packages/libc/libcdk5/unstable/amd64/44302393/

 94s autopkgtest [12:22:08]: test command1: [ "$(dash cdk-config 
--version)" == '5.0.20180306' ]


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libcdk5
Source-Version: 5.0.20230201-3
Done: Steve M. Robbins 

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

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

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated libcdk5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Mar 2024 16:12:29 -0500
Source: libcdk5
Architecture: source
Version: 5.0.20230201-3
Distribution: unstable
Urgency: medium
Maintainer: Steve M. Robbins 
Changed-By: Steve M. Robbins 
Closes: 1067604
Changes:
 libcdk5 (5.0.20230201-3) unstable; urgency=medium
 .
   [ Steve Robbins ]
   * [39247d6] Remove useless autopkgtest.  Closes: #1067604.
Checksums-Sha1:
 327d88eaff1e9acde9c20b68ef7cb9b3a0c26020 2322 libcdk5_5.0.20230201-3.dsc
 30d966d9eb486c757ad020bd905196257aa9c437 15440 
libcdk5_5.0.20230201-3.debian.tar.xz
 8678cbdf7f52e8ef442759e8bd6d7b59223fa315 6713 
libcdk5_5.0.20230201-3_source.buildinfo
Checksums-Sha256:
 024fe2c56cee35c759ffdb4e58d06d233c8b336281d6dce9ba06f7ec3a7b7058 2322 
libcdk5_5.0.20230201-3.dsc
 24e67f431f21677cfcfd7cf64d4746992d802ceb85ed5f0bd928f37cbbd10109 15440 
libcdk5_5.0.20230201-3.debian.tar.xz
 e4c26f3275b2c53a85ced2370661132073b4cfab4144323109213ad05b7db2f5 6713 
libcdk5_5.0.20230201-3_source.buildinfo
Files:
 0bffb5a07b50ddc7f7b3fde9354542ef 2322 libs optional libcdk5_5.0.20230201-3.dsc
 2f9743025a54c1b8f2beeb380b1e5814 15440 libs optional 
libcdk5_5.0.20230201-3.debian.tar.xz
 674df38f894e918302960cc41ff04e32 6713 libs optional 
libcdk5_5.0.20230201-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEy89k8fa3rclNjyokyeVeL63I9LkFAmYAmTAPHHNtckBkZWJp
YW4ub3JnAAoJEMnlXi+tyPS5WDkP/jjUUp17OtoWj5P76FDrBpWaCVDjLVufbp1w
4T+DzHyP2x5IFZB4PpSzxyrvuv9mpxIoKqB7rmzHlZkGXwMQQX+vyGkNjekJK8Q4
U01iZMVZKa9/dpddJ4LJVdIteGjtprIPCSczsk0UhxkEgDFV/KUi1IhABiF8nJb/
wfW3WKHNC4/ylBeFyM5HTAhsCxspvO74vw2rMZwQ1UkW5qmx9OYCHhGzylVKkGRp
GDY2mI+jfoyUdDMBX0bWDZA83tvuJvNX0VYjqqeC0VsOZinCAGeQWt7bLCLcqbXy
tfNNQa7wd9lfkrk41TWOTkKbpjEeYfsdgA4Ytwbg4HXySQFn6yq7HdDXHi3MEBkd
9F/obJNB7G3TcBqvZKicnACv5PZ2EVfAhpLztO6C22sRSVoN/Afn/fRbXQL3pCUM
DbqTtwWt27gGRsC3cWokq4kl3HoNYf5TrDgZJZpabUbnJLQyT8277nd9ZNRakIyy

Bug#1067115: marked as done (gross: CVE-2023-52159)

[Debian Bug Tracking System]

Your message dated Mon, 25 Mar 2024 01:27:41 +
with message-id 
and subject line Bug#1067115: fixed in gross 1.0.2-4.1
has caused the Debian Bug report #1067115,
regarding gross: CVE-2023-52159
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.)


-- 
1067115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gross
Version: 1.0.2-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for gross.

CVE-2023-52159[0]:
| A stack-based buffer overflow vulnerability in gross 0.9.3 through
| 1.x before 1.0.4 allows remote attackers to trigger a denial of
| service (grossd daemon crash) or potentially execute arbitrary code
| in grossd via crafted SMTP transaction parameters that cause an
| incorrect strncat for a log entry.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-52159
https://www.cve.org/CVERecord?id=CVE-2023-52159
[1] 
https://codeberg.org/bizdelnick/gross/wiki/Known-vulnerabilities#cve-2023-52159

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gross
Source-Version: 1.0.2-4.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
gross, 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.
Adrian Bunk  (supplier of updated gross 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: Sat, 23 Mar 2024 23:23:34 +0200
Source: gross
Architecture: source
Version: 1.0.2-4.1
Distribution: unstable
Urgency: high
Maintainer: Antonio Radici 
Changed-By: Adrian Bunk 
Closes: 1067115
Changes:
 gross (1.0.2-4.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * CVE-2023-52159: Stack-based buffer overflow (Closes: #1067115)
Checksums-Sha1:
 29c60c2c7df7f799c095ed39d9396697946d450e 1837 gross_1.0.2-4.1.dsc
 4f41f1324bf79575a04b7d4c0628dc093d88373d 6988 gross_1.0.2-4.1.debian.tar.xz
Checksums-Sha256:
 21539be0b6a4d6caf71599789ac51f457fb55ecd20b9505f1bb53522850f762e 1837 
gross_1.0.2-4.1.dsc
 debd41349767afc70ad4467ef88f1f883b3274107a178aae26f693307325e36d 6988 
gross_1.0.2-4.1.debian.tar.xz
Files:
 b9377c84fa10687c5f512b26b9b73e8c 1837 mail extra gross_1.0.2-4.1.dsc
 63477089d532cc0c9892e073aa8755b5 6988 mail extra gross_1.0.2-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmX/TR8ACgkQiNJCh6LY
mLFbihAAwBP48VQCh3bt+kSBra0Y53eK4ycJfPcv9sTQCj0jaENZ/7tR7ZuUQ6FF
OJfHMLTtnvOYFEMkeVa0HHPm+D23uapu9J8t9DHpcKR20LmmTPx8GX79Uuzwo/rn
laVye8qakNh8R7QQP2ZFh28+2eJTljiE7YBPKO+6ADZAFiryPyMITuS/7MOYToLs
mheBl3A+cT3HqEh67nMF1AWOIWIDXZflEQdH3cRGgByKBROor9JOVa2blURn12KV
LwapLeEYi5m963nUDAhb431BGxUHtU7Bb3sTJEMA1l6OLLEcaIS0rvsPKRes8IfO
Mup2Kh3/ckgiw/D0Mu+eHh47Vn50+9DRD+EOUvixdDogHGbGWV/7wuLJ8fUk7Cu5
HnNDG5fnCQFpmNg3gp7e0okHuXDgaJfvhD1BDt65y4DGyuzWb0mdR4NhISHCYIF0
4MuiKoTERfmRd5NbS6XmOq0wOs7GboI04RBwP44jiOnaPjjBcDNgdsrRNVAxfN4f
i+BPnVdJ2N+yx3xSV67XSxkB4vuimJhgGD9jlYmdrS7d82lnxW3BBlxkB35NCVn4
Gad37Bba+0k5+MGxJ7ZvoZlTAoGLOfepwVnG0oSrrJoZ2WebiRPfP3kWKqyG2pX9
zu13NFKDpfwQTt9UiTEtKWG+Zgf4+/wLc9axtYMDZgmdPLBVfeU=
=yaXr
-END PGP SIGNATURE-



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

Bug#1067491: time_t transition upgrade: failed systemctl call in preinst due to missing pre-dependencies

[Otto Kekäläinen]

Thanks Wouter for reporting this and Michael for submitting a merge
request for a potential fix!

The libcrypto.so.3 is from the OpenSSL package. In your upgrade case
it seems to be switching from
libssl3 [i386] to libssl3t64 [i386]. Your MariaDB packages are amd64.
This makes me wonder what is actually going on.

Were you able to recover? Can you now run manually 'systemctl --system
daemon-reload'?

This is the line dpkg was most likely running:
https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/mariadb-server.postinst#L289

Bug#1066983: monopd: Fails to start monopd.service

[Markus Koschany]

Sylvain Rochet wrote:
> Actually, the main problem is /lib/systemd/system/monopd.socket which 
> set Accept=yes while monopd needs Accept=no (which is the default value).

I wonder if monopd needs a systemd socket file at all and if we should disable
the service after the installation. We have been using this setting since the
introduction of systemd. If monopd runs with Accept=no then we also don't need
a service template file. At some point I also noticed the same warning as
Shriram

"monopd.socket is a disabled or a static unit not running, not starting it." 
and then followed [1] and added the required template file.

I have been running monopd for the past decade and I also suspect the daemon is
affected by some bugs which might be remotely exploitable. Since users usually
don't need the monopd server anyway, if they want to play a game, they should
make a conscious decision to start it if they want to use it locally. For a
simple internet game, the daemon is not required.

[1] https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html


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

Bug#1066198: marked as done (gbatnav: FTBFS: gbnserver.c:411:24: error: implicit declaration of function ‘net_listen’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Mon, 25 Mar 2024 01:18:57 +
with message-id 
and subject line Bug#1066198: fixed in gbatnav 1.0.4cvs20051004-7
has caused the Debian Bug report #1066198,
regarding gbatnav: FTBFS: gbnserver.c:411:24: error: implicit declaration of 
function ‘net_listen’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I.. -I./../common -I./../intl 
> -DGNOMELOCALEDIR=\""/usr/share/locale"\" -I/usr/include  
> -I./../gbnclient/pixmaps -DBINDIR=\"/usr/games\" -I/usr/include/goocanvas-2.0 
> -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread   -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 
> -o batnavggz.o batnavggz.c
> /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas --strict --dry-run  
> --schema-file=net.sf.batnav.gbnserver.gschema.xml && mkdir -p . && touch 
> net.sf.batnav.gbnserver.gschema.valid
> gbnserver.c: In function ‘main_loop’:
> gbnserver.c:411:24: error: implicit declaration of function ‘net_listen’ 
> [-Werror=implicit-function-declaration]
>   411 | usuario.sock = net_listen(usuario.server_name,usuario.port);
>   |^~
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:537: gbnserver.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/gbatnav_1.0.4cvs20051004-6_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: gbatnav
Source-Version: 1.0.4cvs20051004-7
Done: Ying-Chun Liu (PaulLiu) 

We believe that the bug you reported is fixed in the latest version of
gbatnav, 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.
Ying-Chun Liu (PaulLiu)  (supplier of updated gbatnav 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Mar 2024 06:58:52 +0800
Source: gbatnav
Architecture: source
Version: 1.0.4cvs20051004-7
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: 

Processed: let these show up on buildd.d.o overview page

[Debian Bug Tracking System]

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

> tags 883308 + ftbfs
Bug #883308 [libseccomp2] libseccomp2 is missing support for ia64, alpha, sh4, 
sparc64, m68k
Added tag(s) ftbfs.
> tags 1067055 + ftbfs
Bug #1067055 [src:openmpi] openmpi: error: implicit declaration of function 
'OPAL_THREAD_ADD_FETCH64'
Ignoring request to alter tags of bug #1067055 to the same tags previously set
> tags 1067207 + ftbfs
Bug #1067207 [src:mesa] mesa: switch statement too large, might need 
-mlong-jump-table-offsets
Ignoring request to alter tags of bug #1067207 to the same tags previously set
> tags 1067447 + ftbfs
Bug #1067447 [src:jackd2] jackd2: patch to fix ftbfs on m68k; jack{1,2}: 
unneeded libffado-dev B-D on some arches
Added tag(s) ftbfs.
> tags 1067577 + ftbfs
Bug #1067577 [src:sysprof] sysprof: B-D on libunwind-dev which is not generally 
available
Added tag(s) ftbfs.
> tags 1067582 + ftbfs
Bug #1067582 [src:gnuplot] gnuplot: please provide a profile to break B-D cycle
Added tag(s) ftbfs.
> tags 1067613 + ftbfs
Bug #1067613 [src:openjdk-11] openjdk-11: FTBFS on alpha: d/rules references 
deleted patch (trivial fix)
Added tag(s) ftbfs.
> tags 1067643 + ftbfs
Bug #1067643 [src:webkit2gtk] webkit2gtk: please use architecture whitelist for 
libseccomp-dev B-D
Added tag(s) ftbfs.
> tags 1067644 + ftbfs
Bug #1067644 [src:gcc-12] gcc-12: BD-Uninstallable on m68k due to gnat-11 vs 
gnat-12
Added tag(s) ftbfs.
> tags 1067646 + ftbfs
Bug #1067646 [src:llvm-toolchain-17] llvm-toolchain-17: please enable m68k build
Added tag(s) ftbfs.
> tags 1067647 + ftbfs
Bug #1067647 [src:google-perftools] google-perftools: FTBFS: #error Could not 
determine cache line length - unknown architecture
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1067055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067055
1067207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067207
1067447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067447
1067577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067577
1067582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067582
1067613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067613
1067643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067643
1067644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067644
1067646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067646
1067647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067647
883308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1066198: gbatnav: FTBFS: gbnserver.c:411:24: error: implicit declaration of function ‘net_listen’ [-Werror=implicit-function-declaration]

[Ying-Chun Liu (PaulLiu)]

Fixed. Patch as attachment.
Description: Fix FTBFS due to -Werror=implicit-function-declaration
Bug-Debian: https://bugs.debian.org/1066198
Author: Ying-Chun Liu (PaulLiu) 
Last-Update: 2024-03-25
Index: gbatnav-1.0.4cvs20051004/gbnserver/gbnserver.c
===
--- gbatnav-1.0.4cvs20051004.orig/gbnserver/gbnserver.c
+++ gbatnav-1.0.4cvs20051004/gbnserver/gbnserver.c
@@ -44,6 +44,7 @@
 #include "bnwrite.h"
 #include "batnavggz.h"
 #include "common.h"
+#include "net.h"
 
 struct st_datos usuario;
 
Index: gbatnav-1.0.4cvs20051004/gbnclient/sendmsg.c
===
--- gbatnav-1.0.4cvs20051004.orig/gbnclient/sendmsg.c
+++ gbatnav-1.0.4cvs20051004/gbnclient/sendmsg.c
@@ -6,6 +6,7 @@
 #include "pantalla.h"
 #include "gbnclient.h"
 #include "bnwrite.h"
+#include "net.h"
 
 void inputline_return(GtkWidget *w, gpointer data)
 {
Index: gbatnav-1.0.4cvs20051004/gbnclient/gbnclient.c
===
--- gbatnav-1.0.4cvs20051004.orig/gbnclient/gbnclient.c
+++ gbatnav-1.0.4cvs20051004/gbnclient/gbnclient.c
@@ -39,6 +39,8 @@
 #include "bnwrite.h"
 #include "version.h"
 #include "g_connect.h"
+#include "common.h"
+#include "net.h"
 
 struct usuario usuario;
 GSettings *settings;


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: tagging 1067618, tagging 1067624, tagging 1067596, tagging 1067623, tagging 1067609, tagging 1067547 ...

[Debian Bug Tracking System]

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

> tags 1067618 + sid trixie
Bug #1067618 [src:whitedune] FTBFS: error: implicit declaration of function 
'yyerror'; did you mean 'yyerrok'? [-Werror=implicit-function-declaration]
Added tag(s) trixie and sid.
> tags 1067624 + sid trixie
Bug #1067624 {Done: Thorsten Glaser } [src:antimicro] FTBFS: 
error: ‘struct input_event’ has no member named ‘time’
Added tag(s) sid and trixie.
> tags 1067596 + sid trixie
Bug #1067596 [src:xf86-input-multitouch] FTBFS: error: ‘const struct 
input_event’ has no member named ‘time’
Added tag(s) trixie and sid.
> tags 1067623 + sid trixie
Bug #1067623 [src:acm] FTBFS: error: format ‘%ld’ expects argument of type 
‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}
Added tag(s) trixie and sid.
> tags 1067609 + sid trixie
Bug #1067609 {Done: Jeremy Bícha } [gbrainy] gbrainy: Avoid 
hardcoded libcanberra-gtk3-0 build-depends, use libcanberra-gtk3-dev
Added tag(s) sid and trixie.
> tags 1067547 + sid trixie
Bug #1067547 [src:wmweather+] FTBFS: "vsnprintf is so broken we can't 
compensate. Sorry."
Added tag(s) trixie and sid.
> tags 1050523 + sid trixie
Bug #1050523 {Done: Anthony Fok } [src:dh-make-golang] 
dh-make-golang: fails to determine dependencies
Added tag(s) trixie and sid.
> notfound 1067223 1.10-2
Bug #1067223 [src:libflorist] libflorist ftbfs on time_t64 architectures
The source 'libflorist' and version '1.10-2' do not appear to match any binary 
packages
No longer marked as found in versions libflorist/1.10-2.
> found 1067223 2022.0.1~20220616-5
Bug #1067223 [src:libflorist] libflorist ftbfs on time_t64 architectures
Marked as found in versions libflorist/2022.0.1~20220616-5.
> tags 1067223 - sid trixie
Bug #1067223 [src:libflorist] libflorist ftbfs on time_t64 architectures
Removed tag(s) sid and trixie.
> tags 1067367 - sid trixie
Bug #1067367 [src:mathgl] mathgl: FTBFS: debian/tests/run-tests: 37: 
python3.12: not found
Removed tag(s) sid and trixie.
> tags 1067304 - sid trixie
Bug #1067304 [src:gmsh] gmsh: FTBFS: unsatisfiable build-dependencies
Removed tag(s) trixie and sid.
> tags 1067224 - sid trixie
Bug #1067224 [src:ahven] libahven ftbfs on time_t64 architectures
Removed tag(s) trixie and sid.
> tags 1067221 - sid trixie
Bug #1067221 [src:libtemplates-parser] libtemplates-parser ftbfs on time_t64 
architectures
Removed tag(s) sid and trixie.
> tags 1067219 - sid trixie
Bug #1067219 [src:adacgi] adacgi ftbfs on time_t64 architectures
Removed tag(s) sid and trixie.
> tags 1067139 + sid trixie
Bug #1067139 [src:matplotlib] matplotlib: missing depend on python3-all for 
autopkgtest
Added tag(s) trixie and sid.
> notfixed 1065915 1.0.0-3
Bug #1065915 {Done: Matthias Klose } [src:pdfkit] pdfkit: 
Please drop dependencies on python3-distutils
No longer marked as fixed in versions 1.0.0-3.
> fixed 1065915 1.0.0-4
Bug #1065915 {Done: Matthias Klose } [src:pdfkit] pdfkit: 
Please drop dependencies on python3-distutils
Marked as fixed in versions pdfkit/1.0.0-4.
> notfound 1066102 1.1.1-4
Bug #1066102 {Done: David Kunz } [icingaweb2-module-nagvis] 
icingaweb2-module-nagvis: [INTL:de] updated German po file translation
No longer marked as found in versions icingaweb2-module-nagvis/1.1.1-4.
> reassign 1038301 src:runit 2.1.2-54
Bug #1038301 {Done: Lorenzo Puliti } [runit-systemd] 
please drop transitional package runit-systemd from src:runit
Bug reassigned from package 'runit-systemd' to 'src:runit'.
No longer marked as found in versions runit/2.1.2-54.
No longer marked as fixed in versions runit/2.1.2-57.
Bug #1038301 {Done: Lorenzo Puliti } [src:runit] please 
drop transitional package runit-systemd from src:runit
Marked as found in versions runit/2.1.2-54.
> fixed 1038301 2.1.2-57
Bug #1038301 {Done: Lorenzo Puliti } [src:runit] please 
drop transitional package runit-systemd from src:runit
Marked as fixed in versions runit/2.1.2-57.
> reassign 1038304 src:chipmunk 7.0.3-5
Bug #1038304 {Done: Stephen Kitt } [chipmunk-dev] please drop 
transitional package chipmunk-dev from src:chipmunk
Bug reassigned from package 'chipmunk-dev' to 'src:chipmunk'.
No longer marked as found in versions chipmunk/7.0.3-5.
No longer marked as fixed in versions chipmunk/7.0.3-6.
Bug #1038304 {Done: Stephen Kitt } [src:chipmunk] please drop 
transitional package chipmunk-dev from src:chipmunk
Marked as found in versions chipmunk/7.0.3-5.
> fixed 1038304 7.0.3-6
Bug #1038304 {Done: Stephen Kitt } [src:chipmunk] please drop 
transitional package chipmunk-dev from src:chipmunk
Marked as fixed in versions chipmunk/7.0.3-6.
> reassign 1016379 src:nfft 3.5.3-1
Bug #1016379 {Done: Andreas Tille } [libnfft3-double2] nfft: 
soname changes without package renaming and library transition
Bug reassigned from package 'libnfft3-double2' to 'src:nfft'.
No longer marked as found in versions nfft/3.5.3-1.
No longer marked as fixed in versions nfft/3.5.3-2.
Bug #1016379 {Done: Andreas Tille } [src:nfft] nfft: soname 
changes without 

Bug#1063969: marked as done (pytest-sugar: autopkgtest regression with pytest 8)

[Debian Bug Tracking System]

Your message dated Mon, 25 Mar 2024 00:15:35 +0100
with message-id 

and subject line Re: Accepted pytest-sugar 1.0.0-1 (source) into unstable
has caused the Debian Bug report #1063969,
regarding pytest-sugar: autopkgtest regression with pytest 8
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.)


-- 
1063969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pytest-sugar
Version: 0.9.7-1
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pytest-8

Dear maintainer,

your package has a autopkgtest regression with pytest 8.

Typically, packages will start failing if they

- have deprecation warnings of type PytestRemovedIn8Warning, or

- assume a particular pytest stdout/stderr output which might have
changed, or

- rely on implementation details of the pytest test collector, in
particular the pytest.Package class, which has been redesigned for
pytest 8.

Please refer to the upstream changelog [1] for a complete list of
breaking changes and the pytest (pseudo-)excuses [2] related to your
package for details of the regression.

It is possible that the autopkgtest regression is not directly caused
by pytest-sugar, but by one of its dependencies. In that case, feel
free to reassign the bug and mark your package as affected, but do
not close the bug until the autopkgtest passes.

Cheers Timo

[1]
https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023-
12-30 [2]
https://qa.debian.org/excuses.php?experimental=1=pytest
--- End Message ---
--- Begin Message ---

Version: 1.0.0-1
Done: Edward Betts 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 01 Mar 2024 10:46:22 +
Source: pytest-sugar
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Edward Betts 
Changes:
 pytest-sugar (1.0.0-1) unstable; urgency=medium
 .
   * New upstream release.
Checksums-Sha1:
 c83f1d58926b36901964aa19f0baf5040fd8c72a 2115 pytest-sugar_1.0.0-1.dsc
 294e9f8acf2601949a33a2504a92be359808c415 14992 pytest-sugar_1.0.0.orig.tar.gz
 ed7c4cb30a263659978496710ef2bf6f41c3c867 3156 
pytest-sugar_1.0.0-1.debian.tar.xz
 fab4ed8d10035f606fb037977068666ee3a4723a 8503 
pytest-sugar_1.0.0-1_source.buildinfo
Checksums-Sha256:
 6e56bcee420ff0acbcba2ac334217144627808167e661cad093a58333924b740 2115 
pytest-sugar_1.0.0-1.dsc
 6422e83258f5b0c04ce7c632176c7732cab5fdb909cb39cca5c9139f81276c0a 14992 
pytest-sugar_1.0.0.orig.tar.gz
 22493ab761e2ecfc97a4a6295d80162d89e9803425e14b02fcbf9dac79508577 3156 
pytest-sugar_1.0.0-1.debian.tar.xz
 a3cf91d03587265ea0fa359a1cd33e9be99187f2b2a1d986c06f6018d072e11e 8503 
pytest-sugar_1.0.0-1_source.buildinfo
Files:
 e1caab2e7c203308c1b48f8bfa963eb2 2115 python optional pytest-sugar_1.0.0-1.dsc
 f74f51203bffda323ff57a307fe821bd 14992 python optional 
pytest-sugar_1.0.0.orig.tar.gz
 7bd3ab66e2192a2f6e5b85dcb49bacdd 3156 python optional 
pytest-sugar_1.0.0-1.debian.tar.xz
 bade834cb2a082fb5bb2ab1f0432bc5f 8503 python optional 
pytest-sugar_1.0.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+4rPp4xyYInDitAmlgWhCYxjuSoFAmXhusQACgkQlgWhCYxj
uSrLlA//Wfk2BZXAFoxaNaj4/r3HoFRJXxAnFbG/EO1fluGbFOxgIIHN30vLPTdg
yjpLGGwfQZ9FU/vtsJ47LoG5YQiRVhsrxg4lSAabXz8kccTztK7JL0DbAbrHhr04
8d9p9D5Y+mGm9Pn6irjyqtVupUqiagb8pAnHdEOKHj+cDyhcm3hq/tVxeT0KZ9pz
1RiGlY4DeLqo0fh+o2G1pK59okgBRAQY6Koukt6d8FLSuuF4uB0cKwMaq7o+u9us
uek6d6s3R22msBCePTvsPV7p6kCvMKNHQhjBZwDPYrdc0/UxtvHPDeHDft0p587E
1zjVfI/ULSK6W7XTnhh+dJWEWh3hhDhG+JXwmC7SsAP8zKI7O8+gwqSolEKJDOHQ
2ZO8cXmPWCv88gJqMa8eyGriz3TKLDmPWUzO5E8vEa3kWTsIR+PxIq3AwXjPmtY7
1dJly6sXNlJe+EGpAtNnXyHOD6qDsg7Oe0pXfImOcklGWUCd/VzEiV1hK6mxV92b
Xp8zCxx35B4k/7CWnGxMNIcdsur9exsxU3IbH9DdEuTdpUmCZQ/3JkBcsz3fEc4z
42xdwlZT39qoGQN3uF4JNi1NeZCRkOxbbnJ91JEUnpPXFn5fYGVx8xYSSQg8ujpk
n2eefSSQIPSAtTCDztParGt4NAc68eFaYmvu9hNjvCmtFVPFFOU=
=SS6y
-END PGP SIGNATURE-


--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


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

Processed: Re: pytest-services: autopkgtest regression with pytest 8

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-pytest 8.0.1-1
Bug #1063965 [pytest-services] pytest-services: autopkgtest regression with 
pytest 8
Bug reassigned from package 'pytest-services' to 'python3-pytest'.
No longer marked as found in versions 2.2.1+ds-3.
Ignoring request to alter fixed versions of bug #1063965 to the same values 
previously set
Bug #1063965 [python3-pytest] pytest-services: autopkgtest regression with 
pytest 8
Marked as found in versions pytest/8.0.1-1.
> close -1 8.1.1-1
Bug #1063965 [python3-pytest] pytest-services: autopkgtest regression with 
pytest 8
Marked as fixed in versions pytest/8.1.1-1.
Bug #1063965 [python3-pytest] pytest-services: autopkgtest regression with 
pytest 8
Marked Bug as done

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

Bug#1063965: pytest-services: autopkgtest regression with pytest 8

[Timo Röhling]

Control: reassign -1 python3-pytest 8.0.1-1
Control: close -1 8.1.1-1

It looks like this issue was caused by a regression in pytest 8.0 
and is fixed now.


On Thu, 15 Feb 2024 11:36:07 +0100 roehl...@debian.org wrote:

Package: pytest-services
Version: 2.2.1+ds-3
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pytest-8

Dear maintainer,

your package has a autopkgtest regression with pytest 8.

Typically, packages will start failing if they

- have deprecation warnings of type PytestRemovedIn8Warning, or

- assume a particular pytest stdout/stderr output which might have
changed, or

- rely on implementation details of the pytest test collector, in
particular the pytest.Package class, which has been redesigned for
pytest 8.

Please refer to the upstream changelog [1] for a complete list of
breaking changes and the pytest (pseudo-)excuses [2] related to your
package for details of the regression.

It is possible that the autopkgtest regression is not directly caused
by pytest-services, but by one of its dependencies. In that case,
feel free to reassign the bug and mark your package as affected, but
do not close the bug until the autopkgtest passes.

Cheers Timo

[1]
https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023-
12-30 [2]
https://qa.debian.org/excuses.php?experimental=1=pytest




--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Processed: Re: python-b2sdk: autopkgtest regression with pytest 8

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-pytest 8.0.1-1
Bug #1063960 [python-b2sdk] python-b2sdk: autopkgtest regression with pytest 8
Bug reassigned from package 'python-b2sdk' to 'python3-pytest'.
No longer marked as found in versions 1.17.3-2.
Ignoring request to alter fixed versions of bug #1063960 to the same values 
previously set
Bug #1063960 [python3-pytest] python-b2sdk: autopkgtest regression with pytest 8
Marked as found in versions pytest/8.0.1-1.
> close -1 8.1.1-1
Bug #1063960 [python3-pytest] python-b2sdk: autopkgtest regression with pytest 8
Marked as fixed in versions pytest/8.1.1-1.
Bug #1063960 [python3-pytest] python-b2sdk: autopkgtest regression with pytest 8
Marked Bug as done

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

Bug#1063960: python-b2sdk: autopkgtest regression with pytest 8

[Timo Röhling]

Control: reassign -1 python3-pytest 8.0.1-1
Control: close -1 8.1.1-1

As it turns out, there was a regression in pytest 8.0 which has been 
fixed in pytest 8.1


Cheers
Timo

On Thu, 15 Feb 2024 11:36:15 +0100 roehl...@debian.org wrote:

Package: python-b2sdk
Version: 1.17.3-2
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pytest-8

Dear maintainer,

your package has a autopkgtest regression with pytest 8.

Typically, packages will start failing if they

- have deprecation warnings of type PytestRemovedIn8Warning, or

- assume a particular pytest stdout/stderr output which might have
changed, or

- rely on implementation details of the pytest test collector, in
particular the pytest.Package class, which has been redesigned for
pytest 8.

Please refer to the upstream changelog [1] for a complete list of
breaking changes and the pytest (pseudo-)excuses [2] related to your
package for details of the regression.

It is possible that the autopkgtest regression is not directly caused
by python-b2sdk, but by one of its dependencies. In that case, feel
free to reassign the bug and mark your package as affected, but do
not close the bug until the autopkgtest passes.

Cheers Timo

[1]
https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023-
12-30 [2]
https://qa.debian.org/excuses.php?experimental=1=pytest




--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1067115: gross: diff for NMU version 1.0.2-4.1

[Adrian Bunk]

On Sun, Mar 24, 2024 at 11:05:54PM +0100, Antonio Radici wrote:
> On Sat, Mar 23, 2024 at 11:45:58PM +0200, Adrian Bunk wrote:
> > Control: tags 1067115 + patch
> > Control: tags 1067115 + pending
> > 
> > Dear maintainer,
> > 
> > I've prepared an NMU for gross (versioned as 1.0.2-4.1) and uploaded
> > it to DELAYED/2. Please feel free to tell me if I should cancel it.
> > 
> 
> Thanks for working on this, no reason to cancel it.
>...

Thanks, rescheduled for immediate upload.

cu
Adrian

Processed: Re: Bug#1063951: fixed in barectf 3.1.2-2

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1063951 {Done: Michael Jeanson } [barectf] barectf: 
autopkgtest regression with pytest 8
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions barectf/3.1.2-2.
> notfixed -1 3.1.2-2
Bug #1063951 [barectf] barectf: autopkgtest regression with pytest 8
There is no source info for the package 'barectf' at version '3.1.2-2' with 
architecture ''
Unable to make a source version for version '3.1.2-2'
Ignoring request to alter fixed versions of bug #1063951 to the same values 
previously set

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

Bug#1063951: fixed in barectf 3.1.2-2

[Timo Röhling]

Control: reopen -1
Control: notfixed -1 3.1.2-2

On Fri, 15 Mar 2024 21:44:05 + Debian FTP Masters 
 wrote:
   * [2375fb4] Disable pytest8 deprecation warnings (Closes: 
   #1063951)

 - Also (Closes: #1066742) built with pytest8
Unfortunately, this was not a permanent solution, because the 
features which PytestRemovedIn8Warning has been warning about, have 
been actually removed now (pytest 8.1).



Cheers
Timo


--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Processed: forcibly merging 1065799 1066613

[Debian Bug Tracking System]

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

> forcemerge 1065799 1066613
Bug #1065799 [src:ncrack] ncrack: FTBFS on arm{el,hf}: configure: error: *** 
compiler cannot create working executables, check config.log ***
Bug #1065799 [src:ncrack] ncrack: FTBFS on arm{el,hf}: configure: error: *** 
compiler cannot create working executables, check config.log ***
Added tag(s) trixie and sid.
Bug #1066613 [src:ncrack] ncrack: FTBFS: configure: error: *** compiler cannot 
create working executables, check config.log ***
Merged 1065799 1066613
> thanks
Stopping processing here.

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

Bug#1067115: gross: diff for NMU version 1.0.2-4.1

[Antonio Radici]

On Sat, Mar 23, 2024 at 11:45:58PM +0200, Adrian Bunk wrote:
> Control: tags 1067115 + patch
> Control: tags 1067115 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for gross (versioned as 1.0.2-4.1) and uploaded
> it to DELAYED/2. Please feel free to tell me if I should cancel it.
> 

Thanks for working on this, no reason to cancel it.

Sorry I couldn't get to this faster enough

Processed: Bug#1063971 marked as pending in python-dateutil

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1063971 [python-dateutil] python-dateutil: autopkgtest regression with 
pytest 8
Added tag(s) pending.

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

Bug#1063971: marked as pending in python-dateutil

[Julian Gilbey]

Control: tag -1 pending

Hello,

Bug #1063971 in python-dateutil 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/python-dateutil/-/commit/7b821657a3281a3662c85324abd41a105df001ec


New upstream version (closes: #1063971); remove ancient Breaks field and update 
Standards-Version


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063971

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

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 21:19:43 +
with message-id 
and subject line Bug#1067358: fixed in python-flexmock 0.12.0-1
has caused the Debian Bug report #1067358,
regarding anymarkup-core: 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --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_anymarkup-core/build/anymarkup_core
> copying anymarkup_core/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_anymarkup-core/build/anymarkup_core
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_anymarkup-core/build/anymarkup_core
> copying anymarkup_core/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_anymarkup-core/build/anymarkup_core
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_anymarkup-core/build; python3.12 -m 
> pytest test
> = test session starts 
> ==
> platform linux -- Python 3.12.2, pytest-8.1.1, pluggy-1.4.0
> rootdir: /<>
> collected 83 items / 1 error
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.12_anymarkup-core/build/test/test_libs_not_installed.py _
> test/test_libs_not_installed.py:1: in 
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in 
> from flexmock import _integrations  # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in 
> saved_pytest = runner.call_runtest_hook
> E   AttributeError: module '_pytest.runner' has no attribute 
> 'call_runtest_hook'
> === short test summary info 
> 
> ERROR test/test_libs_not_installed.py - AttributeError: module 
> '_pytest.runne...
>  Interrupted: 1 error during collection 
> 
> === 1 error in 0.21s 
> ===
> E: pybuild pybuild:389: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.12_anymarkup-core/build; python3.12 -m 
> pytest test
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.11_anymarkup-core/build; python3.11 -m 
> pytest test
> = test session starts 
> ==
> platform linux -- Python 3.11.8, pytest-8.1.1, pluggy-1.4.0
> rootdir: /<>
> collected 83 items / 1 error
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.11_anymarkup-core/build/test/test_libs_not_installed.py _
> test/test_libs_not_installed.py:1: in 
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in 
> from flexmock import _integrations  # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in 
> saved_pytest = runner.call_runtest_hook
> E   AttributeError: module '_pytest.runner' has no attribute 
> 'call_runtest_hook'
> === short test summary info 
> 
> ERROR test/test_libs_not_installed.py - AttributeError: module 
> '_pytest.runne...
>  Interrupted: 1 error during collection 
> 
> === 1 error in 0.23s 
> ===
> E: pybuild pybuild:389: test: plugin distutils failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.11_anymarkup-core/build; python3.11 -m 
> pytest test
> 

Bug#1067358: marked as done (python-flexmock: FTBFS: AttributeError: module '_pytest.runner' has no attribute 'call_runtest_hook')

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 21:19:43 +
with message-id 
and subject line Bug#1067358: fixed in python-flexmock 0.12.0-1
has caused the Debian Bug report #1067358,
regarding python-flexmock: FTBFS: AttributeError: module '_pytest.runner' has 
no attribute 'call_runtest_hook'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom \
>   --test-args '{interpreter} tests/test_unittest.py'
> I: pybuild base:305: python3.12 tests/test_unittest.py
> Traceback (most recent call last):
>   File "/<>/tests/test_unittest.py", line 6, in 
> from flexmock import flexmock
>   File 
> "/<>/.pybuild/cpython3_3.12_flexmock/build/flexmock/__init__.py",
>  line 2, in 
> from flexmock import _integrations  # pylint: disable=unused-import
> ^^
>   File 
> "/<>/.pybuild/cpython3_3.12_flexmock/build/flexmock/_integrations.py",
>  line 101, in 
> saved_pytest = runner.call_runtest_hook
>
> AttributeError: module '_pytest.runner' has no attribute 'call_runtest_hook'
> E: pybuild pybuild:389: test: plugin custom failed with: exit code=1: 
> python3.12 tests/test_unittest.py
> I: pybuild base:305: python3.11 tests/test_unittest.py
> Traceback (most recent call last):
>   File "/<>/tests/test_unittest.py", line 6, in 
> from flexmock import flexmock
>   File 
> "/<>/.pybuild/cpython3_3.11_flexmock/build/flexmock/__init__.py",
>  line 2, in 
> from flexmock import _integrations  # pylint: disable=unused-import
> ^^
>   File 
> "/<>/.pybuild/cpython3_3.11_flexmock/build/flexmock/_integrations.py",
>  line 101, in 
> saved_pytest = runner.call_runtest_hook
>
> AttributeError: module '_pytest.runner' has no attribute 'call_runtest_hook'
> E: pybuild pybuild:389: test: plugin custom failed with: exit code=1: 
> python3.11 tests/test_unittest.py
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 
> 3.11" --system=custom --test-args "{interpreter} tests/test_unittest.py" 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/python-flexmock_0.11.3-3_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: python-flexmock
Source-Version: 0.12.0-1
Done: Stefano Rivera 

We believe that the bug you reported is fixed in the latest version of
python-flexmock, 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.
Stefano Rivera  (supplier of updated python-flexmock 
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: Sun, 24 Mar 2024 16:07:39 -0400
Source: python-flexmock
Architecture: source
Version: 0.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1067358
Changes:
 python-flexmock (0.12.0-1) unstable; 

Bug#1067624: marked as done (FTBFS: error: ‘struct input_event’ has no member named ‘time’)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 20:49:56 +
with message-id 
and subject line Bug#1067624: fixed in antimicro 3.1.4-2
has caused the Debian Bug report #1067624,
regarding FTBFS: error: ‘struct input_event’ has no member named ‘time’
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=antimicro=armel=3.1.4-1%2Bb1=1711183999=0

/<>/src/eventhandlers/uinputeventhandler.cpp: In member function
‘void UInputEventHandler::write_uinput_event(int, int, int, int, bool)’:
/<>/src/eventhandlers/uinputeventhandler.cpp:454:22: error:
‘struct input_event’ has no member named ‘time’
  454 | gettimeofday(, nullptr);
  |  ^~~~
/<>/src/eventhandlers/uinputeventhandler.cpp:464:27: error:
‘struct input_event’ has no member named ‘time’
  464 | gettimeofday(, nullptr);
  |   ^~~~


-- 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: antimicro
Source-Version: 3.1.4-2
Done: Thorsten Glaser 

We believe that the bug you reported is fixed in the latest version of
antimicro, 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.
Thorsten Glaser  (supplier of updated antimicro 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: SHA384

Format: 1.8
Date: Sun, 24 Mar 2024 20:57:06 +0100
Source: antimicro
Architecture: source
Version: 3.1.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Thorsten Glaser 
Closes: 1067624
Changes:
 antimicro (3.1.4-2) unstable; urgency=low
 .
   * QA upload.
   * Update d/watch to GitHub’s latest changes
   * d/p/work-around-Linux-API-break.diff: new, Closes: #1067624
   * Update Maintainer as orphaned
Checksums-Sha1:
 fe213067fb6ff0d82935a546cd96ed572342597d 2086 antimicro_3.1.4-2.dsc
 3b15f48f88e585b6ae221266956102cfe70525d1 8708 antimicro_3.1.4-2.debian.tar.xz
Checksums-Sha256:
 7f673e869f39e85c35a9bac1966198046cd5c2ed613c217c826a16cbaeb56ebf 2086 
antimicro_3.1.4-2.dsc
 14e0a9bee9cb5c00b4b304cdeb7b46598986f2d5caf13d51b57e70ecf195e85e 8708 
antimicro_3.1.4-2.debian.tar.xz
Files:
 26aea1c7f0a7be71ce0569adb84b2f11 2086 utils optional antimicro_3.1.4-2.dsc
 abae7aae6eaa77952b4af15172a8283f 8708 utils optional 
antimicro_3.1.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)

iQIcBAEBCQAGBQJmAIY7AAoJEHa1NLLpkAfgarUQAIyN/W+EeKVyh0uC6WuHAAmD
pFUG6YuJO5m/qaDVmPVsnSlwt6kXNFIbBAJLh3RFMqxnP2iPDh/PZwXrd9DJ/OtP
rtQ8g2WZioeJgtndjKbI7EvrZYjmHgWCsWCACDCDWvTbp18evssPsHvNmj21Jnxu
ywcW60xyA5uWjy+Ogg/cHtr1xyc1E/xUpixY0WltVzzi9RAjT0dhHk9DyINejsQA
9FfftlRKcJpa/i4VAmgb0aLWEJdCyuxMkHybz+8eXgOPVWyhLTld+qlY+SIZmNJM
BsYYQRuUwkgMdUZH/i04a2Zv0ONUC3odA0WXtSthxRGSq+tCP3VPdenpVDRDImi1
UcN7T7qrhmqCNfMB84zrgCYjSSaDMod7duxyiDaqf9bNqTFuUcIWZX2H0BH17HFJ
OOwvXxW5kvcBCabIIgcpR+494UUwliD7m+/OuIku4o7FDLgPT3VamjvNQJrVt6rZ
NUADCMye3cO52NILHKBLojMuZucSyTIxhSBD43261fyHPNT/XQQQmyM14w5DrL1h
wzi9Tjjl9T3mnxrEPtbE7Ch8fryDXhlnR+vI7nlqy66l0pKZ/XeLovKI5xPKEOyG
NEEKfTgukBDUnrA2u3nO4qlN94lld9/FguiRq6c3nczwPIDjeTXXeF2PNh6n4OJw
sRM3GEEarMbqFzMZ2Epf
=fp4j
-END PGP SIGNATURE-



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

Bug#1050336: marked as done (libnet-xmpp-perl: unable to StartTLS, without any feedback)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 20:44:29 +
with message-id 
and subject line Bug#1064058: fixed in libxml-stream-perl 1.24-4+deb12u1
has caused the Debian Bug report #1064058,
regarding libnet-xmpp-perl: unable to StartTLS, without any feedback
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.)


-- 
1064058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-xmpp-perl
Version: 1.05-1.1
Severity: serious
Justification: cannot perform basic authentication

Hi,

I have a few scripts around that use Net::XMPP to send notifications
when this or that happens, and all of them broke after upgrading from
bullseye to bookworm. This is definitely not related to changes on the
server side (which I control and didn't change), and other existing
hosts still on bullseye still work fine.

The error manifests itself like this:

AuthIQAuth requires a resource arguement at /local/wrapper.pm line 42.

Tracking it down, it appears AuthSend uses AuthSASL on bullseye (OK)
and AuthIQAuth on bookworm (KO). The latter is the fallback:

,---[ Net/XMPP/Protocol.pm ]---
| sub AuthSend
| {
[…]
| if($self->{STREAM}->GetStreamFeature($self->GetStreamID(),"xmpp-sasl"))
| {
| return $self->AuthSASL(%args);
| }
| return $self->AuthIQAuth(%args);
| }
`---

The GetStreamID isn't happy because it tries to pick the ID part of the
SESSION, which is missing.

Diving into the connection implementation, I managed to confirm that the
connection is established at first, giving me a $self->{SESSION} set,
but that goes away later on:

,---[ Net/XMPP/Connection.pm ]---
| sub Connect
| {   
| if ($self->{SESSION})
| {
| $self->{DEBUG}->Log1("Connect: connection made");
| 
| my $weak = $self;
| weaken $weak;
| $self->{STREAM}->SetCallBacks(node=>sub{ $weak->CallBack(@_) });
| $self->{CONNECTED} = 1;
| $self->{RECONNECTING} = 0;
| 
| if (exists($self->{SESSION}->{version}) &&
| ($self->{SESSION}->{version} ne ""))
| {
| my $tls = $self->GetStreamFeature("xmpp-tls");
| if (defined($tls) && $self->{SERVER}->{tls})
| {
| $self->{SESSION} =
| $self->{STREAM}->StartTLS(
| $self->{SESSION}->{id},
| $self->{SERVER}->{timeout},
| );

Here be dragons.

| }
| elsif (defined($tls) && ($tls eq "required"))
| {
| $self->SetErrorCode("The server requires us to use TLS, but 
you did not specify that\nTLS was an option.");
| return;
| }
| }
| 
| return 1;
| }
| else
| {
| $self->SetErrorCode($self->{STREAM}->GetErrorCode());
| return;
| }
`---

I also confirmed (yay for print-debugging) that the xmpp-tls branch is
entered, the StartTLS() fails for some reason (or at least returns
nothing at all), and $self->{SESSION} gets reset. The rest explodes.


There are only minor differences between the package in bullseye and
bookworm (mostly packaging metadata), so it looks to me something
external (undetermined at the moment) triggered this problem during
the upgrade. I thought I'd file my findings then think a little more
about a game plan.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: libxml-stream-perl
Source-Version: 1.24-4+deb12u1
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libxml-stream-perl, 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.
gregor herrmann  (supplier of updated libxml-stream-perl 
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: Sun, 03 Mar 2024 16:02:42 +0100
Source: libxml-stream-perl
Architecture: source
Version: 1.24-4+deb12u1

Bug#1064058: marked as done (libxml-stream-perl: TLS/SSL broken with IO-Socket-SSL >= 2.078 when hostname verification is enabled)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 20:44:29 +
with message-id 
and subject line Bug#1064058: fixed in libxml-stream-perl 1.24-4+deb12u1
has caused the Debian Bug report #1064058,
regarding libxml-stream-perl: TLS/SSL broken with IO-Socket-SSL >= 2.078 when 
hostname verification is enabled
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.)


-- 
1064058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxml-stream-perl
Version: 1.24-4
Severity: normal
Tags: upstream
Control: affects -1 sendxmpp libnet-xmpp-perl

Dear Maintainers,

after upgrading to Debian Bookworm, we noticed that the sendxmpp command
line tool was not working anymore in our setup. During the investigation
of this issue, I noticed that downgrading IO-Socket-SSL to the version
in Bullseye made sendxmpp work again. I then started to try all versions
of IO-Socket-SSL between the version in Bullseye and the one in Bookworm
and found that it stopped working with version 2.078. Eventually, I came
up with a pull request [1] containing a patch that fixed it for us -
apparently, the way XML-Stream was using IO-Socket-SSL most likely
always resulted in the hostname verification to be done against the IP
address of the peer instead of an actual hostname, which was always
considered to be successful in IO-Socket-SSL < 2.078, but not anymore in
newer versions.

Since the upstream seems quite inactive, it might be worth considering
to add this or a similar patch to the package in Debian, as I came
across several other bug reports in the Debian BTS which might actually
be caused by this issue, like #986971 [2], #1032868 [3] and maybe also
#1050336 [4] - at least the error messages in the first two look very
similar to what I saw.

Cheers,
Manfred

[1]: https://github.com/dap/XML-Stream/pull/28
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986971
[3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032868
[4]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050336

-- 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/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.utf8, LC_CTYPE=de_CH.utf8 (charmap=UTF-8), LANGUAGE=de_CH:de
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages libxml-stream-perl depends on:
ii  libauthen-sasl-perl2.1600-3
ii  libio-socket-ssl-perl  2.081-2
ii  perl   5.36.0-7+deb12u1

libxml-stream-perl recommends no packages.

Versions of packages libxml-stream-perl suggests:
ii  libnet-dns-perl  1.36-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libxml-stream-perl
Source-Version: 1.24-4+deb12u1
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libxml-stream-perl, 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.
gregor herrmann  (supplier of updated libxml-stream-perl 
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: Sun, 03 Mar 2024 16:02:42 +0100
Source: libxml-stream-perl
Architecture: source
Version: 1.24-4+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1064058
Changes:
 libxml-stream-perl (1.24-4+deb12u1) bookworm; urgency=medium
 .
   * Team upload.
   * Add Set_SSL_verifycn_name_parameter_to_fix_hostname_verification.patch
 to adjust to IO::Socket::SSL >= 2.078.
 Thanks to Manfred Stock for the bug report and the patch.
 (Closes: #1064058)
Checksums-Sha1:
 fb30bd6a1ea3e8ace0475749f6f5cb65137d960c 2523 
libxml-stream-perl_1.24-4+deb12u1.dsc
 bec97360ef55ee94793a7827fa89a667be233aeb 7140 
libxml-stream-perl_1.24-4+deb12u1.debian.tar.xz
Checksums-Sha256:
 5e3b78e6fca3396feee7456fd6e38fcb038563fde93de1032e01e745787c779d 2523 
libxml-stream-perl_1.24-4+deb12u1.dsc
 

Bug#1032868: marked as done (sendxmpp: Stopped working with version of prosody that's in bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 20:44:29 +
with message-id 
and subject line Bug#1064058: fixed in libxml-stream-perl 1.24-4+deb12u1
has caused the Debian Bug report #1064058,
regarding sendxmpp: Stopped working with version of prosody that's in bullseye
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.)


-- 
1064058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendxmpp
Version: 1.24-3
Severity: normal

When I run "sendxmpp -t $ADDRESS" with an account on a Prosody server running
on Bullseye from a system on Debian/Testing it gives the below error messages.
The same server accepts mesages from sendxmpp running on Bullseye.  This is
sendxmpp losing functionality that it had in Bullseye.

Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1828.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 2739.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2741.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1667.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1668.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1668.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1670.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1672.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1672.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1674.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1677.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2619.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 2739.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2741.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1439.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1442.
Use of uninitialized value $status{"newconnection"} in numeric eq (==) at 
/usr/share/perl5/XML/Stream.pm line 1505.
Use of uninitialized value in subtraction (-) at /usr/share/perl5/XML/Stream.pm 
line 1506.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1668.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1672.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 433.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 440.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 433.
Use of uninitialized value in string eq at /usr/bin/sendxmpp line 515.
Error 'AuthSend': [?]
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1667.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1668.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1670.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1672.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1265.
Use of uninitialized value in string eq at /usr/share/perl5/XML/Stream.pm line 
1265.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1265.
Use of uninitialized value in string eq at /usr/share/perl5/XML/Stream.pm line 
1265.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1266.
Use of uninitialized value in delete at /usr/share/perl5/XML/Stream.pm line 
1266.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1267.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1269.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1269.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1269.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1269.
Use of uninitialized value $sid in hash element at 

Bug#986971: marked as done (sendxmpp: Sendxmpp doesn't work with current XMPP servers)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 20:44:29 +
with message-id 
and subject line Bug#1064058: fixed in libxml-stream-perl 1.24-4+deb12u1
has caused the Debian Bug report #1064058,
regarding sendxmpp: Sendxmpp doesn't work with current XMPP servers
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.)


-- 
1064058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendxmpp
Version: 1.24-3
Severity: normal
X-Debbugs-Cc: spam-deb...@mdosch.de

Dear Maintainer,

sendxmpp stopped working for me a long time ago and as I see a lot of people
are writing alternatives as sendxmpp stopped working for them (I also did this
myself), e.g. https://github.com/xsf/xmpp.org/pull/612#issue-319614396.
As upstream seems to be dead it might be better to drop sendxmpp and pick one
of the various alternatives rather than shipping a broken sendxmpp.

```
martin@schlepptop ~ % date |sendxmpp -t mar...@mdosch.de
Error 'AuthSend': error: malformed-request[?]
```


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (500, 'unstable-debug'),
(500, 'testing-security'), (500, 'testing-debug'), (500, 'experimental'), (1,
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 sendxmpp depends on:
ii  libnet-xmpp-perl  1.05-1.1
ii  perl  5.32.1-3

sendxmpp recommends no packages.

sendxmpp suggests no packages.
--- End Message ---
--- Begin Message ---
Source: libxml-stream-perl
Source-Version: 1.24-4+deb12u1
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libxml-stream-perl, 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.
gregor herrmann  (supplier of updated libxml-stream-perl 
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: Sun, 03 Mar 2024 16:02:42 +0100
Source: libxml-stream-perl
Architecture: source
Version: 1.24-4+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1064058
Changes:
 libxml-stream-perl (1.24-4+deb12u1) bookworm; urgency=medium
 .
   * Team upload.
   * Add Set_SSL_verifycn_name_parameter_to_fix_hostname_verification.patch
 to adjust to IO::Socket::SSL >= 2.078.
 Thanks to Manfred Stock for the bug report and the patch.
 (Closes: #1064058)
Checksums-Sha1:
 fb30bd6a1ea3e8ace0475749f6f5cb65137d960c 2523 
libxml-stream-perl_1.24-4+deb12u1.dsc
 bec97360ef55ee94793a7827fa89a667be233aeb 7140 
libxml-stream-perl_1.24-4+deb12u1.debian.tar.xz
Checksums-Sha256:
 5e3b78e6fca3396feee7456fd6e38fcb038563fde93de1032e01e745787c779d 2523 
libxml-stream-perl_1.24-4+deb12u1.dsc
 eadf675738027ab8447228686bfe8d20c6dd521f3c7a9ab31d809288c6e6d92d 7140 
libxml-stream-perl_1.24-4+deb12u1.debian.tar.xz
Files:
 328f6fcb20ce0c9cf8c0f740da766a9e 2523 perl optional 
libxml-stream-perl_1.24-4+deb12u1.dsc
 140814e7bf2be6f8c54c982b2aabe05a 7140 perl optional 
libxml-stream-perl_1.24-4+deb12u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmXkkfJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgavnBAAsuD/5y/HrswOTmuSxZ1hBxDi3utJfqD+OqWcKRUk9EcUrEJImMRWnRRa
1Whsmj3Cz2Rp/vH2xMzkFp2a63O/j3UqbRKk/+KD18oYi5eD/yRQxEKii84AQB91
MX1hwsjYF6LlGf6tXxZbXEuOYhM941RC26QLs+MTmqRSPwe3HYvFI6eAYizxhdj1
/0yFkBb2LOD7dS3jwRFkDMwbk0Fsy+36U3s3mU5nfHJuqGsCB/rw04mHUBIhruJX
MXAI7yBUT41fG8jz5YCK3xdQQu8wDsig/e1BjaJQ5v5uJeIYIkXJbbYAwnO/Zh9P
vnDba2XJOa00iFiDEHXD8M5GX9OUdKo5iS3zfAswRijDH4y2A4QguQmAlrlRWRGS
u2P723Ec6PpaaEhp+PGwV1joPE1hyTaw3Q+N80MtQUZZ4Bc6fZ4ADLcJcgxhUpqX
maKi+pTaK9ujQIfPE/XUszBP52q1C1xp2xJ1EWO0wuS0QdAk3PAqg5cwYvzBkR8q

Bug#1067630: emacs: release 29.3 fixes "several security vulnerabilities"

[David Bremner]

Source: emacs
Version: 29.2+1-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team , 
debian-emac...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


According to the 29.3 release notes

* Changes in Emacs 29.3
Emacs 29.3 is an emergency bugfix release intended to fix several
security vulnerabilities described below.

** Arbitrary Lisp code is no longer evaluated as part of turning on Org mode.
This is for security reasons, to avoid evaluating malicious Lisp code.

** New buffer-local variable 'untrusted-content'.
When this is non-nil, Lisp programs should treat buffer contents with
extra caution.

** Gnus now treats inline MIME contents as untrusted.
To get back previous insecure behavior, 'untrusted-content' should be
reset to nil in the buffer.

** LaTeX preview is now by default disabled for email attachments.
To get back previous insecure behavior, set the variable
'org--latex-preview-when-risky' to a non-nil value.

** Org mode now considers contents of remote files to be untrusted.
Remote files are recognized by calling 'file-remote-p'.

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

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

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmYAhNIACgkQA0U5G1Wq
FSEANg//cukjqohXxNRpkxbutqHHvOB1aAr3d78jowjP3Yb9ozAArNxUjuJHEdSZ
5HCASm269atf5753maZILjyx3VmF/qUihyGjbbWjqMwNrQkkQiuXBfYn1F4R76/V
tyFile5NZVXIgYMykLb+rSHap6KMBnhjvLWSwNsDMuD8WB7OPH7KOI2xYqkUb7ue
SIgkCr0GJ+LaHOAYlRKkAYok4qwIfijLBw41Bt7t9Tawh+5d5nDkNPDphFOB+bG+
1hOQD8KVYWIceRK83wcDictSxbeTSo/cp6cEtVZX3yrDvBRbj3VKjKWL+0UIKfWO
iGWQYn622B7WbBIwEddQMmla+nxa5rxEN9VMEE8N5xcpI1lnL0lVSxw0jbT0FopJ
PmwFYmz1+pxB2fhRTv1T7ZTSAJS3BKQ9u2R8tuKO5ilSYp1zJrBBIazGPZ3Q+UBS
EoPh4hy5G4IZ3X3yaE9cX76fdDMMGPQ7HIinkw5A7KWb8zHse5m3+WG+iPNuveHU
GRwOB9pDDRTQrQVG8of2YVS0kLb9eu2jUD0sbi8As3P5Mr/gXHlrSgs5t1qg3HuA
Kkg7m7PAONZu0LBZNZsItm/V0weDqBdE+LZsa/1LUk3H+zvswhctlNLuZ7Y4mKqh
YpuwmZ2+cv1To2M/DKbBx2ngl5EiojF8hk5pGezcZ811NRFAQKc=
=BxE4
-END PGP SIGNATURE-

Bug#1067628: FTBFS: Error: symbol `open64' is already define

[Andrey Rakhmatullin]

Source: cctools
Version: 9.9-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=cctools=armel=9.9-4%2Bb2=1711271394=0


/tmp/ccxWFvuU.s: Assembler messages:
/tmp/ccxWFvuU.s:1927: Error: symbol `open64' is already defined


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

Processed: tagging 1066866

[Debian Bug Tracking System]

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

> tags 1066866 + ftbfs
Bug #1066866 [railway-gtk] railway-gtk: FTBFS on i386 "type annotations needed"
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1067627: FTBFS: error: comparison of integer expressions of different signedness: ‘long unsigned int’ and ‘long int’

[Andrey Rakhmatullin]

Source: xpra
Version: 3.1.5+dfsg1-0.2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=xpra=i386=3.1.5%2Bdfsg1-0.2%2Bb3=1710056306=0

xpra/x11/bindings/keyboard_bindings.c: In function ‘__Pyx_PyInt_AndObjC’:
xpra/x11/bindings/keyboard_bindings.c:30158:36: error: comparison of integer
expressions of different signedness: ‘long unsigned int’ and ‘long int’
[-Werror=sign-compare]
30158 | if ((intval & PyLong_MASK) == intval) {
  |^~
xpra/x11/bindings/keyboard_bindings.c:30160:71: error: operand of ‘?:’ changes
signedness from ‘long int’ to ‘long unsigned int’ due to unsignedness of other
operand [-Werror=sign-compare]
30160 | long result = intval & (likely(__Pyx_PyLong_IsPos(op1)) ?
last_digit : (PyLong_MASK - last_digit + 1));
  |
^~


Note that the package enables -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#1067626: FTBFS: fopen_fails test failed

[Andrey Rakhmatullin]

Source: pacemaker
Version: 2.1.6-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pacemaker=armel=2.1.6-5=1711156223=0

PASS: pcmk__output_new_test 1 - empty_formatters
PASS: pcmk__output_new_test 2 - invalid_params
PASS: pcmk__output_new_test 3 - no_such_format
PASS: pcmk__output_new_test 4 - create_fails
PASS: pcmk__output_new_test 5 - init_fails
FAIL: pcmk__output_new_test 6 - fopen_fails
PASS: pcmk__output_new_test 7 - everything_succeeds
PASS: pcmk__output_new_test 8 - no_fmt_name_given
ERROR: pcmk__output_new_test - exited with status 1


-- 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#1067625: FTBFS on armel: undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'

[Andrey Rakhmatullin]

Source: transmission
Version: 4.0.5-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=transmission=armel=4.0.5-1%2Bb1=1711181507=0

/usr/bin/ld: ../../libtransmission/libtransmission.a(web.cc.o): undefined
reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'
/usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: DSO
missing from command line


-- 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#1067624: FTBFS: error: ‘struct input_event’ has no member named ‘time’

[Andrey Rakhmatullin]

Source: antimicro
Version: 3.1.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=antimicro=armel=3.1.4-1%2Bb1=1711183999=0

/<>/src/eventhandlers/uinputeventhandler.cpp: In member function
‘void UInputEventHandler::write_uinput_event(int, int, int, int, bool)’:
/<>/src/eventhandlers/uinputeventhandler.cpp:454:22: error:
‘struct input_event’ has no member named ‘time’
  454 | gettimeofday(, nullptr);
  |  ^~~~
/<>/src/eventhandlers/uinputeventhandler.cpp:464:27: error:
‘struct input_event’ has no member named ‘time’
  464 | gettimeofday(, nullptr);
  |   ^~~~


-- 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#1067623: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}

[Andrey Rakhmatullin]

Source: acm
Version: 6.0+20200416-1.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=acm=armel=6.0%2B20200416-1.1%2Bb2=1711183805=0

disscope.c: In function ‘main’:
disscope.c:242:45: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘__time64_t’ {aka ‘long long int’} [-Werror=format=]
  242 | printf ("Time stamp   %ld.%ld\n", tm.tv_sec,


Note that the package enables -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

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

[Debian Bug Tracking System]

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

> severity 1066765 important
Bug #1066765 {Done: Antonio Valentino } 
[src:pygac] pygac: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" returned exit code 13
Severity set to 'important' from 'serious'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
sebas...@debian.org).
> usertags 1066765 time-t-downgrade
There were no usertags set.
Usertags are now: time-t-downgrade.
> thanks
Stopping processing here.

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

Bug#1067616: FTBFS: error: ‘struct input_event’ has no member named ‘time’

[Simon McVittie]

On Sun, 24 Mar 2024 at 23:06:18 +0500, Andrey Rakhmatullin wrote:
> GLX/input_device_linuxevent.cpp: In member function ‘virtual void
> CL_InputDevice_LinuxEvent::keep_alive()’:
> GLX/input_device_linuxevent.cpp:269:72: error: ‘struct input_event’ has no
> member named ‘time’
>   269 |
> ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].code ? "Config Sync" : "Report
> Sync" );

Looks like another instance of essentially the same issue that's fixed in
SDL by . Applying the
same technique would probably work here too.

smcv

Bug#1067622: FTBFS: error: missing initializer for member ‘input_event::value’

[Andrey Rakhmatullin]

Source: projecteur
Version: 0.10-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=projecteur=armel=0.10-2%2Bb2=1711185228=0

/<>/src/deviceinput.cc: In member function ‘void
InputMapper::Impl::emitNativeKeySequence(const NativeKeySequence&)’:
/<>/src/deviceinput.cc:697:64: error: narrowing conversion of
‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
{aka ‘short unsigned int’} [-Werror=narrowing]
  697 |   events.emplace_back(input_event{{}, ie.type, ie.code, ie.value});
  | ~~~^
/<>/src/deviceinput.cc:697:69: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
  697 |   events.emplace_back(input_event{{}, ie.type, ie.code, ie.value});
  | ^
/<>/src/deviceinput.cc: In lambda function:
/<>/src/deviceinput.cc:893:55: error: narrowing conversion of
‘(int32_t)de.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
{aka ‘short unsigned int’} [-Werror=narrowing]
  893 | struct input_event ie = {{}, de.type, de.code, de.value};
  |~~~^
/<>/src/deviceinput.cc:893:60: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
  893 | struct input_event ie = {{}, de.type, de.code, de.value};
  |^
/<>/src/deviceinput.cc: In member function ‘void
InputMapper::addEvents(const KeyEvent&)’:
/<>/src/deviceinput.cc:906:79: error: missing initializer for
member ‘input_event::value’ [-Werror=missing-field-initializers]
  906 |   if (!hasLastSYN) { events.emplace_back(input_event{{}, EV_SYN,
SYN_REPORT, 0}); }
  |
^



Note that this package enables -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#1067344: marked as done (pyspectral: FTBFS: dh_missing: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 18:21:01 +
with message-id 
and subject line Bug#1067344: fixed in pyspectral 0.13.0+ds-2
has caused the Debian Bug report #1067344,
regarding pyspectral: FTBFS: dh_missing: error: missing files, aborting
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.)


-- 
1067344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyspectral
Version: 0.13.0+ds-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):
> make[1]: Entering directory '/<>'
> for f in debian/tmp/usr/bin/*.py; do \
>   mv $f $(dirname $f)/$(basename $f .py);\
> done
> rm -f -r debian/tmp/usr/lib/python*/dist-packages/pyspectral/__pycache__/
> make[1]: Leaving directory '/<>'
>dh_install -O--buildsystem=pybuild
>dh_installdocs -O--buildsystem=pybuild
>dh_sphinxdoc -O--buildsystem=pybuild
>dh_installchangelogs -O--buildsystem=pybuild
>dh_installman -O--buildsystem=pybuild
>dh_python3 -O--buildsystem=pybuild
>dh_installsystemduser -O--buildsystem=pybuild
>dh_lintian -O--buildsystem=pybuild
>dh_perl -O--buildsystem=pybuild
>dh_link -O--buildsystem=pybuild
>dh_strip_nondeterminism -O--buildsystem=pybuild
>dh_compress -O--buildsystem=pybuild
>dh_fixperms -O--buildsystem=pybuild
>dh_missing -O--buildsystem=pybuild
> dh_missing: warning: 
> usr/lib/python3.11/dist-packages/.pytest_cache/.gitignore exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/lib/python3.11/dist-packages/.pytest_cache/CACHEDIR.TAG exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: usr/lib/python3.11/dist-packages/.pytest_cache/README.md 
> exists in debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/lib/python3.11/dist-packages/.pytest_cache/v/cache/nodeids exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/lib/python3.11/dist-packages/.pytest_cache/v/cache/stepwise exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/lib/python3.12/dist-packages/.pytest_cache/.gitignore exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/lib/python3.12/dist-packages/.pytest_cache/CACHEDIR.TAG exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: usr/lib/python3.12/dist-packages/.pytest_cache/README.md 
> exists in debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/lib/python3.12/dist-packages/.pytest_cache/v/cache/nodeids exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: 
> usr/lib/python3.12/dist-packages/.pytest_cache/v/cache/stepwise exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: error: missing files, aborting
>   The following debhelper tools have reported what they installed (with 
> files per package)
>* dh_install: pyspectral-bin (4), python3-pyspectral (68), 
> python3-pyspectral-doc (2)
>* dh_installdocs: pyspectral-bin (0), python3-pyspectral (0), 
> python3-pyspectral-doc (1)
>* dh_installman: pyspectral-bin (4), python3-pyspectral (0), 
> python3-pyspectral-doc (0)
>   If the missing files are installed by another tool, please file a bug 
> against it.
>   When filing the report, if the tool is not part of debhelper itself, 
> please reference the
>   "Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz)
>   Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
> when only a subset is built
>   If the omission is intentional or no other helper can take care of this 
> consider adding the
>   paths to debian/not-installed.
> make: *** [debian/rules:11: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/pyspectral_0.13.0+ds-1_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

Bug#1067621: FTBFS on 32-bit time64 architectures: error: implicit declaration of function ‘gzopen64’

[Andrey Rakhmatullin]

Source: berkeley-abc
Version: 1.01+20230625git01b1bd1+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=berkeley-
abc=armel=1.01%2B20230625git01b1bd1%2Bdfsg-3%2Bb2=1711273244=0

In file included from src/base/io/ioReadBlifMv.c:21:
src/base/io/ioReadBlifMv.c: In function ‘Io_MvLoadFileGz’:
./src/misc/zlib/zlib.h:1583:18: error: implicit declaration of function
‘gzopen64’; did you mean ‘gzopen’? [-Werror=implicit-function-declaration]
 1583 | #  define gzopen gzopen64


-- 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#1067619: FTBFS: tests segfault

[Andrey Rakhmatullin]

Source: falcosecurity-libs
Version: 0.14.1-5.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=falcosecurity-
libs=i386=0.14.1-5.1=1709205669=0

[ RUN  ] sinsp_with_test_input.spawn_process
Segmentation fault
gmake[9]: *** [libsinsp/test/CMakeFiles/run-unit-test-
libsinsp.dir/build.make:73: libsinsp/test/CMakeFiles/run-unit-test-libsinsp]
Error 139


-- 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#1067618: FTBFS: error: implicit declaration of function 'yyerror'; did you mean 'yyerrok'? [-Werror=implicit-function-declaration]

[Andrey Rakhmatullin]

Source: whitedune
Version: 0.30.10-2.2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=whitedune=armel=0.30.10-2.2%2Bb1=1711185326=0

y.tab.c: In function 'yyparse':
y.tab.c:2666:7: error: implicit declaration of function 'yyerror'; did you mean
'yyerrok'? [-Werror=implicit-function-declaration]


linux/SDL_sysjoystick.c: In function ‘HandleHat’:
linux/SDL_sysjoystick.c:525:9: error: implicit declaration of function
‘SDL_PrivateJoystickHat’ [-Werror=implicit-function-declaration]
  525 | SDL_PrivateJoystickHat(stick, hat,
  | ^~
linux/SDL_sysjoystick.c: In function ‘JS_HandleEvents’:
linux/SDL_sysjoystick.c:567:21: error: implicit declaration of function
‘SDL_PrivateJoystickAxis’ [-Werror=implicit-function-declaration]
  567 | SDL_PrivateJoystickAxis(joystick,
  | ^~~
linux/SDL_sysjoystick.c:598:17: error: implicit declaration of function
‘SDL_PrivateJoystickButton’ [-Werror=implicit-function-declaration]
  598 | SDL_PrivateJoystickButton(joystick,
  | ^
linux/SDL_sysjoystick.c: In function ‘SDL_SYS_JoystickUpdate’:
linux/SDL_sysjoystick.c:717:13: error: implicit declaration of function
‘SDL_PrivateJoystickBall’ [-Werror=implicit-function-declaration]
  717 | SDL_PrivateJoystickBall(joystick, (Uint8)i, xrel, yrel);
  | ^~~


-- 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#1067616: FTBFS: error: ‘struct input_event’ has no member named ‘time’

[Andrey Rakhmatullin]

Source: clanlib
Version: 1.0~svn3827-11.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=clanlib=armel=1.0%7Esvn3827-11.1=1711185366=0

GLX/input_device_linuxevent.cpp: In member function ‘virtual void
CL_InputDevice_LinuxEvent::keep_alive()’:
GLX/input_device_linuxevent.cpp:269:72: error: ‘struct input_event’ has no
member named ‘time’
  269 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].code ? "Config Sync" : "Report
Sync" );
  |
^~~~
GLX/input_device_linuxevent.cpp:269:91: error: ‘struct input_event’ has no
member named ‘time’
  269 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].code ? "Config Sync" : "Report
Sync" );
  |
^~~~
GLX/input_device_linuxevent.cpp:274:72: error: ‘struct input_event’ has no
member named ‘time’
  274 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
  |
^~~~
GLX/input_device_linuxevent.cpp:274:91: error: ‘struct input_event’ has no
member named ‘time’
  274 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
  |
^~~~
GLX/input_device_linuxevent.cpp:283:72: error: ‘struct input_event’ has no
member named ‘time’
  283 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,
  |
^~~~
GLX/input_device_linuxevent.cpp:283:91: error: ‘struct input_event’ has no
member named ‘time’
  283 |
ev[i].time.tv_sec, ev[i].time.tv_usec, ev[i].type,


-- 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#1064139: marked as done (ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 18:00:13 +
with message-id 
and subject line Bug#1064139: fixed in ogre-1.12 1.12.10+dfsg2-4
has caused the Debian Bug report #1064139,
regarding ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of 
‘ImGuiFreeType’
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.)


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

Dear maintainer,

ogre-1.12 fails to build from source, probably due to a change in imgui.
From my build log on amd64:

| [ 73%] Building CXX object 
Components/Overlay/CMakeFiles/OgreOverlay.dir/src/OgreFontManager.cpp.o
| cd /<>/obj-x86_64-linux-gnu/Components/Overlay && /usr/bin/c++ 
-DOgreOverlay_EXPORTS -I/<>/Components/Overlay/include 
-I/usr/include/freetype2 -I/misc/freetype -I/<>/OgreMain/include 
-I/<>/obj-x86_64-linux-gnu/include -isystem /usr/include/imgui 
-isystem /usr/include/stb -Wall -Winit-self -Wcast-qual -Wwrite-strings -Wextra 
-Wundef -Wmissing-declarations -Wno-unused-parameter -Wshadow 
-Wno-missing-field-initializers -Wno-long-long -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -pipe 
-Wall -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -msse 
-std=c++11 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT 
Components/Overlay/CMakeFiles/OgreOverlay.dir/src/OgreFontManager.cpp.o -MF 
CMakeFiles/OgreOverlay.dir/src/OgreFontManager.cpp.o.d -o 
CMakeFiles/OgreOverlay.dir/src/OgreFontManager.cpp.o -c 
/<>/Components/Overlay/src/OgreFontManager.cpp
| [ 73%] Building CXX object 
Components/Overlay/CMakeFiles/OgreOverlay.dir/src/OgreImGuiOverlay.cpp.o
| cd /<>/obj-x86_64-linux-gnu/Components/Overlay && /usr/bin/c++ 
-DOgreOverlay_EXPORTS -I/<>/Components/Overlay/include 
-I/usr/include/freetype2 -I/misc/freetype -I/<>/OgreMain/include 
-I/<>/obj-x86_64-linux-gnu/include -isystem /usr/include/imgui 
-isystem /usr/include/stb -Wall -Winit-self -Wcast-qual -Wwrite-strings -Wextra 
-Wundef -Wmissing-declarations -Wno-unused-parameter -Wshadow 
-Wno-missing-field-initializers -Wno-long-long -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -pipe 
-Wall -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -msse 
-std=c++11 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT 
Components/Overlay/CMakeFiles/OgreOverlay.dir/src/OgreImGuiOverlay.cpp.o -MF 
CMakeFiles/OgreOverlay.dir/src/OgreImGuiOverlay.cpp.o.d -o 
CMakeFiles/OgreOverlay.dir/src/OgreImGuiOverlay.cpp.o -c 
/<>/Components/Overlay/src/OgreImGuiOverlay.cpp
| /<>/Components/Overlay/src/OgreImGuiOverlay.cpp: In member 
function ‘void Ogre::ImGuiOverlay::ImGUIRenderable::createFontTexture()’:
| /<>/Components/Overlay/src/OgreImGuiOverlay.cpp:118:20: error: 
‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’
|   118 | ImGuiFreeType::BuildFontAtlas(io.Fonts, 0);
|   |^~
| make[4]: *** [Components/Overlay/CMakeFiles/OgreOverlay.dir/build.make:121: 
Components/Overlay/CMakeFiles/OgreOverlay.dir/src/OgreImGuiOverlay.cpp.o] Error 
1
| make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[3]: *** [CMakeFiles/Makefile2:1187: 
Components/Overlay/CMakeFiles/OgreOverlay.dir/all] Error 2
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [Makefile:159: all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
| make[1]: *** [debian/rules:65: override_dh_auto_build-indep] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:41: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

A full build log is also available on riscv64:
https://buildd.debian.org/status/fetch.php?pkg=ogre-1.12=riscv64=1.12.10%2Bdfsg2-3%2Bb1=1707901622=0

The issue is also visible on the reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ogre-1.12_1.12.10+dfsg2-3.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/ogre-1.12_1.12.10+dfsg2-3.rbuild.log.gz

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: ogre-1.12
Source-Version: 

Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

[Chris Lamb]

Alberto Bertogli wrote:

> I'll try to get a debian install to boot for armhf, but it'll take me a 
> bit because it's not straightforward (to put it mildly :).

Oh, yeah. :/ Perhaps qemu might be better option here. There might
even be pre-built disk images flying around.

> How urgent/important is this issue?

Medium? As it is technically a regression (as in, armhf used to build
before), this was filed with a severity of "serious". What this means
in practical terms is that newer versions of libfiu we upload will not
migrate to the staging area for the next release of Debian.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1067615: FTBFS: error: size of array ‘dummyinfo_does_not_fit’ is negative

[Andrey Rakhmatullin]

Source: osmo-pcu
Version: 1.1.0-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=osmo-
pcu=armel=1.1.0-3%2Bb2=1711272169=0

/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"osmo-pcu\"
-DPACKAGE_TARNAME=\"osmo-pcu\" -DPACKAGE_VERSION=\"1.1.0\"
-DPACKAGE_STRING=\"osmo-pcu\ 1.1.0\" -DPACKAGE_BUGREPORT=\"osmocom-net-
g...@lists.osmocom.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"osmo-pcu\"
-DVERSION=\"1.1.0\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\".libs/\" -I.  -I../include -Wall -I/usr/include/ -pthread
-I/usr/include/ -pthread  -I/usr/include/ -pthread  -I/usr/include/ -pthread
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -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 -std=gnu11 -c -o osmobts_sock.lo
osmobts_sock.c
In file included from /usr/include/osmocom/core/msgb.h:20,
 from llc.c:21:
llc.c: In function ‘llc_queue_enqueue’:
llc.c:145:9: error: size of array ‘dummyinfo_does_not_fit’ is negative
  145 | osmo_static_assert(sizeof(*meta_storage) <=
sizeof(llc_msg->cb), info_does_not_fit);
  | ^~


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

Processed: Re: Bug#1066465 closed by Debian FTP Masters (reply to Filip Hroch ) (Bug#1066465: fixed in dcraw 9.28-4)

[Debian Bug Tracking System]

Processing control commands:

> found -1 dcraw/9.28-4
Bug #1066465 {Done: Filip Hroch } [src:dcraw] dcraw: 
FTBFS: fujiturn.c:76:37: error: implicit declaration of function ‘ntohs’ 
[-Werror=implicit-function-declaration]
The source dcraw and version 9.28-4 do not appear to match any binary packages
Marked as found in versions dcraw/9.28-4; no longer marked as fixed in versions 
dcraw/9.28-4 and reopened.

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

Bug#1066465: closed by Debian FTP Masters (reply to Filip Hroch ) (Bug#1066465: fixed in dcraw 9.28-4)

[Andrey Rakhmatullin]

Control: found -1 dcraw/9.28-4

On Sun, Mar 24, 2024 at 05:21:05PM +, Debian Bug Tracking System wrote:
>  dcraw (9.28-4) unstable; urgency=low
>  .
>* Added missing headers. Closes: #1066465
Unfortunately, by overwriting the 9.28-3.1 changes you removed the fix,
not added it, as your independent fix is not enough:
https://buildd.debian.org/status/fetch.php?pkg=dcraw=armhf=9.28-4=1711301891=0
This also suggests that you have some workflow problems which you should
fix, as ignoring NMUs, working on already closed bugs and uploading
packages that don't build shouldn't ideally happen.

Processed: Re: Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

[Debian Bug Tracking System]

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

> reopen 1067486
Bug #1067486 {Done: Julian Andres Klode } 
[grub-efi-amd64-signed] Depends: grub-common (= 2.12-1) but it is not going to 
be installed
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1+2.12+1+b1.
> reassign 1067486 apt
Bug #1067486 [grub-efi-amd64-signed] Depends: grub-common (= 2.12-1) but it is 
not going to be installed
Bug reassigned from package 'grub-efi-amd64-signed' to 'apt'.
No longer marked as found in versions grub-efi-amd64-signed/1+2.12+1.
Ignoring request to alter fixed versions of bug #1067486 to the same values 
previously set
> severity 1067486 normal
Bug #1067486 [apt] Depends: grub-common (= 2.12-1) but it is not going to be 
installed
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory

[Andreas Metzler]

Control: tags -1 patch

On 2024-03-24 Andrey Rakhmatullin  wrote:
> On Wed, Mar 13, 2024 at 01:03:20PM +0100, Lucas Nussbaum wrote:
> > > ./config.h:2540:11: fatal error: trio.h: No such file or directory
> > >  2540 | # include "trio.h"
> > >   |   ^~~~
> (this suggests that using trio is not actually supported but that's
> irrelevant)
> This is caused by the stdio detection failing and should be fixed by
> adding #include  to the test case code in m4/needtrio.m4 but this
> package doesn't run autoreconf so fixing d/rules to at least do that is
> also needed.
[...]

As a hotfix touch-magic can also be used.

cu Andreas

diff --git a/debian/rules b/debian/rules
index e0872ed..ab41336 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,6 +19,9 @@ CFLAGS += -g -Wall
 
 #configure: configure-stamp
 configure-stamp:
+	# Avoid autoconf rebuild due to patching input files.
+	touch --reference=aclocal.m4 configure m4/needtrio.m4
+	touch --reference=Makefile.am m4/needtrio.m4
 	dh_testdir
 	# Add here commands to configure the package.
 	CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure \
--- lftp-4.9.2.orig/configure
+++ lftp-4.9.2/configure
@@ -57429,6 +57429,7 @@ else
   cat confdefs.h - <<_ACEOF >conftest.$ac_ext
 /* end confdefs.h.  */
 
+	#include 
 	 int main()
 	 {
 	unsigned long long x=0,x1;
--- lftp-4.9.2.orig/m4/needtrio.m4
+++ lftp-4.9.2/m4/needtrio.m4
@@ -9,6 +9,7 @@ AC_DEFUN([LFTP_NEED_TRIO],[
   else
 
   AC_RUN_IFELSE([AC_LANG_SOURCE([[
+	#include 
 	 int main()
 	 {
 	unsigned long long x=0,x1;

Processed: Re: Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066396 [src:lftp] lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: 
No such file or directory
Added tag(s) patch.

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

Bug#1067499: marked as done (libconsensuscore-dev: ships /usr/include/meson.build)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 18:24:23 +0100
with message-id <1bc9d224-1c9a-4692-bbb6-8c71fd589...@debian.org>
and subject line Re: libconsensuscore-dev: ships /usr/include/meson.build
has caused the Debian Bug report #1067499,
regarding libconsensuscore-dev: ships /usr/include/meson.build
to be marked as done.

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

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


-- 
1067499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libconsensuscore-dev
Version: 1.1.1+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

your package ships /usr/include/meson.build which is an overly generic
name and causes file conflicts with other packages doing the same
mistake.


Andreas
--- End Message ---
--- Begin Message ---

Version: 1.1.1+dfsg-5

Whoops, forgot to mark this in the changelog!


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

Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

[Eduard Bloch]

reopen 1067486
reassign 1067486 apt
severity 1067486 normal
thanks

Am Fri, Mar 22, 2024 at 11:46:02PM +0100 schrieb Julian Andres Klode:

> > Please upload a new version so grub-efi-amd64-signed can be installable.
> > Thanks!
> 
> I'm getting a bit tired of this. This is normal, the packages are
> automatically generated but need to be approved by ftpteam. 

This might be a normal condition but a) this is not transparent to user,
and b) it really does break apt's operation, at least partly.

For a) maybe we should make this somehow auto-checked remotely and shown
in reportbug? Or would you have a better idea?

And for b) all "dist-upgrade" or "full-upgrade" failed suddenly. Yes,
failing, user getting completely locked out. And "upgrade" operation
installed just a fraction of the potential candidates (there were more
reasons for that but the lack of dist-upgrade feature is still PITA).
And the reason has not been obvious, and even debugging with
-oDebug::pkgProblemResolver=true is NO FUN on bigger upgrades.

And the eventual solution was close examination, and some
guessing/observing that apt is confused and jumps between amd64 and
i386, and then some FORCE magic, i.e.

dpkg --remove --force-depends grub-common:i386

(don't ask me how this package got installed before, that system
installation has been migrated a lot). Another candidate was an old
iproute:i386 package which I also had to remove.

Best regards,
Eduard.

Bug#1066465: marked as done (dcraw: FTBFS: fujiturn.c:76:37: error: implicit declaration of function ‘ntohs’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 17:19:42 +
with message-id 
and subject line Bug#1066465: fixed in dcraw 9.28-4
has caused the Debian Bug report #1066465,
regarding dcraw: FTBFS: fujiturn.c:76:37: error: implicit declaration of 
function ‘ntohs’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"dcraw\" -DPACKAGE_TARNAME=\"dcraw\" 
> -DPACKAGE_VERSION=\"9.28\" -DPACKAGE_STRING=\"dcraw\ 9.28\" 
> -DPACKAGE_BUGREPORT=\"hr...@physics.muni.cz\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"dcraw\" -DVERSION=\"9.28\" -DHAVE_LIBM=1 -DHAVE_STDIO_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 
> -DSTDC_HEADERS=1 -DHAVE_JPEGLIB_H=1 -DHAVE_LIBJPEG=1 -DHAVE_LCMS2_H=1 
> -DHAVE_LIBLCMS2=1 -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 -O4 -c -o clean_crw.o clean_crw.c
> fujiturn.c: In function ‘main’:
> fujiturn.c:61:3: warning: ignoring return value of ‘fread’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>61 |   fread (in, iwide, sizeof *in, ifp);
>   |   ^~
> fujiturn.c:78:5: warning: ignoring return value of ‘fread’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>78 | fread (in, iwide, sizeof *in, ifp);
>   | ^~
> fujiturn.c: In function ‘main’:
> fujiturn.c:76:37: error: implicit declaration of function ‘ntohs’ 
> [-Werror=implicit-function-declaration]
>76 |   mid[orow*owide+ocol][i] = ntohs(in[icol][i]);
>   | ^
> fujiturn.c:90:28: error: implicit declaration of function ‘htons’ 
> [-Werror=implicit-function-declaration]
>90 | out[ocol][i] = htons (
>   |^
> fujiturn.c:61:3: warning: ignoring return value of ‘fread’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>61 |   fread (in, iwide, sizeof *in, ifp);
>   |   ^~
> fujiturn.c:78:5: warning: ignoring return value of ‘fread’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>78 | fread (in, iwide, sizeof *in, ifp);
>   | ^~
> clean_crw.c: In function ‘main’:
> clean_crw.c:54:5: warning: ignoring return value of ‘fread’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>54 | fread (buffer, 1, size, fp);
>   | ^~~
> fuji_green.c: In function ‘read_shorts’:
> fuji_green.c:72:29: error: implicit declaration of function ‘ntohs’ 
> [-Werror=implicit-function-declaration]
>72 |   if ((order == 0x4949) == (ntohs(0x1234) == 0x1234))
>   | ^
> fuji_green.c:73:5: error: implicit declaration of function ‘swab’ 
> [-Werror=implicit-function-declaration]
>73 | swab (pixel, pixel, count*2);
>   | ^~~~
> fuji_green.c: In function ‘write_psd’:
> fuji_green.c:249:11: error: implicit declaration of function ‘htonl’ 
> [-Werror=implicit-function-declaration]
>   249 |   hw[0] = htonl(height*2);  /* write the header */
>   |   ^
> fuji_green.c: In function ‘main’:
> fuji_green.c:307:9: error: implicit declaration of function ‘isatty’ 
> [-Werror=implicit-function-declaration]
>   307 | if (isatty(1)) {
>   | ^~
> fuji_green.c: In function ‘read_shorts’:
> fuji_green.c:71:3: warning: ignoring return value of ‘fread’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>71 |   fread (pixel, 2, count, ifp);
>   |   ^~~~
> fuji_green.c: In function ‘parse_tiff’:
> 

Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

[Eduard Bloch]

On Fri, 22 Mar 2024 23:46:02 +0100 Julian Andres Klode 
 wrote:
> Version: 1+2.12+1+b1
> 
> (this should be the right version when it gets accepted)
> 
> On Fri, Mar 22, 2024 at 06:23:06PM +0800, Tianyu Chen wrote:
> > Package: grub-efi-amd64-signed
> > Version: 1+2.12+1
> > Severity: serious
> > X-Debbugs-Cc: sweetyf...@deepin.org
> > 
> > Hi,
> > 
> > grub-efi-amd64-signed seems uninstallable now in sid. This might caused
> > by a binNMU in src:grub2.
> > 
> > The following packages have unmet dependencies:
> >  grub-efi-amd64-signed : Depends: grub-common (= 2.12-1) but it is not 
> > going to be installed
> > 
> > $ apt policy grub-common
> > grub-common:
> >   Installed: (none)
> >   Candidate: 2.12-1+b1
> >   Version table:
> >  2.12-1+b1 500
> > 500 http://mirrors.cernet.edu.cn/debian sid/main amd64 Packages
> > 
> > Please upload a new version so grub-efi-amd64-signed can be installable.
> > Thanks!
> 
> I'm getting a bit tired of this. This is normal, the packages are
> automatically generated but need to be approved by ftpteam. 
> 
> And people are probably understandably hesitant to accept them because future
> binNMUs are expected.
> 
> So Please do not file bugs for them, it is out of our hands.
> 
> -- 
> debian developer - deb.li/jak | jak-linux.org - free software dev
> ubuntu core developer  i speak de, en
> 
> 

Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

[Eduard Bloch]

On Fri, 22 Mar 2024 23:46:02 +0100 Julian Andres Klode 
 wrote:
> Version: 1+2.12+1+b1
> 
> (this should be the right version when it gets accepted)
> 
> On Fri, Mar 22, 2024 at 06:23:06PM +0800, Tianyu Chen wrote:
> > Package: grub-efi-amd64-signed
> > Version: 1+2.12+1
> > Severity: serious
> > X-Debbugs-Cc: sweetyf...@deepin.org
> > 
> > Hi,
> > 
> > grub-efi-amd64-signed seems uninstallable now in sid. This might caused
> > by a binNMU in src:grub2.
> > 
> > The following packages have unmet dependencies:
> >  grub-efi-amd64-signed : Depends: grub-common (= 2.12-1) but it is not 
> > going to be installed
> > 
> > $ apt policy grub-common
> > grub-common:
> >   Installed: (none)
> >   Candidate: 2.12-1+b1
> >   Version table:
> >  2.12-1+b1 500
> > 500 http://mirrors.cernet.edu.cn/debian sid/main amd64 Packages
> > 
> > Please upload a new version so grub-efi-amd64-signed can be installable.
> > Thanks!
> 
> I'm getting a bit tired of this. This is normal, the packages are
> automatically generated but need to be approved by ftpteam. 
> 
> And people are probably understandably hesitant to accept them because future
> binNMUs are expected.
> 
> So Please do not file bugs for them, it is out of our hands.
> 
> -- 
> debian developer - deb.li/jak | jak-linux.org - free software dev
> ubuntu core developer  i speak de, en
> 
> 

Bug#1066500: marked as done (vorbisgain: FTBFS: misc.c:268:9: error: implicit declaration of function ‘isatty’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 17:10:47 +
with message-id 
and subject line Bug#1066500: fixed in vorbisgain 0.37-2.1
has caused the Debian Bug report #1066500,
regarding vorbisgain: FTBFS: misc.c:268:9: error: implicit declaration of 
function ‘isatty’ [-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.)


-- 
1066500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vorbisgain
Version: 0.37-2
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.   -Wdate-time -D_FORTIFY_SOURCE=2  -O2 
> -fsigned-char -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> `test -f 'misc.c' || echo './'`misc.c
> misc.c: In function ‘get_console_size’:
> misc.c:268:9: error: implicit declaration of function ‘isatty’ 
> [-Werror=implicit-function-declaration]
>   268 | if (isatty(fd))
>   | ^~
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:256: misc.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/vorbisgain_0.37-2_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: vorbisgain
Source-Version: 0.37-2.1
Done: Håvard F. Aasen 

We believe that the bug you reported is fixed in the latest version of
vorbisgain, 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.
Håvard F. Aasen  (supplier of updated vorbisgain 
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: Sun, 24 Mar 2024 09:00:42 +0100
Source: vorbisgain
Architecture: source
Version: 0.37-2.1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Martí 
Changed-By: Håvard F. Aasen 
Closes: 1066500
Changes:
 vorbisgain (0.37-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch to fix missing header declaration. (Closes: #1066500)
Checksums-Sha1:
 c531d9c22b94704821003f978cb2747b6aff4821 1616 vorbisgain_0.37-2.1.dsc
 83b384a10c708943b650bb0bdaef84e62668796e 10252 
vorbisgain_0.37-2.1.debian.tar.xz
 1cfda125c76e16fb1e23b50c5c88c334a01e1dcb 6242 
vorbisgain_0.37-2.1_source.buildinfo
Checksums-Sha256:
 30a3e3f3966614e807631fd47a5101793c535a442ed687c38a43863f699d6373 1616 
vorbisgain_0.37-2.1.dsc
 414d80e86c3112a3ed68efa86e0f8596b43db95e7f18295d603662780b18ce90 10252 
vorbisgain_0.37-2.1.debian.tar.xz
 be4de501d55a36490f11f9208b63c660806875d4f20aee484ae792e67d979a88 6242 
vorbisgain_0.37-2.1_source.buildinfo
Files:
 d31061373ae24e06c4c7cb5577f04e01 1616 sound optional vorbisgain_0.37-2.1.dsc
 afb6837f4cc5084b668ccbda71a06e25 10252 sound optional 
vorbisgain_0.37-2.1.debian.tar.xz
 843c48b5e725aaa8bc37de2c60a2acf7 6242 sound optional 
vorbisgain_0.37-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1066324: marked as done (lucy: FTBFS: poly.c:22:9: error: implicit declaration of function ‘abi_code’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 17:09:25 +
with message-id 
and subject line Bug#1066324: fixed in lucy 1.20-4
has caused the Debian Bug report #1066324,
regarding lucy: FTBFS: poly.c:22:9: error: implicit declaration of function 
‘abi_code’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2  -c -o poly.o poly.c
> done!
> qual_trim.c:10:1: warning: "/*" within comment [-Wcomment]
>10 | /* qual_trim.c - Quality trimming algorithm which determines a "clean"
>   |  
> qual_trim.c:11:1: warning: "/*" within comment [-Wcomment]
>11 | /*range for a sequence based on its phred quality values.
>   |  
> qual_trim.c:12:1: warning: "/*" within comment [-Wcomment]
>12 | /*
>   |  
> qual_trim.c:13:1: warning: "/*" within comment [-Wcomment]
>13 | /* Written by Michael Holmes, 4/13/99.
>   |  
> qual_trim.c:14:1: warning: "/*" within comment [-Wcomment]
>14 | /*
>   |  
> qual_trim.c:15:1: warning: "/*" within comment [-Wcomment]
>15 | /* 1/31/2000, Michael Holmes -- Added default_windows().
>   |  
> qual_trim.c:16:1: warning: "/*" within comment [-Wcomment]
>16 | /* 2/15/2000, Michael Holmes -- Added bracket_clean_range() and
>   |  
> qual_trim.c:17:1: warning: "/*" within comment [-Wcomment]
>17 | /*set_bracket().
>   |  
> qual_trim.c:18:1: warning: "/*" within comment [-Wcomment]
>18 | /* 2/18/2000, Michael Holmes -- Minor change to test-mode output only.
>   |  
> qual_trim.c:19:1: warning: "/*" within comment [-Wcomment]
>19 | /*
>   |  
> qual_trim.c:20:1: warning: "/*" within comment [-Wcomment]
>20 | /* Copyright (C) 1999, 2000, The Institute for Genomic Research.  All 
> rights
>   |  
> qual_trim.c:21:1: warning: "/*" within comment [-Wcomment]
>21 | /* reserved.
>   |  
> qual_trim.c:22:1: warning: "/*" within comment [-Wcomment]
>22 | /*
>   |  
> qual_trim.c:23:1: warning: "/*" within comment [-Wcomment]
>23 | /* Note: phred quality values are based on the log (base 10) of the
>   |  
> qual_trim.c:24:1: warning: "/*" within comment [-Wcomment]
>24 | /* probability that the corresponding base call is in error:
>   |  
> qual_trim.c:25:1: warning: "/*" within comment [-Wcomment]
>25 | /*
>   |  
> qual_trim.c:26:1: warning: "/*" within comment [-Wcomment]
>26 | /*Q = -10 log(P_error)
>   |  
> qual_trim.c:27:1: warning: "/*" within comment [-Wcomment]
>27 | /*
>   |  
> qual_trim.c:28:1: warning: "/*" within comment [-Wcomment]
>28 | /* Thanks to Granger Sutton for valuable suggestions.
>   |  
> qual_trim.c:29:1: warning: "/*" within comment [-Wcomment]
>29 | /*
>   |  
> qual_trim.c:30:1: warning: "/*" within comment [-Wcomment]
>30 | /* The main functions of interest to external code (such as lucy) are
>   |  
> qual_trim.c:31:1: warning: "/*" within comment [-Wcomment]
>31 | /* default_windows() and quality_trim().  The grim() function 
> emulates the
>   |  
> qual_trim.c:32:1: warning: "/*" within comment [-Wcomment]
>32 | /* interface that was used by the old quality trimmimg algorithm 
> (grim),
>   |  
> qual_trim.c:33:1: warning: "/*" within comment [-Wcomment]
>33 | /* but it is not called by lucy.  The main() function is compiled 
> only if
>   |  
> qual_trim.c:34:1: warning: "/*" within comment [-Wcomment]
>34 | /* TEST_THIS_CODE is #defined.
>   |  
> qual_trim.c:35:1: warning: "/*" within comment [-Wcomment]
>35 | /*
>   |  
> qual_trim.c:36:1: warning: "/*" within comment [-Wcomment]
>36 | /* The calling hierarchy is:
>   |  
> qual_trim.c:37:1: warning: 

Bug#1067175: marked as done (exaile: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 16:49:59 +
with message-id 
and subject line Bug#1067175: fixed in exaile 4.1.3+dfsg-3
has caused the Debian Bug report #1067175,
regarding exaile: hard-coded dependency on libgtk-3-0 will become uninstallable 
on armel/armhf
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.)


-- 
1067175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exaile
Version: 4.1.3+dfsg-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

exaile is an Architecture: all package, but has a direct dependency on
libgtk-3-0, as well as an indirect dependency on libgtk-3-0t64 via
gir1.2-gtk-3.0.

On the architectures affected by the 64-bit time_t transition (notably
armel and armhf), this is an impossible dependency, because libgtk-3-0 and
libgtk-3-0t64 conflict.

Please remove the explicit dependency on libgtk-3-0. For Python code
that uses GTK via GObject-Introspection, it is sufficient to depend
on gir1.2-gtk-3.0.

More information about this transition is available on
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: exaile
Source-Version: 4.1.3+dfsg-3
Done: luzip665 

We believe that the bug you reported is fixed in the latest version of
exaile, 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.
luzip665  (supplier of updated exaile 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: Sat, 23 MAR 2024 12:32:16 +0200
Source: exaile
Architecture: source
Version: 4.1.3+dfsg-3
Distribution: unstable
Urgency: low
Maintainer: luzip665 
Changed-By: luzip665 
Closes: 1067175
Changes:
 exaile (4.1.3+dfsg-3) unstable; urgency=low
 .
   * Removing direct dependency to libgtk-3-0 (Closes: #1067175)
Checksums-Sha1:
 811c6f6f80802fef389acaa43783c371f4f79b89 1648 exaile_4.1.3+dfsg-3.dsc
 153307431d7cb9ff136213055f34c14ccfdc98bc 71512 
exaile_4.1.3+dfsg-3.debian.tar.xz
 5ad55f2903e5319a11b5ef8d8d16392ddc9904a1 7683 
exaile_4.1.3+dfsg-3_source.buildinfo
Checksums-Sha256:
 3781db7404e307d9d3952c5d9f6082501cb835d22562270f1d81f8df12a653e4 1648 
exaile_4.1.3+dfsg-3.dsc
 082f0b3c1aba972e284a0792d9d0f6aa874cf12be84e07ae89ace7eb65049555 71512 
exaile_4.1.3+dfsg-3.debian.tar.xz
 2bbf66f243e34984cf74465167da461865553ca8f66c1050c6359d123eca555e 7683 
exaile_4.1.3+dfsg-3_source.buildinfo
Files:
 71a514e238ff2704b26e901e78a92c59 1648 sound optional exaile_4.1.3+dfsg-3.dsc
 9dd265e54ad6c1670e36c9129a24c0d4 71512 sound optional 
exaile_4.1.3+dfsg-3.debian.tar.xz
 5cb83f67c8b4b2820fcba151b5de8728 7683 sound optional 
exaile_4.1.3+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYAVaIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFIBAC/9cYUq7Z9AWPX4yLp17SeOmt2aCwD/XwTVg
BXYH6TZst3tzh5ioRroRkVlBxUPyiuDBwHwThZr/ysrToG7ji9t2LMo9FcoAW2gD
sNc2FeO2Yf61yOR8JgKTSVi+4Qs2tG6dDikoMjPAjSWf/HVoG9hesYMOdT5E9+nh
R50pALAW75RXv2cad0XMHfupuCcNUsO2ilmVSk7/ndCGii6NXg0b2RGPJRj1m6Vo
xkhtZKboslB2u0VAsR6syr07dg9zMPV3RZxSBf0PvNgXJ1YT2QRIoxG12p+RoIRF
0saUKHLY8+e2lCHikHTiADJnq0BIz+inKXEhlwjRtnOu+jUPmCkzmCxDkwD8rsYg
JEyIL1VJabtAnhFkDRdRGNS9pV3pIF8OiWPXdK/WEWLwOPO2PRT2KnBtD+cAM/gk
xGwOP9uzqSQej8e4neqvDpyuBdRh2vz0wveSuaJ0BXV3TkoySb6yBVybQQNpDxOO
3fiZEHeXVMx7VeOdnlMDRnGGVIFtIcU=
=AY2f
-END PGP SIGNATURE-



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

Bug#1067257: marked as done (astroml: 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 Sun, 24 Mar 2024 16:49:16 +
with message-id 
and subject line Bug#1067257: fixed in astroml 1.0.2-4
has caused the Debian Bug report #1067257,
regarding astroml: 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --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/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files 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.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running config
> I: pybuild base:305: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files 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.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> 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/config/setupcfg.py:293: 
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
> 
> 
> 
> The license_file parameter is deprecated, use license_files 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.
> 
> 
> 
> !!
>   parsed = self.parsers.get(option_name, lambda x: x)(value)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/crossmatch.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/resample.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/correlation.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/sum_of_norms.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/filters.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/decorators.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/conftest.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/lumfunc.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/cosmology.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> copying astroML/fourier.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML
> creating /<>/.pybuild/cpython3_3.12_astroml/build/astroML/tests
> copying astroML/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_astroml/build/astroML/tests
> copying 

Bug#1067136: marked as done (astroml: numpy.testing.run_module_suite no longer exists)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 16:49:15 +
with message-id 
and subject line Bug#1067136: fixed in astroml 1.0.2-4
has caused the Debian Bug report #1067136,
regarding astroml: numpy.testing.run_module_suite no longer exists
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.)


-- 
1067136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astroml
Version: 1.0.2-3
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package has an autopkgtest regression due to a change in NumPy.
The run_module_suite function used to be a wrapper for nose, which is no 
longer supported. NumPy upstream recommends that tests be run using 
pytest directly.


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmX5YLEACgkQ+C8H+466
LVnF3wwAhy8xIYazieR4ZeawBRHJaeSZh5NjYZQRHzFJJeyqL0YRVm6zqjyakdT7
tw1aClmxk7sC0z82FLkkFYO5exbzF2Y+VXYFejyKnENo21WkYd9sRXbOU0gtgvCL
iXodr1r3PFfbvJ89jJeo/TwqWZlgqs+jnP+Pr8bfYWtVLuIWGCDmVa9sKabh18Xg
RWZqp4LBn1miRZYzQtZfEJawSIEy3KxfWpQpn2gXq8IiVn29wIbs2D86IRp/ldUu
vgss94o58ofKehq+h4cOaFHP/OzR9gG+Sf5wE4rOYXLuq2v4OSa89Z6qkEOw7x+o
TDR9Oi+uh/41ArtWYW2dyNgr0rdIuTqbppE6NYp6iV7lBtFMMoMfFAR+RjHTm7DI
2/n7mC8e6Iw8e46GBR3Ku6oVCP6Ls6AOjIpghQ6ujWY9LvuJ+KnmnuCdxJepTdP1
IBxB9Il00AXANyyg7eZktay3LGbIw5SxnBsbqon7jAKbZprFpRB376ZSrohTKUZx
pcq2GAen
=MSgE
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: astroml
Source-Version: 1.0.2-4
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
astroml, 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.
Michael R. Crusoe  (supplier of updated astroml 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: Sun, 24 Mar 2024 17:41:22 +0100
Source: astroml
Architecture: source
Version: 1.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Michael R. Crusoe 
Closes: 1067136 1067257
Changes:
 astroml (1.0.2-4) unstable; urgency=medium
 .
   * Team upload.
   * d/patches/newer_numpy.patch: cherry-pick fix for numpy>=1.25 from
 upstream. Closes: #1067136, #1067257
   * d/control: enable PEP517 building using pyproject.
   * d/tests/control: run on all versions of Python.
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * watch file standard 4 (routine-update)
   * d/gitlab-ci.yml: build the nocheck profile
Checksums-Sha1:
 8499e030d5e350998d31e013efede5e0c1b050b5 2361 astroml_1.0.2-4.dsc
 7d00b5a98136e5f6fa24f16c362b06d5c3f4b17a 6004 astroml_1.0.2-4.debian.tar.xz
 50a23b21ad89a27de5a4b1969774b0c5dfeb25fb 11812 astroml_1.0.2-4_source.buildinfo
Checksums-Sha256:
 1e137826703bf14f3718d2e331bdacb06331479f8157f12f4b75f02fce563437 2361 
astroml_1.0.2-4.dsc
 22e1308df308606ddaab7faad0d87f62ed4ad2757f0e52ee0db296e118a48f72 6004 
astroml_1.0.2-4.debian.tar.xz
 6ba3c88e8cc44753cb2b500cdfc6aa909f0d31fae716f585daf662692670140c 11812 
astroml_1.0.2-4_source.buildinfo
Files:
 d4d7048f7b8c441d8b394f6c3bd11cd0 2361 python optional astroml_1.0.2-4.dsc
 ea48b65d011a7c1dfdc006d91799e4cf 6004 python optional 
astroml_1.0.2-4.debian.tar.xz
 d3b34333a9b0eecfd0935ec849e34c45 11812 python optional 
astroml_1.0.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmYAWGoACgkQPCZ2P2xn
5uK32g/+PADm2yGSH01jaTDVl4lDUw8JJ5ibq8WUS6vVfLttH5WMvUMmkp2on0IY
PG1iYU2RW1wszrckHXY+XwY3cUmVbiza5bBCNzR3Y6ALjvVKytqfHYonzowEbdwQ
t7CrYuTBJMJ/WgIGawjKruroqCYwaUrZb/X+p5chncErOPpFHPUaczJ/JpCzfLZO
ZkxVKQrKP1rA+zWgcVuHiYmA5PUf8v5bm13fMTnKf5ikzpHpB//uhS2tCZUXgRJs
mjQnkc4Fi77CvS2NNTRZgNSLnSCtMX+dqfQqRhRF/7BndzH/v0LN9i10vwC+L6Is
8QRQawTZDzNEd/tpZQcoub9JdehrTun8fJp2P6Sk0Nxc/skhxpaMHjOCOgeL9kNU
Jks9Z/omzdEpKpITBSTKuah9pXg5e30K001JL12fqFukJyXL3TAsgTaUEqkA/8W6
UsLka0mFnkv5pa6u/JypxwjcCicQI7Yfj4OnX0fsAEOho+N+yA06OPT2GbpmXHhY
/1WfpU8R9IgSTm9svzGqbfvCWJq3MdvLueaROPcwkMXjSXMwMx+YFWNgZwQtwTC1

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

[Daniel Gröber]

Hi Matthias,

On Thu, Mar 21, 2024 at 11:16:56PM +0100, Matthias Klose wrote:
> Package: src:yosys-plugin-ghdl

> * Use ghdl-mcode instead of ghdl-gcc as it's more portable
> 
> but ghdl-mcode is only available on amd64 and i386.  With this choice you're
> making things worse.

My bad, I was under the impression mcode was an interpreter backend. Will
fix this with the next upload.

--Daniel


signature.asc
Description: PGP signature

Bug#1067609: marked as done (gbrainy: Avoid hardcoded libcanberra-gtk3-0 build-depends, use libcanberra-gtk3-dev)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 16:21:11 +
with message-id 
and subject line Bug#1067609: fixed in gbrainy 1:2.4.6-2
has caused the Debian Bug report #1067609,
regarding gbrainy: Avoid hardcoded libcanberra-gtk3-0 build-depends, use 
libcanberra-gtk3-dev
to be marked as done.

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

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


-- 
1067609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gbrainy
Version: 1:2.4.6-1
Severity: serious
Tags: patch
X-Debbugs-Cc: juli...@ubuntu.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch


*** /tmp/tmpxuguf7sd/bug_body

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

  * Replace libcanberra-gtk3-0 build-depends with libcanberra-gtk3-dev to
pick up the latest libcanberra-gtk3 soname.

Otherwise it fails to build with libcanberra-gtk3-0-t64

Thanks for considering the patch.

*** /tmp/tmpxuguf7sd/gbrainy_1:2.4.6-1ubuntu1.debdiff
diff -Nru gbrainy-2.4.6/debian/control.in gbrainy-2.4.6/debian/control.in
--- gbrainy-2.4.6/debian/control.in 2024-03-19 07:10:14.0 +0100
+++ gbrainy-2.4.6/debian/control.in 2024-03-24 16:50:00.0 +0100
@@ -12,7 +11,7 @@
  dh-sequence-gnome,
  intltool (>= 0.35),
  itstool,
- libcanberra-gtk3-0,
+ libcanberra-gtk3-dev,
  libgtk3.0-cil-dev,
  librsvg2-dev,
  yelp-tools


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

Kernel: Linux 6.8.0-11-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
--- End Message ---
--- Begin Message ---
Source: gbrainy
Source-Version: 1:2.4.6-2
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gbrainy 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: Sun, 24 Mar 2024 12:10:52 -0400
Source: gbrainy
Built-For-Profiles: noudeb
Architecture: source
Version: 1:2.4.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1067609
Changes:
 gbrainy (1:2.4.6-2) unstable; urgency=medium
 .
   [ Julian Andres Klode ]
   * Build-Depend on libcanberra-gtk3-dev instead of hard-coded library name
 (Closes: #1067609)
 .
   [ Jeremy Bícha ]
   * Stop using debian/control.in & dh-sequence-gnome
Checksums-Sha1:
 5023abac509da822d103b28fdb65d8723715057c 2117 gbrainy_2.4.6-2.dsc
 5535984e8adfadbe70bd767067af2819cd269867 13324 gbrainy_2.4.6-2.debian.tar.xz
 261d6d125815cca8dc248ee414a9f1c32ecb92cc 18123 gbrainy_2.4.6-2_source.buildinfo
Checksums-Sha256:
 259a5bdfb6c6f7d51f8be095f279d7ecd0a5fb3fee7f57e74513c23fd1944902 2117 
gbrainy_2.4.6-2.dsc
 fff36df4ccec3e79aacec89ac48ec158cad8833a80bdee99541596fdf6b1c352 13324 
gbrainy_2.4.6-2.debian.tar.xz
 16108f2b59f122e4f4572d1c352f8b09de18784f001ad145a3b66a46a245f507 18123 
gbrainy_2.4.6-2_source.buildinfo
Files:
 6ae0235f11f989cee8ac545394642424 2117 games optional gbrainy_2.4.6-2.dsc
 c290bbc17b64bfc853d48e3f75269e5b 13324 games optional 
gbrainy_2.4.6-2.debian.tar.xz
 df7a28a05d774d92ae94e9e011858db3 18123 games optional 
gbrainy_2.4.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYAULgACgkQ5mx3Wuv+
bH2T4w/9FeduSGtlS6NQ2c6RzB0/nvbyNCkupFAR2alX2wu+wbHpAzjNuDuWP3KC
JSZfivf9wXTAz6prG87XvG2V/Z6AwgYzMKjeu9D0Oa243KPlD7CA17pYHXIArz2I
pgb+vV0NQpXhVdofrTOwcUSKh+/vkb1Nn73kEahTpv6xlDnHibM0jDfbTmV9hqjf
C5LIh3trjKL/K+1Qa4SgedPHk/nRLx8Ff4imWfiEqAuTsWFzr/bzk+gMeUVn8a5C

Bug#1067609: gbrainy: Avoid hardcoded libcanberra-gtk3-0 build-depends, use libcanberra-gtk3-dev

[Julian Andres Klode]

Package: gbrainy
Version: 1:2.4.6-1
Severity: serious
Tags: patch
X-Debbugs-Cc: juli...@ubuntu.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch


*** /tmp/tmpxuguf7sd/bug_body

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

  * Replace libcanberra-gtk3-0 build-depends with libcanberra-gtk3-dev to
pick up the latest libcanberra-gtk3 soname.

Otherwise it fails to build with libcanberra-gtk3-0-t64

Thanks for considering the patch.

*** /tmp/tmpxuguf7sd/gbrainy_1:2.4.6-1ubuntu1.debdiff
diff -Nru gbrainy-2.4.6/debian/control.in gbrainy-2.4.6/debian/control.in
--- gbrainy-2.4.6/debian/control.in 2024-03-19 07:10:14.0 +0100
+++ gbrainy-2.4.6/debian/control.in 2024-03-24 16:50:00.0 +0100
@@ -12,7 +11,7 @@
  dh-sequence-gnome,
  intltool (>= 0.35),
  itstool,
- libcanberra-gtk3-0,
+ libcanberra-gtk3-dev,
  libgtk3.0-cil-dev,
  librsvg2-dev,
  yelp-tools


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

Kernel: Linux 6.8.0-11-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#1066983: monopd: Fails to start monopd.service

[Sylvain Rochet]

Hi,

On Sat, Mar 23, 2024 at 09:35:38PM +0100, Sylvain Rochet wrote:
> 
> That might be related to the latest change "Add a service template for 
> compatibility reasons with monopd.socket.".

Actually, the main problem is /lib/systemd/system/monopd.socket which 
set Accept=yes while monopd needs Accept=no (which is the default value).

By the way, I just released monopd 0.10.3 that detect this 
misconfiguration and exit instead of spinning forever over accept() :)

Sylvain


signature.asc
Description: Digital signature

Bug#1066113: guix: CVE-2024-27297

[pelzflorian (Florian Pelz)]

On 2024-03-16, Vagrant Cascadian wrote:
> For anyone with Guix or Nix installed, if I understand correctly, it
> basically allows arbitrarily replacing the source code for anything that
> you might build using Guix or Nix.

Yes, for multi-user systems and people running untrusted code in “guix
shell -CW” container isolation, there is risk.

Regards,
Florian

Bug#1066375: canna: FTBFS: context.c:105:13: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration]

[Andreas Metzler]

On 2024-03-13 Lucas Nussbaum  wrote:
> Source: canna
> Version: 3.7p3-20
> Severity: serious
[...]
> 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

Hello,

I started working on this, but stopped. There are dozens of instances of
implicit internal[1] function references without prototype. The whole thing
looks very dated.

I cannot judge how important canna is, popcon is low (29 installations).
It might be time to drop canna, Fedora already did, there has not been
upstream work for more almost 20 years, also it has been maintained with
QA uploads and NMUs since 2008

Cc-ing packages with b-d on libcanna1g-dev to perhaps get some further
input.

cu Andreas


[1] defined without prototype in foo.c, also used in bar.c
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined

[Alberto Bertogli]

On Mon, Mar 18, 2024 at 12:29:40PM +, Chris Lamb wrote:

Dear Alberto,


Hi!



Hope this finds you well. Any quick/immediate ideas on what might be
behind this build failure? Note that this is on ARM architectures
rather than amd64 — I often misread and conflate them at speed. :) Oh,
and I can't reproduce this on amd64 locally, at least, so I don't think
it is, say, due to some *general* update to the GLIBC build toolchain.


Nothing obvious.

It's a bit strange because the "symbol X already defined" errors most 
likely come from the assembler when building the individual files, not 
from linking stage.


While it's impossible to be 100% sure because of the parallel build and 
the lack of command-output correlation in the logs, everything points to 
that being the case.


I'll try to get a debian install to boot for armhf, but it'll take me a 
bit because it's not straightforward (to put it mildly :).


How urgent/important is this issue?

Thanks,
Alberto




- Original message -
From: Sebastian Ramacher 
To: Debian Bug Tracking System 
Subject: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: 
symbol `open64' is already defined
Date: Friday, 15 March 2024 6:50 PM

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

https://buildd.debian.org/status/fetch.php?pkg=libfiu=armhf=1.2-2=1710292712=0

cc -D_XOPEN_SOURCE=600 -fPIC -DFIU_ENABLE=1 -D_LARGEFILE64_SOURCE=1 -I. -I../../libfiu/ -g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -D_GNU_SOURCE -c codegen.c -o codegen.o
/tmp/cc54dEva.s: Assembler messages:
/tmp/cc54dEva.s:726: Error: symbol `open64' is already defined
/tmp/cchEoHpC.s: Assembler messages:
/tmp/cchEoHpC.s:474: Error: symbol `mmap64' is already defined
make[4]: *** [Makefile:67: modules/posix.mm.mod.o] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: *** [Makefile:67: modules/posix.custom.o] Error 1
/tmp/cct4HXD3.s: Assembler messages:
/tmp/cct4HXD3.s:1810: Error: symbol `pread64' is already defined
/tmp/cct4HXD3.s:3995: Error: symbol `pwrite64' is already defined
/tmp/cct4HXD3.s:5803: Error: symbol `truncate64' is already defined
/tmp/cct4HXD3.s:6480: Error: symbol `ftruncate64' is already defined
/tmp/ccInAMjZ.s: Assembler messages:
/tmp/ccInAMjZ.s:437: Error: symbol `fopen64' is already defined
make[4]: *** [Makefile:67: modules/posix.io.mod.o] Error 1
/tmp/ccInAMjZ.s:1099: Error: symbol `freopen64' is already defined
/tmp/ccInAMjZ.s:3393: Error: symbol `tmpfile64' is already defined
/tmp/ccInAMjZ.s:5973: Error: symbol `ftello64' is already defined
/tmp/ccInAMjZ.s:7007: Error: symbol `fseeko64' is already defined
/tmp/ccInAMjZ.s:7699: Error: symbol `fsetpos64' is already defined
make[4]: *** [Makefile:67: modules/posix.stdio.mod.o] Error 1





Alberto

Bug#1067604: src:libcdk5: autopkgtest regression, tests the old version and more issues

[Paul Gevers]

Source: libcdk5
Version: 5.0.20230201-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you 
please investigate the situation and fix it? I copied some of the output 
at the bottom of this report. I note that the version it tests against 
is the previous version.


On top of that, this test is really, really superficial, please mark it 
as such [2]. Also, autopkgtest is supposed to be tested against the 
*installed* packages. It doesn't look like your test needs a build, can 
you please remove the "build-needed" restriction (it's probably what's 
causing the migration test to fail in view of the time_t)?


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
[2] https://release.debian.org/testing/rc_policy.txt section 6(a) (bottom)

https://ci.debian.net/packages/libc/libcdk5/unstable/amd64/44302393/

 94s autopkgtest [12:22:08]: test command1: [ "$(dash cdk-config 
--version)" == '5.0.20180306' ]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066543: marked as done (ucx: FTBFS: cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror])

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 12:21:02 +
with message-id 
and subject line Bug#1066543: fixed in ucx 1.16.0+ds-5
has caused the Debian Bug report #1066543,
regarding ucx: FTBFS: cc1plus: error: ‘-Werror=’ argument 
‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror]
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.)


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

Hi,

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

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

Relevant part (hopefully):
> /bin/bash ../../../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H 
> -I. -I../../../..  -DCPU_FLAGS="" -I/<>/src -I/<> 
> -I/<>/src -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall 
> -Werror -funwind-tables -Wno-missing-field-initializers -Wno-unused-parameter 
> -Wno-unused-label -Wno-long-long -Wno-endif-labels -Wno-sign-compare 
> -Wno-multichar -Wno-deprecated-declarations -Winvalid-pch -fopenmp -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -nostdlib  -std=c++11 -c -o 
> libucxperf_la-ucp_tests.lo `test -f 'ucp_tests.cc' || echo './'`ucp_tests.cc
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../.. -DCPU_FLAGS= 
> -I/<>/src -I/<> -I/<>/src 
> -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall -Werror -funwind-tables 
> -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label 
> -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar 
> -Wno-deprecated-declarations -Winvalid-pch -Wno-pointer-sign 
> -Werror-implicit-function-declaration -Wno-format-zero-length 
> -Wnested-externs -Wshadow -Werror=declaration-after-statement -fopenmp -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c libperf_memory.c  -fPIC -DPIC 
> -DUCX_SHARED_LIB -o .libs/libucxperf_la-libperf_memory.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../.. -DCPU_FLAGS= 
> -I/<>/src -I/<> -I/<>/src 
> -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall -Werror -funwind-tables 
> -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label 
> -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar 
> -Wno-deprecated-declarations -Winvalid-pch -Wno-pointer-sign 
> -Werror-implicit-function-declaration -Wno-format-zero-length 
> -Wnested-externs -Wshadow -Werror=declaration-after-statement -fopenmp -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c libperf.c  -fPIC -DPIC 
> -DUCX_SHARED_LIB -o .libs/libucxperf_la-libperf.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../.. -DCPU_FLAGS= 
> -I/<>/src -I/<> -I/<>/src 
> -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall -Werror -funwind-tables 
> -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label 
> -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar 
> -Wno-deprecated-declarations -Winvalid-pch -Wno-pointer-sign 
> -Werror-implicit-function-declaration -Wno-format-zero-length 
> -Wnested-externs -Wshadow -Werror=declaration-after-statement -fopenmp -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c libperf_thread.c  -fPIC -DPIC 
> -DUCX_SHARED_LIB -o .libs/libucxperf_la-libperf_thread.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. -DCPU_FLAGS= 
> -I/<>/src -I/<> -I/<>/src 
> -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall -Werror -funwind-tables 
> -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label 
> -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar 
> -Wno-deprecated-declarations -Winvalid-pch -fopenmp -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> 

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

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 11:54:55 +
with message-id 
and subject line Bug#1067208: fixed in umockdev 0.18.1-1
has caused the Debian Bug report #1067208,
regarding umockdev: #error "_TIME_BITS=64 is allowed only with 
_FILE_OFFSET_BITS=64"
to be marked as done.

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

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


-- 
1067208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: umockdev
Version: 0.18.0-1
Severity: serious
Justification: FTBFS on t64-affected archs
X-Debbugs-Cc: t...@mirbsd.de
Tags: ftbfs

cc -Ilibumockdev-preload.so.0.0.0.p -I. -I.. -fdiagnostics-color=always -Wall 
-Winvalid-pch -std=gnu11 -Werror=missing-prototypes -Werror=strict-prototypes 
-Werror=nested-externs -Werror=pointer-arith 
-Werror=implicit-function-declaration -Werror=implicit-int 
-Werror=int-conversion -Werror=old-style-definition -Werror=pointer-arith 
-Werror=init-self -Werror=format-security -Werror=format=2 -Werror=return-type 
-Werror=uninitialized -Wcast-align -Wno-error=pragmas 
-Wno-error=discarded-qualifiers -Wno-error=incompatible-pointer-types 
-Wno-error=pointer-sign -Wno-unused-but-set-variable -Wno-unused-function 
-Wno-unused-label -Wno-unused-value -Wno-unused-variable -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=default -MD 
-MQ libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o -MF 
libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o.d -o 
libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o -c 
../src/libumockdev-preload.c
In file included from /usr/include/features.h:393,
 from /usr/include/assert.h:35,
 from ../src/libumockdev-preload.c:31:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
only with _FILE_OFFSET_BITS=64"
   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^


I admit I don’t exactly see what’s going on here. Does it
maybe #unset _FILE_OFFSET_BITS or something?
--- End Message ---
--- Begin Message ---
Source: umockdev
Source-Version: 0.18.1-1
Done: Martin Pitt 

We believe that the bug you reported is fixed in the latest version of
umockdev, 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.
Martin Pitt  (supplier of updated umockdev 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: Sun, 24 Mar 2024 11:54:21 +0100
Source: umockdev
Architecture: source
Version: 0.18.1-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt 
Changed-By: Martin Pitt 
Closes: 1067208
Changes:
 umockdev (0.18.1-1) unstable; urgency=medium
 .
   * New upstream release:
 - preload: Provide wrappers for functions specific to 64-bit time_t 
(thanks Steve Langasek)
 - preload: Fix building with _FILE_OFFSET_BITS (thanks Zixing Liu and 
Steve Langasek)
 - tests: Skip usbfs_ioctl_pcap on sparc64 (fixes FTBFS)
 - Closes: #1067208
Checksums-Sha1:
 422f2ff27ba7963bd1fabc88cbe367aafc248e87 2492 umockdev_0.18.1-1.dsc
 b0daf8365a583c5bdc4df76cce2f408981743808 493816 umockdev_0.18.1.orig.tar.xz
 eb82db13ad1abcb5e4291e42c05b7bdef143847b 8728 umockdev_0.18.1-1.debian.tar.xz
 7b8fcb523ac35b758bafd0a874a21227018d7889 9180 
umockdev_0.18.1-1_source.buildinfo
Checksums-Sha256:
 43d2faa628fa6198fe93fd5004209193deca4ea5c0ba2b2e2b7f154322410204 2492 
umockdev_0.18.1-1.dsc
 651b6869033bb1488136ed73c58e9245f5b01856261e1cea041030b83fb1ed7c 493816 
umockdev_0.18.1.orig.tar.xz
 1bc1aa1ecc1966b2c01244dc2b4ece3d4b054c92e93cea967b0c6f4c7ce53beb 8728 
umockdev_0.18.1-1.debian.tar.xz
 c02fb8927c715d8d36c7dc309f2850928537eb3e9e2abcd78fd6651538de73ff 9180 
umockdev_0.18.1-1_source.buildinfo
Files:
 82b07bb5b02ebbcfec13f33e1afcb395 2492 devel optional umockdev_0.18.1-1.dsc
 74342306a6d25e266dfa2a7b7695c2e1 493816 devel optional 
umockdev_0.18.1.orig.tar.xz
 

Bug#1066433: marked as done (uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type)

[Debian Bug Tracking System]

Your message dated Sun, 24 Mar 2024 10:51:33 +
with message-id 
and subject line Bug#1066433: fixed in uim 1:1.8.8-9.3
has caused the Debian Bug report #1066433,
regarding uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression 
with array type
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.)


-- 
1066433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uim
Version: 1:1.8.8-9.2
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):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../uim -I../replace -I../uim  -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 -O1 -pedantic -pipe -Wall 
> -Wchar-subscripts -Wmissing-declarations -Wredundant-decls 
> -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align 
> -Wsign-compare -Wno-long-long -Wno-overlength-strings -DNDEBUG -c -o 
> getpeereid.lo getpeereid.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../uim -I../replace -I../uim 
> -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 -O1 
> -pedantic -pipe -Wall -Wchar-subscripts -Wmissing-declarations 
> -Wredundant-decls -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
> -Wcast-align -Wsign-compare -Wno-long-long -Wno-overlength-strings -DNDEBUG 
> -c daemon.c  -fPIC -DPIC -o .libs/daemon.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../uim -I../replace -I../uim 
> -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 -O1 
> -pedantic -pipe -Wall -Wchar-subscripts -Wmissing-declarations 
> -Wredundant-decls -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
> -Wcast-align -Wsign-compare -Wno-long-long -Wno-overlength-strings -DNDEBUG 
> -c bsd-poll.c  -fPIC -DPIC -o .libs/bsd-poll.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../uim -I../replace -I../uim 
> -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 -O1 
> -pedantic -pipe -Wall -Wchar-subscripts -Wmissing-declarations 
> -Wredundant-decls -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
> -Wcast-align -Wsign-compare -Wno-long-long -Wno-overlength-strings -DNDEBUG 
> -c bsd-misc.c  -fPIC -DPIC -o .libs/bsd-misc.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../uim -I../replace -I../uim 
> -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 -O1 
> -pedantic -pipe -Wall -Wchar-subscripts -Wmissing-declarations 
> -Wredundant-decls -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
> -Wcast-align -Wsign-compare -Wno-long-long -Wno-overlength-strings -DNDEBUG 
> -c bsd-snprintf.c  -fPIC -DPIC -o .libs/bsd-snprintf.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../uim -I../replace -I../uim 
> -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 -O1 
> -pedantic -pipe -Wall -Wchar-subscripts -Wmissing-declarations 
> -Wredundant-decls -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
> -Wcast-align -Wsign-compare -Wno-long-long -Wno-overlength-strings -DNDEBUG 
> -c fake-rfc2553.c  -fPIC -DPIC -o .libs/fake-rfc2553.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../uim -I../replace -I../uim 
> -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 -O1 
> -pedantic -pipe -Wall -Wchar-subscripts -Wmissing-declarations 
> -Wredundant-decls -Wmissing-prototypes -Wnested-externs -Wpointer-arith 
> -Wcast-align -Wsign-compare -Wno-long-long 

Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 01:03:20PM +0100, Lucas Nussbaum wrote:
> > ./config.h:2540:11: fatal error: trio.h: No such file or directory
> >  2540 | # include "trio.h"
> >   |   ^~~~
(this suggests that using trio is not actually supported but that's
irrelevant)
This is caused by the stdio detection failing and should be fixed by
adding #include  to the test case code in m4/needtrio.m4 but this
package doesn't run autoreconf so fixing d/rules to at least do that is
also needed.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/martinpitt/umockdev/issues/216
Bug #1067208 [src:umockdev] umockdev: #error "_TIME_BITS=64 is allowed only 
with _FILE_OFFSET_BITS=64"
Set Bug forwarded-to-address to 
'https://github.com/martinpitt/umockdev/issues/216'.
> tag -1 upstream pending
Bug #1067208 [src:umockdev] umockdev: #error "_TIME_BITS=64 is allowed only 
with _FILE_OFFSET_BITS=64"
Added tag(s) upstream and pending.

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

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

[Martin Pitt]

Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/216
Control: tag -1 upstream pending

Hello all,

Thorsten Glaser [2024-03-20  3:05 +]:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
> only with _FILE_OFFSET_BITS=64"
>26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
>   | ^
>
>
> I admit I don’t exactly see what’s going on here. Does it
> maybe #unset _FILE_OFFSET_BITS or something?

Yes, it currently does on main/latest release, see 
https://github.com/martinpitt/umockdev/issues/216

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

Correct.

As it happens, the latest Ubuntu package got fixes for both of these issues
recently, thanks to Steve Langasek and Zixing Liu! I'll integrate them upstream
and then make a new release.

Martin

Processed: bug 1067545 is forwarded to https://github.com/klatexformula/klatexformula/pull/75, tagging 1067545

[Debian Bug Tracking System]

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

> forwarded 1067545 https://github.com/klatexformula/klatexformula/pull/75
Bug #1067545 [src:klatexformula] FTBFS on 32-bit time64 arches: cannot convert 
‘long int*’ to ‘time_t*’ {aka ‘long long int*’}
Set Bug forwarded-to-address to 
'https://github.com/klatexformula/klatexformula/pull/75'.
> tags 1067545 + upstream fixed-upstream
Bug #1067545 [src:klatexformula] FTBFS on 32-bit time64 arches: cannot convert 
‘long int*’ to ‘time_t*’ {aka ‘long long int*’}
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#1067596: FTBFS: error: ‘const struct input_event’ has no member named ‘time’

[Andrey Rakhmatullin]

Source: xf86-input-multitouch
Version: 1.0~rc3-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=xf86-input-
multitouch=armel=1.0%7Erc3-2%2Bb2=1711272573=0

src/hwstate.c: In function ‘finish_packet’:
src/hwstate.c:43:24: error: ‘const struct input_event’ has no member named
‘time’
   43 | s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
  |^~
src/hwstate.c:43:49: error: ‘const struct input_event’ has no member named
‘time’
   43 | s->evtime = syn->time.tv_usec / ms + syn->time.tv_sec * ms;
  | ^~



It also has multiple "warning: implicit declaration of function" which are not
errors because the package ignores compiler flags from dh_auto_build (which is
also a bug, not sure if RC or not).


-- 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#1066433: uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type

[Andreas Metzler]

Control: tags -1 patch

On 2024-03-13 Lucas Nussbaum  wrote:
> Source: uim
> Version: 1:1.8.8-9.2
> 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):
[...]
> > bsd-snprintf.c: In function ‘dopr’:
> > bsd-snprintf.c:104:38: error: assignment to expression with array type
> >   104 | #   define VA_COPY(dest, src) (dest) = (src)
> >   |  ^
> > bsd-snprintf.c:186:9: note: in expansion of macro ‘VA_COPY’
> >   186 | VA_COPY(args, args_in);
> >   | ^~~
[...]

I intend to fix this by NMU.

cu Andreas
Avoid an undeclared exit function call in the snprintf configure check.
This improves compatibility with strict(er) C99 compilers, which may
not support implicit function declarations because they were removed
from the C language in 1999.

Submitted upstream: 

diff --git a/configure.ac b/configure.ac
index 042d68927b76435c..84fcd38c9d3245db 100644
--- a/configure.ac
+++ b/configure.ac
@@ -595,7 +595,7 @@ if test "x$ac_cv_func_snprintf" = xyes; then
 	AC_RUN_IFELSE(
 		[AC_LANG_SOURCE([[
 #include 
-int main(void){char b[5];snprintf(b,5,"123456789");exit(b[4]!='\0');}
+int main(void){char b[5];snprintf(b,5,"123456789");return b[4]!='\0';}
 		]])],
 		[AC_MSG_RESULT(yes)],
 		[

Processed: Re: Bug#1066433: uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to expression with array type

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066433 [src:uim] uim: FTBFS: bsd-snprintf.c:104:38: error: assignment to 
expression with array type
Added tag(s) patch.

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

Processed: tagging 1067567, tagging 1067545, tagging 1067560, tagging 1067428, tagging 1067546, tagging 1052841 ...

[Debian Bug Tracking System]

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

> tags 1067567 + sid trixie
Bug #1067567 [dhcp-probe] dhcp-probe: [time_t] Remove hardcoded dependencies on 
libpcap0.8, libnet, shlibs takes care of them
Added tag(s) sid and trixie.
> tags 1067545 + sid trixie
Bug #1067545 [src:klatexformula] FTBFS on 32-bit time64 arches: cannot convert 
‘long int*’ to ‘time_t*’ {aka ‘long long int*’}
Added tag(s) trixie and sid.
> tags 1067560 + sid trixie
Bug #1067560 [src:deepin-log-viewer] FTBFS on 32-bit time64 architectures: 
cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}
Added tag(s) sid and trixie.
> tags 1067428 + sid trixie
Bug #1067428 {Done: Gianfranco Costamagna } 
[contextfree] contextfree: diff for NMU version 3.4+dfsg-1.1
Added tag(s) sid and trixie.
> tags 1067546 + sid trixie
Bug #1067546 [src:kluppe] FTBFS: ‘struct input_event’ has no member named ‘time’
Added tag(s) sid and trixie.
> tags 1052841 - sid trixie
Bug #1052841 {Done: Patrick Franz } [src:kcontacts] 
kcontacts: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test 
ARGS\+=--verbose ARGS\+=-j1 returned exit code 2
Ignoring request to alter tags of bug #1052841 to the same tags previously set
> notfound 1067223 1.10-2build4
Bug #1067223 [src:libflorist] libflorist ftbfs on time_t64 architectures
The source 'libflorist' and version '1.10-2build4' do not appear to match any 
binary packages
No longer marked as found in versions libflorist/1.10-2build4.
> found 1067223 1.10-2
Bug #1067223 [src:libflorist] libflorist ftbfs on time_t64 architectures
The source 'libflorist' and version '1.10-2' do not appear to match any binary 
packages
Marked as found in versions libflorist/1.10-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052841
1067223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067223
1067428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067428
1067545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067545
1067546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067546
1067560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067560
1067567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Andreas Beckmann]

On Thu, 21 Mar 2024 18:39:00 +0100 Jochen Sprickerhof 
 wrote:

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

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


Does the package work with /usr/share/doc excluded from installation?
https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation.
"Packages must not require the existence of any files in /usr/share/doc/ 
in order to function. [6] Any files that are used or read by programs 
but are also useful as stand alone documentation should be installed 
elsewhere, such as under /usr/share/package/, and then included via 
symbolic links in /usr/share/doc/package."



Andreas

Processed: ITP: golang-github-skeema-knownhosts -- Go SSH known_hosts wrapper with host key lookup

[Debian Bug Tracking System]

Processing control commands:

> block 1060701 by -1
Bug #1060701 [src:golang-github-go-git-go-git] golang-github-go-git-go-git: 
CVE-2023-49568 CVE-2023-49569
1060701 was blocked by: 1067593
1060701 was not blocking any bugs.
Added blocking bug(s) of 1060701: 1067594

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

Processed: ITP: golang-github-pjbgf-sha1cd -- SHA1 implementation with collision detection

[Debian Bug Tracking System]

Processing control commands:

> block 1060701 by -1
Bug #1060701 [src:golang-github-go-git-go-git] golang-github-go-git-go-git: 
CVE-2023-49568 CVE-2023-49569
1060701 was not blocked by any bugs.
1060701 was not blocking any bugs.
Added blocking bug(s) of 1060701: 1067593

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

Bug#1066500: vorbisgain: diff for NMU version 0.37-2.1

[Håvard F . Aasen]

Control: tags 1066500 + patch
Control: tags 1066500 + pending


Dear maintainer,

I've prepared an NMU for vorbisgain (versioned as 0.37-2.1). The diff
is attached to this message.

I require a sponsor to have it uploaded.

Regards.
-- 
Håvarddiff -Nru vorbisgain-0.37/debian/changelog vorbisgain-0.37/debian/changelog
--- vorbisgain-0.37/debian/changelog	2012-07-01 14:48:01.0 +0200
+++ vorbisgain-0.37/debian/changelog	2024-03-24 09:00:42.0 +0100
@@ -1,3 +1,10 @@
+vorbisgain (0.37-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix missing header declaration. (Closes: #1066500)
+
+ -- Håvard F. Aasen   Sun, 24 Mar 2024 09:00:42 +0100
+
 vorbisgain (0.37-2) unstable; urgency=low
 
   * Updated maintainer's info
diff -Nru vorbisgain-0.37/debian/patches/0011-missing-header-decl.patch vorbisgain-0.37/debian/patches/0011-missing-header-decl.patch
--- vorbisgain-0.37/debian/patches/0011-missing-header-decl.patch	1970-01-01 01:00:00.0 +0100
+++ vorbisgain-0.37/debian/patches/0011-missing-header-decl.patch	2024-03-24 09:00:42.0 +0100
@@ -0,0 +1,16 @@
+Description: Add missing header declaration for isatty()
+Author: Håvard F. Aasen 
+Bug-Debian: https://bugs.debian.org/1066500
+Forwarded: no
+
+---
+--- a/misc.c
 b/misc.c
+@@ -14,6 +14,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include "i18n.h"
+ #include "misc.h"
diff -Nru vorbisgain-0.37/debian/patches/series vorbisgain-0.37/debian/patches/series
--- vorbisgain-0.37/debian/patches/series	2012-07-01 14:48:01.0 +0200
+++ vorbisgain-0.37/debian/patches/series	2024-03-24 09:00:42.0 +0100
@@ -8,3 +8,4 @@
 0008-manpage_recursion_mistake.patch
 0009-hardening.patch
 0010-fclose.patch
+0011-missing-header-decl.patch

Processed: vorbisgain: diff for NMU version 0.37-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1066500 + patch
Bug #1066500 [src:vorbisgain] vorbisgain: FTBFS: misc.c:268:9: error: implicit 
declaration of function ‘isatty’ [-Werror=implicit-function-declaration]
Added tag(s) patch.
> tags 1066500 + pending
Bug #1066500 [src:vorbisgain] vorbisgain: FTBFS: misc.c:268:9: error: implicit 
declaration of function ‘isatty’ [-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Processed: tagging 1056893

[Debian Bug Tracking System]

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

> tags 1056893 + ftbfs
Bug #1056893 [src:uvloop] uvloop: ftbfs with cython 3.0.x
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1064423: bug 1064423: src:gnome-keyring: FTBFS on s390x

[Paul Gevers]

Hi all,

[s390x porters in CC, maybe they can help?]

On Wed, 21 Feb 2024 22:22:54 +0100 Paul Gevers  wrote:

Source: gnome-keyring


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:gnome-keyring has been trying to migrate 
for 32 days [2]. Hence, I am filing this bug. The version in unstable 
(and version 42.2) failed to build on s390x.


By now three uploads in a row of gnome-keyring FTBFS on s390x on Debian
buildds (but at least the last ones built on Ubuntu's infrastructure).
This is a key package [3], so autoremoval doesn't happen and most likely
(I haven't checked) removal of the binary on s390x isn't going to be
trivial (otherwise it wouldn't be key). Hence, the issue needs to be
solved for gnome-keyring to migrate. Is there any progress on this?

Paul


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

[3] https://release.debian.org/key-packages.html


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Bug#1066261 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066261 [src:lintian] lintian: FTBFS: hello.c:9:5: error: implicit 
declaration of function 'strcpy' [-Werror=implicit-function-declaration]
Bug #1065431 [src:lintian] lintian: autopkgtests fail due to implicit 
definition of memcpy
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1066261: marked as pending in lintian

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1066261 in lintian 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/lintian/lintian/-/commit/53dc310d4d5af6b0701d55577b30fb9a7e493bd1


t: Fix compilation failures with dpkg 1.22.6

Dpkg 1.22.6 enables -Werror=implicit-function-declaration by default.
This causes various compilation failures in the tests, mainly due to
missing includes.

The remaining failures are due to newer GCC versions defaulting to the
C11 standard, which doesn't expose the gets() function anymore.  For
these tests, explicitly compile with -std=c99 to re-expose the function.

Closes: #1066261
Signed-off-by: James McCoy 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066261