Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

[Vincent Lefevre]

Package: firmware-misc-nonfree
Version: 20230625-1
Severity: grave
Justification: renders package unusable

firmware-misc-nonfree triggers the following warnings:

update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for module 
r8152
W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/hs_bl_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/hs_bl_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/hs_bl_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/hs_bl_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/desc.bin for 
module nouveau

while https://forums.debian.net/viewtopic.php?t=155793 says that
the solution is to install firmware-misc-nonfree!

And I get in the journalctl output:

Dec 19 04:02:54 qaa kernel: [ cut here ]
Dec 19 04:02:54 qaa kernel: nouveau :01:00.0: timeout
Dec 19 04:02:54 qaa kernel: WARNING: CPU: 7 PID: 1347 at 
drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1792 
gf100_gr_init_ctxctl_ext+0x555/0x570 [nouveau]
Dec 19 04:02:54 qaa kernel: Modules linked in: cmac algif_hash algif_skcipher 
af_alg snd_hda_codec_hdmi qrtr bnep binfmt_misc snd_sof_pci_intel_tgl 
snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation 
snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp intel_uncore_frequency snd_sof intel_uncore_frequency_common 
snd_sof_utils snd_soc_hdac_hda x86_pkg_temp_thermal snd_hda_ext_core 
intel_powerclamp snd_soc_acpi_intel_match btusb snd_soc_acpi coretemp 
snd_ctl_led btrtl snd_soc_core iwlmvm snd_hda_codec_realtek btbcm snd_compress 
btintel 

Processed: slepc4py 3.19

[Debian Bug Tracking System]

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

> block 1057863 by 1058944
Bug #1057863 [src:slepc4py] slepc4py ftbfs with Python 3.12
1057863 was not blocked by any bugs.
1057863 was not blocking any bugs.
Added blocking bug(s) of 1057863: 1058944
> thanks
Stopping processing here.

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

Processed: Re: Bug#1052939: marked as done (lsp-mode: FTBFS: make: *** [debian/rules:4: binary] Error 25)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1052939 {Done: Arto Jantunen } [src:lsp-mode] lsp-mode: 
FTBFS: make: *** [debian/rules:4: binary] Error 25
'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 lsp-mode/8.0.0-6.
> found -1 8.0.0-6
Bug #1052939 [src:lsp-mode] lsp-mode: FTBFS: make: *** [debian/rules:4: binary] 
Error 25
Marked as found in versions lsp-mode/8.0.0-6.

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

Bug#1052939: marked as done (lsp-mode: FTBFS: make: *** [debian/rules:4: binary] Error 25)

[Xiyue Deng]

Control: reopen -1
Control: found -1 8.0.0-6

It looks like the attempted fix in 8.0.0-6 is not reliable and still
fails in ppc64el[1] and s390x[2].  I'm working on a better fix which
is also forwarded upstream.

[1] https://ci.debian.net/packages/l/lsp-mode/testing/ppc64el/40221847/
[2] https://ci.debian.net/packages/l/lsp-mode/testing/s390x/40222364/

-- 
Xiyue Deng


signature.asc
Description: PGP signature

Processed: postfix: diff for NMU version 3.8.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1054485 + patch
Bug #1054485 [src:postfix] postfix: installs a systemd unit twice when 
dh_installsystemd installs below /usr
Ignoring request to alter tags of bug #1054485 to the same tags previously set
> tags 1054485 + pending
Bug #1054485 [src:postfix] postfix: installs a systemd unit twice when 
dh_installsystemd installs below /usr
Added tag(s) pending.

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

Bug#1054485: postfix: diff for NMU version 3.8.2-1.1

[Chris Hofstaedtler]

Control: tags 1054485 + patch
Control: tags 1054485 + pending

Dear maintainer,

I've prepared an NMU for postfix (versioned as 3.8.2-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer. Better, upload yourself in the meantime.

Best,
Chris

