Bug#1068644: gnutls-bin: "Fatal error: The encryption algorithm is not supported" appeared with 3.8.5 upgrade
On 2024-04-08 18:30, Andreas Metzler wrote: >> It fails with "*** Fatal error: The encryption algorithm is not supported." > > Thank you and sorry. I have done a bisect and will try reverting the > offending upstream commit as a hotfix. Thank you for the quick fix. I've just updated the packages to 3.8.5-2 and have re-tested: The connection works fine now. -- -Sanjoy
Bug#1068689: urfkill dependencies unsatisfiable on 32-bit non-i386 architectures.
Package: urfkill Version: 0.5.0-7.1 Tags: trixie, sid Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, urfkill depends on both libglib2.0-0 and libglib2.0-0t64. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports architectures). Ubuntu has already fixed this issue by removing the hardcoded dependency on libglib2.0-0. http://launchpadlibrarian.net/720796799/urfkill_0.6.0~20150318.103828.5539c0d.1-0ubuntu10_0.6.0~20150318.103828.5539c0d.1-0ubuntu11.diff.gz
Bug#1068688: tpm2-initramfs-tool dependencies unsatisfiable on 32-bit non-i386 architectures.
Package: tpm2-initramfs-tool Version: 1.0.1-1 Tags: trixie, sid Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, tpm2-initramfs-tool depends on both libtss2-esys-3.0.2-0 and libtss2-esys-3.0.2-0t64. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports architectures). Ubuntu has already fixed this issue by replacing the hardcoded dependency on libtss2-esys-3.0.2-0 with code in debian/rules that generates a dependency (not sure why they didn't just remove it). http://launchpadlibrarian.net/720835666/tpm2-initramfs-tool_0.2.2-2build1_0.2.2-2ubuntu1.diff.gz
Bug#1068684: bornagain: FTBFS on many architectures
Source: bornagain
Version: 21.1+ds3-4
Severity: serious
Tags: ftbfs
Dear Maintainer,
Recently upload did not fixed ftbfs on many architectures, see:
https://buildd.debian.org/status/package.php?p=bornagain
Tests failed on arm64, ppc64el, riscv64 and s390x. Build issue on
arm{el,hf} and i386.
--
Regards,
--
Bo YU
signature.asc
Description: PGP signature
Bug#1068683: zmat: FTBFS: ar: blosc2/blosc/*.o: No such file or directory
Source: zmat Version: 0.9.9+ds.1-2 Severity: serious Tags: ftbfs Dear Maintainer, The package has ftbfs issue but on amd64 and i386, the common issue is follows: ``` CC obj/conf_91c451f6ae5e059804729dd256611361/static/cover.o CC obj/conf_91c451f6ae5e059804729dd256611361/static/divsufsort.o CC obj/conf_91c451f6ae5e059804729dd256611361/static/fastcover.o CC obj/conf_91c451f6ae5e059804729dd256611361/static/zdict.o compiling single-threaded static library 1.5.5 make[4]: Leaving directory '/<>/src/blosc2/internal-complibs/zstd' make[3]: Leaving directory '/<>/src/blosc2' Building ../lib/libzmat.a ar cr -o ../lib/libzmat.a zmatlib.o miniz/miniz.o easylzma/compress.o easylzma/decompress.o easylzma/lzma_header.o easylzma/lzip_header.o easylzma/common_internal.o easylzma/pavlov/LzmaEnc.o easylzma/pavlov/LzmaDec.o easylzma/pavlov/LzmaLib.o easylzma/pavlov/LzFind.o easylzma/pavlov/Bra.o easylzma/pavlov/BraIA64.o easylzma/pavlov/Alloc.o easylzma/pavlov/7zCrc.o blosc2/blosc/*.o blosc2/internal-complibs/zstd/obj/*/static/*.o ar: blosc2/blosc/*.o: No such file or directory make[2]: *** [makefile:194: ../lib/libzmat.a] Error 1 make[2]: Leaving directory '/<>/src' make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary-arch] Error 2 ... ``` See https://buildd.debian.org/status/fetch.php?pkg=zmat=arm64=0.9.9%2Bds.1-2=1712139942=0 and https://buildd.debian.org/status/fetch.php?pkg=zmat=riscv64=0.9.9%2Bds.1-2=1712403175=0 -- Regards, -- Bo YU signature.asc Description: PGP signature
Bug#1054680: newsboat: FTBFS: test/cliargsparser.cpp:1:10: fatal error: 3rd-party/catch.hpp: No such file or directory
Control: forwarded -1 https://github.com/newsboat/newsboat/issues/2716 On Fri, 27 Oct 2023 21:15:28 +0200 Lucas Nussbaum wrote: > Source: newsboat > Version: 2.32-3 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231027 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss - I/<>/target/cxxbridge/ -Werror -Wall -Wextra -Wunreachable- code -DLOCALEDIR='"/usr/local/share/locale"' -I/usr/include/x86_64-linux- gnu -I/usr/include/libxml2 -I/usr/include/json-c -D_DEFAULT_SOURCE - D_XOPEN_SOURCE=600 -g -O2 -ffile-prefix-map=/<>=. -fstack- protector-strong -fstack-clash-protection -Wformat -Werror=format- security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MP -MF .deps/test/controller.cpp -o test/controller.o -c test/controller.cpp > > test/cliargsparser.cpp:1:10: fatal error: 3rd-party/catch.hpp: No such file or directory > > 1 | #include "3rd-party/catch.hpp" > > | ^ > > compilation terminated. This is caused by Debian's catch2 upgrading to v3.x. While newsboat upstream is working on catch2 3.x support, a quickfix is to disable the ln -sf lines in debian/rules and use the embedded catch2 2.x headers. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Processed: Re: newsboat: FTBFS: test/cliargsparser.cpp:1:10: fatal error: 3rd-party/catch.hpp: No such file or directory
Processing control commands: > forwarded -1 https://github.com/newsboat/newsboat/issues/2716 Bug #1054680 [src:newsboat] newsboat: FTBFS: test/cliargsparser.cpp:1:10: fatal error: 3rd-party/catch.hpp: No such file or directory Set Bug forwarded-to-address to 'https://github.com/newsboat/newsboat/issues/2716'. -- 1054680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067957: [EXTERNAL] Re: [[maude-bugs]] Maude fails to build on armhf
Hi Nilish, I don't have a 32-bit machine to test on, but my understanding is that Linux has moved to a 64-bit signed integer for time_t and this is a long long on 32-bit machines which is explicitly not supported by GMP's C++ API. https://en.wikipedia.org/wiki/Year_2038_problem https://gmplib.org/manual/C_002b_002b-Interface-Integers I'm not happy converting a signed value to an unsigned value for all architectures. But mpz_class nanoSeconds(static_cast(timeValue.tv_sec)); should fix the problem, at least until 2038. Can you check that this works? If so I'll put it in the next public alpha. Steven On 4/7/24 08:28, Nilesh Patra wrote: On Sun, Apr 07, 2024 at 07:45:33PM +0530, Nilesh Patra wrote: Hi, Maude fails to build on armhf/arm32 arch with: In file included from timeManagerSymbol.cc:64: timeActions.cc: In member function ‘void TimeManagerSymbol::getTimeSinceEpoch(FreeDagNode*, ObjectSystemRewritingContext&)’: timeActions.cc:43:41: error: call of overloaded ‘__gmp_expr(__time64_t&)’ is ambiguous 43 | mpz_class nanoSeconds(timeValue.tv_sec); | ^ In file included from ../../src/BuiltIn/succSymbol.hh:28, from timeManagerSymbol.cc:53: /usr/include/gmpxx.h:1646:3: note: candidate: ‘__gmp_expr<__mpz_struct [1], __mpz_struct [1]>::__gmp_expr(double)’ 1646 | __GMPXX_DEFINE_ARITHMETIC_CONSTRUCTORS | ^~ /usr/include/gmpxx.h:1646:3: note: candidate: ‘__gmp_expr<__mpz_struct [1], __mpz_struct [1]>::__gmp_expr(float)’ Full long here: https://buildd.debian.org/status/fetch.php?pkg=maude=armhf=3.4-1=1712489526=0 And Debian bug report here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067957 Would be great if you have the cycles to look into it. This patch fixes the issue at hand but I am unsure if it is sensible to apply it. diff --git a/src/ObjectSystem/timeActions.cc b/src/ObjectSystem/timeActions.cc index 77395aa..63aa028 100644 --- a/src/ObjectSystem/timeActions.cc +++ b/src/ObjectSystem/timeActions.cc @@ -40,7 +40,7 @@ TimeManagerSymbol::getTimeSinceEpoch(FreeDagNode* message, ObjectSystemRewriting DebugSave(r, clock_gettime(CLOCK_REALTIME, )); Assert(r == 0, "clock_gettime() failed: " << strerror(errno)); - mpz_class nanoSeconds(timeValue.tv_sec); + mpz_class nanoSeconds(static_cast(timeValue.tv_sec)); nanoSeconds *= BILLION; nanoSeconds += timeValue.tv_nsec; Best, Nilesh
Bug#1065088: marked as done (pam 1.5.3-5 not suitable because pam_userdb is missing)
Your message dated Mon, 08 Apr 2024 23:05:55 + with message-id and subject line Bug#1065088: fixed in pam 1.5.3-7 has caused the Debian Bug report #1065088, regarding pam 1.5.3-5 not suitable because pam_userdb is missing 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.) -- 1065088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: pam version: 1.5.3-5 severity: serious This version of pam drops pam_userdb which can break systems that use pam_userdb in their configuration. Long term we do want to split it out and possibly drop. However, this change is purely for the time_t transition and will be reverted. This version of pam is not suitable for testing. --- End Message --- --- Begin Message --- Source: pam Source-Version: 1.5.3-7 Done: Sam Hartman We believe that the bug you reported is fixed in the latest version of pam, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sam Hartman (supplier of updated pam package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 Apr 2024 16:35:07 -0600 Source: pam Architecture: source Version: 1.5.3-7 Distribution: unstable Urgency: medium Maintainer: Sam Hartman Changed-By: Sam Hartman Closes: 1065064 1065088 1065806 Changes: pam (1.5.3-7) unstable; urgency=medium . * Correct Build depends for docbook5, Closes: #1065064 * Regenerate patches to capture date change in pam_getitem.3 * Depend on libdb-dev again, bringing back pam_userdb, Closes: #1065088 * Document pam_umask change, Closes: #1065806 Checksums-Sha1: f295abd00dbfb0e05f7e0236e663ab0852df7eb3 2253 pam_1.5.3-7.dsc 49dfc4b661e10aea01e0c714987a89f4aaba1d97 139288 pam_1.5.3-7.debian.tar.xz Checksums-Sha256: 05666dde2c8057ff436975a5da7dad91210ab5a5dfdaea43976ac4a6bc75b1e7 2253 pam_1.5.3-7.dsc 494106a8f40a5436b82f8955e04a83598439b48636f16a30d0b6a32d86d0fc61 139288 pam_1.5.3-7.debian.tar.xz Files: 9406826b530ee14d1a3e8e4aca318b13 2253 libs optional pam_1.5.3-7.dsc f66385657f2875b74d0b5c82084f8e57 139288 libs optional pam_1.5.3-7.debian.tar.xz -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSj2jRwbAdKzGY/4uAsbEw8qDeGdAUCZhRy2QAKCRAsbEw8qDeG dJo9AQDT3dqY3tF/KO66qnYNt7oVemlR75yE7r4VxAXAWMLwLAEAkCMKYPgsaRqY qQ0QN6JOATylofntGKOOrYC3P/Hjog8= =J19s -END PGP SIGNATURE- pgpwnx52wzv2w.pgp Description: PGP signature --- End Message ---
Processed: Apply commands
Processing commands for cont...@bugs.debian.org:
> reopen 1064128
Bug #1064128 {Done: Kyle Robbertze } [src:liquidsoap]
liquidsoap: FTBFS: Error: Unbound module Pcre
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions liquidsoap/2.2.4-1.
> notfixed 1064128 2.2.4-1
Bug #1064128 [src:liquidsoap] liquidsoap: FTBFS: Error: Unbound module Pcre
Ignoring request to alter fixed versions of bug #1064128 to the same values
previously set
> forwarded 1064128 https://github.com/savonet/liquidsoap/issues/3750
Bug #1064128 [src:liquidsoap] liquidsoap: FTBFS: Error: Unbound module Pcre
Ignoring request to change the forwarded-to-address of bug#1064128 to the same
value
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1064128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066681: marked as done (scilab: FTBFS: sci_gateway/c/sci_getURL.c:43:5: error: implicit declaration of function ‘Sciwarning’ [-Werror=implicit-function-declaration])
Your message dated Mon, 08 Apr 2024 22:07:01 +
with message-id
and subject line Bug#1066681: fixed in scilab 2024.0.0+dfsg-6
has caused the Debian Bug report #1066681,
regarding scilab: FTBFS: sci_gateway/c/sci_getURL.c:43:5: error: implicit
declaration of function ‘Sciwarning’ [-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.)
--
1066681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scilab
Version: 2024.0.0+dfsg-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I../../modules/core/includes -I./includes/ -I./src/c/ -I./src/cpp/
> -I../../modules/ast/includes/ast/ -I../../modules/ast/includes/exps/
> -I../../modules/ast/includes/operations/ -I../../modules/ast/includes/parse/
> -I../../modules/ast/includes/symbol/ -I../../modules/ast/includes/system_env/
> -I../../modules/ast/includes/types/ -I../../modules/api_scilab/includes
> -I../../modules/output_stream/includes
> -I../../modules/functions_manager/includes -I../../modules/string/includes
> -I../../modules/io/includes -I../../modules/threads/includes
> -I../../modules/console/includes -I../../modules/localization/includes
> -I../../modules/dynamic_link/includes -I../../modules/preferences/includes
> -I/usr/include/hdf5/serial -I/usr/include/libxml2 -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
> -DNDEBUG -g -O2 -m64 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT
> sci_gateway/c/libscifileio_la-sci_getURL.lo -MD -MP -MF
> sci_gateway/c/.deps/libscifileio_la-sci_getURL.Tpo -c -o
> sci_gateway/c/libscifileio_la-sci_getURL.lo `test -f
> 'sci_gateway/c/sci_getURL.c' || echo './'`sci_gateway/c/sci_getURL.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../modules/core/includes
> -I./includes/ -I./src/c/ -I./src/cpp/ -I../../modules/ast/includes/ast/
> -I../../modules/ast/includes/exps/ -I../../modules/ast/includes/operations/
> -I../../modules/ast/includes/parse/ -I../../modules/ast/includes/symbol/
> -I../../modules/ast/includes/system_env/ -I../../modules/ast/includes/types/
> -I../../modules/api_scilab/includes -I../../modules/output_stream/includes
> -I../../modules/functions_manager/includes -I../../modules/string/includes
> -I../../modules/io/includes -I../../modules/threads/includes
> -I../../modules/console/includes -I../../modules/localization/includes
> -I../../modules/dynamic_link/includes -I../../modules/preferences/includes
> -I/usr/include/hdf5/serial -I/usr/include/libxml2 -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
> -DNDEBUG -g -O2 -m64 -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -MT
> sci_gateway/c/libscifileio_la-sci_getURL.lo -MD -MP -MF
> sci_gateway/c/.deps/libscifileio_la-sci_getURL.Tpo -c
> sci_gateway/c/sci_getURL.c -fPIC -DPIC -o
> sci_gateway/c/.libs/libscifileio_la-sci_getURL.o
> sci_gateway/c/sci_getURL.c: In function ‘sci_getURL’:
> sci_gateway/c/sci_getURL.c:43:5: error: implicit declaration of function
> ‘Sciwarning’ [-Werror=implicit-function-declaration]
>43 | Sciwarning(_("%s: %s will be permanently removed in Scilab %s.\n
> Please use %s instead.\n"), _("Warning"), "getURL", "2025.0.0", "http_get");
> | ^~
> cc1: some warnings being treated as errors
> make[4]: *** [Makefile:1798: sci_gateway/c/libscifileio_la-sci_getURL.lo]
> Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/scilab_2024.0.0+dfsg-5_unstable.log
Bug#1068251: glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t
Hi Helmut,
On 2024-04-08 22:19, Helmut Grohne wrote:
> Control: tags -1 + patch
>
> Hi Aurelien and Canonical folks,
>
> On Tue, Apr 02, 2024 at 08:53:31PM +0200, Aurelien Jarno wrote:
> > Starting with gcc-12 version 12.3.0-15, -D_TIME_BITS=64 together with
> > -D_FILE_OFFSET_BITS=64 are passed by default on 32-bit architectures
> > except i386.
> >
> > This has been partially fixed in the 2.37-15.1 NMU by adding
> > -U_TIME_BITS to CFLAGS, however it causes failures in the testsuite:
>
> There are two subtleties about -U_TIME_BITS in a moment.
>
> > | +-+
> > | | Encountered regressions that don't match expected failures. |
> > | +-+
> > | FAIL: conform/ISO/stdio.h/linknamespace
>
> The detail for this failure is:
>
> | [initial] fgetpos64
> | [initial] fopen64
> | [initial] freopen64
> | [initial] fsetpos64
>| [initial] tmpfine64
>
> What linknamespace.py wants to tell us here is that it expected
> fgetpos64, but no fgetpos64 was declared. It was not declared, because
> there is no difference between fgetpos and fgetpos64 after defining
> -D_FILE_OFFSET_BITS=64 (which is also in the default compiler flags).
>
> The other failures are of very similar kind, but there also is another
> kind.
>
> > | FAIL: conform/POSIX/sys/stat.h/conform
>
> The detail for this failure contains:
>
> | /tmp/tmpnzda_r9j/test.c:90:35: error: conflicting types for 'b2_8'; have
> '__time64_t' {aka 'long long int'}
> |90 | extern __typeof__ (a2_8.st_atime) b2_8;
> | | ^~~~
> | /tmp/tmpnzda_r9j/test.c:89:17: note: previous declaration of 'b2_8' with
> type '__time_t' {aka 'long int'}
> |89 | extern __time_t b2_8;
> | | ^~~~
>
> Here, it tells us that it expected the st_atime field of struct stat to
> have type __time_t (the 32 bit one), but it really has __time64_t.
>
> Looking at the invocation of linknamespace.py you can see:
>
> | python3 -B linknamespace.py --cc='arm-linux-gnueabihf-gcc-12'
> --flags='-I../include
> -I/build/reproducible-path/glibc-2.37/build-tree/armhf-libc
> -I../sysdeps/unix/sysv/linux/arm/le -I../sysdeps/unix/sysv/linux/arm
> -I../sysdeps/arm/nptl -I../sysdeps/unix/sysv/linux/include
> -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread
> -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv
> -I../sysdeps/unix/arm -I../sysdeps/unix -I../sysdeps/posix
> -I../sysdeps/arm/le/armv7/multiarch -I../sysdeps/arm/armv7/multiarch
> -I../sysdeps/arm/le/armv7 -I../sysdeps/arm/armv7 -I../sysdeps/arm/armv6t2
> -I../sysdeps/arm/armv6 -I../sysdeps/arm/le -I../sysdeps/arm/include
> -I../sysdeps/arm -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/flt-32
> -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754 -I../sysdeps/generic
> -nostdinc -isystem /usr/lib/gcc/arm-linux-gnueabihf/12/include -isystem
> /build/reproducible-path/glibc-2.37/debian/include -I..' ...
>
> In particular, what you do not see is -U_TIME_BITS inside --flags.
>
> > Ubuntu has just ignored those failures for now, but I am just afraid
> > that if we do the same, nobody will fix them.
>
> Armed with this knowledge, I think we need two changes. For one thing
> debian/sysdeps/linux.mk needs to add -U_FILE_OFFSET_BITS to extra_cflags
> to revert any possible ABI changing effects. For another, the
> conformance tests use independent compiler flags defined in
> conform/Makefile. There, a naive patch seems to be:
>
> -conformtest-cc-flags = -I../include $(+sysdep-includes) $(sysincludes) -I..
> +conformtest-cc-flags = -U_FILE_OFFSET_BITS -U_TIME_BITS -I../include
> $(+sysdep-includes) $(sysincludes) -I..
>
> With these two changes, I am able to successfully build glibc on armhf
> with the conformance test suite passing.
>
> > In addition it means that upstream glibc does not build anymore by
> > default on a 32-bit Debian. Not really a Debian issue, but that is not
> > nice either and should probably be fixed.
>
> I think that latter change may be applicable upstream. Running the
> conformance test suite with either _FILE_OFFSET_BITS or _TIME_BITS set
> is not expected nor supported. This is partially evident from
> conform/linknamespace.py in a comment:
>
> | # * Header inclusions should be compiled several times with
> | # different options such as -O2, -D_FORTIFY_SOURCE and
> | # -D_FILE_OFFSET_BITS=64 to find out what symbols are undefined
> | # from such a compilation; this is not yet implemented.
>
> The conformance test suite clearly wants to manage these macros (and its
> effects on symbols) explicitly and does not expect them to be
> pre-defined.
Thanks for you analysis and your patch. In short your proposal is to
extend the initial patch from Steve to fully hide the fact that the
compiler default to -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64.
This
Bug#1068513: marked as done (dablin: FTBFS on arm{el,hf}: manually disables mpg123's large file API)
Your message dated Mon, 08 Apr 2024 21:19:08 +
with message-id
and subject line Bug#1068513: fixed in dablin 1.16.0-1
has caused the Debian Bug report #1068513,
regarding dablin: FTBFS on arm{el,hf}: manually disables mpg123's large file API
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.)
--
1068513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dablin
Version: 1.15.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=dablin=armel=1.15.0-1%2Bb2=1712391165=0
[ 97%] Linking CXX executable dablin
cd /<>/obj-arm-linux-gnueabi/src && /usr/bin/cmake -E
cmake_link_script CMakeFiles/dablin.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -pie -z
now -rdynamic CMakeFiles/dablin.dir/sdl_output.cpp.o
CMakeFiles/dablin.dir/dabplus_decoder.cpp.o
CMakeFiles/dablin.dir/ensemble_source.cpp.o
CMakeFiles/dablin.dir/ensemble_player.cpp.o
CMakeFiles/dablin.dir/edi_source.cpp.o CMakeFiles/dablin.dir/edi_player.cpp.o
CMakeFiles/dablin.dir/eti_source.cpp.o CMakeFiles/dablin.dir/eti_player.cpp.o
CMakeFiles/dablin.dir/dab_decoder.cpp.o CMakeFiles/dablin.dir/fic_decoder.cpp.o
CMakeFiles/dablin.dir/pcm_output.cpp.o CMakeFiles/dablin.dir/tools.cpp.o
CMakeFiles/dablin.dir/version.cpp.o CMakeFiles/dablin.dir/dablin.cpp.o -o
dablin ../fec/libfec.a /usr/lib/arm-linux-gnueabi/libatomic.so.1 -lmpg123
-lSDL2 -lfaad -lc -lm
/usr/bin/ld: CMakeFiles/dablin.dir/dab_decoder.cpp.o: in function
`MP2Decoder::DecodeFrame(unsigned char**)':
./obj-arm-linux-gnueabi/src/./src/dab_decoder.cpp:166:(.text+0x1bb4): undefined
reference to `mpg123_framebyframe_decode'
collect2: error: ld returned 1 exit status
make[3]: *** [src/CMakeFiles/dablin.dir/build.make:313: src/dablin] Error 1
make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
make[2]: *** [CMakeFiles/Makefile2:263: src/CMakeFiles/dablin.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs
[100%] Linking CXX executable dablin_gtk
cd /<>/obj-arm-linux-gnueabi/src && /usr/bin/cmake -E
cmake_link_script CMakeFiles/dablin_gtk.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -pie -z
now -rdynamic CMakeFiles/dablin_gtk.dir/sdl_output.cpp.o
CMakeFiles/dablin_gtk.dir/dabplus_decoder.cpp.o
CMakeFiles/dablin_gtk.dir/ensemble_source.cpp.o
CMakeFiles/dablin_gtk.dir/ensemble_player.cpp.o
CMakeFiles/dablin_gtk.dir/edi_source.cpp.o
CMakeFiles/dablin_gtk.dir/edi_player.cpp.o
CMakeFiles/dablin_gtk.dir/eti_source.cpp.o
CMakeFiles/dablin_gtk.dir/eti_player.cpp.o
CMakeFiles/dablin_gtk.dir/dab_decoder.cpp.o
CMakeFiles/dablin_gtk.dir/fic_decoder.cpp.o
CMakeFiles/dablin_gtk.dir/pcm_output.cpp.o
CMakeFiles/dablin_gtk.dir/tools.cpp.o CMakeFiles/dablin_gtk.dir/version.cpp.o
CMakeFiles/dablin_gtk.dir/mot_manager.cpp.o
CMakeFiles/dablin_gtk.dir/pad_decoder.cpp.o
CMakeFiles/dablin_gtk.dir/dablin_gtk.cpp.o
CMakeFiles/dablin_gtk.dir/dablin_gtk_dl_plus.cpp.o
CMakeFiles/dablin_gtk.dir/dablin_gtk_sls.cpp.o -o dablin_gtk ../fec/libfec.a
/usr/lib/arm-linux-gnueabi/libatomic.so.1 -lmpg123 -lSDL2 -lfaad -lc
-lgtkmm-3.0 -latkmm-1.6 -lgdkmm-3.0 -lgiomm-2.4 -lgtk-3 -lgdk-3 -lz -latk-1.0
-lcairo-gobject -lgio-2.0 -lpangomm-1.4 -lglibmm-2.4 -lcairomm-1.0 -lsigc-2.0
-lpangocairo-1.0 -lpango-1.0 -lharfbuzz -lcairo -lgdk_pixbuf-2.0 -lgobject-2.0
-lglib-2.0 -lm
/usr/bin/ld: CMakeFiles/dablin_gtk.dir/dab_decoder.cpp.o: in function
`MP2Decoder::DecodeFrame(unsigned char**)':
./obj-arm-linux-gnueabi/src/./src/dab_decoder.cpp:166:(.text+0x1bb4): undefined
reference to `mpg123_framebyframe_decode'
collect2: error: ld returned 1 exit status
make[3]: *** [src/CMakeFiles/dablin_gtk.dir/build.make:377: src/dablin_gtk]
Error 1
This is caused by
#define MPG123_NO_LARGENAME // disable large file API here
in src/dab_decoder.h
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: dablin
Source-Version: 1.16.0-1
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version
Bug#1068666: haskell-fold-debounce: FTBFS on arm{el,hf}: 14 examples, 2 failures
Source: haskell-fold-debounce
Version: 0.2.0.11-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=haskell-fold-debounce=armel=0.2.0.11-1%2Bb2=1712466208=0
Failures:
test/Control/FoldDebounceSpec.hs:81:40:
1) Control.FoldDebounce.Trigger emits the output event 'delay' interval after
the first input event (alwaysResetTimer = False)
expected: Just [10,20,30,40,50]
but got: Just [10,20,30]
To rerun use: --match "/Control.FoldDebounce/Trigger/emits the output event
'delay' interval after the first input event (alwaysResetTimer = False)/"
test/Control/FoldDebounceSpec.hs:143:21:
2) Control.FoldDebounce.Trigger emits output events even if input events are
coming intensely
predicate failed on: ["abc"]
To rerun use: --match "/Control.FoldDebounce/Trigger/emits output events even
if input events are coming intensely/"
Randomized with seed 1347232098
Finished in 2.9315 seconds
14 examples, 2 failures
Test suite spec-threaded: FAIL
Test suite logged to: dist-ghc/test/fold-debounce-0.2.0.11-spec-threaded.log
0 of 2 test suites (0 of 2 test cases) passed.
-e: error: debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct
returned exit code 1
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 875.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 614
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 477
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "test",
"--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 692
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] Error 25
Cheers
--
Sebastian Ramacher
Bug#1068665: cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed
Source: cfengine3 Version: 3.21.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=cfengine3=armel=3.21.4-1=1712477798=0 == Starting test: files_interfaces_test.c == test_cfreadline_valid: Starting test test_cfreadline_valid: Test completed successfully. test_cfreadline_corrupted: Starting test test_cfreadline_corrupted: Test completed successfully. All 2 tests passed PASS: files_interfaces_test 1 != 3 ERROR: connection_management_test.c:39 Failure! 1 != 2 ERROR: connection_management_test.c:69 Failure! 1 != 2 ERROR: connection_management_test.c:99 Failure! 1 != 2 ERROR: connection_management_test.c:129 Failure! 4 out of 4 tests failed! test_purge_old_connections_nochange test_purge_old_connections_purge_first test_purge_old_connections_purge_middle test_purge_old_connections_purge_last == Starting test: connection_management_test.c == test_purge_old_connections_nochange: Starting test test_purge_old_connections_nochange: Test failed. test_purge_old_connections_purge_first: Starting test test_purge_old_connections_purge_first: Test failed. test_purge_old_connections_purge_middle: Starting test test_purge_old_connections_purge_middle: Test failed. test_purge_old_connections_purge_last: Starting test test_purge_old_connections_purge_last: Test failed. FAIL: connection_management_test Cheers -- Sebastian Ramacher
Bug#1068664: haskell-filestore: FTBFS on arm{el,hf}: Total Cases: 42 Tried: 42 Errors: 1 Failures: 1
Source: haskell-filestore
Version: 0.6.5-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
Running 1 test suites...
Test suite test-filestore: RUNNING...
Cases: 21 Tried: 0 Errors: 0 Failures: 0
Cases: 21 Tried: 1 Errors: 0 Failures: 0
Cases: 21 Tried: 2 Errors: 0 Failures: 0
Cases: 21 Tried: 3 Errors: 0 Failures: 0
Cases: 21 Tried: 4 Errors: 0 Failures: 0
Cases: 21 Tried: 5 Errors: 0 Failures: 0
Cases: 21 Tried: 6 Errors: 0 Failures: 0
Cases: 21 Tried: 7 Errors: 0 Failures: 0
Cases: 21 Tried: 8 Errors: 0 Failures: 0
Cases: 21 Tried: 9 Errors: 0 Failures: 0
Cases: 21 Tried: 10 Errors: 0 Failures: 0
Cases: 21 Tried: 11 Errors: 0 Failures: 0
Cases: 21 Tried: 12 Errors: 0 Failures: 0
Cases: 21 Tried: 13 Errors: 0 Failures: 0
Cases: 21 Tried: 14 Errors: 0 Failures: 0
Cases: 21 Tried: 15 Errors: 0 Failures: 0
Cases: 21 Tried: 16 Errors: 0 Failures: 0
Cases: 21 Tried: 17 Errors: 0 Failures: 0
Cases: 21 Tried: 18 Errors: 0 Failures: 0
### Failure in: 18:Git (history and revision)
tests/Tests.hs:335
history from now + 1 day onwards is empty
Cases: 21 Tried: 19 Errors: 0 Failures: 1
Cases: 21 Tried: 20 Errors: 0 Failures: 1
Cases: 21 Tried: 21 Errors: 0 Failures: 1
Cases: 21 Tried: 0 Errors: 0 Failures: 0
Cases: 21 Tried: 1 Errors: 0 Failures: 0
Cases: 21 Tried: 2 Errors: 0 Failures: 0
Cases: 21 Tried: 3 Errors: 0 Failures: 0
Cases: 21 Tried: 4 Errors: 0 Failures: 0
Cases: 21 Tried: 5 Errors: 0 Failures: 0
Cases: 21 Tried: 6 Errors: 0 Failures: 0
Cases: 21 Tried: 7 Errors: 0 Failures: 0
Cases: 21 Tried: 8 Errors: 0 Failures: 0
Cases: 21 Tried: 9 Errors: 0 Failures: 0
Cases: 21 Tried: 10 Errors: 0 Failures: 0
Cases: 21 Tried: 11 Errors: 0 Failures: 0
Cases: 21 Tried: 12 Errors: 0 Failures: 0
Cases: 21 Tried: 13 Errors: 0 Failures: 0
Cases: 21 Tried: 14 Errors: 0 Failures: 0
Cases: 21 Tried: 15 Errors: 0 Failures: 0
Cases: 21 Tried: 16 Errors: 0 Failures: 0
Cases: 21 Tried: 17 Errors: 0 Failures: 0
Cases: 21 Tried: 18 Errors: 0 Failures: 0
### Error in: 18:Mercurial (history and revision)
UnknownError: mercurial log returned error status.
hg: parse error: invalid date: '134982229649-07-10 23:17:33'
Cases: 21 Tried: 19 Errors: 1 Failures: 0
Cases: 21 Tried: 20 Errors: 1 Failures: 0
Cases: 21 Tried: 21 Errors: 1 Failures: 0
Total Cases: 42 Tried: 42 Errors: 1 Failures: 1
Test suite test-filestore: FAIL
Test suite logged to: dist-ghc/test/filestore-0.6.5-test-filestore.log
0 of 1 test suites (0 of 1 test cases) passed.
-e: error: debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct
returned exit code 1
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 875.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 614
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 477
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "test",
"--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 692
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] Error 25
Cheers
--
Sebastian Ramacher
Bug#1068663: zzuf: FTBFS on arm{el,hf}: /tmp/ccnMZahz.s:1620: Error: symbol `open64' is already defined
Source: zzuf Version: 0.15-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=zzuf=armhf=0.15-3=1712473020=0 In file included from /usr/include/arm-linux-gnueabihf/sys/cdefs.h:24, from libzzuf/lib-mem.c:24: /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DLIBZZUF -I./libzzuf -I./common -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -std=c99 -g -O2 -Wall -W -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow -Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -c libzzuf/lib-signal.c -o libzzuf/la-lib-signal.o >/dev/null 2>&1 /tmp/ccnMZahz.s: Assembler messages: /tmp/ccnMZahz.s:1620: Error: symbol `open64' is already defined /tmp/ccnMZahz.s:4926: Error: symbol `lseek64' is already defined make[3]: *** [Makefile:708: libzzuf/la-lib-fd.lo] Error 1 make[3]: *** Waiting for unfinished jobs /tmp/ccKhQeYR.s: Assembler messages: /tmp/ccKhQeYR.s:1867: Error: symbol `mmap64' is already defined Cheers -- Sebastian Ramacher
Bug#1064724: marked as done (yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Mon, 08 Apr 2024 20:34:58 + with message-id and subject line Bug#1064724: fixed in yapet 2.6-2 has caused the Debian Bug report #1064724, regarding yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1064724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yapet Version: 2.6-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/tests/crypt' > FAIL: blowfish > PASS: key448 > PASS: blowfishfactory > FAIL: file_blowfish > FAIL: foreign > PASS: cryptofactoryhelper > PASS: aes256 > PASS: key256 > PASS: aes256factory > PASS: file_aes256 > === >YAPET 2.6: tests/crypt/test-suite.log > === > > # TOTAL: 10 > # PASS: 7 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 3 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: blowfish > == > > .E.E.E. > > > !!!FAILURES!!! > Test Results: > Run: 4 Failures: 0 Errors: 3 > > > 1) test: should encrypt and decrypt (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 2) test: should throw on decrypting corrupted data (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 3) test: should throw on decrypting with wrong password (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > FAIL blowfish (exit status: 1) > > FAIL: file_blowfish > === > > .E.E.E.E.E.E.E.E.E.E > > > !!!FAILURES!!! > Test Results: > Run: 10 Failures: 0 Errors: 10 > > > 1) test: should correctly read empty file (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 2) test: should correctly read empty file (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 3) test: should throw expected exception on invalid password (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 4) test: should write passwords (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 5) test: should detect file modification on password save (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 6) test: should force password save on modified file (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 7) test: should get the correct time when the master password was set (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 8) test: should properly set new password (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 9) test: should allow saving passwords after password change (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 10) test: should throw exception on reading corrupt file (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > FAIL file_blowfish (exit status: 1) > > FAIL: foreign > = > > .E.E.E.E.E.E.E.E > > > !!!FAILURES!!! > Test Results: > Run: 8 Failures: 0 Errors: 8 > > > 1) test: 32bit little endian pre 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 2) test: 32bit big endian pre 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 3) test: 64bit little endian pre 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 4) test: 64bit big endian pre 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 5) test: 32bit little endian 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 6) test: 32bit big endian 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 7) test: 64bit little endian 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 8) test: 64bit big endian 0.6 (E) > uncaught exception
Bug#1068045: marked as done (libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB)
Your message dated Mon, 08 Apr 2024 20:34:58 + with message-id and subject line Bug#1064724: fixed in yapet 2.6-2 has caused the Debian Bug report #1064724, regarding libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB 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.) -- 1064724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libssl3 depends on: ii libc6 2.36-9+deb12u5 libssl3 recommends no packages. libssl3 suggests no packages. -- no debconf information -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: yapet Source-Version: 2.6-2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of yapet, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated yapet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Apr 2024 21:32:50 +0200 Source: yapet Architecture: source Version: 2.6-2 Distribution: unstable Urgency: medium Maintainer: Salvatore Bonaccorso Changed-By: Salvatore Bonaccorso Closes: 1064724 Changes: yapet (2.6-2) unstable; urgency=medium . * crypt/blowfish: Remove EVP_CIPHER_CTX_set_key_length() (Closes: #1064724) * crypt/aes: Remove EVP_CIPHER_CTX_set_key_length() Checksums-Sha1: 77a9dbb34c6c2046ffe5b63a38017ef71e4c3002 2032 yapet_2.6-2.dsc fe1fbdf8a638b496a141b2d35069be4e20ec3645 7996 yapet_2.6-2.debian.tar.xz Checksums-Sha256: 6c9b34160d20ce23c0b0c9d230268c0d4cfe9c62751cdd233bda74fd62a1c3c8 2032 yapet_2.6-2.dsc d730ba75509e872bb65261172cd71325aa24b7e4daa007a41d1c33c1a02b0995 7996 yapet_2.6-2.debian.tar.xz Files: 80259088fe14003a53ce2c90aea62b26 2032 utils optional yapet_2.6-2.dsc bfbb7689511ec6fb58b5601b605f0405 7996 utils optional yapet_2.6-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYURxZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EH24QAJmmjht7mDwrJXoZnInXsJV6oDbcMQ5C 5QyfHZW8X15MQCzkYyFhu+xFTpvsHLaYzDeUm3ikZP1c18vphvCzIDgDnTlaBoeq Xato2YDoOl1hpwAZ/rFL7C0rb/XhEqrGpe0NjYANfglQKwug6KuEb2ll0+cDIQI0 se/Ovvkbe3sH40UjFv+e0gu0S79f0uz9eMQj3+DM1XG9Rtl6BNiG6A+dGxsEJr01 E8TpOQ5CwiOQl5S16Uax2NqZcEGXTbdY5ngfWmpI1MyL0PfXKBM0W9xi7sGCQc+O GwH1YIjyIgD6lKumI9kGzQx0jG3ev8ivDrY2czVWDeTTolKUwXbSKeKkrmHMPZbi 0Yz8Eazv5c96wPfdxAYB0DMjNEVT4OYgYt6ukjQrxtcf96YUKSp0e9gIxRh8tiUH 8BOTE7uJO3t8xZYnxdLuJtxSF1dpiDgL1DDZwpFYgAhdNcSU4yUkARDXeU5XItid SMus9NjXszlG0m9FQ8Rle8Q1JgoCiESE1Udro1tLES5LmQKat1UkfDzzSkpNfpFS kGsL57PM6hDrfQFclxmGjWlxDbi6WwZX102Jfsob/P0k96b2aZ5zRqmPEsF/NIis Jukm3YxzrV4YKewbyRaD52AACItKJIg527XbY9p0gPBc992q+CHF0zp3pYaO5z1b /SxKnB/9dp6m =pbZe -END PGP SIGNATURE- pgpDiwrWXKjR9.pgp Description: PGP signature --- End Message ---
Bug#1068251: glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t
Control: tags -1 + patch
Hi Aurelien and Canonical folks,
On Tue, Apr 02, 2024 at 08:53:31PM +0200, Aurelien Jarno wrote:
> Starting with gcc-12 version 12.3.0-15, -D_TIME_BITS=64 together with
> -D_FILE_OFFSET_BITS=64 are passed by default on 32-bit architectures
> except i386.
>
> This has been partially fixed in the 2.37-15.1 NMU by adding
> -U_TIME_BITS to CFLAGS, however it causes failures in the testsuite:
There are two subtleties about -U_TIME_BITS in a moment.
> | +-+
> | | Encountered regressions that don't match expected failures. |
> | +-+
> | FAIL: conform/ISO/stdio.h/linknamespace
The detail for this failure is:
| [initial] fgetpos64
| [initial] fopen64
| [initial] freopen64
| [initial] fsetpos64
| [initial] tmpfile64
What linknamespace.py wants to tell us here is that it expected
fgetpos64, but no fgetpos64 was declared. It was not declared, because
there is no difference between fgetpos and fgetpos64 after defining
-D_FILE_OFFSET_BITS=64 (which is also in the default compiler flags).
The other failures are of very similar kind, but there also is another
kind.
> | FAIL: conform/POSIX/sys/stat.h/conform
The detail for this failure contains:
| /tmp/tmpnzda_r9j/test.c:90:35: error: conflicting types for 'b2_8'; have
'__time64_t' {aka 'long long int'}
|90 | extern __typeof__ (a2_8.st_atime) b2_8;
| | ^~~~
| /tmp/tmpnzda_r9j/test.c:89:17: note: previous declaration of 'b2_8' with type
'__time_t' {aka 'long int'}
|89 | extern __time_t b2_8;
| | ^~~~
Here, it tells us that it expected the st_atime field of struct stat to
have type __time_t (the 32 bit one), but it really has __time64_t.
Looking at the invocation of linknamespace.py you can see:
| python3 -B linknamespace.py --cc='arm-linux-gnueabihf-gcc-12'
--flags='-I../include
-I/build/reproducible-path/glibc-2.37/build-tree/armhf-libc
-I../sysdeps/unix/sysv/linux/arm/le -I../sysdeps/unix/sysv/linux/arm
-I../sysdeps/arm/nptl -I../sysdeps/unix/sysv/linux/include
-I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread
-I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv
-I../sysdeps/unix/arm -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/arm/le/armv7/multiarch -I../sysdeps/arm/armv7/multiarch
-I../sysdeps/arm/le/armv7 -I../sysdeps/arm/armv7 -I../sysdeps/arm/armv6t2
-I../sysdeps/arm/armv6 -I../sysdeps/arm/le -I../sysdeps/arm/include
-I../sysdeps/arm -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/flt-32
-I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754 -I../sysdeps/generic
-nostdinc -isystem /usr/lib/gcc/arm-linux-gnueabihf/12/include -isystem
/build/reproducible-path/glibc-2.37/debian/include -I..' ...
In particular, what you do not see is -U_TIME_BITS inside --flags.
> Ubuntu has just ignored those failures for now, but I am just afraid
> that if we do the same, nobody will fix them.
Armed with this knowledge, I think we need two changes. For one thing
debian/sysdeps/linux.mk needs to add -U_FILE_OFFSET_BITS to extra_cflags
to revert any possible ABI changing effects. For another, the
conformance tests use independent compiler flags defined in
conform/Makefile. There, a naive patch seems to be:
-conformtest-cc-flags = -I../include $(+sysdep-includes) $(sysincludes) -I..
+conformtest-cc-flags = -U_FILE_OFFSET_BITS -U_TIME_BITS -I../include
$(+sysdep-includes) $(sysincludes) -I..
With these two changes, I am able to successfully build glibc on armhf
with the conformance test suite passing.
> In addition it means that upstream glibc does not build anymore by
> default on a 32-bit Debian. Not really a Debian issue, but that is not
> nice either and should probably be fixed.
I think that latter change may be applicable upstream. Running the
conformance test suite with either _FILE_OFFSET_BITS or _TIME_BITS set
is not expected nor supported. This is partially evident from
conform/linknamespace.py in a comment:
| # * Header inclusions should be compiled several times with
| # different options such as -O2, -D_FORTIFY_SOURCE and
| # -D_FILE_OFFSET_BITS=64 to find out what symbols are undefined
| # from such a compilation; this is not yet implemented.
The conformance test suite clearly wants to manage these macros (and its
effects on symbols) explicitly and does not expect them to be
pre-defined.
Hope this helps
Helmut
Processed: Re: Bug#1068251: glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t
Processing control commands: > tags -1 + patch Bug #1068251 [src:glibc] glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t Added tag(s) patch. -- 1068251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1064724 marked as pending in yapet
Processing control commands: > tag -1 pending Bug #1064724 [src:yapet] yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Bug #1068045 [src:yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Added tag(s) pending. Added tag(s) pending. -- 1064724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064724 1068045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064724: marked as pending in yapet
Control: tag -1 pending Hello, Bug #1064724 in yapet reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/carnil/yapet/-/commit/06ca998023176a9c6234861b1281ee2172b301c9 crypt/blowfish: Remove EVP_CIPHER_CTX_set_key_length() Closes: #1064724 (this message was generated automatically) -- Greetings https://bugs.debian.org/1064724
Processed: Forward deepin-log-viewer 64-bit time_t on 32-bit OS bug report
Processing commands for cont...@bugs.debian.org:
> forwarded 1067560 https://github.com/linuxdeepin/developer-center/issues/7771
Bug #1067560 [src:deepin-log-viewer] FTBFS on 32-bit time64 architectures:
cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}
Set Bug forwarded-to-address to
'https://github.com/linuxdeepin/developer-center/issues/7771'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068657: pkcs11-provider FTBFS with openssl 3.2.1-3
Source: pkcs11-provider
Version: 0.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pkcs11-provider=ppc64el=0.3-1%2Bb2=1712517987=0
...
FAIL: basic-softhsm
===
Executing ./tbasic
## Raw Sign check error
openssl
pkeyutl -sign -inkey "${BASEURI}"
-pkeyopt pad-mode:none
-in ${TMPPDIR}/64Brandom.bin
-out ${TMPPDIR}/raw-sig.bin
Public Key operation error
00493C8EFF7F:error:027A:rsa routines:p11prov_sig_operate:data too small
for key size:signature.c:894:
## Sign and Verify with provided Hash and RSA
openssl dgst -sha256 -binary -out ${TMPPDIR}/sha256.bin ${SEEDFILE}
openssl
pkeyutl -sign -inkey "${PRIURI}"
-in ${TMPPDIR}/sha256.bin
-out ${TMPPDIR}/sha256-sig.bin
openssl
pkeyutl -verify -inkey "${PUBURI}"
-pubin
-in ${TMPPDIR}/sha256.bin
-sigfile ${TMPPDIR}/sha256-sig.bin
Signature Verified Successfully
## Sign and Verify with provided Hash and RSA with DigestInfo struct
openssl dgst -sha256 -binary -out ${TMPPDIR}/sha256.bin ${SEEDFILE}
openssl
pkeyutl -sign -inkey "${PRIURI}" -pkeyopt digest:sha256
-in ${TMPPDIR}/sha256.bin
-out ${TMPPDIR}/sha256-sig.bin
openssl
pkeyutl -verify -inkey "${PUBURI}" -pkeyopt digest:sha256
-pubin
-in ${TMPPDIR}/sha256.bin
-sigfile ${TMPPDIR}/sha256-sig.bin
Signature Verified Successfully
## DigestSign and DigestVerify with RSA
openssl
pkeyutl -sign -inkey "${BASEURI}"
-digest sha256
-in ${RAND64FILE}
-rawin
-out ${TMPPDIR}/sha256-dgstsig.bin
openssl
pkeyutl -verify -inkey "${BASEURI}" -pubin
-digest sha256
-in ${RAND64FILE}
-rawin
-sigfile ${TMPPDIR}/sha256-dgstsig.bin
Signature Verified Successfully
openssl
pkeyutl -verify -inkey "${PUBURI}"
-pubin
-digest sha256
-in ${RAND64FILE}
-rawin
-sigfile ${TMPPDIR}/sha256-dgstsig.bin
Signature Verified Successfully
RSA basic encrypt and decrypt
openssl
pkeyutl -encrypt -inkey "${PUBURI}" -pubin
-in ${SECRETFILE}
-out ${SECRETFILE}.enc
openssl
pkeyutl -decrypt -inkey "${PRIURI}"
-in ${SECRETFILE}.enc
-out ${SECRETFILE}.dec
## Test Disallow Public Export
openssl pkey -in $PUBURI -pubin -pubout -text
## Test CSR generation from RSA private keys
openssl
req -new -batch -key "${PRIURI}" -out ${TMPPDIR}/rsa_csr.pem
openssl
req -in ${TMPPDIR}/rsa_csr.pem -verify -noout
Certificate request self-signature verify OK
## Test fetching public keys without PIN in config files
openssl pkey -in $PUBURI -pubin -pubout -out ${TMPPDIR}/rsa.pub.nopin.pem
openssl pkey -in $ECPUBURI -pubin -pubout -out ${TMPPDIR}/ec.pub.nopin.pem
openssl pkey -in $ECXPUBURI -pubin -pubout -out ${TMPPDIR}/ecx.pub.nopin.pem
## Test fetching public keys with a PIN in URI
openssl pkey -in $BASEURIWITHPIN -pubin -pubout -out
${TMPPDIR}/rsa.pub.uripin.pem
openssl pkey -in $ECBASEURIWITHPIN -pubin -pubout -out
${TMPPDIR}/ec.pub.uripin.pem
openssl pkey -in $ECXBASEURIWITHPIN -pubin -pubout -out
${TMPPDIR}/ecx.pub.uripin.pem
## Test prompting without PIN in config files
## Test EVP_PKEY_eq on public RSA key both on token
## Test EVP_PKEY_eq on public EC key both on token
## Test EVP_PKEY_eq on public explicit EC key both on token
Failed to load key from URI: pkcs11:type=public;id=%00%07
FAIL basic-softhsm.t (exit status: 1)
...
Testsuite summary for pkcs11-provider 0.3
# TOTAL: 34
# PASS: 15
# SKIP: 18
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
See tests/test-suite.log
Please report to s...@redhat.com
make[4]: *** [Makefile:1070: test-suite.log] Error 1
Bug#1068656: pgsql-http accesses the internet during the build
Source: pgsql-http
Version: 1.6.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian PostgreSQL Maintainers
https://buildd.debian.org/status/fetch.php?pkg=pgsql-http=arm64=1.6.0-1=1712600451=0
...
regression.diffs
diff -U3 /<>/expected/http.out /<>/results/http.out
--- /<>/expected/http.out 2023-08-10 16:17:30.0 +
+++ /<>/results/http.out 2024-04-08 18:20:45.564039027 +
@@ -9,11 +9,7 @@
-- Status code
SELECT status
FROM http_get('https://httpbun.org/status/202');
- status
-
-202
-(1 row)
-
+ERROR: Could not resolve host: httpbun.org
...
Bug#1068655: lomiri-telephony-service FTBFS with abseil 20230802.1
Source: lomiri-telephony-service
Version: 0.5.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=lomiri-telephony-service=amd64=0.5.3-1%2Bb3=1712518065=0
...
/<>/libtelephonyservice/contactwatcher.cpp: In member function
‘void ContactWatcher::updateAlias()’:
/<>/libtelephonyservice/contactwatcher.cpp:157:21: error:
‘dgettext’ is not a member of ‘C’; did you mean ‘dgettext’?
157 | setAlias(C::dgettext("telephony-service", "Private Number"));
| ^~~~
In file included from
/usr/include/x86_64-linux-gnu/c++/13/bits/messages_members.h:36,
from /usr/include/c++/13/bits/locale_facets_nonio.h:2064,
from /usr/include/c++/13/locale:43,
from /usr/include/c++/13/iomanip:45,
from /usr/include/absl/strings/internal/str_format/arg.h:23,
from /usr/include/absl/strings/str_format.h:78,
from /usr/include/absl/crc/crc32c.h:32,
from /usr/include/absl/crc/internal/crc_cord_state.h:23,
from /usr/include/absl/strings/cord.h:79,
from
/usr/include/absl/container/internal/hash_function_defaults.h:56,
from /usr/include/absl/container/node_hash_set.h:42,
from /usr/include/phonenumbers/phonenumberutil.h:33,
from /<>/libtelephonyservice/phoneutils.h:27,
from
/<>/libtelephonyservice/contactwatcher.cpp:25:
/usr/include/libintl.h:44:14: note: ‘dgettext’ declared here
44 | extern char *dgettext (const char *__domainname, const char *__msgid)
| ^~~~
/<>/libtelephonyservice/contactwatcher.cpp:159:21: error:
‘dgettext’ is not a member of ‘C’; did you mean ‘dgettext’?
159 | setAlias(C::dgettext("telephony-service", "Unknown Number"));
| ^~~~
/usr/include/libintl.h:44:14: note: ‘dgettext’ declared here
44 | extern char *dgettext (const char *__domainname, const char *__msgid)
| ^~~~
...
Bug#1068589: marked as done (gem2deb: autopkgtest needs update for new version of ruby3.1: "libc6 (>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby | ruby-interpreter\n"] expected to include 'ru
Your message dated Mon, 08 Apr 2024 18:04:42 + with message-id and subject line Bug#1068589: fixed in gem2deb 2.2.3 has caused the Debian Bug report #1068589, regarding gem2deb: autopkgtest needs update for new version of ruby3.1: "libc6 (>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby | ruby-interpreter\n"] expected to include 'ruby (>= something)' 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.) -- 1068589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gem2deb Version: 2.2.2 Severity: serious X-Debbugs-CC: ruby...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby3.1 Dear maintainer(s), With a recent upload of ruby3.1 (in the time_t transition) the autopkgtest of gem2deb fails in testing when that autopkgtest is run with the binary packages of ruby3.1 from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby3.1from testing3.1.2-8.3 gem2debfrom testing2.2.2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby3.1 to testing [1]. Of course, ruby3.1 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby3.1 was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby3.1 should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby3.1 https://ci.debian.net/data/autopkgtest/testing/amd64/g/gem2deb/44893387/log.gz 42s W: Inconsistent version numbers: lib/gem2deb/version.rb says 2.1, debian/changelog says 2.2.2 42s => Unit tests ... 108s test: multibinary source package should inject dependency on ruby (>= something). : F 108s === 108s Failure: test: multibinary source package should inject dependency on ruby (>= something). (Gem2DebTest): 108s ["libc6 (>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby | ruby-interpreter\n"] expected to include 'ruby (>= something)'. 108sis not true. 108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:83:in `block (3 levels) in ' 108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:87:in `instance_exec' 108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:87:in `block in create_test_from_should_hash' 108s === OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gem2deb Source-Version: 2.2.3 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of gem2deb, 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. Antonio Terceiro (supplier of updated gem2deb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 Apr 2024 13:45:25 -0300 Source: gem2deb Architecture: source Version: 2.2.3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Closes: 1068589 Changes: gem2deb (2.2.3) unstable; urgency=medium . * dh_ruby_fixdepends: extract package name into a variable * dh_ruby_fixdepends: workaround presence of
Processed: Bug#1068589 marked as pending in gem2deb
Processing control commands: > tag -1 pending Bug #1068589 [src:gem2deb] gem2deb: autopkgtest needs update for new version of ruby3.1: "libc6 (>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby | ruby-interpreter\n"] expected to include 'ruby (>= something)' Added tag(s) pending. -- 1068589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068589: marked as pending in gem2deb
Control: tag -1 pending Hello, Bug #1068589 in gem2deb 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/ruby-team/gem2deb/-/commit/31ab3f4026d0365e9300a521d2a75931626d209b dh_ruby_fixdepends: workaround presence of libruby3.1t64 Closes: #1068589 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068589
Processed: python-pomegranate: autopkgtest regression with NumPy 1.26
Processing control commands:
> tags -1 + patch
Bug #1067233 [src:python-pomegranate] python-pomegranate: autopkgtest
regression with NumPy 1.26
Bug #1067294 [src:python-pomegranate] python-pomegranate: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned
exit code 13
Added tag(s) patch.
Added tag(s) patch.
--
1067233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067233
1067294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067233: python-pomegranate: autopkgtest regression with NumPy 1.26
Control: tags -1 + patch Hi Maintainer The attached patch fixes the test failures for me. I noticed in this package's changelog that its only purpose is to work with cnvkit. I have not tested whether cnvkit still functions with this patch in place. Regards Graham Description: Only compare init as a string after determining its type Avoids the following with error NumPy 1.26: ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all() Bug-Debian: https://bugs.debian.org/1067233 Author: Graham Inggs Last-Update: 2024-04-06 --- a/pomegranate/kmeans.pyx +++ b/pomegranate/kmeans.pyx @@ -229,10 +229,6 @@ def __init__(self, k, init='kmeans++', n_init=10): self.k = k - if init != 'first-k': - self.n_init = n_init - else: - self.n_init = 1 self.centroid_norms = calloc(self.k, sizeof(double)) if isinstance(init, (list, numpy.ndarray)): @@ -246,8 +242,14 @@ self.centroid_norms[i] = self.centroids[i].dot(self.centroids[i]) self.init = 'fixed' + self.n_init = n_init elif isinstance(init, str): self.init = init + if init != 'first-k': +self.n_init = n_init + else: +self.n_init = 1 + def __dealloc__(self): free(self.centroid_norms)
Bug#1068644: marked as done (gnutls-bin: "Fatal error: The encryption algorithm is not supported" appeared with 3.8.5 upgrade)
Your message dated Mon, 08 Apr 2024 17:19:41 + with message-id and subject line Bug#1068644: fixed in gnutls28 3.8.5-2 has caused the Debian Bug report #1068644, regarding gnutls-bin: "Fatal error: The encryption algorithm is not supported" appeared with 3.8.5 upgrade 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.) -- 1068644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnutls-bin Version: 3.8.5-1 Severity: normal X-Debbugs-Cc: none, Sanjoy Mahajan File: /usr/bin/gnutls-cli After dist-upgrading today, exim4 could no longer talk to my usual outgoing mail server. I reproduced the problem using just gnutls-cli. The problem started after today's upgrade of the various gnutls packages. They were upgraded from 3.8.4-2 to 3.8.5-1. The following command with the given input lines reproduces the problem: $ gnutls-cli -V -d 9 --starttls --crlf --port 587 -V outgoing.mit.edu EHLO randomhost STARTTLS ctrl-D [to send EOF] It fails with "*** Fatal error: The encryption algorithm is not supported." (I haven't tried it with other outgoing servers, but this one definitely shows the problem.) The problem goes away after downgrading the relevant packages to 3.8.4-2 : # apt install gnutls-bin=3.8.4-2 gnutls-doc=3.8.4-2 libgnutls-dane0t64=3.8.4-2 libgnutls-openssl27t64=3.8.4-2 libgnutls28-dev=3.8.4-2 libgnutls30t64=3.8.4-2 (My sources.list includes the snapshots repos deb [check-valid-until=no] http://snapshot.debian.org/archive/debian/20240329T213539Z/ unstable main deb-src [check-valid-until=no] http://snapshot.debian.org/archive/debian/20240329T213539Z/ unstable main ) The lines around the fatal error message with 3.8.5-1 are: |<4>| HSK[0x5632451d5260]: SERVER HELLO DONE (14) was received. Length 0[0], frag offset 0, frag length: 0, sequence: 0 |<3>| ASSERT: ../../lib/buffers.c[get_last_packet]:1130 |<3>| ASSERT: ../../lib/buffers.c[_gnutls_handshake_io_recv_int]:1374 |<3>| ASSERT: ../../../lib/nettle/pk.c[_wrap_nettle_pk_encrypt]:773 |<3>| ASSERT: ../../../lib/auth/rsa.c[_gnutls_gen_rsa_client_kx]:288 |<3>| ASSERT: ../../lib/kx.c[_gnutls_send_client_kx_message]:379 |<3>| ASSERT: ../../lib/handshake.c[handshake_client]:3183 *** Fatal error: The encryption algorithm is not supported. |<5>| REC: Sending Alert[2|80] - Internal error |<5>| REC[0x5632451d5260]: Preparing Packet Alert(21) with length: 2 and min pad: 0 |<9>| ENC[0x5632451d5260]: cipher: NULL, MAC: MAC-NULL, Epoch: 0 |<5>| REC[0x5632451d5260]: Sent Packet[2] Alert(21) in epoch 0 and length: 7 *** Handshake has failed |<5>| REC[0x5632451d5260]: Start of epoch cleanup |<5>| REC[0x5632451d5260]: End of epoch cleanup |<5>| REC[0x5632451d5260]: Epoch #0 freed |<5>| REC[0x5632451d5260]: Epoch #1 freed I've kept my packages at 3.8.4-2 for now,n but I can do more debug tests if needed (by upgrading, testing, and downgrading). -Sanjoy -- System Information: Debian Release: sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 gnutls-bin depends on: ii libc6 2.37-15.1 ii libgnutls-dane0t64 3.8.5-1 ii libgnutls30t64 3.8.5-1 ii libtasn1-6 4.19.0-3+b2 gnutls-bin recommends no packages. gnutls-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gnutls28 Source-Version: 3.8.5-2 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of gnutls28, 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. Andreas Metzler (supplier of updated gnutls28 package) (This message was generated automatically at their request; if you believe that there is a problem with it
Bug#1031969: marked as done (python3.10-venv: python3-venv no longer installable since python3-distutils 3.11.2-2)
Your message dated Mon, 8 Apr 2024 19:18:28 +0200
with message-id <0b7fe4e3-592c-abb3-6a02-0c6dd4100...@debian.org>
and subject line python3.10 has been removed from Debian
has caused the Debian Bug report #1031969,
regarding python3.10-venv: python3-venv no longer installable since
python3-distutils 3.11.2-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1031969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3.10-venv
Version: 3.10.10-2
Severity: normal
Today's apt full-upgrade removed python3.10-venv and it can't be
installed any more, as it depends on python3.10-distutils which isn't
provided by python3-distutils any more. Up until today, everything
worked—I had both 3.10 and 3.11 venvs lying around and working fine.
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (990, 'stable-security'), (990, 'testing'), (500,
'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500,
'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_USER, TAINT_WARN
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3.10-venv depends on:
ii python3-pip-whl 23.0+dfsg-2
ii python3-setuptools-whl 66.1.1-1
ii python3.10 3.10.10-2
pn python3.10-distutils
python3.10-venv recommends no packages.
python3.10-venv suggests no packages.
--
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/
--- End Message ---
--- Begin Message ---
Version: 3.10.13-1+rm
src:python3.10 was never part of a stable release.
It has been superseded by newer versions (python3.11 in
bookworm/trixie/sid, python3.12 in trixie/sid).
See https://bugs.debian.org/1068368 for details on the removal.
I'm closing the remaining bug reports now.
In case the bug is still present in recent releases, please reopen and
reassign it.
Andreas--- End Message ---
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
Hi Sebastian, On Mon, Apr 08, 2024 at 06:43:01PM +0200, Sebastian Andrzej Siewior wrote: > control: tags -1 patch > control: reassign -1 yapet 2.6-1 > > On 2024-04-08 08:32:58 [+0200], Kurt Roeckx wrote: > > There might be a related change that doesn't allow restarting the > > operation with the same context without setting things up again. > > Yapet is broken and the openssl update revealed the problem. I > reassigned it to yapet 2.6 but probably affects earlier versions. > But then the 1.1.1 series is no longer maintained so… > > Patches attached and they hold the details of why and such. > > This needs to be applied to unstable and Bookworm. > The testsuite passes and I can open Sean's test file. > Further testing is welcome by actual users ;) Thanks for the investigation and bringing the fixes to upstream already: https://github.com/RafaelOstertag/yapet/pull/29 > > I can NMU if needed just yell. No need for that, will take it with my maintainers hat on from here. Regards, Salvatore
Processed: reassign 1068045 to src:yapet, forcibly merging 1064724 1068045
Processing commands for cont...@bugs.debian.org: > reassign 1068045 src:yapet Bug #1068045 [yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Bug reassigned from package 'yapet' to 'src:yapet'. No longer marked as found in versions yapet/2.6-1. Ignoring request to alter fixed versions of bug #1068045 to the same values previously set > forcemerge 1064724 1068045 Bug #1064724 [src:yapet] yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Bug #1068045 [src:yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Set Bug forwarded-to-address to 'https://github.com/RafaelOstertag/yapet/issues/26'. Severity set to 'serious' from 'grave' Removed indication that 1068045 affects yapet Marked as found in versions yapet/2.6-1. Added tag(s) trixie, upstream, confirmed, sid, and ftbfs. Bug #1064724 [src:yapet] yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) patch. Merged 1064724 1068045 > thanks Stopping processing here. Please contact me if you need assistance. -- 1064724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064724 1068045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: symfit: autopkgtest regression with NumPy 1.26
Processing control commands:
> tags -1 + patch
Bug #1067234 [src:symfit] symfit: autopkgtest regression with NumPy 1.26
Bug #1067282 [src:symfit] symfit: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) patch.
Added tag(s) patch.
--
1067234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067234
1067282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067234: symfit: autopkgtest regression with NumPy 1.26
Control: tags -1 + patch
Hi Maintainer
While asserting that no warnings are raised is a useful test for the
upstream developers, I don't think it makes sense for downstreams.
I propose to disable the assertion as follows:
--- a/tests/test_minimizers.py
+++ b/tests/test_minimizers.py
@@ -117,7 +117,7 @@
# Should no longer raise warnings, because internally we practice
# what we preach.
fit_custom = BFGS(chi_squared, [a, b])
-assert len(recwarn) == 0
+#assert len(recwarn) == 0
fit_custom_result = fit_custom.execute()
Please let me know if you are happy with a team upload and I will proceed.
As a bonus, I attach a patch that fixes several SyntaxWarnings that
occur with Python 3.12.
Regards
Graham
Description: Fix several SyntaxWarnings
Use raw strings to avoid invalid escape sequence
Author: Graham Inggs
Last-Update: 2024-04-06
--- a/symfit/core/operators.py
+++ b/symfit/core/operators.py
@@ -45,7 +45,7 @@
# return orig_ne(self.__class__, other)
def call(self, *values, **named_values):
-"""
+r"""
Call an expression to evaluate it at the given point.
Future improvements: I would like if func and signature could be buffered after the
--- a/symfit/core/support.py
+++ b/symfit/core/support.py
@@ -293,7 +293,7 @@
return jac
def key2str(target):
-"""
+r"""
In ``symfit`` there are many dicts with symbol: value pairs.
These can not be used immediately as \*\*kwargs, even though this would make
a lot of sense from the context.
@@ -321,4 +321,4 @@
base_str += 'd{}{}'.format(var, count if count > 1 else '')
return base_str
-sympy.Derivative.name = property(name)
\ No newline at end of file
+sympy.Derivative.name = property(name)
--- a/symfit/core/fit.py
+++ b/symfit/core/fit.py
@@ -29,7 +29,7 @@
from the model.
"""
def __init__(self, model, *ordered_data, absolute_sigma=None, **named_data):
-"""
+r"""
:param model: (dict of) sympy expression or ``Model`` object.
:param bool absolute_sigma: True by default. If the sigma is only used
for relative weights in your problem, you could consider setting it to
--- a/symfit/core/minimizers.py
+++ b/symfit/core/minimizers.py
@@ -208,7 +208,7 @@
:class:`~symfit.core.minimizers.DifferentialEvolution`.
"""
def __init__(self, *args, minimizers=None, **kwargs):
-'''
+r'''
:param minimizers: a :class:`~collections.abc.Sequence` of
:class:`~symfit.core.minimizers.BaseMinimizer` objects, which need
to be run in order.
@@ -324,7 +324,7 @@
def execute(self, bounds=None, jacobian=None, hessian=None,
constraints=None, *, tol=1e-9, **minimize_options):
-"""
+r"""
Calls the wrapped algorithm.
:param bounds: The bounds for the parameters. Usually filled by
@@ -790,7 +790,7 @@
return lbounds, ubounds
def execute(self, jacobian=None, method='trf', **minpack_options):
-"""
+r"""
:param \*\*minpack_options: Any named arguments to be passed to
:func:`scipy.optimize.least_squares`
"""
--- a/symfit/core/fit_results.py
+++ b/symfit/core/fit_results.py
@@ -26,7 +26,7 @@
:class:`~symfit.core.models.Model`'s.
"""
def __init__(self, model, popt, covariance_matrix, minimizer, objective, message, *, constraints=None, **minimizer_output):
-"""
+r"""
:param model: :class:`~symfit.core.models.Model` that was fit to.
:param popt: best fit parameters, same ordering as in model.params.
:param covariance_matrix: covariance matrix.
@@ -276,4 +276,4 @@
f_is = [f_is[var] for var in model.dependent_vars]
SS_res = np.sum([np.sum((y_i - f_i)**2) for y_i, f_i in zip(y_is, f_is) if y_i is not None])
SS_tot = np.sum([np.sum((y_i - y_bar)**2) for y_i, y_bar in zip(y_is, y_bars) if y_i is not None])
-return 1 - SS_res/SS_tot
\ No newline at end of file
+return 1 - SS_res/SS_tot
--- a/symfit/core/objectives.py
+++ b/symfit/core/objectives.py
@@ -386,7 +386,7 @@
class HessianObjectiveJacApprox(HessianObjective):
-"""
+r"""
This object should only be used as a Mixin for covariance matrix estimation.
Since the covariance matrix for the least-squares method is proportional to
the Hessian of :math:`S`, this function attempts to return the Hessian
@@ -552,4 +552,4 @@
)
return np.array(evaluated_hess[0])
else:
-return None
\ No newline at end of file
+return None
Processed: Merge numpy bugs
Processing commands for cont...@bugs.debian.org:
> merge 1067234 1067282
Bug #1067234 [src:symfit] symfit: autopkgtest regression with NumPy 1.26
Bug #1067234 [src:symfit] symfit: autopkgtest regression with NumPy 1.26
Added tag(s) trixie, ftbfs, and sid.
Bug #1067282 [src:symfit] symfit: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Merged 1067234 1067282
> merge 1067233 1067294
Bug #1067233 [src:python-pomegranate] python-pomegranate: autopkgtest
regression with NumPy 1.26
Bug #1067233 [src:python-pomegranate] python-pomegranate: autopkgtest
regression with NumPy 1.26
Added tag(s) sid, ftbfs, and trixie.
Bug #1067294 [src:python-pomegranate] python-pomegranate: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned
exit code 13
Merged 1067233 1067294
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067233
1067234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067234
1067282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067282
1067294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
control: tags -1 patch
control: reassign -1 yapet 2.6-1
On 2024-04-08 08:32:58 [+0200], Kurt Roeckx wrote:
> There might be a related change that doesn't allow restarting the
> operation with the same context without setting things up again.
Yapet is broken and the openssl update revealed the problem. I
reassigned it to yapet 2.6 but probably affects earlier versions.
But then the 1.1.1 series is no longer maintained so…
Patches attached and they hold the details of why and such.
This needs to be applied to unstable and Bookworm.
The testsuite passes and I can open Sean's test file.
Further testing is welcome by actual users ;)
I can NMU if needed just yell.
Sebastian
From a54b5e81a61aa7e77e45a970ce88b9b4269fde7d Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior
Date: Mon, 8 Apr 2024 18:03:30 +0200
Subject: [PATCH 1/2] crypt/blowfish: Remove EVP_CIPHER_CTX_set_key_length().
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
yapet did for blowfish:
| EVP_CipherInit_ex(ctx, cipher, NULL, KEY, iv, mode);
| EVP_CIPHER_CTX_set_key_length(ctx, KEY_LENGTH);
| EVP_CipherUpdate(ctx, …);
this worked in earlier OpenSSL versions and stopped working in
openssl-3.0.13. The problem here is that the
EVP_CIPHER_CTX_set_key_length() is ignored and the later OpenSSL version
returns rightfully an error "Provider routines::no key set" here.
Blowfish does support variable key lenghts but the key length has to be
set first followed by the actual key. Otherwise the blocksize (16) will
be used.
The correct way to deal with this would be:
| EVP_CipherInit_ex(ctx, cipher, NULL, NULL, NULL, mode);
| EVP_CIPHER_CTX_set_key_length(ctx, KEY_LENGTH);
| EVP_CipherInit_ex(ctx, NULL, NULL, KEY, IV, mode);
| EVP_CipherUpdate(ctx, …);
Using now the proper way will break earlier databases because in the
blowfish case, always the default blocksize / 16 has been used.
In order to keep compatibility with earlier versions of the database and
openssl remove the EVP_CIPHER_CTX_set_key_length() invocation.
Fixes #26
Fixes #24
Signed-off-by: Sebastian Andrzej Siewior
---
src/libs/crypt/crypto.cc | 10 --
1 file changed, 10 deletions(-)
diff --git a/src/libs/crypt/crypto.cc b/src/libs/crypt/crypto.cc
index ade991edf961a..139e0823e753a 100644
--- a/src/libs/crypt/crypto.cc
+++ b/src/libs/crypt/crypto.cc
@@ -98,16 +98,6 @@ EVP_CIPHER_CTX* Crypto::initializeOrThrow(MODE mode) {
throw CipherError{_("Error initializing cipher")};
}
-success = EVP_CIPHER_CTX_set_key_length(context, _key->keySize());
-if (success != SSL_SUCCESS) {
-destroyContext(context);
-char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
-std::snprintf(msg, YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE,
- _("Cannot set key length on context to %d"),
- _key->keySize());
-throw CipherError{msg};
-}
-
return context;
}
--
2.43.0
>From aaa573b14bafcc9a6b46495bd4ffc15b90d35902 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior
Date: Mon, 8 Apr 2024 18:19:12 +0200
Subject: [PATCH 2/2] crypt/aes: Remove EVP_CIPHER_CTX_set_key_length().
The EVP_CIPHER_CTX_set_key_length() in the AES-256-CBC case is pointless
because the key here is fixed EVP_CIPHER_CTX_set_key_length() and the
function does not change the size.
Remove the EVP_CIPHER_CTX_set_key_length() invocation.
Signed-off-by: Sebastian Andrzej Siewior
---
src/libs/crypt/aes256.cc | 11 ---
1 file changed, 11 deletions(-)
diff --git a/src/libs/crypt/aes256.cc b/src/libs/crypt/aes256.cc
index 1041b9c57347c..e105b1a5beddd 100644
--- a/src/libs/crypt/aes256.cc
+++ b/src/libs/crypt/aes256.cc
@@ -113,17 +113,6 @@ EVP_CIPHER_CTX* Aes256::initializeOrThrow(const SecureArray& ivec, MODE mode) {
throw CipherError{_("Error initializing cipher")};
}
-success = EVP_CIPHER_CTX_set_key_length(context, getKey()->keySize());
-if (success != SSL_SUCCESS) {
-LOG_MESSAGE(std::string{__func__} + ": Error setting key length");
-destroyContext(context);
-char msg[YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE];
-std::snprintf(msg, YAPET::Consts::EXCEPTION_MESSAGE_BUFFER_SIZE,
- _("Cannot set key length on context to %d"),
- getKey()->keySize());
-throw CipherError{msg};
-}
-
return context;
}
--
2.43.0
Processed: Re: [Pkg-openssl-devel] Bug#1068045: libssl3: breaks YAPET
Processing control commands: > tags -1 patch Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Added tag(s) patch. > reassign -1 yapet 2.6-1 Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Bug reassigned from package 'libssl3,yapet' to 'yapet'. No longer marked as found in versions 3.2.1-3, yapet/2.6-1, and openssl/3.0.13-1~deb12u1. No longer marked as fixed in versions openssl/3.0.11-1~deb12u2. Bug #1068045 [yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB Marked as found in versions yapet/2.6-1. -- 1068045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1068644: gnutls-bin: "Fatal error: The encryption algorithm is not supported" appeared with 3.8.5 upgrade
Processing control commands: > severity -1 serious Bug #1068644 [gnutls-bin] gnutls-bin: "Fatal error: The encryption algorithm is not supported" appeared with 3.8.5 upgrade Severity set to 'serious' from 'normal' > forwarded -1 https://gitlab.com/gnutls/gnutls/-/issues/1540 Bug #1068644 [gnutls-bin] gnutls-bin: "Fatal error: The encryption algorithm is not supported" appeared with 3.8.5 upgrade Set Bug forwarded-to-address to 'https://gitlab.com/gnutls/gnutls/-/issues/1540'. -- 1068644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068653: evolution: Can't use google accounts
Package: evolution Version: 3.50.3-1+b1 Severity: grave I have two accounts (personal and work) and both of them are returning “Timeout was reached”. I have tried removing the accounts and re-adding them without success. personal account is @gmail.com work account is @EMPLOYER'S-DOMAIN -- System Information Debian Release: 12.5 Kernel Version: Linux gabriel 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux -- http://hexmode.com/ Don't ask me who's influenced me. A lion is made up of the lambs he's digested, and I've been reading all my life. -- Giorgos Seferis
Bug#1065791: marked as done (sleuthkit: FTBFS on arm{el,hf}: /usr/include/zlib.h:1840:5: error: unknown type name ‘off64_t’)
Your message dated Mon, 08 Apr 2024 16:21:32 +
with message-id
and subject line Bug#1065791: fixed in sleuthkit 4.12.1+dfsg-2
has caused the Debian Bug report #1065791,
regarding sleuthkit: FTBFS on arm{el,hf}: /usr/include/zlib.h:1840:5: error:
unknown type name ‘off64_t’
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.)
--
1065791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sleuthkit
Version: 4.12.1+dfsg-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=sleuthkit=armel=4.12.1%2Bdfsg-1.1=1709542529=0
In file included from /usr/include/zlib.h:34,
from decmpfs.c:13:
/usr/include/zlib.h:1840:5: error: unknown type name ‘off64_t’
1840 | z_off64_t pos;
| ^
/usr/include/zlib.h:1860:12: error: unknown type name ‘off64_t’
1860 |ZEXTERN z_off64_t ZEXPORT gzseek64(gzFile, z_off64_t, int);
|^
/usr/include/zlib.h:1860:47: error: unknown type name ‘off64_t’; did you mean
‘off_t’?
1860 |ZEXTERN z_off64_t ZEXPORT gzseek64(gzFile, z_off64_t, int);
| ^
/usr/include/zlib.h:1861:12: error: unknown type name ‘off64_t’
1861 |ZEXTERN z_off64_t ZEXPORT gztell64(gzFile);
|^
/usr/include/zlib.h:1862:12: error: unknown type name ‘off64_t’
1862 |ZEXTERN z_off64_t ZEXPORT gzoffset64(gzFile);
|^
/usr/include/zlib.h:1863:58: error: unknown type name ‘off64_t’; did you mean
‘off_t’?
1863 |ZEXTERN uLong ZEXPORT adler32_combine64(uLong, uLong, z_off64_t);
| ^
/usr/include/zlib.h:1864:56: error: unknown type name ‘off64_t’; did you mean
‘off_t’?
1864 |ZEXTERN uLong ZEXPORT crc32_combine64(uLong, uLong, z_off64_t);
|^
make[4]: *** [Makefile:547: decmpfs.lo] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: sleuthkit
Source-Version: 4.12.1+dfsg-2
Done: Francisco Vilmar Cardoso Ruviaro
We believe that the bug you reported is fixed in the latest version of
sleuthkit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Francisco Vilmar Cardoso Ruviaro (supplier of updated
sleuthkit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 08 Apr 2024 15:58:50 +
Source: sleuthkit
Architecture: source
Version: 4.12.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Francisco Vilmar Cardoso Ruviaro
Closes: 1065791
Changes:
sleuthkit (4.12.1+dfsg-2) unstable; urgency=medium
.
* Team upload.
* Add debian/patches/fix-armhf-build.patch.
Thanks to Steve Langasek . (Closes: #1065791)
* Update packaging copyright years.
Checksums-Sha1:
ee52742b230e257d3de9bcb612769db52fad5706 2184 sleuthkit_4.12.1+dfsg-2.dsc
04398aa67cd55d04bc348c4761cada3b0f059a8a 34008
sleuthkit_4.12.1+dfsg-2.debian.tar.xz
ec600730736fa71f70fb3ac41278a1dd514b32d8 9148
sleuthkit_4.12.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
f4a008e17b98cadcee9c94261efb2326214dde63a69a0fbb941ca99427a2a380 2184
sleuthkit_4.12.1+dfsg-2.dsc
361bc0c6c2fad1d735efc9b826b7f06d320758fb98de059dda5021b5cf6d5724 34008
sleuthkit_4.12.1+dfsg-2.debian.tar.xz
63f7cdacd9ce278f48e7a2aa75c686e5951da2c938f81f800a510aabecd2e835 9148
sleuthkit_4.12.1+dfsg-2_amd64.buildinfo
Files:
e9afd6469ec6eaafedfa2511338decbe 2184 admin optional
sleuthkit_4.12.1+dfsg-2.dsc
4f2fde1cdf27953b84a782b4448bfad2 34008 admin optional
sleuthkit_4.12.1+dfsg-2.debian.tar.xz
5683f06d2a90055f6ae8f0bd64b2021a 9148 admin optional
sleuthkit_4.12.1+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEG4z2Vu87hEcvSPDngvv3BgsvfQAFAmYUFh0SHHZpbG1hckBk
Processed: Bug#1065791 marked as pending in sleuthkit
Processing control commands:
> tag -1 pending
Bug #1065791 [src:sleuthkit] sleuthkit: FTBFS on arm{el,hf}:
/usr/include/zlib.h:1840:5: error: unknown type name ‘off64_t’
Added tag(s) pending.
--
1065791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1065791: marked as pending in sleuthkit
Control: tag -1 pending Hello, Bug #1065791 in sleuthkit 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/pkg-security-team/sleuthkit/-/commit/14a7cc2194f4762350a3dfc821817aceb6e16525 Add debian/patches/fix-armhf-build.patch Thanks to Steve Langasek (Closes: #1065791) (this message was generated automatically) -- Greetings https://bugs.debian.org/1065791
Bug#1068608: tfortune dependencies unsatisfiable on 32-bit non-i386 architectures.
[Cc Steve] On Sun, Apr 07, 22:02, Peter Michael Green wrote: > After being rebuilt for the time64 transition, tfortune > depends on both liblopsub1 and liblopsub1t64. As a > result it is uninstallable on architectures that are undergoing > the time64 transition (armel, armhf and some debian-ports > architectures). > > Ubuntu has already fixed this issue by removing the hardcoded > dependency on liblopsub1. > > https://launchpadlibrarian.net/720835658/tfortune_1.0.1-1build1_1.0.1-1ubuntu1.diff.gz This was fixed already on February 2nd as suggested by Steve, see upstream commit f40f0aae211f. Please let me know if any further action is required on my part. Thanks Andre -- Max Planck Institute for Biology Max-Planck-Ring 5, 72076 Tübingen, Germany. Phone: (+49) 7071 601 829 http://people.tuebingen.mpg.de/maan/ signature.asc Description: PGP signature
Bug#1066396: lftp: FTBFS: ./config.h:2540:11: fatal error: trio.h: No such file or directory
On Sun, Mar 24, 2024 at 03:42:18PM +0500, Andrey Rakhmatullin wrote: > On Wed, Mar 13, 2024 at 01:03:20PM +0100, Lucas Nussbaum wrote: > > > ./config.h:2540:11: fatal error: trio.h: No such file or directory > > > 2540 | # include "trio.h" > > > | ^~~~ > (this suggests that using trio is not actually supported but that's > irrelevant) > This is caused by the stdio detection failing and should be fixed by > adding #include to the test case code in m4/needtrio.m4 but this > package doesn't run autoreconf so fixing d/rules to at least do that is > also needed. I gave the following a try, but it makes `make install` fail with an error suggesting a variable was left empty. Making install in po make[3]: Entering directory '/<>/po' /<>/debian/lftp/usr/share make[3]: /<>/debian/lftp/usr/share: Permission denied make[3]: *** [Makefile:304: install-data-yes] Error 127 make[3]: Leaving directory '/<>/po' ... diff -Nru lftp-4.9.2/debian/rules lftp-4.9.2/debian/rules --- lftp-4.9.2/debian/rules 2018-09-17 09:33:33.0 +0200 +++ lftp-4.9.2/debian/rules 2024-04-08 16:46:06.0 +0200 @@ -20,6 +20,8 @@ #configure: configure-stamp configure-stamp: dh_testdir + dh_update_autotools_config + dh_autoreconf # Add here commands to configure the package. CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure \ --prefix=/usr \ @@ -56,6 +58,7 @@ [ ! -f Makefile ] || $(MAKE) distclean rm -f doc/lftp.inf* + dh_autoreconf_clean dh_clean install: build
Processed: severity 1064996 important
Processing commands for cont...@bugs.debian.org:
> severity 1064996 important
Bug #1064996 {Done: Michael R. Crusoe }
[src:azure-uamqp-python] azure-uamqp-python: CVE-2024-27099
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1064996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068647: python-pot: autopkgtest regression on i386 with NumPy 1.26.4
Source: python-pot
Version: 0.9.3+dfsg-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
your package has a autopkgtest regression on i386 with NumPy 1.26.4.
Hopefully relevant excerpt from test log at
https://ci.debian.net/data/autopkgtest/testing/i386/p/python-pot/45030103/log.gz
follows:
207s === FAILURES
===
207s ___ test_solve_sample_methods[numpy-{'method': 'gaussian'}]
207s
207s nx =
207s method_params = {'method': 'gaussian'}
207s
207s @pytest.mark.parametrize("method_params",
lst_method_params_solve_sample)
207s def test_solve_sample_methods(nx, method_params):
207s
207s n_samples_s = 20
207s n_samples_t = 7
207s n_features = 2
207s rng = np.random.RandomState(0)
207s
207s x = rng.randn(n_samples_s, n_features)
207s y = rng.randn(n_samples_t, n_features)
207s a = ot.utils.unif(n_samples_s)
207s b = ot.utils.unif(n_samples_t)
207s
207s xb, yb, ab, bb = nx.from_numpy(x, y, a, b)
207s
207s sol = ot.solve_sample(x, y, **method_params)
207s solb = ot.solve_sample(xb, yb, ab, bb, **method_params)
207s
207s # check some attributes (no need )
207s assert_allclose_sol(sol, solb)
207s
207s sol2 = ot.solve_sample(x, x, **method_params)
207s if method_params['method'] not in ['factored', 'lowrank']:
207s > np.testing.assert_allclose(sol2.value, 0)
207s
207s test/test_solvers.py:419:
207s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
207s
207s args = (.compare at 0xf0b37e88>,
array(8.8817842e-16), array(0))
207s kwds = {'equal_nan': True, 'err_msg': '', 'header': 'Not equal to
tolerance rtol=1e-07, atol=0', 'verbose': True}
207s
207s @wraps(func)
207s def inner(*args, **kwds):
207s with self._recreate_cm():
207s > return func(*args, **kwds)
207s E AssertionError:
207s E Not equal to tolerance rtol=1e-07, atol=0
207s E
207s E Mismatched elements: 1 / 1 (100%)
207s E Max absolute difference: 8.8817842e-16
207s E Max relative difference: inf
207s Ex: array(8.881784e-16)
207s Ey: array(0)
207s
207s /usr/lib/python3.12/contextlib.py:81: AssertionError
Cheers
Timo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmYT6yAACgkQzIxr3RQD
9MoOQQ/+N1NSlnHlih5jhMBGkClnHTDpLmz8UBBdjnYoqEjQnz/SoBazuViOLd6Z
+eLeUJ8N26fsfe67eiNoVqD4ugEfMNItAq74BMQF2XF2vYVqPztLmxUwQpBrGVkD
oUOQTWos/iJCn8ITMLj+8cYl7EW99UYgh/4shhnbIhKvsKui0fnNqN+sri7gfiAX
om6UJddYkTsQmEGCTkqKgqGqZc70N9Se+mpGFngfhQXFEgQblWIn/HkahnBBp3fJ
dGTbjlT401snZ+81E/h2Ltdz3a0pQ05lN7KoJv03hy18UlToYZDcjDZMc4xIwQNG
SetjCn5+Lfm2NeXwrJ+iYNB+yc3Z4/P03VljuMJfo9pZAeNMnkyMJzQxSDLpeluV
3DeI7KQjAs/y5B/LDtvjPCUcDOoKesYcTDOyDAXRgs1Pu3WwUU5Yi7HmPgKJefmz
UXbnvsOdWgB1UQBX9rh5CKK0VHEb8ZhSZK3EuWjbiel467xml8ic2UYhr3iKadYt
a5H3nfjau1wxoGt2lkH6oOUC19A+iJXQYEZXCM9BWIZC12A6SGsBRrfcxS0jrTGs
Dg5ddnoEreJ7hAWyJHZPbbob/ITLsEKh62js7OH5zLhg2nzT/qXQCwKiDla1lhGY
jn9KxRMnV23CDMGjU2JPeImN9ha2ifVZ1zo/RRzXTu2bw3sHrVs=
=ypga
-END PGP SIGNATURE-
Bug#1068646: pyorbital: autopkgtest regression on i386 with NumPy 1.26.4
Source: pyorbital
Version: 1.8.2-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
the pyorbital package has an autopkgtest regression on i386 only with
NumPy 1.26.4. Hopefully relevant excerpt from test log at
https://ci.debian.net/data/autopkgtest/testing/i386/p/pyorbital/45030100/log.gz
follows:
127s === FAILURES
===
127s _ TestGetObserverLook.test_basic_dask
__
127s
127s self =
127s
127s def test_basic_dask(self):
127s """Test with dask array inputs"""
127s from pyorbital import orbital
127s import dask.array as da
127s sat_lon = da.from_array(self.sat_lon, chunks=2)
127s sat_lat = da.from_array(self.sat_lat, chunks=2)
127s sat_alt = da.from_array(self.sat_alt, chunks=2)
127s lon = da.from_array(self.lon, chunks=2)
127s lat = da.from_array(self.lat, chunks=2)
127s alt = da.from_array(self.alt, chunks=2)
127s azi, elev = orbital.get_observer_look(sat_lon, sat_lat,
127s sat_alt, self.t,
127s lon, lat, alt)
127s > np.testing.assert_allclose(azi.compute(), self.exp_azi)
127s
127s /usr/lib/python3/dist-packages/pyorbital/tests/test_orbital.py:259:
127s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
127s
127s args = (.compare at 0xf0c0cf28>,
array([[331.00275902, 330.95954165, 180., 86.4354...00275902,
330.95954165, 180., 86.435411 ],
127s[330.91642994, 180., 0., 273.232073 ]]))
127s kwds = {'equal_nan': True, 'err_msg': '', 'header': 'Not equal to
tolerance rtol=1e-07, atol=0', 'verbose': True}
127s
127s @wraps(func)
127s def inner(*args, **kwds):
127s with self._recreate_cm():
127s > return func(*args, **kwds)
127s E AssertionError:
127s E Not equal to tolerance rtol=1e-07, atol=0
127s E
127s E Mismatched elements: 1 / 8 (12.5%)
127s E Max absolute difference: 14.03624347
127s E Max relative difference: 0.07797913
127s Ex: array([[331.002759, 330.959542, 180. , 86.435411],
127s E [330.91643 , 165.963757, 0. , 273.232073]])
127s Ey: array([[331.002759, 330.959542, 180. , 86.435411],
127s E [330.91643 , 180. , 0. , 273.232073]])
127s
127s /usr/lib/python3.11/contextlib.py:81: AssertionError
127s _ TestGetObserverLook.test_basic_numpy
_
127s
127s self =
127s
127s def test_basic_numpy(self):
127s """Test with numpy array inputs"""
127s from pyorbital import orbital
127s azi, elev = orbital.get_observer_look(self.sat_lon, self.sat_lat,
127s self.sat_alt, self.t,
127s self.lon, self.lat,
self.alt)
127s > np.testing.assert_allclose(azi, self.exp_azi)
127s
127s /usr/lib/python3/dist-packages/pyorbital/tests/test_orbital.py:243:
127s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
127s
127s args = (.compare at 0xf0abaf28>,
array([[331.00275902, 330.95954165, 180., 86.4354...00275902,
330.95954165, 180., 86.435411 ],
127s[330.91642994, 180., 0., 273.232073 ]]))
127s kwds = {'equal_nan': True, 'err_msg': '', 'header': 'Not equal to
tolerance rtol=1e-07, atol=0', 'verbose': True}
127s
127s @wraps(func)
127s def inner(*args, **kwds):
127s with self._recreate_cm():
127s > return func(*args, **kwds)
127s E AssertionError:
127s E Not equal to tolerance rtol=1e-07, atol=0
127s E
127s E Mismatched elements: 1 / 8 (12.5%)
127s E Max absolute difference: 14.03624347
127s E Max relative difference: 0.07797913
127s Ex: array([[331.002759, 330.959542, 180. , 86.435411],
127s E [330.91643 , 165.963757, 0. , 273.232073]])
127s Ey: array([[331.002759, 330.959542, 180. , 86.435411],
127s E [330.91643 , 180. , 0. , 273.232073]])
127s
127s /usr/lib/python3.11/contextlib.py:81: AssertionError
127s __ TestGetObserverLook.test_xarray_with_dask
___
127s
127s self =
127s
127s def test_xarray_with_dask(self):
127s """Test with xarray DataArray with dask array as inputs"""
127s from pyorbital import orbital
127s import dask.array as da
127s import xarray as xr
127s
127s def _xarr_conv(input):
127s
Bug#1063077: syslog-ng: identified for time_t transition but no ABI in shlibs
Ok. I re-checked the patch and realized that I checked the only wrong
module (the only one which is arch all and not any).
So my apologies for the fuzz and will apply the patch with the
appropriate changes.
But here my original reply too:
I admit that I joined late to this conversation. But my complain is not
about the time_t change.
My complain is the contradiction between two thing:
1. https://wiki.debian.org/binNMU says that I should declar[e]
dependency between an arch: all to an arch: any package: Depends: foo
(>= ${source:Version}), foo (<< ${source:Version}.1~)
2. The bug report ask to depend on 'syslog-ng-core (=
$${binary:Version})'
This two is contradict and because syslog-ng complies with the binNMU
request, I really reluctant to change that. Especially because in that
case another ticket will be created in no-time to revert it.
This is from the proposed changelog:
+ * Adjust shlibs for syslog-ng-core to use a strict versioned depends;
+previously, modules used >=, << dependencies which did not account for
+the possibility of ABI skew in a binNMU, which is exactly what happens
+with the 64-bit time_t transition.
And my question is again, is the rules really changed or we bend the
rules just because of one transition?
On Fri, 2024-04-05 at 15:15 +0200, Bernd Zeimetz wrote:
> Hi Attila,
>
> On Fri, 2024-04-05 at 09:47 +0100, Attila Szalay wrote:
> > Based on https://wiki.debian.org/NonMaintainerUpload, the binNMU
> > should
> > be careful
>
> I think you are confusing binNMUs and NMUs.
> See https://wiki.debian.org/binNMU
>
> They are handled more or less automatic as soon as a rebuild is
> needed
> for a transition.
>
> You might want to read the bug report again, it basically says that
> no
> NMU will be uploaded, but you package will break if you don't apply
> the
> attached patch. And the binNMU that will most likely break it will
> happen.
>
> The way how the time_t change happens was discussed for a *long*
> time,
> you are a bit late with complaints.
>
>
> Bernd
>
>
Bug#1068634: marked as done (libdialog-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libdialog.a)
Your message dated Mon, 08 Apr 2024 11:05:00 + with message-id and subject line Bug#1068634: fixed in dialog 1.3-20240307-2 has caused the Debian Bug report #1068634, regarding libdialog-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libdialog.a to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1068634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdialog-dev Version: 1.3-20240307-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + dialog libdialog-dev has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/libdialog.a is contained in the packages * dialog * 1.3-20201126-1 as present in bullseye * 1.3-20230209-1 as present in bookworm * 1.3-20240101-1 as present in trixie * libdialog-dev/1.3-20240307-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: dialog Source-Version: 1.3-20240307-2 Done: Santiago Vila We believe that the bug you reported is fixed in the latest version of dialog, 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. Santiago Vila (supplier of updated dialog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Apr 2024 12:40:00 +0200 Source: dialog Architecture: source Version: 1.3-20240307-2 Distribution: unstable Urgency: medium Maintainer: Santiago Vila Changed-By: Santiago Vila Closes: 1068634 Changes: dialog (1.3-20240307-2) unstable; urgency=medium . * Fix Breaks and Replaces fields. Closes: #1068634. Thanks to Helmut Grohne for the report. Checksums-Sha1: d5cdcb6cfa89a677b5435dc0f841cd6b6e1f8ff7 1839 dialog_1.3-20240307-2.dsc 089ef9a5ca6ade21954ee31697727b8b45115b21 16272 dialog_1.3-20240307-2.debian.tar.xz 74350ced7d85afe417c07824348242ac8e3dac6e 5382 dialog_1.3-20240307-2_source.buildinfo Checksums-Sha256: 99ff11eb3077b66cb110440a6b754304850c93e944ce212aaff9171c91d350e5 1839 dialog_1.3-20240307-2.dsc ff27fb75c10e8076a13f493c41bf75b91fb488061122c05960fe9930859208a5 16272 dialog_1.3-20240307-2.debian.tar.xz a73d13fe04b287341903a16591877180f72c01eaaeb208e8b7609b27207df820 5382 dialog_1.3-20240307-2_source.buildinfo Files: 16eb3151d7d2de75132e65514ac498a1 1839 misc optional dialog_1.3-20240307-2.dsc 75a9b0e0dc26b4297e00156247bb09ed 16272 misc optional dialog_1.3-20240307-2.debian.tar.xz df431b3b7ff57c94ca1d01389bdf3d7d 5382 misc optional dialog_1.3-20240307-2_source.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmYTycMACgkQQc5/C58b izLZlgf/dzwgB0H+9OMo5pWKylfkOXw1B5qJU6eQ6fGKmKx/qcG6OwwstCrCVqAo ccTJNSeOjzd++n6fcwLkUIz4LOwxbL5LFxLa3MpuhFnKSJMROeN6PtVEk5swqWqB be5/goNeBzq/NS1KFjUzjaYgNeZ9/e6SVl+QvZt+v7E9mnL09zXQeXWo7shZNqgh 8YuR0S+juhiz07WBhgRAjig3krJoOqVS6Z1VboxwqDXnlCH8ezUUh/mqAY/8QBQl 8rEG3sx6eO9X8Be9YcH+gyKpF9C7GMsVcDsn7CYIahps+vSoZZ89Vp527FF6Ftez yf4ZlpwfFO3hl4Ns/O0llEDiKZbj3w== =bZm2 -END PGP SIGNATURE- pgpIPpq4Nc5Tm.pgp Description: PGP signature --- End Message ---
Bug#1068634: libdialog-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libdialog.a
Just for the record: I finally used this, in line with the original proposal: Replaces: dialog (<< 1.3-20240307-1~) Breaks: dialog (<< 1.3-20240307-1~) Thanks.
Bug#1066657: marked as done (daemonize: FTBFS: daemonize.c:118:12: error: implicit declaration of function ‘basename’; did you mean ‘rename’? [-Werror=implicit-function-declaration])
Your message dated Mon, 08 Apr 2024 10:49:37 + with message-id and subject line Bug#1066657: fixed in daemonize 1.7.8-4 has caused the Debian Bug report #1066657, regarding daemonize: FTBFS: daemonize.c:118:12: error: implicit declaration of function ‘basename’; did you mean ‘rename’? [-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.) -- 1066657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: daemonize Version: 1.7.8-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): > gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -D_FORTIFY_SOURCE=2 -O1 -c getopt.c -I. -I. > daemonize.c: In function ‘usage’: > daemonize.c:118:12: error: implicit declaration of function ‘basename’; did > you mean ‘rename’? [-Werror=implicit-function-declaration] > 118 | prog = basename(prog); > |^~~~ > |rename > daemonize.c:118:10: warning: assignment to ‘char *’ from ‘int’ makes pointer > from integer without a cast [-Wint-conversion] > 118 | prog = basename(prog); > | ^ > cc1: some warnings being treated as errors > make[1]: *** [Makefile:22: daemonize.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/daemonize_1.7.8-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: daemonize Source-Version: 1.7.8-4 Done: SZ Lin (林上智) We believe that the bug you reported is fixed in the latest version of daemonize, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. SZ Lin (林上智) (supplier of updated daemonize package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Apr 2024 18:13:55 +0800 Source: daemonize Architecture: source Version: 1.7.8-4 Distribution: unstable Urgency: medium Maintainer: SZ Lin (林上智) Changed-By: SZ Lin (林上智) Closes: 1066657 Changes: daemonize (1.7.8-4) unstable; urgency=medium . * Fix FTBFS issue by including the required library (Closes: #1066657) * d/control: - Bump Standards-Version to 4.7.0.0 Checksums-Sha1: 910333d0660d484b5af416256d8dc2a2b439c580 1840 daemonize_1.7.8-4.dsc af3b10c718c7ce4ba727eeb81d0cad6cfa46b74e 8564 daemonize_1.7.8-4.debian.tar.xz 5b91a63e0e1687900afeeb66b998804e79094d88 6564 daemonize_1.7.8-4_amd64.buildinfo Checksums-Sha256: 8454e74fdf5dce589411042fd6c795ecc0707ff4a1d29fd728b136004556bf74 1840 daemonize_1.7.8-4.dsc 28abf2d59a7d3bf5955ada6faaeca31b12e1c4ab2ead6d23d7b5eaff4cf876a0 8564 daemonize_1.7.8-4.debian.tar.xz cc1af4e2bd046d124703f8f12352e6e20e2d266acde38efb6ccb75d2c69e9ec0 6564 daemonize_1.7.8-4_amd64.buildinfo Files: 6da291f7a6992ef698bcd2bb9c368a55 1840 admin optional daemonize_1.7.8-4.dsc 775a5aa1fa4f6d3b8736159e067d27f5 8564
Bug#1068089: marked as done (FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’})
Your message dated Mon, 08 Apr 2024 10:35:31 +
with message-id
and subject line Bug#1068089: fixed in ukui-control-center 3.22.1.26-1
has caused the Debian Bug report #1068089,
regarding FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka
‘const long long int*’}
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.)
--
1068089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: ukui-control-center
Source-Version: 3.22.1.26-1
Done: handsome_feng
We believe that the bug you reported is fixed in the latest version of
ukui-control-center, 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.
handsome_feng (supplier of updated
ukui-control-center package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Apr 2024 18:10:12 +0800
Source: ukui-control-center
Architecture: source
Version: 3.22.1.26-1
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team
Changed-By: handsome_feng
Closes: 1068089
Changes:
ukui-control-center (3.22.1.26-1) unstable; urgency=medium
.
* New upstream bugfix release.
[ Michael Hudson-Doyle ]
- Fix build where time_t != long. (Closes: #1068089)
.
[ handsome_feng ]
- Fix crash when select theme module from ukui-control-center.
- Delete an interface with potential security risks.
- Fix the wrong version num and wrong background color.
Checksums-Sha1:
9a28ff1e82ad4aaf226fd8e8c7abdf8220433c35 2851
ukui-control-center_3.22.1.26-1.dsc
5d803ebd7857e67af11bc0b7d40176c55f2eaabc 25831784
ukui-control-center_3.22.1.26.orig.tar.gz
24a215d74a3c69907fbe9c77d4ea32afe9a788c4 5632
ukui-control-center_3.22.1.26-1.debian.tar.xz
bc4ed869911b06dce0f789fbe06e92362b77afae 26115
ukui-control-center_3.22.1.26-1_source.buildinfo
Checksums-Sha256:
bc0d8e5157c519dd91dc7701e93369cc88ad8385f79675a094aa66a77cb6685b
Bug#1067067: marked as done (ruby-rdiscount: FTBFS: rdiscount.c:50:17: error: implicit declaration of function ‘rb_rdiscount__get_flags’ [-Werror=implicit-function-declaration])
Your message dated Mon, 08 Apr 2024 10:35:04 + with message-id and subject line Bug#1067067: fixed in ruby-rdiscount 2.1.8-3 has caused the Debian Bug report #1067067, regarding ruby-rdiscount: FTBFS: rdiscount.c:50:17: error: implicit declaration of function ‘rb_rdiscount__get_flags’ [-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.) -- 1067067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rdiscount Version: 2.1.8-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=ruby-rdiscount=amd64=2.1.8-2%2Bb3=1710698993=0 gcc -fdebug-prefix-map=/<>=. -I. -I/usr/include/x86_64-linux-gnu/ruby-3.1.0 -I/usr/include/ruby-3.1.0/ruby/backward -I/usr/include/ruby-3.1.0 -I. -DHAVE_RANDOM -DHAVE_SRANDOM -DHAVE_RAND -DHAVE_SRAND -DSIZEOF_UNSIGNED_LONG=8 -DSIZEOF_UNSIGNED_INT=4 -DSIZEOF_UNSIGNED_INT=4 -DVERSION=\"2.1.8\" -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=BUILDDIR=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -o rdiscount.o -c rdiscount.c rdiscount.c: In function ‘rb_rdiscount_to_html’: rdiscount.c:50:17: error: implicit declaration of function ‘rb_rdiscount__get_flags’ [-Werror=implicit-function-declaration] 50 | int flags = rb_rdiscount__get_flags(self); | ^~~ cc1: some warnings being treated as errors make[1]: *** [Makefile:246: rdiscount.o] Error 1 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: ruby-rdiscount Source-Version: 2.1.8-3 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-rdiscount, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-rdiscount package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Apr 2024 11:46:43 +0200 Source: ruby-rdiscount Architecture: source Version: 2.1.8-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 1048229 1067067 Changes: ruby-rdiscount (2.1.8-3) unstable; urgency=medium . * Declare explicitly rb_rdiscount__get_flags (Closes: #1067067) * clean ext/ruby-config.h to build twice in a row (Closes: #1048229) * Move debian/watch to gemwatch.debian.net * X?-Ruby-Versions: fields from debian/control * Rules-Requires-Root set to no * Bump Standards-Version to 4.6.2 (no changes needed) * Drop dependency on ruby-interpreter * Add myself to uploaders * Update year in copyright file Checksums-Sha1: 93380b8fa0c553cd6c1e0e0c3fd192c90a9b1a60 1456 ruby-rdiscount_2.1.8-3.dsc b73a8b4df2d7e658d19be90af838b4277451b1ef 63216 ruby-rdiscount_2.1.8.orig.tar.gz 9cbc8d1ac63fac5a65a97721622914f8bd333208 3928 ruby-rdiscount_2.1.8-3.debian.tar.xz 842ae7bae8411acacf2cd2445fbcde8c2a3bfb0d 9032 ruby-rdiscount_2.1.8-3_amd64.buildinfo Checksums-Sha256: 43cae82e96acea75a3d8f2e8d5d2df5aa1e97ddb97e205f0c9e1a8f234132fb9 1456 ruby-rdiscount_2.1.8-3.dsc e10a83a37a3ac44aefaa8763ae06bc419f76748d75008f580a91f41cd1761d0b 63216 ruby-rdiscount_2.1.8.orig.tar.gz a8ac1b33d3c41a56b38f07d28717fb38e13269123dc8fbf3d3a01e2d8b19d28f 3928 ruby-rdiscount_2.1.8-3.debian.tar.xz 311031e5191e6dba1bbf8e58f1eaa441bf8b67e591880a554fdab55754b57df2 9032 ruby-rdiscount_2.1.8-3_amd64.buildinfo Files: ac0c2e4951e3ca7e3a167bc4d63a2f84 1456 ruby optional ruby-rdiscount_2.1.8-3.dsc f74feadd3378d6441f91c693357f2727 63216 ruby optional ruby-rdiscount_2.1.8.orig.tar.gz d8178bd51ca100a15de6457d5f992044 3928 ruby optional ruby-rdiscount_2.1.8-3.debian.tar.xz 27bd20f31ab24d414fc00f436cc7004c 9032 ruby optional ruby-rdiscount_2.1.8-3_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1068637: apt does not always install Recommends
Control: severity -1 wishlist On Mon, Apr 08, 2024 at 11:50:04AM +0200, Vincent Lefevre wrote: > Package: apt > Version: 2.7.14 > Severity: serious > > The lvm2 package is installed, but not thin-provisioning-tools, > though lvm2 recommends it. This can yield a broken system: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857142 > > the fix of this bug being > >* Make lvm2 recommend thin-provisioning-tools. (closes: #857142) That's a packaging bug. If the tool is mandatory for correct behavior of the system it should be a Depends. Now back to the topic, this is not a release critical bug in APT. APT installs any Recommends with easily satisfiable dependencies. Recommends will get broken easily if there's large scale dependency issues like now. This works out well if you Recommend an Architecture: all package and it Depends on packages that are not available on all architectures - it is just being skipped on those. In this particular instance you're getting bit by time_t transition issues and Recommends disappear on you (even if they may be satisfiable it may simply be easier to break the Recommends for apt than to figure out the right solution). However I do agree with you and I've already set this a couple of times before that I want to move away from treating Recommends as optional dependencies that we want to satisfy as many of as we can. My proposal is quite simple: Recommends that point to an existing real package are promoted to Depends, except that you may remove them by explicit action (remove them after install, mark them for removal before installing, or if it is unsatisfied in the installed package it remains unsatisfied). This applies to the entire or group. If you Recommends: real | virtual, the recommends may also be satisfied by the virtual package. I do not know what the behavior should be for Recommends exclusively n virtual packages, I feel like promoting them could have unforeseen issues, people think less about them than real packages. Ultimately this may be a bit challenging to implement but I didn't actually get around to looking at it yet, and it certainly will take some time to sort out the uninstallabilities this introduces in the archive especially on niche architectures where Architecture: all packages are Recommended but not installable. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Processed: Re: Bug#1068637: apt does not always install Recommends
Processing control commands: > severity -1 wishlist Bug #1068637 [apt] apt does not always install Recommends Severity set to 'wishlist' from 'serious' -- 1068637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068634: libdialog-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libdialog.a
Ok. This is a little bit subtle. I naively tried to simplify the fields by using this: Replaces: dialog (<< 1.3-20240307) Breaks: dialog (<< 1.3-20240307) But this actually means upstream version 1.3, debian revision 20240307, not upstream 1.3-20240307. I guess I should use 1.3-20240307-0 at minimum. Thanks.
Bug#1067067: marked as pending in ruby-rdiscount
Control: tag -1 pending Hello, Bug #1067067 in ruby-rdiscount 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/ruby-team/ruby-rdiscount/-/commit/9466581097edb1691b75ca53a31a6bc3346da751 Declare explicitly rb_rdiscount__get_flags (Closes: #1067067) (this message was generated automatically) -- Greetings https://bugs.debian.org/1067067
Processed: Bug#1067067 marked as pending in ruby-rdiscount
Processing control commands: > tag -1 pending Bug #1067067 [src:ruby-rdiscount] ruby-rdiscount: FTBFS: rdiscount.c:50:17: error: implicit declaration of function ‘rb_rdiscount__get_flags’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1067067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059839: marked as done (cython-legacy: autopkgtest regression with Python 3.12 on 32-bit)
Your message dated Mon, 08 Apr 2024 09:50:14 + with message-id and subject line Bug#1059839: fixed in cython-legacy 0.29.37-2 has caused the Debian Bug report #1059839, regarding cython-legacy: autopkgtest regression with Python 3.12 on 32-bit 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.) -- 1059839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cython-legacy Version: 0.29.36-3 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer cython-legacy's autopkgtests fail with Python 3.12 on 32-bit architectures [1][2][3]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/c/cython-legacy/testing/armel/ [2] https://ci.debian.net/packages/c/cython-legacy/testing/armhf/ [3] https://ci.debian.net/packages/c/cython-legacy/testing/i386/ 3519s == 3519s FAIL: test_raiseMemError (test_unicode.UnicodeTest.test_raiseMemError) 3519s -- 3519s Traceback (most recent call last): 3519s File "tests/run/test_unicode.pyx", line 2356, in test_unicode.UnicodeTest.test_raiseMemError (test_unicode.c:138318) 3519s self.assertRaises(MemoryError, alloc) 3519s AssertionError: MemoryError not raised by lambda 3519s 3519s == 3519s FAIL: test_raiseMemError (test_unicode.UnicodeTest.test_raiseMemError) 3519s -- 3519s Traceback (most recent call last): 3519s File "tests/run/test_unicode.pyx", line 2356, in test_unicode.UnicodeTest.test_raiseMemError (test_unicode.cpp:138332) 3519s self.assertRaises(MemoryError, alloc) 3519s AssertionError: MemoryError not raised by lambda 3519s 3519s -- 3519s Ran 5423 tests in 3411.871s 3519s 3519s FAILED (failures=2, skipped=48) --- End Message --- --- Begin Message --- Source: cython-legacy Source-Version: 0.29.37-2 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of cython-legacy, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated cython-legacy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Apr 2024 09:22:30 + Source: cython-legacy Built-For-Profiles: noudeb Architecture: source Version: 0.29.37-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Graham Inggs Closes: 1059839 Changes: cython-legacy (0.29.37-2) unstable; urgency=medium . * Remove usages of deprecated numpy.distutils * Disable unicode test_raiseMemError (Closes: #1059839) Checksums-Sha1: b69ce774cb1e2347de74e731254ad61328097c4a 2362 cython-legacy_0.29.37-2.dsc b28e4c121322a02d91156d68f0444a851b439251 28712 cython-legacy_0.29.37-2.debian.tar.xz Checksums-Sha256: 4a0607948652e031fa88f320fe133301e17a25fcc5d19f99d5084a32709631d9 2362 cython-legacy_0.29.37-2.dsc 56669493f598d442e898b393ab56a3c20712b2725e88c18411af74b23f460b33 28712 cython-legacy_0.29.37-2.debian.tar.xz Files: d92c33216acb927da3b52c12abddc025 2362 python optional cython-legacy_0.29.37-2.dsc 31599c298a36d3ee67768fcde5c4cba5 28712 python optional cython-legacy_0.29.37-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmYTt+AACgkQr8/sjmac 4cKNcxAArojWXWOS6pldJozrPEWGevJRRZwOwh+JPGlcsUWqTG9urMl6ebwLNyRT 4vN57TlmfbYmoZMNr9luzGpnQBXcLqIHBYcp+4VioHBqoFK96M2HoBfFXlE1sB/8 45RVQddQNqsGGMIlyoxkPTbb4EjHcl2k4RlnuQr3BknWfoeeZlulB3nBGJDJreIZ 6qCX6xijsrOaVqb5YSVwob+leZx/4kfFVMDxKiHCALGsoQvi26FxHQdVpslOuz9I pCvK7LwlLwJ5WI98GjV6Edau22811F4v5UshxYBnK0qdxPGEh4GUde8vRaSwkpYB m/kpYcjnN9Bb0RgeMTI+6a36KaxcsVdn9xgkTCrnrrEBtpUQ0CGLWgGykkmq/VpM wCKKtBQv9kttpFNTuLh53q0tFzKkl/CMa94Mc/da6jesOh4Nk32VJcr6qUOkEqjV
Bug#1068634: libdialog-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libdialog.a
El 8/4/24 a las 9:18, Helmut Grohne escribió: Package: libdialog-dev Version: 1.3-20240307-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + dialog libdialog-dev has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/libdialog.a is contained in the packages * dialog * 1.3-20201126-1 as present in bullseye * 1.3-20230209-1 as present in bookworm * 1.3-20240101-1 as present in trixie * libdialog-dev/1.3-20240307-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Thanks for the report. libdialog-dev has: Replaces: dialog (<< 1.3-20240307) Breaks: dialog (<< 1.3-20240307) Is this really not enough? Is Policy up to date regarding this? (Cc: Sven, who was helping with the package split). Thanks.
Bug#1068637: apt does not always install Recommends
Package: apt Version: 2.7.14 Severity: serious The lvm2 package is installed, but not thin-provisioning-tools, though lvm2 recommends it. This can yield a broken system: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857142 the fix of this bug being * Make lvm2 recommend thin-provisioning-tools. (closes: #857142) -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Key ""; APT::Key::Assert-Pubkey-Algo ">=rsa2048,ed25519,ed448"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "tasks"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Update ""; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 0 ; apt-show-versions -i"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "0"; APT::Compressor::zstd ""; APT::Compressor::zstd::Name "zstd"; APT::Compressor::zstd::Extension ".zst"; APT::Compressor::zstd::Binary "zstd"; APT::Compressor::zstd::Cost "60"; APT::Compressor::zstd::CompressArg ""; APT::Compressor::zstd::CompressArg:: "-19"; APT::Compressor::zstd::UncompressArg ""; APT::Compressor::zstd::UncompressArg:: "-d"; APT::Compressor::lz4 ""; APT::Compressor::lz4::Name "lz4"; APT::Compressor::lz4::Extension ".lz4"; APT::Compressor::lz4::Binary "false"; APT::Compressor::lz4::Cost "50"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "100"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-6n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "200"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "300"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-6"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::lzma ""; APT::Compressor::lzma::Name "lzma"; APT::Compressor::lzma::Extension ".lzma"; APT::Compressor::lzma::Binary "xz"; APT::Compressor::lzma::Cost "400"; APT::Compressor::lzma::CompressArg ""; APT::Compressor::lzma::CompressArg:: "--format=lzma"; APT::Compressor::lzma::CompressArg:: "-6"; APT::Compressor::lzma::UncompressArg ""; APT::Compressor::lzma::UncompressArg:: "--format=lzma"; APT::Compressor::lzma::UncompressArg:: "-d"; Dir "/"; Dir::State "var/lib/apt"; Dir::State::lists "lists/"; Dir::State::cdroms "cdroms.list"; Dir::State::extended_states "extended_states"; Dir::State::status "/var/lib/dpkg/status"; Dir::Cache "var/cache/apt"; Dir::Cache::archives "archives/"; Dir::Cache::srcpkgcache "srcpkgcache.bin"; Dir::Cache::pkgcache "pkgcache.bin"; Dir::Etc "etc/apt"; Dir::Etc::sourcelist "sources.list"; Dir::Etc::sourceparts "sources.list.d"; Dir::Etc::main "apt.conf"; Dir::Etc::netrc "auth.conf"; Dir::Etc::netrcparts "auth.conf.d"; Dir::Etc::parts "apt.conf.d"; Dir::Etc::preferences "preferences"; Dir::Etc::preferencesparts "preferences.d"; Dir::Etc::trusted "trusted.gpg"; Dir::Etc::trustedparts "trusted.gpg.d"; Dir::Etc::apt-listchanges-main "listchanges.conf"; Dir::Etc::apt-listchanges-parts "listchanges.conf.d"; Dir::Etc::apt-file-main "apt-file.conf"; Dir::Bin ""; Dir::Bin::methods "/usr/lib/apt/methods"; Dir::Bin::solvers ""; Dir::Bin::solvers:: "/usr/lib/apt/solvers"; Dir::Bin::planners ""; Dir::Bin::planners:: "/usr/lib/apt/planners"; Dir::Bin::dpkg "/usr/bin/dpkg"; Dir::Bin::gzip "/bin/gzip"; Dir::Bin::bzip2 "/bin/bzip2"; Dir::Bin::xz "/usr/bin/xz"; Dir::Bin::lz4 "/usr/bin/lz4"; Dir::Bin::zstd "/usr/bin/zstd"; Dir::Bin::lzma "/usr/bin/xz";
Processed: Re: Bug#1068610: dico: binary-all FTBFS
Processing control commands: > tags -1 + patch Bug #1068610 [src:dico] dico: binary-all FTBFS Added tag(s) patch. -- 1068610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068610: dico: binary-all FTBFS
Control: tags -1 + patch Hi Adrian, On Mon, Apr 08, 2024 at 02:03:01AM +0300, Adrian Bunk wrote: > Source: dico > Version: 2.11-4 > Severity: serious > Tags: ftbfs > X-Debbugs-Cc: Helmut Grohne Thank you for notifying me. Mea culpa. Patch attached. > https://buildd.debian.org/status/logs.php?pkg=dico=all > > ... >debian/rules execute_after_dh_installsystemd > make[1]: Entering directory '/<>' > ln -s dicod.service debian/dicod/`test -e > debian/dicod/lib/systemd/system/dicod.service || echo > usr/`lib/systemd/system/dictd.service > ln: failed to create symbolic link > 'debian/dicod/usr/lib/systemd/system/dictd.service': No such file or directory > make[1]: *** [debian/rules:52: execute_after_dh_installsystemd] Error 1 Helmut diff --minimal -Nru dico-2.11/debian/changelog dico-2.11/debian/changelog --- dico-2.11/debian/changelog 2024-03-01 12:57:59.0 +0100 +++ dico-2.11/debian/changelog 2024-04-08 09:21:47.0 +0200 @@ -1,3 +1,10 @@ +dico (2.11-4.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix indep-only FTBFS arising from #1054187. (Closes: #1068610) + + -- Helmut Grohne Mon, 08 Apr 2024 09:21:47 +0200 + dico (2.11-4.1) unstable; urgency=medium * Non-maintainer upload. diff --minimal -Nru dico-2.11/debian/rules dico-2.11/debian/rules --- dico-2.11/debian/rules 2023-11-20 17:26:32.0 +0100 +++ dico-2.11/debian/rules 2024-04-08 09:21:31.0 +0200 @@ -48,5 +48,5 @@ mkdir -p $(TEST_HOME) HOME=$(TEST_HOME) dh_auto_test || cat dicod/tests/testsuite.log -execute_after_dh_installsystemd: +execute_after_dh_installsystemd-arch: ln -s dicod.service debian/dicod/`test -e debian/dicod/lib/systemd/system/dicod.service || echo usr/`lib/systemd/system/dictd.service
Bug#1068634: libdialog-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libdialog.a
Package: libdialog-dev Version: 1.3-20240307-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + dialog libdialog-dev has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/libdialog.a is contained in the packages * dialog * 1.3-20201126-1 as present in bullseye * 1.3-20230209-1 as present in bookworm * 1.3-20240101-1 as present in trixie * libdialog-dev/1.3-20240307-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
Processed: libdialog-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libdialog.a
Processing control commands: > affects -1 + dialog Bug #1068634 [libdialog-dev] libdialog-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libdialog.a Added indication that 1068634 affects dialog -- 1068634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068045: [Pkg-openssl-devel] Bug#1068045: Bug#1068045: libssl3: breaks YAPET
There might be a related change that doesn't allow restarting the operation with the same context without setting things up again.
Bug#1041435: marked as done (bitsnpicas: Contains potentially non-free binary unicode data)
Your message dated Mon, 08 Apr 2024 11:05:36 +0200 with message-id and subject line bitsnpicas: Contains potentially non-free binary unicode data has caused the Debian Bug report #1041435, regarding bitsnpicas: Contains potentially non-free binary unicode data 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.) -- 1041435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bitsnpicas Version: 2.0+ds-1 Severity: serious X-Debbugs-Cc: t...@debian.org Dear Maintainer, bitsnpicas is currently unusable and chokes with: $ bitsnpicas Exception in thread "main" java.lang.NullPointerException at java.base/java.io.Reader.(Reader.java:168) at java.base/java.io.InputStreamReader.(InputStreamReader.java:76) at java.base/java.util.Scanner.(Scanner.java:566) at com.kreative.unicode.data.Encoding.(Encoding.java:26) at com.kreative.unicode.data.EncodingList.(EncodingList.java:58) at com.kreative.unicode.data.EncodingList.instance(EncodingList.java:20) at com.kreative.bitsnpicas.edit.GlyphListModelList$GlyphListModelRootNode.(GlyphListModelList.java:93) at com.kreative.bitsnpicas.edit.GlyphListModelList.(GlyphListModelList.java:29) at com.kreative.bitsnpicas.edit.GlyphListPanel.(GlyphListPanel.java:34) at com.kreative.bitsnpicas.edit.BitmapListFrame.(BitmapListFrame.java:19) at com.kreative.bitsnpicas.edit.Main.openFont(Main.java:158) at com.kreative.bitsnpicas.edit.Main.newBitmapFont(Main.java:71) at com.kreative.bitsnpicas.edit.Main.main(Main.java:55) at com.kreative.bitsnpicas.main.Main.main(Main.java:12) This is because of the exclusion of following files w/o patching the code properly main/java/BitsNPicas/src/com/kreative/unicode/mappings/Mac*.txt main/java/BitsNPicas/src/com/kreative/unicode/mappings/Windows*.txt main/java/BitsNPicas/src/com/kreative/unicode/mappings/IBM*.txt I applied a patch trying to exclude unicodes and can get it to a usable state. The patch is attached with this bug report. However, even after being able to launch the menu, I see windows and IBM related unicode options in the menu. I did not dive deep into the code, but it could be stemming from main/java/BitsNPicas/src/com/kreative/unicode/data/unidata.ucd In which case the unicode bin itself contains non-free content and needs fixing accordingly. Thanks, Nilesh -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_IN, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bitsnpicas depends on: ii xdg-utils 1.1.3-4.1 bitsnpicas recommends no packages. bitsnpicas suggests no packages. -- no debconf information diff --git a/main/java/BitsNPicas/Makefile b/main/java/BitsNPicas/Makefile index d339248..3955afc 100644 --- a/main/java/BitsNPicas/Makefile +++ b/main/java/BitsNPicas/Makefile @@ -48,47 +48,16 @@ BitsNPicas.jar: bin jar cmf dep/MANIFEST.MF BitsNPicas.jar -C bin com/kreative/unicode -C bin com/kreative/bitsnpicas chmod +x BitsNPicas.jar -BitsNPicas.app: BitsNPicas-Pre10.15.app BitsNPicas-MacOS10.15.app BitsNPicas-MacOS11.0.app +BitsNPicas.app: BitsNPicas-Pre10.15.app BitsNPicas-Pre10.15.app: dep BitsNPicas.jar - mkdir -p BitsNPicas-Pre10.15.app/Contents/MacOS mkdir -p BitsNPicas-Pre10.15.app/Contents/Resources/Java cp -f dep/PkgInfo BitsNPicas-Pre10.15.app/Contents cp -f dep/Info.plist BitsNPicas-Pre10.15.app/Contents - cp -f dep/universalJavaApplicationStub-Pre10.15 BitsNPicas-Pre10.15.app/Contents/MacOS/BitsNPicas cp -f dep/kbnp*.icns dep/dmov*.icns dep/movr*.icns BitsNPicas-Pre10.15.app/Contents/Resources cp -f dep/*.jar BitsNPicas-Pre10.15.app/Contents/Resources/Java cp -f BitsNPicas.jar BitsNPicas-Pre10.15.app/Contents/Resources/Java -BitsNPicas-MacOS10.15.app: dep BitsNPicas.jar - mkdir -p BitsNPicas-MacOS10.15.app/Contents/MacOS - mkdir -p BitsNPicas-MacOS10.15.app/Contents/Resources/Java - cp -f dep/PkgInfo BitsNPicas-MacOS10.15.app/Contents - cp -f dep/Info.plist BitsNPicas-MacOS10.15.app/Contents - cp -f dep/universalJavaApplicationStub-MacOS10.15 BitsNPicas-MacOS10.15.app/Contents/MacOS/BitsNPicas - cp -f dep/kbnp*.icns dep/dmov*.icns dep/movr*.icns
Processed: tagging 1066628
Processing commands for cont...@bugs.debian.org:
> tags 1066628 - trixie
Bug #1066628 {Done: tony mancill } [src:tlf] tlf: FTBFS:
test_wwv.c:26:5: error: implicit declaration of function ‘g_strchomp’; did you
mean ‘strcmp’? [-Werror=implicit-function-declaration]
Removed tag(s) trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1066628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042262: cumin: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13
Pyparsing upstream finally made the v3.1.2 release the other day with the fix. So I guess once that lands in unstable it should be ok. On Sat, Apr 6, 2024 at 12:30 AM Antoine Beaupré wrote: > On 2023-07-27 13:04:22, Riccardo Coccioli wrote: > > I've checked the issue and opened a bug upstream to pyparsing [1] as this > > is indeed a regression. > > Running CI on cumin I've also found that pylint is reporting new issues > > related to pyparsing code, for which I've opened a separate bug upstream > > [2]. > > > > [1] https://github.com/pyparsing/pyparsing/issues/502 > > [2] https://github.com/pyparsing/pyparsing/issues/501 > > Hi! > > Thanks for this! It looks like those are fixed upstream, do we need to > update pyparsing to 3.1.2 to fix this bug or what's the next step? > > (upstream 502 is fixed in 3.1.1, in unstable, but 501 is only in > 3.1.2...) > > a. > > -- > Sous le projecteur, on ne voit pas les autres. > - Félix Leclerc >
Processed: severity of 1066501 is important
Processing commands for cont...@bugs.debian.org:
> severity 1066501 important
Bug #1066501 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:pd-wiimote] pd-wiimote: FTBFS: wiimote.c:736:7: error: implicit
declaration of function ‘error’; did you mean ‘perror’?
[-Werror=implicit-function-declaration]
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1066501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067916: FTBFS: tests failed
On Mon, Apr 08, 2024 at 12:58:13AM +, tony mancill wrote: > This may be a naive question, but since we're dealing with a syscall > that passes a timespec, is there a minimum kernel version required for > the time_t 64 userspace? I've never heard anything about this. > In any event, I'm not sure about the next steps here. Any suggestions? > Should I work with DSA to try to get a porter box with a newer kernel to > confirm that that resolves the issue with the test? (I think this would > have eventual implications for the buildds.) I would ask in a more public place (as I'm not sure there is a dedicated t64 place which the t64 experts read). Also you can try making a qemu VM and try different kernels there. -- WBR, wRAR signature.asc Description: PGP signature
Processed: closing 1063982
Processing commands for cont...@bugs.debian.org: > close 1063982 Bug #1063982 [setuptools-scm] setuptools-scm: autopkgtest regression with pytest 8 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1063982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068449: marked as done (opentracker: libowfat headers have moved)
Your message dated Mon, 08 Apr 2024 07:06:40 + with message-id and subject line Bug#1068449: fixed in opentracker 0.0~git20210823.110868e-9 has caused the Debian Bug report #1068449, regarding opentracker: libowfat headers have moved 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.) -- 1068449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opentracker Version: 0.0~git20210823.110868e-8 Severity: important The package will start to FTBFS when the fix for #932313 arrives. The headers hove to a new place, so opentracker needs to be modified. The debdiff is included. opentracker_0.0~git20210823.110868e-8.1.debdiff Description: Binary data --- End Message --- --- Begin Message --- Source: opentracker Source-Version: 0.0~git20210823.110868e-9 Done: Agathe Porte We believe that the bug you reported is fixed in the latest version of opentracker, 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. Agathe Porte (supplier of updated opentracker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Apr 2024 08:43:42 +0200 Source: opentracker Architecture: source Version: 0.0~git20210823.110868e-9 Distribution: unstable Urgency: medium Maintainer: Agathe Porte Changed-By: Agathe Porte Closes: 1068449 Changes: opentracker (0.0~git20210823.110868e-9) unstable; urgency=medium . [ Agathe Porte ] * Update copyright year . [ Bastian Germann ] * Hand over changed LIBOWFAT_HEADERS (Closes: #1068449) Checksums-Sha1: 11eff474b6bb9f741b50304d9c3f0564b027df9e 2229 opentracker_0.0~git20210823.110868e-9.dsc 84910796a9b34f5ff05e68dee737004f1df0562f 7448 opentracker_0.0~git20210823.110868e-9.debian.tar.xz e19fbb2de888a188fc8dde1e632a0a19ea51d700 6585 opentracker_0.0~git20210823.110868e-9_source.buildinfo Checksums-Sha256: f10603e4016e2bab321c00a103e3cbb2523feff429a2fb94ee3062f642a7daeb 2229 opentracker_0.0~git20210823.110868e-9.dsc 55eeb6bef0c7633fd474ee55feecec526902d4bd868c6b54e8e2962dcd17b7e0 7448 opentracker_0.0~git20210823.110868e-9.debian.tar.xz a779b2cc0fc863b24e6628532e6161d170aeb0c69d2de5013cc7d07ed7593052 6585 opentracker_0.0~git20210823.110868e-9_source.buildinfo Files: a09b428c8d97512d49695068b8a027ff 2229 net optional opentracker_0.0~git20210823.110868e-9.dsc 5317fe83b6bf6715e10e1425528f 7448 net optional opentracker_0.0~git20210823.110868e-9.debian.tar.xz f2b0d53bcf33d2cd7d5b2f9c21f58466 6585 net optional opentracker_0.0~git20210823.110868e-9_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEE2xMJtrCqCOwoob8cBjaerR0+AQUFAmYTkkkSHGdhZ2F0aEBk ZWJpYW4ub3JnAAoJEAY2nq0dPgEFeJ4P/2CvqBGGhAwuJzEO0QhYF3mgjE0DTcbt UA/VMvT1a87gPzLUn6JAobWrXxLWZeovqq1q0GLGGkyb0nefDTBG57246VDC4Brt dMy5uhFvoO3tBhSVBirAm7YnwlpHntvOrTAw9Sp9FdltIhdPi71icS1izAZTAjld foYcfTdx3kRM/RjrhvpLNLqdZA87rkgFvczp+r8brSMNNJQ+vNH2yteY1jMDhr2p sO/GiVjbVRH3qCDg4BLkPExlvYpoTGbpzpS6stEoIWVbSqqpYTsFcgMgwPKOUUHy 10MSrFWzZ073WDZQ9u89+A3OM0MxHYne15kPr3cmla8N54UBxzWld2P9X4f84Cd8 QZkrFb3pkIx1y56rbF99PuQbe2G5bfOu3toN0I91m1ga1RKPbcJdM9XCqUQdzSHa sjDmXNz+jJVABlQGrweGKRpsqgf4SYrYF/nlslaXdpd/KpvnLTV26iSaH8NC4nSv 9OHcrjy/Q9R7UTnJSlEWqOekt9RC6GArG7ok7rU4Edw0PYGmqvC23FAtSAReo6UG jUVxWNN0r3/NZO3wNSWooSB/X1ZZIaWWelmSJy5QxPPf17oG0F2xftXaclX1CyGP fda5cxMo5qrPFOjTlJWsliuXw/9tC/8/wBK7QSkM1LzvkILy+27sINAs1IKMePYD ETxTjSZask+y =G5m4 -END PGP SIGNATURE- pgp6tQHQ4pG72.pgp Description: PGP signature --- End Message ---
Bug#1068613: marked as done (lomiri-history-service FTBFS with abseil 20230802.1)
Your message dated Mon, 08 Apr 2024 07:05:55 + with message-id and subject line Bug#1068613: fixed in lomiri-history-service 0.5-2 has caused the Debian Bug report #1068613, regarding lomiri-history-service FTBFS with abseil 20230802.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1068613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lomiri-history-service Version: 0.5-1 Severity: serious Tags: ftbfs Forwarded: https://gitlab.com/ubports/development/core/history-service/-/merge_requests/35 https://buildd.debian.org/status/fetch.php?pkg=lomiri-history-service=amd64=0.5-1%2Bb2=1712518035=0 ... In file included from /usr/include/absl/base/config.h:86, from /usr/include/absl/algorithm/algorithm.h:29, from /usr/include/absl/algorithm/container.h:53, from /usr/include/absl/container/node_hash_set.h:40, from /usr/include/phonenumbers/phonenumberutil.h:33, from /<>/src/phoneutils.cpp:28: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported." 79 | #error "C++ versions less than C++14 are not supported." | ^ ... --- End Message --- --- Begin Message --- Source: lomiri-history-service Source-Version: 0.5-2 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of lomiri-history-service, 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. Mike Gabriel (supplier of updated lomiri-history-service package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 Apr 2024 08:44:16 +0200 Source: lomiri-history-service Architecture: source Version: 0.5-2 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 1068613 Changes: lomiri-history-service (0.5-2) unstable; urgency=medium . * debian/watch: + Update file for recent GitLab changes of the tags overview page. * debian/patches: + Add 1001_bump-to-c++17.patch. Cherry-picked from upstream MR !35. (Closes: #1068613). * debian/control: + Switch from pkg-config to pkgconf. Thanks, lintian. Checksums-Sha1: efed592113f0638abf6cac62ebc7cfb4bdb49c51 2746 lomiri-history-service_0.5-2.dsc b474ab157678ca7f1b682b71df02aa289515f652 5628 lomiri-history-service_0.5-2.debian.tar.xz e898bf17e3194cc3f108ec9a8dc79774bbe1 16670 lomiri-history-service_0.5-2_source.buildinfo Checksums-Sha256: cbac0848cf64f50c3727bc19d7ae35135000363f6e8b544508e43008a47bf9f7 2746 lomiri-history-service_0.5-2.dsc 2df4e25b4e9a450c57124d0f9b3d9df26f8bd4dbe6814da10f923fee48d04b40 5628 lomiri-history-service_0.5-2.debian.tar.xz cb867c376b252f40550e0119e92cbc015cb4108b668892f958cfb000b2874613 16670 lomiri-history-service_0.5-2_source.buildinfo Files: 86989e943feb968e52060766e8fc4b89 2746 libs optional lomiri-history-service_0.5-2.dsc 954967544dd221e47b8bc088df9e53fd 5628 libs optional lomiri-history-service_0.5-2.debian.tar.xz e8ca3f525269d3a3797938a817d7970d 16670 libs optional lomiri-history-service_0.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmYTky0VHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxaoEQAKp5CHx8iM9jTCciay/9mHiSHED+ yBvJz+2gjjNLpgUmttnCENAz+L2REo+cGcKYrqNOgXP/ZdyfG4VU9XFX6loDtVf7 9zVR7XJ6gmgjFmvksShv8G11RH7CgJK5WiYL4DSBUFls4yjzyjFgP2FkLctwd+Cz 11Cpwa9YR/VBoeV17wDou+qm+mzqO14EKt6Tq14EHg35KcwiH2d7CKvzTBQqvexZ 52BRyQPRE4WZle9YjFwT3nieOdMtsYDugBdcXODQBqbNzKt5vVVYNDoRd//CShZy UEoRmxjmyTjkNGsHP2Na+hcgZ/n4J4HOn3i7Ui+4hXJ/i3rwh6dURCVhHdwPRJBC W1zQwiPs8KL4kuMK60KIwa9xjD+gyqMe6E6E3WGR/kFf5J6ByRsQPKRAQhHUtfuk m4zt3lVw2GuDFahPaL/1PSfkt/GCzmcKEQDATfcutM0/8Yk0JLMvE2ZWe2v4YBZQ bsq/f9Ih3KfJy6FY2wHYwj6ZNBi0pCHirQ8OD38cJnwZfiz/EU0YsLLV4JyqnP26 IzxiMJxvBK+sHetBacBwUfQjdEVNzXH0KiWsjsY/7PudT8eeL7HuaEljxGk6qSG0 6fTu1iuAyR3WiLz60Fmx2aUsuVOvHuKY8SKfttngM854+DWdqS7mrKw5M6j7Xh7Y SbirofR9MFpY81cB =zZL7 -END PGP SIGNATURE- pgpONyPMh2WuI.pgp
Bug#1068430: marked as done (libqt5-ukui-style1 dependencies unsatisfiable on 32-bit non-i386 architectures.)
Your message dated Mon, 08 Apr 2024 06:53:02 + with message-id and subject line Bug#1068430: fixed in qt5-ukui-platformtheme 1.0.8-2 has caused the Debian Bug report #1068430, regarding libqt5-ukui-style1 dependencies unsatisfiable on 32-bit non-i386 architectures. 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.) -- 1068430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libqt5-ukui-style1 Version: 1.0.8-1 Tags: trixie, sid Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, libqt5-ukui-style1 depends on both libqt5widgets5 and libqt5widgets5. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports architectures). Ubuntu appear to have already fixed this. http://launchpadlibrarian.net/721518881/qt5-ukui-platformtheme_1.0.8-1build9_1.0.8-1ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: qt5-ukui-platformtheme Source-Version: 1.0.8-2 Done: handsome_feng We believe that the bug you reported is fixed in the latest version of qt5-ukui-platformtheme, 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. handsome_feng (supplier of updated qt5-ukui-platformtheme package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 Apr 2024 14:05:35 +0800 Source: qt5-ukui-platformtheme Architecture: source Version: 1.0.8-2 Distribution: unstable Urgency: medium Maintainer: Kylin Team Changed-By: handsome_feng Closes: 1068430 Changes: qt5-ukui-platformtheme (1.0.8-2) unstable; urgency=medium . [Steve langasek] * Remove hard-coded dependencies on libqt5widgets5 and libgsettings-qt1. and don't hard-code dependency on shared libglib library. (Closes: #1068430) Checksums-Sha1: c4f558972cda05c0e3c72d05455a3c1a01e382c4 2501 qt5-ukui-platformtheme_1.0.8-2.dsc 0a594e77c8e6f0050c7c8adb787821e4a84cd5e9 133915 qt5-ukui-platformtheme_1.0.8.orig.tar.gz dceb4320ab72385c3a65d566220bc96919ff899d 3160 qt5-ukui-platformtheme_1.0.8-2.debian.tar.xz 3d6930e5ea884e22f232f4178069b01efede80cd 14340 qt5-ukui-platformtheme_1.0.8-2_source.buildinfo Checksums-Sha256: b2ddbfecced3cbacda430faaed5668f9e1e3069e0f2d82123353906081229ee4 2501 qt5-ukui-platformtheme_1.0.8-2.dsc bbc868c81c5785b97aef4fd0eabe8334d89890e8936a1a52986aae913c71a797 133915 qt5-ukui-platformtheme_1.0.8.orig.tar.gz 4086337279a4d40e1d6479aa7cbfa1e6e67792c953dde82fd118e080efc54f36 3160 qt5-ukui-platformtheme_1.0.8-2.debian.tar.xz 064c59bec489498d57ac1bd7a532828b14952f01770e84e798a14e5b504b5d57 14340 qt5-ukui-platformtheme_1.0.8-2_source.buildinfo Files: f12f24a344b01d311b7810f4f2b8be9a 2501 libs optional qt5-ukui-platformtheme_1.0.8-2.dsc eac6cee451fbe1d8c21ad1d80c9c5a09 133915 libs optional qt5-ukui-platformtheme_1.0.8.orig.tar.gz cb6c4966eac4e383aa34ae7cacb8a7ab 3160 libs optional qt5-ukui-platformtheme_1.0.8-2.debian.tar.xz c24d8ccf6989f1ae59a20996131566e0 14340 libs optional qt5-ukui-platformtheme_1.0.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmYTjEwbHGppYW5mZW5n bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8MtCIP/RaKuCc7WV70A0Wzn6ii 7ycEd8w0YK/aGDM3V+O/5MHR8YSw/DVQiZy+2yLML+jCw+QcEi0lU3AWd4PkP+dh sXyIGys0jAS1C1avCoPuDWZybeNxxIpY+q19hFfG9JPAR9kk9qEAfzl0vJveRSsi dpQx4fe7hqp/y5HtfmtgyyIUv/JG8X6AGwbOweZnDjD8aFGGddF8RAs+CPo13+OH y+MRY7m0s2bjLWJMRASk3RdL5/Rsuelc4S/mGKQuKhcEQHePDaU//C4rdu5Sk/PC 4oaH2vWzBlw9ZPcFh3o7D+hYVH7cSTZ/SHq6KOX/F/RM9Mt+0WxxRfCprGED9pja mXkF2DxE4dC2hE/gO/KVGpM1fTyH7h47stxs74sU0+Qh5/jpohsxGIBbU1qNE2Ga Em7Hf/6tPlwR1/2HKhkmBPw/HZRzD1dS909PZ9TExPWsxBokVCpbFb/oxbv3f3wh ZqE37BqGhB/16ZuC4HD8KXe7y8NjKILcyAzZqJhyHfrfmjXY9MujXcLxOVTeCdqh WquXsXrSIbPxhY/l8Ssxs3DOdzoXW7XhZhvbZ0s+UDY5blCHsxCfCtP4FUwsPh71 bP+s2QekXB/7OfgdcJ20GyvuJ/JhMQDGrEyDGSRzCMQdJxbCA4FLez3Sul9xHvZW YA+SBbFrhAAchq6FL9JX4moC =mm5q -END PGP SIGNATURE- pgpoa89VP4W0Y.pgp Description: PGP signature --- End Message ---
Bug#1068613: marked as pending in lomiri-history-service
Control: tag -1 pending Hello, Bug #1068613 in lomiri-history-service 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/ubports-team/lomiri-history-service/-/commit/4b872bffc0b806a06f65bac2eebba8d80ae84179 debian/patches: Add 1001_bump-to-c++17.patch. Cherry-picked from upstream MR !35. (Closes: #1068613). (this message was generated automatically) -- Greetings https://bugs.debian.org/1068613
Processed: Bug#1068613 marked as pending in lomiri-history-service
Processing control commands: > tag -1 pending Bug #1068613 [src:lomiri-history-service] lomiri-history-service FTBFS with abseil 20230802.1 Added tag(s) pending. -- 1068613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068599: marked as done (ruby-xapian - still depends on old libruby3.1 after binnmu)
Your message dated Mon, 08 Apr 2024 06:23:28 + with message-id and subject line Bug#1068599: fixed in xapian-bindings 1.4.22-2 has caused the Debian Bug report #1068599, regarding ruby-xapian - still depends on old libruby3.1 after binnmu 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.) -- 1068599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-xapian Version: 1.4.22-1 Severity: grave Tags: trixie, sid User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, ruby-xapian still depends on libruby3.1 rather than libruby3.1t64. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports architectures). The following lines in the build log look like a likely culprit. # The module(s) are linked against libruby2.x but use none of its # symbols, so there's no dependency generated. That's unhelpful for # users and for transitions (https://bugs.debian.org/816775) so # generate a suitable dependency. # # If RUBY_VERSIONS is 2.1 2.2 2.3, Depends: libruby2.3|libruby2.1 |libruby2.2 echo "ruby:Depends=libruby3.1" \ >> debian/ruby-xapian.substvars --- End Message --- --- Begin Message --- Source: xapian-bindings Source-Version: 1.4.22-2 Done: Olly Betts We believe that the bug you reported is fixed in the latest version of xapian-bindings, 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. Olly Betts (supplier of updated xapian-bindings package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Apr 2024 17:05:15 +1200 Source: xapian-bindings Architecture: source Version: 1.4.22-2 Distribution: unstable Urgency: medium Maintainer: Olly Betts Changed-By: Olly Betts Closes: 1068599 Changes: xapian-bindings (1.4.22-2) unstable; urgency=medium . * debian/control.in: Mark conformance with policy 4.7.0. * debian/rules: Adjust ruby-xapian generated "Depends" to pick up t64 suffix. (Closes: #1068599) Checksums-Sha1: 13aa079443ecab4ecdc42ae6a27dc9289f35a87a 2713 xapian-bindings_1.4.22-2.dsc 4017636c87491dd44af4f55db8cc0bf4e271eb9b 22920 xapian-bindings_1.4.22-2.debian.tar.xz 1c2a1d4032090d6f61c195f58c42133b2c7877b6 17486 xapian-bindings_1.4.22-2_amd64.buildinfo Checksums-Sha256: 24b9013a0eb2301dff7f8eb7202c90487388cba9e875e372c058f43ea6f7c282 2713 xapian-bindings_1.4.22-2.dsc ffd554a16a7efc87eaa027f1e974de56b5243d4dfb7bce47b7e9b1e15e68ac22 22920 xapian-bindings_1.4.22-2.debian.tar.xz f763a6e5a5c70ef037110307a2767901668e32c7da3172cf76724008f7269ad8 17486 xapian-bindings_1.4.22-2_amd64.buildinfo Files: 641b52714306cf9319fd5e0c157ef2ef 2713 libs optional xapian-bindings_1.4.22-2.dsc 833bfa09102166862dad0b5b0f3821d8 22920 libs optional xapian-bindings_1.4.22-2.debian.tar.xz 8ec802d8bfd5a78f0ddb735f7ed017fe 17486 libs optional xapian-bindings_1.4.22-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAmYThvsACgkQGBR7Bzut KwfJSA/+LcH/ZBa8nhMb9S9qxuKOkbLidJXdbCcpoO5vDulcyp00nmUXkK3Pvagb /Jqpz0AFY1QyMwRefrbSp30ATxwP39+nDrcjaBmZXEnkAYEgCXIZpH0xz53BKbfp f3J1FmaM76kGP7J6b7pNDiXRdkof/msvWWLM5I0GhPwWj8vmD3j2cJEBQe3WcfI2 ued0I11EHvr1uNG9tWOwoXay8fYJBysn48z0Szp/oA98U9/SPBtlOUCJG3hEZ+E6 8e1TgaFL4IUnzrJItZwQt3+8wfFAJAbCdsCKBlb1sCk+h5ASQCtg755DMHKzErVa Xjj/xzQLZCQo7YcQTC44lKaXIZjySWDBc0s895gJMYcMxkH60vfOLgy27+wQRKH9 SJkmgWnK8vJIiBDN52xpDHaeLiMbMg+PegqV1QAVvA/kMR74WtsvuUFPiEdOipZ2 eJ/D59gpO+ywK6KhATAbzlwNRZ7a65U5ylQVOdUdc4bMiSNJmkFUoLTD4em8Ak2Y A9z4WxAT4gxqcC2MEYamlPI1T9TXjb/6Vzt2GVX+zuEOm4VKNeqSKJw7Ln0sVNCd ytAmv3SYSBDh6lTOn6f5l9RhprEu5hzur2V45qzovfHfycg/RBzlyPp5Svd4Acsl YGh/Cd3joV3HcO028fu1U3+qmnIMmh3kdx29A6WWEzzY8ni6hqI= =NjOB -END PGP SIGNATURE- pgp8U0NfkThCz.pgp Description: PGP signature --- End Message ---
Bug#1063982: setuptools-scm: autopkgtest regression with pytest 8
* Andrey Rakhmatullin [2024-04-07 17:13]: This works in a current sid chroot, both build-time tests and autopkgests. Timo, do you think we can close this or does something else need to be checked? pytest 8.1 fixed a few regressions, so it is likely that either that or another fix in a dependent package has repaired the tests. Please go ahead and close the bug. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
