Processed: Re: Bug#1086551: ansible-core: uninstallable in unstable: Depends: python3-resolvelib (< 1.1.0)
Processing control commands: > tags 1086551 +fixed-upstream Bug #1086551 [ansible-core] ansible-core: uninstallable in unstable: Depends: python3-resolvelib (< 1.1.0) Added tag(s) fixed-upstream. -- 1086551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1079398: fscacher: FTBFS: test_memoize_path_dir fails
Processing control commands: > severity 1079398 important Bug #1079398 [src:fscacher] fscacher: FTBFS: test_memoize_path_dir fails Severity set to 'important' from 'grave' -- 1079398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: burrow: FTBFS on riscv64: undefined: syscall.Dup2
Processing commands for cont...@bugs.debian.org: > owner 1086799 ! Bug #1086799 [src:burrow] burrow: FTBFS on riscv64: undefined: syscall.Dup2 Owner recorded as Santiago Vila . > thanks Stopping processing here. Please contact me if you need assistance. -- 1086799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1085450 marked as pending in sbuild
Processing control commands: > tag -1 pending Bug #1085450 [src:sbuild] mmdebootstrap: sbuild autopkgtest for unshare backend fails Added tag(s) pending. -- 1085450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1080464: marked as done (Fix feature check for clang-19+)
Your message dated Wed, 06 Nov 2024 11:19:56 + with message-id and subject line Bug#1080464: fixed in xtensor 0.25.0-2 has caused the Debian Bug report #1080464, regarding Fix feature check for clang-19+ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1080464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xtensor Version: 0.25.0-1 Severity: important Tags: sid trixie patch Fix feature check for clang-19+, taken from upstream. Patch at https://launchpadlibrarian.net/747418683/xtensor_0.25.0-1_0.25.0-1ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: xtensor Source-Version: 0.25.0-2 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of xtensor, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated xtensor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 06 Nov 2024 00:34:10 +0100 Source: xtensor Architecture: source Version: 0.25.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 1080464 Changes: xtensor (0.25.0-2) unstable; urgency=medium . * debian patch clang19_feature_check.patch updates preprocessor feature check to allow building with Clang 19. See upstream issue#2783. Closes: #1080464. * Standards-Version: 4.7.0 Checksums-Sha1: 19460f2d2429a4d70e541849f5564631bfea75da 2448 xtensor_0.25.0-2.dsc f9719c460c8b72fe62803f30d82ec2dbf92c3458 10056 xtensor_0.25.0-2.debian.tar.xz Checksums-Sha256: 49539cec9d5da2c87f1939cc6d92753bf81e778b4dc477b59caffac09d799cca 2448 xtensor_0.25.0-2.dsc 499a491e0976bc067c6b7e74897529e2b5b0706e6c8545ec653df18274967923 10056 xtensor_0.25.0-2.debian.tar.xz Files: 8e2a99c00d4ac5b44fbf0643a95765c3 2448 libs optional xtensor_0.25.0-2.dsc 7c0b33adceeac73839223e68f091c5c2 10056 libs optional xtensor_0.25.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmcrRGkACgkQVz7x5L1a Afoe3w//TqFEji0OBld/ATt1PS5rhpeuw0/D/LlGsf5B3uQVp3sr3a4x8j4R5z4z I5gC9pyBitweqWyza/8RNP67m2lRgT9Xv1tIsXovrzq37UiniNy5O04CvOenQqwJ nRUqW7DQEsMF7WlzBoXgWoTdUcfWcoBAoCE3EYSSXm+DI4Hq+z+vXdyXAcdbxToh g+hidElbnfUloo/5eASuCztTvG1MZ3MoWN8sIPHSiDE9eyO7CbCQxC0zZjhFEafA DzvKLbZTdInTit9ZMuBYRkIoI++RDmHy3a+AmrJ8OhlOkrkRgH7qIKoBkh/F4gy7 QjBUN6J88lLsayBk0R349boN+TDGEAm0KXtNn5vyaAZYR6mVJdan+moO75Rn5Lek J8KxzA1TIZxQpHFv1y96nTU8HvhDB5WmICcJJOIyAWYIo0TnpDEPZ8t71uflSkFI 5e1JsHQqPS9ospSaPjrvDbldDR9oHLkLdI8hj2hoIM10/+VkRRi5FVF6J96gVrQ1 lyMtagpQfm+1aLUOPF/7e1HCUOqhy+yJy89F+5z81TvE9J3JO6VRVfZwfBCMFW7Y Brp3vnls/FXr/dzhR53BgTbPzb41OGkNqxvq6KMATTzVtqsC3zKPVePltEL/owtz PJcubMNCJgjWIMLwHhihxRgnblKtcTumIGUXlwyzaEmd5mIwEHY= =T1s4 -END PGP SIGNATURE- pgpQgTQmbSAyj.pgp Description: PGP signature --- End Message ---
Processed: affects 1086750
Processing commands for cont...@bugs.debian.org: > affects 1086750 grub-installer Bug #1086750 [src:grub] grub-installer still uses old grub-legacy Added indication that 1086750 affects grub-installer > thanks Stopping processing here. Please contact me if you need assistance. -- 1086750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1085354 closed by Debian FTP Masters (reply to Andrea Pappacoda ) (Bug#1085354: fixed in mbedtls 3.6.2-2)
Processing control commands:
> reopen -1
Bug #1085354 {Done: Andrea Pappacoda } [src:mbedtls]
mbedtls FTBFS on arm64 with gcc 14
'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 mbedtls/3.6.2-2.
--
1085354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: remove grub-legacy support
Processing control commands: > block 1086750 by -1 Bug #1086750 [src:grub] grub-installer still uses old grub-legacy 1086750 was not blocked by any bugs. 1086750 was not blocking any bugs. Added blocking bug(s) of 1086750: 1086840 -- 1086750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086750 1086840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1085354: marked as done (mbedtls FTBFS on arm64 with gcc 14)
Your message dated Wed, 06 Nov 2024 12:19:33 + with message-id and subject line Bug#1085354: fixed in mbedtls 3.6.2-2 has caused the Debian Bug report #1085354, regarding mbedtls FTBFS on arm64 with gcc 14 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.) -- 1085354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mbedtls Version: 3.6.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mbedtls&arch=arm64&ver=3.6.0-3&stamp=1729201458&raw=0 ... In file included from /<>/library/ctr_drbg.c:13: In function ‘mbedtls_xor’, inlined from ‘ctr_drbg_update_internal’ at /<>/library/ctr_drbg.c:372:5: /<>/library/common.h:235:17: error: array subscript 48 is outside array bounds of ‘unsigned char[48]’ [-Werror=array-bounds=] 235 | r[i] = a[i] ^ b[i]; |~^~~ /<>/library/ctr_drbg.c: In function ‘ctr_drbg_update_internal’: /<>/library/ctr_drbg.c:335:19: note: at offset 48 into object ‘tmp’ of size 48 335 | unsigned char tmp[MBEDTLS_CTR_DRBG_SEEDLEN]; | ^~~ In function ‘mbedtls_xor’, inlined from ‘ctr_drbg_update_internal’ at /<>/library/ctr_drbg.c:372:5: /<>/library/common.h:235:24: error: array subscript 48 is outside array bounds of ‘const unsigned char[48]’ [-Werror=array-bounds=] 235 | r[i] = a[i] ^ b[i]; | ~^~~ /<>/library/ctr_drbg.c: In function ‘ctr_drbg_update_internal’: /<>/library/ctr_drbg.c:333:57: note: at offset 48 into object ‘data’ of size [0, 48] 333 | const unsigned char data[MBEDTLS_CTR_DRBG_SEEDLEN]) | ^~ In function ‘mbedtls_xor’, inlined from ‘ctr_drbg_update_internal’ at /<>/library/ctr_drbg.c:372:5: /<>/library/common.h:235:14: error: array subscript 48 is outside array bounds of ‘unsigned char[48]’ [-Werror=array-bounds=] 235 | r[i] = a[i] ^ b[i]; | ~^ /<>/library/ctr_drbg.c: In function ‘ctr_drbg_update_internal’: /<>/library/ctr_drbg.c:335:19: note: at offset 48 into object ‘tmp’ of size 48 335 | unsigned char tmp[MBEDTLS_CTR_DRBG_SEEDLEN]; | ^~~ ... Upstream might be qualified to determine whether this is an mbedtls or gcc bug. The easiest short-term workaround to unblock the transition is export DEB_CFLAGS_MAINT_APPEND = -Wno-error=array-bounds --- End Message --- --- Begin Message --- Source: mbedtls Source-Version: 3.6.2-2 Done: Andrea Pappacoda We believe that the bug you reported is fixed in the latest version of mbedtls, 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 1085...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrea Pappacoda (supplier of updated mbedtls package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 06 Nov 2024 12:54:54 +0100 Source: mbedtls Architecture: source Version: 3.6.2-2 Distribution: unstable Urgency: medium Maintainer: Debian IoT Maintainers Changed-By: Andrea Pappacoda Closes: 1085354 Changes: mbedtls (3.6.2-2) unstable; urgency=medium . * d/patches: fix builds with GCC 14. Thanks to Adrian, Christian, and Emilio for the report! (Closes: #1085354) Checksums-Sha1: fce3b301a87da56c91c2a24fd27577b399b2d697 1937 mbedtls_3.6.2-2.dsc 55d4b755deccc31e16995c37aea3a67f4692e8fa 18544 mbedtls_3.6.2-2.debian.tar.xz Checksums-Sha256: 8001a535331600e4cf97bd4a92cb66a3fd7629c1c2f29992a31e826c3d4bd29c 1937 mbedtls_3.6.2-2.dsc 0165f453efadd283d3d76a90367c60b7257c656b10f723ebf7ceb91c9cc0821d 18544 mbedtls_3.6.2-2.debian.tar.xz Files: 4ed8efda01f173d6b69e8aa9616c09d6 1937 libs optional mbedtls_3.6.2-2.dsc e424a47a4ca59dfcbc58991983993854 18544 libs optional mbedtls_3.6.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQS6VuNIvZRFHt7JcAdKkgiiRVB3pwUCZytbhQAKCRBKkgiiRVB3 p8ksAQDRtKBpdbahTbJlWwH+0lpaHeId
Processed: tagging 1086836, tagging 1086754, tagging 1055447, tagging 1086645, tagging 1033761, tagging 1033528
Processing commands for cont...@bugs.debian.org:
> tags 1086836 + sid trixie
Bug #1086836 [src:rust-inflector] project is dead - successor seems to be cruet
Added tag(s) trixie and sid.
> tags 1086754 + sid trixie
Bug #1086754 {Done: Emmanuel Bourg } [jameica-datasource]
jameica-datasource - build-depends on dropped package.
Added tag(s) sid and trixie.
> tags 1055447 + trixie
Bug #1055447 {Done: Pierre Gruet } [src:htsjdk] htsjdk: FTBFS:
35741 tests completed, 9 failed, 10 skipped
Added tag(s) trixie.
> tags 1086645 + sid trixie
Bug #1086645 [src:dbus-test-runner] dbus-test-runner: autopkgtest regression:
test depends on obsolete package bustle
Added tag(s) sid and trixie.
> tags 1033761 + bullseye bookworm trixie sid
Bug #1033761 {Done: Debian FTP Masters }
[nautilus-scripts-manager] nautilus-scripts-manager: nautilus-script-manager
throws exception under bookworm
Added tag(s) bullseye, bookworm, trixie, and sid.
> tags 1033528 + bookworm trixie sid
Bug #1033528 {Done: Drew Parsons } [src:apbs] apbs:
autopkgtest regression: apbs_tester.py': [Errno 2] No such file or directory
Added tag(s) bookworm, trixie, and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1033528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033528
1033761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033761
1055447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055447
1086645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086645
1086754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086754
1086836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1086836 is forwarded to https://github.com/whatisinternet/Inflector/issues/83
Processing commands for cont...@bugs.debian.org: > forwarded 1086836 https://github.com/whatisinternet/Inflector/issues/83 Bug #1086836 [src:rust-inflector] project is dead - successor seems to be cruet Set Bug forwarded-to-address to 'https://github.com/whatisinternet/Inflector/issues/83'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1086836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1086799 marked as pending in burrow
Processing control commands: > tag -1 pending Bug #1086799 [src:burrow] burrow: FTBFS on riscv64: undefined: syscall.Dup2 Added tag(s) pending. -- 1086799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1086799: marked as done (burrow: FTBFS on riscv64: undefined: syscall.Dup2)
Your message dated Wed, 06 Nov 2024 13:49:06 +
with message-id
and subject line Bug#1086799: fixed in burrow 1.2.1-4
has caused the Debian Bug report #1086799,
regarding burrow: FTBFS on riscv64: undefined: syscall.Dup2
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.)
--
1086799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: burrow
Version: 1.2.1-3
Severity: serious
Tags: ftbfs patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org, mengz...@iscas.ac.cn
Dear Maintainer,
Thanks for the build support on riscv64 in previous upload.
But unforuntately, there is still failed to build it on riscv64:
```
github.com/linkedin/Burrow/core/internal/zookeeper
github.com/linkedin/Burrow/core
# github.com/linkedin/Burrow/core
src/github.com/linkedin/Burrow/core/open_out_log_unix.go:22:17: undefined:
syscall.Dup2
dh_auto_build: error: cd obj-riscv64-linux-gnu && go install -trimpath -v -p 4
github.com/linkedin/Burrow github.com/linkedin/Burrow/core
github.com/linkedin/Burrow/core/internal
github.com/linkedin/Burrow/core/internal/cluster
github.com/linkedin/Burrow/core/internal/consumer
github.com/linkedin/Burrow/core/internal/evaluator
github.com/linkedin/Burrow/core/internal/helpers
github.com/linkedin/Burrow/core/internal/httpserver
github.com/linkedin/Burrow/core/internal/notifier
github.com/linkedin/Burrow/core/internal/storage
github.com/linkedin/Burrow/core/internal/zookeeper
github.com/linkedin/Burrow/core/protocol returned exit code 1
make: *** [debian/rules:11: binary-arch] Error 25
```
The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=burrow&arch=riscv64&ver=1.2.1-3&stamp=1730811760&raw=0
It seems PR #763 of upstream which supports riscv64 did not included
correctly in the patch(it's really esay to get lost indeed).
Thanks for Meng Zhuo's kindly help and proposed patch, the ftbfs issue
has been fixed with the attached patch and has been tested on my
Unmatched board. Could you apply it at next upload? TIA.
--
Regards,
--
Bo YU
diff -Nru burrow-1.2.1/debian/changelog burrow-1.2.1/debian/changelog
--- burrow-1.2.1/debian/changelog 2024-11-05 09:00:00.0 +0800
+++ burrow-1.2.1/debian/changelog 2024-11-06 12:04:24.0 +0800
@@ -1,3 +1,10 @@
+burrow (1.2.1-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs on riscv64. (Closes: #-1)
+
+ -- Bo YU Wed, 06 Nov 2024 12:04:24 +0800
+
burrow (1.2.1-3) unstable; urgency=medium
* Team upload.
diff -Nru burrow-1.2.1/debian/patches/riscv64-loong64.patch
burrow-1.2.1/debian/patches/riscv64-loong64.patch
--- burrow-1.2.1/debian/patches/riscv64-loong64.patch 2024-11-05
08:57:36.0 +0800
+++ burrow-1.2.1/debian/patches/riscv64-loong64.patch 2024-11-06
12:04:24.0 +0800
@@ -1,9 +1,12 @@
Description: Adapt upstream PR for riscv64 and loong64
Author: Gianfranco Costamagna
+Meng Zhuo
Bug-Debian: https://bugs.debian.org/1042514
Bug-Debian: https://bugs.debian.org/1055081
Last-Update: 2024-11-02
+Index: b/core/open_out_log_linux_loong64.go
+===
--- /dev/null
+++ b/core/open_out_log_linux_loong64.go
@@ -0,0 +1,23 @@
@@ -30,11 +33,14 @@
+func internalDup2(oldfd uintptr, newfd uintptr) error {
+ return syscall.Dup3(int(oldfd), int(newfd), 0)
+}
+Index: b/core/open_out_log_linux_dup3.go
+===
--- /dev/null
+++ b/core/open_out_log_linux_dup3.go
-@@ -0,0 +1,24 @@
-+// +build linux,arm64
-+// +build linux,riscv64
+@@ -0,0 +1,25 @@
++//go:build linux && (arm64 || riscv64)
++// +build linux
++// +build arm64,riscv64
+
+/* Copyright 2017 LinkedIn Corp. Licensed under the Apache License, Version
+ * 2.0 (the "License"); you may not use this file except in compliance with
@@ -57,12 +63,45 @@
+func internalDup2(oldfd uintptr, newfd uintptr) error {
+ return syscall.Dup3(int(oldfd), int(newfd), 0)
+}
+Index: b/core/open_out_log_unix.go
+===
--- a/core/open_out_log_unix.go
+++ b/core/open_out_log_unix.go
-@@ -1,5 +1,6 @@
+@@ -1,5 +1,8 @@
++//go:build !windows && !(linux && arm64) && !(linux && loong64) && !(linux &&
riscv64)
// +build !windows
- // +build !arm64
-+// +build !loong64
+-// +build !arm64
++//
Bug#1085505: marked as done (petsc: Current Petsc packages incompatible with openmpi 5.x in sid)
Your message dated Wed, 6 Nov 2024 10:42:02 +0100 with message-id <1ca08008-51c2-49a3-8d3d-c36f9585a...@debian.org> and subject line Re: petsc: Current Petsc packages incompatible with openmpi 5.x in sid has caused the Debian Bug report #1085505, regarding petsc: Current Petsc packages incompatible with openmpi 5.x in sid 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.) -- 1085505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: petsc Version: 3.21.6+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, with the recent release on sid of openmpi version 5.0.x, Petsc and Slepc became uninstallable on a sid system, unless openmpi is downgraded and/or held to a 4.x version. Please update Petsc to make it compatible with current openmpi in sid (or at least another available MPI implementation on sid). Thanks in advance, best regards Giacomo Mulas -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.11.2-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 3.21.6+dfsg1-2 On Sun, 20 Oct 2024 12:26:52 + Francesco Ballarin wrote: Source: petsc Followup-For: Bug #1085505 X-Debbugs-Cc: giacomo.mu...@inaf.it, francesco.balla...@unicatt.it, dpars...@debian.org Hi Giacomo, we already encountered this in Bug #1085405, and released this morning a fix PETSc 3.21.6+dfsg1-2. Let's close this bug then. Emilio--- End Message ---
Bug#1069486: marked as done (priv-wrapper: FTBFS on armhf: 1: [ LINE ] --- ./tests/test_setrlimit.c:63: error: Failure!)
Your message dated Wed, 06 Nov 2024 09:19:55 + with message-id and subject line Bug#1069486: fixed in priv-wrapper 1.0.1-4 has caused the Debian Bug report #1069486, regarding priv-wrapper: FTBFS on armhf: 1: [ LINE ] --- ./tests/test_setrlimit.c:63: error: Failure! to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069486 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: priv-wrapper Version: 1.0.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[1]: Entering directory '/<>/build' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j4 > UpdateCTestConfiguration from :/<>/build/DartConfiguration.tcl > Parse Config file:/<>/build/DartConfiguration.tcl > UpdateCTestConfiguration from :/<>/build/DartConfiguration.tcl > Parse Config file:/<>/build/DartConfiguration.tcl > Test project /<>/build > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: test_setrlimit > > 1: Test command: /<>/build/tests/test_setrlimit > 1: Working Directory: /<>/build/tests > 1: Environment variables: > 1: LD_PRELOAD=/<>/build/src/libpriv_wrapper.so > 1: Test timeout computed to be: 1500 > test 2 > Start 2: test_chroot > > 2: Test command: /<>/build/tests/test_chroot > 2: Working Directory: /<>/build/tests > 2: Environment variables: > 2: LD_PRELOAD=/<>/build/src/libpriv_wrapper.so > 2: Test timeout computed to be: 1500 > test 3 > Start 3: test_prctl > > 3: Test command: /<>/build/tests/test_prctl > 3: Working Directory: /<>/build/tests > 3: Environment variables: > 3: LD_PRELOAD=/<>/build/src/libpriv_wrapper.so > 3: Test timeout computed to be: 1500 > 1: [==] tests: Running 3 test(s). > 1: [ RUN ] test_RLIMIT_FSIZE > 1: [ OK ] test_RLIMIT_FSIZE > 1: [ RUN ] test_RLIMIT_FSIZE_fail > 1: [ ERROR ] --- rc < 0, errno(22): Invalid argument > 1: [ LINE ] --- ./tests/test_setrlimit.c:63: error: Failure! > 1: [ FAILED ] test_RLIMIT_FSIZE_fail > 1: [ RUN ] test_setrlimit_combination > 1: [ OK ] test_setrlimit_combination > 1: [==] tests: 3 test(s) run. > 1: [ PASSED ] 2 test(s). > 1: [ FAILED ] tests: 1 test(s), listed below: > 1: [ FAILED ] test_RLIMIT_FSIZE_fail > 1: > 1: 1 FAILED TEST(S) > 2: [==] tests: Running 2 test(s). > 2: [ RUN ] test_chroot > 2: [ OK ] test_chroot > 2: [ RUN ] test_chroot_fail > 2: [ OK ] test_chroot_fail > 2: [==] tests: 2 test(s) run. > 2: [ PASSED ] 2 test(s). > 1/3 Test #1: test_setrlimit ...***Failed0.00 sec > [==] tests: Running 3 test(s). > [ RUN ] test_RLIMIT_FSIZE > [ OK ] test_RLIMIT_FSIZE > [ RUN ] test_RLIMIT_FSIZE_fail > [ ERROR ] --- rc < 0, errno(22): Invalid argument > [ LINE ] --- ./tests/test_setrlimit.c:63: error: Failure! > [ FAILED ] test_RLIMIT_FSIZE_fail > [ RUN ] test_setrlimit_combination > [ OK ] test_setrlimit_combination > [==] tests: 3 test(s) run. > [ PASSED ] 2 test(s). > [ FAILED ] tests: 1 test(s), listed below: > [ FAILED ] test_RLIMIT_FSIZE_fail > > 1 FAILED TEST(S) > > 2/3 Test #2: test_chroot .. Passed0.00 sec > 3: [==] tests: Running 7 test(s). > 3: [ RUN ] test_prctl_ALL > 3: [ OK ] test_prctl_ALL > 3: [ RUN ] test_prctl_PR_SET_SECCOMP > 3: [ OK ] test_prctl_PR_SET_SECCOMP > 3: [ RUN ] test_prctl_PR_SET_SECCOMP_fail > 3: [ OK ] test_prctl_PR_SET_SECCOMP_fail > 3: [ RUN ] test_prctl_PR_SET_NO_NEW_PRIVS > 3: [ OK ] test_prctl_PR_SET_NO_NEW_PRIVS > 3: [ RUN ] test_prctl_PR_SET_NO_NEW_PRIVS_fail > 3: [ OK ] test_prctl_PR_SET_NO_NEW_PRIVS_fail > 3: [ RUN ] test_prctl_PR_SET_DUMPABLE > 3: [ OK ] test_pr
Processed: [patch, pending] mpg321: ftbfs with GCC-14
Processing control commands: > tags -1 patch Bug #1075291 [src:mpg321] mpg321: ftbfs with GCC-14 Added tag(s) patch. > tags -1 pending Bug #1075291 [src:mpg321] mpg321: ftbfs with GCC-14 Added tag(s) pending. -- 1075291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1076245: marked as done (lintian-brush: hangs and when killed leaved lock in Git repository)
Your message dated Wed, 06 Nov 2024 03:34:21 + with message-id and subject line Bug#1076245: fixed in lintian-brush 0.158 has caused the Debian Bug report #1076245, regarding lintian-brush: hangs and when killed leaved lock in Git repository 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.) -- 1076245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian-brush Version: 0.155 Severity: grave Justification: renders package unusable Hi, I'm currently do not use lintian-brush extensively currently (since I reduced my packaging work in DPL) term but *always* when using it hangs. Not even some ^C in terminal kann bring back some prompt I have to kill the process manually or close the terminal. After this some lock files are remaining in the Git repository which need to be manually removed. Latest example https://salsa.debian.org/med-team/tao-json tao-json(master) $ lintian-brush 88/153 ^C^C^C^C^C This is not only true for this specific package but for *all* packages I tried in the last couple of weeks. Kind regards Andreas. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian-brush depends on: ii devscripts 2.23.7 ii libc62.38-14 ii libgcc-s114.1.0-3 ii liblzma5 5.6.2-2 ii libpython3.11t64 3.11.9-1 ii libssl3t64 3.2.2-1 ii python3 3.12.2-1 ii python3-breezy 3.3.6-1+b1 ii python3-debian 0.1.49 ii python3-debmutate0.68 ii python3-distro-info 1.7 ii python3-dulwich 0.21.6-1+b1 ii python3-iniparse 0.5-2 ii python3-iso8601 1.0.2-1 ii python3-levenshtein 0.25.1-3 ii python3-psycopg2 2.9.9-1+b1 ii python3-pyinotify0.9.6-2 ii python3-ruamel.yaml 0.18.6+ds-3 ii python3-semver 2.10.2-3 ii python3-tomlkit 0.12.5-1 ii python3-tqdm 4.66.4-1 ii python3-upstream-ontologist 0.1.37-1 Versions of packages lintian-brush recommends: ii debhelper 13.16 ii decopy0.2.4.8-0.1 ii dos2unix 7.5.2-1 ii gpg 2.2.43-7 ii lintian 2.117.0 ii ognibuild 0.0.20-1 ii python3-bs4 4.12.3-1 ii python3-docutils 0.20.1+dfsg-3 ii python3-lxml 5.2.1-1 ii python3-markdown 3.6-1 Versions of packages lintian-brush suggests: ii brz-debian 2.8.79 ii git-buildpackage 0.9.34 ii gnome-pkg-tools0.22.9 ii po-debconf 1.0.21+nmu1 ii postgresql-common 261 -- no debconf information --- End Message --- --- Begin Message --- Source: lintian-brush Source-Version: 0.158 Done: Jelmer Vernooij We believe that the bug you reported is fixed in the latest version of lintian-brush, 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 1076...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated lintian-brush package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Jun 2024 15:44:16 +0100 Source: lintian-brush Architecture: source Version: 0.158 Distribution: experimental Urgency: medium Maintainer: Jelmer Vernooij Changed-By: Jelmer Vernooij Closes: 1075953 1076245 1076706 1082363 Changes: lintian-brush (0.158) experimental; urgency=medium .
Bug#1082363: marked as done (FTBFS: error: failed to select a version for the requirement `clap = "^4, <4.5"`)
Your message dated Wed, 06 Nov 2024 03:34:21 +
with message-id
and subject line Bug#1082363: fixed in lintian-brush 0.158
has caused the Debian Bug report #1082363,
regarding FTBFS: error: failed to select a version for the requirement `clap =
"^4, <4.5"`
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.)
--
1082363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lintian-brush
Version: 0.157
Severity: serious
Tags: ftbfs
Justification: FTBFS
Dear maintainer,
During a test rebuild, lintian-brush failed to rebuild.
---
[...]
running build_ext
running build_rust
error: failed to select a version for the requirement `clap = "^4, <4.5"`
candidate versions found which didn't match: 4.5.16
location searched: directory source `/usr/share/cargo/registry` (which is
replacing registry `crates-io`)
required by package `lintian-brush v0.157.0 (/<>/lintian-brush)`
perhaps a crate was updated and forgotten to be re-vendored?
error: `cargo metadata --manifest-path debianize/Cargo.toml --format-version 1`
failed with code 101
-- Output captured from stdout:
ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:389: build: plugin pyproject failed with: exit code=1:
python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir
/<>/.pybuild/cpython3_3.12
dh_auto_build: error: pybuild --build -i python{version} -p 3.12 returned exit
code 13
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Build finished at 2024-09-19T22:01:10Z
---
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/799351/
About the archive rebuild: The build was made on debusine.debian.net,
on arm64 using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/38935/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Stefano
--- End Message ---
--- Begin Message ---
Source: lintian-brush
Source-Version: 0.158
Done: Jelmer Vernooij
We believe that the bug you reported is fixed in the latest version of
lintian-brush, 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 1082...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jelmer Vernooij (supplier of updated lintian-brush package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 27 Jun 2024 15:44:16 +0100
Source: lintian-brush
Architecture: source
Version: 0.158
Distribution: experimental
Urgency: medium
Maintainer: Jelmer Vernooij
Changed-By: Jelmer Vernooij
Closes: 1075953 1076245 1076706 1082363
Changes:
lintian-brush (0.158) experimental; urgency=medium
.
* Bump pyo3 to 0.22.
* Drop dependency on dead python3-pyinotify. Closes: #1075953
* Add hint about misisng Python package when it can't be found.
* Rebuild against python 3.12. Closes: #1076706
* Support newer clap. Closes: #1082363
* When running fixers, restrict how long they can be running.
Closes: #1076245
Checksums-Sha1:
2d56c2629cf19e8931c8e48b3b35b8b400e1de3b 3290 lintian-brush_0.158.dsc
36b27c195d9530951d1fbb448ce40e1bbc8e5cfe 1101164 lintian-brush_0.158.tar.xz
b1a1b4c51f96df2449aee6b422d626820e85e1f7 56025
lintian-brush_0.158_source.buildinfo
Checksums-Sha256:
2255ac2d1c2a9e71f3fddc1ee14a6042e6311eebb240140159d3f584f3e9de9f 3290
lintian-brush_0.158.dsc
ef0a5418dfbce79622a7265965f1dd8a52e1
Processed: Re: Bug#1086795: rsyslog: Segmentation fault
Processing control commands: > severity -1 normal Bug #1086795 [rsyslog] rsyslog: Segmentation fault Severity set to 'normal' from 'grave' -- 1086795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1086791: lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant
Processing control commands: > severity -1 important Bug #1086791 [src:lziprecover] lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant Severity set to 'important' from 'serious' > reassign -1 gcc-14 Bug #1086791 [src:lziprecover] lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant Bug reassigned from package 'src:lziprecover' to 'gcc-14'. No longer marked as found in versions lziprecover/1.25~pre1-1. Ignoring request to alter fixed versions of bug #1086791 to the same values previously set > retitle -1 gcc: riscv64 backend emits large relocations due to loop strength > reduction Bug #1086791 [gcc-14] lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant Changed Bug title to 'gcc: riscv64 backend emits large relocations due to loop strength reduction' from 'lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant'. > forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117460 Bug #1086791 [gcc-14] gcc: riscv64 backend emits large relocations due to loop strength reduction Set Bug forwarded-to-address to 'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117460'. > affects -1 lziprecover Bug #1086791 [gcc-14] gcc: riscv64 backend emits large relocations due to loop strength reduction Added indication that 1086791 affects lziprecover -- 1086791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074865: marked as done (catdvi: ftbfs with GCC-14)
Your message dated Tue, 05 Nov 2024 22:19:07 +
with message-id
and subject line Bug#1074865: fixed in catdvi 0.14-16
has caused the Debian Bug report #1074865,
regarding catdvi: ftbfs with GCC-14
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.)
--
1074865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:catdvi
Version: 0.14-15
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/catdvi_0.14-15_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
Sufficient free space for build
User Environment
APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-3ff7698b-91e7-4a89-b929-ec22c37cb3c7
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42
dpkg-buildpackage
-
Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package catdvi
dpkg-buildpackage: info: source version 0.14-15
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Petter Reinholdtsen
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
debian/rules clean
test -x debian/rules
rm -f debian/stamp-makefile-build debian/stamp-makefile-install
/usr/bin/make -C . -k distclean
make[1]: Entering directory '/<>'
GNUmakefile:43: *** Sorry. Stop.
make[1]: Leaving directory '/<>'
make: [/usr/share/cdbs/1/class/makefile.mk:91: makefile-clean] Error 2 (ignored)
rm -f debian/stamp-autotools
rmdir --ignore-fail-on-non-empty .
rmdir: failed to remove '.': Invalid argument
make: [/usr/share/cdbs/1/class/autotools.mk:64: makefile-clean] Error 1
(ignored)
dh_clean
rm -f debian/stamp-autotools-files
if [ -f update-config-stamp ] ; then \
mv d-r-orig/* . ; \
rmdir d-r-orig ; \
rm update-config-stamp ; \
fi
debian/rules binary
test -x debian/rules
dh_testroot
dh_prep
dh_installdirs -A
mkdir -p "."
mkdir d-r-orig
cp -p *.d version.h d-r-orig
touch update-config-stamp
touch debian/stamp-autotools-files
chmod a+x /<>/./configure
mkdir -p .
cd . && CFLAGS="-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection"
CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection"
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro"
/<>/./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir="\${prefix}/include" --mandir="\${prefix}/share/man"
--infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var
--libexecdir="\${prefix}/lib/catdvi" --srcdir=. --disable-maintainer-mode
--disable-dependency-tracking --disable-silent-rules --prefix=/usr
--mandir=\${prefix}/share/man
creating cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/&
Bug#1086366: marked as done (nfdump: FTBFS: FAIL: runtest.sh)
Your message dated Tue, 05 Nov 2024 22:05:52 + with message-id and subject line Bug#1086366: fixed in nfdump 1.7.5-1 has caused the Debian Bug report #1086366, regarding nfdump: FTBFS: FAIL: runtest.sh 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.) -- 1086366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nfdump Version: 1.7.4-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 libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:18: installing './compile' configure.ac:27: installing './config.guess' [... snipped ...] tcp flags= 0x02 ..S. src port =80 @@ -111,9 +111,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841031310 [2019-07-11 10:30:31.310] - last = 1562841031360 [2019-07-11 10:30:31.360] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833831310 [2019-07-11 10:30:31.310] + last = 1562833831360 [2019-07-11 10:30:31.360] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x10 ...A src port =80 @@ -142,9 +142,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841032310 [2019-07-11 10:30:32.310] - last = 1562841032360 [2019-07-11 10:30:32.360] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833832310 [2019-07-11 10:30:32.310] + last = 1562833832360 [2019-07-11 10:30:32.360] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x01 ...F src port =80 @@ -173,9 +173,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841032311 [2019-07-11 10:30:32.311] - last = 1562841032361 [2019-07-11 10:30:32.361] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833832311 [2019-07-11 10:30:32.311] + last = 1562833832361 [2019-07-11 10:30:32.361] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x12 ...A..S. src port = 2 @@ -204,9 +204,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841033311 [2019-07-11 10:30:33.311] - last = 1562841033361 [2019-07-11 10:30:33.361] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833833311 [2019-07-11 10:30:33.311] + last = 1562833833361 [2019-07-11 10:30:33.361] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x10 ...A src port = 2 @@ -235,9 +235,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841034311 [2019-07-11 10:30:34.311] - last = 1562841034361 [2019-07-11 10:30:34.361] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833834311 [2019-07-11 10:30:34.311] + last = 1562833834361 [2019-07-11 10:30:34.361] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x01 ...F src port = 2 @@ -266,9 +266,9 @@ engine type =60 engine ID= 5 export sysid =
Bug#1086735: marked as done (libx11-6: buggy shlibs, libx11-xcb1 vs. libx11-6-udeb)
Your message dated Tue, 05 Nov 2024 20:34:49 + with message-id and subject line Bug#1086735: fixed in libx11 2:1.8.10-2 has caused the Debian Bug report #1086735, regarding libx11-6: buggy shlibs, libx11-xcb1 vs. libx11-6-udeb 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.) -- 1086735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libx11-6 Version: 2:1.8.10-1 Severity: serious Tags: d-i Justification: broken shlibs, breaks udebs, etc. X-Debbugs-Cc: debian-b...@lists.debian.org Hi, [ Now turning the initial mail ping into a proper bug report. ] Spotted via dose's reporting lots of uninstallable udebs on arm64: the new shlibs for libx11-6 is broken, with various libx* packages now depending on libx11-xcb1 (not a udeb). https://d-i.debian.org/dose/graph-unstable-arm64.png The new debian/rules has: override_dh_makeshlibs: dh_makeshlibs -a -plibx11-6 -V'libx11-6 (>= 2:1.6.0)' --add-udeb=libx11-6-udeb -- -c4 dh_makeshlibs -a -plibx11-xcb1 -V'libx11-xcb1' -- -c4 dh_makeshlibs -a -Nlibx11-6 -Nlibx11-xcb1 -- -c4 which leads to the following for libx11-6.shlibs (amd64): libX11 6 libx11-xcb1 udeb: libX11 6 libx11-xcb1 Meanwhile, libx11-xcb1 has: libX11-xcb 1 libx11-xcb1 which seems to match the intent in changelog. Out of curiosity, pausing the build after the first dh_makeshlibs call, the shlibs for libx11-6 is indeed correct at that point: libX11 6 libx11-6 (>= 2:1.6.0) udeb: libX11 6 libx11-6-udeb (>= 2:1.6.0) and the second call is responsible for busting it up, since afterwards it's amended to become what's found in the package: libX11 6 libx11-xcb1 udeb: libX11 6 libx11-xcb1 So it looks like some confusion due to the -a/-p/-N combinations? Going back to pausing between first and second dh_makeshlibs calls, here's the slibs file for libx11-xcb1… libX11-xcb 1 libx11-6 (>= 2:1.6.0) udeb: libX11-xcb 1 libx11-6 (>= 2:1.6.0) which convinces me the flag combinations aren't fine as they are. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant --- End Message --- --- Begin Message --- Source: libx11 Source-Version: 2:1.8.10-2 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of libx11, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated libx11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 05 Nov 2024 21:10:08 +0100 Source: libx11 Architecture: source Version: 2:1.8.10-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Julien Cristau Closes: 1086735 Changes: libx11 (2:1.8.10-2) unstable; urgency=medium . * Fix dh_makeshlibs calls to generate correct libx11-6.shlibs (closes: #1086735) Checksums-Sha1: 719db6c0ed5617d5c3cd99d592f3d7d7d0ae1923 2519 libx11_1.8.10-2.dsc ddc65966bec14b0212caa956d755b6ec4a28448f 74852 libx11_1.8.10-2.diff.gz Checksums-Sha256: 3c251eb0a8ac14ddaeac6ca1720d993e1164086b42c5f979df428ada4f029479 2519 libx11_1.8.10-2.dsc 6c5853a7ab0c012a20821396122509da105dcf432d33d52da98898cc0b0d391e 74852 libx11_1.8.10-2.diff.gz Files: 5324028b26647d399e52c99f31516fcb 2519 x11 optional libx11_1.8.10-2.dsc a262b4a89b574a6c4512d58195767b17 74852 x11 optional libx11_1.8.10-2.diff.gz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmcqfBsUHGpjcmlzdGF1 QGRlYmlhbi5vcmcACgkQnbAjVVb4z60svg//fKeJLkrPnUdf/BEhs//MAGI52mzK 7lEb80Txx77qbJcx6fx9AdRhvu7xpgl0wrVXsKbFtTig68LsKYsWkE2kd3+GsneW /TcLWpTfS/FZ2mU9A6fR/unREDzK6fULNo8N8ISIO0mip3VsksQHNVIHvtAL3wFl hSJOMeu/NjYq7wjOzZawpYdiSDo8CyY2Xi+CVHrMvX0tbHTkgm4VXxFCQ1J21sp8 e7FSE046XQpctbJ/EKRy7IxIEenH3epJ4VhFZgI0cb4OqD7MhtMj3LcA7avpZewa GgRnc/S/dlrS4A4OlYnznRgNVysQcpv+cjSiVOkhmG/jLNVm27wnEIsY2y4ElYi
Bug#1086676: marked as done (Not installable with python3-pycodestyle/sid)
Your message dated Tue, 05 Nov 2024 20:35:18 + with message-id and subject line Bug#1086676: fixed in python-flake8 7.1.1-2 has caused the Debian Bug report #1086676, regarding Not installable with python3-pycodestyle/sid 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.) -- 1086676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-flake8 Version: 7.1.1-1 Severity: serious pycodestyle 2.12.1-1 was just uploaded, making python3-flake8 not installable. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.10.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-flake8 depends on: ii python3 3.12.6-1 ii python3-mccabe 0.7.0-1 ii python3-pycodestyle 2.11.1-1 ii python3-pyflakes 3.2.0-1 ii python3-setuptools 75.2.0-1 python3-flake8 recommends no packages. python3-flake8 suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Source: python-flake8 Source-Version: 7.1.1-2 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of python-flake8, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated python-flake8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 05 Nov 2024 17:02:40 -0300 Source: python-flake8 Architecture: source Version: 7.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Emmanuel Arias Closes: 1086676 Changes: python-flake8 (7.1.1-2) unstable; urgency=medium . * Team upload * d/control: Bump pycodestyle dependencies according to upstream (Closes: #1086676). Checksums-Sha1: eec13942a82c2b649b45631858022e103f1b1f29 2399 python-flake8_7.1.1-2.dsc d9f73434c57e7c3f7d6362a5a17a812d1bde13e6 8812 python-flake8_7.1.1-2.debian.tar.xz 4d691df50f615fb95540ee2a88cc417e30755502 7637 python-flake8_7.1.1-2_amd64.buildinfo Checksums-Sha256: 8dc84b418e11adf03de417795c98f0dc5ea0b955dc479e34d818dec5f5760d02 2399 python-flake8_7.1.1-2.dsc 37648be8a8cc1b217117d2fb89e7e0bc09723576c458d946b28d6246ae744382 8812 python-flake8_7.1.1-2.debian.tar.xz 28ed577d7f860385adf9198416e20ccca9b956a12a92b6d3a9514529265fe8b2 7637 python-flake8_7.1.1-2_amd64.buildinfo Files: 2d89003bb51d64088be7c49653013be0 2399 python optional python-flake8_7.1.1-2.dsc 68e71bce9791dc24ce643922ecf8cb5d 8812 python optional python-flake8_7.1.1-2.debian.tar.xz a886aff16d2160993441aaffd9ef0558 7637 python optional python-flake8_7.1.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmcqfioSHGVhbWFudUBk ZWJpYW4ub3JnAAoJEPqd7F3hHGPxLR4QAKOjZy/dyUJQh31X8u8HeKIusxPUWiFc AWp9X4faeDJS2Mk6mZeL4Y+rvNZWxFl5fC6U94NzwITIKL3T0RTm9BJPH+0lDJVZ zNKA5WjAdFqCTMSjwECvF9xF2ERBkNVJ8oEDbN2kgTvtcesaoRfTigR6KcqqVlBP uYcIkxQdtPZ0iIvbsKD9NYodhjzEjMSmV6lX4Mzf5GVkoK8bNHoVh0WMveXHgc6M RQcURVi6SL1wNk5ajDtGh4HoWAxrYBVB4iGGzpO9AqvBEkwH/CaUUm/W53z3BSNV uLeshU9GwVlFoPDs2pjIirMAEjOrRoiCrbRLIIcqvROxAOzMNBDw++as89PMWCH6 vVAjRGhTn8CYfkxCJfHIryZH0NsZo6ABzm13XZctHF1IDMqA1caliCsM3mP4Daqs zRpZp9SD6psTt9coUxuUHRhl03sHvFiNDpNBJWuwjFJvOyyheV4PGULpJNxB4Qq+ kloDDFspaLaHsVvm9glnHLW+lOIbM822BjslYBqXhwwuopjB6h132Weptd5RCcPO ejtUvMx7LK6rfDZjIai1+NEjdoiPg1dTcuRH4dMb2sT0qvTlRrhAU5Da/iyeP+/D 4BXC9Ri6ieyQvUxkv4D2qaxhMlrHQMe95TrMTIGkvHh5ttDjR9oJkeTjDnHTgjvj lKG9RnL3QcMS =zIpv -END PGP SIGNATURE- pgp6TNFX32atq.pgp Description: PGP signature --- End Message ---
Processed: Bug#1086634 marked as pending in veyon
Processing control commands: > tag -1 pending Bug #1086634 [src:veyon] veyon: FTBFS on armel: /usr/include/c++/14/bits/atomic_base.h:501:(.text+0xa5d0): undefined reference to `__atomic_load_8' Ignoring request to alter tags of bug #1086634 to the same tags previously set -- 1086634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:wlroots: fails to migrate to testing for too long
Processing control commands: > close -1 0.18.1-1 Bug #1086786 [src:wlroots] src:wlroots: fails to migrate to testing for too long Marked as fixed in versions wlroots/0.18.1-1. Bug #1086786 [src:wlroots] src:wlroots: fails to migrate to testing for too long Marked Bug as done -- 1086786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: autopkgtest: test command2 is failing
Processing control commands: > severity -1 serious Bug #1086488 [src:xtensor-blas] autopkgtest: test command2 is failing Severity set to 'serious' from 'important' -- 1086488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1086676 marked as pending in python-flake8
Processing control commands: > tag -1 pending Bug #1086676 [python3-flake8] Not installable with python3-pycodestyle/sid Ignoring request to alter tags of bug #1086676 to the same tags previously set -- 1086676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1086676
Processing commands for cont...@bugs.debian.org: > tags 1086676 + pending Bug #1086676 [python3-flake8] Not installable with python3-pycodestyle/sid Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1086676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forwarded 1086621 https://gitlab.com/charliecloud/main/-/issues/1929
Processing commands for cont...@bugs.debian.org: > forwarded 1086621 https://gitlab.com/charliecloud/main/-/issues/1929 Bug #1086621 [src:charliecloud] charliecloud: FTBFS: sphinx.errors.SphinxWarning: Calling get_html_theme_path is deprecated. If you are calling it to define html_theme_path, you are safe to remove that code. Set Bug forwarded-to-address to 'https://gitlab.com/charliecloud/main/-/issues/1929'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1086621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1086758: elpa-magit: 4.1.2-1 doesn't depends on elpa-git-commit but still requires it
Processing control commands: > severity -1 serious Bug #1086758 [elpa-magit] elpa-magit: 4.1.2-1 doesn't depends on elpa-git-commit but still requires it Severity set to 'serious' from 'normal' -- 1086758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073443: marked as done (pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Tue, 05 Nov 2024 16:20:04 +
with message-id
and subject line Bug#1073443: fixed in pytest-rerunfailures 14.0-2
has caused the Debian Bug report #1073443,
regarding pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1073443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-rerunfailures
Version: 12.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
> module
> I: pybuild base:311: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_pytest-rerunfailures
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> copying pytest_rerunfailures.py -> build/lib
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> copying build/lib/pytest_rerunfailures.py -> build/bdist.linux-x86_64/wheel
> running install_egg_info
> running egg_info
> creating pytest_rerunfailures.egg-info
> writing pytest_rerunfailures.egg-info/PKG-INFO
> writing dependency_links to pytest_rerunfailures.egg-info/dependency_links.txt
> writing entry points to pytest_rerunfailures.egg-info/entry_points.txt
> writing requirements to pytest_rerunfailures.egg-info/requires.txt
> writing top-level names to pytest_rerunfailures.egg-info/top_level.txt
> writing manifest file 'pytest_rerunfailures.egg-info/SOURCES.txt'
> reading manifest file 'pytest_rerunfailures.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'pytest_rerunfailures.egg-info/SOURCES.txt'
> Copying pytest_rerunfailures.egg-info to
> build/bdist.linux-x86_64/wheel/pytest_rerunfailures-12.0.egg-info
> running install_scripts
> creating
> build/bdist.linux-x86_64/wheel/pytest_rerunfailures-12.0.dist-info/WHEEL
> creating
> '/<>/.pybuild/cpython3_3.12_pytest-rerunfailures/.tmp-ref1teng/pytest_rerunfailures-12.0-py3-none-any.whl'
> and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'pytest_rerunfailures.py'
> adding 'pytest_rerunfailures-12.0.dist-info/LICENSE'
> adding 'pytest_rerunfailures-12.0.dist-info/METADATA'
> adding 'pytest_rerunfailures-12.0.dist-info/WHEEL'
> adding 'pytest_rerunfailures-12.0.dist-info/entry_points.txt'
> adding 'pytest_rerunfailures-12.0.dist-info/top_level.txt'
> adding 'pytest_rerunfailures-12.0.dist-info/RECORD'
> removing build/bdist.linux-x86_64/wheel
> Successfully built pytest_rerunfailures-12.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with
> "installer" module
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build"
> module
> I: pybuild base:311: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_pytest-rerunfailures
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64/wheel
> copying build/lib/pytest_rerunfailures.py -> build/bdist.linux-x86_64/wheel
> running install_egg_info
> running egg_info
> writing pytest_rerunfailures.egg-info/PKG-INFO
> writing dependency_links to pytest_rerunfailures.egg-info/dependency_links.txt
> writing entry points to pytest_rerunfailures.egg-info/entry_points.
Processed: Re: Bug#1075647: xarclock: ftbfs with GCC-14
Processing control commands: > tags -1 patch Bug #1075647 [src:xarclock] xarclock: ftbfs with GCC-14 Added tag(s) patch. -- 1075647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1073443 marked as pending in pytest-rerunfailures
Processing control commands:
> tag -1 pending
Bug #1073443 [src:pytest-rerunfailures] pytest-rerunfailures: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12
3.11" returned exit code 13
Added tag(s) pending.
--
1073443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1086552: marked as done (mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame)
Your message dated Tue, 05 Nov 2024 15:07:21 + with message-id and subject line Bug#1086552: fixed in mutter 47.1-2 has caused the Debian Bug report #1086552, regarding mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame 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.) -- 1086552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mutter Version: 47.1-1 Severity: serious Tags: ftbfs experimental Justification: fails to build from source (but built successfully in the past) mutter failed to build from source on several architectures, including 'all', with this failure in the "mutter:clutter+clutter/conform / timeline" test-case: > 1..1 > # Start of timeline tests > Without delay... > 3: Doing frame 10, delta = 0 > 2: Doing frame 0, delta = 0 > 1: Doing frame 0, delta = 0 > # libmutter-INFO: Acquired name org.gnome.Mutter.InputMapping > # libmutter-INFO: Acquired name org.gnome.Mutter.ServiceChannel > 3: Doing frame 8, delta = 261 > 3: Marker 'start-marker' (1666) reached, delta = 261 > 2: Doing frame 2, delta = 261 > 1: Doing frame 2, delta = 261 > 1: Marker 'start-marker' (0) reached, delta = 261 > 3: Doing frame 8, delta = 100 > 3: Marker 'baz' (1333) reached, delta = 100 > 2: Doing frame 2, delta = 100 > 2: Marker 'bar' (333) reached, delta = 100 > 1: Doing frame 2, delta = 100 > 3: Doing frame 7, delta = 100 > 2: Doing frame 3, delta = 100 > 1: Doing frame 3, delta = 100 > 3: Doing frame 7, delta = 100 > 2: Doing frame 3, delta = 100 > 1: Doing frame 3, delta = 100 > 3: Doing frame 6, delta = 100 > 2: Doing frame 4, delta = 100 > 1: Doing frame 4, delta = 100 > 3: Doing frame 5, delta = 100 > 2: Doing frame 5, delta = 100 > 1: Doing frame 5, delta = 100 > 3: Doing frame 5, delta = 100 > 3: Marker 'foo' (833) reached, delta = 100 > 2: Doing frame 5, delta = 100 > 1: Doing frame 5, delta = 100 > 1: Marker 'baz' (833) reached, delta = 100 > 1: Marker 'bar' (833) reached, delta = 100 > 1: Marker 'foo' (833) reached, delta = 100 > 3: Doing frame 4, delta = 100 > 2: Doing frame 6, delta = 100 > 1: Doing frame 6, delta = 100 > 3: Doing frame 4, delta = 100 > 2: Doing frame 6, delta = 100 > 1: Doing frame 6, delta = 100 > 3: Doing frame 3, delta = 100 > 2: Doing frame 7, delta = 100 > 1: Doing frame 7, delta = 100 > 3: Doing frame 2, delta = 100 > 2: Doing frame 8, delta = 100 > 1: Doing frame 8, delta = 100 > 3: Doing frame 2, delta = 100 > 2: Doing frame 8, delta = 100 > 1: Doing frame 8, delta = 100 > 3: Doing frame 1, delta = 100 > 2: Doing frame 9, delta = 100 > 1: Doing frame 9, delta = 100 > 3: Doing frame 1, delta = 100 > 3: Marker 'near-end-marker' (166) reached, delta = 100 > 2: Doing frame 9, delta = 100 > 1: Doing frame 9, delta = 100 > 1: Marker 'near-end-marker' (1500) reached, delta = 100 > 3: Doing frame 0, delta = 100 > 2: Doing frame 10, delta = 100 > 1: Doing frame 10, delta = 100 > 3: Doing frame 0, delta = 100 > 3: Marker 'end-marker' (0) reached, delta = 100 > 3: Completed > 2: Doing frame 10, delta = 100 > 2: Completed > 1: Doing frame 10, delta = 100 > 1: Marker 'end-marker' (1666) reached, delta = 100 > 1: Completed > FAIL: missed 1 frame for timeline 1 > ** > Clutter-Conform:ERROR:../src/tests/clutter/conform/timeline.c:281:timeline_base: > assertion failed: (check_timeline (timeline_1, &data_1, TRUE)) If this is operating in real-time, then I think this test might need to be disabled or marked as flaky for buildd purposes: on an un-loaded developer machine with a real GPU and other nice amenities, we might be able to assert that the deadline for a frame is never missed, but on a buildd that is set up for batch processing, rendering in software and potentially running other things in parallel, I don't think that assertion is realistic. It might also be pragmatic to disable the tests when we are only doing an Architecture: all build (like we do in glib2.0), so that those always succeed, even if some builds for specific architectures fail. smcv --- End Message --- --- Begin Message --- Source: mutter Source-Version: 47.1-2 Done: Simon McVittie We believe that the bug you reported is
Bug#1084383: marked as done (traitlets: FTBFS: AssertionError: assert {''} > {'DEBUG', 'INFO'})
Your message dated Tue, 5 Nov 2024 15:01:05 +0100
with message-id
and subject line traitlets: FTBFS: AssertionError: assert {''} > {'DEBUG',
'INFO'}
has caused the Debian Bug report #1084383,
regarding traitlets: FTBFS: AssertionError: assert {''} > {'DEBUG', 'INFO'}
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.)
--
1084383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:traitlets
Version: 5.14.3+really5.14.3-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 --with sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
module
I: pybuild base:311: python3.12 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.12_traitlets
* Building wheel...
Successfully built traitlets-5.14.3-py3-none-any.whl
I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with
"installer" module
debian/rules execute_after_dh_auto_build
make[1]: Entering directory '/<>'
PYTHONPATH=$(pwd) make -C docs html
make[2]: Entering directory '/<>/docs'
sphinx-build -b html -d build/doctrees source build/html
Running Sphinx v7.4.7
loading translations [en]... done
making output directory... done
Converting `source_suffix = '.rst'` to `source_suffix = {'.rst':
'restructuredtext'}`.
myst v4.0.0: MdParserConfig(commonmark_only=False, gfm_only=False,
enable_extensions=set(), disable_syntax=[], all_links_external=False,
links_external_new_tab=False, url_schemes=('http', 'https', 'mailto', 'ftp'),
ref_domains=None, fence_as_directive=set(), number_code_blocks=[],
title_to_header=False, heading_anchors=0, heading_slug_func=None, html_meta={},
footnote_sort=True, footnote_transition=True, words_per_minute=200,
substitutions={}, linkify_fuzzy_links=True, dmath_allow_labels=True,
dmath_allow_space=True, dmath_allow_digits=True, dmath_double_inline=False,
update_mathjax=True,
mathjax_classes='tex2jax_process|mathjax_process|math|output_area',
enable_checkboxes=False, suppress_warnings=[], highlight_code_blocks=True)
loading intersphinx inventory 'python' from
/usr/share/doc/python3-doc/html/objects.inv...
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 10 source files that are out of date
updating environment: [new config] 10 added, 0 changed, 0 removed
reading sources... [ 10%] api
reading sources... [ 20%] changelog
reading sources... [ 30%] config
reading sources... [ 40%] config-api
reading sources... [ 50%] defining_traits
reading sources... [ 60%] index
reading sources... [ 70%] migration
reading sources... [ 80%] trait_types
reading sources... [ 90%] using_traitlets
reading sources... [100%] utils
/<>/docs/source/utils.rst:4: WARNING: duplicate object description
of traitlets, other instance in trait_types, use :no-index: for one of them
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
copying assets...
copying static files... done
copying extra files... done
copying assets: done
writing output... [ 10%] api
writing output... [ 20%] changelog
writing output... [ 30%] config
writing output... [ 40%] config-api
writing output... [ 50%] defining_traits
writing output... [ 60%] index
writing output... [ 70%] migration
writing output... [ 80%] trait_types
writing output... [ 90%] using_traitlets
writing output... [100%] utils
generating indices... genindex py-modindex done
writing additional pages... search done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded, 1 warning.
The HTML pages are in build/html.
Build finished. The HTML pages are in build/html.
make[2]: Leaving directory '/<>/docs'
make[1]: Leaving directory '/<>'
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd
/<>/.pybuild/cpython3_3.12
Bug#1084810: marked as done (lomiri FTBFS with the nocheck build profile)
Your message dated Tue, 05 Nov 2024 12:50:58 + with message-id and subject line Bug#1084810: fixed in lomiri 0.3.0-3 has caused the Debian Bug report #1084810, regarding lomiri FTBFS with the nocheck build profile 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.) -- 1084810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lomiri Version: 0.3.0-2 Severity: serious Tags: ftbfs trixie sid Justification: nocheck ftbfs is rc since trixie lomiri fails to build from source when enabling the nocheck build profile. The relevant excerpt likely is: | -- Checking for modules 'libqtdbustest-1;libqtdbusmock-1' | -- Package 'libqtdbustest-1', required by 'virtual:world', not found | -- Package 'libqtdbusmock-1', required by 'virtual:world', not found | CMake Error at /usr/share/cmake-3.30/Modules/FindPkgConfig.cmake:645 (message): | The following required packages were not found: | |- libqtdbustest-1 |- libqtdbusmock-1 | | Call Stack (most recent call first): | /usr/share/cmake-3.30/Modules/FindPkgConfig.cmake:873 (_pkg_check_modules_internal) | CMakeLists.txt:215 (pkg_check_modules) | | | -- Configuring incomplete, errors occurred! | cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt Either there are too many annotations or some flag should be passed to cmake to make the annotated dependencies practically optional. Helmut --- End Message --- --- Begin Message --- Source: lomiri Source-Version: 0.3.0-3 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of lomiri, 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 1084...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated lomiri package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Oct 2024 09:53:54 +0200 Source: lomiri Architecture: source Version: 0.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 1084810 Changes: lomiri (0.3.0-3) unstable; urgency=medium . [ Mike Gabriel ] * debian/control: + Add C (lomiri-greeter): unity-greeter. Avoid pulling in old Ubuntu Indicators + Unity Greeter on Ubuntu. + Add R: (lomiri): ciborium. * debian/patches: + Add 2012_no-app-suspension-on-Debian+Ubuntu-proper.patch. Don't suspend apps in Debian + Ubuntu proper. . [ Guido Berhoerster ] * debian/: + Fix nocheck build profile (Closes: #1084810) Checksums-Sha1: e79e49559ea519b2a285d8b8fca6e8c7f1a5cb95 4295 lomiri_0.3.0-3.dsc eb655b3fc7f22044262d213af6148b14c9e58def 40992 lomiri_0.3.0-3.debian.tar.xz f30f9c8e3c85d940a18cae7b5a047a68b1793131 26979 lomiri_0.3.0-3_source.buildinfo Checksums-Sha256: 76a7d7fd4d5bea3c5f8b28fad8263e3ecdefe216500025ec366301cb13ecd5ab 4295 lomiri_0.3.0-3.dsc 050dcaefe8408ac040f7dd06130c6a9299384ec182f5bb758b3c1226161b6577 40992 lomiri_0.3.0-3.debian.tar.xz 318010c217bf574551be3d181bae4fbf4079bb754c8afef485bfe983fc4e09d0 26979 lomiri_0.3.0-3_source.buildinfo Files: f9f54f9fb384b06fe80f6c1e961e68d2 4295 x11 optional lomiri_0.3.0-3.dsc 05e542ae37eb44831b331a1c9b7b3fd1 40992 x11 optional lomiri_0.3.0-3.debian.tar.xz c7c299b43e7806897c36831b375bdbd5 26979 x11 optional lomiri_0.3.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmcqDcMVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxRp0P/3VP6kqQ1+ZUR3UX23z9p3h7B9eK K8JrGN9RR6Znppa4mESR80YRC7KqbvmMrCietW9jnf1t69xHWxM84nxSVaJm1dmn DJwQZBRu8QMN6QfXQNzmgRVI5mm8IaTgl4NUXe6nifH/rn43W1/ZfSz9GrLenmCv 4dYxSVKYJjIxmUW3R6RYGSXRbok2QKgfaJgWKD5ePeTxHOkYv9GXCWKaWBQHCKUJ rN3uoaK75FXWEoaQ0kxQzso0siqJyhDTXJy62SquKVs5cTy/b5p/SuYyiiXD5zjC nOJHdKWO9R58+D5M0ptlfeIUKRswAKqtX0KWwXiao71tKaMWmVkc8sxzsAfF8Jyg 7M0AUN2Pc3d+mHAqfmzeLI49crj4iKdAI7vEyQIW1P3JsLzsRRxKGxA6ERuvQ0FA RgodKeZYe66bszz8QirC+/XJyMZxjGM4nijzIQTgda9E9V9M/eJQSIUS0rau3SmB hMTEqQvMb96xNbD7rZXebZkkez7ThaUgSd3tUYrhZ+0W9QcMHjlA+PPlEtwBm3Kd 0
Bug#1086751: marked as done (srt: libsrt-openssl-dev and libsrt-gnutls-dev only suggest packages needed by .pc file)
Your message dated Tue, 05 Nov 2024 12:27:17 + with message-id and subject line Bug#1086751: fixed in srt 1.5.3-2 has caused the Debian Bug report #1086751, regarding srt: libsrt-openssl-dev and libsrt-gnutls-dev only suggest packages needed by .pc file 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.) -- 1086751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: srt Version: 1.5.1-1 Severity: serious Tags: sid trixie bookworm Hello, Both the libsrt-openssl-dev and libsrt-gnutls-dev have .pc files with unsatisfied dependencies. They only suggest the needed package instead of a hard depend on them libsrt-openssl-dev: $ grep Requires usr/lib/x86_64-linux-gnu/pkgconfig/*.pc usr/lib/x86_64-linux-gnu/pkgconfig/haisrt.pc:Requires.private: openssl libcrypto usr/lib/x86_64-linux-gnu/pkgconfig/srt.pc:Requires.private: openssl libcrypto libsrt-gnutls-dev: usr/lib/x86_64-linux-gnu/pkgconfig/haisrt.pc:Requires.private: gnutls nettle usr/lib/x86_64-linux-gnu/pkgconfig/srt.pc:Requires.private: gnutls nettle libssl-dev or libgnutls28-dev need to be bumped to a hard dependency accordingly. And a hard dependency against nettle-dev should be added for the gnutls flavour Kind regards, Laurent Bigonville -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.11.5-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: srt Source-Version: 1.5.3-2 Done: Florian Ernst We believe that the bug you reported is fixed in the latest version of srt, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Ernst (supplier of updated srt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 05 Nov 2024 12:19:15 +0100 Source: srt Architecture: source Version: 1.5.3-2 Distribution: unstable Urgency: medium Maintainer: Florian Ernst Changed-By: Florian Ernst Closes: 1086751 Changes: srt (1.5.3-2) unstable; urgency=medium . * [0bc278e] d/control: B-D pkg-config -> pkgconf * [9154f06] d/copyright: clarify that some parts are dual-licensed * [2af4f41] d/control: correct hard dependencies for dev packages. Thanks to Laurent Bigonville (Closes: #1086751) * [5f509fc] d/copyright: update years Checksums-Sha1: 591836a01aa17224cb184cf4c9d93c79124cd715 2317 srt_1.5.3-2.dsc ae2d82b2a5d0dc048160d5c9f702c57d0b8f38ba 16184 srt_1.5.3-2.debian.tar.xz 0c15d262fbf986660c477fa05efe88306ba569c6 11847 srt_1.5.3-2_amd64.buildinfo Checksums-Sha256: ae9bb2321b7f5581b4a94a78e97b8fc59e3e7434e66217c8d243e501723e58f8 2317 srt_1.5.3-2.dsc 3a55ef7c61756b297136b57e2fa2dfbe6b54eda66c96128ccba299ba82de3181 16184 srt_1.5.3-2.debian.tar.xz 7117b08b0c1cb52c5a5bfa51c4788a136d54bc9d27f5d0f3388c48bfdb5a4d81 11847 srt_1.5.3-2_amd64.buildinfo Files: 0dac0f37c0ac674fbfd4c03d0c026cf5 2317 libs optional srt_1.5.3-2.dsc 161296090a404a9bd9e0bad109172a79 16184 libs optional srt_1.5.3-2.debian.tar.xz 47f8ae53997ead5401d104a1a489f970 11847 libs optional srt_1.5.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEBn03XtJwVyplJ26xBjdBuvXdHs4FAmcqANUACgkQBjdBuvXd Hs7pJQ//U83J4Hbvu6wG391rmjs15j9xXeAH9vSECQOT6KhPZHhV+sb4FZXq85D2 0TO9qx+CiHA/I1NYIC3kx8dAKYzA8XjNJwdT3bolntOddG2NTzN9KHhR8EV3MQfi 9zf+8uK7DswexOPbBkK4YyQaxJqolFurgsRDK7d1Zuf+QiwQYME+ERrt0Hds+f55 MwEau1Q0mbANMfekEZLuePE0mD4FNo/aO07LqIZX2gIBAt9j4R3rv0QKSPkb3B0t yO6tDM+H7KDEbMVccXStSRETHGI4UWHGn8DXr+Fgzst5aln5n2LLEb9F1XbPOkZy JWRu2b/breEpOGJFQrCdOfUhNlIVxFGryaRQPpLbNZWLl+YaEHUaN4rhHNaNVLxp hO2qM+EflV8zipDQyyqlfc/SmJnIn2rgFP/Xug6g88nQrXC4fO8hpBXvWq6vopLm LAvZ6Ow0mP8HARFoYNAkd
Bug#1086754: marked as done (jameica-datasource - build-depends on dropped package.)
Your message dated Tue, 05 Nov 2024 11:50:17 + with message-id and subject line Bug#1086754: fixed in jameica-datasource 2.8.1+dfsg-5 has caused the Debian Bug report #1086754, regarding jameica-datasource - build-depends on dropped package. 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.) -- 1086754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jameica-datasource Version: 2.8.1+dfsg-4 Severity: serious Justification: rc-policy - packages must be buildable within the same release. User: debian...@lists.debian.org Usertags: edos-uninstallable jameica-datasource build-depends on libmckoisqldb-java-doc which is no longer built by the mckoisqldb source package, it is still present in unstable as a cruft package, but is completely gone from testing. --- End Message --- --- Begin Message --- Source: jameica-datasource Source-Version: 2.8.1+dfsg-5 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of jameica-datasource, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated jameica-datasource package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 05 Nov 2024 12:36:35 +0100 Source: jameica-datasource Architecture: source Version: 2.8.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 1086754 Changes: jameica-datasource (2.8.1+dfsg-5) unstable; urgency=medium . * Team upload. * Removed the -java-doc package (Closes: #1086754) * Standards-Version updated to 4.7.0 Checksums-Sha1: 7da7d0cea8ab5a2c85119e6d620ae02c580830a2 2205 jameica-datasource_2.8.1+dfsg-5.dsc b0ee06779142263de2408307cd6857a8808113ad 2732 jameica-datasource_2.8.1+dfsg-5.debian.tar.xz c77dbf48aee756fb04e32170293062e0c45011c8 14831 jameica-datasource_2.8.1+dfsg-5_source.buildinfo Checksums-Sha256: 8f28ce66fe2e504ccf05674cd83e59706741f749d8c991f6bea06a95ed762961 2205 jameica-datasource_2.8.1+dfsg-5.dsc 8789f3cbb24217db270bb9017a27772a6a1acaba03e1f1e7a61165c275f52f26 2732 jameica-datasource_2.8.1+dfsg-5.debian.tar.xz e6ab5d786eef032d239f110fd16e7a5257aff290e8983477114df95566986e0d 14831 jameica-datasource_2.8.1+dfsg-5_source.buildinfo Files: 9691d6f0f681ab2c3f4ff965d735db0c 2205 java optional jameica-datasource_2.8.1+dfsg-5.dsc 76033c9497b5a5f8d34694c6bee397dc 2732 java optional jameica-datasource_2.8.1+dfsg-5.debian.tar.xz ad1b634bc88bcbb2ee99377e48a397a7 14831 java optional jameica-datasource_2.8.1+dfsg-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmcqA1ASHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsgyUQAIGkdsYIl6rDh+DvxtBEFgy9T8LpHgu1 CX/WsFk3u6DpLXdy9q9RKFxULstSBZdpGDGfEMTDuSyHmGBeiRt77My+kSa6Lwjh yfpupsv96Hw55QgBFqklmHLhAUu/Ydamfk75BTLSDAtDS3dM2aESo0brSxG42YFH Sg1+qXM38Y5kxiwA3yEhbEGEqryhPLpVaZqHA69M6427QqIJZMn3F7Df0ToVooui jGcAdQUG2k1QXkjzU/j3G0RFZikKKf26MJwrv2Wl5Xyre3euRr/HJCimIU4tf+DP sgGzTwW1NYAHvOHv8ikMujNy+qjG2CWaj6bqjwGD4Koqd+EvsX7qeftlay5R9vL6 JKv0c3U0feLfJQ+gEFTQgn7Ka8tSTVudidVN+LzxWsuBNukJsPBUn2+bqb2vEIwK fvYRJLTPt45l3BOKtXGG0WyNDVa1y/GCg++1veXLvZ/8RLZ3OsKUjF0NR6kemdFV nBoxW2jPiB46udTJKSOBb9sap1mF2MXiEiVR7ZCKT78nyxHaOUQzKypPUjI2Row6 bx2m0BWYHaXx+cRmIn5yV+OuiA9X8Xdx91x3+KE3NrnSMPFdFCiUb/MlAgCUNh6I b8fL7XwSweia7zScxzcmtw/+PsBMBR8yRQvOBFM1AuAzHPoYoz1tPyfUnQyT82e1 fUVvJrY5xht5 =Ovu4 -END PGP SIGNATURE- pgpS85UZ8HYHc.pgp Description: PGP signature --- End Message ---
Bug#1085594: marked as done (reposurgeon: Missing build dependency on tzdata-legacy)
Your message dated Tue, 05 Nov 2024 11:35:16 + with message-id and subject line Bug#1085594: fixed in reposurgeon 4.38-2 has caused the Debian Bug report #1085594, regarding reposurgeon: Missing build dependency on tzdata-legacy 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.) -- 1085594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: reposurgeon Version: 4.38-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=reposurgeon&ver=4.38-1%2Bb3 ... === RUN TestReadAuthorMap reposurgeon: in readAuthorMap, while parsing line 3: [ill-formed timezone offset EST] reposurgeon_test.go:1417: expected 3 people but got 2 --- FAIL: TestReadAuthorMap (0.00s) ... EST is now in tzdata-legacy. Additionally, a runtime dependency on tzdata-legacy might also be appropriate? --- End Message --- --- Begin Message --- Source: reposurgeon Source-Version: 4.38-2 Done: Santiago Vila We believe that the bug you reported is fixed in the latest version of reposurgeon, 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 1085...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Santiago Vila (supplier of updated reposurgeon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 05 Nov 2024 12:10:00 +0100 Source: reposurgeon Architecture: source Version: 4.38-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Santiago Vila Closes: 1085594 Changes: reposurgeon (4.38-2) unstable; urgency=medium . * Team upload. [ Aurelien Jarno ] * Build-Depends and Depends on tzdata-legacy to support obsolete System V names. Closes: #1085594. Checksums-Sha1: 8ce66a4c3ff2a60bb8a7238579c796e003840a01 2242 reposurgeon_4.38-2.dsc faea324080a305569ac677aa6e5e446130bba88e 25060 reposurgeon_4.38-2.debian.tar.xz f54380e65e82dfa3c877b6b6bf499d6e5ccc2b33 6158 reposurgeon_4.38-2_source.buildinfo Checksums-Sha256: 3562375ec24b1a235249b645826e86762951b745a26e74f1dba7385eb6aeb05c 2242 reposurgeon_4.38-2.dsc 2f24398041edc51f18535da1ea70c619dc9d8aaa1d2a9e5545a52f08259dea38 25060 reposurgeon_4.38-2.debian.tar.xz 1c39c274259a0316625d865742c85d129f99f96af7281640da600cc907d3898d 6158 reposurgeon_4.38-2_source.buildinfo Files: 3d2747ae88e9cdba8245720a2c931f24 2242 vcs optional reposurgeon_4.38-2.dsc 758b841aca3a8843f9a56794a7d3f075 25060 vcs optional reposurgeon_4.38-2.debian.tar.xz 55e84db52c5e7c10c6dce4831c48d6f5 6158 vcs optional reposurgeon_4.38-2_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmcp/r0ACgkQQc5/C58b izKtNwf9HIRVbGQ+Tt5ivWRSViIKY+JOzFelDJHNSaVx92HCz7cPNu9+ukr1NyQx 8skic/6vETfAaRzsKNkYLDmOmgnIwdAsuKAVKW2WEFqy5ihjTrxvUMNnIZ+6QCpf SA+XwDTRgmMgMcQRzjlu918Osqp3l13EAUXrjYeL98UYLYQrzzw/mP5JGd7p39qE qAqjjrKWZX4nBJuUYwF2iHH0RZLvk+4nQ6MCBGqrjTRWi34uR3N1tdbeWNfqdRvL rGSHHkw0hHex6UNd3G06Lict/w2SELRhhEblexOUue+eIC1Ixu6kYix5l6epl1Sw iOYL6JNu/vCJ7AeKGaP7scL7WZqlwg== =ubrD -END PGP SIGNATURE- pgpanVJKTxdkB.pgp Description: PGP signature --- End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1086224 important Bug #1086224 [libgd-securityimage-perl] RC: Argument " " isn't numeric in division (/) at /usr/share/perl5/GD/SecurityImage/Magick.pm Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1086224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1086752: rust-tealdeer - depends on yansi 0.5 but trixie/sid has version 1
Processing control commands: > forwarded -1 https://github.com/tealdeer-rs/tealdeer/pull/389 Bug #1086752 [rust-tealdeer] rust-tealdeer - depends on yansi 0.5 but trixie/sid has version 1 Set Bug forwarded-to-address to 'https://github.com/tealdeer-rs/tealdeer/pull/389'. -- 1086752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#1086224: RC: Argument " " isn't numeric in division (/) at /usr/share/perl5/GD/SecurityImage/Magick.pm
Processing control commands: > tags -1 + important Unknown tag/s: important. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky forky-ignore. Bug #1086224 [libgd-securityimage-perl] RC: Argument " " isn't numeric in division (/) at /usr/share/perl5/GD/SecurityImage/Magick.pm Requested to add no tags; doing nothing. -- 1086224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1085594 marked as pending in reposurgeon
Processing control commands: > tag -1 pending Bug #1085594 [src:reposurgeon] reposurgeon: Missing build dependency on tzdata-legacy Added tag(s) pending. -- 1085594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1086750 to src:grub
Processing commands for cont...@bugs.debian.org: > reassign 1086750 src:grub 0.97-83 Bug #1086750 [src:grub-pc] grub-installer still uses old grub-legacy Warning: Unknown package 'src:grub-pc' Bug reassigned from package 'src:grub-pc' to 'src:grub'. No longer marked as found in versions grub-pc/0.97-83. Ignoring request to alter fixed versions of bug #1086750 to the same values previously set Bug #1086750 [src:grub] grub-installer still uses old grub-legacy Marked as found in versions grub/0.97-83. > thanks Stopping processing here. Please contact me if you need assistance. -- 1086750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1085075 is normal
Processing commands for cont...@bugs.debian.org: > severity 1085075 normal Bug #1085075 [ftp.debian.org] RM: rtl8723bt-firmware -- ROM; replacement available Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1085075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1086552 marked as pending in mutter
Processing control commands: > tag -1 pending Bug #1086552 [src:mutter] mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame Added tag(s) pending. -- 1086552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075358: marked as done (pam-ssh-agent-auth: ftbfs with GCC-14)
Your message dated Tue, 05 Nov 2024 09:06:09 +0100 with message-id and subject line Accepted pam-ssh-agent-auth 0.10.3-10 (source) into unstable has caused the Debian Bug report #1075358, regarding pam-ssh-agent-auth: ftbfs with GCC-14 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.) -- 1075358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pam-ssh-agent-auth Version: 0.10.3-9 Severity: important Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/pam-ssh-agent-auth_0.10.3-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -fstack-protector-all -I. -I.. -I. -I./.. -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -c sigact.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -fstack-protector-all -I. -I.. -I. -I./.. -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -c strlcat.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -fstack-protector-all -I. -I.. -I. -I./.. -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -c strlcpy.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -fstack-protector-all -I. -I.. -I. -I./.. -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -c strmode.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -fstack-protector-all -I. -I.. -I. -I./.. -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -c strsep.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -fstack-protector-all -I. -I.. -I. -I./.. -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -c strtoll.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -fstack-protector-all -I. -I.. -I. -I./.. -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -c strtonum.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -fstack-protector-all -I. -I.. -I. -I./.. -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -c strtoul.c gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -Wall -Wpointer-arith -Wuninitialized -
Processed: severity 1085075 critical
Processing commands for cont...@bugs.debian.org: > severity 1085075 critical Bug #1085075 [ftp.debian.org] RM: rtl8723bt-firmware -- ROM; replacement available Severity set to 'critical' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1085075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:orange-spectroscopy: fails to migrate to testing for too long
Processing control commands: > close -1 0.7.2-2 Bug #1086743 [src:orange-spectroscopy] src:orange-spectroscopy: fails to migrate to testing for too long The source 'orange-spectroscopy' and version '0.7.2-2' do not appear to match any binary packages Marked as fixed in versions orange-spectroscopy/0.7.2-2. Bug #1086743 [src:orange-spectroscopy] src:orange-spectroscopy: fails to migrate to testing for too long Marked Bug as done -- 1086743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:ejabberd-contrib: fails to migrate to testing for too long
Processing control commands: > close -1 0.2024.07.18~dfsg0-1 Bug #1086745 [src:ejabberd-contrib] src:ejabberd-contrib: fails to migrate to testing for too long Marked as fixed in versions ejabberd-contrib/0.2024.07.18~dfsg0-1. Bug #1086745 [src:ejabberd-contrib] src:ejabberd-contrib: fails to migrate to testing for too long Marked Bug as done -- 1086745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:ejabberd: fails to migrate to testing for too long
Processing control commands: > close -1 24.07-2 Bug #1086746 [src:ejabberd] src:ejabberd: fails to migrate to testing for too long Marked as fixed in versions ejabberd/24.07-2. Bug #1086746 [src:ejabberd] src:ejabberd: fails to migrate to testing for too long Marked Bug as done -- 1086746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:ruby-excon: fails to migrate to testing for too long
Processing control commands: > close -1 0.112.0-2 Bug #1086742 [src:ruby-excon] src:ruby-excon: fails to migrate to testing for too long The source 'ruby-excon' and version '0.112.0-2' do not appear to match any binary packages Marked as fixed in versions ruby-excon/0.112.0-2. Bug #1086742 [src:ruby-excon] src:ruby-excon: fails to migrate to testing for too long Marked Bug as done -- 1086742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:erlang-p1-eimp: fails to migrate to testing for too long
Processing control commands: > close -1 1.0.23-2 Bug #1086744 [src:erlang-p1-eimp] src:erlang-p1-eimp: fails to migrate to testing for too long Marked as fixed in versions erlang-p1-eimp/1.0.23-2. Bug #1086744 [src:erlang-p1-eimp] src:erlang-p1-eimp: fails to migrate to testing for too long Marked Bug as done -- 1086744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1086701: autopkgtest: Same package version considered downgrade
Processing control commands: > notfound -1 5.42 Bug #1086701 [autopkgtest] autopkgtest: Same package version considered downgrade No longer marked as found in versions autopkgtest/5.42. -- 1086701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066247: marked as done (uhub: FTBFS: adcclient.c:178:33: error: implicit declaration of function ‘ADC_client_connect_internal’; did you mean ‘ADC_client_connect’? [-Werror=implicit-function-decla
Your message dated Tue, 05 Nov 2024 06:50:45 + with message-id and subject line Bug#1066247: fixed in uhub 0.4.1-3.3 has caused the Debian Bug report #1066247, regarding uhub: FTBFS: adcclient.c:178:33: error: implicit declaration of function ‘ADC_client_connect_internal’; did you mean ‘ADC_client_connect’? [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uhub Version: 0.4.1-3.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /usr/bin/cc -DSSL_SUPPORT=1 -DSSL_USE_OPENSSL=1 -I/<>/src -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -MD -MT > CMakeFiles/utils.dir/src/util/list.c.o -MF > CMakeFiles/utils.dir/src/util/list.c.o.d -o > CMakeFiles/utils.dir/src/util/list.c.o -c /<>/src/util/list.c > /<>/src/tools/adcclient.c: In function ‘event_callback’: > /<>/src/tools/adcclient.c:178:33: error: implicit declaration of > function ‘ADC_client_connect_internal’; did you mean ‘ADC_client_connect’? > [-Werror=implicit-function-declaration] > 178 | ADC_client_connect_internal(client); > | ^~~ > | ADC_client_connect > [ 9%] Building C object CMakeFiles/utils.dir/src/util/log.c.o > /usr/bin/cc -DSSL_SUPPORT=1 -DSSL_USE_OPENSSL=1 -I/<>/src -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -MD -MT > CMakeFiles/utils.dir/src/util/log.c.o -MF > CMakeFiles/utils.dir/src/util/log.c.o.d -o > CMakeFiles/utils.dir/src/util/log.c.o -c /<>/src/util/log.c > [ 10%] Building C object CMakeFiles/utils.dir/src/util/memory.c.o > /usr/bin/cc -DSSL_SUPPORT=1 -DSSL_USE_OPENSSL=1 -I/<>/src -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -MD -MT > CMakeFiles/utils.dir/src/util/memory.c.o -MF > CMakeFiles/utils.dir/src/util/memory.c.o.d -o > CMakeFiles/utils.dir/src/util/memory.c.o -c /<>/src/util/memory.c > [ 11%] Building C object CMakeFiles/utils.dir/src/util/misc.c.o > /usr/bin/cc -DSSL_SUPPORT=1 -DSSL_USE_OPENSSL=1 -I/<>/src -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -MD -MT > CMakeFiles/utils.dir/src/util/misc.c.o -MF > CMakeFiles/utils.dir/src/util/misc.c.o.d -o > CMakeFiles/utils.dir/src/util/misc.c.o -c /<>/src/util/misc.c > [ 13%] Building C object CMakeFiles/utils.dir/src/util/rbtree.c.o > /usr/bin/cc -DSSL_SUPPORT=1 -DSSL_USE_OPENSSL=1 -I/<>/src -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -MD -MT > CMakeFiles/utils.dir/src/util/rbtree.c.o -MF > CMakeFiles/utils.dir/src/util/rbtree.c.o.d -o > CMakeFiles/utils.dir/src/util/rbtree.c.o -c /<>/src/util/rbtree.c > [ 14%] Building C object CMakeFiles/utils.dir/src/util/threads.c.o > /usr/bin/cc -DSSL_SU
Processed: tagging 1086676
Processing commands for cont...@bugs.debian.org: > tags 1086676 + fixed-upstream patch Bug #1086676 [python3-flake8] Not installable with python3-pycodestyle/sid Added tag(s) fixed-upstream and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1086676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging with patch
Processing commands for cont...@bugs.debian.org: > tags 1075684 patch Bug #1075684 [src:xshisen] xshisen: ftbfs with GCC-14 Ignoring request to alter tags of bug #1075684 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1075684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging with patch
Processing commands for cont...@bugs.debian.org: > tags 1075694 patch Bug #1075694 [src:xxkb] xxkb: ftbfs with GCC-14 Ignoring request to alter tags of bug #1075694 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1075694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging the patch
Processing commands for cont...@bugs.debian.org: > tags 1075684 patch Bug #1075684 [src:xshisen] xshisen: ftbfs with GCC-14 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging with patch
Processing commands for cont...@bugs.debian.org: > tags 1075694 patch Bug #1075694 [src:xxkb] xxkb: ftbfs with GCC-14 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054814: marked as done (criu: FTBFS: bad install directory or PYTHONPATH)
Your message dated Mon, 04 Nov 2024 21:50:01 + with message-id and subject line Bug#1054814: fixed in criu 3.19-1 has caused the Debian Bug report #1054814, regarding criu: FTBFS: bad install directory or PYTHONPATH 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.) -- 1054814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: criu Version: 3.17.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > Note: Building criu without amdgpu_plugin. > Note: libdrm and libdrm_amdgpu are required to build amdgpu_plugin. > make[2]: git: No such file or directory > GEN footer.txt > GEN crit.1 > GEN criu-ns.1 > GEN compel.1 > GEN amdgpu_plugin.1 > make[3]: 'compel/plugins/std.lib.a' is up to date. > GEN criu.8 > make[3]: Nothing to be done for 'all'. > make[3]: 'compel/plugins/fds.lib.a' is up to date. > make[3]: 'soccr/libsoccr.a' is up to date. > CC compel/arch/x86/src/lib/handle-elf.o > CC compel/src/lib/handle-elf.o > CC compel/src/main.o > LINK compel/built-in.o > make[3]: Nothing to be done for 'all'. > make[3]: 'compel/libcompel.a' is up to date. > LINK compel/libcompel.so > make[3]: 'compel/compel-host-bin' is up to date. > LINK compel/compel > INSTALL compel > INSTALL libcompel.so > INSTALL libcompel.a > INSTALL compel uapi > INSTALL compel plugins > INSTALL compel plugins uapi > Note: Writing crit.1 > Note: Writing criu-ns.1 > Note: Writing compel.1 > Note: Writing amdgpu_plugin.1 > make[3]: 'images/built-in.o' is up to date. > make[4]: Nothing to be done for 'all'. > make[4]: Nothing to be done for 'all'. > make[4]: Nothing to be done for 'all'. > make[4]: Nothing to be done for 'all'. > make[3]: Nothing to be done for 'all'. > make[3]: 'all' is up to date. > make[4]: Nothing to be done for 'all'. > make[3]: Nothing to be done for 'install'. > make[4]: 'lib/c/built-in.o' is up to date. > make[4]: Nothing to be done for 'all'. > make[4]: Nothing to be done for 'all'. > make[4]: 'lib/c/built-in.o' is up to date. > make[4]: Nothing to be done for 'lib/c/criu.pc.in'. > make[4]: Nothing to be done for 'all'. > INSTALL criu/criu > INSTALL scripts/criu-ns > INSTALL lib > INSTALL pkgconfig/criu.pc > INSTALL crit > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > EasyInstallDeprecationWarning: easy_install command is deprecated. > !! > > > > Please avoid running ``setup.py`` and ``easy_install``. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://github.com/pypa/setuptools/issues/917 for details. > > > > !! > self.initialize_options() > TEST FAILED: > /<>/debian/criu/usr/local/lib/python3.11/dist-packages/ does NOT > support .pth files > bad install directory or PYTHONPATH > > You are attempting to install a package to a directory that is not > on PYTHONPATH and which Python does not read ".pth" files f
Bug#1081079: marked as done (python3-nipype: unsatisfiable dependency)
Your message dated Mon, 04 Nov 2024 21:53:02 + with message-id and subject line Bug#1081079: fixed in nipype 1.9.0-1 has caused the Debian Bug report #1081079, regarding python3-nipype: unsatisfiable dependency 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.) -- 1081079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:heudiconv Version: 1.1.6-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-nipype : Depends: python3-funcsigs but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202409/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: nipype Source-Version: 1.9.0-1 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of nipype, 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 1081...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated nipype 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, 04 Nov 2024 21:45:12 +0100 Source: nipype Architecture: source Version: 1.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1064732 1081079 1084625 1085740 Changes: nipype (1.9.0-1) unstable; urgency=medium . [ Alexandre Detiste ] * remove dependency on python3-funcsigs (Closes: #1081079) * python3-looseversion is packaged, use it . [ Étienne Mollier ] * New upstream version 1.9.0 (Closes: #1064732, #1084625, #1085740) * d/copyright: document nipype/external/due.py, under BSD-2-Clause. * remove-dead-code.patch: remove dead patch. * d/patches/*: unfuzz all patches that needed it. * d/control: tests depend on python3-puremagic. * fixup-strict-digraph-test.patch: new: nudge a test to pass. * d/patches/*: normalize Last-Update. * d/control: migrate to pyproject. * d/control: declare compliance to standards version 4.7.0. Checksums-Sha1: 8941369fafab9ae7a943d6d7af119c8bb824bf01 2886 nipype_1.9.0-1.dsc 92c87dd1e200d72892848a3214962ff6b489bc01 2918608 nipype_1.9.0.orig.tar.gz 151c186db748cd0b703ec0edf4e3642c422f9bf8 16616 nipype_1.9.0-1.debian.tar.xz Checksums-Sha256: 9c4a856ec970d15b9388171165a11c58eba0a0313d4f90ab7921d41ff2186756 2886 nipype_1.9.0-1.dsc 6be5d0a7d758aeb0a3ca5c3965487541f3bcc49d34e6e05eeac6c66d702600da 2918608 nipype_1.9.0.orig.tar.gz a31867ec33e919bb766a49e7ee8c7cebfcc130719951bae9bc74691165903d3a 16616 nipype_1.9.0-1
Bug#1081856: marked as done (agg: FTBFS: agg_font_freetype.cpp:182:35: error: invalid conversion from 'unsigned char*' to 'char*' [-fpermissive])
Your message dated Mon, 04 Nov 2024 21:19:25 +
with message-id
and subject line Bug#1081856: fixed in agg 1:2.7.0.r145+dfsg-1
has caused the Debian Bug report #1081856,
regarding agg: FTBFS: agg_font_freetype.cpp:182:35: error: invalid conversion
from 'unsigned char*' to 'char*' [-fpermissive]
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.)
--
1081856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:agg
Version: 1:2.6.1-r134+dfsg1-2.1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:11: warning: The macro 'AC_ISC_POSIX' is obsolete.
configure.ac:11: You should run autoupdate.
./lib/autoconf/specific.m4:732: AC_ISC_POSIX is expanded from...
configure.ac:11: the top level
configure.ac:16: warning: The macro 'AM_PROG_LIBTOOL' is obsolete.
configure.ac:16: You should run autoupdate.
aclocal.m4:123: AM_PROG_LIBTOOL is expanded from...
configure.ac:16: the top level
configure.ac:23: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:23: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:23: the top level
configure.ac:27: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:27: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:27: the top level
configure.ac:30: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:30: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:30: the top level
configure.ac:67: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:67: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:67: the top level
configure.ac:80: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:80: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:80: the top level
configure.ac:89: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:89: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:89: the top level
configure.ac:145: warning: AC_OUTPUT should be used without arguments.
configure.ac:145: You should run autoupdate.
configure.ac:9: installing './compile'
configure.ac:3: installing './config.guess'
configure.ac:3: installing './config.sub'
configure.ac:5: installing './install-sh'
configure.ac:5: installing './missing'
Makefile.am:3: warning: SUBDIRS was already defined in condition TRUE, which
includes condition ENABLE_GPC ...
Makefile.am:1: ... 'SUBDIRS' previously defined here
Makefile.am: installing './INSTALL'
Makefile.am: installing './COPYING' using GNU General Public License v3 file
Makefile.am: Consider adding the COPYING file to the version control system
Makefile.am: for your code, to avoid questions about which license your
project uses
examples/Makefile.am:17: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS'
(or '*_CPPFLAGS')
examples/Makefile.am: installing './depcomp'
src/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or
'*_CPPFLAGS')
src/ctrl/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS'
(or '*_CPPFLAGS')
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
checking build system type... x86_64-
Bug#1086725: marked as done (z3 FTBFS on mips64el)
Your message dated Mon, 04 Nov 2024 20:56:47 + with message-id and subject line Bug#1086725: fixed in z3 4.8.12-3.2 has caused the Debian Bug report #1086725, regarding z3 FTBFS on mips64el 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.) -- 1086725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: z3 Version: 4.8.12-3.1 Severity: serious Tags: ftbfs trixie sid patch https://buildd.debian.org/status/fetch.php?pkg=z3&arch=mips64el&ver=4.8.12-3.1%2Bb3&stamp=1730452483&raw=0 ... /usr/bin/ld: not enough GOT space for local GOT entries /usr/bin/ld: BFD (GNU Binutils for Debian) 2.43.1 internal error, aborting at ../../bfd/elfxx-mips.c:10716 in _bfd_mips_elf_relocate_section Please report this bug. collect2: error: ld returned 1 exit status make[3]: *** [src/shell/CMakeFiles/shell.dir/build.make:1824: z3] Error 1 Fix: --- debian/rules.old2024-11-04 11:45:54.227726947 + +++ debian/rules2024-11-04 11:46:31.291697870 + @@ -10,6 +10,10 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-as-needed -Wl,-latomic -Wl,--as-needed endif +ifeq ($(DEB_HOST_ARCH),mips64el) +export DEB_CXXFLAGS_MAINT_APPEND += -mxgot +endif + DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) ifneq (,$(shell dh_listpackages -a | grep libz3-jni)) --- End Message --- --- Begin Message --- Source: z3 Source-Version: 4.8.12-3.2 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of z3, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated z3 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, 04 Nov 2024 20:47:25 +0100 Source: z3 Architecture: source Version: 4.8.12-3.2 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 1055476 1086725 Changes: z3 (4.8.12-3.2) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS on mips64el (Closes: #1086725) Thanks to Adrian Bunk for the patch * Fix hurd-amd64 build (Closes: #1055476) Thanks to Samuel Thibault for the patch * Update standards version to 4.6.2, no changes needed. Avoid explicitly specifying -Wl,--as-needed linker flag. * Standards-Version: 4.7.0 Checksums-Sha1: 3cf2318006b16cfaa45dac9dc895e1414f37d44e 2636 z3_4.8.12-3.2.dsc bbb285ad7839494cd8678b1f0e00020135a1e314 10452 z3_4.8.12-3.2.debian.tar.xz 3d26556bf0d0e284c4537b5e9f2890a8b66191ee 15877 z3_4.8.12-3.2_amd64.buildinfo Checksums-Sha256: e3f7e3aa5a9117116f350464048dfdbe4b50f1582fdbed6e45e071c2a6fe54f3 2636 z3_4.8.12-3.2.dsc e3a203619e06d2eeac4b9f4d082620238c21d92dfef6003a2cda99035584f50d 10452 z3_4.8.12-3.2.debian.tar.xz aff1cb2a570fdd1c22ac325de9d640382153a10a918db7838b20e8f5f3d4ac48 15877 z3_4.8.12-3.2_amd64.buildinfo Files: d7502cf0c68f2d8ef7e22f4f54cfef1a 2636 science optional z3_4.8.12-3.2.dsc 94f0e043c77f83f955d1764610d3f32e 10452 science optional z3_4.8.12-3.2.debian.tar.xz 6a0639da69b54ba22bbab57bf84e9199 15877 science optional z3_4.8.12-3.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmcpKygACgkQfmUo2nUv G+HBvhAAi6FXyAzrup0Ih+M8lvhVKzDYpPRyv3Aty1aEdHdKNWdM2jN3SyffVh4X MRdy11brx8sCdr2Xotrd10Apud+nIpvQucZO7wpvGXCq9U3bCTNCTVbo1dSIbehu o483PrNIkv4XzKWlUYXoBSZMyM/i7nd4uNTZgCBj4niFV5+UagCOknsd3VPLu/SQ SvKLrdp3cVRbtbZSugxmypAp9C6QSfBLsfIAbBQnQ/3IDd0JdAcvvswM8esdC1bS D0T5207m907ShmQo/3L4VzWljmQwfU89iCDPSI5Z2piF5fk4dkU1f/Zzjg9dHKWm QPt4wHi7QXpLaTzUtgrGrWQxxCjdghGmbqLbbrocisbCD03pj0Av/BIXif3hdHLX Y8uUG5D77Sg+ynu3Rad0oFEjZjB6LRnKTFyORaLxWqHTGl2NGBVkoukiWf5LcUoj X2CBm4kGhaho2T9kf1+E89mMOVG5uD1qv4F1Lw/ZT6SpZSLe0NP8T7tA+VHETg8Y rU8ZqES+bqeAfZ53gPU3iZzPbWF4ieWkXNbXZtX50CBuc1G9EdYTEFFbX77pEdXc X+TketQTSgQteamPLUvjdMCCs/fA1IWcE1J+r9h4L0LH/M4hGFCc7BuqnhT4XOaP rCLwdvm145kh1IFJ7fdLpCWVTB/EF3NXN5sDIv7dIRF7Rlv02HM= =aHkF -END PGP SIGNATURE- pgpKi88l2X5UA.pgp Description: PGP signature --- End Message ---
Processed: Re: Bug#1016062: haskell-cborg FTBFS on 32bit: error: Couldn't match expected type ‘Int64#’ with actual type ‘Int#’
Processing control commands: > severity -1 important Bug #1016062 [src:haskell-cborg] haskell-cborg FTBFS on 32bit: error: Couldn't match expected type ‘Int64#’ with actual type ‘Int#’ Severity set to 'important' from 'serious' -- 1016062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1086562: marked as done (gnustep-gui: Please build-depend on imagemagick 7)
Your message dated Mon, 04 Nov 2024 19:49:24 + with message-id and subject line Bug#1086562: fixed in gnustep-gui 0.31.1-6 has caused the Debian Bug report #1086562, regarding gnustep-gui: Please build-depend on imagemagick 7 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.) -- 1086562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnustep-gui Version: 0.31.1-5 Severity: serious Justification: Prevents imagemagick 7 migration Control: block 1060103 by -1 Hello, We are migrating to imagemagick 7 but gnustep-gui explicitly build-depends on libmagickcore-6.q16-dev, thus preventing the migration. Could you bump the dependency to libmagickcore-7.q16-dev ? Thanks, Samuel -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.11.4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Samuel "And the next time you consider complaining that running Lucid Emacs 19.05 via NFS from a remote Linux machine in Paraguay doesn't seem to get the background colors right, you'll know who to thank." (By Matt Welsh) --- End Message --- --- Begin Message --- Source: gnustep-gui Source-Version: 0.31.1-6 Done: Yavor Doganov We believe that the bug you reported is fixed in the latest version of gnustep-gui, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated gnustep-gui 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, 02 Nov 2024 09:19:26 +0200 Source: gnustep-gui Architecture: source Version: 0.31.1-6 Distribution: unstable Urgency: medium Maintainer: Debian GNUstep maintainers Changed-By: Yavor Doganov Closes: 1086562 Changes: gnustep-gui (0.31.1-6) unstable; urgency=medium . * Run wrap-and-sort -ast. * debian/templates/control.m4 (Build-Depends): Replace libmagickcore-6.q16-dev with libmagickcore-7.q16-dev (Closes: #1086562). * debian/control: Regenerate. Checksums-Sha1: 1eaab7e3fb002913602216cc05bd60410a441c57 2864 gnustep-gui_0.31.1-6.dsc b9ecc3ccbeee10ef26185effe8092887c8f7fdc7 23824 gnustep-gui_0.31.1-6.debian.tar.xz bce1b031c9f77199db1bd1be1bd3672b7c0e0ed3 16933 gnustep-gui_0.31.1-6_source.buildinfo Checksums-Sha256: c5bb4bf64755aae3e61933bb0171bd00f7d7b8803b206737f69c5308220145a7 2864 gnustep-gui_0.31.1-6.dsc 8bbee500df299445b9d619cdb6f43f349b4114990afc4653abcd26e17fda0e23 23824 gnustep-gui_0.31.1-6.debian.tar.xz f2bbd48f03ff81f765fdc60e9128775731a4c89f9d930440b24d5add199a581f 16933 gnustep-gui_0.31.1-6_source.buildinfo Files: 5a0974b4e18ad6cbc8f805329b8ebbec 2864 gnustep optional gnustep-gui_0.31.1-6.dsc 4a06bc12d208d81e5e481bbb5429082d 23824 gnustep optional gnustep-gui_0.31.1-6.debian.tar.xz a78dd1078d2b48bc4f9c4170da873771 16933 gnustep optional gnustep-gui_0.31.1-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmcpIZQACgkQEWhSvN91 FcAMhQ//SklBKRBJwUHe/wI4/yF2i7MUgRzifo0Qawts782zT52UZohtA0QuyL0F 8TVRE0IYD5+nhyuC6Dg+VM3cEkNbAmYt8+tRs9GQ/fuJgWNt1N50OzPtG8HqPiI9 gs8tCjGuWBIRCb5V4Bq2V0HMqAE5y0k71iCLryMudgF0yageBH17tmIST7a63o6C IFc9N/QtmJT1rpN391nS246cjb2cLdYGEqj2Zl2JKPXiPwciNriee8jXYwn08s6s lSqHBOJONMFfuOhhLiVg9e2
Bug#1014187: marked as done (fruit: Binary file without a source code)
Your message dated Mon, 04 Nov 2024 18:19:00 + with message-id and subject line Bug#1079960: Removed package(s) from unstable has caused the Debian Bug report #1014187, regarding fruit: Binary file without a source code 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.) -- 1014187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fruit Version: 2.1.dfsg-9 Severity: serious Justification: Policy 2.1 Dear Maintainer, The fruit package comes with a binary file named `book_small.bin'. This binary file does not have a source code. Discussion about this can be found on debian-legal [1]. [1] https://lists.debian.org/debian-legal/2022/06/threads.html#6 Best Regards, mt --- End Message --- --- Begin Message --- Version: 2.1.dfsg-10+rm Dear submitter, as the package fruit has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079960 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1022630: marked as done (node-mermaid: Unable to build with rollup 3)
Your message dated Mon, 04 Nov 2024 18:24:29 + with message-id and subject line Bug#1080267: Removed package(s) from unstable has caused the Debian Bug report #1022630, regarding node-mermaid: Unable to build with rollup 3 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.) -- 1022630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-mermaid Severity: important Tags: ftbfs User: pkg-javascript-de...@lists.alioth.debian.org Usertags: rollup-3 Sent with mass-bug node-mermaid's build failed with rollup 3. This is often due to a bad rollup.config.js which was accepted before (ES in a .js file). To fix it, try to move rollup.config.js into rollup.config.mjs or rewrite it into CommonJS. rollup 3.x is available in experimental branch. --- End Message --- --- Begin Message --- Version: 8.14.0+~cs11.4.14-1+rm Dear submitter, as the package node-mermaid has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080267 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1066987: marked as done (clickhouse: FTBFS: flaky tests)
Your message dated Mon, 04 Nov 2024 18:41:09 + with message-id and subject line Bug#1086505: Removed package(s) from unstable has caused the Debian Bug report #1066987, regarding clickhouse: FTBFS: flaky 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.) -- 1066987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clickhouse Version: 18.16.1+ds-7.4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=clickhouse&arch=amd64&ver=18.16.1%2Bds-7.4%2Bb5&stamp=1710317462&raw=0 10/10 Test #10: with_server ***Failed 357.43 sec The following tests passed: test_longjmp test_siglongjmp test_local_date_time_comparison test_unit_tests_libcommon test_hashing_read_buffer test_multi_version test_expression_analyzer test_in_join_subqueries_preprocessor test_hashing_write_buffer 90% tests passed, 1 tests failed out of 10 Total Test time (real) = 357.54 sec The following tests FAILED: 10 - with_server (Failed) Errors while running CTest Output from these tests are in: /<>/obj-x86_64-linux-gnu/Testing/Temporary/LastTest.log https://buildd.debian.org/status/fetch.php?pkg=clickhouse&arch=mips64el&ver=18.16.1%2Bds-7.4&stamp=1694786851&raw=0 5/7 Test #4: test_hashing_write_buffer .. Passed0.46 sec 7: [OK] SELECT number AS n FROM system.numbers LIMIT 0 7: [OK] SELECT number AS n FROM system.numbers LIMIT 0 6/7 Test #6: test_in_join_subqueries_preprocessor ...***Exception: SegFault 1.64 sec 7/7 Test #7: test_expression_analyzer ... Passed1.64 sec The following tests passed: test_local_date_time_comparison test_multi_version test_hashing_read_buffer test_hashing_write_buffer test_expression_analyzer 71% tests passed, 2 tests failed out of 7 Total Test time (real) = 1.92 sec The following tests FAILED: 3 - test_unit_tests_libcommon (SEGFAULT) 6 - test_in_join_subqueries_preprocessor (SEGFAULT) Errors while running CTest Output from these tests are in: /<>/obj-mips64el-linux-gnuabi64/Testing/Temporary/LastTest.log Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 18.16.1+ds-7.4+rm Dear submitter, as the package clickhouse has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1086505 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1016319: marked as done (apertium-crh-tur: FTBFS: make[2]: *** [Makefile:890: crh-tur.t1x.bin] Error 1)
Your message dated Mon, 04 Nov 2024 18:26:58 + with message-id and subject line Bug#1080410: Removed package(s) from unstable has caused the Debian Bug report #1016319, regarding apertium-crh-tur: FTBFS: make[2]: *** [Makefile:890: crh-tur.t1x.bin] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-crh-tur Version: 0.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > /bin/mkdir -p .deps > apertium-validate-dictionary apertium-crh-tur.crh-tur.dix > cp /<>/apertium-crh-0.2.0/crh.prob crh-tur.prob > cg-comp /<>/apertium-crh-0.2.0/apertium-crh.crh.rlx > crh-tur.rlx.bin > lrx-comp apertium-crh-tur.crh-tur.lrx crh-tur.autolex.bin > cp /<>/apertium-tur-0.2.0/tur.autogen.bin crh-tur.autogen.bin > touch .deps/.d > cp /<>/apertium-tur-0.2.0/tur.autopgen.bin crh-tur.autopgen.bin > apertium-validate-transfer apertium-crh-tur.crh-tur.t1x > apertium-validate-interchunk apertium-crh-tur.crh-tur.t2x > Sections: 3, Rules: 72, Sets: 91, Tags: 96 > 2 rules cannot be skipped by index. > apertium-validate-postchunk apertium-crh-tur.crh-tur.t3x > 13: 282@315 > apertium-validate-transfer apertium-crh-tur.crh-tur.t4x > /bin/zcat /<>/apertium-tur-0.2.0/tur.automorf.att.gz | > hfst-txt2fst > .deps/tur.automorf.hfst > apertium-preprocess-transfer apertium-crh-tur.crh-tur.t1x crh-tur.t1x.bin > apertium-preprocess-transfer apertium-crh-tur.crh-tur.t2x crh-tur.t2x.bin > apertium-preprocess-transfer apertium-crh-tur.crh-tur.t3x crh-tur.t3x.bin > apertium-preprocess-transfer apertium-crh-tur.crh-tur.t4x crh-tur.t4x.bin > apertium-validate-dictionary apertium-crh-tur.crh-tur.dix > cp /<>/apertium-tur-0.2.0/tur.prob tur-crh.prob > cg-comp /<>/apertium-tur-0.2.0/apertium-tur.tur.rlx > tur-crh.rlx.bin > lrx-comp apertium-crh-tur.tur-crh.lrx tur-crh.autolex.bin > cp /<>/apertium-crh-0.2.0/crh.autogen.bin tur-crh.autogen.bin > Error at line 566, column 91: Undefined attr-item a_tags. > make[2]: *** [Makefile:890: crh-tur.t1x.bin] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/07/28/apertium-crh-tur_0.3.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 0.3.0-2+rm Dear submitter, as the package apertium-crh-tur has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080410 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1008982: marked as done (adacontrol: depends on unavailable asis)
Your message dated Mon, 04 Nov 2024 18:31:57 + with message-id and subject line Bug#1080507: Removed package(s) from unstable has caused the Debian Bug report #1008982, regarding adacontrol: depends on unavailable asis 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.) -- 1008982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: adacontrol Severity: serious Tags: upstream ftbfs Justification: Policy 2.2.1 ASIS will soon be removed from Debian. Adacontrol depends on ASIS and should also be removed. --- End Message --- --- Begin Message --- Version: 1.21r6b-7+rm Dear submitter, as the package adacontrol has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080507 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1059261: marked as done (clickhouse: CVE-2023-48298 CVE-2023-47118 CVE-2022-44011 CVE-2022-44010)
Your message dated Mon, 04 Nov 2024 18:41:09 + with message-id and subject line Bug#1086505: Removed package(s) from unstable has caused the Debian Bug report #1059261, regarding clickhouse: CVE-2023-48298 CVE-2023-47118 CVE-2022-44011 CVE-2022-44010 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.) -- 1059261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clickhouse X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for clickhouse. CVE-2023-48298[0]: | ClickHouse® is an open-source column-oriented database management | system that allows generating analytical data reports in real-time. | This vulnerability is an integer underflow resulting in crash due to | stack buffer overflow in decompression of FPC codec. It can be | triggered and exploited by an unauthenticated attacker. The | vulnerability is very similar to CVE-2023-47118 with how the | vulnerable function can be exploited. https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-qw9f-qv29-8938 https://github.com/ClickHouse/ClickHouse/pull/56795 CVE-2023-47118[1]: | ClickHouse® is an open-source column-oriented database management | system that allows generating analytical data reports in real-time. | A heap buffer overflow issue was discovered in ClickHouse server. An | attacker could send a specially crafted payload to the native | interface exposed by default on port 9000/tcp, triggering a bug in | the decompression logic of T64 codec that crashes the ClickHouse | server process. This attack does not require authentication. Note | that this exploit can also be triggered via HTTP protocol, however, | the attacker will need a valid credential as the HTTP authentication | take places first. This issue has been fixed in version | 23.10.2.13-stable, 23.9.4.11-stable, 23.8.6.16-lts and | 23.3.16.7-lts. https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-g22g-p6q2-x39v CVE-2022-44011[2]: | An issue was discovered in ClickHouse before 22.9.1.2603. An | authenticated user (with the ability to load data) could cause a | heap buffer overflow and crash the server by inserting a malformed | CapnProto object. The fixed versions are 22.9.1.2603, 22.8.2.11, | 22.7.4.16, 22.6.6.16, and 22.3.12.19. https://github.com/ClickHouse/ClickHouse/pull/40241 CVE-2022-44010[3]: | An issue was discovered in ClickHouse before 22.9.1.2603. An | attacker could send a crafted HTTP request to the HTTP Endpoint | (usually listening on port 8123 by default), causing a heap-based | buffer overflow that crashes the process. This does not require | authentication. The fixed versions are 22.9.1.2603, 22.8.2.11, | 22.7.4.16, 22.6.6.16, and 22.3.12.19. https://github.com/ClickHouse/ClickHouse/pull/40292 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-48298 https://www.cve.org/CVERecord?id=CVE-2023-48298 [1] https://security-tracker.debian.org/tracker/CVE-2023-47118 https://www.cve.org/CVERecord?id=CVE-2023-47118 [2] https://security-tracker.debian.org/tracker/CVE-2022-44011 https://www.cve.org/CVERecord?id=CVE-2022-44011 [3] https://security-tracker.debian.org/tracker/CVE-2022-44010 https://www.cve.org/CVERecord?id=CVE-2022-44010 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Version: 18.16.1+ds-7.4+rm Dear submitter, as the package clickhouse has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1086505 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1075992: marked as done (laminard: move lib/systemd/system/laminar.service to /usr for DEP17)
Your message dated Mon, 04 Nov 2024 18:23:36 + with message-id and subject line Bug#1080075: Removed package(s) from unstable has caused the Debian Bug report #1075992, regarding laminard: move lib/systemd/system/laminar.service to /usr for DEP17 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.) -- 1075992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: laminard Version: 1.1-1.1 Severity: important User: helm...@debian.org Usertags: dep17m2 laminard installs /lib/systemd/system/laminar.service. Due to /usr-merge, this is an aliased location and we want to resolve aliasing effects in trixie by moving files to their corresponding physical location (DEP17). You have the following options: * Add dh-sequence-movetousr to Build-Depends. (Safe for bookworm-backports) * Pass -DSYSTEMD_UNITDIR=/usr/lib/systemd/system to dh_auto_configure and pick up the new name in debian/lamniard.install. (Not safe for bookworm-backports) * Somehow install the unit using dh_installsystemd (typically by adding a symlink to debian/laminard.laminar.service pointing at the upstream file and adding lib/systemd/system/laminard.install to debian/not-installed) rather than dh_install. (Safe for bookworm-backports, but increased complexity) For more information refer to https://wiki.debian.org/UsrMerge and don't hesitate to ask in case of questions. Helmut --- End Message --- --- Begin Message --- Version: 1.1-1.1+rm Dear submitter, as the package laminar has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080075 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1036688: marked as done (node-mermaid: node-stylis is now packaged separately)
Your message dated Mon, 04 Nov 2024 18:24:29 + with message-id and subject line Bug#1080267: Removed package(s) from unstable has caused the Debian Bug report #1036688, regarding node-mermaid: node-stylis is now packaged separately 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.) -- 1036688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-mermaid Version: 8.14.0+~cs11.4.14-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts node-stylis is now available in a separate package. Please stop shipping a copy of node-stylis and depend on node-stylis instead. Andreas --- End Message --- --- Begin Message --- Version: 8.14.0+~cs11.4.14-1+rm Dear submitter, as the package node-mermaid has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080267 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1032109: marked as done (Don't release with bookworm)
Your message dated Mon, 04 Nov 2024 18:35:41 + with message-id and subject line Bug#1081322: Removed package(s) from unstable has caused the Debian Bug report #1032109, regarding Don't release with bookworm 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.) -- 1032109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-jesseduffield-gocui Version: 0.3.0+git20190803.ad0cd60-1 Severity: serious X-Debbugs-Cc: z...@debian.org Fork of golang-github-jroimartin-gocui. No reverse-depends. --- End Message --- --- Begin Message --- Version: 0.3.0+git20190803.ad0cd60-1+rm Dear submitter, as the package golang-github-jesseduffield-gocui has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1081322 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1019455: marked as done (laminard: WebUI of laminar fails because newer incompatible version of Chart.js is included)
Your message dated Mon, 04 Nov 2024 18:23:36 + with message-id and subject line Bug#1080075: Removed package(s) from unstable has caused the Debian Bug report #1019455, regarding laminard: WebUI of laminar fails because newer incompatible version of Chart.js is included 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.) -- 1019455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: laminard Version: 1.1-1+b2 Severity: grave Justification: renders package unusable laminar currently uses Chart.js 2.7.2 (also in newer version 1.2 and on latest master) Debian packaging replaces this with the version packaged in Debian, which is 3.9.x curently, the bookworm-package of laminar seems to actually include 3.7.1. Version 2 and 3 of Chart.js are not compatible and thus the WebUI of laminar cannot be used at all! The JavaScript error in Browser-console is "Chart.scaleService is undefined". See https://github.com/ohwgiles/laminar/issues/175 for the related upstream report. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages laminard depends on: ii init-system-helpers 1.64 ii libc62.34-7 ii libcapnp-0.9.1 0.9.1-4+b1 ii libgcc-s112.2.0-1 ii libsqlite3-0 3.39.3-1 ii libstdc++6 12.2.0-1 ii sysuser-helper 1.3.7+really1.4.1 ii zlib1g 1:1.2.11.dfsg-4.1 Versions of packages laminard recommends: ii daemon 0.8-1 laminard suggests no packages. -- Configuration Files: /etc/laminar.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1-1.1+rm Dear submitter, as the package laminar has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080075 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1071455: marked as done (python-html-sanitizer: python3-lxml-html-clean is now a separate package)
Your message dated Mon, 04 Nov 2024 18:22:04 + with message-id and subject line Bug#1080054: Removed package(s) from unstable has caused the Debian Bug report #1071455, regarding python-html-sanitizer: python3-lxml-html-clean is now a separate package 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.) -- 1071455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-html-sanitizer Version: 2.2-1 lxml.html.clean has been moved from python3-lxml to a new package python3-lxml-html-clean (as discussed in https://bugs.launchpad.net/lxml/+bug/1958539). This package uses lxml.html.clean but only declares a relationship on python3-lxml. I don't know how central the functionality that requires lxml.html.clean is, and hence whether Depends, Recommends or Suggests is appropriate. In the longer term, if you are using lxml.html.clean for security against code injection, be aware that it is not a very secure approach. lxml upstream recommend moving to something stronger e.g. python3-bleach or nh3. --- End Message --- --- Begin Message --- Version: 2.2-1+rm Dear submitter, as the package python-html-sanitizer has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080054 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1008366: marked as done (python-html-sanitizer: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)
Your message dated Mon, 04 Nov 2024 18:22:04 +
with message-id
and subject line Bug#1080054: Removed package(s) from unstable
has caused the Debian Bug report #1008366,
regarding python-html-sanitizer: 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.)
--
1008366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-html-sanitizer
Version: 1.9.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/html_sanitizer
> copying html_sanitizer/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/html_sanitizer
> copying html_sanitizer/__main__.py ->
> /<>/.pybuild/cpython3_3.9/build/html_sanitizer
> copying html_sanitizer/tests.py ->
> /<>/.pybuild/cpython3_3.9/build/html_sanitizer
> copying html_sanitizer/django.py ->
> /<>/.pybuild/cpython3_3.9/build/html_sanitizer
> copying html_sanitizer/sanitizer.py ->
> /<>/.pybuild/cpython3_3.9/build/html_sanitizer
> running egg_info
> creating html_sanitizer.egg-info
> writing html_sanitizer.egg-info/PKG-INFO
> writing dependency_links to html_sanitizer.egg-info/dependency_links.txt
> writing requirements to html_sanitizer.egg-info/requires.txt
> writing top-level names to html_sanitizer.egg-info/top_level.txt
> writing manifest file 'html_sanitizer.egg-info/SOURCES.txt'
> reading manifest file 'html_sanitizer.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'html_sanitizer.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m unittest discover -v
> test_01_sanitize (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_02_a_tag (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_03_merge (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_04_p_in_li (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_05_p_in_p (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_06_allowlist (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_07_configuration (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_08_li_with_marker (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_09_empty_p_text_in_li (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_10_broken_html (html_sanitizer.tests.SanitizerTestCase) ...
> test_11_nofollow (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_12_replacements (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_13_autolink (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_14_classes (html_sanitizer.tests.SanitizerTestCase)
> Class attributes should not be treated specially ... ok
> test_15_classes (html_sanitizer.tests.SanitizerTestCase)
> Class attributes may disable merging ... ok
> test_16_emoji (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_anchor_names (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_billion_laughs (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_blob (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_custom_allowed_attribute (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_data_attributes (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_keep_consecutive_br_tags (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_keep_typographic_whitespace (html_sanitizer.tests.SanitizerTestCase) ...
> ok
> test_more_merging (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_remove_everything (html_sanitizer.tests.SanitizerTestCase) ... ok
> test_strip_typographic_whitespace (html_sanitizer.tests.SanitizerTestCa
Bug#1070710: marked as done (python-html-sanitizer: CVE-2024-34078: Arbitrary HTML present after sanitization because of unicode normalization)
Your message dated Mon, 04 Nov 2024 18:22:04 + with message-id and subject line Bug#1080054: Removed package(s) from unstable has caused the Debian Bug report #1070710, regarding python-html-sanitizer: CVE-2024-34078: Arbitrary HTML present after sanitization because of unicode normalization 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.) -- 1070710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-html-sanitizer Version: 2.2-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for python-html-sanitizer. CVE-2024-34078[0]: | html-sanitizer is an allowlist-based HTML cleaner. If using | `keep_typographic_whitespace=False` (which is the default), the | sanitizer normalizes unicode to the NFKC form at the end. Some | unicode characters normalize to chevrons; this allows specially | crafted HTML to escape sanitization. The problem has been fixed in | 2.4.2. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-34078 https://www.cve.org/CVERecord?id=CVE-2024-34078 [1] https://github.com/matthiask/html-sanitizer/security/advisories/GHSA-wvhx-q427-fgh3 [2] https://github.com/matthiask/html-sanitizer/commit/48db42fc5143d0140c32d929c46b802f96913550 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Version: 2.2-1+rm Dear submitter, as the package python-html-sanitizer has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080054 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#958692: marked as done (node-matrix-js-sdk: Remove dependency to node-request)
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #958692, regarding node-matrix-js-sdk: Remove dependency to node-request to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 958692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-matrix-js-sdk Severity: important Control: block 956423 by -1 Upstream has deprecated node-request: https://github.com/request/request/issues/3142 It can be replaced by node-got --- End Message --- --- Begin Message --- Version: 9.11.0+~cs9.9.16-2+rm Dear submitter, as the package node-matrix-js-sdk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080047 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1077820: marked as done (clickhouse: CVE-2024-6873)
Your message dated Mon, 04 Nov 2024 18:41:09 + with message-id and subject line Bug#1086505: Removed package(s) from unstable has caused the Debian Bug report #1077820, regarding clickhouse: CVE-2024-6873 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.) -- 1077820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clickhouse X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for clickhouse. CVE-2024-6873[0]: | It is possible to crash or redirect the execution flow of the | ClickHouse server process from an unauthenticated vector by sending | a specially crafted request to the ClickHouse server native | interface. This redirection is limited to what is available within a | 256-byte range of memory at the time of execution, and no known | remote code execution (RCE) code has been produced or exploited. | Fixes have been merged to all currently supported version of | ClickHouse. If you are maintaining your own forked version of | ClickHouse or using an older version and cannot upgrade, the fix for | this vulnerability can be found in this commit | https://github.com/ClickHouse/ClickHouse/pull/64024 . https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-432f-r822-j66f https://github.com/ClickHouse/ClickHouse/pull/64024 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-6873 https://www.cve.org/CVERecord?id=CVE-2024-6873 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Version: 18.16.1+ds-7.4+rm Dear submitter, as the package clickhouse has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1086505 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1070658: marked as done (FTBFS: error: expected ‘)’ before ‘maxLength’)
Your message dated Mon, 04 Nov 2024 18:41:09 + with message-id and subject line Bug#1086505: Removed package(s) from unstable has caused the Debian Bug report #1070658, regarding FTBFS: error: expected ‘)’ before ‘maxLength’ 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.) -- 1070658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clickhouse Version: 18.16.1+ds-7.4 Severity: serious Tags: ftbfs Justification: ftbfs clickhouse FTBFS in unstable: [ 87%] Building CXX object dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o cd /<>/obj-x86_64-linux-gnu/dbms && /usr/bin/c++ -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_NO_LIB -DBOOST_SYSTEM_DYN_LINK -DBOOST_SYSTEM_NO_LIB -Ddbms_EXPORTS -I/<>/contrib/cityhash102/include -I/<>/libs/libpocoext/include -I/<>/libs/libmysqlxx/include -I/<>/contrib/libbtrie/include -isystem /<>/contrib/libdivide -isystem /<>/dbms/src -isystem /<>/obj-x86_64-linux-gnu/dbms/src -isystem /<>/contrib/libpcg-random/include -isystem /<>/libs/libcommon/include -isystem /<>/obj-x86_64-linux-gnu/libs/libcommon/include -isystem /usr/include/metrohash -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fno-omit-frame-pointer -Wall -Wnon-virtual-dtor -Wextra -O2 -g -DNDEBUG -O3 -std=c++17 -flto=auto -fno-fat-lto-objects -fPIC -fno-tree-loop-distribute-patterns -MD -MT dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o -MF CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o.d -o CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o -c /<>/dbms/src/Storages/MergeTree/LevelMergeSelector.cpp In file included from /<>/dbms/src/Interpreters/InterserverIOHandler.h:8, from /<>/dbms/src/Storages/MergeTree/DataPartsExchange.h:3, from /<>/dbms/src/Storages/MergeTree/DataPartsExchange.cpp:1: /usr/include/Poco/BinaryWriter.h:137:14: error: expected ‘)’ before ‘maxLength’ 137 | void writeCString(const char* cString, std::streamsize maxLength = DEFAULT_MAX_CSTR_LENGTH); | ^~~~ /usr/include/Poco/BinaryWriter.h:137:14: note: to match this ‘(’ 137 | void writeCString(const char* cString, std::streamsize maxLength = DEFAULT_MAX_CSTR_LENGTH); | ^~~~ Full build log: https://debusine.debian.net/artifact/66597/clickhouse_18.16.1+ds-7.4_amd64-2024-05-06T16:48:46Z.build Stefano --- End Message --- --- Begin Message --- Version: 18.16.1+ds-7.4+rm Dear submitter, as the package clickhouse has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1086505 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1030453: marked as done (devpi-common: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Mon, 04 Nov 2024 18:33:08 +
with message-id
and subject line Bug#1080509: Removed package(s) from unstable
has caused the Debian Bug report #1030453,
regarding devpi-common: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1030453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: devpi-common
Version: 3.2.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="cd {dir}; {interpreter} -m pytest"
> dh_auto_test
> I: pybuild base:240: cd /<>; python3.11 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.1, pluggy-1.0.0+repack
> rootdir: /<>, configfile: tox.ini
> collected 175 items
>
> testing/test_archive.py [
> 16%]
> testing/test_lazydecorator.py [
> 18%]
> testing/test_metadata.py ... [
> 45%]
> .F.F.[
> 54%]
> testing/test_proc.py .. [
> 56%]
> testing/test_request.py .[
> 58%]
> testing/test_types.py .. [
> 60%]
> testing/test_url.py [
> 89%]
> .. [
> 90%]
> testing/test_validation.py
> [100%]
>
> === FAILURES
> ===
> _ TestBasenameMeta.test_noversion_sameproject
> __
>
> self =
>
> def test_noversion_sameproject(self):
> meta1 = BasenameMeta("py-1.0.zip", sameproject=True)
> > meta2 = BasenameMeta("master", sameproject=True)
>
> testing/test_metadata.py:132:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> devpi_common/metadata.py:151: in __init__
> self.cmpval = (parse_version(version), normalize_name(name), ext)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self = <[AttributeError("'Version' object has no attribute '_version'")
> raised in repr()] Version object at 0x7f8495c2cc90>
> version = ''
>
> def __init__(self, version: str) -> None:
>
> # Validate the version and parse it into pieces
> match = self._regex.search(version)
> if not match:
> > raise InvalidVersion(f"Invalid version: '{version}'")
> E pkg_resources.extern.packaging.version.InvalidVersion: Invalid
> version: ''
>
> /usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/version.py:266:
> InvalidVersion
> _ TestBasenameMeta.test_sort_sameproject_links
> _
>
> self =
>
> def test_sort_sameproject_links(self):
> links = ["master", "py-1.0.zip", "trunk.zip", "py-1.1.tgz"]
> > newlinks = sorted_sameproject_links(links)
>
> testing/test_metadata.py:147:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> devpi_common/metadata.py:159: in sorted_sameproject_links
> s = sorted((BasenameMeta(link, sameproject=True)
> devpi_common/metadata.py:159: in
> s = sorted((BasenameMeta(link, sameproject=True)
> devpi_common/metadata.py:151: in __init__
> self.cmpval = (parse_version(version), normalize_name(name), ext)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self = <[AttributeError("&#x
Bug#1018970: marked as done (node-matrix-js-sdk: CVE-2022-36059)
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #1018970, regarding node-matrix-js-sdk: CVE-2022-36059 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.) -- 1018970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-matrix-js-sdk Version: 9.11.0+~cs9.9.16-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for node-matrix-js-sdk. CVE-2022-36059[0]: 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-2022-36059 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36059 [1] https://matrix.org/blog/2022/08/31/security-releases-matrix-js-sdk-19-4-0-and-matrix-react-sdk-3-53-0/ [2] https://github.com/matrix-org/matrix-js-sdk/commit/8716c1ab9ba93659173b806097c46a2be115199f Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Version: 9.11.0+~cs9.9.16-2+rm Dear submitter, as the package node-matrix-js-sdk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080047 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1033621: marked as done (node-matrix-js-sdk: CVE-2023-28427)
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #1033621, regarding node-matrix-js-sdk: CVE-2023-28427 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.) -- 1033621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-matrix-js-sdk Version: 9.11.0+~cs9.9.16-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for node-matrix-js-sdk. CVE-2023-28427[0]: | Prototype pollution If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-28427 https://www.cve.org/CVERecord?id=CVE-2023-28427 [1] https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-mwq8-fjpf-c2gr Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Version: 9.11.0+~cs9.9.16-2+rm Dear submitter, as the package node-matrix-js-sdk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080047 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#994213: marked as done (node-matrix-js-sdk: CVE-2021-40823: E2EE vulnerability)
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #994213, regarding node-matrix-js-sdk: CVE-2021-40823: E2EE vulnerability 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.) -- 994213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-matrix-js-sdk Version: 9.11.0+~cs9.9.16-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for node-matrix-js-sdk. CVE-2021-40823[0]: | E2EE vulnerability 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-2021-40823 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40823 [1] https://matrix.org/blog/2021/09/13/vulnerability-disclosure-key-sharing/ [2] https://github.com/matrix-org/matrix-js-sdk/commit/894c24880da0e1cc81818f51c0db80e3c9fb2be9 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 9.11.0+~cs9.9.16-2+rm Dear submitter, as the package node-matrix-js-sdk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080047 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1021136: marked as done (node-matrix-js-sdk: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251)
Your message dated Mon, 04 Nov 2024 18:21:25 + with message-id and subject line Bug#1080047: Removed package(s) from unstable has caused the Debian Bug report #1021136, regarding node-matrix-js-sdk: CVE-2022-39236 CVE-2022-39249 CVE-2022-39251 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.) -- 1021136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sox X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for sox. CVE-2022-39236[0]: | Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. | Starting with version 17.1.0-rc.1, improperly formed beacon events can | disrupt or impede the matrix-js-sdk from functioning properly, | potentially impacting the consumer's ability to process data safely. | Note that the matrix-js-sdk can appear to be operating normally but be | excluding or corrupting runtime data presented to the consumer. This | is patched in matrix-js-sdk v19.7.0. Redacting applicable events, | waiting for the sync processor to store data, and restarting the | client are possible workarounds. Alternatively, redacting the | applicable events and clearing all storage will fix the further | perceived issues. Downgrading to an unaffected version, noting that | such a version may be subject to other vulnerabilities, will | additionally resolve the issue. https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-hvv8-5v86-r45x https://github.com/matrix-org/matrix-js-sdk/commit/a587d7c36026fe1fcf93dfff63588abee359be76 https://github.com/matrix-org/matrix-spec-proposals/pull/3488 CVE-2022-39249[1]: | Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. | Prior to version 19.7.0, an attacker cooperating with a malicious | homeserver can construct messages appearing to have come from another | person. Such messages will be marked with a grey shield on some | platforms, but this may be missing in others. This attack is possible | due to the matrix-js-sdk implementing a too permissive key forwarding | strategy on the receiving end. Starting with version 19.7.0, the | default policy for accepting key forwards has been made more strict in | the matrix-js-sdk. matrix-js-sdk will now only accept forwarded keys | in response to previously issued requests and only from own, verified | devices. The SDK now sets a `trusted` flag on the decrypted message | upon decryption, based on whether the key used to decrypt the message | was received from a trusted source. Clients need to ensure that | messages decrypted with a key with `trusted = false` are decorated | appropriately, for example, by showing a warning for such messages. | This attack requires coordination between a malicious homeserver and | an attacker, and those who trust your homeservers do not need a | workaround. https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-6263-x97c-c4gg https://github.com/matrix-org/matrix-js-sdk/commit/a587d7c36026fe1fcf93dfff63588abee359be76 https://github.com/matrix-org/matrix-spec-proposals/pull/3061 https://matrix.org/blog/2022/09/28/upgrade-now-to-address-encryption-vulns-in-matrix-sdks-and-clients CVE-2022-39251[2]: | Matrix Javascript SDK is the Matrix Client-Server SDK for JavaScript. | Prior to version 19.7.0, an attacker cooperating with a malicious | homeserver can construct messages that legitimately appear to have | come from another person, without any indication such as a grey | shield. Additionally, a sophisticated attacker cooperating with a | malicious homeserver could employ this vulnerability to perform a | targeted attack in order to send fake to-device messages appearing to | originate from another user. This can allow, for example, to inject | the key backup secret during a self-verification, to make a targeted | device start using a malicious key backup spoofed by the homeserver. | These attacks are possible due to a protocol confusion vulnerability | that accepts to-device messages encrypted with Megolm instead of Olm. | Starting with version 19.7.0, matrix-js-sdk has been modified to only | accept Olm-encrypted to-device messages. Out of caution, several other | checks have been audited or added. This attack requires coordination | between a malicious home server and an attacker, so those who trust | their home servers do not need a workaround. https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-r48r-j8fx-mq2c https://github.com/matrix-org/matrix-js-sdk/c
Processed: limit source to criu, tagging 1054814
Processing commands for cont...@bugs.debian.org: > limit source criu Limiting to bugs with field 'source' containing at least one of 'criu' Limit currently set to 'source':'criu' > tags 1054814 + pending Bug #1054814 [src:criu] criu: FTBFS: bad install directory or PYTHONPATH Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997156: marked as done (crazydiskinfo: FTBFS: main.cpp:217:18: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Mon, 04 Nov 2024 18:30:12 + with message-id and subject line Bug#1080504: Removed package(s) from unstable has caused the Debian Bug report #997156, regarding crazydiskinfo: FTBFS: main.cpp:217:18: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: crazydiskinfo Version: 1.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -MD -MT CMakeFiles/CrazyDiskInfo.dir/main.cpp.o -MF > CMakeFiles/CrazyDiskInfo.dir/main.cpp.o.d -o > CMakeFiles/CrazyDiskInfo.dir/main.cpp.o -c /<>/main.cpp > /<>/main.cpp: In function ‘void drawVersion(WINDOW*)’: > /<>/main.cpp:217:18: error: format not a string literal and no > format arguments [-Werror=format-security] > 217 | mvwprintw(window, 0, (width - title.length()) / 2, > title.c_str()); > | > ~^~~~ > /<>/main.cpp: In function ‘void drawDeviceBar(WINDOW*, const > std::vector&, int)’: > /<>/main.cpp:235:53: warning: format ‘%f’ expects argument of > type ‘double’, but argument 5 has type ‘const std::pair’ > [-Wformat=] > 235 | mvwprintw(window, 1, x, "%.1f ", > smartList[i].temperature); > | ~~~^ > | | > | double > /<>/main.cpp:250:34: error: format not a string literal and no > format arguments [-Werror=format-security] > 250 | mvwprintw(window, 2, x, > smartList[i].deviceName.c_str()); > | > ~^~~ > /<>/main.cpp:259:34: error: format not a string literal and no > format arguments [-Werror=format-security] > 259 | mvwprintw(window, 2, x, > smartList[i].deviceName.c_str()); > | > ~^~~ > /<>/main.cpp: In function ‘void drawStatus(WINDOW*, const > SMART&, const Option&)’: > /<>/main.cpp:358:38: warning: format ‘%llu’ expects argument of > type ‘long long unsigned int’, but argument 3 has type ‘long unsigned int’ > [-Wformat=] > 358 | wprintw(window, " %llu ", > std::get<1>(smart.powerOnCount)); > | ~~~^ > ~~~ > | | | > | | long unsigned int > | long long unsigned int > | %lu > /<>/main.cpp:375:38: warning: format ‘%llu’ expects argument of > type ‘long long unsigned int’, but argument 3 has type ‘long unsigned int’ > [-Wformat=] > 375 | wprintw(window, " %llu ", > std::get<1>(smart.powerOnHour)); > | ~~~^ > ~~ > | | | > | | long unsigned int > | long long unsigned int > | %lu > cc1plus: some warnings being treated as errors > make[3]: *** [CMakeFiles/CrazyDiskInfo.dir/build.make:79: > CMakeFiles/CrazyDiskInfo.dir/main.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/crazydiskinfo_1.1.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this packag
Bug#1027037: marked as done (backdoor-factory: Backdoor-factory isn't working after python3 transition)
Your message dated Mon, 04 Nov 2024 18:29:34 +
with message-id
and subject line Bug#1080503: Removed package(s) from unstable
has caused the Debian Bug report #1027037,
regarding backdoor-factory: Backdoor-factory isn't working after python3
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.)
--
1027037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: backdoor-factory
Version: 3.4.2+dfsg-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: charlesmel...@outlook.com
Dear Maintainers, hi.
I was working to get a new debian release of backdoor-factory (bdf) before the
freeze and noted while testing it that it doesn't work with python3.
I tested the application trying to patch a binary in 4 scenarios:
1. ELF binary - ssh with -fPIE compiler flag set (it
shouldn't work as warned in the man page);
2. ELF binary - devtodo without -fPIE flag set (I've built it locally
and disabled hardening option in d/rules);
3. PE binary - premake4.exe;
4. PE binary - PSTools from microsoft (the one actually show in the README
example).
In all test scenarios, bdf showed a message saying the binary wasn't
compatible although they were in 3 out of 4 scenarios.
Digging a little deeper in the source code, I've found the problem.
Even though bdf was patched to build with python3, those changes only
fixed syntactic problems (mostly print statements). The actual problem -
and source of the bug - is the change on how files are read in python3.
In python2, everything read from a file was considered a string. But in
python3 it is considered a bitearray if the file was opened as a binary
('rb' option for example). In the source code of bdf, everything is treated
as strings (comparisons, assignments, operations, etc), but now everything
read from the binary file is a bytearray so the program fails to
identify it as a susceptible binary.
Even though it would be easy to patch this to make bdf correctly
identify the file, every step after that would also need to be fixed
(Right now, it basicaly fails to identify the files as susceptible and
exits). That would require a major rewrite of the program, together with
testing and debugging.
Cheers,
Charles
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 3.4.2+dfsg-5+rm
Dear submitter,
as the package backdoor-factory has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1080503
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#988156: marked as done (breezy breaks breezy-loom autopkgtest: FAILED (failures=4))
Your message dated Mon, 04 Nov 2024 18:28:56 +
with message-id
and subject line Bug#1080502: Removed package(s) from unstable
has caused the Debian Bug report #988156,
regarding breezy breaks breezy-loom autopkgtest: FAILED (failures=4)
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.)
--
988156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breezy, breezy-loom
Control: found -1 breezy/3.2.0-1
Control: found -1 breezy-loom/3.0.0+bzr167-1
Severity: serious
Tags: sid bullseye bullseye-ignore
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of breezy the autopkgtest of breezy-loom fails in
testing when that autopkgtest is run with the binary packages of breezy
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
breezy from testing3.2.0-1
breezy-loomfrom testing3.0.0+bzr167-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of breezy to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package? Note, because we're in the freeze for
bullseye, we need to take a bit of care. I have marked this bug as
bullseye-ignore because I don't intent this bug to cause the removal of
breezy-loom from bullseye and the autopkgtest failure will keep this
version of breezy out of bullseye automatically.
More information about this bug and the reason for filing it can be found
on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=breezy
https://ci.debian.net/data/autopkgtest/testing/amd64/b/breezy-loom/12136628/log.gz
==
FAIL:
breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits
--
Traceback (most recent call last):
testtools.testresult.real._StringException: log: {{{
2.916 creating repository in
file:///tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source/.bzr/.
2.919 creating branch in
file:///tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source/
2.926 trying to create missing lock
'/tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source/.bzr/checkout/dirstate'
2.926 opening working tree
'/tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source'
2.933 opening working tree
'/tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source'
2.937 opening working tree
'/tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source'
2.945 preparing to commit
INFO Committing to:
/tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source/
2.948 Selecting files for commit with filter None
INFO Committed revision 1.
2.958 Committed revid b'bottom-1' as revno 1.
2.965 Base revid: b'null:'
INFO All changes applied successfully.
INFO Moved to thread 'top'.
INFO This thread is now empty, you may wish to run "bzr
combine-thread" to remove it.
2.976 preparing to commit
INFO Committing to:
/tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source/
2.978 Selecting files for commit with filter None
INFO Committed revision 2.
2.988 Committed revid b'top-1' as revno 2.
INFO All changes applied successfully.
INFO Moved to thread 'bottom'.
3.006 preparing to commit
INFO Committing to:
/tmp/testbzr-629rrjpc.tmp/breezy.plugins.loom.tests.test_tree.TestTreeDecorator.test_up_many_commits/work/source/
3.008 Selecting files for commit with filter None
INFO Committed revision 2.
3.017 Committed revid b'bottom-2' as revno 2.
3.028 Base revid: b'bottom-1'
INFO All c
Bug#414092: marked as done (airport-utils: Tools start and quit immediately without working)
Your message dated Mon, 04 Nov 2024 18:28:00 + with message-id and subject line Bug#1080501: Removed package(s) from unstable has caused the Debian Bug report #414092, regarding airport-utils: Tools start and quit immediately without working 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.) -- 414092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: airport-utils Version: 1-3 Severity: grave Justification: renders package unusable All of the aiport-utils tools don't seem to be working anymore. They start up and immediately stop without any error. Trying to run the tools with java -jar sometool.jar gives the same result. Disk rattling, program starting, but then nothing and you're returned to the shell prompt without a workable tool. Is there maybe some mysterious incompatibility problem between the Sun 6 JRE and the airport utils? Arjan -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19.1 Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages airport-utils depends on: pn gij | java-virtual-machine (no description available) ii libgcj7-awt 4.1.1-20 AWT peer runtime libraries for use ii sun-java6-jre [java2-runtime] 6-00-2 Sun Java(TM) Runtime Environment ( airport-utils recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 2-8+rm Dear submitter, as the package airport-utils has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080501 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1008348: marked as done (apertium-sme-nob: FTBFS: semanticroles.cg3: Error: Expected set on line 4400 near `;␊␊TEMPLATE uniqueLO`!)
Your message dated Mon, 04 Nov 2024 18:27:31 + with message-id and subject line Bug#1080411: Removed package(s) from unstable has caused the Debian Bug report #1008348, regarding apertium-sme-nob: FTBFS: semanticroles.cg3: Error: Expected set on line 4400 near `;␊␊TEMPLATE uniqueLO`! 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.) -- 1008348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-sme-nob Version: 0.6.1+ds.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/giella-sme-0.1.0/src/syntax' > CP dependency.cg3 > CG3COMP disambiguator.bin > CP functions.cg3 > CG3COMP semanticroles.bin > CG3COMP valency.bin > CP korp.cg3 > CG3COMP semsets.bin > CG3COMP dependency.bin > CG3COMP functions.bin > CG3COMP korp.bin > Warning: No corresponding rule available for anchor 'END' on line 112! > Sections: 0, Rules: 0, Sets: 1, Tags: 369 > Sections: 1, Rules: 363, Sets: 439, Tags: 665 > 3 rules cannot be skipped by index. > Grammar has dependency rules. > Sections: 1, Rules: 451, Sets: 901, Tags: 1462 > 16 rules cannot be skipped by index. > semanticroles.cg3: Error: Expected set on line 4400 near `;␊␊TEMPLATE > uniqueLO`! > Sections: 1, Rules: 467, Sets: 908, Tags: 1467 > 16 rules cannot be skipped by index. > Error: Grammar could not be parsed - exiting! > make[4]: *** [Makefile:851: semanticroles.bin] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-sme-nob_0.6.1+ds.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 0.6.1+ds.1-2+rm Dear submitter, as the package apertium-sme-nob has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080411 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1016336: marked as done (apertium-mlt-ara: FTBFS: make[1]: *** [Makefile:790: ara-mlt.t1x.bin] Error 1)
Your message dated Mon, 04 Nov 2024 18:25:17 + with message-id and subject line Bug#1080405: Removed package(s) from unstable has caused the Debian Bug report #1016336, regarding apertium-mlt-ara: FTBFS: make[1]: *** [Makefile:790: ara-mlt.t1x.bin] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-mlt-ara Version: 0.2.0~r62623-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > apertium-validate-dictionary apertium-mlt-ara.mlt.dix > if [ ! -d .deps ]; then mkdir .deps; fi > apertium-validate-transfer apertium-mlt-ara.mlt-ara.t1x > apertium-validate-interchunk apertium-mlt-ara.mlt-ara.t2x > apertium-validate-postchunk apertium-mlt-ara.mlt-ara.t3x > apertium-validate-dictionary apertium-mlt-ara.ara.dix > apertium-validate-dictionary apertium-mlt-ara.post-ara.dix > apertium-validate-dictionary apertium-mlt-ara.translit.dix > xsltproc lexchoicebil.xsl apertium-mlt-ara.mlt-ara.dix > > .deps/apertium-mlt-ara.mlt-ara.dix > apertium-preprocess-transfer apertium-mlt-ara.mlt-ara.t3x mlt-ara.t3x.bin > apertium-preprocess-transfer apertium-mlt-ara.mlt-ara.t2x mlt-ara.t2x.bin > lt-comp lr apertium-mlt-ara.post-ara.dix mlt-ara.autopgen.bin > lt-comp lr apertium-mlt-ara.translit.dix ara-mlt.autotra.bin > cg-comp apertium-mlt-ara.mlt-ara.rlx mlt-ara.rlx.bin > apertium-validate-dictionary apertium-mlt-ara.ara.dix > main@standard 35 136 > apertium-validate-transfer apertium-mlt-ara.ara-mlt.t1x > apertium-mlt-ara.mlt-ara.rlx: Warning: Expected closing ; on line 158 after > previous rule! > apertium-mlt-ara.mlt-ara.rlx: Warning: Expected closing ; on line 187 after > previous rule! > main@inconditional 5 41 > Sections: 1, Rules: 29, Sets: 24, Tags: 81 > apertium-validate-dictionary apertium-mlt-ara.mlt.dix > apertium-validate-dictionary apertium-mlt-ara.post-mlt.dix > apertium-preprocess-transfer apertium-mlt-ara.mlt-ara.t1x mlt-ara.t1x.bin > apertium-preprocess-transfer apertium-mlt-ara.ara-mlt.t1x ara-mlt.t1x.bin > lt-comp lr apertium-mlt-ara.post-mlt.dix ara-mlt.autopgen.bin > Error at line 599, column 21: Undefined attr-item a_trans. > Error at line 2112, column 51: Undefined attr-item a_mood. > make[1]: *** [Makefile:790: ara-mlt.t1x.bin] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/07/28/apertium-mlt-ara_0.2.0~r62623-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 0.2.0~r62623-3+rm Dear submitter, as the package apertium-mlt-ara has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080405 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Bug#1016320: marked as done (apertium-cy-en: FTBFS: make[2]: *** [Makefile:816: en-cy.t2x.bin] Error 1)
Your message dated Mon, 04 Nov 2024 18:25:47 + with message-id and subject line Bug#1080407: Removed package(s) from unstable has caused the Debian Bug report #1016320, regarding apertium-cy-en: FTBFS: make[2]: *** [Makefile:816: en-cy.t2x.bin] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-cy-en Version: 0.1.1~r57554-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > apertium-validate-dictionary apertium-cy-en.cy.dix > apertium-validate-dictionary apertium-cy-en.cy-en.dix > apertium-validate-dictionary apertium-cy-en.en.dix > apertium-validate-dictionary apertium-cy-en.post-en.dix > apertium-validate-dictionary apertium-cy-en.en.dix > apertium-validate-dictionary apertium-cy-en.cy-en.dix > apertium-validate-dictionary apertium-cy-en.cy.dix > apertium-validate-dictionary apertium-cy-en.post-cy.dix > lt-comp lr apertium-cy-en.post-en.dix cy-en.autopgen.bin > main@standard 44 64 > apertium-validate-dictionary apertium-cy-en.orth-cy.dix > lt-comp lr apertium-cy-en.orth-cy.dix en-cy.autoorth.bin > main@standard 27 310 > cg-comp apertium-cy-en.cy-en.rlx cy-en.rlx.bin > apertium-cy-en.cy-en.rlx: Warning: Tag '+' on line 83 looks like a set > operator. Maybe you meant to do SET instead of LIST? > apertium-cy-en.cy-en.rlx: Warning: Tag '+' on line 84 looks like a set > operator. Maybe you meant to do SET instead of LIST? > apertium-cy-en.cy-en.rlx: Warning: Tag '+' on line 85 looks like a set > operator. Maybe you meant to do SET instead of LIST? > apertium-cy-en.cy-en.rlx: Warning: Tag '+' on line 86 looks like a set > operator. Maybe you meant to do SET instead of LIST? > apertium-cy-en.cy-en.rlx: Warning: Tag '+' on line 87 looks like a set > operator. Maybe you meant to do SET instead of LIST? > apertium-cy-en.cy-en.rlx: Warning: Tag '+' on line 88 looks like a set > operator. Maybe you meant to do SET instead of LIST? > lt-comp lr apertium-cy-en.post-cy.dix en-cy.autopgen.bin > Sections: 2, Rules: 107, Sets: 150, Tags: 217 > 15 rules cannot be skipped by index. > apertium-validate-transfer apertium-cy-en.cy-en.t1x > apertium-preprocess-transfer apertium-cy-en.cy-en.t1x cy-en.t1x.bin > Warning at line 1154, column 9: Paths to rule 4 blocked by rule 3. > Warning at line 2387, column 11: Paths to rule 30 blocked by rule 3. > Warning at line 2387, column 11: Paths to rule 30 blocked by rule 4. > Warning at line 2387, column 11: Paths to rule 30 blocked by rule 4. > Warning at line 2387, column 11: Paths to rule 30 blocked by rule 4. > Warning at line 2425, column 9: Paths to rule 31 blocked by rule 29. > Warning at line 2425, column 9: Paths to rule 31 blocked by rule 29. > Warning at line 2425, column 9: Paths to rule 31 blocked by rule 29. > Warning at line 2425, column 9: Paths to rule 31 blocked by rule 29. > Warning at line 2425, column 9: Paths to rule 31 blocked by rule 29. > Warning at line 2425, column 9: Paths to rule 31 blocked by rule 29. > Warning at line 2425, column 9: Paths to rule 31 blocked by rule 29. > Warning at line 2425, column 9: Paths to rule 31 blocked by rule 29. > main@standard 12 109 > mutations@standard 28 147 > apertium-validate-interchunk apertium-cy-en.cy-en.t2x > apertium-preprocess-transfer apertium-cy-en.cy-en.t2x cy-en.t2x.bin > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule 11. > Warning at line 1437, column 17: Paths to rule 15 blocked by rule
Bug#1005670: marked as done (apertium-kaz-tat: FTBFS: ERROR: Transducer contains epsilon transition to a final state. Aborting.)
Your message dated Mon, 04 Nov 2024 18:26:18 + with message-id and subject line Bug#1080408: Removed package(s) from unstable has caused the Debian Bug report #1005670, regarding apertium-kaz-tat: FTBFS: ERROR: Transducer contains epsilon transition to a final state. Aborting. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1005670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-kaz-tat Version: 0.2.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/apertium-kaz-0.1.0' > /bin/mkdir -p .deps > /usr/bin/cg-comp apertium-kaz.kaz.rlx kaz.rlx.bin > apertium-validate-modes modes.xml > touch .deps/.d > cat apertium-kaz.kaz.lexc | grep -v -e 'Dir/RL' > .deps/kaz.LR.lexc > cat apertium-kaz.kaz.lexc | grep -v -e 'Err/Orth' > .deps/kaz.EL.lexc > apertium-gen-modes modes.xml > Sections: 3, Rules: 143, Sets: 198, Tags: 228 > 1 rules cannot be skipped by index. > hfst-twolc apertium-kaz.kaz.twol -o .deps/kaz.twol.hfst > hfst-twolc apertium-kaz.err.twol -o .deps/kaz.err.hfst > Reading input from apertium-kaz.kaz.twol. > Writing output to .deps/kaz.twol.hfst. > Reading input from apertium-kaz.err.twol. > Writing output to .deps/kaz.err.hfst. > cat apertium-kaz.kaz.lexc | grep -v -e 'Dir/LR' -e 'Err/Orth' > > .deps/kaz.RL.lexc > hfst-lexc --Werror .deps/kaz.LR.lexc -o .deps/kaz.LR.lexc.hfst -v > Reading alphabet. > Reading alphabet. > Reading sets.Reading sets. > > Reading rules and compiling their contexts and centers. > Reading rules and compiling their contexts and centers. > hfst-lexc: warning: Defaulting to OpenFst tropical type > Reading from .deps/kaz.LR.lexc, writing to .deps/kaz.LR.lexc.hfst > Parsing lexc file .deps/kaz.LR.lexc > Root...21 CASE-NONOM...7 CASE-ETC-NONOM...2 FULL-NOMINAL-INFLECTION-NONOM...2 > SUBST-NONOM...2 SQRD...5 NUM-DIGIT...38 LASTDIGIT...9 LASTDIGIT-REST...9 > POWERS...2 LOOP...12 DIGITLEX...10 CLIT-EMPH...2 CLIT-QST-MA...1 CLIT-QST...1 > CLIT-MODEMO...2 CLIT-MODASS...3 CLIT-GHANA-ETC...6 CLIT-COP...2 > CLITICS-NO-COP...5 CLITICS-NO-COP-NO-QST...3 CLITICS-INCL-COP...2 > CASES-COMMON...5 CASES...4 ATTR-SUBST...6 GENERAL-POSSESSIVE-ETC...8 > CASES-ETC...2 POSSESSIVES...7 ABESSIVE-POSTPOSITION...1 LI-POSTPOSITION...1 > PLURAL...3 FULL-NOMINAL-INFLECTION...5 A1...9 A2...6 A3...2 A4...1 A6...3 > V-ADJ...2 V-PERS-S1-NO3PERSON...6 V-PERS-S1...3 V-PERS-S2...8 V-PERS-AOR...8 > V-PERS-IFI_EVID...3 VOL-ENDINGS...9 GER-CASE-NO_COPULA...4 GER-ATTR/SUBST...1 > GER-ABE-ETC...1 GER-GENERAL-POSSESSIVE-ETC...3 GER-CASE-ETC...2 > GER-POSSESSIVES...7 GER-INFL...5 V-FINITE-IRREGULAR_NEGATIVE...9 > V-FINITE-REGULAR_NEGATIVE...9 V-NONFINITE-IRREGULAR_NEGATIVE...21 > V-NONFINITE-REGULAR_NEGATIVE...25 V-COMMON...7 V-DER...1 V-TV-NOPASS...2 > V-TV-PASS...1 V-TV...3 V-IV...2 Vinfl-AUX-IMPF...2 Vinfl-AUX-IMPF-NEG...2 > Vinfl-AUX...1 Copula...6 PRON-P12SG-CASES...12 PRON-P3SG-CASES...13 > PRON-PERS-INFL...1 PRON-PERS...15 PRON-DEM-INFL...13 PRON-DEM-BUL...29 > PRON-DEM-MINA...13 PRON-DEM-ALGI...9 PRON-DEM-MINAU...12 PRON-DEM-ANA...13 > DemonstrativePronouns...21 PRON-ITG-INFL...1 PRON-ITG-QAYSI-CASES...8 > PRON-ITG-QAYSI...2 PRON-ITG-QANSHA...1 PRON-ITG-QANDAY...5 > InterrogativePronouns...7 PRON-QNT-POSS...1 PRON-QNT...1 PRON-IND...1 > PRON-IND-PL...1 PRNNEG...2 PRON-RECIP...1 PRON-REF-ADV...2 PRON-REF...8 > DET-DEM...1 DET-QNT...1 DET-IND...1 DET-ITG...1 DET-NEG...1 DET-REF...1 > N1-ABBR...4 N1...2 N1-Ә...3 N-COMPOUND-PX-COMMON...2 N-COMPOUND-PX...2 > N-COMPOUND-PX-PL...1 N3...2 N5...1 N6...2 N-INFL-NKI...3 ADV-LANG...2 > NP-COMMON...1 NP-TOP-RUS...2 NP-TOP...2 NP-TOP-ASSR...3 NP-TOP-COMPOUND...2 > NP-TOP-ABBR...4 NP-ANT-M...2 NP-ANT-F...2 NP-COG-M...2 NP-COG-MF...2 > NP-COG-OBIN-FEM...2 NP-COG-OB...5 NP-COG-IN...3 NP-PAT-VICH...2 NP-ORG...3 > NP-ORG-LAT...4 NP-ORG-COMPOUND...1 NP-ORG-ABBR...4 NP-AL...1 NP-AL-ABBR...4 > NUM-COMMON...2 NUM...3 NUM-TWENTY...3 NUM-ITG...3 NUM-COLL...2 NUM-ROMAN...1 > LTR...1 POST...1 POSTADV...1 KI...2 ADV...1 ADV-WITH-KI...3 ADV-WITH-KI-I...2 > ADV-ITG...1 CC...1 CS...1 CA...1 QST..
Processed: [bts-link] source package src:blueprint-compiler
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:blueprint-compiler > # 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 #1084500 (http://bugs.debian.org/1084500) > # Bug title: blueprint-compiler: FTBFS: FAIL: test_samples > (tests.test_samples.TestSamples.test_samples) [deprecations] > # * https://gitlab.gnome.org/jwestman/blueprint-compiler/-/issues/178 > # * remote status changed: opened -> closed > # * closed upstream > tags 1084500 + fixed-upstream Bug #1084500 [src:blueprint-compiler] blueprint-compiler: FTBFS: FAIL: test_samples (tests.test_samples.TestSamples.test_samples) [deprecations] Added tag(s) fixed-upstream. > usertags 1084500 - status-opened Usertags were: status-opened. There are now no usertags set. > usertags 1084500 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1084500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997203: marked as done (gigedit: FTBFS: ../compat.h:194:21: error: ‘const Pango::Alignment Pango::ALIGN_LEFT’ redeclared as different kind of entity)
Your message dated Mon, 04 Nov 2024 18:20:51 + with message-id and subject line Bug#1079966: Removed package(s) from unstable has caused the Debian Bug report #997203, regarding gigedit: FTBFS: ../compat.h:194:21: error: ‘const Pango::Alignment Pango::ALIGN_LEFT’ redeclared as different kind of entity 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.) -- 997203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gigedit Version: 1.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../../.. -pthread -I/usr/include/gtkmm-3.0 > -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 > -I/usr/lib/x86_64-linux-gnu/atkmm-1.6/include > -I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 > -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 > -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pangomm-1.4 > -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 > -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 > -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 > -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi > -I/usr/include/harfbuzz -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 > -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o yellow_dot.lo > yellow_dot.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -pthread > -I/usr/include/gtkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include > -I/usr/include/atkmm-1.6 -I/usr/lib/x86_64-linux-gnu/atkmm-1.6/include > -I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 > -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 > -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pangomm-1.4 > -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 > -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 > -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 > -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/pango-1.0 > -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi > -I/usr/include/harfbuzz -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 > -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c yellow_dot.c -o > yellow_dot.o > In file included from builtinpix.cpp:2: > ../compat.h:194:21: error: ‘const Pango::Alignment Pango::ALIGN_LEFT’ > redeclared as different kind of entity > 194 | const Alignment ALIGN_LEFT = Alignment::LEFT; > | ^~ > In file included from /usr/include/gtkmm-3.0/gtkmm/widget.h:32, > from /usr/include/gtkmm-3.0/gtkmm/container.h:28, > from /usr/include/gtkmm-3.0/gtkmm/box.h:27, >
Bug#964195: marked as done (CVE-2020-9497 CVE-2020-9498)
Your message dated Mon, 04 Nov 2024 18:20:19 + with message-id and subject line Bug#1079964: Removed package(s) from unstable has caused the Debian Bug report #964195, regarding CVE-2020-9497 CVE-2020-9498 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.) -- 964195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: guacamole-client Severity: grave Tags: security Please see https://www.openwall.com/lists/oss-security/2020/07/02/3 https://www.openwall.com/lists/oss-security/2020/07/02/2 Cheers, Moritz --- End Message --- --- Begin Message --- Version: 1.3.0-1.3+rm Dear submitter, as the package guacamole-server has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1079964 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
