Bug#1070733: linux-image-5.10.0-29-amd64 fails to boot with Error 16: Inconsistent filesystem structure

[Dan Poltawski]

Package: src:linux
Version: 5.10.216-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading to linux-image-5.10.0-29 the system fails to boot with
grub 'Error 16: Inconsistent filesystem structure'. Booting into 
linux-image-5.10.0-28-amd64
and the system is once again bootable

The console displays:
Booting 'Debian GNU/Linux, kernel 5.10.0-29-amd64'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-5.10.0-29-amd64 root=UUID=ca38e015-f8d1-4ef0-9dc9-b56d7c8
le0f1 ro
[Linux-bzImage, setup=0x3c00, size=0x6b5f40]
Initrd /boot/initrd. img-5.10.0-29-amd64
Error 16: Inconsistent filesystem structure
Press any key to continue...-





-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: QEMU
product_name: Standard PC (i440FX + PIIX, 1996)
product_version: pc-i440fx-8.1
chassis_vendor: QEMU
chassis_version: pc-i440fx-8.1
bios_vendor: SeaBIOS
bios_version: rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:05.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio SCSI [1af4:1004]
Subsystem: Red Hat, Inc. Virtio SCSI [1af4:0008]
Physical Slot: 5
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:12.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device 
[1af4:1000]
Subsystem: Red Hat, Inc. Virtio network device [1af4:0001]
Physical Slot: 18
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:13.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device 
[1af4:1000]
Subsystem: Red Hat, Inc. Virtio network device [1af4:0001]
Physical Slot: 19
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:1e.0 PCI bridge [0604]: Red Hat, Inc. QEMU PCI-PCI bridge [1b36:0001] 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

00:1f.0 PCI bridge [0604]: Red Hat, Inc. QEMU PCI-PCI bridge [1b36:0001] 
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 


** USB devices:
not available


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

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

Versions of packages linux-image-5.10.0-29-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.140
ii  kmod28-1
ii  linux-base  4.6

Versions of packages linux-image-5.10.0-29-amd64 recommends:
ii  apparmor 2.13.6-10
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.10.0-29-amd64 suggests:
pn  debian-kernel-handbook   
pn  grub-pc | grub-efi-amd64 | extlinux  
pn  linux-doc-5.10   

Versions of packages linux-image-5.10.0-29-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  

Bug#1061421: Fails to start after an upgrade

[duck]

Quack,

On 2024-04-22 00:44, Jeremy Bícha wrote:

There have been a huge amount of changes, but most of those changes
were in Unstable and haven't reached Testing yet.


I can confirm the problem is still there in latest unstable.


Marc, there is a fix for sway 1.9 in wlgreet 0.5. Do you want to try
if that improves anything here?


Not sure this is the same problem but I would say it's worth a try.
I'll prepare the package and let you know how it goes.

Regards.
\_o<

--
Marc Dequènes

Bug#1069410: efitools: FTBFS on arm64: make[1]: *** [Make.rules:130: HelloWorld-signed.efi] Error 1

[Steve McIntyre]

Control: tags -1 +confirmed

On Sat, Apr 20, 2024 at 02:01:48PM +0200, Lucas Nussbaum wrote:
>Source: efitools
>Version: 1.9.2-3
>Severity: serious
>Justification: FTBFS
>Tags: trixie sid ftbfs
>User: lu...@debian.org
>Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64
>
>Hi,
>
>During a rebuild of all packages in sid, your package failed to build
>on arm64.

...

>> Signature at: 40
>> sbsign --key DB.key --cert DB.crt --output HelloWorld-signed.efi 
>> HelloWorld.efi
>> ./cert-to-efi-sig-list -g ----123456789abc PK.crt PK.esl
>> Invalid DOS header magic
>> make[1]: *** [Make.rules:130: HelloWorld-signed.efi] Error 1

I can reproduce this here. The HelloWorld.efi binary seems to be
totally malformed. Digging further...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
You lock the door
And throw away the key
There's someone in my head but it's not me 

Processed: Re: Bug#1069410: efitools: FTBFS on arm64: make[1]: *** [Make.rules:130: HelloWorld-signed.efi] Error 1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +confirmed
Bug #1069410 [src:efitools] efitools: FTBFS on arm64: make[1]: *** 
[Make.rules:130: HelloWorld-signed.efi] Error 1
Added tag(s) confirmed.

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

Bug#1005165: marked as done (fwupd-amd64-signed uninstallable for a few weeks now)

[Debian Bug Tracking System]

Your message dated Tue, 7 May 2024 22:14:08 +0100
with message-id <20240507211408.ga2949...@tack.einval.com>
and subject line Re: Bug#1005165: fwupd-amd64-signed uninstallable for a few 
weeks now
has caused the Debian Bug report #1005165,
regarding fwupd-amd64-signed uninstallable for a few weeks now
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.)


-- 
1005165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd-amd64-signed
Version: 1.5.7+5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vent...@debian.org

Dear Maintainer,

fwupd-amd64-signed is uninstallable as it depends on fwupd < 1.5.7-6, however
the current version in unstable is 1.7.4-1.


Cheers,

Bastian

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
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 fwupd-amd64-signed depends on:
ii  fwupd  1.7.4-1

fwupd-amd64-signed recommends no packages.

fwupd-amd64-signed suggests no packages.
--- End Message ---
--- Begin Message ---
Closing this old bug...

On Thu, Feb 02, 2023 at 02:38:09PM +0100, Paul Gevers wrote:
>Hi,
>
>On Tue, 08 Feb 2022 11:11:35 +0100 Bastian Venthur 
>wrote:
>> Package: fwupd-amd64-signed
>> Version: 1.5.7+5
>> Severity: grave
>> Justification: renders package unusable
>> X-Debbugs-Cc: vent...@debian.org
>> 
>> Dear Maintainer,
>> 
>> fwupd-amd64-signed is uninstallable as it depends on fwupd < 1.5.7-6, however
>> the current version in unstable is 1.7.4-1.
>
>This bug is already marked fixed, but not closed. I think it can be closed,
>right?

Agreed.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back--- End Message ---

Processed: Re: Bug#1070706: gtk4 udeb has unsatisfiable dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity 1070706 normal
Bug #1070706 [gtk4] gtk4 udeb has unsatisfiable dependencies
Severity set to 'normal' from 'serious'
> severity 1070714 normal
Bug #1070714 [src:vte2.91] libvte-2.91-0-udeb depends on both GTK 3 and GTK 4
Severity set to 'normal' from 'serious'

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

Bug#1070706: gtk4 udeb has unsatisfiable dependencies

[Simon McVittie]

Control: severity 1070706 normal
Control: severity 1070714 normal

On Tue, 07 May 2024 at 22:53:33 +0200, Cyril Brulebois wrote:
> Simon McVittie  (2024-05-07):
> > do the release/installer teams consider udeb dependencies
> > on non-udeb packages, by udebs that d-i does not currently need or use,
> > to be a RC issue or merely a nice-to-have?
> 
> If udebs are actually used, I call that an RC bug and try to get it
> fixed swiftly (sometimes NMUing right away when time is of the essence).
> Otherwise I usually let those fly (without even filing bug reports).

In that case I'm downgrading #1070714 and #1070706 to normal, because the
issues I noticed while investigating #1070706 are worth tracking and being
aware of but non-RC, and the issue that Peter originally reported is not
actionable for the gtk4 maintainers (it needs to be fixed via a binNMU).

We'll need to revisit #1070714 and #1070706 if someone makes a concerted
effort to GTK3ize the installer, but that has been on my to-do list since
before bookworm and shows no signs of approaching the top, so it might
have to be someone else's project.

Thanks!

smcv

Bug#1066624: marked as done (xfireworks: FTBFS: etc.c:11:19: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 21:08:48 +
with message-id 
and subject line Bug#1066624: fixed in xfireworks 1.3-14
has caused the Debian Bug report #1066624,
regarding xfireworks: FTBFS: etc.c:11:19: error: implicit declaration of 
function ‘time’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> cc -c arguments.c -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
> etc.c: In function ‘InitializeRand’:
> etc.c:11:19: error: implicit declaration of function ‘time’ 
> [-Werror=implicit-function-declaration]
>11 |   srand((unsigned)time(NULL));
>   |   ^~~~
> etc.c:2:1: note: ‘time’ is defined in header ‘’; did you forget to 
> ‘#include ’?
> 1 | #include "etc.h"
>   +++ |+#include 
> 2 | 
> cat xfireworks.1 | gzip -9 > xfireworks.6.gz
> gzip: warning: GZIP environment variable is deprecated; use an alias or script
> cat xfireworks.conf | ./mkconf > xfireworks_conf.h
> cc -c XFireworks.c -I/usr/X11R6/include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:73: etc.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/xfireworks_1.3-13_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: xfireworks
Source-Version: 1.3-14
Done: Yukiharu YABUKI 

