Bug#980795: marked as done (Security fixes from the January 2021 CPU)
Your message dated Mon, 25 Jan 2021 07:05:17 + with message-id and subject line Bug#980795: fixed in mysql-8.0 8.0.23-1 has caused the Debian Bug report #980795, regarding Security fixes from the January 2021 CPU 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.) -- 980795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mysql-8.0 Version: 8.0.22 Severity: grave Tags: security upstream fixed-upstream The Oracle Critical Patch Update for October 2020 lists CVEs affecting MySQL 8.0 that are fixed in 8.0.23 CVE list: - CVE-2021-1998 CVE-2021-2001 CVE-2021-2002 CVE-2021-2087 - CVE-2021-2009 CVE-2021-2012 CVE-2021-2016 CVE-2021-2019 - CVE-2021-2020 CVE-2021-2021 CVE-2021-2022 CVE-2021-2024 - CVE-2021-2028 CVE-2021-2030 CVE-2021-2031 CVE-2021-2032 - CVE-2021-2036 CVE-2021-2038 CVE-2021-2042 CVE-2021-2046 - CVE-2021-2048 CVE-2021-2055 CVE-2021-2056 CVE-2021-2058 - CVE-2021-2060 CVE-2021-2061 CVE-2021-2065 CVE-2021-2070 - CVE-2021-2072 CVE-2021-2076 CVE-2021-2081 CVE-2021-2088 - CVE-2021-2122 Ref: https://www.oracle.com/security-alerts/cpujan2021.html#AppendixMSQL Regards, Lars Tangvald --- End Message --- --- Begin Message --- Source: mysql-8.0 Source-Version: 8.0.23-1 Done: Lars Tangvald We believe that the bug you reported is fixed in the latest version of mysql-8.0, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lars Tangvald (supplier of updated mysql-8.0 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: Tue, 19 Jan 2021 14:07:46 + Source: mysql-8.0 Architecture: source Version: 8.0.23-1 Distribution: unstable Urgency: medium Maintainer: Debian MySQL Maintainers Changed-By: Lars Tangvald Closes: 980795 Launchpad-Bugs-Fixed: 1911032 Changes: mysql-8.0 (8.0.23-1) unstable; urgency=medium . [ Lars Tangvald ] * Imported upstream version 8.0.23 to fix security issues: - https://www.oracle.com/security-alerts/cpujan2021.html#AppendixMSQL - CVE-2021-1998 CVE-2021-2001 CVE-2021-2002 CVE-2021-2087 - CVE-2021-2009 CVE-2021-2012 CVE-2021-2016 CVE-2021-2019 - CVE-2021-2020 CVE-2021-2021 CVE-2021-2022 CVE-2021-2024 - CVE-2021-2028 CVE-2021-2030 CVE-2021-2031 CVE-2021-2032 - CVE-2021-2036 CVE-2021-2038 CVE-2021-2042 CVE-2021-2046 - CVE-2021-2048 CVE-2021-2055 CVE-2021-2056 CVE-2021-2058 - CVE-2021-2060 CVE-2021-2061 CVE-2021-2065 CVE-2021-2070 - CVE-2021-2072 CVE-2021-2076 CVE-2021-2081 CVE-2021-2088 - CVE-2021-2122 Upstream release notes: - https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-23.html - https://dev.mysql.com/doc/relnotes/mysql-router/en/news-8-0-23.html (Closes: #980795) * d/install: Removed mysql_protocol.so from router package This plugin file has been obsoleted and removed by upstream. * Fix test failure due to hardcoded date (LP: #1911032) * d/patches: Update atomics patch for riscv. * d/symbols: Add new symbol from 8.0.23 to client library * d/install: Add new plugins to router and server packages . [ Marc Deslauriers ] * d/symbols: Add new symbol from 8.0.22 to client library Checksums-Sha1: a44c8955e89aeff5c296578b2e3d64b0507277b6 3668 mysql-8.0_8.0.23-1.dsc 78350bb4c12dfc869f2c23f0272affa90417538f 291039175 mysql-8.0_8.0.23.orig.tar.gz bda094b02103d2b462fde5ec292c39d80ccf5d6b 232 mysql-8.0_8.0.23.orig.tar.gz.asc 0152a74561ef2f6b54df8101fd4bb75e9c7cc9ee 157888 mysql-8.0_8.0.23-1.debian.tar.xz 22d2a6a2c021be2d6e1ea6e64ddd86653a7038cc 9351 mysql-8.0_8.0.23-1_source.buildinfo Checksums-Sha256: ff2a8f48f1a75e5f87cb058b2d1f69aec73c66e0eb8452b2dd64d04b14066ebf 3668 mysql-8.0_8.0.23-1.dsc 1c7a424303c134758e59607a0b3172e43a21a27ff08e8c88c2439ffd4fc724a5 291039175 mysql-8.0_8.0.23.orig.tar.gz c1a2783792a2fa7b36b5cd11275bf2353f269cc04371f6056c59dff968595367 232 mysql-8.0_8.0.23.orig.tar.gz.asc 75790d012c9eb06e0fb20ce8e137cec6117dbb2002f95b1f7095193acf0f73ca 157888 mysql-8.0_8.0.23-1.debian.tar.xz 2a1
Bug#948346: [PATCH] Ensure graceful signal handling when the pid file exists
On Sun, Jan 10, 2021 at 12:10:16PM +0100, Eduard Bloch wrote: >... > I am setting this to RC severity because it's just NOT ok and obvious to > fix. Going to change mentioned things and NMU this in a couple of weeks > if there is no further reaction from maintainers. Could you make an upload to DELAYED instead of further waiting? > Best regards, > Eduard. Thanks Adrian
Bug#978079: heads up: rapid-photo-downloader might not make it to bullseye
On Sun, Jan 24, 2021 at 8:44 PM Antoine Beaupré wrote: > Maybe then there is an easy fix to keep RPD in Debian if > rawkit disappears. > > There is no need for any kind of fix in the code itself. Just remove the mention of rawkit from the Rapid Photo Downloader Debian package. Rapid Photo Downloader will run without rawkit, without any changes to its code. If rawkit is present and working, Rapid Photo Downloader will use it. If rawkit is either not working or not present, Rapid Photo Downloader won't use it. -- https://damonlynch.net
Bug#980168: marked as done (Missing dependency causes nomad-driver-lxc FTBFS)
Your message dated Mon, 25 Jan 2021 03:48:26 + with message-id and subject line Bug#980168: fixed in nomad 0.12.9+dfsg1-2 has caused the Debian Bug report #980168, regarding Missing dependency causes nomad-driver-lxc FTBFS 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.) -- 980168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: golang-github-hashicorp-nomad-dev Version: 0.12.9+dfsg1-1 Severity: serious X-Debbugs-Cc: z...@debian.org https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/nomad-driver-lxc_0.3.0-1.rbuild.log.gz src/github.com/hashicorp/nomad/helper/mount/mount_linux.go:6:2: cannot find package "github.com/docker/docker/pkg/mount" in any of: /build/1st/nomad-driver-lxc-0.3.0/_build/src/github.com/hashicorp/nomad/vendor/github.com/docker/docker/pkg/mount (vendor tree) /usr/lib/go-1.15/src/github.com/docker/docker/pkg/mount (from $GOROOT) /build/1st/nomad-driver-lxc-0.3.0/_build/src/github.com/docker/docker/pkg/mount (from $GOPATH) src/github.com/hashicorp/nomad/client/pluginmanager/csimanager/volume.go:12:2: cannot find package "github.com/grpc-ecosystem/go-grpc-middleware/retry" in any of: /build/1st/nomad-driver-lxc-0.3.0/_build/src/github.com/hashicorp/nomad/vendor/github.com/grpc-ecosystem/go-grpc-middleware/retry (vendor tree) /usr/lib/go-1.15/src/github.com/grpc-ecosystem/go-grpc-middleware/retry (from $GOROOT) /build/1st/nomad-driver-lxc-0.3.0/_build/src/github.com/grpc-ecosystem/go-grpc-middleware/retry (from $GOPATH) The FTBFS of nomad-driver-lxc is in the src/github.com/hashicorp/nomad, so I think it's problem in golang-github-hashicorp-nomad-dev. --- End Message --- --- Begin Message --- Source: nomad Source-Version: 0.12.9+dfsg1-2 Done: Dmitry Smirnov We believe that the bug you reported is fixed in the latest version of nomad, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Smirnov (supplier of updated nomad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 25 Jan 2021 14:03:27 +1100 Source: nomad Architecture: source Version: 0.12.9+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov Changed-By: Dmitry Smirnov Closes: 980168 Changes: nomad (0.12.9+dfsg1-2) unstable; urgency=medium . * dev:Depends (Closes: #980168): + golang-github-grpc-ecosystem-go-grpc-middleware-dev + golang-github-docker-docker-dev (>= 20.10.0~) . Thanks, Shengjing Zhu. Checksums-Sha1: 1716e491d9c72e43839641e2a61bc8cb90a07346 7717 nomad_0.12.9+dfsg1-2.dsc 782fe2377d3fb55d0cfe14a99b12495f792519d0 24952 nomad_0.12.9+dfsg1-2.debian.tar.xz 85460ddb0bb96459ccedb2c0f1d0ed8cde77b49f 23901 nomad_0.12.9+dfsg1-2_amd64.buildinfo Checksums-Sha256: 6d7328d5a2eb2789c0f07f5e88ce541131dee44320cfdaac385f2d8e9993b57d 7717 nomad_0.12.9+dfsg1-2.dsc 041297d1e79a7a331e3704e7554c94a621aa9d4e5ada070beae4474c43fe8392 24952 nomad_0.12.9+dfsg1-2.debian.tar.xz f09420a0d7a84b1243d96b3e446eb0833686fb6f633ca64b1b1ab72fe91313e2 23901 nomad_0.12.9+dfsg1-2_amd64.buildinfo Files: 545d35799e5ada67cd4b508471d69f62 7717 admin optional nomad_0.12.9+dfsg1-2.dsc 997a6db9942cef21076f3fcebc1b140d 24952 admin optional nomad_0.12.9+dfsg1-2.debian.tar.xz 0f29ed458d4def46f7ac301ec277892a 23901 admin optional nomad_0.12.9+dfsg1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmAOOj4ACgkQUra72VOW jRtpPg//bSMUgmnLzMz1phjciMncAWEFQxnMwN0lf1d9Kb3rL90bwfReXwZEnj0u ny8sKv6TWVtExHPOP+2My4tIxMcpecDTdte2yPx3obHMlkhzXPwj8PCUc56zGmxV OomMf1ge854rpgHZfODufvGwLet+BCdv2mk1P80swkVqWvp5W3dv0evZj1OKNRTC kgfmlS7DCCNqQmImlQjSR7D+eWnBySh4f7iOANYmm7LvMC2XOAI3b8JISw3D7Y25 KjAXIgN/4OSHQnqlcsufO0cEZ9XtlEZHye54x3CP041fFleEUAUvbeg4Ygrq5vyU s/8lQPmUfcG0jkoXC6IxcAH/vB4KdM//jBN9PClLbUVZC+2pKTA5qMWQ74iFmDez 9rgJMybzDqD2YLzvMuHdE4XPE20XFLp+vZewr99D7iDWDlYAwFiPgQnixeWHpKXX 3cId0KxnBqL0LrFOqxnrTJwyL6tMlqEGW0i+bJFYEgYYaywZ2rhnZfJNgy+z1XBI Ik45kBMnHCIg0Kd9xmctZwlJvOb
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 972747 + pending Bug #972747 [sbuild] sbuild: bullseye: /updates -> -security Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 972747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980594: marked as done (abiword: FTBFS: ./../../../backends/service/xp/ServiceAccountHandler.h:152:28: error: ‘error’ is not a member of ‘asio::placeholders’)
Your message dated Mon, 25 Jan 2021 03:33:21 + with message-id and subject line Bug#980594: fixed in abiword 3.0.4~dfsg-3 has caused the Debian Bug report #980594, regarding abiword: FTBFS: ./../../../backends/service/xp/ServiceAccountHandler.h:152:28: error: ‘error’ is not a member of ‘asio::placeholders’ 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.) -- 980594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abiword Version: 3.0.4~dfsg-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../../../../libtool --tag=CXX --mode=compile g++ > -DHAVE_CONFIG_H -I. -I../../../../.. -pthread -I/usr/include/libgsf-1 > -I/usr/include/telepathy-1.0 -I/usr/include/loudmouth-1.0 > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 > -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi > -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/libsoup-2.4 > -I/usr/include/libxml2 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/p11-kit-1 -DABICOLLAB_HANDLER_TELEPATHY > -DABICOLLAB_HANDLER_XMPP -DABICOLLAB_HANDLER_TCP -DABICOLLAB_HANDLER_SUGAR > -DABICOLLAB_HANDLER_SERVICE -DSOUP24 -pthread -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libpng16 -pthread > -I/usr/include/wv -I/usr/include/freetype2 -I/usr/include/enchant-2 > -I/usr/include/libgsf-1 -I/usr/include/rasqal -I/usr/include/raptor2 > -I/usr/include/evolution-data-server -I/usr/include/nss -I/usr/include/nspr > -I/usr/include/libsecret-1 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 > -I/usr/include/cairo -I/usr/include/gtk-3.0/unix-print -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/librsvg-2.0 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libgoffice-0.10 -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_0 > -I/usr/include -I../../../../.. -I../../../../../src/af/ev/gtk > -I../../../../../src/af/ev/xp -I../../../../../src/af/gr/gtk > -I../../../../../src/af/gr/xp -I../../../../../src/af/util/unix > -I../../../../../src/af/util/xp -I../../../../../src/af/xap/gtk > -I../../../../../src/af/xap/xp -I../../../../../src/text/fmt/gtk > -I../../../../../src/text/fmt/xp -I../../../../../src/text/ptbl/xp > -I../../../../../src/wp/impexp/gtk -I../../../../../src/wp/impexp/xp > -I../../../../../src/wp/ap/gtk -I../../../../../src/wp/ap/xp > -I../../../../../src/plugins -DABI_DLL -I./.. -I./../.. -I./../../.. > -I./../../../core -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra > -Wsign-compare -Wpointer-arith -Wchar-subscripts -Wwrite-strings > -Wmissing-noreturn -Wunused -Wpointer-arith -Wshadow -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wno-overloaded-virtual -MT > ServiceUnixAccountHandler.lo -MD -MP -MF .deps/ServiceUnixAccountHandler.Tpo > -c -o ServiceUnixAccountHandler.lo ServiceUnixAccountHandler.cpp > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../../.. -pthread > -I/usr/include/libgsf-1 -I/usr/include/telepathy-1.0 > -I/usr/include/loudmouth-1.0 -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/
Bug#980670: pantalaimon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Dear Maintainer, Your package builds fine in a sid chroot environment after applying this commit [1]. Kind Regards [1] https://github.com/matrix-org/pantalaimon/commit/726e969
Bug#980670: marked as done (pantalaimon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Mon, 25 Jan 2021 01:48:31 +
with message-id
and subject line Bug#980670: fixed in pantalaimon 0.9.1-1
has caused the Debian Bug report #980670,
regarding pantalaimon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
980670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pantalaimon
Version: 0.8.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package pantalaimon
> dpkg-buildpackage: info: source version 0.8.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Jonas Smedegaard
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean
>dh_testdir
>dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean
>dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building pantalaimon using existing
> ./pantalaimon_0.8.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building pantalaimon in pantalaimon_0.8.0-2.debian.tar.xz
> dpkg-source: info: building pantalaimon in pantalaimon_0.8.0-2.dsc
> debian/rules binary
> dh binary
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/panctl.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/daemon.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/index.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/store.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/client.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/thread_messages.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/config.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/ui.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/log.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
> copying pantalaimon/main.py ->
> /<>/.pybuild/cpython3_3.9/build/pantalaimon
>dh_auto_test
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.9.1+, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
> rootdir: /<>
> collected 16 items
>
> tests/pan_client_test.py ..ss. [
> 31%]
> tests/proxy_test.py .[
> 62%]
> tests/store_test.py ...Fs.
> [100%]
>
> === FAILURES
> ===
> _ TestClass.test_fetcher_tasks
> _
>
> self =
> panstore_with_users = PanStore(store_path='/tmp/tmpeylexotu',
> database_name='pan.db', database= 0x7f6a18766040>, database_path='/tmp/tmpeylexotu/pan.db')
>
> def test_fetcher_tasks(self, panstore_with_users):
> panstore = panstore_with_users
> accounts = panstore.load_all_users()
> user, _ = accounts[0]
>
> task = FetchTask(TEST_ROOM, "abc1234")
> task2 = FetchTask(TEST_ROOM2, "abc1234")
>
> > assert not panstore.load_fetcher_tasks("example", user)
>
> tests/store_test.py:113:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> pantalaimon/store.py:230: in load_fetcher_tasks
> serve
Bug#978079: heads up: rapid-photo-downloader might not make it to bullseye
On 2021-01-24 20:18:27, Damon Lynch wrote: >> Otherwise I'm afraid we won't be able to ship >> RPD with Debian starting with bullseye, which would really be a shame... > > I am the developer of Rapid Photo Downloader. I am not impressed by this > suggestion. Rapid Photo Downloader has an optional, soft dependency on > rawkit. Rapid Photo Downloader will install and run perfectly well without > rawkit, which has been the case for some years now. > > If you have any packaging questions about Rapid Photo Downloader you can > ask me, instead of > simply removing the package from Debian. To be as polite as possible, I am > somewhat taken aback by a suggestion to remove it without any communication > with me. I was merely stating the current situation, which is that there is currently a hard dependency between RPD and rawkit right now, and rawkit will be removed. This means that RPD, without change, will also be removed. I was not suggesting that RPD *must* be removed from Debian. I use it regularly, and I would hate to see it go... > FWIW, the latest version of Rapid Photo Downloader is 0.9.26. The Debian > package is somewhat out of date these days. ... and in fact, I would love if the package was more up to date to. :) But this is the hand we're given right now. I'm glad to hear that the rawkit dependency is not as "hard" as I first understood it. Maybe then there is an easy fix to keep RPD in Debian if rawkit disappears. But I figured I would share my concerns rather than stay silent, because otherwise this would have all happened automatically and you probably would have noticed too late. I'm sorry if it sounded a bit cavalier, I wasn't expecting you to read this thread directly, and I did suggest the maintainer contact you directly as well. I unfortunately do not have time to deal with this problem myself (other than raising this red flag) so I hope that others will be able to. A. -- >From the age of uniformity, from the age of solitude, from the age of Big Brother, from the age of doublethink - greetings! - Winston Smith, 1984
Bug#980647: marked as done (python-matrix-nio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Mon, 25 Jan 2021 02:36:25 +0100
with message-id <161153858538.1590156.10727786700688039...@auryn.jones.dk>
and subject line Re: [Pkg-matrix-maintainers] Bug#980647: python-matrix-nio:
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
3.9 returned exit code 13
has caused the Debian Bug report #980647,
regarding python-matrix-nio: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
980647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-matrix-nio
Version: 0.15.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-matrix-nio
> dpkg-buildpackage: info: source version 0.15.2-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Jonas Smedegaard
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-matrix-nio using existing
> ./python-matrix-nio_0.15.2.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building python-matrix-nio in
> python-matrix-nio_0.15.2-1.debian.tar.xz
> dpkg-source: info: building python-matrix-nio in
> python-matrix-nio_0.15.2-1.dsc
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/rooms.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/responses.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/api.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/__init__.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/_compat.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/http.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/log.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/exceptions.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/monitors.py -> /<>/.pybuild/cpython3_3.9/build/nio
> copying nio/schemas.py -> /<>/.pybuild/cpython3_3.9/build/nio
> creating /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/to_device.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/misc.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/account_data.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/room_events.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/invite_events.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/presence.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/common.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> copying nio/events/ephemeral.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/events
> creating /<>/.pybuild/cpython3_3.9/build/nio/client
> copying nio/client/http_client.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/client
> copying nio/client/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/client
> copying nio/client/base_client.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/client
> copying nio/client/async_client.py ->
> /<>/.pybuild/cpython3_3.9/build/nio/client
> creating /<>/.pybuild/cpython3_3.9/build/nio/crypto
> copying nio/crypto/key_export.py ->
> /<>/.
Bug#978079: heads up: rapid-photo-downloader might not make it to bullseye
> Otherwise I'm afraid we won't be able to ship > RPD with Debian starting with bullseye, which would really be a shame... I am the developer of Rapid Photo Downloader. I am not impressed by this suggestion. Rapid Photo Downloader has an optional, soft dependency on rawkit. Rapid Photo Downloader will install and run perfectly well without rawkit, which has been the case for some years now. If you have any packaging questions about Rapid Photo Downloader you can ask me, instead of simply removing the package from Debian. To be as polite as possible, I am somewhat taken aback by a suggestion to remove it without any communication with me. FWIW, the latest version of Rapid Photo Downloader is 0.9.26. The Debian package is somewhat out of date these days. Damon -- https://damonlynch.net
Bug#979641: src:kboot-utils: invalid maintainer address
On Sun, 24 Jan 2021 21:12:54 +0100 Baptiste Beauplat wrote: > Hi Antonio, > > kboot-utils, one of the packages you maintain in Debian has an old, > unreachable > Maitainer address. Could you please update it to prevent it from getting > removed? > > See below the original bug report. > Thank you for reporting this Baptiste. I am actually not sure how useful kboot-utils is nowadays, it was mainly developed to make it easier to boot kernels on the Sony PS3, but I don't think the PS3 is supported by Debian directly anymore. However I would be happy to update the package anyway if there was someone interested to sponsor it, since I cannot upload packages myself and the I doubt my usual sponsor would be interested in it. Ciao, Antonio > Best, > > On 2021/01/09 06:04 PM, Ansgar wrote: > > Source: kboot-utils > > Version: 0.4-1 > > Severity: serious > > Tags: bullseye sid > > X-Debbugs-Cc: Holger Levsen > > > > The maintainer address is invalid, see below. > > > > Ansgar > > > > Start of forwarded message > > From: Mail Delivery System > > Subject: Mail delivery failed: returning message to sender > > Date: Sat, 09 Jan 2021 16:49:56 + > > > > > This message was created automatically by mail delivery software. > > > > A message that you sent could not be delivered to one or more of its > > recipients. This is a permanent error. The following address(es) failed: > > > > osp...@studenti.unina.it > > host fmvip.unina.it [192.132.34.7] > > SMTP error from remote mail server after RCPT > > TO:: > > 550 5.1.1 ... User unknown > > > Reporting-MTA: dns; muffat.debian.org > > > > Action: failed > > Final-Recipient: rfc822;osp...@studenti.unina.it > > Status: 5.0.0 > > Remote-MTA: dns; fmvip.unina.it > > Diagnostic-Code: smtp; 550 5.1.1 ... User unknown > > > > -- > Baptiste Beauplat - lyknode -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#957248: marked as done (gadmin-proftpd: ftbfs with GCC-10)
Your message dated Sun, 24 Jan 2021 23:48:27 +
with message-id
and subject line Bug#957248: fixed in gadmin-proftpd 1:0.4.2-1.1
has caused the Debian Bug report #957248,
regarding gadmin-proftpd: ftbfs with GCC-10
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.)
--
957248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gadmin-proftpd
Version: 1:0.4.2-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/gadmin-proftpd_0.4.2-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html
[...]
53 | void password_virtual_user(G_CONST_RETURN gchar *username,
G_CONST_RETURN gchar *password);
| ^~~
functions.h:53:13: warning: const
functions.h:55:13: warning: const
55 | void password_user(G_CONST_RETURN gchar *username, G_CONST_RETURN gchar
*password);
| ^~~
functions.h:55:13: warning: const
mv -f .deps/add_standard_users.Tpo .deps/add_standard_users.Po
gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/share"\"
-DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread -I/usr/include/gtk-2.0
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
-I/usr/include/fribidi -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid
-I/usr/include/freetype2 -I/usr/include/libpng16-g -O2 -Wall -MT
show_help.o -MD -MP -MF .deps/show_help.Tpo -c -o show_help.o show_help.c
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:33,
from show_help.c:22:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is
deprecated [-Wdeprecated-declarations]
236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
| ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
from /usr/include/glib-2.0/gobject/gbinding.h:29,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from show_help.c:22:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
679 | {
| ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126,
from show_help.c:22:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: war
Processed: tagging 977056
Processing commands for cont...@bugs.debian.org: > tags 977056 + ftbfs patch Bug #977056 [src:beanbag] beanbag FTBFS with pytest 6 Added tag(s) patch and ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 977056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978389: easyh10: diff for NMU version 1.5-4.1
Control: tags 978389 + patch
Control: tags 978389 + pending
Dear maintainer,
I've prepared an NMU for easyh10 (versioned as 1.5-4.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru easyh10-1.5/debian/changelog easyh10-1.5/debian/changelog
--- easyh10-1.5/debian/changelog 2016-10-09 23:43:46.0 +0300
+++ easyh10-1.5/debian/changelog 2021-01-25 01:08:02.0 +0200
@@ -1,3 +1,10 @@
+easyh10 (1.5-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove usage of obsolete AM_LANGINFO_CODESET. (Closes: #978389)
+
+ -- Adrian Bunk Mon, 25 Jan 2021 01:08:02 +0200
+
easyh10 (1.5-4) unstable; urgency=medium
* Fix the 40-fix-FTBFS-Hurd.patch.
diff -Nru easyh10-1.5/debian/patches/50-no-am-langinfo-codeset.patch easyh10-1.5/debian/patches/50-no-am-langinfo-codeset.patch
--- easyh10-1.5/debian/patches/50-no-am-langinfo-codeset.patch 1970-01-01 02:00:00.0 +0200
+++ easyh10-1.5/debian/patches/50-no-am-langinfo-codeset.patch 2021-01-25 01:08:02.0 +0200
@@ -0,0 +1,38 @@
+Description: Remove usage of obsolete AM_LANGINFO_CODESET
+Author: Adrian Bunk
+Bug-Debian: https://bugs.debian.org/978389
+
+--- easyh10-1.5.orig/configure.in
easyh10-1.5/configure.in
+@@ -181,7 +181,6 @@ case $with_libiconv in
+ AC_DEFINE(USE_LIBICONV_NATIVE, 1, [Using a native implementation of iconv in a separate library])
+ ;;
+ esac
+-AM_LANGINFO_CODESET
+
+
+ dnl Checks for id3tag
+--- easyh10-1.5.orig/cui/main.c
easyh10-1.5/cui/main.c
+@@ -41,9 +41,7 @@
+ #include
+ #include
+
+-#ifdef HAVE_LANGINFO_CODESET
+ #include
+-#endif
+
+ #ifdef HAVE_GETOPT_H
+ #include
+@@ -889,11 +887,9 @@ int main(int argc, char *argv[])
+ if (!encoding_specified) {
+ const char *encoding = getenv("CHARSET");
+
+-#ifdef HAVE_LANGINFO_CODESET
+ if (!encoding) {
+ encoding = nl_langinfo(CODESET);
+ }
+-#endif/*HAVE_LANGINFO_CODESET*/
+
+ if (encoding) {
+ /* EasyH10 could detect the character encoding. */
diff -Nru easyh10-1.5/debian/patches/series easyh10-1.5/debian/patches/series
--- easyh10-1.5/debian/patches/series 2016-10-09 23:43:46.0 +0300
+++ easyh10-1.5/debian/patches/series 2021-01-25 01:08:02.0 +0200
@@ -2,3 +2,4 @@
20-dont-install-docs.patch
30-fix-spelling.patch
40-fix-FTBFS-Hurd.patch
+50-no-am-langinfo-codeset.patch
Processed: easyh10: diff for NMU version 1.5-4.1
Processing control commands: > tags 978389 + patch Bug #978389 [src:easyh10] easyh10: FTBFS: configure.in:184: error: possibly undefined macro: AM_LANGINFO_CODESET (caused by gettext 0.19 -> 0.21?) Added tag(s) patch. > tags 978389 + pending Bug #978389 [src:easyh10] easyh10: FTBFS: configure.in:184: error: possibly undefined macro: AM_LANGINFO_CODESET (caused by gettext 0.19 -> 0.21?) Added tag(s) pending. -- 978389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978346: marked as done (gtick: FTBFS: configure:6437: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))
Your message dated Sun, 24 Jan 2021 22:48:21 + with message-id and subject line Bug#978346: fixed in gtick 0.5.5-2 has caused the Debian Bug report #978346, regarding gtick: FTBFS: configure:6437: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?) 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.) -- 978346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtick Version: 0.5.5-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf > Copying file intl/COPYING.LIB > Copying file intl/plural.c > Creating directory m4 > Copying file m4/codeset.m4 > Copying file m4/extern-inline.m4 > Copying file m4/fcntl-o.m4 > Copying file m4/gettext.m4 > Copying file m4/glibc2.m4 > Copying file m4/glibc21.m4 > Copying file m4/iconv.m4 > Copying file m4/intdiv0.m4 > Copying file m4/intl.m4 > Copying file m4/intldir.m4 > Copying file m4/intlmacosx.m4 > Copying file m4/intmax.m4 > Copying file m4/inttypes-pri.m4 > Copying file m4/inttypes_h.m4 > Copying file m4/lcmessage.m4 > Copying file m4/lib-ld.m4 > Copying file m4/lib-link.m4 > Copying file m4/lib-prefix.m4 > Copying file m4/lock.m4 > Copying file m4/longlong.m4 > Copying file m4/nls.m4 > Copying file m4/po.m4 > Copying file m4/printf-posix.m4 > Copying file m4/progtest.m4 > Copying file m4/size_max.m4 > Copying file m4/stdint_h.m4 > Copying file m4/threadlib.m4 > Copying file m4/uintmax_t.m4 > Copying file m4/visibility.m4 > Copying file m4/wchar_t.m4 > Copying file m4/wint_t.m4 > Copying file m4/xsize.m4 > Copying file po/Makevars.template > ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer > supported. > configure.ac:74: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd > /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from... > configure.ac:74: the top level > ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer > supported. > configure.ac:74: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd > aclocal.m4:77: AM_GNU_GETTEXT is expanded from... > configure.ac:74: the top level > ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer > supported. > configure.ac:74: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd > aclocal.m4:77: AM_GNU_GETTEXT is expanded from... > configure.ac:74: the top level > configure:6437: error: possibly undefined macro: AM_INTL_SUBDIR > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > autoreconf: /usr/bin/autoconf failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:9: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/12/26/gtick_0.5.5-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: gtick Source-Version: 0.5.5-2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of gtick, 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 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated gtick 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-
Processed: closing 978264
Processing commands for cont...@bugs.debian.org: > close 978264 Bug #978264 [src:python-escript] python-escript: FTBFS: ImportError: cannot import name 'griddata' from 'matplotlib.mlab' (/usr/lib/python3/dist-packages/matplotlib/mlab.py) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 978264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980972: xxsds-dynamic: Changelog entry missing trailer line
Source: xxsds-dynamic Version: 1.0~alpha.1+2020072524git5390b6c-2 Severity: serious Justification: Policy 4.4 Hi, The changelog entry for 1.0~alpha.1+2020072524git5390b6c-2 is missing a trailer line with maintainer and date information, which violates Debian policy and caused the package to fail to upload to the Ubuntu archive. Can you please add a trailer line accordingly? I added one in Ubuntu based on the information I could garner about the upload. [1] Thanks, Logan [1] http://launchpadlibrarian.net/519371489/xxsds-dynamic_1.0~alpha.1+2020072524git5390b6c-2_1.0~alpha.1+2020072524git5390b6c-2ubuntu1.diff.gz
Bug#967184: marked as done (offlineimap: Unversioned Python removal in sid/bullseye)
Your message dated Sun, 24 Jan 2021 22:18:50 + with message-id and subject line Bug#967184: fixed in offlineimap3 0.0~git20210105.00d395b+dfsg-2 has caused the Debian Bug report #967184, regarding offlineimap: Unversioned Python removal in sid/bullseye 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.) -- 967184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:offlineimap Version: 7.3.3+dfsg1-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: offlineimap3 Source-Version: 0.0~git20210105.00d395b+dfsg-2 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of offlineimap3, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated offlineimap3 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, 24 Jan 2021 21:43:56 + Source: offlineimap3 Architecture: source Version: 0.0~git20210105.00d395b+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Sudip Mukherjee Closes: 937184 967184 Changes: offlineimap3 (0.0~git20210105.00d395b+dfsg-2) unstable; urgency=medium . * Add 'offlineimap' transitional package. - Removes python2 dependency from offlineimap. (Closes: #937184, #967184) Checksums-Sha1: c787cff5c4b5e4036459fd04521b8a6c36ef4ff5 2345 offlineimap3_0.0~git20210105.00d395b+dfsg-2.dsc 643e1ff77630efbc8a0b51523cfbc4d1cfeada69 4576 offlineimap3_0.0~git20210105.00d395b+dfsg-2.debian.tar.xz 6f256597869645850f60bf57231a4ccced1e9b94 7421 offlineimap3_0.0~git20210105.00d395b+dfsg-2_amd64.buildinfo Checksums-Sha256: f445cb1a596449918f5d379a877e5437130c81e0468434e01fe31f49209821b8 2345 offlineimap3_0.0~git20210105.00d395b+dfsg-2.dsc 59597564023210c6febdb08d85087538db286006775091693e7b36510d2256b7 4576 offlineimap3_0.0~git20210105.00d395b+dfsg-2.debian.tar.xz 1e20522aad05e2fd6ae0b35675ef263a066cbee134cd19513304b06a504c844a 7421 offlineimap3_0.0~git20210105.00d395b+dfsg-2_amd64.buildinfo Files: 8262316f07c0c61076dc4c641724e2eb 2345 mail optional offlineimap3_0.0~git20210105.00d395b+dfsg-2.dsc 750abe8fb7276314376f79933380f4cd 4576 mail optional offlineimap3_0.0~git20210105.00d395b+dfsg-2.debian.tar.xz 227b6e7f86007c10b0ec9169bd2debf9 7421 mail optional offlineimap3_0.0~git20210105.00d395b+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAmAN7AwACgkQR5mjUUbR KzWa/RAArIu2/0mcITucWEeCyW0eel/m74nGK0xKWAEzWPC1c6QoneD/uzjZrGcF +/cOlK0mVaIZ/IaLq4J17YQC8E7ty+LNL0S/ZK7C9jg7BRvT0/qzRFao0IPDz4r7 d7zQrXZRi6DUvWwxDEUPZnGv2eDklVMZ6dyzMEQgKm+eKgMCB/AIV4kDIyE7tbTu QsTl4jwdD7abiPz8rBwvD6fNz6ltGtTqxCUd8YjM9SEvaeKgrgxhTNeqX2D4PWSt bZeq/xRGjnoQFQZ1k9f4fnmGVMNTL/MXZFNZYg2Z9SGzBJlennGOvWPmeQFSf1P9 qk6HrrH5sxehGPkvCyScce0PXnX7djB4D3C6B+XM7LZYII9as7K898Dp8xIomdZi FJT07rmb9yW64dBVKkNVp/Z6pRd7nNXK3oy10j1S+Mh72UT8I0jaUgHsNvS7pkEf VZiyid7NdqBhTP3b9a7xzsRk/jomhFnu21XqfCZ8FQ5EWwubZ5qSd1q7Xbe0uc
Bug#937184: marked as done (offlineimap: Python2 removal in sid/bullseye)
Your message dated Sun, 24 Jan 2021 22:18:50 + with message-id and subject line Bug#937184: fixed in offlineimap3 0.0~git20210105.00d395b+dfsg-2 has caused the Debian Bug report #937184, regarding offlineimap: Python2 removal in sid/bullseye 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.) -- 937184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:offlineimap Version: 7.2.3+dfsg1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:offlineimap If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: offlineimap3 Source-Version: 0.0~git20210105.00d395b+dfsg-2 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of offlineimap3, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated offlineimap3 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, 24 Jan 2021 21:43:56 + Source: offlineimap3 Architecture: source Version: 0.0~git20210105.00d395b+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Sudip Mukherjee Closes: 937184 967184 Changes: offlineimap3 (0.0~git20210105.00d395b+dfsg-2) unstable; urgency=medium . * Add 'offlineimap' transitional package. - Removes python2 dependency from offlineimap. (Closes: #937184, #967184) Checksums-Sha1: c787cff5c4b5e4036459fd04521b8a6c36ef4ff5 2345 offlineimap3_0.0~git20210105.00d395b+dfsg-2.dsc 643e1ff77630efbc8a0b51523cfbc4d1cfeada69 4576 offlineimap3_0.0~git20210105.00d395b+dfsg-2.debian.tar.xz 6f256597869645850f60bf57231a4ccced1e9b94 7421 offlineimap3_0.0~git20210105.00d395b+dfsg-2_amd64.buildinfo Checksums-Sha256: f445cb1a596449918f5d379a877e5437130c81e0468434e01fe31f49209821b8 2345 offlineimap3_0
Processed: Re: python-pgpy: Missing build dependency on python3-wheel
Processing control commands: > tags -1 patch Bug #979037 [src:python-pgpy] python-pgpy: Missing build dependency on python3-wheel Added tag(s) patch. -- 979037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 978032 with 940625
Processing commands for cont...@bugs.debian.org: > block 978032 with 940625 Bug #978032 [src:python-cobra] python-cobra: autopkgtest regression in testing 978032 was not blocked by any bugs. 978032 was not blocking any bugs. Added blocking bug(s) of 978032: 940625 > thanks Stopping processing here. Please contact me if you need assistance. -- 978032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979037: python-pgpy: Missing build dependency on python3-wheel
Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * Add missing build dependency on python3-wheel to fix FTBFS. Thanks for considering the patch. Logan diff -Nru python-pgpy-0.5.3/debian/control python-pgpy-0.5.3/debian/control --- python-pgpy-0.5.3/debian/control2021-01-01 20:15:55.0 -0500 +++ python-pgpy-0.5.3/debian/control2021-01-24 17:02:05.0 -0500 @@ -22,6 +22,7 @@ python3-setuptools, python3-six (>= 1.9.0), python3-sphinx , + python3-wheel Standards-Version: 4.5.1 Vcs-Git: https://github.com/SecurityInnovation/PGPy.git -b debian/master Vcs-Browser: https://github.com/SecurityInnovation/PGPy
Bug#978032: python-cobra: autopkgtest regression in testing
On Thu, Dec 24, 2020 at 09:58:57PM +0200, Graham Inggs wrote:
> Source: python-cobra
> Version: 0.19.0-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: regression
>
> Hi Maintainer
>
> The autopkgtests of python-cobra recently started to fail in testing [1].
> I've copied what I hope is the relevant part of the log below.
>
> Regards
> Graham
>
>
> [1] https://ci.debian.net/packages/p/python-cobra/testing/amd64/
>
>
> ERRORS
>
> __ ERROR at setup of TestManipulation.test_escape_ids
> __
>
> filename = '/usr/lib/python3/dist-packages/cobra/test/data/textbook.xml.gz'
> number =
> f_replace = {'F_GENE': ,
> 'F_GENE_REV': , 'F_GROUP':
> , 'F_GROUP_REV': _f_group_rev at 0x7f75f8531040>, ...}
> kwargs = {}
> doc = 'SBMLDocument *' at 0x7f75f402cc60> >
> cobra_error = CobraSBMLError('Something went wrong reading the SBML
> model. Most likely the SBML model is not valid. Please check
> tha...ame)`\nIf the model is valid and cannot be read please open an
> issue at https://github.com/opencobra/cobrapy/issues .')
This is also a FTBFS.
Trying to upgrade to 0.20.0 for checking whether that would help:
After some minor adjustments the first blocker is missing
diskcache (#940625).
cu
Adrian
Processed: tagging 978257
Processing commands for cont...@bugs.debian.org:
> tags 978257 + fixed-upstream
Bug #978257 [src:pynwb] pynwb: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 returned exit code 13
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 978201 is forwarded to https://github.com/crossbario/autobahn-cpp/commit/eac22bd61117ac18b5efee3c6da16a97835055de
Processing commands for cont...@bugs.debian.org: > forwarded 978201 > https://github.com/crossbario/autobahn-cpp/commit/eac22bd61117ac18b5efee3c6da16a97835055de Bug #978201 [src:autobahn-cpp] autobahn-cpp: FTBFS: wamp_websocketpp_websocket_transport.ipp:55:113: error: ‘::_1’ has not been declared Set Bug forwarded-to-address to 'https://github.com/crossbario/autobahn-cpp/commit/eac22bd61117ac18b5efee3c6da16a97835055de'. > thanks Stopping processing here. Please contact me if you need assistance. -- 978201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gdb-avr: diff for NMU version 7.7-4.1
Processing control commands: > tags 978170 + patch Bug #978170 [src:gdb-avr] gdb-avr: FTBFS: tar (child): /usr/src/gdb.tar.bz2: Cannot open: No such file or directory Added tag(s) patch. > tags 978170 + pending Bug #978170 [src:gdb-avr] gdb-avr: FTBFS: tar (child): /usr/src/gdb.tar.bz2: Cannot open: No such file or directory Added tag(s) pending. -- 978170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978170: gdb-avr: diff for NMU version 7.7-4.1
Control: tags 978170 + patch Control: tags 978170 + pending Dear maintainer, I've prepared an NMU for gdb-avr (versioned as 7.7-4.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru gdb-avr-7.7/debian/changelog gdb-avr-7.7/debian/changelog --- gdb-avr-7.7/debian/changelog 2016-07-14 21:21:43.0 +0300 +++ gdb-avr-7.7/debian/changelog 2021-01-24 23:30:28.0 +0200 @@ -1,3 +1,10 @@ +gdb-avr (7.7-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Adjust to gdb-source changes. (Closes: #978170) + + -- Adrian Bunk Sun, 24 Jan 2021 23:30:28 +0200 + gdb-avr (7.7-4) unstable; urgency=medium * Removed non-free manpage (closes: #828894) diff -Nru gdb-avr-7.7/debian/rules gdb-avr-7.7/debian/rules --- gdb-avr-7.7/debian/rules 2016-07-14 20:24:15.0 +0300 +++ gdb-avr-7.7/debian/rules 2021-01-24 23:30:28.0 +0200 @@ -29,7 +29,7 @@ unpack: unpack-stamp unpack-stamp: - tar xjf /usr/src/gdb.tar.bz2 + tar xf /usr/src/gdb.tar.* mv gdb* src mkdir build touch unpack-stamp
Bug#957183: marked as done (eukleides: ftbfs with GCC-10)
Your message dated Sun, 24 Jan 2021 21:33:22 + with message-id and subject line Bug#957183: fixed in eukleides 1.5.4-4.3 has caused the Debian Bug report #957183, regarding eukleides: ftbfs with GCC-10 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.) -- 957183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:eukleides Version: 1.5.4-4.1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/eukleides_1.5.4-4.1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] dpkg-buildpackage: info: source version 1.5.4-4.1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Matthias Klose dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp configure-stamp /usr/bin/make clean make[1]: Entering directory '/<>' Cleaning binaries Cleaning documentation Cleaning man pages make[1]: Leaving directory '/<>' dh_clean debian/rules build dh_testdir CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" /usr/bin/make make[1]: Entering directory '/<>' Making eukleides Building parser Building lexer Making dependencies Building triangle.o Building error.o Building io.o ../src/common/io.c: In function ‘input_num’: ../src/common/io.c:173:2: warning: ignoring return value of ‘fscanf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 173 | fscanf(data_file, "%lf", &x); | ^~~~ Building interactive.o Building number.o Building compiler.o Building locus.o Building core.o Building setting.o Building utils.o Building function.o Building keywords.o Building test.o Building vector.o Building quadrilateral.o Building conic.o Building variable.o Building line.o Building intersection.o Building strings.o Building circle.o Building point.o Building set.o Building symbol.o Building check.o Building draw.o Building main.o Building args.o Building parser.tab.o Building lex.yy.o Linking eukleides /usr/bin/ld: eukleides_build/quadrilateral.o:./build/../src/common/quadrilateral.c:29: multiple definition of `x'; eukleides_build/triangle.o:./build/../src/common/triangle.c:31: first defined here /usr/bin/ld: eukleides_build/quadrilateral.o:./build/../src/common/quadrilateral.c:29: multiple definition of `y'; eukleides_build/triangle.o:./build/../src/common/triangle.c:31: first defined here /usr/bin/ld: eukleides_build/quadrilateral.o:./build/../src/common/quadrilateral.c:31: multiple definition of `C'; eukleides_build/triangle.o:./build/../src/common/triangle.c:29: first defined here /usr/bin/ld: eukleides_build/quadrilateral.o:./build/../src/common/quadrilateral.c:31: multiple definition of `B'; eukleides_build/triangle.o:./build/../src/common/triangle.c:29: first defined here /usr/bin/ld: eukleides_build/quadrilateral.o:./build/../src/common/quadrilateral.c:31: multiple definition of `A'; eukleides_build/triangle.o:./build/../src/common/triangle.c:29: first defined here collect2: error: ld returned 1 exit status make[2]: *** [Makefile:50: eukleides] Error 1 make[1]: *** [Makefile:16: eukleides] Error 2 make[1]: Leaving
Bug#980965: pdns-recursor: flaky autopkgtest on ppc64el
I've uploaded a new revision showing journal output on restart. Maybe that will help debugging this. Also: it would be great if I could get email for test failures. Chris
Bug#980964: pdns: flaky autopkgtest on s390x
Hi, * Paul Gevers [210124 21:51]: > Please do get in touch if we need to dive into this together. Or if you > want to discuss this issue. [..] > + service pdns restart > Job for pdns.service failed because the control process exited with > error code. > See "systemctl status pdns.service" and "journalctl -xe" for details. > + kill -TERM 1986 > autopkgtest [19:05:43]: test smoke-mysql: ---] Yeah, I think we need to look into this (and #980965) together. I don't see why this would "just fail randomly". I don't think its a timing thing. Maybe this worker is weird in a different way. Chris
Processed: bats breaks ruby-build autopkgtest: /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found
Processing control commands: > found -1 bats/1.2.1-1 Bug #980967 [src:bats] bats breaks ruby-build autopkgtest: /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found Marked as found in versions bats/1.2.1-1. > affects -1 ruby-build Bug #980967 [src:bats] bats breaks ruby-build autopkgtest: /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found Added indication that 980967 affects ruby-build -- 980967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980967: bats breaks ruby-build autopkgtest: /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found
Source: bats Control: found -1 bats/1.2.1-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Control: affects -1 ruby-build Dear maintainer(s), With a recent upload of bats the autopkgtest of ruby-build fails in testing when that autopkgtest is run with the binary packages of bats from unstable. It passes when run with only packages from testing. In tabular form: passfail bats from testing1.2.1-1 ruby-build from testing20200401-1 all others from testingfrom testing I copied some of the output at the bottom of this report. It really looks like bats functionality is broken. Currently this regression is blocking the migration of bats to testing [1]. Can you please investigate the situation and fix the problem? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=bats https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-build/9965546/log.gz autopkgtest [06:12:14]: test command1: bats test/ autopkgtest [06:12:14]: test command1: [--- 1..100 /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line 194: bats-exec-test: command not found /usr/libexec/bats-core/bats-exec-file: line
Bug#979865: m2crypto FTBFS on IPV6-only buildds
On Sun, Jan 24, 2021 at 07:48:55PM +0100, Sebastian Andrzej Siewior wrote: > On 2021-01-12 08:22:05 [+0200], Adrian Bunk wrote: > > Source: m2crypto > > Version: 0.37.1-1 > > Severity: serious > > Tags: ftbfs > > I suggest to lower the severity to important The release team considers these bugs release critical. > and let it migrate to > testing. After all this bug did not first appear in 0.37.1-1, >... If this is true, then the proper action would be a found indicating the first broken version. > Sebastian cu Adrian
Bug#980965: pdns-recursor: flaky autopkgtest on ppc64el
Source: pdns-recursor Version: 4.4.2-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), Your package has an autopkgtest, great. However, I looked into the history of your autopkgtest [1] on ppc64el (because it is blocking boost1.74) and I noticed it fails regularly, while a rerun passes. I copied some of the output at the bottom of this report. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Please do get in touch if we need to dive into this together. Or if you want to discuss this issue. I noticed that all the failed runs I checked were done on the same worker. Could the problem be a timing issue? (The worker has a spinning disk and is slower than our other workers). Paul https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/pdns-recursor/9755158/log.gz autopkgtest [06:22:39]: test smoke: [--- + cat + cat + service pdns-recursor restart Job for pdns-recursor.service failed because the control process exited with error code. See "systemctl status pdns-recursor.service" and "journalctl -xe" for details. autopkgtest [06:23:05]: test smoke: ---] OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: pdns: flaky autopkgtest on s390x
Processing control commands: > retitle -1 pdns: flaky autopkgtest on ppc64el Bug #980964 [src:pdns] pdns: flaky autopkgtest on s390x Changed Bug title to 'pdns: flaky autopkgtest on ppc64el' from 'pdns: flaky autopkgtest on s390x'. -- 980964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980964: pdns: flaky autopkgtest on s390x
Control: retitle -1 pdns: flaky autopkgtest on ppc64el Hi, On 24-01-2021 21:50, Paul Gevers wrote: > Your package has an autopkgtest, great. However, I looked into > the history of your autopkgtest [1] on s390x (because it is blocking Should read ppc64el. > https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/pdns/9891909/log.gz As mentioned here. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#980964: pdns: flaky autopkgtest on s390x
Source: pdns Version: 4.4.0-3 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), Your package has an autopkgtest, great. However, I looked into the history of your autopkgtest [1] on s390x (because it is blocking boost1.74) and I noticed it fails regularly, while a rerun passes. I copied some of the output at the bottom of this report. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Please do get in touch if we need to dive into this together. Or if you want to discuss this issue. Paul https://ci.debian.net/data/autopkgtest/testing/ppc64el/p/pdns/9891909/log.gz autopkgtest [19:02:43]: test smoke-bind: [--- + ZONE=bind.example.org + cat + cat + service pdns restart Job for pdns.service failed because the control process exited with error code. See "systemctl status pdns.service" and "journalctl -xe" for details. autopkgtest [19:03:09]: test smoke-bind: ---] autopkgtest [19:04:56]: test smoke-mysql: [--- + service mysql stop + trap 'kill -TERM $DB_SERVER_PID' EXIT TERM INT + DB_SERVER_PID=1986 + mysqladmin ping + /usr/bin/mysqld_safe mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists! + sleep 0.5 210122 19:05:22 mysqld_safe Logging to syslog. 210122 19:05:22 mysqld_safe Starting mariadbd daemon with databases from /var/lib/mysql + mysqladmin ping mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists! + sleep 0.5 + mysqladmin ping mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists! + sleep 0.5 + mysqladmin ping mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists! + sleep 0.5 + mysqladmin ping mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists! + sleep 0.5 + mysqladmin ping mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists! + sleep 0.5 + mysqladmin ping mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists! + sleep 0.5 + mysqladmin ping mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/run/mysqld/mysqld.sock' exists! + sleep 0.5 + mysqladmin ping mysqld is alive + DBNAME=pdns + DBUSER=pdns + ZONE=mysql.example.org + cat + mysql --user=root mysql + mysql -uroot pdns + find /etc/powerdns/pdns.d/ -type f -delete + cat /usr/share/doc/pdns-backend-mysql/examples/gmysql.conf + sed -e ' s/_DBSERVER_/127.0.0.1/; s/_DBPORT_/3306/; s/_DBNAME_/pdns/; s/_DBUSER_/pdns/; s/_DBPASS_/password/; ' + chmod 0640 /etc/powerdns/pdns.d/gmysql.conf + chgrp pdns /etc/powerdns/pdns.d/gmysql.conf + cat /etc/powerdns/pdns.d/gmysql.conf # See https://doc.powerdns.com/authoritative/backends/generic-mysql.html launch+=gmysql # # gmysql-dbname Database name to connect to # # gmysql-dbname=powerdns gmysql-dbname=pdns # # gmysql-dnssec Enable DNSSEC processing # # gmysql-dnssec=no gmysql-dnssec=yes # # gmysql-group Database backend MySQL 'group' to connect as # # gmysql-group=client # # gmysql-host Database backend host to connect to # # gmysql-host= gmysql-host=127.0.0.1 # # gmysql-innodb-read-committed Use InnoDB READ-COMMITTED transaction isolation level # # gmysql-innodb-read-committed=yes # # gmysql-password Database backend password to connect with # # gmysql-password= gmysql-password=passw
Bug#892326: marked as done (herisvm: tests fail)
Your message dated Sun, 24 Jan 2021 20:24:04 + with message-id and subject line Bug#892326: fixed in herisvm 0.9.0-1 has caused the Debian Bug report #892326, regarding herisvm: tests fail 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.) -- 892326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: herisvm Version: 0.7.0-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/herisvm.html ... FAILED --- /tmp/herisvm.16571/1 2018-03-07 22:19:44.792884621 -1200 +++ /tmp/herisvm.16571/2 2018-03-07 22:20:03.535690938 -1200 @@ -1,20 +1,6 @@ Total statistics Class 0 P, R, F1: 0.973 36/37 , 0.9 36/40 , 0.9351 Class 1 P, R, F1: 0.875 28/32 , 0.965528/29 , 0.918 Accuracy : 0.927564/69 Total cross-folds statistics - Macro average max/std deviation(P) : 12.5 %4.55 - Class 0 max/std deviation(P) : 11.1 %4.97 - Class 1 max/std deviation(P) : 25 %11 - - Macro average max/std deviation(R) : 12.5 %4.52 - Class 0 max/std deviation(R) : 25 %10.5 - Class 1 max/std deviation(R) : 16.7 %7.45 - - Macro average max/std deviation(F1) : 14.3 %5.06 - Class 0 max/std deviation(F1) : 14.3 %5.08 - Class 1 max/std deviation(F1) : 14.3 %5.15 - -max/std deviation(A) : 14.3 %5.06 - heri-eval #8.1 -p -t2... /build/1st/herisvm-0.7.0/scripts/heri-stat-addons:123:in `%': incomplete format specifier; use %% (double %) instead (ArgumentError) from /build/1st/herisvm-0.7.0/scripts/heri-stat-addons:123:in `block (2 levels) in ' from /build/1st/herisvm-0.7.0/scripts/heri-stat-addons:120:in `each' from /build/1st/herisvm-0.7.0/scripts/heri-stat-addons:120:in `block in ' from /build/1st/herisvm-0.7.0/scripts/heri-stat-addons:111:in `each' from /build/1st/herisvm-0.7.0/scripts/heri-stat-addons:111:in `' FAILED --- /tmp/herisvm.16571/1 2018-03-07 22:20:06.139525113 -1200 +++ /tmp/herisvm.16571/2 2018-03-07 22:21:09.043519516 -1200 @@ -37,34 +37,20 @@ Class 0 P, R, F1: 1 8/8 , 1 8/8 , 1 Class 1 P, R, F1: 1 6/6 , 1 6/6 , 1 Accuracy : 1 14/14 Fold 2x4 statistics Class 0 P, R, F1: 1 7/7 , 0.875 7/8 , 0.9333 Class 1 P, R, F1: 0.8571 6/7 , 1 6/6 , 0.9231 Accuracy : 0.928613/14 Fold 2x5 statistics Class 0 P, R, F1: 1 8/8 , 1 8/8 , 1 Class 1 P, R, F1: 1 5/5 , 1 5/5 , 1 Accuracy : 1 13/13 Total statistics Class 0 P, R, F1: 0.973 72/74 , 0.9 72/80 , 0.9351 Class 1 P, R, F1: 0.875 56/64 , 0.965556/58 , 0.918 Accuracy : 0.9275 128/138 Total cross-folds statistics - Macro average max/std deviation(P) : 14.6 %6.42 - Class 0 max/std deviation(P) : 12.5 %5.27 - Class 1 max/std deviation(P) : 25 %10.3 - - Macro average max/std deviation(R) : 14.6 %6.43 - Class 0 max/std deviation(R) : 25 %9.86 - Class 1 max/std deviation(R) : 16.7 %7.03 - - Macro average max/std deviation(F1) : 14.6 %6.81 - Class 0 max/std deviation(F1) : 14.3 %6.34 - Class 1 max/std deviation(F1) : 16.7 %7.34 - -max/std deviation(A) : 14.3 %6.73 - heri-eval #9.1 -M tfc... FAILED --- /tmp/herisvm.16571/1 2018-03-07 22:21:12.519298211 -1200 +++ /tmp/herisvm.16571/2 2018-03-07 22:21:37.165729032 -1200 @@ -1,33 +1,25 @@ Fold 1x1 statistics Class 0 P, R, F1: 0.95 19/20 , 0.95 19/20 , 0.95 Class 1 P, R, F1: 0.933314/15 , 0.933314/15 , 0.9333 Accuracy : 0.942933/35 Macro average P, R, F1: 0.9417 , 0.9417 , 0.9417 Fold 1x2 statistics Class 0 P, R, F1: 1
Processed: tagging 980935, tagging 979970, notfixed 977371 in facter/3.14.12-1+b2
Processing commands for cont...@bugs.debian.org:
> tags 980935 + sid bullseye
Bug #980935 [pyzo] pyzo: Crash at startup with python3.9
Added tag(s) sid and bullseye.
> tags 979970 + experimental
Bug #979970 [libselinux1] libselinux1: dependency to newer libc6 ignored
by/missing for aptitude
Added tag(s) experimental.
> notfixed 977371 facter/3.14.12-1+b2
Bug #977371 {Done: Radoslav Bodó } [facter] facter segfault
inside libleatherman/libboost-filesystem
The source facter and version 3.14.12-1+b2 do not appear to match any binary
packages
No longer marked as fixed in versions facter/3.14.12-1+b2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977371
979970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979970
980935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979641: src:kboot-utils: invalid maintainer address
Hi Antonio, kboot-utils, one of the packages you maintain in Debian has an old, unreachable Maitainer address. Could you please update it to prevent it from getting removed? See below the original bug report. Best, On 2021/01/09 06:04 PM, Ansgar wrote: > Source: kboot-utils > Version: 0.4-1 > Severity: serious > Tags: bullseye sid > X-Debbugs-Cc: Holger Levsen > > The maintainer address is invalid, see below. > > Ansgar > > Start of forwarded message > From: Mail Delivery System > Subject: Mail delivery failed: returning message to sender > Date: Sat, 09 Jan 2021 16:49:56 + > > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > osp...@studenti.unina.it > host fmvip.unina.it [192.132.34.7] > SMTP error from remote mail server after RCPT > TO:: > 550 5.1.1 ... User unknown > Reporting-MTA: dns; muffat.debian.org > > Action: failed > Final-Recipient: rfc822;osp...@studenti.unina.it > Status: 5.0.0 > Remote-MTA: dns; fmvip.unina.it > Diagnostic-Code: smtp; 550 5.1.1 ... User unknown -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#978079: heads up: rapid-photo-downloader might not make it to bullseye
On 2021-01-24 14:59:03, Antoine Beaupré wrote: > Hi, > > It seems like rapid-photo-downloader will not make it into the next > Debian stable release (bullseye). It depends on "rawkit" (which I happen > to maintain for some reason), and *that* package fails with newer libraw > versions: > > https://bugs.debian.org/978079 > > I'm not sure how to fix this, and I don't have the cycles to do so right > now. But since you're the RPD maintainer, I figured you might have extra > motivation to fix this... Otherwise I'm afraid we won't be able to ship > RPD with Debian starting with bullseye, which would really be a shame... > > It might be worth bringing this up with upstream as well, if you can > find the time... Actually, I just found out that there's an active fork which fixes those problems, called rawpy: https://discuss.pixls.us/t/rawkit-unmaintained-path-forward-for-rapid-photo-downloader/14299 There's a patch in Arch to port rawkit to libraw19, but I feel it would be ill-advised to carry such a hack through a stable Debian release. So I think the way forward for RPD is to package rawpy, remove rawkit, and have RPD depend on rawpy. I don't have time to do this work myself and, since RPD is the only thing that needs rawkit in Debian, I would suggest you take on the dependency as well. Unfortunately, this would need to happen in the coming week, otherwise we'll miss the NEW window before the soft freeze (2021-02-12). Do you have time to deal with this until then? Thanks, a. -- The flesh you so fancifully fry Is not succulent, tasty or kind It's death for no reason And death for no reason is murder - Morrissey
Bug#978079: heads up: rapid-photo-downloader might not make it to bullseye
Hi, It seems like rapid-photo-downloader will not make it into the next Debian stable release (bullseye). It depends on "rawkit" (which I happen to maintain for some reason), and *that* package fails with newer libraw versions: https://bugs.debian.org/978079 I'm not sure how to fix this, and I don't have the cycles to do so right now. But since you're the RPD maintainer, I figured you might have extra motivation to fix this... Otherwise I'm afraid we won't be able to ship RPD with Debian starting with bullseye, which would really be a shame... It might be worth bringing this up with upstream as well, if you can find the time... a. -- Advertisers, not governments, are the primary censors of media content in the United States today. - C. Edwin Baker
Processed: bug 978079 is forwarded to https://github.com/photoshell/rawkit/issues/155
Processing commands for cont...@bugs.debian.org: > forwarded 978079 https://github.com/photoshell/rawkit/issues/155 Bug #978079 [python3-rawkit] python3-rawkit: Support for libraw20 missing Set Bug forwarded-to-address to 'https://github.com/photoshell/rawkit/issues/155'. > thanks Stopping processing here. Please contact me if you need assistance. -- 978079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967170: markupsafe: Unversioned Python removal in sid/bullseye
Control: fixed -1 1.1.1-1 Control: close -1 On Sun, Jan 24, 2021 at 09:12:04AM +0100, Jann Haber wrote: > fixed -1 1.1.1-1 > close -1 > thanks > > Looking at the package, it seems like this bug has been fixed in version > 1.1.1-1 - I can find no more references to unversioned python in that > version. I marked the bug as fixed. Please re-open if I am mistaken. > > Best, > Jann > > On Tue, 04 Aug 2020 09:28:33 + Matthias Klose wrote: > > Package: src:markupsafe > > Version: 1.1.1-1 > > Severity: serious > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2unversioned > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > > > We will keep some Python2 package as discussed in > > https://lists.debian.org/debian-python/2020/07/msg00039.html > > but removing the unversioned python packages python-minimal, python, > > python-dev, python-dbg, python-doc. > > > > Your package either build-depends, depends on one of those packages. > > Please either convert these packages to Python3, or if that is not > > possible, replaces the dependencies on the unversioned Python > > packages with one of the python2 dependencies (python2, python2-dev, > > python2-dbg, python2-doc). > > > > Please check for dependencies, build dependencies AND autopkg tests. > > > > If there are questions, please refer to the wiki page for the removal: > > https://wiki.debian.org/Python/2Removal, or ask for help on IRC > > #debian-python, or the debian-pyt...@lists.debian.org mailing list. > > > > signature.asc Description: PGP signature
Processed: Re: Bug#967170: markupsafe: Unversioned Python removal in sid/bullseye
Processing control commands: > fixed -1 1.1.1-1 Bug #967170 [src:markupsafe] markupsafe: Unversioned Python removal in sid/bullseye Marked as fixed in versions markupsafe/1.1.1-1. > close -1 Bug #967170 [src:markupsafe] markupsafe: Unversioned Python removal in sid/bullseye Marked Bug as done -- 967170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#978079: python3-rawkit: Support for libraw20 missing
Processing control commands: > forward -1 https://github.com/photoshell/rawkit/issues/155 Unknown command or malformed arguments to command. > tags -1 +confirmed Bug #978079 [python3-rawkit] python3-rawkit: Support for libraw20 missing Ignoring request to alter tags of bug #978079 to the same tags previously set -- 978079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#978079: python3-rawkit: Support for libraw20 missing
Processing control commands: > forward -1 https://github.com/photoshell/rawkit/issues/155 Unknown command or malformed arguments to command. > tags -1 +confirmed Bug #978079 [python3-rawkit] python3-rawkit: Support for libraw20 missing Added tag(s) confirmed. -- 978079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978079: python3-rawkit: Support for libraw20 missing
Control: forward -1 https://github.com/photoshell/rawkit/issues/155 Control: tags -1 +confirmed On 2020-12-25 16:58:42, Kendy Kutzner wrote: > sudo aptitude install libraw20 python3-rawkit > python3 from rawkit.raw import Raw r=Raw(filename='1608680820.cr2') > [...] > ImportError: Unsupported Libraw version: 0.20.2. > > I'm using bullseye/sid. Unfortunately, not only does it look like an upstream issue with no fix, but worse, it seems like upstream is dead. Or at least, the git repository is "archived": https://github.com/photoshell/rawkit/ ... not sure what to make of this :( a. -- By now the computer has moved out of the den and into the rest of your life. It will consume all of your spare time, and even your vacation, if you let it. It will empty your wallet and tie up your thoughts. It will drive away your family. Your friends will start to think of you as a bore. And what for? - The True Computerist by Tom Pittman
Bug#980957: llvm-toolchain-11 autopkgtest segfaults on armhf
Source: llvm-toolchain-11
Version: 1:11.0.0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainers,
You package has an autopkgtest, great. However, it fails on armhf with a
segfault.
The error code is unfortunate as autopkgtest interprets it as a tmpfail,
so the test is tried over and over again. I'll put the failure on the
ci.d.n blocklist, to avoid that, and will lift the block when this bug
is closed.
Paul
https://ci.debian.net/data/autopkgtest/testing/armhf/l/llvm-toolchain-11/9960854/log.gz
echo '#include
int main() {
if (1==1) {
printf("true");
}else{
printf("false");
return 42;
}
return 0;}' > foo.c
Testing linking ...
rm foo bar.cc
clang-$VERSION -flto foo.c -o foo
clang: error: unable to execute command: Segmentation fault
clang: error: linker command failed due to signal (use -v to see invocation)
autopkgtest [02:17:39]: ERROR: testbed failure: testbed auxverb failed
with exit code 254
OpenPGP_signature
Description: OpenPGP digital signature
Bug#980956: r-cran-magrittr breaks r-cran-dbplyr autopkgtest: could not find function "split_chain"
Source: r-cran-magrittr, r-cran-dbplyr
Control: found -1 r-cran-magrittr/2.0.1-1
Control: found -1 r-cran-dbplyr/1.4.4-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Control: block 980851 by -1
Dear maintainer(s),
With a recent upload (62 days ago) of r-cran-magrittr the autopkgtest of
r-cran-dbplyr fails in testing when that autopkgtest is run with the
binary packages of r-cran-magrittr from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
r-cran-magrittrfrom testing2.0.1-1
r-cran-dbplyr from testing2.0.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of r-cran-magrittr
to testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=r-cran-magrittr
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-dbplyr/9966925/log.gz
autopkgtest [08:12:46]: test run-unit-test: [---
BEGIN TEST testthat.R
R version 4.0.3 (2020-10-10) -- "Bunny-Wunnies Freak Out"
Copyright (C) 2020 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> library(testthat)
> library(dbplyr)
>
> test_check("dbplyr")
Registering testing src: sqlite OK
══ Skipped tests
═══
● identical(Sys.getenv("GITHUB_POSTGRES"), "true") is not TRUE (1)
● Need at least two srcs to compare (6)
● No MariaDB (3)
● No mssql (2)
● No postgres (2)
● On CRAN (60)
══ Failed tests
── Error (test-translate-sql.R:75:3): magrittr pipe is translated
──
Error: could not find function "split_chain"
Backtrace:
█
1. ├─testthat::expect_identical(translate_sql(1 %>% is.na()),
translate_sql(is.na(1))) test-translate-sql.R:75:2
2. │ └─testthat::quasi_label(enquo(object), label, arg = "object")
3. │ └─rlang::eval_bare(expr, quo_get_env(quo))
4. ├─dbplyr::translate_sql(1 %>% is.na())
5. │ └─dbplyr::translate_sql_(...)
6. │ └─base::lapply(...)
7. │ └─dbplyr:::FUN(X[[i]], ...)
8. │ ├─dbplyr::escape(eval_tidy(x, mask), con = con)
9. │ └─rlang::eval_tidy(x, mask)
10. └─1 %>% is.na()
[ FAIL 1 | WARN 0 | SKIP 74 | PASS 662 ]
Error: Test failures
Execution halted
autopkgtest [08:13:01]: test run-unit-test: ---]
OpenPGP_signature
Description: OpenPGP digital signature
Processed: r-cran-magrittr breaks r-cran-dbplyr autopkgtest: could not find function "split_chain"
Processing control commands:
> found -1 r-cran-magrittr/2.0.1-1
Bug #980956 [src:r-cran-magrittr, src:r-cran-dbplyr] r-cran-magrittr breaks
r-cran-dbplyr autopkgtest: could not find function "split_chain"
Marked as found in versions r-cran-magrittr/2.0.1-1.
> found -1 r-cran-dbplyr/1.4.4-1
Bug #980956 [src:r-cran-magrittr, src:r-cran-dbplyr] r-cran-magrittr breaks
r-cran-dbplyr autopkgtest: could not find function "split_chain"
Marked as found in versions r-cran-dbplyr/1.4.4-1.
> block 980851 by -1
Bug #980851 {Done: Paul Gevers } [src:r-cran-magrittr]
src:r-cran-magrittr: fails to migrate to testing for too long: causes
autopkgtest regression
980851 was not blocked by any bugs.
980851 was not blocking any bugs.
Added blocking bug(s) of 980851: 980956
--
980851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980851
980956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#936345: marked as done (crossfire-maps: Python2 removal in sid/bullseye)
Your message dated Sun, 24 Jan 2021 19:18:42 + with message-id and subject line Bug#936345: fixed in crossfire-maps 1.75.0+dfsg1-1 has caused the Debian Bug report #936345, regarding crossfire-maps: Python2 removal in sid/bullseye 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.) -- 936345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:crossfire-maps Version: 1.71.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:crossfire-maps If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: crossfire-maps Source-Version: 1.75.0+dfsg1-1 Done: Kari Pahula We believe that the bug you reported is fixed in the latest version of crossfire-maps, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kari Pahula (supplier of updated crossfire-maps 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, 24 Jan 2021 20:27:20 +0200 Source: crossfire-maps Architecture: source Version: 1.75.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Kari Pahula Changed-By: Kari Pahula Closes: 936345 965469 Changes: crossfire-maps (1.75.0+dfsg1-1) unstable; urgency=medium . * New upstream release. * Standards-Version 4.5.1 and DH compat 13. (Closes: #965469) * Drop cdbs. * Use --with python3. (Closes: #936345) * Repackaged to remove a script with an NC license and other cruft. Checksums-Sha1: eaafd2b8e028b978e47cffee3e20c3d3ef28010f 1834 crossfire-maps_1.75.0+dfsg1-1.dsc 9b443664064622a3274c5efb69003b7fb1e3c717 14810260 crossfire-maps_1.75.0+dfsg1.orig.tar.xz 335ce9b424a2393137750eb646f8c17345d1d9e6 3384 crossfire-maps_1.75.0+dfsg1-1.debian.tar.xz a79be87b35f7afbb33f484cc01e3fefb69b7ea2d 6876 crossfire-maps_1.75.0+dfsg1-1_source.buildinfo Checksums-Sha256: 358a
Bug#936344: marked as done (crossfire: Python2 removal in sid/bullseye)
Your message dated Sun, 24 Jan 2021 19:18:33 + with message-id and subject line Bug#936344: fixed in crossfire 1.75.0-1 has caused the Debian Bug report #936344, regarding crossfire: Python2 removal in sid/bullseye 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.) -- 936344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:crossfire Version: 1.71.0+dfsg1-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:crossfire If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: crossfire Source-Version: 1.75.0-1 Done: Kari Pahula We believe that the bug you reported is fixed in the latest version of crossfire, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kari Pahula (supplier of updated crossfire 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, 24 Jan 2021 20:02:52 +0200 Source: crossfire Architecture: source Version: 1.75.0-1 Distribution: unstable Urgency: medium Maintainer: Kari Pahula Changed-By: Kari Pahula Closes: 936344 Changes: crossfire (1.75.0-1) unstable; urgency=medium . * Standards-Version 4.5.1 * New upstream release. * Switch to use DH in debian/rules, dh compat 13. * Add a postinst script to convert python2 shelve files to python3. * Build with Python 3 (Closes: #936344) Checksums-Sha1: aa07f86c2939df7a025cb31372a8ce6dc49f321e 1959 crossfire_1.75.0-1.dsc e1a4406186aa437391a2872b5592a43e 7199792 crossfire_1.75.0.orig.tar.gz 89b77bee684771e3ee04ea7abc9a441c6d5e2e6a 8448 crossfire_1.75.0-1.debian.tar.xz 4a7acf4ed2ada2d3b5c4bbfdd0bc5abc60c3e178 7187 crossfire_1.75.0-1_source.buildinfo Checksums-Sha256: b0ccbca64224b5dbce86a42c42c908abb4ccbaa98afb1bce7adf070ff97580d5 1959 crossfire_1.75.0-1.dsc 0441832166f6eece9d64a8a724b
Bug#980951: erlang-ranch: FTBFS: ssl:cipher_suites/0 is deprecated
Source: erlang-ranch Severity: serious Version: 1.3.0-2 X-Debbugs-CC: iwama...@debian.org t...@debian.org Dear Debian erlang-ranch package maintainers, Current erlang-ranch/1.3.0-2 fails to build from source. The main error is as follows: dh build dh_update_autotools_config dh_autoreconf dh_auto_configure debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make SKIP_DEPS=yes make[2]: Entering directory '/<>' DEPEND ranch.d ERLC ranch.erl ranch_acceptor.erl ranch_acceptors_sup.erl ranch_app.erl ranch_conns_sup.erl ranch_listener_sup.erl ranch_protocol.erl ranch_server.erl ranch_ssl.erl ranch_sup.erl ranch_tcp.erl ranch_transport.erl compile: warnings being treated as errors src/ranch_ssl.erl:237: ssl:cipher_suites/0 is deprecated and will be removed in OTP 24; use use cipher_suites/2,3 instead src/ranch_ssl.erl:239: ssl:cipher_suites/0 is deprecated and will be removed in OTP 24; use use cipher_suites/2,3 instead make[3]: *** [erlang.mk:5069: ebin/ranch.app] Error 1 make[2]: *** [erlang.mk:4872: app] Error 2 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: build] Error 2 = The full buildlog is provided in the attachment. -- Thanks, Boyuan Yang sbuild (Debian sbuild) 0.80.1 (05 December 2020) on hosiet-vm-home +==+ | erlang-ranch 1.3.0-2 (amd64) Sun, 24 Jan 2021 19:08:48 + | +==+ Package: erlang-ranch Version: 1.3.0-2 Source Version: 1.3.0-2 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-a5d3c470-2e25-4528-a683-b7ddc3aaf012' with '<>' I: NOTICE: Log filtering will replace 'build/erlang-ranch-SNSq4k/resolver-4ZEvPD' with '<>' +--+ | Update chroot| +--+ Hit:1 https://incoming.debian.org/debian-buildd buildd-unstable InRelease Hit:2 https://deb.debian.org/debian unstable InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Local sources - /dev/shm/build-area/erlang-ranch_1.3.0-2.dsc exists in /dev/shm/build-area; copying to chroot I: NOTICE: Log filtering will replace 'build/erlang-ranch-SNSq4k/erlang-ranch-1.3.0' with '<>' I: NOTICE: Log filtering will replace 'build/erlang-ranch-SNSq4k' with '<>' +--+ | Install package build dependencies | +--+ Setup apt archive - Merged Build-Depends: debhelper (>= 11), dpkg-dev (>= 1.16.1~), erlang-dev (>= 1:15.b), erlang-eunit (>= 1:15.b), erlang-edoc (>= 1:15.b), libxml2-utils, asciidoc, asciidoc-dblatex, docbook-xml, dblatex, docbook-xsl, erlang-asciideck, build-essential, fakeroot Filtered Build-Depends: debhelper (>= 11), dpkg-dev (>= 1.16.1~), erlang-dev (>= 1:15.b), erlang-eunit (>= 1:15.b), erlang-edoc (>= 1:15.b), libxml2-utils, asciidoc, asciidoc-dblatex, docbook-xml, dblatex, docbook-xsl, erlang-asciideck, build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. Ign:1 copy:/<>/apt_archive ./ InRelease Get:2 copy:/<>/apt_archive ./ Release [957 B] Ign:3 copy:/<>/apt_archive ./ Release.gpg Get:4 copy:/<>/apt_archive ./ Sources [444 B] Get:5 copy:/<>/apt_archive ./ Packages [531 B] Fetched 1932 B in 0s (0 B/s) Reading package lists... Reading package lists... Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: asciidoc asciidoc-base asciidoc-common asciidoc-dblatex autoconf automake autopoint autotools-dev bsdextrautils dblatex debhelper dh-autoreconf dh-strip-nondeterminism distro-info-data docbook-dsssl docbook-utils docbook-xml docbook-xsl dwz erlang-asciideck erlang-asn1 erlang-base erlang-crypt
Bug#900599: marked as done ([fceux] include non free file)
Your message dated Sun, 24 Jan 2021 19:03:26 + with message-id and subject line Bug#900599: fixed in fceux 2.3.0+dfsg1-1 has caused the Debian Bug report #900599, regarding [fceux] include non free file 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.) -- 900599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fceux Severity: serious version: 2.2.2+dfsg0-1 The following file source files include material under a non-free license from Unicode Inc. Therefore, it is not possible to ship this in main or contrib. src/utils/ConvertUTF.c This license does not grant any permission to modify the files (thus failing DFSG#3). Moreover, the license grant seems to attempt to restrict use to "products supporting the Unicode Standard" (thus failing DFSG#6). In this case a solution is to use libicu and to remove this code by repacking. If this is a false-positive, please report a bug against Lintian. Refer to https://bugs.debian.org/823100 for details. signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: fceux Source-Version: 2.3.0+dfsg1-1 Done: Joseph Nahmias We believe that the bug you reported is fixed in the latest version of fceux, 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 900...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joseph Nahmias (supplier of updated fceux 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, 24 Jan 2021 13:43:30 -0500 Source: fceux Architecture: source Version: 2.3.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Joseph Nahmias Changed-By: Joseph Nahmias Closes: 880770 900599 Changes: fceux (2.3.0+dfsg1-1) unstable; urgency=medium . * [8335acb] d/watch: use sf.net redirector on qa.d.o * [6127cf0] have uscan repack the downloaded tarball * [0143014] have gbp use DEP-14 repo layout * [2fcf17c] remove non-free UTF conversion code which is only used on windows (Closes: #900599) * [ccddd79] update VCS-* headers to point to salsa repo * [c79122b] New upstream version 2.3.0+dfsg1 * [85ffcf0] update maintainer address * [aa54847] d/control: expand B-D to one per line and sort * [6806127] bump dh-compat to 13 * [58a89f6] drop old patches * [c71bcae] update to use new upstream build system - cmake (Closes: #880770) * [b6a8507] remove non-free ConvertUTF from build list * [65263c5] d/control: set R-R-R to no * [53fa926] install fceux to /usr/games * [457ef83] build & install fceux-server as well * [4383769] drop prohibited menu entry * [c34a499] drop redundant mime entry; .desktop handles this * [e145ace] enable all hardening flags * [54c1de2] d/control: change priority to optional (from extra) * [a10bf37] d/control: bump S-V to 4.5.1, changes committed individually * [6fad12b] update copyrights * [3888763] fix spelling mistakes caught by lintian * [1924cf5] use correct git repo & commit hash for upstream release * [b625678] use debhelper verbose mode * [8c3626e] use GL vendor neutral dispatch * [ba3050b] note that this version is based on an upstream public release * [bd3f17f] replace upstream's corrupted manpages with original version * [865f0e3] fix fceux-net-server Makefile to honor standard env vars * [ce9c9f8] fceux.desktop: use proper Exec field code * [3be1948] add lua docs to doclist for installation * [ee82ab7] commit updated interim changelog * [a982088] more copyright cleanup * [eb824f5] enable salsa-ci pipeline * [9b5baaa] disable unneeded build-all salsa-ci test Checksums-Sha1: f1667228fc5f0b94aeeef2939ee892e6e2db09fc 1977 fceux_2.3.0+dfsg1-1.dsc 9ecdb83665bf59132990c07933b3b557d58b996b 1765236 fceux_2.3.0+dfsg1.orig.tar.xz ca54e95360f27723a041c2a0fc82661b014cb5ba 14164 fceux_2.3.0+dfsg1-1.debian.tar.xz 6672bcf1a5195d1d269602e53a2c4abceb71b8a0 13292 fceux_2.3.0+dfsg1-1_amd64.buildinfo Checksums-Sha256: a2d1fd2f9cb362808ed898d38139bf0c4f262b4f39613264eaaadbe001ee8751 1977 fceux_2.3.0+dfsg1-1
Bug#880770: marked as done (fceux build depends on removed libgd2*-dev provides)
Your message dated Sun, 24 Jan 2021 19:03:26 + with message-id and subject line Bug#880770: fixed in fceux 2.3.0+dfsg1-1 has caused the Debian Bug report #880770, regarding fceux build depends on removed libgd2*-dev provides 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.) -- 880770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fceux Version: 2.2.2+dfsg0-1 Severity: serious Tags: buster sid The following packages have unmet dependencies: builddeps:fceux : Depends: libgd2-xpm-dev but it is not installable Please change the build dependency to libgd-dev. --- End Message --- --- Begin Message --- Source: fceux Source-Version: 2.3.0+dfsg1-1 Done: Joseph Nahmias We believe that the bug you reported is fixed in the latest version of fceux, 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 880...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joseph Nahmias (supplier of updated fceux 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, 24 Jan 2021 13:43:30 -0500 Source: fceux Architecture: source Version: 2.3.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Joseph Nahmias Changed-By: Joseph Nahmias Closes: 880770 900599 Changes: fceux (2.3.0+dfsg1-1) unstable; urgency=medium . * [8335acb] d/watch: use sf.net redirector on qa.d.o * [6127cf0] have uscan repack the downloaded tarball * [0143014] have gbp use DEP-14 repo layout * [2fcf17c] remove non-free UTF conversion code which is only used on windows (Closes: #900599) * [ccddd79] update VCS-* headers to point to salsa repo * [c79122b] New upstream version 2.3.0+dfsg1 * [85ffcf0] update maintainer address * [aa54847] d/control: expand B-D to one per line and sort * [6806127] bump dh-compat to 13 * [58a89f6] drop old patches * [c71bcae] update to use new upstream build system - cmake (Closes: #880770) * [b6a8507] remove non-free ConvertUTF from build list * [65263c5] d/control: set R-R-R to no * [53fa926] install fceux to /usr/games * [457ef83] build & install fceux-server as well * [4383769] drop prohibited menu entry * [c34a499] drop redundant mime entry; .desktop handles this * [e145ace] enable all hardening flags * [54c1de2] d/control: change priority to optional (from extra) * [a10bf37] d/control: bump S-V to 4.5.1, changes committed individually * [6fad12b] update copyrights * [3888763] fix spelling mistakes caught by lintian * [1924cf5] use correct git repo & commit hash for upstream release * [b625678] use debhelper verbose mode * [8c3626e] use GL vendor neutral dispatch * [ba3050b] note that this version is based on an upstream public release * [bd3f17f] replace upstream's corrupted manpages with original version * [865f0e3] fix fceux-net-server Makefile to honor standard env vars * [ce9c9f8] fceux.desktop: use proper Exec field code * [3be1948] add lua docs to doclist for installation * [ee82ab7] commit updated interim changelog * [a982088] more copyright cleanup * [eb824f5] enable salsa-ci pipeline * [9b5baaa] disable unneeded build-all salsa-ci test Checksums-Sha1: f1667228fc5f0b94aeeef2939ee892e6e2db09fc 1977 fceux_2.3.0+dfsg1-1.dsc 9ecdb83665bf59132990c07933b3b557d58b996b 1765236 fceux_2.3.0+dfsg1.orig.tar.xz ca54e95360f27723a041c2a0fc82661b014cb5ba 14164 fceux_2.3.0+dfsg1-1.debian.tar.xz 6672bcf1a5195d1d269602e53a2c4abceb71b8a0 13292 fceux_2.3.0+dfsg1-1_amd64.buildinfo Checksums-Sha256: a2d1fd2f9cb362808ed898d38139bf0c4f262b4f39613264eaaadbe001ee8751 1977 fceux_2.3.0+dfsg1-1.dsc fc2201505e59998e515ebfc228e84c32c9db645eb13ed946b348931d315ac808 1765236 fceux_2.3.0+dfsg1.orig.tar.xz d7cefcf7ac1236baec4ee99ed6ac9b1e1e732b33bbd838009a3e94e7f34ca968 14164 fceux_2.3.0+dfsg1-1.debian.tar.xz f17adeef9363414600b057cb5fcd30ec4c99fd5def89f0fd006fce4edcb65388 13292 fceux_2.3.0+dfsg1-1_amd64.buildinfo Files: 1d85f2fa57ff57868a79374601849f36 1977 games optional fceux_2.3.0+dfsg1-1.dsc c1981e63e14a2a75331b28670b240d79 1765236 games optional
Bug#979865: m2crypto FTBFS on IPV6-only buildds
On 2021-01-12 08:22:05 [+0200], Adrian Bunk wrote: > Source: m2crypto > Version: 0.37.1-1 > Severity: serious > Tags: ftbfs I suggest to lower the severity to important and let it migrate to testing. After all this bug did not first appear in 0.37.1-1, it has been exposed after it hit buildd that is IPv6 only. The package built on all release architectures by now. Sebastian
Processed: tagging 979970
Processing commands for cont...@bugs.debian.org: > tags 979970 + sid bullseye Bug #979970 [libselinux1] libselinux1: dependency to newer libc6 ignored by/missing for aptitude Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 979970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 979970 in 3.1-1, notfound 979970 in 2.8-1
Processing commands for cont...@bugs.debian.org: > found 979970 3.1-1 Bug #979970 [libselinux1] libselinux1: dependency to newer libc6 ignored by/missing for aptitude Marked as found in versions libselinux/3.1-1. > notfound 979970 2.8-1 Bug #979970 [libselinux1] libselinux1: dependency to newer libc6 ignored by/missing for aptitude No longer marked as found in versions libselinux/2.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 979970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980708: marked as done (trapperkeeper-scheduler-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact com.fasterxml.jackson.core:jackson-core:jar
Your message dated Sun, 24 Jan 2021 17:34:39 + with message-id and subject line Bug#980708: fixed in trapperkeeper-scheduler-clojure 1.1.3-2 has caused the Debian Bug report #980708, regarding trapperkeeper-scheduler-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not been downloaded from it before. 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.) -- 980708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trapperkeeper-scheduler-clojure Version: 1.1.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not been > downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not been > downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact > com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:debian has not > been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:debian > has not been downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact > com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:debian has not > been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:debian > has not been downloaded from it before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/trapperkeeper-scheduler-clojure_1.1.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: trapperkeeper-scheduler-clojure Source-Version: 1.1.3-2 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of trapperkeeper-scheduler-clojure, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated trapperkeeper-scheduler-clojure 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, 24 Jan 2021 12:12:22 -0500 Source: trapperkeeper-scheduler-clojure Binary: libtrapperkeeper-scheduler-clojure Architecture: source all Version: 1.1.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Louis-Philippe Véronneau Description: libtrapperkeeper-scheduler-clojure - Trapperkeeper service for scheduling background tasks Closes: 980708 Changes: trapperkeeper-scheduler-clojure (1.1.3-2) u
Bug#971316: marked as done (onionbalance: Switch to python3-pycryptodome)
Your message dated Sun, 24 Jan 2021 17:34:08 + with message-id and subject line Bug#971316: fixed in onionbalance 0.2.0-4 has caused the Debian Bug report #971316, regarding onionbalance: Switch to python3-pycryptodome 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.) -- 971316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: onionbalance Version: 0.2.0-3 Severity: important Tags: sid bullseye Usertags: pycrypto Dear maintainer, onionbalance currently Build-Depends or Depends on python3-crypto from PyCrypto. This project is no longer maintained and PyCryptodome (https://www.pycryptodome.org/en/latest/) provides a drop in replacement. Please switch to python3-pycryptodome. I'd like to remove python-crypto before the release of bullseye. Cheers --- End Message --- --- Begin Message --- Source: onionbalance Source-Version: 0.2.0-4 Done: Federico Ceratto We believe that the bug you reported is fixed in the latest version of onionbalance, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Federico Ceratto (supplier of updated onionbalance 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, 24 Jan 2021 15:38:48 + Source: onionbalance Architecture: source Version: 0.2.0-4 Distribution: unstable Urgency: high Maintainer: Federico Ceratto Changed-By: Federico Ceratto Closes: 971316 Changes: onionbalance (0.2.0-4) unstable; urgency=high . * Switch to python3-pycryptodome (Closes: #971316) Checksums-Sha1: 555eed6a8afd6754d12a791d4d8684c00aa6bc52 2195 onionbalance_0.2.0-4.dsc 4fb3183c24f3c273d89004b2a398ea6a2fa3534d 13964 onionbalance_0.2.0-4.debian.tar.xz 265d7eb5bb27981baa822fd6f1b9c4f1cdf1192a 7962 onionbalance_0.2.0-4_amd64.buildinfo Checksums-Sha256: d53c018fa50a703f238ddc9b3edd7e20d0625522468e0aad3a81096206ed9fb5 2195 onionbalance_0.2.0-4.dsc d494b1310fd6e15abec3ae2dcccfb7cc78281241c19e6d399855eaa2fbb479fe 13964 onionbalance_0.2.0-4.debian.tar.xz 7765ca025e65a6ddcd3a90620be77f8538f90fef4ef771d20077d8374a8fcd1a 7962 onionbalance_0.2.0-4_amd64.buildinfo Files: 5566121bfa47b6b8b9f56a7d0b28cb61 2195 net optional onionbalance_0.2.0-4.dsc 082516278e1aa6139366d25ccb45aa64 13964 net optional onionbalance_0.2.0-4.debian.tar.xz 855350555eed6fdf14ab2fb37ec95604 7962 net optional onionbalance_0.2.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAmANq1oACgkQbzG8RPUX farUJxAAs0HoQX/ArFNsbCHIno/rBVZNrfjkik+JG8G0cr2JiCdjWkSlO6UbdTUx XLT/CCrj0NlRs78gQiwA5rOTZ86uX0uOhqEy0zkVKlZTfhlleIJ5my5wodZ/nB0P 1Uf7NgHhwbL47j4T2BWMchIEBN3hOxVck/EpKI2rx3W9D71+kZlrnfTBiP8SaEUC ET5l2NC8mqT1AlweLJ6CLZXaDuFNOzZJnCHqOWcJqcyiAzwmPjakl4b/ZZpF+1P+ Jh5JTQeCUoP4jDyJMzhayN7LlOrU7VaB9fkUWdQkLzpXiCKo+9j0677HPx2gBJ/e Kb7xK252aVc3hvtnDcvntAVv5ddN4jUOyuEc57bjRK2tm8Shzxwa5tiLbWlgTSHa mmmbAkM8fU1kijzIu9mXJY9Z8Dx0/QmdMqgRd5i8UzqCk8JW6Z3hBVvAld0C2xVT rmX8r6Ns9EmmjWTe6dpldEef2UjsqXuA1J7mxeB1ZnQmATPkvoXW2he0SC/oFIVH agmzsNZmhucN0EeQ9fKFPcX1b5Esj/b/D3Sag3+Mis4HkpaYUKtuqA3JgGzbwmjp qvVUexTUZ/TD7hMkUy2mkniQ3SEIS/R9zdRr5aJnJoLO261o2pZSKSqU+4W+6vvH isYwEsFRZMEwHiLZ5jhPllNspkdsmVBJlEZEWNK7g6gShzRQRZs= =i7H1 -END PGP SIGNATURE End Message ---
Bug#980676: marked as done (puppetlabs-ring-middleware-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.yaml:snakeyaml:jar:debian has not be
Your message dated Sun, 24 Jan 2021 17:20:38 + with message-id and subject line Bug#980676: fixed in puppetlabs-ring-middleware-clojure 1.3.0-2 has caused the Debian Bug report #980676, regarding puppetlabs-ring-middleware-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.yaml:snakeyaml:jar:debian has not been downloaded from it before. 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.) -- 980676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppetlabs-ring-middleware-clojure Version: 1.3.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > Wrote /<>/debian/pom.xml > lein i18n make > Running 'make i18n' > lein jar > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.yaml:snakeyaml:jar:debian has not been downloaded from it > before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact org.yaml:snakeyaml:jar:debian has not been downloaded from it before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/puppetlabs-ring-middleware-clojure_1.3.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: puppetlabs-ring-middleware-clojure Source-Version: 1.3.0-2 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of puppetlabs-ring-middleware-clojure, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated puppetlabs-ring-middleware-clojure 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, 24 Jan 2021 11:27:28 -0500 Source: puppetlabs-ring-middleware-clojure Architecture: source Version: 1.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Louis-Philippe Véronneau Closes: 980676 Changes: puppetlabs-ring-middleware-clojure (1.3.0-2) unstable; urgency=medium . * Team upload. * d/patches: fix snakeyaml error in 0001. (Closes: #980676) * d/tests: fix failure in build and run proper tests for unittests. Checksums-Sha1: 64cd797ce2c876edc79839e8a72f9a4c56293763 2790 puppetlabs-ring-middleware-clojure_1.3.0-2.dsc 3c19fa0741439dee3920244064661f36fa923381 4108 puppetlabs-ring-middleware-clojure_1.3.0-2.debian.tar.xz 06d8ca4497c3543fa9c6cab8a1400483f89c1043 13903 puppetlabs-ring-middleware-clojure_1.3.0-2_amd64.buildinfo Checksums-Sha256: d9ab1c89ebac12166ef1d8b36a967c2bfbf6a95982be9b712c822edbfcc3233d 2790 puppetlabs-ring-middleware-clojure_1.3.0-2.dsc cbb8acd9a339b34cdf3a9ba8cb3ade4e25ae0bb262ef52cab42ff9801ff62fe5 4108 puppetlabs-ring-middleware-clojure_1.3.0-2.debian.tar.xz a54478f843eee237884627000df589ab6d0c6d08e1953e7de22a8100481a03d1 13903 puppetlabs-ring-middleware-clojure_1.3.0-2_amd64.buildinfo Files: a4e44238cd221cc008cf078
Bug#980708: marked as pending in trapperkeeper-scheduler-clojure
Control: tag -1 pending Hello, Bug #980708 in trapperkeeper-scheduler-clojure reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/trapperkeeper-scheduler-clojure/-/commit/6c6e7dcc0437229204af72bc9f318c2771afb5fa Use lein i18n, as gettext has been fixed. (Closes: #980708 ) (this message was generated automatically) -- Greetings https://bugs.debian.org/980708
Processed: Bug#980708 marked as pending in trapperkeeper-scheduler-clojure
Processing control commands: > tag -1 pending Bug #980708 [src:trapperkeeper-scheduler-clojure] trapperkeeper-scheduler-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not been downloaded from it before. Added tag(s) pending. -- 980708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 980928 in 7.4.0+ds-1
Processing commands for cont...@bugs.debian.org: > notfound 980928 7.4.0+ds-1 Bug #980928 [npm] npm: Installing any package gives "npm ERR! current.merge is not a function" Ignoring request to alter found versions of bug #980928 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 980928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980660: marked as done (librole-tiny-perl: base class not required in create_class_with_roles)
Your message dated Sun, 24 Jan 2021 17:08:56 +
with message-id
and subject line Bug#980660: fixed in librole-tiny-perl 2.002004-1
has caused the Debian Bug report #980660,
regarding librole-tiny-perl: base class not required in create_class_with_roles
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.)
--
980660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmoox-traits-perl
Version: 0.005-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness"
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib',
> 'blib/arch')" t/*.t t/from-moosex-traits/*.t
> t/01basic.t ...
> ok 1 - use MooX::Traits;
> 1..1
> ok
> t/02packagevariant.t ..
> 1..11
> ok 1 - making class is OK
> ok 2 - making class with no traits is OK
> ok 3 - prole is applied OK
> ok 4 - An object of class 'Class__WITH__PRole::_Variant_A001' isa 'Class'
> ok 5 - OHHAI accessor works
> ok 6 - prole is applied OK along with a normal role
> ok 7 - Class__WITH__PRole::_Variant_A002__AND__Role->can(...)
> ok 8 - prole is applied OK along with a normal role (2)
> ok 9 - Class__WITH__Role__AND__PRole::_Variant_A003->can(...)
> ok 10 - regular roles with args can be applied, but args are ignored
> ok 11 - Class__WITH__Role->can('gorge')
> ok
> t/03roletiny.t
> ok 1 - An object of class 'Class__WITH__Trait' isa 'Class'
> ok 2 - Class__WITH__Trait->can('foo')
> ok 3
> ok 4 - An object of class 'Class__WITH__Trait' isa 'Class'
> ok 5 - Class__WITH__Trait->can('foo')
> ok 6
> ok 7 - An object of class 'Class' isa 'Class'
> ok 8 - this one cannot foo
> ok 9 - An object of class 'Class' isa 'Class'
> ok 10 - this one cannot foo either
> ok 11 - An object of class 'Another::Class__WITH__Another::Trait' isa
> 'Another::Class'
> ok 12 - Another::Class__WITH__Another::Trait->can('bar')
> ok 13
> ok 14 - An object of class 'Another::Class__WITH__Another::Trait' isa
> 'Another::Class'
> ok 15 - Another::Class__WITH__Another::Trait->can('bar')
> ok 16
> ok 17 - An object of class 'Another::Class__WITH__Another::Trait__AND__Trait'
> isa 'Another::Class'
> ok 18 - Another::Class__WITH__Another::Trait__AND__Trait->can('foo')
> ok 19 - Another::Class__WITH__Another::Trait__AND__Trait->can('bar')
> ok 20
> ok 21
> 1..21
> ok
> t/04onebyone.t
> ok 1 - Cannot compose Foo because missing Bar
> ok 2 - Cannot compose Bar because missing Foo
> ok 3 - Can compose Foo and Bar simultaneously
> ok 4 - MyClass__WITH__Foo__AND__Bar->can(...)
> 1..4
> ok
> t/from-moosex-traits/basic.t ..
> ok 1 - An object of class 'Class__WITH__Trait' isa 'Class'
> ok 2 - Class__WITH__Trait->can('foo')
> ok 3
> ok 4 - An object of class 'Class__WITH__Trait' isa 'Class'
> ok 5 - Class__WITH__Trait->can('foo')
> ok 6
> ok 7 - foo is required
> ok 8 - An object of class 'Class' isa 'Class'
> ok 9 - this one cannot foo
> ok 10 - An object of class 'Class' isa 'Class'
> ok 11 - this one cannot foo either
> ok 12 - An object of class 'Another::Class__WITH__Another::Trait' isa
> 'Another::Class'
> ok 13 - Another::Class__WITH__Another::Trait->can('bar')
> ok 14
> ok 15 - An object of class 'Another::Class__WITH__Another::Trait' isa
> 'Another::Class'
> ok 16 - Another::Class__WITH__Another::Trait->can('bar')
> ok 17
> ok 18 - An object of class 'Another::Class__WITH__Another::Trait__AND__Trait'
> isa 'Another::Class'
> ok 19 - Another::Class__WITH__Another::Trait__AND__Trait->can('foo')
> ok 20 - Another::Class__WITH__Another::Trait__AND__Trait->can('bar')
> ok 21
> ok 22
> 1..22
> ok
> While trying to resolve method call OH NOES__WITH__Trait->can() can not
> locate package "OH NOES" yet it is mentioned in @OH NOES__WITH__Trait::ISA
> (perhaps you forgot to load "OH NOES"?) at /usr/share/perl5/Role/Tiny.pm line
> 473.
> While trying to resolve method call OH NOES__WITH__Trait->does() can not
> locate package "OH NOES" yet it is mentioned in @OH NOES__WITH__Trait::ISA
> (perhaps you forgot to load "OH NOES"?) at /usr/share/perl5/Role/Tiny.pm line
> 473.
> While trying to resolve method call OH NOES__WITH__Trait->DOES() can not
> locate package "OH NOES" yet it is mentioned in @OH NOES__WITH__Trait::ISA
> (perhaps
Processed: reassign 980660 to librole-tiny-perl, affects 980660 ..., tagging 980660
Processing commands for cont...@bugs.debian.org: > reassign 980660 librole-tiny-perl 2.002003-1 Bug #980660 [src:libmoox-traits-perl] libmoox-traits-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Bug reassigned from package 'src:libmoox-traits-perl' to 'librole-tiny-perl'. No longer marked as found in versions libmoox-traits-perl/0.005-1.1. Ignoring request to alter fixed versions of bug #980660 to the same values previously set Bug #980660 [librole-tiny-perl] libmoox-traits-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Marked as found in versions librole-tiny-perl/2.002003-1. > affects 980660 + src:libmoox-traits-perl Bug #980660 [librole-tiny-perl] libmoox-traits-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added indication that 980660 affects src:libmoox-traits-perl > retitle 980660 librole-tiny-perl: base class not required in > create_class_with_roles Bug #980660 [librole-tiny-perl] libmoox-traits-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Changed Bug title to 'librole-tiny-perl: base class not required in create_class_with_roles' from 'libmoox-traits-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2'. > tags 980660 - ftbfs Bug #980660 [librole-tiny-perl] librole-tiny-perl: base class not required in create_class_with_roles Removed tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 980660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980422: marked as done (kitchensink-clojure: autopkgtest failure on i386)
Your message dated Sun, 24 Jan 2021 16:04:09 + with message-id and subject line Bug#980422: fixed in kitchensink-clojure 3.1.1-3 has caused the Debian Bug report #980422, regarding kitchensink-clojure: autopkgtest failure on i386 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.) -- 980422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kitchensink-clojure Version: 3.1.1-2 Severity: serious Control: block 975207 by -1 https://ci.debian.net/data/autopkgtest/testing/i386/k/kitchensink-clojure/9803014/log.gz ... autopkgtest [17:24:31]: test unittests: [--- WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: puppetlabs.kitchensink.core-test, being replaced by: #'puppetlabs.kitchensink.core/boolean? WARNING: uuid? already refers to: #'clojure.core/uuid? in namespace: puppetlabs.kitchensink.core-test, being replaced by: #'puppetlabs.kitchensink.core/uuid? Syntax error (FileNotFoundException) compiling at (./test/puppetlabs/kitchensink/core_test.clj:1:1). Could not locate puppetlabs/kitchensink/testutils__init.class, puppetlabs/kitchensink/testutils.clj or puppetlabs/kitchensink/testutils.cljc on classpath. Full report at: /tmp/clojure-12994910647831856891.edn autopkgtest [17:24:39]: test unittests: ---] autopkgtest [17:24:39]: test unittests: - - - - - - - - - - results - - - - - - - - - - unittestsFAIL non-zero exit status 123 autopkgtest [17:24:39]: test unittests: - - - - - - - - - - stderr - - - - - - - - - - WARNING: boolean? already refers to: #'clojure.core/boolean? in namespace: puppetlabs.kitchensink.core-test, being replaced by: #'puppetlabs.kitchensink.core/boolean? WARNING: uuid? already refers to: #'clojure.core/uuid? in namespace: puppetlabs.kitchensink.core-test, being replaced by: #'puppetlabs.kitchensink.core/uuid? Syntax error (FileNotFoundException) compiling at (./test/puppetlabs/kitchensink/core_test.clj:1:1). Could not locate puppetlabs/kitchensink/testutils__init.class, puppetlabs/kitchensink/testutils.clj or puppetlabs/kitchensink/testutils.cljc on classpath. Full report at: /tmp/clojure-12994910647831856891.edn autopkgtest [17:24:39]: summary buildPASS (superficial) unittestsFAIL non-zero exit status 123 --- End Message --- --- Begin Message --- Source: kitchensink-clojure Source-Version: 3.1.1-3 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of kitchensink-clojure, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated kitchensink-clojure 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, 24 Jan 2021 10:11:32 -0500 Source: kitchensink-clojure Architecture: source Version: 3.1.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Louis-Philippe Véronneau Closes: 980422 Changes: kitchensink-clojure (3.1.1-3) unstable; urgency=medium . * Team upload. * d/tests: fix broken autopkgtest. (Closes: #980422) Checksums-Sha1: 1fb2d113b6b9c9bc6c3b53eb34229a9bf36b04d9 2493 kitchensink-clojure_3.1.1-3.dsc 1c9f96e5f6d437e7c6d74146020cffd35a49a06b 4052 kitchensink-clojure_3.1.1-3.debian.tar.xz 9d8485f33276d255f35e92a7555781a749fe9e6b 10837 kitchensink-clojure_3.1.1-3_amd64.buildinfo Checksums-Sha256: 8f998468d097b88209da0fc8dc13dfb26a4ac010affe4e6664d9bd51c544037d 2493 kitchensink-clojure_3.1.1-3.dsc b01de006991bcf5e6a64e2043b1786f2394250876e12148967475812cd1c8f44 4052 kitchensink-clojure_3.1.1-3.debian.tar.xz e1c7a0264606b3bc0c0d155164fded049d5dce3b3b1c6ecb8cb9d7f306f5358c 10837 kitchensink-clojure_3.1.1-3_amd64.buildinfo Files: 5c3b11f279aa526f91a3b72b0214553c 2493 java optional kitchensink-clojure_3.1.1-3.dsc 56e4bdbf069c579415a46d45af48691e 4052 java optional kitchensink-clojure_3.1.1-3.debian.tar.xz a979015e684f4f38cc8898ad450ba75e 10837 java optional kitchensi
Bug#980935: pyzo: Crash at startup with python3.9
Package: pyzo
Version: 4.4.3-1.2
Severity: grave
Tags: patch upstream
Justification: renders package unusable
Dear Maintainer,
When trying to launch pyzo in a standard debian environment with python3.9, I
face the following error:
Traceback (most recent call last):
File "/usr/bin/pyzo", line 11, in
load_entry_point('pyzo==4.4.3', 'console_scripts', 'pyzo')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/share/pyzo/pyzo/__init__.py", line 73, in
if commandline.is_our_server_running():
File "/usr/share/pyzo/pyzo/core/commandline.py", line 150, in
is_our_server_running
return server and server.isAlive()
AttributeError: 'Server' object has no attribute 'isAlive'
This error seems to be related to
https://github.com/pyzo/pyzo/issues/713
Applying the upstream patch fixes the problem - see attached. Upgrading pyzo to
a newer version should also be OK.
Regards,
Alexis Bienvenüe.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pyzo depends on:
ii famfamfam-silk 1.3-1.1
ii fonts-dejavu-core 2.37-2
ii fonts-dejavu-extra 2.37-2
ii python3 3.9.1-1
ii python3-pkg-resources 51.3.3-1
ii python3-qtpy 1.9.0-3
pyzo recommends no packages.
Versions of packages pyzo suggests:
pn pyzo-doc
-- no debconf information
diff -Nru pyzo-4.4.3/debian/changelog pyzo-4.4.3/debian/changelog
--- pyzo-4.4.3/debian/changelog 2019-01-11 19:09:52.0 +0100
+++ pyzo-4.4.3/debian/changelog 2021-01-24 15:52:14.0 +0100
@@ -1,3 +1,9 @@
+pyzo (4.4.3-1.3) UNRELEASED; urgency=medium
+
+ * Fix crash with python3.9
+
+ -- Alexis Bienvenüe Sun, 24 Jan 2021 15:52:14 +0100
+
pyzo (4.4.3-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru pyzo-4.4.3/debian/patches/0002-replace-isAlive-per-is_alive-to-become-Python-3.9-compat.patch pyzo-4.4.3/debian/patches/0002-replace-isAlive-per-is_alive-to-become-Python-3.9-compat.patch
--- pyzo-4.4.3/debian/patches/0002-replace-isAlive-per-is_alive-to-become-Python-3.9-compat.patch 1970-01-01 01:00:00.0 +0100
+++ pyzo-4.4.3/debian/patches/0002-replace-isAlive-per-is_alive-to-become-Python-3.9-compat.patch 2021-01-24 15:50:46.0 +0100
@@ -0,0 +1,31 @@
+Description: Replace isAlive per is_alive to become Python 3.9 compatible
+ With python3.9, pyzo 4.4.3 crashes at startup with
+ AttributeError: 'Server' object has no attribute 'isAlive'
+Author: Alexis Bienvenüe
+Origin: upstream
+Bug: https://github.com/pyzo/pyzo/issues/713
+Applied-Upstream: https://github.com/pyzo/pyzo/pull/714/commits/9d9b2fe126f70f70ff8b0fa9dd5ba047f595b75a
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/pyzo/core/commandline.py
b/pyzo/core/commandline.py
+@@ -147,7 +147,7 @@ def is_our_server_running():
+ not running, this is probably not the first Pyzo, but there might
+ also be problem with starting the server.
+ """
+-return server and server.isAlive()
++return server and server.is_alive()
+
+
+ def is_pyzo_server_running():
+--- a/pyzo/yoton/channels/channels_reqrep.py
b/pyzo/yoton/channels/channels_reqrep.py
+@@ -714,7 +714,7 @@ class RepChannel(BaseChannel):
+ self._timer.start()
+ elif mode in [2, 'thread', 'thread-driven']:
+ self._run_mode = 2
+-if not self._thread.isAlive():
++if not self._thread.is_alive():
+ self._thread.start()
+ else:
+ raise ValueError('Invalid mode for ReqChannel instance.')
diff -Nru pyzo-4.4.3/debian/patches/series pyzo-4.4.3/debian/patches/series
--- pyzo-4.4.3/debian/patches/series 2018-11-30 16:17:17.0 +0100
+++ pyzo-4.4.3/debian/patches/series 2021-01-24 15:43:45.0 +0100
@@ -1,2 +1,3 @@
Disable-install-of-appdata.patch
0001-replace-async-per-basync-to-become-Python-3.7-compat.patch
+0002-replace-isAlive-per-is_alive-to-become-Python-3.9-compat.patch
Processed: closing 885273, closing 942971
Processing commands for cont...@bugs.debian.org: > close 885273 0.6.0-1 Bug #885273 [src:diffuse] diffuse: Depends on unmaintained pygtk Marked as fixed in versions diffuse/0.6.0-1. Bug #885273 [src:diffuse] diffuse: Depends on unmaintained pygtk Marked Bug as done > close 942971 0.6.0-1 Bug #942971 [src:diffuse] diffuse: Python2 removal in sid/bullseye Marked as fixed in versions diffuse/0.6.0-1. Bug #942971 [src:diffuse] diffuse: Python2 removal in sid/bullseye Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 885273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885273 942971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 885273, reopening 885273, unarchiving 942971, reopening 942971, unarchiving 793352 ...
Processing commands for cont...@bugs.debian.org:
> # src:diffuse was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 885273
Bug #885273 {Done: Debian FTP Masters }
[src:diffuse] diffuse: Depends on unmaintained pygtk
Unarchived Bug 885273
> reopen 885273
Bug #885273 {Done: Debian FTP Masters }
[src:diffuse] diffuse: Depends on unmaintained pygtk
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.4.8-4+rm.
> unarchive 942971
Bug #942971 {Done: Debian FTP Masters }
[src:diffuse] diffuse: Python2 removal in sid/bullseye
Unarchived Bug 942971
> reopen 942971
Bug #942971 {Done: Debian FTP Masters }
[src:diffuse] diffuse: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.4.8-4+rm.
> unarchive 793352
Bug #793352 {Done: Debian FTP Masters }
[diffuse] diffuse: [INTL:th] Please add Thai program translation.
Unarchived Bug 793352
> reopen 793352
Bug #793352 {Done: Debian FTP Masters }
[diffuse] diffuse: [INTL:th] Please add Thai program translation.
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.4.8-4+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
793352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793352
885273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885273
942971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#980928: npm: Installing any package gives "npm ERR! current.merge is not a function"
Package: npm Version: 7.4.0+ds-1~bpo10+2 Severity: grave Justification: renders package unusable Tried out via, e.g., "npm install serialport" inside a debian:buster-slim container. Happens with both "npm node-*" as well only the required node-packages takes from backports. -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.3.18-lp152.60-default (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages npm depends on: ii ca-certificates 20200601~deb10u1 ii node-abbrev 1.1.1-1 ii node-agent-base 6.0.2-1~bpo10+1 ii node-ajv5.0.0-1 ii node-ansi 0.3.0-3 ii node-ansi-regex 3.0.0-1 ii node-ansi-styles3.2.1-1 ii node-ansistyles 0.1.3-1 ii node-aproba 1.2.0-1 ii node-archy 1.0.0-2 ii node-are-we-there-yet 1.1.4-1 ii node-asap 2.0.6-1 ii node-asn1 0.2.3-1 ii node-assert-plus1.0.0-1 ii node-asynckit 0.4.0-2 ii node-aws-sign2 0.7.1-1 ii node-aws4 1.8.0-1 ii node-balanced-match 0.4.2-1 ii node-bcrypt-pbkdf 1.0.1-1 ii node-brace-expansion1.1.8-1 ii node-builtins 1.0.3-1 ii node-cacache15.0.5+~cs13.9.21-1~bpo10+1 ii node-caseless 0.12.0-1 ii node-chalk 2.3.0-2 ii node-chownr 1.1.3-5~bpo10+1 ii node-clone 2.1.2-1 ii node-color-convert 1.9.0-3 ii node-color-name 1.1.3-1 ii node-colors 1.1.2-1 ii node-columnify 1.5.4-1 ii node-combined-stream1.0.7-1 ii node-concat-map 0.0.1-1 ii node-console-control-strings1.1.0-1 ii node-core-util-is 1.0.2-1 ii node-dashdash 1.14.1-2 ii node-debug 4.3.1+~cs4.1.5-1~bpo10+1 ii node-defaults 1.0.3-1 ii node-delayed-stream 0.0.5-1 ii node-delegates 1.0.0-1 ii node-depd 1.1.2-1 ii node-ecc-jsbn 0.1.1-1 ii node-encoding 0.1.12-2 ii node-err-code 1.1.2+dfsg-1 ii node-extend 3.0.2-1 ii node-extsprintf 1.3.0-1 ii node-fast-deep-equal1.0.0-1 ii node-forever-agent 0.6.1-1 ii node-form-data 2.3.2-2 ii node-fs.realpath1.0.0-1 ii node-function-bind 1.1.1+ds-2 ii node-gauge 2.7.4-1 ii node-getpass0.1.7-1 ii node-glob 7.1.3-2 ii node-graceful-fs4.1.11-1 ii node-gyp6.1.0-3~bpo10+1 ii node-har-schema 2.0.0-1 ii node-har-validator 5.1.0-1 ii node-has-flag 2.0.0-1 ii node-http-signature 1.2.0-1 ii node-https-proxy-agent 5.0.0-2~bpo10+1 ii node-iconv-lite 0.4.13-2 ii node-imurmurhash0.1.4-1 ii node-indent-string 3.2.0-1 ii node-inflight 1.0.6-1 ii node-inherits 2.0.3-1 ii node-ini1.3.5-1 ii node-ip 1.1.5-3 ii node-ip-regex 3.0.0-1 ii node-is-typedarray 1.0.0-2 ii node-isarray2.0.4-1 ii node-isexe 2.0.0-4 ii node-isstream 0.1.2+dfsg-1 ii node-jsbn 1.1.0-1 ii node-json-parse-better-errors 1.0.2+~2.3.1-1~bpo10+1 ii node-json-schema0.2.3-1 ii node-json-schema-traverse 0.3.1-1 ii node-json-stable-stringify 1.0.1-1 ii node-json-stringify-safe5.0.1-1 ii node-jsonparse 1.3.1-6 ii node-jsonstream 1.3.2-1 ii node-jsprim 1.4.0-1 ii node-leven 2.1.0-2 ii node-lockfile 1.0.4-1 ii node-mime 2.4.0-1 ii node-mime-types 2.1.21-1 ii node-minimatch 3.0.4-3 ii node-mkdirp 1.0.4-3~bpo10+2 ii node-ms 2.1.1-1 ii node-mute-stream0.0.8-1 ii node-nopt 3.0.6-3 ii node-normalize-package-data 2.4.0-1 ii node-npm-bundled1.0.3-1 ii node-npm-package-arg6.1.1-1~bpo10+1 ii node-npml
Bug#957317: closing 957317
close 957317 0.11pre0+cvs.2003.11.02-11 thanks Patch from Alexey Sokolov fixed GCC-10 bug. Much appreciated!
Processed: closing 957317
Processing commands for cont...@bugs.debian.org: > close 957317 0.11pre0+cvs.2003.11.02-11 Bug #957317 [src:gtkboard] gtkboard: ftbfs with GCC-10 Marked as fixed in versions gtkboard/0.11pre0+cvs.2003.11.02-11. Bug #957317 [src:gtkboard] gtkboard: ftbfs with GCC-10 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 957317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972747: Where is /usr/share/sbuild/create-chroot actually used?
Am Sonntag, dem 24.01.2021 um 11:48 +0100 schrieb Johannes Schauer Marin Rodrigues: > Hi Bruno, > > Quoting Bruno Kleinert (2021-01-24 06:46:39) > > I looked into /usr/share/sbuild/create-chroot to create a patch, but began > > to > > wonder where and if that script is actually used. I use sbuild to locally > > build packages on my desktop computer, so it's installed, and > > > > grep -r create-chroot /usr/sbin/sbuild* /usr/bin/sbuild* > > > > does not show any matches. > > > > Reverse dependencies and reverse recommends of sbuild are: > >1. mini-buildd > >2. arriero > >3. xbuilder > >4. ubuntu-dev-tools > >5. schroot > >6. sbuild-debian-developer-setup > >7. ratt > >8. qemu-sbuild-utils > >9. pk4 > > 10. packaging-dev > > 11. debomatic > > 12. lava-dev > > 13. git-buildpackage > > > > I downloaded and extracted them and grepped for 'create-chroot' in > > their contents: No matches. > > > > Looking into create-chroot revealed: > > > > […] > > OLDSTABLE="squeeze" > > STABLE="wheezy" > > TESTING="jessie" > > […] > > > > That leaves the impression the script was last used a couple of releases ago > > and could simply be removed to close this bug. > > I have no objections. Aurelien Jarno also confirmed in IRC that it is not used > in buildd purposes. > > Feel free to create a MR against the sbuild packaging repository. > > Thanks! > > cheers, josch Hi josch, alright, I submitted a merge requests here https://salsa.debian.org/debian/sbuild/-/merge_requests/12 Cheers, Bruno signature.asc Description: This is a digitally signed message part
Bug#974666: marked as done (gnome-sound-recorder: The export file dialog disappears suddendly after a few seconds.)
Your message dated Sun, 24 Jan 2021 13:03:25 +
with message-id
and subject line Bug#974666: fixed in gnome-sound-recorder 3.38.0-3
has caused the Debian Bug report #974666,
regarding gnome-sound-recorder: The export file dialog disappears suddendly
after a few seconds.
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.)
--
974666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-sound-recorder
Version: 3.38.0-1
Severity: grave
Tags: patch
Justification: causes non-serious data loss
X-Debbugs-Cc: rasters...@gmail.com
Dear Maintainer,
After doing a recording, pressing the "export" button shows, as expected, a
file dialog to choose where to export the file. The problem is that the
dialog disappears sudendly after some seconds (a variable number: sometimes
as soon as three-four seconds, others between ten and twelve seconds). To
trigger this bug, just press the "export" button and wait.
This is critical because if the user want to navigate to a folder and uses too
much time, the dialog closes before being able to do the operation.
This seems a problem with the garbage collector. I attach a patch that fixes
it.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-sound-recorder depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.38.0-1
ii gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-5
ii gir1.2-glib-2.0 1.66.1-1
ii gir1.2-gst-plugins-bad-1.0 1.18.1-1
ii gir1.2-gst-plugins-base-1.0 1.18.1-1
ii gir1.2-gstreamer-1.0 1.18.1-1
ii gir1.2-gtk-3.0 3.24.23-2
ii gir1.2-handy-1 1.0.1-1
ii gir1.2-pango-1.0 1.46.2-3
ii gjs 1.66.1-1
ii gstreamer1.0-plugins-base1.18.1-1
ii gstreamer1.0-plugins-good1.18.1-1
ii gstreamer1.0-pulseaudio 1.18.1-1
gnome-sound-recorder recommends no packages.
gnome-sound-recorder suggests no packages.
-- no debconf information
diff --git a/src/row.js b/src/row.js
index 154c0ef..743de63 100644
--- a/src/row.js
+++ b/src/row.js
@@ -68,16 +68,17 @@ var Row = GObject.registerClass({
let exportAction = new Gio.SimpleAction({ name: 'export' });
exportAction.connect('activate', () => {
const window = Gio.Application.get_default().get_active_window();
-const dialog = Gtk.FileChooserNative.new(_('Export Recording'),
window, Gtk.FileChooserAction.SAVE, _('_Export'), _('_Cancel'));
-
dialog.set_current_name(`${this._recording.name}.${this._recording.extension}`);
-dialog.connect('response', (_dialog, response) => {
+this.exportDialog = Gtk.FileChooserNative.new(_('Export
Recording'), window, Gtk.FileChooserAction.SAVE, _('_Export'), _('_Cancel'));
+
this.exportDialog.set_current_name(`${this._recording.name}.${this._recording.extension}`);
+this.exportDialog.connect('response', (_dialog, response) => {
if (response === Gtk.ResponseType.ACCEPT) {
-const dest = dialog.get_file();
+const dest = this.exportDialog.get_file();
this._recording.save(dest);
}
-dialog.destroy();
+this.exportDialog.destroy();
+this.exportDialog = null;
});
-dialog.show();
+this.exportDialog.show();
});
this.actionGroup.add_action(exportAction);
--- End Message ---
--- Begin Message ---
Source: gnome-sound-recorder
Source-Version: 3.38.0-3
Done: Simon McVittie
We believe that the bug you reported is fixed in the latest version of
gnome-sound-recorder, 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 974...
Processed: Re: Bug#980922: debian-games: please move to the new name udd-mirror.debian.net
Processing control commands: > severity -1 normal Bug #980922 [debian-games] debian-games: please move to the new name udd-mirror.debian.net Severity set to 'normal' from 'serious' -- 980922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980922: debian-games: please move to the new name udd-mirror.debian.net
Control: severity -1 normal Hello, Am Sonntag, den 24.01.2021, 13:22 +0100 schrieb Mattia Rizzolo: [...] > As announced in https://lists.debian.org/debian-qa/2020/11/msg00011.html > we don't plan to remove public-udd-mirror.xvm.mit within less than a > year. > > I'm filing this bug as RC, as I wouldn't want this package to break > during the course of bullseye if it's released as it is and then the old > hostname gets retired. If you consider that script unimportant then > feel free to downgrate the severity. The script is only used manually when I update the package. Nothing will break if the old mirror goes offline. I intend to fix this with the next update of debian-games. Regards, Markus signature.asc Description: This is a digitally signed message part
Bug#980922: debian-games: please move to the new name udd-mirror.debian.net
Package: debian-games Version: 3.2 Severity: serious Hi! Looking at codesearch.debian.net, it looks like debian-games is the only package using the name public-udd-mirror.xvm.net in its src/debian_games_updater.py. Please change: conn = connect( database='udd', port=5432, host='public-udd-mirror.xvm.mit.edu', user='public-udd-mirror', password='public-udd-mirror') to: conn = connect( database='udd', port=5432, host='udd-mirror.debian.net', user='udd-mirror', password='udd-mirror') to help us deprecate the former name. As announced in https://lists.debian.org/debian-qa/2020/11/msg00011.html we don't plan to remove public-udd-mirror.xvm.mit within less than a year. I'm filing this bug as RC, as I wouldn't want this package to break during the course of bullseye if it's released as it is and then the old hostname gets retired. If you consider that script unimportant then feel free to downgrate the severity. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#980917: libpmix-dev fails to upgrade from 3.2.2~rc1-1 to 4.0.0-4
Package: libpmix-dev X-Debbugs-Cc: g...@nonempty.org Version: 4.0.0-4 Severity: serious Justification: Policy 7.6 Dear Maintainer, Upgrading libpmix-dev from 3.2.2~rc1-1 to 4.0.0-4 fails with dpkg: error processing archive /tmp/apt-dpkg-install-xYYyH5/070-libpmix-dev_4.0.0-4_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/pmix2/lib/libmca_common_dstore.so', which is also in package libpmix2:amd64 3.2.2~rc1-1 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/6 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpmix-dev depends on: iu libpmix2 4.0.0-4 libpmix-dev recommends no packages. libpmix-dev suggests no packages. signature.asc Description: PGP signature
Bug#980872: marked as done (qbs FTBFS on mipsel/mips64el: FAIL! : TestBlackboxJobLimits::jobLimits(project:0/product:0/module:1/prefs:-1/cli:-1/project precedence) Received a fatal error.)
Your message dated Sun, 24 Jan 2021 11:34:21 +
with message-id
and subject line Bug#980872: fixed in qbs 1.18.0-4
has caused the Debian Bug report #980872,
regarding qbs FTBFS on mipsel/mips64el: FAIL! :
TestBlackboxJobLimits::jobLimits(project:0/product:0/module:1/prefs:-1/cli:-1/project
precedence) Received a fatal error.
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.)
--
980872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qbs
Version: 1.18.0-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=qbs&arch=mipsel
https://buildd.debian.org/status/logs.php?pkg=qbs&arch=mips64el
...
=== Received signal at function time: 300013ms, total time: 300390ms, dumping
stack ===
=== End of stack trace ===
QFATAL :
TestBlackboxJobLimits::jobLimits(project:0/product:0/module:1/prefs:-1/cli:-1/project
precedence) Test function timed out
FAIL! :
TestBlackboxJobLimits::jobLimits(project:0/product:0/module:1/prefs:-1/cli:-1/project
precedence) Received a fatal error.
Loc: [Unknown file(0)]
Totals: 253 passed, 1 failed, 0 skipped, 0 blacklisted, 300395ms
* Finished testing of TestBlackboxJobLimits *
Aborted
make[5]: *** [Makefile.blackbox-joblimits:409: check] Error 134
--- End Message ---
--- Begin Message ---
Source: qbs
Source-Version: 1.18.0-4
Done: Dmitry Shachnev
We believe that the bug you reported is fixed in the latest version of
qbs, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated qbs 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, 24 Jan 2021 14:18:12 +0300
Source: qbs
Architecture: source
Version: 1.18.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Closes: 980872
Changes:
qbs (1.18.0-4) unstable; urgency=medium
.
* Skip TestBlackboxJobLimits::jobLimits test that sometimes hangs on
mipsel/mips64el (closes: #980872).
* Run the remaining tests with QBS_AUTOTEST_ALWAYS_LOG_STD{OUT,ERR}=1.
Checksums-Sha1:
547a20da7f33b6a03a19117114450129cfe5954e 2475 qbs_1.18.0-4.dsc
c10689e1442d18aff6befa3397ba44de0b866e64 32072 qbs_1.18.0-4.debian.tar.xz
2635a12a810397b83853e663372c66ec5716a1b7 10165 qbs_1.18.0-4_source.buildinfo
Checksums-Sha256:
e3c335285ca0bce0e9aa5f8bbaa62efd1601a311e02ef6ddde7b6b71ef9547f2 2475
qbs_1.18.0-4.dsc
f4aae38b6f2622f9547f0ebdc45ae65dfc93155c95b4be5a2485de27b592b88c 32072
qbs_1.18.0-4.debian.tar.xz
ca8b62cc46b948a69bb1abafd44e29770c3f4fc8d46f290956aa15c4d578b869 10165
qbs_1.18.0-4_source.buildinfo
Files:
9bcce37379915ea29fd13d850f3e9f8b 2475 devel optional qbs_1.18.0-4.dsc
78344593cf4a00f11bdfc2e268ab3310 32072 devel optional
qbs_1.18.0-4.debian.tar.xz
b9839325a3db159cc06ac942097c1aa8 10165 devel optional
qbs_1.18.0-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmANWAETHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy4nxD/4hEMMjXxVysRqfVYaxFLAw70h9X4Dg
79Vz1Dtzay379R2IB41GOqnmG2Vbm1ZgerLlNux90XN4HmTz9uigA8qjDRs/l3SY
MZzJ9msKmSeu+Cu6LqN8p52taH/SXnc50ZZGLbalYjktmLBWl7zqr7kSRLetyXCy
yFkYEoPHg4Cr3qFrDcMBcDjoWKFvLCY1s96IOZGsPgD80jZM9u7oOsh5xbr+kAO+
qRKMsUoT6yv+AbIHtcjfYsKFkLNgRrxF+W40hO1cGn25oB7ayxf5QNNkcz3G9Zoi
3pK8/sxmtdJf4GF7rDOcYRbcQJiv+8+MpqWCx/E6ITyPoYzGKkh8Pyho/Rm46ILP
TKN1swiND/RKIkFeuCUujnQnQx3VoQ6d1T06p2aFBjSR3WVSDu5RiX4CvP/8HHK2
Z2g2Ua1c2zw37DmVHH7KkpySyRqDItYS/xbLD3s40Ing/NyKcDu7jMycA10rc0lT
W5WgQ52xeu939gTdHfv6HDhwJ+kyRceFKPaT4+NiUqXNFPRp4jdxGX/rc5HdjAyF
cMi5Lsy+gPerAUmGULLnnZOllynAxQeZfjSIqrApexJodERgktkobINEVrQgZfDH
7MBHG6QJ+xk9Me/a9dOhmVtHN4NDxp4LUvguhUdrAIEJ/v/45XM+hyCY2+Tz7xfG
YsmOzI49qh3h6w==
=BR4u
-END PGP SIGNATURE End Message ---
Bug#980906: libpython3.9: _collections_abc.py :type 'types.GenericAlias' is not an acceptable base type
Package: libpython3.9 Version: 3.9.1-3 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: lenni_...@yahoo.de Dear Maintainer, after running a normal apt update and apt upgrade I started getting errors from python3 packages that should also be upgraded: Fatal Python error: init_import_site: Failed to import the site module Python runtime state: initialized Traceback (most recent call last): File "/usr/lib/python3.9/site.py", line 79, in import os File "/usr/lib/python3.9/os.py", line 29, in from _collections_abc import _check_methods File "/usr/lib/python3.9/_collections_abc.py", line 416, in class _CallableGenericAlias(GenericAlias): TypeError: type 'types.GenericAlias' is not an acceptable base type >From the update log it is visible that first the python3.9 packages were updates which leds to this error. If you change the line 416 of the /usr/lib/python3.9/_collections_abc.py file from: class _CallableGenericAlias(GenericAlias): to the type the GenerticAlias represents (Defined at the beginning of the file as: GenericAlias = type(list[int]): class _CallableGenericAlias(list[int]): everything works fine again. I only have python3.9 and python2.7 installed on my system. Greetings -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 libpython3.9 depends on: ii libc62.31-9 ii libexpat12.2.10-1 ii libpython3.9-stdlib 3.9.1-3 ii zlib1g 1:1.2.11.dfsg-2 libpython3.9 recommends no packages. libpython3.9 suggests no packages. -- no debconf information
Processed: Re: #980085 upstream progress
Processing control commands: > severity -1 grave Bug #980085 [open-iscsi] open-iscsi: initiator does not connect Severity set to 'grave' from 'important' > tags -1 + upstream Bug #980085 [open-iscsi] open-iscsi: initiator does not connect Added tag(s) upstream. -- 980085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980625: marked as done (olm: FTBFS: IndexError: pop from empty list)
Your message dated Sun, 24 Jan 2021 12:17:09 +0100 with message-id <161148702989.2797347.6641569934638695...@auryn.jones.dk> and subject line Re: [Pkg-matrix-maintainers] Bug#980625: olm: FTBFS: IndexError: pop from empty list has caused the Debian Bug report #980625, regarding olm: FTBFS: IndexError: pop from empty list 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.) -- 980625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: olm Version: 3.2.1~dfsg-6 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > mkdir -p build/javascript/src/ > mkdir -p build/javascript/src/ > mkdir -p build/javascript/src/ > mkdir -p build/javascript/src/ > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/account.o src/account.cpp > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/base64.o src/base64.cpp > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/cipher.o src/cipher.cpp > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/crypto.o src/crypto.cpp > shared:INFO: (Emscripten: Running sanity checks) > shared:INFO: (Emscripten: Running sanity checks) > shared:INFO: (Emscripten: Running sanity checks) > shared:INFO: (Emscripten: Running sanity checks) > mkdir -p build/javascript/src/ > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/memory.o src/memory.cpp > mkdir -p build/javascript/src/ > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/message.o src/message.cpp > mkdir -p build/javascript/src/ > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/olm.o src/olm.cpp > mkdir -p build/javascript/src/ > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/pickle.o src/pickle.cpp > mkdir -p build/javascript/src/ > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/pk.o src/pk.cpp > mkdir -p build/javascript/src/ > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 > -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=1 -MMD -c -o > build/javascript/src/ratchet.o src/ratchet.cpp > mkdir -p build/javascript/src/ > emcc -s ASSERTIONS=1 -O2 -ffile-prefix-map=/<>=. -Wformat > -Werror=format-security -Wall -Werror -std=c++11 -O3 -Wdate-time > -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR
Bug#972262: marked as done (FTBFS with OCaml 4.11.1 (-unsafe-string is not available))
Your message dated Sun, 24 Jan 2021 10:48:32 + with message-id and subject line Bug#972262: fixed in ocamlviz 1.01-5 has caused the Debian Bug report #972262, regarding FTBFS with OCaml 4.11.1 (-unsafe-string is not available) 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.) -- 972262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ocamlviz Version: 1.01-4 Severity: serious Tags: ftbfs Dear Maintainer, Your package ocamlviz FTBFS with OCaml 4.11.1 because -unsafe-string is no longer available. Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: ocamlviz Source-Version: 1.01-5 Done: Mehdi Dogguy We believe that the bug you reported is fixed in the latest version of ocamlviz, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mehdi Dogguy (supplier of updated ocamlviz 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, 24 Jan 2021 11:22:04 +0100 Source: ocamlviz Architecture: source Version: 1.01-5 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Mehdi Dogguy Closes: 972262 Changes: ocamlviz (1.01-5) unstable; urgency=medium . * Fix FTBFS by using Bytes where necessary (Closes: #972262) - Remove 0003-Compile-with-unsafe-string-for-now.patch, which is not needed anymore - Add 0003-Use-Bytes-only-where-necessary.patch Checksums-Sha1: c565f2281242d34fa5a969499e5f6e2d2a3ec26e 2251 ocamlviz_1.01-5.dsc aef6ebba6e1371fd4048dbb9050ac3e090d5d819 5192 ocamlviz_1.01-5.debian.tar.xz 5b092ff1e3d97632dd9b6ad1c03d318142d21d7b 12011 ocamlviz_1.01-5_source.buildinfo Checksums-Sha256: a77ed363656139ccb4b508102dc49b5cd60872a57b6e44b17e6949b34c0c66bf 2251 ocamlviz_1.01-5.dsc 09f3d207f2bedfc28faa776b236f9b76b206e18525533dd9ff4bb1bbd8094fc5 5192 ocamlviz_1.01-5.debian.tar.xz d0bcbf75abc554d0ffd796cee40be748153ad82333a1ac6ec2a57c104cbb9d05 12011 ocamlviz_1.01-5_source.buildinfo Files: 34adbe7bebbfeda0db002085da0fb7ee 2251 ocaml optional ocamlviz_1.01-5.dsc a97030efd9ca41bedd5955b8c835d7fb 5192 ocaml optional ocamlviz_1.01-5.debian.tar.xz 881c1317e6d1202bdb7251cc53feb6fb 12011 ocaml optional ocamlviz_1.01-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE/IeFmw45V03XKU7GPfRgADmhQMQFAmANStwRHG1laGRpQGRl Ymlhbi5vcmcACgkQPfRgADmhQMSTsw//YDmyXGo1GMfks/uKh8EyyZipQlomiAWH atuMg3HXYTLey+WQo3F9L/ZBEWkva/VivLxgzpXv+Nkmnym2yOmEvJkMcybIlAu8 mZa6e9uH3RdZdJldj1MaY/CgerVxrinXoCMpqIbGuL4/gf+h+R22FYWiH5GPApo3 8atdPDlT7qvTpGDDaSfliwIh+xVnp7Y22meLQWzRP/WA78zmxrMR2GqxyakUyWWB pFQxKl4rkxPPlyiVI1hriawNc20YwosX9FHvFvS5pf/BJ9/Hxqf/U4tgvbbEfu2k wbf2/C+421OzEBp0ABmcLfhtq3xxJGwuFTT0m85Z8LnL6aSGRbFSgAExenN6h/s3 EXjdeKTzkH4ieBKokrzBqYEWpt773sC6yBjUC1QWhaZR6ZcS3xOxtsSSqjofNRoq VNSMIDVFl3uvBsA7hFaetqAxxEDV8GMQHGw9M0Gt0s8Ya+qtqLbHcjNeuo8to5b1 2oWW0p3QadgWCoT6EJ9wijhGZ8X0MJGpBEUEfRmY570twGfEtNasgIWZfNDzxU8X 2i2A6nbpmK6EZup8/0BruH/hey8x8DHAGfT8lp0IhjNvyxkn1OTBFMansgaUVaHZ ZVILpA6UAc6VIRh1iZkRbglTHa9Odi3v4V78e0R64GmKS4LU4wrk6T5dG7062WRh 5vuLKs2/HHk= =I30q -END PGP SIGNATURE End Message ---
Bug#972747: Where is /usr/share/sbuild/create-chroot actually used?
Hi Bruno, Quoting Bruno Kleinert (2021-01-24 06:46:39) > I looked into /usr/share/sbuild/create-chroot to create a patch, but began to > wonder where and if that script is actually used. I use sbuild to locally > build packages on my desktop computer, so it's installed, and > > grep -r create-chroot /usr/sbin/sbuild* /usr/bin/sbuild* > > does not show any matches. > > Reverse dependencies and reverse recommends of sbuild are: >1. mini-buildd >2. arriero >3. xbuilder >4. ubuntu-dev-tools >5. schroot >6. sbuild-debian-developer-setup >7. ratt >8. qemu-sbuild-utils >9. pk4 > 10. packaging-dev > 11. debomatic > 12. lava-dev > 13. git-buildpackage > > I downloaded and extracted them and grepped for 'create-chroot' in > their contents: No matches. > > Looking into create-chroot revealed: > > […] > OLDSTABLE="squeeze" > STABLE="wheezy" > TESTING="jessie" > […] > > That leaves the impression the script was last used a couple of releases ago > and could simply be removed to close this bug. I have no objections. Aurelien Jarno also confirmed in IRC that it is not used in buildd purposes. Feel free to create a MR against the sbuild packaging repository. Thanks! cheers, josch signature.asc Description: signature
Bug#972262: marked as pending in ocamlviz
Control: tag -1 pending Hello, Bug #972262 in ocamlviz 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/ocamlviz/-/commit/d2a599e56e82e14a1284fbb6c5e2a7b7886ae9eb Fix FTBFS by using Bytes where necessary (Closes: #972262) - Remove 0003-Compile-with-unsafe-string-for-now.patch, which is not needed anymore - Add 0003-Use-Bytes-only-where-necessary.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/972262
Processed: Bug#972262 marked as pending in ocamlviz
Processing control commands: > tag -1 pending Bug #972262 [src:ocamlviz] FTBFS with OCaml 4.11.1 (-unsafe-string is not available) Added tag(s) pending. -- 972262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978327: marked as done (python-schema-salad: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)
Your message dated Sun, 24 Jan 2021 09:49:05 +
with message-id
and subject line Bug#978327: fixed in python-schema-salad 7.0.20200811075006-2
has caused the Debian Bug report #978327,
regarding python-schema-salad: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
978327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-schema-salad
Version: 7.0.20200811075006-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_install
> I: pybuild base:232: /usr/bin/python3 setup.py install --root
> /<>/debian/python3-schema-salad
> running install
> running build
> running build_py
> running egg_info
> writing schema_salad.egg-info/PKG-INFO
> writing dependency_links to schema_salad.egg-info/dependency_links.txt
> writing entry points to schema_salad.egg-info/entry_points.txt
> writing requirements to schema_salad.egg-info/requires.txt
> writing top-level names to schema_salad.egg-info/top_level.txt
> reading manifest file 'schema_salad.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*~' found anywhere in
> distribution
> warning: no previously-included files matching '*.pyc' found anywhere in
> distribution
> writing manifest file 'schema_salad.egg-info/SOURCES.txt'
> running install_lib
> creating /<>/debian/python3-schema-salad/usr
> creating /<>/debian/python3-schema-salad/usr/lib
> creating /<>/debian/python3-schema-salad/usr/lib/python3.9
> creating
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages
> creating
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/validate.py
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/__init__.py
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/__main__.py
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/sourceline.py
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/python_codegen_support.py
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/py.typed
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/schema.py
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad
> creating
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad/tests
> creating
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad/tests/docimp
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/tests/docimp/d2.md
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad/tests/docimp
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/tests/docimp/d5.md
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad/tests/docimp
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/tests/docimp/d1.yml
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad/tests/docimp
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/tests/docimp/d4.yml
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad/tests/docimp
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/tests/docimp/dpre.json
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad/tests/docimp
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/build/schema_salad/tests/docimp/d3.yml
> ->
> /<>/debian/python3-schema-salad/usr/lib/python3.9/dist-packages/schema_salad/tests/docimp
> copying
> /<>/.pybuild/cpython3_3.9_schema-salad/bu
Bug#970124: software-properties-common: add-apt-repository: missing dependency gpg (gnupg) (Was: Re: Bug#970124: Patch prepared for NMU)
Control: severity -1 normal On Sun, Jan 24, 2021 at 08:28:22AM +0100, Bruno Kleinert wrote: > Hi, > > please find attached a patch. If Julian or nobody else objects or jumps > in, I can NMU in about one week. Did you test it? I don't think this works, this is probably still the old version that actually needs key server functionality (dirmngr and gnupg), and I absolutely do not want to depend on those. I also don't think this is a release critical bug - the script is not the main attraction, it does not produce immediate useful results on Debian anyway if you add a PPA, given that the PPAs do not exist for Debian in the first place, and other uses do not involve that codepath AFAIUI. Anyhow, this email was the first time I heard about this bug, and it did not provide any context (and I can't open attachments on my phone), so I was a bit unhappy, and I did not have a lot of time to dig into it yet. My advise for future NMU emails: Please keep the original bug subject in the subject, and quote the bug report so readers can make sense out of it without having to search for the bug in the BTS. We really ought to update software-properties to the Ubuntu 20.04 version rather than try to ship the 16.04 one - it's 5 years old by now. I have no idea what happened here that we're still on the old version, I did upload the 18.04 one to experimental 2 years ago. This also fixes this bug because it now talks to the keyserver directly, and drops the file into trusted.gpg.d. Generally, please: If I have not answered you for a month, your email was lost, if it's still a problem, please ping me. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en signature.asc Description: PGP signature
Processed: Bug#970124: software-properties-common: add-apt-repository: missing dependency gpg (gnupg) (Was: Re: Bug#970124: Patch prepared for NMU)
Processing control commands: > severity -1 normal Bug #970124 [software-properties-common] software-properties-common: add-apt-repository: missing dependency gpg (gnupg) Severity set to 'normal' from 'serious' -- 970124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979405: marked as done (emscripten: FTBFS: Fatal: globalBase must be set)
Your message dated Sun, 24 Jan 2021 09:33:33 + with message-id and subject line Bug#979405: fixed in emscripten 2.0.10~dfsg-1 has caused the Debian Bug report #979405, regarding emscripten: FTBFS: Fatal: globalBase must be set 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.) -- 979405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emscripten Version: 2.0.9~dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, emscripten/experimental FTBFS with [...] PATH="/build/emscripten-2.0.9~dfsg:$PATH" EM_CACHE="/build/emscripten-2.0.9~dfsg/debian/em_cache" emcc tests/hello_world.c shared:INFO: (Emscripten: Running sanity checks) cache:INFO: generating system library: libc.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libc.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libcompiler_rt.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libcompiler_rt.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libc++-noexcept.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libc++-noexcept.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libc++abi-noexcept.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libc++abi-noexcept.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libdlmalloc.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libdlmalloc.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libpthread_stub.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libpthread_stub.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libc_rt_wasm.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libc_rt_wasm.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system library: libsockets.a... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/libsockets.a" for subsequent builds) cache:INFO: - ok cache:INFO: generating system asset: generated_struct_info.json... (this will be cached in "/build/emscripten-2.0.9~dfsg/debian/em_cache/wasm/generated_struct_info.json" for subsequent builds) Fatal: globalBase must be set emcc: error: '/usr/bin/wasm-emscripten-finalize --detect-features --minimize-wasm-changes --dyncalls-i64 /tmp/tmplzjtvhxu.wasm -o /tmp/tmplzjtvhxu.wasm' failed (1) FAIL: Compilation failed!: ['emcc', '-D_GNU_SOURCE', '-o', '/tmp/tmplzjtvhxu.js', '/tmp/tmprdy33uqc.c', '-O0', '--memory-init-file', '0', '-Werror', '-Wno-format', '-s', 'BOOTSTRAPPING_STRUCT_INFO=1', '-s', 'WARN_ON_UNDEFINED_SYMBOLS=0', '-s', 'STRICT=1', '-s', 'SINGLE_FILE=1', '-Wno-error=version-check', '-Wno-deprecated'] make[1]: *** [debian/rules:260: override_dh_auto_test] Error 1 make[1]: Leaving directory '/build/emscripten-2.0.9~dfsg' make: *** [debian/rules:244: binary] Error 2 Andreas emscripten_2.0.9~dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: emscripten Source-Version: 2.0.10~dfsg-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of emscripten, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated emscripten 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, 24 Jan 2021 10:16:41 +0100 Source: emscripten Architecture: source Version: 2.0.10~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 976520 979405 Changes: emscripten (2.0.10~dfsg-1) unstable; urgency=medium . [ upstream ] * new release; closes: bug#979405, thanks to Andreas Beckmann . [ Jonas Smedegaard ]
Processed: forcibly merging 976735 978648
Processing commands for cont...@bugs.debian.org: > forcemerge 976735 978648 Bug #976735 [spyder] spyder needs source upload for Python 3.9 transition Bug #978648 [spyder] spyder: Exits at startup with an import error for module zmq.backend.cython Severity set to 'serious' from 'grave' Merged 976735 978648 > thanks Stopping processing here. Please contact me if you need assistance. -- 976735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976735 978648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967170: markupsafe: Unversioned Python removal in sid/bullseye
fixed -1 1.1.1-1 close -1 thanks Looking at the package, it seems like this bug has been fixed in version 1.1.1-1 - I can find no more references to unversioned python in that version. I marked the bug as fixed. Please re-open if I am mistaken. Best, Jann On Tue, 04 Aug 2020 09:28:33 + Matthias Klose wrote: Package: src:markupsafe Version: 1.1.1-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list.
Processed: Issue confirmed, comes from upstream : forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 979465 https://github.com/wbhart/flint2/issues/889 Bug #979465 [src:flint] flint: FTBFS twice in a row Set Bug forwarded-to-address to 'https://github.com/wbhart/flint2/issues/889'. > thanks Stopping processing here. Please contact me if you need assistance. -- 979465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 937102
Processing commands for cont...@bugs.debian.org: > tags 937102 + help Bug #937102 [src:mysql-workbench] mysql-workbench: Python2 removal in sid/bullseye Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 937102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
On Saturday, 23 January 2021 6:28:09 AM AEDT Moritz Mühlenhoff wrote: > Indeed, the latest 8.0.23 release is now fixed: > | * MySQL Workbench now uses Python 3 for functionality such > | as migration, scripting shell, administrative tasks, and > | its SQL IDE. Just released, thanks for letting me know. It's been just several days since I've checked for new release. :) I've updated packaging for 8.0.23 but could not fix a new FTBFS problem... -- All the best, Dmitry Smirnov GPG key : 4096R/52B6BBD953968D1B --- The great enemy of the truth is very often not the lie -- deliberate, contrived and dishonest, but the myth, persistent, persuasive, and unrealistic. Belief in myths allows the comfort of opinion without the discomfort of thought. -- John F Kennedy --- And how long a lockdown is enough? If we open now, will lockdown recur in autumn? Next year? Whenever authoritarianism so wishes? No dictatorship could imagine a better precedent for absolute control. -- https://www.bmj.com/content/369/bmj.m1924.long :: BMJ 2020;369:m1924 "Should governments continue lockdown to slow the spread of covid-19?" signature.asc Description: This is a digitally signed message part.
