Bug#1067829: marked as done (nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We
Your message dated Sun, 07 Apr 2024 05:21:43 +
with message-id
and subject line Bug#1067829: fixed in nfs-utils 1:2.6.4-4
has caused the Debian Bug report #1067829,
regarding nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51: error: format
‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’
{aka ‘long long int’} [-Werror=format=]
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.)
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nfs-utils
Version: 1:2.6.4-3
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=nfs-utils=armel=1%3A2.6.4-3%2Bb2=1711452552=0
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
-I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
-Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
-Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
-Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
-Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
-Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
-Werror=int-conversion -Werror=incompatible-pointer-types
-Werror=misleading-indentation -Wno-cast-function-type -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -c xml.c -fPIC -DPIC -o .libs/xml.o
export-cache.c: In function ‘junction_flush_exports_cache’:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
110 | snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
| ~~^ ~~~
| | |
| | time_t {aka
long long int}
| long int
| %lld
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
-I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
-Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
-Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
-Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
-Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
-Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
-Werror=int-conversion -Werror=incompatible-pointer-types
-Werror=misleading-indentation -Wno-cast-function-type -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -c display.c -o display.o >/dev/null 2>&1
cc1: some warnings being treated as errors
make[3]: *** [Makefile:489: export-cache.lo] Error 1
make[3]: *** Waiting for unfinished jobs
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: nfs-utils
Source-Version: 1:2.6.4-4
Done: Salvatore Bonaccorso
We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Salvatore Bonaccorso (supplier of updated nfs-utils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 07 Apr 2024 07:01:47 +0200
Source: nfs-utils
Architecture: source
Version: 1:2.6.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
Hello, On Sat 06 Apr 2024 at 09:30pm +02, Sebastian Andrzej Siewior wrote: > On 2024-04-06 17:17:45 [+0800], Sean Whitton wrote: >> Hello, > Hi, > >> It looks like the problem is opening YAPET1.0-format databases, which >> the manpage explicitly says is meant to work. >> >> I've made a sample YAPET1.0 database using a stretch VM. Using the >> attached: >> >> - On bookworm, invoke 'yapet yapet1.0.pet', and you can decrypt it. >> - On stable or on bookworm with libssl3/3.0.13-1~deb12u1, you can't. > > Thank you for the testcase. It asks for a password, what is it? Sorry! It's 'asdf'. -- Sean Whitton
Processed: Re: Bug#1066763: liferea: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Processing control commands:
> notfixed -1 1.15.5-1
Bug #1066763 {Done: Paul Gevers } [src:liferea] liferea:
FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose"
VERBOSE=1 returned exit code 2
No longer marked as fixed in versions 1.15.5-1.
--
1066763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066763: liferea: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
control: notfixed -1 1.15.5-1 On 04-04-2024 6:04 p.m., Paul Gevers wrote: So, marking the bug as not affecting the version in testing to avoid autoremoval. And also removing the fixed version. There was only a *time* that liferea was broken (by liblzma), not a version of liferea, nor was there a version that fixed the problem. Otherwise the BTS still thinks that the version in testing is affected and our tools schedule an autoremoval. Because of the time_t transition, liferea in unstable can't migrate soon. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1066630: marked as done (libnet-ldapapi-perl: FTBFS: LDAPapi.c:624:18: error: implicit declaration of function ‘ldap_bind_s’ [-Werror=implicit-function-declaration])
Your message dated Sun, 07 Apr 2024 04:21:09 + with message-id and subject line Bug#1066630: fixed in libnet-ldapapi-perl 3.0.7-4 has caused the Debian Bug report #1066630, regarding libnet-ldapapi-perl: FTBFS: LDAPapi.c:624:18: error: implicit declaration of function ‘ldap_bind_s’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnet-ldapapi-perl Version: 3.0.7-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > x86_64-linux-gnu-gcc -c -I/usr/include -I/usr/include/sasl -I/usr/include > -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe > -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -DVERSION=\"3.0.7\" -DXS_VERSION=\"3.0.7\" -fPIC > "-I/usr/lib/x86_64-linux-gnu/perl/5.38/CORE" -DOPENLDAP LDAPapi.c > LDAPapi.c: In function ‘XS_Net__LDAPapi_ldap_bind_s’: > LDAPapi.c:624:18: error: implicit declaration of function ‘ldap_bind_s’ > [-Werror=implicit-function-declaration] > 624 | RETVAL = ldap_bind_s(ldp, dn, passwd, authmethod); > | ^~~ > LDAPapi.xs: In function ‘XS_Net__LDAPapi_ldap_search_s’: > LDAPapi.xs:487:17: error: implicit declaration of function ‘ldap_search_s’; > did you mean ‘ldap_search_ext’? [-Werror=implicit-function-declaration] > 487 |RETVAL = ldap_search_s(ldp, base, scope, filter, attrs, > attrsonly, ); > | ^ > | ldap_search_ext > LDAPapi.c: In function ‘XS_Net__LDAPapi_ldap_perror’: > LDAPapi.c:2402:9: error: implicit declaration of function ‘ldap_perror’; did > you mean ‘ldap_destroy’? [-Werror=implicit-function-declaration] > 2402 | ldap_perror(ld, s); > | ^~~ > | ldap_destroy > LDAPapi.xs: In function ‘XS_Net__LDAPapi_ldap_explode_dn’: > LDAPapi.xs:1349:11: error: implicit declaration of function > ‘ldap_value_free’; did you mean ‘ldap_value_free_len’? > [-Werror=implicit-function-declaration] > 1349 | ldap_value_free(LDAPGETVAL); > | ^~~ > | ldap_value_free_len > LDAPapi.xs: In function ‘XS_Net__LDAPapi_ldap_sort_entries’: > LDAPapi.xs:1674:17: error: implicit declaration of function > ‘ldap_sort_entries’; did you mean ‘ldap_count_entries’? > [-Werror=implicit-function-declaration] > 1674 |RETVAL = ldap_sort_entries(ld,,attr,StrCaseCmp); > | ^ > | ldap_count_entries > cc1: some warnings being treated as errors > make[1]: *** [Makefile:343: LDAPapi.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/libnet-ldapapi-perl_3.0.7-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libnet-ldapapi-perl Source-Version: 3.0.7-4 Done: Russ Allbery We believe that the bug you reported is fixed in the latest version of libnet-ldapapi-perl, 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
Bug#1066346: sc: FTBFS: sc.c:1301:46: error: implicit declaration of function ‘list_frames’; did you mean ‘list_ranges’? [-Werror=implicit-function-declaration]
Hi, I've fixed the bug. And I'll do NMU if no one object in 10 days. I'll upload it to the delay/10 queue. Attachment is the debdiff. Please review it. Yours, Paul diff -Nru sc-7.16/debian/changelog sc-7.16/debian/changelog --- sc-7.16/debian/changelog2022-01-26 01:22:23.0 +0800 +++ sc-7.16/debian/changelog2024-04-07 09:47:51.0 +0800 @@ -1,3 +1,11 @@ +sc (7.16-4.2) unstable; urgency=low + + * Non-maintainer upload. + * Fix FTBFS by -Werror=implicit-function-declaration (Closes: #1066346) +- Add debian/patches/fix-ftbfs-implicit-function-declaration.patch + + -- Ying-Chun Liu (PaulLiu) Sun, 07 Apr 2024 09:47:51 +0800 + sc (7.16-4.1) unstable; urgency=low [ Ying-Chun Liu (PaulLiu) ] diff -Nru sc-7.16/debian/patches/fix-ftbfs-implicit-function-declaration.patch sc-7.16/debian/patches/fix-ftbfs-implicit-function-declaration.patch --- sc-7.16/debian/patches/fix-ftbfs-implicit-function-declaration.patch 1970-01-01 08:00:00.0 +0800 +++ sc-7.16/debian/patches/fix-ftbfs-implicit-function-declaration.patch 2024-04-07 09:47:51.0 +0800 @@ -0,0 +1,27 @@ +Description: fix ftbfs caused by -Werror=implicit-function-declaration + For dpkg >= 1.22.6, -Werror=implicit-function-declaration is turned + on by default. So we need to declare every functions. +Bug-Debian: http://bugs.debian.org/1066346 +Author: Ying-Chun Liu (PaulLiu) +Last-Update: 2024-04-07 +Index: sc-7.16/sc.h +=== +--- sc-7.16.orig/sc.h sc-7.16/sc.h +@@ -641,3 +641,16 @@ void leftlimit(); + void rightlimit(); + void gototop(); + void gotobottom(); ++void list_frames(FILE *); ++void yankrow(int); ++void yankcol(int); ++void ljustify(int, int, int, int); ++void rjustify(int, int, int, int); ++void center(int, int, int, int); ++void gotonote(); ++void add_abbr(char *); ++void getframe(int); ++void getrange(char *, int); ++void doeval(struct enode *, char *, int, int, int); ++void doseval(struct enode *, int, int, int); ++void dogetkey(); diff -Nru sc-7.16/debian/patches/series sc-7.16/debian/patches/series --- sc-7.16/debian/patches/series 2022-01-26 00:34:21.0 +0800 +++ sc-7.16/debian/patches/series 2024-04-07 09:47:51.0 +0800 @@ -4,3 +4,4 @@ function_definitions nonotimeout.patch hardening +fix-ftbfs-implicit-function-declaration.patch OpenPGP_0x44173FA13D05.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: tags 1054822 patch
Processing commands for cont...@bugs.debian.org: > tags 1054822 patch Bug #1054822 [src:opam] opam: FTBFS: sed: can't read opam.install: No such file or directory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066620: marked as done (zzuf: FTBFS: zzat.c:482:32: error: implicit declaration of function ‘_IO_getc’ [-Werror=implicit-function-declaration])
Your message dated Sun, 07 Apr 2024 03:06:15 + with message-id and subject line Bug#1066620: fixed in zzuf 0.15-3 has caused the Debian Bug report #1066620, regarding zzuf: FTBFS: zzat.c:482:32: error: implicit declaration of function ‘_IO_getc’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zzuf Version: 0.15-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -DLIBDIR=\"/usr/lib/x86_64-linux-gnu/zzuf\" -I./common -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -std=c99 -g -O2 -Wall -W > -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow > -Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -c -o > util/zzuf-hex.o `test -f 'util/hex.c' || echo './'`util/hex.c > zzat.c: In function ‘run’: > zzat.c:482:32: error: implicit declaration of function ‘_IO_getc’ > [-Werror=implicit-function-declaration] > 482 | MY_FREAD(ch = (n = _IO_getc(f)), , (n != EOF)); > |^~~~ > zzat.c:310:9: note: in definition of macro ‘MY_FCALL’ > 310 | cmd; \ > | ^~~ > zzat.c:482:13: note: in expansion of macro ‘MY_FREAD’ > 482 | MY_FREAD(ch = (n = _IO_getc(f)), , (n != EOF)); > | ^~~~ > zzat.c:482:32: warning: nested extern declaration of ‘_IO_getc’ > [-Wnested-externs] > 482 | MY_FREAD(ch = (n = _IO_getc(f)), , (n != EOF)); > |^~~~ > zzat.c:310:9: note: in definition of macro ‘MY_FCALL’ > 310 | cmd; \ > | ^~~ > zzat.c:482:13: note: in expansion of macro ‘MY_FREAD’ > 482 | MY_FREAD(ch = (n = _IO_getc(f)), , (n != EOF)); > | ^~~~ > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -DLIBDIR=\"/usr/lib/x86_64-linux-gnu/zzuf\" -I./common -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -std=c99 -g -O2 -Wall -W > -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow > -Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -c -o > common/zzuf-random.o `test -f 'common/random.c' || echo './'`common/random.c > zzat.c:565:26: error: implicit declaration of function ‘__fseeko64’; did you > mean ‘fseeko64’? [-Werror=implicit-function-declaration] > 565 | MY_FSEEK(l = __fseeko64(f, l1, SEEK_CUR), > | ^~ > zzat.c:310:9: note: in definition of macro ‘MY_FCALL’ > 310 | cmd; \ > | ^~~ > zzat.c:565:13: note: in expansion of macro ‘MY_FSEEK’ > 565 | MY_FSEEK(l = __fseeko64(f, l1, SEEK_CUR), > | ^~~~ > zzat.c:565:26: warning: nested extern declaration of ‘__fseeko64’ > [-Wnested-externs] > 565 | MY_FSEEK(l = __fseeko64(f, l1, SEEK_CUR), > | ^~ > zzat.c:310:9: note: in definition of macro ‘MY_FCALL’ > 310 | cmd; \ > | ^~~ > zzat.c:565:13: note: in expansion of macro ‘MY_FSEEK’ > 565 | MY_FSEEK(l = __fseeko64(f, l1, SEEK_CUR), > | ^~~~ > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -DLIBDIR=\"/usr/lib/x86_64-linux-gnu/zzuf\" -I./common -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -std=c99 -g -O2 -Wall -W > -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow > -Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -c -o > common/zzuf-ranges.o `test -f 'common/ranges.c' || echo
Bug#1054822: opam: FTBFS: sed: can't read opam.install: No such file or directory
Hi, On Fri, Oct 27, 2023 at 09:42:50PM +0200, Lucas Nussbaum wrote: ; windows_unicode = false } ; instrument_with = [] } Actual targets: - _build/default/opam-installer.install - _build/default/opam.install Running[1]: (cd _build/default/src/client && /bin/sh -c 'git describe --exact HEAD || echo [dev]') > _build/default/src/client/git-describe 2> /dev/null Running[2]: (cd _build/default/src/client && /bin/sh -c 'git rev-parse --quiet --verify HEAD || echo .') > _build/default/src/client/git-sha 2> /dev/null sed -f process.sed opam.install > processed-opam.install sed: can't read opam.install: No such file or directory make[2]: *** [Makefile:166: processed-opam.install] Error 2 Just fyi, I have commited one patch to salsa: https://salsa.debian.org/ocaml-team/opam/-/commit/ce22a7ae844e4bb9266748beb23a6750afb3c3f6 It was the same with debdiff file. But there is one issue was unclear to me, see https://lists.debian.org/debian-ocaml-maint/2024/04/msg00028.html -- Regards, -- Bo YU diff -Nru opam-2.1.5/debian/changelog opam-2.1.5/debian/changelog --- opam-2.1.5/debian/changelog 2023-09-02 13:35:29.0 +0800 +++ opam-2.1.5/debian/changelog 2024-04-06 22:30:28.0 +0800 @@ -1,3 +1,10 @@ +opam (2.1.5-2) UNRELEASED; urgency=medium + + * Team upload. + * Add 0003-opam-dune-3.11.patch to fix ftbfs issue. (Closes: #1054822) + + -- Bo YU Sat, 06 Apr 2024 22:30:28 +0800 + opam (2.1.5-1) unstable; urgency=medium * Team upload diff -Nru opam-2.1.5/debian/patches/0003-opam-dune-3.11.patch opam-2.1.5/debian/patches/0003-opam-dune-3.11.patch --- opam-2.1.5/debian/patches/0003-opam-dune-3.11.patch 1970-01-01 08:00:00.0 +0800 +++ opam-2.1.5/debian/patches/0003-opam-dune-3.11.patch 2024-04-06 22:30:28.0 +0800 @@ -0,0 +1,20 @@ +Description: fix ftbfs due to opam-dune 3.11 +Origin: https://src.fedoraproject.org/rpms/opam/blob/rawhide/f/opam-dune-3.11.patch +Bug: https://bugs.debian.org/1054822 +Last-Update: 2024-04-05 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/Makefile b/Makefile +@@ -162,7 +162,10 @@ + $(DUNE) install --root . opam-$$p; \ + done + +-processed-%.install: %.install ++processed-opam.install: _build/default/opam.install ++ sed -f process.sed $^ > $@ ++ ++processed-opam-installer.install: _build/default/opam-installer.install + sed -f process.sed $^ > $@ + + install: processed-opam.install processed-opam-installer.install diff -Nru opam-2.1.5/debian/patches/series opam-2.1.5/debian/patches/series --- opam-2.1.5/debian/patches/series2023-09-02 13:35:29.0 +0800 +++ opam-2.1.5/debian/patches/series2024-04-06 22:30:28.0 +0800 @@ -1,2 +1,3 @@ 0001-Add-a-test-target.patch 0002-Use-HOME-env-variable-instead-of.patch +0003-opam-dune-3.11.patch signature.asc Description: PGP signature
Bug#1068526: samba-dsdb-modules dependencies unsatisfiable on 32-bit non-i386 architectures.
Package: samba-dsdb-modules Version: 2:4.19.5+dfsg-4 Tags: trixie, sid Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, samba-dsdb-modules depends on both libgpgme11 and libgpgme11t64. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports architectures). Ubuntu has already fixed this issue by removing the hardcoded dependency on libgpgme11 http://launchpadlibrarian.net/720831431/riseup-vpn_0.21.11+ds1-5build3_0.21.11+ds1-5ubuntu1.diff.gz While poking through the ubuntu changelog, I noticed another change that looks relavent (but non-rc) http://launchpadlibrarian.net/720831431/riseup-vpn_0.21.11+ds1-5build3_0.21.11+ds1-5ubuntu1.diff.gz
Bug#1067290: marked as done (pymeeus: FTBFS: FAILED tests/test_interpolation.py::test_interpolation_call - RuntimeError: I...)
Your message dated Sun, 07 Apr 2024 02:51:18 + with message-id and subject line Bug#1067290: fixed in pymeeus 0.5.12+dfsg1-1 has caused the Debian Bug report #1067290, regarding pymeeus: FTBFS: FAILED tests/test_interpolation.py::test_interpolation_call - RuntimeError: I... to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pymeeus Version: 0.5.11+dfsg1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules 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:305: python3.12 setup.py config > running config > I: pybuild base:305: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:305: /usr/bin/python3.12 setup.py build > running build > running build_py > file base.py (for module base) not found > creating /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Coordinates.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/__init__.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Minor.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Epoch.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/CurveFitting.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/JupiterMoons.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Venus.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Saturn.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Pluto.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Moon.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Sun.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/base.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Mars.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Neptune.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Earth.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Mercury.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Uranus.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Jupiter.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Angle.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > copying pymeeus/Interpolation.py -> > /<>/.pybuild/cpython3_3.12_pymeeus/build/pymeeus > file base.py (for module base) not found > I: pybuild base:305: /usr/bin/python3 setup.py build > running build > running build_py > file base.py (for module base) not found > creating /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Coordinates.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/__init__.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Minor.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Epoch.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/CurveFitting.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/JupiterMoons.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Venus.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Saturn.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Pluto.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Moon.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Sun.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/base.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Mars.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Neptune.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Earth.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus > copying pymeeus/Mercury.py -> > /<>/.pybuild/cpython3_3.11_pymeeus/build/pymeeus >
Processed: Bug#1067290 marked as pending in pymeeus
Processing control commands: > tag -1 pending Bug #1067290 [src:pymeeus] pymeeus: FTBFS: FAILED tests/test_interpolation.py::test_interpolation_call - RuntimeError: I... Added tag(s) pending. -- 1067290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067290: marked as pending in pymeeus
Control: tag -1 pending Hello, Bug #1067290 in pymeeus 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/pymeeus/-/commit/17a5c3310920d3f86bcdca25a033160598693ded Fix pytest 7.2+ support and FTBFS in test suite (Closes: #1067290) (this message was generated automatically) -- Greetings https://bugs.debian.org/1067290
Bug#1067916: FTBFS: tests failed
On Fri, Mar 29, 2024 at 12:13:57AM +0500, Andrey Rakhmatullin wrote: > Source: capnproto > Version: 1.0.1-3 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=capnproto=armhf=1.0.1-3%2Bb2=1711652087=0 Thank you for the bug report. I'm not able to reproduce the test failure when cross-building on amd64, so am in the process of triaging on a porter box. signature.asc Description: PGP signature
Bug#1068068: bobcat, time_t transition lead to apparent ABI break (was: Need rebootstrapping on armel and armhf).
On Wed, Apr 03, 2024 at 11:37:20AM +0200, Frank B. Brokken wrote: > Dear Peter Green, you wrote: > > > Also, the bootstrapping procedure is only required when icmake isn't > > > available ... > > Thanks for your bugreport: I'm about to update icmake so that the circular > dependency between bobcat and icmake is removed. Shortly after icmake's > update bobcat will also be updated. icmake 12.0.01-1 [1] has landed in the archive and is being chewed on by the buildds now [2]. Once it is installed on armhf and armel, I will trigger givebacks for bobcat. As noted in the icmake changelog, the icmake bootstrap was accomplished by vendoring in the bobcat sources. This interim measure seemed warranted to get the r-build-deps unstuck. The long-term approach will be addressed by a separate bobcat-source package (#1068510 [3]). Thank you for your help and patience with this one. tony [1] https://tracker.debian.org/news/1517256/accepted-icmake-120001-1-source-into-unstable/ [2] https://buildd.debian.org/status/package.php?p=icmake [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068510 signature.asc Description: PGP signature
Bug#1068068: marked as done (Need rebootstrapping on armel and armhf)
Your message dated Sat, 06 Apr 2024 21:37:44 + with message-id and subject line Bug#1068068: fixed in icmake 12.00.01-1 has caused the Debian Bug report #1068068, regarding Need rebootstrapping on armel and armhf 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.) -- 1068068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: icmake,libbobcat6 Severity: serious Tags: ftbfs As src:icmake B-D:libbobcat-dev, src:bobcat B-D:icmake, there seems to be zero packaging-level support for bootstrapping, the packages are not cross-buildable and the upstream bootstrapping instructions are too tedious, I'm filing this for visibility (as there are ~14 packages B-D:libbobcat-dev). -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: icmake Source-Version: 12.00.01-1 Done: tony mancill We believe that the bug you reported is fixed in the latest version of icmake, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated icmake 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, 06 Apr 2024 10:17:58 -0700 Source: icmake Architecture: source Version: 12.00.01-1 Distribution: unstable Urgency: medium Maintainer: Francesco Paolo Lovergine Changed-By: tony mancill Closes: 1051966 1068068 Changes: icmake (12.00.01-1) unstable; urgency=medium . [ Frank B. Brokken ] * New upstream version 12.00.01 * Remove the circular dependency between icmake and bobcat by vendoring in the bobcat sources. (Closes: #1068068, #1051966) This is a temporary measure to enable the bootstrap. The long-term solution is to create an arch-all bobcat-sources package that both icmake and bobcat will use as a build-dep. * The icmake manpages are now part of the upstream distribution, avoiding yet another circular build-time dependency on Yodl. Sources for these manpages are still available in the source package. . [ tony mancill ] * Exclude /usr/share/icmake/bobcat.tgz from the icmake binary package. Checksums-Sha1: ad99a12f5fcb1f8f615e8aff056e1fc153b2048b 2003 icmake_12.00.01-1.dsc 8dc37a5de08e64c484141175953a225f13e9fd73 620574 icmake_12.00.01.orig.tar.gz b1ee3f79967bf740ca1a3ee2e85c3efc0c84b861 9060 icmake_12.00.01-1.debian.tar.xz a800b66a7988d3fc6355ba8efeda0eb517a58499 6228 icmake_12.00.01-1_amd64.buildinfo Checksums-Sha256: a199b533d45de67c58380e79ee52e8a533e25dc263e6959cf0a4ff3f94707bbf 2003 icmake_12.00.01-1.dsc a281a725dd77a95b448b2044f5f6cefdedcc48f5e1e895addeafdd76f205ff3f 620574 icmake_12.00.01.orig.tar.gz 1df1e1e25668aaea0e7e3ed48d54903373d58ce4abc31e6eefac0f409aa66efd 9060 icmake_12.00.01-1.debian.tar.xz 9ab61f82bef9f7afc7a26a2ba540503c467850d4c11014e1578a93d81884ce86 6228 icmake_12.00.01-1_amd64.buildinfo Files: afaa399846efe0230b5d29d19deb1bab 2003 devel optional icmake_12.00.01-1.dsc 0b021db6fd9d9884820d6ab07b71a9aa 620574 devel optional icmake_12.00.01.orig.tar.gz e49235b5b6fdc50f01da2396c805dc3a 9060 devel optional icmake_12.00.01-1.debian.tar.xz f467f2a805699ccebd0452b8f7e215e0 6228 devel optional icmake_12.00.01-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmYRu/8UHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpa+RBAAz3F0Ygc4WF7xJu8FGNDHfQi/0X6M nFX6XwSKaIX/KCk7MNK59v46kOM/HHoSSTHdjp/qFWSPB6PYru+fBCUdjEyk6Ke5 ghmiZcxqboLLJVvsfT+ewcBU8M1VH/3QZ0Xwd8V6gE+N4xi5/+PRKFqEsabQbYxY
Bug#1067321: marked as done (cachy: 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, 6 Apr 2024 18:23:51 -0300
with message-id <655eb736-4a34-40e1-a15c-e11d1d962...@yaerobi.com>
and subject line cachy: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
has caused the Debian Bug report #1067321,
regarding cachy: 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.)
--
1067321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cachy
Version: 0.3.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules 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:305: python3.12 setup.py config
> I: pybuild base:305: python3.11 setup.py config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> I: pybuild base:305: /usr/bin/python3 setup.py build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.12_cachy/build;
> python3.12 -m pytest --ignore=tests/stores/test_memcached_store.py
> = test session starts
> ==
> platform linux -- Python 3.12.2, pytest-8.1.1, pluggy-1.4.0
> rootdir: /<>/.pybuild/cpython3_3.12_cachy/build
> configfile: pyproject.toml
> plugins: mock-3.12.0
> collected 10 items / 5 errors
>
> ERRORS
>
> ___ ERROR collecting tests/stores/test_dict_store.py
> ___
> tests/stores/test_dict_store.py:4: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> ___ ERROR collecting tests/stores/test_file_store.py
> ___
> tests/stores/test_file_store.py:10: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> _ ERROR collecting tests/test_cache_manager.py
> _
> tests/test_cache_manager.py:6: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> __ ERROR collecting tests/test_repository.py
> ___
> tests/test_repository.py:5: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> _ ERROR collecting tests/test_tagged_cache.py
> __
> tests/test_tagged_cache.py:10: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> === short test summary info
>
> ERROR tests/stores/test_dict_store.py - AttributeError: module
> '_pytest.runne...
> ERROR
Bug#1067321: marked as done (cachy: 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, 6 Apr 2024 17:56:03 -0300
with message-id <4080bf9e-5d31-4f44-8837-110e79b2a...@debian.org>
and subject line cachy: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
has caused the Debian Bug report #1067321,
regarding cachy: 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.)
--
1067321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cachy
Version: 0.3.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules 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:305: python3.12 setup.py config
> I: pybuild base:305: python3.11 setup.py config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> I: pybuild base:305: /usr/bin/python3 setup.py build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.12_cachy/build;
> python3.12 -m pytest --ignore=tests/stores/test_memcached_store.py
> = test session starts
> ==
> platform linux -- Python 3.12.2, pytest-8.1.1, pluggy-1.4.0
> rootdir: /<>/.pybuild/cpython3_3.12_cachy/build
> configfile: pyproject.toml
> plugins: mock-3.12.0
> collected 10 items / 5 errors
>
> ERRORS
>
> ___ ERROR collecting tests/stores/test_dict_store.py
> ___
> tests/stores/test_dict_store.py:4: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> ___ ERROR collecting tests/stores/test_file_store.py
> ___
> tests/stores/test_file_store.py:10: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> _ ERROR collecting tests/test_cache_manager.py
> _
> tests/test_cache_manager.py:6: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> __ ERROR collecting tests/test_repository.py
> ___
> tests/test_repository.py:5: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> _ ERROR collecting tests/test_tagged_cache.py
> __
> tests/test_tagged_cache.py:10: in
> from flexmock import flexmock
> /usr/lib/python3/dist-packages/flexmock/__init__.py:2: in
> from flexmock import _integrations # pylint: disable=unused-import
> /usr/lib/python3/dist-packages/flexmock/_integrations.py:101: in
> saved_pytest = runner.call_runtest_hook
> E AttributeError: module '_pytest.runner' has no attribute
> 'call_runtest_hook'
> === short test summary info
>
> ERROR tests/stores/test_dict_store.py - AttributeError: module
> '_pytest.runne...
> ERROR
Bug#1064192: marked as done (openrefine: CVE-2024-23833)
Your message dated Sat, 06 Apr 2024 20:37:30 + with message-id and subject line Bug#1064192: fixed in openrefine 3.7.8-1 has caused the Debian Bug report #1064192, regarding openrefine: CVE-2024-23833 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.) -- 1064192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openrefine Version: 3.7.7-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for openrefine. Markus, please adjust severity if you think grave/RC severity is not appropriate. openrefine updates were batches previously as well just in point release, that might be enough here as well. CVE-2024-23833[0]: | OpenRefine is a free, open source power tool for working with messy | data and improving it. A jdbc attack vulnerability exists in | OpenRefine(version<=3.7.7) where an attacker may construct a JDBC | query which may read files on the host filesystem. Due to the newer | MySQL driver library in the latest version of OpenRefine (8.0.30), | there is no associated deserialization utilization point, so | original code execution cannot be achieved, but attackers can use | this vulnerability to read sensitive files on the target server. | This issue has been addressed in version 3.7.8. Users are advised to | upgrade. There are no known workarounds for this vulnerability. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-23833 https://www.cve.org/CVERecord?id=CVE-2024-23833 [1] https://github.com/OpenRefine/OpenRefine/security/advisories/GHSA-6p92-qfqf-qwx4 [2] https://github.com/OpenRefine/OpenRefine/commit/41ccf574847d856e22488a7c0987ad8efa12a84a Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: openrefine Source-Version: 3.7.8-1 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of openrefine, 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 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated openrefine 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, 06 Apr 2024 21:45:36 +0200 Source: openrefine Architecture: source Version: 3.7.8-1 Distribution: unstable Urgency: high Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 1064192 Changes: openrefine (3.7.8-1) unstable; urgency=high . * New upstream version 3.7.8 - Fix CVE-2024-23833: A jdbc attack vulnerability exists in OpenRefine where an attacker may construct a JDBC query which may read files on the host filesystem. (Closes: #1064192) Thanks to Salvatore Bonaccorso for the report. Checksums-Sha1: db1ea80492009c7f88022b910aa0d0f569fb9dc7 3613 openrefine_3.7.8-1.dsc 13d0d733d33971054fa7871f5f7c7dd9452670a2 4288064 openrefine_3.7.8.orig.tar.xz b3e70722ffd02b68caf7d650281a49c1e2b3e254 309112 openrefine_3.7.8-1.debian.tar.xz 16c43d96f6fe57d6f2bf869d9d9b528b741179a6 19133 openrefine_3.7.8-1_amd64.buildinfo Checksums-Sha256: 0a9fbb24aa4a25d676370fb9043bb77ef8777982d2b3222486f8759e4f5dbd9c 3613 openrefine_3.7.8-1.dsc 7d79bc097c47d7fe1aae4f14c72a96a5a954f2423f13d5805b88e6e54fd73b36 4288064 openrefine_3.7.8.orig.tar.xz 7b9718dc85bf8a51bb81598bef739233a11d28294f0e1d2d5fd362bcf089f9f8 309112 openrefine_3.7.8-1.debian.tar.xz 109398ee7b162bdfa5f1f462394bdd8b2c6ea93f74edf7327c8d0e2f02b0f4c6 19133 openrefine_3.7.8-1_amd64.buildinfo Files: bb8e95ddf713492ab47fc311d3b6c94e 3613 java optional openrefine_3.7.8-1.dsc 9d8c0ccd036a61609d402d99cf6c0503 4288064 java optional openrefine_3.7.8.orig.tar.xz ebf7337b97b7bbceb84f48c4585eff0e 309112 java optional openrefine_3.7.8-1.debian.tar.xz aae95b881f31b05963a9f681a10c31d7 19133 java optional openrefine_3.7.8-1_amd64.buildinfo -BEGIN PGP
Bug#1068513: dablin: FTBFS on arm{el,hf}: manually disables mpg123's large file API
Source: dablin Version: 1.15.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=dablin=armel=1.15.0-1%2Bb2=1712391165=0 [ 97%] Linking CXX executable dablin cd /<>/obj-arm-linux-gnueabi/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/dablin.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -pie -z now -rdynamic CMakeFiles/dablin.dir/sdl_output.cpp.o CMakeFiles/dablin.dir/dabplus_decoder.cpp.o CMakeFiles/dablin.dir/ensemble_source.cpp.o CMakeFiles/dablin.dir/ensemble_player.cpp.o CMakeFiles/dablin.dir/edi_source.cpp.o CMakeFiles/dablin.dir/edi_player.cpp.o CMakeFiles/dablin.dir/eti_source.cpp.o CMakeFiles/dablin.dir/eti_player.cpp.o CMakeFiles/dablin.dir/dab_decoder.cpp.o CMakeFiles/dablin.dir/fic_decoder.cpp.o CMakeFiles/dablin.dir/pcm_output.cpp.o CMakeFiles/dablin.dir/tools.cpp.o CMakeFiles/dablin.dir/version.cpp.o CMakeFiles/dablin.dir/dablin.cpp.o -o dablin ../fec/libfec.a /usr/lib/arm-linux-gnueabi/libatomic.so.1 -lmpg123 -lSDL2 -lfaad -lc -lm /usr/bin/ld: CMakeFiles/dablin.dir/dab_decoder.cpp.o: in function `MP2Decoder::DecodeFrame(unsigned char**)': ./obj-arm-linux-gnueabi/src/./src/dab_decoder.cpp:166:(.text+0x1bb4): undefined reference to `mpg123_framebyframe_decode' collect2: error: ld returned 1 exit status make[3]: *** [src/CMakeFiles/dablin.dir/build.make:313: src/dablin] Error 1 make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi' make[2]: *** [CMakeFiles/Makefile2:263: src/CMakeFiles/dablin.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs [100%] Linking CXX executable dablin_gtk cd /<>/obj-arm-linux-gnueabi/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/dablin_gtk.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -pie -z now -rdynamic CMakeFiles/dablin_gtk.dir/sdl_output.cpp.o CMakeFiles/dablin_gtk.dir/dabplus_decoder.cpp.o CMakeFiles/dablin_gtk.dir/ensemble_source.cpp.o CMakeFiles/dablin_gtk.dir/ensemble_player.cpp.o CMakeFiles/dablin_gtk.dir/edi_source.cpp.o CMakeFiles/dablin_gtk.dir/edi_player.cpp.o CMakeFiles/dablin_gtk.dir/eti_source.cpp.o CMakeFiles/dablin_gtk.dir/eti_player.cpp.o CMakeFiles/dablin_gtk.dir/dab_decoder.cpp.o CMakeFiles/dablin_gtk.dir/fic_decoder.cpp.o CMakeFiles/dablin_gtk.dir/pcm_output.cpp.o CMakeFiles/dablin_gtk.dir/tools.cpp.o CMakeFiles/dablin_gtk.dir/version.cpp.o CMakeFiles/dablin_gtk.dir/mot_manager.cpp.o CMakeFiles/dablin_gtk.dir/pad_decoder.cpp.o CMakeFiles/dablin_gtk.dir/dablin_gtk.cpp.o CMakeFiles/dablin_gtk.dir/dablin_gtk_dl_plus.cpp.o CMakeFiles/dablin_gtk.dir/dablin_gtk_sls.cpp.o -o dablin_gtk ../fec/libfec.a /usr/lib/arm-linux-gnueabi/libatomic.so.1 -lmpg123 -lSDL2 -lfaad -lc -lgtkmm-3.0 -latkmm-1.6 -lgdkmm-3.0 -lgiomm-2.4 -lgtk-3 -lgdk-3 -lz -latk-1.0 -lcairo-gobject -lgio-2.0 -lpangomm-1.4 -lglibmm-2.4 -lcairomm-1.0 -lsigc-2.0 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -lcairo -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lm /usr/bin/ld: CMakeFiles/dablin_gtk.dir/dab_decoder.cpp.o: in function `MP2Decoder::DecodeFrame(unsigned char**)': ./obj-arm-linux-gnueabi/src/./src/dab_decoder.cpp:166:(.text+0x1bb4): undefined reference to `mpg123_framebyframe_decode' collect2: error: ld returned 1 exit status make[3]: *** [src/CMakeFiles/dablin_gtk.dir/build.make:377: src/dablin_gtk] Error 1 This is caused by #define MPG123_NO_LARGENAME // disable large file API here in src/dab_decoder.h Cheers -- Sebastian Ramacher
Processed: fixed 1068100 in 0.3.1~beta-7.1
Processing commands for cont...@bugs.debian.org:
> fixed 1068100 0.3.1~beta-7.1
Bug #1068100 {Done: Drew Parsons } [src:armci-mpi]
armci-mpi: autopkgtest spuriously fails
Marked as fixed in versions armci-mpi/0.3.1~beta-7.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068512: welle.io: FTBFS on arm{el,hf}: manually disables mpg123's LFS API
Source: welle.io Version: 2.4+ds-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=welle.io=armel=2.4%2Bds-2%2Bb3=1712391447=0 [ 99%] Linking CXX executable welle-io /usr/bin/cmake -E cmake_link_script CMakeFiles/welle-io.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -rdynamic "CMakeFiles/welle-io.dir/welle-io_autogen/mocs_compilation.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/main.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/audio_output.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/mot_image_provider.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/gui_helper.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/radio_controller.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/mpris/mpris.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/mpris/mpris_mp2.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/mpris/mpris_mp2_player.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/debug_output.cpp.o" "CMakeFiles/welle-io.dir/src/welle-gui/waterfallitem.cpp.o" "CMakeFiles/welle-io.dir/src/backend/dab-audio.cpp.o" "CMakeFiles/welle-io.dir/src/backend/decoder_adapter.cpp.o" "CMakeFiles/welle-io.dir/src/backend/dab_decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/dabplus_decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/charsets.cpp.o" "CMakeFiles/welle-io.dir/src/backend/dab-constants.cpp.o" "CMakeFiles/welle-io.dir/src/backend/mot_manager.cpp.o" "CMakeFiles/welle-io.dir/src/backend/pad_decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/eep-protection.cpp.o" "CMakeFiles/welle-io.dir/src/backend/fib-processor.cpp.o" "CMakeFiles/welle-io.dir/src/backend/fic-handler.cpp.o" "CMakeFiles/welle-io.dir/src/backend/msc-handler.cpp.o" "CMakeFiles/welle-io.dir/src/backend/freq-interleaver.cpp.o" "CMakeFiles/welle-io.dir/src/backend/ofdm-decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/ofdm-processor.cpp.o" "CMakeFiles/welle-io.dir/src/backend/phasereference.cpp.o" "CMakeFiles/welle-io.dir/src/backend/phasetable.cpp.o" "CMakeFiles/welle-io.dir/src/backend/tii-decoder.cpp.o" "CMakeFiles/welle-io.dir/src/backend/protTables.cpp.o" "CMakeFiles/welle-io.dir/src/backend/radio-receiver.cpp.o" "CMakeFiles/welle-io.dir/src/backend/tools.cpp.o" "CMakeFiles/welle-io.dir/src/backend/uep-protection.cpp.o" "CMakeFiles/welle-io.dir/src/backend/viterbi.cpp.o" "CMakeFiles/welle-io.dir/src/various/Socket.cpp.o" "CMakeFiles/welle-io.dir/src/various/Xtan2.cpp.o" "CMakeFiles/welle-io.dir/src/various/channels.cpp.o" "CMakeFiles/welle-io.dir/src/various/fft.cpp.o" "CMakeFiles/welle-io.dir/src/various/profiling.cpp.o" "CMakeFiles/welle-io.dir/src/various/wavfile.c.o" "CMakeFiles/welle-io.dir/src/libs/fec/decode_rs_char.c.o" "CMakeFiles/welle-io.dir/src/libs/fec/encode_rs_char.c.o" "CMakeFiles/welle-io.dir/src/libs/fec/init_rs_char.c.o" "CMakeFiles/welle-io.dir/src/input/input_factory.cpp.o" "CMakeFiles/welle-io.dir/src/input/null_device.cpp.o" "CMakeFiles/welle-io.dir/src/input/raw_file.cpp.o" "CMakeFiles/welle-io.dir/src/input/rtl_tcp.cpp.o" "CMakeFiles/welle-io.dir/src/input/rtl_sdr.cpp.o" "CMakeFiles/welle-io.dir/src/input/airspy_sdr.cpp.o" "CMakeFiles/welle-io.dir/src/input/soapy_sdr.cpp.o" "CMakeFiles/welle-io.dir/welle-io_autogen/MOX6SOXE6H/qrc_resources.cpp.o" -o welle-io -lrtlsdr -lairspy -lfftw3f -lfaad /usr/lib/arm-linux-gnueabi/libSoapySDR.so.0.8.1 -lmpg123 /usr/lib/arm-linux-gnueabi/libQt5Multimedia.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Charts.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5QuickControls2.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5DBus.so.5.15.10 -pthread /usr/lib/arm-linux-gnueabi/libQt5Widgets.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Quick.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5QmlModels.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Qml.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Network.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Gui.so.5.15.10 /usr/lib/arm-linux-gnueabi/libQt5Core.so.5.15.10 /usr/bin/ld: CMakeFiles/welle-io.dir/src/backend/dab_decoder.cpp.o: in function `MP2Decoder::DecodeFrame(unsigned char**)': ./obj-arm-linux-gnueabi/./src/backend/dab_decoder.cpp:168:(.text+0x1c6c): undefined reference to `mpg123_framebyframe_decode' collect2: error: ld returned 1 exit status This is caused by #define MPG123_NO_LARGENAME // disable large file API here in src/dab_decoder.h Cheers -- Sebastian Ramacher
Bug#1068363: src:autopkgtest: flaky autopkgtest (host dependent?) on ppc64el
The mystery continues. On 04-04-2024 10:08 p.m., Paul Gevers wrote: I forgot that on amd64, autopkgtest's autopkgtest now runs in qemu which doesn't benefit yet as much from tmpfs as lxc does, so it's not a good comparison. On ci-worker13: """ root@elbrus:/tmp/autopkgtest-lxc.ww6f2cls/downtmp/build.VWV/src# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 250G 44G 207G 18% / none492K 4.0K 488K 1% /dev tmpfs 126G 0 126G 0% /dev/shm tmpfs51G 52K 51G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock root@elbrus:/tmp/autopkgtest-lxc.ww6f2cls/downtmp/build.VWV/src# AUTOPKGTEST_TEST_SCHROOT=testing-amd64-sbuild tests/autopkgtest SchrootRunner.test_copy_timeout test_copy_timeout (__main__.SchrootRunner.test_copy_timeout) handling copying timeout ... ok -- Ran 1 test in 5.768s OK """ So it's not only tmpfs. I ran the test on ci-worker-ppc64el-05 (no other tests were running at the time) with adapted timeout. If I reduce the current 3 sec copy-timeout to 1 sec the test passes (2 seconds is too long, only int allowed). If I try the same thing in the opposite direction on ci-worker13, raising to 4 seconds causes failure in the """self.assertLess(huge_size, 100)""", with bumping to 5 seconds fails in the same way. ci-worker13 was running quite some tests at the same time, not sure if that's related. Anyways, it looks like we could just lower the timeout to 1 second and hope were fine for some time to come. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1067829: Fails to build on arm{el,hf} with 64bit time_t: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We
> On Apr 6, 2024, at 3:15 PM, Salvatore Bonaccorso wrote:
>
> Hi Chuck, hi Steve,
>
> In Debian, as you might have heard there is a 64bit time_t
> transition[1] ongoing affecting the armel and armhf architectures.
> While doing so, nfs-utils was found to fail to build for those
> architectures after the switch, reported in Debian as [2]. Vladimir
> Petko from Ubuntu has as well filled it in [3].
>
> [1]: https://lists.debian.org/debian-devel-announce/2024/02/msg5.html
> [2]: https://bugs.debian.org/1067829
> [3]: https://bugzilla.kernel.org/show_bug.cgi?id=218540
>
> The report is full-quoted below.
>
> Vladimir Petko has created a patch in the bugzilla which I'm attaching
> here as well. If this is not an acceptable format due to missing
> Signed-off's I'm attaching a variant with a Suggested-by for Vladimir
> to properly credit the patch origin.
>
> Let me know if that works. I changed it slightly and only casting to
> long long, and made it almost checkpatch clean.
I suppose strftime(3) might be nicer, but this works.
Reviewed-by: Chuck Lever mailto:chuck.le...@oracle.com>>
> Regards,
> Salvatore
>
> - Forwarded message from Sebastian Ramacher -
>
> From: Sebastian Ramacher
> Resent-From: Sebastian Ramacher
> Reply-To: Sebastian Ramacher , 1067...@bugs.debian.org
> Date: Wed, 27 Mar 2024 11:02:25 +0100
> To: Debian Bug Tracking System
> Subject: Bug#1067829: nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51:
> error: format ‘%ld’ expects argument of
> type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’}
> [-Werror=format=]
> Delivered-To: sub...@bugs.debian.org
> Message-ID:
>
> Source: nfs-utils
> Version: 1:2.6.4-3
> 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=nfs-utils=armel=1%3A2.6.4-3%2Bb2=1711452552=0
>
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
> -I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
> -D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
> -Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
> -Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
> -Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
> -Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
> -Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
> -Werror=int-conversion -Werror=incompatible-pointer-types
> -Werror=misleading-indentation -Wno-cast-function-type -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -c xml.c -fPIC -DPIC -o .libs/xml.o
> export-cache.c: In function ‘junction_flush_exports_cache’:
> export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long
> int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
> 110 | snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
> | ~~^ ~~~
> | | |
> | | time_t {aka
> long long int}
> | long int
> | %lld
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
> -I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
> -D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
> -Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
> -Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
> -Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
> -Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
> -Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
> -Werror=int-conversion -Werror=incompatible-pointer-types
> -Werror=misleading-indentation -Wno-cast-function-type -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -c display.c -o display.o >/dev/null 2>&1
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:489: export-cache.lo] Error 1
> make[3]: *** Waiting for unfinished jobs
>
> Cheers
> --
> Sebastian Ramacher
>
> - End forwarded message -
> <0001-junction-export-cache-cast-to-a-type-with-a-known-si.patch>
--
Chuck Lever
Bug#1060977: marked as done (dfdatetime: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13)
Your message dated Sat, 06 Apr 2024 19:34:13 +
with message-id
and subject line Bug#1060977: fixed in dfdatetime 20240220-1
has caused the Debian Bug report #1060977,
regarding dfdatetime: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1060977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dfdatetime
Version: 20210509-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} run_tests.py"
> dh_auto_test
> I: pybuild base:305: python3.11 run_tests.py
> Using Python version 3.11.7 (main, Dec 8 2023, 14:22:46) [GCC 13.2.0]
> Checking availability and versions of dependencies.
>
> Checking availability and versions of test dependencies.
> [OK] mock version: 5.1.0
> [FAILURE] missing: pbr
> [FAILURE] missing: six
>
> E: pybuild pybuild:391: test: plugin custom failed with: exit code=1:
> python3.11 run_tests.py
> dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit
> code 13
The full build log is available from:
http://qa-logs.debian.net/2024/01/15/dfdatetime_20210509-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: dfdatetime
Source-Version: 20240220-1
Done: Sven Geuer
We believe that the bug you reported is fixed in the latest version of
dfdatetime, 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 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sven Geuer (supplier of updated dfdatetime package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 08 Mar 2024 22:19:02 +0100
Source: dfdatetime
Architecture: source
Version: 20240220-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Sven Geuer
Closes: 1060977
Changes:
dfdatetime (20240220-1) unstable; urgency=medium
.
* Team upload.
.
[ Sven Geuer ]
* Update d/watch to recognize new upstream versions again.
* New upstream version 20240220 (Closes: #1060977).
* Update d/copyright:
- Bump upstream's copyright years to 2024.
- Add missing copyright holders regarding debian/*.
* Update d/control:
- Fix lintian issue missing-prerequisite-for-pyproject-backend.
- Bump Standards-Version to 4.6.2.
- Apply 'wrap-and-sort -at'.
* Update d/rules:
- Drop override_dh_missing, 'dh_missing --fail-missing' is the default now.
- Replace override_dh_auto_install by execute_after_dh_auto_install.
.
[ Samuel Henrique ]
* d/copyright: Update upstream details
Checksums-Sha1:
4eb2b0e3fb05c873fe521f7cbb4361130bbc6b4d 2061 dfdatetime_20240220-1.dsc
67607487d027af9e1afdc7eff11857e6ee07efec 71040 dfdatetime_20240220.orig.tar.gz
89fc133c0cef4d42763bbdce9becacb0727a3537 3520
dfdatetime_20240220-1.debian.tar.xz
05d7c73d156e3308b27ac1b0232343fec5afb6d0 6995
dfdatetime_20240220-1_amd64.buildinfo
Checksums-Sha256:
21f94b6a7db92510b2b695875c703c831cff7fc29bd426ac92283f1a2d214488 2061
dfdatetime_20240220-1.dsc
43a3db9011c1bbb651e925413dfd84d5b8cf9a27d1834c0d39c41ab8938d4a1e 71040
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
On 2024-04-06 17:17:45 [+0800], Sean Whitton wrote: > Hello, Hi, > It looks like the problem is opening YAPET1.0-format databases, which > the manpage explicitly says is meant to work. > > I've made a sample YAPET1.0 database using a stretch VM. Using the > attached: > > - On bookworm, invoke 'yapet yapet1.0.pet', and you can decrypt it. > - On stable or on bookworm with libssl3/3.0.13-1~deb12u1, you can't. Thank you for the testcase. It asks for a password, what is it? Sebastian
Processed: bug 1067829 is forwarded to https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u
Processing commands for cont...@bugs.debian.org:
> forwarded 1067829
> https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Changed Bug forwarded-to-address to
'https://lore.kernel.org/linux-nfs/zhgfupxclzeoz...@eldamar.lan/T/#u' from
'https://bugzilla.kernel.org/show_bug.cgi?id=218540'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1067829
Processing commands for cont...@bugs.debian.org:
> tags 1067829 + confirmed pending
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Added tag(s) pending and confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067829: Fails to build on arm{el,hf} with 64bit time_t: export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-We
Hi Chuck, hi Steve,
In Debian, as you might have heard there is a 64bit time_t
transition[1] ongoing affecting the armel and armhf architectures.
While doing so, nfs-utils was found to fail to build for those
architectures after the switch, reported in Debian as [2]. Vladimir
Petko from Ubuntu has as well filled it in [3].
[1]: https://lists.debian.org/debian-devel-announce/2024/02/msg5.html
[2]: https://bugs.debian.org/1067829
[3]: https://bugzilla.kernel.org/show_bug.cgi?id=218540
The report is full-quoted below.
Vladimir Petko has created a patch in the bugzilla which I'm attaching
here as well. If this is not an acceptable format due to missing
Signed-off's I'm attaching a variant with a Suggested-by for Vladimir
to properly credit the patch origin.
Let me know if that works. I changed it slightly and only casting to
long long, and made it almost checkpatch clean.
Regards,
Salvatore
- Forwarded message from Sebastian Ramacher -
From: Sebastian Ramacher
Resent-From: Sebastian Ramacher
Reply-To: Sebastian Ramacher , 1067...@bugs.debian.org
Date: Wed, 27 Mar 2024 11:02:25 +0100
To: Debian Bug Tracking System
Subject: Bug#1067829: nfs-utils: FTBFS on arm{el,hf}: export-cache.c:110:51:
error: format ‘%ld’ expects argument of
type ‘long int’, but argument 4 has type ‘time_t’ {aka ‘long long int’}
[-Werror=format=]
Delivered-To: sub...@bugs.debian.org
Message-ID:
Source: nfs-utils
Version: 1:2.6.4-3
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=nfs-utils=armel=1%3A2.6.4-3%2Bb2=1711452552=0
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
-I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
-Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
-Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
-Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
-Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
-Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
-Werror=int-conversion -Werror=incompatible-pointer-types
-Werror=misleading-indentation -Wno-cast-function-type -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -c xml.c -fPIC -DPIC -o .libs/xml.o
export-cache.c: In function ‘junction_flush_exports_cache’:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
110 | snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
| ~~^ ~~~
| | |
| | time_t {aka
long long int}
| long int
| %lld
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../support/include
-I/usr/include/tirpc -I/usr/include/libxml2 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -pipe -Wall -Wextra -Werror=strict-prototypes
-Werror=missing-prototypes -Werror=missing-declarations -Werror=format=2
-Werror=undef -Werror=missing-include-dirs -Werror=strict-aliasing=2
-Werror=init-self -Werror=implicit-function-declaration -Werror=return-type
-Werror=switch -Werror=overflow -Werror=parentheses -Werror=aggregate-return
-Werror=unused-result -fno-strict-aliasing -Werror=format-overflow=2
-Werror=int-conversion -Werror=incompatible-pointer-types
-Werror=misleading-indentation -Wno-cast-function-type -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -c display.c -o display.o >/dev/null 2>&1
cc1: some warnings being treated as errors
make[3]: *** [Makefile:489: export-cache.lo] Error 1
make[3]: *** Waiting for unfinished jobs
Cheers
--
Sebastian Ramacher
- End forwarded message -
Description: cast to a type with a known size to ensure sprintf works
Author: Vladimir Petko
Bug: https://bugzilla.kernel.org/show_bug.cgi?id=218540
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2055349
Last-Update: 2024-02-29
--- a/support/junction/export-cache.c
+++ b/support/junction/export-cache.c
@@ -107,7 +107,7 @@
xlog(D_GENERAL, "%s: time(3) failed", __func__);
return FEDFS_ERR_SVRFAULT;
}
- snprintf(flushtime, sizeof(flushtime), "%ld\n", now);
+ snprintf(flushtime, sizeof(flushtime), "%lld\n", (long long int)now);
Processed: tagging 1067829
Processing commands for cont...@bugs.debian.org:
> tags 1067829 + upstream
Bug #1067829 [src:nfs-utils] nfs-utils: FTBFS on arm{el,hf}:
export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long int’,
but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error: symbol `open64' is already defined
Processing commands for cont...@bugs.debian.org:
> found 1065951 vde2/2.3.2+r586-9
Bug #1065951 [src:vde2] vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error:
symbol `open64' is already defined
Marked as found in versions vde2/2.3.2+r586-9.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1065951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066308: marked as done (click: FTBFS: clickpreload.c:422:16: error: implicit declaration of function ‘__fxstat’; did you mean ‘__xstat’? [-Werror=implicit-function-declaration])
Your message dated Sat, 06 Apr 2024 17:35:11 + with message-id and subject line Bug#1066308: fixed in python-whey 0.0.26-1 has caused the Debian Bug report #1066308, regarding click: FTBFS: clickpreload.c:422:16: error: implicit declaration of function ‘__fxstat’; did you mean ‘__xstat’? [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: click Version: 0.5.0-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -c -o clickpreload.lo > clickpreload.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -c clickpreload.c -fPIC -DPIC -o .libs/clickpreload.o > clickpreload.c: In function ‘__xstat’: > clickpreload.c:422:16: error: implicit declaration of function ‘__fxstat’; > did you mean ‘__xstat’? [-Werror=implicit-function-declaration] > 422 | return __fxstat (ver, package_fd, buf); > |^~~~ > |__xstat > clickpreload.c: In function ‘__xstat64’: > clickpreload.c:433:16: error: implicit declaration of function ‘__fxstat64’; > did you mean ‘__xstat64’? [-Werror=implicit-function-declaration] > 433 | return __fxstat64 (ver, package_fd, buf); > |^~ > |__xstat64 > cc1: some warnings being treated as errors > make[4]: *** [Makefile:467: clickpreload.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/click_0.5.0-10_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: python-whey Source-Version: 0.0.26-1 Done: Josenilson Ferreira da Silva We believe that the bug you reported is fixed in the latest version of python-whey, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josenilson Ferreira da Silva (supplier of updated python-whey 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, 06 Apr 2024 13:31:57 -0300 Source: python-whey Architecture: source Version: 0.0.26-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Josenilson Ferreira da Silva Closes: 1066308 Changes: python-whey (0.0.26-1) unstable; urgency=medium . * New upstream version 0.0.26 (closes:#1066308) * debian/manpage/whey.1: Version updade * debian/patches: Update with new version
Bug#1067936: marked as done (Explicitly depends on a pre-t64 library name)
Your message dated Sat, 06 Apr 2024 17:19:39 + with message-id and subject line Bug#1067936: fixed in libgsecuredelete 0.3-3.2 has caused the Debian Bug report #1067936, regarding Explicitly depends on a pre-t64 library name 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.) -- 1067936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgsecuredelete0 Version: 0.3-3.1 Severity: serious The package has explicit Depends: libglib2.0-0 which needs to be replaced with libglib2.0-0t64 if it's really needed and removed otherwise. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: libgsecuredelete Source-Version: 0.3-3.2 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of libgsecuredelete, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated libgsecuredelete 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, 06 Apr 2024 16:55:41 + Source: libgsecuredelete Architecture: source Version: 0.3-3.2 Distribution: unstable Urgency: medium Maintainer: Debian Privacy Tools Maintainers Changed-By: Bastian Germann Closes: 1067936 Changes: libgsecuredelete (0.3-3.2) unstable; urgency=medium . * Non-maintainer upload * Drop explicit Depends: libglib2.0-0 (Closes: #1067936) * Drop non-existing Homepage Checksums-Sha1: bbd05f4e479a21a31a166da8593664e1f5d443ec 2215 libgsecuredelete_0.3-3.2.dsc cd2c80502816c23c666b0bc163f16eeecbb62c90 8624 libgsecuredelete_0.3-3.2.debian.tar.xz 1c0256b4b2ad89a4b4b51ded63cc9856ab2fcd30 6635 libgsecuredelete_0.3-3.2_source.buildinfo Checksums-Sha256: a37df6eaea958945b4194572116ae00ecf2c334265680e4a9a08277be8a2ca9d 2215 libgsecuredelete_0.3-3.2.dsc 30fd6d7a592fc0c83357746f157f4f092efe1bf77bf05091b79e651a521f71f0 8624 libgsecuredelete_0.3-3.2.debian.tar.xz 7a932e3d0b393074876a4b36b9303f24fd785ab4774218fbfb745d32e9505d9a 6635 libgsecuredelete_0.3-3.2_source.buildinfo Files: 55dca3c916f112aa1b8395735ca0fecc 2215 gnome optional libgsecuredelete_0.3-3.2.dsc 59e9ad70fcab545d9125b50f6b9dee5e 8624 gnome optional libgsecuredelete_0.3-3.2.debian.tar.xz a493975928d679020407d28fb60742f3 6635 gnome optional libgsecuredelete_0.3-3.2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYRgR4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFAfmC/4s+e12309SvA7iuHwMqIlPgcRk4p5Xpujs 6vgq32XruTs4FXrLb5edeO1Uw71a8HjF97VxPu0msdtWl+D0LvfEe4wNXgMZTDOU GG5ZmH/t7GTH0bkwvV1dt2TbHEpZpNBt/f15J3+tNpFl/Ne8RRe1Fsm975vBZORq MiCUHg8swZxbdHqIv2vdV5wneO5K5prhj/K63IBP69LqKxQeBWyzoOkcE7Eos5uT HkpRiKyOkpYg6mIhaNaOCkWQz+lyGAMyV+poq2rUB51SfKUjaPYvF6y+ejuZGdmm RJa901Z6ayDThoKSn93I9Jnplqp8oFN8VT0f8RHfOGoMcSRo5dcIJ1tjqIWCeqDk HIJLVCUXaTiKMwqcbFq59IyA5Gh4CUhJIXnQqcVxidcS8h5NE3wfkudcmL5PW498 P5th0lQoVO7LY+5oqt+s0Pb+9snhFyZMw4pU3JcYPWSlLUbpLLT62oevE+HCtGCZ /UGMYlHyLiKqsXK4+Gb2VgNzMQYB6tQ= =+CCL -END PGP SIGNATURE- pgpR6dhXM4wiN.pgp Description: PGP signature --- End Message ---
Processed: tag ftbfs
Processing commands for cont...@bugs.debian.org: > tags 1064676 + ftbfs Bug #1064676 [src:android-platform-tools-apksig] android-platform-tools-apksig: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=android-platform-tools-apksig -Dfile.encoding=UTF-8 --parallel --max-workers=8 test returned exit code 1 Ignoring request to alter tags of bug #1064676 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1064676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Also happening in stable
Processing commands for cont...@bugs.debian.org:
> found 1064034 3.1.2-7
Bug #1064034 {Done: Chris Hofstaedtler } [src:ruby3.1] FTBFS:
Expired test certificate
Marked as found in versions ruby3.1/3.1.2-7.
> tags 1064034 + bookworm
Bug #1064034 {Done: Chris Hofstaedtler } [src:ruby3.1] FTBFS:
Expired test certificate
Added tag(s) bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1064034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Already happening in stable
Processing commands for cont...@bugs.debian.org: > tags 1056196 + bookworm trixie sid Bug #1056196 [src:python3-onelogin-saml2] python3-onelogin-saml2: Please package new version 1.16.0, as current version will FTBFS soon Added tag(s) sid, bookworm, and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Also happening in stable
Processing commands for cont...@bugs.debian.org:
> tags 1055877 + bookworm trixie sid
Bug #1055877 {Done: Ole Streicher } [src:ndcube] ndcube:
FTBFS in bookworm: leap-second file is expired
Added tag(s) sid, bookworm, and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1055877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: also happening in stable
Processing commands for cont...@bugs.debian.org: > found 1057544 2.4.0+dfsg-3 Bug #1057544 [src:barrier] barrier: FTBFS: failing test Marked as found in versions barrier/2.4.0+dfsg-3. > tags 1057544 + bookworm Bug #1057544 [src:barrier] barrier: FTBFS: failing test Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1057544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Also happening in stable
Processing commands for cont...@bugs.debian.org: > tags 1064676 + bookworm Bug #1064676 [src:android-platform-tools-apksig] android-platform-tools-apksig: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=android-platform-tools-apksig -Dfile.encoding=UTF-8 --parallel --max-workers=8 test returned exit code 1 Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066910: marked as done (chromium: downloads non-free component libchromescreenai.so without asking)
Your message dated Sat, 06 Apr 2024 16:32:10 + with message-id and subject line Bug#1066910: fixed in chromium 123.0.6312.86-1~deb12u1 has caused the Debian Bug report #1066910, regarding chromium: downloads non-free component libchromescreenai.so without asking 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.) -- 1066910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 122.0.6261.128-1 Severity: serious In recent versions, chromium started downloading a file ~/.config/chromium/screen_ai/*/libchromescreenai.so. Evidently, the source of this shared object is not in the chromium source package. I think the chromium package - being in main - should not download a shared object and run it without user confirmation. Helmut --- End Message --- --- Begin Message --- Source: chromium Source-Version: 123.0.6312.86-1~deb12u1 Done: Timothy Pearson We believe that the bug you reported is fixed in the latest version of chromium, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timothy Pearson (supplier of updated chromium 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: Thu, 28 Mar 2024 11:57:05 -0400 Source: chromium Architecture: source Version: 123.0.6312.86-1~deb12u1 Distribution: bookworm-security Urgency: high Maintainer: Debian Chromium Team Changed-By: Timothy Pearson Closes: 1066235 1066910 1067886 Changes: chromium (123.0.6312.86-1~deb12u1) bookworm-security; urgency=high . * New upstream stable release. - CVE-2024-2883: Use after free in ANGLE. Reported by Cassidy Kim(@cassidy6564). - CVE-2024-2885: Use after free in Dawn. Reported by wgslfuzz. - CVE-2024-2886: Use after free in WebCodecs. Reported by Seunghyun Lee (@0x10n) of KAIST Hacking Lab, via Pwn2Own 2024. - CVE-2024-2887: Type Confusion in WebAssembly. Reported by Manfred Paul, via Pwn2Own 2024. * d/patches/ppc64le: - fixes/fix-clang-selection.patch: select clang on ppc64 platforms - ppc64le/third_party/0001-Add-PPC64-support-for-boringssl.patch: fix ARM builds. . [ Andres Salomon ] * d/patches: - fixes/bad-font-gc1.patch, fixes/bad-font-gc2.patch: revert a pair of upstream commits that result in blink's garbage collector frequently deadlocking and crashing (closes: #1067886). . chromium (123.0.6312.58-1~deb12u1) bookworm-security; urgency=high . * New upstream stable release. - CVE-2024-2625: Object lifecycle issue in V8. Reported by Ganjiang Zhou(@refrain_areu) of ChaMd5-H1 team. - CVE-2024-2626: Out of bounds read in Swiftshader. Reported by Cassidy Kim(@cassidy6564). - CVE-2024-2627: Use after free in Canvas. Reported by Anonymous. - CVE-2024-2628: Inappropriate implementation in Downloads. Reported by Ath3r1s. - CVE-2024-2629: Incorrect security UI in iOS. Reported by Muneaki Nishimura (nishimunea). - CVE-2024-2630: Inappropriate implementation in iOS. Reported by James Lee (@Windowsrcer). - CVE-2024-2631: Inappropriate implementation in iOS. Reported by Ramit Gangwar. * d/patches: - upstream/bitset.patch: drop, merged upstream. - upstream/bookmarknode.patch: drop, merged upstream. - upstream/optional.patch: drop, merged upstream. - upstream/uniqptr.patch: drop, merged upstream. - fixes/gcc13-headers.patch: drop, merged upstream. - fixes/optional.patch: drop, merged upstream. - fixes/material-utils.patch: drop part that was merged upstream. - disable/catapult.patch: refresh. - bookworm/constexpr-equality.patch: include another similar fix. - bookworm/nvt.patch: refresh. - bookworm/undo-internal-alloc.patch: drop, as this was fixed upstream. - ungoogled/disable-privacy-sandbox.patch: update from ungoogled-chromium. - disable/angle-perftests.patch: drop, replace with a gn build argument. - bookworm/rust-downgrade-osstr-users.patch: add new patch
Bug#1066136: marked as done (python3-xapian-haystack: unusable on stable due to use of deprecated module django.utils.six)
Your message dated Sat, 06 Apr 2024 16:32:29 + with message-id and subject line Bug#1066136: fixed in python-xapian-haystack 2.1.1-1+deb12u1 has caused the Debian Bug report #1066136, regarding python3-xapian-haystack: unusable on stable due to use of deprecated module django.utils.six 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.) -- 1066136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-xapian-haystack Version: 2.1.1-1 Severity: grave Tags: upstream patch Justification: renders package unusable Dear Maintainer, I installed python3-xapian-haystack in order to employ Xapian as a Haystack backend in mailman3-web on stable (bookworm). However, upon actually trying to use it, I got the following traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py", line 54, in search results = EmptySearchQuerySet() File "/usr/lib/python3/dist-packages/haystack/query.py", line 25, in __init__ self._determine_backend() File "/usr/lib/python3/dist-packages/haystack/query.py", line 58, in _determine_backend self.query = connections[backend_alias].get_query() File "/usr/lib/python3/dist-packages/haystack/utils/loading.py", line 114, in __getitem__ self.thread_local.connections[key] = load_backend( File "/usr/lib/python3/dist-packages/haystack/utils/loading.py", line 60, in load_backend return import_class(full_backend_path) File "/usr/lib/python3/dist-packages/haystack/utils/loading.py", line 22, in import_class module_itself = importlib.import_module(module_path) File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1206, in _gcd_import File "", line 1178, in _find_and_load File "", line 1149, in _find_and_load_unlocked File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/xapian_backend.py", line 10, in from django.utils import six Exception Type: ImportError at /hyperkitty/search Exception Value: cannot import name 'six' from 'django.utils' (/usr/lib/python3/dist-packages/django/utils/__init__.py) django.utils.six was removed in Django 3.0; the version of Django in stable is 3.2. Hence python3-xapian-haystack is currently unusable in stable, as it simply throws an ImportError upon loading. Upstream fixed this issue when they dropped Python 2 support in [0]. However, I have a simpler patch that just removes the six import and changes all occurences of `six.moves.range()` to the built-in `range()`, which I've applied locally (hence the debsums complaint) and seems to do the trick. I would very much like a stable-update for this given that the package simply does not work without the patch. Many thanks, Ole [0]: https://github.com/notanumber/xapian-haystack/commit/0f9d94fb23ebf8cf194a3a88948a86f6dc69e786#diff-b4466d919fc4105c6306804abd396d6e0ba5e4630346928df34a5308c4700d97 -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.8 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_NO:en_DK:en_US:en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-xapian-haystack depends on: ii python3 3.11.2-1+b1 ii python3-django-haystack 3.2.1-1 ii python3-xapian 1.4.22-1 python3-xapian-haystack recommends no packages. python3-xapian-haystack suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /usr/lib/python3/dist-packages/xapian_backend.py (from python3-xapian-haystack package) --- xapian_backend.py 2017-05-18 08:50:23.0 +0200 +++ /usr/lib/python3/dist-packages/xapian_backend.py2024-03-12 01:06:33.011301452 +0100 @@ -7,7 +7,6 @@ import shutil import sys -from django.utils import six from django.conf
Processed: python-workalendar: FTBFS because of failing tests
Processing commands for cont...@bugs.debian.org:
> forwarded 1060939 https://github.com/workalendar/workalendar/issues/764
Bug #1060939 [src:python-workalendar] python-workalendar: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned
exit code 13
Set Bug forwarded-to-address to
'https://github.com/workalendar/workalendar/issues/764'.
> tags 1060939 + bookworm
Bug #1060939 [src:python-workalendar] python-workalendar: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned
exit code 13
Added tag(s) bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1060939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060939: python-workalendar: FTBFS because of failing tests
forwarded 1060939 https://github.com/workalendar/workalendar/issues/764 tags 1060939 + bookworm thanks
Processed: Re: opentracker: libowfat headers have moved
Processing control commands: > severity -1 serious Bug #1068449 [src:opentracker] opentracker: libowfat headers have moved Severity set to 'serious' from 'important' -- 1068449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066609: marked as done (yagiuda: FTBFS: input.c:60:9: error: implicit declaration of function ‘gets’; did you mean ‘fgets’? [-Werror=implicit-function-declaration])
Your message dated Sat, 06 Apr 2024 15:04:14 +
with message-id
and subject line Bug#1066609: fixed in yagiuda 1.19-11
has caused the Debian Bug report #1066609,
regarding yagiuda: FTBFS: input.c:60:9: error: implicit declaration of function
‘gets’; did you mean ‘fgets’? [-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yagiuda
Version: 1.19-10
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"yagiuda\" -DPACKAGE_TARNAME=\"yagiuda\"
> -DPACKAGE_VERSION=\"1.19\" -DPACKAGE_STRING=\"yagiuda\ 1.19\"
> -DPACKAGE_BUGREPORT=\"david.kir...@onetel.net\" -DPACKAGE_URL=\"\"
> -DPACKAGE=\"yagiuda\" -DVERSION=\"1.19\" -DHAVE_LIBM=1 -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_STDIO_H=1 -DHAVE_MATH_H=1 -DHAVE_ERRNO_H=1
> -DHAVE_STDLIB_H=1 -DHAVE_TIME_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_STRING_H=1
> -DHAVE_CTYPE_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_VALUES_H=1
> -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRUCT_STAT_ST_BLKSIZE=1
> -DHAVE_ST_BLKSIZE=1 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c -o output.o output.c
> input.c: In function ‘main’:
> input.c:60:9: error: implicit declaration of function ‘gets’; did you mean
> ‘fgets’? [-Werror=implicit-function-declaration]
>60 | gets(notes);
> | ^~~~
> | fgets
> input.c:64:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
>64 | scanf("%lf", );
> | ^~~~
> input.c:66:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
>66 | scanf("%lf", _f);
> | ^~~~
> input.c:68:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
>68 | scanf("%lf", _f);
> | ^~~~
> input.c:70:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
>70 | scanf("%lf", _f);
> | ^
> input.c:77:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
>77 | scanf("%c", _entry);
> | ^~~~
> input.c:78:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
>78 | scanf("%c", _entry);
> | ^~~~
> input.c:98:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
>98 | scanf("%d",);
> | ^
> input.c:106:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 106 | scanf("%lf",_step);
> | ^~
> input.c:118:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 118 | scanf("%c",);
> | ^
> input.c:119:9: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 119 | scanf("%c",);
> | ^
> input.c:123:17: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’ [-Wunused-result]
> 123 | scanf("%lf", );
> | ^~~
> input.c:132:17: warning: ignoring return value of ‘scanf’ declared with
> attribute ‘warn_unused_result’
Bug#1067794: marked as done (flask-login: FTBFS: failing tests)
Your message dated Sat, 06 Apr 2024 14:49:04 + with message-id and subject line Bug#1067794: fixed in flask-login 0.6.3-2 has caused the Debian Bug report #1067794, regarding flask-login: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:flask-login Version: 0.6.3-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild dh_auto_build -O--buildsystem=pybuild I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" module I: pybuild base:305: python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_flask-login * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/flask_login copying src/flask_login/__about__.py -> build/lib/flask_login copying src/flask_login/test_client.py -> build/lib/flask_login copying src/flask_login/login_manager.py -> build/lib/flask_login copying src/flask_login/mixins.py -> build/lib/flask_login copying src/flask_login/utils.py -> build/lib/flask_login copying src/flask_login/signals.py -> build/lib/flask_login copying src/flask_login/__init__.py -> build/lib/flask_login copying src/flask_login/config.py -> build/lib/flask_login running egg_info creating src/Flask_Login.egg-info writing src/Flask_Login.egg-info/PKG-INFO writing dependency_links to src/Flask_Login.egg-info/dependency_links.txt writing requirements to src/Flask_Login.egg-info/requires.txt writing top-level names to src/Flask_Login.egg-info/top_level.txt writing manifest file 'src/Flask_Login.egg-info/SOURCES.txt' reading manifest file 'src/Flask_Login.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'docs/_build' warning: no previously-included files matching '*.pyc' found anywhere in distribution adding license file 'LICENSE' writing manifest file 'src/Flask_Login.egg-info/SOURCES.txt' installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/flask_login copying build/lib/flask_login/__about__.py -> build/bdist.linux-x86_64/wheel/flask_login copying build/lib/flask_login/test_client.py -> build/bdist.linux-x86_64/wheel/flask_login copying build/lib/flask_login/login_manager.py -> build/bdist.linux-x86_64/wheel/flask_login copying build/lib/flask_login/mixins.py -> build/bdist.linux-x86_64/wheel/flask_login copying build/lib/flask_login/utils.py -> build/bdist.linux-x86_64/wheel/flask_login copying build/lib/flask_login/signals.py -> build/bdist.linux-x86_64/wheel/flask_login copying build/lib/flask_login/__init__.py -> build/bdist.linux-x86_64/wheel/flask_login copying build/lib/flask_login/config.py -> build/bdist.linux-x86_64/wheel/flask_login running install_egg_info Copying src/Flask_Login.egg-info to build/bdist.linux-x86_64/wheel/Flask_Login-0.6.3.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/Flask_Login-0.6.3.dist-info/WHEEL creating '/<>/.pybuild/cpython3_3.12_flask-login/.tmp-ouobfdbj/Flask_Login-0.6.3-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'flask_login/__about__.py' adding 'flask_login/__init__.py' adding 'flask_login/config.py' adding 'flask_login/login_manager.py' adding 'flask_login/mixins.py' adding 'flask_login/signals.py' adding 'flask_login/test_client.py' adding 'flask_login/utils.py' adding 'Flask_Login-0.6.3.dist-info/LICENSE' adding 'Flask_Login-0.6.3.dist-info/METADATA' adding 'Flask_Login-0.6.3.dist-info/WHEEL' adding 'Flask_Login-0.6.3.dist-info/top_level.txt' adding 'Flask_Login-0.6.3.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Successfully built Flask_Login-0.6.3-py3-none-any.whl I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with "installer" module I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" module I: pybuild base:305: python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir
Bug#1068100: marked as done (armci-mpi: autopkgtest spuriously fails)
Your message dated Sat, 06 Apr 2024 14:34:11 +
with message-id
and subject line Bug#1068100: fixed in armci-mpi
0.3.1-beta+git20221202.f1c4dae-1
has caused the Debian Bug report #1068100,
regarding armci-mpi: autopkgtest spuriously fails
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.)
--
1068100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: armci-mpi
Version: 0.3.1~beta-7
Severity: serious
Tags: patch upstream fixed-upstream
Forwarded: https://github.com/pmodels/armci-mpi/pull/47
Justification: Prevents mpich migration
Hello,
The test_mpi_indexed_gets test is currently failing spuriously
in debian unstable due to an uninitialized value, e.g.
https://ci.debian.net/packages/a/armci-mpi/testing/amd64/44486187/ ,
preventing the newer mpich version from migrating to unstable.
I have forwarded a fix to upstream
https://github.com/pmodels/armci-mpi/pull/47
which is already merged.
Unless somebody objects, I'll NMU it.
Samuel
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unreleased'),
(500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500,
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500,
'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 6.8.0 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
commit 80cc91748392aec9eced295eb531548a565dac0e
Author: Samuel Thibault
Date: Sat Mar 30 16:35:11 2024 +0100
tests/mpi/test_mpi_indexed_gets.c: Fix reception buffer initialization
loc_buf was completely uninitialized, while the second and third loop nests
are checking that the values are 1.0 + rank. With luck it would be zero, and
thus the actual - expected > 1e-10 check would pass (since the difference is
then negative). With less luck the check would spuriously fail for the part
that is not overwritten by the MPI_Get.
Signed-off-by: Samuel Thibault
commit 9c0f6b08ba706a7c2f3e74d325cfd2a010300108
Author: Samuel Thibault
Date: Sat Mar 30 16:38:58 2024 +0100
tests/mpi: Fix comparison of floating-double types
In case the actual value is zero and the expected value is positive, the
check would spuriously succeed.
Signed-off-by: Samuel Thibault
commit cd001a46801fed9f406ea57238a131b0a0e063fe
Author: Samuel Thibault
Date: Sat Mar 30 16:41:58 2024 +0100
tests/mpi/test_mpi_indexed_gets.c: Strengthen test
Now that it is fixed, we can make it actually perform strided accesses.
Signed-off-by: Samuel Thibault
diff --git a/tests/mpi/test_mpi_indexed_gets.c
b/tests/mpi/test_mpi_indexed_gets.c
index dc1bd9d..3570492 100644
--- a/tests/mpi/test_mpi_indexed_gets.c
+++ b/tests/mpi/test_mpi_indexed_gets.c
@@ -44,8 +44,10 @@ int main(int argc, char **argv) {
if (rank == 0)
printf("MPI RMA Strided Get Test:\n");
-for (i = 0; i < XDIM*YDIM; i++)
+for (i = 0; i < XDIM*YDIM; i++) {
*(win_buf + i) = 1.0 + rank;
+*(loc_buf + i) = 1.0 + rank;
+}
MPI_Win_create(win_buf, bufsize, 1, MPI_INFO_NULL, MPI_COMM_WORLD,
_win);
diff --git a/tests/mpi/test_mpi_accs.c b/tests/mpi/test_mpi_accs.c
index ee9b0a9..730a632 100644
--- a/tests/mpi/test_mpi_accs.c
+++ b/tests/mpi/test_mpi_accs.c
@@ -55,7 +55,7 @@ int main(int argc, char **argv) {
for (j = 0; j < YDIM; j++) {
const double actual = *(buffer + i + j*XDIM);
const double expected = (1.0 + rank) + (1.0 +
((rank+nranks-1)%nranks)) * (ITERATIONS);
-if (actual - expected > 1e-10) {
+if (fabs(actual - expected) > 1e-10) {
printf("%d: Data validation failed at [%d, %d] expected=%f
actual=%f\n",
rank, j, i, expected, actual);
errors++;
diff --git a/tests/mpi/test_mpi_indexed_accs.c
b/tests/mpi/test_mpi_indexed_accs.c
index 78c06bd..0fc3baa 100644
--- a/tests/mpi/test_mpi_indexed_accs.c
+++ b/tests/mpi/test_mpi_indexed_accs.c
@@ -97,7 +97,7 @@ int main(int argc, char **argv) {
for (j = 0; j < SUB_YDIM; j++) {
Processed: severity of 1062709 is grave
Processing commands for cont...@bugs.debian.org: > severity 1062709 grave Bug #1062709 [src:python-aiohttp] python-aiohttp: CVE-2024-23334 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1062709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067691: FTBFS: double free or corruption
Hi Andrey, on my aarch64 Raspberry Pi 4, I can successfully build the armel package. How can I find a way to reproduce that memory error? Maybe I should remove the fft const test. Thanks for the help. -- Matteo Bini
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> notfound 1068228 4:24.2.2-3
Bug #1068228 {Done: René Engelhard } [libreoffice-core]
libreoffice-core: fails to open any documents (ods/odt) after latest upgrades,
missing components
No longer marked as found in versions libreoffice/4:24.2.2-3.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1068228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> severity 1068228 grave
Bug #1068228 {Done: René Engelhard } [libreoffice-core]
libreoffice-core: fails to open any documents (ods/odt) after latest upgrades,
missing components
Severity set to 'grave' from 'important'
> tag 1068228 + unreproducible
Bug #1068228 {Done: René Engelhard } [libreoffice-core]
libreoffice-core: fails to open any documents (ods/odt) after latest upgrades,
missing components
Added tag(s) unreproducible.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1068228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068393: src:pytest-testinfra: unsatisfied build dependency in testing: ansible
Processing control commands: > block -1 by 1061781 Bug #1068393 [src:pytest-testinfra] src:pytest-testinfra: unsatisfied build dependency in testing: ansible 1068393 was not blocked by any bugs. 1068393 was not blocking any bugs. Added blocking bug(s) of 1068393: 1061781 -- 1068393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068393: src:pytest-testinfra: unsatisfied build dependency in testing: ansible
Control: block -1 by 1061781 Hi Paul, On Thu, 2024-04-04 at 14:38 +0200, Paul Gevers wrote: > Dose [1] is reporting a build issue with your package, it's missing a > build dependency. Obviously your build dependencies shouldn't be > removed from testing, but unfortunately there are multiple scenarios > where that can happen nevertheless. To uphold our social contract, > Debian requires that packages can be rebuild from source in the suite > we are shipping them, so currently this is a serious issue with your > package in testing. > > Can you please investigate the situation and figure out how to resolve > it? Regularly, if the build dependency is available in unstable, > helping the maintainer of your Build-Depends to enable migration to > testing is a great way to solve the issue. If your build dependency is > gone from unstable and testing, you'll have to fix the build process > in some other way. Thanks for the hint. I'm not sure I can help ansible migrate (it would need an update to the latest upstream and that's not a trivial task), but I'll do the maintenance on this bug report, closing it once pytest- testinfra is removed from testing. Best, -- Baptiste Beauplat signature.asc Description: This is a digitally signed message part
Processed: found 1068045 in 3.2.1-3
Processing commands for cont...@bugs.debian.org: > found 1068045 3.2.1-3 Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB There is no source info for the package 'libssl3' at version '3.2.1-3' with architecture '' There is no source info for the package 'yapet' at version '3.2.1-3' with architecture '' Unable to make a source version for version '3.2.1-3' Marked as found in versions 3.2.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
Hi Sean, On Sat, Apr 06, 2024 at 04:54:14PM +0800, Sean Whitton wrote: > control: reassign -1 libssl3,yapet > control: found -1 libssl3/3.1.5-1 > control: found -1 yapet/2.6-1 > control: retitle -1 libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB > > Hello, > > On Sat 30 Mar 2024 at 03:01pm +01, Sebastian Andrzej Siewior wrote: > > >> > >>> Also, yapet is unchanged in unstable. Is the problem there, too? > >> > > I have now confirmed that the problem is in unstable too. As it is a regression caused by libssl3 3.0.11 based to 3.0.13, why is it reassigned to yapet? (the regression is as well present in unstable). That said: You are right, opening 1.0 format databases should still work that said, but is regressing with the openssl update. And as per manpage: YAPET 2.0 will read and write pre YAPET 2.0 files. Pre YAPET 2.0 files are converted to YAPET 2.0 files when changing the master password. Once converted, the files can no longer be read by pre YAPET 2.0 versions. I can ask upstream, but currently yapet will FTBFS with problems in the testsuite anyway, and the problems are related. And yapet FTBFS with the new openssl in bookworm-pu in same way as in unstable (but not with the old version). Thus I believe #1068045 and #1064724 are actually related. Regards, Salvatore
Bug#1068045: Bug#1064724: yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Hi, On Thu, Mar 21, 2024 at 09:09:02AM +0100, Salvatore Bonaccorso wrote: > Hi Vladimir, > > On Thu, Mar 21, 2024 at 08:39:32PM +1300, Vladimir Petko wrote: > > Package: yapet > > Followup-For: Bug #1064724 > > User: ubuntu-de...@lists.ubuntu.com > > Usertags: origin-ubuntu noble ubuntu-patch > > Control: tags -1 patch > > > > Dear Maintainer, > > > > The package fails to build due to the recent changes in openssl. > > I have disabled the affected tests, but probably the issue should be fixed > > upstream. > > > > When investigating test failure I've also noticed that the tests fail on > > armhf > > due to the usage of std::memset that was optimized away. I have replaced the > > call with std::fill() > > > > In Ubuntu, the attached patch was applied to achieve the following: > > > > * d/p/use-std-fill.patch: use std::fill to reset memory instead of > > std::memset. This fixes armhf test failure (LP: 2058584). > > * d/p/disable-blowfish-tests.patch: disable failing blowfish tests. > > See Debian bug 1064724. > > > > > > Thanks for considering the patch. > > Thanks for your work. I would like to give upstream some time to look > at the two reported issues. I'm not going to apply the patch for now, as the underlying issue is triggered due to a change in openssl. Cf. #1068045. Regards, Salvatore
Processed: tagging 1064724
Processing commands for cont...@bugs.debian.org: > tags 1064724 - patch Bug #1064724 [src:yapet] yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066469: marked as done (tack: FTBFS: configure: error: No curses header-files found)
Your message dated Sat, 06 Apr 2024 13:05:15 + with message-id and subject line Bug#1066469: fixed in tack 1.09+20230201-1 has caused the Debian Bug report #1066469, regarding tack: FTBFS: configure: error: No curses header-files found 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.) -- 1066469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tack Version: 1.08-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > configure: WARNING: pkg-config is not installed > checking for specific curses-directory... no > checking for specified curses library type... curses > checking for extra include directories... no > checking if we have identified curses headers... none > configure: error: No curses header-files found > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2024/03/13/tack_1.08-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: tack Source-Version: 1.09+20230201-1 Done: Sven Joachim We believe that the bug you reported is fixed in the latest version of tack, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sven Joachim (supplier of updated tack 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, 06 Apr 2024 10:03:12 +0200 Source: tack Architecture: source Version: 1.09+20230201-1 Distribution: unstable Urgency: medium Maintainer: Sven Joachim Changed-By: Sven Joachim Closes: 1066469 Changes: tack (1.09+20230201-1) unstable; urgency=medium . [ Debian Janitor ] * Use secure copyright file specification URI. * Bump debhelper from old 10 to 13. * Set debhelper-compat version in Build-Depends. * Fix field name case in debian/copyright (Upstream-name => Upstream-Name). * Use canonical URL in Vcs-Browser. * Fix field name case in debian/copyright (Upstream-contact ⇒ Upstream-Contact). . [ Sven Joachim ] * New upstream snapshot. - Fixes FTBFS with -Werror=implicit-function-declaration (Closes: #1066469). * Update debian/watch to version 4, and look for tarballs on https://invisible-mirror.net. * Add a debian/watch.snapshot file for checking/downloading snapshots with uscan. * Update debian/upstream/signing-key.asc. - Add new key 19882D92DDA4C400C22C0D56CC2AF4472167BE03. - Drop old SHA1 key C52048C0C0748FEE. * Build-depend on libncurses-dev rather than on libncurses5-dev. * Bump Standards-Version to 4.6.2, no changes needed. * Update debian/copyright. * Add a debian/salsa-ci.yml file for the Salsa CI pipeline. - Disable the arm64 crossbuild job, not supported. Checksums-Sha1: d028b64b5cd326be164bb183e7f93018cd9af659 1998 tack_1.09+20230201-1.dsc 4373862e3280a90f817498ddcd84ee66c000f6d9 256410 tack_1.09+20230201.orig.tar.gz 6cc2a703764162214014a8fab8d359d6dcfc3f60 729 tack_1.09+20230201.orig.tar.gz.asc 69e63664e092bde2f0684b28b5edf9a067896886 6344 tack_1.09+20230201-1.debian.tar.xz 896a885e99d3f1392d519bca963846ddc2ea9801 5538 tack_1.09+20230201-1_source.buildinfo Checksums-Sha256:
Bug#1058291: marked as done (python-urllib3: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Sat, 6 Apr 2024 16:06:15 +0500
with message-id
and subject line Re: Bug#1058291: python-urllib3: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13
has caused the Debian Bug report #1058291,
regarding python-urllib3: FTBFS: dh_auto_test: error: pybuild --test -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.)
--
1058291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-urllib3
Version: 1.26.18-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f src/urllib3/packages/six.py
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build
> /usr/lib/python3/dist-packages/setuptools/dist.py:744:
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
>
>
>
> Usage of dash-separated 'provides-extra' will not be supported in
> future
> versions. Please use the underscore name 'provides_extra' instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/dist.py:744:
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
>
>
>
> Usage of dash-separated 'requires-dist' will not be supported in
> future
> versions. Please use the underscore name 'requires_dist' instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293:
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
>
>
>
> The license_file parameter is deprecated, use license_files instead.
>
> This deprecation is overdue, please update your project and remove
> deprecated
> calls to avoid build errors in the future.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> parsed = self.parsers.get(option_name, lambda x: x)(value)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/__init__.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/poolmanager.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/exceptions.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/fields.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/_version.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/filepost.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/_collections.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/response.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/connectionpool.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/request.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> copying src/urllib3/connection.py ->
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3
> creating
> /<>/.pybuild/cpython3_3.12_urllib3/build/urllib3/packages
> copying src/urllib3/packages/__init__.py ->
>
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> severity 1058653 grave
Bug #1058653 {Done: Rene Engelhard }
[libreoffice-writer-nogui] libreoffice-writer-nogui: fails to convert ODT to
PDF without libreoffice-core (libcuilo.so): Error: source file could not be
loaded
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1058653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1056435 is forwarded to https://github.com/ponyorm/pony/issues/703, tagging 1056435
Processing commands for cont...@bugs.debian.org: > forwarded 1056435 https://github.com/ponyorm/pony/issues/703 Bug #1056435 [src:ponyorm] ponyorm's autopkg tests fail with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/ponyorm/pony/issues/703'. > tags 1056435 + upstream Bug #1056435 [src:ponyorm] ponyorm's autopkg tests fail with Python 3.12 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056458: marked as done (python-b2sdk's autopkg tests fail with Python 3.12)
Your message dated Sat, 6 Apr 2024 16:31:31 +0500
with message-id
and subject line Re: Bug#1056458: python-b2sdk's autopkg tests fail with Python
3.12
has caused the Debian Bug report #1056458,
regarding python-b2sdk'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.)
--
1056458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-b2sdk
Version: 1.17.3-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-b2sdk's autopkg tests fail with Python 3.12:
[...]
643s autopkgtest [18:37:31]: test command1: [---
643s [*] testing on python3.12:
643s Traceback (most recent call last):
643s File "", line 198, in _run_module_as_main
643s File "", line 88, in _run_code
643s File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5,
in
643s raise SystemExit(pytest.console_main())
643s ^
643s File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 192, in console_main
643s code = main()
643s^^
643s File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 150, in main
643s config = _prepareconfig(args, plugins)
643s ^
643s File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 331, in _prepareconfig
643s config = pluginmanager.hook.pytest_cmdline_parse(
643s
643s File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493,
in __call__
643s return self._hookexec(self.name, self._hookimpls, kwargs,
firstresult)
643s
^^^
643s File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line
115, in _hookexec
643s return self._inner_hookexec(hook_name, methods, kwargs,
firstresult)
643s
^
643s File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line
130, in _multicall
643s teardown[0].send(outcome)
643s File "/usr/lib/python3/dist-packages/_pytest/helpconfig.py", line
104, in pytest_cmdline_parse
643s config: Config = outcome.get_result()
643s
643s File "/usr/lib/python3/dist-packages/pluggy/_result.py", line
114, in get_result
643s raise exc.with_traceback(exc.__traceback__)
643s File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line
77, in _multicall
643s res = hook_impl.function(*args)
643s ^
643s File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 1075, in pytest_cmdline_parse
643s self.parse(args)
643s File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 1425, in parse
643s self._preparse(args, addopts=addopts)
643s File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py",
line 1305, in _preparse
643s self.pluginmanager.load_setuptools_entrypoints("pytest11")
643s File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line
398, in load_setuptools_entrypoints
643s plugin = ep.load()
643s ^
643s File "/usr/lib/python3.12/importlib/metadata/__init__.py", line
205, in load
643s module = import_module(match.group('module'))
643s
643s File "/usr/lib/python3.12/importlib/__init__.py", line 90, in
import_module
643s return _bootstrap._gcd_import(name[level:], package, level)
643s
643s File "", line 1381, in _gcd_import
643s File "", line 1354, in _find_and_load
643s File "", line 1325, in
_find_and_load_unlocked
643s File "", line 929, in _load_unlocked
643s File "", line 994, in
exec_module
643s File "", line 488, in
_call_with_frames_removed
643s File "/usr/lib/python3/dist-packages/pyfakefs/pytest_plugin.py",
line 14, in
643s from pyfakefs.fake_filesystem_unittest import Patcher
643s File
"/usr/lib/python3/dist-packages/pyfakefs/fake_filesystem_unittest.py",
line 72, in
643s from pyfakefs import fake_pathlib
643s File "/usr/lib/python3/dist-packages/pyfakefs/fake_pathlib.py",
line 164, in
643s flavour = pathlib._Flavour # type: ignore [attr-defined]
643s
643s AttributeError: module 'pathlib' has no attribute '_Flavour'
644s
Processed: bug 1058300 is forwarded to https://github.com/tholo/pytest-flake8/issues/100
Processing commands for cont...@bugs.debian.org:
> forwarded 1058300 https://github.com/tholo/pytest-flake8/issues/100
Bug #1058300 [src:python-pytest-flake8] python-pytest-flake8: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12
3.11" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/tholo/pytest-flake8/issues/100'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: affects 1063957
Processing commands for cont...@bugs.debian.org:
> affects 1063957 src:python-b2sdk
Bug #1063957 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture:
autopkgtest regression with pytest 8
Bug #1063973 [src:python-pytest-lazy-fixture] python-marshmallow-sqlalchemy:
autopkgtest regression with pytest 8
Bug #1066727 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture: Needs
update for Pytest 8 (AttributeError: 'CallSpec2' object has no attribute
'funcargs')
Bug #1066784 [src:python-pytest-lazy-fixture] python-marshmallow-sqlalchemy:
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
"3.12 3.11" returned exit code 13
Bug #1066785 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture:
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
"3.12 3.11" returned exit code 13
Bug #1066789 [src:python-pytest-lazy-fixture] pycoast: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned
exit code 13
Added indication that 1063957 affects src:python-b2sdk
Added indication that 1063973 affects src:python-b2sdk
Added indication that 1066727 affects src:python-b2sdk
Added indication that 1066784 affects src:python-b2sdk
Added indication that 1066785 affects src:python-b2sdk
Added indication that 1066789 affects src:python-b2sdk
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1063957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063957
1063973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063973
1066727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066727
1066784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066784
1066785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066785
1066789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1059647 is forwarded to https://github.com/scikit-fmm/scikit-fmm/issues/78
Processing commands for cont...@bugs.debian.org: > forwarded 1059647 https://github.com/scikit-fmm/scikit-fmm/issues/78 Bug #1059647 [src:scikit-fmm] scikit-fmm: autopkgtest failure with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/scikit-fmm/scikit-fmm/issues/78'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063418: mdp ftbfs in unstable
It currently fails even earlier:
ImportError while loading conftest '/<>/mdp/test/conftest.py'.
mdp/__init__.py:133: in
utils.symeig = configuration.get_symeig(numx_linalg)
mdp/configuration.py:335: in get_symeig
args = getargs(numx_linalg.eigh)[0]
/usr/lib/python3.11/inspect.py:1379: in getfullargspec
raise TypeError('unsupported callable') from ex
E TypeError: unsupported callable
This is reported upstream at
https://github.com/mdp-toolkit/mdp-toolkit/issues/99 and probably fixed at
https://github.com/mdp-toolkit/mdp-toolkit/pull/100 .
Not sure about the initially reported test_dtype_consistency failures.
--
WBR, wRAR
signature.asc
Description: PGP signature
Bug#1068502: Dead upstream and broken, remove or switch to a fork?
Source: python-pytest-flake8 Severity: serious https://github.com/tholo/pytest-flake8/issues/98 https://github.com/tholo/pytest-flake8/issues/97 https://github.com/tholo/pytest-flake8/issues/92 https://github.com/tholo/pytest-flake8/issues/91 -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1068500: Installs /usr/LICENSE
Package: python3-xmlrunner Version: 3.2.0-2 Severity: serious drwxr-xr-x root/root 0 2023-01-22 01:39 ./ drwxr-xr-x root/root 0 2023-01-22 01:39 ./usr/ -rw-r--r-- root/root 1532 2022-02-02 16:17 ./usr/LICENSE Note that it's caught by lintian: W: python3-xmlrunner: file-in-unusual-dir [usr/LICENSE] I: python3-xmlrunner: extra-license-file [usr/LICENSE] I: python3-xmlrunner: package-contains-documentation-outside-usr-share-doc [usr/LICENSE] -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-xmlrunner depends on: ii python3 3.11.8-1 ii python3-lxml 5.2.1-1 python3-xmlrunner recommends no packages. python3-xmlrunner suggests no packages.
Bug#1068473: icinga2: crashes on startup on ppc64el
On 4/6/24 1:29 PM, Aurelien Jarno wrote: On 2024-04-06 08:01, Sebastiaan Couwenberg wrote: On 4/5/24 9:51 PM, Aurelien Jarno wrote: For Bookworm given we can not fix the compiler easily, I propose to just build icinga2 with -O1 on ppc64el. If you are fine with that option, I can take care of proposing a patch and submitting it to the stable release team. A patch for this is very welcome. How do you propose to implement that? Something like this maybe? --- a/debian/rules +++ b/debian/rules @@ -9,6 +9,11 @@ include /usr/share/dpkg/architecture.mk export CTEST_OUTPUT_ON_FAILURE=1 +ifneq (,$(filter $(DEB_HOST_ARCH), ppc64el)) + export DEB_CXXFLAGS_STRIP = -O2 + export DEB_CXXFLAGS_MAINT_APPEND = -O1 +endif + ifneq (,$(filter $(DEB_HOST_ARCH), armel mips mipsel powerpc)) export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic -Wl,--as-needed endif Yes, something like that works. I even tested without the DEB_CXXFLAGS_STRIP, gcc is smart enough to just take the last flag, so -O1. Also it seems that your diff applies to the Trixie/Sid version, while it should be applied to Bookworm instead. Correct, I did not actually prepare a bookworm branch as you offered to take care of that. Since it's not that much work, I did that now: https://salsa.debian.org/nagios-team/icinga2/-/commits/bookworm?ref_type=heads If you can confirm that those changes fix the issue, I can also fix the bookworm-pu bugreport, or you can do that if you want. Note that we ignore test failures on ppc64el which might have caught this issue. I don't think so. Tests are not ignored for Bookworm and haven't caught the issue. OTOH they are ignored for Trixie/Sid, while this version works fine. The version command also doesn't trigger the segfault, the autopkgtest also didn't catch this. Upstream doesn't care about those architectures, so we're on our own to resolve issues on architectures other than amd64/i386/arm64. Pretty much all packages I maintain don't have actual users on non-amd64 architectures, so I don't consider it worth the effort to ask the porters for help, they should spend their time on packages that are actually used. With DSA's use of icinga2 on porterboxes it's the exception to the norm. Yes, I agree that the upstream situation is not nice. I personally try to get things fixed [1], but it went nowhere. And the issue was not really architecture specific, just that icinga2 testsuite doesn't support page sizes bigger than 4K... Thanks for your work on that. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1068497: golang-github-antonini-golibjpegturbo: FTBFS: Tries to access the network during build
Package: src:golang-github-antonini-golibjpegturbo Version: 0.0~git20141208.c03a2fa-2 Severity: serious Tags: ftbfs [...] github.com/antonini/golibjpegturbo dh_auto_test -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 20 github.com/antonini/golibjpegturbo panic: Get "https://farm1.staticflickr.com/47/139138903_3d9600174d_b_d.jpg": dial tcp: lookup farm1.staticflickr.com on [::1]:53: read udp [::1]:40015->[::1]:53: read: connection refused https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-antonini-golibjpegturbo.html
Bug#1064852: fixed in incus 0.6-2
(Touching bug to reset AUTORM countdown.) signature.asc Description: This is a digitally signed message part
Processed: Processed: Severity for 1036805 was serious and we even released with it
Processing commands for cont...@bugs.debian.org: > severity 1036805 important Bug #1036805 [libreoffice-writer] libreoffice's toolbar buttons became hard to see after upgrading to Debian 12 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1036805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068473: icinga2: crashes on startup on ppc64el
On 2024-04-06 08:01, Sebastiaan Couwenberg wrote: > On 4/5/24 9:51 PM, Aurelien Jarno wrote: > > For Bookworm given we can not fix the compiler easily, I propose to just > > build icinga2 with -O1 on ppc64el. If you are fine with that option, I > > can take care of proposing a patch and submitting it to the stable > > release team. > > A patch for this is very welcome. How do you propose to implement that? > Something like this maybe? > > --- a/debian/rules > +++ b/debian/rules > @@ -9,6 +9,11 @@ include /usr/share/dpkg/architecture.mk > > export CTEST_OUTPUT_ON_FAILURE=1 > > +ifneq (,$(filter $(DEB_HOST_ARCH), ppc64el)) > + export DEB_CXXFLAGS_STRIP = -O2 > + export DEB_CXXFLAGS_MAINT_APPEND = -O1 > +endif > + > ifneq (,$(filter $(DEB_HOST_ARCH), armel mips mipsel powerpc)) > export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic > -Wl,--as-needed > endif Yes, something like that works. I even tested without the DEB_CXXFLAGS_STRIP, gcc is smart enough to just take the last flag, so -O1. Also it seems that your diff applies to the Trixie/Sid version, while it should be applied to Bookworm instead. > Note that we ignore test failures on ppc64el which might have caught this > issue. I don't think so. Tests are not ignored for Bookworm and haven't caught the issue. OTOH they are ignored for Trixie/Sid, while this version works fine. > Upstream doesn't care about those architectures, so we're on our own > to resolve issues on architectures other than amd64/i386/arm64. Pretty much > all packages I maintain don't have actual users on non-amd64 architectures, > so I don't consider it worth the effort to ask the porters for help, they > should spend their time on packages that are actually used. With DSA's use > of icinga2 on porterboxes it's the exception to the norm. Yes, I agree that the upstream situation is not nice. I personally try to get things fixed [1], but it went nowhere. And the issue was not really architecture specific, just that icinga2 testsuite doesn't support page sizes bigger than 4K... Regards Aurelien [1] https://github.com/Icinga/icinga2/issues/9954#issuecomment-1875209616 -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net signature.asc Description: PGP signature
Processed: affects 1068349 + src:python-pint
Processing commands for cont...@bugs.debian.org:
> affects 1068349 + src:python-pint
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml
5.2: lxml.html.clean
Added indication that 1068349 affects src:python-pint
> block 1067229 by 1068349
Bug #1067229 [src:python-pint] metpy: autopkgtest regression with NumPy 1.26
1067229 was not blocked by any bugs.
1067229 was not blocking any bugs.
Added blocking bug(s) of 1067229: 1068349
> block 1067318 by 1068349
Bug #1067318 [src:python-pint] python-pint: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
1067318 was not blocked by any bugs.
1067318 was not blocking any bugs.
Added blocking bug(s) of 1067318: 1068349
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067229
1067318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067318
1068349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1065547: marked as done (gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments)
Your message dated Sat, 06 Apr 2024 11:05:54 +
with message-id
and subject line Bug#1065547: fixed in pygobject 3.48.2-1
has caused the Debian Bug report #1065547,
regarding gst-python1.0 FTBFS: TypeError: function takes at most 0 arguments
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.)
--
1065547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-python1.0
Version: 1.23.90-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=gst-python1.0=1.23.90-1
https://buildd.debian.org/status/logs.php?pkg=gst-python1.0=1.24.0-1
...
3/3 =
test: Test fundamentals
start time: 12:22:01
duration: 2.03s
result: exit status 1
command: ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
GST_OVERRIDE_BUILD_PATH=/<>/build-3.12/testsuite/../gi/overrides
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
MALLOC_PERTURB_=73
GST_PLUGIN_LOADING_WHITELIST=gstreamer:gst-plugins-base:gst-python@/<>/build-3.12
GST_REGISTRY='/<>/build-3.12/testsuite/Test
fundamentals.registry'
GST_PLUGIN_PATH_1_0=/<>/build-3.12:/usr/lib/x86_64-linux-gnu/gstreamer-1.0:/usr/lib/x86_64-linux-gnu/gstreamer-1.0:/<>/build-3.12/plugin:/<>/testsuite
GST_OVERRIDE_SRC_PATH=/<>/testsuite/../gi/overrides
/usr/bin/python3.12 /<>/build-3.12/../testsuite/runtests.py
test_types.py
--- stderr ---
.EE.
==
ERROR: testConstructor (test_types.TestBitmask.testConstructor)
--
Traceback (most recent call last):
File "/<>/testsuite/test_types.py", line 387, in testConstructor
r = Gst.Bitmask(1 << 5)
^^^
TypeError: function takes at most 0 arguments (1 given)
==
ERROR: testGetValue (test_types.TestBitmask.testGetValue)
--
Traceback (most recent call last):
File "/<>/testsuite/test_types.py", line 393, in testGetValue
self.assertEqual(Gst.Structure('test,test=(bitmask)0x20')['test'], 1 << 5)
File "/<>/testsuite/../gi/overrides/Gst.py", line 330, in
__getitem__
return self.get_value(key)
^^^
TypeError: function takes at most 0 arguments (1 given)
==
ERROR: testStr (test_types.TestBitmask.testStr)
--
Traceback (most recent call last):
File "/<>/testsuite/test_types.py", line 398, in testStr
r = Gst.Bitmask(1 << 5)
^^^
TypeError: function takes at most 0 arguments (1 given)
...
FAILED (errors=30)
==
Summary of Failures:
3/3 Test fundamentals FAIL2.03s exit status 1
Ok: 2
Expected Fail: 0
Fail: 1
Unexpected Pass:0
Skipped:0
Timeout:0
dh_auto_test: error: cd build-3.12 && DEB_PYTHON_INSTALL_LAYOUT=deb
LC_ALL=C.UTF-8 MESON_TESTTHREADS=6 meson test returned exit code 1
make[1]: *** [debian/rules:28: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: pygobject
Source-Version: 3.48.2-1
Done: Jeremy Bícha
We believe that the bug you reported is fixed in the latest version of
pygobject, 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 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jeremy Bícha (supplier of updated pygobject 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, 06 Apr 2024 06:49:50 -0400
Source: pygobject
Built-For-Profiles: noudeb
Architecture:
Bug#1064170: marked as done (mediastreamer2: NMU diff for 64-bit time_t transition)
Your message dated Sat, 06 Apr 2024 10:00:10 +
with message-id
and subject line Bug#1064170: fixed in mediastreamer2 1:5.2.0+dfsg-3.2
has caused the Debian Bug report #1064170,
regarding mediastreamer2: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1064170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mediastreamer2
Version: 1:5.2.0+dfsg-3.1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
mediastreamer2 as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for mediastreamer2
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mediastreamer2-5.2.0+dfsg/debian/changelog
mediastreamer2-5.2.0+dfsg/debian/changelog
--- mediastreamer2-5.2.0+dfsg/debian/changelog 2024-01-30 14:30:19.0
+
+++ mediastreamer2-5.2.0+dfsg/debian/changelog 2024-02-18 00:13:01.0
+
@@ -1,3 +1,10 @@
+mediastreamer2 (1:5.2.0+dfsg-3.2) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Sun, 18 Feb 2024 00:13:01 +
+
mediastreamer2 (1:5.2.0+dfsg-3.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru mediastreamer2-5.2.0+dfsg/debian/control
mediastreamer2-5.2.0+dfsg/debian/control
--- mediastreamer2-5.2.0+dfsg/debian/control2024-01-30 14:30:14.0
+
+++ mediastreamer2-5.2.0+dfsg/debian/control2024-02-18 00:13:01.0
+
@@ -58,7 +58,10 @@
Vcs-Browser:
https://salsa.debian.org/pkg-voip-team/linphone-stack/mediastreamer2
Description: Multimedia streaming engine for telephony
-Package: libmediastreamer13
+Package: libmediastreamer13t64
+Provides: ${t64:Provides}
+Replaces: libmediastreamer13
+Breaks: libmediastreamer13 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
@@ -86,7 +89,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libmediastreamer13 (= ${binary:Version}),
+Depends: libmediastreamer13t64 (= ${binary:Version}),
${misc:Depends},
# the .pc file mentions these 2, so a Depends: is needed
# also the headers reference files from these 2
diff -Nru mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install
mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install
--- mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install 2024-01-30
14:20:36.0 +
+++ mediastreamer2-5.2.0+dfsg/debian/libmediastreamer13.install 1970-01-01
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libmediastreamer.so.*
diff -Nru
Bug#1063419: marked as done (sugar-artwork: Please package version 0.121 needed by sugar-session)
Your message dated Sat, 06 Apr 2024 09:36:56 + with message-id and subject line Bug#1063419: fixed in sugar-artwork 0.121-1 has caused the Debian Bug report #1063419, regarding sugar-artwork: Please package version 0.121 needed by sugar-session 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.) -- 1063419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sugar-artwork Version: 0.120-2 Severity: serious Control: affects -1 src:sugar X-Debbugs-CC: d...@jones.dk sugar-session in Unstable depends on sugar-themes (>= 0.121) but that version is not available in Unstable yet. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: sugar-artwork Source-Version: 0.121-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-artwork, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-artwork 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, 06 Apr 2024 11:14:53 +0200 Source: sugar-artwork Architecture: source Version: 0.121-1 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 1063419 Changes: sugar-artwork (0.121-1) unstable; urgency=medium . [ upstream ] * new release; closes: bug#1063419, thanks to Jeremy Bícha . [ Jonas Smedegaard ] * update copyright info: update coverage Checksums-Sha1: fb08db05a4b56f23e7741a1ce354d60490dda594 2170 sugar-artwork_0.121-1.dsc 36338c4eb41eee16a2c4ea6e5a6636167ff93e4b 461540 sugar-artwork_0.121.orig.tar.xz b25b3ecc26b5130306e5aa4a7bf69cd43f1b0fef 12816 sugar-artwork_0.121-1.debian.tar.xz 206d36a6f1b5e380e3d17bd6ebfc37920f05ccd8 16194 sugar-artwork_0.121-1_amd64.buildinfo Checksums-Sha256: 279887e5d06c06c9dabd7efa64e80986d1b62092606d270cdfda5a9e292e88b0 2170 sugar-artwork_0.121-1.dsc d28a9b17ec54eab29f39e3dbd490956e9a588357209d523b1978c3df40d7bee2 461540 sugar-artwork_0.121.orig.tar.xz c489ad35b7a36cbf20d3a0720a8863a154671902a1b77b74203335f775ed8b45 12816 sugar-artwork_0.121-1.debian.tar.xz b4c496892f660ef0c5c397ca9776f2eb5dda8e0fb1fca62a1e5283a7161881f8 16194 sugar-artwork_0.121-1_amd64.buildinfo Files: ee022da634bd1151ea2c3f8f589ae9f1 2170 x11 optional sugar-artwork_0.121-1.dsc a54b17052f379fa76c3ffe4778362ea2 461540 x11 optional sugar-artwork_0.121.orig.tar.xz 4b178aa1f3ac83b2e00d253ae10806e6 12816 x11 optional sugar-artwork_0.121-1.debian.tar.xz b66f5e29aae4f357a402f29f5b51e97d 16194 x11 optional sugar-artwork_0.121-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYREzUACgkQLHwxRsGg ASFxwA//ZOAQd9gikfRi8GtXPkSx6ihSsH+MY0nkEzfIEggqLjsNqQApc6lhflil xduRYblDjJpxrR5oJtu09qsL0k3ars/2iXnIy8HD1GjF8FWQdp5otlTvZiOp9Baq r81VAmqfji54uxGneyqgrKOFi4IktN0j3+Z3LqtJUAhgkvAwsQzTg6V4vAfbIPHn NDRfVRTz98qGmoyWtAClsk1ekGLitwKe0KgEudSFl+88DdF4yHqRzuSZ9G0JwtVX BaovRPS+OsnMFjefZlVvbxM+B7Q2Uc1zCj9BzqXi5cYx3iEhQ/rvtAfbJTvMGnZH vRcaBJgdxtEiSJOn8N31CGq6hDcsnoVh7J+9WIxh/aJyBRYLA6D3H6UKbwVTxyfo h62uBZkzSmlOnGCznU3gJrOZzhryXkAmCRA+cQnKITAseq5CM2U7ZpSkzZsnNGaj 8Rye2KFOGOmVXnpTpfrGXnNw/9zOhihKJnsXnKhXrkf1lojE4XGB6/SzYszf9Afo d6fcXFUZM2tbC+VMWayjkWaG+BBYef6bDbji+t6m8PbGdEmgNiYiRvNfF1BBwbdv X6PP1Gm9qz3+3jcMX8ENzFcWslL0eiPyR//zJF7YClUEoiES5L7FanHW5BVte9N9 lMhbr9Yy9HIq9+jaH2gqx7FzSIuvocMTmhaTQHzOpQuhby3k63g= =yslU -END PGP SIGNATURE- pgpac4G_Q4Q9f.pgp Description: PGP signature --- End Message ---
Bug#1068157: siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT
Hi William, I noticed you "binNMU"-ed siridb-server in Ubuntu where it built successfully on all arches. In Debian I got the bug below reported. Any idea what the difference could be between the state of Debian and the state of Ubuntu that causes this? reproducible-builds [1] confirms that the problem exists in both unstable and testing, introduced somewhere after 2023-11-02. Paul [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/siridb-server.html On 01-04-2024 12:00 a.m., Sebastian Ramacher wrote: Source: siridb-server Version: 2.0.51-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=siridb-server=2.0.51-2%2Bb3=armhf=1711922161 Testing expr␛[32mOK␛[0m (8.519 ms) ==3276877== ==3276877== Process terminating with default action of signal 11 (SIGSEGV) ==3276877== Access not within mapped region at address 0xFEC4F704 ==3276877==at 0x495F6F0: pcre2_compile_8 (in /usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.11.2) ==3276877== If you believe this happened as a result of a stack ==3276877== overflow in your program's main thread (unlikely but ==3276877== possible), you can try to increase the size of the ==3276877== main thread stack using the --main-stacksize= flag. ==3276877== The main thread stack size used in this run was 8388608. ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT Cheers OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068479: libreoffice-writer: space between paragraphs missing in spacing and indentation
tag 1068479 + moreinfo tag 1068479 + unreproducible severity 1068479 important thanks Hi, Am 06.04.24 um 00:34 schrieb José Luis González: The setting for spacing between paragraphs is missing in the spacing and indentation tab of the paragraph dialog. ? It's definitely there. Format -> Paragraph has spacing "after/before". See here (yes, from stable): Serious severity because the bug has a major effect on the usability of the package, without rendering it completely unusable, considering paragraphs are a key feature in a word processor, and spacing is something very very basic for them and incredibly necessary. Don't overfinflate severities. That is the definition of important "5 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. 6 serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive); may or may not affect the usability of the package. Note that non-severe policy violations may be 'normal,' 'minor,' or 'wishlist' bugs. (Package maintainers may also designate other bugs as 'serious' and thus release-critical; however, end users should not do so.). For the canonical list of issues deserving a serious severity you can refer to this webpage: https://release.debian.org/testing/rc_policy.txt . " This matches 5, not 6. And it's unreproducible. Regards, Rene
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
Hello, On Sat 30 Mar 2024 at 03:01pm +01, Sebastian Andrzej Siewior wrote: > On 30 March 2024 13:14:37 CET, Sean Whitton wrote: > >>I downgraded, changed the password for my database to 'asdf', >>changed it back to the password it had before, upgraded libssl3, >>and the bug did not appear. >> >>I reverted to my original db, downgraded again, deleted an entry without >>changing the password, upgraded, and the bug appeared. >> >>I can't really say more without compromising my opsec. But does the >>above give any clues / further debugging ideas? > > I would look at the function yapet is using from openssl and compare the > results. > Could create a database from scratch an use similar patterns in terms number > of entries and password (length, special characters) until you have something > that you can share with me. I don't mind if throw it in my inbox without Cc: > the bug. It looks like the problem is opening YAPET1.0-format databases, which the manpage explicitly says is meant to work. I've made a sample YAPET1.0 database using a stretch VM. Using the attached: - On bookworm, invoke 'yapet yapet1.0.pet', and you can decrypt it. - On stable or on bookworm with libssl3/3.0.13-1~deb12u1, you can't. Thanks again. -- Sean Whitton yapet1.0.pet Description: Binary data signature.asc Description: PGP signature
Processed: Bug#1068479: libreoffice-writer: space between paragraphs missing in spacing and indentation
Processing commands for cont...@bugs.debian.org: > tag 1068479 + moreinfo Bug #1068479 [libreoffice-writer] libreoffice-writer: space between paragraphs missing in spacing and indentation Added tag(s) moreinfo. > tag 1068479 + unreproducible Bug #1068479 [libreoffice-writer] libreoffice-writer: space between paragraphs missing in spacing and indentation Added tag(s) unreproducible. > severity 1068479 important Bug #1068479 [libreoffice-writer] libreoffice-writer: space between paragraphs missing in spacing and indentation Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1068479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068463: marked as done (procyon: Untrusted code execution via cwd in classpath)
Your message dated Sat, 06 Apr 2024 09:21:26 + with message-id and subject line Bug#1068463: fixed in procyon 0.6.0-2 has caused the Debian Bug report #1068463, regarding procyon: Untrusted code execution via cwd in classpath 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.) -- 1068463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: procyon-decompiler Version: 0.6.0-1 Tags: security Severity: grave In the default configuration, procyon prepends current working directory to the java classpath. This is done in the shell script /usr/bin/procyon, which sets, apparently by mistake, CLASSPATH=$CLASSPATH:..., where $CLASSPATH is a usually empty environment variable - and empty string in this context is interpreted as a current working directory by java. This is potentially dangerous, especially with a decompiler, which is supposed to deal with untrusted code. In a possible bad scenario, a user (without CLASSPATH environment variable, which is the debian default) might try to decompile an untrusted malicious jar: wget ".../bad.jar" jar xf bad.jar procyon ... Regardless of what command line arguments are given to procyon, if the extracted jar contained e.g. the jcommander class, then it will get executed. --- End Message --- --- Begin Message --- Source: procyon Source-Version: 0.6.0-2 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of procyon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated procyon 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, 06 Apr 2024 10:46:00 +0200 Source: procyon Architecture: source Version: 0.6.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 1068463 Changes: procyon (0.6.0-2) unstable; urgency=medium . * Prevent untrusted code execution from the command line (Closes: #1068463) Checksums-Sha1: a81914368787af40ac2ca79a0c10433f263ae7cf 2126 procyon_0.6.0-2.dsc 2356ad74e4f3d3120d4fb6567274d139c938db80 8352 procyon_0.6.0-2.debian.tar.xz 494205d5b18a9550ef3168058ba99de961859d0c 16872 procyon_0.6.0-2_source.buildinfo Checksums-Sha256: 110e78a5f31f17fa10793498be633bd6e5713264584b4cfdf35bdf3cdb3ba691 2126 procyon_0.6.0-2.dsc 1a0fdea456430d40370f3ab8a1bfc8036427cd8c9eeb0b3c41b1be290637d30d 8352 procyon_0.6.0-2.debian.tar.xz f361ec278567bb4f95f40efa87804af890e928277126dca59fca9872cc92d8a1 16872 procyon_0.6.0-2_source.buildinfo Files: 88699c5c3e942ae1ffbb4bfe9cb07f13 2126 java optional procyon_0.6.0-2.dsc 8eaaab4134da64ba14feec086274367b 8352 java optional procyon_0.6.0-2.debian.tar.xz 3c28b430258f0e6a55d70e803043e5b1 16872 java optional procyon_0.6.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmYRC+kSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsK+gP/1h4cdjx6L8cy6+vGqEtdajM+usbc8Lg uFc2cC9Q7P2kuL7uDZZvhUCMFa/zVsc5rfF/6NQNRGq1GgkxbGy7G/bkXZiVsdbu agbKukEpDGE3CEJWmfM+umVua6gJX5ZTOUf/Waq+Me9uYtAJAfT6USx0LhvC2LLE sWqi4b0fItaaftMOVfSEWf6OjK4gb3VISRi28VoZzqaWllU9IqqaIFqei80BMig6 pNVHJilfm1oGphABM/mFUWU1D363f+uAO4A7uAD05trGJ6XQLbDEZiSy6ridcCV0 Oyfn/Gh/7ScqG342t24AdJPtNPPEKyIyxcHnCB4OkwDhV2AY04jD6JHgx8dP5XL6 Dt20VOXJyIuABTjBPuHZV0NX2do6262VwprgUL6X35Qt7fbYN0NpgQx23NLFTDZJ WGhLsDPNoJbGlFWsxFn82ivOo3CjzL4Td210GfduW46Fe7m+hF9s1/BYI7m0gUwP iWmwh3lKtCWVVYPC6+gb+PQb9sW6d17jPDXdura2cWVpRS22JEoQCem9KvkbEuke fkNp24u/8vTjkCs+wwlqDZr2WxQGu4J1646EpjLtH94+JM4QTOyKYhkv5b4jo20N jwSKf+E+06PkOj+eU/lSKWmNQlxIASiQiCdBX8MoJFKBs24gpWPP0qqPPXn9639b 2LaHNWndI2xa =LXjA -END PGP SIGNATURE- pgpFYdBKlAvcI.pgp Description: PGP signature --- End Message ---
Processed: notfound 1068045 in libssl3/3.1.5-1, found 1068045 in openssl/3.0.13-1~deb12u1 ...
Processing commands for cont...@bugs.debian.org: > notfound 1068045 libssl3/3.1.5-1 Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB The source libssl3 and version 3.1.5-1 do not appear to match any binary packages No longer marked as found in versions libssl3/3.1.5-1. > found 1068045 openssl/3.0.13-1~deb12u1 Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Marked as found in versions openssl/3.0.13-1~deb12u1. > fixed 1068045 openssl/3.0.11-1~deb12u2 Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Marked as fixed in versions openssl/3.0.11-1~deb12u2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1068045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
Processing control commands: > reassign -1 libssl3,yapet Bug #1068045 [libssl3] libssl3: breaks YAPET Bug reassigned from package 'libssl3' to 'libssl3,yapet'. No longer marked as found in versions openssl/3.0.13-1~deb12u1. No longer marked as fixed in versions openssl/3.0.11-1~deb12u2. > found -1 libssl3/3.1.5-1 Bug #1068045 [libssl3,yapet] libssl3: breaks YAPET The source libssl3 and version 3.1.5-1 do not appear to match any binary packages Marked as found in versions libssl3/3.1.5-1. > found -1 yapet/2.6-1 Bug #1068045 [libssl3,yapet] libssl3: breaks YAPET Marked as found in versions yapet/2.6-1. > retitle -1 libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Bug #1068045 [libssl3,yapet] libssl3: breaks YAPET Changed Bug title to 'libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB' from 'libssl3: breaks YAPET'. -- 1068045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
control: reassign -1 libssl3,yapet control: found -1 libssl3/3.1.5-1 control: found -1 yapet/2.6-1 control: retitle -1 libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Hello, On Sat 30 Mar 2024 at 03:01pm +01, Sebastian Andrzej Siewior wrote: >> >>> Also, yapet is unchanged in unstable. Is the problem there, too? >> I have now confirmed that the problem is in unstable too. -- Sean Whitton signature.asc Description: PGP signature
Bug#1036805: Processed: Severity for 1036805 was serious and we even released with it
severity 1036805 important thanks Hi, > Serious severity because it has a major effect on the usability of the > package without rendering it completely unusable, not minor No, it's not. "serious" has it's own meaning though and that's not it. At most it's important but I don't buy this since as I said back then it looked fine here. And you didn't even reply to the mail. Ignoring the moreinfo tag. Ii's also not the fine style to not CC the actual bug so the text gets actually sent there. Regards, Rene
Processed: Bug#1068463 marked as pending in procyon
Processing control commands: > tag -1 pending Bug #1068463 [procyon-decompiler] procyon: Untrusted code execution via cwd in classpath Added tag(s) pending. -- 1068463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068463: marked as pending in procyon
Control: tag -1 pending Hello, Bug #1068463 in procyon 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/java-team/procyon/-/commit/5d917ba977596412dd3b207a9195c78390cadc7b Prevent untrusted code execution from the command line (Closes: #1068463) (this message was generated automatically) -- Greetings https://bugs.debian.org/1068463
Bug#1067796: marked as done (mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment)
Your message dated Sat, 06 Apr 2024 08:42:52 +
with message-id
and subject line Bug#1067796: fixed in mailscripts 29-1
has caused the Debian Bug report #1067796,
regarding mailscripts: FTBFS: email-print-mime-structure:51: error: Unused
"type: ignore" comment
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.)
--
1067796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mailscripts
Version: 28-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --with elpa --with bash-completion
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
dh_auto_build
make -j2
make[1]: Entering directory '/<>'
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=mdmv \
mdmv.1.pod mdmv.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=mbox2maildir \
mbox2maildir.1.pod mbox2maildir.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=notmuch-slurp-debbug \
notmuch-slurp-debbug.1.pod notmuch-slurp-debbug.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=notmuch-extract-patch \
notmuch-extract-patch.1.pod notmuch-extract-patch.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=maildir-import-patch \
maildir-import-patch.1.pod maildir-import-patch.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=mbox-extract-patch \
mbox-extract-patch.1.pod mbox-extract-patch.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=imap-dl \
imap-dl.1.pod imap-dl.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=email-extract-openpgp-certs \
email-extract-openpgp-certs.1.pod email-extract-openpgp-certs.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=email-print-mime-structure \
email-print-mime-structure.1.pod email-print-mime-structure.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=notmuch-import-patch \
notmuch-import-patch.1.pod notmuch-import-patch.1
pod2man --section=1 --date="Debian Project" --center="User Commands" \
--utf8 \
--name=gmi2email \
gmi2email.1.pod gmi2email.1
mkdir -p completions/bash
register-python-argcomplete email-print-mime-structure
>completions/bash/email-print-mime-structure.tmp
mv completions/bash/email-print-mime-structure.tmp
completions/bash/email-print-mime-structure
mkdir -p completions/bash
register-python-argcomplete imap-dl >completions/bash/imap-dl.tmp
mv completions/bash/imap-dl.tmp completions/bash/imap-dl
make[1]: Leaving directory '/<>'
dh_auto_test
make -j2 check
make[1]: Entering directory '/<>'
./tests/email-print-mime-structure.sh
Testing alternative.eml
Testing attachment.eml
Testing encrypted.eml (PGPy)
/usr/lib/python3/dist-packages/pgpy/constants.py:192:
CryptographyDeprecationWarning: IDEA has been deprecated and will be removed in
a future release
bs = {SymmetricKeyAlgorithm.IDEA: algorithms.IDEA,
/usr/lib/python3/dist-packages/pgpy/constants.py:194:
CryptographyDeprecationWarning: CAST5 has been deprecated and will be removed
in a future release
SymmetricKeyAlgorithm.CAST5: algorithms.CAST5,
/usr/lib/python3/dist-packages/pgpy/constants.py:195:
CryptographyDeprecationWarning: Blowfish has been deprecated and will be
removed in a future release
SymmetricKeyAlgorithm.Blowfish: algorithms.Blowfish,
Testing encrypted.eml (GnuPG PGP/MIME)
Testing simple.eml
Testing smime-encrypted.eml (OpenSSL)
Testing smime-encrypted.eml (GnuPG S/MIME)
gpgsm: issuer certificate (#/CN=Sample LAMPS Certificate Authority) not found
Testing smime-signed.eml
mypy --strict ./email-print-mime-structure
email-print-mime-structure:51: error: Unused "type: ignore" comment
[unused-ignore]
email-print-mime-structure:53: error: Incompatible types in assignment (expression has
type "None", variable has type Module) [assignment]
email-print-mime-structure:77: error:
Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment
control: tag -1 + pending Hello, On Sat 06 Apr 2024 at 01:23am -04, Daniel Kahn Gillmor wrote: > On Sat 2024-04-06 11:40:14 +0800, Sean Whitton wrote: >> On Thu 04 Apr 2024 at 06:37pm -04, Daniel Kahn Gillmor wrote: >> >>> On Wed 2024-04-03 13:03:19 +0800, Sean Whitton wrote: Thanks, but can you sign this off? Ty! >>> >>> Sure, attached. Let me know if you need anything different. >> >> Thanks. Unfortunately, it doesn't seem to fix the FTBFS, on sid. > > Here is a replacement patch, tested now against mypy 1.9.0-4. It also > updates the typechecking for imap-dl for the same version of mypy. Thanks! Just to note that I also had to add python3-gssapi as a b-d. -- Sean Whitton signature.asc Description: PGP signature
Processed: Re: Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment
Processing control commands: > tag -1 + pending Bug #1067796 [src:mailscripts] mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment Added tag(s) pending. -- 1067796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1068179 is important
Processing commands for cont...@bugs.debian.org:
> severity 1068179 important
Bug #1068179 [ghc] FTBFS: error: warning: assignment to ‘ffi_arg’ {aka ‘long
unsigned int’} from ‘HsPtr’ {aka ‘void *’} makes integer from pointer without a
cast
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068204: marked as done (pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 subtests failed.)
Your message dated Sat, 06 Apr 2024 07:34:36 + with message-id and subject line Bug#1068204: fixed in pdl 1:2.087-1 has caused the Debian Bug report #1068204, regarding pdl: FTBFS on i386: Failed 1/45 test programs. 2/2262 subtests failed. 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.) -- 1068204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdl Version: 1:2.086-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=pdl=i386=1%3A2.086-1=1712002199=0 not ok 569 - col=0 not ok 570 - col=1 ... Test Summary Report --- t/pdl_from_string.t (Wstat: 0 Tests: 144 Failed: 0) TODO passed: 60-62 t/primitive-random.t (Wstat: 0 Tests: 3 Failed: 0) TODO passed: 1 t/slice.t(Wstat: 512 (exited 2) Tests: 602 Failed: 2) Failed tests: 569-570 Non-zero exit status: 2 Files=45, Tests=2262, 56 wallclock secs ( 0.48 usr 0.12 sys + 54.74 cusr 5.00 csys = 60.34 CPU) Result: FAIL Failed 1/45 test programs. 2/2262 subtests failed. make[2]: *** [Makefile:1077: test_dynamic] Error 255 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: pdl Source-Version: 1:2.087-1 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of pdl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated pdl 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, 06 Apr 2024 08:31:39 +0200 Source: pdl Architecture: source Version: 1:2.087-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Bas Couwenberg Closes: 1068204 Changes: pdl (1:2.087-1) unstable; urgency=medium . * Team upload. * New upstream release. (closes: #1068204) * Remove additional generated files in clean target. Checksums-Sha1: 9b26e0f3477b2286d61a58012059ffd5e695af53 2420 pdl_2.087-1.dsc b907a1a300843a0d6ea4d76b367205532ca16320 2980457 pdl_2.087.orig.tar.gz 5abe993de6a177cfb610087e8e2ce21c57b7f2d9 29532 pdl_2.087-1.debian.tar.xz 3a3682317f92fbe960e3e2b6d2512125d76524dc 14785 pdl_2.087-1_amd64.buildinfo Checksums-Sha256: 5457e31fb5b8d99fa83f3cfd79bdbb3372267b1e4524a046d0f1990826707c41 2420 pdl_2.087-1.dsc 6a321c70ff60e3ca5c687fbdf6f8c3170c867c35066a018adbfecef898a75acd 2980457 pdl_2.087.orig.tar.gz d6a008503b3c9cbb03e2467f361619cce71076fd7eace9edf0f0707c98f2a0b7 29532 pdl_2.087-1.debian.tar.xz d01df2e064f04cc8c6404f7b645a0d6d930ddb6072bc5f84a9e5b5335b142c6d 14785 pdl_2.087-1_amd64.buildinfo Files: 1911b2ae2ab050a43245cf11dbd5ae9f 2420 math optional pdl_2.087-1.dsc 4ff85228b9e9fdd6345c1178f00446d2 2980457 math optional pdl_2.087.orig.tar.gz 184aa1c9529076782e74dd98b65667b0 29532 math optional pdl_2.087-1.debian.tar.xz 0f991fcda249b26364f9d3ecf4570d6e 14785 math optional pdl_2.087-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmYQ9acACgkQZ1DxCuiN SvHUMw/+MHtSqjkXRhhwe+tZoJES08aBLWCEqXqcQ+uS8eoPEvTuk8K5C1cZ6K3i SSIIH3aJwcimmU+b2jU4+TE1qFvMt4+Hb/X/8WdFrZwUk87FIhGIa7w+yusKauhW abman1dEm0PP891nw4286wCXMzNiALVeTaVlgC8q15rrApJB/TIxCX9dAf1iFokY kgUpdzPhqWNOhOXzPYQdH1D4XV2U2yHPfZ+snu/QUzn8D5UJOAa25td0rQY7U/lo XWyJaa//fFM4jlOyvxVoUajlzZ6GisbwPf3yo0EdWecHRzBIqhLPj8hiETIMoB05 GD0PaEulE+a4UJyK33EhFP2V2oGNuMa5kS9LiJCMOUFDp8+PQBQgd3si7lyPUr/2 GtW/dWaaC9cPtlt/drRqdD/6u8CazGSiOnO0BTli08KQDR9M1vFKEOwmehMqeMe8 u1obrlEN8VPhTcSVzCP44CGO5AdQ6GBpZ1TW1gmV7fBz6/3QS9oTjmwN9x3vnVpq u6N9uFdw1tVKGU9eCNWzau1uavfkw/aZ0aORvnY4N0v4+avxA//muxm8ivCTZ9Gu H759wnreABqYOSUxZmrDJOJwEcOd7n8DhCoqTIcxq/SS6P0AyAAzapxjLedu4B/p Do1fq+giPkjTnD6bR5Af+xlZJsD8vq8pzjZ4bbjPo1V0laCgv8M= =PyTW -END PGP SIGNATURE- pgpq24eBrBHOB.pgp Description: PGP signature --- End Message ---
Processed: reassign 1068179 to ghc, affects 1068179 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1068179 ghc 9.4.7-3
Bug #1068179 [src:haskell-gi-gtk] FTBFS: error: warning: assignment to
‘ffi_arg’ {aka ‘long unsigned int’} from ‘HsPtr’ {aka ‘void *’} makes integer
from pointer without a cast
Bug reassigned from package 'src:haskell-gi-gtk' to 'ghc'.
No longer marked as found in versions haskell-gi-gtk/3.0.41-1.
Ignoring request to alter fixed versions of bug #1068179 to the same values
previously set
Bug #1068179 [ghc] FTBFS: error: warning: assignment to ‘ffi_arg’ {aka ‘long
unsigned int’} from ‘HsPtr’ {aka ‘void *’} makes integer from pointer without a
cast
Marked as found in versions ghc/9.4.7-3.
> affects 1068179 haskell-gi-gtk
Bug #1068179 [ghc] FTBFS: error: warning: assignment to ‘ffi_arg’ {aka ‘long
unsigned int’} from ‘HsPtr’ {aka ‘void *’} makes integer from pointer without a
cast
Added indication that 1068179 affects haskell-gi-gtk
> forwarded 1068179 https://gitlab.haskell.org/ghc/ghc/-/issues/23456
Bug #1068179 [ghc] FTBFS: error: warning: assignment to ‘ffi_arg’ {aka ‘long
unsigned int’} from ‘HsPtr’ {aka ‘void *’} makes integer from pointer without a
cast
Set Bug forwarded-to-address to
'https://gitlab.haskell.org/ghc/ghc/-/issues/23456'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068473: icinga2: crashes on startup on ppc64el
On 4/5/24 9:51 PM, Aurelien Jarno wrote: For Bookworm given we can not fix the compiler easily, I propose to just build icinga2 with -O1 on ppc64el. If you are fine with that option, I can take care of proposing a patch and submitting it to the stable release team. A patch for this is very welcome. How do you propose to implement that? Something like this maybe? --- a/debian/rules +++ b/debian/rules @@ -9,6 +9,11 @@ include /usr/share/dpkg/architecture.mk export CTEST_OUTPUT_ON_FAILURE=1 +ifneq (,$(filter $(DEB_HOST_ARCH), ppc64el)) + export DEB_CXXFLAGS_STRIP = -O2 + export DEB_CXXFLAGS_MAINT_APPEND = -O1 +endif + ifneq (,$(filter $(DEB_HOST_ARCH), armel mips mipsel powerpc)) export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic -Wl,--as-needed endif Note that we ignore test failures on ppc64el which might have caught this issue. Upstream doesn't care about those architectures, so we're on our own to resolve issues on architectures other than amd64/i386/arm64. Pretty much all packages I maintain don't have actual users on non-amd64 architectures, so I don't consider it worth the effort to ask the porters for help, they should spend their time on packages that are actually used. With DSA's use of icinga2 on porterboxes it's the exception to the norm. PowerPC porters, can you help fix the test failures of icinga2 on ppc64el? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