We believe that the bug you reported is fixed in the latest version of
xfireworks, 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.
Yukiharu YABUKI  (supplier of updated xfireworks 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: Wed, 08 May 2024 05:21:23 +0900
Source: xfireworks
Binary: xfireworks xfireworks-dbgsym
Architecture: source amd64
Version: 1.3-14
Distribution: unstable
Urgency: high
Maintainer: Yukiharu YABUKI 
Changed-By: Yukiharu YABUKI 
Description:
 xfireworks - Fireworks in your root window
Closes: 1066624
Changes:
 xfireworks (1.3-14) unstable; urgency=high
 .
   [ Yukiharu YABUKI ]
   * Fix FBTFS for time_t transition
   (Closes: #1066624)
Checksums-Sha1:
 5e9244392ad87667033d83a8f2f084e6f05e211d 1830 xfireworks_1.3-14.dsc
 f4fbee7973f3d640a586b2078f40e062fa9a1736 6456 xfireworks_1.3-14.debian.tar.xz
 58a0b8e4fdf40f4512eec55b754da490c2ea9624 63112 
xfireworks-dbgsym_1.3-14_amd64.deb
 f6988bfea88e90f146c893a2f4dd2a5611fa46ff 6811 xfireworks_1.3-14_amd64.buildinfo
 

Bug#1069452: marked as done (purelibc: FTBFS on armhf: ccPREIBJ.s:380: Error: symbol `readdir64' is already defined)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 20:50:44 +
with message-id 
and subject line Bug#1069452: fixed in purelibc 1.0.8-1
has caused the Debian Bug report #1069452,
regarding purelibc: FTBFS on armhf: ccPREIBJ.s:380: Error: symbol `readdir64' 
is already defined
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.)


-- 
1069452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: purelibc
Version: 1.0.6-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> /usr/bin/cc -D_GNU_SOURCE -Dpurelibc_EXPORTS -I/<> -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -Wall -pedantic -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FORTIFY_SOURCE=2 -ggdb -Wall -Wextra -pedantic -std=gnu11 
> -Wno-incompatible-pointer-types -Wno-unused-parameter -fPIC -MD -MT 
> CMakeFiles/purelibc.dir/syscalls.c.o -MF 
> CMakeFiles/purelibc.dir/syscalls.c.o.d -o 
> CMakeFiles/purelibc.dir/syscalls.c.o -c /<>/syscalls.c
> /tmp/ccPREIBJ.s: Assembler messages:
> /tmp/ccPREIBJ.s:380: Error: symbol `readdir64' is already defined
> /tmp/ccPREIBJ.s:984: Error: symbol `scandir64' is already defined
> /tmp/ccPREIBJ.s:1045: Error: symbol `scandirat64' is already defined
> make[3]: *** [CMakeFiles/purelibc.dir/build.make:79: 
> CMakeFiles/purelibc.dir/dir.c.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/purelibc_1.0.6-1_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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: purelibc
Source-Version: 1.0.8-1
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated purelibc 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, 07 May 2024 22:18:19 +0200
Source: purelibc
Architecture: source
Version: 1.0.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VirtualSquare Team 
Changed-By: Mattia Rizzolo 
Closes: 1069002 1069452
Changes:
 purelibc (1.0.8-1) unstable; urgency=medium
 .
   * Team upload.
   * Import version 1.0.8.
 + Add support for loong64.  Closes: #1069002
 + Fix FTBFS with __USE_FILE_OFFSET64/__USE_TIME_BITS64 on armhf.
   Closes: #1069452
Checksums-Sha1:
 7a71afa3d2fa3dde3b7181334d17300ecb81f95d 2073 purelibc_1.0.8-1.dsc
 708d6c3f624dfe910cfa0fc2863bc0853c49f05c 27849 purelibc_1.0.8.orig.tar.gz
 fdd8debd6b99d9daaed703a6dea912ace3052cb3 3592 purelibc_1.0.8-1.debian.tar.xz
 1cf6375694c829a607806eb22022da593fc2f85d 7442 purelibc_1.0.8-1_amd64.buildinfo
Checksums-Sha256:
 3e0f99ddf7724c038cd37c8c258ff1288b5863681d664d433cb800debe9825cf 2073 
purelibc_1.0.8-1.dsc
 4c79969cd700e13459f852fa43c978d6d7f4305ad3f32b4280e57ce70a415ac6 27849 
purelibc_1.0.8.orig.tar.gz
 6578fb2382c69eb969eda19ed3d75d002f34b4f212cc427c6ad562fb20016f6d 3592 
purelibc_1.0.8-1.debian.tar.xz
 b8abd2af366a345b4a62cb2fb793bfa17dfb7501f603c5b40e4f336426097786 7442 
purelibc_1.0.8-1_amd64.buildinfo

Bug#1070706: gtk4 udeb has unsatisfiable dependencies

[Simon McVittie]

On Tue, 07 May 2024 at 22:02:12 +0200, Paul Gevers wrote:
> On 07-05-2024 7:49 p.m., Simon McVittie wrote:
> > The version in testing, 4.12.5+ds-3, has the same dependencies, so this
> > is not a regression.
> 
> Is it? It seems that the version in unstable depends on libpng16-16t64-udeb
> where the version in testing depends on libpng16-16-udeb. The later exists,
> the former not.

Oh, well spotted! It looks as though src:gtk4 needs a binNMU against
libpng-dev (>= 1.6.43-4) for #1066069, because we were unlucky with
the timing of gtk4's most recent upload and so it got built against the
incorrect libpng-dev.

My understanding is that a binNMU would be better than a sourceful upload
of gtk4 because it won't reset the migration clock. If that's correct,
please could someone with release team or wanna-build powers schedule it?

nmu gtk4_4.12.5+ds-6 . ALL . -m 'rebuild with #1066069 fixed'

Looking at the d-i Packages.gz for amd64, the only other source
package that has picked up the bad libpng16-16t64-udeb dependency
seems to be matchbox-keyboard, which needs a sourceful upload to fix an
implicit-declarations FTBFS anyway, therefore isn't useful to binNMU.

After those binNMUs, the gtk4 udeb will still not be installable into
the debian-installer environment (either in testing or in unstable), but
it should at least be able to migrate, because all of its dependencies
will be packages that exist (whether deb or udeb).

After that: do the release/installer teams consider udeb dependencies
on non-udeb packages, by udebs that d-i does not currently need or use,
to be a RC issue or merely a nice-to-have?

Thanks,
smcv

Bug#1070720: tpm2-tss: test/unit/tcti-spidev failure on 32bit with 64bit time_t

[Adrian Bunk]

Source: tpm2-tss
Version: 4.1.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=tpm2-tss=4.1.0-1

...
SKIP: test/unit/tcti-libtpms


WARNING:test:test/unit/tcti-libtpms.c:1793:main() _FILE_OFFSET == 64 would 
produce cmocka errors. 
SKIP test/unit/tcti-libtpms (exit status: 77)

SKIP: test/unit/tcti-device
===

WARNING:tests:test/unit/tcti-device.c:454:main() _FILE_OFFSET == 64 would 
produce cmocka errors. 
SKIP test/unit/tcti-device (exit status: 77)

SKIP: test/unit/tcti-pcap
=

WARNING:tests:test/unit/tcti-pcap.c:736:main() _FILE_OFFSET == 64 would produce 
cmocka errors. 
SKIP test/unit/tcti-pcap (exit status: 77)

FAIL: test/unit/tcti-spidev
===

[==] tests: Running 1 test(s).
[ RUN  ] tcti_spi_init_test
ERROR:tcti:src/tss2-tcti/tcti-spidev.c:48:platform_spi_acquire() SPI acquire 
failed: Bad file descriptor 
ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:164:spi_tpm_helper_log_register_access()
 READ register 0xd40f00 (4 bytes) failed in transaction start 
ERROR:tcti:src/tss2-tcti/tcti-spidev.c:68:platform_spi_release() SPI release 
failed: Bad file descriptor 
ERROR:tcti:src/tss2-tcti/tcti-spidev.c:48:platform_spi_acquire() SPI acquire 
failed: Bad file descriptor 
ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:164:spi_tpm_helper_log_register_access()
 READ register 0xd40f00 (4 bytes) failed in transaction start 
ERROR:tcti:src/tss2-tcti/tcti-spidev.c:68:platform_spi_release() SPI release 
failed: Bad file descriptor 
ERROR:tcti:src/tss2-tcti/tcti-spidev.c:48:platform_spi_acquire() SPI acquire 
failed: Bad file descriptor 
ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:164:spi_tpm_helper_log_register_access()
 READ register 0xd40f00 (4 bytes) failed in transaction start 
ERROR:tcti:src/tss2-tcti/tcti-spidev.c:68:platform_spi_release() SPI release 
failed: Bad file descriptor 
...
ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:164:spi_tpm_helper_log_register_access()
 READ register 0xd40f00 (4 bytes) failed in transaction start 
ERROR:tcti:src/tss2-tcti/tcti-spidev.c:68:platform_spi_release() SPI release 
failed: Bad file descriptor 
ERROR:tcti:src/tss2-tcti/tcti-spi-helper.c:728:Tss2_Tcti_Spi_Helper_Init() 
Probing TPM failed 
[  ERROR   ] --- 0xa000a != 0
[   LINE   ] --- test/unit/tcti-spidev.c:200: error: Failure!
[  FAILED  ] tcti_spi_init_test
[==] tests: 1 test(s) run.
[  PASSED  ] 0 test(s).
[  FAILED  ] tests: 1 test(s), listed below:
[  FAILED  ] tcti_spi_init_test

 1 FAILED TEST(S)
FAIL test/unit/tcti-spidev (exit status: 1)

SKIP: test/unit/fapi-io
===

WARNING:tests:test/unit/fapi-io.c:370:main() _FILE_OFFSET == 64 would produce 
cmocka errors. 
SKIP test/unit/fapi-io (exit status: 77)


Testsuite summary for tpm2-tss 4.1.0

# TOTAL: 61
# PASS:  56
# SKIP:  4
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to https://github.com/tpm2-software/tpm2-tss/issues

make[3]: *** [Makefile:33547: test-suite.log] Error 1

Bug#1070706: gtk4 udeb has unsatisfiable dependencies

[Paul Gevers]

Hi,

On 07-05-2024 7:49 p.m., Simon McVittie wrote:

The version in testing, 4.12.5+ds-3, has the same dependencies, so this
is not a regression.


Is it? It seems that the version in unstable depends on 
libpng16-16t64-udeb where the version in testing depends on 
libpng16-16-udeb. The later exists, the former not.



Is this requirement newly enforced by britney?


No.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1061216: Please upgrade to llvm-toolchain-17

[Gregor Riepl]

If a fix for this can't be released on time, I'm requesting an exception for 
llvm-15. Removing OpenVDB from Debian will affect Blender, which is is 
relatively high-profile and should not just be axed for the sake if a pruning 
operation.


You still have time, we aren't going to release the trixie anytime soon :) but 
we won't probably block the removal in testing for openvdb (the popcon isn't 
high IMHO).


Let's hope upstream notices the issue and fixes it.

In the meantime, it may be possible to remove the immediate pressure by simply 
disabling the build of libopenvdb-ax. The rest of OpenVDB doesn't require LLVM 
15, and I couldn't find any Debian package that depends on it (save for 
python3-openvdb, which will simply not have AX support).

This should at least bring Blender back into trixie.

I did a quick build test with the AX component disabled, and that seems to work 
fine. Blender also compiles. Didn't try to install and run the final result, 
though.

Processed: Re: kdeconnectd: should not listen on all interfaces by default

[Debian Bug Tracking System]

Processing control commands:

> severity 998197 serious
Bug #998197 [kdeconnect] kdeconnectd: should not listen on all interfaces by 
default
Severity set to 'serious' from 'normal'
> tags 998197 + security
Bug #998197 [kdeconnect] kdeconnectd: should not listen on all interfaces by 
default
Added tag(s) security.

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

Bug#978511: marked as done (gcc-python-plugin: non-standard gcc/g++ used for build (gcc-9))

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 18:59:25 +
with message-id 
and subject line Bug#1026175: Removed package(s) from unstable
has caused the Debian Bug report #978511,
regarding gcc-python-plugin: non-standard gcc/g++ used for build (gcc-9)
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.)


-- 
978511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-python-plugin
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-10/g++-10.  If the package cannot be built with GCC 10 because
of a compiler bug, please file a report for gcc-10.

Please keep this report open until the package uses the default
compiler version (or gcc-10) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.
--- End Message ---
--- Begin Message ---
Version: 0.17-6+rm

Dear submitter,

as the package gcc-python-plugin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026175

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#963999: marked as done (gcc-python-plugin: FTBFS: invalid literal for int() with base 10)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 18:59:25 +
with message-id 
and subject line Bug#1026175: Removed package(s) from unstable
has caused the Debian Bug report #963999,
regarding gcc-python-plugin: FTBFS: invalid literal for int() with base 10
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.)


-- 
963999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-python-plugin
Version: 0.17-6
Severity: serious
Tags: ftbfs

This package fails to build from source on current sid.

  Exception occurred:
File "/usr/lib/python3/dist-packages/sphinx/writers/html5.py", line 548, in 
visit_image
  atts['width'] = int(atts['width']) * scale
  ValueError: invalid literal for int() with base 10: '550px'
  The full traceback has been saved in /tmp/sphinx-err-b_30quqh.log, if you 
want to report the issue to the developers.
  Please also report this if it was a user error, so that a better error 
message can be provided next time.
  A bug report can be filed in the tracker at 
. Thanks!
  make[1]: *** [Makefile:42: html] Error 2
  make[1]: Leaving directory '/<>/docs'
  make: *** [debian/rules:70: doc-stamp] Error 2
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Version: 0.17-6+rm

Dear submitter,

as the package gcc-python-plugin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026175

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1000213: marked as done (gcc-python-plugin: Don't use -Werror=deprecated-declarations)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 18:59:25 +
with message-id 
and subject line Bug#1026175: Removed package(s) from unstable
has caused the Debian Bug report #1000213,
regarding gcc-python-plugin: Don't use -Werror=deprecated-declarations
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.)


-- 
1000213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-python-plugin
Version: 0.17-6
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hello,

The gcc-python-plugin package currently fails to build because the source
uses functions that are deprecated in python3.9:

  gcc-python.c:791:24: error: ‘void PyEval_InitThreads()’ is deprecated 
[-Werror=deprecated-declarations]

Since there is no upstream fix for this deprecation warning, it doesn't seem
worth failing the build on, so I've prepared the attached patch to fix it. 
As a side effect, it fixes the fact that gcc-python-plugin was not
previously using the cflags from dpkg-buildflags for the build, which seems
kind of important!

I've uploaded this patch to Ubuntu.  Please consider including it in Debian
as well.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gcc-python-plugin-0.17/debian/rules 
gcc-python-plugin-0.17/debian/rules
--- gcc-python-plugin-0.17/debian/rules 2020-02-20 05:15:45.0 -0800
+++ gcc-python-plugin-0.17/debian/rules 2021-11-19 11:24:09.0 -0800
@@ -14,6 +14,7 @@
 INTERP = python3 python3-dbg # python python-dbg
 
 export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS)
+export CFLAGS := $(shell env 
DEB_CFLAGS_MAINT_APPEND=-Wno-error=deprecated-declarations dpkg-buildflags 
--get CFLAGS)
 
 build-arch: $(INTERP:%=build-stamp-%)
 build-indep: doc-stamp
--- End Message ---
--- Begin Message ---
Version: 0.17-6+rm

Dear submitter,

as the package gcc-python-plugin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1026175

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1067285: whitakers-words in Debian, gnat-13 transition

[Nicolas Boulenguez]

Hello.
The package needs to build with gnat-13 in order to be part of next
Debian release.
Are you planning a new upload in the near future?
Else, are you OK with a non maintainer upload fixing this specific bug?

Bug#1068755: closing 1068755

[Reinhard Tartler]

close 1068755 20.10.25+dfsg1-3
thanks

docker.io 20.10.25+dfsg1-3 comes with a backported patch that addresses this
FTBFS

Processed: closing 1068755

[Debian Bug Tracking System]

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

> close 1068755 20.10.25+dfsg1-3
Bug #1068755 [src:docker.io] docker.io: FTBFS: failing tests
Marked as fixed in versions docker.io/20.10.25+dfsg1-3.
Bug #1068755 [src:docker.io] docker.io: FTBFS: failing tests
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1068389: marked as done (src:pcp: unsatisfied build dependency in testing: python3-bpfcc)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 18:03:03 +
with message-id 
and subject line Bug#1068389: fixed in pcp 6.2.1-1
has caused the Debian Bug report #1068389,
regarding src:pcp: unsatisfied build dependency in testing: python3-bpfcc
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.)


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

Source: pcp
Version: 6.2.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pcp
Source-Version: 6.2.1-1
Done: Nathan Scott 

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

