Processed: tagging 1071930
Processing commands for cont...@bugs.debian.org: > tags 1071930 + pending Bug #1071930 [src:kwallet-pam] kwallet-pam: Searches for libgcrypt with libgcrypt-config Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1071930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061001: marked as done (scikit-fmm: FTBFS: avx512pfintrin.h:180:3: error: ‘base’ may be used uninitialized [-Werror=maybe-uninitialized])
Your message dated Sat, 06 Jul 2024 05:36:47 + with message-id and subject line Bug#1061001: fixed in scikit-fmm 2024.05.29-1 has caused the Debian Bug report #1061001, regarding scikit-fmm: FTBFS: avx512pfintrin.h:180:3: error: ‘base’ may be used uninitialized [-Werror=maybe-uninitialized] 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.) -- 1061001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scikit-fmm Version: 2022.08.15-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240115 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cython3 --cplus -3 /<>/skfmm/pheap.pyx > dh_auto_configure > I: pybuild base:305: python3.12 setup.py config > /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: > UserWarning: Unknown distribution option: 'configuration' > warnings.warn(msg) > /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: > Normalizing '2022.08.15' to '2022.8.15' > self.metadata.version = self._normalize_version( > running config > I: pybuild base:305: python3.11 setup.py config > /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:265: > UserWarning: Unknown distribution option: 'configuration' > warnings.warn(msg) > /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: > Normalizing '2022.08.15' to '2022.8.15' > self.metadata.version = self._normalize_version( > running config > make[1]: Leaving directory '/<>' >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:305: /usr/bin/python3.12 setup.py build > /<>/setup.py:116: DeprecationWarning: > > `numpy.distutils` is deprecated since NumPy 1.23.0, as a result > of the deprecation of `distutils` itself. It will be removed for > Python >= 3.12. For older Python versions it will remain present. > It is recommended to use `setuptools < 60.0` for those Python versions. > For more details, see: > https://numpy.org/devdocs/reference/distutils_status_migration.html > > > from numpy.distutils.core import setup > /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly: > Normalizing '2022.08.15' to '2022.8.15' > self.metadata.version = self._normalize_version( > running build > running config_cc > INFO: unifing config_cc, config, build_clib, build_ext, build commands > --compiler options > running config_fc > INFO: unifing config_fc, config, build_clib, build_ext, build commands > --fcompiler options > running build_src > INFO: build_src > INFO: building extension "skfmm.cfmm" sources > INFO: building extension "skfmm.pheap" sources > INFO: build_src: building npy-pkg config files > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > running build_py > creating /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > copying skfmm/__init__.py -> > /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > copying skfmm/setup.py -> > /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > copying skfmm/heap.py -> > /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > copying skfmm/pfmm.py -> > /<>/.pybuild/cpython3_3.12_scikit-fmm/build/skfmm > running build_ext > INFO: customize UnixCCompiler > INFO: customize UnixCCompiler using build_ext > INFO: CCompilerOpt.cc_test_flags[1077] : testing flags (-march=native) > INFO: C compiler: x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare > -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection > -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 > -I/usr/include/python3.11 -I/usr/include/python3.11 -Wsign-compare -g > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -DNDEBUG -g -fwrapv -O2 -Wall > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > > creating /tmp/tmp4j7s8560/usr > creating /tmp/tmp4j7s8560/usr/lib >
Bug#1059647: marked as done (scikit-fmm: autopkgtest failure with Python 3.12)
Your message dated Sat, 06 Jul 2024 05:36:47 + with message-id and subject line Bug#1059647: fixed in scikit-fmm 2024.05.29-1 has caused the Debian Bug report #1059647, regarding scikit-fmm: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1059647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scikit-fmm Version: 2022.08.15-4 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer scikit-fmm's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/s/scikit-fmm/testing/amd64/ 35s autopkgtest [20:09:41]: test command1: - - - - - - - - - - results - - - - - - - - - - 35s command1 FAIL stderr: :488: RuntimeWarning: compiletime version 3.11 of module 'skfmm.pheap' does not match runtime version 3.12 35s autopkgtest [20:09:41]: test command1: - - - - - - - - - - stderr - - - - - - - - - - 35s :488: RuntimeWarning: compiletime version 3.11 of module 'skfmm.pheap' does not match runtime version 3.12 --- End Message --- --- Begin Message --- Source: scikit-fmm Source-Version: 2024.05.29-1 Done: Bdale Garbee We believe that the bug you reported is fixed in the latest version of scikit-fmm, 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. Bdale Garbee (supplier of updated scikit-fmm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 22:55:57 -0600 Source: scikit-fmm Architecture: source Version: 2024.05.29-1 Distribution: unstable Urgency: medium Maintainer: Bdale Garbee Changed-By: Bdale Garbee Closes: 1059647 1061001 Changes: scikit-fmm (2024.05.29-1) unstable; urgency=medium . * new upstream version, closes: #1059647, #1061001 Checksums-Sha1: ac391d0d1d055e1d2ad14082c016c114ea75b99e 2068 scikit-fmm_2024.05.29-1.dsc 526ec9d7a907b716e5a2cdf4abd7063e0b8b1072 460911 scikit-fmm_2024.05.29.orig.tar.gz 473375d6851676bd3695607c6a4d743ac7f643f9 4072 scikit-fmm_2024.05.29-1.debian.tar.xz 110491bd509b1a4beb81ef481a0c506b67fc6c91 7820 scikit-fmm_2024.05.29-1_amd64.buildinfo Checksums-Sha256: 50e33a6398b4d249d0683c1f06d2c29d46478e606fe3167856440d77c080304c 2068 scikit-fmm_2024.05.29-1.dsc a6024294dff01377ee5cb95a869c7c86373eccfe0d83314503cc99b76713343e 460911 scikit-fmm_2024.05.29.orig.tar.gz e5c9a813159bda3f4cdc6b8ab9b29e320ae765a94e43a0efd547fa2e0ee74fed 4072 scikit-fmm_2024.05.29-1.debian.tar.xz 896b191d60cf8cd1781f12c3735757ddedf8dedc8659ca1d6a9d6211640ade11 7820 scikit-fmm_2024.05.29-1_amd64.buildinfo Files: dff07bb66e4d6242a668fed67962c1d1 2068 python optional scikit-fmm_2024.05.29-1.dsc 1363d18c4640be8b60e5772503fd65a6 460911 python optional scikit-fmm_2024.05.29.orig.tar.gz 5958865d12133758af44d4e97591941d 4072 python optional scikit-fmm_2024.05.29-1.debian.tar.xz 6c29209e06ad16cf202874918a31b9d9 7820 python optional scikit-fmm_2024.05.29-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAmaI0f4ACgkQtwRxBYML n6Hs0xAA1X3gIDIuM7VK5pI3rY1QBt5TqqEowzAR2eTPo/KxIoBl93pVQpgEpjMT sHAZIrH5ElJGpQmB7IpElaGtjoz3ZnMM+R0KdNk1LMDZ/Wun6nVKaLHaQ97MQjyw NxcpF2eNGGbgZN3aOy0LT2KCFvzRgvAGLyG7FoZocIdgg7fyKI73A8RUY5iIr6jB IdSABx+g4h7MoSEoDpsDKv66UltSKjdHNw9dYjDMGcoXC0YAcyelBfgPVy7obCxv efZjHBJeCpoR+ZcXSIyul0oSwIBcjMK3+0LxkTl3LsCWX8zwkMqcgf4uHZRrTQ2K bq9uRtr+CoNG22wX2r+A4ILXQCIYYBO8hHcHb+khYrCmNqHmujawyXZST8F+EOX5 Qk05juWaU0v8/ACh9+g3IdqkYs7yhIGZVf+MED4xucko6mI4qnYrSoJN18RdUXY9 W2wgaXTs6q/OvxvM2vYWA1AGSpmV6bUx6I+16aoEPjXGMqVt5eOHCCRYYC+2Q5qr M8p+xzyE/dWesxWE5qJcPB/RPG3RpGr4IKI1uWzuPXhl1tyGuZPWZggoAJcEHzNM u6wjYKYr4xoiQgzn6x55wWOH4sPoPYaimsXPjBPU+P53IeSeOm7AUVcF9/IsV/Va 9vLg9i3QHJ8uddXDNyhhLHtuvkmZxMQBeUZr4ke/TTqf8dNkLqU= =VEmO -END PGP SIGNATURE- pgpTq04QUPf0g.pgp Description: PGP signature --- End Message ---
Bug#1074673: libktoblzcheck: FTBFS: tests failed
Control: tags -1 moreinfo Hi Lucas, Thank you for taking the time to file this bug report. Unfortunately not all reproduction details are available. And given these two lines in the logs: > 4: Could not read directory "/usr/share/ktoblzcheck": No such file or > directory > 4: Oops, no bank data file was found in directory "/usr/share/ktoblzcheck"! > The ktoblzcheck library will not work. ... I fear something went wrong during installation or so. Could you please accurately describe what you were doing in order to let the build fail? I'd also like to receive the full build log. Kind regards, Micha
Processed: Re: Bug#1074673: libktoblzcheck: FTBFS: tests failed
Processing control commands: > tags -1 moreinfo Bug #1074673 [src:libktoblzcheck] libktoblzcheck: FTBFS: tests failed Added tag(s) moreinfo. -- 1074673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073339: marked as done (abiword: FTBFS: ut_stringbuf.cpp:578:17: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’?)
Your message dated Sat, 06 Jul 2024 05:04:24 + with message-id and subject line Bug#1073339: fixed in abiword 3.0.5~dfsg-3.3 has caused the Debian Bug report #1073339, regarding abiword: FTBFS: ut_stringbuf.cpp:578:17: error: ‘xmlFree’ was not declared in this scope; did you mean ‘xmlFreeURI’? 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.) -- 1073339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abiword Version: 3.0.5~dfsg-3.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../../../libtool --tag=CXX --mode=compile g++ -std=c++11 > -DHAVE_CONFIG_H -I. -I../../../.. -I/usr/include/libpng16 > -I/usr/include/fribidi -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 > -I/usr/include/libgsf-1 -I/usr/include/libxml2 -I/usr/include/wv > -I/usr/include/enchant-2 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/libgoffice-0.10 -I/usr/include/gtk-3.0 > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu > -I/usr/include/webp -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/librsvg-2.0 > -I/usr/include/raptor2 -I/usr/include/rasqal > -I/usr/include/evolution-data-server -I/usr/include/libsoup-3.0 > -I/usr/include/json-glib-1.0 -I/usr/include/libsecret-1 > -I/usr/include/gtk-3.0/unix-print -pthread > -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_0 -I/usr/include -I../../../.. > -I../../../../src/af/ev/gtk -I../../../../src/af/ev/xp > -I../../../../src/af/gr/gtk -I../../../../src/af/gr/xp > -I../../../../src/af/util/unix -I../../../../src/af/util/xp > -I../../../../src/af/xap/gtk -I../../../../src/af/xap/xp -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wsign-compare -Wpointer-arith > -Wchar-subscripts -Wwrite-strings -Wmissing-noreturn -Wformat-overflow=2 > -Wunused -Wpointer-arith -Wshadow -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wno-overloaded-virtual -MT ut_svg.lo -MD -MP -MF .deps/ut_svg.Tpo -c -o > ut_svg.lo ut_svg.cpp > libtool: compile: g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../../../.. > -I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 > -I/usr/include/libgsf-1 -I/usr/include/libxml2 -I/usr/include/wv > -I/usr/include/enchant-2 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/libgoffice-0.10 -I/usr/include/gtk-3.0 > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu > -I/usr/include/webp -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders > -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/librsvg-2.0 > -I/usr/include/raptor2 -I/usr/include/rasqal > -I/usr/include/evolution-data-server -I/usr/include/libsoup-3.0 > -I/usr/include/json-glib-1.0 -I/usr/include/libsecret-1 > -I/usr/include/gtk-3.0/unix-print -pthread > -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_0 -I/usr/include -I../../../.. > -I../../../../src/af/ev/gtk -I../../../../src/af/ev/xp > -I../../../../src/af/gr/gtk -I../../../../src/af/gr/xp > -I../../../../src/af/util/unix -I../../../../src/af/util/xp > -I../../../../src/af/xap/gtk -I../../../../src/af/xap/xp -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wsign-compare -Wpointer-arith > -Wchar-subscripts -Wwrite-strings -Wmissing-noreturn -Wformat-overflow=2 > -Wunused -Wpointer-arith -Wshadow -g -O2 > "-ffile-prefix-map=/<>=." -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wno-overloaded-virtual -MT ut_string.lo -MD -MP -MF .deps/ut_string.Tpo -c > ut_string.cpp -fPIC -DPIC -o .libs/ut_string.o > libtool: compile: gcc
Bug#1070892: marked as done (abiword: Please use pkg-config instead of libgcrypt-config to locate libgcrypt)
Your message dated Sat, 06 Jul 2024 05:04:24 + with message-id and subject line Bug#1070892: fixed in abiword 3.0.5~dfsg-3.3 has caused the Debian Bug report #1070892, regarding abiword: Please use pkg-config instead of libgcrypt-config to locate libgcrypt 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.) -- 1070892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abiword Version: 3.0.5~dfsg-3.2 Severity: normal Tags: patch User: ametz...@debian.org Usertags: libgcrypt-config-removal Control: block 714589 by -1 Hello, Please switch from using libgcrypt-config to pkg-config to locate libgcrypt. libgcrypt-config will be dropped in the next libgcrypt major release. Upstream's AM_PATH_LIBGCRYPT() nowadays uses gpgrt-config iff AM_PATH_GPG_ERROR() is also used. However a) abiword ships an old copy of libgcrypt.m4 so the newer code is not used by autoreconf and b) abiword does not use AM_PATH_GPG_ERROR(). Find attached a trivial patch to simply switch to pkg-config (which is a lot faster than gpgrt-config.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' Description: Use pkg-config to locate gcrypt abiword has an old copy AM_PATH_LIBGCRYPT that alsways uses libgcrypt-config. Newer versions of that macro would use gpgrt-config when used with AM_PATH_GPG_ERROR() which abiword does not. pkgconf does the same job faster. Author: Andreas Metzler Origin: vendor Last-Update: 2024-05-11 --- a/configure.ac +++ b/configure.ac @@ -982,19 +982,16 @@ fi AM_CONDITIONAL(DEBUG, test "$abi_cv_debug" = "yes") # # Optional dependencies handling # -AM_PATH_LIBGCRYPT( 1.4.5, - [ - abi_cv_gcrypt=no - AC_DEFINE([HAVE_GCRYPT], [1], [Use gcrypt for the cryptos]) - ], - [ - abi_cv_gcrypt=yes - ] ) -AM_CONDITIONAL(HAVE_GCRYPT, test "$abi_cv_gcrypt" = "yes") +PKG_CHECK_MODULES([LIBGCRYPT], [libgcrypt >= 1.4.5], + [AC_DEFINE([HAVE_GCRYPT], [1], [Use gcrypt for the cryptos])] + gcryptfound="yes", + [AC_MSG_NOTICE([gcrypt not found])] + gcryptfound="no") +AM_CONDITIONAL(HAVE_GCRYPT, test "$gcryptfound" = "yes") if test "$abi_cv_gnomevfs" = "yes"; then AC_DEFINE([WITH_GNOMEVFS], [1], [Define if using gnome-vfs]) fi --- End Message --- --- Begin Message --- Source: abiword Source-Version: 3.0.5~dfsg-3.3 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of abiword, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated abiword 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: Wed, 03 Jul 2024 18:41:46 +0200 Source: abiword Architecture: source Version: 3.0.5~dfsg-3.3 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Andreas Metzler Closes: 1070892 1073339 Changes: abiword (3.0.5~dfsg-3.3) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS against libxml2 2.12, using patch from upstream GIT. Closes: #1073339 * Drop outdated copy of libgcrypt.m4 to let autoreconf use the current version which works without libgcrypt-config even when AM_PATH_GPG_ERROR() is not used. Closes: #1070892 Checksums-Sha1: 73bfd2353e6368f6193e3b037f9e272a02a24752 2758 abiword_3.0.5~dfsg-3.3.dsc 0ea16aca30068eeadc34d051b7d7f8d09befe9d9 71508 abiword_3.0.5~dfsg-3.3.debian.tar.xz Checksums-Sha256: 38f00e06fd308b41c03ce7fcc1d33ae7bceaa6c4f7c92ffb9a47d90f3d12712f 2758 abiword_3.0.5~dfsg-3.3.dsc ad9d3939b5a35b4c8b37b55024713e6c03fb34954af4d7e4641296edbac34d3d 71508 abiword_3.0.5~dfsg-3.3.debian.tar.xz Files: fb455fb34c0f31cab2ee90c15f8c9e80 2758 gnome optional abiword_3.0.5~dfsg-3.3.dsc 6e178c2298382d90f94ae67ca9114bf3 71508 gnome optional abiword_3.0.5~dfsg-3.3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmaIy9QACgkQpU8BhUOC
Bug#1073397: marked as done (vedo: FTBFS: build-dependency not installable: python3-vtk9 (< 9.1.1))
Your message dated Sat, 06 Jul 2024 02:36:28 + with message-id and subject line Bug#1073397: fixed in vedo 2024.5.2-1 has caused the Debian Bug report #1073397, regarding vedo: FTBFS: build-dependency not installable: python3-vtk9 (< 9.1.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.) -- 1073397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vedo Version: 2023.4.6-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, python3, > python3-setuptools, python3-vtk9 (<< 9.1.1) | python3-vtk7, python3-numpy, > python3-deprecated, python3-pygments, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, python3, > python3-setuptools, python3-vtk9 (<< 9.1.1), python3-numpy, > python3-deprecated, python3-pygments, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [750 B] > Get:5 copy:/<>/apt_archive ./ Packages [767 B] > Fetched 2126 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: python3-vtk9 (< 9.1.1) but it is > not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/06/15/vedo_2023.4.6-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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: vedo Source-Version: 2024.5.2-1 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of vedo, 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 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated vedo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jul 2024 03:30:45 +0200 Source: vedo Architecture: source Version: 2024.5.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 1073397 Changes: vedo (2024.5.2-1) unstable; urgency=medium . * New upstream release. - drop
Bug#1073344: marked as done (libsmpp34: FTBFS: ../test_apps/esme.h:32:16: error: implicit declaration of function ‘strtol’; did you mean ‘strtok’? [-Werror=implicit-function-declaration])
Your message dated Fri, 05 Jul 2024 23:49:05 + with message-id and subject line Bug#1073344: fixed in libsmpp34 1.14.4-1 has caused the Debian Bug report #1073344, regarding libsmpp34: FTBFS: ../test_apps/esme.h:32:16: error: implicit declaration of function ‘strtol’; did you mean ‘strtok’? [-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.) -- 1073344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsmpp34 Version: 1.14.3-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I../aux_config -I../src -I.. -I/usr/include/libxml2 > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wall -fPIC -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > -o sendwp-tcp.o `test -f '../test_apps/tcp.c' || echo './'`../test_apps/tcp.c > In file included from ../test_apps/tcp.c:38: > ../test_apps/tcp.c: In function ‘do_tcp_connect’: > ../test_apps/esme.h:32:16: error: implicit declaration of function ‘strtol’; > did you mean ‘strtok’? [-Werror=implicit-function-declaration] >32 | dst = strtol((char*)clave, NULL, 10);\ > |^~ > ../test_apps/tcp.c:57:5: note: in expansion of macro ‘GET_PROP_INT’ >57 | GET_PROP_INT(port, p, "port"); > | ^~~~ > In file included from ../test_apps/smpp.c:40: > ../test_apps/smpp.c: In function ‘do_smpp_send_message2’: > ../test_apps/esme.h:32:16: error: implicit declaration of function ‘strtol’; > did you mean ‘strtok’? [-Werror=implicit-function-declaration] >32 | dst = strtol((char*)clave, NULL, 10);\ > |^~ > ../test_apps/smpp.c:223:5: note: in expansion of macro ‘GET_PROP_INT’ > 223 | GET_PROP_INT( req.source_addr_ton, p, "source_addr_ton" ); > | ^~~~ > cc1: some warnings being treated as errors > make[3]: *** [Makefile:1366: esme-tcp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/06/15/libsmpp34_1.14.3-1.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=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: libsmpp34 Source-Version: 1.14.4-1 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of libsmpp34, 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 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated libsmpp34 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jul 2024 00:57:04 +0200 Source: libsmpp34 Architecture: source Version: 1.14.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Mobcom Maintainers Changed-By: Thorsten Alteholz Closes: 1073344 Changes: libsmpp34 (1.14.4-1) unstable; urgency=medium . * New upstream release. (Closes: #1073344) * debian/control: bump standard to 4.7.0 (no changes) Checksums-Sha1:
Bug#1075832: tk-html3: Completely remove hv3 (and tk-html3), for good reasons
Source: tk-html3 Severity: serious Version: 3.0~fossil20110109-9 X-Debbugs-CC: oleb...@debian.org Dear Debian tk-html3/hv3 package maintainers, Today I encountered a discussion around package hv3 in Debian. With some brief investigation, I found some abnormally high popcon values [2] for hv3 and tk-html3, which is alarming since this software saw no upstream development since 2011 and definitely shall not see so many installations. My current thought is that it may have been accidentally introduced due to Provides: www-browser somewhere (e.g., with Debian XFCE installer as a default www-browser provider), but I haven't really dig into it. By all means, I believe tk-html3/hv3 shall not linger in Debian archive anymore in 2024. Especially since hv3 is a web browser, having an outdated web browser is especially problematic. Ubuntu also had the concensus [3] back in 2022. If you agree, please submit a RM bug against Debian FTP Masters to remove the source package. If you find this source package still useful, please consider dropping the hv3 binary package. At the very very least -- dropping the Provides: www-browser from hv3 could help if you don't want to remove anything at all. I don't see any reverse dependencies or reverse build-dependencies around tk-html3 (build-deps(1) seems to be reporting false positives), so the removal shall be harmless and beneficial. Please let me know if you have any comments. Thanks! Best Regards, Boyuan Yang [1] https://www.reddit.com/r/debian/comments/1dw2yk8/hv3_web_browser/ [2] https://qa.debian.org/popcon.php?package=tk-html3 [3] https://bugs.launchpad.net/ubuntu/+source/tk-html3/+bug/1982578 signature.asc Description: This is a digitally signed message part
Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8
Hi Mathieu, Thank you for the report. This was fixed long ago upstream, but I did not deploy a new version. Sorry for the FTBFS, that is my bad. Greg Sharp gregsh...@geocities.com
Bug#1075794: marked as done (orthanc-wsi FTBFS with DCMTK 3.6.8)
Your message dated Fri, 05 Jul 2024 23:21:18 + with message-id and subject line Bug#1075794: fixed in orthanc-wsi 2.0+dfsg-3 has caused the Debian Bug report #1075794, regarding orthanc-wsi FTBFS with DCMTK 3.6.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1075794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: orthanc-wsi Version: 2.0+dfsg-2 Severity: serious Tags: ftbfs /<>/Framework/Inputs/CytomineImage.cpp:36:10: fatal error: openssl/hmac.h: No such file or directory 36 | #include | ^~~~ compilation terminated. https://people.debian.org/~emollier/transitions/dcmtk/orthanc-wsi_dcmtk.build.xz --- End Message --- --- Begin Message --- Source: orthanc-wsi Source-Version: 2.0+dfsg-3 Done: Sebastien Jodogne We believe that the bug you reported is fixed in the latest version of orthanc-wsi, 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 1075...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Jodogne (supplier of updated orthanc-wsi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Jul 2024 00:49:54 +0200 Source: orthanc-wsi Architecture: source Version: 2.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sebastien Jodogne Closes: 1075794 Changes: orthanc-wsi (2.0+dfsg-3) unstable; urgency=medium . * Added dependency on libpng-dev and libssl-dev. Closes: #1075794 Checksums-Sha1: 221142673e2a0d96c23419e627802fb3dad59034 2311 orthanc-wsi_2.0+dfsg-3.dsc ed5752dfe5b02d1123a4ad976482fde76a344328 2082056 orthanc-wsi_2.0+dfsg-3.debian.tar.xz 87e61f68105c04b0858936be96770306a5d8a42c 15749 orthanc-wsi_2.0+dfsg-3_source.buildinfo Checksums-Sha256: 101d79b795b96e20df0ae47400a6d71654c1f44b2acc696e51efd914810ea5b9 2311 orthanc-wsi_2.0+dfsg-3.dsc 0ab45f60a6d1ee500c7ca3f58e5c0b52796a1993cd00ca6dfbb3524b373c9f18 2082056 orthanc-wsi_2.0+dfsg-3.debian.tar.xz f0fca28884c7db5df4f6668fcb1bba64596189f2aea9c02cc4f54a53cb62a729 15749 orthanc-wsi_2.0+dfsg-3_source.buildinfo Files: 72d5c555111f2d2e896d2dbde2c7c461 2311 science optional orthanc-wsi_2.0+dfsg-3.dsc 0c88ee81d64e92959d13f0353cbd30a1 2082056 science optional orthanc-wsi_2.0+dfsg-3.debian.tar.xz cf674c4c3b40042cca1d9d2e0e6b97fb 15749 science optional orthanc-wsi_2.0+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAmaIeioUHHMuam9kb2du ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw13SsxAAhFQpOgns8o+hbtRvA0UMUOl1qCsR QrZrl5eWNXMUPuqIe08jG8CW6eZKTaZP/0DPe4xGSROKx8HjbDuf3ezwKTO3999K +qrqUM7zmmzGGM6T6q9+Xr3jB6g09jEV0tsieLO7QcWCx34F7/aBtEopHSmKlYdV /P8zJ6kNqXmR/mBnO1aOeH4xGnyy9hgHk+2Tl52cjDX1AhhRBwFy6AEln4anRHXL NVSm5gLKqeMniJbCt41cIkDCQ16DD/B67dUm8qZ48cvpaXbz574tlYh8kfgyD49M ORgUfTTiWpARUOYojqFxWZuBCq7cmd/z/CdbzKwlTBaJNkv/Z/NPygq25RoQkFQt hvcfjMlUtbZGASE9x618kr3pbCvY+SbyuEenAdmnihwSYSb7WDTwTs9KAKjm4Nh3 LXtnZcO676DaiujEXHRxH1ijTV9NPrhQtBqTgf/qsv4LRw1ZedDkjuW0DUPIn2G7 C3+7stXRlw8z5L+TYp7G8I0lt3Do+8scQKBdl3LiZutIayLLu+kvERgHTDISDUTL bOPlZWOe7Ty7VxaV2FDB7M2BMZMkYd0WH5zbDOAkuN8VH62tgPVZifiJ9rXoXSor NGwXgVZ7+D7yaLbQEUySEOoK3xQaV6XXYZy+cbn+orX/6OKZ8rHsf6vx1sLbCsQD LJy278NTfe8/mf4= =U4Sx -END PGP SIGNATURE- pgpFENwb7W9pk.pgp Description: PGP signature --- End Message ---
Bug#1075795: marked as done (orthanc FTBFS with DCMTK 3.6.8)
Your message dated Fri, 05 Jul 2024 22:35:43 + with message-id and subject line Bug#1075795: fixed in orthanc 1.12.4+dfsg-2 has caused the Debian Bug report #1075795, regarding orthanc FTBFS with DCMTK 3.6.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1075795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: orthanc Version: 1.12.4+dfsg-1 Severity: serious Tags: ftbfs -- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY OPENSSL_INCLUDE_DIR) CMake Error at /<>/OrthancFramework/Resources/CMake/OpenSslConfiguration.cmake:64 (message): Unable to find OpenSSL Call Stack (most recent call first): /<>/OrthancFramework/Resources/CMake/OrthancFrameworkConfiguration.cmake:260 (include) CMakeLists.txt:114 (include) -- Configuring incomplete, errors occurred! cd BuildStaticFramework && tail -v -n \+0 CMakeCache.txt https://people.debian.org/~emollier/transitions/dcmtk/orthanc_dcmtk.build.xz --- End Message --- --- Begin Message --- Source: orthanc Source-Version: 1.12.4+dfsg-2 Done: Sebastien Jodogne We believe that the bug you reported is fixed in the latest version of orthanc, 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 1075...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Jodogne (supplier of updated orthanc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 23:57:08 +0200 Source: orthanc Architecture: source Version: 1.12.4+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sebastien Jodogne Closes: 1075795 Changes: orthanc (1.12.4+dfsg-2) unstable; urgency=medium . * Added dependency on libssl-dev. Closes: #1075795 Checksums-Sha1: b0154010459ea31a7a8411a931cff51d6c0fd71a 2698 orthanc_1.12.4+dfsg-2.dsc 7aa5224f3e8bdae860a3d7440426587e81f9055f 232240 orthanc_1.12.4+dfsg-2.debian.tar.xz e874500154c3881e1bbaf27d3b8a7b77eaabdbd4 15670 orthanc_1.12.4+dfsg-2_source.buildinfo Checksums-Sha256: 0851e5ab323d60d29b777e5c863e8a5dd42d8ee1a76ec41ee49fc87df9f662a3 2698 orthanc_1.12.4+dfsg-2.dsc f2ef6f15cb4195fd013f0830a6739227caf11f71bffd74e3ba43362b23397390 232240 orthanc_1.12.4+dfsg-2.debian.tar.xz 0c50f2e1d16cda91dc5dc404e5773560d06caa983dce21523b4f3687cba6dee7 15670 orthanc_1.12.4+dfsg-2_source.buildinfo Files: 72abe687219bb352345371f585c386fb 2698 science optional orthanc_1.12.4+dfsg-2.dsc a24eeed84f4e5413c53001efcb1993ae 232240 science optional orthanc_1.12.4+dfsg-2.debian.tar.xz b684d4804984a52c32b8526acf04 15670 science optional orthanc_1.12.4+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAmaIcCEUHHMuam9kb2du ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw12w6A/+Ka3FI93D64fF7wfN8pvVn6DQkhC3 T/VpZMhbfgdxBB9xLhq8QOBkBkh76RgNCtXkRO0/4sL4vaJGXmln0XEhMsH3uVxt s/AiL1ccgT7ztit5Vvur30+igMyXT516+PYM8g5UK4tfcgV0jQNw20QZ6N2nLQUm BoN/s5vcXV1doNssdsJXXhlAPNdTp0iLK/uWxF3VqkKRu3eeALjrnMZJi/c2DlBk Fu6sU1NF1pfuU95UxsfrI769cVNs1nRPqZ7XKOcK2ewqghQ3xBCIAuChhGep3/mP C9BXJE550fE2sSYB60A/WHLxSHpV0no6rSDJvuERpqW4kq6zd4Q+o1JAcHQBqePE BPe9KdhAcXdfqMG0816qez/PzT4iyehUvxiL71tQWrkU16izEXKP5mDRh/5bSLTY 7WqjLqVYdjcu45SnU4Ry1oaqjjCaTfJTXnC/aM93ePjZpOZtSdBNnttRpUAW6fk6 rvX5ahJZtAyzzDlvHI4Z74nZlgjaiwdOl5NDWceHk/QT/VvV4l3DWVsXm778wOt3 O5dW9kVczRnHs9+w0HVd2LHGnPiyLVETsv106aKA2FTRdfLtYiPUVMn9afnnQ0G0 SvQxYBngPgW05JiLkBOIEDNMcunnMuI79u7BkJ5DzW1FvScqd4nDmIpbmKFL6ca9 l4w39p+cwfVi/YQ= =Ytog -END PGP SIGNATURE- pgp_Xpv6NCL9j.pgp Description: PGP signature --- End Message ---
Bug#1075824: closed by Michael Tokarev (Re: Bug#1075824: qemu: CVE-2024-4467)
Hi,
On Fri, Jul 05, 2024 at 09:27:03PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:qemu package:
>
> #1075824: qemu: CVE-2024-4467
>
> It has been closed by Michael Tokarev .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Tokarev
> by
> replying to this email.
>
>
> --
> 1075824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075824
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> From: Michael Tokarev
> User-Agent: Mozilla Thunderbird
> Date: Sat, 6 Jul 2024 00:23:36 +0300
> To: 1075824-d...@bugs.debian.org
> Subject: Re: Bug#1075824: qemu: CVE-2024-4467
> Message-ID: <85f6d51a-8c62-46ce-b38b-7ec5d4409...@tls.msk.ru>
>
> Version: 1:9.0.1+ds-1
>
> 05.07.2024 23:41, Salvatore Bonaccorso wrote:
> > Source: qemu
> > Version: 1:8.2.5+ds-2
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team
> >
> >
> > Hi,
> >
> > The following vulnerability was published for qemu.
> >
> > CVE-2024-4467[0]:
> > | A flaw was found in the QEMU disk image utility (qemu-img) 'info'
> > | command. A specially crafted image file containing a `json:{}` value
> > | describing block devices in QMP could cause the qemu-img process on
> > | the host to consume large amounts of memory or CPU time, leading to
> > | denial of service or read/write to an existing external file.
>
> This is fixed by qemu uploaded earlier today.
>
> Patches are already prepared for bookworm (for qemu 7.2.x series) and
> already verified upstream and passed the tests.
Yes thanks, had only the 1:8.2.5+ds-2 initially to check.
Updated the security-tracker accordingly now.
Regards,
Salvatore
Bug#1075824: marked as done (qemu: CVE-2024-4467)
Your message dated Sat, 6 Jul 2024 00:23:36 +0300
with message-id <85f6d51a-8c62-46ce-b38b-7ec5d4409...@tls.msk.ru>
and subject line Re: Bug#1075824: qemu: CVE-2024-4467
has caused the Debian Bug report #1075824,
regarding qemu: CVE-2024-4467
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.)
--
1075824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:8.2.5+ds-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for qemu.
CVE-2024-4467[0]:
| A flaw was found in the QEMU disk image utility (qemu-img) 'info'
| command. A specially crafted image file containing a `json:{}` value
| describing block devices in QMP could cause the qemu-img process on
| the host to consume large amounts of memory or CPU time, leading to
| denial of service or read/write to an existing external file.
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2024-4467
https://www.cve.org/CVERecord?id=CVE-2024-4467
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2278875
[2]
https://gitlab.com/qemu-project/qemu/-/commit/bd385a5298d7062668e804d73944d52aec9549f1
https://gitlab.com/qemu-project/qemu/-/commit/2eb42a728d27a43fdcad5f37d3f65706ce6deba5
https://gitlab.com/qemu-project/qemu/-/commit/7e1110664ecbc4826f3c978ccb06b6c1bce823e6
https://gitlab.com/qemu-project/qemu/-/commit/7ead946998610657d38d1a505d5f25300d4ca613
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 1:9.0.1+ds-1
05.07.2024 23:41, Salvatore Bonaccorso wrote:
Source: qemu
Version: 1:8.2.5+ds-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for qemu.
CVE-2024-4467[0]:
| A flaw was found in the QEMU disk image utility (qemu-img) 'info'
| command. A specially crafted image file containing a `json:{}` value
| describing block devices in QMP could cause the qemu-img process on
| the host to consume large amounts of memory or CPU time, leading to
| denial of service or read/write to an existing external file.
This is fixed by qemu uploaded earlier today.
Patches are already prepared for bookworm (for qemu 7.2.x series) and
already verified upstream and passed the tests.
Thanks,
/mjt
--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98
ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0
8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt--- End Message ---
Bug#1075712: marked as done (graphite-carbon: daemon does not start)
Your message dated Fri, 05 Jul 2024 21:05:52 + with message-id and subject line Bug#1075712: fixed in graphite-carbon 1.1.10-1 has caused the Debian Bug report #1075712, regarding graphite-carbon: daemon does not start 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.) -- 1075712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: graphite-carbon Version: 1.1.7-1.2 Severity: grave Tags: patch upstream Justification: renders package unusable Dear Maintainer, The daemon fails to start with the following traceback. -- systemd[1]: Starting carbon-cache.service - Graphite Carbon Cache... carbon-cache[262]: Traceback (most recent call last): carbon-cache[262]: File "/usr/bin/carbon-cache", line 32, in carbon-cache[262]: run_twistd_plugin(__file__) carbon-cache[262]: File "/usr/lib/python3/dist-packages/carbon/util.py", line 71, in run_twistd_plugin carbon-cache[262]: from carbon.conf import get_parser carbon-cache[262]: File "/usr/lib/python3/dist-packages/carbon/conf.py", line 31, in carbon-cache[262]: from carbon.routers import DatapointRouter carbon-cache[262]: File "/usr/lib/python3/dist-packages/carbon/routers.py", line 1, in carbon-cache[262]: import imp carbon-cache[262]: ModuleNotFoundError: No module named 'imp' systemd[1]: carbon-cache.service: Control process exited, code=exited, status=1/FAILURE -- This seems to be fixed upstream. https://github.com/graphite-project/carbon/commit/dea2ddb038b01eff16f5da4a19c7282e438ec19a Thanks. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages graphite-carbon depends on: ii adduser3.137 ii debconf [debconf-2.0] 1.5.86 ii lsb-base 11.6 ii python33.12.2-1 ii python3-cachetools 5.3.3-1 ii python3-twisted24.3.0-2 ii python3-urllib32.0.7-2 ii python3-whisper1.1.4-2.2 ii sysvinit-utils [lsb-base] 3.09-2 graphite-carbon recommends no packages. Versions of packages graphite-carbon suggests: pn graphite-web -- debconf information: * graphite-carbon/postrm_remove_databases: false --- End Message --- --- Begin Message --- Source: graphite-carbon Source-Version: 1.1.10-1 Done: Alexandre Rossi We believe that the bug you reported is fixed in the latest version of graphite-carbon, 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 1075...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Rossi (supplier of updated graphite-carbon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 15:32:02 +0200 Source: graphite-carbon Architecture: source Version: 1.1.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Graphite Group Changed-By: Alexandre Rossi Closes: 1022922 1044615 1074696 1075712 Changes: graphite-carbon (1.1.10-1) unstable; urgency=medium . [ Debian Janitor ] * Use secure copyright file specification URI. * Bump debhelper from old 10 to 13. + Replace python_distutils buildsystem with pybuild. + Use dh_installsystemd rather than deprecated dh_systemd_enable. + Use dh_installsystemd rather than deprecated dh_systemd_start. * Set debhelper-compat version in Build-Depends. * Replace /var/run with /run for the Service PIDFile. . [ Alexandre Rossi ] * update d/watch with move from md5 to sha256 * New upstream version 1.1.10 * Rules-Requires-Root: no * add myself to uploaders * add Pre-depends for --skip-systemd-native * declare compliance to policy 4.7.0 (no change) * port to py3.12 (Closes: #1074696, #1075712) * do not mess with python shebang (Closes: #1022922) * let dh do its cleaning magic (Closes: #1044615)
Bug#1074696: marked as done (graphite-carbon: FTBFS: AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'?)
Your message dated Fri, 05 Jul 2024 21:05:51 + with message-id and subject line Bug#1074696: fixed in graphite-carbon 1.1.10-1 has caused the Debian Bug report #1074696, regarding graphite-carbon: FTBFS: AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you mean: 'read'? 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.) -- 1074696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: graphite-carbon Version: 1.1.7-1.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240702 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > GRAPHITE_NO_PREFIX=True python3 setup.py install --install-layout=deb --root > /<>/debian/graphite-carbon > Traceback (most recent call last): > File "/<>/setup.py", line 27, in > cf.readfp(f, 'setup.cfg') > ^ > AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you > mean: 'read'? > make[1]: *** [debian/rules:19: override_dh_install] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/07/02/graphite-carbon_1.1.7-1.2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240702=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: graphite-carbon Source-Version: 1.1.10-1 Done: Alexandre Rossi We believe that the bug you reported is fixed in the latest version of graphite-carbon, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Rossi (supplier of updated graphite-carbon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 15:32:02 +0200 Source: graphite-carbon Architecture: source Version: 1.1.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Graphite Group Changed-By: Alexandre Rossi Closes: 1022922 1044615 1074696 1075712 Changes: graphite-carbon (1.1.10-1) unstable; urgency=medium . [ Debian Janitor ] * Use secure copyright file specification URI. * Bump debhelper from old 10 to 13. + Replace python_distutils buildsystem with pybuild. + Use dh_installsystemd rather than deprecated dh_systemd_enable. + Use dh_installsystemd rather than deprecated dh_systemd_start. * Set debhelper-compat version in Build-Depends. * Replace /var/run with /run for the Service PIDFile. . [ Alexandre Rossi ] * update d/watch with move from md5 to sha256 * New upstream version 1.1.10 * Rules-Requires-Root: no * add myself to uploaders * add Pre-depends for --skip-systemd-native * declare compliance to policy 4.7.0 (no change) * port to py3.12 (Closes: #1074696, #1075712) * do not mess with python shebang (Closes: #1022922) * let dh do its cleaning magic (Closes: #1044615) * drop dep on lsb-base * StandardError= and StandardOutput= in unit files no longer support "syslog" Checksums-Sha1: 0a8c27dec907a9edb6a86b9e601f27d1d4d62a67 2127 graphite-carbon_1.1.10-1.dsc 8f4f8f7aac163faf2b2d57ac9b18a6f0785ecb32 77091 graphite-carbon_1.1.10.orig.tar.gz 78dd663c54d453b006cc81b8e596096fa545c7c0 14200 graphite-carbon_1.1.10-1.debian.tar.xz 46019f3c9006475974b20ecc8e4bce1d8a90736b 6944 graphite-carbon_1.1.10-1_source.buildinfo Checksums-Sha256:
Bug#1072207: marked as done (click: fails to upgrade from bookworm: prerm fails to run click)
Your message dated Fri, 05 Jul 2024 21:05:08 + with message-id and subject line Bug#1072207: fixed in click 0.5.2-4 has caused the Debian Bug report #1072207, regarding click: fails to upgrade from bookworm: prerm fails to run click 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.) -- 1072207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: click Version: 0.5.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'bookworm'. It installed fine in 'bookworm', then the upgrade to 'trixie' fails. >From the attached log (scroll to the bottom...): Preparing to unpack .../06-click_0.5.2-3_amd64.deb ... Traceback (most recent call last): File "/usr/bin/click", line 31, in import gi File "/usr/lib/python3/dist-packages/gi/__init__.py", line 40, in from . import _gi ImportError: /lib/x86_64-linux-gnu/libgirepository-1.0.so.1: undefined symbol: g_once_init_leave_pointer dpkg: warning: old click package pre-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Traceback (most recent call last): File "/usr/bin/click", line 31, in import gi File "/usr/lib/python3/dist-packages/gi/__init__.py", line 40, in from . import _gi ImportError: /lib/x86_64-linux-gnu/libgirepository-1.0.so.1: undefined symbol: g_once_init_leave_pointer dpkg: error processing archive /tmp/apt-dpkg-install-7xvYff/06-click_0.5.2-3_amd64.deb (--unpack): new click package pre-removal script subprocess returned error exit status 1 The .prerm calls 'click hook remove click-desktop' which fails because python3-gi is temporarily not usable (because libglib2.0-0t64 is not yet unpacked). Do you really need to run that command in the 'upgrade' case? Or could that be restricted to 'remove' (and 'purge')? cheers, Andreas PS: please use 'command -v' instead of 'which' click_0.5.2-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: click Source-Version: 0.5.2-4 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of click, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated click 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: Fri, 05 Jul 2024 21:09:25 +0200 Source: click Architecture: source Version: 0.5.2-4 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 1072207 Changes: click (0.5.2-4) unstable; urgency=medium . * debian/patches: + Add 1021_click-remove-hook-only-on-removal.patch. Only run dh_click prerm code on removal, not on upgrade. (Closes: #1072207). Checksums-Sha1: b0802876a6ebd81fbcd17daf0bae654345b02a7b 2911 click_0.5.2-4.dsc 8c9abbbfee53dcf9ebb54ac60d862a9a29917589 37672 click_0.5.2-4.debian.tar.xz 8b867a371c94d282931d7ccbe854d52b6d0325d5 10396 click_0.5.2-4_source.buildinfo Checksums-Sha256: acf0483fd428b801b0f81bf60616c60d164c6a210ad88ab916266648c4c9f633 2911 click_0.5.2-4.dsc 376acc698676d46e26b5a7f0ccd8988da23904961fc4322d9b0198a714c96e45 37672 click_0.5.2-4.debian.tar.xz 06ad70dade37ac3ecd26831fa4fa589dbbdbf8d31b58b381a4900ff62f198cd3 10396 click_0.5.2-4_source.buildinfo Files: 610eea47c95e78242c693999282b5a29 2911 admin optional click_0.5.2-4.dsc f6edb0adce09c35e29f12cee0ec9c3ba 37672 admin optional click_0.5.2-4.debian.tar.xz 6e8351a7c109d450860c7ff3278c6d12 10396 admin optional click_0.5.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmaIVpwVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxCR8P/00vEfuG5QQtUNd3Vz3nADjJf1UZ n8xy4v1HiOMm+vSf7FGA711yIi4nEkjiPZg9SkSe/9mW0SuxzstK74LWEXxhVobJ 3HruHcGAUFbr60TDt0cql9tsxMPiFH6oUAfT2sllg1CMIbfQizMirjPUYl6Y40Up grr46eAPAvVDEBNhLSst6y5HXPN8WoWRRMqocpzPX1u7CnkaEwxnm+JK5cQnYU6l
Bug#1065863: marked as done (galpy: Please drop dependencies on python3-distutils)
Your message dated Fri, 05 Jul 2024 21:05:28 + with message-id and subject line Bug#1065863: fixed in galpy 1.8.1-3 has caused the Debian Bug report #1065863, regarding galpy: Please drop dependencies on python3-distutils 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.) -- 1065863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: galpy Version: 1.8.1-2.1 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham --- End Message --- --- Begin Message --- Source: galpy Source-Version: 1.8.1-3 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of galpy, 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. Alexandre Detiste (supplier of updated galpy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 22:20:26 +0200 Source: galpy Architecture: source Version: 1.8.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers Changed-By: Alexandre Detiste Closes: 1065863 Changes: galpy (1.8.1-3) unstable; urgency=medium . * Team Upload * Add debian/clean * Remove runtime dependency on python3-distutils (Closes: #1065863) Checksums-Sha1: 9c36d3dbf5081933b6b7534fd4f9c5d258510fc8 2144 galpy_1.8.1-3.dsc 995670b101cc2e6d6cb51f70642d20d083812771 5432 galpy_1.8.1-3.debian.tar.xz 7e43b80ffd5a53007e06980e7736869be9f22aef 10064 galpy_1.8.1-3_source.buildinfo Checksums-Sha256: ce4f544d6246682b7e4338be5a08b95d345fc108ba5fae72dd274d93e49f7e77 2144 galpy_1.8.1-3.dsc dff6e4a0d7d2b56bbc1bdd84946599ded57b57286149582c133ed40a3d54f1ef 5432 galpy_1.8.1-3.debian.tar.xz 8cbb0beb9479a4baef8f8236cfc180dc616504459a9de5a54b00a24fb818b951 10064 galpy_1.8.1-3_source.buildinfo Files: 1dda5e5582581bfdbfc70531782e54b2 2144 python optional galpy_1.8.1-3.dsc 78902a21ee2af18eef3a7b089a10ce9d 5432 python optional galpy_1.8.1-3.debian.tar.xz bf5292003fddd2ac69f7bc5513f91e3f 10064 python optional galpy_1.8.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmaIWJIRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBqNhw/8C9VUmUHAa7ODPhSbt2y1vBMvDvjIzHW+ dG/QVE/B9BqFFwbv+Z+TE9Cd/S845+XFP8E25mYS7PtDge5YhwoJ9Wd14KqCtD+2 Nm0bDLiOGh6jtza1q72dh86PzPuWAn9c8hCEj+jmm0L2gEgBRsjWydPQvk9c0+MM wd/J1V+fuGEj+nJSIvpJeBX7skYg012vawmswn1Xegpp1h6rO4RGx++BhOAGaQUm FdDDQAITmCnJi9AG5/LNUORo5FO69mso4dWEB0DDw6aQXDOvUkiMRUnpkCHRpGCw hN16BeC/a0wfA/Rfn2ieUJ7MlAFiwEx4uaF1wnbDj+9668ztb+/pTLehQzptbgHy evZZb6KxV49rYV6tXO50rD470CGh+erTl/eBnq+lA42dsgdRCWabgQWonb+N+OW/ dZ4Vxn18QyoATupsDwtly5NgjVtazfnw5cg1PDXNxxHD6QGPQgQ0qZPHH7LUJS2j vxUP+wYNvJ4z8qXYJEw0y/CxqwL/dUJkq3mZ6AoGsVSXbu59zCJVH0qpuh0D4nPv R6oyTwMX+vOzDjWUTBkjzP0f4Z2WvD4Pdc1fxNf+1YarWjYmcipjLS4LY9Sq/Kvh qH52W4N0cMj580cnoZ31ypyw+DB1+GXXgNB0fUkGimOCLdl/UCL7YTraxvqqieC8 vBqC2/A7z7Q= =5w83 -END PGP SIGNATURE- pgpyqgD2lJe6G.pgp Description: PGP signature --- End Message ---
Bug#1075824: qemu: CVE-2024-4467
Source: qemu
Version: 1:8.2.5+ds-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for qemu.
CVE-2024-4467[0]:
| A flaw was found in the QEMU disk image utility (qemu-img) 'info'
| command. A specially crafted image file containing a `json:{}` value
| describing block devices in QMP could cause the qemu-img process on
| the host to consume large amounts of memory or CPU time, leading to
| denial of service or read/write to an existing external file.
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2024-4467
https://www.cve.org/CVERecord?id=CVE-2024-4467
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2278875
[2]
https://gitlab.com/qemu-project/qemu/-/commit/bd385a5298d7062668e804d73944d52aec9549f1
https://gitlab.com/qemu-project/qemu/-/commit/2eb42a728d27a43fdcad5f37d3f65706ce6deba5
https://gitlab.com/qemu-project/qemu/-/commit/7e1110664ecbc4826f3c978ccb06b6c1bce823e6
https://gitlab.com/qemu-project/qemu/-/commit/7ead946998610657d38d1a505d5f25300d4ca613
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
Bug#1072207: click: fails to upgrade from bookworm: prerm fails to run click
On Fr 05 Jul 2024 22:29:30 CEST, Mike Gabriel wrote: Do I actually upload a second time then, because I think that at build time of click, the already installed dh_click gets used? Remembered it now and found the part in d/rules. Click uses its own dh_click from the source tree at build time. Let's see if piuparts works now. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpzSg6bOmD4S.pgp Description: Digitale PGP-Signatur
Processed: closing 1067312
Processing commands for cont...@bugs.debian.org: > close 1067312 2024.1-1 Bug #1067312 [src:spirv-tools] spirv-tools: FTBFS: operand.kinds-unified1.inc:566:97: error: ‘SPV_OPERAND_TYPE_NAMED_MAXIMUM_NUMBER_OF_REGISTERS’ was not declared in this scope Marked as fixed in versions spirv-tools/2024.1-1. Bug #1067312 [src:spirv-tools] spirv-tools: FTBFS: operand.kinds-unified1.inc:566:97: error: ‘SPV_OPERAND_TYPE_NAMED_MAXIMUM_NUMBER_OF_REGISTERS’ was not declared in this scope Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1067312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072207: click: fails to upgrade from bookworm: prerm fails to run click
Hi, On Do 30 Mai 2024 12:14:59 CEST, Andreas Beckmann wrote: Package: click Version: 0.5.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'bookworm'. It installed fine in 'bookworm', then the upgrade to 'trixie' fails. From the attached log (scroll to the bottom...): Preparing to unpack .../06-click_0.5.2-3_amd64.deb ... Traceback (most recent call last): File "/usr/bin/click", line 31, in import gi File "/usr/lib/python3/dist-packages/gi/__init__.py", line 40, in from . import _gi ImportError: /lib/x86_64-linux-gnu/libgirepository-1.0.so.1: undefined symbol: g_once_init_leave_pointer dpkg: warning: old click package pre-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... Traceback (most recent call last): File "/usr/bin/click", line 31, in import gi File "/usr/lib/python3/dist-packages/gi/__init__.py", line 40, in from . import _gi ImportError: /lib/x86_64-linux-gnu/libgirepository-1.0.so.1: undefined symbol: g_once_init_leave_pointer dpkg: error processing archive /tmp/apt-dpkg-install-7xvYff/06-click_0.5.2-3_amd64.deb (--unpack): new click package pre-removal script subprocess returned error exit status 1 The .prerm calls 'click hook remove click-desktop' which fails because python3-gi is temporarily not usable (because libglib2.0-0t64 is not yet unpacked). Do you really need to run that command in the 'upgrade' case? Or could that be restricted to 'remove' (and 'purge')? I have now uploaded a fix for this (limiting the DH prerm recipe to remove (ah... and purge... needs a follow then...)). Do I actually upload a second time then, because I think that at build time of click, the already installed dh_click gets used? cheers, Andreas PS: please use 'command -v' instead of 'which' Ah, also that one... Needs a follow-up as well. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpSoS43PfhF4.pgp Description: Digitale PGP-Signatur
Processed: Bug#1072207 marked as pending in click
Processing control commands: > tag -1 pending Bug #1072207 [click] click: fails to upgrade from bookworm: prerm fails to run click Added tag(s) pending. -- 1072207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072207: marked as pending in click
Control: tag -1 pending Hello, Bug #1072207 in click 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/click/-/commit/15ceca04c61f0ec4e62b81b7d8cf155786f1b26c debian/patches: Add 1021_click-remove-hook-only-on-removal.patch. Only run dh_click prerm code on removal, not on upgrade. (Closes: #1072207). (this message was generated automatically) -- Greetings https://bugs.debian.org/1072207
Processed: retitle 1074716 to package-update-indicator FTBFS with gettext 0.22
Processing commands for cont...@bugs.debian.org: > retitle 1074716 package-update-indicator FTBFS with gettext 0.22 Bug #1074716 [src:package-update-indicator] package-update-indicator: FTBFS: make[2]: *** [Makefile:227: org.guido-berhoerster.code.package-update-indicator.desktop] Error 1 Changed Bug title to 'package-update-indicator FTBFS with gettext 0.22' from 'package-update-indicator: FTBFS: make[2]: *** [Makefile:227: org.guido-berhoerster.code.package-update-indicator.desktop] Error 1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075821: summer can get size wrong on 32-bit host!
Package: chiark-utils-bin Version: 7.0.1 Severity: serious Seen in a backup confirmation checksum diff -08b4ed2ab7e1723fdf84ca56f055cabb 5656798178 660 0 ... +08b4ed2ab7e1723fdf84ca56f055cabb 1361830882 660 0 ... These two values differ by 2^32. (This is with a locally-built backport binary, not a buildd binary, but I doubt that makes much difference.) -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#1065899: marked as done (lomiri-calculator-app: Please drop dependencies on python3-distutils)
Your message dated Fri, 05 Jul 2024 19:18:58 + with message-id and subject line Bug#1065899: fixed in lomiri-calculator-app 4.0.2-2 has caused the Debian Bug report #1065899, regarding lomiri-calculator-app: Please drop dependencies on python3-distutils 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.) -- 1065899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lomiri-calculator-app Version: 4.0.2-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham --- End Message --- --- Begin Message --- Source: lomiri-calculator-app Source-Version: 4.0.2-2 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of lomiri-calculator-app, 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. Mike Gabriel (supplier of updated lomiri-calculator-app 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: Fri, 05 Jul 2024 20:58:26 +0200 Source: lomiri-calculator-app Architecture: source Version: 4.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 1065899 Changes: lomiri-calculator-app (4.0.2-2) unstable; urgency=medium . * debian/watch: + Update file for recent GitLab changes of the tags overview page. * debian/patches: + Add 2001_ignore-autopilot.patch. Skip building tests/ folder. * debian/control: + Drop from B-D: python3, python3-distutils, npm. (Closes: #1065899). Checksums-Sha1: a497402a3e07ca69eb1c5e54d2134507a469b46f 2192 lomiri-calculator-app_4.0.2-2.dsc 3bf386a728fe533f78ac5eea1bca5e9fc3b72e5a 4836 lomiri-calculator-app_4.0.2-2.debian.tar.xz dc5b2bbaf0d9994783e9f177e2e30a7a2ed576ff 12156 lomiri-calculator-app_4.0.2-2_source.buildinfo Checksums-Sha256: 580c19c06f1683cae1ad0c701a2cfe5b67e71bda51f7f07570b40507f50486c7 2192 lomiri-calculator-app_4.0.2-2.dsc f047513905f1a6b1e46d52b133e0a475f61941524905e11f5861470511344f6c 4836 lomiri-calculator-app_4.0.2-2.debian.tar.xz a2a886df5551717bd4cf181f5dfeec4ae11bd0b7f2c5f22459522ac683ecfef4 12156 lomiri-calculator-app_4.0.2-2_source.buildinfo Files: 0c4513db36f50b5c37ffd1b824212fb1 2192 misc optional lomiri-calculator-app_4.0.2-2.dsc 7e75e43028c948fedef218c2c5067151 4836 misc optional lomiri-calculator-app_4.0.2-2.debian.tar.xz 4d8d96f626950525a3788537c45fa201 12156 misc optional lomiri-calculator-app_4.0.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmaIQmUVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxBmgP/i730X1U0VQYsEPzXwMVntNvr+kZ 1QrCfRgs+lEuaJP+5+7xw5RkykkQ53GmCASsohs76FopERtMC3Yvwqd3B/acuqgq 8JH/QyD4T/JJqKFhpIe/1EcEiPL+MlPtbyYx2uhIscL6Wh2bVjP8UtccMh3sungv dmBls9mtq17qprpVHlYuT/8sqykkgEnbLTMblmnkriTszNeXZVSU2pNcCpLG12po ayIKyH4ENikaL3SlMKc/w47uuGXm7cC7f11iKkcDZwyD9JAy8BD5g2M4KtTKtas5 J82Szq13d/vWZhL+0zXXDbdjAGYsg3/h8hT5jxUJ9Z8ZchDkk/ZgC99LRYpE7rH+ l6PnjKqtLAGVQ+jN95GgwGoDnR54RLoeP+HaGsPBQoHPORyfpHXEr6Z99ZTae/Ws i4Y4uwQTgXaN9uJPrA7p5z6sxwMBP34ETmpHfe3WsHaEGhdcHM7OnDJ9vMZ+sNYK ZRtDhennd3Iy0w9WmYq7uLc0wLGR0UjZDrQxZOHBy8faux81fSa8lMyHNa+iLN9V jvuUZzh0EDaF/4VdCFcWJ6O5SYODkZwKOP6+wEKNU28wCb8j86Rwe8nWk5T02n+u gFnPnFK/Tp8TnzO6HAaaz5HId33JrcVcV+kEMF9ItqEVnt6i2PrKfOf4fE8t7NnI 5kfLseV8xfroO241 =YtQ+ -END PGP SIGNATURE- pgpdhCPICQQcc.pgp Description: PGP signature --- End Message ---
Processed: Re: Bug#1067507: lomiri-ui-toolkit ftbfs with Python 3.12
Processing control commands:
> close -1
Bug #1067507 [src:lomiri-ui-toolkit] lomiri-ui-toolkit ftbfs with Python 3.12
Marked Bug as done
> fixed -1 1.3.5100+dfsg-1
Bug #1067507 {Done: Mike Gabriel }
[src:lomiri-ui-toolkit] lomiri-ui-toolkit ftbfs with Python 3.12
Marked as fixed in versions lomiri-ui-toolkit/1.3.5100+dfsg-1.
--
1067507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067507: lomiri-ui-toolkit ftbfs with Python 3.12
Control: close -1 Control: fixed -1 1.3.5100+dfsg-1 On Fr 22 Mär 2024 17:44:56 CET, Matthias Klose wrote: Package: src:lomiri-ui-toolkit Version: 1.3.5012+dfsg-5 Severity: important Tags: sid trixie patch User: debian-pyt...@lists.debian.org Usertags: python3.12 lomiri-ui-toolkit ftbfs with Python 3.12, patch at http://launchpadlibrarian.net/720653257/lomiri-ui-toolkit_1.3.5012+dfsg-5_1.3.5012+dfsg-5ubuntu1.diff.gz I didn't check if the quoting is correct. This issue has been addressed (differently) for upstream release 1.3.5100. I also tried a rebuild against recent Debian unstable (including python3.12 as default Python version). No build problem found. So, closing... Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpvGe3vopeZq.pgp Description: Digitale PGP-Signatur
Bug#1065899: marked as pending in lomiri-calculator-app
Control: tag -1 pending Hello, Bug #1065899 in lomiri-calculator-app 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-calculator-app/-/commit/ce5d98860e1590fca8192edc381c0882413a8da8 debian/control: Drop from B-D: python3, python3-distutils, npm. (Closes: #1065899). (this message was generated automatically) -- Greetings https://bugs.debian.org/1065899
Processed: Bug#1065899 marked as pending in lomiri-calculator-app
Processing control commands: > tag -1 pending Bug #1065899 [src:lomiri-calculator-app] lomiri-calculator-app: Please drop dependencies on python3-distutils Added tag(s) pending. -- 1065899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075813: marked as done (Krb5: fails to pick up debian configuration)
Your message dated Fri, 05 Jul 2024 17:49:49 + with message-id and subject line Bug#1075813: fixed in krb5 1.21.3-3 has caused the Debian Bug report #1075813, regarding Krb5: fails to pick up debian configuration 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.) -- 1075813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: krb5-kdc severity: grave version: 1.21.3-2 A typo in version 1.21.3-2 incorrectly interrupts the configure args, among other things causing sysconfdir to be incorrectly set. This breaks krb5-kdc because it does not read /etc/krb5kdc/kdc.conf. Found by CI tests. signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: krb5 Source-Version: 1.21.3-3 Done: Sam Hartman We believe that the bug you reported is fixed in the latest version of krb5, 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 1075...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sam Hartman (supplier of updated krb5 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 11:25:26 -0600 Source: krb5 Architecture: source Version: 1.21.3-3 Distribution: unstable Urgency: medium Maintainer: Sam Hartman Changed-By: Sam Hartman Closes: 1075813 Changes: krb5 (1.21.3-3) unstable; urgency=medium . * Fix sysconfdir in call to configure, broken in previous upload, Closes: #1075813 Checksums-Sha1: 94355e1ebafdecfa29b8e92e75042c9be759523c 3381 krb5_1.21.3-3.dsc 6a3825731d7e35b7d22eefc55dd21bf176535621 103380 krb5_1.21.3-3.debian.tar.xz 0cf136482552f0f2c306fbacd53b55304054edf8 4999 krb5_1.21.3-3_source.buildinfo Checksums-Sha256: 561af05f1e9c42ca9eab01eaa7ea6cd903494bb5b462917c8fff7d86bbedc872 3381 krb5_1.21.3-3.dsc c7b7bceb2f1bd782d0118904bded8ddaba1aaa54f1b3b2fc0dc3ecaeac450b5b 103380 krb5_1.21.3-3.debian.tar.xz 91c957647b60ea070c56e46087a25a470f6a5019204507cee53869c744d9ff05 4999 krb5_1.21.3-3_source.buildinfo Files: c48c3d9d18bf6e68ed02507d9ab6d12a 3381 net optional krb5_1.21.3-3.dsc 6434e48f096ee4d8cf1596cb8b9523b2 103380 net optional krb5_1.21.3-3.debian.tar.xz 3499758042ace963d11013b7568b00e7 4999 net optional krb5_1.21.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQSj2jRwbAdKzGY/4uAsbEw8qDeGdAUCZogtFAAKCRAsbEw8qDeG dFVBAQD38VDSVkIXvTtTsVHj7caVl7SLP7iyv9vKxRWuMnDqlwD9FeQyMICtl8Ij FjfzuzFxb+5vkJxh+P1V6ZEDbE94YgU= =mEuY -END PGP SIGNATURE- pgpRPJWYz8ydY.pgp Description: PGP signature --- End Message ---
Bug#1075814: plotpy: Fails to build on arm64
Source: plotpy Version: 2.4.0-1 Severity: serious Tags: ftbfs User: debian-...@lists.debian.org Usertags: arm64 X-Debbugs-CC: debian-...@lists.debian.org, lola...@debian.org plotpy fails to build on arm64. Because it built once on arm64, its build needs to be fixed or you could file a RM bug to remove it only on arm64. https://buildd.debian.org/status/package.php?p=plotpy Thank you, Jeremy Bícha
Bug#1075815: plotpy: Failing autopkgtests
Source: plotpy Version: 2.4.0-1 Severity: serious X-Debbugs-CC: debian-...@lists.debian.org, lola...@debian.org plotpy is unable to migrate to Testing because its autopkgtests are failing. (This is true even though its autopkgtests have always failed.) https://qa.debian.org/excuses.php?package=plotpy Thank you, Jeremy Bícha
Processed: found 1063648 in 1.21.3-2
Processing commands for cont...@bugs.debian.org:
> found 1063648 1.21.3-2
Bug #1063648 {Done: Sam Hartman } [src:krb5] krb5: FTBFS
on IPv6-only buildds: "Can't resolve hostname" in dh_auto_test
Marked as found in versions krb5/1.21.3-2; no longer marked as fixed in
versions krb5/1.21.3-2 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1063648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1075813: Krb5: fails to pick up debian configuration
package: krb5-kdc severity: grave version: 1.21.3-2 A typo in version 1.21.3-2 incorrectly interrupts the configure args, among other things causing sysconfdir to be incorrectly set. This breaks krb5-kdc because it does not read /etc/krb5kdc/kdc.conf. Found by CI tests. signature.asc Description: PGP signature
Bug#1075785: marked as done (exim4: CVE-2024-39929: Incorrect parsing of multiline rfc2231 header filename)
Your message dated Fri, 05 Jul 2024 16:35:06 + with message-id and subject line Bug#1075785: fixed in exim4 4.98~RC3-2 has caused the Debian Bug report #1075785, regarding exim4: CVE-2024-39929: Incorrect parsing of multiline rfc2231 header filename 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.) -- 1075785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: exim4 Version: 4.97-8 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://bugs.exim.org/show_bug.cgi?id=3099 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for exim4. CVE-2024-39929[0]: | Exim through 4.97.1 misparses a multiline RFC 2231 header filename, | and thus remote attackers can bypass a $mime_filename extension- | blocking protection mechanism, and potentially deliver executable | attachments to the mailboxes of end users. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-39929 https://www.cve.org/CVERecord?id=CVE-2024-39929 [1] https://bugs.exim.org/show_bug.cgi?id=3099#c4 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: exim4 Source-Version: 4.98~RC3-2 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of exim4, 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 1075...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated exim4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 18:06:31 +0200 Source: exim4 Architecture: source Version: 4.98~RC3-2 Distribution: unstable Urgency: medium Maintainer: Exim4 Maintainers Changed-By: Andreas Metzler Closes: 1075785 Changes: exim4 (4.98~RC3-2) unstable; urgency=medium . * Upload to unstable. * RC3 fixes CVE-2024-39929 Closes: #1075785 Checksums-Sha1: 6e376bf486ab296dd80422248e1aac00551dc11d 2963 exim4_4.98~RC3-2.dsc d38440c1463a9e1cdb2ebfad79f38c1e064d1a04 469524 exim4_4.98~RC3-2.debian.tar.xz Checksums-Sha256: 17bb054dacda7ab7144a2ca572d33b53216417a731286e3a5f6c4369e56c3310 2963 exim4_4.98~RC3-2.dsc ca4b7486565cd46e1c37481930a806ec78a3ef032273791d7f6be0c9d1eedc54 469524 exim4_4.98~RC3-2.debian.tar.xz Files: 828091414c6a38f4d8e7e5a9131bccc1 2963 mail standard exim4_4.98~RC3-2.dsc 706465480bec744b4a5d6b41ae6104b8 469524 mail standard exim4_4.98~RC3-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmaIGuAACgkQpU8BhUOC FISLhA/6AtJ4KuWZUsvUVcFB0J73mGEVHY6dBZm90J5Tv+nKBqlt+He1d7bMKsho sISxiYr854dfh2+3OwvAVY1jafbXpweqMFSBV8sjhhbyNMe9enoNKXn1gROp/haS lDEWdXAwilncd2NRytmjqnnPJKSjYATEweKktVFb8AKU/Xk34KcZU+LdCSNsa6XW o1ahj2cjMavJtEVkGIYgIxPurygsoPAjcAB8SJQCBRSrEV9gca8DouXRThIvccXw 8ZXaICmvvD+ndImsxhE/9OH8d8cPUICvpVuVu0bE0mVTndkPnGBctc5kpYx97ew0 qoO3z7L9zNULBoXqLv6PTY/wTz35/PjhwmRdIGPB0Xl7u6ax66ArKJAGnDeyPkuw tjbWod95klzq15TOe7p3lJSjxmkYYJ9r20FtRUdTeXVdfhiVFIA/9850jzTxv7VS YuXBckDn7FktpxBOGI42MLLTI1RjUPKa7AycAS/2zmX5RMRrwqYrGOjrkpA1QCpJ 5Tjd7oTytj0fayL4CKCnoQUtYjVHFYABKb0bXEIQI7Lzu+n3IX384HGN9i2vcQtw /fx857U6P7cN6JQZSp/H6kiIm645x6ErO+ci98iIAPHcV244Br//aRSfD5rVvNsm 12eqK+NqvydOzyCOLvM0YIWRa/MxwpCH0+Mb7I7X+HajQG/ngpE= =75Zs -END PGP SIGNATURE- pgphDEW3WKH4a.pgp Description: PGP signature --- End Message ---
Bug#1075804: marked as done (rust-libp2p-identity: Fails to build)
Your message dated Fri, 05 Jul 2024 18:28:04 +0200 with message-id <172019688421.255930.9675021562993103...@auryn.jones.dk> and subject line Re: Bug#1075804: rust-libp2p-identity: Fails to build has caused the Debian Bug report #1075804, regarding rust-libp2p-identity: Fails to build 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.) -- 1075804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-libp2p-identity Version: 0.2.9+ds-2 Severity: serious Tags: ftbfs rust-libp2p-identity fails to build. Here's the build log excerpt: error: failed to select a version for the requirement `rmp-serde = "^1.3"` candidate versions found which didn't match: 1.1.1 https://buildd.debian.org/status/package.php?p=rust-libp2p-identity Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Version: 0.2.9+ds-3 Quoting Jeremy Bícha (2024-07-05 14:48:22) > rust-libp2p-identity fails to build. Here's the build log excerpt: > > error: failed to select a version for the requirement `rmp-serde = "^1.3"` > candidate versions found which didn't match: 1.1.1 > > https://buildd.debian.org/status/package.php?p=rust-libp2p-identity Fixed concurrently with this bugreport. Thanks for reporting, regardless. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature --- End Message ---
Bug#1075799: chiark-utils: ftbfs with time_t errors
Jeremy Bícha writes ("Bug#1075799: chiark-utils: ftbfs with time_t errors"):
> chiark-utils fails to build on 64-bit architectures with errors like:
>
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is
> allowed only with _FILE_OFFSET_BITS=64"
>26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
>
>
> https://buildd.debian.org/status/package.php?p=chiark-utils
Thanks for the report.
I had *intended* to enable 64-bit file offsets too.
Ian.
Bug#1075811: autokey-qt can be installed but will nor run
Package: autokey-qt
Version: 0.95.10-2.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Autokey is loaded on login, but not always used. Today I found it did
not function, and had not been loaded. I believe it has been used
within the last three weeks.
Installing autokey-qt after purging autokey-qt and autokey-common
appears to work normally, no errors are shown.
Running it from the GUI menu does nothing, running from the terminal
produces these python errors:
joe@jrenewsid:~$ autokey-qt
Traceback (most recent call last):
File "/usr/bin/autokey-qt", line 33, in
sys.exit(load_entry_point('autokey==0.95.10', 'console_scripts',
'autokey- qt')())
^
File "/usr/bin/autokey-qt", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 205,
in load module = import_module(match.group('module'))
File "/usr/lib/python3.12/importlib/__init__.py", line 90, in
import_module return _bootstrap._gcd_import(name[level:], package,
level)
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in
_find_and_load_unlocked File "", line 935,
in _load_unlocked File "", line
995, in exec_module File "", line 488, in
_call_with_frames_removed File
"/usr/lib/python3/dist-packages/autokey/qtui/__main__.py", line 23, in
from autokey.qtapp import Application
File "/usr/lib/python3/dist-packages/autokey/qtapp.py", line 37, in
from autokey import service, monitor
File "/usr/lib/python3/dist-packages/autokey/monitor.py", line 24, in
from pyinotify import WatchManager, Notifier, EventsCodes,
ProcessEvent File "/usr/lib/python3/dist-packages/pyinotify.py", line
71, in import asyncore
ModuleNotFoundError: No module named 'asyncore'
It appears the asyncore module has been deprecated and removed from
python. I have tried autokey-gtk but it also uses asyncore.
I can find no Debian bug reports for autokey-qt, possibly there are not
many users.
Is there a workaround?
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.9.7-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages autokey-qt depends on:
ii autokey-common 0.95.10-2.1
ii python3 3.12.2-1
ii python3-pyqt55.15.10+dfsg-1+b3
ii python3-pyqt5.qsci 2.14.1+dfsg-1+b3
ii python3-pyqt5.qtsvg 5.15.10+dfsg-1+b3
autokey-qt recommends no packages.
Versions of packages autokey-qt suggests:
pn gnome-shell-extension-appindicator
-- no debconf information
Best regards,
Joe
Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test
> "Chris" == Chris Hofstaedtler writes: Chris> Adam (adsb) points out that the test code in Chris> lib/rpc/unit-test/client.c [1] uses code that does not Chris> support IPv6(-only). I.e. gethostbyname for a name that has Chris> no IPv4 address will fail. So, are the builds going to unshare or not? given that the code is apparently quite happy to work with a hostname that points to ipv4 loopback and given that I already spent a good chunk of time dealing with buildd churn this month, I don't have a lot of love for dealing with more gratuitous environment changes entirely outside my control. I'm kind of tempted to take this to the TC and ask for clarity about what is reasonable to expecte from buildds. --Sam
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > forwarded 1072969 https://github.com/pytorch/pytorch/issues/129228 Bug #1072969 [src:pytorch] pytorch: CVE-2024-5480 Set Bug forwarded-to-address to 'https://github.com/pytorch/pytorch/issues/129228'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1072969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074222: pycorrfit FTBFS with Python 3.12 as default
Hi All, AFAIK pycorrfit GUI should know about the location of the pdf file. Though it is a minor issue. Please feel free to upload, otherwise I'll try to have a look the next week. Thanks, Alex On 7/5/24 15:27, Bo YU wrote: Hi, On Fri, Jul 5, 2024 at 1:55 PM Andreas Tille wrote: Control: tags -1 pending Am Tue, Jul 02, 2024 at 05:07:08PM +0200 schrieb Andreas Tille: I'm fine with whatever solution you might find and you can perfectly skip me when doing some team upload. Could someone please fix W: pycorrfit: file-in-unusual-dir [usr/pycorrfit_doc/CHANGELOG] W: pycorrfit: file-in-unusual-dir [usr/pycorrfit_doc/PyCorrFit_doc.pdf] W: pycorrfit: non-standard-dir-in-usr [usr/pycorrfit_doc/] before uploading. I have pushed one commit which is trying to fix these warnings. Apparently there is no point in keeping the CHANGELOG in the Debian package, so is it okay to drop it? I have moved the PyCorrFit_doc.pdf file to usr/share/doc, but this will introduce possible-documentation-but-no-doc-base-registration info but we do not have -doc package so just left it there. https://salsa.debian.org/med-team/pycorrfit/-/tree/master/debian?ref_type=heads BR, Bo Sorry, I'm too busy with other things Andreas. -- https://fam-tille.de
Bug#1074222: pycorrfit FTBFS with Python 3.12 as default
Hi, On Fri, Jul 5, 2024 at 1:55 PM Andreas Tille wrote: > > Control: tags -1 pending > > Am Tue, Jul 02, 2024 at 05:07:08PM +0200 schrieb Andreas Tille: > > I'm fine with whatever solution you might find and you can > > perfectly skip me when doing some team upload. > > Could someone please fix > > W: pycorrfit: file-in-unusual-dir [usr/pycorrfit_doc/CHANGELOG] > W: pycorrfit: file-in-unusual-dir [usr/pycorrfit_doc/PyCorrFit_doc.pdf] > W: pycorrfit: non-standard-dir-in-usr [usr/pycorrfit_doc/] > > before uploading. > I have pushed one commit which is trying to fix these warnings. Apparently there is no point in keeping the CHANGELOG in the Debian package, so is it okay to drop it? I have moved the PyCorrFit_doc.pdf file to usr/share/doc, but this will introduce possible-documentation-but-no-doc-base-registration info but we do not have -doc package so just left it there. https://salsa.debian.org/med-team/pycorrfit/-/tree/master/debian?ref_type=heads BR, Bo > Sorry, I'm too busy with other things > Andreas. > > -- > https://fam-tille.de
Processed: Debian bugs #1057286, #1057287, #1074722, #1074575, #1074576, #1070376, #1051496, #1069767
Processing commands for cont...@bugs.debian.org: > tags 1057286 + pending Bug #1057286 [xtrkcad] xtrkcad: Please package current stable version 5.2.2aGA Added tag(s) pending. > tags 1057287 + pending Bug #1057287 [src:xtrkcad] xtrkcad: please update Maintainer / Uploaders list Added tag(s) pending. > tags 1074722 + pending Bug #1074722 [src:xtrkcad] xtrkcad: FTBFS: make[3]: *** [app/i18n/CMakeFiles/messages.dir/build.make:85: app/i18n/fi/LC_MESSAGES/xtrkcad.mo] Error 1 Added tag(s) pending. > tags 1074575 + pending Bug #1074575 [src:shotwell] shotwell: Please add dependencies for heif gdk-pixbuf loader Added tag(s) pending. > tags 1074576 + pending Bug #1074576 [src:shotwell] shotwell: Please drop Build-Depends python3-distutils Added tag(s) pending. > tags 1070376 + pending Bug #1070376 [src:uriparser] uriparser: CVE-2024-34402 CVE-2024-34403 Added tag(s) pending. > tags 1051496 + pending Bug #1051496 [mailgraph] mailgraph: does not support the new syslog format Added tag(s) pending. > tags 1069767 + pending Bug #1069767 [dmidecode] dmidecode: New upstream version 3.6 available Added tag(s) pending. > -- Stopping processing here. Please contact me if you need assistance. -- 1051496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051496 1057286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057286 1057287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057287 1069767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069767 1070376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070376 1074575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074575 1074576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074576 1074722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075804: rust-libp2p-identity: Fails to build
Source: rust-libp2p-identity Version: 0.2.9+ds-2 Severity: serious Tags: ftbfs rust-libp2p-identity fails to build. Here's the build log excerpt: error: failed to select a version for the requirement `rmp-serde = "^1.3"` candidate versions found which didn't match: 1.1.1 https://buildd.debian.org/status/package.php?p=rust-libp2p-identity Thank you, Jeremy Bícha
Bug#1069361: marked as done (libgweather4: FTBFS on arm64: Location 'Greenland' has invalid timezone 'America/Godthab')
Your message dated Fri, 05 Jul 2024 12:35:06 + with message-id and subject line Bug#1069361: fixed in libgweather4 4.4.2-2 has caused the Debian Bug report #1069361, regarding libgweather4: FTBFS on arm64: Location 'Greenland' has invalid timezone 'America/Godthab' 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.) -- 1069361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgweather4 Version: 4.4.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -- --timeout-multiplier=3 > cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb > LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 > ninja: Entering directory `/<>/obj-aarch64-linux-gnu' > ninja: no work to do. > 1/4 libgweather / duplicatesOK 0.03s 2 > subtests passed > 2/4 libgweather:lint / Valid Locations file OK 0.04s > 3/4 libgweather / test_libgweather OK 5.10s 6 > subtests passed > 4/4 libgweather / timezones ERROR 5.50s exit > status 1 > >>> LIBGWEATHER_LOCATIONS_PATH=/<>/obj-aarch64-linux-gnu/data/Locations.bin > >>> G_TEST_BUILDDIR=/<>/obj-aarch64-linux-gnu/libgweather/tests > >>> G_ENABLE_DIAGNOSTIC=0 > >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 > >>> G_TEST_SRCDIR=/<>/libgweather/tests GIO_USE_VFS=local > >>> GSETTINGS_BACKED=memory > >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 > >>> MALLOC_PERTURB_=220 > >>> /<>/obj-aarch64-linux-gnu/libgweather/tests/timezones --tap > >>> -k > > > Ok: 3 > Expected Fail: 0 > Fail: 1 > Unexpected Pass:0 > Skipped:0 > Timeout:0 > > Full log written to > /<>/obj-aarch64-linux-gnu/meson-logs/testlog.txt > cd obj-aarch64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt > ==> meson-logs/testlog.txt <== > Log of Meson test suite run on 2024-04-20T04:26:01.916473 > > Inherited environment: SCHROOT_GID=1001 DEB_HOST_MULTIARCH=aarch64-linux-gnu > LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu > DEB_BUILD_GNU_TYPE=aarch64-linux-gnu DEB_LDFLAGS_MAINT_APPEND='-Wl,-O1 > -Wl,-z,defs' DEB_TARGET_ARCH_LIBC=gnu FFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -mbranch-protection=standard' > DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu > CFLAGS_FOR_BUILD='-g -O2' OBJCXXFLAGS_FOR_BUILD='-g -O2' > DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=4 DEB_HOST_ARCH=arm64 > LDFLAGS_FOR_BUILD='' DEB_TARGET_ARCH_ENDIAN=little > SOURCE_DATE_EPOCH=1711219899 OBJCFLAGS_FOR_BUILD='-g -O2' OBJCXXFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security > -mbranch-protection=standard' DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS=w > SCHROOT_GROUP=user42 DEB_TARGET_ARCH=arm64 DPKG_GENSYMBOLS_CHECK_LEVEL=4 > DH_INTERNAL_OPTIONS='' DEB_HOST_GNU_CPU=aarch64 DEB_BUILD_ARCH_LIBC=gnu > MFLAGS=-w DEB_TARGET_ARCH_BITS=64 CXXFLAGS_FOR_BUILD='-g -O2' ASFLAGS='' > DEB_BUILD_ARCH_CPU=arm64 LC_COLLATE=C.UTF-8 SCHROOT_ALIAS_NAME=unstable-arm64 > DEB_HOST_ARCH_OS=linux SHELL=/bin/sh FCFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -mbranch-protection=standard' > DEB_HOST_ARCH_CPU=arm64 SCHROOT_USER=user42 > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > DEB_BUILD_ARCH_ABI=base CPPFLAGS_FOR_BUILD='' DEB_BUILD_ARCH=arm64 > FFLAGS_FOR_BUILD='-g -O2' DEB_HOST_ARCH_LIBC=gnu > SCHROOT_SESSION_ID=sid-arm64-sbuild-9d7cf05d-91ef-4183-902b-2cd003e67d1c > DEB_TARGET_ARCH_CPU=arm64 DEB_HOST_GNU_TYPE=aarch64-linux-gnu > DEB_BUILD_ARCH_OS=linux FCFLAGS_FOR_BUILD='-g -O2' DFLAGS_FOR_BUILD=-frelease > LOGNAME=user42 CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' > DEB_TARGET_MULTIARCH=aarch64-linux-gnu DEB_BUILD_GNU_CPU=aarch64 > DEB_TARGET_ARCH_OS=linux USER=user42 DEB_HOST_ARCH_ABI=base > DEB_BUILD_MULTIARCH=aarch64-linux-gnu LDFLAGS='-Wl,-z,relro -Wl,-z,now > -Wl,-O1 -Wl,-z,defs' DEB_TARGET_GNU_TYPE=aarch64-linux-gnu > DEB_TARGET_ARCH_ABI=base CFLAGS='-g -O2 -Werror=implicit-function-declaration >
Bug#1073464: marked as done (libgweather4: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory)
Your message dated Fri, 05 Jul 2024 12:35:06 + with message-id and subject line Bug#1069361: fixed in libgweather4 4.4.2-2 has caused the Debian Bug report #1069361, regarding libgweather4: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory 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.) -- 1069361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgweather4 Version: 4.4.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test -- --timeout-multiplier=3 > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > MESON_TESTTHREADS=8 meson test --timeout-multiplier=3 > ninja: Entering directory `/<>/obj-x86_64-linux-gnu' > ninja: no work to do. > 1/4 libgweather:lint / Valid Locations file OK 0.06s > 2/4 libgweather / duplicatesOK 0.04s 2 > subtests passed > 3/4 libgweather / test_libgweather OK 5.08s 6 > subtests passed > 4/4 libgweather / timezones ERROR 6.12s exit > status 1 > >>> MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 > >>> GSETTINGS_BACKED=memory G_TEST_SRCDIR=/<>/libgweather/tests > >>> MALLOC_PERTURB_=216 > >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 > >>> GIO_USE_VFS=local > >>> G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/libgweather/tests > >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 > >>> G_ENABLE_DIAGNOSTIC=0 > >>> LIBGWEATHER_LOCATIONS_PATH=/<>/obj-x86_64-linux-gnu/data/Locations.bin > >>> /<>/obj-x86_64-linux-gnu/libgweather/tests/timezones --tap > >>> -k > > > Ok: 3 > Expected Fail: 0 > Fail: 1 > Unexpected Pass:0 > Skipped:0 > Timeout:0 > > Full log written to > /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt > ==> meson-logs/testlog.txt <== > Log of Meson test suite run on 2024-06-16T12:14:40.945448 > > Inherited environment: SCHROOT_GID=1001 DEB_HOST_MULTIARCH=x86_64-linux-gnu > LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu > DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_LDFLAGS_MAINT_APPEND='-Wl,-O1 > -Wl,-z,defs' DEB_TARGET_ARCH_LIBC=gnu FFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -fcf-protection' DEB_BUILD_ARCH_ENDIAN=little > DEB_BUILD_GNU_SYSTEM=linux-gnu CFLAGS_FOR_BUILD='-g -O2' > OBJCXXFLAGS_FOR_BUILD='-g -O2' DEB_BUILD_ARCH_BITS=64 > DEB_BUILD_OPTIONS=parallel=8 DEB_HOST_ARCH=amd64 LDFLAGS_FOR_BUILD='' > DEB_TARGET_ARCH_ENDIAN=little SOURCE_DATE_EPOCH=1711219899 > OBJCFLAGS_FOR_BUILD='-g -O2' OBJCXXFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' > DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS=w SCHROOT_GROUP=user42 > DEB_TARGET_ARCH=amd64 DPKG_GENSYMBOLS_CHECK_LEVEL=4 DH_INTERNAL_OPTIONS='' > DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS=-w > DEB_TARGET_ARCH_BITS=64 CXXFLAGS_FOR_BUILD='-g -O2' ASFLAGS='' > DEB_BUILD_ARCH_CPU=amd64 LC_COLLATE=C.UTF-8 SCHROOT_ALIAS_NAME=unstable > DEB_HOST_ARCH_OS=linux SHELL=/bin/sh FCFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -fcf-protection' DEB_HOST_ARCH_CPU=amd64 > SCHROOT_USER=user42 > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > DEB_BUILD_ARCH_ABI=base CPPFLAGS_FOR_BUILD='' DEB_BUILD_ARCH=amd64 > FFLAGS_FOR_BUILD='-g -O2' DEB_HOST_ARCH_LIBC=gnu > SCHROOT_SESSION_ID=sid-amd64-sbuild-8a093c7d-3400-4b88-84d6-4a79ba4315b4 > DEB_TARGET_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=x86_64-linux-gnu > DEB_BUILD_ARCH_OS=linux FCFLAGS_FOR_BUILD='-g -O2' DFLAGS_FOR_BUILD=-frelease > LOGNAME=user42 CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' > DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64 > DEB_TARGET_ARCH_OS=linux USER=user42 DEB_HOST_ARCH_ABI=base > DEB_BUILD_MULTIARCH=x86_64-linux-gnu LDFLAGS='-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,-z,defs' DEB_TARGET_GNU_TYPE=x86_64-linux-gnu
Bug#1073384: marked as done (tpm2-pytss: FTBFS: make: *** [debian/rules:17: binary] Error 25)
Your message dated Fri, 05 Jul 2024 11:49:05 +
with message-id
and subject line Bug#1073384: fixed in tpm2-pytss 2.3.0-1
has caused the Debian Bug report #1073384,
regarding tpm2-pytss: FTBFS: make: *** [debian/rules:17: binary] Error 25
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.)
--
1073384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tpm2-pytss
Version: 2.2.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild --with python3,sphinxdoc
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
> module
> I: pybuild base:311: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_tpm2_pytss
> * Building wheel...
> /<>/scripts/prepare_headers.py:27: SyntaxWarning: invalid escape
> sequence '\('
> s = re.sub("#define TSS2_RC_LAYER\(level\).*", "", s)
> /<>/scripts/prepare_headers.py:28: SyntaxWarning: invalid escape
> sequence '\('
> s = re.sub("(#define.*)TSS2_RC_LAYER\(0xff\)", "\g<1>0xff", s)
> /<>/scripts/prepare_headers.py:28: SyntaxWarning: invalid escape
> sequence '\g'
> s = re.sub("(#define.*)TSS2_RC_LAYER\(0xff\)", "\g<1>0xff", s)
> /<>/scripts/prepare_headers.py:31: SyntaxWarning: invalid escape
> sequence '\*'
> s = re.sub("/\*.*?\*/", "", s, flags=re.MULTILINE)
> /<>/scripts/prepare_headers.py:34: SyntaxWarning: invalid escape
> sequence '\('
> s = re.sub("(#define [A-Za-z0-9_]+) +\(\(.*?\) \(.*?\)\)", "\g<1>...", s)
> /<>/scripts/prepare_headers.py:34: SyntaxWarning: invalid escape
> sequence '\g'
> s = re.sub("(#define [A-Za-z0-9_]+) +\(\(.*?\) \(.*?\)\)", "\g<1>...", s)
> /<>/scripts/prepare_headers.py:35: SyntaxWarning: invalid escape
> sequence '\('
> s = re.sub("(#define [A-Za-z0-9_]+) +\(\(.*?\).*?\) ", "\g<1>...", s)
> /<>/scripts/prepare_headers.py:35: SyntaxWarning: invalid escape
> sequence '\g'
> s = re.sub("(#define [A-Za-z0-9_]+) +\(\(.*?\).*?\) ", "\g<1>...", s)
> /<>/scripts/prepare_headers.py:37: SyntaxWarning: invalid escape
> sequence '\)'
> "(#define [A-Za-z0-9_]+) .*\n.*?.*\)\)", "\g<1>...", s, flags=re.MULTILINE
> /<>/scripts/prepare_headers.py:37: SyntaxWarning: invalid escape
> sequence '\g'
> "(#define [A-Za-z0-9_]+) .*\n.*?.*\)\)", "\g<1>...", s, flags=re.MULTILINE
> /<>/scripts/prepare_headers.py:39: SyntaxWarning: invalid escape
> sequence '\g'
> s = re.sub("(#define [A-Za-z0-9_]+) .*", "\g<1>...", s)
> /<>/scripts/prepare_headers.py:42: SyntaxWarning: invalid escape
> sequence '\['
> s = re.sub("\[.+?\]", "[...]", s)
> /<>/scripts/prepare_headers.py:77: SyntaxWarning: invalid escape
> sequence '\)'
> "#define TPM2_MAX_TAGGED_POLICIES.*\n.*TPMS_TAGGED_POLICY\)\)",
> /<>/scripts/prepare_headers.py:270: SyntaxWarning: invalid
> escape sequence '\s'
> "TSS2_RC\s+Tss2_MU_BYTE_Marshal\(.+?\);", s, re.DOTALL | re.MULTILINE
> /<>/scripts/prepare_headers.py:274: SyntaxWarning: invalid
> escape sequence '\s'
> "TSS2_RC\s+Tss2_MU_BYTE_Marshal\(.+?\);", "", s, 1, re.DOTALL | re.MULTILINE
> /<>/scripts/prepare_headers.py:278: SyntaxWarning: invalid
> escape sequence '\s'
> "TSS2_RC\s+Tss2_MU_BYTE_Unmarshal\(.+?\);", s, re.DOTALL | re.MULTILINE
> /<>/scripts/prepare_headers.py:282: SyntaxWarning: invalid
> escape sequence '\s'
> "TSS2_RC\s+Tss2_MU_BYTE_Unmarshal\(.+?\);",
> adding path: /<>/scripts
> Traceback (most recent call last):
> File
> "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
> line 373, in
> main()
> File
> "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
> line 357, in main
> json_out["return_val"] = hook(**hook_input["kwargs"])
>
> File
> "/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py",
> line 271, in build_wheel
> return _build_backend().build_wheel(
>^
> File "/usr/lib/python3/dist-packages/setuptools/build_meta.py", line 434,
> in build_wheel
> return self._build_with_temp_dir(
>
Bug#1075799: chiark-utils: ftbfs with time_t errors
Source: chiark-utils Version: 7.0.1 Severity: serious Tags: ftbfs User: debian-...@lists.debian.org Usertags: time-t chiark-utils fails to build on 64-bit architectures with errors like: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" https://buildd.debian.org/status/package.php?p=chiark-utils Thank you, Jeremy Bícha
Bug#1075798: tifffile: Failing autopkgtest on s390x
Source: tifffile Version: 20240702-1 Severity: serious X-Debbugs-CC: oleb...@debian.org tifffile is unable to migrate to Testing because its autopkgtest is failing on s390x which is a release architecture. https://qa.debian.org/excuses.php?package=tifffile Additionally, a source-only upload is needed for migration. Thank you, Jeremy Bícha
Bug#1074731: marked as done (gtkhash: FTBFS: make[4]: *** [Makefile:570: libgtkhash-properties-caja.caja-extension] Error 1)
Your message dated Fri, 05 Jul 2024 10:04:38 + with message-id and subject line Bug#1074731: fixed in gtkhash 1.5-2 has caused the Debian Bug report #1074731, regarding gtkhash: FTBFS: make[4]: *** [Makefile:570: libgtkhash-properties-caja.caja-extension] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1074731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtkhash Version: 1.5-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240702 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/data/caja' > /usr/bin/msgfmt --desktop --keyword Name --keyword Description --template > libgtkhash-properties-caja.caja-extension.in -d ../../po -o > libgtkhash-properties-caja.caja-extension > /usr/bin/msgfmt: no input file should be given if --desktop and -d are > specified > Try '/usr/bin/msgfmt --help' for more information. > make[4]: *** [Makefile:570: libgtkhash-properties-caja.caja-extension] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/07/02/gtkhash_1.5-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240702=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: gtkhash Source-Version: 1.5-2 Done: xiao sheng wen We believe that the bug you reported is fixed in the latest version of gtkhash, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. xiao sheng wen (supplier of updated gtkhash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 17:40:53 +0800 Source: gtkhash Architecture: source Version: 1.5-2 Distribution: unstable Urgency: medium Maintainer: xiao sheng wen Changed-By: xiao sheng wen Closes: 1074731 Changes: gtkhash (1.5-2) unstable; urgency=medium . * d/copyright: update year info to 2024 * d/control: Bump Standards-Version: 4.7.0, no changes needed * add d/p/fix-msgfmt-keyword-use-space.patch (Closes: #1074731) Checksums-Sha1: 134fdfb73b89e2fad90d31296d93bb30f0f7c758 2159 gtkhash_1.5-2.dsc b08ee1550c89a54f47b00f0667a9277c60ba00e2 11308 gtkhash_1.5-2.debian.tar.xz cb65b1743d4637c4c65e85b8cdf5ee4e891aac67 15809 gtkhash_1.5-2_source.buildinfo Checksums-Sha256: ee4456fbd8b6b9bcbadb37a4ada78df26e39097dc162b45e9868681c48c14738 2159 gtkhash_1.5-2.dsc 4ec8274f4d99fe27696752752313ab2e9836db51bc182a2149f36c2a660d50f6 11308 gtkhash_1.5-2.debian.tar.xz c30b487f63ec15ae1eabb824d0d2ac3626097d871f1ac61c976d0cd16db4abb9 15809 gtkhash_1.5-2_source.buildinfo Files: 3b2a7a14b18ec984bb9b517f25aef319 2159 utils optional gtkhash_1.5-2.dsc 22a965cb67c40117bbecac4b950ee3d0 11308 utils optional gtkhash_1.5-2.debian.tar.xz 73d8bdaab32115a7927c6f5e0f9c1064 15809 utils optional gtkhash_1.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEvGv7H5NUQYeSuhtTJ2Egg8PSprAFAmaHwCcSHGF0emxpbnV4 QHNpbmEuY29tAAoJECdhIIPD0qawoeUQAIpZWP1XEXp5lvuFpn1Z5I4mmmWrH9W+ alTFutnArslOGTmw2MwShXG4TaOFzGpQosci28RaQYsfRBp3h7HLS8ep1vWWopTA sYhA3SRLQtn5gnQ8NnztSFoMY8nqmmc4GngLBsFGD1f/reHHoGLbNzBHWwFAN6FO Q1+LVz3Micn3eLUDU3SIaJZ1KcTh61YBEQXcWu/uGyVYKABWnX4WczHtv88/FBEM oLge2yu9QL/3x1wdZuloq6qhST6J5o9qIzinTrNUSqeaImMJ8kmwuYcQyu/+fnQQ Q9hNtFOraROrTJdoNdI1JxAgeles7OMJMQc/xFizzPdWby+Pts746jZnnEZ9Xjii
Bug#1075795: orthanc FTBFS with DCMTK 3.6.8
Source: orthanc Version: 1.12.4+dfsg-1 Severity: serious Tags: ftbfs -- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY OPENSSL_INCLUDE_DIR) CMake Error at /<>/OrthancFramework/Resources/CMake/OpenSslConfiguration.cmake:64 (message): Unable to find OpenSSL Call Stack (most recent call first): /<>/OrthancFramework/Resources/CMake/OrthancFrameworkConfiguration.cmake:260 (include) CMakeLists.txt:114 (include) -- Configuring incomplete, errors occurred! cd BuildStaticFramework && tail -v -n \+0 CMakeCache.txt https://people.debian.org/~emollier/transitions/dcmtk/orthanc_dcmtk.build.xz
Bug#1075794: orthanc-wsi FTBFS with DCMTK 3.6.8
Source: orthanc-wsi Version: 2.0+dfsg-2 Severity: serious Tags: ftbfs /<>/Framework/Inputs/CytomineImage.cpp:36:10: fatal error: openssl/hmac.h: No such file or directory 36 | #include | ^~~~ compilation terminated. https://people.debian.org/~emollier/transitions/dcmtk/orthanc-wsi_dcmtk.build.xz
Bug#1064232: marked as done (rust-axum: Failing autopkgtests)
Your message dated Fri, 05 Jul 2024 09:19:44 + with message-id and subject line Bug#1064232: fixed in rust-axum 0.6.20-19 has caused the Debian Bug report #1064232, regarding rust-axum: Failing autopkgtests 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.) -- 1064232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-axum Version: 0.6.20-16 Severity: serious rust-axum is unable to migrate to Testing because its autopkgtests are failing https://qa.debian.org/excuses.php?package=rust-axum Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: rust-axum Source-Version: 0.6.20-19 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of rust-axum, 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. Jonas Smedegaard (supplier of updated rust-axum package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 10:59:29 +0200 Source: rust-axum Architecture: source Version: 0.6.20-19 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1064232 Changes: rust-axum (0.6.20-19) unstable; urgency=medium . * add patch 1002 to add feature fences for tests; closes: bug#1064232, thanks (again) to Jeremy Bícha * update dh-cargo fork * update copyright info: update coverage Checksums-Sha1: c8a785bccbe4b386de8cbb2bfbd2f7ea14bedef9 7647 rust-axum_0.6.20-19.dsc 5e9e4b7f74566a7591012f58e3c7f8f22bc9f659 21804 rust-axum_0.6.20-19.debian.tar.xz 6485b730008fcbd58668cc43a18c97211453c35c 24592 rust-axum_0.6.20-19_amd64.buildinfo Checksums-Sha256: a41af59e2fd065f8c87e917f1325e9114ebb06ab711fe92da927793ffb413e6f 7647 rust-axum_0.6.20-19.dsc 350e2a3f851c0f5b827f4698a0fad28f5e128b64e69734ca35d843efc6ce490c 21804 rust-axum_0.6.20-19.debian.tar.xz f9de6931744054ae6f389d017e5901a73ed51164db9ba1b22b50d3ad7f6da5e4 24592 rust-axum_0.6.20-19_amd64.buildinfo Files: 107ee2692ca34db2cb9008bbb0781eb9 7647 rust optional rust-axum_0.6.20-19.dsc 65396b4d150f57b2cf6e00f88d342d64 21804 rust optional rust-axum_0.6.20-19.debian.tar.xz d12fd55874896495699be58e9e1cac32 24592 rust optional rust-axum_0.6.20-19_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmaHtmsACgkQLHwxRsGg ASFsQg//fRF5odmncZnRkFkRY1K8EGZbLTntkYn2GykAtM8guyTSmeo2x5/HkrVE Ih2BZciDNmplf2taQip96NNq3HtphMxDv1wzBJZDUWsOurFe/oNnWfDTCG1K+Dct KFxhx1C3zUh+RyeKnXc53X0b9bH9r+uYA2tjveUkrBnV/ebb4IKtRALlJsBhmmNV ciHvdC/kpxqoYjdBwOpM3KJFPvYr17Vo4JkHNQiMcTk7BmFhR7GaReVceGvVRyOI ubjxN+XfwcLAADzxobhCetyqdxMdCQiduLSGrtG/IbXPv1TN+xUft+/qlJIzAXUs HPIIyw4QR3Z77LCGyigD/9fLGagHQGEEUwSzZm3p2qmAEd8D8Tt7BzvgC66dasC5 guX7Pux0c1caxcJXutk+XC845anv/xLMcoGEQ3hV6AtL8ThJkqGl9aUS1uwfk+38 m6oslkqwAHeVrvsA6ghd2bQAB0jeViYQnBSYH0czjcaQBXQxEDcV39i11LfaStet lqdatcJffGYA9uvRsKN7hUlDU1tJ4ShJqoMqF4tmWflsrWZGn66JnEokIYpgD40X cpsPaDKNyyu9decB8TwO0ZrMoWgPufCfzyTcn6N8ZJOvVEtx0YKpn5ctXR0LXkUF ALkn47FsJVznyjYCTWvkZZqA8M8b4pMIeb1jDcF5+TznpF+8lhs= =OfPF -END PGP SIGNATURE- pgpX6W_K0Fr2u.pgp Description: PGP signature --- End Message ---
Bug#1075792: sight FTBFS with DCMTK 3.6.8
Source: sight Version: 23.1.0-3 Severity: serious Tags: ftbfs sight::core::com::Slot&, unsigned int, const std::__cxx11::basic_string&)>::sptr)’: /<>/libs/io/dimse/SeriesEnquirer.cpp:140:41: error: ‘UID_RFC2557MIMEEncapsulationTransferSyntax’ was not declared in this scope; did you mean ‘UID_RETIRED_RFC2557MIMEEncapsulationTransferSyntax’? 140 | transferSyntaxes.DCMTK_EMPLACE_BACK(UID_RFC2557MIMEEncapsulationTransferSyntax); | ^~ | UID_RETIRED_RFC2557MIMEEncapsulationTransferSyntax /<>/libs/io/dimse/SeriesEnquirer.cpp:141:41: error: ‘UID_XMLEncodingTransferSyntax’ was not declared in this scope; did you mean ‘UID_RETIRED_XMLEncodingTransferSyntax’? 141 | transferSyntaxes.DCMTK_EMPLACE_BACK(UID_XMLEncodingTransferSyntax); | ^ | UID_RETIRED_XMLEncodingTransferSyntax [ 49%] Building CXX object libs/geometry/data/CMakeFiles/geometry_data.dir/MeshFunctions.cpp.o https://people.debian.org/~emollier/transitions/dcmtk/sight_dcmtk.build.xz
Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8
Source: plastimatch Version: 1.9.4+dfsg.1-2 Severity: serious Tags: ftbfs /<>/src/plastimatch/base/dcmtk_rtss.cxx: In member function ‘void Dcmtk_rt_study::rtss_save(const char*)’: /<>/src/plastimatch/base/dcmtk_rtss.cxx:475:46: error: ‘DCM_ROIObservationLabel’ was not declared in this scope; did you mean ‘DCM_ObservationNumber’? 475 | rtroio_item->putAndInsertString (DCM_ROIObservationLabel, | ^~~ | DCM_ObservationNumber https://people.debian.org/~emollier/transitions/dcmtk/plastimatch_dcmtk.build.xz It has been retired: % cat dcmdata/include/dcmtk/dcmdata/dcdeftag.h | grep 3006 | grep 85 #define DCM_RETIRED_ROIObservationLabel DcmTagKey(0x3006, 0x0085)
Bug#1072847: fixed in lacme 0.8.3-1
Hi Sakari, On Fri, 05 Jul 2024 at 08:23:56 +, Sakari Ailus wrote: > The removal of the intermediate certificates (or not including the current > ones) however is an issue as the server using the issued certificate still > needs to provide them to the clients. The path pointed to by ‛certificate-chain’ contains the entire chain (excluding the root) as provided by Let's Encrypt. > While it's certainly possible for the lacme user to obtain these > certificates directly from Let's encrypt, it'd be quite convenient to > continue to provide them in the lacme package itself, even if the package > does need to be updated from time to time for that reason. Do you have a concrete usecase? It appears Let's Encrypt has settled on intermediates with <2y lifetime (i.e., shorter than Debian Stable's lifetime), and earlier rotation is at their own discretion, so I don't see how we can reliably provide them as part of the source package. (Updating via (o)s-pu might be an option, but that would only work if the rotation is announced early enough ahead of the point release freeze.) Cheers, -- Guilhem. signature.asc Description: PGP signature
Bug#1072847: fixed in lacme 0.8.3-1
Hi Guilhem, Thank you for fixing the post-issuange logic. The removal of the intermediate certificates (or not including the current ones) however is an issue as the server using the issued certificate still needs to provide them to the clients. Some clients may already have them, such as Firefox, but they don't seem to come in Debian ca-certificates.crt for instance. The result for other clients thus is a validation failure. While it's certainly possible for the lacme user to obtain these certificates directly from Let's encrypt, it'd be quite convenient to continue to provide them in the lacme package itself, even if the package does need to be updated from time to time for that reason. Or alternatively, download them automatically, which likely is error-prone as well unless Let's encrypt provides a canonical URL for them (which they probably do, at least for now). -- Kind regards, Sakari Ailus
Bug#1070910: marked as done (llvm-toolchain-18: autopkgtest fails on amd64)
Your message dated Fri, 5 Jul 2024 10:03:06 +0200
with message-id <864825be-7ae8-44d0-a60f-6fcbdf2ee...@debian.org>
and subject line Fixed: llvm-toolchain-18: autopkgtest fails on amd64
has caused the Debian Bug report #1070910,
regarding llvm-toolchain-18: autopkgtest fails on amd64
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.)
--
1070910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-18
Version: 1:18.1.5-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
https://ci.debian.net/packages/l/llvm-toolchain-18/testing/amd64/46304375/#S6
150s # Builds the test application
150s clang++-$VERSION -std=c++20 \
150s-nostdinc++ \
150s-isystem /usr/lib/llvm-$VERSION/include/c++/v1/ \
150s-L /usr/lib/llvm-$VERSION/lib \
150s-fmodule-file=std=std.pcm \
150s-fmodule-file=std.compat=std.compat.pcm \
150sstd.pcm \
150sstd.compat.pcm \
150s-lc++ \
150sfoo.cpp
151s
151s # Runs the test application
151s # The output should be
151s # Hello modular world
151s # Hello compat modular world
151s ./a.out
151s Hello modular world
151s Hello compat modular world
151s
151s if test ! -f /usr/lib/llvm-$VERSION/include/cxxabi.h; then
151s echo "Install libc++abi-$VERSION-dev";
151s exit -1;
151s fi
151s
151s # Force the usage of libc++abi
151s clang++-$VERSION -stdlib=libc++ -lc++abi foo.cpp -o o
151s foo.cpp:1:1: error: unknown type name 'import'
151s 1 | import std;
151s | ^
151s foo.cpp:2:1: error: unknown type name 'import'
151s 2 | import std.compat;
151s | ^
151s foo.cpp:2:11: error: expected ';' after top level declarator
151s 2 | import std.compat;
151s | ^
151s | ;
151s foo.cpp:5:3: error: 'std' is not a class, namespace, or enumeration
151s 5 | std::cout << "Hello modular world\n";
151s | ^
151s foo.cpp:2:8: note: 'std' declared here
151s 2 | import std.compat;
151s |^
151s foo.cpp:6:5: error: no
member named 'printf' in the global namespace
151s 6 | ::printf("Hello compat modular world\n");
151s | ~~^
151s 5 errors generated.
151s autopkgtest [23:36:28]: test command1: ---]
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
thanks--- End Message ---
Bug#1074175: netkit-rwho: remove for trixie?
Hi. Most tools from netkit are candidates for migration to GNU InetUtils, and rwho(d) may be another one -- see email and bug report below. Cc'ing debian-devel to have broader discussion. First, I think we need to understand the rationale for doing anything about 'netkit-rwho': do we want to do something because 1) it is not maintained upstream? or 2) because it is an insecure design?, or 3) something else? I believe that like telnet and ftp the second argument is not convincing enough: sometimes you need these implementations for various strange things, and it is poor style to dictate what people must do with their software. The position I've taken in GNU InetUtils is that it is better for users to offer maintained tools and include a notice that they are insecure, rather to offer un-maintained tools and refuse to work further on them because they are insecure, putting users into a worse situation than before. Some people may disagree, and instead believe it is better to actively kill old things rather than continue support them. This is a subjective decision, and if people are willing to do the work to keep things alive, I think it is better to let them than to refuse this contribution. So, are our reason for doing anything about netkit-rwho really because netkit upstream is not maintained? If so, then one option is to add a rwho(d) implementation to GNU InetUtils and let that replace the netkit implementation in Debian. Historically, netkit tools have often had unclear or weird license situation, so my preference is to import rwho(d) from some of the BSD and to make that build for a wide variety of architectures and platforms like we do with other tools in GNU InetUtils. The BSD implementations are usually not intended to be portable, and often have some minor flaw that makes them troublesome to build on Debian -- we fix those issues in GNU InetUtils. That said, introducing yet another fork into the ecosystem shouldn't be done lightly, so we should explore some way to pool resources (like I've tried to establish with tnftp(d) maintainers when we have joint bugs). I haven't analyzed what rwho(d) implementations are out there. I see NetBSD/FreeBSD has one still in -current, but OpenBSD removed it during 5.x. Are people aware of any other implementations worth considering? What do you think? /Simon Gürkan Myczko writes: > rwho(d) is a design from a different time, when networks were > trusted, and so on. It seems to me, we should and could stop > shipping it for trixie. > > I'm raising this bug now, to: > 1) establish awareness > > I was long aware of this, as I was using rwhod/ruptime when networks > were not split into thousand networks... > > 2) auto-rm it from trixie > > I'd rather have a migration path, not binary compatible, but > functionality compatible > > 3) give people time to chime in / secure replacements to show up > > Please have a look at https://github.com/alexmyczko/rutpime (there's > an ITP for it, and it has > been in new queue several times: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013361 > > After a while I intend to clone this bug to ftp.debian.org for > removal from unstable. > > Please do not remove it if possible. I really wish to have a migration > path for this, but well > we're waiting for ftp team. > > Best, > Alex > > Chris > > signature.asc Description: PGP signature
Bug#1071885: marked as done (rust-glycin: FTBFS: unsatisfiable build-dependencies)
Your message dated Fri, 5 Jul 2024 09:28:54 +0200 with message-id <20741d73-593a-4d83-a5af-3eb7ceb8c...@riseup.net> and subject line has caused the Debian Bug report #1071885, regarding rust-glycin: FTBFS: unsatisfiable build-dependencies 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.) -- 1071885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rust-glycin Version: 0.1.0-5 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: librust-gdk4-0.7+default-dev (>= 0.7.1-~~) but it is not installable Depends: librust-gdk4-0.7+v4-12-dev (>= 0.7.1-~~) but it is not installable Depends: librust-gio-0.18+default-dev (>= 0.18.1-~~) but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202405/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Version: 1.0.1--- End Message ---
Processed: fixed 1074680 in 1.7.0-3
Processing commands for cont...@bugs.debian.org: > fixed 1074680 1.7.0-3 Bug #1074680 [src:osc] osc: FTBFS: ModuleNotFoundError: No module named 'imp' Marked as fixed in versions osc/1.7.0-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073452: marked as done (pandas: FTBFS: unsatisfiable build-dependency: libzstd1 (< 1.5.6~) but 1.5.6+dfsg-1 is to be installed)
Your message dated Fri, 5 Jul 2024 07:34:32 +0100 with message-id and subject line not any more Re: pandas FTBFS has caused the Debian Bug report #1073452, regarding pandas: FTBFS: unsatisfiable build-dependency: libzstd1 (< 1.5.6~) but 1.5.6+dfsg-1 is to be installed 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.) -- 1073452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pandas Version: 2.1.4+dfsg-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, faketime, > locales-all, python3-all-dev, cython3 (>= 0.29.33~), python3-bottleneck (>= > 1.3.4~), python3-bs4 (>= 4.11.1~), python3-dask (>= 2023.2.0~), > python3-dateutil, python3-fsspec (>= 2022.05.0~), python3-html5lib (>= 1.1~), > python3-hypothesis (>= 6.46.1~), python3-jinja2 (>= 3.1.2~), python3-lxml (>= > 4.8.0~), python3-matplotlib (>= 3.6.1~), python3-numexpr (>= 2.8.0~), > python3-numpy (>= 1:1.23.2~), python3-odf (>= 1.4.1~), python3-openpyxl (>= > 3.0.10~), python3-py, python3-pyreadstat (>= 1.1.5~), python3-pytest (>= > 7.3.2~), python3-pytest-asyncio (>= 0.17~), python3-pytest-forked, > python3-pytest-localserver, python3-pytest-xdist (>= 2.2.0~), python3-scipy > (>= 1.8.1~), python3-setuptools (>= 51~), python3-sqlalchemy (>= 1.4.36~), > python3-tables (>= 3.7.0~), python3-tk, python3-tz (>= 2022.1~), > python3-versioneer, python3-zstandard (>= 0.17.0~), sphinx-common, > tzdata-legacy, xvfb, xauth, xsel, build-essential, fakeroot, python3-sphinx, > python3-sphinx-copybutton, python3-sphinx-design, > python3-pydata-sphinx-theme, python3-ipykernel, python3-notebook (>= 6.0.3~), > python3-nbconvert (>= 6.4.5~), python3-nbsphinx, python3-numpydoc, > python3-pygments, ipython3 (>= 7.11.1~), jdupes, pandoc, python3-doc, > python-scipy-doc, python-statsmodels-doc, python3-rpy2, python3-seaborn, > python3-sqlalchemy, python3-statsmodels, python3-xarray (>= 2022.03.0~) > Filtered Build-Depends: debhelper-compat (= 13), dh-python, faketime, > locales-all, python3-all-dev, cython3 (>= 0.29.33~), python3-bottleneck (>= > 1.3.4~), python3-bs4 (>= 4.11.1~), python3-dask (>= 2023.2.0~), > python3-dateutil, python3-fsspec (>= 2022.05.0~), python3-html5lib (>= 1.1~), > python3-hypothesis (>= 6.46.1~), python3-jinja2 (>= 3.1.2~), python3-lxml (>= > 4.8.0~), python3-matplotlib (>= 3.6.1~), python3-numexpr (>= 2.8.0~), > python3-numpy (>= 1:1.23.2~), python3-odf (>= 1.4.1~), python3-openpyxl (>= > 3.0.10~), python3-py, python3-pyreadstat (>= 1.1.5~), python3-pytest (>= > 7.3.2~), python3-pytest-asyncio (>= 0.17~), python3-pytest-forked, > python3-pytest-localserver, python3-pytest-xdist (>= 2.2.0~), python3-scipy > (>= 1.8.1~), python3-setuptools (>= 51~), python3-sqlalchemy (>= 1.4.36~), > python3-tables (>= 3.7.0~), python3-tk, python3-tz (>= 2022.1~), > python3-versioneer, python3-zstandard (>= 0.17.0~), sphinx-common, > tzdata-legacy, xvfb, xauth, xsel, build-essential, fakeroot, python3-sphinx, > python3-sphinx-copybutton, python3-sphinx-design, > python3-pydata-sphinx-theme, python3-ipykernel, python3-notebook (>= 6.0.3~), > python3-nbconvert (>= 6.4.5~), python3-nbsphinx, python3-numpydoc, > python3-pygments, ipython3 (>= 7.11.1~), jdupes, pandoc, python3-doc, > python-scipy-doc, python-statsmodels-doc, python3-rpy2, python3-seaborn, > python3-sqlalchemy, python3-statsmodels, python3-xarray (>= 2022.03.0~) > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [2861 B] > Get:5 copy:/<>/apt_archive ./ Packages [1997 B] > Fetched 5473 B in 0s (517 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies >
