Bug#1057401: marked as done (mwparserfromhell ftbfs with Python 3.12 (but falls back to Python code))
Your message dated Sun, 17 Dec 2023 07:04:13 + with message-id and subject line Bug#1057401: fixed in mwparserfromhell 0.6.5-2 has caused the Debian Bug report #1057401, regarding mwparserfromhell ftbfs with Python 3.12 (but falls back to Python 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.) -- 1057401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mwparserfromhell Version: 0.6.5-1 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 mwparserfromhell ftbfs with Python 3.12 (but falls back to Python code). the packaging probably should check if the extensions are really built. [...] x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12 -c src/mwparserfromhell/parser/ctokenizer/tokenizer.c -o build/temp.linux-x86_64-cpython-312/src/mwparserfromhell/parser/ctokenizer/tokenizer.o src/mwparserfromhell/parser/ctokenizer/tokenizer.c: In function ‘init_tokenizer_text’: src/mwparserfromhell/parser/ctokenizer/tokenizer.c:91:18: error: ‘PyUnicode_WCHAR_KIND’ undeclared (first use in this function); did you mean ‘PyUnicode_4BYTE_KIND’? 91 | text->kind = PyUnicode_WCHAR_KIND; | ^~~~ | PyUnicode_4BYTE_KIND src/mwparserfromhell/parser/ctokenizer/tokenizer.c:91:18: note: each undeclared identifier is reported only once for each function it appears in error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 Falling back to pure Python mode. [...] --- End Message --- --- Begin Message --- Source: mwparserfromhell Source-Version: 0.6.5-2 Done: Kunal Mehta We believe that the bug you reported is fixed in the latest version of mwparserfromhell, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kunal Mehta (supplier of updated mwparserfromhell 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, 20 Nov 2023 13:11:01 -0500 Source: mwparserfromhell Architecture: source Version: 0.6.5-2 Distribution: unstable Urgency: medium Maintainer: Kunal Mehta Changed-By: Kunal Mehta Closes: 1055565 1057401 Changes: mwparserfromhell (0.6.5-2) unstable; urgency=medium . * Cherry-pick upstream patch for Python 3.12 support (Closes: #1055565, #1057401) Checksums-Sha1: 83e7cf8c9d0551f39439595cea00dcc5aa493382 2100 mwparserfromhell_0.6.5-2.dsc d6a8906198971611fa94b8b7672e877cbe42df53 3388 mwparserfromhell_0.6.5-2.debian.tar.xz 9c05304928463a5e62bd7a50ad819bb61e8470ad 7661 mwparserfromhell_0.6.5-2_amd64.buildinfo Checksums-Sha256: 6aef5208f7334e3ffe41b3ab76a7422204f3463747c9ee095827c55a2aaa38e9 2100 mwparserfromhell_0.6.5-2.dsc 6b1ce422ddd8d4a2f71f269aa14570f58c211fbdf92b981d4c2f4415d4d6cb91 3388 mwparserfromhell_0.6.5-2.debian.tar.xz 80144f6a70c1266a9a755938d01a80ef2e14f9513c92b842c308ce0637acb445 7661 mwparserfromhell_0.6.5-2_amd64.buildinfo Files: f044ecd39fa208316de90d8f40c1f4f7 2100 python optional mwparserfromhell_0.6.5-2.dsc 63c6f8e3a30fb82a6dfcf79d6a78125a 3388 python optional mwparserfromhell_0.6.5-2.debian.tar.xz 886d7480fabfa99205d3a06b905a57a7 7661 python optional mwparserfromhell_0.6.5-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAmV+mgUTHGxlZ29rdG1A cmlzZXVwLm5ldAAKCRDxBfgQGwUmmz6hEADBgz9yIGnKebP2bfgoe6ZyBpAGlcnl RjULyExZT4UORx/xzX09vWR4ItWOOVTMrkLLTyTuEtwdv+0XyadMRq7I+YUg369X TcEYyB5VNu+zy3Jc4BChxB9X+G3Q5MuJTIz/9iTi6tFKbrsh3WmNUMICP5WSfceG wx1AkHGKork8Hby8vqPZzgqkfrSuQhiL+Z5UN2PCfEDkuEi4OdamVysvInZLBTBE QwvgExvD0nV5KqUwIZMYt0wEoD/bTw2YSNC9mkjzKGzWw8DZjnC62Y4mvMXMIaPU Qeq8YuDr+n7nnINyaSG5ys6xVZ3JR9Z76c3rFkzWUT0oYPhpMIy5Tn85jCm0QtwB
Processed: reassign 1057546 to calamares-extensions
Processing commands for cont...@bugs.debian.org: > reassign 1057546 calamares-extensions Bug #1057546 [calamares] calamares-extensions: FTBFS: Unknown CMake command "set_package_properties". Bug reassigned from package 'calamares' to 'calamares-extensions'. No longer marked as found in versions calamares/3.3.0~alpha6-2. Ignoring request to alter fixed versions of bug #1057546 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1057546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031402: marked as done (mutt-wizard: ships and generates invalid neomutt rc files)
Your message dated Sun, 17 Dec 2023 04:06:11 + with message-id and subject line Bug#1031402: fixed in mutt-wizard 3.3.1-4 has caused the Debian Bug report #1031402, regarding mutt-wizard: ships and generates invalid neomutt rc files 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.) -- 1031402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mutt-wizard Version: 3.3.1-2 Severity: important I've just discovered mutt-wizard and thought I'd give it a go. I have the neomutt version as in the archive frozen for Bookworm (version string in the boilerplate below as usual). From what I can see, this basically does not work at all in Debian, at least in conjunction with Bookworm's version of neomutt. ;mw -u jon -a redac...@example.org Give your email server's IMAP address (excluding the port number): redacted Give your email server's SMTP address (excluding the port number): redacted Enter password for redac...@example.org: Retype password for redac...@example.org: [master b270548] Add given password for redac...@example.org to store. 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 redac...@example.org.gpg sed: can't read /home/jon/.config/mutt/muttrc: No such file or directory redac...@example.org (account #1) added successfully. After execution, the file sed was complaining about (/home/jon/.config/mutt/muttrc) exists and is a regular file. Tracing the mw script reveals this to be the sed on line 227, within the function "getboxes", for what it's worth. Moving on… ;neomutt -F ~/.config/mutt/muttrc Error in /usr/share/mutt-wizard/mutt-wizard.muttrc, line 11: Option smtp_authenticators: gssapi is not a valid authenticator Error in /home/jon/.config/mutt/muttrc, line 2: source: file /usr/share/mutt-wizard/mutt-wizard.muttrc could not be sourced Error in /home/jon/.config/mutt/accounts/Redacted.muttrc, line 12: .: unknown command Error in /home/jon/.config/mutt/muttrc, line 3: source: file /home/jon/.config/mutt/accounts/Redacted.muttrc could not be sourced source: errors in /home/jon/.config/mutt/muttrc Press any key to continue... The first error is clear enough: this line in the package's etc file specifies an authenticator that is not supplied in the neovim package (anymore? There's a report against the neomutt package requesting it at #1026356) line 12 in my Redacted.muttrc looks like this \. /usr/share/mutt-wizard/switch.muttrc Perhaps this is a consequence of the failing sed earlier? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mutt-wizard depends on: ii curl 7.87.0-2 ii isync 1.4.4-5 ii msmtp 1.8.23-1 ii neomutt20220429+dfsg1-4.1 ii pass 1.7.4-6 ii xdg-utils 1.1.3-4.1 Versions of packages mutt-wizard recommends: ii abook0.6.1-2+b1 ii cron 3.0pl1-156 ii lynx 2.9.0dev.12-1 ii notmuch 0.37-1+b1 ii urlview 0.9-23.1 Versions of packages mutt-wizard suggests: pn links2 pn mpop ii mpv 0.35.1-1 ii w3m 0.5.3+git20230121-2 pn zathura -- no debconf information --- End Message --- --- Begin Message --- Source: mutt-wizard Source-Version: 3.3.1-4 Done: Braulio Henrique Marques Souto We believe that the bug you reported is fixed in the latest version of mutt-wizard, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Braulio Henrique Marques Souto (supplier of updated mutt-wizard package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Dec 2023 15:20:47 -0300 Source: mutt-wizard
Processed: Re: linphone FTBFS with zxing-cpp 2.2.1
Processing control commands: > tags -1 +patch +sid +experimental Bug #1058849 [src:linphone] linphone FTBFS with zxing-cpp 2.2.1 Added tag(s) patch. Bug #1058849 [src:linphone] linphone FTBFS with zxing-cpp 2.2.1 Added tag(s) sid. Bug #1058849 [src:linphone] linphone FTBFS with zxing-cpp 2.2.1 Added tag(s) experimental. -- 1058849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058849: linphone FTBFS with zxing-cpp 2.2.1
Control: tags -1 +patch +sid +experimental On Sun, 17 Dec 2023 02:09:02 +0200 Adrian Bunk wrote: > Source: linphone > Version: 5.2.0-4 > Severity: serious > Tags: ftbfs > Forwarded: > https://gitlab.linphone.org/BC/public/liblinphone/-/commit/5cff6f87a82cea59041869a6d1ed391921ab589d > > https://buildd.debian.org/status/logs.php?pkg=linphone=5.2.0-4%2Bb1 > > ... > In file included from /usr/include/ZXing/Flags.h:8, > from /usr/include/ZXing/BarcodeFormat.h:9, > from /<>/src/factory/factory.cpp:25: > /usr/include/ZXing/BitHacks.h:37:55: error: ‘is_integral_v’ is not a member > of ‘std’; did you mean ‘is_integral’? > 37 | templatestd::enable_if_t>> > | ^ > | is_integral > ... Looks like the reason is that zxing-cpp headers require C++17 features (std::is_integral_v), while current linphone is built with C++14 by default [2]. [2] https://sources.debian.org/src/linphone/5.2.0-4/CMakeLists.txt/#L96 With the current condition, the simple solution would be patching linphone to be built using C++17 standard (see patch below). My local rebuilds did not reveal regressions after switching to C++17 from C++14, and in the meanwhile linphone upstream has already made such switch in the trunk code [3]. [3] https://gitlab.linphone.org/BC/public/liblinphone/-/commit/5cff6f87a82cea59041869a6d1ed391921ab589d +diff --git a/CMakeLists.txt b/CMakeLists.txt +index b3060af..c846dc7 100644 +--- a/CMakeLists.txt b/CMakeLists.txt +@@ -93,7 +93,7 @@ cmake_dependent_option(ENABLE_QRCODE "Enable QRCode support" YES "ENABLE_VIDEO" + # * DISABLE_BC_PACKAGE_SEARCH: skip find_package() for every BC package (bctoolbox, ortp, etc.) + # * DISABLE_SOCI_PACKAGE_SEARCH: skip find_package() for Soci. + +-set(CMAKE_CXX_STANDARD 14) ++set(CMAKE_CXX_STANDARD 17) + set(CMAKE_CXX_EXTENSIONS NO) + + if(NOT CMAKE_BUILD_TYPE) Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1058849: linphone FTBFS with zxing-cpp 2.2.1
Source: linphone Version: 5.2.0-4 Severity: serious Tags: ftbfs Forwarded: https://gitlab.linphone.org/BC/public/liblinphone/-/commit/5cff6f87a82cea59041869a6d1ed391921ab589d https://buildd.debian.org/status/logs.php?pkg=linphone=5.2.0-4%2Bb1 ... In file included from /usr/include/ZXing/Flags.h:8, from /usr/include/ZXing/BarcodeFormat.h:9, from /<>/src/factory/factory.cpp:25: /usr/include/ZXing/BitHacks.h:37:55: error: ‘is_integral_v’ is not a member of ‘std’; did you mean ‘is_integral’? 37 | template>> | ^ | is_integral ...
Bug#999984: prads: depends on obsolete pcre3 library
Control: tags -1 + patch
Please find a patch attached.
I could not observe problems while testing it.
>From 014406e858e3e2af471bfb2b392ea693674120e3 Mon Sep 17 00:00:00 2001
From: Yavor Doganov
Date: Sun, 17 Dec 2023 00:53:23 +0200
Subject: [PATCH] Port to PCRE2 (#84)
---
debian/changelog | 8 +
debian/control| 5 +-
debian/patches/debian-changes | 359 ++
src/Makefile | 2 +-
src/prads.c | 5 +-
src/prads.h | 6 +-
src/servicefp/servicefp.c | 31 ++-
src/servicefp/servicefp.h | 4 +-
src/servicefp/tcpc.c | 18 +-
src/servicefp/tcps.c | 18 +-
src/servicefp/udps.c | 18 +-
11 files changed, 430 insertions(+), 44 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 445f0e0..9735891 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+prads (0.3.3-8) UNRELEASED; urgency=medium
+
+ * Port to PCRE2 (Closes: #84).
+ * debian/control (Depends): Drop libpcre3.
+(Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+
+ -- Yavor Doganov Sun, 17 Dec 2023 00:51:17 +0200
+
prads (0.3.3-7) unstable; urgency=medium
* Remove 1 obsolete maintscript entry.
diff --git a/debian/control b/debian/control
index 5895778..a2fb71f 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Stig Sandbeck Mathisen
Build-Depends:
debhelper-compat (= 13),
libpcap-dev,
- libpcre3-dev,
+ libpcre2-dev,
python3-docutils,
Standards-Version: 4.6.0
Homepage: https://gamelinux.github.com/prads/
@@ -15,8 +15,7 @@ Vcs-Browser: https://salsa.debian.org/debian/prads
Package: prads
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, libpcap0.8, libpcre3,
- adduser
+Depends: ${shlibs:Depends}, ${misc:Depends}, libpcap0.8, adduser
Description: Passive Real-time Asset Detection System
PRADS is a Passive Real-time Asset Detection System.
.
diff --git a/debian/patches/debian-changes b/debian/patches/debian-changes
index 89c1c18..848acc3 100644
--- a/debian/patches/debian-changes
+++ b/debian/patches/debian-changes
@@ -58,6 +58,15 @@ A single combined diff, containing all the changes, follows.
# for finding static libraries
LIBDIR=/usr/lib/x86_64-linux-gnu
+@@ -28,7 +28,7 @@ ifeq (${STATIC},)
+ ifeq (${TCMALLOC},y)
+ LDFLAGS+=-ltcmalloc
+ endif
+-LDFLAGS+=-lpcap -lpcre -lresolv
++LDFLAGS+=-lpcap -lpcre2-8 -lresolv
+ CFLAGS+=-DCONFDIR='"${CONFDIR}/"'
+ else
+ ifeq (${TCMALLOC},y)
--- prads-0.3.3.orig/src/output-plugins/log.h
+++ prads-0.3.3/src/output-plugins/log.h
@@ -19,8 +19,8 @@ typedef struct _output_plugin {
@@ -82,3 +91,353 @@ A single combined diff, containing all the changes, follows.
/* --
* FUNCTION : init_identification
+@@ -135,8 +135,8 @@ int parse_raw_signature(bstring line, in
+ signature *sig, *head;
+ sig = head = NULL;
+ bstring pcre_string = NULL;
+-const char *err = NULL; /* PCRE */
+-int erroffset; /* PCRE */
++int err;/* PCRE */
++PCRE2_SIZE erroffset; /* PCRE */
+ int ret = 0;
+ int i;
+
+@@ -207,18 +207,17 @@ int parse_raw_signature(bstring line, in
+ */
+ if (pcre_string != NULL) {
+ if ((sig->regex =
+- pcre_compile((char *)bdata(pcre_string), 0, ,
+- , NULL)) == NULL) {
++ pcre2_compile((PCRE2_SPTR)bdata(pcre_string),
++ PCRE2_ZERO_TERMINATED, 0, ,
++ , NULL)) == NULL) {
++PCRE2_UCHAR buf[120];
++
++pcre2_get_error_message(err, buf, sizeof(buf));
+ printf("Unable to compile signature: %s at line %d (%s)",
+- err, lineno, bdata(line));
++ buf, lineno, bdata(line));
+ ret = -1;
+ }
+ }
+-if (ret != -1) {
+-sig->study = pcre_study(sig->regex, 0, );
+-if (err != NULL)
+-printf("Unable to study signature: %s", err);
+-}
+
+ /*
+ * Add signature to 'signature_list' data structure.
+@@ -266,8 +265,7 @@ void free_signature_list (signature *hea
+ bdestroy(head->title.app);
+ bdestroy(head->title.ver);
+ bdestroy(head->title.misc);
+-if (head->regex != NULL) free(head->regex);
+-if (head->study != NULL) free(head->study);
++pcre2_code_free(head->regex);
+ tmp = head->next;
+ free(head);
+ head = NULL;
+@@ -297,11 +295,11 @@ void del_signature_lists()
+ * INPUT: 0 - Signature Pointer
+ * : 1 - payload
+ * : 2 - ovector
+- * : 3 - rc (return from pcre_exec)
++ * :
Processed: Re: Bug#999984: prads: depends on obsolete pcre3 library
Processing control commands: > tags -1 + patch Bug #84 [src:prads] prads: depends on obsolete pcre3 library Added tag(s) patch. -- 84: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057169: pdftk-java: FTBFS with bouncycastle 1.77
Dear pdftk-java maintainers,
Please find attached a patch to fix this FTBFS due to bouncycastle update.
Because the package gtg depends on pdftk-java, I could provide an NMU. Just let
me know.
Best,
François
Description: Fix FTBFS with new version of bouncycastle (#1057169)
Author: Francois Mazen
Forwarded: https://gitlab.com/pdftk-java/pdftk/-/issues/155
--- a/java/com/gitlab/pdftk_java/com/lowagie/text/pdf/PdfPKCS7.java
+++ b/java/com/gitlab/pdftk_java/com/lowagie/text/pdf/PdfPKCS7.java
@@ -225,7 +225,7 @@
ASN1ObjectIdentifier objId = (ASN1ObjectIdentifier)signedData.getObjectAt(0);
if (!objId.getId().equals(ID_PKCS7_SIGNED_DATA))
throw new SecurityException("Not a valid PKCS#7 object - not signed data");
-ASN1Sequence content = (ASN1Sequence)((DERTaggedObject)signedData.getObjectAt(1)).getObject();
+ASN1Sequence content = (ASN1Sequence)((DERTaggedObject)signedData.getObjectAt(1)).getBaseObject();
// the positions that we care are:
// 0 - version
// 1 - digestAlgorithms
@@ -258,7 +258,7 @@
// the possible ID_PKCS7_DATA
ASN1Sequence rsaData = (ASN1Sequence)content.getObjectAt(2);
if (rsaData.size() > 1) {
-DEROctetString rsaDataContent = (DEROctetString)((DERTaggedObject)rsaData.getObjectAt(1)).getObject();
+DEROctetString rsaDataContent = (DEROctetString)((DERTaggedObject)rsaData.getObjectAt(1)).getBaseObject();
RSAdata = rsaDataContent.getOctets();
}
@@ -294,7 +294,7 @@
next = 3;
if (signerInfo.getObjectAt(next) instanceof ASN1TaggedObject) {
ASN1TaggedObject tagsig = (ASN1TaggedObject)signerInfo.getObjectAt(next);
-ASN1Sequence sseq = (ASN1Sequence)tagsig.getObject();
+ASN1Sequence sseq = (ASN1Sequence)tagsig.getBaseObject();
ByteArrayOutputStream bOut = new ByteArrayOutputStream();
ASN1OutputStream dout = ASN1OutputStream.create(bOut);
try {
signature.asc
Description: This is a digitally signed message part
Processed: tagging 1058814, tagging 1058813, tagging 1057951, tagging 1057968, tagging 1054849
Processing commands for cont...@bugs.debian.org:
> tags 1058814 + sid trixie
Bug #1058814 [src:flint-arb] flint-arb: FTBFS:
/<>/fmpz_extras.h:208:1: error: static declaration of
‘fmpz_ui_pow_ui’ follows non-static declaration
Added tag(s) sid and trixie.
> tags 1058813 + sid trixie
Bug #1058813 [src:antic] antic: FTBFS: error: unknown type name ‘n_primes_t’
Added tag(s) trixie and sid.
> tags 1057951 + sid trixie
Bug #1057951 {Done: Andrius Merkys } [src:promod3] promod3:
FTBFS: tests may fail to run in parallel
Ignoring request to alter tags of bug #1057951 to the same tags previously set
> tags 1057968 + sid trixie
Bug #1057968 [python3-flake8] python3-flake8: cannot import name
'missing_whitespace_around_operator' from 'pycodestyle'
Added tag(s) trixie and sid.
> tags 1054849 + sid trixie
Bug #1054849 {Done: Scott Talbert }
[src:haskell-clash-prelude] haskell-clash-prelude: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
Ignoring request to alter tags of bug #1054849 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1054849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054849
1057951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057951
1057968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057968
1058813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058813
1058814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 1058822 to llvm-toolchain-14: do not release with trixie
Processing commands for cont...@bugs.debian.org: > retitle 1058822 llvm-toolchain-14: do not release with trixie Bug #1058822 [src:llvm-toolchain-14] llvm-toolchain-16: do not release with trixie Changed Bug title to 'llvm-toolchain-14: do not release with trixie' from 'llvm-toolchain-16: do not release with trixie'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058822: llvm-toolchain-16: do not release with trixie
Source: llvm-toolchain-14 Version: 1:14.0.6-16 Severity: serious X-Debbugs-Cc: sramac...@debian.org See #1050069. Cheers -- Sebastian Ramacher
Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...
* Rafael Laboissière [2023-12-15 21:44]: * Santiago Vila [2023-12-15 18:15]: The thing I don't understand here is why this problem in octave-vibes was diagnosed as an "unwritable $HOME" in the first place. This is what I concluded after running some tests, but I do not remember the details. I will try to replicate it. I did the investigation again, using pbuilder. Here is what I found: – In my case, pbuilder sets HOME=/nonexistent/ and debhelper (compat level = 13) keeps that setting. Hence, the package FTBFS. – If I use "export HOME = /tmp", for instance, in debian/rules, then the build succeeds. Best, Rafael Laboissière
Bug#1058817: picom: depends on obsolete pcre3 library
Source: picom Version: 10.2-1 Severity: serious Tags: sid trixie fixed-upstream User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, During the mass bug filing for the pcre3->pcre2 transition [*], this package was left out somehow. I am filing this (edited copy) post-factum. Fortunately this bug has been fixed upstream. [*] https://release.debian.org/transitions/html/pcre3-to-pcre2.html Your package still depends on the old, obsolete PCRE3 libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, we would like to remove the pcre3 libraries from Debian. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html
Bug#1058312: marked as done (python-pytest-toolbox: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Sat, 16 Dec 2023 21:04:55 +
with message-id
and subject line Bug#1058312: fixed in python-pytest-toolbox 0.4-4
has caused the Debian Bug report #1058312,
regarding python-pytest-toolbox: 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.)
--
1058312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pytest-toolbox
Version: 0.4-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config
> running config
> I: pybuild base:310: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.12_pytest-toolbox/build/pytest_toolbox
> copying pytest_toolbox/__init__.py ->
> /<>/.pybuild/cpython3_3.12_pytest-toolbox/build/pytest_toolbox
> copying pytest_toolbox/version.py ->
> /<>/.pybuild/cpython3_3.12_pytest-toolbox/build/pytest_toolbox
> copying pytest_toolbox/main.py ->
> /<>/.pybuild/cpython3_3.12_pytest-toolbox/build/pytest_toolbox
> copying pytest_toolbox/comparison.py ->
> /<>/.pybuild/cpython3_3.12_pytest-toolbox/build/pytest_toolbox
> running egg_info
> creating pytest_toolbox.egg-info
> writing pytest_toolbox.egg-info/PKG-INFO
> writing dependency_links to pytest_toolbox.egg-info/dependency_links.txt
> writing entry points to pytest_toolbox.egg-info/entry_points.txt
> writing requirements to pytest_toolbox.egg-info/requires.txt
> writing top-level names to pytest_toolbox.egg-info/top_level.txt
> writing manifest file 'pytest_toolbox.egg-info/SOURCES.txt'
> reading manifest file 'pytest_toolbox.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'pytest_toolbox.egg-info/SOURCES.txt'
> I: pybuild base:310: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.11_pytest-toolbox/build/pytest_toolbox
> copying pytest_toolbox/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pytest-toolbox/build/pytest_toolbox
> copying pytest_toolbox/version.py ->
> /<>/.pybuild/cpython3_3.11_pytest-toolbox/build/pytest_toolbox
> copying pytest_toolbox/main.py ->
> /<>/.pybuild/cpython3_3.11_pytest-toolbox/build/pytest_toolbox
> copying pytest_toolbox/comparison.py ->
> /<>/.pybuild/cpython3_3.11_pytest-toolbox/build/pytest_toolbox
> running egg_info
> writing pytest_toolbox.egg-info/PKG-INFO
> writing dependency_links to pytest_toolbox.egg-info/dependency_links.txt
> writing entry points to pytest_toolbox.egg-info/entry_points.txt
> writing requirements to pytest_toolbox.egg-info/requires.txt
> writing top-level names to pytest_toolbox.egg-info/top_level.txt
> reading manifest file 'pytest_toolbox.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'pytest_toolbox.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:314: cp -r /<>/tests
> /<>/.pybuild/cpython3_3.12_pytest-toolbox/build
> I: pybuild base:310: cd
> /<>/.pybuild/cpython3_3.12_pytest-toolbox/build; python3.12 -m
> pytest tests
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> configfile: setup.cfg
> plugins: timeout-2.2.0
> timeout: 10.0s
> timeout method: signal
> timeout func_only: False
> collected 20 items
>
> tests/test_comparison.py .. [
> 50%]
> tests/test_methods.py ..
> [100%]
>
> === FAILURES
> ===
> test_close_to_now_true
>
>
> def test_close_to_now_true():
> > c2n = CloseToNow()
>
> tests/test_comparison.py:10:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self = <[AttributeError("'CloseToNow' object has no
Bug#1000001: pgpcre: depends on obsolete pcre3 library
Control: tags -1 + patch
Please find attached a patch.
I have not tested the package except the build-time tests. Initially,
I tried to follow upstream's desire for custom memory management, so I
created a pcre2_general_context in _PG_init (changing the
pgpcre_malloc/pgpcre_free prototypes as is required). Unfortunately,
the test program crashes when pfree is invoked in
src:pcre2:src/pcre2_match.c:6846. It looks like palloc/pfree are not
suitable as PCRE2 custom memory management functions as they use memory
context like in PCRE2 itself. Or I am misunderstanding something.
>From f46d9ca762751a3c856369d781cf69554c31e001 Mon Sep 17 00:00:00 2001
From: Yavor Doganov
Date: Sat, 16 Dec 2023 22:29:20 +0200
Subject: [PATCH] Port to PCRE2 (#101).
---
debian/changelog | 6 +
debian/control | 2 +-
debian/control.in | 2 +-
debian/patches/pcre2.patch | 268 +
debian/patches/series | 1 +
5 files changed, 277 insertions(+), 2 deletions(-)
create mode 100644 debian/patches/pcre2.patch
create mode 100644 debian/patches/series
diff --git a/debian/changelog b/debian/changelog
index 1d0f545..cba8632 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pgpcre (0.20190509-7) UNRELEASED; urgency=medium
+
+ * Port to PCRE2 (Closes: #101).
+
+ -- Yavor Doganov Sat, 16 Dec 2023 22:27:38 +0200
+
pgpcre (0.20190509-6) unstable; urgency=medium
* Upload for PostgreSQL 16.
diff --git a/debian/control b/debian/control
index 1073417..bb8c141 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Uploaders:
Christoph Berg ,
Build-Depends:
debhelper-compat (= 13),
- libpcre3-dev,
+ libpcre2-dev,
pkg-config,
postgresql-all (>= 217~),
Standards-Version: 4.6.2
diff --git a/debian/control.in b/debian/control.in
index 5fe2318..0f01b24 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -6,7 +6,7 @@ Uploaders:
Christoph Berg ,
Build-Depends:
debhelper-compat (= 13),
- libpcre3-dev,
+ libpcre2-dev,
pkg-config,
postgresql-all (>= 217~),
Standards-Version: 4.6.2
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
new file mode 100644
index 000..f138fb1
--- /dev/null
+++ b/debian/patches/pcre2.patch
@@ -0,0 +1,268 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/101
+Author: Yavor Doganov
+Forwarded: no
+Last-Update: 2023-12-16
+---
+
+--- pgpcre-0.20190509.orig/Makefile
pgpcre-0.20190509/Makefile
+@@ -6,12 +6,12 @@
+ OBJS = pgpcre.o
+ DATA = pgpcre--0.sql pgpcre--1.sql pgpcre--0--1.sql
+
+-ifeq (no,$(shell $(PKG_CONFIG) libpcre || echo no))
++ifeq (no,$(shell $(PKG_CONFIG) libpcre2-8 || echo no))
+ $(warning libpcre not registed with pkg-config, build might fail)
+ endif
+
+-PG_CPPFLAGS += $(shell $(PKG_CONFIG) --cflags-only-I libpcre)
+-SHLIB_LINK += $(shell $(PKG_CONFIG) --libs libpcre)
++PG_CPPFLAGS += $(shell $(PKG_CONFIG) --cflags-only-I libpcre2-8)
++SHLIB_LINK += $(shell $(PKG_CONFIG) --libs libpcre2-8)
+
+ REGRESS = init test unicode
+ REGRESS_OPTS = --inputdir=test
+--- pgpcre-0.20190509.orig/pgpcre.c
pgpcre-0.20190509/pgpcre.c
+@@ -5,7 +5,8 @@
+ #include
+ #include
+
+-#include
++#define PCRE2_CODE_UNIT_WIDTH 8
++#include
+
+ PG_MODULE_MAGIC;
+
+@@ -57,19 +58,19 @@
+ pcre_in(PG_FUNCTION_ARGS)
+ {
+ char *input_string = PG_GETARG_CSTRING(0);
+- pcre *pc;
+- const char *err;
+- int erroffset;
+- size_t in_strlen;
+- int rc, total_len, pcsize;
++ pcre2_code *pc;
++ int err;
++ PCRE2_SIZE erroffset;
++ size_t in_strlen, pcsize;
++ int rc, total_len;
+ pgpcre *result;
+
+ in_strlen = strlen(input_string);
+
+ if (GetDatabaseEncoding() == PG_UTF8)
+- pc = pcre_compile(input_string, PCRE_UTF8 | PCRE_UCP, ,
, NULL);
++ pc = pcre2_compile((PCRE2_SPTR) input_string, in_strlen,
PCRE2_UTF | PCRE2_UCP, , , NULL);
+ else if (GetDatabaseEncoding() == PG_SQL_ASCII)
+- pc = pcre_compile(input_string, 0, , , NULL);
++ pc = pcre2_compile((PCRE2_SPTR) input_string, in_strlen, 0,
, , NULL);
+ else
+ {
+ char *utf8string;
+@@ -78,22 +79,27 @@
+
in_strlen,
+
GetDatabaseEncoding(),
+
PG_UTF8);
+- pc = pcre_compile(utf8string, PCRE_UTF8 | PCRE_UCP, ,
, NULL);
++ pc = pcre2_compile((PCRE2_SPTR) utf8string, strlen(utf8string),
PCRE2_UTF | PCRE2_UCP, , , NULL);
+ if (utf8string != input_string)
+
Processed: Re: Bug#1000001: pgpcre: depends on obsolete pcre3 library
Processing control commands: > tags -1 + patch Bug #101 [src:pgpcre] pgpcre: depends on obsolete pcre3 library Added tag(s) patch. -- 101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058815: calcium: FTBFS: /usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration
Source: calcium
Version: 0.4.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
gcc -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-I/<> -I/usr/local/include -I/usr/local/include -I/usr/include
-I/usr/local/include -I/usr/local/include -c write.c -o
../build/calcium/write.lo -MMD -MP -MF "../build/calcium/write.d" -MT
"../build/calcium/write.d" -MT "../build/calcium/write.lo"
In file included from /usr/include/fmpr.h:30,
from /usr/include/arf.h:27,
from /usr/include/acb.h:22,
from /<>/calcium.h:24,
from write.c:13:
/usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’
follows non-static declaration
208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
| ^~
In file included from /<>/calcium.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’
with type ‘void(fmpz *, mp_limb_t, mp_limb_t)’ {aka ‘void(long int *, long
unsigned int, long unsigned int)’}
422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
| ^~
/usr/include/fmpr.h: In function ‘fmpr_set_ui’:
/usr/include/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated. Use
'flint_ctz' instead.
360 | count_trailing_zeros(b, c);
| ^
/usr/include/fmpr.h: In function ‘fmpr_set_si’:
/usr/include/fmpr.h:375:11: error: 'count_trailing_zeros' is deprecated. Use
'flint_ctz' instead.
375 | count_trailing_zeros(b, c);
| ^
In file included from /usr/include/fmpr.h:30,
from /usr/include/arf.h:27,
from /usr/include/acb.h:22,
from /<>/calcium.h:24,
from version.c:12:
/usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’
follows non-static declaration
208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
| ^~
In file included from /<>/calcium.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’
with type ‘void(fmpz *, mp_limb_t, mp_limb_t)’ {aka ‘void(long int *, long
unsigned int, long unsigned int)’}
422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
| ^~
/usr/include/arf.h: In function ‘arf_init_set_ui’:
/usr/include/arf.h:435:11: error: 'count_leading_zeros' is deprecated. Use
'flint_clz' instead.
435 | count_leading_zeros(c, v);
| ^~~~
/usr/include/arf.h: In function ‘arf_set_ui’:
/usr/include/arf.h:467:11: error: 'count_leading_zeros' is deprecated. Use
'flint_clz' instead.
467 | count_leading_zeros(c, v);
| ^~~~
/usr/include/fmpr.h: In function ‘fmpr_set_ui’:
/usr/include/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated. Use
'flint_ctz' instead.
360 | count_trailing_zeros(b, c);
| ^
/usr/include/fmpr.h: In function ‘fmpr_set_si’:
/usr/include/fmpr.h:375:11: error: 'count_trailing_zeros' is deprecated. Use
'flint_ctz' instead.
375 | count_trailing_zeros(b, c);
| ^
/usr/include/arf.h: In function ‘arf_bits’:
/usr/include/arf.h:656:11: error: 'count_trailing_zeros' is deprecated. Use
'flint_ctz' instead.
656 | count_trailing_zeros(c, xp[0]);
| ^
In file included from /usr/include/fmpr.h:30,
from /usr/include/arf.h:27,
from /usr/include/acb.h:22,
from /<>/calcium.h:24,
from func_name.c:12:
/usr/include/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’
follows non-static declaration
208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
| ^~
In file included from /<>/calcium.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’
with type ‘void(fmpz *, mp_limb_t, mp_limb_t)’ {aka ‘void(long int *, long
unsigned int, long unsigned int)’}
422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
| ^~
/usr/include/fmpr.h: In function ‘fmpr_set_ui’:
/usr/include/arf.h: In function ‘arf_init_set_ui’:
/usr/include/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated. Use
'flint_ctz' instead.
360 | count_trailing_zeros(b, c);
| ^
Bug#1057545: marked as done (bosh: FTBFS: bosh.c:453:23: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’})
Your message dated Sat, 16 Dec 2023 20:34:43 +
with message-id
and subject line Bug#1057545: fixed in bosh 0.6-12
has caused the Debian Bug report #1057545,
regarding bosh: FTBFS: bosh.c:453:23: error: invalid use of incomplete typedef
‘WINDOW’ {aka ‘struct _win_st’}
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.)
--
1057545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bosh
Version: 0.6-11
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
autoreconf: warning: autoconf input should be named 'configure.ac', not
'configure.in'
aclocal: warning: autoconf input should be named 'configure.ac', not
'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are
deprecated.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:429: AM_INIT_AUTOMAKE is expanded from...
configure.in:2: the top level
configure.in:14: warning: AC_OUTPUT should be used without arguments.
configure.in:14: You should run autoupdate.
automake: warning: autoconf input should be named 'configure.ac', not
'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are
deprecated. For more info, see:
configure.in:2:
https://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:3: installing './compile'
automake: warning: autoconf input should be named 'configure.ac', not
'configure.in'
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 for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for ncurses.h... yes
checking for initscr in -lncurses... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
dh_auto_build
make -j2
make[1]: Entering directory '/<>'
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE_URL=\"\" -DPACKAGE=\"bosh\" -DVERSION=\"0.6\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_LIBNCURSES=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2
-Wall -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o
bosh.o bosh.c
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE_URL=\"\" -DPACKAGE=\"bosh\" -DVERSION=\"0.6\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_LIBNCURSES=1 -I. -Wdate-time
Bug#1058814: flint-arb: FTBFS: /<>/fmpz_extras.h:208:1: error: static declaration of ‘fmpz_ui_pow_ui’ follows non-static declaration
Source: flint-arb
Version: 1:2.23.0-1
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=flint-arb=amd64=1%3A2.23.0-1%2Bb2=1702719943=0
gcc -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-I/<> -I/usr/local/include -I/usr/local/include -I/usr/include -c
add_si.c -o ../build/fmpr/add_si.lo -MMD -MP -MF "../build/fmpr/add_si.d" -MT
"../build/fmpr/add_si.d" -MT "../build/fmpr/add_si.lo"
In file included from /<>/fmpr.h:30,
from add_naive.c:12:
/<>/fmpz_extras.h:208:1: error: static declaration of
‘fmpz_ui_pow_ui’ follows non-static declaration
208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
| ^~
In file included from /<>/fmpr.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’
with type ‘void(fmpz *, mp_limb_t, mp_limb_t)’ {aka ‘void(long int *, long
unsigned int, long unsigned int)’}
422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
| ^~
/<>/fmpr.h: In function ‘fmpr_set_ui’:
/<>/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated.
Use 'flint_ctz' instead.
360 | count_trailing_zeros(b, c);
| ^
/<>/fmpr.h: In function ‘fmpr_set_si’:
/<>/fmpr.h:375:11: error: 'count_trailing_zeros' is deprecated.
Use 'flint_ctz' instead.
375 | count_trailing_zeros(b, c);
| ^
In file included from /<>/fmpr.h:30,
from add_eps.c:12:
/<>/fmpz_extras.h:208:1: error: static declaration of
‘fmpz_ui_pow_ui’ follows non-static declaration
208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
| ^~
In file included from /<>/fmpr.h:30,
from add_fmpz.c:12:
/<>/fmpz_extras.h:208:1: error: static declaration of
‘fmpz_ui_pow_ui’ follows non-static declaration
208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
| ^~
In file included from /<>/fmpr.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’
with type ‘void(fmpz *, mp_limb_t, mp_limb_t)’ {aka ‘void(long int *, long
unsigned int, long unsigned int)’}
422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
| ^~
In file included from /<>/fmpr.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’
with type ‘void(fmpz *, mp_limb_t, mp_limb_t)’ {aka ‘void(long int *, long
unsigned int, long unsigned int)’}
422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
| ^~
In file included from /<>/fmpr.h:30,
from add.c:12:
/<>/fmpz_extras.h:208:1: error: static declaration of
‘fmpz_ui_pow_ui’ follows non-static declaration
208 | fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e)
| ^~
In file included from /<>/fmpr.h:23:
/usr/include/flint/fmpz.h:422:6: note: previous declaration of ‘fmpz_ui_pow_ui’
with type ‘void(fmpz *, mp_limb_t, mp_limb_t)’ {aka ‘void(long int *, long
unsigned int, long unsigned int)’}
422 | void fmpz_ui_pow_ui(fmpz_t x, ulong b, ulong e);
| ^~
/<>/fmpr.h: In function ‘fmpr_set_ui’:
/<>/fmpr.h: In function ‘fmpr_set_ui’:
/<>/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated.
Use 'flint_ctz' instead.
360 | count_trailing_zeros(b, c);
| ^
/<>/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated.
Use 'flint_ctz' instead.
360 | count_trailing_zeros(b, c);
| ^
/<>/fmpr.h: In function ‘fmpr_set_si’:
/<>/fmpr.h:375:11: error: 'count_trailing_zeros' is deprecated.
Use 'flint_ctz' instead.
375 | count_trailing_zeros(b, c);
| ^
/<>/fmpr.h: In function ‘fmpr_set_si’:
/<>/fmpr.h:375:11: error: 'count_trailing_zeros' is deprecated.
Use 'flint_ctz' instead.
375 | count_trailing_zeros(b, c);
| ^
/<>/fmpr.h: In function ‘fmpr_set_ui’:
/<>/fmpr.h:360:11: error: 'count_trailing_zeros' is deprecated.
Use 'flint_ctz' instead.
360 | count_trailing_zeros(b, c);
| ^
/<>/fmpr.h: In function ‘fmpr_set_si’:
/<>/fmpr.h:375:11: error: 'count_trailing_zeros' is deprecated.
Use 'flint_ctz' instead.
375 | count_trailing_zeros(b, c);
| ^
make[4]: ***
Bug#1058813: antic: FTBFS: error: unknown type name ‘n_primes_t’
Source: antic Version: 0.2.5+ds-1 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=antic=amd64=0.2.5%2Bds-1%2Bb3=1702719778=0 make[3]: Leaving directory '/<>/nf_elem' make[3]: Entering directory '/<>/qfb' CC ../build/qfb/exponent.lo CC ../build/qfb/exponent_element.lo CC ../build/qfb/exponent_grh.lo CC ../build/qfb/hash_clear.lo exponent_grh.c: In function ‘qfb_exponent_grh’: exponent_grh.c:30:4: error: unknown type name ‘n_primes_t’ 30 |n_primes_t iter; |^~ exponent_grh.c:32:4: warning: implicit declaration of function ‘n_primes_init’ [-Wimplicit-function-declaration] 32 |n_primes_init(iter); |^ exponent_grh.c:54:15: warning: implicit declaration of function ‘n_primes_next’ [-Wimplicit-function-declaration] 54 | pr = n_primes_next(iter); | ^ exponent_grh.c:57:40: warning: implicit declaration of function ‘n_jacobi’; did you mean ‘mpz_jacobi’? [-Wimplicit-function-declaration] 57 | || (pr != 2 && nmodpr != 0 && n_jacobi(nmodpr, pr) < 0)); |^~~~ |mpz_jacobi exponent_grh.c:105:4: warning: implicit declaration of function ‘n_primes_clear’ [-Wimplicit-function-declaration] 105 |n_primes_clear(iter); |^~ make[3]: *** [../Makefile.subdirs:60: ../build/qfb/exponent_grh.lo] Error 1 make[3]: *** Waiting for unfinished jobs Cheers -- Sebastian Ramacher
Bug#1058812: llvm-toolchain-15: do not release with trixie
Source: llvm-toolchain-15 Version: 1:15.0.7-10 Severity: serious X-Debbugs-Cc: sramac...@debian.org See #1050070. Cheers -- Sebastian Ramacher
Bug#1057545: bosh: FTBFS: bosh.c:453:23: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Hi Sven,
On Sat, Dec 16, 2023 at 07:44:21PM +0100, Sven Joachim wrote:
> Control: tags -1 + patch
>
> On 2023-12-05 23:03 +0100, Santiago Vila wrote:
>
> > Package: src:bosh
> > Version: 0.6-11
> > Severity: serious
> > Tags: ftbfs
> >
> > Dear maintainer:
> >
> > During a rebuild of all packages in unstable, your package failed to build:
> >
> >
> > [...]
> > gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
> > -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"
> > -DPACKAGE=\"bosh\" -DVERSION=\"0.6\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1
> > -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1
> > -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1
> > -DHAVE_LIBNCURSES=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> > -c -o bosh.o bosh.c
> > In file included from bosh.c:23:
> > bosh.c: In function ‘keyhandler_readstr’:
> > bosh.c:453:23: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> > ‘struct _win_st’}
> > 453 | mvaddch(stdscr->_cury,stdscr->_curx-1,' ');
> > | ^~
> > bosh.c:453:37: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> > ‘struct _win_st’}
> > 453 | mvaddch(stdscr->_cury,stdscr->_curx-1,' ');
> > | ^~
> > bosh.c:454:20: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> > ‘struct _win_st’}
> > 454 | move(stdscr->_cury,stdscr->_curx-1);
> > |^~
> > bosh.c:454:34: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> > ‘struct _win_st’}
> > 454 | move(stdscr->_cury,stdscr->_curx-1);
> > | ^~
>
> The attached patch fixes that, using the getcury()/getcurx() functions
> rather than accessing the stdscr structure directly which no longer
> works in current ncurses. It is straightforward, but I have only tested
> that bosh builds, not if it works.
Thanks a lot for the patch!
Regards,
Salvatore
Bug#1058811: src:python-diagrams: fails to migrate to testing for too long: not installable
Source: python-diagrams Version: 0.21.1-1 Severity: serious Control: close -1 0.23.4-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1057174 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:python-diagrams has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The version in unstable is not installable as reported in bug 1057174. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=python-diagrams OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:python-diagrams: fails to migrate to testing for too long: not installable
Processing control commands:
> close -1 0.23.4-1
Bug #1058811 [src:python-diagrams] src:python-diagrams: fails to migrate to
testing for too long: not installable
Marked as fixed in versions python-diagrams/0.23.4-1.
Bug #1058811 [src:python-diagrams] src:python-diagrams: fails to migrate to
testing for too long: not installable
Marked Bug as done
> block -1 by 1057174
Bug #1058811 {Done: Paul Gevers } [src:python-diagrams]
src:python-diagrams: fails to migrate to testing for too long: not installable
1058811 was not blocked by any bugs.
1058811 was not blocking any bugs.
Added blocking bug(s) of 1058811: 1057174
--
1058811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1053799: golang-github-libgit2-git2go: no upstream support for latest libgit2
On Sun, 5 Nov 2023 07:07:21 +0800 Shengjing Zhu wrote: git2go is packaged for building gitaly. gitaly upstream has dropped the git2go dependency. Ref: https://gitlab.com/groups/gitlab-org/-/epics/9092 gitaly in salsa dropped this dependency. Once gitlab 16.4 is ready, this will be uploaded to experimental along with gitlab. Then once it is reuploaded to unstable, we can request removal of this package from the archive. So IMO you can start libgit2 transition, and bump this bug's severity. -- Shengjing Zhu OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Processed: Bug#1057545 marked as pending in bosh
Processing control commands:
> tag -1 pending
Bug #1057545 [src:bosh] bosh: FTBFS: bosh.c:453:23: error: invalid use of
incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) pending.
--
1057545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:wordpress: fails to migrate to testing for too long: uploader built arch:all binaries
Processing control commands: > close -1 6.4.1+dfsg1-1 Bug #1058810 [src:wordpress] src:wordpress: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions wordpress/6.4.1+dfsg1-1. Bug #1058810 [src:wordpress] src:wordpress: fails to migrate to testing for too long: uploader built arch:all binaries Marked Bug as done -- 1058810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057545: marked as pending in bosh
Control: tag -1 pending Hello, Bug #1057545 in bosh reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/carnil/bosh/-/commit/d4ddff2fc72b3013cdffb30766bb49254bc2e3b1 Avoid accessing internal ncurses structures (fixes FTBFS) Thanks: Sven Joachim Closes: #1057545 (this message was generated automatically) -- Greetings https://bugs.debian.org/1057545
Bug#1058810: src:wordpress: fails to migrate to testing for too long: uploader built arch:all binaries
Source: wordpress Version: 6.3.2+dfsg1-1 Severity: serious Control: close -1 6.4.1+dfsg1-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:wordpress has been trying to migrate for 32 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=wordpress OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:yash: fails to migrate to testing for too long: FTBFS
Processing control commands:
> close -1 2.55-1
Bug #1058809 [src:yash] src:yash: fails to migrate to testing for too long:
FTBFS
The source 'yash' and version '2.55-1' do not appear to match any binary
packages
Marked as fixed in versions yash/2.55-1.
Bug #1058809 [src:yash] src:yash: fails to migrate to testing for too long:
FTBFS
Marked Bug as done
> block -1 by 1058530
Bug #1058809 {Done: Paul Gevers } [src:yash] src:yash: fails
to migrate to testing for too long: FTBFS
1058809 was not blocked by any bugs.
1058809 was not blocking any bugs.
Added blocking bug(s) of 1058809: 1058530
--
1058809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058809: src:yash: fails to migrate to testing for too long: FTBFS
Source: yash Version: 2.52-2 Severity: serious Control: close -1 2.55-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1058530 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:yash has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The version in unstable failed to build as reported in 1058530. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=yash OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: tagging 1057613
Processing commands for cont...@bugs.debian.org:
> tags 1057613 + fixed-upstream
Bug #1057613 [src:shed] shed: FTBFS: error: invalid use of incomplete typedef
‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1057613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}
Hello Sven, Debian team,
I was about to apply a very similar fix to the "develop" branch of
Linpac at https://sourceforge.net/p/linpac/linpac/ci/develop/tree though
my changes didn't include the "-1" at the end of the changes. Not sure
if that's needed / important. Regardless, I am planning to eventually
merge the develop branch into the Master branch and releae 0.29 in the
near future which will include this and other fixes.
--David
KI6ZHD
On 12/16/2023 10:01 AM, Sven Joachim wrote:
Control: tags -1 + patch
On 2023-12-05 23:07 +0100, Santiago Vila wrote:
Package: src:linpac
Version: 0.28-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
g++ -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o
mail_screen.o mail_screen.cc
mail_screen.cc: In function ‘void init_main_screen()’:
mail_screen.cc:39:16: error: invalid use of incomplete type ‘WINDOW’ {aka
‘struct _win_st’}
39 | maxx = stdscr->_maxx;
|^~
In file included from mail_screen.cc:13:
/usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
‘struct _win_st’}
442 | typedef struct _win_st WINDOW;
|^~~
mail_screen.cc:40:16: error: invalid use of incomplete type ‘WINDOW’ {aka
‘struct _win_st’}
40 | maxy = stdscr->_maxy;
|^~
/usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
‘struct _win_st’}
442 | typedef struct _win_st WINDOW;
|^~~
mail_screen.cc: In function ‘void redraw()’:
mail_screen.cc:70:15: error: invalid use of incomplete type ‘WINDOW’ {aka
‘struct _win_st’}
70 |main_window->_clear = TRUE;
| ^~
/usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
‘struct _win_st’}
442 | typedef struct _win_st WINDOW;
The attached patch, which can be added to the series file fixes, these
errors and two additional ones in src/linpac.cc, but I have only tested
that the package builds, not if it works. Note that getmaxx(win)
returns win->_maxx + 1, and similar for getmaxy.
Cheers,
Sven
Bug#1058805: python3-open3d: SyntaxError: f-string: expecting '=', or '!', or ':', or '}'
Package: python3-open3d
Version: 0.17.0+ds-8+b1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Since the last binNMU, python3-open3d fails to configure at install
time:
Setting up python3-open3d (0.17.0+ds-8+b1) ...
/usr/lib/python3/dist-packages/open3d/examples/geometry/rgbd_datasets.py:35:
SyntaxWarning: invalid escape sequence '\s'
b"(^P5\s(?:\s*#.*[\r\n])*"
/usr/lib/python3/dist-packages/open3d/examples/geometry/rgbd_datasets.py:36:
SyntaxWarning: invalid escape sequence '\d'
b"(\d+)\s(?:\s*#.*[\r\n])*"
/usr/lib/python3/dist-packages/open3d/examples/geometry/rgbd_datasets.py:37:
SyntaxWarning: invalid escape sequence '\d'
b"(\d+)\s(?:\s*#.*[\r\n])*"
/usr/lib/python3/dist-packages/open3d/examples/geometry/rgbd_datasets.py:38:
SyntaxWarning: invalid escape sequence '\d'
b"(\d+)\s(?:\s*#.*[\r\n]\s)*)", buffer).groups()
/usr/lib/python3/dist-packages/open3d/examples/t_reconstruction_system/pose_graph_optim.py:16:
SyntaxWarning: invalid escape sequence '\i'
'''
File
"/usr/lib/python3/dist-packages/open3d/visualization/tensorboard_plugin/summary.py",
line 427
f"{tensor.shape[k-1] for tensor in tensor_tuple}.")
^^^
SyntaxError: f-string: expecting '=', or '!', or ':', or '}'
dpkg: error processing package python3-open3d (--configure):
installed python3-open3d package post-installation script subprocess returned
error exit status 1
- -- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-open3d depends on:
ii libc6 2.37-13
ii libfmt9 9.1.0+ds1-2
ii libgcc-s1 13.2.0-9
ii libopen3d0.17 0.17.0+ds-8+b1
ii libstdc++6 13.2.0-9
ii open3d-gui-data 0.17.0+ds-8
ii python3 3.11.6-1
ii python3-configargparse 1.5.3-1
ii python3-nbformat5.9.1-1
ii python3-numpy [python3-numpy-abi9] 1:1.24.2-2
ii python3-torch 2.0.1+dfsg-5
ii python3-werkzeug2.2.2-3
python3-open3d recommends no packages.
Versions of packages python3-open3d suggests:
pn open3d-doc
pn open3d-tools
- -- no debconf information
-BEGIN PGP SIGNATURE-
iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmV9+DkACgkQ+C8H+466
LVlvxQv/STeBt+9PrCco5maXUBgJUV67o1sgiY/2udgNZtk7DfkzjY5hOuK9R5YR
dRPCAkHpR7ptOy/skXmz/cVl1AChiT3WrkuVJXYxMX+K3ue4ReYO+kDucPUuz1OL
kWC3hI0dnBiJA74p2X7BeCJaeB3tEyehGFgZOkHvOX7rp48o1lhbghzWfebGfkEl
aS97muuoDN/Zy693qkL8cqWn7rfvAY6X95IQX3/O9EN96zbwk/PuH5Og/nZqtKh9
uKWLmnE3CacNnfBu3E7/U2cyFB8pnf048ucnFe9QYBM9olKxmZuXlwNMxEimvo6g
D/KozgKIU/e7ub2HRhlF0/0RiVp8E0zAUykD2gvc28ZdmwTOwqUecA+gCfWdDKmY
sEAVrl6uOjFH1nvaze7YBkzr8kt6epI6Njvr/r2RT5JvMO0uMTMpAdiWEata9Gd/
eiiYuRvt5Rw/ZPpuImP6aY65Qc+vVvfBobJaX/kMTIm4GAS6lhQiO+q5at7Cd/ma
EaYQxzfa
=4eus
-END PGP SIGNATURE-
Bug#1055492: marked as done (appstream-generator: FTBFS with ldc 1.35)
Your message dated Sat, 16 Dec 2023 18:49:05 + with message-id and subject line Bug#1055492: fixed in appstream-generator 0.9.1-1 has caused the Debian Bug report #1055492, regarding appstream-generator: FTBFS with ldc 1.35 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.) -- 1055492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: appstream-generator Version: 0.9.0-1 Severity: serious Tags: ftbfs sid trixie 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=appstream-generator=amd64=0.9.0-1%2Bb1=1699230502=0 [58/149] ldc2 -I=src/asgen/appstream-generator.p -I=src/asgen -I=../src/asgen -I=src -I=../src -I=girepo -I=../girepo -I/usr/include/d/glibd-2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/appstream -I/usr/include/appstream-compose -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -enable-color -wi -O -g -release -wi -J../src/asgen/../../data -Jsrc/asgen/../../data -makedeps=src/asgen/appstream-generator.p/.._app.d.o.deps -of=src/asgen/appstream-generator.p/.._app.d.o -c ../src/app.d FAILED: src/asgen/appstream-generator.p/.._app.d.o ldc2 -I=src/asgen/appstream-generator.p -I=src/asgen -I=../src/asgen -I=src -I=../src -I=girepo -I=../girepo -I/usr/include/d/glibd-2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/appstream -I/usr/include/appstream-compose -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/webp -enable-color -wi -O -g -release -wi -J../src/asgen/../../data -Jsrc/asgen/../../data -makedeps=src/asgen/appstream-generator.p/.._app.d.o.deps -of=src/asgen/appstream-generator.p/.._app.d.o -c ../src/app.d ../src/asgen/backends/rpmmd/rpmpkgindex.d(28): Error: unable to read module `xml` ../src/asgen/backends/rpmmd/rpmpkgindex.d(28):Expected 'std/xml.d' or 'std/xml/package.d' in one of the following import paths: import path[0] = src/asgen/appstream-generator.p import path[1] = src/asgen import path[2] = ../src/asgen import path[3] = src import path[4] = ../src import path[5] = girepo import path[6] = ../girepo import path[7] = /usr/include/d/glibd-2 import path[8] = /usr/include/glib-2.0 import path[9] = /usr/lib/x86_64-linux-gnu/glib-2.0/include import path[10] = /usr/include/libmount import path[11] = /usr/include/blkid import path[12] = /usr/include/appstream import path[13] = /usr/include/appstream-compose import path[14] = /usr/include/gdk-pixbuf-2.0 import path[15] = /usr/include/libpng16 import path[16] = /usr/include/x86_64-linux-gnu import path[17] = /usr/include/webp import path[18] = /usr/lib/ldc/x86_64-linux-gnu/include/d import path[19] = /usr/include/d Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: appstream-generator Source-Version: 0.9.1-1 Done: Matthias Klumpp We believe that the bug you reported is fixed in the latest version of appstream-generator, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klumpp (supplier of updated appstream-generator 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, 16 Dec 2023 18:52:40 +0100 Source: appstream-generator Architecture: source Version: 0.9.1-1 Distribution: unstable Urgency: medium Maintainer: Matthias Klumpp Changed-By: Matthias Klumpp Closes: 1055492 Changes: appstream-generator (0.9.1-1) unstable; urgency=medium . * New upstream version 0.9.1 - Fixes build with LDC >= 1.35 (Closes: #1055492) * Update d/watch * Bump build-dep on appstream Checksums-Sha1: 294c1d3bd26507cff19b286bc6eab9f1e572e2ce 2340 appstream-generator_0.9.1-1.dsc dd2c83488490082374c697ff602d58bba88e7c4e 548052 appstream-generator_0.9.1.orig.tar.gz
Bug#1057545: bosh: FTBFS: bosh.c:453:23: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Control: tags -1 + patch
On 2023-12-05 23:03 +0100, Santiago Vila wrote:
> Package: src:bosh
> Version: 0.6-11
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
>
> [...]
> gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"
> -DPACKAGE=\"bosh\" -DVERSION=\"0.6\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1
> -DHAVE_LIBNCURSES=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o bosh.o bosh.c
> In file included from bosh.c:23:
> bosh.c: In function ‘keyhandler_readstr’:
> bosh.c:453:23: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct
> _win_st’}
> 453 | mvaddch(stdscr->_cury,stdscr->_curx-1,' ');
> | ^~
> bosh.c:453:37: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct
> _win_st’}
> 453 | mvaddch(stdscr->_cury,stdscr->_curx-1,' ');
> | ^~
> bosh.c:454:20: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct
> _win_st’}
> 454 | move(stdscr->_cury,stdscr->_curx-1);
> |^~
> bosh.c:454:34: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct
> _win_st’}
> 454 | move(stdscr->_cury,stdscr->_curx-1);
> | ^~
The attached patch fixes that, using the getcury()/getcurx() functions
rather than accessing the stdscr structure directly which no longer
works in current ncurses. It is straightforward, but I have only tested
that bosh builds, not if it works.
Cheers,
Sven
From 4e13fe3db4df26574709c107a24bed9eb8b1924b Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Sat, 16 Dec 2023 19:30:56 +0100
Subject: [PATCH] Avoid accessing internal ncurses structures
Since ncurses patchlevel 20231021 the WINDOW structure is opaque, its
members cannot be addressed directly. Use the functions ncurses
provides for this purpose instead.
---
bosh.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/bosh.c b/bosh.c
index 7c634a4..4133c18 100644
--- a/bosh.c
+++ b/bosh.c
@@ -450,8 +450,8 @@ int *keyhandler_readstr(int key) {
case KEY_BACKSPACE:
if(strlen(REPLY)) {
REPLY[strlen(REPLY)-1] = 0;
-mvaddch(stdscr->_cury,stdscr->_curx-1,' ');
-move(stdscr->_cury,stdscr->_curx-1);
+mvaddch(getcury(stdscr),getcurx(stdscr)-1,' ');
+move(getcury(stdscr),getcurx(stdscr)-1);
}
break;
case '\n':
--
2.43.0
Processed: Re: Bug#1057545: bosh: FTBFS: bosh.c:453:23: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Processing control commands:
> tags -1 + patch
Bug #1057545 [src:bosh] bosh: FTBFS: bosh.c:453:23: error: invalid use of
incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) patch.
--
1057545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}
Processing control commands:
> tags -1 + patch
Bug #1057573 [src:linpac] linpac: FTBFS: error: invalid use of incomplete type
‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) patch.
--
1057573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057573: linpac: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’}
Control: tags -1 + patch
On 2023-12-05 23:07 +0100, Santiago Vila wrote:
> Package: src:linpac
> Version: 0.28-2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
>
> [...]
> g++ -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c
> -o mail_screen.o mail_screen.cc
> mail_screen.cc: In function ‘void init_main_screen()’:
> mail_screen.cc:39:16: error: invalid use of incomplete type ‘WINDOW’ {aka
> ‘struct _win_st’}
>39 | maxx = stdscr->_maxx;
> |^~
> In file included from mail_screen.cc:13:
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
> ‘struct _win_st’}
> 442 | typedef struct _win_st WINDOW;
> |^~~
> mail_screen.cc:40:16: error: invalid use of incomplete type ‘WINDOW’ {aka
> ‘struct _win_st’}
>40 | maxy = stdscr->_maxy;
> |^~
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
> ‘struct _win_st’}
> 442 | typedef struct _win_st WINDOW;
> |^~~
> mail_screen.cc: In function ‘void redraw()’:
> mail_screen.cc:70:15: error: invalid use of incomplete type ‘WINDOW’ {aka
> ‘struct _win_st’}
>70 |main_window->_clear = TRUE;
> | ^~
> /usr/include/curses.h:442:16: note: forward declaration of ‘WINDOW’ {aka
> ‘struct _win_st’}
> 442 | typedef struct _win_st WINDOW;
The attached patch, which can be added to the series file fixes, these
errors and two additional ones in src/linpac.cc, but I have only tested
that the package builds, not if it works. Note that getmaxx(win)
returns win->_maxx + 1, and similar for getmaxy.
Cheers,
Sven
From 205aeb6a6c956589ad2a94d16778a138057dfc6e Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Sat, 16 Dec 2023 18:45:57 +0100
Subject: [PATCH] Avoid accessing internal ncurses structures
Since ncurses patchlevel 20231021 the WINDOW structure is opaque, its
members cannot be addressed directly. Use the functions ncurses
provides for this purpose instead.
---
src/applications/mailer/mail_screen.cc | 6 +++---
src/linpac.cc | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/applications/mailer/mail_screen.cc b/src/applications/mailer/mail_screen.cc
index 688b8ca..54697e4 100644
--- a/src/applications/mailer/mail_screen.cc
+++ b/src/applications/mailer/mail_screen.cc
@@ -36,8 +36,8 @@ void init_main_screen()
{
initscr();
- maxx = stdscr->_maxx;
- maxy = stdscr->_maxy;
+ maxx = getmaxx(stdscr) -1;
+ maxy = getmaxy(stdscr) -1;
noecho();
cbreak();
nodelay(stdscr, TRUE);
@@ -67,7 +67,7 @@ void init_main_screen()
void redraw()
{
- main_window->_clear = TRUE;
+ clearok(main_window, TRUE);
redrawwin(main_window);
wrefresh(main_window);
/*if (focus_window != NULL)
diff --git a/src/linpac.cc b/src/linpac.cc
index 54cfa09..1796f88 100644
--- a/src/linpac.cc
+++ b/src/linpac.cc
@@ -234,8 +234,8 @@ void init()
setIConfig("edit_end_line", 17);
setIConfig("chn_line", iconfig("edit_end_line") + 1);
setIConfig("mon_start_line", iconfig("chn_line") +1);
-setIConfig("mon_end_line", stdscr->_maxy);
-setIConfig("max_x", stdscr->_maxx);
+setIConfig("mon_end_line", getmaxy(stdscr) -1);
+setIConfig("max_x", getmaxx(stdscr) -1);
setBConfig("swap_edit", false);
setBConfig("monitor", true);
setBConfig("mon_bin", true);
--
2.43.0
Bug#1042189: marked as done (nlohmann-json3: FTBFS: alloc_traits.h:70:31: error: static assertion failed: allocator_traits::rebind_alloc must be A)
Your message dated Sat, 16 Dec 2023 17:49:41 +
with message-id
and subject line Bug#1042189: fixed in nlohmann-json3 3.11.3-1
has caused the Debian Bug report #1042189,
regarding nlohmann-json3: FTBFS: alloc_traits.h:70:31: error: static assertion
failed: allocator_traits::rebind_alloc must be A
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.)
--
1042189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nlohmann-json3
Version: 3.11.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++
> -DDOCTEST_CONFIG_SUPER_FAST_ASSERTS -DJSON_TEST_KEEP_MACROS
> -DJSON_TEST_USING_MULTIPLE_HEADERS=1
> -I/<>/tests/thirdparty/doctest
> -I/<>/tests/thirdparty/fifo_map
> -I/<>/obj-x86_64-linux-gnu/include -I/<>/include -g
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11
> -Wno-deprecated -Wno-float-equal -Wno-deprecated-declarations -MD -MT
> tests/CMakeFiles/test-allocator_cpp11.dir/src/unit-allocator.cpp.o -MF
> CMakeFiles/test-allocator_cpp11.dir/src/unit-allocator.cpp.o.d -o
> CMakeFiles/test-allocator_cpp11.dir/src/unit-allocator.cpp.o -c
> /<>/tests/src/unit-allocator.cpp
> In file included from /usr/include/c++/13/ext/alloc_traits.h:34,
> from /usr/include/c++/13/bits/basic_string.h:39,
> from /usr/include/c++/13/string:54,
> from /usr/include/c++/13/bits/locale_classes.h:40,
> from /usr/include/c++/13/bits/ios_base.h:41,
> from /usr/include/c++/13/streambuf:43,
> from /usr/include/c++/13/bits/streambuf_iterator.h:35,
> from /usr/include/c++/13/iterator:66,
> from /<>/include/nlohmann/json.hpp:28,
> from /<>/tests/src/unit-allocator.cpp:12:
> /usr/include/c++/13/bits/alloc_traits.h: In instantiation of ‘struct
> std::__allocator_traits_base::__rebind<{anonymous}::bad_allocator std::__cxx11::basic_string,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> > >, std::pair std::__cxx11::basic_string,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> >, void>’:
> /usr/include/c++/13/bits/alloc_traits.h:94:11: required by substitution of
> ‘template using std::__alloc_rebind = typename
> std::__allocator_traits_base::__rebind<_Alloc, _Up>::type [with _Alloc =
> {anonymous}::bad_allocator,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> > >; _Up = std::pair std::__cxx11::basic_string,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> >]’
> /usr/include/c++/13/bits/alloc_traits.h:228:8: required by substitution of
> ‘template template using std::allocator_traits<
> >::rebind_alloc = std::__alloc_rebind<_Alloc, _Tp>
> [with _Tp = std::pair,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> >; _Alloc =
> {anonymous}::bad_allocator,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> > >]’
> /usr/include/c++/13/ext/alloc_traits.h:126:65: required from ‘struct
> __gnu_cxx::__alloc_traits<{anonymous}::bad_allocator std::__cxx11::basic_string,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> > >, std::pair std::__cxx11::basic_string,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> > >::rebind std::__cxx11::basic_string,
> nlohmann::json_abi_v3_11_2::basic_json std::__cxx11::basic_string, bool, long int, long unsigned int, double,
> {anonymous}::bad_allocator> > >’
> /usr/include/c++/13/bits/stl_map.h:152:28: required from ‘class
> std::map,
> nlohmann::json_abi_v3_11_2::basic_json
Bug#1058395: marked as done (scikit-build-core: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Sat, 16 Dec 2023 17:37:13 +
with message-id
and subject line Bug#1058395: fixed in scikit-build-core 0.7.0-1
has caused the Debian Bug report #1058395,
regarding scikit-build-core: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-build-core
Version: 0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> 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:110: Building wheel for python3.12 with "build"
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_scikit-build-core
> * Building wheel...
> Successfully built scikit_build_core-0.6.1-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.12 with
> "installer" module
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
> module
> I: pybuild base:310: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_scikit-build-core
> * Building wheel...
> Successfully built scikit_build_core-0.6.1-py3-none-any.whl
> I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd
> /<>/.pybuild/cpython3_3.12_scikit-build-core/build; python3.12
> -m pytest -k 'not network and not test_cmake_config and not test_get_requires
> and not test_prepare_metadata and not test_program_search and not
> test_setuptools_abi3 and not test_setuptools_pep517'
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> installed packages of interest: build==0.10.0 cattrs==22.2.0 packaging==23.2
> pathspec==0.11.1 pyproject-metadata==0.7.1 pytest==7.4.3
> scikit_build_core==0.6.1 setuptools==68.1.2 setuptools-scm==7.1.0
> typing-extensions==4.7.1 virtualenv==20.25.0+ds wheel==0.42.0
> sysconfig platform: linux-x86_64
> rootdir: /<>/.pybuild/cpython3_3.12_scikit-build-core/build
> configfile: pyproject.toml
> testpaths: tests
> collected 217 items / 41 deselected / 1 skipped / 176 selected
>
> tests/test_builder.py FXs. [
> 11%]
> tests/test_dynamic_metadata.py .s.F..[
> 17%]
> tests/test_editable_unit.py .. [
> 18%]
> tests/test_file_processor.py . [
> 18%]
> tests/test_fileapi.py [
> 21%]
> tests/test_generator_default.py ... [
> 22%]
> tests/test_json_schema.py [
> 27%]
> tests/test_logging.py ...[
> 28%]
> tests/test_module_dir.py .. [
> 30%]
> tests/test_name_main.py ... [
> 31%]
> tests/test_process_scripts.py . [
> 32%]
> tests/test_pyproject_abi3.py F [
> 32%]
> tests/test_pyproject_extra_dirs.py ..[
> 34%]
> tests/test_pyproject_pep517.py ..FFs.[
> 39%]
> tests/test_pyproject_pep660.py F [
> 40%]
> tests/test_schema.py .sss[
> 58%]
> tests/test_settings.py [
> 76%]
> tests/test_settings_overrides.py . [
> 88%]
> tests/test_shutil.py ... [
> 90%]
> tests/test_simple_pure.py ...[
> 92%]
> tests/test_simplest_c.py .
Bug#1056528: marked as done (scikit-build-core's autopkg tests fail with Python 3.12)
Your message dated Sat, 16 Dec 2023 17:37:13 +
with message-id
and subject line Bug#1056528: fixed in scikit-build-core 0.7.0-1
has caused the Debian Bug report #1056528,
regarding scikit-build-core's autopkg tests fail with Python 3.12
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.)
--
1056528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:scikit-build-core
Version: 0.5.1-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
scikit-build-core's autopkg tests fail with Python 3.12:
[...]
188s = test session starts
==
188s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
188s installed packages of interest: build==0.10.0 cattrs==22.2.0
importlib-metadata==4.12.0 packaging==23.2 pathspec==0.11.1
pyproject-metadata==0.7.1 pytest==7.4.3 rich==13.3.1
scikit_build_core==0.5.1 setuptools==68.1.2 setuptools-scm==7.1.0
typing-extensions==4.7.1 wheel==0.41.2
188s sysconfig platform: linux-x86_64
188s rootdir: /tmp/autopkgtest.iZVGqP/autopkgtest_tmp/build
188s configfile: pyproject.toml
188s testpaths: tests
188s collected 180 items / 37 deselected / 1 skipped / 143 selected
188s
189s tests/test_builder.py FXs.
[ 13%]
189s tests/test_dynamic_metadata.py .s.E..
[ 20%]
189s tests/test_file_processor.py .
[ 21%]
189s tests/test_fileapi.py
[ 24%]
189s tests/test_generator_default.py ...
[ 26%]
189s tests/test_json_schema.py
[ 32%]
189s tests/test_logging.py ...
[ 34%]
189s tests/test_module_dir.py ..
[ 35%]
190s tests/test_name_main.py ...
[ 37%]
190s tests/test_process_scripts.py .
[ 38%]
190s tests/test_pyproject_abi3.py E
[ 39%]
190s tests/test_pyproject_extra_dirs.py ..
[ 40%]
195s tests/test_pyproject_pep517.py ..EEs.
[ 47%]
195s tests/test_pyproject_pep660.py F
[ 48%]
195s tests/test_schema.py .s
[ 63%]
195s tests/test_settings.py
[ 86%]
195s tests/test_shutil.py ...
[ 88%]
196s tests/test_simple_pure.py ...
[ 90%]
197s tests/test_simplest_c.py .
[ 93%]
197s tests/test_skbuild_settings.py ...
[ 98%]
197s tests/test_wheelfile_utils.py ..
[100%]
197s
197s ERRORS
197s _ ERROR at setup of test_pep517_wheel
__
197s
197s self =
197s context =
namespace(env_dir='/tmp/pytest-of-ubuntu/pytest-0/test_pep517_wheel0/venv',
env_name='venv', prompt='(venv) ',
executa.../test_pep517_wheel0/venv/bin/python3.12',
cfg_path='/tmp/pytest-of-ubuntu/pytest-0/test_pep517_wheel0/venv/pyvenv.cfg')
197s
197s def _setup_pip(self, context):
197s """Installs or upgrades pip in a virtual environment"""
197s try:
197s > self._call_new_python(context, '-m', 'ensurepip',
'--upgrade',
197s '--default-pip',
stderr=subprocess.STDOUT)
197s
197s /usr/lib/python3.12/venv/__init__.py:360:
197s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
197s /usr/lib/python3.12/venv/__init__.py:355: in _call_new_python
197s subprocess.check_output(args, **kwargs)
197s /usr/lib/python3.12/subprocess.py:466: in check_output
197s return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
197s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _
197s
197s input = None, capture_output = False, timeout = None, check = True
197s popenargs =
(['/tmp/pytest-of-ubuntu/pytest-0/test_pep517_wheel0/venv/bin/python3.12',
'-m', 'ensurepip', '--upgrade', '--default-pip'],)
197s kwargs = {'cwd':
'/tmp/pytest-of-ubuntu/pytest-0/test_pep517_wheel0/venv', 'env':
{'ADTTMP': '/tmp/autopkgtest.iZVGqP/autopkgte...facts', ...},
'executable':
'/tmp/pytest-of-ubuntu/pytest-0/test_pep517_wheel0/venv/bin/python3.12',
'stderr': -2, ...}
197s process = ['/tmp/pytest-of-ubuntu/pytest-0/test_pep517_whe...>
197s stdout =
b'/tmp/pytest-of-ubuntu/pytest-0/test_pep517_wheel0/venv/bin/python3.12:
No module named ensurepip\n'
197s stderr = None, retcode = 1
197s
197s def run(*popenargs,
197s input=None, capture_output=False, timeout=None,
check=False, **kwargs):
197s """Run command with arguments and return a CompletedProcess
instance.
197s
197s The returned
Bug#1055962: fixed in intel-microcode 3.20231114.1~deb10u1 (source amd64) for oldoldstable
Control: fixed -1 3.20231114.1~deb10u1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 16 Dec 2023 16:57:23 +0100 Source: intel-microcode Binary: intel-microcode Architecture: source amd64 Version: 3.20231114.1~deb10u1 Distribution: buster-security Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Tobias Frost Description: intel-microcode - Processor microcode firmware for Intel CPUs Closes: 1055962 Changes: intel-microcode (3.20231114.1~deb10u1) buster-security; urgency=medium . * Non-maintainer upload by the LTS Security Team. * No-change upload of the bullseye version, rebuilt for buster (LTS), fixing CVE-2023-23583 (Closes: #1055962) See changelog entry from November 16th 2023 or DSA-5563-1 for details about the security vulnerability. Checksums-Sha1: e6063e55cb84b37f080807886b4476f5be035326 1821 intel-microcode_3.20231114.1~deb10u1.dsc dcab82d32fd7faf6697f753b6d9a14c67f4a0781 6792632 intel-microcode_3.20231114.1~deb10u1.tar.xz 334ce8840bfe1215e20c168c4d9468283e11eebe 5688 intel-microcode_3.20231114.1~deb10u1_amd64.buildinfo b2105ab7679ce564b100de7d507e344935d571ca 6120188 intel-microcode_3.20231114.1~deb10u1_amd64.deb Checksums-Sha256: 4c71f53bc3dd9617681117e4bb38124f1a6f19053d5630598b25498754aba0f1 1821 intel-microcode_3.20231114.1~deb10u1.dsc 113f91e76ade1da2094f6b924d4adc38c271255ec8d104718bd5ed00e3a1872d 6792632 intel-microcode_3.20231114.1~deb10u1.tar.xz 7ab9a50215a633e3c553b5fcfcd39dcf5a77398b8a2324a98bdb814780295c2c 5688 intel-microcode_3.20231114.1~deb10u1_amd64.buildinfo 2f77678e739f704a2a53d38520f4115afc5c552ee12f0b3e09b4d54a6411fd87 6120188 intel-microcode_3.20231114.1~deb10u1_amd64.deb Files: e27ba406815aa5cf28fd321841f2d3ae 1821 non-free/admin standard intel-microcode_3.20231114.1~deb10u1.dsc 2407b021328beb18330cbead67717477 6792632 non-free/admin standard intel-microcode_3.20231114.1~deb10u1.tar.xz 483c7fec0979f02b683fa0c650766708 5688 non-free/admin standard intel-microcode_3.20231114.1~deb10u1_amd64.buildinfo f09471c94fbeba8942f1803444c1ce1f 6120188 non-free/admin standard intel-microcode_3.20231114.1~deb10u1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmV9yiAACgkQkWT6HRe9 XTaDcg//THWr44UhGrxPJW1cdcIsb+wg8GmIehA5yKP4/8dRPrhJCuNzTV7l4pev uFIGUw9ftuSyD/4gyFafrYcBtC9ZQ85GAmEMtYNuxMGydJj/UR5muwz9xBfCZLET 9Yh3qhU31o4J2SDfiVrXlr/U1qxwy2rNQvwEOr2zOAResQo7psyFZby9Jx5IlHmU kV5RmY0XWBftvIqeMxfcao78IZ74otGfytR38fLkH4aQu/eJIzp3kkU5e8/IelVZ Vl8lS0E5PNiOMKbSDPXNwJ/tXibTchq37EdK9uivu+cCNBfuF36qOGHGyp/y7fxc XMXAfp1rtzy1CUpOsgpdAqDlizLNsjr1w7ww1yKMLHgc7gbquaQypQfGpnA/mvzf ZiKKnrz8wpCYFuLDMU978DhTFLK/KTQoHVZfGIaaRTvJQlq7Uc205J/3r0a/efyf IGTxLONlo6V8vHq6o7todhLrfd6L7+bdtW58rD38/giPAB7mMEIgevGvTmzQBKb2 9vyImuGF/rSrVxlWlLW9M4gYrPO7jNPAgybP1fz8IWDyTBDZEr9L5R8H33kisYk8 p9dQl0qhm7p5iFXQzpYNZ4XROaoDSCSPx4UAwKtzIzx/o9omHCT/UQ4KPvkZLdrI WTm0nmJXOKcQJsyMVKbRsKTBy2SYcEHNQ+MWELpMu0DjPr7d4Ko= =JHZ4 -END PGP SIGNATURE-
Processed: fixed in intel-microcode 3.20231114.1~deb10u1 (source amd64) for oldoldstable
Processing control commands:
> fixed -1 3.20231114.1~deb10u1
Bug #1055962 {Done: Henrique de Moraes Holschuh }
[src:intel-microcode] intel-microcode: CVE-2023-23583: INTEL-SA-00950
The source 'intel-microcode' and version '3.20231114.1~deb10u1' do not appear
to match any binary packages
Marked as fixed in versions intel-microcode/3.20231114.1~deb10u1.
--
1055962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058657: python3-apt: undefined symbol: PyAptWarning
This bug can be reproduced with just a single import statement ``` import apt_inst ```
Bug#1057967: This bug is not resolved completely
I'm observing same misbehaviours, as described by Kevin Price (Gnome becomes unusable), even with newest image installed (linux-image-6.1.0-16-amd64). I had to install version 13 to omit the bug (linux-image-6.1.0-13-amd64). With 13: everything works stable. With 16: as long, as I use only WiFi, everything works stable too. But as soon as I connect cable to LAN socket of laptop, Gnome loses network and all problems occurs again, like described in first message. It is enough to boot image 13, and I can use both cable and wireless network without any trouble. If you'd like to read a logs, then please tell which files to copy and after what actions? Debian version is 12.4.
Processed: Bug#1057578 marked as pending in mpd
Processing control commands:
> tag -1 pending
Bug #1057578 {Done: Geoffroy Youri Berret } [src:mpd] mpd:
FTBFS: error: ‘AVERROR_EOF’ was not declared in this scope
Added tag(s) pending.
--
1057578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057578: marked as pending in mpd
Control: tag -1 pending Hello, Bug #1057578 in mpd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/mpd-team/mpd/-/commit/3f80faf83610a1529ce9ec99857e912179e86b11 Fixed FTBS with ffmpeg 6.1 (closes: #1057578) (this message was generated automatically) -- Greetings https://bugs.debian.org/1057578
Bug#1000009: opencollada: depends on obsolete pcre3 library
Control: tags -1 + patch
Please find attached a patch.
Tested with an example COLLADA file.
>From f1772e60500e6cbdf3231792a6f7216eb1ac53e0 Mon Sep 17 00:00:00 2001
From: Yavor Doganov
Date: Sat, 16 Dec 2023 15:34:11 +0200
Subject: [PATCH] Port to PCRE2 (#109)
---
debian/changelog | 7 +
debian/control | 2 +-
debian/patches/pcre2.patch | 785 +
debian/patches/series | 1 +
4 files changed, 794 insertions(+), 1 deletion(-)
create mode 100644 debian/patches/pcre2.patch
diff --git a/debian/changelog b/debian/changelog
index c87ac4f..f0634a2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+opencollada (0.1.0~20180719.619d942+dfsg0-3) UNRELEASED; urgency=medium
+
+ * debian/patches/pcre2.patch: New; port to PCRE2 (Closes: #109).
+ * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+
+ -- Yavor Doganov Sat, 16 Dec 2023 15:32:13 +0200
+
opencollada (0.1.0~20180719.619d942+dfsg0-2) unstable; urgency=medium
* Upload to unstable
diff --git a/debian/control b/debian/control
index da6c13e..4c64ef8 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Uploaders: Matteo F. Vescovi
Build-Depends:
cmake,
debhelper-compat (= 11),
- libpcre3-dev,
+ libpcre2-dev,
libxml2-dev
Standards-Version: 4.2.1
Homepage: http://www.opencollada.org/
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
new file mode 100644
index 000..6849bc6
--- /dev/null
+++ b/debian/patches/pcre2.patch
@@ -0,0 +1,785 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/109
+Author: Yavor Doganov
+Forwarded: no
+Last-Update: 2023-12-16
+---
+
+--- opencollada.orig/CMakeLists.txt
opencollada/CMakeLists.txt
+@@ -257,16 +257,8 @@
+ find_package(PCRE)
+ if (PCRE_FOUND)
+ message(STATUS "SUCCESSFUL: PCRE found")
+-else () # if pcre not found building its local copy from ./Externals
+- if (WIN32 OR APPLE)
+- message("WARNING: Native PCRE not found, taking PCRE from
./Externals")
+- add_definitions(-DPCRE_STATIC)
+- add_subdirectory(${EXTERNAL_LIBRARIES}/pcre)
+- set(PCRE_INCLUDE_DIR ${libpcre_include_dirs})
+- set(PCRE_LIBRARIES pcre)
+- else ()
+- message("ERROR: PCRE not found, please install pcre library")
+- endif ()
++else ()
++ message("ERROR: PCRE not found, please install pcre library")
+ endif ()
+
+ # building required libs
+--- opencollada.orig/COLLADABaseUtils/include/COLLADABUPcreCompiledPattern.h
opencollada/COLLADABaseUtils/include/COLLADABUPcreCompiledPattern.h
+@@ -12,6 +12,8 @@
+ #define __COLLADABU_PCRECOMPILEDPATTERN_H__
+
+ #include "COLLADABUPrerequisites.h"
++#define PCRE2_CODE_UNIT_WIDTH 8
++#include
+
+ struct real_pcre;
+ typedef struct real_pcre pcre;
+@@ -29,7 +31,7 @@
+ {
+ private:
+ /** The compiled pattern.*/
+- pcre *mCompiledPattern;
++ pcre2_code *mCompiledPattern;
+
+ /** True, if we need to free the pattern in the destructor,
false otherwise.*/
+ bool mFreePattern;
+@@ -44,7 +46,7 @@
+ virtual ~PcreCompiledPattern();
+
+ /** Returns the compiled pattern. */
+- pcre* getCompiledPattern() const;
++ pcre2_code* getCompiledPattern() const;
+
+ private:
+
+@@ -55,7 +57,7 @@
+ const PcreCompiledPattern& operator= ( const
PcreCompiledPattern& pre );
+
+ /** Compiles the pattern.*/
+- pcre* compilePattern( const char* pattern );
++ pcre2_code* compilePattern( const char* pattern );
+
+ };
+
+--- opencollada.orig/COLLADABaseUtils/src/COLLADABUPcreCompiledPattern.cpp
opencollada/COLLADABaseUtils/src/COLLADABUPcreCompiledPattern.cpp
+@@ -11,7 +11,6 @@
+ #include "COLLADABUStableHeaders.h"
+ #include "COLLADABUPcreCompiledPattern.h"
+
+-#include "pcre.h"
+
+ namespace COLLADABU
+ {
+@@ -30,17 +29,18 @@
+ {
+ if ( mFreePattern )
+ {
+- pcre_free(mCompiledPattern);
++ pcre2_code_free(mCompiledPattern);
+ }
+ }
+
+ //--
+- pcre* PcreCompiledPattern::compilePattern( const char* pattern )
++ pcre2_code* PcreCompiledPattern::compilePattern( const char* pattern )
+ {
+- const char *error;
+- int erroffset;
+- pcre* compiledPattern = pcre_compile(
+- pattern,
/* the pattern */
++ int error;
++ size_t erroffset;
++ pcre2_code* compiledPattern = pcre2_compile(
++
(PCRE2_SPTR)pattern, /* the pattern */
++
Processed: Re: Bug#1000009: opencollada: depends on obsolete pcre3 library
Processing control commands: > tags -1 + patch Bug #109 [src:opencollada] opencollada: depends on obsolete pcre3 library Added tag(s) patch. -- 109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057410: marked as done (pymupdf: FTBFS in testing and unstable)
Your message dated Sat, 16 Dec 2023 15:04:44 + with message-id and subject line Bug#1057402: fixed in pymupdf 1.23.7+ds1-1 has caused the Debian Bug report #1057402, regarding pymupdf: FTBFS in testing and unstable 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.) -- 1057402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pymupdf Version: 1.22.5+ds1-1 Severity: serious Tags: ftbfs Hi Maintainer As can be seen in reproducible builds [1], pymupdf currently FTBFS in testing and unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/pymupdf.html I: pybuild base:310: cd /build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build; python3.11 -m unittest discover -v fitz (unittest.loader._FailedTest.fitz) ... ERROR == ERROR: fitz (unittest.loader._FailedTest.fitz) -- ImportError: Failed to import test module: fitz Traceback (most recent call last): File "/usr/lib/python3.11/unittest/loader.py", line 452, in _find_test_path package = self._get_module_from_name(name) File "/usr/lib/python3.11/unittest/loader.py", line 362, in _get_module_from_name __import__(name) File "/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/__init__.py", line 10, in import fitz.fitz as fitz File "/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/fitz.py", line 14, in from . import _fitz ImportError: /build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/_fitz.cpython-311-x86_64-linux-gnu.so: undefined symbol: pdf_lookup_anchor -- Ran 1 test in 0.003s FAILED (errors=1) --- End Message --- --- Begin Message --- Source: pymupdf Source-Version: 1.23.7+ds1-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of pymupdf, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated pymupdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Dec 2023 19:43:12 +0100 Source: pymupdf Architecture: source Version: 1.23.7+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Bastian Germann Closes: 1046144 1057402 Changes: pymupdf (1.23.7+ds1-1) unstable; urgency=medium . * Team upload * Clean helper-git-versions.i (Closes: #1046144) * New upstream version 1.23.7+ds1 (Closes: #1057402) * Make sure the package builds with the new build system Checksums-Sha1: 934bcd3748bdb947aa6a8a1ec57d6633a75764c5 2069 pymupdf_1.23.7+ds1-1.dsc 55ff39e60e397627b1036a446c7f9ca3553b1687 28658740 pymupdf_1.23.7+ds1.orig.tar.xz a0b971c9df1c4f8a0e2ee16102bacd9b0e26c1a7 16100 pymupdf_1.23.7+ds1-1.debian.tar.xz 5de9490546deb3b525b1de8a52ff22705b78996c 9557 pymupdf_1.23.7+ds1-1_source.buildinfo Checksums-Sha256: ef34cd99f68d8a0854840b0d9021ec8ff89e7064705551c1fa946a4bcea440f8 2069 pymupdf_1.23.7+ds1-1.dsc 2153d35774a1a77b5cacd7647514d8e85720d7502a74864f3ee07ef9fb69c7c1 28658740 pymupdf_1.23.7+ds1.orig.tar.xz 496574cdae8f4a01e746eb31ad236a9a99c676c6b0193c94579ed67fc60ccf97 16100 pymupdf_1.23.7+ds1-1.debian.tar.xz c28bcf2cdaeb47b784311a1eb752c3a00418d34501b53cbedbe946a9cb7df238 9557 pymupdf_1.23.7+ds1-1_source.buildinfo Files: 57bce27414f623d9233c8d6ae67f1230 2069 python optional pymupdf_1.23.7+ds1-1.dsc 3eb938e1ba7571bd2d23ca135156621c 28658740 python optional pymupdf_1.23.7+ds1.orig.tar.xz c159e7028ecd29fb7a677ba2fc29c993 16100 python optional pymupdf_1.23.7+ds1-1.debian.tar.xz c1ec4e513a2a48233c8edcdf07dac0aa 9557 python optional pymupdf_1.23.7+ds1-1_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#1057402: marked as done (pymupdf ftbfs with Python 3.12)
Your message dated Sat, 16 Dec 2023 15:04:44 +
with message-id
and subject line Bug#1057402: fixed in pymupdf 1.23.7+ds1-1
has caused the Debian Bug report #1057402,
regarding pymupdf ftbfs with Python 3.12
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.)
--
1057402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pymupdf
Version: 1.22.5+ds1-1
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
pymupdf ftbfs with Python 3.12 in unstable:
I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12/build;
python3.12 -m unittest discover -v
fitz (unittest.loader._FailedTest.fitz) ... ERROR
==
ERROR: fitz (unittest.loader._FailedTest.fitz)
--
ImportError: Failed to import test module: fitz
Traceback (most recent call last):
File "/usr/lib/python3.12/unittest/loader.py", line 427, in
_find_test_path
package = self._get_module_from_name(name)
File "/usr/lib/python3.12/unittest/loader.py", line 337, in
_get_module_from_name
__import__(name)
File
"/<>/.pybuild/cpython3_3.12/build/fitz/__init__.py", line
10, in
import fitz.fitz as fitz
File "/<>/.pybuild/cpython3_3.12/build/fitz/fitz.py",
line 14, in
from . import _fitz
ImportError:
/<>/.pybuild/cpython3_3.12/build/fitz/_fitz.cpython-312-x86_64-linux-gnu.so:
undefined symbol: pdf_lookup_anchor
--
Ran 1 test in 0.000s
FAILED (errors=1)
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1:
cd /<>/.pybuild/cpython3_3.12/build; python3.12 -m unittest
discover -v
I: pybuild base:310: cd /<>/.pybuild/cpython3_3.11/build;
python3.11 -m unittest discover -v
fitz (unittest.loader._FailedTest.fitz) ... ERROR
==
ERROR: fitz (unittest.loader._FailedTest.fitz)
--
ImportError: Failed to import test module: fitz
Traceback (most recent call last):
File "/usr/lib/python3.11/unittest/loader.py", line 452, in
_find_test_path
package = self._get_module_from_name(name)
File "/usr/lib/python3.11/unittest/loader.py", line 362, in
_get_module_from_name
__import__(name)
File
"/<>/.pybuild/cpython3_3.11/build/fitz/__init__.py", line
10, in
import fitz.fitz as fitz
File "/<>/.pybuild/cpython3_3.11/build/fitz/fitz.py",
line 14, in
from . import _fitz
ImportError:
/<>/.pybuild/cpython3_3.11/build/fitz/_fitz.cpython-311-x86_64-linux-gnu.so:
undefined symbol: pdf_lookup_anchor
--
Ran 1 test in 0.000s
FAILED (errors=1)
E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1:
cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m unittest
discover -v
dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11"
returned exit code 13
--- End Message ---
--- Begin Message ---
Source: pymupdf
Source-Version: 1.23.7+ds1-1
Done: Bastian Germann
We believe that the bug you reported is fixed in the latest version of
pymupdf, 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 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann (supplier of updated pymupdf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Dec 2023 19:43:12 +0100
Source: pymupdf
Architecture: source
Version: 1.23.7+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Bastian Germann
Closes: 1046144 1057402
Changes:
pymupdf (1.23.7+ds1-1) unstable; urgency=medium
.
* Team upload
* Clean helper-git-versions.i (Closes: #1046144)
* New upstream version 1.23.7+ds1 (Closes: #1057402)
* Make sure the package builds with the new
Bug#1058787: marked as done (libmirisdr4: introduces new file into /lib while being m-a:same)
Your message dated Sat, 16 Dec 2023 14:49:12 + with message-id and subject line Bug#1058787: fixed in libmirisdr 2.0.0-3 has caused the Debian Bug report #1058787, regarding libmirisdr4: introduces new file into /lib while being m-a:same 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.) -- 1058787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmirisdr4 Version: 2.0.0-1 Severity: serious Tags: patch User: helm...@debian.org Usertags: dep17p7 X-Debbugs-Cc: helm...@debian.org Hi, your package libmirisdr4 is marked Multi-Arch: Same and introduced a new file into /lib. I'm filing this bug now so your package will not hit testing. I see two options forward: 1) introduce the DEP17 P7 M10 mitigations again and move the file to /usr/lib. 2) just move the file to /usr/lib, possibly triggering the file loss for users in unstable. If you want to go with this option, you can do that now; it's your decision if this is appropriate for your users in unstable. For the mitigations option, someone will have to find time to write and test a patch. **In any case** _please_ upload to _experimental_ first and give the dumat tool [1] time to check your package. Chris [1] https://wiki.debian.org/UsrMerge --- End Message --- --- Begin Message --- Source: libmirisdr Source-Version: 2.0.0-3 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of libmirisdr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated libmirisdr 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, 16 Dec 2023 08:56:56 -0500 Source: libmirisdr Architecture: source Version: 2.0.0-3 Distribution: experimental Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Closes: 1058787 Changes: libmirisdr (2.0.0-3) experimental; urgency=medium . * upload to experimental for dumat tool * Move udev files from /lib to /usr/lib, including protective diversion against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #1058787) Checksums-Sha1: 9627a1ad87f0b1634bb501298b381c3a049f580f 2029 libmirisdr_2.0.0-3.dsc c94b86f78c89ef6b7d52a34f220123a5036bd735 7784 libmirisdr_2.0.0-3.debian.tar.xz eb0be517758a4bbaf10b6b04fc1f66420a6f8626 8215 libmirisdr_2.0.0-3_amd64.buildinfo Checksums-Sha256: a6f4961e62d96c6b5ef444676fd0a2a8c0a595c503b7cac82d285c640907bd3e 2029 libmirisdr_2.0.0-3.dsc 03b14e92ef082e70f96df271d9c9479790fa6c0ac18a30825bf63118afa3bb87 7784 libmirisdr_2.0.0-3.debian.tar.xz a075c554f95b924f3f7c1450ea6c943d357a041494f2820e8efd9cd45acb801c 8215 libmirisdr_2.0.0-3_amd64.buildinfo Files: 1e94f63ca3b7715a4e821dbf9f1d9909 2029 libs optional libmirisdr_2.0.0-3.dsc 1575cc6aca15f945f4108317e527d030 7784 libs optional libmirisdr_2.0.0-3.debian.tar.xz 428d16b5cda61855d4fa25305ccc174f 8215 libs optional libmirisdr_2.0.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmV9siMACgkQUEHxiR9E 4JCGThAA6u+AEC0iexc/LRWueaVTYyZymA7/MYE1EzgN4oHIKLUq3qPyGmoGU1HG MDn4nWzPux3oBQzaKlMqqbJ4KkPkPYTi9Plj8EUnS43oMczsyjL8RXdquO1Cp3Op mt5v6SDvHtJ2yskEvZZSU8tHmRI+h7Lr7wdWI+c986/8G9DM+/7Hs2UFac5lIs9n vtnYFoG6yh4YxH/pdSDDeR/qAp581TTQeUkhlRLsRZ9VnfQus2am/P5lWQvn0KiD +Rzvae0E4YbbpdaN+15uGbvGw4kRFXeoz77XO/KBmoPaBn4TZM6XZ3PFR0GAy18u H9zlIoYPtApdBFyp6vIFPM1Q3aAQ5T5Tn87S81m5KIU2KAfeWuevsn/3cairAUDW aZoCptk7ML0E2HUhF7idpOboq6F1YMhZQ5QJEe06pwfVo7xdWdYF9Nb/TFuDVbXm BQM1YSqDjHhybyldMsqEK9PXVmHBwfErARX6DivqOWfM9RIyai6FxQeohUueDamF SXCQsiC/qd2QiD8G9zkrLxxVPZv8jNfr8vU/3E/0NfIFDNyDqwTC1b+gk325mIlj lfUFbMHLS/JjIn21AAJU7189DLxTXKLwNIChv2SCRUptvK0D3nNqGEmsvCXyX3CQ eH0yegCj0yz8gk+rdGp/RkwCeelEBp5yiLFt6+GOrVbxmOEDrZ0= =h6NA -END PGP SIGNATURE End Message ---
Bug#1058787: marked as pending in libmirisdr
Control: tag -1 pending Hello, Bug #1058787 in libmirisdr reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-hamradio-team/libmirisdr/-/commit/4d9102902ed0633bf2e336b582cfbac6e4f14799 Import Debian changes 2.0.0-3 libmirisdr (2.0.0-3) experimental; urgency=medium . * upload to experimental for dumat tool * Move udev files from /lib to /usr/lib, including protective diversion against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #1058787) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058787
Processed: Bug#1058787 marked as pending in libmirisdr
Processing control commands: > tag -1 pending Bug #1058787 [libmirisdr4] libmirisdr4: introduces new file into /lib while being m-a:same Added tag(s) pending. -- 1058787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058795: installing docker.io makes all qemu guests lose internet connection
Package: docker.io
Version: 20.10.24+dfsg1-1+b3
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
* What led up to the situation?
installed docker.io with existing qemu guests in bridge mode, did not do
anything else.
* What was the outcome of this action?
qemu guests lost internet
* What outcome did you expect instead?
qemu guests should still have internet OR the installer should notice that
other bridge users already exist and show a big fat warning.
Also, uninstalling docker.io should restore the original situation which it
does not.
In dmesg I found
Bridge firewalling registered
Initializing XFRM netlink socket
It seems this is what docker.io does.
I can fix the problem by disabling sysctl net.bridge.bridge-nf-
call-{ip6tables,iptables,arptables}
Found the solution here:
https://wiki.libvirt.org/Net.bridge.bridge-nf-call_and_sysctl.conf.html
apt remove --purge does NOT fix the problem, an additional reboot is needed.
In the attachment please find networking info before installing docker.io
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.61-169 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 docker.io depends on:
ii adduser3.134
ii containerd 1.6.20~ds1-1+b1
ii init-system-helpers1.65.2
ii iptables 1.8.9-2
ii libc6 2.36-9+deb12u3
ii libdevmapper1.02.1 2:1.02.185-2
ii libsystemd0252.19-1~deb12u1
ii lsb-base 11.6
ii runc 1.1.5+ds1-1+b1
ii sysvinit-utils [lsb-base] 3.06-4
ii tini 0.19.0-1
Versions of packages docker.io recommends:
ii apparmor 3.0.8-3
ii ca-certificates 20230311
ii cgroupfs-mount 1.4
ii git 1:2.39.2-1.1
ii needrestart 3.6-4
ii xz-utils 5.4.1-0.2
Versions of packages docker.io suggests:
pn aufs-tools
ii btrfs-progs6.2-1
ii debootstrap1.0.128+nmu2+deb12u1
pn docker-doc
ii e2fsprogs 1.47.0-2
pn rinse
pn rootlesskit
ii xfsprogs 6.1.0-1
pn zfs-fuse | zfsutils-linux
-- no debconf information
ip r ==
default via 10.210.30.1 dev br0 onlink
10.210.30.0/24 dev br0 proto kernel scope link src 10.210.30.3
ip a ==
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: lan0: mtu 1500 qdisc pfifo_fast master br0
state UP group default qlen 1000
link/ether 50:eb:f6:2c:3f:74 brd ff:ff:ff:ff:ff:ff
3: br0: mtu 1500 qdisc noqueue state UP group
default qlen 1000
link/ether 1a:12:4d:40:d2:62 brd ff:ff:ff:ff:ff:ff
inet 10.210.30.3/24 brd 10.210.30.255 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::1812:4dff:fe40:d262/64 scope link
valid_lft forever preferred_lft forever
4: vnet0: mtu 1500 qdisc noqueue master br0
state UNKNOWN group default qlen 1000
link/ether fe:54:00:51:71:5c brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe51:715c/64 scope link
valid_lft forever preferred_lft forever
5: vnet1: mtu 1500 qdisc noqueue master br0
state UNKNOWN group default qlen 1000
link/ether fe:54:00:7f:ef:9d brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe7f:ef9d/64 scope link
valid_lft forever preferred_lft forever
iconfig -a ==
br0: flags=4163 mtu 1500
inet 10.210.30.3 netmask 255.255.255.0 broadcast 10.210.30.255
inet6 fe80::1812:4dff:fe40:d262 prefixlen 64 scopeid 0x20
ether 1a:12:4d:40:d2:62 txqueuelen 1000 (Ethernet)
RX packets 42346 bytes 6405978 (6.1 MiB)
RX errors 0 dropped 375 overruns 0 frame 0
TX packets 28794 bytes 237355775 (226.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lan0: flags=4163 mtu 1500
ether 50:eb:f6:2c:3f:74 txqueuelen 1000 (Ethernet)
RX packets 44272 bytes 8116108 (7.7 MiB)
RX errors 0 dropped 18 overruns 0 frame 0
TX packets 179833 bytes 247674510 (236.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000
Bug#1055002: marked as done (shaarli: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)
Your message dated Sat, 16 Dec 2023 08:22:06 -0500 with message-id <8a917e01-4bb5-4903-b176-5b6006cd9...@mailbox.org> and subject line fixed has caused the Debian Bug report #1055002, regarding shaarli: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shaarli Version: 0.12.1+dfsg-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > --- > PHPUNIT > --- > PHPUnit 9.6.13 by Sebastian Bergmann and contributors. > > Warning: Your XML configuration validates against a deprecated schema. > Suggestion:Migrate your XML configuration using "--migrate-configuration"! > > ..S..SS 63 / 939 ( > 6%) > ... 126 / 939 ( > 13%) > ... 189 / 939 ( > 20%) > ... 252 / 939 ( > 26%) > ... 315 / 939 ( > 33%) > ... 378 / 939 ( > 40%) > .SSS... 441 / 939 ( > 46%) > .E..E.E.E.. 504 / 939 ( > 53%) > ...S... 567 / 939 ( > 60%) > ....S.S...S 630 / 939 ( > 67%) > ... 693 / 939 ( > 73%) > ... 756 / 939 ( > 80%) > .S. 819 / 939 ( > 87%) > ... 882 / 939 ( > 93%) > .S... 939 / 939 > (100%) > > Time: 00:01.455, Memory: 34.00 MB > > There were 12 errors: > > 1) > Shaarli\Front\Controller\Visitor\DailyControllerTest::testValidIndexControllerInvokeDefault > IntlException: datefmt_create: invalid locale: U_ILLEGAL_ARGUMENT_ERROR > > /<>/application/Utils.php:323 > /<>/application/helper/DailyPageHelper.php:185 > /<>/application/front/controller/visitor/DailyController.php:35 > /<>/tests/front/controller/visitor/DailyControllerTest.php:99 > /usr/bin/phpunit:82 > > 2) > Shaarli\Front\Controller\Visitor\DailyControllerTest::testValidIndexControllerInvokeNoFutureOrPast > IntlException: datefmt_create: invalid locale: U_ILLEGAL_ARGUMENT_ERROR > > /<>/application/Utils.php:323 > /<>/application/helper/DailyPageHelper.php:185 > /<>/application/front/controller/visitor/DailyController.php:35 > /<>/tests/front/controller/visitor/DailyControllerTest.php:222 > /usr/bin/phpunit:82 > > 3) > Shaarli\Front\Controller\Visitor\DailyControllerTest::testValidIndexControllerInvokeHeightAdjustment > IntlException: datefmt_create: invalid locale: U_ILLEGAL_ARGUMENT_ERROR > > /<>/application/Utils.php:323 > /<>/application/helper/DailyPageHelper.php:185 > /<>/application/front/controller/visitor/DailyController.php:35 > /<>/tests/front/controller/visitor/DailyControllerTest.php:280 > /usr/bin/phpunit:82 > > 4) > Shaarli\Front\Controller\Visitor\DailyControllerTest::testValidIndexControllerInvokeNoBookmark > IntlException: datefmt_create: invalid locale: U_ILLEGAL_ARGUMENT_ERROR > > /<>/application/Utils.php:323 > /<>/application/helper/DailyPageHelper.php:185 > /<>/application/front/controller/visitor/DailyController.php:35 > /<>/tests/front/controller/visitor/DailyControllerTest.php:325 > /usr/bin/phpunit:82 > > 5) > Shaarli\Front\Controller\Visitor\DailyControllerTest::testValidRssControllerInvokeDefault > IntlException: datefmt_create: invalid locale: U_ILLEGAL_ARGUMENT_ERROR > > /<>/application/Utils.php:323 > /<>/application/helper/DailyPageHelper.php:185 > /<>/application/front/controller/visitor/DailyController.php:134 > /<>/tests/front/controller/visitor/DailyControllerTest.php:373 > /usr/bin/phpunit:82 > > 6) Shaarli\Front\Controller\Visitor\DailyControllerTest::testSimpleIndexWeekly > IntlException: datefmt_create: invalid
Bug#1058510: marked as done (kaidan: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)
Your message dated Sat, 16 Dec 2023 13:19:30 + with message-id and subject line Bug#1056583: fixed in kaidan 0.9.1-3 has caused the Debian Bug report #1056583, regarding kaidan: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1056583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kaidan Version: 0.9.1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j8 > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: PresenceCacheTest > > 1: Test command: /<>/obj-x86_64-linux-gnu/bin/PresenceCacheTest > 1: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 1: Environment variables: > 1: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 1: Test timeout computed to be: 1000 > test 2 > Start 2: RosterItemWatcherTest > > 2: Test command: > /<>/obj-x86_64-linux-gnu/bin/RosterItemWatcherTest > 2: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 2: Environment variables: > 2: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 2: Test timeout computed to be: 1000 > test 3 > Start 3: UserPresenceWatcherTest > > 3: Test command: > /<>/obj-x86_64-linux-gnu/bin/UserPresenceWatcherTest > 3: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 3: Environment variables: > 3: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 3: Test timeout computed to be: 1000 > test 4 > Start 4: TrustDbTest > > 4: Test command: /<>/obj-x86_64-linux-gnu/bin/TrustDbTest > 4: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 4: Environment variables: > 4: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 4: Test timeout computed to be: 1000 > test 5 > Start 5: OmemoDbTest > > 5: Test command: /<>/obj-x86_64-linux-gnu/bin/OmemoDbTest > 5: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 5: Environment variables: > 5: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 5: Test timeout computed to be: 1000 > test 6 > Start 6: PublicGroupChatTest > > 6: Test command: /<>/obj-x86_64-linux-gnu/bin/PublicGroupChatTest > 6: Working Directory: /<>/obj-x86_64-linux-gnu/tests > 6: Environment variables: > 6: QT_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/bin: > 6: Test timeout computed to be: 1000 > 1: * Start testing of PresenceCacheTest * > 1: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), > debian unknown > 3: * Start testing of UserPresenceWatcherTest * > 3: Config: Using QtTest library 5.15.10, Qt 5.15.10 > (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.2.0), > debian unknown > 1: PASS : PresenceCacheTest::initTestCase() > 1: PASS : PresenceCacheTest::presenceChangedSignal() > 1: PASS : PresenceCacheTest::presenceGetter(bob1) > 1: PASS : PresenceCacheTest::presenceGetter(bob2) > 1: PASS : PresenceCacheTest::presenceGetter(alice1) > 3: PASS : UserPresenceWatcherTest::initTestCase() > 1: PASS : PresenceCacheTest::presenceGetter(alice2) > 1: PASS : PresenceCacheTest::presenceGetter(unknwon presence) > 1: PASS : PresenceCacheTest::idealResource(DND) > 3: PASS : UserPresenceWatcherTest::testBasic() > 3: PASS : UserPresenceWatcherTest::cleanupTestCase() > 1: PASS : PresenceCacheTest::idealResource(Chat) > 1: PASS : PresenceCacheTest::idealResource(XA) > 1: PASS : PresenceCacheTest::idealResource(Away) > 1: PASS : PresenceCacheTest::idealResource(status text [DND]) > 1: PASS : PresenceCacheTest::idealResource(status text [XA]) > 1: PASS : PresenceCacheTest::cleanupTestCase() > 3: Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms > 3: * Finished testing of UserPresenceWatcherTest * > 1: Totals: 14 passed, 0
Bug#1056583: marked as done (kaidan: FTBFS with disabled network)
Your message dated Sat, 16 Dec 2023 13:19:30 + with message-id and subject line Bug#1056583: fixed in kaidan 0.9.1-3 has caused the Debian Bug report #1056583, regarding kaidan: FTBFS with disabled network 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.) -- 1056583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kaidan Version: 0.9.1-2 Severity: serious Hello, the package FTBFS trying to call search.jabber.network, something forbidden by policy. 6: QWARN : GroupChatTest::test_GroupChatSearchManager_GroupChatModel() public-group-chat.search: Search request error: Host search.jabber.network not found 6: FAIL! : GroupChatTest::test_GroupChatSearchManager_GroupChatModel() 'spyError.isEmpty()' returned FALSE. () Full log available e.g. here: https://launchpadlibrarian.net/698369989/buildlog_ubuntu-noble-amd64.kaidan_0.9.1-2_BUILDING.txt.gz I think disabling that test function should work as workaround. G. OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: kaidan Source-Version: 0.9.1-3 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of kaidan, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kaidan package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 16 Dec 2023 14:05:45 +0100 Source: kaidan Architecture: source Version: 0.9.1-3 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Pino Toscano Closes: 1056583 Changes: kaidan (0.9.1-3) unstable; urgency=medium . * Team upload. * Disable the test test_GroupChatSearchManager_GroupChatModel, as it requires an Internet connectivity. (Closes: #1056583) Checksums-Sha1: 046b27118e88314107204bfa0e0cfb5516096d06 2776 kaidan_0.9.1-3.dsc ffd4c1b5b2fd94ec20b5740142e52a82901ed9a9 17680 kaidan_0.9.1-3.debian.tar.xz 7393be38bba8cad7f5965ec03c0d547e073b77d5 18487 kaidan_0.9.1-3_source.buildinfo Checksums-Sha256: 500d5c85bccc3803538650077319a58bfbfb4ba0f67ca6f111c1c7470d841b8f 2776 kaidan_0.9.1-3.dsc f05aa1834521dd6280beba811b5adda44716808bf91fcf2cf1202e7588335f1a 17680 kaidan_0.9.1-3.debian.tar.xz 8b58fbaa905f150a6e24c368c49a83fc19b527ae2b11aff3d050c7bc4cec14eb 18487 kaidan_0.9.1-3_source.buildinfo Files: cbedc520c866f1410412dd37e2ba5d25 2776 net optional kaidan_0.9.1-3.dsc 83da3a710d90dfca0bebc40fffa2 17680 net optional kaidan_0.9.1-3.debian.tar.xz 5b106c000fc61fc280a8a84fb9b6fb8b 18487 net optional kaidan_0.9.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmV9oNgACgkQLRkciEOx P02pTQ/8Dt3gZBELYLfMv3LcZb1xG2gtpj05pTItsivyYEXiRsTp9l+Uo2kT5oQj p+qt2HmQbuw/RQ139+q5Qxym+EGVwov/Mmhaw6gNjv4O3NwtjtV8pAPGMCAFHM/s GXBP+y4KnrVVH/8Y14EFJIqxfat7qYkJTRmC5CWAcHtzjZPdddSVtr22SacrjPq1 oAO0P53qkOKTbqcJvx9VLxmCf8pxjEy0xkBZEONgadSktObc0v3LkWGpWp/kxsvu 5thWlCMwaiuqpYE0hroq0Vl2Fx8A/7Mrm7k+OsjACXvsadBzWxVkfgXnuxjkDWQZ 8lLG371tg3qdwjMlHhTdtiClEnFQvnkEnj7pEMA5lDiuWOxGLK1tXVPnGItm9uBY zMNYd7unyBoccEUG4DKRgkFgojn+gD0gFYO6/26KbrbM/PFImqCD5Amp4KDqUA9O x2KJkByBBkoocBsnBlyHuIOmE7/6F9Mqpg6TZEqFsvtfCQgSSF5Em8FTzQiRDY+6 UIz50WDHaAQVDCbpcyMLbAh3u+ENnVpt1StMp/dMikwp/D8/Vq4Qor7jKuaKkoos g0q5PNuACkRA8vd0CT/4owgO+i15BidMxSp8uQeiTqSWZ2gC588MxaWasn2ms9V+ jVJAH6bFe3aP6REIrHs+g7DaQRnScar88D238hiB7T25rQKwmIU= =VDiz -END PGP SIGNATURE End Message ---
Bug#1057930: cunit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Control: tags -1 + patch
On 2023-12-10 20:17 +0100, Santiago Vila wrote:
> Package: src:cunit
> Version: 2.1-3-dfsg-2.6
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
>
> [...]
>>/debian/build-ncurses/CUnit/Headers -std=c99 -c -o Curses.lo Curses.c
> Curses.c: In function ‘initialize_windows’:
> Curses.c:259:41: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 259 | f_nLeft = application_windows.pMainWin->_begx;
> | ^~
> Curses.c:260:40: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 260 | f_nTop = application_windows.pMainWin->_begy;
> |^~
> Curses.c:261:42: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 261 | f_nWidth = application_windows.pMainWin->_maxx;
> | ^~
> Curses.c:262:43: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 262 | f_nHeight = application_windows.pMainWin->_maxy;
> | ^~
> Curses.c: In function ‘refresh_windows’:
> Curses.c:361:41: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 361 | f_nLeft = application_windows.pMainWin->_begx;
> | ^~
> Curses.c:362:40: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 362 | f_nTop = application_windows.pMainWin->_begy;
> |^~
> Curses.c:363:42: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 363 | f_nWidth = application_windows.pMainWin->_maxx;
> | ^~
> Curses.c:364:43: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 364 | f_nHeight = application_windows.pMainWin->_maxy;
> | ^~
> Curses.c: In function ‘create_pad’:
> Curses.c:910:52: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 910 | pPad->uiWinLeft = application_windows.pDetailsWin->_begx + 1;
> |^~
> Curses.c:911:51: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 911 | pPad->uiWinTop = application_windows.pDetailsWin->_begy + 1;
> | ^~
> Curses.c:912:55: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 912 | pPad->uiWinColumns = application_windows.pDetailsWin->_maxx - 2;
> | ^~
> Curses.c:913:52: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 913 | pPad->uiWinRows = application_windows.pDetailsWin->_maxy - 2;
> |^~
The attached patch, which can be added to the series file, fixes these
errors, but I have only tested that the package builds, not if it works.
Note that getmaxx(win) returns win->_maxx + 1, and similar for getmaxy.
Cheers,
Sven
From 6412a56519dabfc18365d97abb06388c029d84aa Mon Sep 17 00:00:00 2001
From: Sven Joachim
Date: Sat, 16 Dec 2023 11:23:40 +0100
Subject: [PATCH] Fix FTBFS with newer ncurses
Since ncurses patchlevel 20231021 the WINDOW structure is opaque, its
members cannot be addressed directly. Use the functions ncurses
provides for this purpose instead.
---
CUnit/Sources/Curses/Curses.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/CUnit/Sources/Curses/Curses.c b/CUnit/Sources/Curses/Curses.c
index 17eaa30..eda272e 100644
--- a/CUnit/Sources/Curses/Curses.c
+++ b/CUnit/Sources/Curses/Curses.c
@@ -256,10 +256,10 @@ static bool initialize_windows(void)
start_color();
- f_nLeft = application_windows.pMainWin->_begx;
- f_nTop = application_windows.pMainWin->_begy;
- f_nWidth = application_windows.pMainWin->_maxx;
- f_nHeight = application_windows.pMainWin->_maxy;
+ f_nLeft = getbegx(application_windows.pMainWin);
+ f_nTop = getbegy(application_windows.pMainWin);
+ f_nWidth = getmaxx(application_windows.pMainWin) - 1;
+ f_nHeight = getmaxy(application_windows.pMainWin) - 1;
if (NULL == (application_windows.pTitleWin = newwin(3, f_nWidth, 0, 0))) {
goto title_fail;
@@ -358,10 +358,10 @@ static void refresh_windows(void)
{
refresh();
- f_nLeft = application_windows.pMainWin->_begx;
- f_nTop = application_windows.pMainWin->_begy;
- f_nWidth = application_windows.pMainWin->_maxx;
- f_nHeight = application_windows.pMainWin->_maxy;
+ f_nLeft = getbegx(application_windows.pMainWin);
+ f_nTop =
Processed: Re: Bug#1057930: cunit: FTBFS: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Processing control commands:
> tags -1 + patch
Bug #1057930 [src:cunit] cunit: FTBFS: invalid use of incomplete typedef
‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) patch.
--
1057930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1056583
Processing commands for cont...@bugs.debian.org: > tags 1056583 + pending Bug #1056583 [src:kaidan] kaidan: FTBFS with disabled network Bug #1058510 [src:kaidan] kaidan: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056583 1058510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055517: opensysusers: modifies host system instead of target environment
Hi Ansgar, On Tue, 07 Nov 2023 19:38:25 +0100 Ansgar wrote: > opensysusers doesn't really implement the `--root` option (though it > pretends a bit). Functions like `add_group` always access > `/etc/group` and use tools like `groupadd`: > > ```sh > grep -q "^$1:" /etc/group || groupadd -r "$1" > ``` > > So they will always modify the host system, even when supposed to > operate on some chroot environment. > > Applying changes intended for some other environment to the host > system looks like a potential security issue. Thanks for the report, I wasn't aware of this issue and I agree with you that yeah, this can be a security issue, and quite an unexpeted behaviour. How do you think this should be handled? opensysusers is pretty much dead upstream (they accept patches, but the Artix Linux community isn't working on it anymore), so I don't expect them to fix this bug. I'll report it though. Still, groupadd and useradd support a "--root" option which seems to do exactly what we need here, so writing a patch to fix the issue looks reasonable. I'm not sure how to test such patch though. > AFAIR there are other incompatibilities with systemd-sysusers so that > opensysusers should arguably not claim to be a compatible drop-in > replacement. This has been discussed both recently and some years ago, and while using opensysusers as a drop-in replacement seemed appropriate in the past, I don't think it still is *that* compelling, not because using a systemd-sysusers alternative doesn't make sense (I have personally worked to develop one in the past), but because opensysusers is Linux-only, and it can be used in the same exact scenarios as the standalone version of systemd-sysusers, so from a technical point of view I don't really see opensysusers' usefulness anymore (a standalone version of systemd-sysusers hasn't always existed). You could say that opensysusers is "more secure" because it isn't written in C, but the sh scripting language isn't exactly that secure compared to e.g. Rust or Go. In conclusion, I'm still not sure what the best thing to do right now is. For now, I'll limit myself at fixing this bug. Thanks again! Bye :)
Bug#1058790: marked as done (mayavi2: autopkgtest failure in pysurfer since python-traitsui 8)
Your message dated Sat, 16 Dec 2023 12:04:07 +
with message-id
and subject line Bug#1058790: fixed in mayavi2 4.8.1-2
has caused the Debian Bug report #1058790,
regarding mayavi2: autopkgtest failure in pysurfer since python-traitsui 8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mayavi2
Version: 4.8.1-1
Severity: serious
Justification: autopkgtest failure in reverse dependecy
Tags: patch upstream fixed-upstream
Affects: pysurfer
Forwarded: https://github.com/enthought/mayavi/pull/1255
Dear Maintainer,
Since introduction of python3-traitsui 8, pysurfer is failing
its autopkgtest suite with errors like[1]:
ERRORS
_ ERROR collecting tests/test_utils.py
_
ImportError while importing test module
'/tmp/autopkgtest.pQ5bOG/autopkgtest_tmp/tests/test_utils.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_utils.py:9: in
from surfer import utils
/usr/lib/python3/dist-packages/surfer/__init__.py:1: in
from .viz import Brain, TimeViewer # noqa
/usr/lib/python3/dist-packages/surfer/viz.py:17: in
from mayavi.core.ui.api import SceneEditor
/usr/lib/python3/dist-packages/mayavi/core/ui/api.py:4: in
from tvtk.pyface.scene_editor import SceneEditor
/usr/lib/python3/dist-packages/tvtk/pyface/scene_editor.py:12: in
SceneEditor = toolkit_object('scene_editor:SceneEditor')
/usr/lib/python3/dist-packages/pyface/base_toolkit.py:127: in __call__
module = import_module(mname, package)
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
/usr/lib/python3/dist-packages/tvtk/pyface/ui/qt4/scene_editor.py:16:
in
from traitsui.qt4.editor import Editor
E ModuleNotFoundError: No module named 'traitsui.qt4.editor'
[1]: https://ci.debian.net/packages/p/pysurfer/unstable/amd64/39514398/
They look to stem from mayavi2 trying to make use of an old way
of loading the editor module, now called traitsui.qt.editor.
Upstream prepared the a patch[2] to upcoming versions of
mayavi2, but it is not there yet.
[2]: https://github.com/enthought/mayavi/pull/1255
I have verified the patch fixes the autopkgtest regression in
pysurfer, and did not raise any obvious issues in mayavi2. I'm
considering providing a team upload to resolve this particular
issue.
Have a nice day, :)
--
.''`. Étienne Mollier
: :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
`. `' sent from /dev/pts/7, please excuse my verbosity
`-on air: K2 - Storm at Sunset
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mayavi2
Source-Version: 4.8.1-2
Done: Étienne Mollier
We believe that the bug you reported is fixed in the latest version of
mayavi2, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Étienne Mollier (supplier of updated mayavi2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Dec 2023 12:25:27 +0100
Source: mayavi2
Architecture: source
Version: 4.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Étienne Mollier
Closes: 1058790
Changes:
mayavi2 (4.8.1-2) unstable; urgency=medium
.
* Team upload.
* traitsui-8.patch: fix missing traitsui.qt4.editor. (Closes: #1058790)
Checksums-Sha1:
02644944bb64415953cb6f0335d6db00c4557474 2348 mayavi2_4.8.1-2.dsc
bb48c2e529366a414bf0f8c8eb9b63c450acc57e 366720 mayavi2_4.8.1-2.debian.tar.xz
Checksums-Sha256:
Bug#1058790: marked as pending in mayavi2
Control: tag -1 pending Hello, Bug #1058790 in mayavi2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/mayavi2/-/commit/ecd9bc059dfb7bd0406e15f218917bebd3ff8e56 traitsui-8.patch: fix missing traitsui.qt4.editor. Closes: #1058790 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058790
Processed: fix affection of src:pysurfer by mayavi2 bug of compatibility with tratsui 8
Processing commands for cont...@bugs.debian.org: > affects 1058790 src:pysurfer Bug #1058790 [src:mayavi2] mayavi2: autopkgtest failure in pysurfer since python-traitsui 8 Added indication that 1058790 affects src:pysurfer > thank you Stopping processing here. Please contact me if you need assistance. -- 1058790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1058790 marked as pending in mayavi2
Processing control commands: > tag -1 pending Bug #1058790 [src:mayavi2] mayavi2: autopkgtest failure in pysurfer since python-traitsui 8 Added tag(s) pending. -- 1058790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057553: marked as done (dosbox: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka ‘struct _win_st’})
Your message dated Sat, 16 Dec 2023 11:20:06 +
with message-id
and subject line Bug#1057553: fixed in dosbox 0.74-3-5
has caused the Debian Bug report #1057553,
regarding dosbox: FTBFS: error: invalid use of incomplete type ‘WINDOW’ {aka
‘struct _win_st’}
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.)
--
1057553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dosbox
Version: 0.74-3-4
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
configure.ac:12: warning: The macro `AC_CONFIG_HEADER' is obsolete.
configure.ac:12: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:12: the top level
configure.ac:31: warning: The macro `AC_TRY_RUN' is obsolete.
configure.ac:31: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
acinclude.m4:4: AM_PATH_SDL is expanded from...
configure.ac:31: the top level
configure.ac:31: warning: The macro `AC_TRY_LINK' is obsolete.
[... snipped ...]
../../../src/cpu/core_dynrec/dyn_fpu.h:354:86: warning: format ‘%d’ expects
argument of type ‘int’, but argument 4 has type ‘Bitu’ {aka ‘long unsigned
int’} [-Wformat=]
354 | LOG(LOG_FPU,LOG_WARN)("ESC 2:Unhandled group %d
subfunction %d",decode.modrm.reg,decode.modrm.rm);
|
~^ ~~~
|
||
|
int Bitu {aka long unsigned int}
|
%ld
../../../src/cpu/core_dynrec/dyn_fpu.h: In function ‘void dyn_fpu_esc3()’:
../../../src/cpu/core_dynrec/dyn_fpu.h:373:110: warning: format ‘%d’ expects
argument of type ‘int’, but argument 3 has type ‘Bitu’ {aka ‘long unsigned
int’} [-Wformat=]
373 | LOG(LOG_FPU,LOG_ERROR)("8087 only fpu code
used esc 3: group 4: subfuntion: %d",decode.modrm.rm);
|
~^ ~~~
|
| |
|
int Bitu {aka long unsigned
int}
|
%ld
../../../src/cpu/core_dynrec/dyn_fpu.h:386:69: warning: format ‘%d’ expects
argument of type ‘int’, but argument 2 has type ‘Bitu’ {aka ‘long unsigned
int’} [-Wformat=]
386 | E_Exit("ESC 3:ILLEGAL OPCODE group %d
subfunction %d",decode.modrm.reg,decode.modrm.rm);
|~^
| |
|
| int
Bitu {aka long unsigned int}
|%ld
../../../src/cpu/core_dynrec/dyn_fpu.h:386:84: warning: format ‘%d’ expects
argument of type ‘int’, but argument 3 has type ‘Bitu’ {aka ‘long unsigned
int’} [-Wformat=]
386 | E_Exit("ESC 3:ILLEGAL OPCODE group %d
subfunction %d",decode.modrm.reg,decode.modrm.rm);
|
~^ ~~~
|
||
|
int Bitu {aka long unsigned int}
|
Bug#1058790: mayavi2: autopkgtest failure in pysurfer since python-traitsui 8
Source: mayavi2
Version: 4.8.1-1
Severity: serious
Justification: autopkgtest failure in reverse dependecy
Tags: patch upstream fixed-upstream
Affects: pysurfer
Forwarded: https://github.com/enthought/mayavi/pull/1255
Dear Maintainer,
Since introduction of python3-traitsui 8, pysurfer is failing
its autopkgtest suite with errors like[1]:
ERRORS
_ ERROR collecting tests/test_utils.py
_
ImportError while importing test module
'/tmp/autopkgtest.pQ5bOG/autopkgtest_tmp/tests/test_utils.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_utils.py:9: in
from surfer import utils
/usr/lib/python3/dist-packages/surfer/__init__.py:1: in
from .viz import Brain, TimeViewer # noqa
/usr/lib/python3/dist-packages/surfer/viz.py:17: in
from mayavi.core.ui.api import SceneEditor
/usr/lib/python3/dist-packages/mayavi/core/ui/api.py:4: in
from tvtk.pyface.scene_editor import SceneEditor
/usr/lib/python3/dist-packages/tvtk/pyface/scene_editor.py:12: in
SceneEditor = toolkit_object('scene_editor:SceneEditor')
/usr/lib/python3/dist-packages/pyface/base_toolkit.py:127: in __call__
module = import_module(mname, package)
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
/usr/lib/python3/dist-packages/tvtk/pyface/ui/qt4/scene_editor.py:16:
in
from traitsui.qt4.editor import Editor
E ModuleNotFoundError: No module named 'traitsui.qt4.editor'
[1]: https://ci.debian.net/packages/p/pysurfer/unstable/amd64/39514398/
They look to stem from mayavi2 trying to make use of an old way
of loading the editor module, now called traitsui.qt.editor.
Upstream prepared the a patch[2] to upcoming versions of
mayavi2, but it is not there yet.
[2]: https://github.com/enthought/mayavi/pull/1255
I have verified the patch fixes the autopkgtest regression in
pysurfer, and did not raise any obvious issues in mayavi2. I'm
considering providing a team upload to resolve this particular
issue.
Have a nice day, :)
--
.''`. Étienne Mollier
: :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
`. `' sent from /dev/pts/7, please excuse my verbosity
`-on air: K2 - Storm at Sunset
signature.asc
Description: PGP signature
Bug#1058767: netplug: unmaintained
On Friday 15 December 2023 21:56:01 Chris Hofstaedtler wrote: > Source: netplug > Version: 1.2.9.2-3.2 > Severity: serious > > I'm filing this to get netplug removed from testing, with the goal > of removing it from unstable later, and before that happens, anyone > who wants to actually maintain this package can speak up. > > As demonstrated today, having packages in stable that end up used in > downstream distros, and at the same time being completely > unmaintained in Debian for ~7 years is bad for everybody. > > If you like to keep netplug in Debian, please start maintaining it > and then close this bug. > > Otherwise I'll also file an RM bug for unstable later in this > development cycle. > > Chris Hello, I talked with the author of the netplug (Bryan O'Sullivan) and I got permission to continue working on this project. I can continue maintaining this package on Debian, so please let me know what is needed to fix for preventing its removal. Thanks.
Bug#1053424: marked as done (cargo: flaky autopkgtest:)
Your message dated Sat, 16 Dec 2023 11:28:03 +0100
with message-id <20231216102803.46ic7x7rkdn7i4qo@bla>
and subject line Re: cargo: flaky autopkgtest:
has caused the Debian Bug report #1053424,
regarding cargo: flaky autopkgtest:
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.)
--
1053424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cargo
Version: 0.66.0+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it fails very often.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Don't hesitate to reach out if you need help and some more information
from our infrastructure.
Paul
E.g.
https://ci.debian.net/data/autopkgtest/testing/armhf/c/cargo/38257775/log.gz
401s failures:
401s publish::api_error_200
401s publish::api_other_error
401s
401s test result: FAILED. 2461 passed; 2 failed; 142 ignored; 0
measured; 0 filtered out; finished in 199.82s
https://ci.debian.net/data/autopkgtest/testing/amd64/c/cargo/38436894/log.gz
183s failures:
183s
183s credential_process::publish stdout
183s running
`/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/debug/cargo
build`
183s running
`/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/debug/cargo
publish --no-verify --registry alternative -Z credential-process`
183s req: Request {
183s url: Url {
183s scheme: "http",
183s cannot_be_a_base: false,
183s username: "",
183s password: None,
183s host: Some(
183s Ipv4(
183s 127.0.0.1,
183s ),
183s ),
183s port: Some(
183s 39447,
183s ),
183s path: "/api/v1/crates/new",
183s query: None,
183s fragment: None,
183s },
183s method: "put",
183s authorization: Some(
183s "sekrit",
183s ),
183s if_modified_since: None,
183s if_none_match: None,
183s }
183s thread 'credential_process::publish' panicked at '
183s test failed running
`/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/debug/cargo
publish --no-verify --registry alternative -Z credential-process`
183s error: process exited with code 101 (expected 0)
183s --- stdout
183s
183s --- stderr
183s Updating `alternative` index
183sPackaging foo v0.1.0
(/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/tmp/cit/t810/foo)
183sUploading foo v0.1.0
(/tmp/autopkgtest-lxc.37ebfcox/downtmp/build.Dyo/src/target/tmp/cit/t810/foo)
183s error: failed to publish to registry at http://127.0.0.1:39447/
183s
183s Caused by:
183s [55] Failed sending data to the peer (Send failure: Broken pipe)
183s ', tests/testsuite/credential_process.rs:203:10
183s note: run with `RUST_BACKTRACE=1` environment variable to display a
backtrace
183s
183s
183s failures:
183s credential_process::publish
183s
183s test result: FAILED. 2463 passed; 1 failed; 142 ignored; 0
measured; 0 filtered out; finished in 68.41s
https://ci.debian.net/data/autopkgtest/testing/i386/c/cargo/38284747/log.gz
2413s failures:
2413s
2413s credential_process::publish stdout
2413s running
`/tmp/autopkgtest-lxc.8p0qkl9z/downtmp/build.rLB/src/target/debug/cargo
build`
2413s running
`/tmp/autopkgtest-lxc.8p0qkl9z/downtmp/build.rLB/src/target/debug/cargo
publish --no-verify --registry alternative -Z credential-process`
2413s req: Request {
2413s url: Url {
2413s scheme: "http",
2413s cannot_be_a_base: false,
2413s username: "",
2413s password: None,
2413s host: Some(
2413s Ipv4(
2413s 127.0.0.1,
2413s ),
2413s ),
2413s port: Some(
2413s 44181,
2413s ),
2413s path: "/api/v1/crates/new",
2413s query: None,
2413s fragment: None,
2413s },
2413s method: "put",
2413s authorization: Some(
2413s "sekrit",
2413s ),
2413s if_modified_since: None,
2413s if_none_match: None,
2413s }
2413s thread 'credential_process::publish' panicked at '
2413s test failed running
`/tmp/autopkgtest-lxc.8p0qkl9z/downtmp/build.rLB/src/target/debug/cargo
publish --no-verify --registry
Bug#1058787: libmirisdr4: introduces new file into /lib while being m-a:same
Package: libmirisdr4 Version: 2.0.0-1 Severity: serious Tags: patch User: helm...@debian.org Usertags: dep17p7 X-Debbugs-Cc: helm...@debian.org Hi, your package libmirisdr4 is marked Multi-Arch: Same and introduced a new file into /lib. I'm filing this bug now so your package will not hit testing. I see two options forward: 1) introduce the DEP17 P7 M10 mitigations again and move the file to /usr/lib. 2) just move the file to /usr/lib, possibly triggering the file loss for users in unstable. If you want to go with this option, you can do that now; it's your decision if this is appropriate for your users in unstable. For the mitigations option, someone will have to find time to write and test a patch. **In any case** _please_ upload to _experimental_ first and give the dumat tool [1] time to check your package. Chris [1] https://wiki.debian.org/UsrMerge
Bug#1054726: python-daemon: FTBFS: ValueError: ("Missing 'Version:' header and/or PKG-INFO file at path: /<>/python_daemon.egg-info/PKG-INFO", python-daemon [unknown version] (/<
Dear Maintainer, I've just checked your package does build fine in a sid chroot environment and reproducible-builds confirms that [1] >From the log: >> Get:75 http://127.0.0.1:12990/debian sid/main amd64 dh-python all 6.20231025 [107 kB] it was built against dh-python/6.20231025 but the current version in sid is dh-python/6.20231204. I can reproduce the failure with this commit reverted [2]. Kind Regards [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-daemon.html [2] https://salsa.debian.org/python-team/tools/dh-python/-/commit/31553e7169b1cd72f6
Bug#1058784: esbuild: [armel] install @esbuild/arm
Package: esbuild Version: 0.19.8-1 Severity: serious Tags: ftbfs patch Justification: node-esbuild-unusable-on-armel X-Debbugs-Cc: y...@debian.org Hi, my armel patch was wrong: armel build uses @esbuild/arm, not @esbuild/armel. I fixed this in a merge request [MR4] [MR4]: https://salsa.debian.org/go-team/packages/golang-github-evanw-esbuild/-/merge_requests/4
