Processed: Re: Bug#1067952: mes: FTBFS on armhf
Processing control commands: > forwarded 1067952 > https://lists.gnu.org/archive/html/bug-mes/2024-01/msg8.html Bug #1067952 [src:mes] mes: FTBFS on armhf Set Bug forwarded-to-address to 'https://lists.gnu.org/archive/html/bug-mes/2024-01/msg8.html'. -- 1067952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067952: mes: FTBFS on armhf
Control: forwarded 1067952 https://lists.gnu.org/archive/html/bug-mes/2024-01/msg8.html On 2024-03-29, Kentaro HAYASHI wrote: > mes 0.26-1 fails to build on armhf. > > FYI: > > https://buildd.debian.org/status/fetch.php?pkg=mes=armhf=0.26-1=1704511792=0 Yeah, forwarded this upstream in January, but have not yet found a fix. live well, vagrant signature.asc Description: PGP signature
Bug#1067376: [nore...@release.debian.org: gforth is marked for autoremoval from testing]
I had a look at building gforth 0.7.3 from within Debian sid and dpkg- buildpackage. What's happening here is that lt_dlopen() can't find the just generated files; the generated libraries are in the build directory (a subdirectory of it) and fine, they are just in a place where the loader doesn't look at. The development snapshots (which will become Gforth 1.0 soon) have a solution for that that isn't too easy to backport, and doesn't work for cross-compiling (the cross compiled libraries won't load into the host's Gforth), in which case these errors are just ignored. Therefore I recommend to ignore the error, see attached libcc-err-ignore.patch (to be applied last). Furthermore, I have some issues building Gforth 0.7.3 when the current development Gforth is already installed. That patch (gforth-ditc-for- kernel.patch) could become useful in future. When you already are at it: What I would strongly recommend to revert the removal of the documentation: It's GFDL with no invariant sections, so it is compatible with the Debian rules since 2006 (which was even before we released Gforth 0.7). Gforth without documentation isn't very useful, we recommend Gforth users not to use Debian's package for any other purpose than to compile the source code (from git; the tarball doesn't need it). But for that purpose it should stay there. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/ Description: Ignore failure on open-lib with libcc build stuff Author: Bernd Paysan Bug-Debian: https://bugs.debian.org/1067376 Last-Update: 2024-03-30 --- gforth-0.7.3+dfsg.orig/Makefile.in +++ gforth-0.7.3+dfsg/Makefile.in @@ -652,7 +652,7 @@ uninstall: FORCE build-libcc-named: $(LIBCC_BUILD_SRC) $(FORTH_GEN) $(GEN) FORCE $(RMTREE) lib/gforth/$(VERSION)/libcc-named/ - for i in $(LIBCC_BUILD_SRC); do ./gforth -e "s\" `pwd`/lib/gforth/$(VERSION)/libcc-named/\" libcc-named-dir-v 2! libcc-path clear-path libcc-named-dir libcc-path also-path :noname 2drop s\" $(libccdir)\" ; is replace-rpath" $(srcdir)/$$i -e bye; done + -for i in $(LIBCC_BUILD_SRC); do ./gforth -e "s\" `pwd`/lib/gforth/$(VERSION)/libcc-named/\" libcc-named-dir-v 2! libcc-path clear-path libcc-named-dir libcc-path also-path :noname 2drop s\" $(libccdir)\" ; is replace-rpath" $(srcdir)/$$i -e bye; done check: gforths gforth.fi $(MAKE) checkone check-nofast ENGINE="./gforth --no-dynamic" >/dev/null 2>&1 Description: Build gforth-ditc first before building the kernel, use gforth-ditc for that Author: Bernd Paysan Bug-Debian: https://bugs.debian.org/1067376 Last-Update: 2024-03-30 --- gforth-0.7.3+dfsg.orig/Makefile.in +++ gforth-0.7.3+dfsg/Makefile.in @@ -449,7 +449,7 @@ FORTH_GEN = $(FORTH_GEN0) @KERNEL@ gfor FORTH_GEN1 = $(FORTH_GEN0) @kernel_fi@ build-ec #kernel dependencies -KERN_DEPS = $(KERN_SRC) kernel/version.fs machpc.fs $(FORTH_GEN0) compat/strcomp.fs +KERN_DEPS = $(KERN_SRC) kernel/version.fs machpc.fs $(FORTH_GEN0) gforth-ditc$(EC)$(EXE) compat/strcomp.fs #distributed documentation DOCDIST = doc/gforth.info doc/gforth.info-* doc/gforth.ps \ --- gforth-0.7.3+dfsg.orig/preforth.in +++ gforth-0.7.3+dfsg/preforth.in @@ -17,7 +17,7 @@ #You should have received a copy of the GNU General Public License #along with this program. If not, see http://www.gnu.org/licenses/. -test -z "$ENGINE" && ENGINE=./gforth +test -z "$ENGINE" && ENGINE=./gforth-ditc test -f "@srcdir@/@kernel_fi@" && KERNEL="@srcdir@/@kernel_fi@" test -f "@kernel_fi@" && KERNEL="@kernel_fi@" if test -f $ENGINE -a -f $KERNEL; then signature.asc Description: This is a digitally signed message part.
Bug#1068116: python-pylibdmtx: depends on pre-t64 packages
Source: python-pylibdmtx Version: 0.1.10-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org python3-pylibdtmtx depends on a package that was renamed for the time_t 64 transition. The dependency needs to be updated to the new package name. Cheers -- Sebastian Ramacher
Bug#1068115: tardy: FTBFS on arm{el,hf}: ./tardy/main.cc:282:(.text.startup+0x578): undefined reference to `tardy_mtime(long)'
Source: tardy Version: 1.25-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=tardy=armel=1.25-2%2Bb2=1711746975=0 g++ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -I. -c libtardy/version.cc mv version.o libtardy/version.o rm -f libtardy/libtardy.a ar qc libtardy/libtardy.a libtardy/ac/stdio.o libtardy/ac/string.o libtardy/ac/zlib.o libtardy/arglex.o libtardy/cannonical.o libtardy/endian.o libtardy/file/input.o libtardy/file/input/factory.o libtardy/file/input/gunzip.o libtardy/file/input/normal.o libtardy/file/input/position.o libtardy/file/input/stdin.o libtardy/file/output.o libtardy/file/output/buffer.o libtardy/file/output/factory.o libtardy/file/output/gzip.o libtardy/file/output/hexdump.o libtardy/file/output/normal.o libtardy/file/output/stdout.o libtardy/filenamelist.o libtardy/filenamelist/file.o libtardy/filenamelist/filter.o libtardy/filenamelist/filter/progress.o libtardy/format_family.o libtardy/fstrcmp.o libtardy/gmatch.o libtardy/mprintf.o libtardy/rcstring.o libtardy/rcstring/accumulator.o libtardy/rcstring/accumulator/pop_front.o libtardy/rcstring/accumulator/printf.o libtardy/rcstring/basename.o libtardy/rcstring/clear.o libtardy/rcstring/dirname.o libtardy/rcstring/downcase.o libtardy/rcstring/ends_with.o libtardy/rcstring/eq.o libtardy/rcstring/hexdump.o libtardy/rcstring/list/appelistuniq.o libtardy/rcstring/list/append.o libtardy/rcstring/list/append_list.o libtardy/rcstring/list/append_uniqu.o libtardy/rcstring/list/assign_op.o libtardy/rcstring/list/clear.o libtardy/rcstring/list/constructor.o libtardy/rcstring/list/copy.o libtardy/rcstring/list/destructor.o libtardy/rcstring/list/equal.o libtardy/rcstring/list/intersection.o libtardy/rcstring/list/member.o libtardy/rcstring/list/member_nocas.o libtardy/rcstring/list/pop_back.o libtardy/rcstring/list/pop_front.o libtardy/rcstring/list/prepend.o libtardy/rcstring/list/prepend_list.o libtardy/rcstring/list/quote.o libtardy/rcstring/list/remove.o libtardy/rcstring/list/remove_list.o libtardy/rcstring/list/sort.o libtardy/rcstring/list/sort_long_short.o libtardy/rcstring/list/sort_nocase.o libtardy/rcstring/list/sort_vers.o libtardy/rcstring/list/str2wl.o libtardy/rcstring/list/subset.o libtardy/rcstring/list/validate.o libtardy/rcstring/list/wl2str.o libtardy/rcstring/list/xor.o libtardy/rcstring/printf.o libtardy/rcstring/quote_c.o libtardy/rcstring/substitute.o libtardy/rcstring/substring.o libtardy/rcstring/upcase.o libtardy/read_whole_directory.o libtardy/roff.o libtardy/symtab.o libtardy/tar/format.o libtardy/tar/header.o libtardy/tar/input.o libtardy/tar/input/ar.o libtardy/tar/input/ar/bsd.o libtardy/tar/input/ar/factory.o libtardy/tar/input/ar/pdp11.o libtardy/tar/input/ar/v7.o libtardy/tar/input/cpio.o libtardy/tar/input/cpio/binary.o libtardy/tar/input/cpio/crc.o libtardy/tar/input/cpio/factory.o libtardy/tar/input/cpio/new_ascii.o libtardy/tar/input/cpio/old_ascii.o libtardy/tar/input/directory.o libtardy/tar/input/factory.o libtardy/tar/input/filename.o libtardy/tar/input/filenamelist.o libtardy/tar/input/filter.o libtardy/tar/input/filter/ar_long_names.o libtardy/tar/input/filter/ar_long_names2.o libtardy/tar/input/filter/clean.o libtardy/tar/input/filter/exclude.o libtardy/tar/input/filter/group_name.o libtardy/tar/input/filter/group_numbr.o libtardy/tar/input/filter/gunzip.o libtardy/tar/input/filter/mode_clear.o libtardy/tar/input/filter/mode_set.o libtardy/tar/input/filter/mtime.o libtardy/tar/input/filter/prefix.o libtardy/tar/input/filter/relative_paths.o libtardy/tar/input/filter/remov_prefi.o libtardy/tar/input/filter/remove_prefix_count.o libtardy/tar/input/filter/suppr_direc.o libtardy/tar/input/filter/user_name.o libtardy/tar/input/filter/user_number.o libtardy/tar/input/tar.o libtardy/tar/input/tar/bsd.o libtardy/tar/input/tar/posix.o libtardy/tar/input/tar/ustar.o libtardy/tar/input/tar_output_factory.o libtardy/tar/output.o libtardy/tar/output/ar.o libtardy/tar/output/ar/bsd.o libtardy/tar/output/ar/pdp11.o libtardy/tar/output/ar/port5.o libtardy/tar/output/ar/v7.o libtardy/tar/output/cpio.o libtardy/tar/output/cpio/binary.o libtardy/tar/output/cpio/crc.o libtardy/tar/output/cpio/newascii.o libtardy/tar/output/cpio/oldascii.o libtardy/tar/output/extract.o libtardy/tar/output/filter.o libtardy/tar/output/filter/ar_long_names.o libtardy/tar/output/filter/ar_long_names2.o libtardy/tar/output/filter/basename.o libtardy/tar/output/filter/gzip.o libtardy/tar/output/filter/list.o libtardy/tar/output/tar.o libtardy/tar/output/tar/bsd.o libtardy/tar/output/tar/posix.o libtardy/tar/output/tar/ustar.o libtardy/tar/output/tar/v7.o libtardy/trace.o
Bug#1068100: armci-mpi: autopkgtest spuriously fails
Samuel Thibault, le sam. 30 mars 2024 16:55:11 +0100, a ecrit:
> 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.
I have uploaded the attached changes to delayed/2.
Samuel
diff -Nru armci-mpi-0.3.1~beta/debian/changelog
armci-mpi-0.3.1~beta/debian/changelog
--- armci-mpi-0.3.1~beta/debian/changelog 2023-03-19 14:08:54.0
+0100
+++ armci-mpi-0.3.1~beta/debian/changelog 2024-03-30 23:17:18.0
+0100
@@ -1,3 +1,12 @@
+armci-mpi (0.3.1~beta-7.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * patches/fix-test.patch: Fix test_mpi_indexed_gets.c test and strengthen
+the others. Closes: #1066227.
+ * patches/ftbfs.patch: Fix build with qa=+bug-implicit-func.
+
+ -- Samuel Thibault Sat, 30 Mar 2024 23:17:18 +0100
+
armci-mpi (0.3.1~beta-7) unstable; urgency=medium
* Team upload.
diff -Nru armci-mpi-0.3.1~beta/debian/patches/fix-test.patch
armci-mpi-0.3.1~beta/debian/patches/fix-test.patch
--- armci-mpi-0.3.1~beta/debian/patches/fix-test.patch 1970-01-01
01:00:00.0 +0100
+++ armci-mpi-0.3.1~beta/debian/patches/fix-test.patch 2024-03-30
23:17:18.0 +0100
@@ -0,0 +1,193 @@
+https://github.com/pmodels/armci-mpi/pull/47
+
+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
+
+---
+ tests/mpi/test_mpi_accs.c |2 +-
+ tests/mpi/test_mpi_indexed_accs.c |6 +++---
+ tests/mpi/test_mpi_indexed_gets.c | 12 +++-
+ tests/mpi/test_mpi_indexed_puts_gets.c |6 +++---
+ tests/mpi/test_mpi_subarray_accs.c |6 +++---
+ 5 files changed, 17 insertions(+), 15 deletions(-)
+
+--- a/tests/mpi/test_mpi_indexed_gets.c
b/tests/mpi/test_mpi_indexed_gets.c
+@@ -19,7 +19,7 @@
+
+ #define XDIM 8
+ #define YDIM 1024
+-#define SUB_XDIM 8
++#define SUB_XDIM 4
+ #define SUB_YDIM 256
+
+ int main(int argc, char **argv) {
+@@ -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);
+
+@@ -88,7 +90,7 @@ int main(int argc, char **argv) {
+ for (j = 0; j < SUB_YDIM; j++) {
+ const double actual = *(loc_buf + i + j*XDIM);
+ const double expected = (1.0 + peer);
+-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++;
+@@ -100,7 +102,7 @@ int main(int argc, char **argv) {
+ for (j = 0; j < SUB_YDIM; j++) {
+ const double actual = *(loc_buf + i + j*XDIM);
+ const double expected = 1.0 + rank;
+-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++;
+@@ -112,7 +114,7 @@ int main(int argc, char **argv) {
+ for (j = SUB_YDIM; j < YDIM; j++) {
+ const double actual = *(loc_buf + i + j*XDIM);
+ const double expected = 1.0 + rank;
+-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++;
+--- a/tests/mpi/test_mpi_accs.c
b/tests/mpi/test_mpi_accs.c
+@@ -55,7 +55,7 @@ int main(int argc, char **argv) {
+
Bug#1068043: BinNMU 1.11-1+b1 depends on both, libmspack0 and libmspack0t64, and is hence uninstallable (at least on armhf)
On Fri, Mar 29, 2024 at 6:30 PM Axel Beckert wrote: > This is likely caused by hardcoding a dependency on libmspack0 in > debian/control: > > https://sources.debian.org/src/cabextract/1.11-1/debian/control/#L10 > The hardcoded dependency was added for Debian bug #914263 to work around an issue in libmspack0. It's probably been long enough that it's no longer needed and can be removed. Eric Sharkey
Bug#1068068: Need rebootstrapping on armel and armhf
On Sat, Mar 30, 2024 at 01:29:42PM +0500, Andrey Rakhmatullin wrote: > 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). Thank you for the bug report. Frank (the upstream author) is in the process of updating icmake to no longer depend on bobcat, thus breaking the cycle. signature.asc Description: PGP signature
Bug#1061203: marked as done (gtkmm2.4: upstream branch is end-of life)
Your message dated Sat, 30 Mar 2024 16:04:58 -0400 with message-id and subject line Re: gtkmm2.4: upstream branch is end-of life has caused the Debian Bug report #1061203, regarding gtkmm2.4: upstream branch is end-of life 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.) -- 1061203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtkmm2.4 Severity: serious While gtkmm 3.x and 4.x are still maintained, gtkmm2.4 is abandoned upstream. It should not be released with trixie, even if the gtk2 removal does not happen. A popular reverse dependency is ardour, which is in the process of vendoring the gtkmm2.4 parts that it needs, so ardour should not be considered a blocker. --- End Message --- --- Begin Message --- I am closing this bug because it is a duplicate of the much older https://bugs.debian.org/967497 . The other bug is also correctly linked to bugs for the remaining reverse dependencies in Testing. Merging the 2 bugs doesn't look helpful to me. Speaking for the Debian GNOME team: we are not opposed to the removal of gtkmm2.4, but you'll need to work with the maintainers of those reverse dependencies. However, GTK2 will not be removed from Debian Testing for a long time and I personally don't see much benefit to removing the C++ bindings when the C library is still permitted. There were reasons to move faster for pygtk, libgnome, etc. On behalf of the Debian GNOME team, Jeremy Bícha--- End Message ---
Bug#1066438: backuppc-rsync: FTBFS: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’
Le 13/03/2024 à 13:02, Lucas Nussbaum a écrit : […] Hi, During a rebuild of all packages in sid, your package failed to build on amd64. […] Thanks for such information. Since no action was taken in last 2 weeks, I opened a bug upstream [1]. [1] https://github.com/backuppc/rsync-bpc/issues/40 I was able to reproduce this bug, but I am not able to resolv it as I do not understand how rsync-bpc is made from rsync. :-/ Thanks for any hint and regards. -- J. Fernando Lagrange Absent les mercredis des semaines paires PROBESYS - Spécialistes OpenSource 9 rue de chamrousse 38100 Grenoble Standard : 09 74 76 47 86 GLPi: 01 86 95 99 85 site web : https://www.probesys.com
Processed: Bug#1068047 marked as pending in libarchive
Processing control commands: > tag -1 pending Bug #1068047 [libarchive13t64] Suspicious commit merged in 2021 from account responsible for xz backdoor Added tag(s) pending. -- 1068047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068047: marked as pending in libarchive
Control: tag -1 pending Hello, Bug #1068047 in libarchive reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/libarchive/-/commit/31fcf28c3be82824c34dd115c7465748adb2b787 Add the robust-error-reporting upstream patch Closes: #1068047 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068047
Bug#1068104: pandas: FTBFS on 32-bit architectures with -D_TIME_BITS=64
Source: pandas Version: 2.1.4+dfsg-6 Severity: serious Tags: ftbfs patch Hi Maintainer pandas FTBFS on 32-bit architectures with -D_TIME_BITS=64 (e.g. armel and armhf), due to tests expected to fail, now passing. I've copied what I hope are the relevant parts of the log below. The following is my first attempt at a patch, which would pass on armel and armhf, but fail on i386 and hurd-i386, which are not built with -D_TIME_BITS=64. --- a/pandas/tests/indexes/datetimes/test_ops.py +++ b/pandas/tests/indexes/datetimes/test_ops.py @@ -33,7 +33,7 @@ ) def test_resolution(self, request, tz_naive_fixture, freq, expected): tz = tz_naive_fixture -if freq == "A" and not IS64 and isinstance(tz, tzlocal): +if freq == "A" and isinstance(tz, tzlocal): request.node.add_marker( pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038") ) --- a/pandas/tests/tseries/offsets/test_common.py +++ b/pandas/tests/tseries/offsets/test_common.py @@ -139,7 +139,7 @@ if tz is not None: assert t.tzinfo is not None -if isinstance(tz, tzlocal) and not IS64 and _offset is not DateOffset: +if isinstance(tz, tzlocal) and _offset is not DateOffset: # If we hit OutOfBoundsDatetime on non-64 bit machines # we'll drop out of the try clause before the next test request.node.add_marker( The following is my second attempt at a patch, which does not fail if the expected test failures succeed. --- a/pandas/tests/indexes/datetimes/test_ops.py +++ b/pandas/tests/indexes/datetimes/test_ops.py @@ -35,7 +35,7 @@ tz = tz_naive_fixture if freq == "A" and not IS64 and isinstance(tz, tzlocal): request.node.add_marker( -pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038") +pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038",strict=False) ) idx = date_range(start="2013-04-01", periods=30, freq=freq, tz=tz) --- a/pandas/tests/tseries/offsets/test_common.py +++ b/pandas/tests/tseries/offsets/test_common.py @@ -143,7 +143,7 @@ # If we hit OutOfBoundsDatetime on non-64 bit machines # we'll drop out of the try clause before the next test request.node.add_marker( -pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038") +pytest.mark.xfail(reason="OverflowError inside tzlocal past 2038", strict=False) ) elif ( isinstance(tz, tzlocal) Regards Graham [1] https://buildd.debian.org/status/logs.php?pkg=pandas=armhf [2] https://buildd.debian.org/status/logs.php?pkg=pandas=armel === short test summary info FAILED pandas/tests/indexes/datetimes/test_ops.py::TestDatetimeIndexOps::test_resolution[tzlocal()-A-day] = 1 failed, 15623 passed, 383 skipped, 5 deselected, 46 xfailed, 4 xpassed in 47.98s = rdjoqkol test state = false === short test summary info FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BusinessDay] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BusinessHour] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BusinessMonthEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BusinessMonthBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BQuarterEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-BQuarterBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-CustomBusinessDay] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-CustomBusinessHour] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-CustomBusinessMonthEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-CustomBusinessMonthBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-MonthEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-MonthBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-SemiMonthBegin] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-SemiMonthEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-QuarterEnd] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-LastWeekOfMonth] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-WeekOfMonth] FAILED pandas/tests/tseries/offsets/test_common.py::test_apply_out_of_range[tzlocal()-Week]
Processed: Re: Bug#1068047: Suspicious commit merged in 2021 from account responsible for xz backdoor
Processing control commands: > severity -1 serious Bug #1068047 [libarchive13t64] Suspicious commit merged in 2021 from account responsible for xz backdoor Severity set to 'serious' from 'important' > found -1 3.6.0-1 Bug #1068047 [libarchive13t64] Suspicious commit merged in 2021 from account responsible for xz backdoor There is no source info for the package 'libarchive13t64' at version '3.6.0-1' with architecture '' Unable to make a source version for version '3.6.0-1' Marked as found in versions 3.6.0-1. -- 1068047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053196: Please remove librados-dev build-depends on all 32 bits arch
Hi, Looks like a patch with fix for this issue is already in the repository. A release with this fix before April 8th would prevent auto-removal of a uwsgi and a large number of dependencies including freedombox from testing. Thank you for all the contributions, -- Sunil OpenPGP_0x36C361440C9BC971.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1068100: armci-mpi: autopkgtest spuriously fails
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++) {
const double actual = *(win_buf + 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++;
@@ -109,7 +109,7 @@ int main(int argc, char **argv) {
for (j = 0; j < SUB_YDIM; j++) {
const double actual = *(win_buf + i + j*XDIM);
const double expected = 1.0 + rank;
-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++;
Processed: reassign 1067272 to haskell-haskell-gi, affects 1067272 ...
Processing commands for cont...@bugs.debian.org: > reassign 1067272 haskell-haskell-gi 0.26.7-2 Bug #1067272 [src:haskell-gi-glib] haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1 Bug reassigned from package 'src:haskell-gi-glib' to 'haskell-haskell-gi'. No longer marked as found in versions haskell-gi-glib/2.0.29-1. Ignoring request to alter fixed versions of bug #1067272 to the same values previously set Bug #1067272 [haskell-haskell-gi] haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1 There is no source info for the package 'haskell-haskell-gi' at version '0.26.7-2' with architecture '' Unable to make a source version for version '0.26.7-2' Marked as found in versions 0.26.7-2. > affects 1067272 haskell-gi-glib Bug #1067272 [haskell-haskell-gi] haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1 Added indication that 1067272 affects haskell-gi-glib > forwarded 1067272 https://github.com/haskell-gi/haskell-gi/pull/430 Bug #1067272 [haskell-haskell-gi] haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1 Set Bug forwarded-to-address to 'https://github.com/haskell-gi/haskell-gi/pull/430'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1067272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
On 30 March 2024 13:14:37 CET, Sean Whitton wrote: >Hello, Hi, >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. > >> Also, yapet is unchanged in unstable. Is the problem there, too? > >Unfortunately I do not have an unstable machine to hand right now, and >until we know more about the xz-utils situation I would want to set up >something air-gapped before copying my password db in there -- but can >do that if we can't otherwise make progress. The 5.6 xz is no more in unstable. But as you wish. I was just curious why this was not yet reported. > >Thanks for looking! > -- Sebastian
Bug#1068068: Need rebootstrapping on armel and armhf
On Sat, Mar 30, 2024 at 02:14:24PM +0100, Frank B. Brokken wrote: > > there seems to be zero packaging-level support for bootstrapping, the > > packages are not cross-buildable and the upstream bootstrapping instructions > > are too tedious, > > So far no issues were encountered when the bootstrapping procedure as > described in the README.bobatbootstrap file in icmake's src distribution is > followed. > > If you could be a bit more specific about what you mean by 'bootstrapping > instructions are too tedious' then I'm sure those instructions can be changed > so that they're less tedious. It looked to me that I need to make a chroot, run the bootstrap script to build some kind of local bootstrap bobcat, build local icmake with that bobcat, build local bobcat with that icmake, build the icmake .deb, install it in a new chroot, build the bobcat .deb, then ideally build a clean icmake .deb again; and do that twice as two architectures need bootstrapping. This is much much much more than I'm going to do for random packages so I decided against it. > Wrt the package not being cross-buildable: > > The https://packages.debian.org/sid/libbobcat-dev shows the following lines > for armel and armhf: > > armel 6.04.00-1 1,604.2 kB 8,598.0 kB [list of files] > armhf 6.04.00-1 1,608.4 kB 8,126.0 kB [list of files] > > although I also see packages for which version 6.04.00-1+b2 or 6.04.00-1+b4 is > listed. So maybe for unstable some issues recently appeared? Not sure what did you want to say here, sorry? By not being cross-buildable I mean they lack cross-building support, both at the packaging level (no proper M-A headers, no B-D annotation) and at the upstream level (the gcc running was not the cross one). > Also, the bootstrapping procedure is only required when icmake isn't avaialble > yet. For the construction of the bobcat library icmake 11.01.02-1 is required, > and icmake.01.02-1 needs libbobcat-dev >= 5.07.00, which is available since > bullseye (oldstable). icmake is indeed not available on armel and armhf until libbobcat6 is rebuilt against libssl3t64. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1068068: Need rebootstrapping on armel and armhf
Dear Andrey Rakhmatullin, you wrote: > > 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). Thanks for your bug report. You write: > there seems to be zero packaging-level support for bootstrapping, the > packages are not cross-buildable and the upstream bootstrapping instructions > are too tedious, So far no issues were encountered when the bootstrapping procedure as described in the README.bobatbootstrap file in icmake's src distribution is followed. If you could be a bit more specific about what you mean by 'bootstrapping instructions are too tedious' then I'm sure those instructions can be changed so that they're less tedious. Wrt the package not being cross-buildable: The https://packages.debian.org/sid/libbobcat-dev shows the following lines for armel and armhf: armel 6.04.00-1 1,604.2 kB 8,598.0 kB [list of files] armhf 6.04.00-1 1,608.4 kB 8,126.0 kB [list of files] although I also see packages for which version 6.04.00-1+b2 or 6.04.00-1+b4 is listed. So maybe for unstable some issues recently appeared? Also, the bootstrapping procedure is only required when icmake isn't avaialble yet. For the construction of the bobcat library icmake 11.01.02-1 is required, and icmake.01.02-1 needs libbobcat-dev >= 5.07.00, which is available since bullseye (oldstable). So maybe you can also provide some info about why the bootstrapping procedure is needed/used? In any case: the dependence on icmake when constructing the full bobcat library could be avoided, but I'd rather not do that once icmake *is* available. So please advise. -- Frank B. Brokken (+31) 6 5353 2509 PGP Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA signature.asc Description: PGP signature
Processed: Bug#1014781 marked as pending in mom
Processing control commands: > tag -1 pending Bug #1014781 [mom] momd crashing due to error in HypervisorInterfaces/libvirtInterface.py Added tag(s) pending. -- 1014781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014781: marked as pending in mom
Control: tag -1 pending Hello, Bug #1014781 in mom reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/mom/-/commit/3e078bba96232b0dae1080c5d6a52dde7e50ea8e Fix python2 code for python3 (str vs bytes) Closes: #1014781 (this message was generated automatically) -- Greetings https://bugs.debian.org/1014781
Bug#1068090: Update Build-Depends for the time64 library renames
Source: tetzle Version: 2.2.3-1 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libqt6*, this needs to be changed to libqt6*t64 if it's needed at all. -- 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
Bug#1068089: FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}
Source: ukui-control-center
Version: 3.22.1.25-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=ukui-control-
center=armhf=3.22.1.25-2=1711794461=0
plugins/about/aboutinterface.cpp: In member function ‘char*
AboutInterface::ntpdate(char*)’:
plugins/about/aboutinterface.cpp:438:18: error: cannot convert ‘long int*’ to
‘const time_t*’ {aka ‘const long long int*’}
438 | return ctime();
| ^
| |
| long int*
In file included from /usr/include/features.h:490,
from /usr/include/arm-linux-
gnueabihf/c++/13/bits/os_defines.h:39,
from /usr/include/arm-linux-
gnueabihf/c++/13/bits/c++config.h:679,
from /usr/include/c++/13/type_traits:38,
from /usr/include/arm-linux-gnueabihf/qt5/QtCore/qglobal.h:45,
from /usr/include/arm-linux-
gnueabihf/qt5/QtCore/qnamespace.h:43,
from /usr/include/arm-linux-
gnueabihf/qt5/QtCore/qobjectdefs.h:48,
from /usr/include/arm-linux-gnueabihf/qt5/QtCore/qobject.h:46,
from /usr/include/arm-linux-gnueabihf/qt5/QtCore/QObject:1,
from plugins/about/aboutinterface.h:21,
from plugins/about/aboutinterface.cpp:18:
/usr/include/time.h:186:14: note: initializing argument 1 of ‘char*
ctime(const time_t*)’
186 | extern char *__REDIRECT_NTH (ctime, (const time_t *__timer),
__ctime64);
| ^~
-- 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
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
Hello, On Sat 30 Mar 2024 at 09:29am +01, Sebastian Andrzej Siewior wrote: > On 2024-03-30 09:25:27 [+0800], Sean Whitton wrote: >> Package: libssl3 >> Version: 3.0.13-1~deb12u1 >> Severity: grave >> Justification: renders package unusable >> X-Debbugs-Cc: t...@security.debian.org >> Control: affects -1 + yapet >> >> Dear maintainer, >> >> This version of libssl3 from bookworm-proposed-updates breaks YAPET. >> When I try to open my passwords database, it claims the master password I >> type >> is incorrect. But downgrading libssl3 fixes the problem. > > Can you give me more to go on? I installed yapet created a database, > updated and it remains to work. > Maybe supply a test database which works with the old but not with the > new library. 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? > Also, yapet is unchanged in unstable. Is the problem there, too? Unfortunately I do not have an unstable machine to hand right now, and until we know more about the xz-utils situation I would want to set up something air-gapped before copying my password db in there -- but can do that if we can't otherwise make progress. Thanks for looking! -- Sean Whitton signature.asc Description: PGP signature
Bug#1068056: ccls: FTBFS on armhf,i386 (test_response failures)
Control: severity -1 wishlist Control: forcemerge 1068055 -1 On Sat, Mar 30, 2024 at 2:57 PM Kentaro HAYASHI wrote: > > Source: ccls > Severity: serious > Tags: ftbfs > Control: found -1 0.20230717-1 > X-Debbugs-Cc: ken...@xdump.org > > Dear Maintainer, > > ccls fails to build on armhf, i386. > As explained in 1068055. -- Shengjing Zhu
Processed: Re: Bug#1068056: ccls: FTBFS on armhf,i386 (test_response failures)
Processing control commands: > severity -1 wishlist Bug #1068056 [src:ccls] ccls: FTBFS on armhf,i386 (test_response failures) Severity set to 'wishlist' from 'serious' > forcemerge 1068055 -1 Bug #1068055 [src:ccls] ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0') Bug #1068056 [src:ccls] ccls: FTBFS on armhf,i386 (test_response failures) Merged 1068055 1068056 -- 1068055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068055 1068056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068055: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')
Control: severity -1 wishlist On Sat, Mar 30, 2024 at 3:00 PM Kentaro HAYASHI wrote: > > Source: ccls > Severity: serious > Tags: ftbfs > Control: found -1 2.6.0-1 > X-Debbugs-Cc: ken...@xdump.org > > Dear Maintainer, > > ccls fails to build on armel. (missing linking against with -latomic) It's fine, as it never successfully built before. Even if it builds, the test will fail. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934408 -- Shengjing Zhu
Processed: Re: Bug#1068055: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')
Processing control commands: > severity -1 wishlist Bug #1068055 [src:ccls] ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0') Severity set to 'wishlist' from 'serious' -- 1068055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066623: marked as done (daemontools: FTBFS: pathexec_run.c:18:5: error: implicit declaration of function ‘execve’ [-Werror=implicit-function-declaration])
Your message dated Sat, 30 Mar 2024 11:50:01 + with message-id and subject line Bug#1066623: fixed in daemontools 1:0.76-10 has caused the Debian Bug report #1066623, regarding daemontools: FTBFS: pathexec_run.c:18:5: error: implicit declaration of function ‘execve’ [-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.) -- 1066623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: daemontools Version: 1:0.76-9 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): > make[2]: Entering directory '/<>/daemontools-0.76/compile' > sh find-systype.sh > systype > rm -f compile > sh print-cc.sh > compile > chmod 555 compile > ./compile byte_chr.c > ./compile byte_copy.c > ./compile byte_cr.c > ./compile byte_diff.c > ./compile byte_rchr.c > ./compile fmt_uint.c > ./compile fmt_uint0.c > ./compile fmt_ulong.c > rm -f makelib > sh print-ar.sh > makelib > chmod 555 makelib > ./compile scan_ulong.c > ./compile str_chr.c > ./compile str_diff.c > ./compile str_len.c > ./compile str_start.c > ./makelib byte.a byte_chr.o byte_copy.o byte_cr.o byte_diff.o \ > byte_rchr.o fmt_uint.o fmt_uint0.o fmt_ulong.o scan_ulong.o str_chr.o \ > str_diff.o str_len.o str_start.o > rm -f choose > cat warn-auto.sh choose.sh \ > | sed s}HOME}"`head -1 home`"}g \ > > choose > chmod 555 choose > ./choose c trydrent direntry.h1 direntry.h2 > direntry.h > ./compile envdir.c > rm -f load > sh print-ld.sh > load > chmod 555 load > ./compile alloc.c > ./compile alloc_re.c > ./compile buffer.c > ./compile buffer_0.c > ./compile buffer_1.c > ./compile buffer_2.c > ./compile buffer_get.c > ./compile buffer_put.c > ./compile buffer_read.c > ./compile buffer_write.c > ./compile coe.c > ./compile env.c > ./compile error.c > ./compile error_str.c > ./compile fd_copy.c > ./compile fd_move.c > ./choose cl trymkffo hasmkffo.h1 hasmkffo.h2 > hasmkffo.h > ./compile fifo.c > ./choose cl tryflock hasflock.h1 hasflock.h2 > hasflock.h > ./compile lock_ex.c > ./compile lock_exnb.c > ./compile ndelay_off.c > ./compile ndelay_on.c > ./compile open_append.c > ./compile open_read.c > ./compile open_trunc.c > ./compile open_write.c > ./compile openreadclose.c > ./compile pathexec_env.c > ./compile pathexec_run.c > pathexec_run.c: In function ‘pathexec_run’: > pathexec_run.c:18:5: error: implicit declaration of function ‘execve’ > [-Werror=implicit-function-declaration] >18 | execve(file,argv,envp); > | ^~ > pathexec_run.c:18:17: warning: passing argument 2 of ‘execve’ from > incompatible pointer type [-Wincompatible-pointer-types] >18 | execve(file,argv,envp); > | ^~~~ > | | > | const char * const* > pathexec_run.c:18:17: note: expected ‘char * const*’ but argument is of type > ‘const char * const*’ > pathexec_run.c:18:22: warning: passing argument 3 of ‘execve’ from > incompatible pointer type [-Wincompatible-pointer-types] >18 | execve(file,argv,envp); > | ^~~~ > | | > | const char * const* > pathexec_run.c:18:22: note: expected ‘char * const*’ but argument is of type > ‘const char * const*’ > pathexec_run.c:35:18: warning: passing argument 2 of ‘execve’ from > incompatible pointer type [-Wincompatible-pointer-types] >35 | execve(tmp.s,argv,envp); > | ^~~~ > | | > | const char * const* > pathexec_run.c:35:18: note: expected ‘char * const*’ but argument is of type > ‘const char * const*’ > pathexec_run.c:35:23: warning: passing argument 3 of ‘execve’ from > incompatible pointer type [-Wincompatible-pointer-types] >35 | execve(tmp.s,argv,envp); > | ^~~~ > | | > | const char * const* > pathexec_run.c:35:23: note: expected ‘char * const*’ but argument is of type > ‘const char * const*’ > cc1: some warnings being treated as errors > make[2]: *** [Makefile:244: pathexec_run.o]
Bug#1068064: marked as done (Update Build-Depends for the time64 library renames)
Your message dated Sat, 30 Mar 2024 09:51:57 + with message-id and subject line Bug#1068064: fixed in node-node-sass 7.0.3+git20221109.ee13eb9+dfsg-4 has caused the Debian Bug report #1068064, regarding Update Build-Depends for the time64 library renames 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.) -- 1068064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-node-sass Version: 7.0.3git20221109.ee13eb9dfsg-3 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libuv1, this needs to be changed to libuv1t64 if it's needed at all. -- 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: node-node-sass Source-Version: 7.0.3+git20221109.ee13eb9+dfsg-4 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-node-sass, 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. Yadd (supplier of updated node-node-sass 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, 30 Mar 2024 13:35:38 +0400 Source: node-node-sass Built-For-Profiles: nocheck Architecture: source Version: 7.0.3+git20221109.ee13eb9+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1068064 Changes: node-node-sass (7.0.3+git20221109.ee13eb9+dfsg-4) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.6.2 * Drop build dependency to libuv1-dev (Closes: #1068064) Checksums-Sha1: 934b5e2ab6d0ec8c4a28d0ee464d7ebb9bdef651 5896 node-node-sass_7.0.3+git20221109.ee13eb9+dfsg-4.dsc f6616e956a717950c258c86f034a4aa7783172c5 18456 node-node-sass_7.0.3+git20221109.ee13eb9+dfsg-4.debian.tar.xz Checksums-Sha256: af2dd6ca8a68cb1f12466287cbb846587ad176b94ba54d15c38865fe0727b2f7 5896 node-node-sass_7.0.3+git20221109.ee13eb9+dfsg-4.dsc a4925d8bed7998764ee0c2af1e5a9bf367c29015fe81b631e8267f41d55496e5 18456 node-node-sass_7.0.3+git20221109.ee13eb9+dfsg-4.debian.tar.xz Files: e6c7dacbefbabc96a2dc78f482cbcf8a 5896 javascript optional node-node-sass_7.0.3+git20221109.ee13eb9+dfsg-4.dsc 27665475436854a588ee1e6ba27110e7 18456 javascript optional node-node-sass_7.0.3+git20221109.ee13eb9+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmYH3S8ACgkQ9tdMp8mZ 7ulQWQ/+L+SLCZ9jtXBQ5obNKt/zxJ4q+zZFElhiycyQ757TugbLGMiqfTJvGmUM l9/a5hrK3R2tq5WMw8E6bX9+Xus9P/gdVXLy1Epjwdhidc6o/Zl3cAaLGZqZ6JZT 4EzW11n4riHK90LG86slaD15HniiyEmirfUG+Eppl4u/exfzenaKtMGMxktTRxaX bbF6EqeUjmacSLuOUBL1BnvW0voX6PG4oon9Y63qh6Y8OPDYPek6yqrD129pn8RF AT2GH5TKEQv8k7DxACbLeYulS5CmUY608D1j1M5RLDEyJfE6YYh+pGdRXfnUMwXc F5oxeRIre+gdWgsXQFwQkL3C/VXAr7/nJ+9Zq7cEpNkKlIzb/uRDT65CzEq8GllK VnbrR6HRHfQkBudGKYLiksO5BNDotMWEt17ezusPoOR+d9s+u2LgPRn+G0af9eos 78SXwNrQN60bzrUTpo9qqboUgqtqj9lHTiNjj36UuZO4RoyYSuu1AZT78nfSylA+ fSb1wv3dtzzVbKkfoZkPug+GTZSkUcrfFnyVXVX9d5WiuqQLp+y3RXHlvrRnh4As Z1BHUnPPFGutmMppol+U4Pr5eBkMvJuY8OqDTTXRhu2WVQklXx6cl3B1MNtcRo6b nSERlDI7BJRIm3nmX87VNTMxZOSBWT5DhBKhmA1+mYAqdGq+s90= =PkEb -END PGP SIGNATURE- pgpfIlGnqZzwJ.pgp Description: PGP signature --- End Message ---
Processed: bug 1067290 is forwarded to https://github.com/architest/pymeeus/issues/24
Processing commands for cont...@bugs.debian.org: > forwarded 1067290 https://github.com/architest/pymeeus/issues/24 Bug #1067290 [src:pymeeus] pymeeus: FTBFS: FAILED tests/test_interpolation.py::test_interpolation_call - RuntimeError: I... Set Bug forwarded-to-address to 'https://github.com/architest/pymeeus/issues/24'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1067290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1068064 marked as pending in node-node-sass
Processing control commands: > tag -1 pending Bug #1068064 [src:node-node-sass] Update Build-Depends for the time64 library renames Added tag(s) pending. -- 1068064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068064: marked as pending in node-node-sass
Control: tag -1 pending Hello, Bug #1068064 in node-node-sass 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/js-team/node-node-sass/-/commit/6c9e9c0ea92b4555f23df79fd9409677468cac85 Drop build dependency to libuv1-dev Closes: #1068064 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068064
Bug#1068080: Depends on a pre-t64 library name: libvdeplug2
Package: libvdeslirp0 Version: 0.1.1-1 Severity: serious libvdeslirp0 explicitly Depends on libvdeplug2, this needs to be changed to libvdeplug2t64. -- 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 Versions of packages libvdeslirp0 depends on: ii libc6 2.37-15.1 ii libslirp0 4.7.0-1+b1 ii libvdeplug2t64 [libvdeplug2] 4.0.1-5.1 libvdeslirp0 recommends no packages. libvdeslirp0 suggests no packages.
Processed: block 1036884 with 1068068
Processing commands for cont...@bugs.debian.org: > block 1036884 with 1068068 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1055352 1067509 1067494 1067676 1067193 1065816 1067171 1062847 1067916 1065787 1067288 1067189 1066049 1067069 1065973 1067192 1067272 1067508 1067561 1055530 1067677 1067190 1066794 1067458 1067175 1067829 1067170 1066328 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1068068 > thanks Stopping processing here. Please contact me if you need assistance. -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068078: FTBFS on armel: shiboken2:smart::smart_pointer Newly detected Real test failure!
Source: pyside2 Version: 5.15.12-6.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=pyside2=armel=5.15.12-6.1=1711789575=0 RUN 2: Test project /<>/pyside3_build/py3.11-qt5.15.10-32bit- relwithdebinfo/shiboken2 RUN 2: Start 181: smart_smart_pointer RUN 2: 1/1 Test #181: smart_smart_pointer ..***Failed0.23 sec RUN 2: Running garbage collector for reference test RUN 2: FFF RUN 2: == RUN 2: FAIL: testObjSmartPointer (__main__.SmartPointerTests.testObjSmartPointer) RUN 2: -- RUN 2: Traceback (most recent call last): RUN 2: File "/<>/sources/shiboken2/tests/smartbinding/smart_pointer_test.py", line 94, in testObjSmartPointer RUN 2: self.assertEqual(integerCount(), 1) RUN 2: AssertionError: 2 != 1 RUN 2: RUN 2: == RUN 2: FAIL: testSmartPointerConversions (__main__.SmartPointerTests.testSmartPointerConversions) RUN 2: -- RUN 2: Traceback (most recent call last): RUN 2: File "/<>/sources/shiboken2/tests/smartbinding/smart_pointer_test.py", line 221, in testSmartPointerConversions RUN 2: self.assertEqual(integerCount(), 1) RUN 2: AssertionError: 2 != 1 RUN 2: RUN 2: == RUN 2: FAIL: testSmartPointersWithNamespace (__main__.SmartPointerTests.testSmartPointersWithNamespace) RUN 2: -- RUN 2: Traceback (most recent call last): RUN 2: File "/<>/sources/shiboken2/tests/smartbinding/smart_pointer_test.py", line 182, in testSmartPointersWithNamespace RUN 2: self.assertEqual(integerCount(), 2) RUN 2: AssertionError: 3 != 2 RUN 2: RUN 2: -- RUN 2: Ran 7 tests in 0.010s RUN 2: RUN 2: FAILED (failures=3) RUN 2: RUN 2: RUN 2: 0% tests passed, 1 tests failed out of 1 RUN 2: RUN 2: Total Test time (real) = 0.25 sec RUN 2: RUN 2: The following tests FAILED: RUN 2: 181 - smart_smart_pointer (Failed) RUN 2: Errors while running CTest End of the test run RES 2: Test #181: FAIL! smart::smart_pointer() -- 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
Bug#1066444: marked as done (nacl: FTBFS due to -Werror=implicit-function-declaration)
Your message dated Sat, 30 Mar 2024 09:05:37 + with message-id and subject line Bug#1066444: fixed in nacl 20110221-14 has caused the Debian Bug report #1066444, regarding nacl: FTBFS due to -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.) -- 1066444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nacl Version: 20110221-13 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): > make[1]: Entering directory '/<>' > ./do > echo 'log' > log > echo '===' > === > cat build/debianbuildhost/log > === Tue Mar 12 20:30:43 UTC 2024 === starting > === Tue Mar 12 20:30:43 UTC 2024 === hostname > ip-10-84-234-227 > === Tue Mar 12 20:30:43 UTC 2024 === uname -a > Linux ip-10-84-234-227 6.1.0-13-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian > 6.1.55-1 (2023-09-29) x86_64 GNU/Linux > === Tue Mar 12 20:30:43 UTC 2024 === uname -M > uname: invalid option -- 'M' > Try 'uname --help' for more information. > === Tue Mar 12 20:30:43 UTC 2024 === uname -F > uname: invalid option -- 'F' > Try 'uname --help' for more information. > === Tue Mar 12 20:30:43 UTC 2024 === /usr/sbin/lscfg | grep proc > ./do: 57: /usr/sbin/lscfg: not found > === Tue Mar 12 20:30:43 UTC 2024 === /usr/sbin/lsattr -El proc0 > ./do: 59: /usr/sbin/lsattr: not found > === Tue Mar 12 20:30:43 UTC 2024 === cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family: 6 > model : 85 > model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz > stepping : 7 > microcode : 0x5003605 > cpu MHz : 2499.996 > cache size: 36608 KB > physical id : 0 > siblings : 8 > core id : 0 > cpu cores : 4 > apicid: 0 > initial apicid: 0 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp: yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm > constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni > pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt > tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm > 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms > invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd > avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke > bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds > swapgs itlb_multihit mmio_stale_data retbleed gds > bogomips : 4999.99 > clflush size : 64 > cache_alignment : 64 > address sizes : 46 bits physical, 48 bits virtual > power management: > > processor : 1 > vendor_id : GenuineIntel > cpu family: 6 > model : 85 > model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz > stepping : 7 > microcode : 0x5003605 > cpu MHz : 2499.996 > cache size: 36608 KB > physical id : 0 > siblings : 8 > core id : 1 > cpu cores : 4 > apicid: 2 > initial apicid: 2 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp: yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm > constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni > pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt > tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm > 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms > invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd > avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke > bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds > swapgs itlb_multihit mmio_stale_data retbleed gds > bogomips : 4999.99 > clflush size : 64 > cache_alignment : 64 > address sizes : 46 bits physical, 48 bits virtual > power management: > > processor : 2 > vendor_id : GenuineIntel > cpu family: 6 > model : 85 > model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz > stepping : 7 > microcode : 0x5003605 > cpu MHz : 2499.996 >
Processed: block 1036884 with 1067916
Processing commands for cont...@bugs.debian.org: > block 1036884 with 1067916 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1062847 1067288 1066794 1067193 1067190 1067458 1067069 1066328 1067676 1055352 1067170 1067509 1067171 1067829 1067494 1067561 1066049 1065816 1065973 1055530 1067175 1067677 1067272 1067508 1065787 1067189 1067192 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1067916 > thanks Stopping processing here. Please contact me if you need assistance. -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068075: Update Build-Depends for the time64 library renames
Source: tanglet Version: 1.6.5-1 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libqt6*, this needs to be changed to libqt6*t64 if it's needed at all. -- 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
Bug#1068074: Update Build-Depends for the time64 library renames
Source: koko Version: 23.08.5ds.1-1 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libqt5gui5, this needs to be changed to libqt5gui5t64 if it's needed at all. -- 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
Bug#1068073: Hardcoded dependency on liblcmaps0
source: lcmaps-plugins-verify-proxy
version: 1.5.10-2
severity: serious
During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for architectures like armel and armhf, where these
hardcoded dependency on the old package name are now not satisfiable.
Please change these to use either the new name or to depend on either
the old or the new name (liblcmaps0 | liblcmaps0t64).
Package: lcmaps-plugins-verify-proxy
Depends: ${shlibs:Depends}, ${misc:Depends}, liblcmaps0
Mattias
signature.asc
Description: This is a digitally signed message part
Bug#1068072: Hardcoded dependency on liblcmaps0
source: lcmaps-plugins-basic
version: 1.7.1-1
severity: serious
During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for architectures like armel and armhf, where these
hardcoded dependency on the old package name are now not satisfiable.
Please change these to use either the new name or to depend on either
the old or the new name (liblcmaps0 | liblcmaps0t64).
Package: lcmaps-plugins-basic-dummy
Depends: ${misc:Depends}, ${shlibs:Depends}, liblcmaps0
Package: lcmaps-plugins-basic-localaccount
Depends: ${misc:Depends}, ${shlibs:Depends}, liblcmaps0
Package: lcmaps-plugins-basic-poolaccount
Depends: ${misc:Depends}, ${shlibs:Depends}, liblcmaps0
Package: lcmaps-plugins-basic-posixenf
Depends: ${misc:Depends}, ${shlibs:Depends}, liblcmaps0
Package: lcmaps-plugins-basic-ldap
Depends: ${misc:Depends}, ${shlibs:Depends}, liblcmaps0
Mattias
signature.asc
Description: This is a digitally signed message part
Bug#1068071: Hardcoded dependency on liblcmaps0
source: lcmaps-plugins-jobrep
version: 1.5.6-1.1
severity: serious
During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for architectures like armel and armhf, where these
hardcoded dependency on the old package name are now not satisfiable.
Please change these to use either the new name or to depend on either
the old or the new name (liblcmaps0 | liblcmaps0t64).
Package: lcmaps-plugins-jobrep
Depends: ${shlibs:Depends}, ${misc:Depends}, liblcmaps0
Mattias
signature.asc
Description: This is a digitally signed message part
Bug#1068070: Hardcoded dependency on liblcmaps0
source: lcmaps-plugins-voms
version: 1.7.1-1
severity: serious
During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for architectures like armel and armhf, where these
hardcoded dependency on the old package name are now not satisfiable.
Please change these to use either the new name or to depend on either
the old or the new name (liblcmaps0 | liblcmaps0t64).
Package: lcmaps-plugins-voms
Depends: ${shlibs:Depends}, ${misc:Depends},
liblcmaps0 (>= 1.5.0)
Mattias
signature.asc
Description: This is a digitally signed message part
Bug#1066328: marked as done (scalapack: FTBFS: igsum2d_.c:154:7: error: implicit declaration of function ‘BI_imvcopy’; did you mean ‘BI_zmvcopy’? [-Werror=implicit-function-declaration])
Your message dated Sat, 30 Mar 2024 08:37:41 + with message-id and subject line Bug#1066328: fixed in scalapack 2.2.1-3.1 has caused the Debian Bug report #1066328, regarding scalapack: FTBFS: igsum2d_.c:154:7: error: implicit declaration of function ‘BI_imvcopy’; did you mean ‘BI_zmvcopy’? [-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.) -- 1066328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scalapack Version: 2.2.1-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): > make[4]: Entering directory '/<>/build-openmpi' > [ 0%] Building C object CMakeFiles/scalapack.dir/BLACS/SRC/dgesd2d_.c.o > /usr/bin/mpicc.openmpi -DAdd_ -Dscalapack_EXPORTS > -I/usr/lib/x86_64-linux-gnu/openmpi/include > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -pedantic -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -MD -MT > CMakeFiles/scalapack.dir/BLACS/SRC/dgesd2d_.c.o -MF > CMakeFiles/scalapack.dir/BLACS/SRC/dgesd2d_.c.o.d -o > CMakeFiles/scalapack.dir/BLACS/SRC/dgesd2d_.c.o -c > /<>/BLACS/SRC/dgesd2d_.c > [ 0%] Building C object CMakeFiles/scalapack.dir/BLACS/SRC/dtrsd2d_.c.o > [ 0%] Building C object CMakeFiles/scalapack.dir/BLACS/SRC/igesd2d_.c.o > [ 0%] Building C object CMakeFiles/scalapack.dir/BLACS/SRC/zgesd2d_.c.o > [ 0%] Building C object CMakeFiles/scalapack.dir/BLACS/SRC/strsd2d_.c.o > [ 0%] Building C object CMakeFiles/scalapack.dir/BLACS/SRC/itrsd2d_.c.o > /usr/bin/mpicc.openmpi -DAdd_ -Dscalapack_EXPORTS > -I/usr/lib/x86_64-linux-gnu/openmpi/include > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -pedantic -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -MD -MT > CMakeFiles/scalapack.dir/BLACS/SRC/igesd2d_.c.o -MF > CMakeFiles/scalapack.dir/BLACS/SRC/igesd2d_.c.o.d -o > CMakeFiles/scalapack.dir/BLACS/SRC/igesd2d_.c.o -c > /<>/BLACS/SRC/igesd2d_.c > /usr/bin/mpicc.openmpi -DAdd_ -Dscalapack_EXPORTS > -I/usr/lib/x86_64-linux-gnu/openmpi/include > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -pedantic -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -MD -MT > CMakeFiles/scalapack.dir/BLACS/SRC/zgesd2d_.c.o -MF > CMakeFiles/scalapack.dir/BLACS/SRC/zgesd2d_.c.o.d -o > CMakeFiles/scalapack.dir/BLACS/SRC/zgesd2d_.c.o -c > /<>/BLACS/SRC/zgesd2d_.c > /usr/bin/mpicc.openmpi -DAdd_ -Dscalapack_EXPORTS > -I/usr/lib/x86_64-linux-gnu/openmpi/include > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -pedantic -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -MD -MT > CMakeFiles/scalapack.dir/BLACS/SRC/strsd2d_.c.o -MF > CMakeFiles/scalapack.dir/BLACS/SRC/strsd2d_.c.o.d -o > CMakeFiles/scalapack.dir/BLACS/SRC/strsd2d_.c.o -c > /<>/BLACS/SRC/strsd2d_.c > /usr/bin/mpicc.openmpi -DAdd_ -Dscalapack_EXPORTS > -I/usr/lib/x86_64-linux-gnu/openmpi/include > -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wall -pedantic -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -MD -MT > CMakeFiles/scalapack.dir/BLACS/SRC/dtrsd2d_.c.o -MF > CMakeFiles/scalapack.dir/BLACS/SRC/dtrsd2d_.c.o.d -o > CMakeFiles/scalapack.dir/BLACS/SRC/dtrsd2d_.c.o -c > /<>/BLACS/SRC/dtrsd2d_.c > /usr/bin/mpicc.openmpi -DAdd_ -Dscalapack_EXPORTS > -I/usr/lib/x86_64-linux-gnu/openmpi/include >
Bug#1066656: marked as done (libkysdk-base: FTBFS: libkyconf.c:74:9: error: implicit declaration of function ‘isxml’ [-Werror=implicit-function-declaration])
Your message dated Sat, 30 Mar 2024 08:35:47 + with message-id and subject line Bug#1066656: fixed in libkysdk-base 2.2.0.1-1.1 has caused the Debian Bug report #1066656, regarding libkysdk-base: FTBFS: libkyconf.c:74:9: error: implicit declaration of function ‘isxml’ [-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.) -- 1066656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libkysdk-base Version: 2.2.0.1-1 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): > cd /<>/obj-x86_64-linux-gnu/src/config && /usr/bin/cc > -Dkysdk_config_EXPORTS -I/<>/obj-x86_64-linux-gnu > -I/<>/src/config -I/<>/src/utils > -I/<>/src/log -I/<>/src/timer > -I/<>/src/gsettings -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 -fPIC -MD -MT > src/config/CMakeFiles/kysdk-config.dir/structparse.c.o -MF > CMakeFiles/kysdk-config.dir/structparse.c.o.d -o > CMakeFiles/kysdk-config.dir/structparse.c.o -c > /<>/src/config/structparse.c > [ 21%] Building C object src/config/CMakeFiles/kysdk-config.dir/xmlparse.c.o > /<>/src/config/libkyconf.c: In function ‘get_conf_type’: > /<>/src/config/libkyconf.c:74:9: error: implicit declaration of > function ‘isxml’ [-Werror=implicit-function-declaration] >74 | if (isxml(confpath)) > | ^ > cd /<>/obj-x86_64-linux-gnu/src/config && /usr/bin/cc > -Dkysdk_config_EXPORTS -I/<>/obj-x86_64-linux-gnu > -I/<>/src/config -I/<>/src/utils > -I/<>/src/log -I/<>/src/timer > -I/<>/src/gsettings -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 -fPIC -MD -MT > src/config/CMakeFiles/kysdk-config.dir/xmlparse.c.o -MF > CMakeFiles/kysdk-config.dir/xmlparse.c.o.d -o > CMakeFiles/kysdk-config.dir/xmlparse.c.o -c > /<>/src/config/xmlparse.c > /<>/src/config/libkyconf.c:76:14: error: implicit declaration of > function ‘isjson’ [-Werror=implicit-function-declaration] >76 | else if (isjson(confpath)) > | ^~ > /<>/src/config/libkyconf.c:78:14: error: implicit declaration of > function ‘isgsettings’ [-Werror=implicit-function-declaration] >78 | else if (isgsettings(confpath)) > | ^~~ > /<>/src/config/libkyconf.c: In function ‘kdk_conf_reload’: > /<>/src/config/libkyconf.c:238:24: warning: passing argument 1 > of ‘S_destroyParse’ from incompatible pointer type > [-Wincompatible-pointer-types] > 238 | S_destroyParse(>data); > |^~~ > || > |void ** > In file included from /<>/src/config/libkyconf.c:23: > /<>/src/config/structparse.h:55:42: note: expected ‘structParse > **’ but argument is of type ‘void **’ >55 | extern void S_destroyParse(structParse **parse); > |~~^ > [ 23%] Building CXX object > src/diagnostics/CMakeFiles/kydiagnostics.dir/buriedpoint.cpp.o > cd /<>/obj-x86_64-linux-gnu/src/diagnostics && /usr/bin/c++ > -Dkydiagnostics_EXPORTS -I/<>/obj-x86_64-linux-gnu > -I/<>/src/config -I/<>/src/utils > -I/<>/src/log -I/<>/src/timer > -I/<>/src/gsettings -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/<>/src/diagnostics > -I/<>/obj-x86_64-linux-gnu/src/diagnostics -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden > -fvisibility-inlines-hidden -Wall -g -MD -MT > src/diagnostics/CMakeFiles/kydiagnostics.dir/buriedpoint.cpp.o -MF > CMakeFiles/kydiagnostics.dir/buriedpoint.cpp.o.d -o > CMakeFiles/kydiagnostics.dir/buriedpoint.cpp.o -c > /<>/src/diagnostics/buriedpoint.cpp > [ 25%] Linking C shared library
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
On 2024-03-30 09:25:27 [+0800], Sean Whitton wrote: > Package: libssl3 > Version: 3.0.13-1~deb12u1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: t...@security.debian.org > Control: affects -1 + yapet > > Dear maintainer, > > This version of libssl3 from bookworm-proposed-updates breaks YAPET. > When I try to open my passwords database, it claims the master password I type > is incorrect. But downgrading libssl3 fixes the problem. Can you give me more to go on? I installed yapet created a database, updated and it remains to work. Maybe supply a test database which works with the old but not with the new library. Also, yapet is unchanged in unstable. Is the problem there, too? Sebastian
Bug#1068068: Need rebootstrapping on armel and armhf
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
Processed: fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed))
Processing control commands: > found -1 1.3.0-3 Bug #1068067 [src:fpzip] fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed)) Marked as found in versions fpzip/1.3.0-3. -- 1068067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068067: fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed))
Source: fpzip Severity: serious Tags: ftbfs Control: found -1 1.3.0-3 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, fpzip fails to build on armel, armhf, i386. FYI: https://buildd.debian.org/status/fetch.php?pkg=fpzip=armel=1.3.0-3=1685884820=0 https://buildd.debian.org/status/fetch.php?pkg=fpzip=armhf=1.3.0-3=1650541490=0 https://buildd.debian.org/status/fetch.php?pkg=fpzip=i386=1.3.0-3=1685885227=0 Regards,
Processed: docker-registry: FTBFS on armhf (test failure with DriverSuite.TestDeleteOnlyDeletesSubpaths)
Processing control commands: > found -1 2.8.2+ds1-1+b4 Bug #1068066 [src:docker-registry] docker-registry: FTBFS on armhf (test failure with DriverSuite.TestDeleteOnlyDeletesSubpaths) The source 'docker-registry' and version '2.8.2+ds1-1+b4' do not appear to match any binary packages Marked as found in versions docker-registry/2.8.2+ds1-1+b4. -- 1068066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068066: docker-registry: FTBFS on armhf (test failure with DriverSuite.TestDeleteOnlyDeletesSubpaths)
Source: docker-registry Severity: serious Tags: ftbfs Control: found -1 2.8.2+ds1-1+b4 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, docker-registry fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=docker-registry=armhf=2.8.2%2Bds1-1%2Bb4=1704669577=0 Regards,
Bug#1068065: quorum: FTBFS on armel, armhf,i386 (error: no matching function for call to ‘min(const long long unsigned int&, unsigned int)’)
Source: quorum Severity: serious Tags: ftbfs Control: found -1 1.1.2-2 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, quorum fails to build on armel, armhf, i386. FYI: https://buildd.debian.org/status/fetch.php?pkg=quorum=armel=1.1.2-2=1701603381=0 https://buildd.debian.org/status/fetch.php?pkg=quorum=armhf=1.1.2-2=1701603270=0 https://buildd.debian.org/status/fetch.php?pkg=quorum=i386=1.1.2-2=1701603340=0 Regards,
Processed: quorum: FTBFS on armel, armhf,i386 (error: no matching function for call to ‘min(const long long unsigned int&, unsigned int)’)
Processing control commands: > found -1 1.1.2-2 Bug #1068065 [src:quorum] quorum: FTBFS on armel, armhf,i386 (error: no matching function for call to ‘min(const long long unsigned int&, unsigned int)’) Marked as found in versions quorum/1.1.2-2. -- 1068065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1036884 with 1067272 1067494 1067829 1067561
Processing commands for cont...@bugs.debian.org: > block 1036884 with 1067272 1067494 1067829 1067561 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1067193 1067171 1065787 1055530 1067190 1067509 1067189 1067458 1067069 1062847 1067288 1067677 1055352 1065973 1065816 1067192 1066049 1067676 1066794 1066328 1067170 1067508 1067175 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1067272, 1067829, 1067494, and 1067561 > thanks Stopping processing here. Please contact me if you need assistance. -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068064: Update Build-Depends for the time64 library renames
Source: node-node-sass Version: 7.0.3git20221109.ee13eb9dfsg-3 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libuv1, this needs to be changed to libuv1t64 if it's needed at all. -- 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
Processed: sssd: FTBFS on armel, armhf (test failures with test_pam_xxx, test_user_xxx... for 2.9.x)
Processing control commands: > found -1 2.9.4-1.1 Bug #1068063 [src:sssd] sssd: FTBFS on armel, armhf (test failures with test_pam_xxx, test_user_xxx... for 2.9.x) Marked as found in versions sssd/2.9.4-1.1. -- 1068063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068063: sssd: FTBFS on armel, armhf (test failures with test_pam_xxx, test_user_xxx... for 2.9.x)
Source: sssd Severity: serious Tags: ftbfs Control: found -1 2.9.4-1.1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, sssd fails to build on armel, armhf. Though test suite failure was already reported, but target version is 1.11.5.1-1, not 2.x branch. so I've filed as a new bug to raise attension. sssd: FTBFS on many archs due to testsuite failures https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754618 FYI: https://buildd.debian.org/status/fetch.php?pkg=sssd=armel=2.9.4-1.1=1711454828=0 https://buildd.debian.org/status/fetch.php?pkg=sssd=armhf=2.9.4-1.1=1711455028=0 Regards,
Bug#1068062: Update Build-Depends for the time64 library renames
Source: workrave Version: 1.10.52-1 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libglib2.0-0, this needs to be changed to libglib2.0-0t64 if it's needed at all. -- 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
Processed: libkysdk-base: diff for NMU version 2.2.0.1-1.1
Processing control commands: > tags 1066656 + patch Bug #1066656 [src:libkysdk-base] libkysdk-base: FTBFS: libkyconf.c:74:9: error: implicit declaration of function ‘isxml’ [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1066656 + pending Bug #1066656 [src:libkysdk-base] libkysdk-base: FTBFS: libkyconf.c:74:9: error: implicit declaration of function ‘isxml’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: scalapack: diff for NMU version 2.2.1-3.1
Processing control commands: > tags 1066328 + patch Bug #1066328 [src:scalapack] scalapack: FTBFS: igsum2d_.c:154:7: error: implicit declaration of function ‘BI_imvcopy’; did you mean ‘BI_zmvcopy’? [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1066328 + pending Bug #1066328 [src:scalapack] scalapack: FTBFS: igsum2d_.c:154:7: error: implicit declaration of function ‘BI_imvcopy’; did you mean ‘BI_zmvcopy’? [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066656: libkysdk-base: diff for NMU version 2.2.0.1-1.1
Control: tags 1066656 + patch
Control: tags 1066656 + pending
Dear maintainer,
I've prepared an NMU for libkysdk-base (versioned as 2.2.0.1-1.1) and
uploaded it to unstable.
Regards.
--
WBR, wRAR
diff -Nru libkysdk-base-2.2.0.1/debian/changelog libkysdk-base-2.2.0.1/debian/changelog
--- libkysdk-base-2.2.0.1/debian/changelog 2023-09-20 07:25:52.0 +0500
+++ libkysdk-base-2.2.0.1/debian/changelog 2024-03-30 12:44:02.0 +0500
@@ -1,3 +1,10 @@
+libkysdk-base (2.2.0.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066656).
+
+ -- Andrey Rakhmatullin Sat, 30 Mar 2024 12:44:02 +0500
+
libkysdk-base (2.2.0.1-1) unstable; urgency=medium
* New upstream release.
diff -Nru libkysdk-base-2.2.0.1/debian/patches/fix-implicit-function-declaration.patch libkysdk-base-2.2.0.1/debian/patches/fix-implicit-function-declaration.patch
--- libkysdk-base-2.2.0.1/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500
+++ libkysdk-base-2.2.0.1/debian/patches/fix-implicit-function-declaration.patch 2024-03-30 12:44:02.0 +0500
@@ -0,0 +1,31 @@
+Description: Add missing header includes.
+Author: Andrey Rakhmatullin
+Bug-Debian: https://bugs.debian.org/1066656
+Last-Update: 2024-03-30
+
+Index: libkysdk-base-2.2.0.1/src/config/libkyconf.c
+===
+--- libkysdk-base-2.2.0.1.orig/src/config/libkyconf.c
libkysdk-base-2.2.0.1/src/config/libkyconf.c
+@@ -21,6 +21,9 @@
+
+ #include "libkyconf.h"
+ #include "structparse.h"
++#include "jsonparse.h"
++#include "gsettingsparse.h"
++#include "xmlparse.h"
+ #include
+ #include
+ #include
+Index: libkysdk-base-2.2.0.1/src/log/writeFile.c
+===
+--- libkysdk-base-2.2.0.1.orig/src/log/writeFile.c
libkysdk-base-2.2.0.1/src/log/writeFile.c
+@@ -25,6 +25,7 @@
+ #include
+ #include
+ #include
++#include
+
+ static int verify_file(char *pFileName)
+ {
diff -Nru libkysdk-base-2.2.0.1/debian/patches/series libkysdk-base-2.2.0.1/debian/patches/series
--- libkysdk-base-2.2.0.1/debian/patches/series 1970-01-01 05:00:00.0 +0500
+++ libkysdk-base-2.2.0.1/debian/patches/series 2024-03-30 12:44:02.0 +0500
@@ -0,0 +1 @@
+fix-implicit-function-declaration.patch
signature.asc
Description: PGP signature
Bug#1066328: scalapack: diff for NMU version 2.2.1-3.1
Control: tags 1066328 + patch Control: tags 1066328 + pending Dear maintainer, I've prepared an NMU for scalapack (versioned as 2.2.1-3.1) and uploaded it to unstable. Regards. -- WBR, wRAR diff -Nru scalapack-2.2.1/debian/changelog scalapack-2.2.1/debian/changelog --- scalapack-2.2.1/debian/changelog 2023-10-26 03:08:06.0 +0500 +++ scalapack-2.2.1/debian/changelog 2024-03-30 11:47:52.0 +0500 @@ -1,3 +1,11 @@ +scalapack (2.2.1-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Disable -Werror=implicit-function-declaration as that's the only viable +way to make this build (Closes: #1066328). + + -- Andrey Rakhmatullin Sat, 30 Mar 2024 11:47:52 +0500 + scalapack (2.2.1-3) unstable; urgency=medium * Team upload. diff -Nru scalapack-2.2.1/debian/rules scalapack-2.2.1/debian/rules --- scalapack-2.2.1/debian/rules 2023-10-26 03:08:06.0 +0500 +++ scalapack-2.2.1/debian/rules 2024-03-30 11:47:00.0 +0500 @@ -6,6 +6,10 @@ export DEB_CXXFLAGS_MAINT_APPEND = -Wall -pedantic export DEB_FFLAGS_MAINT_APPEND = -std=legacy export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions +# remove -Werror=implicit-function-declaration until BLACS is properly fixed +# https://bugs.debian.org/1066328 +# https://github.com/Reference-ScaLAPACK/scalapack/issues/31 +export DEB_BUILD_MAINT_OPTIONS = qa=-bug-implicit-func include /usr/share/dpkg/architecture.mk signature.asc Description: PGP signature
Bug#1068059: Update Build-Depends for the time64 library renames
Source: gimp-gap Version: 2.6.0dfsg-7 Severity: serious Tags: ftbfs The package explicitly Build-Depends: libglib2.0-0, this needs to be changed to libglib2.0-0t64 if it's needed at all. -- 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
Processed: libgtkada: FTBFS on armhf ( compilation of gtkada-canvas_view.adb failed)
Processing control commands: > found -1 24.0.0-2 Bug #1068058 [src:libgtkada] libgtkada: FTBFS on armhf ( compilation of gtkada-canvas_view.adb failed) Marked as found in versions libgtkada/24.0.0-2. -- 1068058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libgtkada: FTBFS on armel (error: /usr/bin/gprbuild test failed at compile time! )
Processing control commands: > found -1 24.0.0-2 Bug #1068057 [src:libgtkada] libgtkada: FTBFS on armel (error: /usr/bin/gprbuild test failed at compile time! ) Marked as found in versions libgtkada/24.0.0-2. -- 1068057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068058: libgtkada: FTBFS on armhf ( compilation of gtkada-canvas_view.adb failed)
Source: libgtkada Severity: serious Tags: ftbfs Control: found -1 24.0.0-2 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, libgtkada fails to build on armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=libgtkada=armhf=24.0.0-2=1710988310=0 Regards,
Bug#1068057: libgtkada: FTBFS on armel (error: /usr/bin/gprbuild test failed at compile time! )
Source: libgtkada Severity: serious Tags: ftbfs Control: found -1 24.0.0-2 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, libgtkada fails to build on armel. FYI: https://buildd.debian.org/status/fetch.php?pkg=libgtkada=armel=24.0.0-2=1711025590=0 Regards,
Bug#1041803: [Debian-pan-maintainers] Bug#1041803: hyperspy: FTBFS test_image fails
Control: tags -1 ftbfs
Processed: Re: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')
Processing control commands: > notfound -1 2.6.0-1 Bug #1068055 [src:ccls] ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0') The source 'ccls' and version '2.6.0-1' do not appear to match any binary packages No longer marked as found in versions ccls/2.6.0-1. -- 1068055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068055: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')
Control: notfound -1 2.6.0-1
Processed: Re: [Debian-pan-maintainers] Bug#1041803: hyperspy: FTBFS test_image fails
Processing control commands: > tags -1 ftbfs Bug #1041803 [hyperspy] hyperspy: FTBFS test_image fails Added tag(s) ftbfs. -- 1041803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ccls: FTBFS on armhf,i386 (test_response failures)
Processing control commands: > found -1 0.20230717-1 Bug #1068056 [src:ccls] ccls: FTBFS on armhf,i386 (test_response failures) Marked as found in versions ccls/0.20230717-1. -- 1068056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068056: ccls: FTBFS on armhf,i386 (test_response failures)
Source: ccls Severity: serious Tags: ftbfs Control: found -1 0.20230717-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, ccls fails to build on armhf, i386. FYI: https://buildd.debian.org/status/fetch.php?pkg=ccls=armhf=0.20230717-1=1694985920=0 https://buildd.debian.org/status/fetch.php?pkg=ccls=i386=0.20230717-1=1694985457=0 Regards,
Processed: Re: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')
Processing control commands: > found -1 Bug #1068055 [src:ccls] ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0') Ignoring request to alter fixed versions of bug #1068055 to the same values previously set > found -1 0.20230717-1 Bug #1068055 [src:ccls] ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0') Marked as found in versions ccls/0.20230717-1. -- 1068055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068055: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')
Control: found -1 Control: found -1 0.20230717-1
Processed: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')
Processing control commands: > found -1 2.6.0-1 Bug #1068055 [src:ccls] ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0') The source 'ccls' and version '2.6.0-1' do not appear to match any binary packages Marked as found in versions ccls/2.6.0-1. -- 1068055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068055: ccls: FTBFS on armel (undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')
Source: ccls Severity: serious Tags: ftbfs Control: found -1 2.6.0-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, ccls fails to build on armel. (missing linking against with -latomic) FYI: https://buildd.debian.org/status/fetch.php?pkg=ccls=armel=0.20230717-1=1694985537=0 Regards,
Bug#1068054: rauc: FTBFS on armel, armhf (1 test failure)
Source: rauc Severity: serious Tags: ftbfs Control: found -1 1.11.3-1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, rauc fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=rauc=armel=1.11.3-1=1710786055=0 https://buildd.debian.org/status/fetch.php?pkg=rauc=armhf=1.11.3-1=1710785845=0 Regards,
Processed: rauc: FTBFS on armel, armhf (1 test failure)
Processing control commands: > found -1 1.11.3-1 Bug #1068054 [src:rauc] rauc: FTBFS on armel, armhf (1 test failure) Marked as found in versions rauc/1.11.3-1. -- 1068054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: postsrsd: FTBFS on armel, armhf (bats run_postsrsd_tests.bats failure)
Processing control commands: > found -1 1.10-2.1 Bug #1068053 [src:postsrsd] postsrsd: FTBFS on armel, armhf (bats run_postsrsd_tests.bats failure) Marked as found in versions postsrsd/1.10-2.1. -- 1068053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068053: postsrsd: FTBFS on armel, armhf (bats run_postsrsd_tests.bats failure)
Source: postsrsd Severity: serious Tags: ftbfs Control: found -1 1.10-2.1 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, postsrsd fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=postsrsd=armel=1.10-2.1=1710920668=0 https://buildd.debian.org/status/fetch.php?pkg=postsrsd=armhf=1.10-2.1=1710920682=0 Regards,
Processed: openms: FTBFS on armel,armhf (error: ‘QOpenGLFunctions_2_0’ does not name a type)
Processing control commands: > found -1 2.6.0+cleaned1-4 Bug #1068052 [src:openms] openms: FTBFS on armel,armhf (error: ‘QOpenGLFunctions_2_0’ does not name a type) Marked as found in versions openms/2.6.0+cleaned1-4. -- 1068052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068052: openms: FTBFS on armel,armhf (error: ‘QOpenGLFunctions_2_0’ does not name a type)
Source: openms Severity: serious Tags: ftbfs Control: found -1 2.6.0+cleaned1-4 X-Debbugs-Cc: ken...@xdump.org Dear Maintainer, openms fails to build on armel, armhf. FYI: https://buildd.debian.org/status/fetch.php?pkg=openms=armel=2.6.0%2Bcleaned1-4=1703355142=0 https://buildd.debian.org/status/fetch.php?pkg=openms=armhf=2.6.0%2Bcleaned1-4=1703351084=0 Regards,