diff -Nru postfix-3.8.2/debian/changelog postfix-3.8.2/debian/changelog
--- postfix-3.8.2/debian/changelog	2023-09-14 20:08:10.0 +0200
+++ postfix-3.8.2/debian/changelog	2023-12-19 01:24:10.0 +0100
@@ -1,3 +1,13 @@
+postfix (3.8.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [Helmut Grohne]
+
+  * Install units using dh_installsystemd only. (Closes: #1054485)
+
+ -- Chris Hofstaedtler   Tue, 19 Dec 2023 01:24:10 +0100
+
 postfix (3.8.2-1) unstable; urgency=medium
 
   [Scott Kitterman]
diff -Nru postfix-3.8.2/debian/postfix.dirs postfix-3.8.2/debian/postfix.dirs
--- postfix-3.8.2/debian/postfix.dirs	2023-09-14 19:53:19.0 +0200
+++ postfix-3.8.2/debian/postfix.dirs	2023-12-19 01:23:16.0 +0100
@@ -34,5 +34,4 @@
 var/spool/postfix/usr/lib/sasl2
 var/log
 var/lib/postfix
-lib/systemd/system
 lib/systemd/system-generators
diff -Nru postfix-3.8.2/debian/postfix.postfix-resolvconf.path postfix-3.8.2/debian/postfix.postfix-resolvconf.path
--- postfix-3.8.2/debian/postfix.postfix-resolvconf.path	1970-01-01 01:00:00.0 +0100
+++ postfix-3.8.2/debian/postfix.postfix-resolvconf.path	2023-12-19 01:23:16.0 +0100
@@ -0,0 +1,11 @@
+[Unit]
+Description=Watch for resolv.conf updates and restart postfix
+ConditionPathExists=/etc/resolv.conf
+
+[Path]
+PathChanged=/etc/resolv.conf
+Unit=postfix-resolvconf.service
+
+[Install]
+WantedBy=multi-user.target
+
diff -Nru postfix-3.8.2/debian/postfix.postfix-resolvconf.service postfix-3.8.2/debian/postfix.postfix-resolvconf.service
--- postfix-3.8.2/debian/postfix.postfix-resolvconf.service	1970-01-01 01:00:00.0 +0100
+++ postfix-3.8.2/debian/postfix.postfix-resolvconf.service	2023-12-19 01:23:16.0 +0100
@@ -0,0 +1,9 @@
+[Unit]
+Description=Copies updated resolv.conf to postfix chroot and restarts postfix.
+
+[Service]
+Type=simple
+ExecStart=/etc/resolvconf/update-libc.d/postfix
+
+[Install]
+WantedBy=multi-user.target
diff -Nru postfix-3.8.2/debian/postfix-resolvconf.path postfix-3.8.2/debian/postfix-resolvconf.path
--- postfix-3.8.2/debian/postfix-resolvconf.path	2023-09-14 19:53:19.0 +0200
+++ postfix-3.8.2/debian/postfix-resolvconf.path	1970-01-01 01:00:00.0 +0100
@@ -1,11 +0,0 @@
-[Unit]
-Description=Watch for resolv.conf updates and restart postfix
-ConditionPathExists=/etc/resolv.conf
-
-[Path]
-PathChanged=/etc/resolv.conf
-Unit=postfix-resolvconf.service
-
-[Install]
-WantedBy=multi-user.target
-
diff -Nru postfix-3.8.2/debian/postfix-resolvconf.service postfix-3.8.2/debian/postfix-resolvconf.service
--- postfix-3.8.2/debian/postfix-resolvconf.service	2023-09-14 19:53:19.0 +0200
+++ postfix-3.8.2/debian/postfix-resolvconf.service	1970-01-01 01:00:00.0 +0100
@@ -1,9 +0,0 @@
-[Unit]
-Description=Copies updated resolv.conf to postfix chroot and restarts postfix.
-
-[Service]
-Type=simple
-ExecStart=/etc/resolvconf/update-libc.d/postfix
-
-[Install]
-WantedBy=multi-user.target
diff -Nru postfix-3.8.2/debian/rules postfix-3.8.2/debian/rules
--- postfix-3.8.2/debian/rules	2023-09-14 19:53:19.0 +0200
+++ postfix-3.8.2/debian/rules	2023-12-19 01:23:16.0 +0100
@@ -193,8 +193,6 @@
 
 	install debian/configure-instance.sh $(libdir)
 	install debian/postfix-instance-generator ${base}/lib/systemd/system-generators/
-	install -m 644 debian/postfix@.service ${base}/lib/systemd/system/
-	install -m 644 debian/postfix-resolvconf.* ${base}/lib/systemd/system/
 	install debian/ip-up.d ${base}/etc/ppp/ip-up.d/postfix
 	install debian/ip-down.d ${base}/etc/ppp/ip-down.d/postfix
 	install debian/ip-up.d ${base}/etc/network/if-up.d/postfix
@@ -209,8 +207,7 @@
 	fi
 
 override_dh_installsystemd:
-	dh_installsystemd -p postfix --no-enable --no-start postfix-resolvconf.path
-	dh_installsystemd -p postfix --no-enable --no-start postfix-resolvconf.service
+	dh_installsystemd -p postfix --no-enable --no-start --name postfix-resolvconf
 	dh_installsystemd -p postfix --no-restart-after-upgrade postfix.service
 
 execute_before_dh_gencontrol:

Bug#1058849: marked as done (linphone FTBFS with zxing-cpp 2.2.1)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 23:56:29 +
with message-id 
and subject line Bug#1058849: fixed in linphone 5.2.0-4.1
has caused the Debian Bug report #1058849,
regarding linphone FTBFS with zxing-cpp 2.2.1
to be marked as done.

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

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


-- 
1058849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linphone
Version: 5.2.0-4
Severity: serious
Tags: ftbfs
Forwarded: 
https://gitlab.linphone.org/BC/public/liblinphone/-/commit/5cff6f87a82cea59041869a6d1ed391921ab589d

https://buildd.debian.org/status/logs.php?pkg=linphone=5.2.0-4%2Bb1

...
In file included from /usr/include/ZXing/Flags.h:8,
 from /usr/include/ZXing/BarcodeFormat.h:9,
 from /<>/src/factory/factory.cpp:25:
/usr/include/ZXing/BitHacks.h:37:55: error: ‘is_integral_v’ is not a member of 
‘std’; did you mean ‘is_integral’?
   37 | template>>
  |   ^
  |   is_integral
...
--- End Message ---
--- Begin Message ---
Source: linphone
Source-Version: 5.2.0-4.1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated linphone package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Dec 2023 11:31:05 -0500
Source: linphone
Architecture: source
Version: 5.2.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Boyuan Yang 
Closes: 1058849
Changes:
 linphone (5.2.0-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/use-cxx17-standard.patch: Build the whole project
 with C++17 instead of C++14 due to new requirement from zxing-cpp
 headers. (Closes: #1058849)
Checksums-Sha1:
 35b7e22c11196caf55b968ad3a38c7e341811f49 2881 linphone_5.2.0-4.1.dsc
 f3547cfc0f8950b83d1701de5c58b066e175a284 22850117 linphone_5.2.0.orig.tar.gz
 6ce98cd555bdb64a5f20bad9428ff50834edc1d3 36500 linphone_5.2.0-4.1.debian.tar.xz
 b1165c93d7319094da4d922b77f2e2eccdfa1e30 15773 
linphone_5.2.0-4.1_amd64.buildinfo
Checksums-Sha256:
 82e868d2005df661404cee9490a1f8012a689361bacfd3f46e0632e7bdfa167d 2881 
linphone_5.2.0-4.1.dsc
 daefa50e2b4e777f46be5c7793bdb5aa12b28af8b415a8b71699fc88b0d47b7e 22850117 
linphone_5.2.0.orig.tar.gz
 1abb4a9e5dc8385a89a10813cf50a9ef48d94901878bf6be9dadf263d40f5a6c 36500 
linphone_5.2.0-4.1.debian.tar.xz
 e10a03eba524fac6d2f0bc32a119b692e7cd313d18bd23601afeedaafbb330df 15773 
linphone_5.2.0-4.1_amd64.buildinfo
Files:
 80648cafc0ca44f97a9f98db0368f3ca 2881 sound optional linphone_5.2.0-4.1.dsc
 ae889786caad1715463f0a8916e97171 22850117 sound optional 
linphone_5.2.0.orig.tar.gz
 c0d916bde02659b6da9c7d7cd57014c4 36500 sound optional 
linphone_5.2.0-4.1.debian.tar.xz
 1ee6e7676cda741b10f74ac3eaedb184 15773 sound optional 
linphone_5.2.0-4.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmV/JbsACgkQwpPntGGC
Ws6WWRAAkcIXohhpL12D5wKSmw9Ylwsd838sqz7eYP3EHoBZDiIGANfaksYlywCE
cQ33bDo/Rmc0dNWQmyQ0hMyCrshkJFgEHIgPSQrQ63v4m3LL1arwkOpaUCvGa0hC
SXfSV8qglk/bCccYm/JNrUkpghUT9trQY/tndvPcV1AVShesnOIvmN2v9PMh4jyz
9TJWEAy5D5o/mQU2SZ7LyZu1M/bfuGWehtGwPD2tImElKcZJ9T5WqFqYRAk3qSUH
zTmXKhWfIMWtoZYkT78xS4Lc8DYdEjbx6+r5S1sA95dCsmHEc/bXSRqmmx+gNzBD
QLgQgn6sLOr/v/osjNkxzhbJJhqBd5X9Jy0ntL5R2TTDju8irYrWP6+e3AChMrMh
s8uRXDLj79Mel6wizfXbVzY48UEr5Y4TfG/XSAxcKWfXywS2dmssbOpQ5zaNDFOz
iFNbJy/mwR4UmOuuSeHa0GrYIGCBkcOFNARi7reYBaIj3ItwZrybwA7ZjFcqAp9d
zHoSJCVebk1wXyysy/7qo6dqTXRt+w5qwwBYi+Fth0Jr7jR1u0nWua8OxNH8vypq
o9y9BoZ5/1AYUvrldRXfQxcGuPUL8sPHN51CFEKTQxY1ECOXol8ljlyvjj+P6wma
HzcGvNeAh2EfXqbgtvFmViVYybw5+RdrNGrB+0a7mOa5zIj4Ikw=
=lziA
-END PGP SIGNATURE End Message ---

Bug#1058908: marked as done (plasma-workspace 4:5.27.10-1 loses appstream and breeze support)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 23:13:44 +
with message-id 
and subject line Bug#1058908: fixed in plasma-workspace 4:5.27.10-2
has caused the Debian Bug report #1058908,
regarding plasma-workspace 4:5.27.10-1 loses appstream and breeze support
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.)


-- 
1058908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-workspace
Version: 4:5.27.10-1
Severity: serious
X-Debbugs-Cc: Matthias Klumpp 

https://buildd.debian.org/status/fetch.php?pkg=plasma-workspace=amd64=4%3A5.27.10-1=1702876241=0

...
CMake Warning at CMakeLists.txt:99 (find_package):
  Could not find a configuration file for package "Breeze" that is compatible
  with requested version "5.27.10".

  The following configuration files were considered but not accepted:

/usr/lib/x86_64-linux-gnu/cmake/Breeze/BreezeConfig.cmake, version: 5.27.9
/lib/x86_64-linux-gnu/cmake/Breeze/BreezeConfig.cmake, version: 5.27.9
...
CMake Warning at CMakeLists.txt:186 (find_package):
  Could not find a configuration file for package "AppStreamQt5" that is
  compatible with requested version "0.10.6".

  The following configuration files were considered but not accepted:

/usr/lib/x86_64-linux-gnu/cmake/AppStreamQt5/AppStreamQt5Config.cmake, 
version: 1.0.1
/lib/x86_64-linux-gnu/cmake/AppStreamQt5/AppStreamQt5Config.cmake, version: 
1.0.1
...
-- The following OPTIONAL packages have not been found:

 * Breeze (required version >= 5.27.10)
   For setting the default window decoration plugin
 * AppStreamQt5 (required version >= 0.10.6), Access metadata for listing 
available software, 
...
--- End Message ---
--- Begin Message ---
Source: plasma-workspace
Source-Version: 4:5.27.10-2
Done: Matthias Klumpp 

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated plasma-workspace package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Dec 2023 22:12:28 +0100
Source: plasma-workspace
Architecture: source
Version: 4:5.27.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Matthias Klumpp 
Closes: 1058908
Changes:
 plasma-workspace (4:5.27.10-2) unstable; urgency=medium
 .
   * Update AppStream 1.0 compat patch
   * Tighten build-dep on breeze-dev (Closes: #1058908)
Checksums-Sha1:
 6ae6598e975bf462c33e1792a78c9df3dfe8496b 5966 plasma-workspace_5.27.10-2.dsc
 d1bdd066a6b8f87d795c55bf04911557319b22ba 19476860 
plasma-workspace_5.27.10.orig.tar.xz
 bbb4491f6b7f8de9299ac46a53f3ec234685eb90 833 
plasma-workspace_5.27.10.orig.tar.xz.asc
 3098c208fa27b93a159c9d9fa0d89ea1fe9beec4 55040 
plasma-workspace_5.27.10-2.debian.tar.xz
 5a0e117c4ce9c2338f32dd42703f4e85e5e2ecc3 31557 
plasma-workspace_5.27.10-2_source.buildinfo
Checksums-Sha256:
 afb09120df265b7b2e364fea95d5d14b5493e65a5db375257eba5beccc1f0d6e 5966 
plasma-workspace_5.27.10-2.dsc
 525dc164c61a6730f33d54ff5013d57184b9d671786fe898ca7e054426359778 19476860 
plasma-workspace_5.27.10.orig.tar.xz
 8ca9e2ffec5682ff753669359a4912cf334e1fc24ab9f70876841e3b3d9f3c11 833 
plasma-workspace_5.27.10.orig.tar.xz.asc
 0433cd0565acbee13f6abdb7e8b782295832d8c002d47b05fa071af1b2cbbd48 55040 
plasma-workspace_5.27.10-2.debian.tar.xz
 325b97da5412b31a254defd26286fc545ff578a72ab67b22997fdaaeb1107954 31557 
plasma-workspace_5.27.10-2_source.buildinfo
Files:
 fac0a29aba6df698256da304a91d465b 5966 kde optional 
plasma-workspace_5.27.10-2.dsc
 5c2ff5158503e983207e700ce513e929 19476860 kde optional 
plasma-workspace_5.27.10.orig.tar.xz
 075271f7642a6295f706f0f7eddaa8b0 833 kde optional 
plasma-workspace_5.27.10.orig.tar.xz.asc
 03d03380dabe79922eeece27f6b0a20f 55040 kde optional 
plasma-workspace_5.27.10-2.debian.tar.xz
 5f2c21e5201b087ca8829e52d27b1d91 31557 kde optional 
plasma-workspace_5.27.10-2_source.buildinfo

-BEGIN PGP 

Processed: tagging 1056017

[Debian Bug Tracking System]

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

> tags 1056017 + trixie sid
Bug #1056017 [src:rlvm] rlvm: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: severity of 1055973 is serious

[Debian Bug Tracking System]

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

> severity 1055973 serious
Bug #1055973 [src:wesnoth-1.16] wesnoth: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 1056017 is serious

[Debian Bug Tracking System]

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

> severity 1056017 serious
Bug #1056017 [src:rlvm] rlvm: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 1056076

[Debian Bug Tracking System]

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

> tags 1056076 + trixie sid
Bug #1056076 [src:laserboy] laserboy: FTBFS: boost1.83 transition
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Processed: severity of 1056076 is serious

[Debian Bug Tracking System]

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

> severity 1056076 serious
Bug #1056076 [src:laserboy] laserboy: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1057921 https://github.com/OfflineIMAP/offlineimap3/pull/171
Bug #1057921 [offlineimap] offlineimap: NameError: name 'fcntl' is not defined
Set Bug forwarded-to-address to 
'https://github.com/OfflineIMAP/offlineimap3/pull/171'.
> --
Stopping processing here.

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

Processed: tagging 1056077

[Debian Bug Tracking System]

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

> tags 1056077 + trixie sid
Bug #1056077 [src:heaptrack] heaptrack: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: tagging 1056079

[Debian Bug Tracking System]

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

> tags 1056079 + trixie sid
Bug #1056079 [src:graph-tool] graph-tool: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: severity of 1056077 is serious

[Debian Bug Tracking System]

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

> severity 1056077 serious
Bug #1056077 [src:heaptrack] heaptrack: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 1056079 is serious

[Debian Bug Tracking System]

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

> severity 1056079 serious
Bug #1056079 [src:graph-tool] graph-tool: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 1056093

[Debian Bug Tracking System]

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

> tags 1056093 + trixie sid
Bug #1056093 [src:casparcg-server] casparcg-server: FTBFS: boost1.83 transition
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Processed: severity of 1056093 is serious

[Debian Bug Tracking System]

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

> severity 1056093 serious
Bug #1056093 [src:casparcg-server] casparcg-server: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 1056081

[Debian Bug Tracking System]

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

> tags 1056081 + trixie sid
Bug #1056081 [src:fife] fife: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: severity of 1056080 is serious

[Debian Bug Tracking System]

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

> severity 1056080 serious
Bug #1056080 [src:flightcrew] flightcrew: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 1056081 is serious

[Debian Bug Tracking System]

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

> severity 1056081 serious
Bug #1056081 [src:fife] fife: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 1056080

[Debian Bug Tracking System]

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

> tags 1056080 + trixie sid
Bug #1056080 [src:flightcrew] flightcrew: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1056486: Info received (python-mpegdash's autopkg tests fail with Python 3.12)

[Alexandre Detiste]

The patch submitted upstream also removes extraneous unittest2

https://github.com/sangwonl/python-mpegdash/pull/61/files

Processed: tagging 1056486

[Debian Bug Tracking System]

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

> tags 1056486 + patch
Bug #1056486 [src:python-mpegdash] python-mpegdash's autopkg tests fail with 
Python 3.12
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: severity of 1037437 is serious, tagging 1037437

[Debian Bug Tracking System]

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

> severity 1037437 serious
Bug #1037437 [fail2ban] From fresh bookworm install default sshd jail in 
fail2ban won’t work without rsyslog installed
Severity set to 'serious' from 'normal'
> tags 1037437 + bookworm sid trixie
Bug #1037437 [fail2ban] From fresh bookworm install default sshd jail in 
fail2ban won’t work without rsyslog installed
Added tag(s) bookworm, trixie, and sid.
> thanks
Stopping processing here.

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

Bug#1056486: python-mpegdash's autopkg tests fail with Python 3.12

[Alexandre Detiste]

here is a patch that removes extraneous import of future library
& most likely solves this bug
diff --git a/debian/control b/debian/control
index c3fa5b6..12b2535 100644
--- a/debian/control
+++ b/debian/control
@@ -8,8 +8,7 @@ Build-Depends: debhelper-compat (= 13),
dh-python,
python3-all,
python3-setuptools,
-Build-Depends-Indep: python3-future,
- python3-unittest2,
+Build-Depends-Indep: python3-unittest2,
 Standards-Version: 4.6.0
 Homepage: https://github.com/sangwonl/python-mpegdash
 Vcs-Browser: https://salsa.debian.org/python-team/packages/python-mpegdash
diff --git a/mpegdash/utils.py b/mpegdash/utils.py
index 4d7b828..7a08a91 100644
--- a/mpegdash/utils.py
+++ b/mpegdash/utils.py
@@ -1,4 +1,3 @@
-from past.builtins import unicode   # python3 compat
 from xml.dom import minidom
 
 import re
@@ -19,7 +18,7 @@ def parse_child_nodes(xmlnode, tag_name, node_type):
 
 nodes = []
 for elem in elements:
-if node_type in (unicode, str):
+if node_type is str:
 node = xmlnode.firstChild.nodeValue
 else:
 node = node_type()
diff --git a/requirements.txt b/requirements.txt
index 2c6edea..e69de29 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1 +0,0 @@
-future
diff --git a/setup.py b/setup.py
index 20b593d..2db676d 100644
--- a/setup.py
+++ b/setup.py
@@ -17,7 +17,6 @@ setup(
   license="MIT",
   zip_safe=False,
   include_package_data=True,
-  install_requires=["future"],
   url="https://github.com/sangwonl/python-mpegdash;,
   tests_require=["unittest2"],
   test_suite="tests.my_module_suite",

Bug#993014: marked as done (cifs-utils non-parallel FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:33 +
with message-id 
and subject line Bug#993014: fixed in cifs-utils 2:6.11-3.1+deb11u2
has caused the Debian Bug report #993014,
regarding cifs-utils non-parallel FTBFS
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.)


-- 
993014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cifs-utils
Version: 2:6.11-3.1
Severity: serious
Tags: ftbfs


cifs-utils fails to build from source when including parallel=1 in
DEB_BUILD_OPTIONS. A failing build ends with:

| dh_auto_install
| make -j1 install DESTDIR=/<>/debian/cifs-utils 
AM_UPDATE_INFO_DIR=no
| make[2]: Entering directory '/<>'
| Making install in contrib
| make[3]: Entering directory '/<>/contrib'
| Making install in request-key.d
| make[4]: Entering directory '/<>/contrib/request-key.d'
| make[5]: Entering directory '/<>/contrib/request-key.d'
| make[5]: Nothing to be done for 'install-exec-am'.
| make[5]: Nothing to be done for 'install-data-am'.
| make[5]: Leaving directory '/<>/contrib/request-key.d'
| make[4]: Leaving directory '/<>/contrib/request-key.d'
| make[4]: Entering directory '/<>/contrib'
| make[5]: Entering directory '/<>/contrib'
| make[5]: Nothing to be done for 'install-exec-am'.
| make[5]: Nothing to be done for 'install-data-am'.
| make[5]: Leaving directory '/<>/contrib'
| make[4]: Leaving directory '/<>/contrib'
| make[3]: Leaving directory '/<>/contrib'
| make[3]: Entering directory '/<>'
| make[4]: Entering directory '/<>'
|  /bin/mkdir -p '/<>/debian/cifs-utils/usr/bin'
|   /usr/bin/install -c cifscreds getcifsacl setcifsacl smbinfo 
'/<>/debian/cifs-utils/usr/bin'
|  /bin/mkdir -p '/<>/debian/cifs-utils/usr/bin'
|  /usr/bin/install -c smb2-quota '/<>/debian/cifs-utils/usr/bin'
|  /bin/mkdir -p '/<>/debian/cifs-utils/usr/sbin'
|   /usr/bin/install -c cifs.upcall cifs.idmap 
'/<>/debian/cifs-utils/usr/sbin'
| make  install-exec-hook
| make[5]: Entering directory '/<>'
| (cd /<>/debian/cifs-utils/sbin && ln -sf mount.cifs mount.smb3)
| /bin/bash: line 1: cd: /<>/debian/cifs-utils/sbin: No such file 
or directory
| make[5]: *** [Makefile:1506: install-exec-hook] Error 1
| make[5]: Leaving directory '/<>'
| make[4]: *** [Makefile:1385: install-exec-am] Error 2
| make[4]: Leaving directory '/<>'
| make[3]: *** [Makefile:1307: install-am] Error 2
| make[3]: Leaving directory '/<>'
| make[2]: *** [Makefile:998: install-recursive] Error 1
| make[2]: Leaving directory '/<>'
| dh_auto_install: error: make -j1 install 
DESTDIR=/<>/debian/cifs-utils AM_UPDATE_INFO_DIR=no returned exit 
code 2
| make[1]: *** [debian/rules:13: override_dh_auto_install-arch] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:6: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

I suppose that some ordering relation in the makefile is missing and a
parallel build creates the relevant directory quickly enough. In a
parallel=1 build, the race is lost reliably.

Helmut
--- End Message ---
--- Begin Message ---
Source: cifs-utils
Source-Version: 2:6.11-3.1+deb11u2
Done: Michael Tokarev 

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated cifs-utils 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: Sat, 27 Aug 2022 02:20:00 +0200
Source: cifs-utils
Architecture: source
Version: 2:6.11-3.1+deb11u2
Distribution: bullseye
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Michael Tokarev 
Closes: 993014
Changes:
 cifs-utils (2:6.11-3.1+deb11u2) bullseye; urgency=medium
 .
   * Fix non-parallel build. Closes: #993014.
Checksums-Sha1:
 71c8833b5a271cf5c6aa911adf1e59e49ad1d0b2 2174 cifs-utils_6.11-3.1+deb11u2.dsc
 290f2734209739c28cc0fd701437765fd24edf83 16348 
cifs-utils_6.11-3.1+deb11u2.debian.tar.xz
 a4c06407b0fd84a211d702e5fa2e6cf9cbdf579f 6794 

Bug#991066: marked as done (vlfeat FTBFS with imagemagick with the #987504 change)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:45 +
with message-id 
and subject line Bug#991066: fixed in vlfeat 0.9.21+dfsg0-6+deb11u1
has caused the Debian Bug report #991066,
regarding vlfeat FTBFS with imagemagick with the #987504 change
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.)


-- 
991066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vlfeat
Version: 0.9.21+dfsg0-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/vlfeat.html

...
CONVERT doc/figures/cell-bins.png
"convert" -units PixelsPerInch -density 95 -resample 95 -trim 
"doc/build/figures/cell-bins.pdf" "doc/figures/cell-bins.png"
convert-im6.q16: attempt to perform an operation not allowed by the security 
policy `PDF' @ error/constitute.c/IsCoderAuthorized/408.
convert-im6.q16: no images defined `doc/figures/cell-bins.png' @ 
error/convert.c/ConvertImageCommand/3258.
make[2]: *** [make/doc.mak:213: doc/figures/cell-bins.png] Error 1


See #987504 for background.

The Ubuntu diff (linked from tracker.debian.org) seems to contain a fix.
--- End Message ---
--- Begin Message ---
Source: vlfeat
Source-Version: 0.9.21+dfsg0-6+deb11u1
Done: Santiago Vila 

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated vlfeat 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, 12 Dec 2023 21:30:00 +0100
Source: vlfeat
Architecture: source
Version: 0.9.21+dfsg0-6+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Santiago Vila 
Closes: 991066
Changes:
 vlfeat (0.9.21+dfsg0-6+deb11u1) bullseye; urgency=medium
 .
   * Team upload.
   * Apply patch by Dennis Filder to fix build error. Closes: #991066.
Checksums-Sha1:
 5fa1e36932b6941d2ea5c3ad29ea364a712b877a 1963 vlfeat_0.9.21+dfsg0-6+deb11u1.dsc
 733deb49a828192d16943602758f2ef92e9a1b1c 25040 
vlfeat_0.9.21+dfsg0-6+deb11u1.debian.tar.xz
 c500b7d65c2541fb76162d0e4756d105a3be169f 21651 
vlfeat_0.9.21+dfsg0-6+deb11u1_source.buildinfo
Checksums-Sha256:
 6357d0e27c8eb33309fc9cebc0e4ad296c6111a93dbf2a7d6cbe83d1b4e59b73 1963 
vlfeat_0.9.21+dfsg0-6+deb11u1.dsc
 2e90cb82f1eafe897a4ad1d8b0499c7067ab045fd776e0f17eff3126c88d3ca8 25040 
vlfeat_0.9.21+dfsg0-6+deb11u1.debian.tar.xz
 0c2b64c09c5ee2860656e944e985670a8bd62c3c2f50efce191f530a5dec1b7e 21651 
vlfeat_0.9.21+dfsg0-6+deb11u1_source.buildinfo
Files:
 88c5efe0fecab20cea2af0e31d344714 1963 science optional 
vlfeat_0.9.21+dfsg0-6+deb11u1.dsc
 1878c791c27f7c98f32a493da473d94c 25040 science optional 
vlfeat_0.9.21+dfsg0-6+deb11u1.debian.tar.xz
 742b905d2fdaac8badda96a7033c5a8b 21651 science optional 
vlfeat_0.9.21+dfsg0-6+deb11u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmV4xdsACgkQQc5/C58b
izJneQgAlKgl30SpSiOz5jK5eawuQ/J+y/d5uw+5ZXexEGQKUVBD7CKbVr0PoDun
yRn58gl2dOqzurGpagG+uu4XKAzFexUS16TMs8sJjg/GG4zSXSqtLiYT4V7afOWd
QE2iaVftGO9ju+GnVMub3SvJKp6IJU1EOYUJrDRz95KR5zoXM4AuGyk0WKLKlN7X
r4CYhrHUROY6CTGGRtNjsbTtWfkeM3b3QbyqHjVnwHmwf05N1rCosifTWGgijkUe
xwFphF5M0KhHZrkNfWEfVjOEW7rBddsVSi4ZBA0d5LCjjnvoynI4N0rHuMY1g+cB
oXWLvs61Gi0vqUYISuSHgyx1VX6Vng==
=iz37
-END PGP SIGNATURE End Message ---

Bug#976506: marked as done (conda-package-handling: FTBFS in bullseye (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:33 +
with message-id 
and subject line Bug#976506: fixed in conda-package-handling 1.7.2-2+deb11u1
has caused the Debian Bug report #976506,
regarding conda-package-handling: FTBFS in bullseye (failing tests)
to be marked as done.

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

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


-- 
976506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: conda-package-handling
Version: 1.7.2-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package conda-package-handling
> dpkg-buildpackage: info: source version 1.7.2-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Nilesh Patra 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture arm64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: 
> Cython directive 'language_level' not set, using 2 for now (Py2). This will 
> change in a later release! File: 
> /<>/src/conda_package_handling/archive_utils_cy.pyx
>   tree = Parsing.p_module(s, pxd, full_module_name)
> Compiling src/conda_package_handling/archive_utils_cy.pyx because it changed.
> [1/1] Cythonizing src/conda_package_handling/archive_utils_cy.pyx
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under 
> it)
> 'build/bdist.linux-arm64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building conda-package-handling using existing 
> ./conda-package-handling_1.7.2.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building conda-package-handling in 
> conda-package-handling_1.7.2-1.debian.tar.xz
> dpkg-source: info: building conda-package-handling in 
> conda-package-handling_1.7.2-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config 
> /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:369: FutureWarning: 
> Cython directive 'language_level' not set, using 2 for now (Py2). This will 
> change in a later release! File: 
> /<>/src/conda_package_handling/archive_utils_cy.pyx
>   tree = Parsing.p_module(s, pxd, full_module_name)
> Compiling src/conda_package_handling/archive_utils_cy.pyx because it changed.
> [1/1] Cythonizing src/conda_package_handling/archive_utils_cy.pyx
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/tarball.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/utils.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/api.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/exceptions.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/__main__.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/cli.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/conda_fmt.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/interface.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/_version.py -> 
> /<>/.pybuild/cpython3_3.9/build/conda_package_handling
> copying src/conda_package_handling/validate.py 

Bug#1055142: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2023-31022)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:44 +
with message-id 
and subject line Bug#1055142: fixed in nvidia-graphics-drivers-tesla-470 
470.223.02-2~deb11u1
has caused the Debian Bug report #1055142,
regarding nvidia-graphics-drivers-tesla-470: CVE-2023-31022
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.)


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

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

CVE-2023-31022  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where a NULL-pointer
dereference may lead to denial of service.

Linux Driver Branch CVE IDs Addressed
R545, R535, R525, R470  CVE-2023-31022

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R545All driver versions prior to 545.29.02  545.29.02
R535All driver versions prior to 535.129.03 535.129.03
R525All driver versions prior to 525.147.05 525.147.05
R470All driver versions prior to 470.223.02 470.223.02


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.223.02-2~deb11u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 13:31:00 +0100
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.223.02-2~deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1052069 1055136 1055142 1055503 1057078
Changes:
 nvidia-graphics-drivers-tesla-470 (470.223.02-2~deb11u1) bullseye; 
urgency=medium
 .
   * Rebuild for bullseye.
 

Bug#1055136: marked as done (nvidia-graphics-drivers: CVE-2023-31022)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:44 +
with message-id 
and subject line Bug#1055136: fixed in nvidia-graphics-drivers-tesla-470 
470.223.02-2~deb11u1
has caused the Debian Bug report #1055136,
regarding nvidia-graphics-drivers: CVE-2023-31022
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.)


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

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