Debian distribution maintenance software
pp.
Nathan Scott  (supplier of updated pcp 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: Wed, 10 Apr 2024 09:14:46 +1100
Source: pcp
Binary: libpcp-archive1 libpcp-archive1-dev libpcp-gui2 libpcp-gui2-dev 
libpcp-import-perl libpcp-import1 libpcp-import1-dev libpcp-logsummary-perl 
libpcp-mmv-perl libpcp-mmv1 libpcp-mmv1-dev libpcp-pmda-perl libpcp-pmda3 
libpcp-pmda3-dev libpcp-trace2 libpcp-trace2-dev libpcp-web1 libpcp-web1-dev 
libpcp3 libpcp3-dev pcp pcp-conf pcp-doc pcp-export-pcp2elasticsearch 
pcp-export-pcp2graphite pcp-export-pcp2influxdb pcp-export-pcp2json 
pcp-export-pcp2spark pcp-export-pcp2xlsx pcp-export-pcp2xml 
pcp-export-pcp2zabbix pcp-export-zabbix-agent pcp-gui pcp-import-collectl2pcp 
pcp-import-ganglia2pcp pcp-import-iostat2pcp pcp-import-mrtg2pcp 
pcp-import-sar2pcp pcp-import-sheet2pcp pcp-pmda-infiniband pcp-testsuite 
pcp-zeroconf python3-pcp
Architecture: source arm64 all
Version: 6.2.1-1
Distribution: unstable
Urgency: low
Maintainer: PCP Development Team 
Changed-By: Nathan Scott 
Description:
 libpcp-archive1 - Performance Co-Pilot archive writing library
 libpcp-archive1-dev - Performance Co-Pilot archive writing library and headers
 libpcp-gui2 - Performance Co-Pilot graphical client tools library
 libpcp-gui2-dev - Performance Co-Pilot graphical client tools library and 
headers
 libpcp-import-perl - Performance Co-Pilot log import Perl module
 libpcp-import1 - Performance Co-Pilot data import library
 libpcp-import1-dev - Performance Co-Pilot data import library and headers
 libpcp-logsummary-perl - Performance Co-Pilot historical log summary module
 libpcp-mmv-perl - Performance Co-Pilot Memory Mapped Value Perl module
 libpcp-mmv1 - Performance Co-Pilot Memory Mapped Value client library
 libpcp-mmv1-dev - Performance Co-Pilot Memory Mapped Value library and headers
 libpcp-pmda-perl - Performance Co-Pilot Domain Agent Perl module
 libpcp-pmda3 - Performance Co-Pilot Domain Agent library
 libpcp-pmda3-dev - Performance Co-Pilot Domain Agent library and headers
 libpcp-trace2 - Performance Co-Pilot application tracing library
 libpcp-trace2-dev - Performance Co-Pilot 

Processed: Re: Bug#1070706: gtk4 udeb has unsatisfiable dependencies

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + d-i
Bug #1070706 [gtk4] gtk4 - udebs broken.
Added tag(s) d-i.
> found -1 4.12.5+ds-3
Bug #1070706 [gtk4] gtk4 - udebs broken.
There is no source info for the package 'gtk4' at version '4.12.5+ds-3' with 
architecture ''
Unable to make a source version for version '4.12.5+ds-3'
Marked as found in versions 4.12.5+ds-3.
> retitle -1 gtk4 udeb has unsatisfiable dependencies
Bug #1070706 [gtk4] gtk4 - udebs broken.
Changed Bug title to 'gtk4 udeb has unsatisfiable dependencies' from 'gtk4 - 
udebs broken.'.
> clone -1 -2
Bug #1070706 [gtk4] gtk4 udeb has unsatisfiable dependencies
Bug 1070706 cloned as bug 1070714
> retitle -2 libvte-2.91-0-udeb depends on both GTK 3 and GTK 4
Bug #1070714 [gtk4] gtk4 udeb has unsatisfiable dependencies
Changed Bug title to 'libvte-2.91-0-udeb depends on both GTK 3 and GTK 4' from 
'gtk4 udeb has unsatisfiable dependencies'.
> reassign -2 src:vte2.91 0.75.92-1
Bug #1070714 [gtk4] libvte-2.91-0-udeb depends on both GTK 3 and GTK 4
Bug reassigned from package 'gtk4' to 'src:vte2.91'.
No longer marked as found in versions 4.12.5+ds-3 and 4.12.5+dfsg-6.
Ignoring request to alter fixed versions of bug #1070714 to the same values 
previously set
Bug #1070714 [src:vte2.91] libvte-2.91-0-udeb depends on both GTK 3 and GTK 4
Marked as found in versions vte2.91/0.75.92-1.

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

Bug#1070706: gtk4 udeb has unsatisfiable dependencies

[Simon McVittie]

Control: tags -1 + d-i
Control: found -1 4.12.5+ds-3
Control: retitle -1 gtk4 udeb has unsatisfiable dependencies
Control: clone -1 -2
Control: retitle -2 libvte-2.91-0-udeb depends on both GTK 3 and GTK 4
Control: reassign -2 src:vte2.91 0.75.92-1

On Tue, 07 May 2024 at 15:44:02 +0100, Peter Michael Green wrote:
> According to britney, gtk4's udebs are uninstallable.

gtk4 is not yet used by debian-installer (which is still on GTK 2)
so the udeb is not actually necessary, and one workaround would be to
disable it entirely (but then we'd have to put GTK 4 through NEW again
if we are ever able to upgrade d-i to it).

The version in testing, 4.12.5+ds-3, has the same dependencies, so this
is not a regression. Is this requirement newly enforced by britney?

I think a large part of the problem is that when GTK 4 support was added
to src:vte2.91, both the GTK 3 and GTK 4 versions were put into the same
udeb package, libvte-2.91-0-udeb, instead of giving the GTK 4 version
its own udeb. However, I'm unsure how that change got into testing -
if britney is enforcing installability of udebs, I would have expected
that the updated libvte-2.91-0-udeb would have been newly-uninstallable,
preventing its migration?

It seems most realistic that d-i in Debian 13 will depend on GTK 3 if
someone finds the time to do the necessary porting and testing, or stay
on GTK 2 if not, so libvte-2.91-0-udeb should become a udeb version of
only libvte-2.91-0 (i.e. GTK 3 only) as it was in Debian 12, and drop
its GTK 4 parts. That would mean that GTK 4 would no longer be regressing
the installability of libvte-2.91-0-udeb.

If there is a serious attempt to get d-i using GTK *4*, then that would
require a new libvte-2.91-gtk4-0-udeb. However, GTK 4's threading model
is definitely incompatible with the current design of cdebconf-gtk (it
calls into GTK from more than one thread, which is discouraged in GTK
3 and not allowed at all in GTK 4), so a prerequisite for that would
be to move all of cdebconf-gtk's GTK interactions onto one thread,
with message-passing between that thread and the cdebconf thread.

I'm also unsure how GTK 4 can possibly have caused libvte-2.91-0-udeb's
installability to regress anyway, because libvte-2.91-0-udeb in testing
depends on liblz4-1, which does not have a corresponding udeb. That
will need fixing (by adding a liblz4-1-udeb, or linking it statically,
or allowing .deb libraries to satisfy udebs' dependencies) if we ever
want a GTK 3 or later installer.

Making the GTK 4 udeb installable looks like a significant task. It depends
on:

OK - fontconfig-udeb (>= 2.15.0),
OK - libc6-udeb (>= 2.37),
!! - libcairo-script-interpreter2 (>= 1.18.0),
OK - libcairo2-udeb (>= 1.18.0),
OK - libepoxy0-udeb (>= 1.5.4),
OK - libfribidi0-udeb (>= 1.0.13),
OK - libgdk-pixbuf-2.0-0-udeb (>= 2.42.10+dfsg),
OK - libglib2.0-udeb (>= 2.78.4),
!! - libgraphene-1.0-0 (>= 1.10.8),
OK - libharfbuzz0-udeb (>= 8.3.0),
!! - libjpeg62-turbo (>= 1:2.1.5),
OK - libpango1.0-udeb (>= 1.52.1+ds),
OK - libpng16-16t64-udeb (>= 1.6.2),
!! - libtiff6 (>= 4.5.1+git230720),
OK - libx11-6-udeb (>= 2:1.6.0),
OK - libxcursor1-udeb (>> 1.1.2),
!! - libxdamage1 (>= 1:1.1),
OK - libxext6-udeb (>= 2:1.3.0),
OK - libxfixes3-udeb (>= 1:5.0),
OK - libxi6-udeb (>= 2:1.6.99.1),
OK - libxinerama1-udeb (>= 2:1.1.4),
OK - libxrandr2-udeb (>= 2:1.5)

cairo has a udeb, but it doesn't include the equivalent of
libcairo-script-interpreter2. It might be possible to disable the GTK
features that rely on that library? Or it might be possible to add the
script interpreter to the udeb?

graphene does not have udebs at all, and I think it's a mandatory
dependency for GTK 4, so if we ever want a GTK-4-based d-i, there is
no avoiding adding a graphene udeb.

libjpeg-turbo, tiff and libxdamage are in the same situation as graphene
(these were optional in GTK 3 but are required in GTK 4). Unlike graphene,
these are not maintained by the GNOME team, so we cannot unilaterally
add udebs to them.

smcv

Bug#1026061: [+externe Mail+] Re: Bug#1026061: bart: FTBFS randomly in bullseye (failing test)

[Uecker, Martin]

Am Dienstag, dem 07.05.2024 um 19:23 +0200 schrieb Santiago Vila:
> El 7/5/24 a las 18:50, Uecker, Martin escribió:
> > Am Dienstag, dem 07.05.2024 um 17:59 +0200 schrieb Santiago Vila:
> > > El 1/1/23 a las 16:55, Uecker, Martin escribió:
> > > In the meantime, I became member of debian-med, so in theory,
> > > I could fix this myself via team upload. Would you prefer
> > > that I take care of this myself that way?
> > 
> > I wouldn't mind if you did. There are some other bugs
> > which could easily be fixed with a new upload (i.e. with
> > minor patches in the bug tracker)
> > > 
> > > (I would also handle bart-cuda, also affected but not reported yet)
> > 
> > bart-cuda needs to be updated to 0.9.00 which should
> > be straightforward in principle but need more work
> > and a binary upload.
> 
> Well, just in case: I'm talking about making an upload
> for bullseye, using the same fix in bookworm, then
> sending a bug to release.debian.org explaining the
> issue, etc.
> 
> That's mainly bureaucratic and will not interfere with your normal
> work in unstable regarding new upstream releases and such (which
> I still prefer not to handle myself).
> 
Yes, if you do not mind to do the work, please update bullseye.
That would be much appreciated.

Martin

Bug#1026061: [+externe Mail+] Re: Bug#1026061: bart: FTBFS randomly in bullseye (failing test)

[Santiago Vila]

El 7/5/24 a las 18:50, Uecker, Martin escribió:

Am Dienstag, dem 07.05.2024 um 17:59 +0200 schrieb Santiago Vila:

El 1/1/23 a las 16:55, Uecker, Martin escribió:
In the meantime, I became member of debian-med, so in theory,
I could fix this myself via team upload. Would you prefer
that I take care of this myself that way?


I wouldn't mind if you did. There are some other bugs
which could easily be fixed with a new upload (i.e. with
minor patches in the bug tracker)


(I would also handle bart-cuda, also affected but not reported yet)


bart-cuda needs to be updated to 0.9.00 which should
be straightforward in principle but need more work
and a binary upload.


Well, just in case: I'm talking about making an upload
for bullseye, using the same fix in bookworm, then
sending a bug to release.debian.org explaining the
issue, etc.

That's mainly bureaucratic and will not interfere with your normal
work in unstable regarding new upstream releases and such (which
I still prefer not to handle myself).

Thanks.

Bug#1070711: python-werkzeug: CVE-2024-34069

[Salvatore Bonaccorso]

Source: python-werkzeug
Version: 3.0.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-werkzeug.

CVE-2024-34069[0]:
| Werkzeug is a comprehensive WSGI web application library. The
| debugger in affected versions of Werkzeug can allow an attacker to
| execute code on a developer's machine under some circumstances. This
| requires the attacker to get the developer to interact with a domain
| and subdomain they control, and enter the debugger PIN, but if they
| are successful it allows access to the debugger even if it is only
| running on localhost. This also requires the attacker to guess a URL
| in the developer's application that will trigger the debugger. This
| vulnerability is fixed in 3.0.3.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-34069
https://www.cve.org/CVERecord?id=CVE-2024-34069
[1] https://github.com/pallets/werkzeug/security/advisories/GHSA-2g68-c3qc-8985
[2] 
https://github.com/pallets/werkzeug/commit/71b69dfb7df3d912e66bab87fbb1f21f83504967
[3] 
https://github.com/pallets/werkzeug/commit/890b6b62634fa61224222aee31081c61b054ff01

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1070710: python-html-sanitizer: CVE-2024-34078: Arbitrary HTML present after sanitization because of unicode normalization

[Salvatore Bonaccorso]

Source: python-html-sanitizer
Version: 2.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-html-sanitizer.

CVE-2024-34078[0]:
| html-sanitizer is an allowlist-based HTML cleaner. If using
| `keep_typographic_whitespace=False` (which is the default), the
| sanitizer normalizes unicode to the NFKC form at the end. Some
| unicode characters normalize to chevrons; this allows specially
| crafted HTML to escape sanitization. The problem has been fixed in
| 2.4.2.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-34078
https://www.cve.org/CVERecord?id=CVE-2024-34078
[1] 
https://github.com/matthiask/html-sanitizer/security/advisories/GHSA-wvhx-q427-fgh3
[2] 
https://github.com/matthiask/html-sanitizer/commit/48db42fc5143d0140c32d929c46b802f96913550

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1026061: [+externe Mail+] Re: Bug#1026061: bart: FTBFS randomly in bullseye (failing test)

[Uecker, Martin]

Am Dienstag, dem 07.05.2024 um 17:59 +0200 schrieb Santiago Vila:
> El 1/1/23 a las 16:55, Uecker, Martin escribió:
> > I can apply the patch, but I do not have much time now.
> > Is there some urgency?
> 
> Hello. A lot of time passed without activity on this bug.
> 
> In the meantime, I became member of debian-med, so in theory,
> I could fix this myself via team upload. Would you prefer
> that I take care of this myself that way?

I wouldn't mind if you did. There are some other bugs
which could easily be fixed with a new upload (i.e. with
minor patches in the bug tracker)
> 
> (I would also handle bart-cuda, also affected but not reported yet)

bart-cuda needs to be updated to 0.9.00 which should
be straightforward in principle but need more work
and a binary upload.

Otherwise, I would have more time in July to do some work.

Martin

> 
> (Yes, I still think it would be worthy to fix this in bullseye,
> for posterity and before it becomes LTS).
> 
> Thanks.

Bug#1066228: marked as done (xjdic: FTBFS: xjdsa.c:84:31: error: implicit declaration of function ‘Kstrcmp’; did you mean ‘strcmp’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 16:51:01 +
with message-id 
and subject line Bug#1066228: fixed in xjdic 24-11.2
has caused the Debian Bug report #1066228,
regarding xjdic: FTBFS: xjdsa.c:84:31: error: implicit declaration of function 
‘Kstrcmp’; did you mean ‘strcmp’? [-Werror=implicit-function-declaration]
to be marked as done.

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

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


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

Hi,

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

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

Relevant part (hopefully):
> gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -fcommon -O3 -Wl,-z,relro -c 
> -DXJDFRONTEND -DXJDDIC -DMMAP xjdsa.c
> xjdsa.c: In function ‘xjdserver’:
> xjdsa.c:84:31: error: implicit declaration of function ‘Kstrcmp’; did you 
> mean ‘strcmp’? [-Werror=implicit-function-declaration]
>84 | res = Kstrcmp(sch_str_len,sch_str);
>   |   ^~~
>   |   strcmp
> xjdsa.c:179:17: error: implicit declaration of function ‘jindex’; did you 
> mean ‘rindex’? [-Werror=implicit-function-declaration]
>   179 | schix = jindex(it);
>   | ^~
>   | rindex
> xjdsa.c:183:17: error: implicit declaration of function ‘dbchar’ 
> [-Werror=implicit-function-declaration]
>   183 | while ((dbchar(schix) != 0x0a) && (schix >= 0)) schix--;
>   | ^~
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:88: xjdsa.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/xjdic_24-11_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: xjdic
Source-Version: 24-11.2
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
xjdic, 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.
Bastian Germann  (supplier of updated xjdic 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, 07 May 2024 16:30:08 +
Source: xjdic
Architecture: source
Version: 24-11.2
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Drolez 
Changed-By: Bastian Germann 
Closes: 1066228
Changes:
 xjdic (24-11.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix missing function declarations. Closes: #1066228
Checksums-Sha1:
 6f6a7b2cc5b3baadb1af0ad86c362f11c0294395 1502 xjdic_24-11.2.dsc
 d1a5092496b90486dfa6971fc7511278d3df070c 11464 xjdic_24-11.2.debian.tar.xz
 cb25a945107931f53a51d94c606a47930ebd4f51 5331 xjdic_24-11.2_source.buildinfo
Checksums-Sha256:
 a3d29babb7d6794087a768cda428be450d5412d67bb9e0364096b224fa153325 1502 
xjdic_24-11.2.dsc
 

Bug#1066228: xjdic: FTBFS: implicit declaration of functions

[Bastian Germann]

I am uploading a NMU that fixes this.
Please find the debdiff attached that builds on the experimental version.diff -Nru xjdic-24/debian/changelog xjdic-24/debian/changelog
--- xjdic-24/debian/changelog   2023-10-02 10:05:01.0 +
+++ xjdic-24/debian/changelog   2024-05-07 16:30:08.0 +
@@ -1,3 +1,10 @@
+xjdic (24-11.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix missing function declarations. Closes: #1066228
+
+ -- Bastian Germann   Tue, 07 May 2024 16:30:08 +
+
 xjdic (24-11.1) experimental; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xjdic-24/debian/patches/missing-function-declarations.patch 
xjdic-24/debian/patches/missing-function-declarations.patch
--- xjdic-24/debian/patches/missing-function-declarations.patch 1970-01-01 
00:00:00.0 +
+++ xjdic-24/debian/patches/missing-function-declarations.patch 2024-05-07 
16:28:31.0 +
@@ -0,0 +1,70 @@
+diff -u xjdic-24/exjdxgen.c xjdic-24/exjdxgen.c
+--- xjdic-24/exjdxgen.c
 xjdic-24/exjdxgen.c
+@@ -22,7 +22,7 @@
+ #include 
+
+ #include 
+-/*#include */
++#include 
+ #include 
+ #include 
+ #include "xjdic.h"
+diff -u xjdic-24/xjdclient.c xjdic-24/xjdclient.c
+--- xjdic-24/xjdclient.c
 xjdic-24/xjdclient.c
+@@ -32,6 +32,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
+diff -u xjdic-24/xjdfrontend.c xjdic-24/xjdfrontend.c
+--- xjdic-24/xjdfrontend.c
 xjdic-24/xjdfrontend.c
+@@ -196,7 +196,6 @@
+ void RadSet();
+ void Verbtoggle();
+ void FiltSet();
+-void xjdicrc();
+ void DoRADICALS();
+ int Vlookup();
+ void AppKanji(unsigned char c1,unsigned char c2);
+diff -u xjdic-24/xjdic.h xjdic-24/xjdic.h
+--- xjdic-24/xjdic.h
 xjdic-24/xjdic.h
+@@ -71,3 +71,7 @@
+   longxjdrsp_dicloc;
+   unsigned char   xjdrsp_resstr[512];
+   } RSP_PDU;
++
++void EMtoggle();
++void xjdicrc();
++unsigned char dbchar(unsigned long xit);
+diff -u xjdic-24/xjdsa.c xjdic-24/xjdsa.c
+--- xjdic-24/xjdsa.c
 xjdic-24/xjdsa.c
+@@ -30,6 +30,8 @@
+ #include 
+ #include "xjdic.h"
+
++int Kstrcmp(int klen,unsigned char *str1);
++unsigned long jindex(unsigned long xit);
+ unsigned char Dnamet[10][100],XJDXnamet[10][100];
+ unsigned char CBname[100];
+ unsigned char *dicbufft[10];
+diff -u xjdic-24/xjdserver.c xjdic-24/xjdserver.c
+--- xjdic-24/xjdserver.c
 xjdic-24/xjdserver.c
+@@ -36,7 +36,9 @@
+
+ void xjdicrc();
+ void DicSet ();
++int Kstrcmp(int klen,unsigned char *str1);
+ unsigned char *DicName(int dn);
++unsigned long jindex(unsigned long xit);
+
+ int portno=XJ_PORTNO;
+ int DontFork = FALSE;
diff -Nru xjdic-24/debian/patches/series xjdic-24/debian/patches/series
--- xjdic-24/debian/patches/series  2023-10-02 10:05:01.0 +
+++ xjdic-24/debian/patches/series  2024-05-07 16:29:32.0 +
@@ -1 +1,2 @@
 debian.patch
+missing-function-declarations.patch

Processed: Re: ghdl: various suggestions for the packaging

[Debian Bug Tracking System]

Processing control commands:

> tags 1067446 patch
Bug #1067446 [src:ghdl] ghdl fails to build with gnat-13
Added tag(s) patch.
> tags 1067686 patch
Bug #1067686 [src:ghdl] ghdl 4.0 available, builds on s390x
Added tag(s) patch.

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

Bug#1067320: marked as done (topal: FTBFS: debian/rules:8: /usr/share/ada/debian_packaging.mk: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 16:21:57 +
with message-id 
and subject line Bug#1067320: fixed in topal 84-1
has caused the Debian Bug report #1067320,
regarding topal: FTBFS: debian/rules:8: /usr/share/ada/debian_packaging.mk: 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh  /usr/share/ada/debian_packaging.mk
> dh: error: Unknown sequence /usr/share/ada/debian_packaging.mk (choose from: 
> binary binary-arch binary-indep build build-arch build-indep clean install 
> install-arch install-indep)
> debian/rules:8: /usr/share/ada/debian_packaging.mk: No such file or directory
> make: *** [debian/rules:24: /usr/share/ada/debian_packaging.mk] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/topal_81-2_unstable.log

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

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Phil Brooke  (supplier of updated topal 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, 07 May 2024 16:22:36 +0100
Source: topal
Architecture: source
Version: 84-1
Distribution: unstable
Urgency: medium
Maintainer: Phil Brooke 
Changed-By: Phil Brooke 
Closes: 1067320
Changes:
 topal (84-1) unstable; urgency=medium
 .
   * New upstream release.
   * Apply patch from Nicolas Boulenguez (thank you).
 - Fixes /usr/share/ada/debian_packaging.mk missing for
   debian/rules (closes: #1067320).
 - Assorted cleanups to Debian packaging.
   * Move to Salsa as Git VCS and minor polish.
Checksums-Sha1:
 8fc8f3657635647dfb824580f1d571330cedc31d 1904 topal_84-1.dsc
 304d08897aab90c88f8d7da22a825018261b448c 188011 topal_84.orig.tar.gz
 d8ada9aa8c68f9457cf1dde8fd2d9e5996144851 5204 topal_84-1.debian.tar.xz
 5901e442cfa8540be2f4102ba45f460d8bd65d89 8889 topal_84-1_source.buildinfo
Checksums-Sha256:
 42fea1aea415b5462daca8b9a6461e8151bd200bce7170afa9004b771f5aa076 1904 
topal_84-1.dsc
 d907507f04833e48f6fd0ec9f1c3c4dcaf8ab0d3e43f917853aed53d51765964 188011 
topal_84.orig.tar.gz
 a2bb13d37fb6e6b73a6e1036b7932b0e52cde9ac0be864a5f77ec982909dfc64 5204 
topal_84-1.debian.tar.xz
 d7532a46d44877fa16e293d1fa02961ea9a6788ea9f737b13b9c5a6ff48b041f 8889 
topal_84-1_source.buildinfo
Files:
 7a061407befbeb3d3b90ae95beb02034 1904 mail optional topal_84-1.dsc
 b79c635d2e916a40d44d4ce15af70e59 188011 mail optional topal_84.orig.tar.gz
 0a220fc8bf09ccf14a60b4d67529c2e2 5204 mail optional topal_84-1.debian.tar.xz
 c3573576307d7091bd49b7713ea83ea5 8889 mail optional topal_84-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKCMADj+pj/jrfBAKgZ0nig5vmSoFAmY6TxQACgkQgZ0nig5v
mSp4EBAAlRS09qPazWF6Me2MY0C3H+dmlKjxEeq6NGqIMWTfjLfsl1fYurGmoWiS
QohrLZKvdD9c9tzJg0ZS/sPTSwnv03AAkywBcB5WKhTrVOlOmRkwr2/IERgwM/Hh

Bug#1026061: bart: FTBFS randomly in bullseye (failing test)

[Santiago Vila]

El 1/1/23 a las 16:55, Uecker, Martin escribió:

I can apply the patch, but I do not have much time now.
Is there some urgency?


Hello. A lot of time passed without activity on this bug.

In the meantime, I became member of debian-med, so in theory,
I could fix this myself via team upload. Would you prefer
that I take care of this myself that way?

(I would also handle bart-cuda, also affected but not reported yet)

(Yes, I still think it would be worthy to fix this in bullseye,
for posterity and before it becomes LTS).

Thanks.

Bug#1040375: marked as done (/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 14:50:03 +
with message-id 
and subject line Bug#1040375: fixed in simplescreenrecorder 0.4.4-4
has caused the Debian Bug report #1040375,
regarding /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: 
Segmentation fault when used with anything
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.)


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

Package: simplescreenrecorder-lib
Version: 0.4.4-3
Severity: grave
File: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so
Justification: renders package unusable
X-Debbugs-Cc: alanas...@mail.ru

Dear Maintainer,

   * What led up to the situation?
Trying to "Record OpenGL" in simplescreenrecorder.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so 
/usr/bin/true
   * What was the outcome of this action?
Segmentation fault
   * What outcome did you expect instead?
/usr/bin/true exits with 0 status code.

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

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

Versions of packages simplescreenrecorder-lib:amd64 depends on:
ii  libc6   2.36-9
ii  libgcc-s1   12.2.0-14
ii  libglu1-mesa [libglu1]  9.0.2-1.1
ii  libopengl0  1.6.0-1
ii  libstdc++6  12.2.0-14
ii  libx11-62:1.8.4-2+deb12u1
ii  libxfixes3  1:6.0.0-2

simplescreenrecorder-lib:amd64 recommends no packages.

simplescreenrecorder-lib:amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: simplescreenrecorder
Source-Version: 0.4.4-4
Done: Petter Reinholdtsen 

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

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

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated simplescreenrecorder 
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, 07 May 2024 16:20:28 +0200
Source: simplescreenrecorder
Architecture: source
Version: 0.4.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Petter Reinholdtsen 
Closes: 1040375
Changes:
 simplescreenrecorder (0.4.4-4) unstable; urgency=medium
 .
   * Reordered patches according to classfication in README.
   * Fixed typo in 1020-appstream-metadata-category.patch.
   * Extended build rule to validate appstream metadata during build.
   * Renamed build dependencies libgl1-mesa-dev->libgl-dev and
 pkg-config->pkgconf on lintians request.
   * Added 0010-plthook.patch from upstream to fix segfault in 
libssr-glinject.so
 (Closes: #1040375).
   * Updated Standards-Version from 4.6.2 to 4.7.0.
   * Extended Appstream validator step and fix all issues reported.
Checksums-Sha1:
 8b90d18d0f3c71f60dfe96637f394572bbd701ae 2631 simplescreenrecorder_0.4.4-4.dsc
 a7c3e2de27b43a2eb339419402a4bf6b2d370e09 26980 
simplescreenrecorder_0.4.4-4.debian.tar.xz
 d6405cb94d2ac4e8213d4822027155a95f05fb35 16110 
simplescreenrecorder_0.4.4-4_source.buildinfo
Checksums-Sha256:
 db02e47e511e2087c13b39dbaeead4954702c546af01a4aae8482858f2fdb26d 2631 
simplescreenrecorder_0.4.4-4.dsc
 a1f725267c6778eaad6d813ce47a1c5b18295960cac99607f3a82a3b986c084c 26980 
simplescreenrecorder_0.4.4-4.debian.tar.xz
 6f8f295ed6d458a34668ecf12cdb23799225ca0a6e5e87111e3b00d6892956ae 16110 
simplescreenrecorder_0.4.4-4_source.buildinfo
Files:
 408fb0e0df7e0864293fb699a04b3c71 2631 video optional 
simplescreenrecorder_0.4.4-4.dsc
 c59d3266eebc6f14a0b53dc806d859cd 26980 video optional 

Bug#1070706: gtk4 - udebs broken.

[Peter Michael Green]

Package: gtk4
Version: 4.12.5+dfsg-6
Severity: serious

According to britney, gtk4's udebs are uninstallable.

 * ∙ ∙ libgtk-4-1-udeb/amd64 has unsatisfiable dependency
 * ∙ ∙ libgtk-4-1-udeb/arm64 has unsatisfiable dependency
 * ∙ ∙ libgtk-4-1-udeb/i386 has unsatisfiable dependency
 * ∙ ∙ libgtk-4-1-udeb/mips64el has unsatisfiable dependency
 * ∙ ∙ libgtk-4-1-udeb/ppc64el has unsatisfiable dependency
 * ∙ ∙ libgtk-4-1-udeb/s390x has unsatisfiable dependency
 * ∙ ∙ migrating libgtk-4-1-udeb/4.12.5+ds-6/amd64 to testing makes
   libvte-2.91-0-udeb/0.75.92-1/amd64
    uninstallable
 * ∙ ∙ migrating libgtk-4-1-udeb/4.12.5+ds-6/arm64 to testing makes
   libvte-2.91-0-udeb/0.75.92-1/arm64
    uninstallable
 * ∙ ∙ migrating libgtk-4-1-udeb/4.12.5+ds-6/i386 to testing makes
   libvte-2.91-0-udeb/0.75.92-1/i386
    uninstallable
 * ∙ ∙ migrating libgtk-4-1-udeb/4.12.5+ds-6/mips64el to testing makes
   libvte-2.91-0-udeb/0.75.92-1/mips64el
    uninstallable
 * ∙ ∙ migrating libgtk-4-1-udeb/4.12.5+ds-6/ppc64el to testing makes
   libvte-2.91-0-udeb/0.75.92-1/ppc64el
    uninstallable
 * ∙ ∙ migrating libgtk-4-1-udeb/4.12.5+ds-6/s390x to testing makes
   libvte-2.91-0-udeb/0.75.92-1/s390x
    uninstallable


This is preventing gtk4 migrating to testing which is leaving many
packages uninstallable in testing on time64 architectures.

Bug#1040375: marked as pending in simplescreenrecorder

[Petter Reinholdtsen]

Control: tag -1 pending

Hello,

Bug #1040375 in simplescreenrecorder 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/simplescreenrecorder/-/commit/469d4dff951437e022d39bff10e9c4a3cbf8a0d4


Added 0010-plthook.patch from upstream to fix segfault in libssr-glinject.so.

Closes: #1040375


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040375

Processed: Bug#1040375 marked as pending in simplescreenrecorder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040375 [simplescreenrecorder-lib] 
/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation 
fault when used with anything
Ignoring request to alter tags of bug #1040375 to the same tags previously set

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

Processed: Re: Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/taf2/curb/issues/451
Bug #1069258 [src:ruby-curb] ruby-curb: test regression with curl 8.7.1: client 
read function EOF fail, only only 4/5 of needed bytes read
Set Bug forwarded-to-address to 'https://github.com/taf2/curb/issues/451'.

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

Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

[Lucas Nussbaum]

Control: forwarded -1 https://github.com/taf2/curb/issues/451

Hi,

I forwarded this upstream.

Lucas

Processed: librnd: NMU diff for 64-bit time_t transition

[Debian Bug Tracking System]

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

> severity 1062610 serious
Bug #1062610 {Done: Benjamin Drung } [src:librnd] librnd: 
NMU diff for 64-bit time_t transition
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1070491: marked as done (rust-pipewire FTBFS on 32bit with 64bit time_t)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 13:34:23 +
with message-id 
and subject line Bug#1070491: fixed in rust-pipewire 0.8.0-5
has caused the Debian Bug report #1070491,
regarding rust-pipewire FTBFS on 32bit with 64bit time_t
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.)


-- 
1070491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-pipewire
Version: 0.8.0-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=rust-pipewire=0.8.0-4

...
error[E0308]: mismatched types
   --> src/thread_loop.rs:142:43
|
142 | nix::sys::time::TimeSpec::new(abstime.tv_sec, abstime.tv_nsec)
| - ^^ expected `i64`, 
found `i32`
| |
| arguments to this function are incorrect
|
note: associated function defined here
   --> /usr/share/cargo/registry/nix-0.27.1/src/sys/time.rs:339:18
|
339 | pub const fn new(seconds: time_t, nanoseconds: timespec_tv_nsec_t) -> 
Self {
|  ^^^
help: you can convert an `i32` to an `i64`
|
142 | nix::sys::time::TimeSpec::new(abstime.tv_sec.into(), 
abstime.tv_nsec)
| +++

error[E0308]: mismatched types
   --> src/thread_loop.rs:152:25
|
152 | tv_sec: abstime.tv_sec(),
|  expected `i32`, found `i64`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `pipewire` (lib) due to 2 previous errors
...
--- End Message ---
--- Begin Message ---
Source: rust-pipewire
Source-Version: 0.8.0-5
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-pipewire 
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, 07 May 2024 01:51:01 +
Source: rust-pipewire
Architecture: source
Version: 0.8.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1070491
Changes:
 rust-pipewire (0.8.0-5) unstable; urgency=medium
 .
   * Team upload.
   * Package pipewire 0.8.0 from crates.io using debcargo 2.6.1
   * Fix build on time64 architectures (Closes: #1070491)
 + Depend on version of bindgen that enables time64 flags.
 + Use mem::zeroed to create timespec structures to avoid problems caused
   by padding fields.
Checksums-Sha1:
 88d5794be6c4c180e3cab66a4e250abf3a83476e 2791 rust-pipewire_0.8.0-5.dsc
 20f5e8f7c824ea3d97b205b5219372d1abe684e0 4396 
rust-pipewire_0.8.0-5.debian.tar.xz
 e066f4864a41f864ad4358b0dd3453dca3c56786 13796 
rust-pipewire_0.8.0-5_source.buildinfo
Checksums-Sha256:
 5bfe95269cd18a784d833386902a16ee89eff7143a0f785f61a6ca629820fc9f 2791 
rust-pipewire_0.8.0-5.dsc
 37594fda4b455fb17b7ee7286c027500851fca3c3ee3029d5ea43dbd43894767 4396 
rust-pipewire_0.8.0-5.debian.tar.xz
 e1f4f5c4583b897d47f19a0be87738ef1f0672c6a6095a57d006313f4f63e532 13796 
rust-pipewire_0.8.0-5_source.buildinfo
Files:
 55c80a59a1a81ea916e305fa1e32041e 2791 rust optional rust-pipewire_0.8.0-5.dsc
 a1d85f001d969f2503e3fbaf4a8814b6 4396 rust optional 
rust-pipewire_0.8.0-5.debian.tar.xz
 8a4d8352f31b7ce0e4970c52ea122941 13796 rust optional 
rust-pipewire_0.8.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmY6KYoUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvUiA//eC1MJb9loBGgIwXnyDtjsbjIkr9A
pOarN/WyOOHMnsAmu5cSlPcXkxMhul+a/NPHnPRSOPN1Pk2sIlyyGu8uuFqzXLXI
wtWJoLRn47bR+mk410eI7EbIShXsYiFiudfOEzKHZiJGKMB+e005nLjBOyg8l7B/
P6irllBCFJzU9CACd9iatow+LXpA8hPB6LlmMbWTabm9DtcKXHIHOPJgQh/IFg4K
0/sKZjcxj5YiJRvf+zl+WBO1xm3XvMQNXD/p4G13bxQIcxaCFkLS5HSb9+66v+aV
E3jq9WiKM0v1zKYYlv/ApTtLbMEwMlmmO0sFTmnN722PbDJLNz5UsyJEQvgOje4/
OKepbfXqxh4nzx1H7uCJrrYdU6q0IPeGBX8IAjQ3GjhxqkGSLGgiJGFaR74ykxKM

Bug#1069372: marked as done (efibootguard: FTBFS on arm64: kernel-stub/fdt.c:169:49: error: passing argument 2 of ‘CopyMem’ discards ‘const’ qualifier from pointer target type [-Werror=discarded-quali

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 13:19:03 +
with message-id 
and subject line Bug#1069372: fixed in efibootguard 0.17-1
has caused the Debian Bug report #1069372,
regarding efibootguard: FTBFS on arm64: kernel-stub/fdt.c:169:49: error: 
passing argument 2 of ‘CopyMem’ discards ‘const’ qualifier from pointer target 
type [-Werror=discarded-qualifiers]
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.)


-- 
1069372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: efibootguard
Version: 0.16-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> make --no-print-directory all-recursive
> Making all in .
> set -e; echo '  CHK  version.h'; mkdir -p ./; ./gen_version_h ./ < 
> Makefile.in > version.h.tmp; if [ -r version.h ] && cmp -s version.h 
> version.h.tmp; then rm -f version.h.tmp; else echo '  UPD  version.h'; mv 
> -f version.h.tmp version.h; fi
>   CHK  version.h
> /usr/bin/mkdir -p completion/bash; PYTHONPATH=./completion/shtab:./completion 
> /usr/bin/python3 -m shtab -u --shell=bash bg_setenv.cli.bg_setenv 
> >completion/bash/bg_setenv.bash
>   UPD  version.h
> /usr/bin/mkdir -p completion/bash; PYTHONPATH=./completion/shtab:./completion 
> /usr/bin/python3 -m shtab -u --shell=bash bg_printenv.cli.bg_printenv 
> >completion/bash/bg_printenv.bash
> /usr/bin/mkdir -p drivers/watchdog/; gcc -I. -include config.h -I./include 
> -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 
> -I/usr/include/aarch64-linux-gnu  -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic 
> -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare 
> -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -fno-stack-protector  -c 
> drivers/watchdog/init_array_start.S -o drivers/watchdog/init_array_start.o
> /usr/bin/mkdir -p drivers/watchdog/; gcc -I. -include config.h -I./include 
> -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 
> -I/usr/include/aarch64-linux-gnu  -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic 
> -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare 
> -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -fno-stack-protector  -c 
> drivers/watchdog/init_array_end.S -o drivers/watchdog/init_array_end.o
> /usr/bin/mkdir -p env/; gcc -I. -include config.h -I./include -I/usr/include 
> -I/usr/include/efi -I/usr/include/efi/aarch64 
> -I/usr/include/aarch64-linux-gnu  -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic 
> -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare 
> -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -fno-stack-protector  -c 
> env/syspart.c -o env/syspart.o
> /usr/bin/mkdir -p env/; gcc -I. -include config.h -I./include -I/usr/include 
> -I/usr/include/efi -I/usr/include/efi/aarch64 
> -I/usr/include/aarch64-linux-gnu  -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic 
> -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare 
> -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -fno-stack-protector  -c 
> env/fatvars.c -o env/fatvars.o
> /usr/bin/mkdir -p ./; gcc -I. -include config.h -I./include -I/usr/include 
> -I/usr/include/efi -I/usr/include/efi/aarch64 
> -I/usr/include/aarch64-linux-gnu  -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic 
> -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare 
> -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -fno-stack-protector  -c 
> utils.c -o utils.o
> 

Processed: Mark gnat time_t/64 as notfound where necessary

[Debian Bug Tracking System]

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

> notfound 1067224 ahven/2.8-9
Bug #1067224 {Done: Nicolas Boulenguez } [src:ahven] 
libahven ftbfs on time_t64 architectures
No longer marked as found in versions ahven/2.8-9.
> notfound 1067071 libaunit/24.0.0-2
Bug #1067071 {Done: Nicolas Boulenguez } [src:libaunit] 
lubaunit: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : 
a-calend.adb:371 overflow check failed
No longer marked as found in versions libaunit/24.0.0-2.
> thanks
Stopping processing here.

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

Bug#1070699: gdb can not be started on testing

[Michael Becker]

Package: gdb
Version: 13.2-1+b1
Severity: grave
Justification: renders package unusable

mmediately stops with the error:

gdb: symbol lookup error: /lib/x86_64-linux-gnu/libpython3.11.so.1.0: undefined 
symbol: XML_SetReparseDeferralEnabled

libpython3.11.so.1.0 is part of libpython3.11t64


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

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

Versions of packages gdb depends on:
ii  libbabeltrace1   1.5.11-3+b6
ii  libc62.38-7
ii  libdebuginfod1t640.191-1+b1
ii  libexpat12.6.2-1
ii  libgcc-s114-20240330-1
ii  libgmp10 2:6.3.0+dfsg-2+b1
ii  libipt2  2.0.6-1
ii  liblzma5 5.6.1+really5.4.5-1
ii  libmpfr6 4.2.1-1+b1
ii  libncursesw6 6.4+20240414-1
ii  libpython3.11t64 3.11.9-1
ii  libreadline8t64  8.2-4
ii  libsource-highlight4t64  3.1.9-4.3
ii  libstdc++6   14-20240330-1
ii  libtinfo66.4+20240414-1
ii  libxxhash0   0.8.2-2+b1
ii  libzstd1 1.5.5+dfsg2-2
ii  zlib1g   1:1.3.dfsg-3.1

Versions of packages gdb recommends:
ii  libc6-dbg [libc-dbg]  2.38-7

Versions of packages gdb suggests:
pn  gdb-doc
pn  gdbserver  

-- no debconf information

Processed: Re: Processed: Re: Bug#1068349: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean

[Debian Bug Tracking System]

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

> fixed 1068349 nbconvert/6.5.3-5
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml 
5.2: lxml.html.clean
Marked as fixed in versions nbconvert/6.5.3-5.
> thanks
Stopping processing here.

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

Bug#1066624: xfireworks: FTBFS: etc.c:11:19: error: implicit declaration of function ‘time’ [-Werror=implicit-function-declaration]

[Yukiharu YABUKI]

Hi,

Thanks for your comment. I'll try to enable
-Werror=implicit-function-declaratin

On Wed, 13 Mar 2024 12:58:32 +0100
Lucas Nussbaum  wrote:

[snip]
> This is most likely caused by a change in dpkg 1.22.6, that enabled
> -Werror=implicit-function-declaration. For more information, see
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
> 
> Relevant part (hopefully):
> > cc -c arguments.c -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
> > etc.c: In function ‘InitializeRand’:
> > etc.c:11:19: error: implicit declaration of function ‘time’ 
> > [-Werror=implicit-function-declaration]
> >11 |   srand((unsigned)time(NULL));
> >   |   ^~~~
> > etc.c:2:1: note: ‘time’ is defined in header ‘’; did you forget to 
> > ‘#include ’?
> > 1 | #include "etc.h"
> >   +++ |+#include 
> > 2 | 
> > cat xfireworks.1 | gzip -9 > xfireworks.6.gz
> > gzip: warning: GZIP environment variable is deprecated; use an alias or 
> > script
> > cat xfireworks.conf | ./mkconf > xfireworks_conf.h
> > cc -c XFireworks.c -I/usr/X11R6/include -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> > -O2 -Werror=implicit-function-declaration 
> > -ffile-prefix-map=/<>=. -fstack-protector-strong 
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> > cc1: some warnings being treated as errors
> > make[1]: *** [Makefile:73: etc.o] Error 1
[snip]

--
Yukiharu YABUKI 

Bug#1068349: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean

[Vincent Lefevre]

Control: reopen -1

On 2024-05-07 11:25:05 +0200, Vincent Lefevre wrote:
> What's the status of this bug?
> 
> apt-listbugs still reports python3-lxml as buggy:
> 
> serious bugs of python3-lxml (5.1.0-1 → 5.2.1-1) 
>  b1 - #1068349 - nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean 
> (Fixed: nbconvert/6.5.3-5)
> Summary:
>  python3-lxml(1 bug)
> 
> Indeed, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068349
> says: "Found in versions nbconvert/6.5.3-4, lxml/5.2.1-1".
> 
> So python3-lxml 5.2.1-1 is regarded as buggy.

And this bug prevents the migration to testing:

https://tracker.debian.org/pkg/lxml

testing migrations
[...]
Issues preventing migration:
∙ ∙ Updating lxml would introduce bugs in testing: #1068349

It seems that this bug (assigned to 2 different packages) has been
closed by mistake, due to the fix of nbconvert:

Format: 1.8
Date: Sun, 14 Apr 2024 16:52:34 +0100
Source: nbconvert
Architecture: source
Version: 6.5.3-5
[...]
Closes: 1042699 1068349
[...]
   * (Build-)depend on python3-lxml-html-clean (closes: #1068349).

But this is inconsistent with the fact that lxml is still marked as
unfixed. So, reopening.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#1068349: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1068349 {Done: Colin Watson } 
[python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml 5.2: 
lxml.html.clean
'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 nbconvert/6.5.3-5.

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

Bug#1070638: marked as done (kde-spectacle: Build-depends on NBS libkcolorpicker-dev)

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 11:05:29 +
with message-id 
and subject line Bug#1070638: fixed in kde-spectacle 23.08.5-2
has caused the Debian Bug report #1070638,
regarding kde-spectacle: Build-depends on NBS libkcolorpicker-dev
to be marked as done.

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

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


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

Once kcolorpicker is decrufted, this package will FTBFS.  Please update
your build-depends.

Scott K
--- End Message ---
--- Begin Message ---
Source: kde-spectacle
Source-Version: 23.08.5-2
Done: Patrick Franz 

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

Debian distribution maintenance software
pp.
Patrick Franz  (supplier of updated kde-spectacle 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, 07 May 2024 12:45:49 +0200
Source: kde-spectacle
Architecture: source
Version: 23.08.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Patrick Franz 
Closes: 1070638
Changes:
 kde-spectacle (23.08.5-2) unstable; urgency=medium
 .
   [ Patrick Franz ]
   * Team upload.
   * Update B-Ds for kcolorpicker and kimageannotator to the new explicit
 Qt 5 packages (Closes: #1070638).
Checksums-Sha1:
 df7933f58f274c0460e1b2b6e5b26680a77c2bcd 3309 kde-spectacle_23.08.5-2.dsc
 cdef3d9e2b7fb6ff28b820c6c21f491aeec98144 13288 
kde-spectacle_23.08.5-2.debian.tar.xz
 9c4418a090209f36da4caee1fda97682e9d64f84 14678 
kde-spectacle_23.08.5-2_source.buildinfo
Checksums-Sha256:
 722da131beab98129e4fe0cecfcf5046b5775531ca1567031df0d28c910522ee 3309 
kde-spectacle_23.08.5-2.dsc
 4e816121997fc92e21d34d2703d88f42e628ce313b95cae3cd298ca97141c41a 13288 
kde-spectacle_23.08.5-2.debian.tar.xz
 d5a56b98a7c7d713d1c4a75cb7a90e6a8fb2d935df23945b17e91fa85daeae8e 14678 
kde-spectacle_23.08.5-2_source.buildinfo
Files:
 30448fefaa9b1463e141601d4446ce34 3309 kde optional kde-spectacle_23.08.5-2.dsc
 4424ad6010cbc48213a89db0ebbdb483 13288 kde optional 
kde-spectacle_23.08.5-2.debian.tar.xz
 275504493419a0f459bb1eb0969d2d66 14678 kde optional 
kde-spectacle_23.08.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmY6BpEACgkQnp96YDB3
/laAyg//QAAh33EshP/K5vZefd/Kiq5PNShzR5/zMe1H5Z9I0wZiOwHf/hDH5qC/
PIWKSKDahgcTMKly0FJtOGFeFGxComOWdiZujnKkOUrYtC8tTnLmwtHrK+9ydbAU
iQVCcXk0V33mA5VMgtq//VMJ1HvwadCLt0GiWoSd/7ehOYmlGcnt9/J5sic8te9z
CpeklqxmHqGUgt2ABhlA8Kaj62XUJLErP6ycAa3nee7V17e+NKMx6nIcV+dwNt7t
MCdAPSek3olpJIQRRuURgQABtr+YcMh7Zy8Abp4702I5G8a6CA5OviLPwiNaI7KV
uU9/BzAQU4xquST0aFhurBh4e43MH205/+nBKTfOlsTx4VGC5gelcgvGHs6OXHJ5
rIf6kHVT8j49XU4NftJELkYOFw9tSWSh/auZMyQ3jPHFuqOW6i5RWxAGQ4+NVQrI
Wno1KL54iCRpJqERf8JuV2XDye11l8rcFoDc3ZDJuSZYbqfwquxmG3NLgzhwb7X5
eNI7NT4/x/9e6OTnPzma/EQCBSVk6JuAPIjx4xsg8d/6JyMOMHn1R8GanPYp+9vM
ybXX9U5ZhSKGRaB++WtyoZgAKA4GIX7E1CXzJv2L9WBJ9oH8YBv4hRVbzwt0KIsN
CySq65T3iVGuTxdbYIVSwfYhq9fN1vovgKB4+kj5RP5pwmoLlA0=
=FUQ/
-END PGP SIGNATURE-



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

Processed: Re: Bug#1070515: dipy: FTBFS with nocheck profile

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1070515 [src:dipy] dipy: FTBFS with nocheck profile
Added tag(s) help.

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

Bug#1070515: dipy: FTBFS with nocheck profile

[Andreas Tille]

Control: tags -1 help
thanks

Hi Grahamm

Am Mon, May 06, 2024 at 02:08:25PM + schrieb Graham Inggs:
> Source: dipy
> Version: 1.8.0-2
> Severity: serious
> Tags: ftbfs patch

thanks a lot for the patch which looks perfectly sensible.  Unfortunatly
the build runs into a different error as you can see in Salsa CI[1]:

=== FAILURES ===
__ test_shore_fitting_no_constrain_e0 __
def test_shore_fitting_no_constrain_e0():
>   asm = ShoreModel(data.gtab, radial_order=data.radial_order,
 zeta=data.zeta, lambdaN=data.lambdaN,
 lambdaL=data.lambdaL)
E   AttributeError: '_C' object has no attribute 'radial_order'
dipy/reconst/tests/test_shore.py:70: AttributeError


Any help would be welcome
  Andreas.

[1] https://salsa.debian.org/med-team/dipy/-/pipelines/674858

-- 
https://fam-tille.de

Processed: found 1070690 in 1:1.14.19-1, severity of 1070690 is serious

[Debian Bug Tracking System]

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

> found 1070690 1:1.14.19-1
Bug #1070690 [libupnp-dev] libupnp-dev: pkgconfig file no longer carries 
version information
Marked as found in versions pupnp/1:1.14.19-1.
> severity 1070690 serious
Bug #1070690 [libupnp-dev] libupnp-dev: pkgconfig file no longer carries 
version information
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1066211:

[Matthew Danish]

Thanks, this is very timely, I was just discussing it with upstream a
couple days ago.


On Mon, 6 May 2024 at 23:39, Arvin Sedererdj  wrote:

> Control: tags -1 + patch
>
>
>

Processed: update status for Ada time_t 64 bugs

[Debian Bug Tracking System]

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

> notfound 1067070 adacgi/1.6-34
Bug #1067070 {Done: Nicolas Boulenguez } [src:adacgi] 
adacgi: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : 
a-calend.adb:371 overflow check failed
Bug #1067219 {Done: Nicolas Boulenguez } [src:adacgi] 
adacgi ftbfs on time_t64 architectures
No longer marked as found in versions adacgi/1.6-34.
No longer marked as found in versions adacgi/1.6-34.
> notfound 1067071 libanuti/24.0.0-2
Bug #1067071 {Done: Nicolas Boulenguez } [src:libaunit] 
lubaunit: FTBFS on arm{el,hf}: gprbuild: raised CONSTRAINT_ERROR : 
a-calend.adb:371 overflow check failed
The source libanuti and version 24.0.0-2 do not appear to match any binary 
packages
Ignoring request to alter found versions of bug #1067071 to the same values 
previously set
> notfound 1067073 libncursesada/6.3.20211021-11
Bug #1067073 {Done: Nicolas Boulenguez } 
[src:libncursesada] libncursesada: FTBFS on arm{el,hf}: gprbuild: raised 
CONSTRAINT_ERROR : a-calend.adb:371 overflow check failed
No longer marked as found in versions libncursesada/6.3.20211021-11.
> notfound 1067224 libahven/2.8-9
Bug #1067224 {Done: Nicolas Boulenguez } [src:ahven] 
libahven ftbfs on time_t64 architectures
The source libahven and version 2.8-9 do not appear to match any binary packages
Ignoring request to alter found versions of bug #1067224 to the same values 
previously set
> notfound 1069421 dbusada/0.6.2-6
Bug #1069421 {Done: Nicolas Boulenguez } [src:dbusada] 
dbusada: FTBFS on armhf: build-dependency not installable: libahven-dev
No longer marked as found in versions dbusada/0.6.2-6.
> notfound 1069454 libalog/0.6.2-5
Bug #1069454 {Done: Nicolas Boulenguez } [src:libalog] 
libalog: FTBFS on armhf: build-dependency not installable: libahven-dev
No longer marked as found in versions libalog/0.6.2-5.
> notfound 1069468 pcscada/0.7.7-6
Bug #1069468 {Done: Nicolas Boulenguez } [src:pcscada] 
pcscada: FTBFS on armhf: build-dependency not installable: libahven-dev
No longer marked as found in versions pcscada/0.7.7-6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1067070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067070
1067071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067071
1067073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067073
1067219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067219
1067224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067224
1069421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069421
1069454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069454
1069468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1068349: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean

[Vincent Lefevre]

On 2024-04-07 22:06:05 +0100, Rebecca N. Palmer wrote:
> To avoid being blocked by this bug, the pandas version I just uploaded
> temporarily disables the documentation.
> 
> This is also an option for any other affected packages that urgently need to
> be uploaded.  (I don't know whether the other two listed Blocks/Affects are
> that urgent.)

What's the status of this bug?

apt-listbugs still reports python3-lxml as buggy:

serious bugs of python3-lxml (5.1.0-1 → 5.2.1-1) 
 b1 - #1068349 - nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean (Fixed: 
nbconvert/6.5.3-5)
Summary:
 python3-lxml(1 bug)

Indeed, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068349
says: "Found in versions nbconvert/6.5.3-4, lxml/5.2.1-1".

So python3-lxml 5.2.1-1 is regarded as buggy.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1069370: shasta: FTBFS: dpkg-shlibdeps: error: cannot continue due to the error above

[Andreas Tille]

Control: tags -1 help

Hi,

I pushed some potential fix to Git but this does not help[1]. :-(

Any idea is welcome
   Andreas.


[1] https://salsa.debian.org/med-team/shasta/-/jobs/5695708

-- 
https://fam-tille.de

Processed: Re: Bug#1069370: shasta: FTBFS: dpkg-shlibdeps: error: cannot continue due to the error above

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1069370 [src:shasta] shasta: FTBFS: dpkg-shlibdeps: error: cannot find 
library shasta.cpython-311-aarch64-linux-gnu.so needed by 
debian/shasta/usr/bin/shasta
Added tag(s) help.

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

Processed: found 1069552 in 1.0.21-13

[Debian Bug Tracking System]

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

> found 1069552 1.0.21-13
Bug #1069552 [src:freecontact] freecontact: FTBFS on armel: make[1]: *** 
[Makefile:469: all-recursive] Error 1
Marked as found in versions freecontact/1.0.21-13.
> thanks
Stopping processing here.

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

Bug#1070652: marked as done (how-can-i-help: explicitly require 'ostruct')

[Debian Bug Tracking System]

Your message dated Tue, 07 May 2024 08:34:38 +
with message-id 
and subject line Bug#1070652: fixed in how-can-i-help 18
has caused the Debian Bug report #1070652,
regarding how-can-i-help: explicitly require 'ostruct'
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.)


-- 
1070652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-json
Version: 2.7.2+dfsg-1
Severity: grave
Justification: renders package unusable

This new ruby-json version breaks how-can-i-help:

[...]
Unpacking ruby-json:amd64 (2.7.2+dfsg-1) over (2.6.3+dfsg-1+b2) ...
Setting up ruby-json:amd64 (2.7.2+dfsg-1) ...
/usr/bin/how-can-i-help:155:in `': uninitialized constant OpenStruct 
(NameError)

proxy_uri = $proxy_url.nil? ? OpenStruct.new : URI.parse($proxy_url)
  ^^

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

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

Versions of packages ruby-json depends on:
ii  libc6  2.38-7
ii  libruby1:3.1+nmu1
ii  libruby3.1t64  3.1.2-8.3

ruby-json recommends no packages.

ruby-json suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: how-can-i-help
Source-Version: 18
Done: Lucas Nussbaum 

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

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated how-can-i-help 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, 07 May 2024 10:15:00 +0200
Source: how-can-i-help
Architecture: source
Version: 18
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Nitecki 
Changed-By: Lucas Nussbaum 
Closes: 1069108 1070652
Changes:
 how-can-i-help (18) unstable; urgency=medium
 .
   [ Paul Wise ]
   * Always build the manual page from source
   * Do not print the autorm header when all autorm items are hidden
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.6.1, no changes needed.
   * Use debhelper execute_after_* instead of override_
   * Update standards version to 4.6.2, no changes needed.
 .
   [ Athos Ribeiro ]
   * {Dir,File}.exists? were removed from Ruby 3.2. Use .exist? instead.
 Closes: #1069108
 .
   [ Lucas Nussbaum ]
   * Explicitly require ostruct. Closes: #1070652
 + Thanks Vincent Lefevre for the report, and Cédric Boutillier
   for the fix.
   * Add missing build-dep on docbook-xml
Checksums-Sha1:
 eef5c3adb8ed4b8fac9ddc8539884e3a2008c94f 1704 how-can-i-help_18.dsc
 66c33b2687bad5f0eacf8183255727603ca09cbf 11184 how-can-i-help_18.tar.xz
 84327c1b03de20c370b60fb1dc558cd7726b9801 13158 
how-can-i-help_18_source.buildinfo
Checksums-Sha256:
 8f88d7bd11e9814a7b35f5bf0d2976d885d3e969cc00b2893b6fdbfa859c3a93 1704 
how-can-i-help_18.dsc
 66c07fcc7f1a3d6b57a4bdfb7e7ff9854de653d9236c63726feb6d9ee7b5fdc4 11184 
how-can-i-help_18.tar.xz
 bf3638b48ad3a6b02c79950eec92484053e08819d24e0f7a9181c37d68236171 13158 
how-can-i-help_18_source.buildinfo
Files:
 a81cf09fda303e3dbd3ee4ddc3491e17 1704 devel optional how-can-i-help_18.dsc
 96034af8276b797c12fbe9c205b4d4d1 11184 devel optional how-can-i-help_18.tar.xz
 792ee81dacdf07489f9e91c9668dc9f6 13158 devel optional 

Processed: Tagging help

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1070459 [src:psortb] psortb: FTBFS: binding.c:52:13: error: implicit 
declaration of function ‘free’
Added tag(s) help.

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

Bug#1070459: Tagging help

[Andreas Tille]

Control: tags -1 help
thanks

Bug#1070020: autopkgtest: (unrelated) packages not found

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Johannes Schauer Marin Rodrigues (2024-04-28 19:34:07)
> unfortunately, this problem is not transient but reproducible. The problem
> is, that the involved libraries which are 404 have alternative 64bit time_t
> versions in unstable:
> 
> libssl3 -> libssl3t64
> libdb5.3 -> libdb5.3t64
> libgdbm6 -> libgdbm6t64
> libgdbm-compat4 -> libgdbm-compat4t64
> 
> And apt chooses to satisfy the (virtual) dependencies on those differently,
> depending on the surrounding dependency satisfaction problem. Related,
> debootstrap is also broken by the virtual providers of libssl3: #1069787
> 
> Feel free to tell the release team to ignore these failures if necessary.
> They will go away once the 64bit time_t transition is finished.

do you agree that there is nothing for mmdebstrap to do here? If yes, could you
close this bug?

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything

[Petter Reinholdtsen]

[Bernhard Übelacker]
> As far as I see the crash happens because it wants to print this message:
>
> 57  GLINJECT_PRINT("Error: Can't open libdl.so!");
>
> But unfortunately libstdc++ seems not yet prepared to output the
> error.

Thank you very much for the analysis and links.  I applied the upstream
patch to the Debian package build, and it sure seem to fix the
segfault.  Will need to do some more testing, and will upload a fixed
package later.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1070677: fail2ban fails: "Failed during configuration: Have not found any log file for sshd jail"

[Sylvestre Ledru]

Le 07/05/2024 à 03:57, Vincent Lefevre a écrit :

On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:

May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban   
 [557228]: ERROR   Failed during configuration: Have not found any 
log file for sshd jail

I suppose that this is because sshd no longer uses the systemd
backend. This is wrong. If I understand correctly, the point of

https://github.com/fail2ban/fail2ban/issues/3292#issuecomment-2078361360

is to no longer use the systemd backend for all jails, but for
sshd only. So "backend = systemd" has been removed from DEFAULT,
but the above comment also points to

https://github.com/fail2ban/fail2ban/commit/85a4881a9a818b6a746109f74980919296eedad0

which adds for DEFAULT in paths-debian.conf:


banaction = nftables
banaction_allports = nftables[type=allports]

sshd_backend = systemd


But paths-debian.conf has not changed in the fail2ban 1.1.0-1 package.


ok, thanks.

Any idea what the fix should be? I am a bit lost in this conversation :/

Thanks

S