Bug#1041837: libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= trixie: /usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Hi, Am 24.07.23 um 06:52 schrieb Helmut Grohne: libreoffice-draw installs /usr/lib/libreoffice/share/config/soffice.cfg/simpress/layoutlist.xml and /usr/lib/libreoffice/share/config/soffice.cfg/simpress/objectlist.xml which are also contained in libreoffice-impress-nogui from bullseye to trixie. Mmh, indeed. Already fixed in experimental (well, NEW since ~ 2 months) already though: Package: libreoffice-uiconfig-impress Section: misc Architecture: all Replaces: libreoffice-common (<< 4:7.6.0~beta1), libreoffice-draw (<< 4:7.6.0~rc1), libreoffice-draw-nogui (<< 4:7.6.0~rc1), libreoffice-impress (<< 4:7.6.0~rc1), libreoffice-impress-nogui (<< 4:7.6.0~rc1) Leaves "just" sid. Regards, Rene
Processed: Re: libclang-rt-16-dev: undeclared file conflict with libclang-rt-16-dev-wasm{32,64} on /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a
Processing control commands:
> clone -1 -2
Bug #1041834 [libclang-rt-16-dev] libclang-rt-16-dev: undeclared file conflict
with libclang-rt-16-dev-wasm{32,64} on
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a
Bug 1041834 cloned as bug 1041838
> reassign -2 libclang-rt-17-dev
Bug #1041838 [libclang-rt-16-dev] libclang-rt-16-dev: undeclared file conflict
with libclang-rt-16-dev-wasm{32,64} on
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a
Bug reassigned from package 'libclang-rt-16-dev' to 'libclang-rt-17-dev'.
No longer marked as found in versions llvm-toolchain-16/1:16.0.6-5.
Ignoring request to alter fixed versions of bug #1041838 to the same values
previously set
--
1041834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041834
1041838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1041834: libclang-rt-16-dev: undeclared file conflict with libclang-rt-16-dev-wasm{32,64} on /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a
Control: clone -1 -2
Control: reassign -2 libclang-rt-17-dev
On Mon, Jul 24, 2023 at 06:45:00AM +0200, Helmut Grohne wrote:
> libclang-rt-16-dev installs
> /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm{32,64}.a,
> which are also installed by libclang-rt-16-dev-wasm{32,64} respectively.
> Trying to coinstall these packages in unstable results in an unpack
> error. I guess that these files should only be contained in the
> respective wasm packages. Don't forget to include the necessary
> Breaks+Replaces when fixing this.
The same issue exists for version 17.
Helmut
Bug#1041837: libreoffice-draw: undeclared file conflict with libreoffice-impress-nogui <= trixie: /usr/lib/libreoffice/share/config/soffice.cfg/simpress/*.xml
Package: libreoffice-draw Version: 4:7.5.5-2 Severity: serious libreoffice-draw installs /usr/lib/libreoffice/share/config/soffice.cfg/simpress/layoutlist.xml and /usr/lib/libreoffice/share/config/soffice.cfg/simpress/objectlist.xml which are also contained in libreoffice-impress-nogui from bullseye to trixie. Trying to install libreoffice-draw may result in an unpack error. Please add the necessary Breaks and Replaces. Helmut
Bug#1041836: libc6 2.36-9+deb12u1 stack smashing on some but not all amd64
Package: libc6 Version: 2.36-9 Severity: critical Justification: breaks the whole system Dear Maintainer, Installing libc6_2.36-9+deb12u1_amd64.deb on some but not all systems results in every dynamically linked program dying with a spurious report of stack smashing. Getting back to a working system required use of busybox to get bash-static and also creating a fake perl as a shell script containing exit 0 (because /bin/true is dynamic) and then busybox again to wget and dpkg install the 2.36-9. I repeated this three times to be sure. Works OK on e.g. Intel(R) Xeon(R) CPU L5520 @ 2.27GHz Stack smashing on e.g. Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Preparing to unpack .../libc6_2.36-9+deb12u1_amd64.deb ... Unpacking libc6:amd64 (2.36-9+deb12u1) over (2.36-9) ... *** stack smashing detected ***: terminated dpkg: error while cleaning up: rm command for cleanup subprocess was killed by signal (Aborted) *** stack smashing detected ***: terminated E: Sub-process /usr/bin/dpkg exited unexpectedly # ls -l *** stack smashing detected ***: terminated Aborted # Both successes and failures were on multiarch systems with i386 although that does not seem to be relevant. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (2000, 'stable-updates'), (2000, 'stable-security'), (2000, 'stable') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-10-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash-static Init: sysvinit (via /sbin/init) Versions of packages libc6 depends on: ii libgcc-s1 12.2.0-14 Versions of packages libc6 recommends: ii libidn2-0 2.3.3-1+b1 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.82 ii glibc-doc 2.36-9+deb12u1 ii libc-l10n 2.36-9+deb12u1 pn libnss-nis pn libnss-nisplus ii locales2.36-9 -- no debconf information
Bug#1041834: libclang-rt-16-dev: undeclared file conflict with libclang-rt-16-dev-wasm{32,64} on /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a
Package: libclang-rt-16-dev
Version: 1:16.0.6-5
Severity: serious
libclang-rt-16-dev installs
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm{32,64}.a,
which are also installed by libclang-rt-16-dev-wasm{32,64} respectively.
Trying to coinstall these packages in unstable results in an unpack
error. I guess that these files should only be contained in the
respective wasm packages. Don't forget to include the necessary
Breaks+Replaces when fixing this.
Helmut
Bug#1041833: libafl-persistent-ocaml: undeclared file conflict with libafl-persistent-ocaml-dev/bookworm
Package: libafl-persistent-ocaml Version: 1.4-2 Severity: serious libafl-persistent-ocaml installs /usr/lib/ocaml/afl-persistent/META, which is also installed by libafl-persistent-ocaml-dev/bookworm. As such, upgrades may result in an unpack error. If this is an intentional move, please add corresponding Breaks+Replaces. Helmut
Bug#1041832: libsequoia-octopus-librnp: undeclared file conflict with thunerbird
Package: libsequoia-octopus-librnp Version: 1.4.1-1 Severity: serious libsequoia-octopus-librnp installs /usr/lib/thunderbird/librnp.so, which happens to also be installed by thunerbird from bullseye to experimental. Since there currently are no Replaces nor Conflicts nor diversions, unpacking both yields an unpack error. Helmut
Bug#1034348: marked as done (at: autopkgtest regression on arm64: Either at.20377 doesn't exist or the content differs.)
Your message dated Mon, 24 Jul 2023 04:09:05 +0200 with message-id <20230724020905.gd12...@beskar.mdcc.cx> and subject line Re: Bug#1034348: at: autopkgtest regression on arm64 has caused the Debian Bug report #1034348, regarding at: autopkgtest regression on arm64: Either at.20377 doesn't exist or the content differs. 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.) -- 1034348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: at Version: 3.2.5-1 Severity: serious Control: tags -1 bookworm-ignore User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails on arm(64|el|hf) since September 2022 (and slightly longer on s390x). Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes are still welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/arm64/a/at/32696040/log.gz autopkgtest [01:12:17]: test basic-usage: [--- + TMPFILE=at.20377 ++ mktemp -d + WORKDIR=/tmp/tmp.7IsxZpWEJn + trap 'rm -rf /tmp/tmp.7IsxZpWEJn' 0 INT QUIT ABRT PIPE TERM ++ atq ++ wc -l + JOBS_BEFORE=0 + at now + 1 minute ++ date warning: commands will be executed using /bin/sh + echo 'echo Fri Apr 7 01:12:17 CST 2023 > /tmp/tmp.7IsxZpWEJn/at.20377' job 1 at Fri Apr 7 01:13:00 2023 + sleep 2 + test -f at.20377 + echo 'OK, at.20377 doesn'\''t exist yet; expected..' OK, at.20377 doesn't exist yet; expected.. ++ atq ++ wc -l + JOBS_AFTER=1 + [[ 1 -eq 1 ]] + echo 'OK, 1 new queued job exists..' + sleep 58 OK, 1 new queued job exists.. + grep -Fq UTC /tmp/tmp.7IsxZpWEJn/at.20377 + echo 'Either at.20377 doesn'\''t exist or the content differs.' + exit 1 Either at.20377 doesn't exist or the content differs. + rm -rf /tmp/tmp.7IsxZpWEJn autopkgtest [01:13:18]: test basic-usage: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi, Another happy at user here. Jose M Calhariz wrote: > Hi, I believe my last update fixed the problem can someone double check? That was at 3.2.5-2, right? Closing this bug: afaik nobody has been able to reproduce the issue. Therefore better to close and see what happens next. Please reopen if you feel this is not appropriate. Thanks! Bye, Joost--- End Message ---
Bug#1034348: at: autopkgtest regression on arm64
Hi, Another happy at user here. Jose M Calhariz wrote: > Hi, I believe my last update fixed the problem can someone double check? That was at 3.2.5-2, right? Closing this bug: afaik nobody has been able to reproduce the issue. Therefore better to close and see what happens next. Please reopen if you feel this is not appropriate. Thanks! Bye, Joost
Bug#1040053: gjs: autopkgtest regression: free(): invalid pointer
We can close this bug since the autopkgtests are passing now with gjs 1.76.2-3. But I am surprised that this RC bug did not block the migration of gjs 1.76.2-3 to Testing today. Thank you, Jeremy Bicha
Processed: Pending fix
Processing control commands: > tags -1 pending Bug #66 [src:scilab] scilab: depends on obsolete pcre3 library Added tag(s) pending. -- 66: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=66 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999966: Pending fix
Control: tags -1 pending Hi, I intend to upload a fix shortly, after some days reworking the package to get rid of pcre3. I post the contents of the header of the patch I wrote for further reference. This consists in: 1. making changes in the following files: - scilab/modules/spreadsheet/src/c/csvRead.c - scilab/modules/string/src/c/strsubst.c - scilab/modules/string/sci_gateway/cpp/sci_strsubst.cpp - scilab/modules/string/sci_gateway/cpp/sci_grep.cpp - scilab/modules/string/sci_gateway/cpp/sci_strindex.cpp - scilab/modules/string/sci_gateway/cpp/sci_regexp.cpp - scilab/modules/slint/includes/PCREException.hxx - scilab/modules/slint/includes/PCREMatcher.hxx - scilab/modules/slint/src/cpp/PCREException.cpp - scilab/modules/slint/src/cpp/PCREMatcher.cpp in which one needs to use the pcre2 functions. This is somewhat difficult because the upstream codes contains files like scilab/modules/string/src/c/pcre_(internal|private).c which perform the regex matches and are highly dependent on the contents of the pcre library. To avoid rewriting them, I skipped them and put all the pattern compiling and matching stuff in the above .(c|cpp|hxx) files. 2. updating the following files: - scilab/m4/pcre.m4 - scilab/configure.ac - scilab/modules/string/Makefile.am - scilab/modules/slint/Makefile.am so that the flags and libraries of pcre2 are used, not the ones of pcre3. 3. updating all the remaining files in this patch so that delimiters are not provided to the scilab functions working with regular expression patterns and modifiers like "i", "m" or "x" are not provided either, as they are not handled by the modifications I made. This implied also modifying a large part of the unit tests of these functions using the "imx" modifiers and I hope this was done well, as currently the build-time tests are not run during a Debian build. Also I plan to insert a debian/NEWS file to warn about 3. above. Best, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Bug#1041023: marked as done (libsimpleini FTBFS with googletest 1.13.0)
Your message dated Sun, 23 Jul 2023 21:29:05 + with message-id and subject line Bug#1041023: fixed in libsimpleini 4.20+dfsg-1 has caused the Debian Bug report #1041023, regarding libsimpleini FTBFS with googletest 1.13.0 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.) -- 1041023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsimpleini Version: 4.19+dfsg-1 Severity: serious Tags: ftbfs trixie sid Forwarded: https://github.com/brofield/simpleini/commit/7350fcc9228f410309734c3fb6dae2bf513cdd98 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libsimpleini.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from pch.h:8, from ts-roundtrip.cpp:1: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... --- End Message --- --- Begin Message --- Source: libsimpleini Source-Version: 4.20+dfsg-1 Done: Yangfl We believe that the bug you reported is fixed in the latest version of libsimpleini, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yangfl (supplier of updated libsimpleini 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, 15 Jul 2023 12:19:49 +0800 Source: libsimpleini Architecture: source Version: 4.20+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Yangfl Changed-By: Yangfl Closes: 1015524 1041023 Changes: libsimpleini (4.20+dfsg-1) unstable; urgency=medium . * New upstream release * Fix FTBFS with googletest 1.13.0 (Closes: #1041023) * Fix FTBFS with LTO (Closes: #1015524) * Bump Standards-Version to 4.6.2 Checksums-Sha1: c461e748a3f180173c056e17d54fc6934c84e4a9 2070 libsimpleini_4.20+dfsg-1.dsc b578aa52ca483d15e97fe3856d22df655f48aa23 50368 libsimpleini_4.20+dfsg.orig.tar.xz d412b3bc7b9b35ea886af1a8ae691c98841b 7628 libsimpleini_4.20+dfsg-1.debian.tar.xz 3dd2cc0c3e65be459083b7a5be15ab1e7b594857 7277 libsimpleini_4.20+dfsg-1_amd64.buildinfo Checksums-Sha256: 74f48c68b8243c4591506c95ddb94122b6a592ce8ae90b40a7e13e305d30ed94 2070 libsimpleini_4.20+dfsg-1.dsc 7d22e5b0dece8057346d24d516b4f8ce3e0235c2165c82f073b3c2f32d940504 50368 libsimpleini_4.20+dfsg.orig.tar.xz 7b4029fc544dca9ae22ac0bb7d5fc4b62ca93a2f69c9683baab64664431b848c 7628 libsimpleini_4.20+dfsg-1.debian.tar.xz 098148f1262f37296afef32b643f41b6f157171dc5562fe0358e05d88764cacc 7277 libsimpleini_4.20+dfsg-1_amd64.buildinfo Files: 6715ccd746237caf0b95f35db27d2f31 2070 libs optional libsimpleini_4.20+dfsg-1.dsc c7b3075e66a54a9203d2fe8fb16bd999 50368 libs optional libsimpleini_4.20+dfsg.orig.tar.xz 1f853e34cb151d5473e1bb7ed193ae3b 7628 libs optional libsimpleini_4.20+dfsg-1.debian.tar.xz 9b62acb3de07dffaa0fe78cda39f94f6 7277 libs optional libsimpleini_4.20+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmS9iaMACgkQwpPntGGC Ws5dtBAAkFenhoUqsZ56nlPWyUzY4VBI/utTNzvvaHGDtn3MiDY1LIqk3yDDwN+S vEK3i3Knt1jrmVxW701q2Q11mG15Y1nbAiv0XGyoNkW/ZDjHH60Gz7eQi4hAVXoP UYixvscd0Z2idTxkVa4ndXskSZsGVbqcgHTsQ9Im7psGoARPI1yZixuVdbS9Fyr0 ug7s2As5ohUP8Nh1NDhfNsvk6TwIUx0upj1+7PPhr35aoKlfnnc0fBGw195iqzpT C0m2IW4+5ISncGGzQ1FoE3E6oyq6tQoa+yRFrDLbmpOUdLCHMYeQZi6qMAXSjJgj nYAUtr5+UIBctAi0Xvh/tbHk94fUgUKkO/nyGa4M3UDk4nyau22+9cLzTgEHHhG/ jyTQ30KO0WCSkeD1QvlH6nn8tebJBpfFd+jEISIDhUjtSOguLA8qWyH4Iiy6kuJl zHyir1nCUDOKZDmZKjukPYJDalM/zZPiQZ6GuhFIU/dByLRUNkPlQ2lFKac0oa0T my3nxqS7TmQWYGYDR2bBzh9UZjJ3NVRLGpPLzmzf24gvz6RqQrEiZeL2W+jRdYMU PaZ+nOIPvbFvKwyXi1WpGKcA6yhrsSfjObPn+qL3H4mMVWaC1zFDMqsE9R8UPXDd 3DIMPyjUIdQUWWpr/xwfM8ccx+ox1gVrAdDpCWqUDSuPqoMXswE= =URs8 -END PGP SIGNATURE End Message ---
Bug#1041478: marked as done (pymca: depends on python2)
Your message dated Sun, 23 Jul 2023 23:10:00 +0200 (CEST) with message-id <1810496349.53361279.1690146600525.javamail.zim...@synchrotron-soleil.fr> and subject line Re: [Debian-pan-maintainers] Bug#1041478: pymca: depends on python2 has caused the Debian Bug report #1041478, regarding pymca: depends on python2 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.) -- 1041478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pymca Version: 5.8.7+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: pymca : Depends: python2:any but it is not installable Cheers, Andreas --- End Message --- --- Begin Message --- Package: pymca Version: 5.8.7+dfsg-2 now autopjgtest pass on all architectures :).--- End Message ---
Bug#1041819: mysql-8.0: CVE-2023-22058 CVE-2023-22057 CVE-2023-22056 CVE-2023-22054 CVE-2023-22053 CVE-2023-22048 CVE-2023-22046 CVE-2023-22038 CVE-2023-22033 CVE-2023-22008 CVE-2023-22007 CVE-2023-22
Source: mysql-8.0 Version: 8.0.33-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for mysql-8.0. CVE-2023-22058[0]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: DDL). Supported versions that are affected are | 8.0.33 and prior. Difficult to exploit vulnerability allows high | privileged attacker with network access via multiple protocols to | compromise MySQL Server. Successful attacks of this vulnerability | can result in unauthorized ability to cause a hang or frequently | repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score | 4.4 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22057[1]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Replication). Supported versions that are | affected are 8.0.33 and prior. Easily exploitable vulnerability | allows high privileged attacker with network access via multiple | protocols to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized ability to cause a hang or | frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 | Base Score 4.9 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22056[2]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.33 and prior. Easily exploitable vulnerability | allows high privileged attacker with network access via multiple | protocols to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized ability to cause a hang or | frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 | Base Score 4.9 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22054[3]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.33 and prior. Easily exploitable vulnerability | allows high privileged attacker with network access via multiple | protocols to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized ability to cause a hang or | frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 | Base Score 4.9 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22053[4]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Client programs). Supported versions that are affected | are 5.7.42 and prior and 8.0.33 and prior. Difficult to exploit | vulnerability allows low privileged attacker with network access via | multiple protocols to compromise MySQL Server. Successful attacks | of this vulnerability can result in unauthorized ability to cause a | hang or frequently repeatable crash (complete DOS) of MySQL Server | and unauthorized read access to a subset of MySQL Server accessible | data. CVSS 3.1 Base Score 5.9 (Confidentiality and Availability | impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H). CVE-2023-22048[5]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Pluggable Auth). Supported versions that are | affected are 8.0.33 and prior. Difficult to exploit vulnerability | allows low privileged attacker with network access via multiple | protocols to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized read access to a subset of | MySQL Server accessible data. CVSS 3.1 Base Score 3.1 | (Confidentiality impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N). CVE-2023-22046[6]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Optimizer). Supported versions that are | affected are 8.0.33 and prior. Easily exploitable vulnerability | allows high privileged attacker with network access via multiple | protocols to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized ability to cause a hang or | frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 | Base Score 4.9 (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CVE-2023-22038[7]: | Vulnerability in the MySQL Server product of Oracle MySQL | (component: Server: Security: Privileges). Supported versions that | are affected are 8.0.33 and prior. Easily exploitable vulnerability | allows high privileged attacker with network access via multiple | protocols to compromise MySQL Server. Successful attacks of this | vulnerability can result in unauthorized update, insert or delete | access to some of MySQL Server accessible data. CVSS 3.1 Base Score | 2.7 (Integrity impacts). CVSS
Bug#1036113: libpurple0: license conflict with libsasl2
On Wed, 28 Jun 2023 10:14:00 +0200 Bastian Germann wrote: > Am 28.06.23 um 04:42 schrieb Richard Laager: > > What is the remaining instance of RSA-MD licensed code after #767? > > https://github.com/cyrusimap/cyrus-sasl/issues/769 Fyi: that issue has now been closed with https://github.com/cyrusimap/cyrus-sasl/pull/770 -- Cheers, Evangelos PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19 signature.asc Description: This is a digitally signed message part
Bug#1041814: python-mechanicalsoup: CVE-2023-34457
Source: python-mechanicalsoup Version: 0.10.0-6 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 0.10.0-4 Hi, The following vulnerability was published for python-mechanicalsoup. The severity choosen for the bugreport might be slightly overrated, but I am aiming to understand if the package is actively maintained and might rather be removed from testing if not updated to a more recent version. CVE-2023-34457[0]: | MechanicalSoup is a Python library for automating interaction with | websites. Starting in version 0.2.0 and prior to version 1.3.0, a | malicious web server can read arbitrary files on the client using a | `` inside HTML form. All users of | MechanicalSoup's form submission are affected, unless they took very | specific (and manual) steps to reset HTML form field values. Version | 1.3.0 contains a patch for this issue. 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-2023-34457 https://www.cve.org/CVERecord?id=CVE-2023-34457 [1] https://github.com/MechanicalSoup/MechanicalSoup/security/advisories/GHSA-x456-3ccm-m6j4 [2] https://github.com/MechanicalSoup/MechanicalSoup/commit/d57c4a269bba3b9a0c5bfa20292955b849006d9e Regards, Salvatore
Processed: python-mechanicalsoup: CVE-2023-34457
Processing control commands: > found -1 0.10.0-4 Bug #1041814 [src:python-mechanicalsoup] python-mechanicalsoup: CVE-2023-34457 Marked as found in versions python-mechanicalsoup/0.10.0-4. -- 1041814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041751: marked as done (libxml-light-ocaml-dev: undeclared file conflict with libxml-light-ocaml (<= 2.4-1+b4) on /usr/lib/ocaml/xml-light/META)
Your message dated Sun, 23 Jul 2023 20:03:23 + with message-id and subject line Bug#1041751: fixed in xml-light 2.5-2 has caused the Debian Bug report #1041751, regarding libxml-light-ocaml-dev: undeclared file conflict with libxml-light-ocaml (<= 2.4-1+b4) on /usr/lib/ocaml/xml-light/META 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.) -- 1041751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxml-light-ocaml-dev Version: 2.5-1 Severity: serious Control: affects -1 + libxml-light-ocaml libxml-light-ocaml-dev introduces an undeclared file conflict with libxml-light-ocaml up to version 2.4-1+b4 on the file /lib/ocaml/xml-light/META. This may result in an unpack error at package extraction time. Do you miss Breaks + Replaces here? Helmut --- End Message --- --- Begin Message --- Source: xml-light Source-Version: 2.5-2 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of xml-light, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated xml-light package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2023 21:33:15 +0200 Source: xml-light Architecture: source Version: 2.5-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1041751 Changes: xml-light (2.5-2) unstable; urgency=medium . * Team upload * META was wrongly in libxml-light-ocaml-dev (Closes: #1041751) Checksums-Sha1: 4963a169340d007ab00ab812165e6991abb5f174 1827 xml-light_2.5-2.dsc 91065090cc0dc5e12d30ee8ecd5424933f854bc2 3692 xml-light_2.5-2.debian.tar.xz Checksums-Sha256: d3470524e4538d04bf0993fff6be8b30b27e3fdcc460162830864c5162e5b466 1827 xml-light_2.5-2.dsc 8f176cbb523ef9f4344b2057fcf7b98b74f5c900eb68483f5f9eba7668ca531a 3692 xml-light_2.5-2.debian.tar.xz Files: ce876b46e83f0ea9efb7a91f308979a2 1827 ocaml optional xml-light_2.5-2.dsc f8deec4f13e43aea48594c6306e79383 3692 ocaml optional xml-light_2.5-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmS9gRoSHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBfeMH/iv+Ae0qBQaqlWMb8dHdTU4y7+e1k3OL LfhCI7ns4IWWPjuFlHlzfKWv3axP2Pss+9AV9hmz4y/x70cQmZ6zEWF04r7hIyuK +fSlrl+Qu/Ija3ppwUHsaD0B2WI0aMhrE9toivpHN/+Nu1dAWZnx1jrhtriPSSaw 4JHi1+x6b/3khpokKUonsI1ssXoDkgHMOolh8afsv5jlVecL3LhDQzsHAwDKAtGR nDfxlyJpAvRSodtCMkNrSlz5AsGTcO1ByvIclZBMrKvVFooc8NvafD55u518ebHe 3uuQg4ypxxIoKrJdO4lbnC6it63vaU7cnChBj3m1c7XhUKwN9d6kumE= =IRJD -END PGP SIGNATURE End Message ---
Bug#1041783: marked as done (ocaml-cry FTBFS: Error (alert deprecated): SSLv23)
Your message dated Sun, 23 Jul 2023 19:57:40 + with message-id and subject line Bug#1041783: fixed in ocaml-cry 0.6.7-2 has caused the Debian Bug report #1041783, regarding ocaml-cry FTBFS: Error (alert deprecated): SSLv23 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.) -- 1041783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-cry Version: 0.6.7-1 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/logs.php?pkg=ocaml-cry=0.6.7-1%2Bb3 ... Command [10] exited with code 2: $ (cd _build/default && /usr/bin/ocamlc.opt -w @1..3@5..28@30..39@43@46..47@49..57@61..62-40 -strict-sequence -strict-formats -short-paths -keep-locs -g -bin-annot -I src/.cry.objs/byte -I /usr/lib/ocaml/ssl -no-alias-deps -opaque -open Cry__ -o src/.cry.objs/byte/cry__Cry_https.cmo -c -impl src/cry_https.ml) File "src/cry_https.ssl.ml", line 29, characters 33-43: Error (alert deprecated): SSLv23 SSL 2.0 was deprecated in 2011 by RFC 6176. make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 This might have been caused by the new ocaml-ssl? --- End Message --- --- Begin Message --- Source: ocaml-cry Source-Version: 0.6.7-2 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of ocaml-cry, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml-cry package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2023 21:27:06 +0200 Source: ocaml-cry Architecture: source Version: 0.6.7-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1041783 Changes: ocaml-cry (0.6.7-2) unstable; urgency=medium . * Team upload * Use ocaml_dune DH buildsystem (Closes: #1041783) * Bump Standards-Version to 4.6.2 Checksums-Sha1: 54cb8dd9a0e9593e5a5a52ac4d7e61afb5f6d380 1788 ocaml-cry_0.6.7-2.dsc ab3879fd3e233d6cc99d801c2d7d4aa0109f9e8f 2980 ocaml-cry_0.6.7-2.debian.tar.xz Checksums-Sha256: 5f2e2c413e5ae1121758518a388e09c80e7c7a2af9c5692557eeb1b7ef03a078 1788 ocaml-cry_0.6.7-2.dsc fbb5cae03bf4ea2780a47a69d2c5780556c5a4d8b6387ad25c71cf695fa8f5e4 2980 ocaml-cry_0.6.7-2.debian.tar.xz Files: f79273d3d54e2c2424cce5ec3c0f9a92 1788 ocaml optional ocaml-cry_0.6.7-2.dsc 9feef65f7f41470ffed3b2e3582c82f2 2980 ocaml optional ocaml-cry_0.6.7-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmS9f4gSHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBjn8H/RwUxc+WyGUxnJk6SvP8IkLlbmmcpKlZ j3KLTrg1VHi3LJlIBRqJXeAiGLMw89Vvtj3Jv9QSw+nlGSrmVRD3gI9yxG7K8fho OV9doDIFqVyFRQIX1uo3Crbl3B0QZaOclPdkKWe7CS/3dMqlNXnHhEWibqwGtHXh rLqupUghY1pTEsrLMuRs0QYSrh6bUKJeHSlGXwX5FC6YkX6KI1V6dRVG/Hrh2BT+ T6upgwm+/I/0M5Sa+jRbgB6uGjKYpKgxyn5mso5cTbQYeVagFCrv7gEYO0iAZ470 S2bZ2CJeSCNl2bCAaiFZjQYl6xpu4ktam3D50isDw/euvrGZC3GVTu0= =6WxK -END PGP SIGNATURE End Message ---
Bug#1041384: librust-derive-builder-dev: impossible to install
Version: 0.12.0-1 rust-derive-builder has now been updated to match rust-derive-builder-core.
Bug#1041758: marked as done (libcudf-dev is not installable due to bogus janitor change)
Your message dated Sun, 23 Jul 2023 19:52:20 + with message-id and subject line Bug#1041758: fixed in cudf 0.10-2 has caused the Debian Bug report #1041758, regarding libcudf-dev is not installable due to bogus janitor change 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.) -- 1041758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcudf-dev Version: 0.10-1 Severity: serious X-Debbugs-Cc: team+jani...@tracker.debian.org The following packages have unmet dependencies: libcudf-dev : Depends: libtinfo6 (= 6.1+20181013-2+deb10u2) but 6.4+20230625-1 is to be installed Depends: libncurses-dev (= 6.1+20181013-2+deb10u2) but 6.4+20230625-1 is to be installed This is due to: https://salsa.debian.org/ocaml-team/cudf/-/merge_requests/2 cudf (0.10-1) unstable; urgency=medium ... [ Debian Janitor ] ... * Remove constraints unnecessary since buster (oldstable): + libcudf-dev: Replace dependency on transitional package libncurses5-dev with replacement libtinfo6 (= 6.1+20181013-2+deb10u2), libncurses-dev (= 6.1+20181013-2+deb10u2) in Depends. ... I haven't checked whether the replacement package names are correct, but the = dependences hardcoded in debian/control are clearly wrong. --- End Message --- --- Begin Message --- Source: cudf Source-Version: 0.10-2 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of cudf, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated cudf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2023 21:14:07 +0200 Source: cudf Architecture: source Version: 0.10-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1041758 Changes: cudf (0.10-2) unstable; urgency=medium . * Team upload * Fix bogus dependencies in libcudf-dev (Closes: #1041758) Checksums-Sha1: 7c670662ab6f56d6e84992387655c887ffcd00a5 1977 cudf_0.10-2.dsc 3c1b6ba13a60d597a725718ea4eef0b8fd9c8cda 5316 cudf_0.10-2.debian.tar.xz Checksums-Sha256: 5c586adf53dcb19a6cc8d27000f1b365e4049487eab3353d5a8b004f7f96d4c0 1977 cudf_0.10-2.dsc dfdd4d1ff9b795d89271a24c2e69518ccc58b3fe7c091c7a87741b340cf13e28 5316 cudf_0.10-2.debian.tar.xz Files: 4c73107bd75bdde8f0700afbdf9d6fcc 1977 devel optional cudf_0.10-2.dsc 7bbbab579d2536ed1374dcb9511f3522 5316 devel optional cudf_0.10-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmS9fH4SHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCByjAH/1SfYGZ8UmGO6CswB64MUToQIcmXKuGd iK4zXK2tEpTUwOyJb6a0U9eBMuB79oXh+sfAypBTWUFHqX0cUhf5DkLyV4BzLXik r1omdaadFqmoCbGBopR17T5fX9ulywRvga9RF710RqqF/z5Nsfh6gz7wUJuDpOBo +UxKCGVsTkongJOj4ATMWAht/tvlCa/tdQojhMAIYaxQFNE0K1CfmDRBkR/un/aH OfuJpGLm1ouhRKkQCWbaz8gzpUVxju4yDO3UzOjrcvQQjnvLGVL8rFp6YcQA9aI6 HSZiPT9AJ+nttocQZzOoIX9HIUHMO8rxAiZSTY7lqq+5tPMwSilqZZg= =wGE6 -END PGP SIGNATURE End Message ---
Bug#1040718: marked as done (fclib: autopkgtest failure due to new CMake deprecation warning)
Your message dated Sun, 23 Jul 2023 19:53:46 + with message-id and subject line Bug#1040718: fixed in fclib 3.1.0+dfsg-3 has caused the Debian Bug report #1040718, regarding fclib: autopkgtest failure due to new CMake deprecation warning 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.) -- 1040718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fclib Version: 3.1.0+dfsg-2 Severity: important User: roehl...@debian.org Usertags: cmake3.27 Dear maintainer, your package fclib will soon experience autopkgtest failures because the new CMake release 3.27 will issue a deprecation warning on stderr if cmake_minimum_required() asks for compatibility with CMake 3.4 or older. You can check for the exact failure on the cmake pseudo-excuses page from experimental: https://qa.debian.org/excuses.php?experimental=1=cmake For a more in-depth discussion, kindly refer to the debian-devel thread: https://lists.debian.org/debian-devel/2023/06/msg00150.html Cheers Timo --- End Message --- --- Begin Message --- Source: fclib Source-Version: 3.1.0+dfsg-3 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of fclib, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated fclib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2023 21:28:17 +0200 Source: fclib Architecture: source Version: 3.1.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Timo Röhling Closes: 1040718 Changes: fclib (3.1.0+dfsg-3) unstable; urgency=medium . * Team upload. * Fix autopkgtest regression due to CMake warning (Closes: #1040718) Checksums-Sha1: c6d709c54acd5f904b4eab1dfc1ac1dde738a492 2013 fclib_3.1.0+dfsg-3.dsc daad15ffca2242891c50d226ec213beb9dca8b6a 10200 fclib_3.1.0+dfsg-3.debian.tar.xz 4ff6d3c7dedbc54e5c48cfab3c9263bc6e4f32dd 8427 fclib_3.1.0+dfsg-3_amd64.buildinfo Checksums-Sha256: 6b0bc96d16b5843dd7143388afc518575722543e138b94486e71d9b486ca6580 2013 fclib_3.1.0+dfsg-3.dsc 8787287b4bc8422c997a460b6e8310e5c99d2b3c11b1c8dc0b83842f96b512b5 10200 fclib_3.1.0+dfsg-3.debian.tar.xz b6b6de9e1f329a65666e1fdeb91fdd6546a8ada28e5a60620558838668bad17c 8427 fclib_3.1.0+dfsg-3_amd64.buildinfo Files: 228382f9324e28f7f751e8f258698297 2013 science optional fclib_3.1.0+dfsg-3.dsc 58b3e7c65782f9cd224d0b1ae71978f8 10200 science optional fclib_3.1.0+dfsg-3.debian.tar.xz 0e0e8722a58b567f85617e96abdf5be4 8427 science optional fclib_3.1.0+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmS9f7IUHHJvZWhsaW5n QGRlYmlhbi5vcmcACgkQ+C8H+466LVn1ngv9EBxfDikMgRNr0DvA/7/yuQrhbjim oQc7F7LGv8VjwYFqO6w3D1fLgv2TRGul/9TC9PjbVylapC0JDSqY1dClo4LY6dPa nzJ2gIoS7WusA+MG+9OrwoLSyEQQ2POCwO6haY74UuymcRF5hICogtt4yx5ux0ZT T9I9h4AEkopIvAJfAN9666EwgvpDkRlluAb9FtM9M5fGxtNvoZZvbR+SknGEWwNx o11+LXR12QyZeukmQL5WPql+sHdJZktGrAvJOKYJ1lgxwHQ+cn825C+owJmifslS yne6c3LK8/Gey/ko+Lm1GV/dEPn5n2JUE36TBLcD9KJ678AUUSxhpMO8XqrdyTkE AGwGCRvfernn6Cn0oEfnkE5cd8oBvEGCYvMDbeJZO1qSTke2BcCsnQayE5FHTLUE AVFJHp+7otkInGl0vCPtbCRztuu+CetAWCzqx9MDyjWjHBn4autjp+uPxmIpMG5J ocLbzyJAMbhQ5k4hJwdJJNilXXONHXGa9Unh =1jn4 -END PGP SIGNATURE End Message ---
Bug#1040735: ms-gsl: autopkgtest failure due to new CMake deprecation warning
Hi, On Sun, 09 Jul 2023 23:03:07 +0200 roehl...@debian.org wrote: your package ms-gsl will soon experience autopkgtest failures because the new CMake release 3.27 will issue a deprecation warning on stderr if cmake_minimum_required() asks for compatibility with CMake 3.4 or older. I just did an NMU to DELAY/3. Please tell if you want me to cancel. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ diff --git a/debian/changelog b/debian/changelog index 9cb2e41..117793e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +ms-gsl (4.0.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix autopkgtest regression due to CMake warning (Closes: #1040735) + + -- Timo Röhling Sun, 23 Jul 2023 21:10:48 +0200 + ms-gsl (4.0.0-2) unstable; urgency=medium * Ignore -Wpsabi warnings on PowerPC. diff --git a/debian/patches/1040735.patch b/debian/patches/1040735.patch new file mode 100644 index 000..f580449 --- /dev/null +++ b/debian/patches/1040735.patch @@ -0,0 +1,18 @@ +From: =?utf-8?q?Timo_R=C3=B6hling?= +Date: Sun, 23 Jul 2023 21:10:02 +0200 +Subject: Fix for #1040735 + +--- + tests/CMakeLists.txt | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt +index 845ee26..b75648e 100644 +--- a/tests/CMakeLists.txt b/tests/CMakeLists.txt +@@ -1,4 +1,4 @@ +-cmake_minimum_required(VERSION 3.0.2) ++cmake_minimum_required(VERSION 3.13) + + project(GSLTests CXX) + enable_testing() # again, for support standalone testing diff --git a/debian/patches/series b/debian/patches/series index 235bb02..5eb1697 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1 +1,2 @@ PowerPC-warn-suppression.patch +1040735.patch diff --git a/debian/tests/smoke b/debian/tests/smoke index bb52f69..7e6f409 100755 --- a/debian/tests/smoke +++ b/debian/tests/smoke @@ -8,7 +8,7 @@ BASH_XTRACEFD=1 set -x tee CMakeLists.txt < signature.asc Description: PGP signature
Processed: forwarded 1039613 https://github.com/nmap/nmap/issues/2685
Processing commands for cont...@bugs.debian.org: > forwarded 1039613 https://github.com/nmap/nmap/issues/2685 Bug #1039613 [src:nmap, src:udptunnel] nmap breaks udptunnel autopkgtest: UDPTunnel communication failed Set Bug forwarded-to-address to 'https://github.com/nmap/nmap/issues/2685'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1039613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041758: marked as pending in cudf
Control: tag -1 pending Hello, Bug #1041758 in cudf 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/ocaml-team/cudf/-/commit/b71eebdae4437b359876ead63abad1a156978fd6 Fix bogus dependencies in libcudf-dev (Closes: #1041758) (this message was generated automatically) -- Greetings https://bugs.debian.org/1041758
Bug#1041299: marked as done (rawloader: multiple undeclared file conflicts)
Your message dated Sun, 23 Jul 2023 19:17:18 + with message-id and subject line Bug#1041299: fixed in rust-rawloader 0.37.1-2 has caused the Debian Bug report #1041299, regarding rawloader: multiple undeclared file conflicts 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.) -- 1041299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rawloader Version: 0.37.1-1 Severity: serious rawloader contains multiple undeclared file conflicts usr/bin/identify is contained in graphicsmagick-imagemagick-compat. usr/bin/benchmark is contained in libplucene-perl. In general, these names are fairly generic. I recommend renaming them rather than expressing these conflicts. Also adding manual pages would be good. Helmut --- End Message --- --- Begin Message --- Source: rust-rawloader Source-Version: 0.37.1-2 Done: Fab Stz We believe that the bug you reported is fixed in the latest version of rust-rawloader, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fab Stz (supplier of updated rust-rawloader 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: Sun, 23 Jul 2023 20:14:55 +0200 Source: rust-rawloader Architecture: source Version: 0.37.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Fab Stz Closes: 1041299 Changes: rust-rawloader (0.37.1-2) unstable; urgency=medium . * Don't build binaries. Closes: #1041299 Checksums-Sha1: 1bda396ede06cbe0138f7fdce1ed8b2589ddaf0a 2430 rust-rawloader_0.37.1-2.dsc 0b3a4ee73eeb65bd9d8a8e322f55eb9140820317 2164 rust-rawloader_0.37.1-2.debian.tar.xz 7c3d5114c6128712668fd02bf31a76653c3840ba 12163 rust-rawloader_0.37.1-2_source.buildinfo Checksums-Sha256: fb9e90fcd7d59582a83f7fd6e72334072dfbcbfd3fbc227ff20e95e54f7af266 2430 rust-rawloader_0.37.1-2.dsc d7013e370142e1b8a85934ba56424d8184f76655073c58c207a1d2ead331b86d 2164 rust-rawloader_0.37.1-2.debian.tar.xz 3d7c9a42dccfd0739cd77bfd8ef4642c6e97eba00434f34309312a0b9ed13aa6 12163 rust-rawloader_0.37.1-2_source.buildinfo Files: cda5491708eaa3ff01ddd9d402929009 2430 rust optional rust-rawloader_0.37.1-2.dsc c9606b0c5edfe441dfd444da4b7be2a6 2164 rust optional rust-rawloader_0.37.1-2.debian.tar.xz a4a3fafb3a92ade9075d3ba8dad82dc3 12163 rust optional rust-rawloader_0.37.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmS9biIACgkQfmUo2nUv G+FbuQ/+K0/yCGbwnavt8GxukYZqDhJAVDYl9vCQoTSoOamXIeRflzt6oA30sfo8 sWXhYTcV38U203UhlTJovskLw0J3kQbXZqRtzRhBeBu5DZRfY7M3rbGlbluleSCL Bhlg5RI8F30yz2w+OpVJ2clFCVSbV2gzmRaAhBRrO/P38KTgSTY2Po++j93oy3hC zbIQ4dkUBRAsBpGhPJTDszL758rqGn6Hb2k7lbBbvu0gKnrFtDlIKawAvnWohEVs KguVIaGcDS+gEMDNE4DP9v6NeopgLurAfEd/NgNvEkVjP8ZQAtSgepg00SKVhjFP szZkHg4zJ0YxOZ5yabpdeDAO+NNsf0qO/8aZfB8nVE6f3d8evyRZl18wJtXV7jCi k8MjGtYI/hsC7QEAmF6vwA3wQsPRWUHnP58XBM/4WGnG9n9DI1MyhoGFYmFZHZqD vSkRZcvP+d1CXOGFHGVwASK+opRpcbAhWfHn5jBsZj8RXEtmaOcgA3//dGFTgKhL u68P2itt2ass+/GVMLTRHKdDPUpan1uTQN/I/S2s4+4hCk3iLX30THwjyNNWuPaR dbcweNbfRcrAOfk8s02kdy+WyJP5ikigz193tznXj2BebPld5YHxw5Sbfg5BLRmW SZ8hkahzj/Cx/C1+0Y9d4rWJfpoIIejnf4kMtDyXzH4lK0qgCJs= =EYr+ -END PGP SIGNATURE End Message ---
Processed: Bug#1041758 marked as pending in cudf
Processing control commands: > tag -1 pending Bug #1041758 [libcudf-dev] libcudf-dev is not installable due to bogus janitor change Added tag(s) pending. -- 1041758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041808: cura-engine: Several unit test failures on i686
Here's an excerpt of the failing tests: test 21 Start 21: PolygonConnectorTest 21: Test command: cura-engine/obj-i686-linux-gnu/PolygonConnectorTest 21: Working Directory: cura-engine/tests/ 21: Test timeout computed to be: 1500 5: [ OK ] InfillTestcases/InfillTest.TestInfillSanity/InfillTestParameters_P6_Z0_C1_L600__2 (5 ms) 5: [ RUN ] InfillTestcases/InfillTest.TestInfillSanity/InfillTestParameters_P6_Z0_C0_L800__2 6: [ OK ] AllCombinations/AddTravelTest.NoRetractionIfDisabled/62 (4 ms) 6: [ RUN ] AllCombinations/AddTravelTest.NoRetractionIfDisabled/63 21: [==] Running 6 tests from 1 test suite. 21: [--] Global test environment set-up. 21: [--] 6 tests from PolygonConnectorTest 21: [ RUN ] PolygonConnectorTest.getBridgeNestedSquares 21: ./tests/utils/PolygonConnectorTest.cpp:71: Failure 21: Expected equality of these values: 21: LinearAlg2D::getDist2BetweenLineSegments(bridge->a.from_point, bridge->a.to_point, bridge->b.from_point, bridge->b.to_point) 21: Which is: 9801 21: 100 * 100 21: Which is: 1 21: The bridges should be spaced 1 line width (100 units) apart. 21: [ FAILED ] PolygonConnectorTest.getBridgeNestedSquares (0 ms) 21: [ RUN ] PolygonConnectorTest.getBridgeAdjacentSquares 21: ./tests/utils/PolygonConnectorTest.cpp:91: Failure 21: Expected equality of these values: 21: LinearAlg2D::getDist2BetweenLineSegments(bridge->a.from_point, bridge->a.to_point, bridge->b.from_point, bridge->b.to_point) 21: Which is: 9801 21: 100 * 100 21: Which is: 1 21: The bridges should be spaced 1 line width (100 units) apart. test 18 Start 18: IntPointTest 18: Test command: cura-engine/obj-i686-linux-gnu/IntPointTest 18: Working Directory: cura-engine/tests/ 18: Test timeout computed to be: 1500 18: [==] Running 1 test from 1 test suite. 18: [--] Global test environment set-up. 18: [--] 1 test from IntPointTest 18: [ RUN ] IntPointTest.TestRotationMatrix 18: ./tests/utils/IntPointTest.cpp:24: Failure 18: Expected equality of these values: 18: rotated_in_place 18: Which is: (11,20) 18: rotated_in_place_2 18: Which is: (10,20) 18: Matrix composition with translate and rotate failed. 18: [ FAILED ] IntPointTest.TestRotationMatrix (0 ms) 18: [--] 1 test from IntPointTest (0 ms total) 18: 18: [--] Global test environment tear-down 18: [==] 1 test from 1 test suite ran. (0 ms total) 18: [ PASSED ] 0 tests. 18: [ FAILED ] 1 test, listed below: 18: [ FAILED ] IntPointTest.TestRotationMatrix 18: 18: 1 FAILED TEST 15/26 Test #18: IntPointTest .***Failed0.00 sec [==] Running 1 test from 1 test suite. [--] Global test environment set-up. [--] 1 test from IntPointTest [ RUN ] IntPointTest.TestRotationMatrix ./tests/utils/IntPointTest.cpp:24: Failure Expected equality of these values: rotated_in_place Which is: (11,20) rotated_in_place_2 Which is: (10,20) Matrix composition with translate and rotate failed. [ FAILED ] IntPointTest.TestRotationMatrix (0 ms) [--] 1 test from IntPointTest (0 ms total) [--] Global test environment tear-down [==] 1 test from 1 test suite ran. (0 ms total) [ PASSED ] 0 tests. [ FAILED ] 1 test, listed below: [ FAILED ] IntPointTest.TestRotationMatrix
Bug#1041808: cura-engine: Several unit test failures on i686
Source: cura-engine Version: 5.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Usertags: i686 Forwarded: https://github.com/Ultimaker/CuraEngine/issues/1192 X-Debbugs-Cc: onit...@gmail.com On i686, CuraEngine 5.x fails to build due to failing unit tests. This is a longstanding issue, going back to 4.4, where it was fixed by adding a larger tolerance to test values. However, the issue was not investigated thoroughly and returns in 5.0 with more failing unit tests. The root cause of these failures are rounding errors on i686, where the x87 FPU produces different results than floating point units in other processors. These differences are tiny, and usually not more than a few ULPs. CuraEngine uses integer math in most places, but resorts to double-precision floating-point calculations in certain cases. Afterwards, the results are truncated to 64-bit integers (C type long long), and subsequent calculation is done on the integer values. Truncation (aka round-toward-zero) is often ok and works fine on amd64 (SSE2 floating-point math) and other CPUs, but produces different results on the x87 FPU. When truncating, these produce off-by-one errors in many cases, and the these errors can accumulate and lead to huge differences in the unit tests. By strategically adding explicit rounding (round-to-nearest) in the right places, these errors can be eliminated. While this will produce subtly different results in some cases, it is arguably more correct than always truncating. And at least on amd64, there is no performance difference between truncation and rounding: The SSE2 CVTTSD2SI and CVTSD2SI instructions have the same performance. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-2-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 -- no debconf information
Processed: rm
Processing commands for cont...@bugs.debian.org: > reassign 1026433 ftp.debian.org Bug #1026433 [src:mercurial-buildpackage] RM: mercurial-buildpackage -- RoQA; no users left Bug reassigned from package 'src:mercurial-buildpackage' to 'ftp.debian.org'. No longer marked as found in versions mercurial-buildpackage/0.10.1+nmu2. Ignoring request to alter fixed versions of bug #1026433 to the same values previously set > severity 1026433 normal Bug #1026433 [ftp.debian.org] RM: mercurial-buildpackage -- RoQA; no users left Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1026433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037603: marked as done (civetweb: ftbfs with GCC-13)
Your message dated Sun, 23 Jul 2023 18:07:10 + with message-id and subject line Bug#1037603: fixed in civetweb 1.16+dfsg-1 has caused the Debian Bug report #1037603, regarding civetweb: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:civetweb Version: 1.15+dfsg-4 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/civetweb_1.15+dfsg-4_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/civetweb-targets.cmake -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/civetweb-targets-none.cmake -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/civetweb-config.cmake -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/civetweb-config-version.cmake -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/FindLibDl.cmake -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/FindLibRt.cmake -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/FindWinSock.cmake -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb.so.1.15.0 -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb.so.1 -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb.so -- Installing: /<>/debian/tmp/usr/include/civetweb.h -- Installing: /<>/debian/tmp/usr/bin/civetweb -- Set runtime path of "/<>/debian/tmp/usr/bin/civetweb" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so.1.15.0 -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so.1 -- Set runtime path of "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so.1.15.0" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so -- Installing: /<>/debian/tmp/usr/include/CivetServer.h make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_install -O--buildsystem=cmake dh_installdocs -O--buildsystem=cmake dh_installchangelogs -O--buildsystem=cmake dh_installman -O--buildsystem=cmake dh_installsystemduser -O--buildsystem=cmake dh_perl -O--buildsystem=cmake dh_link -O--buildsystem=cmake dh_strip_nondeterminism -O--buildsystem=cmake dh_compress -O--buildsystem=cmake dh_fixperms -O--buildsystem=cmake dh_missing -O--buildsystem=cmake dh_dwz -a -O--buildsystem=cmake dwz: debian/libcivetweb1/usr/lib/x86_64-linux-gnu/libcivetweb.so.1.15.0: DWARF compression not beneficial - old size 164499 new size 167095 dwz: debian/libcivetweb1/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so.1.15.0: DWARF compression not beneficial - old size 297647 new size 300459 dh_strip -a -O--buildsystem=cmake dh_makeshlibs -a -O--buildsystem=cmake dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libcivetweb1/DEBIAN/symbols doesn't match completely debian/libcivetweb1.symbols.amd64 --- debian/libcivetweb1.symbols.amd64 (libcivetweb1_1.15+dfsg-4_amd64) +++ dpkg-gensymbols0Ys4Zu 2023-05-22 02:14:50.802139796 + @@ -61,15 +61,20 @@ _ZN21CivetWebSocketHandlerD0Ev@Base 1.13 _ZN21CivetWebSocketHandlerD1Ev@Base 1.13
Processed: Re: Bug#825098: pcb2gcode: new upstream homepage and new release (1.2.3)
Processing control commands: > severity -1 serious Bug #825098 [src:pcb2gcode] pcb2gcode: new upstream homepage and new release (1.2.3) Severity set to 'serious' from 'wishlist' -- 825098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041803: hyperspy: FTBFS test_image fails
Package: hyperspy Version: 1.7.3-1 Severity: serious hyperspy currently FTBFS with several failing tests: https://launchpadlibrarian.net/678551154/buildlog_ubuntu-mantic-amd64.hyperspy_1.7.3-1_BUILDING.txt.gz
Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]
Is this reproducible for you? If you have experience with building from source, upstream has proposed the following patch. Otherwise, I could build a test package for you. diff --git a/ntpd/nts_cookie.c b/ntpd/nts_cookie.c index 166d0230f..a73955fb7 100644 --- a/ntpd/nts_cookie.c +++ b/ntpd/nts_cookie.c @@ -382,6 +382,9 @@ bool nts_unpack_cookie(uint8_t cookie, int cookielen, if (NULL == cookie_ctx) return false; /* We aren't initialized yet. */ + + if (0 == nts_nKeys) + return false; /* No cookies. We are not an NTS server. */ /* We may get garbage from the net */ if (cookielen > NTS_MAX_COOKIELEN) return false; -- Richard
Bug#1041792: httpie: phones home for version check
Package: httpie
Followup-For: Bug #1041792
Further testing with help of people on IRC revealed the following information:
If you simply install httpie, and don't create any config directories, it will
perform the version check every single time you run httpie.
If you create the directory ~/.config/httpie/ then httpie will download the
file https://packages.httpie.io/latest.json and save it in
~/.config/httpie/version_info.json
If you delete ~/.config/httpie/version_info.json and create the file
~/.config/httpie/config.json with this content:
{
"disable_update_warnings": true
}
then the version checks stop and ~/.config/httpie/version_info.json stops being
created. This is poorly documented upstream.
I don't know if it is a permanent solution, or if it only temporarily stops
this. I'm providing this as a workaround before it is fixed in the debian
package.
In any case, this behavior should be patched out in httpie as distributed by
debian.
Bug#1041792: httpie: phones home for version check
Package: httpie Version: 3.2.1-1 Severity: serious Dear Maintainer, httpie makes a request to packages.httpie.io every time you start it. It does this presumably to check for a newer version, which is irrelevant in debian. It also smells like a policy violation, though I didn't find an exact paragraph that covers this. This can be seen in the source code here: https://sources.debian.org/src/httpie/3.2.1-1/httpie/internal/update_warnings.py/?hl=16#L16 Upstream has some documentation here: https://httpie.io/docs/cli/update-warnings Please remove this update check, not only is it irrelevant in debian, but it also causes a mess in logs due to unintended DNS requests. thanks -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages httpie depends on: ii python3 3.11.2-1+b1 ii python3-charset-normalizer 3.0.1-2 ii python3-defusedxml 0.7.1-2 ii python3-multidict 6.0.4-1+b1 ii python3-pip 23.0.1+dfsg-1 ii python3-pkg-resources 66.1.1-1 ii python3-pygments2.14.0+dfsg-1 ii python3-requests2.28.1+dfsg-1 ii python3-requests-toolbelt 0.10.1-1 ii python3-rich13.3.1-1 ii python3-socks 1.7.1+dfsg-1 httpie recommends no packages. httpie suggests no packages. -- no debconf information
Bug#1027215: Proposed RM: theano, keras, deepnano -- broken by numpy 1.24, theano mostly abandoned upstream
Control: reopen -1 1026539 theano has been mostly abandoned upstream since 2018. (The Aesara fork is not abandoned, but includes interface changes including the import name, so would break reverse dependencies not specifically altered for it.) It is currently broken (FTBFS due to multiple test failures), probably by numpy 1.24 (#1027215). Its reverse dependencies (keras and deepnano) are both also broken by this. (keras _also_ has apparently unrelated problems, #1026738, and is orphaned, #1027938.) This was previously discussed in #1027215, where it was noted that removing keras would also block the addition of qmean (ITP #976981), but attempts to fix it failed. (Note that what is in Salsa isn't actually a fix: theano skips most of its tests in Salsa CI because they take several hours.)
Bug#1039613: nmap breaks udptunnel autopkgtest: UDPTunnel communication failed
Thanks Paul. We did make some changes in Nmap 7.94 which could have caused regressions. I've opened an issue for this on our upstream tracker ( https://github.com/nmap/nmap/issues/2685). Please let us know if you figure anything else out. -Gordon
Bug#1041789: RM: unison-2.51+4.13.1 -- RoQA; newer version packaged
Source: unison-2.51+4.13.1 Version: 2.51.5-1 Severity: serious Why is unison-2.51+4.13.1 not removed yet when unison-2.52 is available?
Bug#1037192: sd: version is lower than in squeeze
Actually the maintainer is OK with bumping to 1.0, saving the effort to go epoch: https://github.com/chmln/sd/issues/200 I'll wait for its release. The point release is unfortunately missed, however. -- Sdrager, Blair Noctis
Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386
On 23 July 2023 at 11:03, Dirk Eddelbuettel wrote: | Note that the mlmRev authors / maintainers are the same as / a subset of the | lme4 authors. They may have an idea. | | https://cran.r-project.org/package=mlmRev I just ran `R CMD check mlmRev_*tar.gz` on my amd64 (under Ubuntu 23.04), it ran fine but also took a moment. In parallel I am also running it in a i386 Docker container for Debian unstable and that seems slow esp on the second file tests/lmerTest.R So if it were me I'd just skip that test file on i386 and move on. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386
On 23 July 2023 at 15:07, Graham Inggs wrote: | Hi | | On Sun, 23 Jul 2023 at 13:11, Nilesh Patra wrote: | > How do you conclude that? | > The versions of affected packages are same in unstable and testing. They | > fail in i386 with a newer version of lme4. | | For what it's worth, r-cran-afex[1] and r-cran-mertools[2] **are** | passing in unstable. Ah. So maybe I did look at that... | So perhaps whatever package fixed this condition has been uploaded, but not | yet migrated. | | Yet r-cran-mlmrev[3] still seems to have the timeout issue in unstable. Note that the mlmRev authors / maintainers are the same as / a subset of the lme4 authors. They may have an idea. https://cran.r-project.org/package=mlmRev Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1041783: ocaml-cry FTBFS: Error (alert deprecated): SSLv23
Source: ocaml-cry Version: 0.6.7-1 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/logs.php?pkg=ocaml-cry=0.6.7-1%2Bb3 ... Command [10] exited with code 2: $ (cd _build/default && /usr/bin/ocamlc.opt -w @1..3@5..28@30..39@43@46..47@49..57@61..62-40 -strict-sequence -strict-formats -short-paths -keep-locs -g -bin-annot -I src/.cry.objs/byte -I /usr/lib/ocaml/ssl -no-alias-deps -opaque -open Cry__ -o src/.cry.objs/byte/cry__Cry_https.cmo -c -impl src/cry_https.ml) File "src/cry_https.ssl.ml", line 29, characters 33-43: Error (alert deprecated): SSLv23 SSL 2.0 was deprecated in 2011 by RFC 6176. make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 This might have been caused by the new ocaml-ssl?
Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386
Hi, On 23-07-2023 15:51, Dirk Eddelbuettel wrote: But if you all think we are better auto-removing lme4 over i386 fails _of packages using it_ as opposed to fails in itself then I cannot stop you. As I mentioned already, we can't even do that easily because lme4 is currently a key package, and key packages are not autoremoved [1]. Paul [1] https://release.debian.org/key-packages.html OpenPGP_signature Description: OpenPGP digital signature
Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386
Hi On Sun, 23 Jul 2023 at 13:11, Nilesh Patra wrote: > How do you conclude that? > The versions of affected packages are same in unstable and testing. They > fail in i386 with a newer version of lme4. For what it's worth, r-cran-afex[1] and r-cran-mertools[2] **are** passing in unstable. So perhaps whatever package fixed this condition has been uploaded, but not yet migrated. Yet r-cran-mlmrev[3] still seems to have the timeout issue in unstable. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-afex/unstable/i386/ [2] https://ci.debian.net/packages/r/r-cran-mertools/unstable/i386/ [3] https://ci.debian.net/packages/r/r-cran-mlmrev/unstable/i386/
Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH
On Sun, 23 Jul 2023 15:59:19 +0200 Sebastiaan Couwenberg wrote: Control: tags -1 pending On 7/23/23 15:26, Timo Röhling wrote: > It is the package maintainer's responsibility to set > DEB_PYTHON_INSTALL_LAYOUT=deb in d/rules, either implicitly through > the use of pybuild, or explicitly with "export > DEB_PYTHON_INSTALL_LAYOUT", as you already did in Salsa. The advise for packages should be DEB_PYTHON_INSTALL_LAYOUT=deb_system based on the python3 changelog as that's intended for package builds. You are right. "deb" also works, but "deb_system" is the canonical scheme name. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Processed: reassign 1041633 to src:qgis, found 1041633 in qgis/3.28.8+dfsg-1
Processing commands for cont...@bugs.debian.org: > reassign 1041633 src:qgis Bug #1041633 [qgis] qgis: needs DEB_PYTHON_INSTALL_LAYOUT=deb to build Bug reassigned from package 'qgis' to 'src:qgis'. No longer marked as found in versions qgis/3.28.8+dfsg-1. Ignoring request to alter fixed versions of bug #1041633 to the same values previously set > found 1041633 qgis/3.28.8+dfsg-1 Bug #1041633 [src:qgis] qgis: needs DEB_PYTHON_INSTALL_LAYOUT=deb to build Marked as found in versions qgis/3.28.8+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH
Control: tags -1 pending On 7/23/23 15:26, Timo Röhling wrote: It is the package maintainer's responsibility to set DEB_PYTHON_INSTALL_LAYOUT=deb in d/rules, either implicitly through the use of pybuild, or explicitly with "export DEB_PYTHON_INSTALL_LAYOUT", as you already did in Salsa. The advise for packages should be DEB_PYTHON_INSTALL_LAYOUT=deb_system based on the python3 changelog as that's intended for package builds. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH
Processing control commands: > tags -1 pending Bug #1041633 [qgis] qgis: needs DEB_PYTHON_INSTALL_LAYOUT=deb to build Added tag(s) pending. -- 1041633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386
On 23 July 2023 at 18:42, Nilesh Patra wrote: | On Sun, 23 Jul 2023 07:15:09 -0500 Dirk Eddelbuettel wrote | > Is this is not an example of a release manager override? The affectect | > packages all work together in unstable and could migrate. | | How do you conclude that? | The versions of affected packages are same in unstable and testing. They | fail in i386 with a newer version of lme4. Sorry, my fault. I was wrong here so thanks for the correction. I looked at the bottom of one of those logs, saw a PASS and missed the FAIL preceding it. Still, it is a self-imposed problem by Debian. At some point we managed to let go of m68k too. But if you all think we are better auto-removing lme4 over i386 fails _of packages using it_ as opposed to fails in itself then I cannot stop you. That does not mean I concur with the decision. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Processed: Re: Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH
Processing control commands: > reassign -1 qgis 3.28.8+dfsg-1 Bug #1041633 [src:cmake] cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH Bug reassigned from package 'src:cmake' to 'qgis'. No longer marked as found in versions cmake/3.27.0-1. Ignoring request to alter fixed versions of bug #1041633 to the same values previously set Bug #1041633 [qgis] cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH Marked as found in versions qgis/3.28.8+dfsg-1. > retitle -1 qgis: needs DEB_PYTHON_INSTALL_LAYOUT=deb to build Bug #1041633 [qgis] cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH Changed Bug title to 'qgis: needs DEB_PYTHON_INSTALL_LAYOUT=deb to build' from 'cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH'. -- 1041633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH
Control: reassign -1 qgis 3.28.8+dfsg-1
Control: retitle -1 qgis: needs DEB_PYTHON_INSTALL_LAYOUT=deb to build
Hi Bas,
* Sebastiaan Couwenberg [2023-07-21 17:17]:
Changes between bookworm and sid:
cmake 3.25.1:
``Python_SITELIB``
Third-party platform independent installation directory.
Information returned by
``distutils.sysconfig.get_python_lib(plat_specific=False,standard_lib=False)``
or else ``sysconfig.get_path('purelib')``.
``Python_SITEARCH``
Third-party platform dependent installation directory.
Information returned by
``distutils.sysconfig.get_python_lib(plat_specific=True,standard_lib=False)``
or else ``sysconfig.get_path('platlib')``.
cmake 3.27.0:
``Python_SITELIB``
Third-party platform independent installation directory.
Information returned by ``sysconfig.get_path('purelib')``.
``Python_SITEARCH``
Third-party platform dependent installation directory.
Information returned by ``sysconfig.get_path('platlib')``.
On bookworm distutils is still used which returns:
>>> distutils.sysconfig.get_python_lib(
plat_specific=False,
standard_lib=False,
)
'/usr/lib/python3/dist-packages'
On sid sysconfig is used which results:
>>> sysconfig.get_path('platlib')
'/usr/local/lib/python3.11/dist-packages'
To get the right path for the Debian python3 interpreter,
you need to add 'deb_system':
>>> sysconfig.get_path('platlib', 'deb_system')
'/usr/lib/python3/dist-packages'
After a bit of discussion in #d-python, I believe that
CMake actually behaves as intended now, and the previous behavior was
unintended.
The default use-case is a local user build, not a package build, and
the default SITELIB reflects that.
It is the package maintainer's responsibility to set
DEB_PYTHON_INSTALL_LAYOUT=deb in d/rules, either implicitly through
the use of pybuild, or explicitly with "export
DEB_PYTHON_INSTALL_LAYOUT", as you already did in Salsa.
Cheers
Timo
--
⢀⣴⠾⠻⢶⣦⠀ ╭╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄ ╰╯
signature.asc
Description: PGP signature
Processed: tagging 1041421, tagging 1041422, tagging 1041423
Processing commands for cont...@bugs.debian.org: > tags 1041421 + upstream Bug #1041421 [gpac] gpac: CVE-2023-3523 CVE-2023-37174 CVE-2023-37765 CVE-2023-37766 CVE-2023-37767 Ignoring request to alter tags of bug #1041421 to the same tags previously set > tags 1041422 + upstream Bug #1041422 [src:openrefine] openrefine: CVE-2023-37476 Ignoring request to alter tags of bug #1041422 to the same tags previously set > tags 1041423 + upstream Bug #1041423 [src:cjose] cjose: CVE-2023-37464 Ignoring request to alter tags of bug #1041423 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1041421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041421 1041422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041422 1041423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fwd: Bug#1041040: aspectc++ autopkg tests fail with GCC 13
Processing commands for cont...@bugs.debian.org: > forwarded 1041040 aspectc-develop...@aspectc.org Bug #1041040 [src:aspectc++] aspectc++ autopkg tests fail with GCC 13 Set Bug forwarded-to-address to 'aspectc-develop...@aspectc.org'. > tag 1041040 upstream Bug #1041040 [src:aspectc++] aspectc++ autopkg tests fail with GCC 13 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386
On Sun, 23 Jul 2023 07:15:09 -0500 Dirk Eddelbuettel wrote > Is this is not an example of a release manager override? The affectect > packages all work together in unstable and could migrate. How do you conclude that? The versions of affected packages are same in unstable and testing. They fail in i386 with a newer version of lme4. Best, Nilesh signature.asc Description: PGP signature
Bug#1040924: marked as done (clevis-udisks2: Depends on NBS libblockdev-crypto2)
Your message dated Sun, 23 Jul 2023 12:46:02 + with message-id and subject line Bug#1040924: fixed in clevis 19-3 has caused the Debian Bug report #1040924, regarding clevis-udisks2: Depends on NBS libblockdev-crypto2 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.) -- 1040924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: clevis-udisks2 Version: 19-2 Severity: serious clevis-udisks2 depends on libblockdev-crypto2 which is no longer built by libblockdev in Unstable. Please update the manual dependency to libblockdev-crypto3 Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: clevis Source-Version: 19-3 Done: Christoph Biedl We believe that the bug you reported is fixed in the latest version of clevis, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated clevis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2023 12:04:17 +0200 Source: clevis Architecture: source Version: 19-3 Distribution: unstable Urgency: medium Maintainer: Christoph Biedl Changed-By: Christoph Biedl Closes: 1040924 Changes: clevis (19-3) unstable; urgency=medium . * Retire versioned dependencies met even in oldstable * libblockdev-crypto2: Drop libblockdev dependency, not needed. Closes: #1040924 Checksums-Sha1: d0535cf4eb7c238c8c7193c949c27bae35835bdf 2522 clevis_19-3.dsc 49e5ab5f634b61b1d40622e90cd4adf2086e1ee1 6980 clevis_19-3.debian.tar.xz d758c286e5187c1809db74caadd3cef7ebea0d9c 12069 clevis_19-3_powerpc.buildinfo Checksums-Sha256: f2f546f37b9e157b0bcbc808f55831cf0f0f840086101c64aeece25c5ee448e8 2522 clevis_19-3.dsc ff27ab3d54cec5d5172a58db79306d2ebeef90f62aaa0da70cba5b272d58cc01 6980 clevis_19-3.debian.tar.xz 1fa53ba72daa461a3975e2b14f8e9ab7cd318ccd729516e1f53bb3167f1b6d19 12069 clevis_19-3_powerpc.buildinfo Files: 51a8755b6772cc3c60ed61197bdbf476 2522 net optional clevis_19-3.dsc 0f716908cbe7d6c4b3654e40e6a94033 6980 net optional clevis_19-3.debian.tar.xz 0c5a53954a73b4b5883629a7111fb964 12069 net optional clevis_19-3_powerpc.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmS9HXQACgkQxCxY61kU kv0sVg//aWBmFbD0cIWfjVMUdeFPTKe/DtEmGTkf4ryfe+ix/Hx3t7Peag7yUfIw 25sbNTFlUALAOwZefM340HcQuKcEYKV3vNp3hUpvJf8x0puuzMM3nsUUiPl9i24h oZLS176bo8Aejx+3QKdU5vAiTN8FP/eDQg83nQi4LkDCaOlSYno1uIJgYWaly3vb XHN0pEqoRqLDJ1MvQMMyw9gF8mGtleoaYAPjIatxetZehbCr9cxQ3dtxRaI+hO0G JCOGq2E3+oCd8Z9RDAdLAJgLX7tHrItG+zOn1078x0z4Cjw7zrhsSRNQfBY1c3K6 wzrcPwR0hbZ4FPe3ko2we6CMlogNQ7IOZoTzJC2yXkoKmuzj6ZJoGSk15HQ2yoIo RbcN7ZUYBmYTUgBkbp9CywPiBPQJisMGSRvCgD4qXuPgw1rPhU2Pum0Z2CkI/i6n uoUyQOncaFbSr09SuTnQBmmltu/dAD/zGc+eqSB8JZ0ZcWAZ494S/E58jbQC3FZ/ dHs/J9zsCg6zdJfj9fbkiq6Whh2t3yjJj1NeF7atquUCYFSEo0a6hReIyVALSy8W q58mdZqSBp/hrdkWHnJXViSH2CpQUg/paOkXeZ7w/w1AbA5NpBRWsPL95xrIxnFR IjWUVJ1HjWL5DXkG7raNxTH+eSVAZ6VQKde1YnAf43SBkOo7g0I= =/+z4 -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12
Processing control commands: > severity -1 grave Bug #1036799 [sylpheed] sylpheed: unable to send or read email after upgrading to Debian 12 Severity set to 'grave' from 'important' -- 1036799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386
Paul, Is this is not an example of a release manager override? The affectect packages all work together in unstable and could migrate. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1037879: marked as done (unifrac-tools: ftbfs with GCC-13)
Your message dated Sun, 23 Jul 2023 11:48:18 +
with message-id
and subject line Bug#1037879: fixed in unifrac-tools 1.3.2-2
has caused the Debian Bug report #1037879,
regarding unifrac-tools: ftbfs with GCC-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1037879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:unifrac-tools
Version: 1.2-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/unifrac-tools_1.2-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
279 | int32_t BPTree::parent(uint32_t i) const {
| ^~
tree.cpp:279:24: error: ‘uint32_t’ was not declared in this scope
279 | int32_t BPTree::parent(uint32_t i) const {
|^~~~
tree.cpp:279:24: note: ‘uint32_t’ is defined in header ‘’; did you
forget to ‘#include ’?
tree.cpp:283:9: error: ‘int32_t su::BPTree::enclose’ is not a static data
member of ‘class su::BPTree’
283 | int32_t BPTree::enclose(uint32_t i) const {
| ^~
tree.cpp:283:25: error: ‘uint32_t’ was not declared in this scope
283 | int32_t BPTree::enclose(uint32_t i) const {
| ^~~~
tree.cpp:283:25: note: ‘uint32_t’ is defined in header ‘’; did you
forget to ‘#include ’?
tree.cpp:290:9: error: ‘int32_t su::BPTree::bwd’ is not a static data member of
‘class su::BPTree’
290 | int32_t BPTree::bwd(uint32_t i, int d) const {
| ^~
tree.cpp:290:21: error: ‘uint32_t’ was not declared in this scope
290 | int32_t BPTree::bwd(uint32_t i, int d) const {
| ^~~~
tree.cpp:290:21: note: ‘uint32_t’ is defined in header ‘’; did you
forget to ‘#include ’?
tree.cpp:290:33: error: expected primary-expression before ‘int’
290 | int32_t BPTree::bwd(uint32_t i, int d) const {
| ^~~
tree.cpp:290:38: error: expression list treated as compound expression in
initializer [-fpermissive]
290 | int32_t BPTree::bwd(uint32_t i, int d) const {
| ^
tree.cpp: In member function ‘void su::BPTree::newick_to_bp(std::string)’:
tree.cpp:350:5: error: ‘nparens’ was not declared in this scope; did you mean
‘parent’?
350 | nparens = structure.size();
| ^~~
| parent
tree.cpp: In member function ‘void su::BPTree::structure_to_openclose()’:
tree.cpp:365:22: error: invalid types ‘int[unsigned int]’ for array subscript
365 | openclose[i] = open_idx;
| ^
tree.cpp:366:22: error: invalid types ‘int[unsigned int]’ for array subscript
366 | openclose[open_idx] = i;
| ^
tree.cpp: In function ‘std::string& rtrim(std::string&)’:
tree.cpp:374:45: warning: ‘std::pointer_to_unary_function<_Arg, _Result>
std::ptr_fun(_Result (*)(_Arg)) [with _Arg = int; _Result = int]’ is
deprecated: use 'std::function' instead [-Wdeprecated-declarations]
374 | std::not1(std::ptr_fun(std::isspace))).base(),
s.end());
| ~~^~
In file included from /usr/include/c++/13/string:49,
from tree.hpp:13:
/usr/include/c++/13/bits/stl_function.h:1126:5: note: declared here
1126 | ptr_fun(_Result (*__x)(_Arg))
| ^~~
tree.cpp: In member function ‘void su::BPTree::newick_to_metadata(std::string)’:
tree.cpp:412:24:
Bug#1041758: libcudf-dev is not installable due to bogus janitor change
On 2023-07-23 10:57 +0300, Adrian Bunk wrote: > On Sun, Jul 23, 2023 at 09:03:24AM +0200, Sven Joachim wrote: >> On 2023-07-23 09:37 +0300, Adrian Bunk wrote: >> > I haven't checked whether the replacement package names are correct, >> > but the = dependences hardcoded in debian/control are clearly wrong. >> >> Hardcoding a dependency on libtinfo6 is also wrong, but libncurses-dev >> is indeed the successor of libncurses5-dev. > > I think the root cause is that the janitor did an automatic and > incorrect replacement based on the transitional package in buster: > > Package: libncurses5-dev > Version: 6.1+20181013-2+deb10u2 > Depends: libtinfo6 (= 6.1+20181013-2+deb10u2), libncurses-dev (= > 6.1+20181013-2+deb10u2) > > libncurses5-dev depending on libtinfo6 might be unnecessary since > libncurses-dev already depends on it, but that doesn't make it bogus. That dependency was created by dh_link, since /usr/share/doc/libncurses5-dev was a symlink to libtinfo6. I could have used libncurses-dev as target of the symlink instead and thereby avoid a direct dependency on libtinfo6 at the cost of slightly complicating debian/rules, but that is moot now. > Using = dependencies in a transitional package is unusual but not > incorrect when these packages are built from the same source package. Again, the /usr/share/doc symlink forced a strict dependency anyway. > The dependency of libncurses5-dev could therefore likely be simplified to > Depends: libncurses-dev That is correct. > but the problem is seems to that the janitor does not have a sanity check > to refuse a replacement. > > I see two bugs in the janitor here: > > 1. >= or >> dependencies in the replacement are OK, = dependencies are not. > <= or << dependencies should likely also be refused since they should > be checked by a human. > > 2. Dependencies on two packages are usually a package split, automatic > replacement works but might often be wrong for the different reason that > it creates too many dependencies. Agreed. Cheers, Sven
Bug#1037746: marked as done (libvbz-hdf-plugin: ftbfs with GCC-13)
Your message dated Sun, 23 Jul 2023 10:07:33 +
with message-id
and subject line Bug#1037746: fixed in libvbz-hdf-plugin 1.0.2-3
has caused the Debian Bug report #1037746,
regarding libvbz-hdf-plugin: ftbfs with GCC-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1037746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libvbz-hdf-plugin
Version: 1.0.2-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/libvbz-hdf-plugin_1.0.2-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
/<>/vbz/v0/vbz_streamvbyte.cpp:99:62: error: template argument 1
is invalid
99 | return StreamVByteWorkerV0::decompress(input_span, output_span);
| ^
/<>/vbz/v0/vbz_streamvbyte.cpp:102:49: error: ‘int32_t’ is not a
member of ‘std’; did you mean ‘int32_t’?
102 | return StreamVByteWorkerV0::decompress(input_span, output_span);
| ^~~
/usr/include/x86_64-linux-gnu/bits/stdint-intn.h:26:19: note: ‘int32_t’
declared here
26 | typedef __int32_t int32_t;
| ^~~
/<>/vbz/v0/vbz_streamvbyte.cpp:102:49: error: ‘int32_t’ is not a
member of ‘std’; did you mean ‘int32_t’?
102 | return StreamVByteWorkerV0::decompress(input_span, output_span);
| ^~~
/usr/include/x86_64-linux-gnu/bits/stdint-intn.h:26:19: note: ‘int32_t’
declared here
26 | typedef __int32_t int32_t;
| ^~~
/<>/vbz/v0/vbz_streamvbyte.cpp:102:63: error: template argument 1
is invalid
102 | return StreamVByteWorkerV0::decompress(input_span, output_span);
| ^
/<>/vbz/v0/vbz_streamvbyte.cpp: In function ‘vbz_size_t
vbz_delta_zig_zag_streamvbyte_compress_v0(const void*, vbz_size_t, void*,
vbz_size_t, int, bool)’:
/<>/vbz/v0/vbz_streamvbyte.cpp:37:13: error: this statement may
fall through [-Werror=implicit-fallthrough=]
37 | if (use_delta_zig_zag_encoding) {
| ^~
/<>/vbz/v0/vbz_streamvbyte.cpp:44:9: note: here
44 | case 2: {
| ^~~~
/<>/vbz/v0/vbz_streamvbyte.cpp:45:13: error: this statement may
fall through [-Werror=implicit-fallthrough=]
45 | if (use_delta_zig_zag_encoding) {
| ^~
/<>/vbz/v0/vbz_streamvbyte.cpp:52:9: note: here
52 | case 4: {
| ^~~~
/<>/vbz/v0/vbz_streamvbyte.cpp:53:13: error: this statement may
fall through [-Werror=implicit-fallthrough=]
53 | if (use_delta_zig_zag_encoding) {
| ^~
/<>/vbz/v0/vbz_streamvbyte.cpp:60:9: note: here
60 | default:
| ^~~
/<>/vbz/v0/vbz_streamvbyte.cpp: In function ‘vbz_size_t
vbz_delta_zig_zag_streamvbyte_decompress_v0(const void*, vbz_size_t, void*,
vbz_size_t, int, bool)’:
/<>/vbz/v0/vbz_streamvbyte.cpp:82:13: error: this statement may
fall through [-Werror=implicit-fallthrough=]
82 | if (use_delta_zig_zag_encoding) {
| ^~
/<>/vbz/v0/vbz_streamvbyte.cpp:89:9: note: here
89 | case 2: {
| ^~~~
/<>/vbz/v0/vbz_streamvbyte.cpp:90:13: error: this statement may
fall through [-Werror=implicit-fallthrough=]
90 |
Bug#1037879: marked as pending in unifrac-tools
Control: tag -1 pending Hello, Bug #1037879 in unifrac-tools 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/med-team/unifrac-tools/-/commit/a14968b435dfb0814cfb01bf67282b613210d5ad gcc-13.patch: new: fix build failures with gcc-13 Closes: #1037879 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037879
Processed: Bug#1037879 marked as pending in unifrac-tools
Processing control commands: > tag -1 pending Bug #1037879 [src:unifrac-tools] unifrac-tools: ftbfs with GCC-13 Added tag(s) pending. -- 1037879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037746: marked as pending in vbz-compression
Control: tag -1 pending Hello, Bug #1037746 in vbz-compression 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/med-team/libvbz-hdf-plugin/-/commit/bbb470883ceece8fe5925d8212353b09954bde6f gcc-13.patch: new: fix build failures with gcc 13. Closes: #1037746 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037746
Processed: Bug#1037746 marked as pending in vbz-compression
Processing control commands: > tag -1 pending Bug #1037746 [src:libvbz-hdf-plugin] libvbz-hdf-plugin: ftbfs with GCC-13 Added tag(s) pending. -- 1037746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039613: nmap breaks udptunnel autopkgtest: UDPTunnel communication failed
On Tue, 27 Jun 2023 21:40:14 +0200 Paul Gevers wrote: > Source: nmap, udptunnel > Control: found -1 nmap/7.94+dfsg1-1 > Control: found -1 udptunnel/1.1-9 ... > With a recent upload of nmap the autopkgtest of udptunnel fails in > testing when that autopkgtest is run with the binary packages of nmap > from unstable. It passes when run with only packages from testing. I think this is likely to be a bug in nmap ncat, when I remove udptunnel from the script by connecting ncat directly to ncat, then the failure still happens with the autopkgtest. I was able to reproduce this issue outside a chroot. I have attached a pair of scripts; bad fails and good succeeds. In the good case, I use `sleep` to hold stdin of `ncat -l` open for 2s, in the bad case I let it use the stdin provided by the shell (a GNOME terminal pty here). Looking at the diff between the verbose logs is interesting. In the good case one select fd is ready and one becomes ready later, the latter one gets used, but in the bad case both fds appear to be ready immediately but neither of them get used. -NCAT DEBUG: select returned 1 fds ready -NCAT DEBUG: fd 3 is ready -NCAT DEBUG: selecting, fdmax 3 -NCAT DEBUG: select returned 1 fds ready +NCAT DEBUG: select returned 2 fds ready So the issue can be worked around in the udptunnel script by piping sleep to the ncat listener instead of launching ncat and then sleeping, or the ncat change that caused this can get bisected and fixed. -- bye, pabs https://wiki.debian.org/PaulWise bad Description: application/shellscript + rm rx tx + echo foo + sleep 2s + ncat - -u -l 127.0.0.1 1234 Ncat: Version 7.94 ( https://nmap.org/ncat ) NCAT DEBUG: Initialized fdlist with 102 maxfds Ncat: Listening on 127.0.0.1:1234 NCAT DEBUG: Added fd 3 to list, nfds 1, maxfd 3 NCAT DEBUG: Added fd 0 to list, nfds 2, maxfd 3 NCAT DEBUG: Initialized fdlist with 100 maxfds NCAT DEBUG: selecting, fdmax 3 + ncat -u 127.0.0.1 1234 NCAT DEBUG: select returned 1 fds ready NCAT DEBUG: fd 3 is ready NCAT DEBUG: Swapping fd[0] (3) with fd[1] (0) NCAT DEBUG: Removed fd 3 from list, nfds 1, maxfd 0 Ncat: Connection from 127.0.0.1:57558. NCAT DEBUG: Added fd 3 to list, nfds 2, maxfd 3 NCAT DEBUG: Added fd 3 to list, nfds 1, maxfd 3 NCAT DEBUG: selecting, fdmax 3 NCAT DEBUG: select returned 2 fds ready NCAT DEBUG: fd 0 is ready NCAT DEBUG: EOF on stdin + sleep 2s + head -vn-0 tx rx ==> tx <== foo ==> rx <== + echo tx tx + hd tx 66 6f 6f 0a |foo.| 0004 + echo rx rx + hd rx + echo diff diff + diff -u tx rx --- tx 2023-07-23 16:49:32.411502343 +0800 +++ rx 2023-07-23 16:49:32.411502343 +0800 @@ -1 +0,0 @@ -foo good Description: application/shellscript + rm rx tx + echo foo + + sleep 2sncat -u 127.0.0.1 1234 + ncat - -u -l 127.0.0.1 1234 Ncat: Version 7.94 ( https://nmap.org/ncat ) NCAT DEBUG: Initialized fdlist with 102 maxfds Ncat: Listening on 127.0.0.1:1234 NCAT DEBUG: Added fd 3 to list, nfds 1, maxfd 3 NCAT DEBUG: Added fd 0 to list, nfds 2, maxfd 3 NCAT DEBUG: Initialized fdlist with 100 maxfds NCAT DEBUG: selecting, fdmax 3 NCAT DEBUG: select returned 1 fds ready NCAT DEBUG: fd 3 is ready NCAT DEBUG: Swapping fd[0] (3) with fd[1] (0) NCAT DEBUG: Removed fd 3 from list, nfds 1, maxfd 0 Ncat: Connection from 127.0.0.1:36688. NCAT DEBUG: Added fd 3 to list, nfds 2, maxfd 3 NCAT DEBUG: Added fd 3 to list, nfds 1, maxfd 3 NCAT DEBUG: selecting, fdmax 3 NCAT DEBUG: select returned 1 fds ready NCAT DEBUG: fd 3 is ready NCAT DEBUG: selecting, fdmax 3 + sleep 2s NCAT DEBUG: select returned 1 fds ready NCAT DEBUG: fd 0 is ready NCAT DEBUG: EOF on stdin + head -vn-0 tx rx ==> tx <== foo ==> rx <== foo + echo tx tx + hd tx 66 6f 6f 0a |foo.| 0004 + echo rx rx + hd rx 66 6f 6f 0a |foo.| 0004 + echo diff diff + diff -u tx rx signature.asc Description: This is a digitally signed message part
Bug#1040178: marked as done (linux-kbuild-6.3: missing Breaks: linux-headers-6.3.0-1-common, ...)
Your message dated Sun, 23 Jul 2023 09:00:12 + with message-id and subject line Bug#1040178: fixed in linux 6.4.4-1 has caused the Debian Bug report #1040178, regarding linux-kbuild-6.3: missing Breaks: linux-headers-6.3.0-1-common, ... 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.) -- 1040178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvidia-kernel-dkms Version: 525.116.04-1 Setting up nvidia-kernel-dkms (525.116.04-1) ... Removing old nvidia-current-525.116.04 DKMS files... Deleting module nvidia-current-525.116.04 completely from the DKMS tree. Loading new nvidia-current-525.116.04 DKMS files... Building for 6.3.0-1-amd64 Building initial module for 6.3.0-1-amd64 Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.116.04/build/make.log for more information. dpkg: error processing package nvidia-kernel-dkms (--configure): installed nvidia-kernel-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of nvidia-driver: nvidia-driver depends on nvidia-kernel-dkms (= 525.116.04-1) | nvidia-kernel-525.116.04 | nvidia-open-kernel-525.116.04 | nvidia-open-kernel-525.116.04; however: Package nvidia-kernel-dkms is not configured yet. Package nvidia-kernel-525.116.04 is not installed. Package nvidia-kernel-dkms which provides nvidia-kernel-525.116.04 is not configured yet. Package nvidia-open-kernel-525.116.04 is not installed. Package nvidia-open-kernel-525.116.04 is not installed. dpkg: error processing package nvidia-driver (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-3) ... Errors were encountered while processing: nvidia-kernel-dkms nvidia-driver E: Sub-process /usr/bin/dpkg returned an error code (1) Build log ends with errors such as: /var/lib/dkms/nvidia-current/525.116.04/build/nvidia-drm.mod.c:10:10: fatal error: asm/orc_header.h: No such file or directory 10 | #include | ^~ compilation terminated. --- End Message --- --- Begin Message --- Source: linux Source-Version: 6.4.4-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2023 08:53:20 +0200 Source: linux Architecture: source Version: 6.4.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1040178 1040346 Changes: linux (6.4.4-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.4.2 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.4.3 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.4.4 - Revert "drm/amd/display: edp do not add non-edid timings" (Closes: #1040346) - netfilter: nf_tables: do not ignore genmask when looking up chain by id (CVE-2023-31248) - netfilter: nf_tables: prevent OOB access in nft_byteorder_eval (CVE-2023-35001) . [ Vincent Pelletier ] * [riscv64] enable CONFIG_SND_HDA_INTEL as module . [ Salvatore Bonaccorso ] * Compile with gcc-13 on all architectures * [rt] Refresh "serial: 8250: implement non-BKL console" * Set ABI to 1 . [ Benjamin Poirier ] * kernel/trace: Enable FPROBE . [ Ben Hutchings ] * d/rules.real: Fix CROSS_COMPILE definition for hppa native build (regression in 6.4~rc7-1~exp1) . [ Bastian Blank ] * Include kbuild package into ABI. (closes: #1040178) * [powerpc,riscv64,s390x] Enable DEBUG_INFO_BTF. Checksums-Sha1: 935aabaae9fdd3fecefeb01e27bdf86040c8b3ba 288676 linux_6.4.4-1.dsc 3b3b9d0850978ce0f548761a5bf8b1809fd30685 140401048 linux_6.4.4.orig.tar.xz
Bug#1041760: marked as done (src:python-geopandas: unsatisfied build dependency in testing: python3-pyepsg)
Your message dated Sun, 23 Jul 2023 08:42:34 + with message-id and subject line Bug#1041760: fixed in python-geopandas 0.13.2-2 has caused the Debian Bug report #1041760, regarding src:python-geopandas: unsatisfied build dependency in testing: python3-pyepsg 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.) -- 1041760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-geopandas Version: 0.13.2-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? python-pyepsg is affected by an RC issue [2] and has been removed from testing, you could help its maintainers to solve the issue. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://bugs.debian.org/1033851 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-geopandas Source-Version: 0.13.2-2 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of python-geopandas, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated python-geopandas package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2023 10:03:07 +0200 Source: python-geopandas Architecture: source Version: 0.13.2-2 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Closes: 1041760 Changes: python-geopandas (0.13.2-2) unstable; urgency=medium . * Team upload. * Bump debhelper compat to 13. * Don't set environment variables in dh_auto_test override. * Use autopkgtest-pkg-pybuild testsuite. * Enable Salsa CI. * Preserve directory structure in pybuild build directory. * Drop obsolete python3-pyepsg build dependency. (closes: #1041760) Checksums-Sha1: 6bdd7e965ba6d08a019ca3a192b92ddc99063f14 2424 python-geopandas_0.13.2-2.dsc 0e4adf6e8bc011e9804fe9bd1b9e884ce926fd63 1322020 python-geopandas_0.13.2-2.debian.tar.xz 2fe31f6a24c72fad7d45ac089834567d1f0a35e0 15416 python-geopandas_0.13.2-2_amd64.buildinfo Checksums-Sha256: 50e267a771f5ca2e1f90725bc43e7ce6b49a7c787a3044fd17f5476c51aa760c 2424 python-geopandas_0.13.2-2.dsc 41ce61789f2e66c2174e27ab459b0de42c7a03b8e94fec486fef7f44ea059525 1322020 python-geopandas_0.13.2-2.debian.tar.xz f5588dbc64a6b2f7c5b66565f775ea1fab78919170f21e5d3a6fd941709af124 15416 python-geopandas_0.13.2-2_amd64.buildinfo Files: 7a067419d2ec5d1ee296ab2e74f95d13 2424 python optional python-geopandas_0.13.2-2.dsc 16cdfeb30037d4f37c8e9d7acba266c3 1322020 python optional python-geopandas_0.13.2-2.debian.tar.xz dbe843a40378aaa0eb84015106b4f058 15416 python optional python-geopandas_0.13.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmS84BIACgkQZ1DxCuiN SvE3nxAAwjXMsZi06ZXRVFcv9s2hA6a62lxeB+ltisTc9tNM/uV7SO2kJUyjkNpD oG9Ef13yH6sh+haYBiZZAwmHR2F3k5NMkDGF2yS8v3ZpkUC1rUJfy054duHrEJJe hbMTzTzE4ZVVXSn1OUfJ7ZgHCsDa2mBE5yg8IqatJG56wvQRKpfM5YfOhCrNsdQJ kBluvfUYOd4mPLdmJkKqTrC6tTvalYlKASel/ukW2c2ihd55U0XUr5IFFGpgDpnL 0acVYKu5KoRbwLNiUEMJA+ZyqDPZZU6QPO5uh++eNv0gaxDDFDAbUykoLJmCVmXF SjGV0IF5VaukSCDLVq7SH4OHEk3a6U+W6efW0EKnrejnJve7jJzijW7TpqDyt2Fn Fd247FT7seZK37TZYAU7NNtMpjEK4LEffXf+wBhUHKRUxdn+6AVU8NAewqUZcwqO
Bug#1041758: libcudf-dev is not installable due to bogus janitor change
On Sun, Jul 23, 2023 at 09:03:24AM +0200, Sven Joachim wrote: > On 2023-07-23 09:37 +0300, Adrian Bunk wrote: > > > Package: libcudf-dev > > Version: 0.10-1 > > Severity: serious > > X-Debbugs-Cc: team+jani...@tracker.debian.org > > > > The following packages have unmet dependencies: > > libcudf-dev : Depends: libtinfo6 (= 6.1+20181013-2+deb10u2) but > > 6.4+20230625-1 is to be installed > >Depends: libncurses-dev (= 6.1+20181013-2+deb10u2) but > > 6.4+20230625-1 is to be installed > > > > This is due to: > > > > https://salsa.debian.org/ocaml-team/cudf/-/merge_requests/2 > > > > cudf (0.10-1) unstable; urgency=medium > > ... > > [ Debian Janitor ] > > ... > >* Remove constraints unnecessary since buster (oldstable): > > + libcudf-dev: Replace dependency on transitional package > > libncurses5-dev > >with replacement libtinfo6 (= 6.1+20181013-2+deb10u2), > > libncurses-dev (= > >6.1+20181013-2+deb10u2) in Depends. > > ... > > > > > > I haven't checked whether the replacement package names are correct, > > but the = dependences hardcoded in debian/control are clearly wrong. > > Hardcoding a dependency on libtinfo6 is also wrong, but libncurses-dev > is indeed the successor of libncurses5-dev. I think the root cause is that the janitor did an automatic and incorrect replacement based on the transitional package in buster: Package: libncurses5-dev Version: 6.1+20181013-2+deb10u2 Depends: libtinfo6 (= 6.1+20181013-2+deb10u2), libncurses-dev (= 6.1+20181013-2+deb10u2) libncurses5-dev depending on libtinfo6 might be unnecessary since libncurses-dev already depends on it, but that doesn't make it bogus. Using = dependencies in a transitional package is unusual but not incorrect when these packages are built from the same source package. The dependency of libncurses5-dev could therefore likely be simplified to Depends: libncurses-dev but the problem is seems to that the janitor does not have a sanity check to refuse a replacement. I see two bugs in the janitor here: 1. >= or >> dependencies in the replacement are OK, = dependencies are not. <= or << dependencies should likely also be refused since they should be checked by a human. 2. Dependencies on two packages are usually a package split, automatic replacement works but might often be wrong for the different reason that it creates too many dependencies. > Cheers, >Sven cu Adrian
Bug#1041760: src:python-geopandas: unsatisfied build dependency in testing: python3-pyepsg
On 7/23/23 09:07, Paul Gevers wrote: Can you please investigate the situation and figure out how to resolve it? python-pyepsg is affected by an RC issue [2] and has been removed from testing, you could help its maintainers to solve the issue. python-geopandas was marked for autoremoval from testing due to the RC bug affecting python-pyepsg but then wasn't. That suggests an issue in britney. pyepsg doesn't appear to be used anymore although it's still referenced in documentation. I'll drop the build dependency to resolve this issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386
Hi Dirk, On 22-07-2023 23:14, Dirk Eddelbuettel wrote: It could be an issue as simple as CRAN (and upstream) no longer checking on i386 though it usually does not fail there. This is what I suspected, but it needs to be resolved in Debian by somebody, somehow. lme4 is a key package, removing it from i386 isn't going to be easy if at all possible. If you don't want to investigate yourself, maybe contact the i386 porter (bunk) and ask his help. Another option is to file bugs for your reverse dependencies if you believe they are at fault. At least r-cran-mlmrev isn't a key package so with an RC bug filed against it, it will be autoremoved in due time. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1037790: nix: ftbfs with GCC-13
control: tag -1 + pending
On Wed, Jun 14, 2023 at 09:29:02AM +, Matthias Klose wrote:
> Package: src:nix
> Version: 2.8.0-1.1
> Severity: normal
> Tags: sid trixie
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-13
>
> [This bug is targeted to the upcoming trixie release]
[snip]
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
> severity of this report will be raised before the trixie release.
>
> The full build log can be found at:
> http://qa-logs.debian.net/2023/05/22/logs/nix_2.8.0-1.1_unstable_gccexp.log
> The last lines of the build log are at the end of this report.
[snip]
> src/libutil/json.cc: In function ‘void nix::toJSON(std::ostream&, const
> char*, const char*)’:
> src/libutil/json.cc:33:22: error: ‘uint16_t’ was not declared in this scope
>33 | put(hex[(uint16_t(*i) >> 12) & 0xf]);
> | ^~~~
> src/libutil/json.cc:5:1: note: ‘uint16_t’ is defined in header ‘’;
> did you forget to ‘#include ’?
> 4 | #include
> +++ |+#include
> 5 |
> make[1]: *** [mk/patterns.mk:3: src/libutil/json.o] Error 1
> make[1]: *** Waiting for unfinished jobs
> make[1]: Leaving directory '/<>'
> dh_auto_build: error: make -j8 returned exit code 2
> make: *** [debian/rules:31: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
> 2
I am attaching the debdiff of the NMU that I uploaded to DELAYED/5 yesterday.
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
diff -Nru nix-2.8.0/debian/changelog nix-2.8.0/debian/changelog
--- nix-2.8.0/debian/changelog 2022-10-15 13:28:28.0 +0300
+++ nix-2.8.0/debian/changelog 2023-07-22 19:16:28.0 +0300
@@ -1,3 +1,11 @@
+nix (2.8.0-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add the gcc13 patch to fix the build with GCC 13.
+Closes: #1037790
+
+ -- Peter Pentchev Sat, 22 Jul 2023 19:16:28 +0300
+
nix (2.8.0-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru nix-2.8.0/debian/patches/gcc13.patch
nix-2.8.0/debian/patches/gcc13.patch
--- nix-2.8.0/debian/patches/gcc13.patch1970-01-01 02:00:00.0
+0200
+++ nix-2.8.0/debian/patches/gcc13.patch2023-07-22 19:13:41.0
+0300
@@ -0,0 +1,17 @@
+Description: Fix the build with GCC 13
+ Include the header for the definition of the uint16_t type.
+Bug-Debian: https://bugs.debian.org/1037790
+Forwarded: no
+Author: Peter Pentchev
+Last-Update: 2023-07-22
+
+--- a/src/libutil/json.cc
b/src/libutil/json.cc
+@@ -1,6 +1,7 @@
+ #include "json.hh"
+
+ #include
++#include
+ #include
+
+ namespace nix {
diff -Nru nix-2.8.0/debian/patches/series nix-2.8.0/debian/patches/series
--- nix-2.8.0/debian/patches/series 2022-05-02 21:55:23.0 +0300
+++ nix-2.8.0/debian/patches/series 2023-07-22 19:16:28.0 +0300
@@ -4,3 +4,4 @@
fix_nix_DIR_in_doc_local_mk.patch
lowdown_does_not_declare_bsd_dep.patch
+gcc13.patch
signature.asc
Description: PGP signature
Processed: Re: nix: ftbfs with GCC-13
Processing control commands: > tag -1 + pending Bug #1037790 [src:nix] nix: ftbfs with GCC-13 Added tag(s) pending. -- 1037790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041763: src:starlette: fails to migrate to testing for too long: triggers autopkgtest failure
Source: starlette Version: 0.26.1-1 Severity: serious Control: close -1 0.30.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: affects -1 src:fastapi Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:starlette has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable triggers autopkgtest failures in fastapi. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=starlette OpenPGP_signature Description: OpenPGP digital signature
Processed: src:starlette: fails to migrate to testing for too long: triggers autopkgtest failure
Processing control commands:
> close -1 0.30.0-1
Bug #1041763 [src:starlette] src:starlette: fails to migrate to testing for too
long: triggers autopkgtest failure
Marked as fixed in versions starlette/0.30.0-1.
Bug #1041763 [src:starlette] src:starlette: fails to migrate to testing for too
long: triggers autopkgtest failure
Marked Bug as done
> affects -1 src:fastapi
Bug #1041763 {Done: Paul Gevers } [src:starlette]
src:starlette: fails to migrate to testing for too long: triggers autopkgtest
failure
Added indication that 1041763 affects src:fastapi
--
1041763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:monty: fails to migrate to testing for too long: dropping architectures impacts reverse dependencies
Processing control commands: > close -1 2023.5.8+dfsg-4 Bug #1041762 [src:monty] src:monty: fails to migrate to testing for too long: dropping architectures impacts reverse dependencies Marked as fixed in versions monty/2023.5.8+dfsg-4. Bug #1041762 [src:monty] src:monty: fails to migrate to testing for too long: dropping architectures impacts reverse dependencies Marked Bug as done -- 1041762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041762: src:monty: fails to migrate to testing for too long: dropping architectures impacts reverse dependencies
Source: monty Version: 2022.9.9+dfsg-1 Severity: serious Control: close -1 2023.5.8+dfsg-4 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:monty has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable makes pymatgen uninstallable on the architectures where support has been droppped but that hasn't been discussed with or reported to its maintainer. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=monty OpenPGP_signature Description: OpenPGP digital signature
Bug#1037573: marked as done (android-platform-art: ftbfs with GCC-13)
Your message dated Sun, 23 Jul 2023 07:19:41 +
with message-id
and subject line Bug#1037573: fixed in android-platform-art 13.0.0+r63-1
has caused the Debian Bug report #1037573,
regarding android-platform-art: ftbfs with GCC-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1037573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:android-platform-art
Version: 11.0.0+r48-5
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/android-platform-art_11.0.0+r48-5_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/stl_iterator_base_types.h:178:14:
note: during template argument deduction for class template partial
specialization '__iterator_traits<_Iterator>' [with _Iterator =
art::mirror::ArrayIter>>]
: public __iterator_traits<_Iterator> { };
^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/stl_iterator_base_types.h:178:14:
note: in instantiation of template class
'std::__iterator_traits>>>' requested here
libartbase/base/iteration_range.h:30:25: note: in instantiation of template
class 'std::iterator_traits>>>' requested here
typedef typename std::iterator_traits::difference_type difference_type;
^
runtime/class_linker.cc:5019:48: note: in instantiation of template class
'art::IterationRange>>>' requested here
for (auto [mirror, idx] : ZipCount(h_methods.Iterate())) {
^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/stl_iterator_base_types.h:127:12:
note: 'iterator>'
has been explicitly marked deprecated here
struct _GLIBCXX17_DEPRECATED iterator
^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/x86_64-linux-gnu/c++/13/bits/c++config.h:121:34:
note: expanded from macro '_GLIBCXX17_DEPRECATED'
# define _GLIBCXX17_DEPRECATED [[__deprecated__]]
^
In file included from runtime/class_linker.cc:50:
libartbase/base/stl_util.h:153:33: warning:
'iterator, unsigned long>>' is deprecated
[-Wdeprecated-declarations]
class ZipLeftIter : public std::iterator<
^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/stl_iterator_base_types.h:162:27:
note: in instantiation of template class
'art::ZipLeftIter>>, art::CountIter>'
requested here
__void_t' [with _Iterator =
art::ZipLeftIter>>, art::CountIter>]
: public __iterator_traits<_Iterator> { };
^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/stl_iterator_base_types.h:178:14:
note: in instantiation of template class
'std::__iterator_traits>>, art::CountIter>>'
requested here
libartbase/base/iteration_range.h:30:25: note: in instantiation of template
class
'std::iterator_traits>>, art::CountIter>>'
requested here
typedef typename std::iterator_traits::difference_type difference_type;
^
runtime/class_linker.cc:5019:29: note: in instantiation of template class
'art::IterationRange>>, art::CountIter>>'
requested here
for (auto [mirror, idx] : ZipCount(h_methods.Iterate())) {
^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/stl_iterator_base_types.h:127:12:
note: 'iterator, unsigned
Processed: src:r-cran-bookdown: fails to migrate to testing for too long: triggers autopkgtest failure
Processing control commands:
> close -1 0.34+dfsg-1
Bug #1041761 [src:r-cran-bookdown] src:r-cran-bookdown: fails to migrate to
testing for too long: triggers autopkgtest failure
Marked as fixed in versions r-cran-bookdown/0.34+dfsg-1.
Bug #1041761 [src:r-cran-bookdown] src:r-cran-bookdown: fails to migrate to
testing for too long: triggers autopkgtest failure
Marked Bug as done
> block -1 by 1041557
Bug #1041761 {Done: Paul Gevers } [src:r-cran-bookdown]
src:r-cran-bookdown: fails to migrate to testing for too long: triggers
autopkgtest failure
1041761 was not blocked by any bugs.
1041761 was not blocking any bugs.
Added blocking bug(s) of 1041761: 1041557
--
1041761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1041761: src:r-cran-bookdown: fails to migrate to testing for too long: triggers autopkgtest failure
Source: r-cran-bookdown Version: 0.32+dfsg-1 Severity: serious Control: close -1 0.34+dfsg-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1041557 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:r-cran-bookdown has been trying to migrate for 42 days [2]. Hence, I am filing this bug. The package in unstable triggers an autopkgtest failure as reported in bug 1041557. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-bookdown OpenPGP_signature Description: OpenPGP digital signature
Bug#1041760: src:python-geopandas: unsatisfied build dependency in testing: python3-pyepsg
Source: python-geopandas Version: 0.13.2-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? python-pyepsg is affected by an RC issue [2] and has been removed from testing, you could help its maintainers to solve the issue. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html [2] https://bugs.debian.org/1033851 OpenPGP_signature Description: OpenPGP digital signature
Bug#1041758: libcudf-dev is not installable due to bogus janitor change
On 2023-07-23 09:37 +0300, Adrian Bunk wrote: > Package: libcudf-dev > Version: 0.10-1 > Severity: serious > X-Debbugs-Cc: team+jani...@tracker.debian.org > > The following packages have unmet dependencies: > libcudf-dev : Depends: libtinfo6 (= 6.1+20181013-2+deb10u2) but > 6.4+20230625-1 is to be installed >Depends: libncurses-dev (= 6.1+20181013-2+deb10u2) but > 6.4+20230625-1 is to be installed > > This is due to: > > https://salsa.debian.org/ocaml-team/cudf/-/merge_requests/2 > > cudf (0.10-1) unstable; urgency=medium > ... > [ Debian Janitor ] > ... >* Remove constraints unnecessary since buster (oldstable): > + libcudf-dev: Replace dependency on transitional package libncurses5-dev >with replacement libtinfo6 (= 6.1+20181013-2+deb10u2), libncurses-dev > (= >6.1+20181013-2+deb10u2) in Depends. > ... > > > I haven't checked whether the replacement package names are correct, > but the = dependences hardcoded in debian/control are clearly wrong. Hardcoding a dependency on libtinfo6 is also wrong, but libncurses-dev is indeed the successor of libncurses5-dev. Cheers, Sven
Bug#1037747: marked as done (libwebsockets: ftbfs with GCC-13)
Your message dated Sun, 23 Jul 2023 06:51:50 + with message-id and subject line Bug#1037747: fixed in libwebsockets 4.3.2-2 has caused the Debian Bug report #1037747, regarding libwebsockets: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libwebsockets Version: 4.1.6-3 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libwebsockets_4.1.6-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] [ 26%] Building C object lib/CMakeFiles/websockets_shared.dir/tls/tls-client.c.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/cc -Dwebsockets_shared_EXPORTS -I/<>/include -I/<>/obj-x86_64-linux-gnu -I/<>/lib -I/<>/lib/. -I/<>/lib/plat/unix/. -I/<>/lib/tls/. -I/<>/lib/core/. -I/<>/lib/misc/. -I/<>/lib/system/./async-dns -I/<>/lib/system/smd/. -I/<>/lib/core-net/. -I/<>/lib/roles/. -I/<>/lib/roles/http/. -I/<>/lib/roles/http/./compression -I/<>/lib/roles/h1/. -I/<>/lib/roles/h2/. -I/<>/lib/roles/ws/. -I/<>/lib/roles/raw-skt/. -I/<>/lib/roles/raw-file/. -I/<>/lib/roles/listen/. -I/<>/lib/event-libs/. -I/<>/lib/event-libs/poll/../poll -I/<>/lib/event-libs/libuv/. -I/<>/lib/event-libs/glib/. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2. 0/include -I/<>/lib/event-libs/libev/. -Wall -Wsign-compare -Wstrict-aliasing -fvisibility=hidden -Wundef -Wuninitialized -Wtype-limits -Wignored-qualifiers -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated-declarations -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -pthread -fPIC -MD -MT lib/CMakeFiles/websockets_shared.dir/tls/tls-client.c.o -MF CMakeFiles/websockets_shared.dir/tls/tls-client.c.o.d -o CMakeFiles/websockets_shared.dir/tls/tls-client.c.o -c /<>/lib/tls/tls-client.c [ 26%] Building C object lib/CMakeFiles/websockets_shared.dir/tls/openssl/openssl-client.c.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/cc -Dwebsockets_shared_EXPORTS -I/<>/include -I/<>/obj-x86_64-linux-gnu -I/<>/lib -I/<>/lib/. -I/<>/lib/plat/unix/. -I/<>/lib/tls/. -I/<>/lib/core/. -I/<>/lib/misc/. -I/<>/lib/system/./async-dns -I/<>/lib/system/smd/. -I/<>/lib/core-net/. -I/<>/lib/roles/. -I/<>/lib/roles/http/. -I/<>/lib/roles/http/./compression -I/<>/lib/roles/h1/. -I/<>/lib/roles/h2/. -I/<>/lib/roles/ws/. -I/<>/lib/roles/raw-skt/. -I/<>/lib/roles/raw-file/. -I/<>/lib/roles/listen/. -I/<>/lib/event-libs/. -I/<>/lib/event-libs/poll/../poll -I/<>/lib/event-libs/libuv/. -I/<>/lib/event-libs/glib/. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2. 0/include -I/<>/lib/event-libs/libev/. -Wall -Wsign-compare -Wstrict-aliasing -fvisibility=hidden -Wundef -Wuninitialized -Wtype-limits -Wignored-qualifiers -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated-declarations -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -pthread -fPIC -MD -MT lib/CMakeFiles/websockets_shared.dir/tls/openssl/openssl-client.c.o -MF CMakeFiles/websockets_shared.dir/tls/openssl/openssl-client.c.o.d -o CMakeFiles/websockets_shared.dir/tls/openssl/openssl-client.c.o -c /<>/lib/tls/openssl/openssl-client.c make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:1323: lib/CMakeFiles/websockets.dir/all] Error 2 make[2]:
Bug#1041758: libcudf-dev is not installable due to bogus janitor change
Package: libcudf-dev Version: 0.10-1 Severity: serious X-Debbugs-Cc: team+jani...@tracker.debian.org The following packages have unmet dependencies: libcudf-dev : Depends: libtinfo6 (= 6.1+20181013-2+deb10u2) but 6.4+20230625-1 is to be installed Depends: libncurses-dev (= 6.1+20181013-2+deb10u2) but 6.4+20230625-1 is to be installed This is due to: https://salsa.debian.org/ocaml-team/cudf/-/merge_requests/2 cudf (0.10-1) unstable; urgency=medium ... [ Debian Janitor ] ... * Remove constraints unnecessary since buster (oldstable): + libcudf-dev: Replace dependency on transitional package libncurses5-dev with replacement libtinfo6 (= 6.1+20181013-2+deb10u2), libncurses-dev (= 6.1+20181013-2+deb10u2) in Depends. ... I haven't checked whether the replacement package names are correct, but the = dependences hardcoded in debian/control are clearly wrong.