CVE-2023-31022  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where a NULL-pointer
dereference may lead to denial of service.

Linux Driver Branch CVE IDs Addressed
R545, R535, R525, R470  CVE-2023-31022

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R545All driver versions prior to 545.29.02  545.29.02
R535All driver versions prior to 535.129.03 535.129.03
R525All driver versions prior to 525.147.05 525.147.05
R470All driver versions prior to 470.223.02 470.223.02


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.223.02-2~deb11u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 13:31:00 +0100
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.223.02-2~deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1052069 1055136 1055142 1055503 1057078
Changes:
 nvidia-graphics-drivers-tesla-470 (470.223.02-2~deb11u1) bullseye; 
urgency=medium
 .
   * Rebuild for bullseye.
 .
 

Bug#1055136: marked as done (nvidia-graphics-drivers: CVE-2023-31022)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:42 +
with message-id 
and subject line Bug#1055136: fixed in nvidia-graphics-drivers 470.223.02-1
has caused the Debian Bug report #1055136,
regarding nvidia-graphics-drivers: CVE-2023-31022
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.)


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

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

CVE-2023-31022  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where a NULL-pointer
dereference may lead to denial of service.

Linux Driver Branch CVE IDs Addressed
R545, R535, R525, R470  CVE-2023-31022

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R545All driver versions prior to 545.29.02  545.29.02
R535All driver versions prior to 535.129.03 535.129.03
R525All driver versions prior to 525.147.05 525.147.05
R470All driver versions prior to 470.223.02 470.223.02


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 470.223.02-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Fri, 17 Nov 2023 17:38:12 +0100
Source: nvidia-graphics-drivers
Architecture: source
Version: 470.223.02-1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1052069 1055136 1055503
Changes:
 nvidia-graphics-drivers (470.223.02-1) bullseye; urgency=medium
 .
   * New upstream long term support branch release 470.223.02 (2023-10-31).
 * Fixed CVE-2023-31022.  (Closes: #1055136)
   

Bug#1051889: marked as done (freeimage: CVE-2020-22524)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:34 +
with message-id 
and subject line Bug#1051889: fixed in freeimage 3.18.0+ds2-6+deb11u1
has caused the Debian Bug report #1051889,
regarding freeimage: CVE-2020-22524
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.)


-- 
1051889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeimage
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for freeimage.

CVE-2020-22524[0]:
| Buffer Overflow vulnerability in FreeImage_Load function in
| FreeImage Library 3.19.0(r1828) allows attackers to cuase a denial
| of service via crafted PFM file.

