Bug#976687: marked as done (python3-escript: mixing incompatible libpython and libboost_python)
Your message dated Fri, 11 Dec 2020 07:33:46 + with message-id and subject line Bug#976687: fixed in python-escript 5.6-2 has caused the Debian Bug report #976687, regarding python3-escript: mixing incompatible libpython and libboost_python 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.) -- 976687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python3-escript Version: 5.5-5 Severity: serious Tags: bookworm sid Control: affects -1 python3-escript python3-escript-mpi $ objdump -p /usr/lib/python3-escript/esys/dudley/dudleycpp.so | grep python /usr/lib/python3-escript/esys/dudley/dudleycpp.so: file format elf64-x86-64 NEEDED libpython3.9.so.1.0 NEEDED libboost_python38.so.1.71.0 $ This is now no longer a problem for bullseye, but will again pop up during python3 transitions for bookworm. --- End Message --- --- Begin Message --- Source: python-escript Source-Version: 5.6-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of python-escript, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated python-escript 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: Thu, 10 Dec 2020 17:53:59 + Source: python-escript Architecture: source Version: 5.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 976555 976687 Changes: python-escript (5.6-2) unstable; urgency=medium . * Ack bugs fixed: Closes: #976555, #976687 * Fix boost_numpy.patch to find lib properly Checksums-Sha1: 900c1b2fc851e017c92c7405a054b690b899bcb4 2752 python-escript_5.6-2.dsc dabfd70680a93e277c16c3c1eb296f25462cced6 18236 python-escript_5.6-2.debian.tar.xz Checksums-Sha256: 12db7d09c3f76cbfe5cdec504c3d6b771f78a62933d4b4b1c60e2ee790c7a3b8 2752 python-escript_5.6-2.dsc c5e790d6927426afd89f7ecaa7f4ed1b763c9d32e171e5b4746b709e6ecf96d5 18236 python-escript_5.6-2.debian.tar.xz Files: d1663c1dd7270be6c0765b31bb8db8fc 2752 science optional python-escript_5.6-2.dsc f92057a44d3e2af46b37ad8d8a38473b 18236 science optional python-escript_5.6-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl/THWUACgkQy+a7Tl2a 06VZRg//Y2tS9nXOPzPnDyh/56ocwW2SKdOB6gvsjHzA0CI6Sbz13FoIDWvP1rvi AtHaFHrV+VHVZ4LJCccY7sAEY4GywsrLJaQEm9yu3aI5PiqOLruvRBlGIM5f0jWU BSVBog/SNMsqS79HSy1bRGrqOtF0LGBMAR5A7KOzby9agEJgygK914u6FYCGxP41 XWlBl4rmkDMCOcg4OefhiHcu6ArO/7bjJKjpfxlVr++JXBrkQ+Hg3KDfgQGSVBY1 32EAyApAf3biKXWY0ximr+GJUCodBh1ggIEcFafw2lYKhcu1eNuifE18UGLHREqF nyk8qt5zgT9bAdfe5Dx4KxYvC73ibNGZRB2dXyU3OQqh54yPM80SkSYM80S+6DEv qrvNFHiaJmVDo29ClWz87w/Ky58OUvh5ALSeHrUsgjNG/vWs/GPwMY/GoSFTBfy0 vnJDbbA4eWU4b21fjVIwo1AEji/9ocCink7440vuz+2FE3zcRAF2/Zck9T5DHgSG SD8OhhxCoFYa16BrrLybVAl9Ud4vWt2Oqm7x3/8PfFPeCawGXtTkNaFV+bnNSL3P zFduDoUUZPCXHiffXoLyLhPAhdhTQpSGmDTjjm29PVJjQUGLW8TtrIj0eNQ3zBxZ ojPWTG8fkG+MOeMndbckb/P7DDIzLjBs0kx6QvKw5Orh3KZnt4o= =hu5n -END PGP SIGNATURE End Message ---
Bug#976845: marked as done (wxpython-tools needs source upload for Python 3.9 transition)
Your message dated Fri, 11 Dec 2020 05:19:20 + with message-id and subject line Bug#976845: fixed in wxpython4.0 4.0.7+dfsg-7 has caused the Debian Bug report #976845, regarding wxpython-tools needs source upload for Python 3.9 transition 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.) -- 976845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wxpython-tools Version: 4.0.7+dfsg-6 Severity: serious Since binNMUs are not possible for binary-all packages, a source upload is needed for the Python 3.9 transition. In a more general note, do the tools have to use the versioned interpreter instead of python3? --- End Message --- --- Begin Message --- Source: wxpython4.0 Source-Version: 4.0.7+dfsg-7 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of wxpython4.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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated wxpython4.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: Thu, 10 Dec 2020 23:21:45 -0500 Source: wxpython4.0 Architecture: source Version: 4.0.7+dfsg-7 Distribution: unstable Urgency: medium Maintainer: wxWidgets Maintainers Changed-By: Scott Talbert Closes: 976845 977047 Changes: wxpython4.0 (4.0.7+dfsg-7) unstable; urgency=medium . * Rebuild for Python 3.9 (Closes: #976845) * Backport upstream fix for wxPseudoDC.FindObjects crash (Closes: #977047) * Backport upstream fix for wxCustomDataObject.GetData crash Checksums-Sha1: ac8df9076f6db791f1c3544b875a0eea8d4018b1 2574 wxpython4.0_4.0.7+dfsg-7.dsc 639d0bff491102c2cacfdbb525a4f28f17dd8dea 36428 wxpython4.0_4.0.7+dfsg-7.debian.tar.xz 302c19db3c2ad5a45ac87eb899b53aed6f9be542 20263 wxpython4.0_4.0.7+dfsg-7_amd64.buildinfo Checksums-Sha256: 95fe41299809f3565600697e3c98667f8462b0bf47850d85fe4f64d508f3dac8 2574 wxpython4.0_4.0.7+dfsg-7.dsc 3169d3c60a95edbefed84ee3ec8b64940283832c59963b60b170390d961eaacd 36428 wxpython4.0_4.0.7+dfsg-7.debian.tar.xz ded6a391e1d095671065d40b23f44d12495a730386abaa5252b0bffcf53d1eb4 20263 wxpython4.0_4.0.7+dfsg-7_amd64.buildinfo Files: fa0fef0357904e8045df5880bd61779f 2574 python optional wxpython4.0_4.0.7+dfsg-7.dsc ee2b4ba059725fd69b303a2228241591 36428 python optional wxpython4.0_4.0.7+dfsg-7.debian.tar.xz 9a88d7eb4cf95547bfa91b6b5dc59715 20263 python optional wxpython4.0_4.0.7+dfsg-7_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAl/S/aQPHHN3dEB0ZWNo aWUubmV0AAoJEFPVvGS1I3ii+GgQAMMzd7tHV6TT+LZWc7zZY6U18eSxxqOqiJQs FQQEK3f6yvNGGf57PwuGpuboZB8X+0nPsMtZPcEl0OM+bXIQ7zxDV3LmXc/pLVA5 z5+gtyc1r7im4u0TgHbHLOBNbwwDG9nrLCWgAC1cFo1jYBlTeYp8WewQK5wNz8+0 4j6OjFtFNaC/+u0NDJlnjK3dVGfPsdBQ3TZIYdYpJEnvLmmDF44ZpCDp7Letl4kh vITCCyr3DYsObxPoN4M6o3at89nEmCdRsMietYmNyIzYyhU+ZZSrylUdE6LjIeXk 53OyREsCAMkyGcMnRsP9QIGt79eFooRxvgI1u/Dy6dKYyqtB9wzIeNCz4pZSsln4 cqAtBjbikM1DAezrLdAI65jtkypWiHm6Mu/iUr3KJv/0vhcCKWZ78/0Bo4TLVE2k 6B1MpgI6S+4YOnim0crMQX8YYy8Q1ZZeQU9WL4guEGcbQ2vU3TFc561LJUGeQuWu mBewUDUIQBkpSGl3D0jSKN1jt2mffUi5dUGvO9tgStdoRfi03Bq7tHQV/nfIOqHB upTiv32AsM2AuByHNOr8bTfxPq/qDZxHPC8xwi4TcYEElP2lRGqugOzc9oZuwI2p zY2GEMclbccA+Batjn1C7VSO3jQ5OfeBvD9zYPDIcz3We0tH+oqOb7nOi4CcRx46 tpz1NrUo =ZMg2 -END PGP SIGNATURE End Message ---
Bug#976845: wxpython-tools needs source upload for Python 3.9 transition
On Wed, 9 Dec 2020, Adrian Bunk wrote: They probably don't. The tools are really just setuptools entry point scripts. The dependency is just coming from the shebang in those scripts I believe. In that case it should be fixed with override_dh_python3: dh_python3 --shebang=/usr/bin/python3 Thanks for that tip! Scott
Bug#976859: marked as done (fprintd: Impossible to verify: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.235")
Your message dated Fri, 11 Dec 2020 03:48:32 + with message-id and subject line Bug#976990: fixed in fprintd 1.90.7-1 has caused the Debian Bug report #976990, regarding fprintd: Impossible to verify: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.235" 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.) -- 976990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fprintd Version: 1.90.5-2 Severity: important Since upgrading to version 1.90.5 fprintd stoped working for me (on 2 different SID systems): $ fprintd-verify Impossible to verify: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.235" (uid=1000 pid=2294557 comm="fprintd-verify ") interface="net.reactivated.Fprint.Manager" member="GetDefaultDevice" error name="(unset)" requested_reply="0" destination=":1.236" (uid=0 pid=2294560 comm="/usr/libexec/fprintd ") It could be since a previous version, not 100% sure. Anyway, it seems v1.90.5 is quite broken (https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/92) and v1.90.6 fixes that ((https://gitlab.freedesktop.org/libfprint/fprintd/tags). Could you please upgrade the debian package to that upstream v1.90.6 as soon as it is possible? I was going to set severity to grave, but wasn’t sure about it. Feel free to change it. Thank you. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_USER, 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fprintd depends on: ii dbus 1.12.20-1 ii libc6 2.31-5 ii libfprint-2-2 1:1.90.5-2 ii libglib2.0-0 2.66.3-2 ii libpolkit-gobject-1-0 0.105-29 ii policykit-10.105-29 fprintd recommends no packages. fprintd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: fprintd Source-Version: 1.90.7-1 Done: =?utf-8?q?Marco_Trevisan_=28Trevi=C3=B1o=29?= We believe that the bug you reported is fixed in the latest version of fprintd, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco Trevisan (Treviño) (supplier of updated fprintd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Dec 2020 00:03:27 +0100 Source: fprintd Architecture: source Version: 1.90.7-1 Distribution: unstable Urgency: medium Maintainer: FingerForce Team Changed-By: Marco Trevisan (Treviño) Closes: 976990 Changes: fprintd (1.90.7-1) unstable; urgency=medium . * New upstream release - Fix fprintd DBus configuration (Closes: #976990) - Change details of what requires authorization - Fix various race conditions in pam_fprintd - Permit interactive authorization from fprintd utilities - Do not allow deletion while another operation is ongoing - pam: Guard strdup calls against NULL pointers * debian/patches: - Refresh - Ignore NameOwnerChanged until fprintd is running Checksums-Sha1: f5eaeb8d1bac11bc79dc1660915f6faea2531276 2458 fprintd_1.90.7-1.dsc c93c249f30a3c974c1e23196fcf3b4a6c27c3fa2 634821 fprintd_1.90.7.orig.tar.bz2 08c3c83ed97721741a470aef2db71b00790c5fc1 7784 fprintd_1.90.7-1.debian.tar.xz eb8eaa77db50c182846734e8c2b793a77d4b3dec 10317 fprintd_1.90.7-1_source.buildinfo Checksums-Sha256: 0b1ffe4a129a5f1a2fa5527af83428bc5d7f455b0860b22c40da65996ace6465 2458 fprintd_1.90.7-1.dsc 7ff9497053fb780ba19cd515eba25dc71f810c16d3db9d9e192fb5f2fb6f282f 634821 fprintd_1.90.7.orig.tar.bz2 9e5a44ad2d2de51ebc54cf03edbb6fc8e3986202e48620d3de95ef14f7996df8 7784 fprintd_1.90.7-1.debian.tar.xz
Bug#976990: marked as done (fprintd: Latest update broke fprintd entirely)
Your message dated Fri, 11 Dec 2020 03:48:32 + with message-id and subject line Bug#976990: fixed in fprintd 1.90.7-1 has caused the Debian Bug report #976990, regarding fprintd: Latest update broke fprintd entirely 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.) -- 976990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fprintd Version: 1.90.5-2 Severity: grave X-Debbugs-Cc: Asher Gordon Dear Maintainer, After upgrading fprintd (and libpam-fprintd) from 1.90.1-2 to 1.90.5-2, it stopped working entirely. Instead of fingerprint authentication, password authentication is used for login and sudo. I have checked that /etc/pam.d/common-auth has the right settings. The problem appears to be that fprintd itself has stopped working, not the PAM module (which is why I reported this bug in fprintd rather than libpam-fprintd). When I use any of the fprintd-* commands, it fails as follows: $ fprintd-delete asher Impossible to get devices: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.184" (uid=1000 pid=15139 comm="fprintd-delete asher ") interface="net.reactivated.Fprint.Manager" member="GetDevices" error name="(unset)" requested_reply="0" destination=":1.185" (uid=0 pid=15143 comm="/usr/libexec/fprintd ") $ fprintd-enroll asher Impossible to enroll: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.186" (uid=1000 pid=15151 comm="fprintd-enroll asher ") interface="net.reactivated.Fprint.Manager" member="GetDefaultDevice" error name="(unset)" requested_reply="0" destination=":1.185" (uid=0 pid=15143 comm="/usr/libexec/fprintd ") $ fprintd-list asher Impossible to get devices: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.188" (uid=1000 pid=15165 comm="fprintd-list asher ") interface="net.reactivated.Fprint.Manager" member="GetDevices" error name="(unset)" requested_reply="0" destination=":1.185" (uid=0 pid=15143 comm="/usr/libexec/fprintd ") $ fprintd-verify Impossible to verify: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.189" (uid=1000 pid=15169 comm="fprintd-verify ") interface="net.reactivated.Fprint.Manager" member="GetDefaultDevice" error name="(unset)" requested_reply="0" destination=":1.185" (uid=0 pid=15143 comm="/usr/libexec/fprintd ") From the org.freedesktop.DBus.Error.AccessDenied error, it seems that it might be a permissions problem. However, the commands do not work, even when run as root: $ sudo fprintd-list asher [sudo] password for asher: Impossible to get devices: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.199" (uid=0 pid=15422 comm="fprintd-list asher ") interface="net.reactivated.Fprint.Manager" member="GetDevices" error name="(unset)" requested_reply="0" destination=":1.200" (uid=0 pid=15425 comm="/usr/libexec/fprintd ") All the above commands returned with an exit status of 1. Also, if I run /usr/libexec/fprintd manually, I get the following warning (although a 0 exit status): $ /usr/libexec/fprintd (fprintd:15733): fprintd-WARNING **: 13:01:49.856: Failed to get name: net.reactivated.Fprint Perhaps this is because fprintd is already running. However 'ps -fe | grep [f]printd' lists no processes. Thanks, Asher -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 fprintd depends on: ii dbus 1.12.20-1 ii libc6 2.31-5 ii libfprint-2-2 1:1.90.5-2 ii libglib2.0-0 2.66.3-2 ii libpolkit-gobject-1-0 0.105-29 ii policykit-10.105-29 fprintd recommends no packages. fprintd suggests no packages. -- no debconf information -- By necessity, by proclivity, and by delight, we all quote. In fact, it is as difficult to appropriate the thoughts of others as it is to invent.
Bug#976934: marked as done (notmuch: FTBFS on ppc64el: FileNotFoundError: [Errno 2] No such file or directory: '/<>/emacs/notmuch.rsti')
Your message dated Fri, 11 Dec 2020 01:33:30 + with message-id and subject line Bug#976934: fixed in notmuch 0.31.2-4 has caused the Debian Bug report #976934, regarding notmuch: FTBFS on ppc64el: FileNotFoundError: [Errno 2] No such file or directory: '/<>/emacs/notmuch.rsti' 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.) -- 976934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: notmuch Version: 0.31.2-3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64. I'm marking this bug as severity:serious since your package currently has ppc64el binary packages in unstable (so this is a regression). Relevant part (hopefully): > make[2]: Entering directory '/<>' > echo 0.31.2 > version.stamp > emacs --quick --directory emacs -batch -l make-deps.el \ > -f batch-make-deps emacs/notmuch-lib.el emacs/notmuch-compat.el > emacs/notmuch-parser.el emacs/notmuch.el emacs/notmuch-query.el > emacs/notmuch-show.el emacs/notmuch-tree.el emacs/notmuch-wash.el > emacs/notmuch-hello.el emacs/notmuch-mua.el emacs/notmuch-address.el > emacs/notmuch-maildir-fcc.el emacs/notmuch-message.el emacs/notmuch-crypto.el > emacs/notmuch-tag.el emacs/coolj.el emacs/notmuch-print.el > emacs/notmuch-version.el emacs/notmuch-jump.el emacs/notmuch-company.el > emacs/notmuch-draft.el > emacs/.eldeps.tmp && \ > mv emacs/.eldeps.tmp emacs/.eldeps > cc -c -DNOTMUCH_VERSION=0.31.2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wextra -Wwrite-strings -Wmissing-declarations > -I./util -I./compat -I./lib -fPIC -fvisibility=hidden -I./parse-time-string > -I. -D_LARGEFILE64_SOURCE -pthread -I/usr/include/gmime-3.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -DHAVE_VALGRIND=0 > -DHAVE_GETLINE=1 -DWITH_EMACS=1 -DHAVE_CANONICALIZE_FILE_NAME=1 > -DHAVE_STRCASESTR=1 -DHAVE_STRSEP=1 -DHAVE_TIMEGM=1 -DHAVE_D_TYPE=1 > -DSTD_GETPWUID=1 -DSTD_ASCTIME=1 -DSILENCE_XAPIAN_DEPRECATION_WARNINGS > -DHAVE_XAPIAN_DB_RETRY_LOCK=1 command-line-arguments.c -o > command-line-arguments.o -MD -MP -MF .deps/command-line-arguments.d > cc -c -DNOTMUCH_VERSION=0.31.2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wextra -Wwrite-strings -Wmissing-declarations > -I./util -I./compat -I./lib -fPIC -fvisibility=hidden -I./parse-time-string > -I. -D_LARGEFILE64_SOURCE -pthread -I/usr/include/gmime-3.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -DHAVE_VALGRIND=0 > -DHAVE_GETLINE=1 -DWITH_EMACS=1 -DHAVE_CANONICALIZE_FILE_NAME=1 > -DHAVE_STRCASESTR=1 -DHAVE_STRSEP=1 -DHAVE_TIMEGM=1 -DHAVE_D_TYPE=1 > -DSTD_GETPWUID=1 -DSTD_ASCTIME=1 -DSILENCE_XAPIAN_DEPRECATION_WARNINGS > -DHAVE_XAPIAN_DB_RETRY_LOCK=1 debugger.c -o debugger.o -MD -MP -MF > .deps/debugger.d > cc -c -DNOTMUCH_VERSION=0.31.2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wextra -Wwrite-strings -Wmissing-declarations > -I./util -I./compat -I./lib -fPIC -fvisibility=hidden -I./parse-time-string > -I. -D_LARGEFILE64_SOURCE -pthread -I/usr/include/gmime-3.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -DHAVE_VALGRIND=0 > -DHAVE_GETLINE=1 -DWITH_EMACS=1 -DHAVE_CANONICALIZE_FILE_NAME=1 > -DHAVE_STRCASESTR=1 -DHAVE_STRSEP=1 -DHAVE_TIMEGM=1 -DHAVE_D_TYPE=1 > -DSTD_GETPWUID=1 -DSTD_ASCTIME=1 -DSILENCE_XAPIAN_DEPRECATION_WARNINGS > -DHAVE_XAPIAN_DB_RETRY_LOCK=1 status.c -o status.o -MD -MP -MF .deps/status.d > cc -c -DNOTMUCH_VERSION=0.31.2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wextra -Wwrite-strings -Wmissing-declarations > -I./util -I./compat -I./lib -fPIC -fvisibility=hidden -I./parse-time-string > -I. -D_LARGEFILE64_SOURCE -pthread -I/usr/include/gmime-3.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -DHAVE_VALGRIND=0
Bug#976934: [PATCH] build/docs: move docstring prereq to file targets
Tomi Ollila writes: > On Wed, Dec 09 2020, David Bremner wrote: > >> Under a sufficiently high level of parallelism [1] there seems to be a >> a race condition that allows sphinx-build to start running before the >> docstrings are extracted. This change moves the docstring stamp from >> the phony targets sphinx-html and sphinx-info to the file targets that >> they depend on. I'm not sure why this makes things better, but I am >> fairly confident it does not make things worse, and experimentally it >> seems to eliminate the race condition. > > Good enough for me if this helps. I also don't see reason why that would > make things better (and probably not things worse), just that I got > headache reading that Makefile ;) (and, for example, these particular > targets mentioned would not need to be marked .PHONY...) > > I'd suggest to monitor the behaviour for a while and if things are > consistently better then merge -- such a things when we don't know > enough experience may be enough (or someone(tm) could try to parse make > debug logs ;/) -- or someone(tm) may tell us why that heleps :D I'll try a test upload to Debian and see if that fixes the problem there. I did 2000 builds (sortof by mistake) at -j32 on a 16 thread / 8 core machine, with no crashes. Much less parallelism than the original report, but lots of repetition. d
Bug#975486: marked as done (rust-libz-sys: autopkgtest failure: src/zlib/adler32.c: No such file or directory)
Your message dated Fri, 11 Dec 2020 01:11:56 +
with message-id
and subject line rust-libz-sys
has caused the Debian Bug report #975486,
regarding rust-libz-sys: autopkgtest failure: src/zlib/adler32.c: No such file
or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
975486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-libz-sys
Version: 1.1.2-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package rust-libz-sys, great.
However, it fails. Currently this failure is blocking the migration to
testing [1]. Can you please investigate the situation and fix it?
I copied some of the output at the bottom of this report.
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=rust-libz-sys
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-libz-sys/7592938/log.gz
Running
`/tmp/tmp.GylevYz9Se/target/debug/build/libz-sys-4d7f2bd81492bad5/build-script-build`
[libz-sys 1.1.2] cargo:rerun-if-env-changed=LIBZ_SYS_STATIC
[libz-sys 1.1.2] cargo:rerun-if-changed=build.rs
[libz-sys 1.1.2] TARGET = Some("x86_64-unknown-linux-gnu")
[libz-sys 1.1.2] OPT_LEVEL = Some("0")
[libz-sys 1.1.2] HOST = Some("x86_64-unknown-linux-gnu")
[libz-sys 1.1.2] CC_x86_64-unknown-linux-gnu = None
[libz-sys 1.1.2] CC_x86_64_unknown_linux_gnu = None
[libz-sys 1.1.2] HOST_CC = None
[libz-sys 1.1.2] CC = None
[libz-sys 1.1.2] CFLAGS_x86_64-unknown-linux-gnu = None
[libz-sys 1.1.2] CFLAGS_x86_64_unknown_linux_gnu = None
[libz-sys 1.1.2] HOST_CFLAGS = None
[libz-sys 1.1.2] CFLAGS = Some("-g -O2
-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=.
-fstack-protector-strong -Wformat -Werror=format-security")
[libz-sys 1.1.2] CRATE_CC_NO_DEFAULTS = None
[libz-sys 1.1.2] DEBUG = Some("true")
[libz-sys 1.1.2] CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
[libz-sys 1.1.2] running: "cc" "-O0" "-ffunction-sections"
"-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-g"
"-O2" "-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=."
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" "-I"
"src/zlib" "-fvisibility=hidden" "-DSTDC" "-D_LARGEFILE64_SOURCE"
"-D_POSIX_SOURCE" "-o"
"/tmp/tmp.GylevYz9Se/target/x86_64-unknown-linux-gnu/debug/build/libz-sys-a4a1831fc0ceaac9/out/build/src/zlib/adler32.o"
"-c" "src/zlib/adler32.c"
[libz-sys 1.1.2] cargo:warning=cc: error: src/zlib/adler32.c: No such
file or directory
[libz-sys 1.1.2] cargo:warning=cc: fatal error: no input files
[libz-sys 1.1.2] cargo:warning=compilation terminated.
[libz-sys 1.1.2] exit code: 1
[libz-sys 1.1.2]
[libz-sys 1.1.2]
[libz-sys 1.1.2] error occurred: Command "cc" "-O0"
"-ffunction-sections" "-fdata-sections" "-fPIC" "-g"
"-fno-omit-frame-pointer" "-m64" "-g" "-O2"
"-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=."
"-fstack-protector-strong" "-Wformat" "-Werror=format-security" "-I"
"src/zlib" "-fvisibility=hidden" "-DSTDC" "-D_LARGEFILE64_SOURCE"
"-D_POSIX_SOURCE" "-o"
"/tmp/tmp.GylevYz9Se/target/x86_64-unknown-linux-gnu/debug/build/libz-sys-a4a1831fc0ceaac9/out/build/src/zlib/adler32.o"
"-c" "src/zlib/adler32.c" with args "cc" did not execute successfully
(status code exit code: 1).
[libz-sys 1.1.2]
[libz-sys 1.1.2]
error: failed to run custom build command for `libz-sys v1.1.2
(/usr/share/cargo/registry/libz-sys-1.1.2)`
Caused by:
process didn't exit successfully:
`/tmp/tmp.GylevYz9Se/target/debug/build/libz-sys-4d7f2bd81492bad5/build-script-build`
(exit code: 1)
--- stdout
cargo:rerun-if-env-changed=LIBZ_SYS_STATIC
cargo:rerun-if-changed=build.rs
TARGET = Some("x86_64-unknown-linux-gnu")
OPT_LEVEL = Some("0")
HOST = Some("x86_64-unknown-linux-gnu")
CC_x86_64-unknown-linux-gnu = None
CC_x86_64_unknown_linux_gnu = None
HOST_CC = None
CC = None
CFLAGS_x86_64-unknown-linux-gnu = None
CFLAGS_x86_64_unknown_linux_gnu = None
HOST_CFLAGS = None
CFLAGS = Some("-g -O2
-fdebug-prefix-map=/usr/share/cargo/registry/libz-sys-1.1.2=.
-fstack-protector-strong -Wformat -Werror=format-security")
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("true")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
running: "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g"
"-fno-omit-frame-pointer" "-m64" "-g" "-O2"
Bug#958604: marked as done (ircd-irc2: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Fri, 11 Dec 2020 00:48:22 + with message-id and subject line Bug#958604: fixed in ircd-irc2 2.11.2p3~dfsg-5.1 has caused the Debian Bug report #958604, regarding ircd-irc2: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ircd-irc2 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package ircd-irc2 declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Source: ircd-irc2 Source-Version: 2.11.2p3~dfsg-5.1 Done: Nicholas D Steeves We believe that the bug you reported is fixed in the latest version of ircd-irc2, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas D Steeves (supplier of updated ircd-irc2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 09 Dec 2020 21:13:51 -0500 Source: ircd-irc2 Architecture: source Version: 2.11.2p3~dfsg-5.1 Distribution: unstable Urgency: medium Maintainer: Kurt Roeckx Changed-By: Nicholas D Steeves Closes: 958604 Changes: ircd-irc2 (2.11.2p3~dfsg-5.1) unstable; urgency=medium . * Non-maintainer upload. * Drop unnecessary dh-systemd build-dep, because debhelper (>= 9.20160709) already provides this (Closes: #958604). * ircd-irc2.lintian-overrides: "package-contains-upstream-install-documentation" no longer exists, so use its replacement "package-contains-upstream-installation-documentation". Checksums-Sha1: b75abce56e6f03f40e8b28799c582a6a4d558736 1994 ircd-irc2_2.11.2p3~dfsg-5.1.dsc 343c0cd75c1bb5c492db29814ff720f469d07962 23568 ircd-irc2_2.11.2p3~dfsg-5.1.debian.tar.xz 89c3a79790dd31f0857a5934ddac9927f554366b 5587 ircd-irc2_2.11.2p3~dfsg-5.1_source.buildinfo Checksums-Sha256: 27e069a8d0380ed63df8aa942e247f4fec513d02720ed328695cde64266eebc1 1994 ircd-irc2_2.11.2p3~dfsg-5.1.dsc fb9332c89d598e159c71ea57f1fe1762f3e15e6421728263b910f63dc4c890b6 23568 ircd-irc2_2.11.2p3~dfsg-5.1.debian.tar.xz 9528bb3228f78708bef77df2fb33d42ef6cc7a561d70fc302353770630bff46b 5587 ircd-irc2_2.11.2p3~dfsg-5.1_source.buildinfo Files: f94c2dbe19acd8068eea010a2ada6b88 1994 net optional ircd-irc2_2.11.2p3~dfsg-5.1.dsc 8187dc570d4fe8db0af852216ba1c42e 23568 net optional ircd-irc2_2.11.2p3~dfsg-5.1.debian.tar.xz a6bd627c3ca030eb25ac6733d22991f5 5587 net optional ircd-irc2_2.11.2p3~dfsg-5.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl/SvF4ACgkQweDZLphv fH4oHA/8Cgd2eO2Fzbk2pBQ9p1uD75uea3rxgG9sQp7Fx7VS7i5O66MMJb3oL0x+ UK8L3pxMQ3rWxMt6QYO0IHZzO8YMLNoLgrZHHQir/c6hAUbIaP/GJmnrHZ+yFk5M Bf7uRE3/xPtZEGs+/FKL0GZeUoziZJG8zbPrtUE49/vazRDA8WL/9wzcWwE8psVQ pALYLI1zR5ivZortki2d4O3NbOSUEuKGHG+mVkeJatqJS7UPp4M3qqAf5bcUEnVl ign51R0wMRkXB71ewjpcsPs0N79rYmlmBZwCSJrWwHDJW7hHpCkFfMJU15eceSZy 6s8rNXNIOuxiNG86yhP6nL24ygTbbn5cIhudo09KOPqp6U7CncU5NrCbj4jfPzdW mKha5QJw/rHM4vGUaYapG0QarfDY8kohglQQK043SBOQ3Jq8w6JJdxh8KHLDD3IL nZkmLGMbwlXrG3tYY6OBDUK/+KWPT2bDngBLbzyC/873l9fOPzPNnFVhNAPUrRJ6 dNgKZkAgEudeUxoujFVI8o4S9llV47JaQdC3SWIyHf0J1qaQLP42Wzq6xcO2tp23 5g8m8q/KcOyL5P8XQgop8OU3cNPrcMGt3DY0aJtdPmjlf/d1tbCYcsl9pSgLok8t 0SUHFLwhWkvNIyas8LB9A0WlYrWcifrJ/MM4wFNeCjQNwjFAqjY= =zUoI -END PGP SIGNATURE End Message ---
Bug#977109: ruby-licensee, autopkgtest failure with ruby-rugged 1.1.0
package: ruby-licensee Version: 8.9.2-1 Severity: serious Tags: bullseye, sid The autopkgtest for ruby-licensee is failing with ruby-rugged 1.1.0. GEM_PATH= ruby2.7 -e gem\ \"licensee\" /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1398:in `rescue in block in activate_dependencies': Could not find 'rugged' (~> 0.24) among 92 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' at: /usr/share/rubygems-integration/all/specifications/licensee-8.9.2.gemspec, execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1395:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309:in `to_specs': Could not find 'rugged' (~> 0.24) - did find: [rugged-1.1.0] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' , execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1396:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' This is blocking ruby-rugged 1.1.0 (which is needed for the libgit2 transition) from migrating to testing.
Bug#977108: ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0
package: ruby-gollum-rugged-apapter Version: 0.4.4.2-2 Severity: serious The autopkgtest for ruby-gollum-rugged-adapter is failing with ruby-rugged 1.1.0. ┌──┐ │ Checking Rubygems dependency resolution on ruby2.7 │ └──┘ GEM_PATH= ruby2.7 -e gem\ \"gitlab-gollum-rugged_adapter\" /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1398:in `rescue in block in activate_dependencies': Could not find 'rugged' (~> 0.25) among 60 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' at: /usr/share/rubygems-integration/all/specifications/gitlab-gollum-rugged_adapter-0.4.4.2.gemspec, execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1395:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309:in `to_specs': Could not find 'rugged' (~> 0.25) - did find: [rugged-1.1.0] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' , execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1396:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' This is blocking ruby-rugged 1.1.0 (which is needed for the libgit2 transition) from migrating to testing.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > package fprintd Limiting to bugs with field 'package' containing at least one of 'fprintd' Limit currently set to 'package':'fprintd' > severity 976859 grave Bug #976859 [fprintd] fprintd: Impossible to verify: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.235" Severity set to 'grave' from 'important' > merge 976859 976990 Bug #976859 [fprintd] fprintd: Impossible to verify: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.235" Bug #976990 [fprintd] fprintd: Latest update broke fprintd entirely Merged 976859 976990 > thanks Stopping processing here. Please contact me if you need assistance. -- 976859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976859 976990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977036: marked as done (skopeo: autopkgtest regression: cannot find package "github.com/containers/common/pkg/retry")
Your message dated Thu, 10 Dec 2020 22:19:20 + with message-id and subject line Bug#977036: fixed in skopeo 1.2.0+dfsg1-2 has caused the Debian Bug report #977036, regarding skopeo: autopkgtest regression: cannot find package "github.com/containers/common/pkg/retry" 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.) -- 977036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: skopeo Version: 1.2.0+dfsg1-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of skopeo the autopkgtest of skopeo fails in testing when that autopkgtest is run with the binary packages of skopeo from unstable. It passes when run with only packages from testing. In tabular form: passfail skopeo from testing1.2.0+dfsg1-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. I triggered the test in unstable, and there it works. It seems like your missing a *versioned* (test) dependency somewhere? Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=skopeo https://ci.debian.net/data/autopkgtest/testing/amd64/s/skopeo/8740501/log.gz autopkgtest [09:16:36]: test dh-golang-autopkgtest: [--- [info] Testing github.com/containers/skopeo... [info] Source code not installed by binary packages, using source package... dh build --buildsystem=golang --with=golang dh_update_autotools_config -O--buildsystem=golang dh_autoreconf -O--buildsystem=golang dh_auto_configure -O--buildsystem=golang dh_auto_build -O--buildsystem=golang cd obj-x86_64-linux-gnu && go generate -v github.com/containers/skopeo/cmd/skopeo github.com/containers/skopeo/cmd/skopeo/inspect github.com/containers/skopeo/version src/github.com/containers/skopeo/cmd/skopeo/cgo_pthread_ordering_workaround.go src/github.com/containers/skopeo/cmd/skopeo/copy.go src/github.com/containers/skopeo/cmd/skopeo/delete.go src/github.com/containers/skopeo/cmd/skopeo/flag.go src/github.com/containers/skopeo/cmd/skopeo/flag_test.go src/github.com/containers/skopeo/cmd/skopeo/inspect.go src/github.com/containers/skopeo/cmd/skopeo/layers.go src/github.com/containers/skopeo/cmd/skopeo/list_tags.go src/github.com/containers/skopeo/cmd/skopeo/list_tags_test.go src/github.com/containers/skopeo/cmd/skopeo/login.go src/github.com/containers/skopeo/cmd/skopeo/logout.go src/github.com/containers/skopeo/cmd/skopeo/main.go src/github.com/containers/skopeo/cmd/skopeo/main_test.go src/github.com/containers/skopeo/cmd/skopeo/manifest.go src/github.com/containers/skopeo/cmd/skopeo/manifest_test.go src/github.com/containers/skopeo/cmd/skopeo/signing.go src/github.com/containers/skopeo/cmd/skopeo/signing_test.go src/github.com/containers/skopeo/cmd/skopeo/sync.go src/github.com/containers/skopeo/cmd/skopeo/unshare_linux.go src/github.com/containers/skopeo/cmd/skopeo/utils.go src/github.com/containers/skopeo/cmd/skopeo/utils_test.go src/github.com/containers/skopeo/cmd/skopeo/inspect/output.go src/github.com/containers/skopeo/version/version.go cd obj-x86_64-linux-gnu && go install -trimpath -v -p 48 github.com/containers/skopeo/cmd/skopeo github.com/containers/skopeo/cmd/skopeo/inspect github.com/containers/skopeo/version src/github.com/containers/skopeo/cmd/skopeo/copy.go:9:2: cannot find package "github.com/containers/common/pkg/retry" in any of: /usr/lib/go-1.15/src/github.com/containers/common/pkg/retry (from $GOROOT) /tmp/autopkgtest-lxc.1skd3arf/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/containers/common/pkg/retry (from $GOPATH) dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 48 github.com/containers/skopeo/cmd/skopeo github.com/containers/skopeo/cmd/skopeo/inspect github.com/containers/skopeo/version returned exit code 1 make: *** [debian/rules:22: build] Error 25 autopkgtest [09:16:38]: test dh-golang-autopkgtest: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: skopeo Source-Version:
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Hi, On 10/12/20 at 22:16 +0100, John Paul Adrian Glaubitz wrote: > Hi! > > On 12/10/20 10:12 PM, Michael Biebl wrote: > >> Did the test machine you used actually have that many cores? > > > > No idea > > I just checked plummer.debian.org and it has only 16 (virtual) CPUs. > > Would be curious to hear whether Lucas' test machine had >= 160 CPUs. It has 160 SMT threads (2 sockets x 10 cores/socket x 8 threads/core). I'll try to reproduce the failure and get more info tomorrow or over the week-end. Lucas
Bug#954270: marked as done (kmc: autopgktest times out on multimulticore hosts)
Your message dated Thu, 10 Dec 2020 21:49:19 + with message-id and subject line Bug#954270: fixed in kmc 3.1.1+dfsg-1 has caused the Debian Bug report #954270, regarding kmc: autopgktest times out on multimulticore hosts 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.) -- 954270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kmc Version: 2.3+dfsg-7 Severity: important X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: timeout Dear maintainer(s), kmc fails its autopkgtest on arm64 due to a time out after 2h47. Can you please investigate the situation? To avoid wasting lots of time on the ci.debian.net infrastructure, I have added your package to the ignore list for arm64. Paul https://ci.debian.net/data/autopkgtest/testing/arm64/k/kmc/4557365/log.gz autopkgtest [14:57:08]: test build-lib: [--- build: OK *autopkgtest [17:43:48]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.psdr2acq/downtmp/build.SOh/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.psdr2acq/downtmp/build-lib-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.psdr2acq/downtmp/build-lib-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.psdr2acq/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.psdr2acq/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=32; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod +x /tmp/autopkgtest-lxc.psdr2acq/downtmp/build.SOh/src/debian/tests/build-lib; touch /tmp/autopkgtest-lxc.psdr2acq/downtmp/build-lib-stdout /tmp/autopkgtest-lxc.psdr2acq/downtmp/build-lib-stderr; /tmp/autopkgtest-lxc.psdr2acq/downtmp/build.SOh/src/debian/tests/build-lib 2> >(tee -a /tmp/autopkgtest-lxc.psdr2acq/downtmp/build-lib-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.psdr2acq/downtmp/build-lib-stdout);" (kind: test) autopkgtest [17:43:49]: test build-lib: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: kmc Source-Version: 3.1.1+dfsg-1 Done: =?utf-8?q?=C3=89tienne_Mollier?= We believe that the bug you reported is fixed in the latest version of kmc, 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 954...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated kmc 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: Thu, 10 Dec 2020 21:59:30 +0100 Source: kmc Architecture: source Version: 3.1.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 954270 Changes: kmc (3.1.1+dfsg-1) unstable; urgency=medium . * Added myself to Uploaders. * New upstream version (Closes: #954270) * Remove changes related to asmlib, not used upstream anymore. * Refresh use-shared-libs patch. * Fold patches to makefile into makefile.patch. * Refresh 0005-Add-static-library-target-to-makefile.patch. * Wrote a new spelling patch as previous patch has been applied upstream. * Refresh patch newish_gcc_build_fix.patch * Removed patch cap-default-thread-count.patch * Activated highly threaded test in autopkgtest * Disable the newer python3 bindings for the moment. Checksums-Sha1: e9998c6526480f8f954569f572aeb4de423bd21a 2224 kmc_3.1.1+dfsg-1.dsc 8a25991be0903612638d1db6b843577170fea19a 241704 kmc_3.1.1+dfsg.orig.tar.xz 4654cd61bf0528e6fed18895b6536b171648cbb3 30392 kmc_3.1.1+dfsg-1.debian.tar.xz
Bug#977103: chromium: FTBFS on armhf: error: write to reserved register 'R7'
Source: chromium
Version: 83.0.4103.116-3.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
chromium fails to build on armhf:
| FAILED: obj/v8/v8_base_without_compiler/cpu-arm.o
| clang++ -MMD -MF obj/v8/v8_base_without_compiler/cpu-arm.o.d -DUSE_UDEV
-DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE
-DCR_CLANG_REVISION=\"n346557-4e0d9925-2\" -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64
-DENABLE_MINOR_MC -DV8_INTL_SUPPORT -DV8_USE_EXTERNAL_STARTUP_DATA
-DV8_CONCURRENT_MARKING -DV8_ARRAY_BUFFER_EXTENSION
-DV8_ENABLE_LAZY_SOURCE_POSITIONS -DV8_EMBEDDED_BUILTINS -DV8_SHARED_RO_HEAP
-DV8_WIN64_UNWINDING_INFO -DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH
-DV8_SNAPSHOT_COMPRESSION -DV8_DEPRECATION_WARNINGS -DV8_TARGET_ARCH_ARM
-DCAN_USE_ARMV7_INSTRUCTIONS -DCAN_USE_VFP3_INSTRUCTIONS -DV8_HAVE_TARGET_OS
-DV8_TARGET_OS_LINUX -DDISABLE_UNTRUSTED_CODE_MITIGATIONS
-DV8_DEPRECATION_WARNINGS -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_40
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_40 -DUSING_SYSTEM_ICU=1
-DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC -DUCHAR_TYPE=uint16_t
-DU_IMPORT=U_EXPORT -DV8_DEPRECATION_WARNINGS -DUSE_SYSTEM_ZLIB=1 -I../.. -Igen
-I../../v8 -Igen/v8 -Igen/shim_headers/icui18n_shim
-Igen/shim_headers/icuuc_shim -Igen/shim_headers/libevent_shim
-Igen/shim_headers/zlib_shim -I../../v8/include -fno-strict-aliasing
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pthread
-fcolor-diagnostics -fmerge-all-constants
-fcrash-diagnostics-dir=../../tools/clang/crashreports -Xclang -mllvm -Xclang
-instcombine-lower-dbg-declare=0 --target=arm-linux-gnueabihf -march=armv7-a
-mfloat-abi=hard -mtune=generic-armv7-a -Wno-builtin-macro-redefined
-D__DATE__= -D__TIME__= -D__TIMESTAMP__= -Xclang -fdebug-compilation-dir
-Xclang . -no-canonical-prefixes -mfpu=vfpv3-d16 -mthumb -Wall -Wextra
-Wimplicit-fallthrough -Wunreachable-code -Wthread-safety -Wextra-semi
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing
-Wno-unneeded-internal-declaration -Wno-undefined-var-template
-Wno-ignored-pragma-optimize -Wno-pointer-to-int-cast -fno-omit-frame-pointer
-g0 -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare
-Wmissing-field-initializers -Wunreachable-code -fno-ident -fdata-sections
-ffunction-sections -fvisibility=default -Wexit-time-destructors
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
-std=c++14 -fno-exceptions -fno-rtti -Wdate-time -D_FORTIFY_SOURCE=2 -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wno-conversion -Wno-unused-function
-Wno-unused-variable -Wno-unused-private-field -Wno-deprecated-declarations
-fno-delete-null-pointer-checks -c ../../v8/src/codegen/arm/cpu-arm.cc -o
obj/v8/v8_base_without_compiler/cpu-arm.o
| ../../v8/src/codegen/arm/cpu-arm.cc:45:16: error: write to reserved register
'R7'
| asm volatile("svc 0\n"
|^
| 1 error generated.
| [32359/39645] CXX obj/v8/v8_base_without_compiler/wasm-serialization.o
| [32360/39645] CXX obj/v8/v8_base_without_compiler/interface-descriptors-arm.o
| [32361/39645] CXX obj/v8/v8_base_without_compiler/assembler-arm.o
| ninja: build stopped: subcommand failed.
See
https://buildd.debian.org/status/fetch.php?pkg=chromium=armhf=83.0.4103.116-3.1%2Bb2=1607626873=0
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
On 12/10/20 10:16 PM, Michael Biebl wrote: >>> Did the test machine you used actually have that many cores? >> >> No idea > > But given that there is only a single test, I wonder if that is really > relevant anyway. You're right. That's rather strange. Hmm. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Hi! On 12/10/20 10:12 PM, Michael Biebl wrote: >> Did the test machine you used actually have that many cores? > > No idea I just checked plummer.debian.org and it has only 16 (virtual) CPUs. Would be curious to hear whether Lucas' test machine had >= 160 CPUs. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Am 10.12.20 um 22:12 schrieb Michael Biebl: Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: Hi Michael! On 12/10/20 8:42 PM, Michael Biebl wrote: Testsuite summary for systemd-bootchart 233 # TOTAL: 1 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 Did the test machine you used actually have that many cores? No idea But given that there is only a single test, I wonder if that is really relevant anyway.
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: Hi Michael! On 12/10/20 8:42 PM, Michael Biebl wrote: Testsuite summary for systemd-bootchart 233 # TOTAL: 1 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 Did the test machine you used actually have that many cores? No idea
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Hi Michael! On 12/10/20 8:42 PM, Michael Biebl wrote: > > Testsuite summary for systemd-bootchart 233 > > # TOTAL: 1 > # PASS: 1 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 0 > # XPASS: 0 > # ERROR: 0 > Did the test machine you used actually have that many cores? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#954270: marked as pending in kmc
Control: tag -1 pending Hello, Bug #954270 in kmc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/kmc/-/commit/8e0202a8386094935f162aa9472b6e743dd858a0 New upstream version closes: #954270 (this message was generated automatically) -- Greetings https://bugs.debian.org/954270
Processed: Bug#954270 marked as pending in kmc
Processing control commands: > tag -1 pending Bug #954270 [src:kmc] kmc: autopgktest times out on multimulticore hosts Added tag(s) pending. -- 954270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#935674: marked as done (librust-blake2-rfc+clippy-dev/amd64 unsatisfiable Depends: librust-clippy-0.0.41+default-dev)
Your message dated Thu, 10 Dec 2020 21:04:01 + with message-id and subject line Bug#935674: fixed in rust-blake2-rfc 0.2.18-3 has caused the Debian Bug report #935674, regarding librust-blake2-rfc+clippy-dev/amd64 unsatisfiable Depends: librust-clippy-0.0.41+default-dev 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.) -- 935674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-blake2-rfc Version: 0.2.18-2 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu eoan The rust-blake2-rfc package generates a binary package that appears to depend on rust-clippy, but there is no rust-clippy package in the archive (or in the new queue). librust-blake2-rfc+clippy-dev/amd64 unsatisfiable Depends: librust-clippy-0.0.41+default-dev -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: rust-blake2-rfc Source-Version: 0.2.18-3 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of rust-blake2-rfc, 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 935...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated rust-blake2-rfc 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: Thu, 10 Dec 2020 21:16:33 +0100 Source: rust-blake2-rfc Architecture: source Version: 0.2.18-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Sylvestre Ledru Closes: 935674 Changes: rust-blake2-rfc (0.2.18-3) unstable; urgency=medium . * Crappy upload by hand. Seems that the tarball cannot be used by debcargo * Team upload. * Package blake2-rfc 0.2.18 from crates.io using debcargo 2.4.3 * Remove the optional clippy dependency (closes: #935674). Checksums-Sha1: 638ab1c82fdcb770176ce80084460db0f140e5da 2194 rust-blake2-rfc_0.2.18-3.dsc 8a821e83188388da966e90cdb5f3f632fe2f9e9c 3068 rust-blake2-rfc_0.2.18-3.debian.tar.xz db2e059b3ff877466adc57f333932c9230a36c59 7471 rust-blake2-rfc_0.2.18-3_amd64.buildinfo Checksums-Sha256: c8ca7a1221d67aa21ef55d004052fcf5b7342fd16ca9f03aa5c46472339ce2db 2194 rust-blake2-rfc_0.2.18-3.dsc 1e532cd3ae4c82b3debbca635546388eb7344a2c443662d43945c66eb9b9c227 3068 rust-blake2-rfc_0.2.18-3.debian.tar.xz 2af4026eaeb493d3bba2fbde0a2bb5a884093cefb3f7b0f021f3089826f9bb0a 7471 rust-blake2-rfc_0.2.18-3_amd64.buildinfo Files: 609ae7734ac58c5ac7f16a5e8ea24b08 2194 rust optional rust-blake2-rfc_0.2.18-3.dsc b9f754dabf3f18ec4906f17c01953897 3068 rust optional rust-blake2-rfc_0.2.18-3.debian.tar.xz 876345f40bca5840889d7ca6ef8c0ea3 7471 rust optional rust-blake2-rfc_0.2.18-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl/SisAACgkQfmUo2nUv G+GR6Q/+N+484a8yBvg93YdAf5l/+5z8qH4qdAvqUtpmwVY9RVXuSVC4BqOyBqx3 WZ4j1eXVmJa+3wSJ8I1NPIGlZopdaU++bck1BYxiSj/ShrmhUNga0z1bc0Mk4IuB 3a4hNlThTILt65iESSFOo5P8vGQmZHrgihJtyVXLtvdiL5OdKohfz6+IqySJ7KrC iOmW21LCESxjJFW7foBcQzk3CbjHsnCFFwJFrORgrs4vVscTwtic2icvphKVHD5Q cJ2gLTrbFgIPQJO/PlPFVv43F2SJX/F1z+r9XDKCk8j/4BYSlzGPgBipIfdvoTqz IHFeWDrpWr5Thnp1bX/90DsSklumonV/SVcaNlDHxNCgZhQNqQvpIxOpfvxQtrsN 2yR//68k1DpGBxwcIulXg6k1s0oMmAO9vhYxaPY/PAizjm+PF3LxlzeE16Q1mTdZ JJVPxRXoRzGrk9sJD1Fz4/q/RIAOOfE//Czm80RtthGpCkirbalg83vpQNDpOwn8 YijWyOvHxoGo3sJv+h941pkuK8DEFt96Bge0aXU3sfGjcAMtUJAC9Z+a89hyqmYn umZden9jnDN9pXVrE4eI+TPpnwXf8tYBZnuBtaTCpOfuT21Egz02H584kRM3gZJt 8vmicLDY2uyTun5BHV/zectinq4NfHotVLFbYeLG5Al11sORLQw= =tUKk -END PGP SIGNATURE End Message ---
Bug#975737: marked as done (src:bluebird-gtk-theme: fails to migrate to testing for too long: maintainer built arch:all binary)
Your message dated Thu, 10 Dec 2020 20:48:26 + with message-id and subject line Bug#975737: fixed in bluebird-gtk-theme 1.3-2.1 has caused the Debian Bug report #975737, regarding src:bluebird-gtk-theme: fails to migrate to testing for too long: maintainer built arch:all binary 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.) -- 975737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bluebird-gtk-theme Version: 1.3-1 Severity: serious Control: close -1 1.3-2 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:bluebird-gtk-theme in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=bluebird-gtk-theme signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: bluebird-gtk-theme Source-Version: 1.3-2.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of bluebird-gtk-theme, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated bluebird-gtk-theme 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: Wed, 25 Nov 2020 20:58:20 +0100 Source: bluebird-gtk-theme Architecture: source Version: 1.3-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Desktop Theme Team Changed-By: Paul Gevers Closes: 975737 Changes: bluebird-gtk-theme (1.3-2.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #975737) Checksums-Sha1: a190f0fd6b7c98ae92ead010e299b5caa60fa542 1867 bluebird-gtk-theme_1.3-2.1.dsc 4a843ffd160ef834f8d679ea5ff30eae77c633fb 46740 bluebird-gtk-theme_1.3-2.1.debian.tar.xz Checksums-Sha256: 13809a2227d8f38dbd775a0cd0d3292f0042dc9bcb3d0971ad420bca22bd31d6 1867 bluebird-gtk-theme_1.3-2.1.dsc 0015a46aafac742653c72dd1baecf10cd0ca5500036b308a6f31526cb767f3c5 46740 bluebird-gtk-theme_1.3-2.1.debian.tar.xz Files: 414a6ac762783146b4e9d7632c6943f9 1867 x11 optional bluebird-gtk-theme_1.3-2.1.dsc dec3663a2c27742051453ceaa33c6188 46740 x11 optional bluebird-gtk-theme_1.3-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl++t3cACgkQnFyZ6wW9 dQosfAf8C9Oxl1aedp/yqKE7YVX4KTdJPVzpbZSXm3RphWTQ/RVnTsPPfrnKaZx8 NeC0GaDUbvkspu19JqrnMQexnY7n4yU/9VX8sktUk/T4oJRswP5MTD3RV7klKlQe o18bnSY7KLk4b5oWAE5VM6TaPaQaihk1sllMqNNtF1AcETnPYBgk4bP4/0aT7fmM
Processed: Re: Bug#977083: pristine-tar: fails to checkout when there are multiple source tarballs
Processing control commands: > reassign -1 git-buildpackage Bug #977083 [pristine-tar,git-buildpackage,devscripts] pristine-tar: fails to checkout when there are multiple source tarballs Bug reassigned from package 'pristine-tar,git-buildpackage,devscripts' to 'git-buildpackage'. No longer marked as found in versions git-buildpackage/0.9.20, pristine-tar/1.49, and devscripts/2.20.5. Ignoring request to alter fixed versions of bug #977083 to the same values previously set > forcemerge 917789 -1 Bug #917789 [git-buildpackage] Wrong tarball id (pristine-tar) when import-orig with --components Bug #977083 [git-buildpackage] pristine-tar: fails to checkout when there are multiple source tarballs Severity set to 'important' from 'serious' Marked as found in versions git-buildpackage/0.9.13. Merged 917789 977083 -- 917789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917789 977083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977083: pristine-tar: fails to checkout when there are multiple source tarballs
Control: reassign -1 git-buildpackage
Control: forcemerge 917789 -1
On Fri, Dec 11, 2020 at 01:39:35AM +0530, Pirate Praveen wrote:
> Package: pristine-tar,git-buildpackage,devscripts
> Control: found -1 pristine-tar/1.49
> Control: found -1 devscripts/2.20.5
> Control: found -1 git-buildpackage/0.9.20
> severity: serious
please, how could this be serios for either of them…
> I'm filing against all 3 possible packages which might have a bug here.
>
> Example package node-mermaid. It fails on all packages that uses multiple
> source tarballs. (gitlab is another example and many node packages use
> multiple source tarballs).
>
> These are usually created with gbp import-orig --pristine-tar
>
> We have to always fall back to 'apt source' command whcih makes pristine-tar
> useless in these situations.
>
> I think origtargz should try apt source when pristine-tar fails.
>
> I'm not sure if it fails only with tar.xz though.
>
> $ origtargz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-webpack-node-externals.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-stylis.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-strip-css-comments.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-slugify.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-scope-css.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-sanitize-url.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-khroma.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-is-regexp.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-escaper.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-entity-decode.tar.xz
> pristine-tar: successfully generated
> ./node-mermaid_8.7.0+ds+~cs27.17.17.orig-crypto-random-string.tar.xz
> fatal: ambiguous argument 'cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}':
> unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git [...] -- [...]'
> fatal: not a valid object name:
> cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}
> tar: This does not look like a tar archive
> tar: Exiting with failure status due to previous errors
> pristine-tar: command failed: git archive --format=tar
> cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4\^\{tree\} | (cd
> '/tmp/pristine-tar.x11yV6IWxf' && tar x)
See #917789 - that's what you are seeing.
gbp import-orig does extra things (that honestly I don't understand why
they are needed), and plain pristine-tar can't checkout a tarball, as
the tree id recorded are something that is build especially by gbp. You
need to use `gbp export-orig` to export such tarballs.
> $ pristine-tar checkout ../node-mermaid_8.7.0+ds+~cs27.17.17.orig.tar.xz
> fatal: ambiguous argument 'cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}':
> unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git [...] -- [...]'
> fatal: not a valid object name:
> cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}
> tar: This does not look like a tar archive
> tar: Exiting with failure status due to previous errors
> pristine-tar: command failed: git archive --format=tar
> cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4\^\{tree\} | (cd
> '/tmp/pristine-tar.JY3lejdcNL' && tar x)
If you wish to use `pristine-tar checkout` see #917789 that contains a
way to hack the .id files so that pristine-tar can do its work again
directly, without the help from gbp.
--
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#956767: marked as done (fusion-icon: Depends on deprecated libappindicator)
Your message dated Thu, 10 Dec 2020 20:36:02 + with message-id and subject line Bug#956767: fixed in fusion-icon 0.2.4-5 has caused the Debian Bug report #956767, regarding fusion-icon: Depends on deprecated libappindicator 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.) -- 956767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fusion-icon Version: 0.2.4-4 Tags: sid bullseye Severity: important Control: block 895037 by -1 User: pkg-ayatana-de...@lists.alioth.debian.org Usertags: ayatana-appindicator This package Depends on gir1.2-appindicator3-0.1, which is deprecated and unmaintained. The supported replacement appears to be gir1.2-ayatanaappindicator3-0.1. Please see #895037 and https://wiki.debian.org/Ayatana/IndicatorsTransition for more details of this deprecation. This bug might get escalated to 'serious' severity (making it release-critical) if the maintainers of the Ayatana stack are serious about getting libappindicator removed from Debian before bullseye. smcv --- End Message --- --- Begin Message --- Source: fusion-icon Source-Version: 0.2.4-5 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of fusion-icon, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated fusion-icon 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: Thu, 10 Dec 2020 21:23:31 +0100 Source: fusion-icon Binary: fusion-icon Architecture: source Version: 0.2.4-5 Distribution: unstable Urgency: medium Maintainer: Hypra Team Changed-By: Samuel Thibault Description: fusion-icon - tray icon to launch and manage Compiz Closes: 956767 Changes: fusion-icon (0.2.4-5) unstable; urgency=medium . [ Holger Paradies ] * rules: Enhance clean. . [ Samuel Thibault ] * watch: Generalize pattern. * control: Remove Cyril from uploaders. * patches/ayatanaappindicator: Use AyatanaAppIndicator instead of AppIndicator. * control: Replace gir1.2-appindicator3-0.1 build-dep with gir1.2-ayatanaappindicator3-0.1 (closes: #956767) . [ Debian Janitor ] * Use secure copyright file specification URI. * Bump debhelper from old 9 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Repository, Repository-Browse. . [ Samuel Thibault ] * watch: switch to gitlab * Update upstream URL * copyright: Fix license of appdata file. * control: Bump Standards-Version to 4.5.0 (no change). Checksums-Sha1: f43fef6b479c8fc354a2824384bb7812fefe755b 1960 fusion-icon_0.2.4-5.dsc de0329b8f6c590cf0c5487b8eb182959b9d600fd 8036 fusion-icon_0.2.4-5.debian.tar.xz Checksums-Sha256: 9e47e615c8d081f36b5e9e5708b892882ca26d73193bf29c8869384cd0950825 1960 fusion-icon_0.2.4-5.dsc 58d91888a3c1ac19f7c11c1b576ba18bc5c43308824bb845cce71ef0774c7c6d 8036 fusion-icon_0.2.4-5.debian.tar.xz Files: e4c9af203648273025c55ca51a8fa759 1960 x11 optional fusion-icon_0.2.4-5.dsc 003da09fff0c5b12b9dace9b84db2d96 8036 x11 optional fusion-icon_0.2.4-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEaBSUQh8zBGvGomB+DvXG2q7gS7IFAl/ShB4ACgkQDvXG2q7g S7KHRBAAtjawR2MP+HrXz01Z+VaruR64L6FZXCyS8SdOM96+RpLb3OjrwLti1ZuN EMAH9/swWi1Rdg/Hg4hs8Dz/UHpd91JEagCsFXRRNnHDMPH5UoZ7w3LBzdb+bHVm m6PY0lJaiXUkGaLG3NvaC5y2S/Mcj7QspexPBYu+vbNkC7QYeDqImtT8ZtCnG6SQ 1FZT5Dq+RgzGzho6b1X9VQFam80RnEuLjf5JdrHlI3FBN0G7hCMQzo9YelvmW5Jr QpSpGeGsPvZcJy/pzsvqRGeWElQ+O5Sns14tAe9W/Rbdhww0JcE3GL6FTHZSRncy 6aMRLHchjollwy6RclrE+oKfbfszmYm2d7JMQ1sWNuRIXi2pfi4UOLvdp/7qqh9e Jie/0ko+nM52x6R4NmbWl4ntP/MQT+3tpLYs1UzXhyGrjQC3LaxnC5JczgQkRVFx Uc2iUxpIhwxo51NGQ0Ys8r4NTthDZK1MGFH1E172hMjbsf+Dn9bwQsNTwhAXfNV6 BvjLSVQE/7ycf0eh8p0p+QNLP4BrKDmbpo9A7i43i+p/5rsHlxKVVxxMfQdSNhq+ A3gNxVc69Gqhr3gMNJajRv0+VAS4Sb+c8YYJAorws1r+EOfW3ikt0epnfSUny//9 P8H+wyVNmfL10170NvI5NEV+XT94++OjNHfOHurpr2SBiGifmQc= =4pgq -END PGP SIGNATURE End Message ---
Bug#977090: The 1.3.7a original tarball includes IETF RFCs documents
Source: proftpd-dfsg Version: 1.3.7a-1 Severity: serious Justification: Policy 2.2.1 As in subject, the RFCs need to be stripped before uploading a new upstream tarball, because not compliant to DFSG. That step was missed at the time of upload. -- Francesco P. Lovergine
Bug#977083: pristine-tar: fails to checkout when there are multiple source tarballs
Package: pristine-tar,git-buildpackage,devscripts
Control: found -1 pristine-tar/1.49
Control: found -1 devscripts/2.20.5
Control: found -1 git-buildpackage/0.9.20
severity: serious
I'm filing against all 3 possible packages which might have a bug here.
Example package node-mermaid. It fails on all packages that uses
multiple source tarballs. (gitlab is another example and many node
packages use multiple source tarballs).
These are usually created with gbp import-orig --pristine-tar
We have to always fall back to 'apt source' command whcih makes
pristine-tar useless in these situations.
I think origtargz should try apt source when pristine-tar fails.
I'm not sure if it fails only with tar.xz though.
$ origtargz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-webpack-node-externals.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-stylis.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-strip-css-comments.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-slugify.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-scope-css.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-sanitize-url.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-khroma.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-is-regexp.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-escaper.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-entity-decode.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-crypto-random-string.tar.xz
fatal: ambiguous argument
'cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}': unknown revision or
path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
fatal: not a valid object name:
cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
pristine-tar: command failed: git archive --format=tar
cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4\^\{tree\} | (cd
'/tmp/pristine-tar.x11yV6IWxf' && tar x)
$ pristine-tar list |grep 8.7.0+ds+~cs27.17.17.orig.tar.xz
node-mermaid_8.7.0+ds+~cs27.17.17.orig.tar.xz
$ pristine-tar checkout ../node-mermaid_8.7.0+ds+~cs27.17.17.orig.tar.xz
fatal: ambiguous argument
'cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}': unknown revision or
path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
fatal: not a valid object name:
cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
pristine-tar: command failed: git archive --format=tar
cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4\^\{tree\} | (cd
'/tmp/pristine-tar.JY3lejdcNL' && tar x)
Processed: pristine-tar: fails to checkout when there are multiple source tarballs
Processing control commands: > found -1 pristine-tar/1.49 Bug #977083 [pristine-tar,git-buildpackage,devscripts] pristine-tar: fails to checkout when there are multiple source tarballs Marked as found in versions pristine-tar/1.49. > found -1 devscripts/2.20.5 Bug #977083 [pristine-tar,git-buildpackage,devscripts] pristine-tar: fails to checkout when there are multiple source tarballs Marked as found in versions devscripts/2.20.5. > found -1 git-buildpackage/0.9.20 Bug #977083 [pristine-tar,git-buildpackage,devscripts] pristine-tar: fails to checkout when there are multiple source tarballs Marked as found in versions git-buildpackage/0.9.20. -- 977083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Am 10.12.20 um 20:18 schrieb John Paul Adrian Glaubitz: Hi Michael! On 12/10/20 7:53 PM, Michael Biebl wrote: Unfortunately, I can't reproduce the issue on a porter box (plummer). So I'm not sure if I can do something about it. It might be an issue with parallel jobs as Lucas built the package with make -j160 and some packages can't cope with that many parallel jobs. export DEB_BUILD_OPTIONS="parallel=160" ... dh_auto_test make -j160 check VERBOSE=1 make[1]: Entering directory '/home/biebl/sd/systemd-bootchart-233' Making check in . make --no-print-directory check-TESTS PASS: tests/run Testsuite summary for systemd-bootchart 233 # TOTAL: 1 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 make[1]: Leaving directory '/home/biebl/sd/systemd-bootchart-233' create-stamp debian/debhelper-build-stamp dh_prep debian/rules override_dh_auto_install make[1]: Entering directory '/home/biebl/sd/systemd-bootchart-233'
Processed: tagging 974546
Processing commands for cont...@bugs.debian.org: > tags 974546 + fixed-upstream Bug #974546 [src:klatexformula] klatexformula FTBFS: error: invalid use of incomplete type ‘class QPainterPath’ Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 974546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976838: marked as done (librocksdb.so: missing libdl linkage)
Your message dated Thu, 10 Dec 2020 19:33:54 + with message-id and subject line Bug#976838: fixed in rocksdb 6.11.4-3 has caused the Debian Bug report #976838, regarding librocksdb.so: missing libdl linkage 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.) -- 976838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librocksdb6.11 Version: 6.11.4-2 Severity: serious Tags: ftbfs Control: affects -1 src:balboa https://buildd.debian.org/status/fetch.php?pkg=rocksdb=amd64=6.11.4-2=1607384772=0 ... dpkg-shlibdeps: warning: symbol dlopen used by debian/librocksdb6.11/usr/lib/librocksdb.so.6.11.4 found in none of the libraries dpkg-shlibdeps: warning: symbol dlclose used by debian/librocksdb6.11/usr/lib/librocksdb.so.6.11.4 found in none of the libraries dpkg-shlibdeps: warning: symbol dlsym used by debian/librocksdb6.11/usr/lib/librocksdb.so.6.11.4 found in none of the libraries dpkg-shlibdeps: warning: symbol dlerror used by debian/librocksdb6.11/usr/lib/librocksdb.so.6.11.4 found in none of the libraries ... https://buildd.debian.org/status/fetch.php?pkg=balboa=amd64=2.0.0%2Bds-3%2Bb1=1607421100=0 ... gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -Ofast -flto -s -fwhole-program -fmax-errors=3 -D__GCC__ -std=c11 -Wall -Wextra -D_GNU_SOURCE -D__TRACE__ -DNDEBUG -I. -I../lib -DMPACK_HAS_CONFIG ../lib/trace.c ../lib/daemon.c ../lib/protocol.c ../lib/engine.c ../lib/mpack.c rocksdb-impl.c main.c -o build/balboa-rocksdb -Wl,-z,relro -Wl,-z,now -lrocksdb -pthread -latomic /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/librocksdb.so: undefined reference to `dlopen' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/librocksdb.so: undefined reference to `dlclose' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/librocksdb.so: undefined reference to `dlerror' /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../../lib/librocksdb.so: undefined reference to `dlsym' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:55: build/balboa-rocksdb] Error 1 --- End Message --- --- Begin Message --- Source: rocksdb Source-Version: 6.11.4-3 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of rocksdb, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated rocksdb 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: Thu, 10 Dec 2020 18:13:16 +0100 Source: rocksdb Architecture: source Version: 6.11.4-3 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 976838 Changes: rocksdb (6.11.4-3) unstable; urgency=medium . * Explicitly link shared library with dynamic linking library (closes: #976838). Checksums-Sha1: f35875a569245f3faba554f117c037b2e10a71cc 2229 rocksdb_6.11.4-3.dsc 16fcf56b6816ebb8257a6f06d7026ed7dfbca8ab 5896 rocksdb_6.11.4-3.debian.tar.xz Checksums-Sha256: 34efd88bdfc8c51e57bb304eb151f7b7b4e3be10618fd70f1760b5e1fe63a539 2229 rocksdb_6.11.4-3.dsc dfcb4288cc2693a360b425f7dffb4f13c07cecb536c78263fbb1be22b9ddd278 5896 rocksdb_6.11.4-3.debian.tar.xz Files: 479bcf2218024ad59567aaba23fcaedc 2229 database optional rocksdb_6.11.4-3.dsc 2266f7b3df1e64b30672b37639f6b7d1 5896 database optional rocksdb_6.11.4-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAl/SceIACgkQ3OMQ54ZM yL9kzw/+ILqb0UVrivqmrG7l+Jp0Gcd+EL7aw8CZC297YZ8myel/EzJQixTWGSwn 1S7lW/8eoNDOxyUtINsF0wVJ8jphrDf4vsmn69aL7lu8nci08g9X6atfjRxp+rc5 Emu1xlySgWeh2wwd2St2Zko7ObTkS1DJuTHp0Oj5cGinvNuU/hk9n+s1VkKCwkkZ h52PYhOq0aHllJIWVAL7k+1K/9y5swPeEizEygv7+GF1RUULo6cBhj39dfztOjNK Ryf9k/G9tLIQsjn/m7LpFuEeAP2EYsHlCwrIXFX4mME2KbcBb0ruwZvoatyt7oEC 9njtTVFALE4ly9mLiJqGiK5zw0jeVtkPB+r0F20Ku+KQbJ8DI9GZqRQnEiO13Xhc e1d0RsAX/tMGSNutW1NUV3j15zOrWWxkGaW+uz/AF3JyXl6RO9QtaBHiTm042A8W
Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Hi Simon, On Do 10 Dez 2020 16:08:00 CET, Simon McVittie wrote: Control: severity -1 serious On Thu, 10 Dec 2020 at 14:37:21 +, Mike Gabriel wrote: On Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote: > We're running into the freeze of bullseye soon. The first bug I checked > is still only severity important, so is it realistic to get this done > before bullseye release? [...] > If yes, action is needed, this isn't going to happen > magically. At the least raising the blocking bugs to severity serious. I'd suggest to raise severity of the still open bugs and get libappindicator kicked out before the bullseye release. The fixes are easy to be done. Maintainers can ping me if they have problems. Raising the blocking bugs to RC as requested. Thanks! I am not so experienced with effective mass manipulation of bugs, Simon, could you bump the severity of the respective bugs? There's no magic to it, you just send mail to the affected bug address(es) with appropriate Control commands. Ok. Yeah. I know the mail commands for debbugs, I simply wasn't sure how to obtain all those bug numbers. Thanks! Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpUn0gzV4q3s.pgp Description: Digitale PGP-Signatur
Processed: bug 975931 is forwarded to https://github.com/pocl/pocl/issues/889
Processing commands for cont...@bugs.debian.org: > forwarded 975931 https://github.com/pocl/pocl/issues/889 Bug #975931 [libllvm10,libllvm11] libgpuarray autopkgtest using pocl on armhf triggers segfault in LLVM Set Bug forwarded-to-address to 'https://github.com/pocl/pocl/issues/889'. > thanks Stopping processing here. Please contact me if you need assistance. -- 975931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Hi Michael! On 12/10/20 7:53 PM, Michael Biebl wrote: > Unfortunately, I can't reproduce the issue on a porter box (plummer). > So I'm not sure if I can do something about it. It might be an issue with parallel jobs as Lucas built the package with make -j160 and some packages can't cope with that many parallel jobs. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Processed: Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Processing control commands: > tags -1 + unreproducible Bug #976922 [src:systemd-bootchart] systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2 Added tag(s) unreproducible. -- 976922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Control: tags -1 + unreproducible Hello Lucas Am 09.12.20 um 09:42 schrieb Lucas Nussbaum: Source: systemd-bootchart Version: 233-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64. I'm marking this bug as severity:serious since your package currently has ppc64el binary packages in unstable (so this is a regression). Relevant part (hopefully): make[1]: Entering directory '/<>' Making check in . make --no-print-directory check-TESTS FAIL: tests/run = systemd-bootchart 233: ./test-suite.log = # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: tests/run === 1..3 Segmentation fault not ok 1 - ./systemd-bootchart -o /tmp/tmp.cNy0lVrga8 -n 2 -r Segmentation fault not ok 2 - ./systemd-bootchart -o /tmp/tmp.cNy0lVrga8 -n 10 -r Segmentation fault not ok 3 - ./systemd-bootchart -o /tmp/tmp.cNy0lVrga8 -n 10 -r -p # Failed 3 out of 3 tests FAIL tests/run (exit status: 1) Testsuite summary for systemd-bootchart 233 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to http://github.com/systemd/systemd-bootchart/issues make[4]: *** [Makefile:1515: test-suite.log] Error 1 make[3]: *** [Makefile:1623: check-TESTS] Error 2 make[2]: *** [Makefile:1859: check-am] Error 2 make[1]: *** [Makefile:1400: check-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2 Unfortunately, I can't reproduce the issue on a porter box (plummer). So I'm not sure if I can do something about it. CCing the powerpc porters mailing list. Maybe they can have a look. Regards, Michael
Bug#976764: marked as done (geophar needs source upload for Python 3.9 transition)
Your message dated Thu, 10 Dec 2020 18:18:25 + with message-id and subject line Bug#976764: fixed in geophar 18.08.6+dfsg1-6 has caused the Debian Bug report #976764, regarding geophar needs source upload for Python 3.9 transition 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.) -- 976764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: geophar Version: 18.08.6+dfsg1-5 Severity: serious Since binNMUs are not possible for binary-all packages, a source upload is needed for the Python 3.9 transition. --- End Message --- --- Begin Message --- Source: geophar Source-Version: 18.08.6+dfsg1-6 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of geophar, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated geophar 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: Thu, 10 Dec 2020 18:59:31 +0100 Source: geophar Architecture: source Version: 18.08.6+dfsg1-6 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 976764 976967 Changes: geophar (18.08.6+dfsg1-6) unstable; urgency=medium . * fixed many wrong syntaxes (replaced "is" by "=="). Closes: #976967 * new source upload; Closes: #976764 Checksums-Sha1: 7a85050914f08ad29ef97c80cf2012630cfd15dc 2127 geophar_18.08.6+dfsg1-6.dsc a8125de50629ff9e175aea09606a9277d7e18e53 17668 geophar_18.08.6+dfsg1-6.debian.tar.xz 5d265cbd8b135b98f5e967acc9f650e6008f5969 12408 geophar_18.08.6+dfsg1-6_source.buildinfo Checksums-Sha256: 1341287f4868b18bdacddfc05abf5f1fa5ab7d3c7e62ee2f927a597bd6fae5c8 2127 geophar_18.08.6+dfsg1-6.dsc 1e1f1ac20b0dde8a3a5004aeb6af132770b53b96b0dfc6a0b184d9502d5d8712 17668 geophar_18.08.6+dfsg1-6.debian.tar.xz ea56cfebf93cd995f1e0fd586f3d12f1db640d80d7651d6290c2232429dca9d5 12408 geophar_18.08.6+dfsg1-6_source.buildinfo Files: 8789b068a7923c118b8f64a1f75fa782 2127 math optional geophar_18.08.6+dfsg1-6.dsc fff770caeddbf3550c0f4ea54ceee74a 17668 math optional geophar_18.08.6+dfsg1-6.debian.tar.xz e75f5b98ec069a2a05b65eafd7f191c1 12408 math optional geophar_18.08.6+dfsg1-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl/SYpYUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmtug/9FBuWV/hvxKAyOJb4E0dm3Z7RvSPz SJsqgDtQVx4KrV805gzTaSscaBl15szcPlQ6leWgJ4wXKGKn4ZwFAnYyqIypvYr1 AXMsr3vq+BUiLT/vpsP7U1zrSrC5QbeRbp5h6WYwKKm9RNoYtrrMqTXrIFTOvnZQ l1NQHQq+CYt4SFpuS9ks71TqrkactuqCxPt56JrKB/i/3PXb0812SGJINFEQfSmD bmubgVvNS+PNANML4QkDcwlSHCHTHCaBcl3XY/dOmJalPihkbPUkVXCuuXHTSKTl QHa8/UzeW+ejMsh9ueBNdH8FbZEksvSsaTaVVwXxjNwtpgL3YfpWFFnlVQLO9umm lCTdQQfQNk+WxR+Irm1wASP9NlAZexh2rB6EM+7hW23VtH4OGe2NNwHna0WQ63NS cgQaOwqdO93mPjn3uTlWsk8Oxv1gweH5elAX+ja3DQ5MsZx9LOuZaktd+SBqhlqL vkGudqBuWZW2EHJR/q/x30msbyhn1mMRzLMpdMcu0lxe8xeQT83L8zGCpi77uzGo UnC+56iPgLwjGIpWUOl5qHPvFgkqmBsrkA2Iy5G+d23HPst0DDg0fn93JJX/QWUW M3d5NtlU5sIycMz3vIy3IXSdVace7i1aPp3j6lthvGOStn5k+lXi20jUmdev8zUO E9mbIdSrSCQRCVw= =7Baq -END PGP SIGNATURE End Message ---
Bug#954270: [Debian-med-packaging] Bug#954270: [RFS] kmc: arm64 autopkgtest time out
Hi Andreas, Hi Paul, Paul Gevers, on 2020-12-10 13:50:59 +0100: > On 10-12-2020 13:10, Andreas Tille wrote: > > My guess is that kmc was developed under and designed for amd64 and it > > runs there. That's explicitly the case for the latest upstream version > > which will not support any arm* out of the box (if I understand Étienne > > correctly). I do not see any need to stress test our hardware with > > some software that will be outdated soonish. I'm merging my changes for the kmc 3.1.1 amd64-only update; will push very soon. > I couldn't resist. I started it up and it hangs. > > Paul [...] > # In the end, default options should, ideally, work on any configuration. > echo 'Running kmc (default thread count)' > Running kmc (default thread count) > rm -f 1.kmc_suf 1.kmc_pre > kmc -ci1 -m1 -k28 $ORIGDIR/debian/tests/sample_6.fastq.gz 1 . > * Thank you very much for the full log! :) I was hoping to see it on the ci logs during my lunch hour, but as I understand now, it was not accessible from the web page (or rather well hidden). Looks like I either screwed my patch or the general issue is way more intricate than I first thought. Looks like I'll have to locate again that RoM removal procedure. Have a nice evening, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/1, please excuse my verbosity. signature.asc Description: PGP signature
Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue
On Thu, Dec 10, 2020 at 04:51:53PM +0100, Sven Mueller wrote: > Hi. > > I just re-ran tests after adding a build dependency on libgrpc-java and > that fixed the reported issue. Hi Sven, Would you mind sharing the build logs for the failed build? It's fine if you send them to me directly. I'm not able to reproduce the build failure locally in a clean sid chroot, and the build failure doesn't occur on the buildds [1], so I just want to make sure that we're addressing the right package and/or root cause. It feels like it might be a transitive dependency issue, like the one addressed in #975842 [2]. Thanks, tony [1] https://buildd.debian.org/status/package.php?p=google-oauth-client-java [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975842 signature.asc Description: PGP signature
Bug#977034: marked as done (libmaxminddb-dev: File conflict libmaxminddb-dev & libmaxminddb0)
Your message dated Thu, 10 Dec 2020 17:34:14 + with message-id and subject line Bug#977034: fixed in libmaxminddb 1.4.3-2 has caused the Debian Bug report #977034, regarding libmaxminddb-dev: File conflict libmaxminddb-dev & libmaxminddb0 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.) -- 977034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmaxminddb-dev Version: 1.3.2-1 Severity: serious Justification: Policy 5.6.10 Dear Maintainer, * What led up to the situation? Upgrade of package libmaxminddb-dev. apt-listchanges: Mailing root: apt-listchanges: changelogs for sid (Reading database ... 148796 files and directories currently installed.) Preparing to unpack .../libmaxminddb-dev_1.4.3-1_i386.deb ... Unpacking libmaxminddb-dev:i386 (1.4.3-1) over (1.3.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libmaxminddb-dev_1.4.3-1_i386.deb (--unpack): trying to overwrite '/usr/share/man/man3/libmaxminddb.3.gz', which is also in package libmaxminddb0:i386 1.3.2-1 If a file is moved from one package to another you need to declare a Breaks & Replaces relationship. Hilmar -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 5.9.0-4-686-pae (SMP w/2 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libmaxminddb-dev depends on: iu libmaxminddb0 1.4.3-1 libmaxminddb-dev recommends no packages. libmaxminddb-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libmaxminddb Source-Version: 1.4.3-2 Done: Sergio Durigan Junior We believe that the bug you reported is fixed in the latest version of libmaxminddb, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergio Durigan Junior (supplier of updated libmaxminddb 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: Thu, 10 Dec 2020 11:55:16 -0500 Source: libmaxminddb Architecture: source Version: 1.4.3-2 Distribution: unstable Urgency: medium Maintainer: Faidon Liambotis Changed-By: Sergio Durigan Junior Closes: 977034 Changes: libmaxminddb (1.4.3-2) unstable; urgency=medium . * d/control: Add Breaks+Replaces on libmaxminddb-dev. libmaxminddb-dev will Break+Replace libmaxminddb0 (<< 1.4.3-2), because of the move of libmaxminddb.3 to libmaxminddb-dev. (Closes: #977034) Checksums-Sha1: 77f9e4d0e30bf00caf9c57e18d7dcce4823813d4 2219 libmaxminddb_1.4.3-2.dsc 7ecfd257e0a65251a39e6da17a6487b6ceef3081 11504 libmaxminddb_1.4.3-2.debian.tar.xz f41ab5c7e008e2e8625876515653f9d1e9e8fea1 7222 libmaxminddb_1.4.3-2_amd64.buildinfo Checksums-Sha256: 464f53aba7eabf40b0c3277156c1f58f2ade14675539aafb1f3df718912e258b 2219 libmaxminddb_1.4.3-2.dsc dea00392ad95118055daff8ccfdbb576f3bbccdcc8a2515fc2ceb53c4eac9240 11504 libmaxminddb_1.4.3-2.debian.tar.xz 45ff9d7d9ada08f5c51121c51f5ff91f1f978f8d2401b8c3cd5cf6aa4b76aad7 7222 libmaxminddb_1.4.3-2_amd64.buildinfo Files: ef92cdc4c578e4506c985a304841e9ab 2219 net optional libmaxminddb_1.4.3-2.dsc 7a69e106403e634636f1dccb1a9cf3f3 11504 net optional libmaxminddb_1.4.3-2.debian.tar.xz 3300a3af55abd95777fbb4d242fb5b91 7222 net optional libmaxminddb_1.4.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEI3pUsQKHKL8A7zH00Ot2KGX8XjYFAl/SWFQUHHNlcmdpb2Rq QGRlYmlhbi5vcmcACgkQ0Ot2KGX8XjZqXQ//fOASSkL48jfdkeMdC7EutidGs4+p gQGrKIMuSWHwf8+hQBfCee3JWABiTEyQeD1udXITMu1Aasw2hY+DDwABGCwM1Uk2 V4Tsw5AVyK6U2CJQsC0Gma2Xna0o3TOsOIp5nG6y8oIvWMLTkBBUsdd9ayPtaHPw oir13cs4sRYUG9JlRoccWUaq2sZFiBfOOhH8ajferFcSRIWPuIx6Cbo+UuY7kqNG O2nm8ICb2+lSSU49Y8LHF2MeNU2Z9p2kOluq6e9u2pi4PO5OdWAZFYleVC4Fc055 woaFj8R+YQymTDnTRi8hWSjvj1GM/rNcQGmBcKcHMm0PB/V+wN4eNZ5Gf8bYhW8R jPj7otDnQNCN/z2xakZVHdSmGLbv5QQ6qi7LnzBrzdiFxwg+TwUruSu+80hRGX/g
Processed: [bts-link] source package src:frr
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:frr > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #972767 (http://bugs.debian.org/972767) > # Bug title: frr ftbfs with python3.9 > # * https://github.com/FRRouting/frr/pull/6598 > # * remote status changed: (?) -> closed > # * closed upstream > tags 972767 + fixed-upstream Bug #972767 [src:frr] frr ftbfs with python3.9 Added tag(s) fixed-upstream. > usertags 972767 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 972767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Error importing plugin "pytest_tornasync": No module named 'pytest_tornasync'
Processing control commands: > severity -1 important Bug #976995 [python3-pytest] Error importing plugin "pytest_tornasync": No module named 'pytest_tornasync' Severity set to 'important' from 'grave' -- 976995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976995: Error importing plugin "pytest_tornasync": No module named 'pytest_tornasync'
Control: severity -1 important Tags: -1 unreproducible Hi Julien, I'm downgrading because the pytest currently does work with hundreds of packages, implying that it cannot be (generally) unusable. On Wed, 09 Dec 2020 21:08:39 +0100 Julien Puydt wrote: > I was trying to update another package in the Debian Python Team, and > couldn't understand why its testsuite failed with the above error. > > After some failed poking around, I put the following in a file named > test_foo.py: > > def test_foo(): > pass This works fine in a clean environment on my end. > PS: the full trace is: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", > line 572, in import_plugin > __import__(importspec) > ModuleNotFoundError: No module named 'pytest_tornasync' That's looking for the tornasync plugin [1], which is not available in Debian. I assume that your source package needs this in one way or another, and it is failing because of this. Could you try to run your test_foo.py above in some other directory? If it works, I recommend checking the upstream source for tornasync, and which part of the tests require it. [1] https://pypi.org/project/pytest-tornasync/ Best, Christian
Bug#976189: marked as done (Catfish not starting anymore after installation of Python 3.9)
Your message dated Thu, 10 Dec 2020 17:18:21 +
with message-id
and subject line Bug#976189: fixed in catfish 1.4.13-2
has caused the Debian Bug report #976189,
regarding Catfish not starting anymore after installation of Python 3.9
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.)
--
976189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: catfish
X-Debbugs-Cc: nie...@posteo.de
Version: 1.4.13-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
upgrading Python to 3.9
* What was the outcome of this action?
Catfish doesn't start anymore:
Traceback (most recent call last):
File "/usr/bin/catfish", line 44, in
catfish.main()
File "/usr/lib/python3/dist-packages/catfish/__init__.py", line 78, in
main
window = CatfishWindow.CatfishWindow()
File "/usr/lib/python3/dist-packages/catfish_lib/Window.py", line 171,
in __new__
builder = get_builder(__builder__['ui_file'])
File "/usr/lib/python3/dist-packages/catfish_lib/helpers.py", line
109, in get_builder
builder.add_from_file(ui_filename)
File "/usr/lib/python3/dist-packages/catfish_lib/Builder.py", line 87,
in add_from_file
ele_widgets = tree.getiterator("object")
AttributeError: 'ElementTree' object has no attribute 'getiterator'
--- End Message ---
--- Begin Message ---
Source: catfish
Source-Version: 1.4.13-2
Done: =?utf-8?q?Andreas_R=C3=B6nnquist?=
We believe that the bug you reported is fixed in the latest version of
catfish, 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 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Rönnquist (supplier of updated catfish 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: Thu, 10 Dec 2020 17:48:31 +0100
Source: catfish
Architecture: source
Version: 1.4.13-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Rönnquist
Closes: 976189
Changes:
catfish (1.4.13-2) unstable; urgency=medium
.
[ Andreas Rönnquist ]
* Team upload
* Add patch to replace tree.getiterator with tree.iter
Fixes compatibility with Python 3.9 (Closes: #976189)
* Use watch file standard version 4
* Update upstream metadata
* Update Standards Version to 4.5.1 (No changes required)
.
[ Ondřej Nový ]
* d/control: Update Maintainer field with new Debian Python Team
contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
.
[ Debian Janitor ]
* Update standards version to 4.5.0, no changes needed.
Checksums-Sha1:
09f6f90c2777fa606ce012755dac15ee07f04994 2006 catfish_1.4.13-2.dsc
149c4d0b1da7ab85cb075f75b3c0e00ebee77a6f 6404 catfish_1.4.13-2.debian.tar.xz
601f6af4a3b26110c9715a014eb6e4b718a540bf 7853 catfish_1.4.13-2_source.buildinfo
Checksums-Sha256:
4412aab37d2b0018b5954ffb6e37e3548babf4a3f01621b025ac0326088aa71d 2006
catfish_1.4.13-2.dsc
9295e18c5a19462bfa960d313be60dadc2a02a408c2df212f5377c50f6fceeef 6404
catfish_1.4.13-2.debian.tar.xz
7b7e03480a1860c03995e489b0aa0d70d2249ca57d74e9626c3f01e54ccc4800 7853
catfish_1.4.13-2_source.buildinfo
Files:
f0495fa8e6dcc849d8ae9de2578c61e8 2006 utils optional catfish_1.4.13-2.dsc
d6d6cd82cf8eba7977d14f9297a335e0 6404 utils optional
catfish_1.4.13-2.debian.tar.xz
755f9cf5ad700edec1afbb1f4376303e 7853 utils optional
catfish_1.4.13-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE2zBuSxD/2Y7021XXGUtjGrLaKIgFAl/SUqoRHGd1c25hbkBn
dXNuYW4uc2UACgkQGUtjGrLaKIhVcQ//cxSoKvRDs2/LAhx02Z/l/Gu28wp5gRxR
f2qmCpplt/phaG9TMdK/cOZ8OUlHtlGukDEYfxIghHcMldPABH1YEnaNg/ozc2u3
BARw1tJL+N+041WLbz9aK5agjZwEmMIE2MB08rgyqkN4T7Vl8GhCtcqiHT8JqQM3
OQd0zxQdy8i5+5J0fvN0vtfLn5adCHOGC1Ie/GHbH9tPDF/GfxmaCEdtDaS/qPrP
zvg8kigEElBdRjMt4H+f7naK44z5vDJQe3n7paBgoXgOqEMSQacT7VEgJ0sDWvfa
PeAzw6rsKjYwk7b5/D9x06ehG5LsAJR7CfsiLRTpZJczlho/4c88SDH4K1We/9Vh
dXY/QZlN39PKhy5dxhoDuNvL9h9QzWCI5pKDvUM4xTNTBTpXJ7BF4IW/UXRPlL+5
lOXvCzLUdTUH5Bbc6QyYMrP775GVZpL14Y1aA7j7yyfLcAqGy0TByiP2sa5hqZ2h
Processed: [bts-link] source package src:nipy
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:nipy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #959138 (http://bugs.debian.org/959138) > # Bug title: numpy breaks nipy autopkgtest: No module named > 'numpy.testing.decorators' > # * https://github.com/nipy/nipy/issues/466 > # * remote status changed: closed -> open > # * reopen upstream > tags 959138 - fixed-upstream Bug #959138 [src:nipy] numpy breaks nipy autopkgtest: No module named 'numpy.testing.decorators' Removed tag(s) fixed-upstream. > usertags 959138 - status-closed Usertags were: status-closed. Usertags are now: . > usertags 959138 + status-open There were no usertags set. Usertags are now: status-open. > thanks Stopping processing here. Please contact me if you need assistance. -- 959138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)
Hi Mathieu, On Thu, Dec 10, 2020 at 11:10:17AM +0100, Mathieu Malaterre wrote: > "make -j160" > > that would be my guess :) This sounds pretty likely, thought. Thanks for the hint. > remove parallel from the dh option, and try again (fixes symptoms) To cure the real issue rather than the symptoms: Is there any way to make sure flex will be called first before the build starts? My knowledge in automake is pretty limited and I have no idea how to express this. Kind regards and thanks for the hint in any case Andreas. -- http://fam-tille.de
Bug#977039: marked as done (pygrib: binary-any FTBFS)
Your message dated Thu, 10 Dec 2020 17:03:44 +
with message-id
and subject line Bug#977039: fixed in pygrib 2.1.1-2
has caused the Debian Bug report #977039,
regarding pygrib: binary-any 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.)
--
977039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygrib
Version: 2.1.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=pygrib=sid
...
debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
find debian/python3-grib -true -print0 2>/dev/null | xargs -0r chown
--no-dereference 0:0
find debian/python3-grib ! -type l -a -true -a -true -print0
2>/dev/null | xargs -0r chmod go=rX,u+rw,a-s
find debian/python3-grib/usr/share/doc -type f -a -true -a ! -regex
'debian/python3-grib/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null |
xargs -0r chmod 0644
find debian/python3-grib/usr/share/doc -type d -a -true -a -true
-print0 2>/dev/null | xargs -0r chmod 0755
find debian/python3-grib/usr/share/man -type f -a -true -a -true
-print0 2>/dev/null | xargs -0r chmod 0644
find debian/python3-grib -type f \( -name '*.so.*' -o -name '*.so' -o
-name '*.la' -o -name '*.a' -o -name '*.js' -o -name '*.css' -o -name '*.scss'
-o -name '*.sass' -o -name '*.jpeg' -o -name '*.jpg' -o -name '*.png' -o -name
'*.gif' -o -name '*.cmxs' -o -name '*.node' \) -a -true -a -true -print0
2>/dev/null | xargs -0r chmod 0644
find debian/python3-grib/usr/bin -type f -a -true -a -true -print0
2>/dev/null | xargs -0r chmod a+x
find debian/python3-grib/usr/lib -type f -name '*.ali' -a -true -a
-true -print0 2>/dev/null | xargs -0r chmod uga-w
find debian/python-grib-doc -name '*.grb' -exec chmod -x {} \;
find: ‘debian/python-grib-doc’: No such file or directory
make[1]: *** [debian/rules:31: override_dh_fixperms] Error 1
--- End Message ---
--- Begin Message ---
Source: pygrib
Source-Version: 2.1.1-2
Done: Alastair McKinstry
We believe that the bug you reported is fixed in the latest version of
pygrib, 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 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry (supplier of updated pygrib 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: Thu, 10 Dec 2020 15:32:33 +
Source: pygrib
Architecture: source
Version: 2.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry
Changed-By: Alastair McKinstry
Closes: 977039
Changes:
pygrib (2.1.1-2) unstable; urgency=medium
.
* Only run fixperms on binary builds. Closes: #977039
Checksums-Sha1:
08ff6bbfdf5011e3e3bb7c1acd5914c8d5082578 2130 pygrib_2.1.1-2.dsc
00e189598b90d395b3209cde1b8573ece367bf27 11104 pygrib_2.1.1-2.debian.tar.xz
Checksums-Sha256:
ac708925c08fdf3f36fdfadbb2330ab1849f6bc2b78200e99f25f67fe6ed8804 2130
pygrib_2.1.1-2.dsc
2564f16daa937767b548690a105aeaaf3fe0d5f16498308c42edc8174bf28259 11104
pygrib_2.1.1-2.debian.tar.xz
Files:
a6f1b3665e3d4e9de7d8c6120579138e 2130 python optional pygrib_2.1.1-2.dsc
5f59f64fcf76707907fa56e27255ff40 11104 python optional
pygrib_2.1.1-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl/SUMkACgkQy+a7Tl2a
06UWow//YNzctDymyOjH/E1mVMKhFFuVAP8hjXAig54+/VnYTEVZ3j6xSyfzbi+Y
5OKruYR/q90RH+/7OceHf83UfVWcCPKQV2nOUrlcVxvUQdGmrxV9me2NqkQGZOyY
1XMfuixIutbqHgVS9UilggZdsnXhYvwj2d5EzhU1EuTMJMj35GN5Fa9Wh9Is/TI1
QZusBc2azpHHwpK5EujsrFxl1DTcnQQ3MrpDR7Ww0M8yXmE2ALnBrsiTcEDeIrIi
KcDZ7HK5VGr+AaUDtqGFjdlVb4/RgXojKoP72KpZQIuhV+tYlwCG1kztLTKL78Q8
N49BJroACK/ENJKzbUj1EvPP+ZVNQcP1InKKZVPjCcBgGSi3wLvPKrIwar6NyxXB
Ir71eFHkoUTYZdidoLRu3ju+YDED2iKNHfgLqL5kf+aGFtdbva3s5QzwlHE2Djo+
t3E+Q6Ovv9Jfgt1zqCmNBiqsmal0lzh6GGm69gVpdSgFqUvfry9kEggG3U+MD5oF
07vD41kQdRjJv0Ng01aoGzxTOwQ0LtsM9wv+rFljam2VoKabQj4sxA3tSWRCFo19
uTS8xBjKvfcAXoCHS3uHbBr9Z1EaKFNbPL0YJhD3x6EQtFR1yuKuzPRJzFa3pTEK
ibWfdoDUb0KG2uP9ss1PH/dp93qCVN0y4NZ+WUXRg9T85IuOu98=
=cfJZ
-END PGP SIGNATURE End Message ---
Bug#955552: marked as done (xpdf: FTBFS with poppler 0.85.0: error: 'getModRegion' was not declared in this scope)
Your message dated Thu, 10 Dec 2020 17:04:00 + with message-id and subject line Bug#92: fixed in xpdf 3.04-14 has caused the Debian Bug report #92, regarding xpdf: FTBFS with poppler 0.85.0: error: 'getModRegion' was not declared in this scope 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.) -- 92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xpdf Version: 3.04-13exp3 Severity: serious Tags: ftbfs sid bullseye experimental Justification: fails to build from source (but built successfully in the past) Hi, xpdf/experimental FTBFS against libpoppler-dev/experimental (0.85.0-1): debian/rules override_dh_auto_build make[1]: Entering directory '/build/xpdf-3.04' x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/build/xpdf-3.04=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo -I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args -Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H -DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\" -c -o build/CoreOutputDev.o build/CoreOutputDev.cc build/CoreOutputDev.cc: In member function 'virtual void CoreOutputDev::dump()': build/CoreOutputDev.cc:50:5: error: 'getModRegion' was not declared in this scope 50 | getModRegion(, , , ); | ^~~~ compilation terminated due to -Wfatal-errors. make[1]: *** [: build/CoreOutputDev.o] Error 1 make[1]: Leaving directory '/build/xpdf-3.04' make: *** [debian/rules:50: build] Error 2 The version in sid (3.04-13) has the same problem. Andreas xpdf_3.04-13exp3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: xpdf Source-Version: 3.04-14 Done: Florian Schlichting We believe that the bug you reported is fixed in the latest version of xpdf, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Schlichting (supplier of updated xpdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 11 Dec 2020 00:43:16 +0800 Source: xpdf Architecture: source Version: 3.04-14 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Florian Schlichting Closes: 901541 945188 92 961597 973573 Changes: xpdf (3.04-14) unstable; urgency=medium . * QA upload * Add patches from xpopple for compatibility with poppler 20.09.0 (closes: #92) * Fix memory leaks, patch from Bernhard Übelacker (closes: #945188) * Fix tempfile warning, thanks Vincent Lefevre (closes: #961597) * Support more MIME types in xpdf.desktop (closes: #901541) * Fix typo in manpage (closes: #973573) Checksums-Sha1: 7abbc2ded48764025dc8b67c1123a68df9d9db5c 1870 xpdf_3.04-14.dsc 350bcbab960bf05f07f12311b853185bad67bc81 120788 xpdf_3.04-14.debian.tar.xz 853b21a68fc2b7f908e544904a8bd84a546fa856 8006 xpdf_3.04-14_amd64.buildinfo Checksums-Sha256: c84ce6cf5feeeb86c630e8ccceb03b5c9a4dc19d0cdde042e31adb8fb1182563 1870 xpdf_3.04-14.dsc 90642076892f0075401e32b57deddf7ec6058b72e4e82cf52660e677d0a187cd 120788 xpdf_3.04-14.debian.tar.xz c60fc3b394118bbaf3be57a65271ac44aa4e46c77628a158ab62cb405d9b56ba 8006 xpdf_3.04-14_amd64.buildinfo Files: 8c9840624a3668274eccb3bfd71a8b8d 1870 text optional xpdf_3.04-14.dsc e6a4c91a2f97e25e0ed70473fc025e49 120788 text optional xpdf_3.04-14.debian.tar.xz f757666e719cd31c19f9a67446d64ccd 8006 text optional xpdf_3.04-14_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEMLI8i05qOwnqprZSEpc7bnLcB7UFAl/SURcACgkQEpc7bnLc B7WvNw//QywamqN1FA+NLAPHLvH0PF9uYSsNcBqmzia6+PE/6/MQ6H2+5bjo+DPn GzKC6PKqmIfXBniWEdd5ruh2SpVeExLombA548t8VY1HYUzTpHtRQXL21hufNMQY 2s3qwjnRSwvG2x032EXT5Tb2TeKQI5K99rm0BYcpDdOkFxKlE3ZFOHA5yyEWqB62 rntlOxuAGwqoyu33MSxDJUJJFyAdxoS6/tEgpDJs+v3pTCnFs4kocMpUXdJ3A/Sw D//jeOGluEtqZi7c4MbwdkigNYa7yNpylicm3JuSUiD8sFPK24nAgZvKwkHoN6Ml 9FDfh+nPbVU2ecGZLSsx8GkSwErzvtADsc0NUvmTVuoiUr87LPDz1q/LtBy6mTSK hSYbzShiIlx0EZ4Ic3BAF4pErZmo4kYear4dTKlAzpfXDNvMVCORxEg+CS8ahEBU
Processed: Bug#955552 marked as pending in xpdf
Processing control commands: > tag -1 pending Bug #92 [src:xpdf] xpdf: FTBFS with poppler 0.85.0: error: 'getModRegion' was not declared in this scope Added tag(s) pending. -- 92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955552: marked as pending in xpdf
Control: tag -1 pending Hello, Bug #92 in xpdf reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/xpdf/-/commit/215057b1f8088fe263053f774b1013f048be50f6 Add patches from xpopple for compatibility with poppler 20.09.0 (closes: #92) See http://offog.org/code/xpopple/ - no end of thanks to Adam Sampson! (this message was generated automatically) -- Greetings https://bugs.debian.org/92
Bug#976975: marked as done (vtk9 FTBFS with freetype 2.10.4)
Your message dated Thu, 10 Dec 2020 16:49:05 + with message-id and subject line Bug#976975: fixed in vtk9 9.0.1+dfsg1-3 has caused the Debian Bug report #976975, regarding vtk9 FTBFS with freetype 2.10.4 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.) -- 976975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vtk9 Version: 9.0.1+dfsg1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=vtk9 ... cd /<>/debian/build/Rendering/FreeType && /usr/bin/mpic++ -DRenderingFreeType_EXPORTS -DVTK_IN_VTK -I/<>/debian/build/Rendering/FreeType -I/<>/Rendering/FreeType -I/<>/debian/build/Common/Core -I/<>/Common/Core -I/<>/debian/build/Common/ExecutionModel -I/<>/Common/ExecutionModel -I/<>/debian/build/Common/DataModel -I/<>/Common/DataModel -I/<>/debian/build/Common/Math -I/<>/Common/Math -I/<>/debian/build/Common/Transforms -I/<>/Common/Transforms -I/<>/debian/build/Rendering/Core -I/<>/Rendering/Core -I/<>/debian/build/Filters/Core -I/<>/Filters/Core -I/<>/debian/build/Common/Misc -I/<>/Common/Misc -I/<>/debian/build/Filters/General -I/<>/Filters/General -isystem /<>/debian/build/Utilities/KWIML -isystem /<>/Utilities/KWIML -isystem /<>/debian/build/Utilities/KWSys -isystem /<>/Utilities/KWSys -isystem /<>/debian/build/ThirdParty/freetype -isystem /<>/ThirdParty/freetype -isystem /usr/include/freetype2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -Wnon-virtual-dtor -Wno-long-long -ansi -Wcast-align -Wchar-subscripts -Wall -Wextra -Wpointer-arith -Wformat-security -Woverloaded-virtual -Wshadow -Wunused-parameter -fno-check-new -fno-common -Werror=undef -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=c++11 -o CMakeFiles/RenderingFreeType.dir/vtkFreeTypeTools.cxx.o -c /<>/Rendering/FreeType/vtkFreeTypeTools.cxx /<>/Rendering/FreeType/vtkFreeTypeTools.cxx:382:1: error: expected constructor, destructor, or type conversion before ‘vtkFreeTypeToolsFaceRequester’ 382 | vtkFreeTypeToolsFaceRequester( | ^ /<>/Rendering/FreeType/vtkFreeTypeTools.cxx: In member function ‘virtual FT_Error vtkFreeTypeTools::CreateFTCManager()’: /<>/Rendering/FreeType/vtkFreeTypeTools.cxx:1154:61: error: ‘vtkFreeTypeToolsFaceRequester’ was not declared in this scope; did you mean ‘vtkFreeTypeToolsCleanupCounter’? 1154 | this->MaximumNumberOfSizes, this->MaximumNumberOfBytes, vtkFreeTypeToolsFaceRequester, | ^ | vtkFreeTypeToolsCleanupCounter make[4]: *** [Rendering/FreeType/CMakeFiles/RenderingFreeType.dir/build.make:267: Rendering/FreeType/CMakeFiles/RenderingFreeType.dir/vtkFreeTypeTools.cxx.o] Error 1 --- End Message --- --- Begin Message --- Source: vtk9 Source-Version: 9.0.1+dfsg1-3 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of vtk9, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated vtk9 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: Thu, 10 Dec 2020 17:33:59 +0100 Source: vtk9 Architecture: source Version: 9.0.1+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Anton Gladky Closes: 976127 976975 Changes: vtk9 (9.0.1+dfsg1-3) unstable; urgency=medium . [ Adrian Bunk ] * [52af841] Revert "Link against latomic" * [381ea98] Link with libatomic on archtectures that need it . [ Anton Gladky ] * [a983346] 80_allow_gles_platforms.patch. * [e79137e] Fix FTBFS against freetype 2.10.4. (Closes: #976975) * [d7ecb86] Add python3-vtk9 as Breaks+Replaces: python3-paraview. (Closes: #976127) * [19fe54e] Update changelog. Checksums-Sha1: fa8c4f3602ca85bc4430bfe306a32d980cb7b30b 3507
Bug#976127: marked as done (python3-vtk9 needs Breaks+Replaces: python3-paraview (<< 5.9.0~rc1-1~))
Your message dated Thu, 10 Dec 2020 16:49:05 + with message-id and subject line Bug#976127: fixed in vtk9 9.0.1+dfsg1-3 has caused the Debian Bug report #976127, regarding python3-vtk9 needs Breaks+Replaces: python3-paraview (<< 5.9.0~rc1-1~) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-vtk9 Version: 9.0.1+dfsg1-2 Severity: normal During upgrade on unstable from paraview 5.7 and python3-vtk7 to the new paraview 5.9 and python3-vtk9, I got this file conflict error: Unpacking python3-vtk9 (9.0.1+dfsg1-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-vtk9_9.0.1+dfsg1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/vtk.py', which is also in package python3-paraview 5.7.0-5+b3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) This is the VTK9 counterpart to Bug#975004 filed against python3-paraview. I think python3-vtk9 also needs a breaks/replaces against python3-paraview 5.7 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-vtk9 depends on: ii libc6 2.31-4 ii libgcc-s1 10.2.0-19 ii libopenmpi3 4.0.5-7 ii libpython3.93.9.1~rc1-2 ii libstdc++6 10.2.0-19 ii libvtk9 9.0.1+dfsg1-2 ii libvtk9-qt 9.0.1+dfsg1-2 ii python3 3.9.0-3 ii python3-mpi4py 3.0.3-7 python3-vtk9 recommends no packages. Versions of packages python3-vtk9 suggests: pn mayavi2 pn vtk9-doc pn vtk9-examples -- no debconf information --- End Message --- --- Begin Message --- Source: vtk9 Source-Version: 9.0.1+dfsg1-3 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of vtk9, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated vtk9 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: Thu, 10 Dec 2020 17:33:59 +0100 Source: vtk9 Architecture: source Version: 9.0.1+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Anton Gladky Closes: 976127 976975 Changes: vtk9 (9.0.1+dfsg1-3) unstable; urgency=medium . [ Adrian Bunk ] * [52af841] Revert "Link against latomic" * [381ea98] Link with libatomic on archtectures that need it . [ Anton Gladky ] * [a983346] 80_allow_gles_platforms.patch. * [e79137e] Fix FTBFS against freetype 2.10.4. (Closes: #976975) * [d7ecb86] Add python3-vtk9 as Breaks+Replaces: python3-paraview. (Closes: #976127) * [19fe54e] Update changelog. Checksums-Sha1: fa8c4f3602ca85bc4430bfe306a32d980cb7b30b 3507 vtk9_9.0.1+dfsg1-3.dsc 3f6e33bd039a2f00efab0a8d34aeaa9c37e66ee6 17288 vtk9_9.0.1+dfsg1-3.debian.tar.xz 7f0694401d80a403a07bf0e3d89203fc2248be40 20655 vtk9_9.0.1+dfsg1-3_source.buildinfo Checksums-Sha256: f89695c9badee563bd5f041aa80825d99861610048e3c7ae236174646c2759cd 3507 vtk9_9.0.1+dfsg1-3.dsc 62810064c536503ea29c1bbf0ab253cf0fdefa542d661d5c811699c31efa0faf 17288 vtk9_9.0.1+dfsg1-3.debian.tar.xz b6867e6fff3d88f8d5851244a4907442fa05220a769e9580039d23acce741b4b 20655 vtk9_9.0.1+dfsg1-3_source.buildinfo Files: 8c92deb28b5a1ab6fba8005538fc5676 3507 graphics optional vtk9_9.0.1+dfsg1-3.dsc b197394b2e93451d60524e60e038f56d 17288 graphics optional vtk9_9.0.1+dfsg1-3.debian.tar.xz a1ea5ec680818f83a1a0f2e3f529f27a 20655 graphics optional vtk9_9.0.1+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl/STlcACgkQ0+Fzg8+n
Bug#977012: octave-level-set FTBFS with Octave 6.1.0: error: ‘const class Array’ has no member named ‘length’
Le jeudi 10 décembre 2020 à 04:39 +0200, Adrian Bunk a écrit :
> Source: octave-level-set
> Version: 0.3.0-11
> Severity: serious
> Tags: ftbfs
I attach a patch that fixes the compilation of the source code (some
functions were deprecated). But then there is a failure in the tests,
which I don’t understand (maybe another regression in Octave core?).
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name
⠈⠳⣄ https://www.debian.org
--- a/src/geomGamma.cpp
+++ b/src/geomGamma.cpp
@@ -192,7 +192,7 @@ DEFUN_DLD (__levelset_geomGamma, args, n
const Matrix inout = args(4).matrix_value ();
/* Extract and check the dimensions. */
- const unsigned nNodes = phi.nelem ();
+ const unsigned nNodes = phi.numel ();
const unsigned nElem = getDimension (nodelist, -1, 4);
const unsigned nBdryEl = getDimension (bdryInd, -1, 1);
getDimension (edges, nBdryEl, 4);
--- a/src/internal_mesh.cpp
+++ b/src/internal_mesh.cpp
@@ -300,7 +300,7 @@ getInnerSegment (const octave_scalar_map
assert (innerPts.empty ());
const ColumnVector inners = segs.contents ("inners").column_vector_value ();
- const unsigned nInners = inners.nelem ();
+ const unsigned nInners = inners.numel ();
for (unsigned i = 0; i < nInners; ++i)
innerPts.push_back (inners(nInners - i - 1) - 1);
}
@@ -387,7 +387,7 @@ DEFUN_DLD (__levelset_internal_mesh, arg
{
const unsigned cur = bdryElems(i) - 1;
const Cell cellSegs = bdryelSegs(i).cell_value ();
- const unsigned nSegs = cellSegs.nelem ();
+ const unsigned nSegs = cellSegs.numel ();
std::vector segs;
indexArr endEdges;
--- a/src/internal_fastmarching.cpp
+++ b/src/internal_fastmarching.cpp
@@ -74,7 +74,7 @@ DEFUN_DLD (__levelset_internal_fastmarch
{
const Array idx = getOctaveIdx (c);
assert (c.size () == D
- && static_cast (idx.length ()) == D);
+ && static_cast (idx.numel ()) == D);
if (domain(idx))
{
@@ -99,7 +99,7 @@ DEFUN_DLD (__levelset_internal_fastmarch
{
const Array idx = getOctaveIdx (c);
assert (c.size () == D
- && static_cast (idx.length ()) == D);
+ && static_cast (idx.numel ()) == D);
const Grid& constGrid(grid);
const Entry* e = constGrid.get (c);
signature.asc
Description: This is a digitally signed message part
Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02
On 10/12/20 5:37 μ.μ., Andreas Beckmann wrote: If it works with Linux 5.8, can you stick to an older kernel (which will not receive security updates) until there is a newer driver release available from Nvidia? I just installed 5.8 from buster-backports along with tesla-440 driver and it seems to give slightly better results,the modules build and load, but similar errors in kernel: [ 15.167039] NVRM: GPU :01:00.0: DMA address not in addressable range of device (0x80020054106-0x80020054106, 0x800-0x8ff) [ 15.167070] NVRM: GPU :01:00.0: DMA address not in addressable range of device (0x80020054106-0x80020054106, 0x800-0x8ff) [ 15.168422] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x31:0x40:937) [ 15.168517] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor number 0 ... [ 18.058799] NVRM: GPU :01:00.0: DMA address not in addressable range of device (0x80020053266-0x80020053266, 0x800-0x8ff) [ 18.058816] NVRM: GPU :01:00.0: DMA address not in addressable range of device (0x80020053266-0x80020053266, 0x800-0x8ff) [ 18.059885] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x31:0x40:937) [ 18.059943] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor number 0 As for Xorg.0.log: ... [ 18.046] (II) NVIDIA GLX Module 440.118.02 Thu Sep 3 09:45:23 UTC 2020 [ 18.049] (II) NVIDIA: The X server supports PRIME Render Offload. [ 18.158] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please [ 18.158] (EE) NVIDIA(GPU-0): check your system's kernel log for additional error [ 18.158] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common Problems in the [ 18.158] (EE) NVIDIA(GPU-0): README for additional information. [ 18.158] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device! [ 18.158] (EE) NVIDIA(0): Failing initialization of X screen [ 18.158] (II) UnloadModule: "nvidia" [ 18.158] (II) UnloadSubModule: "glxserver_nvidia" [ 18.158] (II) Unloading glxserver_nvidia [ 18.158] (II) UnloadSubModule: "wfb" [ 18.158] (II) UnloadSubModule: "fb" [ 18.158] (==) NVIDIA(G0): Depth 24, (==) framebuffer bpp 32 [ 18.158] (==) NVIDIA(G0): RGB weight 888 [ 18.158] (==) NVIDIA(G0): Default visual is TrueColor [ 18.158] (==) NVIDIA(G0): Using gamma correction (1.0, 1.0, 1.0) [ 18.158] (**) NVIDIA(G0): Enabling 2D acceleration [ 18.158] (EE) NVIDIA(G0): GPU screens are not yet supported by the NVIDIA driver [ 18.158] (EE) NVIDIA(G0): Failing initialization of X screen [ 18.158] (II) UnloadModule: "nvidia" [ 18.158] (II) UnloadSubModule: "wfb" [ 18.158] (II) UnloadSubModule: "fb" [ 18.158] (EE) Screen(s) found, but none have a usable configuration. [ 18.158] (EE) Fatal server error: [ 18.158] (EE) no screens found(EE) I don't mind waiting for a newer release, or using an older kernel, however any suggestions to solve the problem would be appreciated, even outside this particular bug report. Regards Konstantinos
Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue
Hi. I just re-ran tests after adding a build dependency on libgrpc-java and that fixed the reported issue. Cheers, Sven
Bug#975796: marked as done (flit: FTBFS: ImportError: cannot import name 'build_thyself' from 'flit_core' (unknown location))
Your message dated Thu, 10 Dec 2020 15:48:44 + with message-id and subject line Bug#975796: fixed in flit 3.0.0-1 has caused the Debian Bug report #975796, regarding flit: FTBFS: ImportError: cannot import name 'build_thyself' from 'flit_core' (unknown location) 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.) -- 975796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flit Version: 2.3.0-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary --with python3 >dh_testroot >dh_prep >debian/rules override_dh_auto_install > make[1]: Entering directory '/<>' > cp debian/build.py . > python3 build.py > Traceback (most recent call last): > File "/<>/build.py", line 19, in > from flit_core import build_thyself > ImportError: cannot import name 'build_thyself' from 'flit_core' (unknown > location) > make[1]: *** [debian/rules:19: override_dh_auto_install] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/11/25/flit_2.3.0-3_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! 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: flit Source-Version: 3.0.0-1 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of flit, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated flit 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: Thu, 10 Dec 2020 12:28:33 -0300 Source: flit Architecture: source Version: 3.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Antonio Terceiro Closes: 964440 968636 975796 977044 Changes: flit (3.0.0-1) unstable; urgency=medium . * Team upload . [ Scott Kitterman ] * Replace failing automatic man page generation with manual process that at least works (Closes: #977044) . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Antonio Terceiro ] * New upstream version 3.0.0 - Makes RECORD deterministic (Closes: #968636) - Builds reproducibly (Closes: #964440) * debian/build.py: fix location of top level directory (Closes: #975796) * debian/build.py: fix wrt the new upstream release * autopkgtest: drop unecessary breaks-testbed restriction * autopkgtest: only test against Debian * autopkgtest: ignore test that fails without `python` Checksums-Sha1: d40556d1233833a7502454cd037f494823112829 2145 flit_3.0.0-1.dsc ed76fb508ea1d4731965e005e4a7b200d87e3104 109641 flit_3.0.0.orig.tar.gz e809368eed9ffb32c1d2a49806add9c554031397 11348 flit_3.0.0-1.debian.tar.xz b5d0e15ba8d0c9427e0349e6d60be868f054ef64 6864 flit_3.0.0-1_amd64.buildinfo Checksums-Sha256: 8b9fed2d6b88814934be6146308d7d3dbb4132e7c02fe9570ee48756f3212756 2145 flit_3.0.0-1.dsc b4fe0f84a1ffbf125d003e253ec98c0b6e3e31290b31fba3ad22d28588c20893 109641 flit_3.0.0.orig.tar.gz bbc90d8d7e99368288483d0adc6a3558a916fccaa36aed08d1f760f97008df68 11348 flit_3.0.0-1.debian.tar.xz 47802b030c16d4758c1416b1356167ab9a3e1dd912cc4fbd19bb384b0a886b8b 6864 flit_3.0.0-1_amd64.buildinfo Files: 04aa0117d54eee9543a18a6d08b89a28 2145 python optional flit_3.0.0-1.dsc 9a8f700a7150eea2b1c59f926840945c 109641 python optional flit_3.0.0.orig.tar.gz 9d7575e8df4c1ed00199c75210c66b65 11348 python optional flit_3.0.0-1.debian.tar.xz 7f9d0f1873821538dce9846c8b34ff8c
Bug#976934: [PATCH] build/docs: move docstring prereq to file targets
On Wed, Dec 09 2020, David Bremner wrote: > Under a sufficiently high level of parallelism [1] there seems to be a > a race condition that allows sphinx-build to start running before the > docstrings are extracted. This change moves the docstring stamp from > the phony targets sphinx-html and sphinx-info to the file targets that > they depend on. I'm not sure why this makes things better, but I am > fairly confident it does not make things worse, and experimentally it > seems to eliminate the race condition. Good enough for me if this helps. I also don't see reason why that would make things better (and probably not things worse), just that I got headache reading that Makefile ;) (and, for example, these particular targets mentioned would not need to be marked .PHONY...) I'd suggest to monitor the behaviour for a while and if things are consistently better then merge -- such a things when we don't know enough experience may be enough (or someone(tm) could try to parse make debug logs ;/) -- or someone(tm) may tell us why that heleps :D Tomi > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976934 > --- > doc/Makefile.local | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/doc/Makefile.local b/doc/Makefile.local > index 60bd7184..f476d1da 100644 > --- a/doc/Makefile.local > +++ b/doc/Makefile.local > @@ -43,7 +43,7 @@ INFO_INFO_FILES := $(INFO_TEXI_FILES:.texi=.info) > rm -f $@ && gzip --no-name --stdout $^ > $@ > > ifeq ($(WITH_EMACS),1) > -$(DOCBUILDDIR)/.roff.stamp sphinx-html sphinx-texinfo: docstring.stamp > +$(DOCBUILDDIR)/.roff.stamp $(DOCBUILDDIR)/.html.stamp > $(DOCBUILDDIR)/.texi.stamp : docstring.stamp > endif > > sphinx-html: $(DOCBUILDDIR)/.html.stamp > -- > 2.29.2 > ___ > notmuch mailing list -- notm...@notmuchmail.org > To unsubscribe send an email to notmuch-le...@notmuchmail.org
Bug#976901: nvidia-tesla-450-kernel-dkms: Fails to build DKMS kernel module on ppc64le 450.80.02
On 12/10/20 10:37 AM, Konstantinos Margaritis wrote: > On 10/12/20 1:19 π.μ., Andreas Beckmann wrote: >> but I'm not sure whether it is worth backporting them, >> since you most likely will be affected by >> #973729 - nvidia-uvm does not work with Linux 5.9 >> which is fixed in 455.45.01 > > Well, I did the replace you suggested below and even though the modules > load, I don't get a display, here is what dmesg gives: > > [ 15.889326] NVRM: GPU :01:00.0: DMA address not in addressable > range of device (0x80020054de8-0x80020054de8, > 0x800-0x8ff) If it works with Linux 5.8, can you stick to an older kernel (which will not receive security updates) until there is a newer driver release available from Nvidia? Andreas
Bug#976994: marked as done (ccls: autopkgtest regression in testing: FAIL: test_response (__main__.TestLSP) [$ccls/info])
Your message dated Thu, 10 Dec 2020 15:18:30 +
with message-id
and subject line Bug#976994: fixed in ccls 0.20201025-2
has caused the Debian Bug report #976994,
regarding ccls: autopkgtest regression in testing: FAIL: test_response
(__main__.TestLSP) [$ccls/info]
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.)
--
976994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ccls
Version: 0.20201025-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of this report. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/c/ccls/8701788/log.gz
autopkgtest [13:23:44]: test lsp-test: [---
test_index (__main__.TestLSP) ... ok
test_response (__main__.TestLSP) ...
==
FAIL: test_response (__main__.TestLSP) [initialize]
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.jn191c8j/downtmp/build.gr1/src/debian/tests/lsp-test",
line 167, in test_response
one(tt)
File
"/tmp/autopkgtest-lxc.jn191c8j/downtmp/build.gr1/src/debian/tests/lsp-test",
line 154, in one
self.assertEqual(case[1], got)
AssertionError: {'jsonrpc': '2.0', 'id': 1, 'result': {'capabilities':
{'text[1146 chars]1'}}} != {'jsonrpc': '2.0', 'method': '$/progress',
'params': {'token'[88 chars]58}}}
- {'id': 1,
- 'jsonrpc': '2.0',
? ^
+ {'jsonrpc': '2.0',
? ^
+ 'method': '$/progress',
+ 'params': {'token': 'index',
+ 'value': {'kind': 'report',
+ 'message': '37/38',
+ 'percentage': 97.36842105263158}}}
- 'result': {'capabilities': {'codeActionProvider': {'codeActionKinds':
['quickfix']},
- 'codeLensProvider': {'resolveProvider':
False},
- 'completionProvider': {'resolveProvider':
False,
-
'triggerCharacters': ['.',
-
':',
-
'>',
-
'#',
-
'<',
-
'"',
-
'/']},
- 'declarationProvider': True,
- 'definitionProvider': True,
- 'documentFormattingProvider': True,
- 'documentHighlightProvider': True,
- 'documentLinkProvider':
{'resolveProvider': True},
- 'documentOnTypeFormattingProvider':
{'firstTriggerCharacter': '}',
-
'moreTriggerCharacter': []},
- 'documentRangeFormattingProvider': True,
- 'documentSymbolProvider': True,
- 'executeCommandProvider': {'commands':
['ccls.xref']},
- 'foldingRangeProvider': True,
- 'hoverProvider': True,
- 'implementationProvider': True,
- 'referencesProvider': True,
- 'renameProvider': True,
- 'signatureHelpProvider':
{'triggerCharacters': ['(',
-
',']},
- 'textDocumentSync': {'change': 2,
- 'openClose': True,
- 'save':
{'includeText': False},
- 'willSave': False,
- 'willSaveWaitUntil':
False},
- 'typeDefinitionProvider': True,
- 'workspace': {'workspaceFolders':
{'changeNotifications': True,
-
'supported': True}},
- 'workspaceSymbolProvider': True},
- 'serverInfo': {'name': 'ccls', 'version': '0.20201025-1'}}}
==
FAIL: test_response (__main__.TestLSP) [$ccls/info]
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.jn191c8j/downtmp/build.gr1/src/debian/tests/lsp-test",
line 167, in test_response
one(tt)
File
Bug#972505: marked as done (pgl-ddl-deploy needs porting to PostgreSQL 13)
Your message dated Thu, 10 Dec 2020 15:19:10 + with message-id and subject line Bug#972505: fixed in pgl-ddl-deploy 2.0.0-2 has caused the Debian Bug report #972505, regarding pgl-ddl-deploy needs porting to PostgreSQL 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.) -- 972505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-12-pgl-ddl-deploy Version: 1.7.0-1 Severity: serious Forwarded: https://github.com/enova/pgl_ddl_deploy/issues/55 pgl-ddl-deploy needs porting to PostgreSQL 13. Please remove pgl-ddl-deploy from testing for the time being so pglogical and the other pglogical reverse-depends can migrate to testing. Christoph --- End Message --- --- Begin Message --- Source: pgl-ddl-deploy Source-Version: 2.0.0-2 Done: Christian Ehrhardt We believe that the bug you reported is fixed in the latest version of pgl-ddl-deploy, 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. Christian Ehrhardt (supplier of updated pgl-ddl-deploy 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, 07 Dec 2020 14:18:20 +0100 Source: pgl-ddl-deploy Architecture: source Version: 2.0.0-2 Distribution: unstable Urgency: medium Maintainer: Jeremy Finzel Changed-By: Christian Ehrhardt Closes: 972505 Changes: pgl-ddl-deploy (2.0.0-2) unstable; urgency=medium . [ Jeremy Finzel ] * Regression fix - add -o wal_level=logical . [ Christian Ehrhardt ] * d/changelog: fix new version to be >2.0.0-1 * revert unmentioned drop of needs-root in d/t/control * d/t/control: update test dependencies for postgresql-13 . pgl-ddl-deploy (2.0.0-1) unstable; urgency=medium . * Support for Native Logical Replication * Support for Postgres 13 (Closes: #972505) Checksums-Sha1: 67e1d7cb53816b678416388efc182b5cecd441ce 2077 pgl-ddl-deploy_2.0.0-2.dsc 2a0015a89f4350f430750db7d0a0ef61928d377f 3500 pgl-ddl-deploy_2.0.0-2.debian.tar.xz Checksums-Sha256: 779e5f69ad96b3104f2f0e995381a3129a1ce4a1ecd4e0a724a3e4d8651be2d3 2077 pgl-ddl-deploy_2.0.0-2.dsc 34ee16b34ade2c6d597502fe1dda0746163bd97890255b93d4a0c9a8533174c1 3500 pgl-ddl-deploy_2.0.0-2.debian.tar.xz Files: 9e4cfea2e4427421d47f9c5199482a2f 2077 database optional pgl-ddl-deploy_2.0.0-2.dsc 246382f1d8d6ce94f580f117f45866c0 3500 database optional pgl-ddl-deploy_2.0.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl/SOJUACgkQTFprqxLS p66VtRAAr4kz6ae12d4oy+G/XdZE0REoAp43uKxGyxJvKBddxEoelmxnfMHN3/cw crItzVjerUfRNnxMcwog/52cJxCccAgaZjW+HvBRnxmmcELfANTL3VuhlS5IN+Za j6ROLm6cqYKOYUtjSmWjLlwQ3VgdpzGTfb9398NZcWXxh17qVgCjbZ2nBVXYxvGS e8dTgVGkFMuAy4wrI56REPCD4cMaMP7KphkmM9+Wgrftpr2jUn2Oj/TcQ7LWVUs6 lmwRFoPm6Lf44pxGvOJVVl6Iyqr2eOFVCMTP8FutZnyImO6IFTcSZXUgh7uI0eDH iVZRh1u+VhBo/jfauKIlyY+e8HINi5j4TUzWLhBkF6Eid4HyDbnSS2ORe6nbMcgx 1mehctO8+KXbQMEmgAH7aMGLqjMzdH0Ord66VrrsvNx+4rjkqOdpyXs9R/7ToQNV j5qYv+YGgVl3q5v3/Kf6THqtfpcZtjlD4AxYWoa+IA5bfCLRQQqg6FoZ1/xjOgwC DJSuQeyYaNcVNGksYTRGLiG47uwbqQ4eZAmng3Lc+ZAdXX/e2dYLDJIQsFW+dxkt kEDjm9D5GUsj7ScVywT3+bqp8BF6MXlvQG4LRSt8WyNSXqEzlA5Q3zV1bV2J4hkB Mg2PSmnU9F8d6Xz4+n5laCY5p9Vzq0sXcNUkXMeMt/nHDctrQYc= =X5m6 -END PGP SIGNATURE End Message ---
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956779 [src:redshift] redshift: Depends on deprecated libappindicator Severity set to 'serious' from 'important' -- 956779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956776 [src:osdlyrics] osdlyrics: Depends on deprecated libappindicator Severity set to 'serious' from 'important' -- 956776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956774 [src:kylin-burner] kylin-burner: Depends on deprecated libappindicator Severity set to 'serious' from 'important' -- 956774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956782 [src:zeal] zeal: Build-Depends (unnecessarily?) on deprecated libappindicator Severity set to 'serious' from 'important' -- 956782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956778 [src:parcellite] parcellite: Depends on deprecated libappindicator Severity set to 'serious' from 'important' -- 956778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956772 [src:hime] hime: Depends on deprecated libappindicator Severity set to 'serious' from 'important' -- 956772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956769 [src:gromit-mpx] gromit-mpx: Depends on deprecated libappindicator Severity set to 'serious' from 'important' -- 956769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956767 [src:fusion-icon] fusion-icon: Depends on deprecated libappindicator Severity set to 'serious' from 'important' -- 956767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956766 [src:gcin] gcin: Build-Depends (unnecessarily?) on deprecated libappindicator Severity set to 'serious' from 'important' -- 956766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956762 [autokey-gtk] autokey-gtk: Depends on deprecated libappindicator Severity set to 'serious' from 'important' -- 956762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #956760 [src:cairo-dock-plug-ins] cairo-dock-plug-ins: (Build-)Depends on deprecated libindicator Severity set to 'serious' from 'important' -- 956760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #921339 [psensor] Please switch to Ayatana AppIndicator Severity set to 'serious' from 'important' -- 921339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to libayatana-indicator instead Ignoring request to change severity of Bug 895038 to the same value. -- 895038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Processing control commands: > severity -1 serious Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s) Ignoring request to change severity of Bug 895037 to the same value. -- 895037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895037: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Control: severity -1 serious On Thu, 10 Dec 2020 at 14:37:21 +, Mike Gabriel wrote: > On Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote: > > We're running into the freeze of bullseye soon. The first bug I checked > > is still only severity important, so is it realistic to get this done > > before bullseye release? [...] > > If yes, action is needed, this isn't going to happen > > magically. At the least raising the blocking bugs to severity serious. > > I'd suggest to raise severity of the still open bugs and get libappindicator > kicked out before the bullseye release. > > The fixes are easy to be done. Maintainers can ping me if they have problems. Raising the blocking bugs to RC as requested. > I am not so experienced with effective mass manipulation of bugs, Simon, > could you bump the severity of the respective bugs? There's no magic to it, you just send mail to the affected bug address(es) with appropriate Control commands. smcv
Bug#966839: marked as done (openmm: withhold the package until a stable release)
Your message dated Thu, 10 Dec 2020 15:05:12 + with message-id and subject line Bug#966839: fixed in openmm 7.5.0+dfsg-1 has caused the Debian Bug report #966839, regarding openmm: withhold the package until a stable release 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.) -- 966839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openmm Severity: grave Owner: Andrius Merkys Control: forwarded -1 https://github.com/openmm/openmm/issues/2784 Hello, The upstream expressed their concern that packaging development version of OpenMM may cause trouble with its users [1]. Therefore it has been agreed to withhold the Debian package until the next stable release. [1] https://github.com/openmm/openmm/issues/2784 Andrius --- End Message --- --- Begin Message --- Source: openmm Source-Version: 7.5.0+dfsg-1 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of openmm, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated openmm 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: Thu, 10 Dec 2020 09:24:19 -0500 Source: openmm Architecture: source Version: 7.5.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 966839 Changes: openmm (7.5.0+dfsg-1) unstable; urgency=medium . * New upstream version 7.5.0+dfsg (Closes: #966839) * Reordering copyright statements. Checksums-Sha1: 921bb81f5410e253d8129b75d005c63d6d9fb309 2249 openmm_7.5.0+dfsg-1.dsc 5cbf321724adfffdf3784f35b31efe6da7067dcd 10454924 openmm_7.5.0+dfsg.orig.tar.xz 4f59e875706178877eb705a2669a27f8ee709fdc 13724 openmm_7.5.0+dfsg-1.debian.tar.xz 679600ea0df59053c8c8fd02204b11423449dad2 8334 openmm_7.5.0+dfsg-1_source.buildinfo Checksums-Sha256: 3642ac57faf692dad745f0b45ed791884ff0efb2b931768a76993444cd519d2f 2249 openmm_7.5.0+dfsg-1.dsc 0ce4132cbb09ef91e751bb932021e70e96e8625a01deb07f06a3547f434fd817 10454924 openmm_7.5.0+dfsg.orig.tar.xz 06e1c58e42841132cdd0026b636bd2e79b714395004c11b0f0094bb19dc91127 13724 openmm_7.5.0+dfsg-1.debian.tar.xz 852f7d324dce5b0191ee4eb73d100af3fddfd8f32d1abb924566d603f0e0dbe1 8334 openmm_7.5.0+dfsg-1_source.buildinfo Files: ebde91c060fced9560fd2fd1aacf9cad 2249 libs optional openmm_7.5.0+dfsg-1.dsc 3ac3b23722dc684cc7c399cc21b1d12e 10454924 libs optional openmm_7.5.0+dfsg.orig.tar.xz 6aff2f1721a9c4ed711a1f80237e8211 13724 libs optional openmm_7.5.0+dfsg-1.debian.tar.xz 8c9d8d947f68468467da7e1c40469073 8334 libs optional openmm_7.5.0+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAl/SNYkSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHc6sP/2PISvR0zdbqSrB64mB3s9DBJrS4A/x7 KP1IkQc1z3aEg2tz059AgdURd/KKXXffAeZsZG0tO3pauWjKOqkk9Bobm6dWBIkb jkvmFetFjo+uM5KGY1djZHu3sICguWfXaU/BjHnUe57uIoOlDtNyVrSNr8hyf3Z7 rS/Dm5GKbVJonMgcYqn4gPbwNFoFGRt/PSk8BTYLHh2cSskxqEE4/KKIWlS702FA THeIr/hwitQYQE+yJ87PzCpVpv8ZMROoYOXjN4Cg/A6euqZqBteY7iHCMbeJvAsn 75ppJCwJnpTWeG8mEtid9wsy+9rsOkBK1HkmO1hkZuCTYzltqiNKKzsEwZJe/n75 aLZYN7OmrBCisQXygv2kBxpn41iQL2T07CnbyNSZMlYbwBYwsuXKvuuYqv+PAY2G ROLSOB7Hs2VotTgpm6xb7nNP2K9IMa8nSgBgkU3dhdn+xSmJVQaZaDVy5D4ITrBM biMschB91i1ssmOw8R+mXawh5pQSyW2PTNczzb1ATsiUPy0byqKGFVme081oHWM8 I/lfev/0L4hOWDTEREp18zBy4QSZJQphZfK3Y5ijE+shDoKTz0whpF3ACohubtBN LGmoiisDERrvAT2Zj2FaD1/oAJO/NmKyHrxCV95chq0yaMKqfuVH/ssPFj8K4D+G Ks5NF0TB3QiA =gTVT -END PGP SIGNATURE End Message ---
Processed: owner 977038
Processing commands for cont...@bugs.debian.org: > owner 977038 tmanc...@debian.org Bug #977038 [google-oauth-client-java] google-oauth-client-java: FTBFS: Failed to execute goal on project google-oauth-client: Could not resolve dependencies for project com.google.api-client:google-api-client:jar:1.27.1: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact io.grpc:grpc-context:jar:debian has not been downloaded from it before. Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 977038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976994: ccls: autopkgtest regression in testing: FAIL: test_response (__main__.TestLSP) [$ccls/info]
Control: tags -1 + pending On Thu, Dec 10, 2020 at 4:09 AM Paul Gevers wrote: > > Source: ccls > Version: 0.20201025-1 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > With a recent change in testing the autopkgtest of your package started > to fail. I copied some of the output at the bottom of this report. Can > you please investigate the situation and fix it? > TLDR, it's caused by binNMU. The test I wrote in this package's autopkgtest, uses `dpkg-parsechangelog -SVersion` to detect the version, then fails to match the binNMU version. Can we have autopkgtest for migration of binNMU? -- Shengjing Zhu
Processed: Re: Bug#976994: ccls: autopkgtest regression in testing: FAIL: test_response (__main__.TestLSP) [$ccls/info]
Processing control commands: > tags -1 + pending Bug #976994 [src:ccls] ccls: autopkgtest regression in testing: FAIL: test_response (__main__.TestLSP) [$ccls/info] Added tag(s) pending. -- 976994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977000: marked as done (python3-apt: dak crashes after security update)
Your message dated Thu, 10 Dec 2020 14:49:14 +
with message-id
and subject line Bug#977000: fixed in python-apt 2.1.7
has caused the Debian Bug report #977000,
regarding python3-apt: dak crashes after security update
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.)
--
977000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-apt
Version: 1.8.4.2
Severity: grave
Tags: security
Justification: renders package unusable
dak crashes with a segmentation fault in python3-apt when processing
uploads or processing the NEW queue on ftp-master; and also on my
playground server (used to generate the backtrace).
$ gdb --batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' \
-args /usr/bin/python3 ~dak/dak/dak/dak.py examine-package \
python3-apt_1.8.4.2_amd64.deb &> dak-segfault.txt
produced the attached backtrace.
The problematic line seems to be:
+---
| return apt_inst.DebFile(fh).control.extractdata("control")
+---[
https://salsa.debian.org/ftp-team/dak/-/blob/891420d6c0c46472f25585ac05760dabc84e74ad/daklib/utils.py#L939
]
and indeed
$ gdb --args python3 -c 'import apt_inst;
apt_inst.DebFile(open("python3-apt_1.8.4.2_amd64.deb")).control.extractdata("control")'
also reproduces the segmentation fault.
Ansgar
-- System Information:
Debian Release: 10.7
Architecture: amd64 (x86_64)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages python3-apt depends on:
ii libapt-inst2.0 1.8.2.2
ii libapt-pkg5.0 1.8.2.2
ii libc6 2.28-10
ii libgcc11:8.3.0-6
ii libstdc++6 8.3.0-6
ii python-apt-common 1.8.4.2
ii python33.7.3-1
Versions of packages python3-apt recommends:
pn iso-codes
pn lsb-release
Versions of packages python3-apt suggests:
ii apt 1.8.2.2
pn python-apt-doc
ii python3-apt-dbg 1.8.4.2
-- no debconf information
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 1948]
Program received signal SIGSEGV, Segmentation fault.
0x768b90e6 in ararchive_new (type=0x768c00a0 ,
args=, kwds=) at /usr/include/c++/8/new:169
169 { return __p; }
#0 0x768b90e6 in ararchive_new (type=0x768c00a0 ,
args=, kwds=) at /usr/include/c++/8/new:169
#1 0x768b973d in debfile_new (type=type@entry=0x768c00a0
, args=args@entry=(<_io.TextIOWrapper at remote
0x75a461f8>,), kwds=kwds@entry=0x0) at python/arfile.cc:613
#2 0x005ce067 in type_call (kwds=0x0, args=(<_io.TextIOWrapper at
remote 0x75a461f8>,), type=0x768c00a0 ) at
../Objects/typeobject.c:929
#3 _PyObject_FastCallKeywords (callable=,
stack=0x75a89a10, nargs=, kwnames=) at
../Objects/call.c:199
#4 0x0053ed81 in call_function (pp_stack=0x7fffd7b0,
oparg=, kwnames=) at ../Python/ceval.c:4619
#5 0x0054653a in _PyEval_EvalFrameDefault (f=,
throwflag=) at ../Python/ceval.c:3093
#6 0x005cd68c in PyEval_EvalFrameEx (throwflag=0, f=Frame
0x75a89890, for file /mnt/data/srv/dak/dak/daklib/utils.py, line 939, in
deb_extract_control (fh=<_io.TextIOWrapper at remote 0x75a461f8>)) at
../Python/ceval.c:547
#7 function_code_fastcall (globals=, nargs=,
args=, co=) at ../Objects/call.c:283
#8 _PyFunction_FastCallKeywords (func=, stack=,
nargs=, kwnames=) at ../Objects/call.c:408
#9 0x0053ebb0 in call_function (pp_stack=0x7fffd990,
oparg=, kwnames=) at ../Python/ceval.c:4616
#10 0x0054653a in _PyEval_EvalFrameDefault (f=,
throwflag=) at ../Python/ceval.c:3093
#11 0x005cd68c in PyEval_EvalFrameEx (throwflag=0, f=Frame 0xedcd38,
for file /mnt/data/srv/dak/dak/dak/examine_package.py, line 261, in
read_control (filename='python3-apt_1.8.4.2_amd64.deb', recommends=[],
predepends=[], depends=[], section='', maintainer='', arch='',
deb_file=<_io.TextIOWrapper at remote 0x75a461f8>)) at ../Python/ceval.c:547
#12 function_code_fastcall (globals=, nargs=,
args=, co=) at ../Objects/call.c:283
#13 _PyFunction_FastCallKeywords (func=, stack=,
nargs=, kwnames=) at ../Objects/call.c:408
#14 0x0054207c in call_function (kwnames=0x0, oparg=,
pp_stack=) at ../Python/ceval.c:4616
#15 _PyEval_EvalFrameDefault (f=, throwflag=) at
../Python/ceval.c:3124
#16 0x0053f732 in
Bug#973493: marked as done (src:rust-log: fails to migrate to testing for too long: autopkgtest regression)
Your message dated Thu, 10 Dec 2020 14:42:20 + with message-id and subject line Bug#973493: fixed in rust-log 0.4.11-2 has caused the Debian Bug report #973493, regarding src:rust-log: fails to migrate to testing for too long: autopkgtest regression 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.) -- 973493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-log Version: 0.4.8-4 Severity: serious Control: close -1 0.4.11-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 970463 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:rust-log in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=rust-log signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: rust-log Source-Version: 0.4.11-2 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of rust-log, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated rust-log 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: Thu, 10 Dec 2020 12:31:03 +0100 Source: rust-log Architecture: source Version: 0.4.11-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Sylvestre Ledru Closes: 970463 973493 Changes: rust-log (0.4.11-2) unstable; urgency=medium . * Package log 0.4.11 from crates.io using debcargo 2.4.3 (Closes: #970463, #973493) * Mark the testsuite as failing: sval isn't available in Debian yet. Checksums-Sha1: 13329015d2fb592d29c6ef5ce45c48dd982b88c1 2234 rust-log_0.4.11-2.dsc 9f879c33ab1ce7b94673f1877b55a5e998d812c3 3912 rust-log_0.4.11-2.debian.tar.xz fa32751f6369b10834043eca113a148275e383f6 8631 rust-log_0.4.11-2_source.buildinfo Checksums-Sha256: bba83935861031f1e6d538541f049318c96ae9a47882d1eac5d0bccb9f3e30bf 2234 rust-log_0.4.11-2.dsc 48d9a22e53629c45351e1e403b8ba5847165fd5b5a43a664d0f2206842430d20 3912 rust-log_0.4.11-2.debian.tar.xz 37987a8875dcef41b2201ddc04104b5bc29d27efc6f0edd36bf69da773743101 8631 rust-log_0.4.11-2_source.buildinfo Files: 134b6c063ec7cb9c94199f578e4293fa 2234 rust optional rust-log_0.4.11-2.dsc 457fa4903018e5d1ab155f84533d6373 3912 rust optional rust-log_0.4.11-2.debian.tar.xz 9348a53fff1352c310a6d8600a6d37e2 8631 rust optional rust-log_0.4.11-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl/SBvwACgkQfmUo2nUv G+E6HQ/9GE/YF+a9y0XIEQEfhyLUgsf7krNboA7kTRTSCofEEj6ak4JqQjIPEnK2 j/q9x0Y/716tJPx6xmBjXwBl+7aDfUvvK/5ZXubd3rScT9PsXHfK+VFAiP5yukl1
Bug#970463: marked as done (rust-log: autopkgtest regression can't find crate for `serde_test`)
Your message dated Thu, 10 Dec 2020 14:42:20 + with message-id and subject line Bug#970463: fixed in rust-log 0.4.11-2 has caused the Debian Bug report #970463, regarding rust-log: autopkgtest regression can't find crate for `serde_test` 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.) -- 970463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-log Version: 0.4.11-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of rust-log the autopkgtest of rust-log fails in testing when that autopkgtest is run with the binary packages of rust-log from unstable. It passes when run with only packages from testing. In tabular form: passfail rust-log from testing0.4.11-1 all others from testingfrom testing Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? Paul [1] https://qa.debian.org/excuses.php?package=rust-log https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-log/7031906/log.gz signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: rust-log Source-Version: 0.4.11-2 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of rust-log, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated rust-log 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: Thu, 10 Dec 2020 12:31:03 +0100 Source: rust-log Architecture: source Version: 0.4.11-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Sylvestre Ledru Closes: 970463 973493 Changes: rust-log (0.4.11-2) unstable; urgency=medium . * Package log 0.4.11 from crates.io using debcargo 2.4.3 (Closes: #970463, #973493) * Mark the testsuite as failing: sval isn't available in Debian yet. Checksums-Sha1: 13329015d2fb592d29c6ef5ce45c48dd982b88c1 2234 rust-log_0.4.11-2.dsc 9f879c33ab1ce7b94673f1877b55a5e998d812c3 3912 rust-log_0.4.11-2.debian.tar.xz fa32751f6369b10834043eca113a148275e383f6 8631 rust-log_0.4.11-2_source.buildinfo Checksums-Sha256: bba83935861031f1e6d538541f049318c96ae9a47882d1eac5d0bccb9f3e30bf 2234 rust-log_0.4.11-2.dsc 48d9a22e53629c45351e1e403b8ba5847165fd5b5a43a664d0f2206842430d20 3912 rust-log_0.4.11-2.debian.tar.xz 37987a8875dcef41b2201ddc04104b5bc29d27efc6f0edd36bf69da773743101 8631 rust-log_0.4.11-2_source.buildinfo Files: 134b6c063ec7cb9c94199f578e4293fa 2234 rust optional rust-log_0.4.11-2.dsc 457fa4903018e5d1ab155f84533d6373 3912 rust optional rust-log_0.4.11-2.debian.tar.xz 9348a53fff1352c310a6d8600a6d37e2 8631 rust optional rust-log_0.4.11-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl/SBvwACgkQfmUo2nUv G+E6HQ/9GE/YF+a9y0XIEQEfhyLUgsf7krNboA7kTRTSCofEEj6ak4JqQjIPEnK2 j/q9x0Y/716tJPx6xmBjXwBl+7aDfUvvK/5ZXubd3rScT9PsXHfK+VFAiP5yukl1 ga7VtO8Jwo6qG+vQ1z87zBbCfvDDFd19X8jOXxuUm8w6ugTPSvVuM3kvCBgCROb7 um1SPRZrJ2u+ecVmOb1/XFo2kQTesICb0r1CaeJwPxZAQX3n6enomyDBcifvnlVQ DzDiKMKiBAtF3sjPDrA6zwE1wRf7pN3aA8NAy6DC4VhloifsjKudV+kxkIouAQOM pyMzU+qdeKe/Zjs2QRhFXWA0j1lnhFU57oPk8+D1cD1DEC4k+zq1UXzwUsyaW5s3 Jhy6IuJCemHkItU0/CubCCqRNfvEvaKrkUyrbREpH2TmvAj2jdCzVBAejI9sYDEf XA3lxGphGeL07FjjhXXwE4bunsKUKeprNA2woC5dNmMPW3aV8RGoA/4J1/I5Q5zC +dVNhUg5ZQ5CUaBm+lQ5qdG23MxVQsAPFEPE9k4CbHDuDXlkh4HqGeTYBElM/Xw8 vwQ1nTkJsqLeqYvch91WCMnH6ZXoPqnCLFUFR5uAEMHCaEMdFLu41idABP94fS+1 m4k+7QIYAM2klHyVqCHby8KeFydIPdjMM8hzmcIVF1ZuzOWXmZM= =BN5/ -END PGP SIGNATURE End Message ---
Bug#973200: marked as done (powa-archivist: FTBFS: diff in generated debian/control)
Your message dated Thu, 10 Dec 2020 15:44:22 +0100
with message-id
and subject line Re: Bug#973200: powa-archivist: FTBFS: diff in generated
debian/control
has caused the Debian Bug report #973200,
regarding powa-archivist: FTBFS: diff in generated debian/control
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.)
--
973200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: powa-archivist
Version: 4.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2020-05-10 10:44:52.0 +
> +++ debian/control.Knpdq7 2020-10-27 12:29:48.260026766 +
> @@ -10,10 +10,10 @@
> Vcs-Browser: https://github.com/powa-team/powa-archivist
> Vcs-Git: https://github.com/powa-team/powa-archivist.git
>
> -Package: postgresql-12-powa
> +Package: postgresql-13-powa
> Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-12
> -Description: PostgreSQL Workload Analyzer -- PostgreSQL 12 extension
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
> +Description: PostgreSQL Workload Analyzer -- PostgreSQL 13 extension
> This package contains the core extension of the PoWA project, a PostgreSQL
> Workload Analyzer that gathers performance stats and provides real-time
> charts
> and graphs to help monitor and tune your PostgreSQL servers.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
> debian/control] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/10/27/powa-archivist_4.0.1-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!
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 ---
Version: 4.1.0-1
Re: Lucas Nussbaum
> > -Package: postgresql-12-powa
> > +Package: postgresql-13-powa
Fixed with the last upload, currently in NEW.
Christoph--- End Message ---
Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Hi Paul, On Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote: Hi Mike, On Wed, 15 Apr 2020 19:06:59 + Mike Gabriel wrote: >> If you want to get this done for bullseye, please upgrade these bugs to >> serious. Autoremovals will take care of some of the packages. The rest will >> need manual fixes. > > I haven't done that. I think the severity of these bugs is a decision > for the maintainer of the replacement to make. I think we should start with important and raise to serious after 8 weeks or so. We're running into the freeze of bullseye soon. The first bug I checked is still only severity important, so is it realistic to get this done before bullseye release? If not, I propose to tag this bug as bullseye-ignore. If yes, action is needed, this isn't going to happen magically. At the least raising the blocking bugs to severity serious. Help towards the maintainers of the affected packages would be very appreciated. Paul I'd suggest to raise severity of the still open bugs and get libappindicator kicked out before the bullseye release. The fixes are easy to be done. Maintainers can ping me if they have problems. I am not so experienced with effective mass manipulation of bugs, Simon, could you bump the severity of the respective bugs? Ok? Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpgq_eMt_fdX.pgp Description: Digitale PGP-Signatur
Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Hi Mike, On Wed, 15 Apr 2020 19:06:59 + Mike Gabriel wrote: > >> If you want to get this done for bullseye, please upgrade these bugs to > >> serious. Autoremovals will take care of some of the packages. The rest will > >> need manual fixes. > > > > I haven't done that. I think the severity of these bugs is a decision > > for the maintainer of the replacement to make. > > I think we should start with important and raise to serious after 8 > weeks or so. We're running into the freeze of bullseye soon. The first bug I checked is still only severity important, so is it realistic to get this done before bullseye release? If not, I propose to tag this bug as bullseye-ignore. If yes, action is needed, this isn't going to happen magically. At the least raising the blocking bugs to severity serious. Help towards the maintainers of the affected packages would be very appreciated. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: bullseye ignore
Processing control commands: > block -1 by 931197 Bug #939733 [lsb-release] lsb-release: lsb_release does not show point release on Debian 10.1 939733 was not blocked by any bugs. 939733 was not blocking any bugs. Added blocking bug(s) of 939733: 931197 > tags -1 bullseye-ignore Bug #939733 [lsb-release] lsb-release: lsb_release does not show point release on Debian 10.1 Added tag(s) bullseye-ignore. -- 939733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939733: bullseye ignore
Control: block -1 by 931197 Control: tags -1 bullseye-ignore Hi, The request to fix this in buster was turned down after some discussion. As such I'm not sure that this should be RC for lsb-release. Without changes, this needs to be fixed at the right time in base-files anyways (there's a bug open about that, severity minor). In any case, I don't think this bug warrants to hold up the release, especially because it won't be a regression anymore. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: notfound 977034 in 1.3.2-1, found 977034 in 1.4.3-1
Processing commands for cont...@bugs.debian.org: > notfound 977034 1.3.2-1 Bug #977034 [libmaxminddb-dev] libmaxminddb-dev: File conflict libmaxminddb-dev & libmaxminddb0 No longer marked as found in versions libmaxminddb/1.3.2-1. > found 977034 1.4.3-1 Bug #977034 [libmaxminddb-dev] libmaxminddb-dev: File conflict libmaxminddb-dev & libmaxminddb0 Marked as found in versions libmaxminddb/1.4.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 977034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976189: Catfish not starting anymore after installation of Python 3.9
I have posted a merge request at https://salsa.debian.org/python-team/packages/catfish/-/merge_requests/2 which fixes this. Please review and merge. /Andreas Rönnquist gus...@debian.org andr...@ronnquist.net
Bug#977039: pygrib: binary-any FTBFS
Source: pygrib
Version: 2.1.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=pygrib=sid
...
debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
find debian/python3-grib -true -print0 2>/dev/null | xargs -0r chown
--no-dereference 0:0
find debian/python3-grib ! -type l -a -true -a -true -print0
2>/dev/null | xargs -0r chmod go=rX,u+rw,a-s
find debian/python3-grib/usr/share/doc -type f -a -true -a ! -regex
'debian/python3-grib/usr/share/doc/[^/]*/examples/.*' -print0 2>/dev/null |
xargs -0r chmod 0644
find debian/python3-grib/usr/share/doc -type d -a -true -a -true
-print0 2>/dev/null | xargs -0r chmod 0755
find debian/python3-grib/usr/share/man -type f -a -true -a -true
-print0 2>/dev/null | xargs -0r chmod 0644
find debian/python3-grib -type f \( -name '*.so.*' -o -name '*.so' -o
-name '*.la' -o -name '*.a' -o -name '*.js' -o -name '*.css' -o -name '*.scss'
-o -name '*.sass' -o -name '*.jpeg' -o -name '*.jpg' -o -name '*.png' -o -name
'*.gif' -o -name '*.cmxs' -o -name '*.node' \) -a -true -a -true -print0
2>/dev/null | xargs -0r chmod 0644
find debian/python3-grib/usr/bin -type f -a -true -a -true -print0
2>/dev/null | xargs -0r chmod a+x
find debian/python3-grib/usr/lib -type f -name '*.ali' -a -true -a
-true -print0 2>/dev/null | xargs -0r chmod uga-w
find debian/python-grib-doc -name '*.grb' -exec chmod -x {} \;
find: ‘debian/python-grib-doc’: No such file or directory
make[1]: *** [debian/rules:31: override_dh_fixperms] Error 1
Bug#976619: marked as done (ts-node: required modules not declared as dependencies)
Your message dated Thu, 10 Dec 2020 13:20:00 + with message-id and subject line Bug#976619: fixed in ts-node 9.1.1-1 has caused the Debian Bug report #976619, regarding ts-node: required modules not declared as dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ts-node Version: 9.0.0-1 Severity: serious Justification: Policy 3.5 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ts-node package lacks declaring its runtime dependencies: node-arg node-diff node-make-error node-source-map-support node-yn (yes, I notice that ts-node is only in experimental for now - I am just eager to play with it: it is needed for recent eslint). - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/MB/8ACgkQLHwxRsGg ASFhSBAAlMIFTKmL+Uix01Akrj+lX0qfIGHZmvcANj7dl4zOuimVd8hMlqAxRKFs 2jt3mwp6m3jo2FW3Qyyon4RSkBQUUXMebBfn/fwiqo1SMiZLtIV02SK1lWuWMuIu ORZuCiHAwUZiVior2Wi1M7roJSTgYO57bzFT+tmjup5lzf3QQCKH8elsWWTtUFT7 sm2vVMK5BnDvZ3nZpUTJ25H6MbkidyQBqVGx/oR2bcnlEwRVTRiUhpRkcz1Z3xGW v2cGR+ou2a1ig7F/BsXJETLWPo9NjAmKPVpjx47qa1zEYuml6XOkLvqeODR06vYt XTVscDSz2/1B4g/xmmx/BHYTN9b4BmH5uSAu+o4F0zB06Prb1Kz9IS6lbfYBdwwn un93crppIopWivtT8UXGbG3NaOf//9xp3C04RhjQI41B6127gZXMw1wYmsuSYrdp +c/oLmFsNPYbp94ID3FSpZ2DfVENKie3F4SGKboDeZOlC6yckPZzu7I5RHHRzcKA UywkoAN77orMIU6RJyJn62k46pzMRwSy3mtoYP7O8wn83cluRLpMVfnQBnx8MB2+ T+HyQG7Urcm7xfHrOJpTK+pxMJ8wmxmITuL5NTzida2u7q7aUyFPN1UyBXCblBaF qt4Gn0rDo7WDJ5W4dM0J/wB1f12/CdMYF2rnCEBjvcv+fogd0+k= =DKy+ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: ts-node Source-Version: 9.1.1-1 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of ts-node, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated ts-node 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: Thu, 10 Dec 2020 14:02:28 +0100 Source: ts-node Architecture: source Version: 9.1.1-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Julien Puydt Closes: 976619 Changes: ts-node (9.1.1-1) experimental; urgency=medium . * Add runtime dependencies. (Closes: #976619) * New upstream release. * Bump std-vers to 4.5.1. * Update fix_compilation patch for newer upstream. Checksums-Sha1: cf24c40c75d983de60fd6b72f21c6b2712ead43c 2111 ts-node_9.1.1-1.dsc 8bb5b78bbdd0a7978e5f4c42765dafc60874ab2b 198768 ts-node_9.1.1.orig.tar.gz daf99f9c891c3ead6e84a7b434c12c93a5390042 4028 ts-node_9.1.1-1.debian.tar.xz 3c9cdd286d94a8ad27f5ca07c2731472680deccb 10176 ts-node_9.1.1-1_source.buildinfo Checksums-Sha256: 7212c69b963caa1d1a0b04753990ad6dc97e58cbce081ffcaf5a498b5ae07f0c 2111 ts-node_9.1.1-1.dsc 93ac9c688a66c14f3dc696861e33eddf33d7b824a34d8af16540b219ebcc8850 198768 ts-node_9.1.1.orig.tar.gz 3183a2e1affef96af08edcb486832753524e18f3955a42e3e6426a5c451b71de 4028 ts-node_9.1.1-1.debian.tar.xz 16425e0e3f57a86cda46feaff3638febf987a72cdc021e05190ccef8649ef8c6 10176 ts-node_9.1.1-1_source.buildinfo Files: 55c80d0964c3f340ee7d5c8608720ca8 2111 javascript optional ts-node_9.1.1-1.dsc dd7cc06056fe0714b6354ee248d1374d 198768 javascript optional ts-node_9.1.1.orig.tar.gz 958b9dcfcafd385ba094de866762a23b 4028 javascript optional ts-node_9.1.1-1.debian.tar.xz b6c9003d8a108d049452f5cd7e247f74 10176 javascript optional ts-node_9.1.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAl/SHMISHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRmmIQAJ2s+N97qE2pVxbff6UDjgRY5O4VeDhh 9fqCM/WPKWoQ+9v9YUCtDGwHrdf03yHzfZ0oTBk2TBFDYqNHMS+PgdzhCFC7xL9b hKvbbDmgPT9cmokPbE+n/t7GSLW6SUlEruRNMm2iATfo58nFKj+w1nsLU1PvFjSD qEhSTfAhn8Rpf4zy4diD3PbWS2KYPFwigRCAW2bYD4dB3wI1bnTpHIlMKC22IZRQ OiKBTUYpWv0nFSqG/+48GDti+gFGkFmQV+qi1o8h4viZ20iyneRcH5Izw/khWJir VkW9qsIVxds1l7/Nb5LsSgc4DkgJKT8u20hH+2Pt6DERbpG1Nt/rw62dO4TCHguY
Bug#977038: google-oauth-client-java: FTBFS: Failed to execute goal on project google-oauth-client: Could not resolve dependencies for project com.google.api-client:google-api-client:jar:1.27.1: Canno
Package: google-oauth-client-java Version: 1.28.0-1 Severity: serious This can likely be fixed with a build dependency on grpc-java [ERROR] Failed to execute goal on project google-oauth-client: Could not resolve dependencies for project com.google.oauth-client:google-oauth-client:jar:1.28.0: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact io.grpc:grpc-context:jar:debian has not been downloaded from it before. -> [Help 1]
Bug#976619: marked as pending in ts-node
Control: tag -1 pending Hello, Bug #976619 in ts-node reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/ts-node/-/commit/79aeb9d5e76194d8153cc23fdc010b4c443f2822 Add runtime dependencies (Closes: #976619) (this message was generated automatically) -- Greetings https://bugs.debian.org/976619
Processed: Bug#976619 marked as pending in ts-node
Processing control commands: > tag -1 pending Bug #976619 [ts-node] ts-node: required modules not declared as dependencies Added tag(s) pending. -- 976619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954270: [RFS] kmc: arm64 autopkgtest time out
Hi On 10-12-2020 13:10, Andreas Tille wrote: > On Thu, Dec 10, 2020 at 11:58:23AM +0100, Paul Gevers wrote: >>> In the kmc case I'm seriously wondering whether we should restrict >>> the architectures to those that are relevant in practice. It seems >>> to be in line with upstream and I'm tempted to follow Étienne's >>> suggestion to upgrade to kmc 3.x which does not even build on armhf >>> any more and remove the package for the non-building architectures. >>> >>> Étienne, would you mind pushing your patches to Git to proceed with >>> this plan? >> >> Shall I run the current package on our big amd64 host to check if it >> fails there and that part of problem is solved? I mean, I understand >> that there was a real problem with hosts that have lots of CPU's and I >> assume you support amd64. > > My guess is that kmc was developed under and designed for amd64 and it > runs there. That's explicitly the case for the latest upstream version > which will not support any arm* out of the box (if I understand Étienne > correctly). I do not see any need to stress test our hardware with > some software that will be outdated soonish. > > Kind regards > >Andreas. > > I couldn't resist. I started it up and it hangs. Paul root@ci-worker13:~# lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 48 On-line CPU(s) list: 0-47 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 2 NUMA node(s):2 Vendor ID: GenuineIntel CPU family: 6 Model: 79 Model name: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz Stepping:1 CPU MHz: 2200.074 CPU max MHz: 2900. CPU min MHz: 1200. BogoMIPS:4400.13 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:30720K NUMA node0 CPU(s): 0-11,24-35 NUMA node1 CPU(s): 12-23,36-47 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap intel_pt xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts flush_l1d root@ci-worker13:~# /usr/bin/autopkgtest --no-built-binaries '--setup-commands=echo '"'"'kmc testing/amd64'"'"' > /var/tmp/debci.pkg 2>&1 || true' --user debci --apt-upgrade '--add-apt-source=deb http://incoming.debian.org/debian-buildd buildd-unstable main contrib non-free' --add-apt-release=unstable --pin-packages=unstable=src:kmc kmc -- lxc --sudo --name elbrus autopkgtest-testing-amd64 [...] autopkgtest [12:45:12]: test build-lib: [--- g++ kmc_dump/*cpp -std=c++11 -lkmc -o $WORKDIR/my_kmcdump [ -x $WORKDIR/my_kmcdump ] echo "build: OK" cd $WORKDIR echo 'Running kmc (single threaded)' kmc -ci1 -m1 -k28 -t1 $ORIGDIR/debian/tests/sample_6.fastq.gz 1 . build: OK Running kmc (single threaded) * * 1st stage: 0.170529s 2nd stage: 0.041426s Total: 0.211955s Tmp size : 0MB Stats: No. of k-mers below min. threshold :0 No. of k-mers above max. threshold :0 No. of unique k-mers : 6435 No. of unique counted k-mers : 6435 Total no. of k-mers: 6714 Total no. of reads : 750 Total no. of super-k-mers : 1234 ls -Al total 1200 -rw-r--r-- 1 debci debci 1114204 Dec 10 12:45 1.kmc_pre -rw-r--r-- 1 debci debci 45053 Dec 10 12:45 1.kmc_suf -rwxr-xr-x 1 debci debci 63024 Dec 10 12:45 my_kmcdump [ -s 1.kmc_suf ] [ -s 1.kmc_pre ] echo "kmc (single threaded): OK" kmc (single threaded): OK ./my_kmcdump 1 out [ -s out ] echo "run: OK" run: OK # FIXME: uncomment the below test once kmc is updated to version 3.1.1 or more. ## Multi-threaded runs have been known to be faulty
Bug#954270: [RFS] kmc: arm64 autopkgtest time out
On Thu, Dec 10, 2020 at 11:58:23AM +0100, Paul Gevers wrote: > > In the kmc case I'm seriously wondering whether we should restrict > > the architectures to those that are relevant in practice. It seems > > to be in line with upstream and I'm tempted to follow Étienne's > > suggestion to upgrade to kmc 3.x which does not even build on armhf > > any more and remove the package for the non-building architectures. > > > > Étienne, would you mind pushing your patches to Git to proceed with > > this plan? > > Shall I run the current package on our big amd64 host to check if it > fails there and that part of problem is solved? I mean, I understand > that there was a real problem with hosts that have lots of CPU's and I > assume you support amd64. My guess is that kmc was developed under and designed for amd64 and it runs there. That's explicitly the case for the latest upstream version which will not support any arm* out of the box (if I understand Étienne correctly). I do not see any need to stress test our hardware with some software that will be outdated soonish. Kind regards Andreas. -- http://fam-tille.de
Bug#935313: missing ebtables dependency
Hi, @Gabriel, the BTS doesn't automatically forward replies to bugs to the submitter, if you want feedback, you need to send it manually. @Antoine, can you please give the feedback still? Paul On Fri, 23 Aug 2019 00:07:29 -0400 Gabriel Filion wrote: > Hello, > > On Wed, 21 Aug 2019 10:16:26 -0400 Antoine Beaupre > wrote: > > Vagrant, using the libvirt backend, started failing me recently, with > > something like this: > > > > anarcat@curie:stretch64(master)$ vagrant up --provider libvirt > > Bringing machine 'default' up with 'libvirt' provider... > > ==> default: Checking if box 'debian/stretch64' version '9.9.0' is up to > > date... > > Error while activating network: Call to virNetworkCreate failed: internal > > error: Failed to initialize a valid firewall backend. > > [1]anarcat@curie:stretch64(master)$ > > > Restarting libvirtd, however, did provide some insightful input: > > > > [...] > > aoû 21 10:10:05 curie systemd[1]: Started Virtualization daemon. > > aoû 21 10:10:05 curie libvirtd[31223]: direct firewall backend requested, > > but /usr/sbin/ebtables is not available: Aucun fichier ou dossier de ce type > > aoû 21 10:10:05 curie libvirtd[31223]: internal error: Failed to initialize > > a valid firewall backend > > fwiw I'm running vagrant + libvirt + vagrant-libvirt in debian sid and I > don't have the ebtables package installed. networking is still functioning. > > Since buster, nftables is now used by default. the iptables package is > now installing nftables wrappers so that one is not mixing nftables with > iptables kernel subsystems. > > # update-alternatives --list ebtables > /usr/sbin/ebtables-nft > > $ dpkg -S /usr/sbin/ebtables-nft > iptables: /usr/sbin/ebtables-nft > > that would explain why the libvirt package does not depend on the > ebtables package. > > > is it possible that your "alternative" for ebtables was somehow blasted > out? e.g. if you try removing the ebtables package and then running: > > # update-alternatives --set ebtables /usr/sbin/ebtables-nft > > does it make your libvirt setup function properly? > > if so, then maybe you might want to check other "alternatives" provided > by iptables so that they use the nftables wrappers. Here's what I have > on my system: > > $ ls -l /etc/alternatives/|grep -- -nft > lrwxrwxrwx 1 root root 23 Dec 22 2018 arptables -> /usr/sbin/arptables-nft > lrwxrwxrwx 1 root root 31 Dec 22 2018 arptables-restore -> > /usr/sbin/arptables-nft-restore > lrwxrwxrwx 1 root root 28 Dec 22 2018 arptables-save -> > /usr/sbin/arptables-nft-save > lrwxrwxrwx 1 root root 22 Dec 22 2018 ebtables -> /usr/sbin/ebtables-nft > lrwxrwxrwx 1 root root 30 Dec 22 2018 ebtables-restore -> > /usr/sbin/ebtables-nft-restore > lrwxrwxrwx 1 root root 27 Dec 22 2018 ebtables-save -> > /usr/sbin/ebtables-nft-save > lrwxrwxrwx 1 root root 23 Dec 22 2018 ip6tables -> /usr/sbin/ip6tables-nft OpenPGP_signature Description: OpenPGP digital signature
