Processed: reassign 1073014 to ci.debian.org

[Debian Bug Tracking System]

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

> reassign 1073014 ci.debian.org
Bug #1073014 [src:dhcpcd] dhcpcd: flaky autopkgtest: Obtaining network 
configuration for veth1 via dhcp... timed out
Bug reassigned from package 'src:dhcpcd' to 'ci.debian.org'.
Warning: Unknown package 'ci.debian.org'
Warning: Unknown package 'ci.debian.org'
No longer marked as found in versions dhcpcd/1:10.0.8-1.
Warning: Unknown package 'ci.debian.org'
Warning: Unknown package 'ci.debian.org'
Ignoring request to alter fixed versions of bug #1073014 to the same values 
previously set
Warning: Unknown package 'ci.debian.org'
> thanks
Stopping processing here.

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

Bug#1072800: marked as done (nvidia-open-gpu-kernel-modules: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jun 2024 03:19:45 +
with message-id 
and subject line Bug#1072800: fixed in nvidia-open-gpu-kernel-modules 
535.183.01-1
has caused the Debian Bug report #1072800,
regarding nvidia-open-gpu-kernel-modules: CVE-2024-0090, CVE-2024-0091, 
CVE-2024-0092
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.)


-- 
1072800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2024-0090, 
CVE-2024-0092
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2024-0090, 
CVE-2024-0092
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2024-0090, 
CVE-2024-0092
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2024-0090, 
CVE-2024-0092
Control: tag -5 + wontfix
Control: close -5 450.248.02-4
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2024-0090, 
CVE-2024-0092
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2024-0090, 
CVE-2024-0092
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2024-0090, CVE-2024-0092
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: tag -8 + wontfix
Control: close -8 525.147.05-6
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2024-0090, 
CVE-2024-0091, CVE-2024-0092
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -9 535.43.02-1
Control: found -9 545.23.06-1
Control: found -9 550.40.07-1
Control: found -9 555.42.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1
Control: found -1 535.43.02-1
Control: found -1 545.23.06-1
Control: found -1 550.40.07-1
Control: found -1 555.42.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5551

CVE-2024-0090   NVIDIA GPU driver for Windows and Linux contains a
vulnerability where a user can cause an out-of-bounds write. A
successful exploit of this vulnerability might lead to code execution,
denial of service, escalation of privileges, information disclosure, and
data tampering.

CVE-2024-0091   NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where a user can cause an untrusted pointer dereference
by executing a driver API. A successful exploit of this vulnerability
might lead to denial of service, information disclosure, and data
tampering.

CVE-2024-0092   NVIDIA GPU Driver for Windows and Linux contains a
vulnerability where an improper check or improper handling of exception
conditions might lead to denial of service.

Linux Driver Branch CVE IDs Addressed
R555, R550  CVE-2024-0090, CVE-2024-0091, CVE-2024-0092
R535, R470  CVE-2024-0090, CVE-2024-0092

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R555All driver versions prior to 555.52.04  555.52.04
R550All driver versions prior to 550.90.07  550.90.07
R535All driver versions prior to 535.183.01 535.183.01
R470All driver versions prior to 470.256.02 470.256.02


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-open-gpu-kernel-modules
Source-Version: 535.183.01-1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-open-gpu-kernel-modules, 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.

Bug#1073335: marked as done (gettext: FTBFS: locating-rule.c:150:7: error: implicit declaration of function ‘free’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 22:34:33 +
with message-id 
and subject line Bug#1073335: fixed in gettext 0.21-15
has caused the Debian Bug report #1073335,
regarding gettext: FTBFS: locating-rule.c:150:7: error: implicit declaration of 
function ‘free’ [-Werror=implicit-function-declaration]
to be marked as done.

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

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


-- 
1073335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gettext
Version: 0.21-14
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 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 
> -DLOCALEDIR=\"/usr/share/locale\" -DBISON_LOCALEDIR=\"/usr/share/locale\" 
> -DLOCALE_ALIAS_PATH=\"/usr/share/locale\" -DUSEJAVA=0 
> -DGETTEXTJAR=\"/usr/share/gettext/gettext.jar\" 
> -DLIBDIR=\"/usr/lib/x86_64-linux-gnu\" 
> -DGETTEXTDATADIR=\"/usr/share/gettext\" 
> -DPROJECTSDIR=\"/usr/share/gettext/projects\" -DEXEEXT=\"\" -DHAVE_CONFIG_H 
> -I. -I..  -I. -I. -I.. -I.. -I../libgrep -I../gnulib-lib -I../gnulib-lib 
> -I../intl -I../../gettext-runtime/intl -I../libgettextpo -I../libgettextpo 
> -I///usr/include/libxml2  -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 
> libgettextsrc_la-locating-rule.lo `test -f 'locating-rule.c' || echo 
> './'`locating-rule.c
> libtool: compile:  gcc -DLOCALEDIR=\"/usr/share/locale\" 
> -DBISON_LOCALEDIR=\"/usr/share/locale\" 
> -DLOCALE_ALIAS_PATH=\"/usr/share/locale\" -DUSEJAVA=0 
> -DGETTEXTJAR=\"/usr/share/gettext/gettext.jar\" 
> -DLIBDIR=\"/usr/lib/x86_64-linux-gnu\" 
> -DGETTEXTDATADIR=\"/usr/share/gettext\" 
> -DPROJECTSDIR=\"/usr/share/gettext/projects\" -DEXEEXT=\"\" -DHAVE_CONFIG_H 
> -I. -I.. -I. -I. -I.. -I.. -I../libgrep -I../gnulib-lib -I../gnulib-lib 
> -I../intl -I../../gettext-runtime/intl -I../libgettextpo -I../libgettextpo 
> -I///usr/include/libxml2 -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 locating-rule.c  -fPIC -DPIC -o 
> .libs/libgettextsrc_la-locating-rule.o
> locating-rule.c: In function ‘locating_rule_match’:
> locating-rule.c:150:7: error: implicit declaration of function ‘free’ 
> [-Werror=implicit-function-declaration]
>   150 |   free (reduced);
>   |   ^~~~
> locating-rule.c:50:1: note: include ‘’ or provide a declaration of 
> ‘free’
>49 | #include "xalloc.h"
>   +++ |+#include 
>50 | 
> locating-rule.c:150:7: warning: incompatible implicit declaration of built-in 
> function ‘free’ [-Wbuiltin-declaration-mismatch]
>   150 |   free (reduced);
>   |   ^~~~
> locating-rule.c:150:7: note: include ‘’ or provide a declaration of 
> ‘free’
> locating-rule.c:169:27: warning: initialization discards ‘const’ qualifier 
> from pointer target type [-Wdiscarded-qualifiers]
>   169 |   xmlError *err = xmlGetLastError ();
>   |   ^~~
> locating-rule.c: In function ‘locating_rule_list_locate’:
> locating-rule.c:217:15: warning: incompatible implicit declaration of 
> built-in function ‘free’ [-Wbuiltin-declaration-mismatch]
>   217 |   free (new_filename);
>   |   ^~~~
> locating-rule.c:217:15: note: include ‘’ or provide a declaration 
> of ‘free’
> locating-rule.c: In function ‘document_locating_rule_destroy’:
> locating-rule.c:244:3: warning: incompatible implicit declaration of built-in 
> function ‘free’ [-Wbuiltin-declaration-mismatch]
>   244 |   free (rule->ns);
>   |   ^~~~
> locating-rule.c:244:3: note: include ‘’ or provide a declaration of 
> ‘free’
> locating-rule.c: In function ‘locating_rule_destroy’:
> locating-rule.c:288:3: warning: incompatible implicit declaration of built-in 
> function ‘free’ [-Wbuiltin-declaration-mismatch]
>   288 |   free (rule->doc_rules.items);
>   |   ^~~~
> locating-rule.c:288:3: note: include ‘’ or provide a declaration of 
> ‘free’
> locating-rule.c: In function ‘locating_rule_list_add_from_directory’:
> locating-rule.c:399:15: warning: incompatible implicit declaration of 
> built-in function ‘free’ [-Wbuiltin-declaration-mismatch]
>   399 |   

Bug#1073290: marked as done (systemd: Please breaks against dracut-core << 102-2~)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 22:36:08 +
with message-id 
and subject line Bug#1073290: fixed in systemd 256.1-1
has caused the Debian Bug report #1073290,
regarding systemd: Please breaks against dracut-core << 102-2~
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.)


-- 
1073290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Severity: serious
Tags: patch
Justification: Breaks unrelated package
Control: affects -1 dracut-core

Dear Maintainer,

Following #1071182 could you add to systemd a breaks: dracut-core << 102-2~

Change is simple so I add patch tag, please remove if needed

Bastien



signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 256.1-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated systemd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jun 2024 23:19:16 +0100
Source: systemd
Architecture: source
Version: 256.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Luca Boccassi 
Closes: 1072562 1073290
Changes:
 systemd (256.1-1) unstable; urgency=medium
 .
   * Bump versioned breaks against dracut to 102-2 (Closes: #1073290)
   * autopkgtest: switch upstream suite to mkosi-based builds
   * Add conflict against sysv-rc, insserv and startpar in systemd-sysv.
 They are not needed, and having them installed causes problems.
 (Closes: #1072562)
   * New upstream version 256.1
   * Drop section from binary packages where it matches the source package
   * Override Lintian false positives about spare manpages
   * Deduplicate template packages descriptions
   * Add Lintian override for template package false positives
   * Rename EFI architecture variable to avoid dpkg clash. Fixes Lintian
 warning: debian-rules-sets-dpkg-architecture-variable
   * Upload to unstable.
Checksums-Sha1:
 c0140d0d38cc9e5b89ec298e8c7e9a63ff7098d0 8075 systemd_256.1-1.dsc
 4893a6a41e9a82a3b3c1bb772e6754ea921505e6 15643508 systemd_256.1.orig.tar.gz
 858328f031a2f25c013901325caa6d913224a18d 170588 systemd_256.1-1.debian.tar.xz
 c0a7518c04cd7444e1eb7f109a3220ed275d88e1 13079 systemd_256.1-1_source.buildinfo
Checksums-Sha256:
 1679e5333519781dcad344f23a32c87db8c8738a7f99969272d4451e8d15ae75 8075 
systemd_256.1-1.dsc
 9c9243209e5b1bf429fc213ade6111a95769531a3a741bdf01c8a5dbeeab9f8a 15643508 
systemd_256.1.orig.tar.gz
 317ac708ec32a7b1cab85676186454988f4d852d40296c4d5f6ac150bc3d13c7 170588 
systemd_256.1-1.debian.tar.xz
 c632373386b7ab869cb8ccf1b04d2b1b1e6fab3c6f6af27a430111fb417808e2 13079 
systemd_256.1-1_source.buildinfo
Files:
 8dff00eed223420510e5d0b78532821b 8075 admin optional systemd_256.1-1.dsc
 46c30853682f8017df979c3d26b9c9dc 15643508 admin optional 
systemd_256.1.orig.tar.gz
 a340ea4c18c10c27433a8c359a1065b9 170588 admin optional 
systemd_256.1-1.debian.tar.xz
 39f44e0f6b269a40033c277bf1664bac 13079 admin optional 
systemd_256.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmZyCGoRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB5lmA//QOVgZaC9wCRB1hADFRmxfCM5hN4B2lJq
naiQQqvaP3Te0Ryb6rVW5rDQb8+iDoAndva2InBGvgp7Y1ImIdGJJaqw35OF5+a6
Lx0idkj/c7w+x2HkBToBJsfDMJTRiPCy+t8TXNH2zrl2T3yBrWH5JfpRuqK10Qbc
OKl65Hgj3X+0MPhhByb83rYZi+agIp+myhPK+thtNNI6ZeuF8vS43lIGkpw60FJI
pDxnhiva0FKK1p3+AFRlZg8Rxp2/YJkftcZJgDjT2ugBV4z5bwSU1h/kw15dv5EG
VkcfmoXk87/d8mVsczMFWju+6qT0TwRfGk1Vnb5tcikgkEJcN4/A6Gfb4fqCq2nh
Djqhc3MgRhMtRr9t0k9tfUSHc21xF0tuS1m+kzMJe0SKVTmKMFWml1XeFNTDXc5w
cVJ52WYDzz9FjTGNg4QGUS7fwRHI3ckB6s4BrtOTUDAjbEHW5BikmZjV3Mq4ie+D
KUiEyfEbo1viGEUvD4L13R2B1nT6xSrkZTMD6e4n/vLk2/pBcLjtJcNSdShIp5rC
FfG6ufEe+njD+DipamyesR5AHnZDolZavL4JvRCfuwzDxiIyW1eMkSCBbwHX8Gd4
M3LdzwBqD0aB8Ietjd58Mt7oYDobLqrQY8rgfg2gZsjTcYBXPEo8Drv7He/x0UdF
zN2FJvQ2+MA=
=lI2X
-END PGP 

Bug#1039883: [PATCH] ext4: don't track ranges in fast_commit if inode has inlined data

[Ben Hutchings]

On Tue, 2024-06-18 at 15:43 +0100, Luis Henriques (SUSE) wrote:
> When fast-commit needs to track ranges, it has to handle inodes that have
> inlined data in a different way because ext4_fc_write_inode_data(), in the
> actual commit path, will attempt to map the required blocks for the range.
> However, inodes that have inlined data will have it's data stored in
> inode->i_block and, eventually, in the extended attribute space.
> 
> Unfortunately, because fast commit doesn't currently support extended
> attributes, the solution is to mark this commit as ineligible.
> 
> Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039883
> Signed-off-by: Luis Henriques (SUSE) 

Reported-by: Hervé Werner 
Tested-by: Ben Hutchings 

I think this should also have:

Fixes: 9725958bb75c ("ext4: fast commit may miss tracking unwritten range 
during ftruncate")

unless you think the problem is even older than that.

Ben.

> ---
>  fs/ext4/fast_commit.c | 6 ++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
> index 87c009e0c59a..d3a67bc06d10 100644
> --- a/fs/ext4/fast_commit.c
> +++ b/fs/ext4/fast_commit.c
> @@ -649,6 +649,12 @@ void ext4_fc_track_range(handle_t *handle, struct inode 
> *inode, ext4_lblk_t star
>   if (ext4_test_mount_flag(inode->i_sb, EXT4_MF_FC_INELIGIBLE))
>   return;
>  
> + if (ext4_has_inline_data(inode)) {
> + ext4_fc_mark_ineligible(inode->i_sb, EXT4_FC_REASON_XATTR,
> + handle);
> + return;
> + }
> +
>   args.start = start;
>   args.end = end;
>  

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.



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

Bug#1039883: [PATCH] ext4: don't track ranges in fast_commit if inode has inlined data

[Luis Henriques (SUSE)]

When fast-commit needs to track ranges, it has to handle inodes that have
inlined data in a different way because ext4_fc_write_inode_data(), in the
actual commit path, will attempt to map the required blocks for the range.
However, inodes that have inlined data will have it's data stored in
inode->i_block and, eventually, in the extended attribute space.

Unfortunately, because fast commit doesn't currently support extended
attributes, the solution is to mark this commit as ineligible.

Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039883
Signed-off-by: Luis Henriques (SUSE) 
---
 fs/ext4/fast_commit.c | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
index 87c009e0c59a..d3a67bc06d10 100644
--- a/fs/ext4/fast_commit.c
+++ b/fs/ext4/fast_commit.c
@@ -649,6 +649,12 @@ void ext4_fc_track_range(handle_t *handle, struct inode 
*inode, ext4_lblk_t star
if (ext4_test_mount_flag(inode->i_sb, EXT4_MF_FC_INELIGIBLE))
return;
 
+   if (ext4_has_inline_data(inode)) {
+   ext4_fc_mark_ineligible(inode->i_sb, EXT4_FC_REASON_XATTR,
+   handle);
+   return;
+   }
+
args.start = start;
args.end = end;
 

Bug#1073439: marked as done (calibre: FTBFS: AttributeError: module 'pyzstd.c._zstd' has no attribute '_ZSTD_c_targetCBlockSize')

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 22:19:15 +
with message-id 
and subject line Bug#1073439: fixed in python-pyzstd 0.16.0+ds-2
has caused the Debian Bug report #1073439,
regarding calibre: FTBFS: AttributeError: module 'pyzstd.c._zstd' has no 
attribute '_ZSTD_c_targetCBlockSize'
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.)


-- 
1073439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: calibre
Version: 7.12.0+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> env TZ=UTC CI=true python3.11 setup.py test --exclude-test-name=fts_pool 
> --exclude-test-name=workers --exclude-test-name=dbus 
> --exclude-test-name=ajax_book --exclude-test-name=workers 
> --exclude-test-name=qt --exclude-test-name=dom_load
> ::group::test
> 
> *
> * Running test
> *
> 
> test_basic_csv_output 
> (calibre.db.cli.tests.PrintCheckLibraryResultsTest.test_basic_csv_output)
> Test simple csv output ... ok [0.0 s]
> test_escaped_csv_output 
> (calibre.db.cli.tests.PrintCheckLibraryResultsTest.test_escaped_csv_output)
> Test more complex csv output ... ok [0.0 s]
> test_human_readable_output 
> (calibre.db.cli.tests.PrintCheckLibraryResultsTest.test_human_readable_output)
> Basic check of the human-readable output. ... ok [0.0 s]
> test_prints_nothing_if_no_errors 
> (calibre.db.cli.tests.PrintCheckLibraryResultsTest.test_prints_nothing_if_no_errors)
>  ... ok [0.0 s]
> test_import_of_all_python_modules 
> (calibre.utils.run_tests.TestImports.test_import_of_all_python_modules) ... 
> ok [3.9 s]
> test_copying_of_trees 
> (calibre.utils.copy_files_test.TestCopyFiles.test_copying_of_trees) ... ok 
> [0.0 s]
> test_renaming_of_files 
> (calibre.utils.copy_files_test.TestCopyFiles.test_renaming_of_files) ... ok 
> [0.0 s]
> test_live_cache (calibre.live.find_tests..LiveTest.test_live_cache) 
> ... ok [0.0 s]
> test_module_loading 
> (calibre.live.find_tests..LiveTest.test_module_loading) ... ok [0.0 s]
> test_add_soft_hyphens 
> (calibre.utils.hyphenation.test_hyphenation.TestHyphenation.test_add_soft_hyphens)
>  ... ok [0.4 s]
> test_hyphenate_html 
> (calibre.utils.hyphenation.test_hyphenation.TestHyphenation.test_hyphenate_html)
>  ... ok [0.1 s]
> test_locale_to_hyphen_dictionary 
> (calibre.utils.hyphenation.test_hyphenation.TestHyphenation.test_locale_to_hyphen_dictionary)
>  ... ok [0.1 s]
> test_viewer_cache 
> (calibre.gui2.viewer.convert_book.find_tests..TestViewerCache.test_viewer_cache)
>  ... ok [0.0 s]
> test_palmdoc_compression 
> (calibre.ebooks.compression.palmdoc.find_tests..Test.test_palmdoc_compression)
>  ... ok [0.0 s]
> test_comments_to_html 
> (calibre.library.comments.find_tests..Test.test_comments_to_html) ... 
> ok [0.0 s]
> test_shm (calibre.utils.shm.find_tests..TestSHM.test_shm) ... ok [0.0 
> s]
> test_html2text_behavior 
> (calibre.utils.html2text.find_tests..TestH2T.test_html2text_behavior) 
> ... ok [0.0 s]
> test_sqp_optimized 
> (calibre.utils.search_query_parser_test.TestSQP.test_sqp_optimized) ... ok 
> [0.0 s]
> test_sqp_tokenizer 
> (calibre.utils.search_query_parser_test.TestSQP.test_sqp_tokenizer) ... ok 
> [0.0 s]
> test_sqp_unoptimized 
> (calibre.utils.search_query_parser_test.TestSQP.test_sqp_unoptimized) ... ok 
> [0.0 s]
> test_exclusive_file_other_process_clean 
> (calibre.utils.test_lock.IPCLockTest.test_exclusive_file_other_process_clean) 
> ... ok [0.2 s]
> test_exclusive_file_other_process_kill 
> (calibre.utils.test_lock.IPCLockTest.test_exclusive_file_other_process_kill) 
> ... ok [0.2 s]
> test_exclusive_file_same_process 
> (calibre.utils.test_lock.IPCLockTest.test_exclusive_file_same_process) ... ok 
> [0.1 s]
> test_single_instance 
> (calibre.utils.test_lock.IPCLockTest.test_single_instance) ... ok [1.3 s]
> test_tdir_in_cache_dir 
> (calibre.utils.test_lock.IPCLockTest.test_tdir_in_cache_dir) ... ok [0.2 s]
> test_shared_file 
> (calibre.utils.shared_file.find_tests..SharedFileTest.test_shared_file)
>  ... ok [0.0 s]
> test_author_mapper 
> (calibre.ebooks.metadata.author_mapper.find_tests..TestAuthorMapper.test_author_mapper)
>  ... ok [0.0 s]
> test_tag_mapper 
> (calibre.ebooks.metadata.tag_mapper.find_tests..TestTagMapper.test_tag_mapper)
>  ... ok [0.0 s]
> test_brackets 
> (calibre.ebooks.metadata.test_author_sort.TestRemoveBracketedText.test_brackets)
>  ... 

Bug#1073424: marked as done (py7zr: 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 Tue, 18 Jun 2024 22:19:15 +
with message-id 
and subject line Bug#1073424: fixed in python-pyzstd 0.16.0+ds-2
has caused the Debian Bug report #1073424,
regarding py7zr: 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.)


-- 
1073424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py7zr
Version: 0.21.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:311: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_py7zr 
>  
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/py7zr
> copying py7zr/__init__.py -> build/lib/py7zr
> copying py7zr/version.py -> build/lib/py7zr
> copying py7zr/exceptions.py -> build/lib/py7zr
> copying py7zr/properties.py -> build/lib/py7zr
> copying py7zr/win32compat.py -> build/lib/py7zr
> copying py7zr/__main__.py -> build/lib/py7zr
> copying py7zr/compressor.py -> build/lib/py7zr
> copying py7zr/callbacks.py -> build/lib/py7zr
> copying py7zr/helpers.py -> build/lib/py7zr
> copying py7zr/cli.py -> build/lib/py7zr
> copying py7zr/py7zr.py -> build/lib/py7zr
> copying py7zr/archiveinfo.py -> build/lib/py7zr
> running egg_info
> creating py7zr.egg-info
> writing py7zr.egg-info/PKG-INFO
> writing dependency_links to py7zr.egg-info/dependency_links.txt
> writing entry points to py7zr.egg-info/entry_points.txt
> writing requirements to py7zr.egg-info/requires.txt
> writing top-level names to py7zr.egg-info/top_level.txt
> writing manifest file 'py7zr.egg-info/SOURCES.txt'
> WARNING setuptools_scm._file_finders.git git archive detected - fallback to 
> listing all files
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.bin' under directory 'tests/data'
> adding license file 'LICENSE'
> writing manifest file 'py7zr.egg-info/SOURCES.txt'
> copying py7zr/py.typed -> build/lib/py7zr
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/__init__.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/version.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/exceptions.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/properties.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/win32compat.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/__main__.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/compressor.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/py.typed -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/callbacks.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/helpers.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/cli.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/py7zr.py -> build/bdist.linux-x86_64/wheel/py7zr
> copying build/lib/py7zr/archiveinfo.py -> build/bdist.linux-x86_64/wheel/py7zr
> running install_egg_info
> Copying py7zr.egg-info to 
> build/bdist.linux-x86_64/wheel/py7zr-0.21.0+dfsg.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/py7zr-0.21.0+dfsg.dist-info/WHEEL
> creating 
> '/<>/.pybuild/cpython3_3.12_py7zr/.tmp-_vilsukb/py7zr-0.21.0+dfsg-py3-none-any.whl'
>  and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'py7zr/__init__.py'
> adding 'py7zr/__main__.py'
> adding 'py7zr/archiveinfo.py'
> adding 'py7zr/callbacks.py'
> adding 'py7zr/cli.py'
> adding 'py7zr/compressor.py'
> adding 'py7zr/exceptions.py'
> adding 'py7zr/helpers.py'
> adding 'py7zr/properties.py'
> adding 'py7zr/py.typed'
> adding 'py7zr/py7zr.py'
> adding 

Bug#1072828: Work-around is ineffective on !amd64

[Preuße]

On 18.06.2024 23:01, Adrien Nader wrote:

Hi Adrien,


I've straced the build and the file seems generated and I see some
interesting things. I've heavily edited the output because the original
is already 11M.

The file is created and written to but it's in
"/build/therion-oW9QKw/therion-6.2.1/build/thbook" rather than
"/tmp/mt646779.tmp" where mktexpk expects it to be.


I rather compared the logs from a working [1] and a not working build
[2] The working build says:

kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600
logo10
mkdir: cannot create directory ‘././sbuild-nonexistent’: Permission denied
mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600;
nonstopmode; input logo10
This is METAFONT, Version 2.71828182 (TeX Live 2023/Debian) (preloaded
base=mf)

(/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo10.mf
(/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo.mf
[77] [69] [84] [65] [70] [80] [83] [79] [78]) )
Font metrics written on logo10.tfm.
Output written on logo10.600gf (9 characters, 1748 bytes).
Transcript written on logo10.log.
mktexpk: /tmp/texfonts/pk/ljfour/public/knuth-lib/logo10.600pk:
successfully generated.
 )
(see the transcript file for additional information)


...so all generated files go to /tmp.

kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600
logo10
mktexpk: Running mf-nowin -progname=mf \mode:=ljfour;
mag:=1+0/600;nonstopmode; input logo10
This is METAFONT, Version 2.71828182 (TeX Live
2025/dev/Debian)(preloaded base=mf)

(/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo10.mf
(/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo.mf
[77] [69] [84] [65] [70] [80] [83] [79] [78]) )
Font metrics written on /<>/build/thbook/logo10.tfm.
Output written on /<>/build/thbook/logo10.600gf (9
characters, 1748 bytes).
Transcript written on /<>/build/thbook/logo1
0.log.

The statement --output-dir= (which is handed over to the pdftex command
by the CMakeLists.txt) is regarded and the generated files are put anywhere.


Note that while running the commands directly myself, it seems I managed
to generate the file in an expected location and I was getting an error
about logo10.720gf rather than .600gf.


Well, this is probably due to no submitting the correct parameters to
mktexpk. In my test package the command is

Running mktexpk --mfmode / --bdpi 600 --mag 1+120/600 --dpi 720 logo10

in the end logo10.720pk is generated

hille@rasppi2:~/tmp-1.0 $ pdffonts thbook.pdf
name type  encoding
emb sub uni object ID
 - 
--- --- --- -
[none]   Type 3Custom
yes no  no   4  0
SDXKYB+CMR10 Type 1Builtin
yes yes no   5  0

...and probably used. This is only a simple test file having the Logo10
as only Type3 font.


Several environment variables refer to the first directory: KPSE_DOT,
TEXINPUTS, OLDPWD, TEXMF_OUTPUT_DIRECTORY.
For TEXMF_OUTPUT_DIRECTORY, I've found the following: 
https://tug.org/pipermail/tex-live-commits/2024-February/028329.html


The commit mostly contains version updates, it is probably not relevant,
but the NEWS message is interesting. I'm wondering at all, why the
therion package cares about the output path of the pdftex engine.


I'll stop there as now I'm definitely out of time for today.


I'll stop here too, maybe simply removing the --output-dir statement
from the CMakeLists.txt solves the issue. I'll test ASAP. If yes, we
don't look at a general issue, which needs to be solved on TL side.

Hilmar

[1]
https://buildd.debian.org/status/fetch.php?pkg=therion=all=6.2.1-1=1710963335=1
[2]
https://buildd.debian.org/status/fetch.php?pkg=therion=amd64=6.2.1-1%2Bb1=1717847632=1
--
sigfault

Bug#1073785: marked as done (debootstrap-udeb: removal of trixie --> sid link causes fatal error in D-I)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 21:04:19 +
with message-id 
and subject line Bug#1073785: fixed in debootstrap 1.0.136
has caused the Debian Bug report #1073785,
regarding debootstrap-udeb: removal of trixie --> sid link causes fatal error 
in D-I
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.)


-- 
1073785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap-udeb
Version: 1.0.135
Severity: serious
User: debian...@lists.debian.org
Usertags: openqa

While testing daily netinst debian-installer images with openQA, we see that
debootstrap fails:

  https://openqa.debian.net/tests/272866#step/install_base/1

  "The debootstrap program exited with an error (return value 1)"

looking in the syslog, one finds:

  debootstrap: E: NOSCRIPT
  debootsrtap: EA: /usr/share/debootstrap/scripts/trixie
  debootstrap: EF: No such script: %s

If I reinstate the trixie --> sid symlink, the installation can then proceed.

I presume that when removing the "redundant" links in commit 2d3eae91, there was
an intent that the scripting should default to "sid" when the required script is
found to be missing, but this seems not to have been done correctly.

It looks to me as if 73e1b5f9 simply fails to deal with the case where
distro-info is unavailable (debian-installer does not include it).

Cheers, Phil.
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.136
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated debootstrap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jun 2024 21:36:25 +0100
Source: debootstrap
Architecture: source
Version: 1.0.136
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Luca Boccassi 
Closes: 1073785
Changes:
 debootstrap (1.0.136) unstable; urgency=medium
 .
   [ Philip Hands ]
   * reinstate Debian codename symlinks (closes: #1073785)
   * drop unneeded addition of "test extras"
   * switch to using branch2repo for salsa-ci
   * avoid setting DEF_MIRROR to https://https://...
Checksums-Sha1:
 f83f8d4d187b4bad3d1c457fd112a7f94b72f77b 2053 debootstrap_1.0.136.dsc
 06a12533a8065be94387fa4f9578c4be002869f4 93499 debootstrap_1.0.136.tar.gz
 03fa202d0888b7dc31925ce9029a87b6fe355339 6589 
debootstrap_1.0.136_source.buildinfo
Checksums-Sha256:
 9f561c4a3f6e891737da7dd7b19a48979298028b6d0cffd03a0dd5f346186549 2053 
debootstrap_1.0.136.dsc
 a5c2067e6480f74df5079016629d3fd35497a2c634c385eb1e1ddf718a9f7498 93499 
debootstrap_1.0.136.tar.gz
 964584ac07b864700049800b3037742a02fab4e8c8e0fb3ce9e9db27d84c2263 6589 
debootstrap_1.0.136_source.buildinfo
Files:
 6c052fb398a6dc7c6fd9b778dce406bd 2053 admin optional debootstrap_1.0.136.dsc
 566b5833560f4098894d622b98b6cdb3 93499 admin optional 
debootstrap_1.0.136.tar.gz
 9969ae1a227ed71d509fa0c4a09035e4 6589 admin optional 
debootstrap_1.0.136_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmZx8AIRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB7e1g//Uu0bt1ZRIwrFV93nhgsqTtjoeH12uWQp
CNxULE2k3eN+TmnuKga+4u4W2y1qG4a19y4E9OljErfGiSz6HogchWyCS8U0dlHW
pZBZ8GtTT5tbAijzavj+BKk+kj9du44eGz7M0YI/yqLeYNiXn6WTTCcQO9x3TrhP
6d/kvkiWEvxJlnnPCHlFIjlK/Waog6X07Lt8cZjjnyDJ8Srg40ACmgR99AUknPZq
vR+tw7vnzmDS1elHCTA5Bv9PhSgQ1xMw5FRsHgLPeR3AZmJDtRUP85nh2S07Bw4o
cb+VajPZe4Rr8seL399msIuF0JtdU7xGFgBDpW4g8UKRe4Jw6EPT48ZWC80vQBPq
eTYMb3tDhlGz3MnC9PJDnAbc3VVmeHJh3PBeXzaTDyQ/dLj8n+2YlM2FpS+pnE8d
G5NUuefHgBwl4/ITk2txhjSLI0/Cjt1cLx/HfJnAaToCJY4I61m7zxJVDPmgt5NH
hbqlXbZeS0AaveS30otRxZCtQcIWSXLN3LKcebD7VgYsVLixzJoMDtYV87FBYxe4
7L9N0BBZBxnA8MaLBejCCx/95Xe1CoEq2apXPsaMsUvc/nlJzJCvbXabgGezfm/C
lHYQvFhZ4vkSZZ9rrGxnAFjV5ShKQXRTSEZ9yujJWRvB6nCRgTI767PIJ/qdgl6y
RyYSQ/hE8Rw=
=QswL
-END PGP SIGNATURE-



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

Bug#1072828: Work-around is ineffective on !amd64

[Adrien Nader]

Hi Hilmar,

You're absolutely right, thanks for having a look and sorry for the
noise. Trying to go too fast was a bad idea yet another time. :) 

I've straced the build and the file seems generated and I see some
interesting things. I've heavily edited the output because the original
is already 11M.

Command:

  strace --decode-fds=all --no-abbrev --decode-pids=all -tt -f -o log -s 4096 
ninja

>  execve("/usr/bin/mkdir", ["mkdir", "/tmp/mt646779.tmp"], 
> 0x5ff64b6b9298 /* 36 vars */) = 0
> [...]
>  execve("/usr/bin/mf-nowin", ["mf-nowin", "-progname=mf", 
> "\\mode:=ljfour;", "mag:=1+0/600;", "nonstopmode;", "input", "logo10"], 
> ["MAKETEX_MAG=1+0/600", 
> "KPSE_DOT=/build/therion-oW9QKw/therion-6.2.1/thbook", 
> "TEXINPUTS=/build/therion-oW9QKw/therion-6.2.1/build/thbook;.", "USER=root", 
> "MAKETEX_MODE=/", "KPATHSEA_DPI=600", "SHLVL=1", "KPATHSEA_FORMAT=pk", 
> "HOME=/sbuild-nonexistent", 
> "OLDPWD=/build/therion-oW9QKw/therion-6.2.1/thbook", 
> "MT_MKTEX_CNF=/etc/texmf/web2c/mktex.cnf", 
> "SCHROOT_CHROOT_NAME=oracular-amd64", "APT_CONFIG=/var/lib/sbuild/apt.conf", 
> "MT_MKTEXUPD=/usr/share/texlive/texmf-dist/web2c/mktexupd", 
> "FORCE_SOURCE_DATE=1", "SCHROOT_UID=1000", "LOGNAME=root", 
> "_=/usr/bin/strace", "SELFAUTOLOC=/usr/bin", "MT_VARTEXFONTS=/tmp/texfonts", 
> "SELFAUTODIR=/usr", "SELFAUTOPARENT=/", 
> "PATH=/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", 
> "MT_MKTEXNAM_OPT=/usr/share/texlive/texmf-dist/web2c/mktexnam.opt", 
> "SCHROOT_COMMAND=/bin/sh -c bash -i /dev/tty 2>/dev/tty", 
> "SCHROOT_SESSION_ID=oracular-amd64-d07c1014-b360-465a-91e8-3cc500813699", 
> "engine=pdftex", "SCHROOT_ALIAS_NAME=oracular-amd64", "LANG=en_US.UTF-8", 
> "MT_TEXMFMAIN=/usr/share/texlive/texmf-dist", 
> "MT_MKTEXDIR_OPT=/usr/share/texlive/texmf-dist/web2c/mktexdir.opt", 
> "SCHROOT_GROUP=adrien", "SCHROOT_USER=adrien", "SHELL=/bin/sh", 
> "TEXMF_OUTPUT_DIRECTORY=/build/therion-oW9QKw/therion-6.2.1/build/thbook", 
> "SELFAUTOGRANDPARENT=/", "KPATHSEA_NAME=logo10", "LC_ALL=C", 
> "PWD=/tmp/mt646779.tmp", 
> "MT_MKTEXNAM=/usr/share/texlive/texmf-dist/web2c/mktexnam", 
> "MAKETEX_BASE_DPI=600", 
> "MT_MKTEX_OPT=/usr/share/texlive/texmf-dist/web2c/mktex.opt", 
> "SCHROOT_GID=1000", "progname=mktexpk", 
> "MT_MKTEXDIR=/usr/share/texlive/texmf-dist/web2c/mktexdir"] 
> [...]
>  openat(AT_FDCWD, 
> "/build/therion-oW9QKw/therion-6.2.1/build/thbook/logo10.600gf", 
> O_WRONLY|O_CREAT|O_TRUNC, 0666) = 8
> [...]
>  
> write(8, 
> "\367\203  METAFONT output 2024.06. ..
>  
> close(8) = 0
> [...]
>  faccessat2(AT_FDCWD, "logo10.600gf", R_OK, 
> AT_EACCESS) = -1 ENOENT (No such file or directory)
> [...]
>  write(1, "mktexpk: `mf-nowin -progname=mf 
> \\mode:=ljfour; mag:=1+0/600; nonstopmode; input logo10' failed to make 
> logo10.600pk.\n", 117) = 117

The file is created and written to but it's in
"/build/therion-oW9QKw/therion-6.2.1/build/thbook" rather than
"/tmp/mt646779.tmp" where mktexpk expects it to be.

Note that while running the commands directly myself, it seems I managed
to generate the file in an expected location and I was getting an error
about logo10.720gf rather than .600gf.

Several environment variables refer to the first directory: KPSE_DOT,
TEXINPUTS, OLDPWD, TEXMF_OUTPUT_DIRECTORY.
For TEXMF_OUTPUT_DIRECTORY, I've found the following: 
https://tug.org/pipermail/tex-live-commits/2024-February/028329.html

> Modified: trunk/Build/source/texk/kpathsea/NEWS
> ===
> --- trunk/Build/source/texk/kpathsea/NEWS 2024-02-05 00:43:32 UTC (rev 
> 69710)
> +++ trunk/Build/source/texk/kpathsea/NEWS 2024-02-05 17:23:27 UTC (rev 
> 69711)
> @@ -2,11 +2,12 @@
>  This file records noteworthy changes.  (Public domain.)
> 
>  6.4.0 (for TeX Live 2024)
> -* Support an extended check for safe filenames, also allowing
> +* Support an extended check for safe filenames which also allows
>TEXMF[SYS]VAR, for Lua(La)TeX; new functions and corresponding
>kpsewhich options.
> -* Allow the new variable TEXMF_OUTPUT_DIRECTORY (as well as TEXMFOUTPUT),
> -  so that subprograms can have access to an --output-directory setting.
> +* Support a new variable TEXMF_OUTPUT_DIRECTORY (alongside the
> +  traditional TEXMFOUTPUT), so that subprograms can have access to an
> +  --output-directory setting in an engine invocation.

I'll stop there as now I'm definitely out of time for today.

-- 
Adrien

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Jonas Smedegaard]

Quoting Matthias Geiger (2024-06-18 15:18:17)
> On Mon, 10 Jun 2024 11:17:04 +0200 Jonas Smedegaard  wrote:
>  > Quoting Jeremy Bícha (2024-04-21 19:47:08)
>  > > Simple patch attached.
>  >
>  > I am not convinced that this issue should be ignored: Might be revealing
>  > the upstream bugs recently tracked upstream, which might in Debian be
>  > affected by relaxed dependencies e.g. on concurrent-queue.
>  >
> 
> Any news on this ? event-listener is currently blocking zbus 4.0 which 
> in turn prevents me from fixing the remaining GTK4 rust packages.

Not sure what you mean.

This bug affects only event-listener in experimental, which will never
transition anywhere. So the concern raised is only for the situation when
event-listener gets released to unstable - which requires all involved
packages to be in sync and buildable at all, and only then does it make
sense to me to check if this instability persists.

It seems these packages still need to be updated as well:

* async-channel
* async-process (awaits new crate async-signal)
* async-std (awaits async-process)
* blocking
* criterion (awaits smol)
* criterion-0.3 (awaits smol)
* fs4 (awaits smol)
* if-watch (awaits smol)
* isahc
* sluice
* smol
* zbus

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1073811: missing dependency on i3ipc

[Antoine Beaupre]

Package: nwg-displays
Version: 0.3.20-1
Severity: serious

Out of the box, installing nwg-displays fails to start:

anarcat@angela:~$ nwg-displays 

(nwg-displays:270283): dbind-WARNING **: 16:47:31.358: AT-SPI: Error retrieving 
accessibility bus address: org.freedesktop.systemd1.UnitMasked: Unit 
at-spi-dbus-bus.service is masked.
Traceback (most recent call last):
  File "/usr/bin/nwg-displays", line 33, in 
sys.exit(load_entry_point('nwg-displays==0.3.20', 'gui_scripts', 
'nwg-displays')())
 
^^^
  File "/usr/bin/nwg-displays", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
module = import_module(match.group('module'))
 
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1149, in _find_and_load_unlocked
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/nwg_displays/main.py", line 34, in 

from nwg_displays.tools import *
  File "/usr/lib/python3/dist-packages/nwg_displays/tools.py", line 15, in 

from i3ipc import Connection
ModuleNotFoundError: No module named 'i3ipc'

Installing python3-i3ipc fixes this problem.

This might be specific to my computer though: I cheated by installing
the package from unstable in bookworm/stable...

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

Kernel: Linux 6.6.13+bpo-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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 nwg-displays depends on:
ii  libgtk-3-dev3.24.38-2~deb12u1
ii  libgtk-layer-shell-dev  0.8.0-1
ii  python3 3.11.2-1+b1

nwg-displays recommends no packages.

nwg-displays suggests no packages.

-- no debconf information

Processed: fix severity

[Debian Bug Tracking System]

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

> severity 1073807 important
Bug #1073807 [libreoffice] windows binaries without source
Severity set to 'important' from 'serious'
> severity 1073808 important
Bug #1073808 [libreoffice] minified inline javascript without sources
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1069575: FTBFS in experimental

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2024-06-18 22:06:09)
> Quoting Matthias Geiger (2024-06-18 15:19:23)
> > anything blocking an upload of async-process 2.3.0 to exp ?
> 
> That it doesn't exist?
> 
> Newest upstream release of async-process is v2.2.3.
> 
> Not sure why you need it - there is zero functional changes for for
> non-android systems since v2.2.1 currently in experimental.
> 
> I'll do the update now, regardless.

Ah, now I remember why I didn't update: recent releases of async-process
needs crate async-signal which is not in Debian.

I have not found time yet to pacakge async-signal - you or anyone else,
feel free to package async-signal.

There is no point in updating async-process, as that won't make the FTBFS
disappear.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1069575: FTBFS in experimental

[Jonas Smedegaard]

Quoting Matthias Geiger (2024-06-18 15:19:23)
> anything blocking an upload of async-process 2.3.0 to exp ?

That it doesn't exist?

Newest upstream release of async-process is v2.2.3.

Not sure why you need it - there is zero functional changes for for
non-android systems since v2.2.1 currently in experimental.

I'll do the update now, regardless.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1072310: marked as done (nheko: FTBFS on armhf: virtual memory exhausted: Cannot allocate memory)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 16:02:16 -0400
with message-id 

and subject line Re: nheko: FTBFS on armhf: virtual memory exhausted: Cannot 
allocate memory
has caused the Debian Bug report #1072310,
regarding nheko: FTBFS on armhf: virtual memory exhausted: Cannot allocate 
memory
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.)


-- 
1072310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nheko
Version: 0.11.3+~0.9.2+~1.0.0+~0.3.0-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=nheko=armhf=0.11.3%2B%7E0.9.2%2B%7E1.0.0%2B%7E0.3.0-2%2Bb1=1717146143=0

In member function ‘constexpr std::vector<_Tp, _Alloc>::reference 
std::vector<_Tp, _Alloc>::emplace_back(_Args&& ...) [with _Args = 
{std::basic_string_view >&, StoredOlmSession&}; 
_Tp = std::pair, StoredOlmSession>; _Alloc = 
std::allocator, StoredOlmSession> 
>]’,
inlined from ‘Cache::runMigrations()::’ at 
/<>/src/Cache.cpp:1355:45:
/usr/include/c++/13/bits/vector.tcc:123:28: note: parameter passing for 
argument of type 
‘__gnu_cxx::__normal_iterator, 
StoredOlmSession>*, std::vector, 
StoredOlmSession> > >’ changed in GCC 7.1
  123 |   _M_realloc_insert(end(), std::forward<_Args>(__args)...);
  |   ~^~~
In file included from /usr/include/c++/13/vector:66:
In member function ‘constexpr void std::vector<_Tp, _Alloc>::push_back(const 
value_type&) [with _Tp = 
std::variant, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::EncryptedEvent, 
mtx::events::RedactionEvent, mtx::events::Sticker, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent >; _Alloc = 
std::allocator,
 mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::EncryptedEvent, 
mtx::events::RedactionEvent, mtx::events::Sticker, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent, 
mtx::events::RoomEvent > >]’,
inlined from ‘Cache::runMigrations()::’ at 
/<>/src/Cache.cpp:1287:60:
/usr/include/c++/13/bits/stl_vector.h:1292:28: note: parameter passing for 
argument of type 
‘__gnu_cxx::__normal_iterator,
 mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 
mtx::events::StateEvent, 

Bug#1073808: minified inline javascript without sources

[Paul Tagliamonte]

Package: libreoffice
Severity: serious
User: paul...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

there looks to be a vendored copy of jQuery in
wizards/source/access2base/*.html

javascript in this form has been an ongoing struggle to get our arms
around as a project. Having the unminimized javascript that that was
generated from in the source tarball is likely the easiest way to get to
complience without modifying the code and adding a package dependency on
jQuery. If there's already a copy I missed, we can just close this bug.

Thank you for all your work,
  paultag

-- 
  ⢀⣴⠾⠻⢶⣦⠀   Paul Tagliamonte 
  ⣾⠁⢠⠒⠀⣿⡁  https://people.debian.org/~paultag | https://pault.ag/
  ⢿⡄⠘⠷⠚⠋Debian, the universal operating system.
  ⠈⠳⣄⠀⠀  4096R / FEF2 EB20 16E6 A856 B98C  E820 2DCD 6B5D E858 ADF3


signature.asc
Description: PGP signature

Bug#1073807: windows binaries without source

[Paul Tagliamonte]

Package: libreoffice
Severity: serious
User: paul...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

There are some windows binaries in
testtools/source/cliversioning/version_libs/version_3_0_0.dll. The readme
notes that the files aren't reproducable given the current build env.

I'd usually spend a bit more time figuring out if we had source for it
and can find a way to maintain them in some form, but I don't think the
windows DLLs are used -- are they?

If it's possible to drop them that'd be ideal; if not, I'd love to make
sure we have (and maybe document in some form) where the source is for
those DLLs.

Thank you for all your work,
  paultag

-- 
  ⢀⣴⠾⠻⢶⣦⠀   Paul Tagliamonte 
  ⣾⠁⢠⠒⠀⣿⡁  https://people.debian.org/~paultag | https://pault.ag/
  ⢿⡄⠘⠷⠚⠋Debian, the universal operating system.
  ⠈⠳⣄⠀⠀  4096R / FEF2 EB20 16E6 A856 B98C  E820 2DCD 6B5D E858 ADF3


signature.asc
Description: PGP signature

Bug#1073451: marked as done (wlgreet: FTBFS: unsatisfiable build-dependency: librust-smithay-client-toolkit-dev (< 0.17~) but 0.18.1-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 19:00:22 +
with message-id 
and subject line Bug#1073451: fixed in rust-smithay-client-toolkit-0.16 0.16.1-5
has caused the Debian Bug report #1073451,
regarding wlgreet: FTBFS: unsatisfiable build-dependency: 
librust-smithay-client-toolkit-dev (< 0.17~) but 0.18.1-1 is to be installed
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-cargo, 
> librust-smithay-client-toolkit-dev (>= 0.16.1~), 
> librust-smithay-client-toolkit-dev (<< 0.17~), librust-rusttype-dev (>= 
> 0.9.2), librust-chrono-dev (>= 0.4), librust-nix-dev (>= 0.15), 
> librust-memmap2-dev (>= 0.3), librust-os-pipe-dev (>= 0.8), 
> librust-wayland-client-0.29-dev, librust-wayland-protocols-0.29-dev, 
> librust-lazy-static-dev (>= 1.4), librust-serde-derive-dev (>= 1.0), 
> librust-greetd-ipc+thiserror-dev (>= 0.10), librust-getopts-dev (>= 0.2), 
> librust-toml-dev (>= 0.5), pkgconf, dh-exec, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-cargo, 
> librust-smithay-client-toolkit-dev (>= 0.16.1~), 
> librust-smithay-client-toolkit-dev (<< 0.17~), librust-rusttype-dev (>= 
> 0.9.2), librust-chrono-dev (>= 0.4), librust-nix-dev (>= 0.15), 
> librust-memmap2-dev (>= 0.3), librust-os-pipe-dev (>= 0.8), 
> librust-wayland-client-0.29-dev, librust-wayland-protocols-0.29-dev, 
> librust-lazy-static-dev (>= 1.4), librust-serde-derive-dev (>= 1.0), 
> librust-greetd-ipc+thiserror-dev (>= 0.10), librust-getopts-dev (>= 0.2), 
> librust-toml-dev (>= 0.5), pkgconf, dh-exec, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1129 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1162 B]
> Fetched 2906 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: 
> librust-smithay-client-toolkit-dev (< 0.17~) but 0.18.1-1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/wlgreet_0.5.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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: rust-smithay-client-toolkit-0.16
Source-Version: 0.16.1-5
Done: James McCoy 

We believe that the bug you reported is fixed in the latest version of
rust-smithay-client-toolkit-0.16, which is due to be installed in 

Bug#1073404: marked as done (kitinerary: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 18:35:47 +
with message-id 
and subject line Bug#1073404: fixed in kitinerary 22.12.3-4
has caused the Debian Bug report #1073404,
regarding kitinerary: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j1
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> 
> [...]
> 
> The following tests FAILED:
>23 - structureddataextractortest (Failed)
>25 - htmldocumenttest (Failed)
>35 - extractortest (Failed)
> Errors while running CTest
> make[2]: *** [Makefile:74: test] Error 8
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test 
> ARGS\+=--verbose ARGS\+=-j1 returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/kitinerary_22.12.3-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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: kitinerary
Source-Version: 22.12.3-4
Done: Patrick Franz 

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

Debian distribution maintenance software
pp.
Patrick Franz  (supplier of updated kitinerary package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jun 2024 20:27:41 +0200
Source: kitinerary
Architecture: source
Version: 22.12.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Patrick Franz 
Closes: 1073404
Changes:
 kitinerary (22.12.3-4) unstable; urgency=medium
 .
   [ Patrick Franz ]
   * Build-depend on pkgconf instead of pkg-config as the latter has been
 superseded by the former.
   * Disable tests (Closes: #1073404).
Checksums-Sha1:
 86f4302448b652bf3c7685f48bb7eb9be39e6a14 2843 kitinerary_22.12.3-4.dsc
 7112f96ed85de57fbc71705944173a391a0461cb 15240 
kitinerary_22.12.3-4.debian.tar.xz
 c40b598f82d4acdbc56bce776817e500c7b1b27e 13003 
kitinerary_22.12.3-4_source.buildinfo
Checksums-Sha256:
 5d51c9714fd2a82fda626c65b669e66c471817291b564cfb09202fde433359c6 2843 
kitinerary_22.12.3-4.dsc
 44c989d58191d85e8033c262b43742777225631be1aea6cdc0ca48976fafc16d 15240 
kitinerary_22.12.3-4.debian.tar.xz
 fb6e901e32e51a33d8519f4028bf89364e0a18330a8966d56dfdebfddfa5a16b 13003 
kitinerary_22.12.3-4_source.buildinfo
Files:
 2149f59b478b3e8bbd0ba8511d168000 2843 libs optional kitinerary_22.12.3-4.dsc
 

Bug#1073785: marked as pending in debootstrap

[Luca Boccassi]

Control: tag -1 pending

Hello,

Bug #1073785 in debootstrap 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/installer-team/debootstrap/-/commit/89571b21021f84488f63c036023746d88f109507


Merge branch 'bug/1073785' into 'master'

reinstate Debian codename symlinks (closes: #1073785)

See merge request installer-team/debootstrap!118


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073785

Processed: Bug#1073785 marked as pending in debootstrap

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073785 [debootstrap-udeb] debootstrap-udeb: removal of trixie --> sid 
link causes fatal error in D-I
Ignoring request to alter tags of bug #1073785 to the same tags previously set

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

Bug#1073785: marked as pending in debootstrap

[Luca Boccassi]

Control: tag -1 pending

Hello,

Bug #1073785 in debootstrap 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/installer-team/debootstrap/-/commit/cf55650623a4a87ab353a7a89fa18debca239f5f


reinstate Debian codename symlinks (closes: #1073785)

This reverts the removal of Debian codename symlinks from
commit 2d3eae916af51cc49ab0989cea1f5bfb58012179
because their absence breaks debootstrap when run in Debian-Installer
(which does not have `distro-info` available).

It seems entierly plausible that the absence of the Ubuntu symlinks will
similarly break debian-installer when used to install Ubuntu, but I'll
leave those as they are until that's confirmed by someone from Ubuntu.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073785

Processed: Bug#1073785 marked as pending in debootstrap

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073785 [debootstrap-udeb] debootstrap-udeb: removal of trixie --> sid 
link causes fatal error in D-I
Added tag(s) pending.

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

Bug#1073394: ktextaddons: FTBFS: unsatisfiable build-dependencies: libkf6archive-dev (>= 6.0.0~), libkf6configwidgets-dev (>= 6.0.0~), libkf6coreaddons-dev (>= 6.0.0~), libkf6i18n-dev (>= 6.0.0~), lib

[Patrick Franz]

Hi,

the package was accidentally uploaded to unstable instead of 
experimental and therefore has unsatisfiable build-dependencies.

This will be solved once the KDE Frameworks 6 are uploaded to unstable. 
But since ktextaddons currently does not have any reverse dependencies 
in Debian, I'll leave it at that.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1066608: marked as done (dvbstreamer: FTBFS: standard/dvb/sdtprocessor.c:299:14: error: implicit declaration of function ‘UTF8_nextchar’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 18:20:43 +
with message-id 
and subject line Bug#1066608: fixed in dvbstreamer 2.1.0-5.7
has caused the Debian Bug report #1066608,
regarding dvbstreamer: FTBFS: standard/dvb/sdtprocessor.c:299:14: error: 
implicit declaration of function ‘UTF8_nextchar’ 
[-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.)


-- 
1066608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvbstreamer
Version: 2.1.0-5.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..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../include  
> -D_GNU_SOURCE -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fno-strict-aliasing -c -o sdtprocessor.o `test -f 
> 'standard/dvb/sdtprocessor.c' || echo './'`standard/dvb/sdtprocessor.c
> standard/dvb/sdtprocessor.c: In function ‘removeControlCodes’:
> standard/dvb/sdtprocessor.c:299:14: error: implicit declaration of function 
> ‘UTF8_nextchar’ [-Werror=implicit-function-declaration]
>   299 | ch = UTF8_nextchar(str, );
>   |  ^
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:905: sdtprocessor.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/dvbstreamer_2.1.0-5.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: dvbstreamer
Source-Version: 2.1.0-5.7
Done: Francisco Vilmar Cardoso Ruviaro 

We believe that the bug you reported is fixed in the latest version of
dvbstreamer, 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.
Francisco Vilmar Cardoso Ruviaro  (supplier of updated 
dvbstreamer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 11 Jun 2024 16:44:11 +
Source: dvbstreamer
Architecture: source
Version: 2.1.0-5.7
Distribution: unstable
Urgency: medium
Maintainer: A Mennucc1 
Changed-By: Francisco Vilmar Cardoso Ruviaro 
Closes: 1066608
Changes:
 dvbstreamer (2.1.0-5.7) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add debian/patches/no-implicit-declarations.patch,
 fix missing declaration of UTF8_nextchar() and typo.
 Thanks to Steve Langasek . (Closes: #1066608)
Checksums-Sha1:
 25f64f47412b63abd10418a2070edcc0103a64f2 1965 dvbstreamer_2.1.0-5.7.dsc
 df76be59e6b9d846df696453dd7c01d497bb9b93 9628 
dvbstreamer_2.1.0-5.7.debian.tar.xz
 81049cbc74513902d3f6f9ca9cefecf9d26ff219 7678 
dvbstreamer_2.1.0-5.7_amd64.buildinfo
Checksums-Sha256:
 5cda65666bf366a1bc956b1a1d23ab12c6098eb3ba120f39eec0f7ba0493b288 1965 
dvbstreamer_2.1.0-5.7.dsc
 b70b501fc0c9bfa18ae349eab356fcfaa99fab9d901703353c8128cd714bd9df 9628 
dvbstreamer_2.1.0-5.7.debian.tar.xz
 

Bug#1072828: Work-around is ineffective on !amd64

[Preuße]

On 18.06.2024 15:26, Adrien Nader wrote:

Hi Adrien,


I hit that issue while working on the vtk9 9.3 transition in Ubuntu and
I also tried to add 'texlive-fonts-recommended' as a dependency (at
least temporarily so that the transition can finish). Unfortunately it
only works on amd64. On arm64, armhf, ppc64el and s390x, the error is
still present (see
https://launchpad.net/~adrien/+archive/ubuntu/oracular-gdcm-ftbfs-vtk-9.3/+sourcepub/16226649/+listing-archive-extra
)

I didn't investigate further.

>
If you look at the build logs you'll notice that only on amd64 the
package texlive-fonts-recommended was installed. Not sure, why this
happened, but you added it to Build-Depends-Indep instead of
Build-Depends (as it was done for texlive-base).

H.
--
sigfault

Processed: bug 1073595 is forwarded to https://github.com/libuv/libuv/issues/4436

[Debian Bug Tracking System]

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

> forwarded 1073595 https://github.com/libuv/libuv/issues/4436
Bug #1073595 [libuv1t64] Missing symbols in the library file compared to the 
headers
Set Bug forwarded-to-address to 'https://github.com/libuv/libuv/issues/4436'.
> thanks
Stopping processing here.

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

Bug#1073801: postgresql-16-pgtt: ships /usr/share/doc/postgresql-doc-16/extension/README.md.gz

[Andreas Beckmann]

Package: postgresql-16-pgtt
Version: 4.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

/usr/share/doc/postgresql-doc-16/extension/README.md.gz is a very
generic name (and not in its package name namespace) that should not be
shipped by any postgresql extension.

This causes file conflicts with other packages doing the same mistake.


cheers,

Andreas

Bug#1073800: postgresql-16-q3c: ships /usr/share/doc/postgresql-doc-16/extension/README.md.gz

[Andreas Beckmann]

Package: postgresql-16-q3c
Version: 2.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

/usr/share/doc/postgresql-doc-16/extension/README.md.gz is a very
generic name (and not in its package name namespace) that should not be
shipped by any postgresql extension.

This causes file conflicts with other packages doing the same mistake.


cheers,

Andreas

Bug#1072073: marked as done (python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 16:21:33 +
with message-id 
and subject line Bug#1072073: fixed in nanopb 0.4.8-2
has caused the Debian Bug report #1072073,
regarding python3-proto-plus has an undeclared file conflict on 
/usr/lib/python3/dist-packages/proto/__init__.py
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.)


-- 
1072073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-proto-plus
Version: 1.23.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + nanopb

python3-proto-plus has an undeclared file conflict. This may result in
an unpack error from dpkg.

The file /usr/lib/python3/dist-packages/proto/__init__.py is contained
in the packages
 * nanopb
   * 0.4.4-2 as present in bullseye
   * 0.4.7-2 as present in bookworm
   * 0.4.8-1 as present in trixie|unstable
 * python3-proto-plus/1.23.0-1 as present in unstable

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

Kind regards

The Debian Usr Merge Analysis Tool

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated nanopb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jun 2024 17:14:12 +0200
Source: nanopb
Architecture: source
Version: 0.4.8-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1072073
Changes:
 nanopb (0.4.8-2) unstable; urgency=medium
 .
   * Do not force install proto files to wrong location (closes: #1072073).
   * Update Standards-Version to 4.7.0 .
Checksums-Sha1:
 a74fd6131143e7c868a7651e42bfc0b679e78771 1837 nanopb_0.4.8-2.dsc
 848ead4bfe747c45caf4d9bee20651f6b6f82aae 4984 nanopb_0.4.8-2.debian.tar.xz
Checksums-Sha256:
 09f97b644a88e3359147a0b3c147330ea79cd47f75f4cf87e336373c25dd6b69 1837 
nanopb_0.4.8-2.dsc
 46cc80b069c3ef37ee54e024e63b432fb263fa0db1805e9f188d0b4d384eac3a 4984 
nanopb_0.4.8-2.debian.tar.xz
Files:
 1df3519b1a7f94d1569e0cb54fa65bc1 1837 devel optional nanopb_0.4.8-2.dsc
 8f2adf08fbc3e67da40e94eb910dce89 4984 devel optional 
nanopb_0.4.8-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmZxrgQACgkQ3OMQ54ZM
yL+aQQ/+OAtAFBgtCuhpb38M0arrkRZidiZvEvJe2PmcfrxvgtpRgm/lUVNhXPJy
zlrucyJR/O4kTPX6Ne1LLu8ntKCBcal5XzhZ6Tvex0GJTBNIUePcsL9BQoR3Kyex
zDpb4RpApugjUjDGpD9paJLCfRzuXodwqrJVLtcRF6UunSkmZXoxTP3H1pUGrwhh
Bhm7AuHD9JKTUrGCBVdI0Kl0S3XxwOBFVxxwIk4rvspikQpzM7XEjouijdaYq43R
S6+VSmkLZZwh+0SbZSCoOmRAnYSJr+DfDcc9e7c6lef5oL4dJc/vNX86MmKjUyKv
pLUKQ/kx0LHkY6JwSATjzriGEtfluam1VtDEcb4lHI8hiMs8B7z9j2GrrsRTtlZc
O2RYE8PNFyT2tJRc1ShJiG2SwCl5c/9Q8QtwHeXt89wGm2DZVMrRc7l6InCXCQza
PUafvNa99KstC80uh9jDeIXS1QXDhqvMP5zflnz965Ofh4yz5gw5oQN4M2O1iXPZ
hqBaIUDlGGCQzDVpKomCmcujLLJA9lC2zdiHoNUD5nOa/CNrE1qMOSA1f7Sh7aW8
zCAFQhWkQgx/6PZsY+oz7CUc07BIN5ykfUVMkSFFdxccKLMbRweguE5ZMAOuexFA
IVhmt/ghc8eov19Dbr8fwluNyRmVgXnqyO+HXOwFIHbxK5RDKAk=
=dvxT
-END PGP SIGNATURE-



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

Bug#1072952: marked as done (krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal TERM after 60 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 15:53:04 +
with message-id 
and subject line Bug#1072952: fixed in krb5 1.21.2-1
has caused the Debian Bug report #1072952,
regarding krb5: FTBFS: ../../src/tests/t_iprop.py - E: Build killed with signal 
TERM after 60 minutes of inactivity
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.)


-- 
1072952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: krb5
Version: 1.20.1-6
Severity: serious
Tags: ftbfs
X-Debbugs-CC: jspri...@debian.org

Filing with severity: serious as the buildd network has started
switching to sbuild with unshare backend, and multiple people have
reproduced this problem.

When building krb5 with sbuild, configured to use the unshare
backend, the t_iprop.py test apparently times out without any
output.

Last few lines:

| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_general.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_hooks.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_dump.py
| PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_iprop.py
| E: Build killed with signal TERM after 60 minutes of inactivity

I'm attaching my own build log, running on arm64. Another build log
showing the same problem can be found here (ran on amd64):

https://people.debian.org/~sanvila/unshare/unstable-20240529/krb5_1.20.1-6_amd64-20240529T214515.396Z

My build log shows the result of an external SIGTERM instead of
sbuild killing it, but that's just a distracting detail.

I'll note this appears unrelated to #1063648.

Chris



krb5_1.20.1-6_arm64-killed.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: krb5
Source-Version: 1.21.2-1
Done: Sam Hartman 

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated krb5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Jun 2024 16:39:28 -0600
Source: krb5
Architecture: source
Version: 1.21.2-1
Distribution: unstable
Urgency: medium
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Closes: 1070848 1072915 1072952
Changes:
 krb5 (1.21.2-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster (oldstable)
 .
   [ Otto Kekäläinen ]
   * Run 'wrap-and-sort'
   * Drop obsolete dependency on package lsb-base
   * Make package Lintian clean
   * Enable Salsa-CI
 .
   [ Chris Hofstaedtler ]
   *  Install systemd unit overrides into /usr. (DEP17 M2). Closes: #1072915
 .
   [ Sam Hartman ]
   * New Upstream version 1.21.2, Closes: #1070848
   * Update symbols and breaks for internal APIs that were removed
   * Allow kpropd to bind even if only loopback is configured, Closes: #1072952
   * Skip keyring tests if keyring blocked by seccomp
Checksums-Sha1:
 60a911739cfda48b4e06e1c0e5632035d602af60 3349 krb5_1.21.2-1.dsc
 b88e9f819974a82d156654dccbd5ee3d1de8a98e 8622513 krb5_1.21.2.orig.tar.gz
 93f86ad296b3563d782bd732def6ae3ced5b7050 833 krb5_1.21.2.orig.tar.gz.asc
 7ce230f0578aa5427b52c02d38db8ff34c943578 105940 krb5_1.21.2-1.debian.tar.xz
 fb428eccef249a0355e136e07053e3febda68583 4964 krb5_1.21.2-1_source.buildinfo
Checksums-Sha256:
 8f80fad14f6601e2140e2e17cffdd82af02213147d7a97bb4d2fc9645b49a29a 3349 
krb5_1.21.2-1.dsc
 9560941a9d843c0243a71b17a7ac6fe31c7cebb5bce3983db79e52ae7e850491 8622513 
krb5_1.21.2.orig.tar.gz
 780b07aad5ac5449d1dd735dd42fd3325ec851b316d075a54a24f35d3e945190 833 
krb5_1.21.2.orig.tar.gz.asc
 2ca45ecfc20dd6c1ac3f4a1bb62544649b853e89d9d7a3a8238ad2f407258866 105940 
krb5_1.21.2-1.debian.tar.xz
 b738b1609a36b35519234b7c6fd61058bed1e261accbc99fb848077201ed6e48 4964 
krb5_1.21.2-1_source.buildinfo
Files:
 b96ddd59a6b293cd55446b8cd5527e47 3349 net optional krb5_1.21.2-1.dsc
 97d5f3a48235c53f6d537c877290d2af 8622513 net optional krb5_1.21.2.orig.tar.gz
 2ef538e3afa3d740821a37675f194c3d 833 net optional krb5_1.21.2.orig.tar.gz.asc
 

Processed: Re: Bug#1073416: jpeg-xl: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test returned exit code 1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #1073416 [src:jpeg-xl] jpeg-xl: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test returned 
exit code 1
Added tag(s) confirmed.

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

Bug#1073416: jpeg-xl: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test returned exit code 1

[Mathieu Malaterre]

Control: tags -1 confirmed

[0.9.x is pending the transition green light from debian-release team]

On Sun, Jun 16, 2024 at 3:35 PM Lucas Nussbaum  wrote:
>
> Source: jpeg-xl
> Version: 0.8.2-4
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240615 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
[...]
> >
> > The following tests FAILED:
> >   1800 - DecodeTest.ExtentedBoxSizeTest (Failed)

It looks like the testdata has changed one file in place. So libjxl
0.8.x and 0.9.x test suite do not seem to have a consistent behavior
with the following file (*).

Moritz, could you confirm that libjxl 0.8.x is expected to fail
DecodeTest.ExtentedBoxSizeTest and as such should be considered an
invalid release for Debian archive ?

(*)
% git log -- jxl/boxes/square-extended-size-container.jxl
commit 8a1dafb89c27ce0d31ab98b122bafa65869e129a
Author: Moritz Firsching 
Date:   Thu Nov 23 10:55:45 2023 +0100

fix extended size container

commit f5158aa87916ffad4b5497bd1edf3ebab8aadbab
Author: Moritz Firsching 
Date:   Wed Jun 15 13:53:10 2022 +0200

add jxl with extented size container (#5)

Bug#1050805: dhcpcd-base: DoS: zero-length packet cause eventual lease expiration

[Martin-Éric Racine]

ti 18. kesäk. 2024 klo 15.52 Nicolas Cavallari
(nicolas.cavall...@green-communications.fr) kirjoitti:
>
> On 18/06/2024 13:14, Martin-Éric Racine wrote:
> > su 16. kesäk. 2024 klo 9.05 Martin-Éric Racine
> > (martin-eric.rac...@iki.fi) kirjoitti:
> >>
> >> la 15. kesäk. 2024 klo 16.55 Nicolas Cavallari
> >> (nicolas.cavall...@green-communications.fr) kirjoitti:
> >>
> >>> I didn't check if there were any adverse effect or if leases are still
> >>> renewed. I can't check on the production system before Monday.
> >>
> >> Please let me know.
> >
> > Any news on this?
>
> My dedicated server receives leases of 86400s, it takes a while to check
> if leases are renewed correctly.

Noted.

> I installed it today. For some reason, dhcpcd was stopped when upgrading
> the 'dhcpcd' package but was not restarted afterward. Looking at the
> dhcpcd maintainer scripts, I see the deb-systemd-invoke stop in preinst
> but i don't see any start in postinst or anywhere else.

Which was fixed in Testing a while back.

For Stable, this is what I would upload, once you've confirmed that
the 3 cherry-picks work:

dhcpcd5 (9.4.1-24~deb12u4) bookworm; urgency=medium
  * Add --no-stop-on-upgrade --no-restart-after-upgrade (Closes: #1057959).
  * Cherry-pick upstream backported fixes for RC bug (Closes: #1050805).
  * Update dhcpcd.preinst version check to match current one.

On the plus side, no attempt will be made to restart it, to prevent
connection loss. On the minus side, it means that the administrator
must restart manually or reboot.

Martin-Éric

Processed: Re: pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> forwarded 1073443 https://github.com/pytest-dev/pytest/issues/12284
Bug #1073443 [src:pytest-rerunfailures] pytest-rerunfailures: FTBFS: 
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 
3.11" returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest/issues/12284'.
> tags 1073443 + upstream
Bug #1073443 [src:pytest-rerunfailures] pytest-rerunfailures: FTBFS: 
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 
3.11" returned exit code 13
Added tag(s) upstream.

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

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

[Timo Röhling]

Control: forwarded 1073443 https://github.com/pytest-dev/pytest/issues/12284
Control: tags 1073443 + upstream

It looks like rerunfailures plugin erroneously deletes the session 
teardown from the execution stack if a test fails and is rerun. You 
can reproduce the bug with the attached script 
pytest_session_fixture.py:


- Running `pytest pytest_session_fixture.py -s` will show "session teardown" 
  is run regardless of the flaky test outcome
- Running `pytest pytest_session_fixture.py -s --reruns 1` will only show 
  "session teardown" if the flaky test succeeds on the first try.


This bug was exposed by a change in pytest 8.2 and currently 
prevents pytest from migrating to testing.



Cheers
Timo

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

import pytest
import random


@pytest.fixture(scope="session", autouse=True)
def my_session():
print("session setup")
yield
print("session teardown")

@pytest.fixture(autouse=True)
def my_function():
print("function setup")
yield
print("function teardown")

def test_flaky():
print("test_flaky")
assert random.randint(0, 1) == 0



signature.asc
Description: PGP signature

Bug#1072828: Work-around is ineffective on !amd64

[Adrien Nader]

Hi,

I hit that issue while working on the vtk9 9.3 transition in Ubuntu and
I also tried to add 'texlive-fonts-recommended' as a dependency (at
least temporarily so that the transition can finish). Unfortunately it
only works on amd64. On arm64, armhf, ppc64el and s390x, the error is
still present (see
https://launchpad.net/~adrien/+archive/ubuntu/oracular-gdcm-ftbfs-vtk-9.3/+sourcepub/16226649/+listing-archive-extra
)

I didn't investigate further.

-- 
Adrien

Bug#1073426: marked as done (spirv-llvm-translator-15: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 13:28:00 +
with message-id 
and subject line Bug#1073426: fixed in spirv-llvm-translator-15 15.0.1-1
has caused the Debian Bug report #1073426,
regarding spirv-llvm-translator-15: FTBFS: dh_auto_test: error: cd build && 
make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2
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.)


-- 
1073426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spirv-llvm-translator-15
Version: 15.0.0-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/build'
> [100%] Running the LLVM-SPIRV regression tests
> cd /<>/build/test && /usr/lib/llvm-15/build/utils/lit/lit.py 
> --verbose -sv /<>/build/test
> lit.py: /usr/lib/llvm-15/build/utils/lit/lit/llvm/config.py:449: note: using 
> clang: /usr/lib/llvm-15/bin/clang
> -- Testing: 693 tests, 8 workers --
> Testing: 0  2  4  6  8  10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 
> 46 48 50 52 54 56 58 
> FAIL: LLVM_SPIRV :: read_image.cl (419 of 693)
>  TEST 'LLVM_SPIRV :: read_image.cl' FAILED 
> 
> Script:
> --
> : 'RUN: at line 1';   /usr/lib/llvm-15/bin/clang -cc1 -internal-isystem 
> /usr/lib/llvm-15/lib/clang/15.0.7/include -nostdsysteminc -triple spir64 
> -fdeclare-opencl-builtins -finclude-default-header -O0 -cl-std=CL2.0 
> -emit-llvm-bc /<>/test/read_image.cl -o 
> /<>/build/test/test_output/Output/read_image.cl.tmp.bc 
> -no-opaque-pointers
> : 'RUN: at line 2';   /<>/build/tools/llvm-spirv/llvm-spirv 
> --spirv-max-version=1.3 
> /<>/build/test/test_output/Output/read_image.cl.tmp.bc -o 
> /<>/build/test/test_output/Output/read_image.cl.tmp.spv
> : 'RUN: at line 3';   /usr/bin/spirv-val 
> /<>/build/test/test_output/Output/read_image.cl.tmp.spv
> : 'RUN: at line 4';   /<>/build/tools/llvm-spirv/llvm-spirv 
> /<>/build/test/test_output/Output/read_image.cl.tmp.spv -to-text 
> -o - | /usr/lib/llvm-15/bin/FileCheck /<>/test/read_image.cl 
> --check-prefix=CHECK-SPIRV
> : 'RUN: at line 5';   /<>/build/tools/llvm-spirv/llvm-spirv -r 
> /<>/build/test/test_output/Output/read_image.cl.tmp.spv -o 
> /<>/build/test/test_output/Output/read_image.cl.tmp.rev.bc 
> --spirv-target-env=SPV-IR
> : 'RUN: at line 6';   /usr/lib/llvm-15/bin/llvm-dis < 
> /<>/build/test/test_output/Output/read_image.cl.tmp.rev.bc | 
> /usr/lib/llvm-15/bin/FileCheck /<>/test/read_image.cl 
> --check-prefix=CHECK-SPV-LLVM
> : 'RUN: at line 7';   /<>/build/tools/llvm-spirv/llvm-spirv 
> --spirv-max-version=1.3 
> /<>/build/test/test_output/Output/read_image.cl.tmp.rev.bc -o 
> /<>/build/test/test_output/Output/read_image.cl.tmp.rev.spv
> : 'RUN: at line 8';   /usr/bin/spirv-val 
> /<>/build/test/test_output/Output/read_image.cl.tmp.rev.spv
> : 'RUN: at line 9';   /<>/build/tools/llvm-spirv/llvm-spirv 
> --spirv-max-version=1.3 
> /<>/build/test/test_output/Output/read_image.cl.tmp.rev.spv 
> -to-text -o - | /usr/lib/llvm-15/bin/FileCheck 
> /<>/test/read_image.cl --check-prefix=CHECK-SPIRV
> --
> Exit Code: 1
> 
> Command Output (stderr):
> --
> error: line 54: ID '9' decorated with Alignment multiple times is not allowed.
>   %input_addr = OpVariable %_ptr_Function_3 Function
> 
> 
> --
> 
> 
> Testing: 0  2  4  6  8  10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 
> 46 48 50 52 54 56 58 60 62 64 66 
> FAIL: LLVM_SPIRV :: transcoding/OpPhi_ArgumentsPlaceholders.ll (486 of 693)
>  TEST 'LLVM_SPIRV :: 
> transcoding/OpPhi_ArgumentsPlaceholders.ll' FAILED 
> Script:
> --
> : 'RUN: at line 15';   /usr/lib/llvm-15/bin/llvm-as 
> /<>/test/transcoding/OpPhi_ArgumentsPlaceholders.ll -o 
> /<>/build/test/test_output/transcoding/Output/OpPhi_ArgumentsPlaceholders.ll.tmp.bc
> : 'RUN: at line 16';   /<>/build/tools/llvm-spirv/llvm-spirv 
> /<>/build/test/test_output/transcoding/Output/OpPhi_ArgumentsPlaceholders.ll.tmp.bc
>  -spirv-text -o 
> /<>/build/test/test_output/transcoding/Output/OpPhi_ArgumentsPlaceholders.ll.tmp.txt
> : 'RUN: at line 17';   /usr/lib/llvm-15/bin/FileCheck < 
> /<>/build/test/test_output/transcoding/Output/OpPhi_ArgumentsPlaceholders.ll.tmp.txt
>  /<>/test/transcoding/OpPhi_ArgumentsPlaceholders.ll 
> --check-prefix=CHECK-SPIRV
> : 'RUN: at line 18';   /<>/build/tools/llvm-spirv/llvm-spirv 
> 

Bug#1061519: shim 15.8-1~deb12u1 missing

[Joe Groocock]

Hi,

We've been awaiting the patched build of shim/shim-unsigned to appear in
bookworm, but despite this commit last month, only the buster package seems
to be available in the repos still
https://salsa.debian.org/efi-team/shim/-/commit/9047a8e8ec4d769b2cb405d109270639096dbde7
Is this expected? Do we know when the patched package might be available?

Thanks, and regards,

*Joe Groocock*  |  System Reliability Engineer
jgrooc...@cloudflare.com
FF8B 8059 B7FA 3FD4 3C05 CB99 0657 91BB A2C6 56A6



1 888 99 FLARE  |  www.cloudflare.com

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Matthias Geiger]

On Mon, 10 Jun 2024 11:17:04 +0200 Jonas Smedegaard  wrote:
> Quoting Jeremy Bícha (2024-04-21 19:47:08)
> > Simple patch attached.
>
> I am not convinced that this issue should be ignored: Might be revealing
> the upstream bugs recently tracked upstream, which might in Debian be
> affected by relaxed dependencies e.g. on concurrent-queue.
>

Any news on this ? event-listener is currently blocking zbus 4.0 which 
in turn prevents me from fixing the remaining GTK4 rust packages.



best, werdahias

Bug#1069575: FTBFS in experimental

[Matthias Geiger]

On Tue, 11 Jun 2024 22:57:35 +0200 Matthias Geiger 
 wrote:
> On Mon, 10 Jun 2024 11:02:23 +0200 Jonas Smedegaard  
wrote:

>
> > >
> > > I will look into updating concurrent-queue to 2.5.0 then.
> >
> > Any news on updating concurrent-queue to 2.5.0?
> >
>
> > - Jonas
>
> Just uploaded to exp along with async-io 2.3.3.
>
>

 Hi Jonas,

anything blocking an upload of async-process 2.3.0 to exp ?


best,


werdahias

Bug#1039883: linux: ext4 corruption with symlinks

[Luis Henriques]

On Tue 18 Jun 2024 10:52:55 AM +01, Luis Henriques wrote;

> On Fri 14 Jun 2024 05:18:45 PM +01, Luis Henriques wrote;
> [...}
>>>
>>> I can also reproduce this error message using the above script and:
>>>
>>> - Linux 6.10-rc2
>>> - A 2 GiB loopback devic instead of /dev/sdb
>>>
>>> I bisected this back to:
>>>
>>> commit 9725958bb75cdfa10f2ec11526fdb23e7485e8e4
>>> Author: Xin Yin 
>>> Date:   Thu Dec 23 11:23:37 2021 +0800
>>>  
>>> ext4: fast commit may miss tracking unwritten range during ftruncate
>>>
>>> It is still possible to cleanly revert that commit from 6.10-rc2, and
>>> doing so removes the error message.
>>
>> Because I recently fixed an issue in the fast commit code[1] I was hoping
>> that you were hitting the same bug.  I've executed the reproducer with the
>> fix (which hasn't been merged yet) and realised it's definitely a
>> different problem.
>>
>> Debugged the issue a bit, it seems to be related with the fact that
>> ext4_fc_write_inode_data() isn't able to cope with the fact that
>> 'ei->i_fc_lblk_len' is set to EXT_MAX_BLOCKS.
>
> OK, I've looked into this again.  And something I didn't pay attention
> before was that the filesystem was created with both fast_commit *and*
> inline_data features.  And after some more debugging, I _think_ the patch
> bellow should be the fix for this bug.
>
> If I understand it correctly, when an inode has inlined data it means that
> there's no inode data to be written and this case should be handled as if
> the inode length was zero.
>
> I'll send out a patch later after running a few more tests just to make
> sure it doesn't break something else.  But it would awesome if you could
> test it too.

Hmm... looking closer, this patch seems to work with this specific test
script, but only because file data is probably small enough to fit in
inode->i_block.  However, it may actually truncate files that have inlined
data if the file data is also stored in the extended attribute space
(i.e. > 60 bytes).

So, the correct fix is probably something like the below patch (which I'll
send out soon).

Cheers,
-- 
Luís

diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
index 87c009e0c59a..d3a67bc06d10 100644
--- a/fs/ext4/fast_commit.c
+++ b/fs/ext4/fast_commit.c
@@ -649,6 +649,12 @@ void ext4_fc_track_range(handle_t *handle, struct inode 
*inode, ext4_lblk_t star
if (ext4_test_mount_flag(inode->i_sb, EXT4_MF_FC_INELIGIBLE))
return;
 
+   if (ext4_has_inline_data(inode)) {
+   ext4_fc_mark_ineligible(inode->i_sb, EXT4_FC_REASON_XATTR,
+   handle);
+   return;
+   }
+
args.start = start;
args.end = end;
 

Bug#1073793: camitk FTBFS with VTK 9.3

[Adrien Nader]

Source: camitk
Version: 5.2.0-1
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source (but built successfully in the past)

While working on the vtk9 9.3 transition in Ubuntu, I found that the
package does not build with VTK 9.3 (at least one incompatibility was
introduced with VTK 9.2).

I've opened a bug report on the upstream bug tracker:
https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/193
and I'm copying the contents here for convenience:

> I found several issues while trying to build camitk for VTK 9.3 in
> Ubuntu/Debian.
> 
> In sdk/components/vtkimage/RawDataDialog.cpp, vtkConfigure.h is not
> packaged anymore and vtkType.h should be included instead
> 
> In sdk/actions/mesh/basicmesh/MeshQuality.cpp, VTK 9.2 has renamed
> SetHexQualityMeasureToMaxEdgeRatios and
> SetQuadQualityMeasureToMaxEdgeRatios: the trailing 's' is removed
> 
> In sdk/actions/mesh/basicmesh/MeshQuality.cpp, VTK 9.2 "vtkMeshQuality
> and vtkCellQuality [...] no longer supports the AspectBeta tetrahedron
> metric", and I'm not sure what to do as this could impact the library's
> API.

The last issue means that API of the package would likely break which
means it would be better to have a new upstream version.

-- 
Adrien

Bug#1073791: shadowsocks-v2ray-plugin: Consider removing the package

[Boyuan Yang]

Source: shadowsocks-v2ray-plugin
Version: 1.3.1-4
Severity: serious
X-Debbugs-CC: r...@debian.org rogershim...@gmail.com 
shadowsocks-v2ray-plu...@packages.debian.org
Tags: sid

Hi,

Following the previous communication in March, I am considering to take action
and remove related packages in the ss-libev ecosystem. Package 
shadowsocks-v2ray-plugin
will be removed together with shadowsocks-libev.

I plan to file RM bug to Debian FTP Masters after 7 days (on 2024-06-25). If you
have any questions, please feel free to let me know.

Thanks,
Boyuan Yang


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

Bug#1050805: dhcpcd-base: DoS: zero-length packet cause eventual lease expiration

[Nicolas Cavallari]

On 18/06/2024 13:14, Martin-Éric Racine wrote:

su 16. kesäk. 2024 klo 9.05 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:


la 15. kesäk. 2024 klo 16.55 Nicolas Cavallari
(nicolas.cavall...@green-communications.fr) kirjoitti:


I didn't check if there were any adverse effect or if leases are still
renewed. I can't check on the production system before Monday.


Please let me know.


Any news on this?


My dedicated server receives leases of 86400s, it takes a while to check 
if leases are renewed correctly.


I installed it today. For some reason, dhcpcd was stopped when upgrading 
the 'dhcpcd' package but was not restarted afterward. Looking at the 
dhcpcd maintainer scripts, I see the deb-systemd-invoke stop in preinst 
but i don't see any start in postinst or anywhere else.

Bug#1071463: marked as done (pygmsh: autopkgtest regression with pytest 8 on i386)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 12:24:47 +
with message-id 
and subject line Bug#1071463: fixed in pygmsh 7.1.17-6
has caused the Debian Bug report #1071463,
regarding pygmsh: autopkgtest regression with pytest 8 on i386
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.)


-- 
1071463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygmsh
Version: 7.1.17-4
Severity: serious
User: debian-rele...@lists.debian.org
Usertags: bsp-2024-05-mdc-ber

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package starting hanging in the autopkgtest on i386 with pytest 8, 
resulting in a timeout.

See https://ci.debian.net/packages/p/pygmsh/testing/i386/46854179/ as example.

Cheers
Timo


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmZKLIsACgkQzIxr3RQD
9MpR0g//WVf5f11r+XYrCspMB2fxm+Z3JNaPh0F+s5zb7Rhwalrjd9k5V+wFy4YO
ebwczCSDHDcg+QTp2ShCj1AZ0LtNi9rVuiGuKoiWou3Up4xYNBjtQ2AnzgVK0gOO
/kWWIwIgFqK7n1mMNRQlEQHl4WEKvkg5yTVVF/YmJ4PDwgbhZRjsGjupM5uv7uVO
4wopGPU4nC/IpBbpiNaQQdou+JpRQbHJZztgQnNR000SIVdy2OJSfaSLlkmGRGxb
vipw1AoCIugJV+6r9rJh6Zn+flZtqdz1eN4Zc/nsaSX2r+WF8CSnTHVw7RIOG8iT
NTI0HDhZelSb2s2q+Awb/yqOXzbEnqszZ1rN6mPME7z9STu2PXIwKhxzMM67p2Ky
GMiknL1v/51AnhNKZxB5iDPsoEnvEK/lJB/fB94AnWW1SjrhnzZxLGIj1e00RkS1
AHJnI6v7epPHSQzT6t1kJVR/VjOn7ptOr3CvhyhzXLr85a9QrTaaEY/ybToTMZ1C
95btUQeCkWMhOC5PXFlkN+1Nx6G5FAvzx2wy5oEfiLbXAL+6X8LUFOxWDG2E4loa
wHlGj/mMrmuWw/UvL3Aw2WLO+Hts4OYdSbWv6z2hLl/YF/ZLGaEyLrmPqya/7SAL
Il/0wMuJ8zk6NV5rWLsOcBNvWvFQsIwudyaXKqMVySscO0PFS0s=
=yFnQ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: pygmsh
Source-Version: 7.1.17-6
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated pygmsh 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: Tue, 18 Jun 2024 13:13:38 +0200
Source: pygmsh
Architecture: source
Version: 7.1.17-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 1071463
Changes:
 pygmsh (7.1.17-6) unstable; urgency=medium
 .
   * simplify test restrictions on i386. Closes: #1071463.
Checksums-Sha1:
 fd4c1114a259b2045b03ab71639bf495deaade0b 2348 pygmsh_7.1.17-6.dsc
 ad59e125319a05b71118285179d08ac1e9778763 4368 pygmsh_7.1.17-6.debian.tar.xz
Checksums-Sha256:
 9f176ea835560033691557bfa2ec82b27b5654447c204a25fe84a25d286b5c47 2348 
pygmsh_7.1.17-6.dsc
 a987ed73944469fc86d3f23551d0082e34a98974090416dc6220031e738dda94 4368 
pygmsh_7.1.17-6.debian.tar.xz
Files:
 c1c9759e475e17b6aa5ff1e776f9b20c 2348 python optional pygmsh_7.1.17-6.dsc
 08582e46487ffb8d97e13a12f5824b0c 4368 python optional 
pygmsh_7.1.17-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmZxbVwACgkQVz7x5L1a
AfpJ0xAAq0zSoUsA8A7fx3vDfDpasSkiRa42+MVc7UlvLd2qwAUgtKZvuq1ZyxJP
6bf8IFOfpWf6pNxbm9jVmb+yiubLSG7XcCaSlF1y7ggsudml2vp0XDo7U/jEhty4
QmXBa49XOLo4rh37Wkl9je8I3rXQspiUOvt3W12a7d8BihaAti8pSnMma45sNmsh
FJBttjVQcXwGooE5dgf4hnzSp8t0QlajuuDc2dPq0PjI0ep/xywrMEnDNtM/CflH
Zqu1coxRDs7+B1zlkvAH8zEDkIg1orzA/LzwQH+98UXLeomZWkcvF3juh+0fbuqy
MkLrEBVPZMXadOy0ZfEVDKrfGOR1c604pUVuUYFA/U/tNTiEmHBYHIN/cO+WBbu0
Zn4kIvawMugVEsvpw8jIICGtwzi46wsSqSS/ZfDTnxdCIoraEW9GNs9//gkXjx6/
8yGT+auHZC5tdtAlHc5AfovK3FMg4/fSdL7vstihGCLrKnW5qeqg4gRtSBCQQUfv
1KADl4OC6nUa4kbpmz/sYjc1mb90b37PjE7wrgIHWvEsk8zRX1XbYq7W9hxSvm6h
mOxbXOnvKTKPbyBTFDxCFoX9Y96U4lAJAqKQiSuBZQzQbMkzhn5mULmpDm127QHK
vtUhJQ8pN676V880FYZBW71GOALAQNYncHRXPCmSxxThp6uPCMU=
=I6YK
-END PGP SIGNATURE-



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

Bug#1073785: rough fix

[Philip Hands]

Hi,

This patch:

  
https://salsa.debian.org/philh/debootstrap/-/commit/b33d53bd2aad01c9ccf5b66b986ff06f472123cf

when built in this pipeline:

  https://salsa.debian.org/philh/debootstrap/-/pipelines/691006

results in this working test:

  https://openqa.debian.net/tests/273854

I'd imagine that there's more to be done if we want this to work nicely
for downstreams however.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil

Processed: Re: Bug#1073788: gimp: whole-system froze when adjusting threshold

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 sway 1.7-6
Bug #1073788 [gimp] gimp: whole-system froze when adjusting threshold
Bug reassigned from package 'gimp' to 'sway'.
No longer marked as found in versions gimp/2.10.34-1+deb12u2.
Ignoring request to alter fixed versions of bug #1073788 to the same values 
previously set
Bug #1073788 [sway] gimp: whole-system froze when adjusting threshold
Marked as found in versions sway/1.7-6.
> retitle -1 sway: whole system froze when adjusting threshold in gimp
Bug #1073788 [sway] gimp: whole-system froze when adjusting threshold
Changed Bug title to 'sway: whole system froze when adjusting threshold in 
gimp' from 'gimp: whole-system froze when adjusting threshold'.

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

Bug#1073788: gimp: whole-system froze when adjusting threshold

[Simon McVittie]

Control: reassign -1 sway 1.7-6
Control: retitle -1 sway: whole system froze when adjusting threshold in gimp

On Tue, 18 Jun 2024 at 13:13:44 +0200, Manny wrote:
> As soon as the slider is moved, *both* screens on a dual headed
> machine go black for ~1½ seconds then pop back on. GIMP is only ever
> present one of the two displays, never spread out. On one occassion,
> the system froze for a few seconds before the cursor could move
> again. On another occasion, the keyboard and mouse were permanently
> frozen. I walked away from the machine for ~5 minutes or so to give it
> time to unfreeze, but it never unfroze. I was ultimately forced to
> physically force a power down of the whole system. It would have been
> catastrophic if I had unsaved work in any application.

It should not be possible for GIMP to achieve this sort of freeze of
the compositor even if it wanted to, so I'm reassigning this to sway
(I've assumed that you're using the version of sway from Debian 12,
please correct the version metadata if that's wrong).

Please check for messages in the systemd journal at the time of this
freeze - I suspect you will see some sort of warning or error from
sway, Xwayland and/or the kernel.

> There is also a security problem here. In principle, what if a user
> were to leave GIMP to enter a password in another app?  GIMP should
> not have access to the keyboard when it is not in focus. This security
> flaw is not in GIMP, but rather in Wayland or Sway and GIMP is merely
> demonstrating how an unfocused app can eavesdrop on the keystrokes.

If the compositor (in your case that's sway) gives GIMP access to the
keyboard at times when you think it should not have access, then that's
also not a GIMP bug: it's the compositor that controls what information
is available to applications, not the other way around.

smcv

Bug#1064232: rust-axum: Failing autopkgtests

[Jeremy Bícha]

Control: reopen -1

I'm reopening this bug since the autopkgtests are still failing.

https://qa.debian.org/excuses.php?package=rust-axum

Thank you,
Jeremy Bícha

Processed: Re: rust-axum: Failing autopkgtests

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1064232 {Done: Jonas Smedegaard } [src:rust-axum] 
rust-axum: Failing autopkgtests
'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 rust-axum/0.6.20-17.

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

Bug#1072912: marked as done (supermin: /lib64: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 13:35:26 +0200
with message-id <20240618113526.ga3588...@subdivi.de>
and subject line Re: Bug#1072912: supermin: /lib64: No such file or directory
has caused the Debian Bug report #1072912,
regarding supermin: /lib64: No such file or directory
to be marked as done.

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

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


-- 
1072912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libguestfs
Version: 1:1.52.0-6.1
Severity: serious
User: helm...@debian.org
Usertags: dep17
X-Debbugs-CC: helm...@debian.org

The debootstrap set was uploaded, including a new glibc and
base-files. The owner and exact management of /lib64 has changed.

libguestfs tests now fail, possibly indicating it relies on some
intricate details of the /lib64 symlink. Please investigate and
update the source/tests.

https://ci.debian.net/packages/libg/libguestfs/testing/amd64/47493845/

> 3078 233s execl: /init: No such file or directory
[..]
> 3683 233s supermin: debug: listing directory /lib64
> 3684 233s /lib64: No such file or directory

Chris
--- End Message ---
--- Begin Message ---
On Mon, Jun 10, 2024 at 10:54:51AM +0200, Chris Hofstaedtler wrote:
> The debootstrap set was uploaded, including a new glibc and
> base-files. The owner and exact management of /lib64 has changed.
> 
> libguestfs tests now fail, possibly indicating it relies on some
> intricate details of the /lib64 symlink. Please investigate and
> update the source/tests.
> 
> https://ci.debian.net/packages/libg/libguestfs/testing/amd64/47493845/
> 
> > 3078 233s execl: /init: No such file or directory
> [..]
> > 3683 233s supermin: debug: listing directory /lib64
> > 3684 233s /lib64: No such file or directory

Now that the debootstrap package set has migrated to trixie, I ran the
tests locally and looked at ci.debian.net and they succeed in both
cases.

It is very plausible that this was a temporary problem as /lib64 would
go missing when combining an old base-files with a newer glibc or vice
versa. Now that these are all in sync and propagated, stuff seems to
work again.

Thus closing the bug.

Helmut--- End Message ---

Processed: gimp: whole-system froze when adjusting threshold

[Debian Bug Tracking System]

Processing control commands:

> affects -1 sway xwayland
Bug #1073788 [gimp] gimp: whole-system froze when adjusting threshold
Added indication that 1073788 affects sway and xwayland

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

Bug#1073788: gimp: whole-system froze when adjusting threshold

[Manny]

Package: gimp
Version: 2.10.34-1+deb12u2
Severity: critical
Tags: upstream
Justification: breaks the whole system
X-Debbugs-Cc: debbug.g...@sideload.33mail.com
Control: affects -1 sway xwayland

A source document was scanned as a grayscale PNG file. It was loaded
into GIMP, cropped, and followed by a “Layer » Layer to Image Size”
operation. No problems so far (and likely irrelevent - it’s just my
typical workflow FWIW).

Opened “Colors » Threshold…”. Some images have an interesting graph to
help determine where to move the slider and some just have an empty
graph. This may not be related but I noticed that both times spaz’d
out it was when an image had an empty graph (or nearly empty).

As soon as the slider is moved, *both* screens on a dual headed
machine go black for ~1½ seconds then pop back on. GIMP is only ever
present one of the two displays, never spread out. On one occassion,
the system froze for a few seconds before the cursor could move
again. On another occasion, the keyboard and mouse were permanently
frozen. I walked away from the machine for ~5 minutes or so to give it
time to unfreeze, but it never unfroze. I was ultimately forced to
physically force a power down of the whole system. It would have been
catastrophic if I had unsaved work in any application.

GIMP’s tendency to affect other apps also manifests in another way
(though less extreme). When GIMP is full screen on one display and
emacs is full screen on the other display, if I click on a menu like
Colors, leave the menu list open and move the mouse cursor out of GIMP
and onto the emacs window, the emacs window takes focus as expected
but GIMP fights to keep control of the keyboard. When I type a few
keys, the first character appears in the emacs buffer but GIMP seems
to react to all keys pressed when emacs is in focus. Emacs only
receives the first key but GIMP acts on all keys pressed. When this
fight for keyboard control is occurring, both displays go all black
for ~1½ seconds before restoring and the mouse is frozen for a second
or two after that. Sometimes the GIMP popup window (triggered by the
keys pressed in emacs) flickers wildly with different buttons in the
window flickering as well. I click cancel to end the madness. So far
in that case the system goes back to normal. But the behaviour is
similar to when the threshold slider is moved so it appears to be
ultimately associated to the same problem.

This is on Wayland with Sway running.

A similar but different bug was reported here:

  https://gitlab.gnome.org/GNOME/gimp/-/issues/11275

Paulo Crepaldi called it a “crash” not a freeze, and that was on
Windows while my experience was on Debian. These bugs could be related
but possibly not. Without more certainty, I did not tag this bug as
forwarded upstream.

There is also a security problem here. In principle, what if a user
were to leave GIMP to enter a password in another app?  GIMP should
not have access to the keyboard when it is not in focus. This security
flaw is not in GIMP, but rather in Wayland or Sway and GIMP is merely
demonstrating how an unfocused app can eavesdrop on the keystrokes.

The upstream bug tracker blocks registration by pushing a broken
CAPTCHA, so I am unable to report this upstream.

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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.34-1+deb12u2
ii  graphviz 2.42.2-7+b3
ii  libaa1   1.4p5-50
ii  libbabl-0.1-01:0.1.98-1+b1
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.36-9+deb12u7
ii  libcairo21.16.0-7
ii  libfontconfig1   2.14.1-4
ii  libfreetype6 2.12.1+dfsg-5
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgegl-0.4-01:0.4.42-2
ii  libgexiv2-2  0.14.0-1+b1
ii  libgimp2.0   2.10.34-1+deb12u2
ii  libglib2.0-0 2.74.6-2+deb12u2
ii  libgs10  10.0.0~dfsg-11+deb12u3
ii  libgtk2.0-0  2.24.33-2
ii  libgudev-1.0-0   237-2
ii  libharfbuzz0b6.0.0+dfsg-3
ii  libheif1 1.15.1-1
ii  libjpeg62-turbo  1:2.1.5-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libjxl0.70.7.0-10
ii  liblcms2-2   2.14-2
ii  liblzma5 5.4.1-0.2
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.6.0-2
ii  libopenexr-3-1-303.1.5-5
ii  libopenjp2-7 2.5.0-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libpangoft2-1.0-0

Bug#1050805: dhcpcd-base: DoS: zero-length packet cause eventual lease expiration

[Martin-Éric Racine]

su 16. kesäk. 2024 klo 9.05 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> la 15. kesäk. 2024 klo 16.55 Nicolas Cavallari
> (nicolas.cavall...@green-communications.fr) kirjoitti:
> >
> > On 15/06/2024 11:33, Martin-Éric Racine wrote:
> > > On Tue, 29 Aug 2023 13:17:51 +0200 Nicolas Cavallari
> > >> This affects version 9.4.1-22 (stable) and 1:9.4.1-24~deb12u2
> > >> (stable proposed update) but not 1:10.0.2-4 (testing/unstable) as
> > >> upstream fixed it in 10.0.2:
> > >>
> > >> Upstream Bug report: 
> > >> https://github.com/NetworkConfiguration/dhcpcd/issues/179
> > >> Upstream Fix: 
> > >> https://github.com/NetworkConfiguration/dhcpcd/commit/8b29c0ddf026c1c5647c3b8c6cfe21699c4056ae
> > >>
> > >> This patch does not apply cleanly to 9.4.1 because the privsep
> > >> structure changed in 10.0.2.  It's likely that only the src/privsep.c
> > >> hunks about len == 0 and eloop_exit() needs to be backported, the other
> > >> changes are just here to avoid compiler warnings about unused
> > >> parameters.
> > >
> > > Upstream got around releasing a backport of this for branch 9 as
> > > commits 53e2f6de4ba87d0534c89cae674e6c1a48724ef0 and
> > > 6e127eac6903524d401b31893167e4529b8ab111 respectively.
> > >
> > > You are hereby invited to test and report whether this fixes it for 
> > > Stable.
> >
> > I did some quick tests on a VM:
> >
> > First, with 9.4.1-24~deb12u3 as present in debian stable:
>
> > Then I apt sourced dhcpcd, applied the two patches, rebuilt debian
> > packages and tested them.  The situation is now worse:
>
> > I then tested this patch from issue #283:
> >
> > https://github.com/NetworkConfiguration/dhcpcd/commit/727c78f503d456875e2a3cee7609288b537d9d25.patch
> >
> > And this time, it appears to fix the problem:
>
> > I didn't check if there were any adverse effect or if leases are still
> > renewed. I can't check on the production system before Monday.
>
> Please let me know.

Any news on this?

Martin-Éric

Processed: Re: Bug#1073757: firmware-nvidia-tesla-gsp: move aliased files from / to /usr (DEP17)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 src:nvidia-graphics-drivers-tesla should not be released with 
> trixie
Bug #1073757 [firmware-nvidia-tesla-gsp] firmware-nvidia-tesla-gsp: move 
aliased files from / to /usr (DEP17)
Changed Bug title to 'src:nvidia-graphics-drivers-tesla should not be released 
with trixie' from 'firmware-nvidia-tesla-gsp: move aliased files from / to /usr 
(DEP17)'.
> severity -1 serious
Bug #1073757 [firmware-nvidia-tesla-gsp] src:nvidia-graphics-drivers-tesla 
should not be released with trixie
Severity set to 'serious' from 'important'
> tags -1 - patch
Bug #1073757 [firmware-nvidia-tesla-gsp] src:nvidia-graphics-drivers-tesla 
should not be released with trixie
Removed tag(s) patch.

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

Bug#1073785: debootstrap-udeb: removal of trixie --> sid link causes fatal error in D-I

[Philip Hands]

Package: debootstrap-udeb
Version: 1.0.135
Severity: serious
User: debian...@lists.debian.org
Usertags: openqa

While testing daily netinst debian-installer images with openQA, we see that
debootstrap fails:

  https://openqa.debian.net/tests/272866#step/install_base/1

  "The debootstrap program exited with an error (return value 1)"

looking in the syslog, one finds:

  debootstrap: E: NOSCRIPT
  debootsrtap: EA: /usr/share/debootstrap/scripts/trixie
  debootstrap: EF: No such script: %s

If I reinstate the trixie --> sid symlink, the installation can then proceed.

I presume that when removing the "redundant" links in commit 2d3eae91, there was
an intent that the scripting should default to "sid" when the required script is
found to be missing, but this seems not to have been done correctly.

It looks to me as if 73e1b5f9 simply fails to deal with the case where
distro-info is unavailable (debian-installer does not include it).

Cheers, Phil.

Bug#1039883: linux: ext4 corruption with symlinks

[Luis Henriques]

On Fri 14 Jun 2024 05:18:45 PM +01, Luis Henriques wrote;
[...}
>>
>> I can also reproduce this error message using the above script and:
>>
>> - Linux 6.10-rc2
>> - A 2 GiB loopback devic instead of /dev/sdb
>>
>> I bisected this back to:
>>
>> commit 9725958bb75cdfa10f2ec11526fdb23e7485e8e4
>> Author: Xin Yin 
>> Date:   Thu Dec 23 11:23:37 2021 +0800
>>  
>> ext4: fast commit may miss tracking unwritten range during ftruncate
>>
>> It is still possible to cleanly revert that commit from 6.10-rc2, and
>> doing so removes the error message.
>
> Because I recently fixed an issue in the fast commit code[1] I was hoping
> that you were hitting the same bug.  I've executed the reproducer with the
> fix (which hasn't been merged yet) and realised it's definitely a
> different problem.
>
> Debugged the issue a bit, it seems to be related with the fact that
> ext4_fc_write_inode_data() isn't able to cope with the fact that
> 'ei->i_fc_lblk_len' is set to EXT_MAX_BLOCKS.

OK, I've looked into this again.  And something I didn't pay attention
before was that the filesystem was created with both fast_commit *and*
inline_data features.  And after some more debugging, I _think_ the patch
bellow should be the fix for this bug.

If I understand it correctly, when an inode has inlined data it means that
there's no inode data to be written and this case should be handled as if
the inode length was zero.

I'll send out a patch later after running a few more tests just to make
sure it doesn't break something else.  But it would awesome if you could
test it too.

Cheers,
-- 
Luís

diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
index 87c009e0c59a..c56b39a51865 100644
--- a/fs/ext4/fast_commit.c
+++ b/fs/ext4/fast_commit.c
@@ -897,7 +897,7 @@ static int ext4_fc_write_inode_data(struct inode *inode, 
u32 *crc)
int ret;
 
mutex_lock(>i_fc_lock);
-   if (ei->i_fc_lblk_len == 0) {
+   if ((ei->i_fc_lblk_len == 0) || (ext4_has_inline_data(inode))) {
mutex_unlock(>i_fc_lock);
return 0;
}

Processed: Re: update dep17 bug metadata

[Debian Bug Tracking System]

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

> # restore found/fixed from earlier reassign
> found 1054084 crowdsec/1.4.6-6
Bug #1054084 [crowdsec] let dh_installsystemd choose the location of systemd 
units
Marked as found in versions crowdsec/1.4.6-6.
> found 1054086 lsm/1.0.4-2
Bug #1054086 [lsm] lsm: let dh_installsystemd choose the location of units
Marked as found in versions lsm/1.0.4-2.
> found 1054480 dogtag-pki/11.2.1-2
Bug #1054480 [pki-server] dogtag-pki: installs a systemd unit twice once 
dh_installsystemd installs to /usr
Marked as found in versions dogtag-pki/11.2.1-2.
> found 1057803 libfli/2.0+20221221182632-1
Bug #1057803 [libfli2] libfli: delegate placement of udev files to pkg-config 
data
Marked as found in versions libfli/2.0+20221221182632-1.
> found 1057900 apcupsd/3.14.14-3.1
Bug #1057900 {Done: Thorsten Alteholz } [apcupsd] apcupsd: 
move files from / to /usr
Marked as found in versions apcupsd/3.14.14-3.1 and reopened.
> fixed 1057900 apcupsd/3.14.14-4
Bug #1057900 [apcupsd] apcupsd: move files from / to /usr
Marked as fixed in versions apcupsd/3.14.14-4.
> found 1058764 opendmarc/1.4.2-4
Bug #1058764 [opendmarc] opendmarc: installs deprecated 
/lib/opendmarc/opendmarc.service.generate
Marked as found in versions opendmarc/1.4.2-4.
> found 1058840 libplayerone/3.1.0+20221218103507-1
Bug #1058840 [libplayeronecamera2] libplayerone: use udev.pc to place udev rules
Marked as found in versions libplayerone/3.1.0+20221218103507-1.
> found 1058844 libinovasdk/1.3.6-3
Bug #1058844 [libinovasdk1] libinovasdk: use udev.pc to place udev rules
Marked as found in versions libinovasdk/1.3.6-3.
> found 1059371 snoopy/2.5.1-1
Bug #1059371 [snoopy] snoopy: installs library into /lib
Marked as found in versions snoopy/2.5.1-1.
> found 1060195 hfsprogs/540.1.linux3-5
Bug #1060195 [hfsprogs] hfsprogs: install files into /usr (DEP17)
Marked as found in versions hfsprogs/540.1.linux3-5.
> found 1061245 cups/2.4.7-1
Bug #1061245 [cups-daemon] cups: install systemd units into /usr
Marked as found in versions cups/2.4.7-1.
> found 1061332 cifs-utils/2:7.0-2
Bug #1061332 [cifs-utils] cifs-utils: install files into /usr
Marked as found in versions cifs-utils/2:7.0-2.
> found 1061527 elogind/252.9-1debian3
Bug #1061527 [libelogind0] elogind: install files into /usr
Marked as found in versions elogind/252.9-1debian3.
> found 1064126 libvirt/10.0.0-2
Bug #1064126 [libnss-libvirt,libvirt-daemon-system] libvirt: install NSS 
modules and systemd units into /usr
Marked as found in versions libvirt/10.0.0-2.
> # really close, found/fixed added earlier
> close 1064887
Bug #1064887 {Done: Helmut Grohne } [src:dash] dash: move 
files to /usr for DEP17
Bug 1064887 is already marked as done; not doing anything.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1054084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054084
1054086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054086
1054480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054480
1057803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057803
1057900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057900
1058764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058764
1058840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058840
1058844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058844
1059371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059371
1060195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060195
1061245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061245
1061332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061332
1061527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061527
1064126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064126
1064887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1073317: marked as done (pd-lyonpotpourri: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 09:35:17 +
with message-id 
and subject line Bug#1073317: fixed in pd-lyonpotpourri 3.0.1-5
has caused the Debian Bug report #1073317,
regarding pd-lyonpotpourri: FTBFS: m_pd.h:85:26: error: static assertion 
failed: "field must be t_float!"
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.)


-- 
1073317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-lyonpotpourri
Version: 3.0.1-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC  -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 -o distortion~.linux-amd64-64.so.o -c 
> distortion~.c
>  info: making rtrig~.linux-amd64-64.so.o in lib lyonpotpourri
> In file included from MSPd.h:31,
>  from distortion~.c:1:
> distortion~.c: In function ‘distortion_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> distortion~.c:35:3: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>35 |   CLASS_MAINSIGNALIN(distortion_class, t_distortion, x_f);
>   |   ^~
> distortion~.c: In function ‘distortion1_perform’:
> distortion~.c:72:15: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>72 |   float *in = (t_float *)(w[2]);
>   |   ^
> distortion~.c:73:16: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>73 |   float *out = (t_float *)(w[5]);
>   |^
> distortion~.c: In function ‘distortion2_perform’:
> distortion~.c:113:15: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>   113 |   float *in = (t_float *)(w[2]);
>   |   ^
> distortion~.c:114:18: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>   114 |   float *data1 = (t_float *)(w[3]);
>   |  ^
> distortion~.c:115:18: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>   115 |   float *data2 = (t_float *)(w[4]);
>   |  ^
> distortion~.c:116:16: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>   116 |   float *out = (t_float *)(w[5]);
>   |^
> distortion~.c: In function ‘distortion3_perform’:
> distortion~.c:165:15: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>   165 |   float *in = (t_float *)(w[2]);
>   |   ^
> distortion~.c:166:18: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>   166 |   float *data1 = (t_float *)(w[3]);
>   |  ^
> distortion~.c:167:18: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>   167 |   float *data2 = (t_float *)(w[4]);
>   |  ^
> distortion~.c:168:16: warning: initialization of ‘float *’ from incompatible 
> pointer type ‘t_float *’ {aka ‘double *’} [-Wincompatible-pointer-types]
>   168 |   float *out = (t_float *)(w[5]);
>   |^
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> distortion~.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-lyonpotpourri_3.0.1-4_unstable.log

All bugs filed during this archive rebuild 

Bug#1073336: marked as done (pd-fftease: FTBFS: m_pd.h:85:26: error: static assertion failed: "field must be t_float!")

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 09:19:52 +
with message-id 
and subject line Bug#1073336: fixed in pd-fftease 3.0.1-7
has caused the Debian Bug report #1073336,
regarding pd-fftease: FTBFS: m_pd.h:85:26: error: static assertion failed: 
"field must be t_float!"
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.)


-- 
1073336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-fftease
Version: 3.0.1-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -DPD -I "/usr/include/pd" -DPD_FLOATSIZE=64 -DUNIX -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC  -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 -o scrape~.linux-amd64-64.so.o -c 
> scrape~.c
>  info: making burrow~.linux-amd64-64.so.o in lib fftease
> In file included from fftease.h:8,
>  from dentist~.c:3:
> dentist~.c: In function ‘dentist_tilde_setup’:
> /usr/include/pd/m_pd.h:85:26: error: static assertion failed: "field must be 
> t_float!"
>85 | #define PD_STATIC_ASSERT _Static_assert
>   |  ^~
> /usr/include/pd/m_pd.h:575:5: note: in expansion of macro ‘PD_STATIC_ASSERT’
>   575 | PD_STATIC_ASSERT(sizeof(((type *)NULL)->field) == 
> sizeof(t_float), "field must be t_float!"); \
>   | ^~~~
> dentist~.c:63:5: note: in expansion of macro ‘CLASS_MAINSIGNALIN’
>63 | CLASS_MAINSIGNALIN(c, t_dentist, x_f);
>   | ^~
> make[1]: *** [/usr/share/pd-lib-builder//Makefile.pdlibbuilder:987: 
> dentist~.linux-amd64-64.so.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/pd-fftease_3.0.1-6_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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: pd-fftease
Source-Version: 3.0.1-7
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-fftease 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: Tue, 18 Jun 2024 11:03:55 +0200
Source: pd-fftease
Architecture: source
Version: 3.0.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1073336
Changes:
 pd-fftease (3.0.1-7) unstable; urgency=medium
 .
   * Patch to fix compilation with Pd64 (Closes: #1073336)
   * Add puredata:Recommends and puredata:Provides
   * Switch to dh-sequence-puredata
   * Bump standards version to 4.7.0
Checksums-Sha1:
 ac17050901938d01267ffd990bd143c2fd441038 2138 pd-fftease_3.0.1-7.dsc
 78afb4fd901cc423e9b73146d8c675996078e1c5 15512 pd-fftease_3.0.1-7.debian.tar.xz
Checksums-Sha256:
 a4a389088136eb666ce370c5a6c819d66af714e2c5d358bd3f1c80c8f6d88120 2138 
pd-fftease_3.0.1-7.dsc
 ce110c1bf725d3bfdcf379df5c941a5679c6ecf3631e43b5511e0065064e8d3e 15512 
pd-fftease_3.0.1-7.debian.tar.xz
Files:
 af1eee926f188c074da1d3bf4010bc8e 

Processed (with 1 error): update dep17 bug metadata

[Debian Bug Tracking System]

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

> # assign from source to binary
> reassign 1051460 crowdsec-custom-bouncer
Bug #1051460 [src:crowdsec-custom-bouncer] crowdsec-custom-bouncer: move 
systemd units to /usr
Bug reassigned from package 'src:crowdsec-custom-bouncer' to 
'crowdsec-custom-bouncer'.
No longer marked as found in versions crowdsec-custom-bouncer/0.0.15-3.
Ignoring request to alter fixed versions of bug #1051460 to the same values 
previously set
> reassign 1054084 crowdsec
Bug #1054084 [src:crowdsec] let dh_installsystemd choose the location of 
systemd units
Bug reassigned from package 'src:crowdsec' to 'crowdsec'.
No longer marked as found in versions crowdsec/1.4.6-6.
Ignoring request to alter fixed versions of bug #1054084 to the same values 
previously set
> reassign 1054086 lsm
Bug #1054086 [src:lsm] lsm: let dh_installsystemd choose the location of units
Bug reassigned from package 'src:lsm' to 'lsm'.
No longer marked as found in versions lsm/1.0.4-2.
Ignoring request to alter fixed versions of bug #1054086 to the same values 
previously set
> reassign 1054480 pki-server
Bug #1054480 [src:dogtag-pki] dogtag-pki: installs a systemd unit twice once 
dh_installsystemd installs to /usr
Bug reassigned from package 'src:dogtag-pki' to 'pki-server'.
No longer marked as found in versions dogtag-pki/11.2.1-2.
Ignoring request to alter fixed versions of bug #1054480 to the same values 
previously set
> reassign 1057803 libfli2
Bug #1057803 [src:libfli] libfli: delegate placement of udev files to 
pkg-config data
Bug reassigned from package 'src:libfli' to 'libfli2'.
No longer marked as found in versions libfli/2.0+20221221182632-1.
Ignoring request to alter fixed versions of bug #1057803 to the same values 
previously set
> reassign 1057900 apcupsd
Bug #1057900 {Done: Thorsten Alteholz } [src:apcupsd] 
apcupsd: move files from / to /usr
Bug reassigned from package 'src:apcupsd' to 'apcupsd'.
No longer marked as found in versions apcupsd/3.14.14-3.1.
No longer marked as fixed in versions apcupsd/3.14.14-4.
> reassign 1058764 opendmarc
Bug #1058764 [src:opendmarc] opendmarc: installs deprecated 
/lib/opendmarc/opendmarc.service.generate
Bug reassigned from package 'src:opendmarc' to 'opendmarc'.
No longer marked as found in versions opendmarc/1.4.2-4.
Ignoring request to alter fixed versions of bug #1058764 to the same values 
previously set
> reassign 1058840 libplayeronecamera2
Bug #1058840 [src:libplayerone] libplayerone: use udev.pc to place udev rules
Bug reassigned from package 'src:libplayerone' to 'libplayeronecamera2'.
No longer marked as found in versions libplayerone/3.1.0+20221218103507-1.
Ignoring request to alter fixed versions of bug #1058840 to the same values 
previously set
> reassign 1058844 libinovasdk1
Bug #1058844 [src:libinovasdk] libinovasdk: use udev.pc to place udev rules
Bug reassigned from package 'src:libinovasdk' to 'libinovasdk1'.
No longer marked as found in versions libinovasdk/1.3.6-3.
Ignoring request to alter fixed versions of bug #1058844 to the same values 
previously set
> reassign 1059371 snoopy
Bug #1059371 [src:snoopy] snoopy: installs library into /lib
Bug reassigned from package 'src:snoopy' to 'snoopy'.
No longer marked as found in versions snoopy/2.5.1-1.
Ignoring request to alter fixed versions of bug #1059371 to the same values 
previously set
> reassign 1060195 hfsprogs
Bug #1060195 [src:hfsprogs] hfsprogs: install files into /usr (DEP17)
Bug reassigned from package 'src:hfsprogs' to 'hfsprogs'.
No longer marked as found in versions hfsprogs/540.1.linux3-5.
Ignoring request to alter fixed versions of bug #1060195 to the same values 
previously set
> reassign 1061245 cups-daemon
Bug #1061245 [src:cups] cups: install systemd units into /usr
Bug reassigned from package 'src:cups' to 'cups-daemon'.
No longer marked as found in versions cups/2.4.7-1.
Ignoring request to alter fixed versions of bug #1061245 to the same values 
previously set
> reassign 1061332 cifs-utils
Bug #1061332 [src:cifs-utils] cifs-utils: install files into /usr
Bug reassigned from package 'src:cifs-utils' to 'cifs-utils'.
No longer marked as found in versions cifs-utils/2:7.0-2.
Ignoring request to alter fixed versions of bug #1061332 to the same values 
previously set
> reassign 1061527 libelogind0
Bug #1061527 [src:elogind] elogind: install files into /usr
Bug reassigned from package 'src:elogind' to 'libelogind0'.
No longer marked as found in versions elogind/252.9-1debian3.
Ignoring request to alter fixed versions of bug #1061527 to the same values 
previously set
> reassign 1064126 libnss-libvirt,libvirt-daemon-system
Bug #1064126 [src:libvirt] libvirt: install NSS modules and systemd units into 
/usr
Bug reassigned from package 'src:libvirt' to 
'libnss-libvirt,libvirt-daemon-system'.
No longer marked as found in versions libvirt/10.0.0-2.
Ignoring request to alter fixed versions of bug #1064126 to the same values 
previously set
> # bump to important as 

Bug#1073269: marked as done (FTBFS in unstable with Error: Unbound type constructor Result.result)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 09:04:01 +
with message-id 
and subject line Bug#1073269: fixed in coq-serapi 8.19.0+0.19.3-3
has caused the Debian Bug report #1073269,
regarding FTBFS in unstable with Error: Unbound type constructor Result.result
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.)


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

Hi,

coq-serapi FTBFS in unstable with the following error:

/usr/bin/make build
make[2]: Entering directory '/<>'
dune build --root . --only-packages=coq-serapi @install
File "serlib/ser_constrexpr.mli", line 106, characters 85-98:
106 | val with_declaration_ast_of_yojson : Yojson.Safe.t -> 
(with_declaration_ast, string) Result.result

   ^
Error: Unbound type constructor Result.result
File "serlib/ser_feedback.mli", line 25, characters 57-70:
25 | val doc_id_of_yojson : Yojson.Safe.t -> (doc_id, string) Result.result
  ^
Error: Unbound type constructor Result.result
File "serlib/ser_goptions.mli", line 31, characters 69-82:
31 | val option_value_of_yojson : Yojson.Safe.t -> (option_value, string) 
Result.result
  
^
Error: Unbound type constructor Result.result
File "serlib/ser_genredexpr.mli", line 30, characters 61-74:
30 | val glob_red_flag_of_yojson : (Yojson.Safe.t -> ('a, string) 
Result.result) -> Yojson.Safe.t -> ('a glob_red_flag,
 string) Result.result
  ^
Error: Unbound type constructor Result.result
File "serlib/ser_glob_term.mli", line 34, characters 63-76:
34 | val glob_sort_of_yojson : Yojson.Safe.t -> (glob_sort, string) 
Result.result

^
Error: Unbound type constructor Result.result
File "serlib/ser_pp.mli", line 26, characters 45-58:
26 | val of_yojson : Yojson.Safe.t -> (t, string) Result.result
  ^
Error: Unbound type constructor Result.result
File "serlib/ser_xml_datatype.mli", line 25, characters 52-65:
25 | val gxml_of_yojson : (Yojson.Safe.t -> ('a, string) Result.result) -> 
Yojson.Safe.t -> ('a gxml, string) Result.re
sult
 ^
Error: Unbound type constructor Result.result
File "serlib/ser_dAst.ml", line 34, characters 62-75:
34 | let thunk_of_yojson : type a b. (Yojson.Safe.t -> (a, string) 
Result.result) -> (Yojson.Safe.t -> (b, string) Resu
lt.result) -> Yojson.Safe.t -> ((a,b) thunk, string) Result.result =
   ^
Error: Unbound type constructor Result.result


Full build log attached.

Thanks!

cheers, josch
sbuild (Debian sbuild) 0.85.0 (04 January 2023) on salat

+==+
| coq-serapi (amd64)   Sat, 15 Jun 2024 12:28:25 + |
+==+

Package: coq-serapi
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

Unpacking /home/josch/.cache/sbuild/unstable-amd64.tar to 
/tmp/tmp.sbuild.K1Xrqr4TDO...
I: NOTICE: Log filtering will replace 'sbuild-unshare-dummy-location' with 
'<>'
I: NOTICE: Log filtering will replace 'build/coq-serapi-MOPvT6/resolver-iw1YuS' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://deb.debian.org/debian unstable InRelease [198 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 Packages [9934 kB]
Fetched 10.1 MB in 1s (9112 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch 

Bug#1073336: marked as pending in pd-fftease

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

Bug #1073336 in pd-fftease 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/multimedia-team/pd/pd-fftease/-/commit/ba9d95c082f1801622f424b20cef3c3b13a53c4b


Patch to fix compilation with Pd64

Closes: #1073336


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073336

Processed: Bug#1073336 marked as pending in pd-fftease

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073336 [src:pd-fftease] pd-fftease: FTBFS: m_pd.h:85:26: error: static 
assertion failed: "field must be t_float!"
Added tag(s) pending.

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

Bug#1073310: marked as done (vulkan-tools: FTBFS: vulkan_hpp_macros.hpp:135:38: error: operator '==' has no left operand)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 07:50:22 +
with message-id 
and subject line Bug#1073310: fixed in vulkan-tools 1.3.283.0+dfsg1-1
has caused the Debian Bug report #1073310,
regarding vulkan-tools: FTBFS: vulkan_hpp_macros.hpp:135:38: error: operator 
'==' has no left operand
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.)


-- 
1073310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vulkan-tools
Version: 1.3.280.0+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<>/build/cube && /usr/bin/cc -DVK_NO_PROTOTYPES 
> -DVK_USE_PLATFORM_WAYLAND_KHR -I/<>/build/cube 
> -I/<>/cube/. -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -fPIE -fvisibility=hidden -Wall 
> -Wextra -Wno-unused-parameter -Wno-missing-field-initializers 
> -Wno-stringop-truncation -MD -MT 
> cube/CMakeFiles/vkcube-wayland.dir/xdg-shell-code.c.o -MF 
> CMakeFiles/vkcube-wayland.dir/xdg-shell-code.c.o.d -o 
> CMakeFiles/vkcube-wayland.dir/xdg-shell-code.c.o -c 
> /<>/build/cube/xdg-shell-code.c
> In file included from /usr/include/vulkan/vulkan.hpp:16,
>  from /<>/cube/cube.cpp:44:
> /usr/include/vulkan/vulkan_hpp_macros.hpp:135:38: error: operator '==' has no 
> left operand
>   135 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> In file included from /usr/include/vulkan/vulkan.hpp:8690:
> /usr/include/vulkan/vulkan_handles.hpp:2416:38: error: operator '==' has no 
> left operand
>  2416 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:2514:38: error: operator '==' has no 
> left operand
>  2514 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:2612:38: error: operator '==' has no 
> left operand
>  2612 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:2701:38: error: operator '==' has no 
> left operand
>  2701 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:2796:38: error: operator '==' has no 
> left operand
>  2796 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:2891:38: error: operator '==' has no 
> left operand
>  2891 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:2986:38: error: operator '==' has no 
> left operand
>  2986 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:3084:38: error: operator '==' has no 
> left operand
>  3084 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:3173:38: error: operator '==' has no 
> left operand
>  3173 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:3268:38: error: operator '==' has no 
> left operand
>  3268 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:3363:38: error: operator '==' has no 
> left operand
>  3363 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:3458:38: error: operator '==' has no 
> left operand
>  3458 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:3553:38: error: operator '==' has no 
> left operand
>  3553 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> /usr/include/vulkan/vulkan_handles.hpp:3648:38: error: operator '==' has no 
> left operand
>  3648 | #if ( VULKAN_HPP_TYPESAFE_CONVERSION == 1 )
>   |  ^~
> 

Bug#1073595: Missing symbols in the library file compared to the headers

[julien . puydt]

Package: libuv1t64
Version: 1.48.0-4
Severity: serious
Affects: ocaml-luv

While updating the ocaml-luv package, I stumbled upon missing symbols
for uv_wtf8_length_as_utf16, uv_wtf8_to_utf16, uv_utf16_length_as_wtf8
and  uv_utf16_to_wtf8.

After some poking around, they are declared in /usr/include/uv.h, but
using objdump -T on /usr/lib/x86_64-linux-gnu/libuv.so.1.0.0 doesn't
show them.

So it looks like there's something wrong with the libuv1t64 package.

Cheers,

J.Puydt

Processed: (No Subject)

[Debian Bug Tracking System]

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

> fixed 1069199 5.8.2-1
Bug #1069199 [src:kamailio] kamailio: FTBFS: 
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less 
than C++14 are not supported."
The source 'kamailio' and version '5.8.2-1' do not appear to match any binary 
packages
Marked as fixed in versions kamailio/5.8.2-1.
> --
Stopping processing here.

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

Bug#1073479: marked as done (gdcm: FTBFS: make[1]: *** [debian/rules:108: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 06:49:10 +
with message-id 
and subject line Bug#1072822: fixed in gdcm 3.0.24-2
has caused the Debian Bug report #1072822,
regarding gdcm: FTBFS: make[1]: *** [debian/rules:108: 
override_dh_auto_configure] Error 2
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.)


-- 
1072822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdcm
Version: 3.0.24-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 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_configure -- -DGDCM_WRAP_JAVA:BOOL=ON -DVTKGDCM_WRAP_JAVA:BOOL=ON 
> -DGDCM_DEFAULT_JAVA_VERSION:STRING=1.8 -DCMAKE_SKIP_RPATH=ON 
> -DCMAKE_BUILD_TYPE:STRING=None -DGDCM_DOXYGEN_NO_FOOTER:BOOL=ON 
> -DGDCM_BUILD_APPLICATIONS:BOOL=ON -DGDCM_DOCUMENTATION:BOOL=ON 
> -DGDCM_VTK_DOCUMENTATION:BOOL=OFF 
> -DDOCUMENTATION_DOWNLOAD_VTK_TAGFILE:BOOL=OFF 
> -DGDCM_PDF_DOCUMENTATION:BOOL=ON -DGDCM_BUILD_SHARED_LIBS:BOOL=ON 
> -DGDCM_WRAP_PYTHON:BOOL=ON -DVTKGDCM_WRAP_PYTHON:BOOL=ON 
> -DVTKGDCM_WRAP_JAVA:BOOL=OFF -DGDCM_WRAP_CSHARP:BOOL=1 
> -DGDCM_WRAP_PHP:BOOL=OFF -DGDCM_USE_PVRG:BOOL=ON 
> -DGDCM_USE_SYSTEM_PVRG:BOOL=ON -DGMCS_EXECUTABLE:FILEPATH=/usr/bin/mono-csc 
> -DEXPAT_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libexpat.so 
> -DGDCM_BUILD_TESTING:BOOL=OFF -DGDCM_USE_SYSTEM_EXPAT:BOOL=ON 
> -DGDCM_USE_SYSTEM_UUID:BOOL=ON -DGDCM_USE_SYSTEM_ZLIB:BOOL=ON 
> -DGDCM_USE_SYSTEM_OPENJPEG:BOOL=ON -DGDCM_USE_SYSTEM_OPENSSL:BOOL=ON 
> -DGDCM_USE_SYSTEM_CHARLS:BOOL=ON -DGDCM_USE_SYSTEM_POPPLER:BOOL=ON 
> -DGDCM_USE_SYSTEM_LIBXML2:BOOL=ON -DGDCM_USE_SYSTEM_JSON:BOOL=ON 
> -DGDCM_USE_PARAVIEW:BOOL=OFF -DGDCM_USE_ACTIVIZ:BOOL=OFF 
> -DGDCM_USE_SYSTEM_PAPYRUS3:BOOL=ON -DGDCM_USE_SYSTEM_SOCKETXX:BOOL=ON 
> -DPython_ADDITIONAL_VERSIONS:STRING=3.11 
> -DGDCM_INSTALL_DOC_DIR:STRING=share/doc/gdcm-doc 
> -DTAGFILES:STRING="/usr/share/doc/vtk-doc/html/vtk9.3.tag=/usr/share/doc/vtk-doc/html/"
>  -DGDCM_INSTALL_PYTHONMODULE_DIR:STRING=lib/python/dist-packages 
> -DGDCM_INSTALL_JAVAMODULE_DIR:STRING=lib/x86_64-linux-gnu/jni 
> -DGDCM_NO_PYTHON_LIBS_LINKING:BOOL=ON -DGDCM_NO_VTKJAVA_LIBS_LINKING:BOOL=ON 
> -DGDCM_INSTALL_LIB_DIR:STRING=lib/x86_64-linux-gnu -DGDCM_USE_VTK:BOOL=ON 
> -DVTK_JAVA_JAR=/usr/share/java/vtk9.jar
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -GNinja -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DGDCM_WRAP_JAVA:BOOL=ON 
> -DVTKGDCM_WRAP_JAVA:BOOL=ON -DGDCM_DEFAULT_JAVA_VERSION:STRING=1.8 
> -DCMAKE_SKIP_RPATH=ON -DCMAKE_BUILD_TYPE:STRING=None 
> -DGDCM_DOXYGEN_NO_FOOTER:BOOL=ON -DGDCM_BUILD_APPLICATIONS:BOOL=ON 
> -DGDCM_DOCUMENTATION:BOOL=ON -DGDCM_VTK_DOCUMENTATION:BOOL=OFF 
> -DDOCUMENTATION_DOWNLOAD_VTK_TAGFILE:BOOL=OFF 
> -DGDCM_PDF_DOCUMENTATION:BOOL=ON -DGDCM_BUILD_SHARED_LIBS:BOOL=ON 
> -DGDCM_WRAP_PYTHON:BOOL=ON -DVTKGDCM_WRAP_PYTHON:BOOL=ON 
> -DVTKGDCM_WRAP_JAVA:BOOL=OFF -DGDCM_WRAP_CSHARP:BOOL=1 
> -DGDCM_WRAP_PHP:BOOL=OFF -DGDCM_USE_PVRG:BOOL=ON 
> -DGDCM_USE_SYSTEM_PVRG:BOOL=ON -DGMCS_EXECUTABLE:FILEPATH=/usr/bin/mono-csc 
> -DEXPAT_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libexpat.so 
> -DGDCM_BUILD_TESTING:BOOL=OFF -DGDCM_USE_SYSTEM_EXPAT:BOOL=ON 
> -DGDCM_USE_SYSTEM_UUID:BOOL=ON -DGDCM_USE_SYSTEM_ZLIB:BOOL=ON 
> -DGDCM_USE_SYSTEM_OPENJPEG:BOOL=ON -DGDCM_USE_SYSTEM_OPENSSL:BOOL=ON 
> -DGDCM_USE_SYSTEM_CHARLS:BOOL=ON -DGDCM_USE_SYSTEM_POPPLER:BOOL=ON 
> -DGDCM_USE_SYSTEM_LIBXML2:BOOL=ON -DGDCM_USE_SYSTEM_JSON:BOOL=ON 
> -DGDCM_USE_PARAVIEW:BOOL=OFF -DGDCM_USE_ACTIVIZ:BOOL=OFF 
> -DGDCM_USE_SYSTEM_PAPYRUS3:BOOL=ON -DGDCM_USE_SYSTEM_SOCKETXX:BOOL=ON 
> -DPython_ADDITIONAL_VERSIONS:STRING=3.11 
> -DGDCM_INSTALL_DOC_DIR:STRING=share/doc/gdcm-doc 
> -DTAGFILES:STRING=/usr/share/doc/vtk-doc/html/vtk9.3.tag=/usr/share/doc/vtk-doc/html/
>  -DGDCM_INSTALL_PYTHONMODULE_DIR:STRING=lib/python/dist-packages 
> -DGDCM_INSTALL_JAVAMODULE_DIR:STRING=lib/x86_64-linux-gnu/jni 
> -DGDCM_NO_PYTHON_LIBS_LINKING:BOOL=ON -DGDCM_NO_VTKJAVA_LIBS_LINKING:BOOL=ON 

Bug#1072822: marked as done (gdcm FTBFS with VTK 9.3.0)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jun 2024 06:49:10 +
with message-id 
and subject line Bug#1072822: fixed in gdcm 3.0.24-2
has caused the Debian Bug report #1072822,
regarding gdcm FTBFS with VTK 9.3.0
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=gdcm=amd64=3.0.24-1%2Bb2=1717845766=0

...
-- Building Utilities/VTK as a VTK 9 Module
CMake Error at /usr/lib/x86_64-linux-gnu/cmake/vtk-9.3/vtkModule.cmake:2121 
(message):
  The `SPDX_DESTINATION` must not be an absolute path.  Use
  `CMAKE_INSTALL_PREFIX` to keep everything in a single installation prefix.
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/vtk-9.3/vtkModule.cmake:2667 
(_vtk_module_check_destinations)
  CMakeLists.txt:696 (vtk_module_build)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: gdcm
Source-Version: 3.0.24-2
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated gdcm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jun 2024 08:28:12 +0200
Source: gdcm
Architecture: source
Version: 3.0.24-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Mathieu Malaterre 
Closes: 1072822
Changes:
 gdcm (3.0.24-2) unstable; urgency=medium
 .
   [ Adrien Nader ]
   * Team upload.
   * d/patches: gdcm FTBFS with VTK 9.3.0. Closes: #1072822
 .
   [ Mathieu Malaterre ]
   * d/control: Bump Std-Vers to 4.7.0 no changes needed
Checksums-Sha1:
 40ac7176902ca043c386cf65e98e8edfa7fcf998 3611 gdcm_3.0.24-2.dsc
 0668ab6d5900760ca20a2f30302814c00c5a1f5b 279784 gdcm_3.0.24-2.debian.tar.xz
 3a16e3dfffbfcd68658e5700b7c7ab20de024f4f 37152 gdcm_3.0.24-2_source.buildinfo
Checksums-Sha256:
 2f5cf80319c32334b36caafa0f10d9379aa0d3a6d1844eb4f462886a84f6b638 3611 
gdcm_3.0.24-2.dsc
 6e7088810b6fa95fc93b43d96ee362e06c607bd5528f918cb09994f0047d51ac 279784 
gdcm_3.0.24-2.debian.tar.xz
 baa7ec6a05980c3c76e130a4dfbfa5a109f5967288f5841289a057a95aa72787 37152 
gdcm_3.0.24-2_source.buildinfo
Files:
 63e322277835d4bc4320db9158a311d2 3611 libs optional gdcm_3.0.24-2.dsc
 df82905fdf4c46387ab170f22fd4f828 279784 libs optional 
gdcm_3.0.24-2.debian.tar.xz
 dffdcfab374e3dc43350f0a1d2a8217e 37152 libs optional 
gdcm_3.0.24-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmZxKZcRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0VCMA//cGTj9D6to1HtPOA7OOuGXAILBOCmNgvx
974+HIcmJgKmYEOhiJ+3aCbgY8XrtTlrviZM09qWIABOaBPUb4cRi7BlVC2zHGJ9
++x7AnupNfZX6/aLukx4HKkEqeFVE/xx3ZZV3nkSvDc3IOIMYF3fl8LgbLnrCNtx
tbSzEXrGKPFDlY+xA7a+XRZ8/NlS5qyfR2/sqY0k0+vp/L92TeaFgKgVnaAg+fMa
zTaFw4AUWYanvgIN4JXPCoqQ9z+18pjrMS+06L22pV1vZXaalmi4mz+ux2bxiVuC
mnc16HliAj2sppebqQXlYOkbY0Noduv4Ohhm9NSWEseIg0X7zG0jvmMQbiSDgP54
OwDvWceF7JHwSho4FZXgJeEqwPayYhzCTnhoToidzItXP4vQOozh8m3HLWL203Ym
nGvcunctnzbeAwxqJ2htWi7BR+Bb/fyN+kMRF0AOQsMSs9B2I2eYFNe/j0j8XfU0
iYj/aJQ+S6Yq+ao/PAd+uu8Eiz4JnlZNYXaDb3WAaAcJOuWEcDYq6adu0KI62aLJ
aUuQZQxeYcGC4ePY4j8KR6N1+8P1zXQmfUpLbFupSgHlAIwUBhvfH7vJpNwhmk1V
AUE5inIGq3CslHKUwbjVyTff+jp88QMBNaflmPwvMqFqbBkodpFWktR6H+H3VWpJ
Dp0ZqhrZdU4=
=Z2QM
-END PGP SIGNATURE-



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

Bug#1072822: marked as pending in gdcm

[Mathieu Malaterre]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/gdcm/-/commit/f923088d30f69598e1476f4fe7139e64b41ec8f2


d/patches: gdcm FTBFS with VTK 9.3.0. Closes: #1072822


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1072822

Processed: Bug#1072822 marked as pending in gdcm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1072822 [src:gdcm] gdcm FTBFS with VTK 9.3.0
Bug #1073479 [src:gdcm] gdcm: FTBFS: make[1]: *** [debian/rules:108: 
override_dh_auto_configure] Error 2
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1073014: dhcpcd: flaky autopkgtest: Obtaining network configuration for veth1 via dhcp... timed out

[Martin-Éric Racine]

to 13. kesäk. 2024 klo 11.52 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> Adding the dnsmasq maintainer in CC.
>
> to 13. kesäk. 2024 klo 11.39 Paul Gevers (elb...@debian.org) kirjoitti:
> > On 13-06-2024 3:36 a.m., Martin-Éric Racine wrote:
> > > Subsequent ones randomly timeout waiting for an IP from the DHCP
> > > server. This could well be an issue with dnsmasq, which is what we use
> > > for the test. Alternately, it could be caused by those constant fails
> > > on glibc. Without more detailed logs, I am not in a position to
> > > investigate this. Help is welcome.
> >
> > Well, I can't give you more logs than what your test writes. So that's
> > in your hands, I suggest you try and make the test more verbose of
> > what's going on, or maybe ensure some logs end up in the artifacts for
> > inspection. Also, if dnsmasq is the problem, you might want to contact
> > the maintainer and discuss the issue (e.g. in a bug report). From my
> > standpoint, it's the autopkgtest of dhcpcd that's having issues and that
> > *is* an issue for src:dhcpcd. You could reassign this bug and mark it
> > "affects dhcpcd".
>
> I'm curious to hear whether any of what appears in the log rings any
> bell for Simon.
>
> > I acknowledge that something fishy seems to be ongoing in the archive
> > when new version of src:glibc binaries appear (not only with dhcpcd I
> > mean). For now I'll not hold that against autopkgtest failures of
> > packages too much.
>
> Which is where I suspect the real issue is.
>
> Personally, I already find it suspicious that the tracker tells me
> about unrelated packages' transitions or issues. If the problem is in
> someone else's code, while mine hasn't changed in ages, that's where
> the bug report needs to go. In this case, dhcpcd's autopkgtest hasn't
> changed in ages, and has been verified to work as-is at Ubuntu, where
> isolation machines were implemented a long time before Debian.

Sorry Paul but, at this point, I'm gonna call CI itself flaky.

Right now, CI hasn't even registered any test attemps for recent
uploads to Unstable and its results for Testing out of sync. Given
this, if you're gonna start mass-filing bugs against any package whose
test reults show discrepancy, first make sure that, in fact, your code
is not the one causing others unnecesary work.

Martin-Éric

Processed: your mail

[Debian Bug Tracking System]

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

> merge 1072822 1073479
Bug #1072822 [src:gdcm] gdcm FTBFS with VTK 9.3.0
Bug #1073479 [src:gdcm] gdcm: FTBFS: make[1]: *** [debian/rules:108: 
override_dh_auto_configure] Error 2
Added tag(s) fixed-upstream, upstream, and patch.
Bug #1072822 [src:gdcm] gdcm FTBFS with VTK 9.3.0
Added tag(s) trixie and sid.
Merged 1072822 1073479
>
End of message, stopping processing here.

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

Bug#1072822: Patch available

[Mathieu Malaterre]

Control: tags -1 upstream fixed-upstream

On Mon, Jun 17, 2024 at 9:36 PM Adrien Nader  wrote:
> I've prepared a fixed version in Ubuntu and Graham uploaded it. There is
> another issue than this SPDX one.
>
> I'm attaching the patch and won't paraphrase it.

Thanks !

Processed: Re: Bug#1072822: Patch available

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream fixed-upstream
Bug #1072822 [src:gdcm] gdcm FTBFS with VTK 9.3.0
Added tag(s) fixed-upstream and upstream.

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