https://sourceforge.net/p/freeimage/bugs/319/
Fixed with r1848 from http://svn.code.sf.net/p/freeimage/svn/FreeImage/


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-2020-22524
https://www.cve.org/CVERecord?id=CVE-2020-22524

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: freeimage
Source-Version: 3.18.0+ds2-6+deb11u1
Done: Moritz Mühlenhoff 

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

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated freeimage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Dec 2023 20:11:17 +0100
Source: freeimage
Architecture: source
Version: 3.18.0+ds2-6+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Moritz Mühlenhoff 
Closes: 1051737 1051738 1051889
Changes:
 freeimage (3.18.0+ds2-6+deb11u1) bullseye-security; urgency=medium
 .
   * CVE-2020-21427 (Closes: #1051737)
   * CVE-2020-21428 (Closes: #1051738)
   * CVE-2020-22524 (Closes: #1051889)
Checksums-Sha1:
 1e04a04fdd0d68e8fefe9daf3c2b246829dcf27e 2572 
freeimage_3.18.0+ds2-6+deb11u1.dsc
 5c5f67837bd03cb2be596eb66d6edae735a4370d 1281524 
freeimage_3.18.0+ds2.orig.tar.xz
 dee1afb63e26e4488b654d60fdc60cf4d40e4856 27796 
freeimage_3.18.0+ds2-6+deb11u1.debian.tar.xz
 8e905e099f32b1053388abd44e85d9a575dee53d 9366 
freeimage_3.18.0+ds2-6+deb11u1_amd64.buildinfo
Checksums-Sha256:
 f983ea41debd44869c57f1794cd818d03e2c3bb1937f9480ec55ec9426175ece 2572 
freeimage_3.18.0+ds2-6+deb11u1.dsc
 4425d04d4691084260848d67eb79949ea7c129d85c73a72066ba609fd3f3aa39 1281524 
freeimage_3.18.0+ds2.orig.tar.xz
 6f374291f14e45972c7a207bdf5331d8ae3c51b780385c7685ec70e925df2078 27796 
freeimage_3.18.0+ds2-6+deb11u1.debian.tar.xz
 2e579f39b0c8508a22f64cc2c45aae2387754a6d86f060cc2e7c094992841067 9366 
freeimage_3.18.0+ds2-6+deb11u1_amd64.buildinfo
Files:
 abbc1dc7ed84a9b3a7257418f950b351 2572 libs optional 
freeimage_3.18.0+ds2-6+deb11u1.dsc
 bf8d7f34b419266773255855aadfd808 1281524 libs optional 
freeimage_3.18.0+ds2.orig.tar.xz
 1789567e7e6eb75d459f3d3e8c007fa9 27796 libs optional 
freeimage_3.18.0+ds2-6+deb11u1.debian.tar.xz
 48c7d7669004c5c42fa752f82ed72f90 9366 libs optional 
freeimage_3.18.0+ds2-6+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmV8p6oACgkQEMKTtsN8
TjaW3w//WGzCZIYlLHHJFo1FfIi6sMso3nLMrGjgbcWCggLaAeff6hPFhJdOOinH
0D9gUzMpN/3THLzV3q5DkXydqotGrL7GyhzZkkXfmj9y6z3MG174BBsuAqhEUpNw
06VESaqYbADUMxIWJ2iEHVp2zb4tGf376FqjJF/MLhEWiGN0sT+aR72UC5HcQAH+
YMYGyzRV6X+L1OneVlehogjretO4YboCESKm7OEMAG7R+Ijz1PEsGI0UO3RZSecm
N2nz7gELAwwHS2Kib+EAXWStK+CN5yI4TQ2MehKOLQW8s3AsrOvG3NWlqPEekIC0
xJqWh3PlohXGDHhxFTsPAWProW8Fi+TB3yiKJkXP5xXJnICAAJNGjgZ2D/C2Qi3f
eqcKskSvKspKAKGHdlN9T5neZgIVFGdzvU4/ethP56UcJe6ghtglYRs7+cI5IPQP
3MiKN2bIEJQqIxPF3We0NecsVpkGkpbG8a9TQ/S2i25jQIy7a9UTc7Iffsj6vond
rSFcq/LaEhJNYVfuVuMR3REyN17VVv/1ctW5NdZ4+N3d8jv6SexjMZSdF1u9267Q
+drAH73HU/UJVXyJlkTmmSZC8RrmzrutEm7JEJSzAn6ZaP0kNItOWO69xA7BSuQq
DuH4adpk0eIbYfTgKu0/8Vw6sSpUybKXDGSE2r71bkX/SgF92r8=

Bug#1051738: marked as done (freeimage: CVE-2020-21428)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:34 +
with message-id 
and subject line Bug#1051738: fixed in freeimage 3.18.0+ds2-6+deb11u1
has caused the Debian Bug report #1051738,
regarding freeimage: CVE-2020-21428
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.)


-- 
1051738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeimage
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for freeimage.

CVE-2020-21428[0]:
| Buffer Overflow vulnerability in function LoadRGB in PluginDDS.cpp
| in FreeImage 3.18.0 allows remote attackers to run arbitrary code
| and cause other impacts via crafted image file.

https://sourceforge.net/p/freeimage/bugs/299/

This appears to be fixed in r1877 of the upstream Subversion repository

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-2020-21428
https://www.cve.org/CVERecord?id=CVE-2020-21428

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: freeimage
Source-Version: 3.18.0+ds2-6+deb11u1
Done: Moritz Mühlenhoff 

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

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated freeimage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Dec 2023 20:11:17 +0100
Source: freeimage
Architecture: source
Version: 3.18.0+ds2-6+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Moritz Mühlenhoff 
Closes: 1051737 1051738 1051889
Changes:
 freeimage (3.18.0+ds2-6+deb11u1) bullseye-security; urgency=medium
 .
   * CVE-2020-21427 (Closes: #1051737)
   * CVE-2020-21428 (Closes: #1051738)
   * CVE-2020-22524 (Closes: #1051889)
Checksums-Sha1:
 1e04a04fdd0d68e8fefe9daf3c2b246829dcf27e 2572 
freeimage_3.18.0+ds2-6+deb11u1.dsc
 5c5f67837bd03cb2be596eb66d6edae735a4370d 1281524 
freeimage_3.18.0+ds2.orig.tar.xz
 dee1afb63e26e4488b654d60fdc60cf4d40e4856 27796 
freeimage_3.18.0+ds2-6+deb11u1.debian.tar.xz
 8e905e099f32b1053388abd44e85d9a575dee53d 9366 
freeimage_3.18.0+ds2-6+deb11u1_amd64.buildinfo
Checksums-Sha256:
 f983ea41debd44869c57f1794cd818d03e2c3bb1937f9480ec55ec9426175ece 2572 
freeimage_3.18.0+ds2-6+deb11u1.dsc
 4425d04d4691084260848d67eb79949ea7c129d85c73a72066ba609fd3f3aa39 1281524 
freeimage_3.18.0+ds2.orig.tar.xz
 6f374291f14e45972c7a207bdf5331d8ae3c51b780385c7685ec70e925df2078 27796 
freeimage_3.18.0+ds2-6+deb11u1.debian.tar.xz
 2e579f39b0c8508a22f64cc2c45aae2387754a6d86f060cc2e7c094992841067 9366 
freeimage_3.18.0+ds2-6+deb11u1_amd64.buildinfo
Files:
 abbc1dc7ed84a9b3a7257418f950b351 2572 libs optional 
freeimage_3.18.0+ds2-6+deb11u1.dsc
 bf8d7f34b419266773255855aadfd808 1281524 libs optional 
freeimage_3.18.0+ds2.orig.tar.xz
 1789567e7e6eb75d459f3d3e8c007fa9 27796 libs optional 
freeimage_3.18.0+ds2-6+deb11u1.debian.tar.xz
 48c7d7669004c5c42fa752f82ed72f90 9366 libs optional 
freeimage_3.18.0+ds2-6+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmV8p6oACgkQEMKTtsN8
TjaW3w//WGzCZIYlLHHJFo1FfIi6sMso3nLMrGjgbcWCggLaAeff6hPFhJdOOinH
0D9gUzMpN/3THLzV3q5DkXydqotGrL7GyhzZkkXfmj9y6z3MG174BBsuAqhEUpNw
06VESaqYbADUMxIWJ2iEHVp2zb4tGf376FqjJF/MLhEWiGN0sT+aR72UC5HcQAH+
YMYGyzRV6X+L1OneVlehogjretO4YboCESKm7OEMAG7R+Ijz1PEsGI0UO3RZSecm
N2nz7gELAwwHS2Kib+EAXWStK+CN5yI4TQ2MehKOLQW8s3AsrOvG3NWlqPEekIC0
xJqWh3PlohXGDHhxFTsPAWProW8Fi+TB3yiKJkXP5xXJnICAAJNGjgZ2D/C2Qi3f
eqcKskSvKspKAKGHdlN9T5neZgIVFGdzvU4/ethP56UcJe6ghtglYRs7+cI5IPQP
3MiKN2bIEJQqIxPF3We0NecsVpkGkpbG8a9TQ/S2i25jQIy7a9UTc7Iffsj6vond
rSFcq/LaEhJNYVfuVuMR3REyN17VVv/1ctW5NdZ4+N3d8jv6SexjMZSdF1u9267Q
+drAH73HU/UJVXyJlkTmmSZC8RrmzrutEm7JEJSzAn6ZaP0kNItOWO69xA7BSuQq

Bug#1051889: marked as done (freeimage: CVE-2020-22524)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:09 +
with message-id 
and subject line Bug#1051889: fixed in freeimage 3.18.0+ds2-9+deb12u1
has caused the Debian Bug report #1051889,
regarding freeimage: CVE-2020-22524
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.)


-- 
1051889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeimage
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for freeimage.

CVE-2020-22524[0]:
| Buffer Overflow vulnerability in FreeImage_Load function in
| FreeImage Library 3.19.0(r1828) allows attackers to cuase a denial
| of service via crafted PFM file.

https://sourceforge.net/p/freeimage/bugs/319/
Fixed with r1848 from http://svn.code.sf.net/p/freeimage/svn/FreeImage/


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-2020-22524
https://www.cve.org/CVERecord?id=CVE-2020-22524

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: freeimage
Source-Version: 3.18.0+ds2-9+deb12u1
Done: Moritz Mühlenhoff 

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

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated freeimage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Dec 2023 20:20:51 +0100
Source: freeimage
Architecture: source
Version: 3.18.0+ds2-9+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Moritz Mühlenhoff 
Closes: 1051737 1051738 1051889
Changes:
 freeimage (3.18.0+ds2-9+deb12u1) bookworm-security; urgency=medium
 .
   * CVE-2020-21427 (Closes: #1051737)
   * CVE-2020-21428 (Closes: #1051738)
   * CVE-2020-22524 (Closes: #1051889)
Checksums-Sha1:
 3c6be411f4bde69a7c4075adaed9fa7049c868db 2573 
freeimage_3.18.0+ds2-9+deb12u1.dsc
 5c5f67837bd03cb2be596eb66d6edae735a4370d 1281524 
freeimage_3.18.0+ds2.orig.tar.xz
 588fcb4af91c1468559e45ec870a6488dce1abd4 29356 
freeimage_3.18.0+ds2-9+deb12u1.debian.tar.xz
 0ff4cd9aeb19a75642623b86f4668bdbc6eded04 9312 
freeimage_3.18.0+ds2-9+deb12u1_amd64.buildinfo
Checksums-Sha256:
 e80f525efd8118ab6d94bcf33cc6395074831681e629d6f7a4ee15a3c22c69bb 2573 
freeimage_3.18.0+ds2-9+deb12u1.dsc
 4425d04d4691084260848d67eb79949ea7c129d85c73a72066ba609fd3f3aa39 1281524 
freeimage_3.18.0+ds2.orig.tar.xz
 ece2cfa2a7cc007e83119828766f429f6494f20bcee4793a9b2037c1d8d8 29356 
freeimage_3.18.0+ds2-9+deb12u1.debian.tar.xz
 7794f4ec10d9a675d5f57d64b0943c7fef1b4f3aa6180c5ba1e188d68cc6ce9f 9312 
freeimage_3.18.0+ds2-9+deb12u1_amd64.buildinfo
Files:
 52a6334b252c81e07d82ac20871742b2 2573 libs optional 
freeimage_3.18.0+ds2-9+deb12u1.dsc
 bf8d7f34b419266773255855aadfd808 1281524 libs optional 
freeimage_3.18.0+ds2.orig.tar.xz
 a857785b3f7ce925c45f5def1a6be5e8 29356 libs optional 
freeimage_3.18.0+ds2-9+deb12u1.debian.tar.xz
 be8cca84ae35b23d8575512406e3c6bf 9312 libs optional 
freeimage_3.18.0+ds2-9+deb12u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmV8qmYACgkQEMKTtsN8
Tja9tg/+K5+b+aSnW5fnQPIn1G88UFCNAcg6xBQ2/dgSVNoS9ziiAt3JqWnHCVCJ
+PWcUhgXYSfBv5S/STgbNxIUP34RVGRDYBL1w/KLK69PjKqP+ss0aLPkiYSQxqmZ
zN99NH+87bjdyFZOwzq+2i5Osc4Zokb3h7B41imSVadubyOGcvqCyCfFpI5K35FR
vTsjhV6ol/zkU2gz4W9SxaWd7gqbDEo8LVmb+ZXvy2Rc69peMmOmWlSPXL8tlKKA
zPaAMFYbnb1P42nEILD8Y1JNAlEKNTQzPUEPcbw55mNAA7Lz/Do60XLjKzjyD5G7
8h1iF0L4Z85vjyk17ydMAlpX2dHCYuulCq6x4fuiGuAHB/tifiiFDYks4NOFYXsS
n2QuICOBFLmlCEysAoUL07AHxzGANfThgamm6Dzkdg2Pz8G+0D04IrQ5K3Eyx0tC
sVU/3wSHVPZ+jshQNxnY0PX69r9uO208XsKtPla91cxhNVpfRtAwaaL5i4x/7PBF
iYs+xwPL+8MRhdVeQC5IiVEWGbCZSWOtURhpKGaYYIEfKOWcv6PjkgWjQRhjAMDA
RkHhwPzpHoDaYzft8RqKyLB/sKQW3hWEPBlcvWf6MVyhQv/XRxjcPgFUfsblB0f5
r5T8V+WZ0dr6kt5q/8MGqXu5+oVy3JwToms1pM8M3Yuf/Zayb6Y=

Bug#1051738: marked as done (freeimage: CVE-2020-21428)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 18:32:09 +
with message-id 
and subject line Bug#1051738: fixed in freeimage 3.18.0+ds2-9+deb12u1
has caused the Debian Bug report #1051738,
regarding freeimage: CVE-2020-21428
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.)


-- 
1051738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeimage
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for freeimage.

CVE-2020-21428[0]:
| Buffer Overflow vulnerability in function LoadRGB in PluginDDS.cpp
| in FreeImage 3.18.0 allows remote attackers to run arbitrary code
| and cause other impacts via crafted image file.

https://sourceforge.net/p/freeimage/bugs/299/

This appears to be fixed in r1877 of the upstream Subversion repository

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-2020-21428
https://www.cve.org/CVERecord?id=CVE-2020-21428

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: freeimage
Source-Version: 3.18.0+ds2-9+deb12u1
Done: Moritz Mühlenhoff 

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

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated freeimage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Dec 2023 20:20:51 +0100
Source: freeimage
Architecture: source
Version: 3.18.0+ds2-9+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Moritz Mühlenhoff 
Closes: 1051737 1051738 1051889
Changes:
 freeimage (3.18.0+ds2-9+deb12u1) bookworm-security; urgency=medium
 .
   * CVE-2020-21427 (Closes: #1051737)
   * CVE-2020-21428 (Closes: #1051738)
   * CVE-2020-22524 (Closes: #1051889)
Checksums-Sha1:
 3c6be411f4bde69a7c4075adaed9fa7049c868db 2573 
freeimage_3.18.0+ds2-9+deb12u1.dsc
 5c5f67837bd03cb2be596eb66d6edae735a4370d 1281524 
freeimage_3.18.0+ds2.orig.tar.xz
 588fcb4af91c1468559e45ec870a6488dce1abd4 29356 
freeimage_3.18.0+ds2-9+deb12u1.debian.tar.xz
 0ff4cd9aeb19a75642623b86f4668bdbc6eded04 9312 
freeimage_3.18.0+ds2-9+deb12u1_amd64.buildinfo
Checksums-Sha256:
 e80f525efd8118ab6d94bcf33cc6395074831681e629d6f7a4ee15a3c22c69bb 2573 
freeimage_3.18.0+ds2-9+deb12u1.dsc
 4425d04d4691084260848d67eb79949ea7c129d85c73a72066ba609fd3f3aa39 1281524 
freeimage_3.18.0+ds2.orig.tar.xz
 ece2cfa2a7cc007e83119828766f429f6494f20bcee4793a9b2037c1d8d8 29356 
freeimage_3.18.0+ds2-9+deb12u1.debian.tar.xz
 7794f4ec10d9a675d5f57d64b0943c7fef1b4f3aa6180c5ba1e188d68cc6ce9f 9312 
freeimage_3.18.0+ds2-9+deb12u1_amd64.buildinfo
Files:
 52a6334b252c81e07d82ac20871742b2 2573 libs optional 
freeimage_3.18.0+ds2-9+deb12u1.dsc
 bf8d7f34b419266773255855aadfd808 1281524 libs optional 
freeimage_3.18.0+ds2.orig.tar.xz
 a857785b3f7ce925c45f5def1a6be5e8 29356 libs optional 
freeimage_3.18.0+ds2-9+deb12u1.debian.tar.xz
 be8cca84ae35b23d8575512406e3c6bf 9312 libs optional 
freeimage_3.18.0+ds2-9+deb12u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmV8qmYACgkQEMKTtsN8
Tja9tg/+K5+b+aSnW5fnQPIn1G88UFCNAcg6xBQ2/dgSVNoS9ziiAt3JqWnHCVCJ
+PWcUhgXYSfBv5S/STgbNxIUP34RVGRDYBL1w/KLK69PjKqP+ss0aLPkiYSQxqmZ
zN99NH+87bjdyFZOwzq+2i5Osc4Zokb3h7B41imSVadubyOGcvqCyCfFpI5K35FR
vTsjhV6ol/zkU2gz4W9SxaWd7gqbDEo8LVmb+ZXvy2Rc69peMmOmWlSPXL8tlKKA
zPaAMFYbnb1P42nEILD8Y1JNAlEKNTQzPUEPcbw55mNAA7Lz/Do60XLjKzjyD5G7
8h1iF0L4Z85vjyk17ydMAlpX2dHCYuulCq6x4fuiGuAHB/tifiiFDYks4NOFYXsS
n2QuICOBFLmlCEysAoUL07AHxzGANfThgamm6Dzkdg2Pz8G+0D04IrQ5K3Eyx0tC
sVU/3wSHVPZ+jshQNxnY0PX69r9uO208XsKtPla91cxhNVpfRtAwaaL5i4x/7PBF
iYs+xwPL+8MRhdVeQC5IiVEWGbCZSWOtURhpKGaYYIEfKOWcv6PjkgWjQRhjAMDA
RkHhwPzpHoDaYzft8RqKyLB/sKQW3hWEPBlcvWf6MVyhQv/XRxjcPgFUfsblB0f5

Bug#1055493: [Emc-developers] Bug#1055493: linuxcnc-uspace, linuxcnc-uspace-dev: both packages ship the manpages

[Sudip Mukherjee]

On Tue, Nov 07, 2023 at 11:06:01AM +, andy pugh wrote:
> On Tue, 7 Nov 2023 at 10:45, Andreas Beckmann  wrote:
> >
> > Package: linuxcnc-uspace,linuxcnc-uspace-dev
> > Version: 2.9.1-2
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: piuparts
> >
> > Hi,
> >
> > during a test with piuparts I noticed your package failed to install
> > because it tries to overwrite other packages files:
> 
> I assume that this could be fixed by deleting the last line here:
> https://github.com/LinuxCNC/linuxcnc/blob/2.9/debian/linuxcnc-uspace-dev.install
> 
> However I haven't so far worked out why the man3 sections are being
> included in the main package installer.
> (the commands in man3 are only of interest to developers)

>From 
>https://sources.debian.org/src/linuxcnc/2.9.1-2/debian/linuxcnc-uspace.manpages/#L2

-- 
Regards
Sudip

Bug#1058849: linphone: diff for NMU version 5.2.0-4.1

[Dennis Filder]

X-Debbugs-CC: Boyuan Yang 

On Sun, Dec 17, 2023 at 11:50:11AM -0500, Boyuan Yang wrote:
> I've prepared an NMU for linphone (versioned as 5.2.0-4.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer or cancel it.

No, it's okay.

Bug#1042967: nheko: diff for NMU version 0.11.3-2.1

[Boyuan Yang]

Control: tags 1042967 + patch
Control: tags 1042967 + pending

Dear maintainer,

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

Regards.

diff -Nru nheko-0.11.3/debian/changelog nheko-0.11.3/debian/changelog
--- nheko-0.11.3/debian/changelog   2023-03-23 12:17:45.0 -0400
+++ nheko-0.11.3/debian/changelog   2023-12-18 12:54:11.0 -0500
@@ -1,3 +1,14 @@
+nheko (0.11.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Force non-parallel build, hopefully fix OOM with
+armhf buildd build.
+  * debian/patches/:
++ 0003-Fix-voip-defaults-being-incorrect-because-OS-constan.patch:
+  Apply upstream fix on launch crashes with arm64. (Closes: #1042967)
+
+ -- Boyuan Yang   Mon, 18 Dec 2023 12:54:11 -0500
+
 nheko (0.11.3-2) unstable; urgency=medium
 
   * debian/control: Downgrade gstreamer1.0-vaapi to a Suggests.
diff -Nru 
nheko-0.11.3/debian/patches/0003-Fix-voip-defaults-being-incorrect-because-OS-constan.patch
 nheko-0.11.3/debian/patches/0003-Fix-voip-defaults-being-incorrect-
because-OS-constan.patch
--- 
nheko-0.11.3/debian/patches/0003-Fix-voip-defaults-being-incorrect-because-OS-constan.patch
 1969-12-31 19:00:00.0 -0500
+++ 
nheko-0.11.3/debian/patches/0003-Fix-voip-defaults-being-incorrect-because-OS-constan.patch
 2023-12-18 12:53:44.0 -0500
@@ -0,0 +1,34 @@
+From: Boyuan Yang 
+Date: Mon, 18 Dec 2023 12:52:42 -0500
+Subject: Fix voip defaults being incorrect because OS constants are not
+ defined
+
+Bug-Debian: https://bugs.debian.org/1042967
+Bug: https://github.com/Nheko-Reborn/nheko/issues/1574
+Applied-Upstream: 
https://github.com/Nheko-Reborn/nheko/commit/159493351313223ee88a7f34c8550c0b7af6b3e6
+---
+ CMakeLists.txt | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 41b01c8..648e8f8 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -47,6 +47,8 @@ macro(hunter_add_package_safe)
+   message("pkg_conf_path: '$ENV{PKG_CONFIG_PATH}', pkg_conf_libdir: 
'$ENV{PKG_CONFIG_LIBDIR}'")
+ endmacro()
+ 
++project(nheko LANGUAGES CXX C)
++
+ option(USE_BUNDLED_SPDLOG "Use the bundled version of spdlog." 
${HUNTER_ENABLED})
+ option(USE_BUNDLED_OLM "Use the bundled version of libolm." ${HUNTER_ENABLED})
+ option(USE_BUNDLED_GTEST "Use the bundled version of Google Test." 
${HUNTER_ENABLED})
+@@ -104,8 +106,6 @@ endif()
+ # Include Qt basic functions
+ include(QtCommon)
+ 
+-project(nheko LANGUAGES CXX C)
+-
+ include(GNUInstallDirs)
+ 
+ set(CPACK_PACKAGE_VERSION_MAJOR "0")
diff -Nru nheko-0.11.3/debian/patches/series nheko-0.11.3/debian/patches/series
--- nheko-0.11.3/debian/patches/series  2023-02-21 21:32:44.0 -0500
+++ nheko-0.11.3/debian/patches/series  2023-12-18 12:53:44.0 -0500
@@ -1,2 +1,3 @@
 cmake_coeurl
 httplib-pkgconfig
+0003-Fix-voip-defaults-being-incorrect-because-OS-constan.patch
diff -Nru nheko-0.11.3/debian/rules nheko-0.11.3/debian/rules
--- nheko-0.11.3/debian/rules   2023-02-21 21:03:58.0 -0500
+++ nheko-0.11.3/debian/rules   2023-12-18 12:50:25.0 -0500
@@ -15,7 +15,7 @@
 endif
 
 %:
-   dh $@
+   dh $@ --no-parallel
 
 # set $HOME to a dummy directory, because cmake tries to write stuff to $HOME
 override_dh_auto_build: FAKEHOME = HOME=$(CURDIR)/fakehome


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

Processed: nheko: diff for NMU version 0.11.3-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1042967 + patch
Bug #1042967 [nheko] nheko crashes on first launch in arm64 (librem 5)
Added tag(s) patch.
> tags 1042967 + pending
Bug #1042967 [nheko] nheko crashes on first launch in arm64 (librem 5)
Added tag(s) pending.

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

Processed: [bts-link] source package src:lazy-object-proxy

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:lazy-object-proxy
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1058384 (http://bugs.debian.org/1058384)
> # Bug title: lazy-object-proxy: FTBFS: dh_auto_test: error: pybuild --test 
> --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
> #  * https://github.com/ionelmc/python-lazy-object-proxy/pull/78
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1058384 + fixed-upstream
Bug #1058384 [src:lazy-object-proxy] lazy-object-proxy: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Added tag(s) fixed-upstream.
> usertags 1058384 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package picom

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package picom
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1040988 (http://bugs.debian.org/1040988)
> # Bug title: Clashes with existing composite manager
> #  * https://github.com/yshui/picom/issues/1104
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1040988 + fixed-upstream
Bug #1040988 [picom] Clashes with existing composite manager
Added tag(s) fixed-upstream.
> usertags 1040988 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1040988 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#991650: marked as done (python-django-imagekit: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 17:32:25 +
with message-id 
and subject line Bug#991650: fixed in python-django-imagekit 4.0.2-3+deb11u1
has caused the Debian Bug report #991650,
regarding python-django-imagekit: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p 3.9 returned exit code 13
to be marked as done.

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

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


-- 
991650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-imagekit
Version: 4.0.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210728 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/registry.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/generatorlibrary.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/lib.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/pkgmeta.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/conf.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/hashers.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/compat.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/admin.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/exceptions.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/signals.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/utils.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/files.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms
> copying imagekit/forms/fields.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms
> copying imagekit/forms/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models
> copying imagekit/models/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/resize.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/crop.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/base.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/utils.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs
> copying imagekit/specs/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs
> copying imagekit/specs/sourcegroups.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags
> copying imagekit/templatetags/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags
> copying imagekit/templatetags/imagekit.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> copying imagekit/cachefiles/backends.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> copying imagekit/cachefiles/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> copying imagekit/cachefiles/strategies.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> copying imagekit/cachefiles/namers.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/management
> copying 

Processed: raising severity; ftbfs with current glibc

[Debian Bug Tracking System]

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

> severity 986494 serious
Bug #986494 [sipxtapi] sipxtapi: FTBFS with glibc >= 2.32
Severity set to 'serious' from 'normal'
> tags 986494 + ftbfs sid
Bug #986494 [sipxtapi] sipxtapi: FTBFS with glibc >= 2.32
Added tag(s) ftbfs and sid.
> thanks
Stopping processing here.

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

Bug#999960: sipxtapi: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Attached is a patch which I tested with the demo program at the end of
sipXportLib/src/utl/UtlRegex.cpp.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/60
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2023-12-18
---

--- sipxtapi-3.3.0~test18+dfsg.1.orig/configure.ac
+++ sipxtapi-3.3.0~test18+dfsg.1/configure.ac
@@ -59,7 +59,7 @@
 CHECK_OPUS
 
 # PCRE is mandatory
-PKG_CHECK_MODULES([DEPS_PCRE], [libpcre >= 4.5])
+PKG_CHECK_MODULES([DEPS_PCRE], [libpcre2-8])
 
 # OpenSSL is mandatory, find it or configure fails:
 CHECK_SSL
--- sipxtapi-3.3.0~test18+dfsg.1.orig/sipXportLib/include/utl/UtlRegex.h
+++ sipxtapi-3.3.0~test18+dfsg.1/sipXportLib/include/utl/UtlRegex.h
@@ -12,7 +12,8 @@
 #define _REGEX_H
 
 #include 
-#include 
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 #include "utl/UtlString.h"
 
 /**
@@ -61,8 +62,8 @@

/// Compile a regular expression to create the matching object.
   RegEx( const char * regex, //< the regular expression
- int   options = 0, //< any sum of PCRE options bits
- unsigned long int maxDepth = MAX_RECURSION // see MAX_RECURSION
+ uint32_t  options = 0, //< any sum of PCRE options bits
+ uint32_t maxDepth = MAX_RECURSION // see MAX_RECURSION
  );
   /**<
* If compiling the regular expression fails, an error message string is
@@ -71,7 +72,7 @@
*/
 
   /// Default maximum for the recursion depth in searches.
-  static const unsigned long int MAX_RECURSION;
+  static const uint32_t MAX_RECURSION;
   /**<
* The PCRE internal match() function implements some searches by recursion.
* This value is the default maximumm allowed depth for that recursion.  It 
can
@@ -115,7 +116,7 @@
   ~RegEx();
 
   /// Count the number of possible substrings returned by this expression
-  int SubStrings(void) const;
+  uint32_t SubStrings(void) const;
   /**<
*   SubStrings() @returns the number of substrings defined by
*   the regular expression.
@@ -142,8 +143,8 @@
 
   /// Search a string for matches to this regular expression
   bool Search( const char * subject,  ///< the string to be searched for a 
match
-   int len = -1,  ///< the length of the subject string
-   int options = 0///< sum of any PCRE options flags
+   PCRE2_SIZE len = -1,   ///< the length of the subject string
+   uint32_t options = 0   ///< sum of any PCRE options flags
);
   /**<
*Apply the regular expression to the subject string.
@@ -156,9 +157,9 @@
 
   /// Search a string starting at some offset for matches to this regular 
expression
   bool SearchAt(const char* subject,  ///< the string to be searched for a 
match
-int offset,   ///< offset to begin search in subject 
string
-int len = -1, ///< the length of the subject string
-int options = 0   ///< sum of any PCRE options flags
+PCRE2_SIZE offset,///< offset to begin search in subject 
string
+PCRE2_SIZE len = 0,   ///< the length of the subject string
+uint32_t options = 0  ///< sum of any PCRE options flags
 );
   /**<
*Apply the regular expression to the subject string, starting at the 
given offset.
@@ -175,7 +176,7 @@
 
 
   /// Repeat the last search operation, starting immediately after the 
previous match
-  bool SearchAgain( int options = 0///< sum of any PCRE options flags
+  bool SearchAgain( uint32_t options = 0   ///< sum of any PCRE options flags
);
   /**<
*SearchAgain() applies the regular expression to the same
@@ -432,17 +433,17 @@
 
   void ClearMatchList(void);
 
-  pcre * re;
+  pcre2_code * re;
+  pcre2_general_context * gen_ctxt;
+  pcre2_match_context * match_ctxt;
   size_t re_size;
-  pcre_extra * pe;
-  bool allocated_study;
-  size_t  study_size;
-  int substrcount; // maximum substrings in pattern
+  uint32_t substrcount;// maximum substrings in pattern
   const char * subjectStr; // original subject
-  int subjectLen;  // original length
-  int lastStart;   // offset of start for most recent Search or 
SearchAgain
-  int lastMatches; // pcre_exec return for most recent Search or 
SearchAgain
-  int * ovector;   // results from (and workspace for) pcre_exec
+  PCRE2_SIZE subjectLen;   // original length
+  PCRE2_SIZE lastStart;// offset of start for most recent Search or 
SearchAgain
+  int lastMatches; // pcre2_match return for most recent Search or 
SearchAgain
+  PCRE2_SIZE * ovector;// results from (and workspace for) pcre2_match
+  pcre2_match_data * md;   // PCRE match data block
   const char * * matchlist;// string cache for Match
 };
 
--- sipxtapi-3.3.0~test18+dfsg.1.orig/sipXportLib/src/utl/UtlRegex.cpp
+++ sipxtapi-3.3.0~test18+dfsg.1/sipXportLib/src/utl/UtlRegex.cpp
@@ 

Processed: Re: Bug#999960: sipxtapi: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #60 [src:sipxtapi] sipxtapi: depends on obsolete pcre3 library
Added tag(s) patch.

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

Bug#984331: sipxtapi: ftbfs with GCC-11

[Yavor Doganov]

Control: tags -1 + patch

Please find attached a patch.
Description: Fix FTBFS with GCC 11+.
Bug-Debian: https://bugs.debian.org/984331
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2023-12-18
---

--- sipxtapi-3.3.0~test18+dfsg.1.orig/sipXtackLib/src/net/SipMessage.cpp
+++ sipxtapi-3.3.0~test18+dfsg.1/sipXtackLib/src/net/SipMessage.cpp
@@ -3806,13 +3806,13 @@
 routeString.append(SIP_MULTIFIELD_SEPARATOR);
 }
 // Make sure the route is in name-addr format
-if(strstr(routeUri,"<") <= 0)
+if(!strstr(routeUri,"<"))
 {
 routeString.append("<");
 }
 
 routeString.append(routeUri);
-if(strstr(routeUri, ">") <= 0)
+if(!strstr(routeUri, ">"))
 {
 routeString.append(">");
 }

Processed: Re: Bug#984331: sipxtapi: ftbfs with GCC-11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #984331 [src:sipxtapi] sipxtapi: ftbfs with GCC-11
Added tag(s) patch.

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

Bug#1057594: tetradraw: FTBFS: interface.c:1069:36: error: invalid use of incomplete typedef ‘ITEM’ {aka ‘struct tagITEM’}

[Sven Joachim]

Control: tags -1 + patch

On 2023-12-05 23:11 +0100, Santiago Vila wrote:

> Package: src:tetradraw
> Version: 2.0.3-10
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> 
> interface.c: In function ‘tv_file_select’:
> interface.c:1069:36: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>  1069 | if(items[y]->index != index) 
> menu_driver(menu, REQ_DOWN_ITEM);
>   |^~
> interface.c:1079:32: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>  1079 | index = current->index;
>   |^~
> interface.c::56: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>   | index = current->index;
>   |^~
> interface.c:1136:40: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>  1136 | index = current->index;
>   |^~
> interface.c:1146:40: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>  1146 | index = current->index;
>   |^~
> interface.c: In function ‘file_select’:
> interface.c:1217:36: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>  1217 | if(items[y]->index != index) 
> menu_driver(menu, REQ_DOWN_ITEM);
>   |^~
> gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.  -Wdate-time -D_FORTIFY_SOURCE=2  -Wall 
> -ggdb3 -c -o load.o load.c
> interface.c:1221:32: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>  1221 | index = current->index;
>   |^~
> interface.c:1259:56: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>  1259 | index = current->index;
>   |^~
> interface.c:1284:40: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
item_index>  1284 | index = current->index;
>   |^~
> interface.c:1299:40: error: invalid use of incomplete typedef ‘ITEM’ {aka 
> ‘struct tagITEM’}
>  1299 | index = current->index;

These errors have been triggered by a recent change in ncurses which
makes the ITEM structure opaque, its members cannot be addressed
directly anymore.  The remedy is rather simple: instead of
item->index, use item_index(item) to retrieve the index.  See the
attached patch which can be added to the series file.

Disclaimer: I have only tested that the package builds, not if it works.

Cheers,
   Sven

From 037e6dd0794674264cee0049f49f39a60fe7cb40 Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Mon, 18 Dec 2023 17:14:36 +0100
Subject: [PATCH] Fix FTBFS with opaque ncurses

Since ncurses patchlevel 20231021 the ITEM structure is opaque, its
members cannot be addressed directly.  Use the item_index function
instead.
---
 src/interface.c | 20 ++--
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/src/interface.c b/src/interface.c
index 2692b18..25a174d 100644
--- a/src/interface.c
+++ b/src/interface.c
@@ -1066,7 +1066,7 @@ char *tv_file_select(int next) {
 		post_menu(menu);

 		for(y = 0; items[y]; y++)
-			if(items[y]->index != index) menu_driver(menu, REQ_DOWN_ITEM);
+			if(item_index(items[y]) != index) menu_driver(menu, REQ_DOWN_ITEM);
 			else break;

 		if(next) {
@@ -1076,7 +1076,7 @@ char *tv_file_select(int next) {
 		}

 		current = current_item(menu);
-		index = current->index;
+		index = item_index(current);
 		wrefresh(wf);
 		while((ch = getch()) != 13) {
 			switch(ch) {
@@ -1108,7 +1108,7 @@ char *tv_file_select(int next) {
 	break;
 case TD_KEY_ESCAPE:
 	current = current_item(menu);
-	index = current->index;
+	index = item_index(current);

 	unpost_menu(menu);
 	free_menu(menu);
@@ -1133,7 +1133,7 @@ char *tv_file_select(int next) {
 	}
 			}
 			current = current_item(menu);
-			index = current->index;
+			index = item_index(current);
 			wrefresh(wf);
 		}
 		if(strcmp("", input)) {
@@ -1143,7 +1143,7 @@ char *tv_file_select(int next) {
 		} else {
 hugehack:
 			current = current_item(menu);
-			index = current->index;
+			index = item_index(current);
 			unpost_menu(menu);
 			free_menu(menu);
 			free_items(items);
@@ -1214,11 +1214,11 @@ char *file_select() {
 		post_menu(menu);

 		for(y = 0; items[y]; y++)
-			if(items[y]->index != index) menu_driver(menu, REQ_DOWN_ITEM);
+			

Processed: Re: Bug#1057594: tetradraw: FTBFS: interface.c:1069:36: error: invalid use of incomplete typedef ‘ITEM’ {aka ‘struct tagITEM’}

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1057594 [src:tetradraw] tetradraw: FTBFS: interface.c:1069:36: error: 
invalid use of incomplete typedef ‘ITEM’ {aka ‘struct tagITEM’}
Added tag(s) patch.

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

Bug#1058941: sipxtapi: FTBFS: PlgSpeex.c:21:10: fatal error: speex/speex.h: No such file or directory

[Yavor Doganov]

Source: sipxtapi
Version:  3.3.0~test18+dfsg.1-0.1
Severity: serious
Tags: sid ftbfs patch

This package fails to build from source because it has to build-depend
on libspeex-dev (libspeexdsp-dev only suggests it).  The exact error is:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../.. 
-I../../../../../sipXmediaLib/include -I../../../../../sipXportLib/include 
-I../../../../../../sipXmediaLib/contrib/libspeex/include 
-I../../../../../sipXmediaLib/contrib/libspeex/include -Wdate-time 
-D_FORTIFY_SOURCE=2 -DHAVE_SSL 
-DDEFAULT_CODECS_PATH=\"/usr/lib/x86_64-linux-gnu/sipxtapi/codecs\" -g -O2 
"-ffile-prefix-map=/<>=." -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-DHAVE_SPEEX -D__pingtel_on_posix__ -D_linux_ -D_REENTRANT 
-D_FILE_OFFSET_BITS=64 -fmessage-length=0 -Wall -Wformat -Wwrite-strings 
-Wpointer-arith -Wnested-externs -Wmissing-declarations -Wmissing-prototypes -c 
speex_nb.c  -fPIC -DPIC -o .libs/codec_speex_la-speex_nb.o
In file included from plgspeex.h:16,
 from speex_nb.c:16:
speex_nb.c:57:33: warning: no previous prototype for ‘speex_get_info_v1_1’ 
[-Wmissing-prototypes]
   57 | CODEC_API int PLG_GET_INFO_V1_1(speex)(const struct MppCodecInfoV1_1 
**codecInfo)
  | ^
../../../../../sipXmediaLib/include/mp/codecs/PlgDefsV1.h:183:40: note: in 
definition of macro ‘PLG_GET_INFO_V1_1’
  183 | #define PLG_GET_INFO_V1_1(x)   x##_get_info_v1_1
  |^
speex_nb.c:66:31: warning: no previous prototype for ‘speex_init_v1_2’ 
[-Wmissing-prototypes]
   66 | CODEC_API void *PLG_INIT_V1_2(speex)(const char* fmtp, int isDecoder,
  |   ^
../../../../../sipXmediaLib/include/mp/codecs/PlgDefsV1.h:184:40: note: in 
definition of macro ‘PLG_INIT_V1_2’
  184 | #define PLG_INIT_V1_2(x)   x##_init_v1_2
  |^
speex_nb.c:73:27: warning: no previous prototype for ‘speex_free_v1’ 
[-Wmissing-prototypes]
   73 | CODEC_API int PLG_FREE_V1(speex)(void* handle, int isDecoder)
  |   ^
../../../../../sipXmediaLib/include/mp/codecs/PlgDefsV1.h:188:40: note: in 
definition of macro ‘PLG_FREE_V1’
  188 | #define PLG_FREE_V1(x) x##_free_v1
  |^
speex_nb.c:78:43: warning: no previous prototype for 
‘speex_get_packet_samples_v1_2’ [-Wmissing-prototypes]
   78 | CODEC_API int PLG_GET_PACKET_SAMPLES_V1_2(speex)(void  *handle,
  |   ^
../../../../../sipXmediaLib/include/mp/codecs/PlgDefsV1.h:185:40: note: in 
definition of macro ‘PLG_GET_PACKET_SAMPLES_V1_2’
  185 | #define PLG_GET_PACKET_SAMPLES_V1_2(x) x##_get_packet_samples_v1_2
  |^
speex_nb.c:88:30: warning: no previous prototype for ‘speex_decode_v1’ 
[-Wmissing-prototypes]
   88 | CODEC_API  int PLG_DECODE_V1(speex)(void* handle, const void* 
pCodedData,
  |  ^
../../../../../sipXmediaLib/include/mp/codecs/PlgDefsV1.h:186:40: note: in 
definition of macro ‘PLG_DECODE_V1’
  186 | #define PLG_DECODE_V1(x)   x##_decode_v1
  |^
speex_nb.c:97:29: warning: no previous prototype for ‘speex_encode_v1’ 
[-Wmissing-prototypes]
   97 | CODEC_API int PLG_ENCODE_V1(speex)(void* handle, const void* 
pAudioBuffer,
  | ^
../../../../../sipXmediaLib/include/mp/codecs/PlgDefsV1.h:187:40: note: in 
definition of macro ‘PLG_ENCODE_V1’
  187 | #define PLG_ENCODE_V1(x)   x##_encode_v1
  |^
PlgSpeex.c:21:10: fatal error: speex/speex.h: No such file or directory
   21 | #include 
  |  ^~~
compilation terminated.
make[7]: *** [Makefile:576: codec_speex_la-PlgSpeex.lo] Error 1

Trivial patch attached.
--- debian/control.orig
+++ debian/control
@@ -2,7 +2,7 @@
 Section: libs
 Priority: optional
 Maintainer: Debian VoIP Team 
-Build-Depends: debhelper-compat (= 12), libssl-dev, libcppunit-dev, automake, 
libpcre3-dev, dpkg-dev (>= 1.16.1~), libxerces-c-dev, pkg-config, libgsm1-dev, 
libspandsp-dev, libspeexdsp-dev, doxygen, libopus-dev
+Build-Depends: debhelper-compat (= 12), libssl-dev, libcppunit-dev, automake, 
libpcre3-dev, dpkg-dev (>= 1.16.1~), libxerces-c-dev, pkg-config, libgsm1-dev, 
libspandsp-dev, libspeexdsp-dev, libspeex-dev, doxygen, libopus-dev
 Homepage: http://www.sipxtapi.org
 Standards-Version: 4.5.0
 Vcs-Git: https://salsa.debian.org/pkg-voip-team/sipxtapi.git

Bug#1056087: marked as done (bali-phy: FTBFS: boost1.83 transition)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 16:28:29 +
with message-id 
and subject line Bug#1056087: fixed in bali-phy 3.6.1+dfsg-2
has caused the Debian Bug report #1056087,
regarding bali-phy: FTBFS: boost1.83 transition
to be marked as done.

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

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


-- 
1056087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bali-phy
Version: 3.6.1+dfsg-1
Severity: normal
User: gl...@debian.org
Usertags: boost183 ftbfs-boost183-transition

Hi,

we are preparing the transition of all libs on the new boost 1.83. During the
rebuild of packages against this library it was identified that probably your
package fails to build.

Relevant part (hopefully):

-

/usr/include/boost/timer.hpp:21:3: error: #error This header is deprecated and 
will be removed. (You can define BOOST_TIMER_ENABLE_DEPRECATED to suppress this 
error.)
   21 | # error This header is deprecated and will be removed. (You can define 
BOOST_TIMER_ENABLE_DEPRECATED to suppress this error.)
  |   ^


-

To reproduce this behavior, you can install  -dev Boost packages from the
experimental repository, as shown in the following command:

  apt install libboost-dev -t experimental


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/bali-phy_3.6.1+dfsg-1_unstable_boost181.log

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

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 are unable to reproduce this, please provide a build log and diff it
so that we can identify any relevant changes that may have occurred in the 
meantime.
--- End Message ---
--- Begin Message ---
Source: bali-phy
Source-Version: 3.6.1+dfsg-2
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated bali-phy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Dec 2023 16:51:59 +0100
Source: bali-phy
Architecture: source
Version: 3.6.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1043647 1056087
Changes:
 bali-phy (3.6.1+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * d/gbp.conf: switch to debian/unstable branch.
   * boost1.83.patch: new: fix ftbfs. (Closes: #1056087)
   * d/lintian-overrides: refresh mismatch.
   * d/s/lintian-overrides: override false positive source missing.
   * d/control: declare compliance to standards version 4.6.2.
   * d/watch: fix uscan recipe; move to git mode.
   * d/rules: cleanup test artifacts. (Closes: #1043647)
Checksums-Sha1:
 eb3bf13e96c95d2e96f241e5d4e171ed938483a2 2340 bali-phy_3.6.1+dfsg-2.dsc
 221e6e85f47a18d9e0b353c192638e73ca6b70cb 5344 
bali-phy_3.6.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 56528dc69b86d79fea1ab21ef535b2c14ddf6a7c10e260ef245c23d298e0dc62 2340 
bali-phy_3.6.1+dfsg-2.dsc
 3502077f59078fd7fb61a8fa991efe0d55f8d6de21adc571891ce3e0e8838c2f 5344 
bali-phy_3.6.1+dfsg-2.debian.tar.xz
Files:
 1d72fb245c743916ee2ece9762692395 2340 science optional 
bali-phy_3.6.1+dfsg-2.dsc
 f01717651d16771912e64e6cb3c38aca 5344 science optional 
bali-phy_3.6.1+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmWAbmAUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqDghAAw/5lk3XmFVTdjI9B/q4hxYikPBdH
TiMOzLgwojiv2gk8/TpYCP9oCEynG4kPQelH/U5bB6kKeWDpMjmy1Wi+beI8aM5u
Gra+35zDdpzaVgnqkVYj446Fot99/wFfQgFdX8m/EjkdY/5Fk8C+ztZt5nWm6lFO
93nzLYMQ75kySLzHpD+TIzRoWJLYYKxT1YUrT3dTF8Gm+gvMlf20YOZYUldknRjA
dI/wlBRZbk4EXqfBkRfYTZVFWH7r03IM6g+s7laibFBqg7tybw87cY/2zhlO1Fth

Bug#1058937: Conflicts with libnfsidmap{2,-regex} involving aliased file locations)

[Ben Hutchings]

Control: user helm...@debian.org
Control: usertag -1 dep17p1

According to the classification in DEP-17
 this is problem type P1.

libnfsidmap1 includes mitigation M7 (Conflicts with the other packages)
since version 1:2.5.4-1~exp2, but although this usually avoids P1 we
now know that this is not always the case.

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer



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

Processed: tagging 1056088

[Debian Bug Tracking System]

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

> tags 1056088 + trixie sid
Bug #1056088 [src:bagel] bagel: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: severity of 1056088 is serious

[Debian Bug Tracking System]

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

> severity 1056088 serious
Bug #1056088 [src:bagel] bagel: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 1056083

[Debian Bug Tracking System]

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

> tags 1056083 + trixie sid
Bug #1056083 [src:dds] dds: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: severity of 1056083 is serious

[Debian Bug Tracking System]

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

> severity 1056083 serious
Bug #1056083 [src:dds] dds: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 1056087 is serious

[Debian Bug Tracking System]

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

> severity 1056087 serious
Bug #1056087 [src:bali-phy] bali-phy: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 1056087

[Debian Bug Tracking System]

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

> tags 1056087 + trixie sid
Bug #1056087 [src:bali-phy] bali-phy: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1058937: Conflicts with libnfsidmap{2,-regex} involving aliased file locations

[Ben Hutchings]

Package: libnfsidmap1
Version: 1:2.5.4-1~exp1
Severity: serious

As receently disvovered by Helmut Grohne, a conflict between binary
packages does not ensure that the files of one will be removed before
the files of the other are installed.  This can result in file loss
when the conflict involves aliased filenames rather than exactly the
same filenames.

This specific scenario exists when installing libnfsidmap1 as a
replacement for libnfsidmap{2,-regex} packages.  I was able to
reproduce it with the following sequence of commands in a minimal
bullseye amd64 chroot:

# apt -y install usrmerge
# apt -y install libnfsidmap{2,-regex}
# sed -i 's/bullseye/bookworm/' /etc/apt/sources.list
# apt update
# apt -d -y install libnfsidmap1
# (cd /var/cache/apt/archives && \
   dpkg -i libc{6,-bin}_2.36-9+deb12u3_amd64.deb \
   libsasl2-{2,modules-db}_2.1.28+dfsg-10_amd64.deb \
   libgmp10_2%3a6.2.1+dfsg1-1.1_amd64.deb \
   libgnutls30_3.7.9-2_amd64.deb libldap-2.5-0_2.5.13+dfsg-5_amd64.deb)
# dpkg -i /var/cache/apt/archives/libnfsidmap1_1%3a2.6.2-4_amd64.deb

Ben.

Bug#1058908: marked as pending in plasma-workspace

[Matthias Klumpp]

Control: tag -1 pending

Hello,

Bug #1058908 in plasma-workspace 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/qt-kde-team/kde/plasma-workspace/-/commit/d99f13a15fcde025095e7f6970c364d9886de309


Tighten build-dep on breeze (Closes: #1058908)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058908

Processed: Bug#1058908 marked as pending in plasma-workspace

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058908 [src:plasma-workspace] plasma-workspace 4:5.27.10-1 loses 
appstream and breeze support
Added tag(s) pending.

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

Bug#1056089: marked as done (autodock-vina: FTBFS: boost1.83 transition)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 14:41:31 +
with message-id 
and subject line Bug#1056089: fixed in autodock-vina 1.2.5-2
has caused the Debian Bug report #1056089,
regarding autodock-vina: FTBFS: boost1.83 transition
to be marked as done.

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

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


-- 
1056089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autodock-vina
Version: 1.2.5-1
Severity: normal
User: gl...@debian.org
Usertags: boost183 ftbfs-boost183-transition

Hi,

we are preparing the transition of all libs on the new boost 1.83. During the
rebuild of packages against this library it was identified that probably your
package fails to build.

Relevant part (hopefully):

-

/usr/include/boost/progress.hpp:23:3: error: #error This header is deprecated 
and will be removed. (You can define BOOST_TIMER_ENABLE_DEPRECATED to suppress 
this error.)
   23 | # error This header is deprecated and will be removed. (You can define 
BOOST_TIMER_ENABLE_DEPRECATED to suppress this error.)
  |   ^

-

To reproduce this behavior, you can install  -dev Boost packages from the
experimental repository, as shown in the following command:

  apt install libboost-dev -t experimental


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/autodock-vina_1.2.5-1_unstable_boost181.log

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

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 are unable to reproduce this, please provide a build log and diff it
so that we can identify any relevant changes that may have occurred in the 
meantime.
--- End Message ---
--- Begin Message ---
Source: autodock-vina
Source-Version: 1.2.5-2
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated autodock-vina 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Dec 2023 15:02:05 +0100
Source: autodock-vina
Architecture: source
Version: 1.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1056089
Changes:
 autodock-vina (1.2.5-2) unstable; urgency=medium
 .
   * Team upload.
   * boost1.83.patch: new: fix ftbfs with boost 1.83.
 Thanks to jalegido (Closes: #1056089)
   * d/t/run-unit-test: remove bashisms flagged by lintian.
Checksums-Sha1:
 cbc12657dc6d7ad8d4ee5fc05c7dc40214c596d1 2238 autodock-vina_1.2.5-2.dsc
 7ce72d1ed61f7b5a9ce1a66b751ade5abd1907de 37528 
autodock-vina_1.2.5-2.debian.tar.xz
Checksums-Sha256:
 98234f2227b34a6a07bc401fc15650627b6a1f72b2a67feb62211a3ead68b329 2238 
autodock-vina_1.2.5-2.dsc
 c0bc32672680ba1b4d0176c0bf98e17daeaeda68860dcd18693879be94228d2e 37528 
autodock-vina_1.2.5-2.debian.tar.xz
Files:
 6a49d1d75f3739862dac09fec487a45e 2238 science optional 
autodock-vina_1.2.5-2.dsc
 df2ab21272d29224a3eed9000b6aa288 37528 science optional 
autodock-vina_1.2.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmWAUggUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdovzg//fiZfUG/8CxR7SY7rJSZaeK2oXnMh
6EhsMHoHJqops1uczNRunCn4qFUL6xXxyY892sITqV5rMBcg8KxeFpsUJgdFH8WH
sGTg7oSamUK8unv6H+3W2yCNR2UEDLRVHVuiEDjHKM+tCiC7rGY7WiC3a+OoP/Kq
GeU+Aacyep50qABL9+wJhOwfXvL9iNhfw9PLZKvXEvU1sOWPxzIYcFxY9rcUxA0u
HodL6NW2Ty4gHG7YQ9m1aPft4eHNfJSvo9ZbxXnv4Dl82xHIUs+zrbT6EE9Knuly
sLmckRUi976Q2qgrhiJl5381Nz87FrfPViDelN0FHrR6b01PFM6VZLLnbskAGsS8
ErBNMkDRD3VC534SirDXcOp+v6QB03+oJfcZQe7iaDa4QggiNe6ee6LyrpkcwSS0
ahTXD4xp/6OEkh4gwoZsXdr85Nx0vUkG16effoZpXDM3ma02mX3QgtxD263nViPQ

Processed: tagging 1056090

[Debian Bug Tracking System]

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

> tags 1056090 + trixie sid
Bug #1056090 [src:aegisub] aegisub: FTBFS: boost1.83 transition
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1000061: cfengine3: depends on obsolete pcre3 library

[Bastian Germann]

On Fri, 18 Aug 2023 12:01:17 +0200 Bastian Germann  wrote:

cfengine3 is a key package and requires pcre, so this has to be fixed.


Upstream claims that this is fixed with 3.24.0.

Processed: Bug#1056089 marked as pending in autodock-vina

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1056089 [src:autodock-vina] autodock-vina: FTBFS: boost1.83 transition
Added tag(s) pending.

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

Bug#1056089: marked as pending in autodock-vina

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/autodock-vina/-/commit/9c5e791a0082163c3fcd96c2b4e7c282ecd66be5


boost1.83.patch: new: fix ftbfs with boost 1.83.

Closes: #1056089
Thanks: jalegido


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056089

Processed: severity of 1056090 is serious

[Debian Bug Tracking System]

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

> severity 1056090 serious
Bug #1056090 [src:aegisub] aegisub: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 1056082 is serious

[Debian Bug Tracking System]

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

> severity 1056082 serious
Bug #1056082 [src:field3d] field3d: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 1056089 is serious

[Debian Bug Tracking System]

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

> severity 1056089 serious
Bug #1056089 [src:autodock-vina] autodock-vina: FTBFS: boost1.83 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Re: Bug#1057933: libjose4j-java: FTBFS: IOException: Only named ECParameters supported

[Debian Bug Tracking System]

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

> severity 1057933 normal
Bug #1057933 [src:libjose4j-java] libjose4j-java: FTBFS: IOException: Only 
named ECParameters supported
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1057933: libjose4j-java: FTBFS: IOException: Only named ECParameters supported

[Santiago Vila]

severity 1057933 normal
thanks

Hi.

It works on m6a.large instances, which have an AMD EPYC processor.
I'm downgrading as a cautionary measure.

My theory right now is that the package needs more than 4 GB of RAM
to build, but does not show a meaningful error message if that's not
the case.

Now you may ask: Why am I building this package with so little memory?

Well, I monitor /proc/meminfo during the build and collect the results,
so that I never try to build a given package on a machine which I know
will need more than the machine has. This usually works well enough
most of the time, but sometimes I have to make exceptions.

(Also, 99.1% of all packages build ok with 4 GB of RAM, so it's not
really such a low amount).

I have to do additional checks.

Thanks.

Bug#1058921: ceph: loss of ceph-volume@.service

[Chris Hofstaedtler]

Source: ceph
Version: 18.2.0+ds-1
Severity: serious
User: helm...@debian.org
Usertags: dep17p1
X-Debbugs-Cc: helm...@debian.org

Hi,

the file /lib/systemd/system/ceph-volume@.service was previously
part of the ceph-osd binary package, but has now moved to
ceph-volume. However, this file will also need to move from /lib to
/usr/lib during trixie.

This combination will become a DEP17 P1 problem: "File loss during
canonicalized file move", and is currently prohibited by the file
move moratorium. As an effect, it is likely the ceph-volume@.service
will be lost in some percentage of upgrades.

There are potential mitigations if this file move needs to happen,
but they are hard to understand and therefore even harder to test.
It would be easier for everyone, if this file move could be avoided
altogether.

I'm therefore asking you to consider not moving the file between
binary packages.

If you come to the conclusion that the file must be moved, please
reply on this bug report and keep the problem confined to
experimental for now.


Thanks,
Chris

Bug#1057969: linux-image-6.1.0-15-amd64: Crash. Cannot poweroff or reboot with 6.1.66 on Lenovo Thinkpad Followup-For: Bug #1057969 Package: src:linux Version: 6.1.66-1

[rpnpif]

Hello,
It seems that this issue was fixed for me in linux-image-6.1.0.16 
(6.1.67-1) from stable-updates.

Thanks.
Rpnpif

Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}

[Dave Hibberd]

Hi both,

I'll prepare a team upload for this in advance of the new upstream release 
(thanks David), and upload it independently or with support depending on the 
outcome of the DAM stage of my NM process (https://nm.debian.org/process/1224/)

Cheers
DH

-- 
  Hibby
  MM0RFN

On Sat, 16 Dec 2023, at 6:32 PM, David Ranch wrote:
> Hello Sven, Debian team,
> 
> I was about to apply a very similar fix to the "develop" branch of Linpac at 
> https://sourceforge.net/p/linpac/linpac/ci/develop/tree though my changes 
> didn't include the "-1" at the end of the changes.  Not sure if that's needed 
> / important.  Regardless, I am planning to eventually merge the develop 
> branch into the Master branch and releae 0.29 in the near future which will 
> include this and other fixes.
> 
> --David
> KI6ZHD
> 
> On 12/16/2023 10:01 AM, Sven Joachim wrote:
>> Control: tags -1 + patch
>> 
>> On 2023-12-05 23:07 +0100, Santiago Vila wrote:
>> 
>> 
>>> Package: src:linpac
>>> Version: 0.28-2
>>> Severity: serious
>>> Tags: ftbfs
>>> 
>>> Dear maintainer:
>>> 
>>> During a rebuild of all packages in unstable, your package failed to build:
>>> 
>>> 
>>> [...]
>>> g++ -DHAVE_CONFIG_H -I. -I../../..   -Wdate-time -D_FORTIFY_SOURCE=2  -g 
>>> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
>>> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
>>> -c -o mail_screen.o mail_screen.cc
>>> mail_screen.cc: In function ‘void init_main_screen()’:
>>> mail_screen.cc:39:16: error: invalid use of incomplete type ‘WINDOW’ {aka 
>>> ‘struct _win_st’}
>>>39 |   maxx = stdscr->_maxx;
>>>   |^~
>>> In file included from mail_screen.cc:13:
>>> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
>>> ‘struct _win_st’}
>>>   442 | typedef struct _win_st WINDOW;
>>>   |^~~
>>> mail_screen.cc:40:16: error: invalid use of incomplete type ‘WINDOW’ {aka 
>>> ‘struct _win_st’}
>>>40 |   maxy = stdscr->_maxy;
>>>   |^~
>>> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
>>> ‘struct _win_st’}
>>>   442 | typedef struct _win_st WINDOW;
>>>   |^~~
>>> mail_screen.cc: In function ‘void redraw()’:
>>> mail_screen.cc:70:15: error: invalid use of incomplete type ‘WINDOW’ {aka 
>>> ‘struct _win_st’}
>>>70 |main_window->_clear = TRUE;
>>>   |   ^~
>>> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka 
>>> ‘struct _win_st’}
>>>   442 | typedef struct _win_st WINDOW;
>>> 
>> The attached patch, which can be added to the series file fixes, these
>> errors and two additional ones in src/linpac.cc, but I have only tested
>> that the package builds, not if it works.  Note that getmaxx(win)
>> returns win->_maxx + 1, and similar for getmaxy.
>> 
>> Cheers,
>>Sven
>> 
>> 

Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones

[Marc Haber]

On Sun, Dec 17, 2023 at 09:55:13PM -0800, Francois Marier wrote:
> With respect to the presence of the real commands in the path, I'm not too
> worried about it personally.

Agreed. Molly-Guard is not a security tool, it provides basic safety
against things like "typed shutdown -r now in the wrong window". Most
people just give the same commands every time, for me it happens to be
shutdown -r now, and if molly-guard reliably catches that then its job
is done.

It was never designed to prevent fully deliberate shots in one's foot by
typing things like shutdown.someweirdsuffixthatnooneeverremembers -r
now.

Thanks for the work, I was never able to fully grasp the issue and the
inner workings of the solution, and thank you for allowing me to remain
silent during the process of finding and implementing the solution.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1058528: marked as done (calamares-extensions: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 2)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 08:24:36 +
with message-id 
and subject line Bug#1058528: fixed in calamares-extensions 1.3.2-2
has caused the Debian Bug report #1058528,
regarding calamares-extensions: FTBFS: make[1]: *** [debian/rules:11: 
override_dh_auto_configure] Error 2
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -DCMAKE_CXX_COMPILER_ARG1="-Wdate-time 
> -D_FORTIFY_SOURCE=2"
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> "-DCMAKE_CXX_COMPILER_ARG1=-Wdate-time -D_FORTIFY_SOURCE=2" ..
> CMake Deprecation Warning at CMakeLists.txt:41 (cmake_minimum_required):
>   Compatibility with CMake < 3.5 will be removed from a future version of
>   CMake.
> 
>   Update the VERSION argument  value or use a ... suffix to tell
>   CMake that the project does not need compatibility with older versions.
> 
> 
> -- The CXX compiler identification is GNU 13.2.0
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Found YAMLCPP: /usr/include  
> -- Found Gettext: /usr/bin/msgmerge (found version "0.21") 
> CMake Error at 
> /usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresAddTranslations.cmake:17 
> (set_package_properties):
>   Unknown CMake command "set_package_properties".
> Call Stack (most recent call first):
>   
> /usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresAddModuleSubdirectory.cmake:40
>  (include)
>   /usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresConfig.cmake:121 
> (include)
>   CMakeLists.txt:64 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Path to a program.
> CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None Debug Release RelWithDebInfo
> // MinSizeRel ...
> CMAKE_BUILD_TYPE:STRING=None
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR_MAKEFILE:BOOL=ON
> 
> //CXX compiler
> CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++
> 
> //A wrapper around 'ar' adding the appropriate '--plugin' option
> // for the GCC compiler
> CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-13
> 
> //No help, variable specified on the command line.
> CMAKE_CXX_COMPILER_ARG1:UNINITIALIZED=-Wdate-time -D_FORTIFY_SOURCE=2
> 
> //A wrapper around 'ranlib' adding the appropriate '--plugin' option
> // for the GCC compiler
> CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-13
> 
> //Flags used by the CXX compiler during all build types.
> CMAKE_CXX_FLAGS:STRING=-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2
> 
> //Flags used by the CXX compiler during DEBUG builds.
> CMAKE_CXX_FLAGS_DEBUG:STRING=-g
> 

Bug#1057546: marked as done (calamares-extensions: FTBFS: Unknown CMake command "set_package_properties".)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2023 08:24:36 +
with message-id 
and subject line Bug#1057546: fixed in calamares-extensions 1.3.2-2
has caused the Debian Bug report #1057546,
regarding calamares-extensions: FTBFS: Unknown CMake command 
"set_package_properties".
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.)


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

Package: src:calamares-extensions
Version: 1.3.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_CXX_COMPILER_ARG1="-Wdate-time -D_FORTIFY_SOURCE=2"
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON 
-DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
"-DCMAKE_CXX_COMPILER_ARG1=-Wdate-time -D_FORTIFY_SOURCE=2" ..
CMake Deprecation Warning at CMakeLists.txt:41 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument  value or use a ... suffix to tell
  CMake that the project does not need compatibility with older versions.


-- The CXX compiler identification is GNU 13.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found YAMLCPP: /usr/include
-- Found Gettext: /usr/bin/msgmerge (found version "0.21")
CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresAddTranslations.cmake:17 
(set_package_properties):
  Unknown CMake command "set_package_properties".
Call Stack (most recent call first):
  
/usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresAddModuleSubdirectory.cmake:40
 (include)
  /usr/lib/x86_64-linux-gnu/cmake/Calamares/CalamaresConfig.cmake:121 (include)
  CMakeLists.txt:64 (find_package)


-- Configuring incomplete, errors occurred!
cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
==> CMakeCache.txt <==
# This is the CMakeCache file.
# For build in directory: /<>/obj-x86_64-linux-gnu
# It was generated by CMake: /usr/bin/cmake
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.


# EXTERNAL cache entries


//Path to a program.
CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line

//Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=None

//Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++

//A wrapper around 'ar' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_CXX_COMPILER_AR:FILEPATH=/usr/bin/gcc-ar-13

//No help, variable specified on the command line.
CMAKE_CXX_COMPILER_ARG1:UNINITIALIZED=-Wdate-time -D_FORTIFY_SOURCE=2

//A wrapper around 'ranlib' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_CXX_COMPILER_RANLIB:FILEPATH=/usr/bin/gcc-ranlib-13

//Flags used by the CXX compiler during all build types.
CMAKE_CXX_FLAGS:STRING=-g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2

//Flags used by the CXX compiler during DEBUG builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=-g

//Flags used by the CXX compiler during MINSIZEREL builds.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

Bug#1058219: Fix pending

[Thomas Goirand]

Hi,

The "slice(0, -1, None)" failed unit tests are due to #1058895 in 
SQLAlchemy, and for the has_calls -> assert_has_calls I have a patch 
locally, but can't upload unless SQLAlchemy is fixed.


Cheers,

Thomas Goirand (zigo)

Bug#1058908: plasma-workspace 4:5.27.10-1 loses appstream and breeze support

[Matthias Klumpp]

Am Mo., 18. Dez. 2023 um 09:09 Uhr schrieb Adrian Bunk :
> [...]
> ...
> -- The following OPTIONAL packages have not been found:
>
>  * Breeze (required version >= 5.27.10)
>For setting the default window decoration plugin
>  * AppStreamQt5 (required version >= 0.10.6), Access metadata for listing 
> available software, 
> 
> ...

Damn, I checked for AppStream, but must have missed that - and Breeze!

Sorry for that, I will look into fixing that issue ASAP today or tomorrow!
Breeze will likely just need a version update, AppStream I am not sure
about yet...

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#1058162: Fixed, but waiting on sqlalchemy

[Thomas Goirand]

Hi,

There's a bunch of tests failing because of #1058895 in SQLAlchemy, the 
remaining 2 unit test failures, I have a patch for them, but this needs 
for SQLAlchemy to be fixed before I can upload.


Cheers,

Thomas Goirand (zigo)

Bug#1058908: plasma-workspace 4:5.27.10-1 loses appstream and breeze support

[Adrian Bunk]

Source: plasma-workspace
Version: 4:5.27.10-1
Severity: serious
X-Debbugs-Cc: Matthias Klumpp 

https://buildd.debian.org/status/fetch.php?pkg=plasma-workspace=amd64=4%3A5.27.10-1=1702876241=0

...
CMake Warning at CMakeLists.txt:99 (find_package):
  Could not find a configuration file for package "Breeze" that is compatible
  with requested version "5.27.10".

  The following configuration files were considered but not accepted:

/usr/lib/x86_64-linux-gnu/cmake/Breeze/BreezeConfig.cmake, version: 5.27.9
/lib/x86_64-linux-gnu/cmake/Breeze/BreezeConfig.cmake, version: 5.27.9
...
CMake Warning at CMakeLists.txt:186 (find_package):
  Could not find a configuration file for package "AppStreamQt5" that is
  compatible with requested version "0.10.6".

  The following configuration files were considered but not accepted:

/usr/lib/x86_64-linux-gnu/cmake/AppStreamQt5/AppStreamQt5Config.cmake, 
version: 1.0.1
/lib/x86_64-linux-gnu/cmake/AppStreamQt5/AppStreamQt5Config.cmake, version: 
1.0.1
...
-- The following OPTIONAL packages have not been found:

 * Breeze (required version >= 5.27.10)
   For setting the default window decoration plugin
 * AppStreamQt5 (required version >= 0.10.6), Access metadata for listing 
available software, 
...