Processed: debhelper: dh_installman error instead of warning on invalid section
Processing control commands: > affects -1 src:esys-particle Bug #962253 [src:debhelper] debhelper: dh_installman error instead of warning on invalid section Added indication that 962253 affects src:esys-particle > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 962252 960413 959573 960427 960412 960418 948122 960416 959463 949837 955581 954711 960414 962173 959417 962251 959437 960378 959479 959480 962229 954351 960383 960422 959439 953871 960426 948127 962070 960385 955579 954649 960424 962086 960500 953873 948407 960381 948281 960421 958156 954648 960331 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962253 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962253: debhelper: dh_installman error instead of warning on invalid section
Source: debhelper Version: 13.1 Severity: serious Control: affects -1 src:esys-particle Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=esys-particle ... dh_installman -a dh_installman: warning: Section for ./debian/esysparticle.1 is computed as "2012-12-30", which is not a valid section dh_installman: error: Could not determine section for ./debian/esysparticle.1 dh_installman: error: Aborting due to earlier error make: *** [debian/rules:15: binary-arch] Error 25 debhelper (13.1) unstable; urgency=low ... * dh_installman: Improve error messages and handling of broken section numbers. Notably ignore (with a warning) sections from manpages that look suspiciously like a version number. Thanks to Paul Gevers for reporting the bug. (Closes: #958343) ...
Processed: orthanc-mysql FTBFS with boost1.71
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 962229 948127 953871 960413 962070 960331 960378 955579 962086 960421 948122 962173 948281 959439 959437 959463 953873 960416 960427 960426 960418 960385 954711 960414 959479 960424 955581 960381 962251 959480 960412 960422 948407 958156 959573 959417 949837 960383 954649 954351 960500 954648 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962252 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962252: orthanc-mysql FTBFS with boost1.71
Source: orthanc-mysql Version: 2.0-2 Severity: serious Tags: ftbfs bullseye sid Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=orthanc-mysql ... -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found version "1.71.0") CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:182 (boost_find_component): boost_find_component Macro invoked with incorrect arguments for macro named: boost_find_component Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindBoost.cmake:443 (find_package) /<>/Build/Orthanc-1.5.2/Resources/CMake/BoostConfiguration.cmake:15 (find_package) /<>/Build/Orthanc-1.5.2/Resources/CMake/OrthancFrameworkConfiguration.cmake:417 (include) /<>/Resources/CMake/DatabasesFrameworkConfiguration.cmake:62 (include) /<>/Resources/CMake/DatabasesPluginConfiguration.cmake:21 (include) CMakeLists.txt:18 (include) orthanc-mysql builds an own copy of src:orthanc, and this copy does not have #953884 fixed.
Bug#962251: hugin: libboost-signals-dev no longer exists with boost1.71
Source: hugin Version: 2019.2.0+dfsg-1 Severity: serious Tags: ftbfs Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=hugin libboost-signals-dev no longer exists with boost1.71.
Processed: hugin: libboost-signals-dev no longer exists with boost1.71
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 960416 962173 962229 959480 960421 954648 960412 958156 953871 953873 959417 959479 949837 960424 960378 954711 960500 960427 948122 959437 955581 960418 960414 959463 960383 960381 962086 948281 955579 960331 959439 959573 960426 960413 954649 954351 948127 960385 948407 960422 962070 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962251 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962250: monero: Please skip hash-variant2-int-sqrt on armel
Source: monero Version: 0.15.0.5-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=monero=armel ... 16/17 Test #7: block_weight . Passed 274.59 sec E: Build killed with signal TERM after 300 minutes of inactivity The non-failing build of 0.15.0.5-2 was: 17/17 Test #17: hash-variant2-int-sqrt ... Passed 17893.94 sec 17893 seconds is narrowly below 5 hours, and this was on a faster buildd. For 0.16.0.0-1 the test passed on identical hardware as the armel failure on armhf - in slightly over an hour. armel has no FPU and no native atomics instructions in the baseline. Please disable this (passing) test on armel.
Bug#962081: marked as done (gnucobol: Failing autopkgtest scripts should report what went wrong)
Your message dated Fri, 05 Jun 2020 02:42:28 + with message-id and subject line Bug#962081: fixed in gnucobol 3.0~rc1-3 has caused the Debian Bug report #962081, regarding gnucobol: Failing autopkgtest scripts should report what went wrong 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.) -- 962081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnucobol Version: 3.0~rc1-2 Severity: serious Tags: patch Several of the automatic tests provided in debian/tests/ currently fail. I am unable to see from the logs what go wrong, but the failure block the package from migrating into testing. When I run the scripts locally, they work. The tests should be fixed to work also in the CI infrastructure. I propose the following patch to make it easier to figure out from the logs what is going wrong: diff --git a/debian/tests/test01 b/debian/tests/test01 index 22d943e..e8f2fc1 100755 --- a/debian/tests/test01 +++ b/debian/tests/test01 @@ -11,6 +11,7 @@ if [ $res ] ; then echo "success: test01 produced proper results" else echo "error: test01 did not produce proper results" +diff -u test01.exp test01.act fi exit $res diff --git a/debian/tests/test02 b/debian/tests/test02 index 2e06f74..ee6caa9 100755 --- a/debian/tests/test02 +++ b/debian/tests/test02 @@ -11,6 +11,7 @@ if [ $res ] ; then echo "success: test02 produced proper results" else echo "error: test02 did not produce proper results" +diff -u test02.exp test02.act fi exit $res diff --git a/debian/tests/test03 b/debian/tests/test03 index f378787..fedf826 100755 --- a/debian/tests/test03 +++ b/debian/tests/test03 @@ -11,6 +11,7 @@ if [ $res ] ; then echo "success: test03 produced proper results" else echo "error: test03 did not produce proper results" +diff -u test03.exp test03.act fi exit $res diff --git a/debian/tests/test04 b/debian/tests/test04 index 04b325e..ff3a33d 100755 --- a/debian/tests/test04 +++ b/debian/tests/test04 @@ -11,6 +11,7 @@ if [ $res ] ; then echo "success: test04 produced proper results" else echo "error: test04 did not produce proper results" +diff -u test04.exp test04.act fi exit $res -- Happy hacking Petter Reinholdtsen --- End Message --- --- Begin Message --- Source: gnucobol Source-Version: 3.0~rc1-3 Done: Al Stone We believe that the bug you reported is fixed in the latest version of gnucobol, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Al Stone (supplier of updated gnucobol 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, 04 Jun 2020 20:10:37 -0600 Source: gnucobol Binary: gnucobol gnucobol-dbgsym libcob4 libcob4-dbgsym libcob4-dev open-cobol Architecture: source amd64 all Version: 3.0~rc1-3 Distribution: unstable Urgency: medium Maintainer: Al Stone Changed-By: Al Stone Description: gnucobol - COBOL compiler libcob4- COBOL compiler - runtime library libcob4-dev - COBOL compiler - development files open-cobol - transitional dummy package for gnucobol Closes: 962081 Changes: gnucobol (3.0~rc1-3) unstable; urgency=medium . * Make some adjustments to the autopkgtest scripts to capture failures better, using the patch supplied with some minor tweaks. Closes: #962081 Checksums-Sha1: 5e8aad8cd596efd40b0fa091ca64df435a128495 2035 gnucobol_3.0~rc1-3.dsc 22bf79d1618f6a5ecaf796ae093adf9969c8a773 18972 gnucobol_3.0~rc1-3.debian.tar.xz 5b510bcdfadd20e59ace43c9e753b30b2fb9ad42 808752 gnucobol-dbgsym_3.0~rc1-3_amd64.deb a8a4f4e189b4f86c84f3be923ea8d25df2d1a831 9110 gnucobol_3.0~rc1-3_amd64.buildinfo 13f6d2ca7b1686070c9afbff63adcb2fbc431fd4 820336 gnucobol_3.0~rc1-3_amd64.deb 75a40a43d4c6f4fb45ef59204a66d590e3996b66 431104 libcob4-dbgsym_3.0~rc1-3_amd64.deb 6fdda078567145074dcd2218d8fcce3e612563d0 193332 libcob4-dev_3.0~rc1-3_amd64.deb 7e3c130b84abb79dc225e4fce6e7a96808432262 159360 libcob4_3.0~rc1-3_amd64.deb 281a607d148b4ec46242eee9da0cd3c25062 12908 open-cobol_3.0~rc1-3_all.deb
Bug#961705: marked as done (pmount: autopkgtest failure: /usr/bin/pmount: Permission denied)
Your message dated Fri, 05 Jun 2020 01:20:16 + with message-id and subject line Bug#961705: fixed in pmount 0.9.23-5 has caused the Debian Bug report #961705, regarding pmount: autopkgtest failure: /usr/bin/pmount: Permission denied 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.) -- 961705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pmount Version: 0.9.23-4 X-Debbugs-CC: debian...@lists.debian.org, jmsrdeb...@protonmail.com Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package pmount, 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. Seems like you need a needs-root restriction. Side note: The package seems to contain a test suite. Why not run that as well during autopkgtesting? 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=pmount https://ci.debian.net/data/autopkgtest/testing/amd64/p/pmount/5574383/log.gz autopkgtest [07:31:38]: test command1: [--- bash: /usr/bin/pmount: Permission denied autopkgtest [07:31:39]: test command1: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pmount Source-Version: 0.9.23-5 Done: Jair Reis We believe that the bug you reported is fixed in the latest version of pmount, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jair Reis (supplier of updated pmount 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, 04 Jun 2020 08:04:42 -0300 Source: pmount Architecture: source Version: 0.9.23-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Jair Reis Closes: 961705 Changes: pmount (0.9.23-5) unstable; urgency=medium . * QA upload. * debian/control: added the field Homepage. * debian/copyright: - Migrated to 1.0 format. - Update all data. * debian/patches/01-man-plugdev.diff: added the 'Authors' and 'Last-Update' fields. * debian/patches/10_fix-spelling-binary-errors.patch: created to fix some spelling errors. * debian/patches/20_fix-spelling-manpage-error.patch: created to fix spelling error. * debian/pmount.install: updated to fix the lintian package-installs-into-obsolete-dir. * debian/tests/control: added 'needs-root' to Restriction field. (Closes: #961705) Checksums-Sha1: 4d4471b51fa8150eadb15cde16fb315f69f50347 1800 pmount_0.9.23-5.dsc dee710f1aca0de6b5ce064d27016cc5db9392f0f 11784 pmount_0.9.23-5.debian.tar.xz 8da147ac99d4da30eac262c2773cfb6d063c3a2e 6966 pmount_0.9.23-5_source.buildinfo Checksums-Sha256: 4075b8ba6fb84a06b0b9116682a14cf4611b0615dfd142a5c625fa3a2c651f81 1800 pmount_0.9.23-5.dsc 5cb8fe1d54cd9a13fe4c16eeec75e3b3bd79f38ecdd11a7804d0f7e08fb68638 11784 pmount_0.9.23-5.debian.tar.xz 00f927a631d4e3ad48e33678b4d7dad2550cd9eee4de8c7732fc86b8fb55e444 6966 pmount_0.9.23-5_source.buildinfo Files: 6cb922c60563539e8401c42da0c17709 1800 utils optional pmount_0.9.23-5.dsc 70e49c4f055e3e436781bf61e5ea2601 11784 utils optional pmount_0.9.23-5.debian.tar.xz 40bc3924fe964544b9610e4ba909395c 6966 utils optional pmount_0.9.23-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl7ZmWoACgkQ3mO5xwTr 6e+EOA/9GXuHBU2vnY/wrlSnpoOiURms2X/9HfXaOwIjMG5ctGN7AxGOSKGqOY7H 0dDScMteCgnMAaxqF8FrsGQc0+lXhB/k5v2ysNYlz5gDoIPWBDHfXw4u8vuudP85 boJ1dWcYjzKxGDo4OXubcJVJPP5JVsta7D7weq0wSVuwy8r+shudHptWNwa+fce6 A7RErxrLHWiJwmzi2Q+pYHqrheSDyogewA07p2IN/MYjLkIdEwvJiPMs7CliwTHV 0pI4c33tT/wfRQqJrF+LfswUDuVlW1YBu9GwTv40DjAmLM7cLZv3fji40d8ANVpG nsWx8yZEEL7hiqIuPqAlGx5ga+mh43JNpsH8x1FzMtA45aSWI7O3VIPIa7gdUc9I
Bug#953871: marked as done (FTBFS with Boost 1.71)
Your message dated Fri, 05 Jun 2020 00:52:34 + with message-id and subject line Bug#953871: fixed in plee-the-bear 0.6.0-7 has caused the Debian Bug report #953871, regarding FTBFS with Boost 1.71 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.) -- 953871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plee-the-bear Version: 0.6.0-6 Severity: wishlist Tags: patch User: team+bo...@tracker.debian.org Usertags: boost1.71 Dear Maintainer, your package fails to build with boost1.71. If you want to attempt the build yourself, an updated version of boost-defaults which brings in boost1.71 dependencies can be found adding this line to your sources.list file: deb https://people.debian.org/~gio/reprepro gio main This bug has severity whishlist for the moment, but it will raised to RC as soon as version 1.71 of Boost is promoted to default. More specifically, your package fails building because it uses the old libboost-signals-dev package, which has now disappeared. The attached patch should fix the bug. Thanks and all the best, Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles From 6a23544a8d2d932f02d68f1d314707f4fd47e49b Mon Sep 17 00:00:00 2001 From: Giovanni Mascellani Date: Sat, 14 Mar 2020 11:08:04 +0100 Subject: [PATCH] Fix FTBFS with Boost 1.71. --- debian/changelog | 7 debian/control| 1 - .../0008-Fix-FTBFS-with-Boost-1.71.patch | 36 +++ debian/patches/series | 1 + 4 files changed, 44 insertions(+), 1 deletion(-) create mode 100644 debian/patches/0008-Fix-FTBFS-with-Boost-1.71.patch diff --git a/debian/changelog b/debian/changelog index e82a372..442251a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +plee-the-bear (0.6.0-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Do not depend on libboost-signals-dev, that does not exit any more. + + -- Giovanni Mascellani Sat, 14 Mar 2020 11:07:48 +0100 + plee-the-bear (0.6.0-6) unstable; urgency=medium * Team upload. diff --git a/debian/control b/debian/control index 39d2804..6881ca0 100644 --- a/debian/control +++ b/debian/control @@ -13,7 +13,6 @@ Build-Depends: debhelper-compat (= 12), libboost-filesystem-dev (>= 1.45), libboost-regex-dev (>= 1.45), libboost-thread-dev (>= 1.45), - libboost-signals-dev (>= 1.45), mesa-common-dev (>= 6.5), libclaw-dev (>= 1.7.0), libclaw-graphic-dev (>= 1.7.0), diff --git a/debian/patches/0008-Fix-FTBFS-with-Boost-1.71.patch b/debian/patches/0008-Fix-FTBFS-with-Boost-1.71.patch new file mode 100644 index 000..2a2d39c --- /dev/null +++ b/debian/patches/0008-Fix-FTBFS-with-Boost-1.71.patch @@ -0,0 +1,36 @@ +From: Giovanni Mascellani +Date: Sat, 14 Mar 2020 11:11:32 +0100 +Subject: Fix FTBFS with Boost 1.71. + +In Boost 1.71 the Signals library has disappears in favour or Signals2. +--- + bear-engine/CMakeLists.txt | 2 +- + plee-the-bear/CMakeLists.txt | 2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/bear-engine/CMakeLists.txt b/bear-engine/CMakeLists.txt +index e65f040..3054347 100644 +--- a/bear-engine/CMakeLists.txt b/bear-engine/CMakeLists.txt +@@ -50,7 +50,7 @@ link_directories( + include(FindBoost) + + find_package( +- Boost 1.42 REQUIRED COMPONENTS filesystem regex signals system thread ++ Boost 1.42 REQUIRED COMPONENTS filesystem regex system thread + ) + if( NOT Boost_FOUND ) + message( FATAL_ERROR +diff --git a/plee-the-bear/CMakeLists.txt b/plee-the-bear/CMakeLists.txt +index ab6d7be..04f886f 100644 +--- a/plee-the-bear/CMakeLists.txt b/plee-the-bear/CMakeLists.txt +@@ -88,7 +88,7 @@ link_directories( + # Boost + include(FindBoost) + +-find_package( Boost 1.35 REQUIRED COMPONENTS signals) ++find_package( Boost 1.35 REQUIRED COMPONENTS) + + if( NOT Boost_FOUND ) + message( FATAL_ERROR diff --git a/debian/patches/series b/debian/patches/series index 9b147a8..aa6d850 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -5,3 +5,4 @@ ptb-signals-v2.diff full-path-menu-icon.diff wx3.0-compat.patch absolute-path-in-desktop-file.patch +0008-Fix-FTBFS-with-Boost-1.71.patch -- 2.25.1 signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: plee-the-bear Source-Version: 0.6.0-7 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of plee-the-bear, which is due to
Bug#937769: python-funcsigs build-dependencies now unsatisfiable in testing, removal of pypy-pytest
On 04/06/2020 23:12, Thomas Goirand wrote: On 6/4/20 10:33 PM, peter green wrote: A few days ago Sandro Tosi uploaded the python-unittest2 and python-funcsigs source packages. It seems that both of these were effectively "team uploads" though they were not marked as such. A few years ago, I've been flamed, them banned from the DPMT for less than this... Though I don't think we should put the blame on Sandro. He did a lot and we should be thankful for his work on Python 2 removal. I'm not looking to place blame on anyone here, I am just looking to get broken build-dependencies in testing dealt with. The thing is, funcsigs is a backport of the PEP 362 function signature features from Python 3.3's inspect module (as per the package description), so it should in fact go away if possible. I don't have any objection to it going away as long as the reverse-dependencies are dealt with. It's now down to four rdeps, two of which (pagure and nipype) are not in testing and one of which (kombu) is tagged pending with you on the uploaders list. I'm really not sure what's going to be the faith of pypy-pytest, maybe it should be replaced by pypy3-pytest? If I remember well the discussion, we wrote that we would just disable the tests for things depending on python 2 test suites. Maybe this includes pypy-pytest? Earlier in the discussion on bug 937769 the following was posted by Stefano Rivera (pypy maintainer) Stefano> pypy itself (the python 2.7 pypy) will continue to exist for the Stefano> foreseeable future, to support building pypy3. But we don't need to ship Stefano> modules for it. I'd be pretty happy if we had working virtualenv, and Stefano> nothing else. And the following was posted by Ondřej Nový (pytest maintainer) Ondřej> I'm perfectly fine with removing pypy-pytest binary package and all other Ondřej> dependencies in chain. It's painfull to maintain it. Based on this it seemed that getting rid of pypy-pytest was the desired way forward. I went through the reverse (build-)depends of pypy-pytest and thier transitive reverse (build-)depends, making the assumption that if the pypy- package was removed from a source package the build-dependencies on any pypy package could also be removed. I concluded that in order for pypy-pytest to go away. * The pypy-atomicwrites, pypy-pluggy, pypy-py pypy-setuptools-scm pypy-wcwidth pypy-importlib-metadata and pypy-zipp binary packages need to go away (or alternatively have their tests disabled). These packages are involved in build-dependency loops with pytest, so they need to be dealt with at the same time as pypy-pytest. All of these have the debian python maintainers team in the maintainer field which according to the team policy indicates "Team in ``Maintainers`` is a strong statement that fully collaborativemaintenance is preferred. Anyone can commit to the Git repository and uploadas needed" so dealing with these as a block should not be an issue. * vanguards needs to stop build-depending on pypy-pytest According to the discussion over at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932820 vanguards uses pypy for performance reasons, the long term goal would be to move to pypy3 but there are (or at least were when that bug was last active) apparently some tooling issues. I filed bug 958848 on pytest ccing the vanguards maintainers, Chris Lamb (part of the team that maintains vanguards but not directly involved in it's maintenance) responded suggesting the possibility of running the vanguards testsuite under python3. Obviously running the testsuite with a different version of python from that which will be used on the running system is sub-optimal, but it's probably better than not running the tests at all. I took Chris's patch, tested that it builds the package succesfully, prepared a debdiff and posted a rc bug report on vanguards. I am now waiting to see if the maintainer responds.
Bug#962158: lintian: New very problematic --fail-on default value
On Thu, 2020-06-04 at 15:58:47 -0700, Felix Lechner wrote: > > This change means that any current caller which uses lintian as part > > of its acceptance testing will now silently let broken things through > > As I explained on IRC this statement is probably untrue (and you did > not have the courtesy to mention that objection here). Err… > From what I can > tell, the FTP Master (who are arguably the one "acceptance tester" who > really matters) parses the tags. [1] Please let me know if you know > otherwise. As mentioned already on IRC and in the original report, at least all the tools I listed are affected, including any local setup, in-house CI deployments, CI integration in source forges (local and public, including salsa), etc. And also as mentioned on IRC, it does not make any sense whatsoever to set such a default for a single user who can just change their code base once, instead of forcing the entire ecosystem, within Debian, its derivatives, and local and private setups to adapt to this change. Considering ftp-masters the only acceptance tester that really matters is a very Debian-centric view that does not match reality. Not to mention that it does not even make sense within a Debian-centric view, as now maintainers uploading to Debian, which rely on lintian to check for brokenness that ftp-masters does not consider fatal, will start uploading such broken packages into the archive… > > If the default change made sense due to some technical rationale, this > > effort might be worthwhile > > As I likewise explained on IRC, Lintian's return status was > unreliable. Some program errors exited with status 1 and others with > status 2, while detecting error tags always produced status 1. Lintian > was also unable to use Perl's 'die'. The proper remedy was to always > use status 1 for program errors. That step alone would require any > automated user to examine their scripts. And as mentioned on IRC, this also has little to do with the default change. When you run lintian and it fails for any reason, be it internal or from linting issues, people in general really want to fail the acceptance test, so that if it is an internal error it can be analyzed, reported, or worked around. In the same way people do not ignore gcc ICE (internal compiler errors) in contrast to syntax errors. So there's really no reason at all in general to be changing callers to special case lintian failing internally. > The 'fail-on' command-line option resolved a long standing problem > with the implicit behavior your so cherish (#709932). Also as mentioned on IRC adding this option has nothing whatsoever to do nor it requires changing the default. > Instead of > adding more complex options, the current solution is simple, elegant, > straighforward and explicit. If with the current solution you mean the default change, then I'll have to very much disagree. That change is just wrong. And you have still not explained what this default change really accomplishes, besides inducing tons of work and breakage, and letting a single caller (DAK) avoid having to add the new option. > And again, automated users already had to > look at their scripts. It was the perfect timing to make both changes. No, they did not. Thanks, Guillem
Bug#962138: marked as done (perl-base: libperl5.30 version skew can break essential functionality)
Your message dated Thu, 04 Jun 2020 23:34:00 +
with message-id
and subject line Bug#962138: fixed in perl 5.30.3-2
has caused the Debian Bug report #962138,
regarding perl-base: libperl5.30 version skew can break essential functionality
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.)
--
962138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl-base
Version: 5.30.2-1
Severity: serious
Our Perl package dependencies and search path arrangements allow
for a suitably versioned libperl5.30 package to break perl-base
functionality. This is bad as perl-base is Essential:yes and is therefore
required to stay functional at all times.
The specific version skew that triggers this is between minor upstream
versions, so for instance 5.30.2-1 -> 5.30.3-1, which are the current
version in testing and unstable.
The transcript at the end, from a current bullseye chroot with perl-base
and libperl5.30 but no perl installed, shows how perl-base can be
upgraded from sid without touching the other packages. After this, the
standard library in libperl5.30 is different version from perl-base but
has preference on the search path, causing version check bailouts and
breaking perl-base.
This works in the other direction too: if a newer version of libperl5.30
is unpacked, perl-base stops working in the same way. However,
the versioned dependency chain libperl5.30 -> perl-modules-5.30 (>=
${source:Version}) -> perl-base (>= ${Upstream-Version}-1) means that
libperl5.30 can't be configured in this combination.
The initial FTBFS of 5.30.3-1 on an arch:all sid buildd briefly resulted
in ideal conditions for this bug to trigger: unstable/amd64 then had
perl-modules-5.30 at version 5.30.2-1, but libperl5.30 and perl-base
at 5.30.3-1. Systems without the perl binary package were at that point
prone to upgrade to the newer perl-base while keeping perl-modules-5.30
and libperl5.30 at the old version. The autopkgtest checks of hkgerman
hit this when /usr/sbin/update-dictcommon-aspell (in dictionaries-common)
broke.
https://ci.debian.net/data/autopkgtest/testing/arm64/h/hkgerman/5736806/log.gz
It's not clear to me what the practical effects of this issue are.
Pretty much all real systems have the perl binary package installed,
which seems to make apt unpack libperl5.30 and perl-base very close to
each other. We haven't had any upgrade failure reports from the recent
5.30.0 -> 5.30.1 upgrade FWIW.
Minor upstream version upgrades in testing/unstable have been relatively
rare in the past, and oldstable -> stable upgrades have always
incorporated a major version bump since the 5.10 times (squeeze), when
the dependencies and the package set were very different.
In any case, I think this needs to be fixed and should probably be
considered release critical.
I'm afraid this also means that a minor upstream version upgrade
in stable has a higher risk of breaking things, so maybe we should
reconsider #961443.
I see two ways of fixing this (but happy to entertain other suggestions too).
A) Move /usr/lib//perl-base up on the @INC search path. This is
shipped in perl-base and includes the parts of the standard library
we consider part of Essential:yes functionality. It's currently last
on @INC. The libperl5.30 and perl-modules-5.30 packages include copies
of these files, shipped in /usr/{lib,share}//perl/5.30,
so that they can be used "standalone" for different architectures or
major versions. The position of these copies higher on @INC makes this
bug possible.
IIRC I put /usr/lib//perl-base last because it's a nonstandard
divergence from the upstream way of doing things, and I wanted it not
to have an effect in the "normal" case when all the related packages
are installed and configured. So it was only supposed to be a safeguard
during upgrades and such. Clearly the safeguard is incomplete.
B) Do away with the /usr/{share,lib/x86_64-linux-gnu}/perl/5.30 -> 5.30.x
symlinks currently shipped in libperl5.30 and perl-modules-5.30,
and have the perl search path include the full upstream version. We
tried this with the multiarch changes in 5.22 but reverted it with
#787158 . As I noted in that bug, this would mean that long running
Perl programs could have @INC changed underneath them during version
upgrades. This is not a showstopper by any means; we already have the
'perl-major-upgrade' trigger for similar situations during major
version upgrades, with at least some buy-in from packages like
Bug#962019: marked as done (perl: build fails on IPv6-only buildds)
Your message dated Thu, 04 Jun 2020 23:34:00 + with message-id and subject line Bug#962019: fixed in perl 5.30.3-2 has caused the Debian Bug report #962019, regarding perl: build fails on IPv6-only buildds 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.) -- 962019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perl Version: 5.30.3-1 Severity: serious Justification: FTBFS Hi Dom an Niko Guess you have seen it but filling a bug for tracking. arch:all build failed on buildd: https://buildd.debian.org/status/fetch.php?pkg=perl=all=5.30.3-1=1591057198=0 Regards, Salvatore --- End Message --- --- Begin Message --- Source: perl Source-Version: 5.30.3-2 Done: Dominic Hargreaves We believe that the bug you reported is fixed in the latest version of perl, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominic Hargreaves (supplier of updated perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 05 Jun 2020 00:21:01 +0100 Source: perl Architecture: source Version: 5.30.3-2 Distribution: unstable Urgency: medium Maintainer: Niko Tyni Changed-By: Dominic Hargreaves Closes: 961928 962019 962138 Changes: perl (5.30.3-2) unstable; urgency=medium . [ Niko Tyni ] * Fix version parsing logic in a maintainer test. * Move perl-base specific library up on @INC. This eliminates the chance of incompatible libperl5.xx modules overriding the perl-base ones during upgrades and the like. (Closes: #962138) . [ Dominic Hargreaves ] * Remove lingering references to old deprecated modules (Closes: #961928) * Fix FTBFS with IPv6-only host (Closes: #962019) Checksums-Sha1: 04d280daa18aba74aac85b6c2aaf6413a5c2f1f4 2868 perl_5.30.3-2.dsc 41249f7a57a5f3b8125bd913c28f860ccfcf26a8 168796 perl_5.30.3-2.debian.tar.xz b89002877ca7201819ebf10ec081369d097668ed 5903 perl_5.30.3-2_source.buildinfo Checksums-Sha256: ca6ead446373fc9883039a47db73c30b388dc4915eace71824f005bd106d5b75 2868 perl_5.30.3-2.dsc 099d7356599abac86d9fb0f0182fb80601691f679a1c165f20dc729a76fdac2e 168796 perl_5.30.3-2.debian.tar.xz 34fcf99e71b6ad905b0054b1f9e7a58bb68bd1fb99894077418ea377350489a6 5903 perl_5.30.3-2_source.buildinfo Files: 6e8b5ab1bd3ec1c96d7ffc32877d69d4 2868 perl standard perl_5.30.3-2.dsc 9c0274a203867bfd59c1676cccd323f7 168796 perl standard perl_5.30.3-2.debian.tar.xz fbbc9039e95bda507bf477b169bd73df 5903 perl standard perl_5.30.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJBBAEBCAArFiEEy0llJ/kAnyscGnbawAV+cU1pT7IFAl7Zgj8NHGRvbUBlYXJ0 aC5saQAKCRDABX5xTWlPslQ7EACz8JQkYavgVUueJChc2AgNT87M7aiSAfP7IrD6 Rk+NFWYewM5KFiCPCX/bg7rZ9iU4gi9LbS8cx50uNE/LAlUn2UmX4M+dY336o3Jr VTD7Ue69gxMnHgcRUjz6hPrzQxtjS3pzKnxdg5OzxVqfRBFmIEy2yddGZyX+zgwy Ns0xouxJ7+eFx05kXWRoJm2myUs4qhtUof/KRfRT8P1gf/Evfj6MLV8fJxqXS3zS 7TCXfSxII/SXtM8utmGDMIlhu0mWoMNVStfO5HzQ836UN08VMA9GvRglARIB+6VM 6KLUfXMv5iRbFQBaVPOLkCU/87jGwmTjim+lNI4UaXEeH0GxdPP9QDp2OGzkTOzt 3a49USJioYyCOKe8qx5+WjeC4OY9Cg3A7gIeiJ8wqWzIaymJSQUK7vxbJjKaqMB9 YsKjsGH1czLXnifWHm9URC4VQCQeLsXYJW10FeUlZGqcfsyUFDM44s09GYlVC+Hv zAz2I6vr7xVGo+w9rYCh9y6zbvla+ev92fgq4a6ZhnQhNQv64T9UAkjndBFP7k9R PRB9Ug1ZR0XuigbsitRLSTfdjW0vY686tz6FgrQQLGbl6Gtkm6G0ooNE0sCCNvn5 /Jb2m4kYQko/o9MnOb/COa8kSiiAz02Hx1EqyMtG+FIti22jrw4fupFFcyGdQ9L/ QzN/4g== =OGxv -END PGP SIGNATURE End Message ---
Processed: tagging 954351
Processing commands for cont...@bugs.debian.org: > tags 954351 + ftbfs Bug #954351 [rdkit] FTBFS with Boost 1.71 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 954351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962073: alsa-info is calling home without asking
On Wed, 3 Jun 2020 17:26:27 +0200 Elimar Riesebieter wrote: > What do you mean with "call home"? Access the Internet without the consent of the person running it. > There is indeed a new version available in [0] and [1]. It will be > contributed witch the next release of alsa-utils. So what makes this > "bug" serious? The bug is a privacy violation. https://wiki.debian.org/PrivacyIssues -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#959798: marked as done (libjs-webrtc-adapter: Build with babel version 7)
Your message dated Thu, 04 Jun 2020 23:03:43 + with message-id and subject line Bug#959798: fixed in libjs-webrtc-adapter 7.6.1~ds-1 has caused the Debian Bug report #959798, regarding libjs-webrtc-adapter: Build with babel version 7 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.) -- 959798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjs-webrtc-adapter Version: 7.5.1~ds-1 Severity: important Control: tags -1 patch Hi Jonas, I'm planning to upload node-grunt-babel 8.0 in unstable (it is in experimental currently). I have fixed all the reverse build dependencies and this is the only remaining blocker. I have fixed this package in babel7 branch of salsa. Let me know if you are ok with the changes in babel7 branch so I can upload node-grunt-babel 8.0 to unstable. Commit that switches to babel 7 for build: https://salsa.debian.org/js-team/libjs-webrtc-adapter/-/commit/166b07b0ebf8a39569bea77ae23eb1246fa91b38 --- End Message --- --- Begin Message --- Source: libjs-webrtc-adapter Source-Version: 7.6.1~ds-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of libjs-webrtc-adapter, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated libjs-webrtc-adapter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jun 2020 00:42:42 +0200 Source: libjs-webrtc-adapter Architecture: source Version: 7.6.1~ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 959798 Changes: libjs-webrtc-adapter (7.6.1~ds-1) unstable; urgency=medium . [ upstram ] * new release(s) . [ Jonas Smedegaard ] * watch: fix syntax * add patch cherry-picked upstream to not remove extmap-allow-mixed in current safari * add superficial skip-not-installable eslint autopkgtest * use rollup; build-depend on node-rollup-plugin-commonjs node-rollup-plugin-node-resolve rollup (not node-browserify-lite); * use babel7: + update babeljs presets; + build-depend on node-babel7 (not node-babel-cli node-babel-preset-env) closes: bug#959798, thanks to Pirate Praveen Checksums-Sha1: 81bfc7e2f669e9489126d3fb36016ac74c52f096 2452 libjs-webrtc-adapter_7.6.1~ds-1.dsc 695ac4fc0fb1c68e35377997b2ed99b2908dd9f0 39024 libjs-webrtc-adapter_7.6.1~ds.orig.tar.xz b884e37aa19c52b86bcc7eed6634abc61d65617e 6484 libjs-webrtc-adapter_7.6.1~ds-1.debian.tar.xz d63e68877ebc2f22774f149b9beee2e1b5666170 13257 libjs-webrtc-adapter_7.6.1~ds-1_amd64.buildinfo Checksums-Sha256: 1d3cd955e6ad2046fbbf8353139cf03615d94e0b7a45efbefe9ea00606a05f08 2452 libjs-webrtc-adapter_7.6.1~ds-1.dsc 62f93e86ecf053bca3d3a0f5a9dc0720e4f37a04ea3415d5b2738003778f120f 39024 libjs-webrtc-adapter_7.6.1~ds.orig.tar.xz 17a485920c20f657712b0b3359d8a37aba1a43b0ab8fc8f14f9f0f7bf59e4246 6484 libjs-webrtc-adapter_7.6.1~ds-1.debian.tar.xz 797de5c19f469cc4fb7b660f8b6382f74125e0a0594750d0d94a7918e8198c11 13257 libjs-webrtc-adapter_7.6.1~ds-1_amd64.buildinfo Files: 0977fe17cdabb45bde55ebd7fb6df2cb 2452 javascript optional libjs-webrtc-adapter_7.6.1~ds-1.dsc e752dcab295366588bbd118717a2d76d 39024 javascript optional libjs-webrtc-adapter_7.6.1~ds.orig.tar.xz d99e03d86d0b56bcc2ca26686da668bb 6484 javascript optional libjs-webrtc-adapter_7.6.1~ds-1.debian.tar.xz e7078903b65ce29383b192bbad519412 13257 javascript optional libjs-webrtc-adapter_7.6.1~ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7ZeqEACgkQLHwxRsGg ASGajxAApUIOQlsbJpxCgeUEHrZJuIiEBDE1GXzV50oJaP0P6XpYMkuYXxxIgLz3 ZFGj/uE1RwZoeftwk68oHdq6XoBknL1oygo9BnTzDXjev9T8YB6Kakxzo/zWDmoU 4Fs/u78Hk6zmkziY9KaF/uUQdwoGp78+D+V9Jle8dOf1VDM/awsef6dzKMDVb8Fj HlMl4kn4GVj0qdNhFRDiRPtjaFdncGIGx3bMCiDb1J6tU/c8HebDoSZkS1pkNsmR Vd+We15IQsgc0/t67Dbd97wPks9tO/Qi1RjGFFxAKLZHXMBd3kr6NwF8fbNgoBFp
Bug#960264: marked as done (libjs-webrtc-adapter: Please remove dependency to node-babel-preset-env)
Your message dated Thu, 04 Jun 2020 23:03:43 + with message-id and subject line Bug#959798: fixed in libjs-webrtc-adapter 7.6.1~ds-1 has caused the Debian Bug report #959798, regarding libjs-webrtc-adapter: Please remove dependency to node-babel-preset-env 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.) -- 959798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjs-webrtc-adapter Severity: important Hi, please remove dependency to node-babel-preset-env: this package seems useless with node-babel7 and is going to be removed with node-babel 6. --- End Message --- --- Begin Message --- Source: libjs-webrtc-adapter Source-Version: 7.6.1~ds-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of libjs-webrtc-adapter, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated libjs-webrtc-adapter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jun 2020 00:42:42 +0200 Source: libjs-webrtc-adapter Architecture: source Version: 7.6.1~ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 959798 Changes: libjs-webrtc-adapter (7.6.1~ds-1) unstable; urgency=medium . [ upstram ] * new release(s) . [ Jonas Smedegaard ] * watch: fix syntax * add patch cherry-picked upstream to not remove extmap-allow-mixed in current safari * add superficial skip-not-installable eslint autopkgtest * use rollup; build-depend on node-rollup-plugin-commonjs node-rollup-plugin-node-resolve rollup (not node-browserify-lite); * use babel7: + update babeljs presets; + build-depend on node-babel7 (not node-babel-cli node-babel-preset-env) closes: bug#959798, thanks to Pirate Praveen Checksums-Sha1: 81bfc7e2f669e9489126d3fb36016ac74c52f096 2452 libjs-webrtc-adapter_7.6.1~ds-1.dsc 695ac4fc0fb1c68e35377997b2ed99b2908dd9f0 39024 libjs-webrtc-adapter_7.6.1~ds.orig.tar.xz b884e37aa19c52b86bcc7eed6634abc61d65617e 6484 libjs-webrtc-adapter_7.6.1~ds-1.debian.tar.xz d63e68877ebc2f22774f149b9beee2e1b5666170 13257 libjs-webrtc-adapter_7.6.1~ds-1_amd64.buildinfo Checksums-Sha256: 1d3cd955e6ad2046fbbf8353139cf03615d94e0b7a45efbefe9ea00606a05f08 2452 libjs-webrtc-adapter_7.6.1~ds-1.dsc 62f93e86ecf053bca3d3a0f5a9dc0720e4f37a04ea3415d5b2738003778f120f 39024 libjs-webrtc-adapter_7.6.1~ds.orig.tar.xz 17a485920c20f657712b0b3359d8a37aba1a43b0ab8fc8f14f9f0f7bf59e4246 6484 libjs-webrtc-adapter_7.6.1~ds-1.debian.tar.xz 797de5c19f469cc4fb7b660f8b6382f74125e0a0594750d0d94a7918e8198c11 13257 libjs-webrtc-adapter_7.6.1~ds-1_amd64.buildinfo Files: 0977fe17cdabb45bde55ebd7fb6df2cb 2452 javascript optional libjs-webrtc-adapter_7.6.1~ds-1.dsc e752dcab295366588bbd118717a2d76d 39024 javascript optional libjs-webrtc-adapter_7.6.1~ds.orig.tar.xz d99e03d86d0b56bcc2ca26686da668bb 6484 javascript optional libjs-webrtc-adapter_7.6.1~ds-1.debian.tar.xz e7078903b65ce29383b192bbad519412 13257 javascript optional libjs-webrtc-adapter_7.6.1~ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7ZeqEACgkQLHwxRsGg ASGajxAApUIOQlsbJpxCgeUEHrZJuIiEBDE1GXzV50oJaP0P6XpYMkuYXxxIgLz3 ZFGj/uE1RwZoeftwk68oHdq6XoBknL1oygo9BnTzDXjev9T8YB6Kakxzo/zWDmoU 4Fs/u78Hk6zmkziY9KaF/uUQdwoGp78+D+V9Jle8dOf1VDM/awsef6dzKMDVb8Fj HlMl4kn4GVj0qdNhFRDiRPtjaFdncGIGx3bMCiDb1J6tU/c8HebDoSZkS1pkNsmR Vd+We15IQsgc0/t67Dbd97wPks9tO/Qi1RjGFFxAKLZHXMBd3kr6NwF8fbNgoBFp LmtQwUkcaTcdgfa1tkItM8AhkPas5EBMUqtkoUuPm1FCpdEWMpos0+7rijBaTvPo x9c63+A1PMt7bxmuvtcMUDRJJqt3zT++ckX/EQDML5q0dHoPa5XxSwyLAIhLCgq7 aCaSDNhlSH3WIpj7PdwjirEnpX8mYJv9cmaZ9EvnnyKhgmWnciXtLcCjcgrkY7pw hpQZxjm0S2Et+GTIkGZbSvhGQaUfi+045Yu+700974+fpjK+ZMC+jFWKHs6MnWJd lNHmuE3LSM4tHsHaFWgQLTNunag/P7nzJeqXqndLZ154kMUQxLYSiSVeZtDOd6l6 egWXUpa6W+Qndr4jrk27Wh7GDoUyZRXdGD4tfv/6R/bJdgcCoSw= =U1hd -END PGP SIGNATURE End Message ---
Processed: Bug#959798 marked as pending in libjs-webrtc-adapter
Processing control commands: > tag -1 pending Bug #959798 [src:libjs-webrtc-adapter] libjs-webrtc-adapter: Build with babel version 7 Bug #960264 [src:libjs-webrtc-adapter] libjs-webrtc-adapter: Please remove dependency to node-babel-preset-env Added tag(s) pending. Added tag(s) pending. -- 959798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959798 960264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959798: marked as pending in libjs-webrtc-adapter
Control: tag -1 pending Hello, Bug #959798 in libjs-webrtc-adapter 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/libjs-webrtc-adapter/-/commit/09690c61fdaf50bd50a386b02d35a990fb539128 use babel7: update babeljs presets; build-depend on node-babel7 (not node-babel-cli node-babel-preset-env); closes: bug#959798, thanks to Pirate Praveen (this message was generated automatically) -- Greetings https://bugs.debian.org/959798
Bug#962158: lintian: New very problematic --fail-on default value
Hi! On Thu, 2020-06-04 at 23:06:29 +0100, Chris Lamb wrote: > severity 962158 serious > thanks > > Severity: important > > > > This probably deserves to be serious, but I'm not sure I can be > > bothered… > > I can relate to this feeling so let me do this for you. At the very > least, this change now won't hit bullseye before being resolved. Great, thanks! On Wed, 2020-06-03 at 20:05:13 -0700, lechner wrote: > retitle 962158 lintian: Swapped exit statuses and --fail-on default value > require downstream adjustments > thanks But then this new title does not reflect what is being reported at all, it's actually the complete opposite. :( And not feeling like restoring it either to avoid even a single bug-control ping-pong… Thanks, Guillem
Bug#962158: lintian: Swapped exit statuses and --fail-on default value require downstream adjustments
Hi On Thu, Jun 4, 2020 at 3:21 PM Chris Lamb wrote: > > I can relate to this feeling so let me do this for you. At the very > least, this change now won't hit bullseye before being resolved. I also agree with this bump in severity. Thanks! > This change means that any current caller which uses lintian as part > of its acceptance testing will now silently let broken things through As I explained on IRC this statement is probably untrue (and you did not have the courtesy to mention that objection here). From what I can tell, the FTP Master (who are arguably the one "acceptance tester" who really matters) parses the tags. [1] Please let me know if you know otherwise. [1] https://salsa.debian.org/ftp-team/dak/-/blob/master/daklib/lintian.py#L73-74 > If the default change made sense due to some technical rationale, this > effort might be worthwhile As I likewise explained on IRC, Lintian's return status was unreliable. Some program errors exited with status 1 and others with status 2, while detecting error tags always produced status 1. Lintian was also unable to use Perl's 'die'. The proper remedy was to always use status 1 for program errors. That step alone would require any automated user to examine their scripts. The 'fail-on' command-line option resolved a long standing problem with the implicit behavior your so cherish (#709932). Instead of adding more complex options, the current solution is simple, elegant, straighforward and explicit. And again, automated users already had to look at their scripts. It was the perfect timing to make both changes. Kind regards, Felix Lechner
Bug#962158: lintian: New very problematic --fail-on default value
severity 962158 serious thanks Guillem, > Severity: important > > This probably deserves to be serious, but I'm not sure I can be > bothered… I can relate to this feeling so let me do this for you. At the very least, this change now won't hit bullseye before being resolved. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#937769: python-funcsigs build-dependencies now unsatisfiable in testing, removal of pypy-pytest
On 6/4/20 10:33 PM, peter green wrote: > A few days ago Sandro Tosi uploaded the python-unittest2 and > python-funcsigs source packages. It seems that both of these were > effectively "team uploads" though they were not marked as such. A few years ago, I've been flamed, them banned from the DPMT for less than this... Though I don't think we should put the blame on Sandro. He did a lot and we should be thankful for his work on Python 2 removal. > The > python-unittest2 upload dropped python 2 support while the > python-funcsigs package dropped python 2 and pypy support. > > python-unittest2, python-traceback2 and python-linecache2 have now > migrated to testing, the result of this is that the build-dependencies > of python-traceback2 and python-linecache2 are now satisfiable in > testing, but those of python-funcsigs are now broken in testing. > > python-funcsigs is unable to migrate to testing because pypy-pytest > depends on pypy-funcsigs . The thing is, funcsigs is a backport of the PEP 362 function signature features from Python 3.3's inspect module (as per the package description), so it should in fact go away if possible. I'm really not sure what's going to be the faith of pypy-pytest, maybe it should be replaced by pypy3-pytest? If I remember well the discussion, we wrote that we would just disable the tests for things depending on python 2 test suites. Maybe this includes pypy-pytest? Your thoughts? Cheers, Thomas Goirand (zigo)
Processed: Re: Bug#962158: lintian: New very problematic --fail-on default value
Processing commands for cont...@bugs.debian.org: > severity 962158 serious Bug #962158 [lintian] lintian: Swapped exit statuses and --fail-on default value require downstream adjustments Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962168: marked as done (loggerhead: Depends on yui3 which is going to be removed)
Your message dated Thu, 04 Jun 2020 21:38:22 + with message-id and subject line Bug#962168: fixed in loggerhead 1.19~bzr498-2 has caused the Debian Bug report #962168, regarding loggerhead: Depends on yui3 which is going to be removed 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.) -- 962168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: loggerhead Severity: serious Hi, as explained one year ago ([1] without any response), yui3 is going to be removed (#962167). Please remove dependency to this library (libjs-yui3-min). As yui3 never entered in testing due to DFSG problems, I chose to set severity to serious here. Cheers, Xavier [1]: https://alioth-lists.debian.net/pipermail/pkg-bazaar-maint/2019-August/008343.html [1]: https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2019-August/034865.html --- End Message --- --- Begin Message --- Source: loggerhead Source-Version: 1.19~bzr498-2 Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= We believe that the bug you reported is fixed in the latest version of loggerhead, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated loggerhead 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, 04 Jun 2020 20:26:08 + Source: loggerhead Architecture: source Version: 1.19~bzr498-2 Distribution: unstable Urgency: medium Maintainer: Debian Bazaar Maintainers Changed-By: Jelmer Vernooij Closes: 962168 Changes: loggerhead (1.19~bzr498-2) unstable; urgency=medium . * Add patch jquery.patch: replace YUI with jQuery. Closes: #962168 Checksums-Sha1: 998dc6a09cfdc40b1d8d5520700c03aa1fdd779b 2576 loggerhead_1.19~bzr498-2.dsc 47b6ecbec25fcc6c3e630b11e6de5ac353b141fc 13464 loggerhead_1.19~bzr498-2.debian.tar.xz 7315654a65bdf0e1ed085586686a0d9127668a5b 7916 loggerhead_1.19~bzr498-2_amd64.buildinfo Checksums-Sha256: 826edc5fa241d14003142bb8ee24344fe590d2790010831ad84b6bdc92331242 2576 loggerhead_1.19~bzr498-2.dsc 08db7ee280fb5b4bfb38c3149af1bd238780629a95d0b4d015daebfd8995a996 13464 loggerhead_1.19~bzr498-2.debian.tar.xz e63ad125497c6daef1bd999b618c2bf2f2334bd11a06089d4f0d6bc7b6558b9c 7916 loggerhead_1.19~bzr498-2_amd64.buildinfo Files: 532a915ece92f05e661425db3e0dab11 2576 devel optional loggerhead_1.19~bzr498-2.dsc aa873c1349019f2ed0c71d6f2b33 13464 devel optional loggerhead_1.19~bzr498-2.debian.tar.xz 3301b1b2b8f7c134a7d533bda4b30a41 7916 devel optional loggerhead_1.19~bzr498-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl7ZWnoACgkQV5wWDUye I+jopg/9HDzORmXYfJHvTB5oOb+RtXEyusNgSdbzdmJy5JMEGGGRLY9g321O6wqZ jnB56y5HASsFRyLmBojkljrMFtRraBbSmq8V1Y4jIh2CMxRpzn1NNL4b35FGIN0f g5M4AybJ+SrfkApFnD41rtyItzucPyt10SIQ3bzrLEuUklbVhWtrd2YPXpi3pZ2R VFtJKRC1/4zlFbWJzJ8X6ECNZir8sw1rQlvT+r2utxATBU4iBaHHDIOTRs/UYkaE 0aqXROfCn58gzHtcftEJQA9/27TVSrsio4JaLOSyDGrJ0gAs4PdE+MBMsb1rkBd0 Cjxr0YvKJxKRMLrXoFKmi1K1TE9iZPHH/lfQdFoevrzzb3KB/mSx5slEPugehF3n 2qG1650Odk1MFBbCmzhB6TER4o+OaOlLYzUSBLS0GiLdE9NaSCBKn/SuyWPnxsis Acv9L6oqAWOcM5XejrFGmRETfG1BwboivG3kE7On1ZC2A5SrJUJk0ejIW1oI+n8c i/OH4EMBM07uU9Aq+/K271YiX/9mdgEuZJ63gXk/TIkpLD+nIVV6M1Z32oN1Jbwe ou9VEFY6MzKdXhrHvBnkIDfrh3yY+VkQ6dcbDghDf2heStPcxVlyEkaKo9Z5dcKc 6QTTGj/u4OmcnkghbOlpqyJ+FipQBe4fHfcruksgsGtePyEOitY= =jGIH -END PGP SIGNATURE End Message ---
Bug#962218: gnutls28: build fails on IPv6-only buildds
On Thu, Jun 4, 2020 at 22:18:10 +0300, Adrian Bunk wrote: > On Thu, Jun 04, 2020 at 07:55:32PM +0200, Julien Cristau wrote: > > Control: tag -1 moreinfo > > > > On Thu, Jun 04, 2020 at 07:59:22PM +0300, Adrian Bunk wrote: > > > FAIL: dtls_hello_random_value > > > = > > > > > > testing: default > > > client:156: client: Handshake failed: Resource temporarily unavailable, > > > try again. > > > server:271: server: Handshake has failed: The TLS connection was > > > non-properly terminated. > > > > > > FAIL dtls_hello_random_value (exit status: 1) > > > > > This particular test seems to use a AF_UNIX socketpair, I'm not sure > > how it would fail due to network setup? > > I copied the log from the 3.6.13-4 arm64 failure. > This specific test passes in the other logs. > > The binary-all log (non-conova) of 3.6.13-4 has no test failures, > but the build fails due to timeout after 150 minutes without output. > > My gut feeling is that there might be an (unrelated) problem with > the #961889 fix, but this is just a guess. > The arch:all failure is at grnet and that buildd has both v4 and v6 addresses, so presumably unrelated. Which leaves us with the armel failure (on arm-conova-03) which does look related to the lack of public v4 address, e.g.: > FAIL: sni-hostname.sh > = > > Checking SNI hostname in gnutls-cli > Echo Server listening on IPv6 :: port 26448...done > Could not connect to 127.0.0.1:26448: Connection refused > Failure: 1. handshake should have succeeded! > Exiting via signal 15 > FAIL sni-hostname.sh (exit status: 1) If we listen on :: and then try to connect to 127.0.0.1, that won't work. And indeed gnutls-serv seems to call getaddrinfo with node == NULL and hints.ai_flags == AI_PASSIVE|AI_ADDRCONFIG, to figure out what address to listen on. If the host has no non-local ipv4 address, that getaddrinfo call returns :: but not 0.0.0.0; and then the test hardcodes 127.0.0.1 as the address for gnutls-cli to connect to, and sadness ensues. Cheers, Julien
Bug#937769: python-funcsigs build-dependencies now unsatisfiable in testing, removal of pypy-pytest
A few days ago Sandro Tosi uploaded the python-unittest2 and python-funcsigs source packages. It seems that both of these were effectively "team uploads" though they were not marked as such. The python-unittest2 upload dropped python 2 support while the python-funcsigs package dropped python 2 and pypy support. python-unittest2, python-traceback2 and python-linecache2 have now migrated to testing, the result of this is that the build-dependencies of python-traceback2 and python-linecache2 are now satisfiable in testing, but those of python-funcsigs are now broken in testing. python-funcsigs is unable to migrate to testing because pypy-pytest depends on pypy-funcsigs . I have just filed a rc bug on vanguards ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962232 ), once that is dealt with it should then be possible to drop pypy-pytest and related module packages ( pypy-atomicwrites, pypy-pluggy, pypy-py pypy-setuptools-scm pypy-wcwidth pypy-importlib-metadata and pypy-zipp )
Bug#962232: vanguards indirectly build-depends on cruft package.
Package: vanguards
Version: 0.3.1-2
Severity: serious
vanguards build-depends on pypy-pytest which depends on pypy-funcsigs which is
no longer built by the python-funcsigs source package. The pytest maintainer
has also said they would like to get rid of pypy support from pytest. Afaict
vanguards is the only application that build-depends on pypy-pytest (there are
also some module packages but they all look like they could drop pypy support
at the same time pytest does).
The ideal fix would be to move to pypy3, but I understand that is currently
blocked on tooling (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932820 ). Over in bug 937769
Chris Lamb proposed a patch to run the testsuite with python 3. Obviously
running the testsuite with a different python version from that used to
actually run the program is suboptimal but I think it's the lesser evil here.
I manually applied the patch, cleaning up some formatting and making the
dependency versioning for the python3-stem build-dependency match that for the
pypy-stem build-dependency. While testing I also noticed some clean target
issues so I fixed them.
A debdiff is attatched, if I get no objections (and the maintainer doesn't
upload this first) I will likely NMU this in a week or so.
diff -Nru vanguards-0.3.1/debian/changelog vanguards-0.3.1/debian/changelog
--- vanguards-0.3.1/debian/changelog2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/changelog2020-06-04 19:21:14.0 +
@@ -1,3 +1,12 @@
+vanguards (0.3.1-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Clean up pytest cache and egg info in clean target.
+ * Run testsuite with python 3 to get rid of build-depends on pypy-pytest
+(thanks to Chris Lamb for the initial patch)
+
+ -- Peter Michael Green Thu, 04 Jun 2020 19:21:14 +
+
vanguards (0.3.1-2) unstable; urgency=medium
[ Nicolas Braud-Santoni ]
diff -Nru vanguards-0.3.1/debian/control vanguards-0.3.1/debian/control
--- vanguards-0.3.1/debian/control 2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/control 2020-06-04 19:21:14.0 +
@@ -8,8 +8,9 @@
dh-python,
pypy,
pypy-setuptools,
+ python3-pytest ,
+ python3-stem (>= 1.6.0-3.1) ,
pypy-stem (>= 1.6.0-3.1),
- pypy-pytest,
pypy-ipaddress
Standards-Version: 4.1.5
Vcs-Browser: https://salsa.debian.org/pkg-privacy-team/vanguards
diff -Nru vanguards-0.3.1/debian/rules vanguards-0.3.1/debian/rules
--- vanguards-0.3.1/debian/rules2019-07-26 16:30:09.0 +
+++ vanguards-0.3.1/debian/rules2020-06-04 19:21:14.0 +
@@ -5,3 +5,10 @@
override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
+
+override_dh_auto_test:
+ dh_auto_test -- --system=custom --test-args='cd {build_dir}; python3 -m
pytest $(CURDIR)/tests'
+
+override_dh_auto_clean:
+ dh_auto_clean
+ rm -rf .pytest_cache src/vanguards.egg-info
Bug#962230: xiphos: FTBFS on mips64el
Source: xiphos Version: 4.1.0.1+dfsg1-1+b1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) xiphos fails to build on ftbfs: | [ 45/131] cxx: src/main/configs.cc -> build/default/src/main/configs_1.o | 22:41:52 runner system command -> ['/usr/bin/g++', '-O2', '-fno-delete-null-pointer-checks', '-DHAVE_CONFIG_H', '-g', '-O2', '-fdebug-prefix-map=/<>=.', '-fstack-protector-strong', '-Wformat', '-Werror=format-security', '-pthread', '-Wdate-time', '-D_FORTIFY_SOURCE=2', '-Wdate-time', '-D_FORTIFY_SOURCE=2', '-Idefault/src/main', '-I../src/main', '-Idefault', '-I..', '-Idefault/src', '-I../src', '-I/usr/include/dbus-1.0', '-I/usr/lib/mips64el-linux-gnuabi64/dbus-1.0/include', '-I/usr/include/glib-2.0', '-I/usr/lib/mips64el-linux-gnuabi64/glib-2.0/include', '-I/usr/include/libgsf-1', '-I/usr/include/webkitgtk-4.0', '-I/usr/include/gtk-3.0', '-I/usr/include/at-spi2-atk/2.0', '-I/usr/include/at-spi-2.0', '-I/usr/include/gio-unix-2.0', '-I/usr/include/cairo', '-I/usr/include/pango-1.0', '-I/usr/include/fribidi', '-I/usr/include/harfbuzz', '-I/usr/include/atk-1.0', '-I/usr/include/pixman-1', '-I/usr/include/uuid', '-I/usr/include/freetype2', '-I/usr/include/libpng16', '-I/usr/include/gdk-pixbuf-2.0', '-I/usr/include/libsoup-2.4', '-I/usr/include/libxml2', '-I/usr/include/libmount', '-I/usr/include/blkid', '-I/usr/include/sword', '-I/usr/include/biblesync/bibleysnc', '../src/main/configs.cc', '-c', '-o', 'default/src/main/configs_1.o'] | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23,0G | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from /usr/include/sword/filemgr.h:26, | from ../src/backend/sword_main.cc:31: | /usr/include/asm-generic/int-l64.h:29:25: error: conflicting declaration ‘typedef long int __s64’ |29 | typedef __signed__ long __s64; | | ^ | In file included from /usr/include/sword/swkey.h:31, | from /usr/include/sword/listkey.h:28, | from /usr/include/sword/swmodule.h:29, | from ../src/backend/sword_main.cc:28: | /usr/include/sword/sysdata.h:49:44: note: previous declaration as ‘typedef long long int __s64’ |49 | __extension__ typedef __signed__ long long __s64; | |^ | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23, | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from /usr/include/sword/filemgr.h:26, | from ../src/backend/sword_main.cc:31: | /usr/include/asm-generic/int-l64.h:30:23: error: conflicting declaration ‘typedef long unsigned int __u64’ |30 | typedef unsigned long __u64; | | ^ | In file included from /usr/include/sword/swkey.h:31, | from /usr/include/sword/listkey.h:28, | from /usr/include/sword/swmodule.h:29, | from ../src/backend/sword_main.cc:28: | /usr/include/sword/sysdata.h:50:42: note: previous declaration as ‘typedef long long unsigned int __u64’ |50 | __extension__ typedef unsigned long long __u64; | | ^ | In file included from /usr/include/sword/swkey.h:31, | from /usr/include/sword/listkey.h:28, | from /usr/include/sword/swmodule.h:29, | from ../src/backend/module_manager.hh:28, | from ../src/backend/module_manager.cc:40: | /usr/include/sword/sysdata.h:49:44: error: conflicting declaration ‘typedef long long int __s64’ |49 | __extension__ typedef __signed__ long long __s64; | |^ | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23, | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from /usr/include/sword/filemgr.h:26, | from ../src/backend/module_manager.cc:36: | /usr/include/asm-generic/int-l64.h:29:25: note: previous declaration as ‘typedef long int __s64’ |29 | typedef __signed__ long __s64; | | ^ | In file included from /usr/include/sword/swkey.h:31, | from /usr/include/sword/listkey.h:28, | from
Bug#961841: fontforge FTBFS on 64bit big endian: test failures
This upstream commit fixes the test failures on s390x: https://github.com/oSoMoN/fontforge/commit/fde85b13382595cb3ab889e38570b4944edad808 . I cherry-picked it and applied it to 1:20190801~dfsg-5 (only the last hunk doesn't apply cleanly, it can be removed), and the build succeeded on amd64, arm64, armhf, ppc64el and s390x (against Ubuntu groovy-proposed).
Processed: tagging 947569
Processing commands for cont...@bugs.debian.org: > tags 947569 + ftbfs Bug #947569 [src:mongo-cxx-driver-legacy] FTBFS with scons 3.1.2-1 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 947569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 936483
Processing commands for cont...@bugs.debian.org: > tags 936483 + ftbfs Bug #936483 [src:enki-aseba] enki-aseba: Python2 removal in sid/bullseye Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 936483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 958156
Processing commands for cont...@bugs.debian.org: > tags 958156 + ftbfs Bug #958156 [slic3r] FTBFS with Boost 1.71 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 958156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: orthanc-postgresql FTBFS with boost1.71
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 960413 960418 958156 962070 960414 960427 960381 955579 953873 948281 962086 955581 948407 960378 948127 960424 959480 959439 960422 960421 949837 959479 954711 960426 960331 960500 962173 959463 959417 948122 959573 960412 960383 960416 954648 959437 954351 960385 954649 953871 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962229 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962229: orthanc-postgresql FTBFS with boost1.71
Source: orthanc-postgresql Version: 3.2-1 Severity: serious Tags: ftbfs bullseye sid Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=orthanc-postgresql=sid ... -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found version "1.71.0") CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:182 (boost_find_component): boost_find_component Macro invoked with incorrect arguments for macro named: boost_find_component Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindBoost.cmake:443 (find_package) /<>/Build/Orthanc-1.5.4/Resources/CMake/BoostConfiguration.cmake:15 (find_package) /<>/Build/Orthanc-1.5.4/Resources/CMake/OrthancFrameworkConfiguration.cmake:417 (include) /<>/Resources/CMake/DatabasesFrameworkConfiguration.cmake:62 (include) /<>/Resources/CMake/DatabasesPluginConfiguration.cmake:21 (include) CMakeLists.txt:22 (include) ... orthanc-postgresql builds an own copy of src:orthanc, and this copy does not have #953884 fixed.
Processed: tagging 960378
Processing commands for cont...@bugs.debian.org: > tags 960378 + ftbfs Bug #960378 [src:cegui-mk2] cegui-mk2: FTBFS with boost 1.71 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 960378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 962226
Processing commands for cont...@bugs.debian.org: > tags 962226 + ftbfs Bug #962226 [src:libdr-tarantool-perl] libdr-tarantool-perl build-depends on obsolete package Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962218: gnutls28: build fails on IPv6-only buildds
On Thu, Jun 04, 2020 at 07:55:32PM +0200, Julien Cristau wrote: > Control: tag -1 moreinfo > > On Thu, Jun 04, 2020 at 07:59:22PM +0300, Adrian Bunk wrote: > > FAIL: dtls_hello_random_value > > = > > > > testing: default > > client:156: client: Handshake failed: Resource temporarily unavailable, try > > again. > > server:271: server: Handshake has failed: The TLS connection was > > non-properly terminated. > > > > FAIL dtls_hello_random_value (exit status: 1) > > > This particular test seems to use a AF_UNIX socketpair, I'm not sure > how it would fail due to network setup? I copied the log from the 3.6.13-4 arm64 failure. This specific test passes in the other logs. The binary-all log (non-conova) of 3.6.13-4 has no test failures, but the build fails due to timeout after 150 minutes without output. My gut feeling is that there might be an (unrelated) problem with the #961889 fix, but this is just a guess. > Cheers, > Julien cu Adrian
Processed: tagging 960426
Processing commands for cont...@bugs.debian.org: > tags 960426 + ftbfs Bug #960426 [src:svgpp] svgpp: FTBFS with boost 1.71 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 960426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 940793 ...
Processing commands for cont...@bugs.debian.org: > tags 940793 + patch Bug #940793 [src:apper] Please replace transitional dependency polkit-kde-1 with polkit-kde-agent-1 Added tag(s) patch. > forwarded 940793 > https://salsa.debian.org/pkgutopia-team/apper/-/merge_requests/1 Bug #940793 [src:apper] Please replace transitional dependency polkit-kde-1 with polkit-kde-agent-1 Set Bug forwarded-to-address to 'https://salsa.debian.org/pkgutopia-team/apper/-/merge_requests/1'. > forwarded 925252 > https://salsa.debian.org/pkgutopia-team/apper/-/merge_requests/1 Bug #925252 [apper] apper: Crashes after performing an update Set Bug forwarded-to-address to 'https://salsa.debian.org/pkgutopia-team/apper/-/merge_requests/1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 925252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925252 940793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962226: libdr-tarantool-perl build-depends on obsolete package
Source: libdr-tarantool-perl Version: 0.45-2 Severity: serious Tags: bullseye, sid libdr-tarantool-perl build-depends on tarantool-lts | tarantool (<< 1.6) tarantool-lts has been removed from Debian and tarantool is now at version 1.9.1.26.g63eb81e3c-1.1
Bug#959410: marked as done (jinja2 breaks oca-core autopkgtest: The server encountered an internal error and was unable to complete your request)
Your message dated Thu, 4 Jun 2020 19:44:01 +0200 with message-id <20200604174401.teig7mpdqcj5n...@sar0.p1otr.com> and subject line fixed in 2.11.2-1 has caused the Debian Bug report #959410, regarding jinja2 breaks oca-core autopkgtest: The server encountered an internal error and was unable to complete your request 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.) -- 959410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jinja2, oca-core Control: found -1 jinja2/2.11.1-1 Control: found -1 oca-core/11.0.20180730-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of jinja2 the autopkgtest of oca-core fails in testing when that autopkgtest is run with the binary packages of jinja2 from unstable. It passes when run with only packages from testing. In tabular form: passfail jinja2 from testing2.11.1-1 oca-core from testing11.0.20180730-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of jinja2 to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=jinja2 https://ci.debian.net/data/autopkgtest/testing/amd64/o/oca-core/5233451/log.gz autopkgtest [05:12:03]: test basic-tests: [--- ● oca-core.service - Odoo's Community Association Open Source ERP and CRM Loaded: loaded (/lib/systemd/system/oca-core.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-05-01 05:12:04 UTC; 10ms ago Main PID: 7301 (odoo) Tasks: 1 (limit: 4915) Memory: 1008.0K CGroup: /system.slice/oca-core.service └─7301 /usr/bin/python3 /usr/bin/odoo --config /etc/odoo/odoo.conf --logfile /var/log/odoo/odoo-server.log May 01 05:12:04 ci-122-22d8115e systemd[1]: Started Odoo's Community Association Open Source ERP and CRM. Try #1 to fetch http://localhost:8069/web ERROR: Odoo is not up and running :-( Output of curl -L http://localhost:8069/web: 500 Internal Server Error Internal Server Error The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application. autopkgtest [05:12:09]: test basic-tests: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: jinja2 Source-Version: 2.11.2-1 fixed in jinja2 2.11.2-1--- End Message ---
Bug#962218: gnutls28: build fails on IPv6-only buildds
On Thu, Jun 04, 2020 at 07:32:13PM +0200, Andreas Metzler wrote: > On 2020-06-04 Adrian Bunk wrote: > > Source: gnutls28 > > Version: 3.6.13-2 > > Severity: serious > > Tags: ftbfs > > > https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-3 > > https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-4 > > > ... > [...] > > > The conova buildds are IPv6-only, see #962019 for a similar > > problem in perl. > > Helo Adrian, > > is there a way to declare a dependency on IPv4 for building? > > Also the setup is strange, both netstat and ifconfig show IPv4: > eth0 has no ipv4, that's all. Why is that strange? Cheers, Julien
Bug#962218: gnutls28: build fails on IPv6-only buildds
On Thu, Jun 04, 2020 at 07:32:13PM +0200, Andreas Metzler wrote: > On 2020-06-04 Adrian Bunk wrote: > > Source: gnutls28 > > Version: 3.6.13-2 > > Severity: serious > > Tags: ftbfs > > > https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-3 > > https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-4 > > > ... > [...] > > > The conova buildds are IPv6-only, see #962019 for a similar > > problem in perl. > > Helo Adrian, > > is there a way to declare a dependency on IPv4 for building? No. > Also the setup is strange, both netstat and ifconfig show IPv4: > > DEBUG info about network setup starts ... > if test -x /sbin/ifconfig ; then /sbin/ifconfig ; else true ; fi > eth0: flags=4163 mtu 1500 > inet6 2a02:16a8:dc41:100::240 prefixlen 64 scopeid 0x0 > inet6 fe80::216:37ff:fed2:16f0 prefixlen 64 scopeid 0x20 > ether 00:16:37:d2:16:f0 txqueuelen 1000 (Ethernet) > RX packets 108814178 bytes 157204088386 (146.4 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 13855486 bytes 11641875516 (10.8 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73 mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10 > loop txqueuelen 1000 (Local Loopback) > RX packets 4506091 bytes 20691973484 (19.2 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 4506091 bytes 20691973484 (19.2 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >... The usage of AI_ADDRCONFIG in src/serv.c:listen_socket() looks similar to the problem described in the perl bug. > cu Andreas >... cu Adrian
Bug#962218: gnutls28: build fails on IPv6-only buildds
Control: tag -1 moreinfo On Thu, Jun 04, 2020 at 07:59:22PM +0300, Adrian Bunk wrote: > FAIL: dtls_hello_random_value > = > > testing: default > client:156: client: Handshake failed: Resource temporarily unavailable, try > again. > server:271: server: Handshake has failed: The TLS connection was non-properly > terminated. > > FAIL dtls_hello_random_value (exit status: 1) > This particular test seems to use a AF_UNIX socketpair, I'm not sure how it would fail due to network setup? Cheers, Julien
Processed: Re: Bug#962218: gnutls28: build fails on IPv6-only buildds
Processing control commands: > tag -1 moreinfo Bug #962218 [src:gnutls28] gnutls28: build fails on IPv6-only buildds Added tag(s) moreinfo. -- 962218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961602: marked as done (castle-game-engine-doc: Depends on removed ttf-dejavu packages)
Your message dated Thu, 04 Jun 2020 17:33:35 + with message-id and subject line Bug#961602: fixed in castle-game-engine 6.4+dfsg1-4 has caused the Debian Bug report #961602, regarding castle-game-engine-doc: Depends on removed ttf-dejavu packages 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.) -- 961602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: castle-game-engine-doc Severity: grave Version: 6.4+dfsg1-3 Tags: sid bullseye X-Debbugs-CC: abou.almonta...@sfr.fr elb...@debian.org Dear Debian castle-game-engine packagers, Recent changes in Debian fonts-dejavu package (2.37-2) dropped the old transitional package ttf-dejavu, ttf-dejavu-core and ttf-dejavu-extra. [1][2] Your package still depends on them, thus will become uninstallable. As you can see in https://codesearch.debian.net/search?q=package%3Acastle-game-engine+ttf-dejavu=0 , your package is using hardcoded paths that points to the lagacy location of the font. Please make another upload and use the new paths provided by fonts-dejavu package. [1] https://tracker.debian.org/news/1146775/accepted-fonts-dejavu-237-2-source-into-unstable/ [2] https://bugs.debian.org/872809 -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: castle-game-engine Source-Version: 6.4+dfsg1-4 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of castle-game-engine, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated castle-game-engine 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, 04 Jun 2020 18:41:09 +0200 Source: castle-game-engine Architecture: source Version: 6.4+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Paul Gevers Closes: 961602 Changes: castle-game-engine (6.4+dfsg1-4) unstable; urgency=medium . [ Olivier Tilloy ] * Update runtime dependency on the transitional dummy ttf-dejavu-core (which was dropped from unstable) to fonts-dejavu-core (Closes: #961602) Checksums-Sha1: 2d4ada7325c2d6710ce2c2f40abcb6a089c09a42 2316 castle-game-engine_6.4+dfsg1-4.dsc 9d57f425d38901ecb72c1858323de2efdd888423 22496 castle-game-engine_6.4+dfsg1-4.debian.tar.xz Checksums-Sha256: ffae8b0648ff9d74854730f197b4f03965083c2f9b949f7d6c45673bb3f7822d 2316 castle-game-engine_6.4+dfsg1-4.dsc 88829679bf10a23d908a6be527988fa4c3b1aadea93a30a63f652c2806d00b57 22496 castle-game-engine_6.4+dfsg1-4.debian.tar.xz Files: 1e68ef77b51a4c7443ac50f3ff9f5e5c 2316 misc optional castle-game-engine_6.4+dfsg1-4.dsc 34dd13df8d8fe908a831ef498669fec9 22496 misc optional castle-game-engine_6.4+dfsg1-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl7ZJV4ACgkQnFyZ6wW9 dQpg4Af7BsjE+YJuUEvY9FqnCKRII4VIapfe34rRH4kJTGWX1m23Px5Lgs0EMV/E 0E/i6MKO9wpNOtnLDyJZGQHZKH4CQIVDugbqEQlw3VVgzLOV4hmN/B7JmLW7RdRP yxxjxYbJHRsv1s0p2Ppt3RoZ6mQP3kmLvithhDhg/K8RdXGZi4fFEDktIT8BAIBr fXmHHS+W1ZslWb4iKt1V+XCh6G23gVuTaB+Zx5KsHp2tE3XkxNi9CbU/ZFJCW2+Z RB4baM4bHNMK4FriZqYgdG83MNn1vkyaR4Bb+YO22WqbR4g8aJEGNlQXSQ4bC5x/ YcXa8YCodBUGO8SBp76/jphr94bDjw== =XoYs -END PGP SIGNATURE End Message ---
Bug#962221: xawtv: CVE-2020-13696
Source: xawtv Version: 3.106-1 Severity: grave Tags: security upstream Hi, The following vulnerability was published for xawtv. CVE-2020-13696[0]: | v4l-conf setuid-root program allows file existence tests and open(..., | O_RDRW) on arbitrary files If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-13696 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13696 [1] https://www.openwall.com/lists/oss-security/2020/06/04/6 Regards, Salvatore
Bug#962218: gnutls28: build fails on IPv6-only buildds
On 2020-06-04 Adrian Bunk wrote: > Source: gnutls28 > Version: 3.6.13-2 > Severity: serious > Tags: ftbfs > https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-3 > https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-4 > ... [...] > The conova buildds are IPv6-only, see #962019 for a similar > problem in perl. Helo Adrian, is there a way to declare a dependency on IPv4 for building? Also the setup is strange, both netstat and ifconfig show IPv4: DEBUG info about network setup starts ... if test -x /sbin/ifconfig ; then /sbin/ifconfig ; else true ; fi eth0: flags=4163 mtu 1500 inet6 2a02:16a8:dc41:100::240 prefixlen 64 scopeid 0x0 inet6 fe80::216:37ff:fed2:16f0 prefixlen 64 scopeid 0x20 ether 00:16:37:d2:16:f0 txqueuelen 1000 (Ethernet) RX packets 108814178 bytes 157204088386 (146.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 13855486 bytes 11641875516 (10.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 4506091 bytes 20691973484 (19.2 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4506091 bytes 20691973484 (19.2 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 netstat -tln Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 0.0.0.0:25 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:56660.0.0.0:* LISTEN tcp0 0 127.0.0.1:530.0.0.0:* LISTEN tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp0 0 127.0.0.1: 0.0.0.0:* LISTEN tcp6 0 0 :::25 :::*LISTEN tcp6 0 0 :::5666 :::*LISTEN tcp6 0 0 :::4949 :::*LISTEN tcp6 0 0 ::1:53 :::*LISTEN tcp6 0 0 :::22 :::*LISTEN ... DEBUG info about network setup ends. dh_auto_test -O--builddirectory=b4deb --verbose -- VERBOSE=1 cd b4deb && make -j4 check VERBOSE=1 VERBOSE=1 cu Andreas PS: I wish the introduction of IPv6-only buildds a) had not happened when I was trying to get a fix for a serious bug into testing (and buster) and b) was not happening without announcement. -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#961997: marked as done (openscenegraph: Cannot migrate to testing (Not built on buildd))
Your message dated Thu, 04 Jun 2020 17:19:46 + with message-id and subject line Bug#961997: fixed in openscenegraph 3.6.5+dfsg1-4 has caused the Debian Bug report #961997, regarding openscenegraph: Cannot migrate to testing (Not built on buildd) 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.) -- 961997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openscenegraph Version: 3.6.5+dfsg1-3 Severity: important Dear Maintainer, The recent upload of openscenegraph (3.6.5+dfsg1-3) to unstable cannot migrate to testing because the binary packages weren't built on a buildd. >From the excuses: " Not built on buildd: arch all binaries uploaded by alua...@udc.es, a new source-only upload is needed to allow migration " The upload also triggered an uncoordinated transition: https://release.debian.org/transitions/html/auto-openscenegraph.html flightgear & openmw FTBFS with the new openscenegraph which also blocks the migration to testing. Please do a source-only upload to unstable and coordinate transitions in the future. Be sure to read the related documentation: https://wiki.debian.org/Teams/ReleaseTeam/Transitions Kind Regards, Bas --- End Message --- --- Begin Message --- Source: openscenegraph Source-Version: 3.6.5+dfsg1-4 Done: =?utf-8?q?Alberto_Luaces_Fern=C3=A1ndez?= We believe that the bug you reported is fixed in the latest version of openscenegraph, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Luaces Fernández (supplier of updated openscenegraph 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: SHA384 Format: 1.8 Date: Thu, 04 Jun 2020 18:03:36 +0200 Source: openscenegraph Architecture: source Version: 3.6.5+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Alberto Luaces Fernández Changed-By: Alberto Luaces Fernández Closes: 961997 Changes: openscenegraph (3.6.5+dfsg1-4) unstable; urgency=medium . * Backported patch for reducing console verbosity. Thanks Bret Curtis! * Upload only the source package to be able to migrate to testing (Closes: #961997). Checksums-Sha1: 4b470cb1a9c665f2ffd91d3af9f3e93240254a26 2287 openscenegraph_3.6.5+dfsg1-4.dsc bc6288cfb30572c371a527d978c213ff0517012c 36148 openscenegraph_3.6.5+dfsg1-4.debian.tar.xz e2c9decacf551c636d156d3000f7739646b6ac0c 21550 openscenegraph_3.6.5+dfsg1-4_amd64.buildinfo Checksums-Sha256: 4ef7bda904f0c91c5d5f38ed27d48364e3c1ee93509e636f4a37575b58b14d3f 2287 openscenegraph_3.6.5+dfsg1-4.dsc 4cb18681224f92360a2ceefd61f4c3fd6e98b7725c5ea51d157ba13e198d921c 36148 openscenegraph_3.6.5+dfsg1-4.debian.tar.xz c17b27434beb663fced2fbecd478d137bab3f7ac7e2f91bab937054a7b629a3e 21550 openscenegraph_3.6.5+dfsg1-4_amd64.buildinfo Files: 5ceae7c85981240498c0ee2b59518966 2287 devel optional openscenegraph_3.6.5+dfsg1-4.dsc 790da4bce3a0d7613a6e06247a1c7ceb 36148 devel optional openscenegraph_3.6.5+dfsg1-4.debian.tar.xz 53a0a38062b0ee55444ff40e93a7bd3b 21550 devel optional openscenegraph_3.6.5+dfsg1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iKUEARMJAC0WIQQAkrD2fjOKzJT6ErrYoCh5SUbfSgUCXtkoKg8cYWx1YWNlc0B1 ZGMuZXMACgkQ2KAoeUlG30o9qQGA6HIXSOrJ+v5DKRPnmw5cdvZRLwcRmD7DjS7l b9rEWN9NuVFiJucENvud7xuEjyYBAYCnLTEx1PtU3hahmYP2WPyFjKS/XQx40/k9 R02tM4/2v37x1SEQeJkrAdcn7FZ3BPk= =zvJi -END PGP SIGNATURE End Message ---
Bug#962090: Same Issue with a Python3 Project for Buster
-- cd /build/ehbackup-api-3.3.2+3+g6939d93~ui10/ && env PATH="/usr/lib/ccache:/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us -uc -d dpkg-buildpackage: info: source package ehbackup-api dpkg-buildpackage: info: source version 3.3.2+3+g6939d93~ui10 dpkg-buildpackage: info: source distribution UNRELEASED dpkg-buildpackage: info: source changed by EhBackup Team dpkg-buildpackage: info: host architecture amd64 dpkg-source --before-build . dpkg-source: info: using options from ehbackup-api-3.3.2+3+g6939d93~ui10/debian/source/options: --tar-ignore=build-bundle --tar-ignore=.git --tar-ignore=.gitignore debian/rules clean dh clean dh_auto_clean dh_auto_clean: warning: Please use the third-party "pybuild" build system instead of python-distutils dh_auto_clean: warning: This feature will be removed in compat 12. Can't exec "pyversions": No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 124. dh_auto_clean: error: failed to run pyversions make: *** [debian/rules:9: clean] Error 255 dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 -- "pyversions" is part of package "python2-minimal". Why python2-minimal if I build a Python3 project? My "Build-Depends" in "debian/control" file is: - Build-Depends: debhelper (>= 8.0.0), build-essential, python3-dev, libmysqlclient-dev | default-libmysqlclient-dev, python3-pip, python3-venv, libxml2-dev, libxslt1-dev, python3-sphinx, python3-setuptools X-Python3-Version: >= 3.7 -- Jürgen 0xA811F9F222306A1E.asc Description: application/pgp-keys
Processed: siconos: autopkgtest needs update for new version of boost-defaults: deprecation warning on stderr
Processing control commands: > affects -1 src:boost-defaults Bug #962219 [src:siconos] siconos: autopkgtest needs update for new version of boost-defaults: deprecation warning on stderr Added indication that 962219 affects src:boost-defaults -- 962219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962219: siconos: autopkgtest needs update for new version of boost-defaults: deprecation warning on stderr
Source: siconos Version: 4.2.0+git20181026.0ee5349+dfsg.2-3 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:boost-defaults [X-Debbugs-CC: debian...@lists.debian.org, boost-defau...@packages.debian.org] Dear maintainer(s), With a recent upload of boost-defaults the autopkgtest of siconos fails in testing when that autopkgtest is run with the binary packages of boost-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail boost-defaultsfrom testing1.71.0.3 siconos from testing4.2.0+git20181026.0ee5349+dfsg.2-3 all othersfrom testingfrom testing I copied some of the output at the bottom of this report. If possible, disable deprecation warnings as autopkgtest is not the place to test for those or, if that's not possible, add the allow-stderr restriction such that these warnings will be ignored. Currently this regression is blocking the migration of boost-defaults to testing [1]. Of course, boost-defaults shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in boost-defaults was intended and your package needs to update to the new situation. 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=boost-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/s/siconos/5757119/log.gz Ran 2 tests. OK autopkgtest [23:12:20]: test mechanics-tests: ---] autopkgtest [23:12:20]: test mechanics-tests: - - - - - - - - - - results - - - - - - - - - - mechanics-tests FAIL stderr: In file included from /usr/include/boost/config/header_deprecated.hpp:18, autopkgtest [23:12:20]: test mechanics-tests: - - - - - - - - - - stderr - - - - - - - - - - In file included from /usr/include/boost/config/header_deprecated.hpp:18, from /usr/include/boost/timer.hpp:20, from /usr/include/siconos/SiconosKernel.hpp:30, from /tmp/autopkgtest-lxc.sn3yur2n/downtmp/autopkgtest_tmp/MultiBodyTest.cpp:85: /usr/include/boost/timer.hpp:21:1: note: #pragma message: This header is deprecated. Use the facilities in instead. 21 | BOOST_HEADER_DEPRECATED( "the facilities in " ) | ^~~ /usr/include/boost/progress.hpp:23:1: note: #pragma message: This header is deprecated. Use the facilities in instead. 23 | BOOST_HEADER_DEPRECATED( "the facilities in " ) | ^~~ In file included from /usr/include/boost/config/header_deprecated.hpp:18, from /usr/include/boost/timer.hpp:20, from /usr/include/siconos/SiconosKernel.hpp:30, from /tmp/autopkgtest-lxc.sn3yur2n/downtmp/autopkgtest_tmp/ContactTest.cpp:12: /usr/include/boost/timer.hpp:21:1: note: #pragma message: This header is deprecated. Use the facilities in instead. 21 | BOOST_HEADER_DEPRECATED( "the facilities in " ) | ^~~ /usr/include/boost/progress.hpp:23:1: note: #pragma message: This header is deprecated. Use the facilities in instead. 23 | BOOST_HEADER_DEPRECATED( "the facilities in " ) | ^~~ signature.asc Description: OpenPGP digital signature
Bug#962218: gnutls28: build fails on IPv6-only buildds
Source: gnutls28 Version: 3.6.13-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-3 https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-4 ... SKIP: ssl30-server-kx-neg = SKIP ssl30-server-kx-neg (exit status: 77) SKIP: ssl30-cipher-neg == SKIP ssl30-cipher-neg (exit status: 77) SKIP: fips-mode-pthread === We are not in FIPS140 mode SKIP fips-mode-pthread (exit status: 77) SKIP: fips-test === Please note that if in FIPS140 mode, you need to assure the library's integrity prior to running this test We are not in FIPS140 mode SKIP fips-test (exit status: 77) SKIP: fips-override-test Please note that if in FIPS140 mode, you need to assure the library's integrity prior to running this test We are not in FIPS140 mode SKIP fips-override-test (exit status: 77) SKIP: ssl30-cert-key-exchange = SKIP ssl30-cert-key-exchange (exit status: 77) FAIL: dtls_hello_random_value = testing: default client:156: client: Handshake failed: Resource temporarily unavailable, try again. server:271: server: Handshake has failed: The TLS connection was non-properly terminated. FAIL dtls_hello_random_value (exit status: 1) SKIP: starttls.sh = SKIP starttls.sh (exit status: 77) SKIP: starttls-ftp.sh = SKIP starttls-ftp.sh (exit status: 77) SKIP: starttls-smtp.sh == SKIP starttls-smtp.sh (exit status: 77) SKIP: starttls-lmtp.sh == SKIP starttls-lmtp.sh (exit status: 77) SKIP: starttls-pop3.sh == SKIP starttls-pop3.sh (exit status: 77) SKIP: starttls-xmpp.sh == SKIP starttls-xmpp.sh (exit status: 77) SKIP: starttls-nntp.sh == SKIP starttls-nntp.sh (exit status: 77) SKIP: starttls-sieve.sh === SKIP starttls-sieve.sh (exit status: 77) SKIP: p11-kit-trust.sh == p11-kit trust module was not found SKIP p11-kit-trust.sh (exit status: 77) Testsuite summary for GnuTLS 3.6.13 # TOTAL: 471 # PASS: 455 # SKIP: 15 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See tests/test-suite.log Please report to b...@gnutls.org make[6]: *** [Makefile:8525: test-suite.log] Error 1 The conova buildds are IPv6-only, see #962019 for a similar problem in perl.
Processed: libgdf: autopkgtest needs update for new version of boost-defaults: deprecation warning on stderr
Processing control commands: > affects -1 src:boost-defaults Bug #962217 [src:libgdf] libgdf: autopkgtest needs update for new version of boost-defaults: deprecation warning on stderr Added indication that 962217 affects src:boost-defaults -- 962217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962217: libgdf: autopkgtest needs update for new version of boost-defaults: deprecation warning on stderr
Source: libgdf
Version: 0.1.3-3
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:boost-defaults
[X-Debbugs-CC: debian...@lists.debian.org,
boost-defau...@packages.debian.org]
Dear maintainer(s),
With a recent upload of boost-defaults the autopkgtest of libgdf fails
in testing when that autopkgtest is run with the binary packages of
boost-defaults from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
boost-defaults from testing1.71.0.3
libgdf from testing0.1.3-3
all others from testingfrom testing
I copied some of the output at the bottom of this report. If possible,
disable deprecation warnings as autopkgtest is not the place to test for
those or, if that's not possible, add the allow-stderr restriction such
that these warnings will be ignored.
Currently this regression is blocking the migration of boost-defaults to
testing [1]. Of course, boost-defaults shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in boost-defaults was intended and your package needs to update
to the new situation.
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=boost-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libgdf/5757118/log.gz
Copying data OK
Copying events
reading non-equidistant samples (NEQS) ... OK
writing non-equidistant samples .
OK
Comparing files OK
Removing test.gdf.tmp
autopkgtest [23:08:06]: test compile-and-run-tests: ---]
autopkgtest [23:08:07]: test compile-and-run-tests: - - - - - - - - - -
results - - - - - - - - - -
compile-and-run-tests FAIL stderr: In file included from
/usr/include/boost/detail/endian.hpp:9,
autopkgtest [23:08:07]: test compile-and-run-tests: - - - - - - - - - -
stderr - - - - - - - - - -
In file included from /usr/include/boost/detail/endian.hpp:9,
from /usr/include/GDF/Types.h:24,
from /usr/include/GDF/HeaderItem.h:22,
from /usr/include/GDF/SignalHeader.h:22,
from /usr/include/GDF/Channel.h:22,
from /usr/include/GDF/RecordBuffer.h:22,
from /usr/include/GDF/Writer.h:22,
from testCreateGDF.cpp:19:
/usr/include/boost/predef/detail/endian_compat.h:11:161: note: #pragma
message: The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER is deprecated.
Please include and use BOOST_ENDIAN_*_BYTE
instead
11 | #pragma message("The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER
is deprecated. Please include and use
BOOST_ENDIAN_*_BYTE instead")
|
^
In file included from /usr/include/boost/detail/endian.hpp:9,
from /usr/include/GDF/Types.h:24,
from /usr/include/GDF/HeaderItem.h:22,
from /usr/include/GDF/SignalHeader.h:22,
from /usr/include/GDF/Channel.h:22,
from /usr/include/GDF/Record.h:22,
from /usr/include/GDF/Reader.h:22,
from testDataTypes.cpp:21:
/usr/include/boost/predef/detail/endian_compat.h:11:161: note: #pragma
message: The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER is deprecated.
Please include and use BOOST_ENDIAN_*_BYTE
instead
11 | #pragma message("The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER
is deprecated. Please include and use
BOOST_ENDIAN_*_BYTE instead")
|
^
In file included from /usr/include/boost/detail/endian.hpp:9,
from /usr/include/GDF/Types.h:24,
from /usr/include/GDF/HeaderItem.h:22,
from /usr/include/GDF/SignalHeader.h:22,
from /usr/include/GDF/Channel.h:22,
from /usr/include/GDF/RecordBuffer.h:22,
from /usr/include/GDF/Writer.h:22,
from testHeader3.cpp:22:
/usr/include/boost/predef/detail/endian_compat.h:11:161: note: #pragma
message: The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER is deprecated.
Please include and use BOOST_ENDIAN_*_BYTE
instead
11 | #pragma message("The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER
is deprecated. Please include and use
BOOST_ENDIAN_*_BYTE instead")
|
^
In file included from /usr/include/boost/detail/endian.hpp:9,
from /usr/include/GDF/Types.h:24,
from /usr/include/GDF/HeaderItem.h:22,
from /usr/include/GDF/SignalHeader.h:22,
from /usr/include/GDF/Channel.h:22,
from /usr/include/GDF/RecordBuffer.h:22,
from /usr/include/GDF/Writer.h:22,
from testRWConsistency.cpp:22:
Bug#962213: package ftbfs on arm64 and armhf
Package: opencpn Version: 5.0.0+dfsg-1 Severity: serious Tags: sid bullseye patch The package ftbfs on arm64 and armhf, trying to link with -ldrm. Apparently libdrm-dev is an implicit b-d for x86 targets, but used explicitly. Fixed by b-d on libdrm-dev everywhere.
Bug#962183: marked as done (jellyfish FTBFS due to Rules-Requires-Root: no)
Your message dated Thu, 04 Jun 2020 15:06:37 + with message-id and subject line Bug#962183: fixed in jellyfish 2.3.0-6 has caused the Debian Bug report #962183, regarding jellyfish FTBFS due to Rules-Requires-Root: no 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.) -- 962183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jellyfish Version: 2.3.0-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=jellyfish ... ls -l debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so -r-xr-xr-x 1 buildd buildd 1630880 Jun 3 20:05 debian/tmp/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/jellyfish/jellyfish.so if [ ! -e debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so ] ; then sleep 1; fi chrpath --delete debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so open: Permission denied elf_open: Invalid argument make[1]: *** [debian/rules:36: override_dh_auto_install] Error 1 --- End Message --- --- Begin Message --- Source: jellyfish Source-Version: 2.3.0-6 Done: cru...@debian.org (Michael R. Crusoe) We believe that the bug you reported is fixed in the latest version of jellyfish, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated jellyfish 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, 04 Jun 2020 16:23:12 +0200 Source: jellyfish Architecture: source Version: 2.3.0-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Closes: 962183 Changes: jellyfish (2.3.0-6) unstable; urgency=medium . [ Andreas Tille ] * Fix permission of shared library Closes: #962183 Checksums-Sha1: e3392039f28549df2a87fc859ebf302c037d567a 2550 jellyfish_2.3.0-6.dsc dfdf6cb9208784f49dd43f234800926f24bcfa3f 13176 jellyfish_2.3.0-6.debian.tar.xz f5525434f3820f039372833246a47a1d817ad9d2 7760 jellyfish_2.3.0-6_source.buildinfo Checksums-Sha256: 2c9073cea5566550bcd6d7a89507c9b13183e1072e8972c58a9d4f17793cdfb0 2550 jellyfish_2.3.0-6.dsc 15261c8b51dfec511bc45ed715b64979d4f40a8273937c2e14d2c128dbfb0262 13176 jellyfish_2.3.0-6.debian.tar.xz 3c3c3ca218474cf913d0b9061915747890b22d3b6156333b5f11fc5e55fd48a3 7760 jellyfish_2.3.0-6_source.buildinfo Files: bc07876bca4f979e43c0992786d79064 2550 science optional jellyfish_2.3.0-6.dsc 50d9c4f5d2907b9d24517b1014a0310a 13176 science optional jellyfish_2.3.0-6.debian.tar.xz 1ed8f4fa53e8a844207279ef12c21800 7760 science optional jellyfish_2.3.0-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl7ZBPwACgkQPCZ2P2xn 5uLyCxAAwiLw4N4u+B2e4WTSVJwswXBIZxreCZwspL7BvLXVdaAplF5i5sRSTQP4 A5AfEbwDClqG97fP5vq9b4lfHCbVYmGEuHHQXY2ELWE3PvPg62zMWLBZYVjCHOaO 46GwDfo+D9mYJzACDTJbYUEuJxYFZKK3bYu6r+LWxgmWJrTbjPsusLyGrHNV8FvP sZj06bMIfwruZFz64HP2ZzxTqYPSPqe1chgiLDhgy9OdeVfdQAZouD3nAK8XlmLw d0qClhrWAeCH8u4lsdg2t5NfyeNark7rgez6dEAMy4wuXbkhUYr0uq+2/41XfEkJ yLhuJdI0mfRUCl3qZaBhetq5JAEucPNr7kbnKe0Pou1zPY1EfRs1hbm4+RGALKlT cLMGbTvO/8hVjJiAoL481ce8ANpJinmQAdJJhHLhvj+XhzfFZA0khyIZcRYwITe8 QiJCNjxqzfS5g82jlP2Hg1nsF/QI9WjZgTBS4QBEqAVv4aHQ0HRl2iXAQtRDjR4G I2nJJraJZKMU4TMmsYUXXyStyA3X4aRmJzRLlfyeCU9rILekn0c2RKmgqNWOlh9Y sDWNZW8WX8TlDHkHdVgj3T6azpbtePUniXmPtIims/oXj6pqGNecEUHySuSnLAPo 3HaAol8husGbLqsqUn9nx7JgPlGrtdZKge3zjeDko0p/j1rwXBg= =NkHs -END PGP SIGNATURE End Message ---
Bug#961602: castle-game-engine-doc: Depends on removed ttf-dejavu packages
Submitted patch in the VCS: https://salsa.debian.org/pascal-team/castle-game-engine/-/merge_requests/1
Bug#958040: marked as done (galera-3 FTBFS on armel: test failure)
Your message dated Thu, 04 Jun 2020 14:37:35 + with message-id and subject line Bug#958040: fixed in galera-3 25.3.29-3~exp1 has caused the Debian Bug report #958040, regarding galera-3 FTBFS on armel: test failure 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.) -- 958040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: galera-3 Version: 25.3.29-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=galera-3=armel=25.3.29-2=1587128672=0 ... builder_unit_test(["gcs/src/unit_tests/gcs_tests.passed"], ["gcs/src/unit_tests/gcs_tests"]) Running suite(s): GCS component message 100%: Checks: 1, Failures: 0, Errors: 0 Running suite(s): GCS send monitor 100%: Checks: 5, Failures: 0, Errors: 0 Running suite(s): GCS state message 100%: Checks: 5, Failures: 0, Errors: 0 Running suite(s): GCS FIFO functions 100%: Checks: 1, Failures: 0, Errors: 0 Running suite(s): GCS core protocol 100%: Checks: 1, Failures: 0, Errors: 0 Running suite(s): GCS defragmenter 100%: Checks: 1, Failures: 0, Errors: 0 Running suite(s): GCS node context 100%: Checks: 1, Failures: 0, Errors: 0 Running suite(s): GCS membership changes 100%: Checks: 1, Failures: 0, Errors: 0 Running suite(s): GCS group context 100%: Checks: 1, Failures: 0, Errors: 0 Running suite(s): GCS backend interface 100%: Checks: 1, Failures: 0, Errors: 0 Running suite(s): GCS state transfer FC 100%: Checks: 3, Failures: 0, Errors: 0 Total test failed: 0 g++ -o libgalera_smm.so -Wl,-z,relro -shared -Wl,--version-script=/<>/galera-sym.map galerautils/src/gu_abort.os galerautils/src/gu_dbug.os galerautils/src/gu_fifo.os galerautils/src/gu_lock_step.os galerautils/src/gu_log.os galerautils/src/gu_mem.os galerautils/src/gu_mmh3.os galerautils/src/gu_spooky.os galerautils/src/gu_crc32c.os galerautils/src/gu_rand.os galerautils/src/gu_threads.os galerautils/src/gu_hexdump.os galerautils/src/gu_to.os galerautils/src/gu_utils.os galerautils/src/gu_uuid.os galerautils/src/gu_backtrace.os galerautils/src/gu_limits.os galerautils/src/gu_time.os galerautils/src/gu_init.os www.evanjones.ca/crc32c.os galerautils/src/gu_vlq.os galerautils/src/gu_datetime.os galerautils/src/gu_exception.os galerautils/src/gu_serialize.os galerautils/src/gu_logger.os galerautils/src/gu_regex.os galerautils/src/gu_string_utils.os galerautils/src/gu_uri.os galerautils/src/gu_buffer.os galerautils/src/gu_utils++.os galerautils/src/gu_config.os galerautils/src/gu_fdesc.os galerautils/src/gu_mmap.os galerautils/src/gu_alloc.os galerautils/src/gu_rset.os galerautils/src/gu_resolver.os galerautils/src/gu_histogram.os galerautils/src/gu_stats.os galerautils/src/gu_asio.os galerautils/src/gu_debug_sync.os galerautils/src/gu_thread.os galerautils/src/gu_hexdump++.os galerautils/src/gu_uuid++.os gcache/src/GCache_seqno.os gcache/src/gcache_params.os gcache/src/gcache_page.os gcache/src/gcache_page_store.os gcache/src/gcache_rb_store.os gcache/src/gcache_mem_store.os gcache/src/GCache_memops.os gcache/src/GCache.os gcomm/src/conf.os gcomm/src/defaults.os gcomm/src/datagram.os gcomm/src/evs_consensus.os gcomm/src/evs_input_map2.os gcomm/src/evs_message2.os gcomm/src/evs_node.os gcomm/src/evs_proto.os gcomm/src/gmcast.os gcomm/src/gmcast_proto.os gcomm/src/pc.os gcomm/src/pc_proto.os gcomm/src/protonet.os gcomm/src/protostack.os gcomm/src/transport.os gcomm/src/uuid.os gcomm/src/view.os gcomm/src/socket.os gcomm/src/asio_tcp.os gcomm/src/asio_udp.os gcomm/src/asio_protonet.os gcs/src/gcs_params.os gcs/src/gcs_conf.os gcs/src/gcs_fifo_lite.os gcs/src/gcs_msg_type.os gcs/src/gcs_comp_msg.os gcs/src/gcs_sm.os gcs/src/gcs_backend.os gcs/src/gcs_dummy.os gcs/src/gcs_act_proto.os gcs/src/gcs_defrag.os gcs/src/gcs_state_msg.os gcs/src/gcs_node.os gcs/src/gcs_group.os gcs/src/gcs_core.os gcs/src/gcs_fc.os gcs/src/gcs.os gcs/src/gcs_gcomm.os galera/src/mapped_buffer.os galera/src/write_set.os galera/src/data_set.os galera/src/key_set.os galera/src/write_set_ng.os galera/src/trx_handle.os galera/src/key_entry_os.os galera/src/wsdb.os galera/src/certification.os galera/src/galera_service_thd.os galera/src/wsrep_params.os galera/src/replicator_smm_params.os galera/src/gcs_action_source.os galera/src/galera_info.os galera/src/replicator.os galera/src/ist.os galera/src/gcs_dummy.os galera/src/saved_state.os galera/src/libmmgalera++-replicator_smm.os galera/src/libmmgalera++-replicator_str.os galera/src/libmmgalera++-replicator_smm_stats.os
Bug#962190: primer3: please disable Big Endian tests on autopkgtests too
control: tags -1 patch
This might work better:
--- primer3-2.4.0/debian/tests/run-unit-test2018-05-28 15:44:30.0
+0200
+++ primer3-2.4.0/debian/tests/run-unit-test2020-06-04 11:47:04.0
+0200
@@ -8,6 +8,12 @@
AUTOPKGTEST_TMP=`mktemp -d /tmp/${pkg}-test.XX`
fi
+BUILDARCH=$(dpkg-architecture -q DEB_BUILD_ARCH_ENDIAN)
+
+P3CORE_FAILED_TESTS="primer_masker primer_masker_formatted"
+
+FAILED_TESTS="testmasker"
+
cp -a /usr/share/doc/${pkg}/examples/* $AUTOPKGTEST_TMP
cd $AUTOPKGTEST_TMP
@@ -19,6 +25,16 @@
ln -s /usr/bin/ntthal ./src/ntthal
ln -s /usr/bin/oligotm ./src/oligotm
+if [ $BUILDARCH = big ]; then
+ cp -a test/p3test.pl test/p3test.pl~
+ cp -a test/Makefile test/Makefile~
+ # exclude tests known to fail on big endian
+ # See README.source for further explanation.
+ for tst in $P3CORE_FAILED_TESTS ; do sed -i "/$tst/d" test/p3test.pl ; done
+ sed -i "0,/$FAILED_TESTS/s///" test/Makefile
+ sed -i "/$FAILED_TESTS/,/endif/d" test/Makefile
+fi
+
cd test/;
echo "testcmdline:"
@@ -36,4 +52,12 @@
echo "testtm:"
perl oligotm_test.pl ${TESTOPTS}
+cd ..
+
+if [ $BUILDARCH = big ]; then
+ # restore original test file
+ mv test/p3test.pl~ test/p3test.pl
+ mv test/Makefile~ test/Makefile
+fi
+
echo "PASS"
Processed: Re: buildstream: Event loop broken on Python 3.8
Processing control commands: > tag -1 upstream fixed-upstream patch Bug #962197 [buildstream] buildstream: Event loop broken on Python 3.8 Added tag(s) upstream, patch, and fixed-upstream. -- 962197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962197: buildstream: Event loop broken on Python 3.8
Control: tag -1 upstream fixed-upstream patch Although there are still some issues with 3.8 upstream, this one is actually fixed. Here's the patch. Ben. -- Ben Hutchings, Software Developer Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street Manchester, M1 2HF, United Kingdom From: Chandan Singh Date: Mon, 21 Oct 2019 14:38:07 +0100 Subject: _scheduler/scheduler.py: Enforce SafeChildWatcher Origin: https://gitlab.com/BuildStream/buildstream/-/commit/0eca9e6a4a01d1094987773bce58d9d3e501f1e8 Bug-Debian: https://bugs.debian.org/962197 In Python 3.8, `ThreadedChildWatcher` is the default watcher that causes issues with our scheduler. Enforce use of `SafeChildWatcher`. [benh: Backported to 1.4.1: adjust filename] --- buildstream/_scheduler/scheduler.py | 6 ++ 1 file changed, 6 insertions(+) --- a/buildstream/_scheduler/scheduler.py +++ b/buildstream/_scheduler/scheduler.py @@ -137,6 +137,12 @@ class Scheduler(): # Hold on to the queues to process self.queues = queues +# NOTE: Enforce use of `SafeChildWatcher` as we generally don't want +# background threads. +# In Python 3.8+, `ThreadedChildWatcher` is the default watcher, and +# not `SafeChildWatcher`. +asyncio.set_child_watcher(asyncio.SafeChildWatcher()) + # Ensure that we have a fresh new event loop, in case we want # to run another test in this thread. self.loop = asyncio.new_event_loop()
Bug#890993: fixed in primer3 2.4.0-2
control: close -1 Lets close, I opened a new one in the meanwhile G.
Bug#962205: buildstream: Missing dependency on bubblewrap
Package: buildstream Version: 1.4.1-1 Severity: serious Dear Maintainer, bubblewrap is a run-time dependency for BuildStream on Linux, but is not included in the package dependencies. Ben. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF- 8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages buildstream depends on: ii python3 3.8.2-3 ii python3-buildstream 1.4.1-1 Versions of packages buildstream recommends: ii python3-bst-external 0.18.0-1 buildstream suggests no packages. -- no debconf information -- Ben Hutchings, Software Developer Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street Manchester, M1 2HF, United Kingdom
Processed: Re: primer3: please disable Big Endian tests on autopkgtests too
Processing control commands: > tags -1 patch Bug #962190 [src:primer3] primer3: please disable Big Endian tests on autopkgtests too Added tag(s) patch. -- 962190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#890993: fixed in primer3 2.4.0-2
Processing control commands: > close -1 Bug #890993 [src:primer3] primer3 FTBFS on big endian: test failure Marked Bug as done -- 890993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962197: buildstream: Event loop broken on Python 3.8
Package: buildstream Version: 1.4.1-1 Severity: grave Dear Maintainer, Un-cached builds with builstream currently fail like this: [--:--:--][][] BUG no running event loop Traceback (most recent call last): File "/usr/bin/bst", line 8, in sys.exit(cli()) File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/buildstream/_frontend/cli.py", line 173, in override_main original_main(self, args=args, prog_name=prog_name, complete_var=None, File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 27, in new_func return f(get_current_context().obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/buildstream/_frontend/cli.py", line 340, in build app.stream.build(elements, File "/usr/lib/python3/dist-packages/buildstream/_stream.py", line 211, in build self._run() File "/usr/lib/python3/dist-packages/buildstream/_stream.py", line 1022, in _run _, status = self._scheduler.run(self.queues) File "/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 153, in run self._sched() File "/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 427, in _sched self._sched_queue_jobs() File "/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 401, in _sched_queue_jobs self._spawn_job(job) File "/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 281, in _spawn_job job.spawn() File "/usr/lib/python3/dist-packages/buildstream/_scheduler/jobs/job.py", line 162, in spawn self._watcher.add_child_handler(self._process.pid, self._parent_child_completed) File "/usr/lib/python3.8/asyncio/unix_events.py", line 1293, in add_child_handler loop = events.get_running_loop() RuntimeError: no running event loop This was reported upstream as: https://gitlab.com/BuildStream/buildstream/-/issues/1246 but is now tracked in: https://gitlab.com/BuildStream/buildstream/-/issues/1173 Ben. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages buildstream depends on: ii python3 3.8.2-3 ii python3-buildstream 1.4.1-1 Versions of packages buildstream recommends: ii python3-bst-external 0.18.0-1 buildstream suggests no packages. -- no debconf information -- Ben Hutchings, Software Developer Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street Manchester, M1 2HF, United Kingdom
Bug#961863: zatacka: Depends/Build-Depends on cruft package ttf-dejavu-core
Patch submitted to the VCS: https://github.com/alexdantas/zatacka.debian/pull/3
Bug#890929: marked as done (golang-pault-go-ykpiv FTBFS with golang-1.10-go: invalid flag in #cgo LDFLAGS: -Wl,--allow-multiple-definition)
Your message dated Thu, 04 Jun 2020 12:33:42 +
with message-id
and subject line Bug#890929: fixed in golang-pault-go-ykpiv 1.3.1-1
has caused the Debian Bug report #890929,
regarding golang-pault-go-ykpiv FTBFS with golang-1.10-go: invalid flag in #cgo
LDFLAGS: -Wl,--allow-multiple-definition
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.)
--
890929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-pault-go-ykpiv
Version: 1.1-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-pault-go-ykpiv.html
...
dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install
-gcflags=\"-trimpath=/build/1st/golang-pault-go-ykpiv-1.1/obj-x86_64-linux-gnu/src\"
-asmflags=\"-trimpath=/build/1st/golang-pault-go-ykpiv-1.1/obj-x86_64-linux-gnu/src\"
-v -p 16 pault.ag/go/ykpiv pault.ag/go/ykpiv/internal/bytearray
pault.ag/go/ykpiv/internal/pkcs1v15
golang.org/x/crypto/pbkdf2
pault.ag/go/ykpiv/internal/pkcs1v15
pault.ag/go/ykpiv/internal/bytearray
pault.ag/go/ykpiv
go build pault.ag/go/ykpiv: invalid flag in #cgo LDFLAGS:
-Wl,--allow-multiple-definition
dh_auto_build: cd obj-x86_64-linux-gnu && go install
-gcflags=\"-trimpath=/build/1st/golang-pault-go-ykpiv-1.1/obj-x86_64-linux-gnu/src\"
-asmflags=\"-trimpath=/build/1st/golang-pault-go-ykpiv-1.1/obj-x86_64-linux-gnu/src\"
-v -p 16 pault.ag/go/ykpiv pault.ag/go/ykpiv/internal/bytearray
pault.ag/go/ykpiv/internal/pkcs1v15 returned exit code 1
make: *** [debian/rules:4: build] Error 1
--- End Message ---
--- Begin Message ---
Source: golang-pault-go-ykpiv
Source-Version: 1.3.1-1
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
golang-pault-go-ykpiv, 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 890...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated golang-pault-go-ykpiv
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 31 May 2020 18:02:11 +0530
Source: golang-pault-go-ykpiv
Architecture: source
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team
Changed-By: Nilesh Patra
Closes: 890929
Changes:
golang-pault-go-ykpiv (1.3.1-1) unstable; urgency=medium
.
* Team Upload.
.
[ aviau ]
* point Vcs-* urls to salsa.debian.org
.
[ Nilesh Patra ]
* New upstream version 1.3.1 (Closes: #890929)
* Change "Architecture: any"
* Fix with cme
* Add "Rules-Requires-Root:no"
* Add upstream/metadata
* Really add VCS - URLs
* Add "Built-Using: ${misc:Built-Using}"
* Add manpage
Checksums-Sha1:
b477acf6bbd25264730d182c2c03ddbde2c36729 2230 golang-pault-go-ykpiv_1.3.1-1.dsc
97078a9e54384878d28e416ad82753ed584b060d 22785
golang-pault-go-ykpiv_1.3.1.orig.tar.gz
ed07757fbecb1890feb21fe73bc1c07862fd4a98 4224
golang-pault-go-ykpiv_1.3.1-1.debian.tar.xz
1443358dfa92f8ac4cbd8cc71c883e351c86a318 6237
golang-pault-go-ykpiv_1.3.1-1_amd64.buildinfo
Checksums-Sha256:
9813b805ef62fdf36fdfb8a4d7f6d0dd1bc309911b5108e60cf1a9ef4f722c4c 2230
golang-pault-go-ykpiv_1.3.1-1.dsc
a41c5dbca4497f33ba8853703e386eab09132ec3bea9995de03ab56e2625593b 22785
golang-pault-go-ykpiv_1.3.1.orig.tar.gz
a2966f03527f1416f047f6c02cf0753a45a3f1242aace5c3512702f9973b906b 4224
golang-pault-go-ykpiv_1.3.1-1.debian.tar.xz
63a3308bdb0b1fa0bf04bd7d572506de57f8a99c94c6057c62ee73127a6f27a7 6237
golang-pault-go-ykpiv_1.3.1-1_amd64.buildinfo
Files:
92220d0bb4ed5e9175e0eaae5332fa7b 2230 devel optional
golang-pault-go-ykpiv_1.3.1-1.dsc
f352571aa5e6b09b3abdc5392973a5bd 22785 devel optional
golang-pault-go-ykpiv_1.3.1.orig.tar.gz
f016bb64414e58ccec42bb85d540c62c 4224 devel optional
golang-pault-go-ykpiv_1.3.1-1.debian.tar.xz
405aeb22e3b0c9cfe3e701eee3551934 6237 devel optional
golang-pault-go-ykpiv_1.3.1-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7Y5/kRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHrbhAAgBNTnCsLqsecUTD1LALMGa7F/CHkgD7V
Processed: enchant -> enchant-2 transition
Processing commands for cont...@bugs.debian.org: > # We don't want to ship two enchants in bullseye. Dear maintainers, > # you can lower the severity until December 2020 if you have a plan to > # fix the issue before the bullseye transition freeze, but please > # document that in the bug in case you do. > severity 956710 serious Bug #956710 [src:abiword] abiword: Please witch to enchant-2 instead of enchant(1) Severity set to 'serious' from 'important' > severity 951143 serious Bug #951143 [src:bluefish] bluefish: Please migrate to enchant-2 Severity set to 'serious' from 'important' > severity 951271 serious Bug #951271 [src:java-gnome] java-gnome: Please migration from enchant(1) to enchant-2 Severity set to 'serious' from 'important' > severity 956700 serious Bug #956700 [src:kvirc] kvirc: Please witch to enchant-2 instead of enchant(1) Severity set to 'serious' from 'important' > severity 954855 serious Bug #954855 [php7.4-enchant] php7.4-enchant: Please switch from enchant(1) to enchant-2 Severity set to 'serious' from 'important' > severity 956691 serious Bug #956691 [src:psi] psi: Please witch to enchant-2 instead of enchant(1) Severity set to 'serious' from 'important' > severity 956680 serious Bug #956680 [src:xneur] xneur: Please migrate to enchant-2 Severity set to 'serious' from 'important' > severity 951140 serious Bug #951140 [src:geany-plugins] geany-plugins: Please switch from enchant(1) to enchant-2 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 951140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951140 951143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951143 951271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951271 954855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954855 956680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956680 956691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956691 956700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956700 956710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962172: closing 962172
close 962172 5.70.0-2 thanks -- Fixed in 5.70.0-2. -- Pino Toscano
Processed: closing 962172
Processing commands for cont...@bugs.debian.org: > close 962172 5.70.0-2 Bug #962172 [src:baloo-kf5] baloo-kf5: autopkgtest regression: dh_acc: error: abi-compliance-checker Marked as fixed in versions baloo-kf5/5.70.0-2. Bug #962172 [src:baloo-kf5] baloo-kf5: autopkgtest regression: dh_acc: error: abi-compliance-checker Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 962172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962190: primer3: please disable Big Endian tests on autopkgtests too
Source: primer3
Version: 2.4.0-2
Severity: serious
Hello, can you please apply the same on autopkgtests? now autopkgtests failures
are considered RC buggy
something like this might work:
--- primer3-2.4.0/debian/changelog 2018-05-28 15:44:30.0 +0200
+++ primer3-2.4.0/debian/changelog 2020-06-04 11:47:04.0 +0200
@@ -1,3 +1,9 @@
+primer3 (2.4.0-2.1) unstable; urgency=medium
+
+ * Also skip autopkgtests that fail on big endian (see: 890993,) Closes: #-1
+
+ -- Gianfranco Costamagna Thu, 04 Jun 2020
11:47:04 +0200
+
primer3 (2.4.0-2) unstable; urgency=medium
[ Liubov Chuprikova ]
diff -Nru primer3-2.4.0/debian/tests/run-unit-test
primer3-2.4.0/debian/tests/run-unit-test
--- primer3-2.4.0/debian/tests/run-unit-test2018-05-28 15:44:30.0
+0200
+++ primer3-2.4.0/debian/tests/run-unit-test2020-06-04 11:47:04.0
+0200
@@ -8,6 +8,13 @@
AUTOPKGTEST_TMP=`mktemp -d /tmp/${pkg}-test.XX`
fi
+BUILDARCH=$(dpkg-architecture -q DEB_BUILD_ARCH_ENDIAN)
+
+P3CORE_FAILED_TESTS='primer_masker' \
+ 'primer_masker_formatted'
+
+FAILED_TESTS=testmasker
+
cp -a /usr/share/doc/${pkg}/examples/* $AUTOPKGTEST_TMP
cd $AUTOPKGTEST_TMP
@@ -19,6 +26,16 @@
ln -s /usr/bin/ntthal ./src/ntthal
ln -s /usr/bin/oligotm ./src/oligotm
+if [ $BUILDARCH = big ]; then
+ cp -a test/p3test.pl test/p3test.pl~
+ cp -a test/Makefile test/Makefile~
+ # exclude tests known to fail on big endian
+ # See README.source for further explanation.
+ for tst in $(P3CORE_FAILED_TESTS) ; do sed -i "/$${tst}/d" test/p3test.pl ;
done
+ sed -i "0,/$(FAILED_TESTS)/s///" test/Makefile
+ sed -i "/$(FAILED_TESTS)/,/endif/d" test/Makefile
+fi
+
cd test/;
echo "testcmdline:"
@@ -36,4 +53,12 @@
echo "testtm:"
perl oligotm_test.pl ${TESTOPTS}
+cd ..
+
+if [ $BUILDARCH = big ]; then
+ # restore original test file
+ mv test/p3test.pl~ test/p3test.pl
+ mv test/Makefile~ test/Makefile
+fi
+
echo "PASS"
On Tue, 29 May 2018 17:36:48 + Liubov Chuprikova
wrote:
> Source: primer3
> Source-Version: 2.4.0-2
>
> We believe that the bug you reported is fixed in the latest version of
> primer3, 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 890...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Liubov Chuprikova (supplier of updated primer3
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Mon, 28 May 2018 13:44:30 +
> Source: primer3
> Binary: primer3 primer3-examples
> Architecture: source
> Version: 2.4.0-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Med Packaging Team
>
> Changed-By: Liubov Chuprikova
> Description:
> primer3- tool to design flanking oligo nucleotides for DNA amplification
> primer3-examples - tool to design flanking oligo nucleotides for DNA
> amplification (
> Closes: 890993
> Changes:
> primer3 (2.4.0-2) unstable; urgency=medium
> .
>[ Liubov Chuprikova ]
>* Team upload.
>* Skip tests that fail on big endian
> Closes: #890993
>* Added d/README.source with explanation why some tests are skipped
>* debian/patches/p3test_fix_exit_status.patch: Fix test to show correct
> exit
> status
> .
>[ Andreas Tille ]
>* Point Vcs fields to salsa.debian.org
>* Standards-Version: 4.1.4
> Checksums-Sha1:
> ed7288049fca41a312d5d528d3e57e0b51be9bdc 2117 primer3_2.4.0-2.dsc
> 9d7f7874ef42796bd45181a610ad4d2d9193ef02 12060 primer3_2.4.0-2.debian.tar.xz
> 60fe57fc774ab8b537785d4c6d07e54647aabd70 5964 primer3_2.4.0-2_amd64.buildinfo
> Checksums-Sha256:
> 541ec07c9092995dd359620326630c45135321868ee2c2350ef61e1d4d67628d 2117
> primer3_2.4.0-2.dsc
> 96247e4223393e0056a8886209b1bb37abfa7dc7fb00eca4e3e695daf62dd71e 12060
> primer3_2.4.0-2.debian.tar.xz
Bug#948450: djview-plugin might be useless now
On Thu, Jun 04 2020 at 11:24 +01, Barak A. Pearlmutter wrote: > It sounds like djview-plugin should just be removed, since it supports > a now-dead plugin API. > > Any objections? What about consulting this with Leon Bottou? Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#890993: fixed in primer3 2.4.0-2
Hello, can you please apply the same on autopkgtests? now autopkgtests failures
are considered RC buggy
something like this might work:
--- primer3-2.4.0/debian/changelog 2018-05-28 15:44:30.0 +0200
+++ primer3-2.4.0/debian/changelog 2020-06-04 11:47:04.0 +0200
@@ -1,3 +1,9 @@
+primer3 (2.4.0-2ubuntu1) groovy; urgency=medium
+
+ * Also skip autopkgtests that fail on big endian (see: 890993)
+
+ -- Gianfranco Costamagna Thu, 04 Jun 2020
11:47:04 +0200
+
primer3 (2.4.0-2) unstable; urgency=medium
[ Liubov Chuprikova ]
diff -Nru primer3-2.4.0/debian/tests/run-unit-test
primer3-2.4.0/debian/tests/run-unit-test
--- primer3-2.4.0/debian/tests/run-unit-test2018-05-28 15:44:30.0
+0200
+++ primer3-2.4.0/debian/tests/run-unit-test2020-06-04 11:47:04.0
+0200
@@ -8,6 +8,13 @@
AUTOPKGTEST_TMP=`mktemp -d /tmp/${pkg}-test.XX`
fi
+BUILDARCH=$(dpkg-architecture -q DEB_BUILD_ARCH_ENDIAN)
+
+P3CORE_FAILED_TESTS='primer_masker' \
+ 'primer_masker_formatted'
+
+FAILED_TESTS=testmasker
+
cp -a /usr/share/doc/${pkg}/examples/* $AUTOPKGTEST_TMP
cd $AUTOPKGTEST_TMP
@@ -19,6 +26,16 @@
ln -s /usr/bin/ntthal ./src/ntthal
ln -s /usr/bin/oligotm ./src/oligotm
+if [ $BUILDARCH = big ]; then
+ cp -a test/p3test.pl test/p3test.pl~
+ cp -a test/Makefile test/Makefile~
+ # exclude tests known to fail on big endian
+ # See README.source for further explanation.
+ for tst in $(P3CORE_FAILED_TESTS) ; do sed -i "/$${tst}/d" test/p3test.pl ;
done
+ sed -i "0,/$(FAILED_TESTS)/s///" test/Makefile
+ sed -i "/$(FAILED_TESTS)/,/endif/d" test/Makefile
+fi
+
cd test/;
echo "testcmdline:"
@@ -36,4 +53,12 @@
echo "testtm:"
perl oligotm_test.pl ${TESTOPTS}
+cd ..
+
+if [ $BUILDARCH = big ]; then
+ # restore original test file
+ mv test/p3test.pl~ test/p3test.pl
+ mv test/Makefile~ test/Makefile
+fi
+
echo "PASS"
On Tue, 29 May 2018 17:36:48 + Liubov Chuprikova
wrote:
> Source: primer3
> Source-Version: 2.4.0-2
>
> We believe that the bug you reported is fixed in the latest version of
> primer3, 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 890...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Liubov Chuprikova (supplier of updated primer3
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Mon, 28 May 2018 13:44:30 +
> Source: primer3
> Binary: primer3 primer3-examples
> Architecture: source
> Version: 2.4.0-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Med Packaging Team
>
> Changed-By: Liubov Chuprikova
> Description:
> primer3- tool to design flanking oligo nucleotides for DNA amplification
> primer3-examples - tool to design flanking oligo nucleotides for DNA
> amplification (
> Closes: 890993
> Changes:
> primer3 (2.4.0-2) unstable; urgency=medium
> .
>[ Liubov Chuprikova ]
>* Team upload.
>* Skip tests that fail on big endian
> Closes: #890993
>* Added d/README.source with explanation why some tests are skipped
>* debian/patches/p3test_fix_exit_status.patch: Fix test to show correct
> exit
> status
> .
>[ Andreas Tille ]
>* Point Vcs fields to salsa.debian.org
>* Standards-Version: 4.1.4
> Checksums-Sha1:
> ed7288049fca41a312d5d528d3e57e0b51be9bdc 2117 primer3_2.4.0-2.dsc
> 9d7f7874ef42796bd45181a610ad4d2d9193ef02 12060 primer3_2.4.0-2.debian.tar.xz
> 60fe57fc774ab8b537785d4c6d07e54647aabd70 5964 primer3_2.4.0-2_amd64.buildinfo
> Checksums-Sha256:
> 541ec07c9092995dd359620326630c45135321868ee2c2350ef61e1d4d67628d 2117
> primer3_2.4.0-2.dsc
> 96247e4223393e0056a8886209b1bb37abfa7dc7fb00eca4e3e695daf62dd71e 12060
> primer3_2.4.0-2.debian.tar.xz
Bug#948450: djview-plugin might be useless now
On Thu, Jun 04, 2020 at 12:08:51PM +0200, Janusz S. Bień wrote: > On Thu, Jun 04 2020 at 13:00 +03, Adrian Bunk wrote: > > On Thu, Jun 04, 2020 at 11:36:32AM +0200, Janusz S. Bień wrote: > >> On Wed, 08 Jan 2020 21:13:33 +0200 Adrian Bunk wrote: > >> > Package: djview-plugin > >> > Version: 4.11-2 > >> > Severity: serious > >> > > >> > This package provides an NPAPI plugin. > >> > All major browsers have dropped support for NPAPI. > >> > >> Looks like there are still some for which it is usable, unfortunately > >> the package does not recommend them. > >> > >> Reportedly it works with epiphane-browser: > >> > >> https://sourceforge.net/p/djvu/bugs/319/#c805/b347 > > > > In the version of epiphany-browser in bullseye NPAPI plugins are > > definitely no longer supported. > > djview-plugin in bullseye recommends chromium - I'm curious why >... 10 years ago all browsers supported NPAPI plugins. Flash was the last important NPAPI plugin, now Flash is dead and NPAPI support removed from browsers. > Janusz cu Adrian
Bug#948450: djview-plugin might be useless now
It sounds like djview-plugin should just be removed, since it supports a now-dead plugin API. Any objections?
Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no
On Thu, Jun 04, 2020 at 01:11:37PM +0300, Adrian Bunk wrote: > Your reply omits the relevant part from the log: > > > -r-xr-xr-x 1 buildd buildd 1630880 Jun 3 20:05 > > > debian/tmp/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/jellyfish/jellyfish.so > ^ > I don't know why this lacks the 'w', but "chmod 644" should workaround it. Ahhh, no idea why this shared lib always creates hassle. I adapted my fix for the patch in git. Waiting with upload for a solution for the 32bit issue. Thanks a lot as always Andreas. -- http://fam-tille.de
Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no
On Thu, Jun 04, 2020 at 11:54:54AM +0200, Andreas Tille wrote: > Control: tags -1 pending > > On Thu, Jun 04, 2020 at 12:44:30PM +0300, Adrian Bunk wrote: > > if [ ! -e debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so ] ; then > > sleep 1; fi > > chrpath --delete debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so > > open: Permission denied > > elf_open: Invalid argument > > make[1]: *** [debian/rules:36: override_dh_auto_install] Error 1 > > I commented "Rules-Requires-Root: no" in d/control to fix this. > However, I'd love to understand why chrpath would require root > permissions. Your reply omits the relevant part from the log: > > -r-xr-xr-x 1 buildd buildd 1630880 Jun 3 20:05 > > debian/tmp/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/jellyfish/jellyfish.so ^ I don't know why this lacks the 'w', but "chmod 644" should workaround it. > Kind regards > >Andreas. cu Adrian
Bug#948450: djview-plugin might be useless now
On Thu, Jun 04 2020 at 13:00 +03, Adrian Bunk wrote: > On Thu, Jun 04, 2020 at 11:36:32AM +0200, Janusz S. Bień wrote: >> On Wed, 08 Jan 2020 21:13:33 +0200 Adrian Bunk wrote: >> > Package: djview-plugin >> > Version: 4.11-2 >> > Severity: serious >> > >> > This package provides an NPAPI plugin. >> > All major browsers have dropped support for NPAPI. >> >> Looks like there are still some for which it is usable, unfortunately >> the package does not recommend them. >> >> Reportedly it works with epiphane-browser: >> >> https://sourceforge.net/p/djvu/bugs/319/#c805/b347 > > In the version of epiphany-browser in bullseye NPAPI plugins are > definitely no longer supported. djview-plugin in bullseye recommends chromium - I'm curious why, because the plugin doesn't seem to work with it, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962181 Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#948450: djview-plugin might be useless now
On Thu, Jun 04, 2020 at 11:36:32AM +0200, Janusz S. Bień wrote: > On Wed, 08 Jan 2020 21:13:33 +0200 Adrian Bunk wrote: > > Package: djview-plugin > > Version: 4.11-2 > > Severity: serious > > > > This package provides an NPAPI plugin. > > All major browsers have dropped support for NPAPI. > > Looks like there are still some for which it is usable, unfortunately > the package does not recommend them. > > Reportedly it works with epiphane-browser: > > https://sourceforge.net/p/djvu/bugs/319/#c805/b347 In the version of epiphany-browser in bullseye NPAPI plugins are definitely no longer supported. > Regards > > Janusz cu Adrian
Processed: Re: Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no
Processing control commands: > tags -1 pending Bug #962183 [src:jellyfish] jellyfish FTBFS due to Rules-Requires-Root: no Added tag(s) pending. -- 962183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> unarchive 890993
Bug #890993 {Done: Liubov Chuprikova } [src:primer3]
primer3 FTBFS on big endian: test failure
Unarchived Bug 890993
> reopen 890993
Bug #890993 {Done: Liubov Chuprikova } [src:primer3]
primer3 FTBFS on big endian: test failure
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions primer3/2.4.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
890993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no
Control: tags -1 pending On Thu, Jun 04, 2020 at 12:44:30PM +0300, Adrian Bunk wrote: > if [ ! -e debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so ] ; then > sleep 1; fi > chrpath --delete debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so > open: Permission denied > elf_open: Invalid argument > make[1]: *** [debian/rules:36: override_dh_auto_install] Error 1 I commented "Rules-Requires-Root: no" in d/control to fix this. However, I'd love to understand why chrpath would require root permissions. Kind regards Andreas. -- http://fam-tille.de
Bug#948450: djview-plugin might be useless now
On Wed, 08 Jan 2020 21:13:33 +0200 Adrian Bunk wrote: > Package: djview-plugin > Version: 4.11-2 > Severity: serious > > This package provides an NPAPI plugin. > All major browsers have dropped support for NPAPI. Looks like there are still some for which it is usable, unfortunately the package does not recommend them. Reportedly it works with epiphane-browser: https://sourceforge.net/p/djvu/bugs/319/#c805/b347 Regards Janusz -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien
Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no
Source: jellyfish Version: 2.3.0-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=jellyfish ... ls -l debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so -r-xr-xr-x 1 buildd buildd 1630880 Jun 3 20:05 debian/tmp/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/jellyfish/jellyfish.so if [ ! -e debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so ] ; then sleep 1; fi chrpath --delete debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so open: Permission denied elf_open: Invalid argument make[1]: *** [debian/rules:36: override_dh_auto_install] Error 1
Bug#962179: wfmath FTBFS on 32bit: symbol differences
Source: wfmath Version: 1.0.2+dfsg1-7 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=wfmath=sid ... dh_makeshlibs -a -a dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libwfmath-1.0-1v5/DEBIAN/symbols doesn't match completely debian/libwfmath-1.0-1v5.symbols --- debian/libwfmath-1.0-1v5.symbols (libwfmath-1.0-1v5_1.0.2+dfsg1-7_i386) +++ dpkg-gensymbolsSnl7JC 2020-06-04 01:44:11.048846158 + @@ -49,6 +49,7 @@ _ZN6WFMath13_ScaleEpsilonEfff@Base 1.0.0 _ZN6WFMath14BoundingSphereILi2ESt6vectorEENS_4BallIXT_EEERKT0_INS_5PointIXT_EEESaIS6_EE@Base 0.3.11 _ZN6WFMath14BoundingSphereILi3ESt6vectorEENS_4BallIXT_EEERKT0_INS_5PointIXT_EEESaIS6_EE@Base 1.0.0 + _ZN6WFMath14SloppyDistanceILi3EEEfRKNS_5PointIXT_EEES4_@Base 1.0.2+dfsg1-7 _ZN6WFMath14_ReadCoordListERSiPfi@Base 0.3.11 _ZN6WFMath15SquaredDistanceILi2EEEfRKNS_5PointIXT_EEES4_@Base 0.3.11 _ZN6WFMath15SquaredDistanceILi3EEEfRKNS_5PointIXT_EEES4_@Base 0.3.11 @@ -607,10 +608,10 @@ (optional=inline)_ZN6WFMath9_miniball5BasisILi3EE4pushERKNS0_13Wrapped_arrayILi3EEE@Base 1.0.0 (optional=inline)_ZN6WFMath9_miniball8MiniballILi2EE13move_to_frontESt14_List_iteratorINS0_13Wrapped_arrayILi2@Base 0.3.11 _ZN6WFMath9_miniball8MiniballILi2EE6mtf_mbESt14_List_iteratorINS0_13Wrapped_arrayILi2@Base 0.3.11 - (optional=GCC10_added)_ZN6WFMath9_miniball8MiniballILi2EE8pivot_mbESt14_List_iteratorINS0_13Wrapped_arrayILi2@Base 1.0.2 +#MISSING: 1.0.2+dfsg1-7# (optional=GCC10_added)_ZN6WFMath9_miniball8MiniballILi2EE8pivot_mbESt14_List_iteratorINS0_13Wrapped_arrayILi2@Base 1.0.2 (optional=inline)_ZN6WFMath9_miniball8MiniballILi3EE13move_to_frontESt14_List_iteratorINS0_13Wrapped_arrayILi3@Base 1.0.0 _ZN6WFMath9_miniball8MiniballILi3EE6mtf_mbESt14_List_iteratorINS0_13Wrapped_arrayILi3@Base 1.0.0 - (optional=GCC10_added)_ZN6WFMath9_miniball8MiniballILi3EE8pivot_mbESt14_List_iteratorINS0_13Wrapped_arrayILi3@Base 1.0.2 +#MISSING: 1.0.2+dfsg1-7# (optional=GCC10_added)_ZN6WFMath9_miniball8MiniballILi3EE8pivot_mbESt14_List_iteratorINS0_13Wrapped_arrayILi3@Base 1.0.2 _ZN6WFMathdVILi2EEERNS_6VectorIXT_EEES3_f@Base 0.3.11 _ZN6WFMathdVILi3EEERNS_6VectorIXT_EEES3_f@Base 0.3.11 _ZN6WFMathdvILi2EEENS_6VectorIXT_EEERKS2_f@Base 0.3.11 @@ -1014,9 +1015,11 @@ (regex|optional=inline)_ZNSt6vectorIfSaIfEE17_M_default_appendE[mj]@Base 1.0.2 _ZNSt6vectorIfSaIfEE17_M_realloc_insertIJRKfEEEvN9__gnu_cxx17__normal_iteratorIPfS1_EEDpOT_@Base 1.0.2 (optional=inline)_ZNSt6vectorIfSaIfEE6insertEN9__gnu_cxx17__normal_iteratorIPKfS1_EERS4_@Base 1.0.2 - _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflfNS0_5__ops15_Iter_less_iterEEvT_T0_SA_T1_T2_@Base 1.0.2 + _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfifNS0_5__ops15_Iter_less_iterEEvT_T0_SA_T1_T2_@Base 1.0.2+dfsg1-7 +#MISSING: 1.0.2+dfsg1-7# _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflfNS0_5__ops15_Iter_less_iterEEvT_T0_SA_T1_T2_@Base 1.0.2 _ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfNS0_5__ops15_Iter_less_iterEEvT_S9_T0_@Base 1.0.2 - _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflNS0_5__ops15_Iter_less_iterEEvT_S9_T0_T1_@Base 1.0.2 + _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfiNS0_5__ops15_Iter_less_iterEEvT_S9_T0_T1_@Base 1.0.2+dfsg1-7 +#MISSING: 1.0.2+dfsg1-7# _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflNS0_5__ops15_Iter_less_iterEEvT_S9_T0_T1_@Base 1.0.2 _ZTIN6WFMath10ParseErrorE@Base 0.3.11 _ZTIN6WFMath15ColinearVectorsILi2EEE@Base 0.3.11 _ZTIN6WFMath15ColinearVectorsILi3EEE@Base 0.3.11 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:7: binary-arch] Error 25
Bug#962176: numba: fails autopktest with numpy 1.18
Source: numba Version: 0.48.0-5 Severity: serious Tags: upstream fixed-upstream The autopkgtests of numba currently fail with numpy 1.18. See https://ci.debian.net/data/autopkgtest/testing/amd64/n/numba/5760086/log.gz Note that these tests already fail during the package build, but there test failures are ignored. This issue appears to be fixed upstream: https://github.com/numba/numba/pull/5758 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: wsjtx: hard-codes boost 1.67
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 960427 960424 955579 948127 962086 960381 960500 960385 959480 960412 959417 948281 960383 960331 958156 960414 959439 959479 954351 960422 960418 959437 948122 960421 960416 962070 953871 955581 949837 960378 960413 954711 954648 954649 953873 959463 948407 959573 960426 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962173 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962173: wsjtx: hard-codes boost 1.67
Source: wsjtx Version: 2.2.0+repack-1 Severity: serious User: team+bo...@tracker.debian.org Usertags: boost1.71 Control: block 961995 by -1 wsjtx hard-codes he boost version Build-Depends. Since the transition to boost 1.71 is currently ongoing, please switch to the the unversioned packages (libboost-dev) or at least replace it with liboost1.71-dev. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#962131: sqlite3 breaks python3.8 autopkgtest: CheckFuncDeterministic (sqlite3.test.userfunctions.FunctionTests)
# Fix bug meta data to avoid issues reassign 962131 src:python3.8 3.8.3-1 forwarded 962131 https://bugs.python.org/issue40784 user debian...@lists.debian.org usertags 962131 - breaks affects 962131 src:sqlite3 thanks signature.asc Description: OpenPGP digital signature
Bug#962172: baloo-kf5: autopkgtest regression: dh_acc: error: abi-compliance-checker
Source: baloo-kf5 Version: 5.70.0-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 baloo-kf5 the autopkgtest of baloo-kf5 fails in testing when that autopkgtest is run with the binary packages of baloo-kf5 from unstable. It passes when run with only packages from testing. In tabular form: passfail baloo-kf5 from testing5.70.0-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. 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 [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from baloo-kf5/5.70.0-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=baloo-kf5 https://ci.debian.net/data/autopkgtest/testing/amd64/b/baloo-kf5/5757117/log.gz autopkgtest [23:08:43]: test acc: [--- cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C Can't "next" outside a loop block at /usr/bin/abi-compliance-checker line 10171. dh_acc: error: abi-compliance-checker -q -l baloo-kf5-dev -v1 5.70.0-1 -dump debian/baloo-kf5-dev.acc -dump-path debian/baloo-kf5-dev/usr/lib/x86_64-linux-gnu/dh-acc/baloo-kf5-dev_5.70.0-1.abi.tar.gz returned exit code 5 autopkgtest [23:08:51]: test acc: ---] signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#962131: sqlite3 breaks python3.8 autopkgtest: CheckFuncDeterministic (sqlite3.test.userfunctions.FunctionTests)
Processing commands for cont...@bugs.debian.org: > # Fix bug meta data to avoid issues > reassign 962131 src:python3.8 3.8.3-1 Bug #962131 [src:sqlite3, src:python3.8] bad SQLite deterministic check in self-tests Bug reassigned from package 'src:sqlite3, src:python3.8' to 'src:python3.8'. No longer marked as found in versions python3.8/3.8.3-1. Ignoring request to alter fixed versions of bug #962131 to the same values previously set Bug #962131 [src:python3.8] bad SQLite deterministic check in self-tests Marked as found in versions python3.8/3.8.3-1. > forwarded 962131 https://bugs.python.org/issue40784 Bug #962131 [src:python3.8] bad SQLite deterministic check in self-tests Set Bug forwarded-to-address to 'https://bugs.python.org/issue40784'. > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was elb...@debian.org). > usertags 962131 - breaks Usertags were: breaks needs-update. Usertags are now: needs-update. > affects 962131 src:sqlite3 Bug #962131 [src:python3.8] bad SQLite deterministic check in self-tests Added indication that 962131 affects src:sqlite3 > thanks Stopping processing here. Please contact me if you need assistance. -- 962131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:wine-development: fails to migrate to testing for too long: FTBFS on arm*
Processing control commands:
> close -1 5.5-3
Bug #962171 [src:wine-development] src:wine-development: fails to migrate to
testing for too long: FTBFS on arm*
Marked as fixed in versions wine-development/5.5-3.
Bug #962171 [src:wine-development] src:wine-development: fails to migrate to
testing for too long: FTBFS on arm*
Marked Bug as done
> block -1 by 956028
Bug #962171 {Done: Paul Gevers } [src:wine-development]
src:wine-development: fails to migrate to testing for too long: FTBFS on arm*
962171 was not blocked by any bugs.
962171 was not blocking any bugs.
Added blocking bug(s) of 962171: 956028
--
962171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#962171: src:wine-development: fails to migrate to testing for too long: FTBFS on arm*
Source: wine-development Version: 5.4-1 Severity: serious Control: close -1 5.5-3 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 956028 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:wine-development in its current version in unstable has been trying to migrate for 60 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=wine-development signature.asc Description: OpenPGP digital signature
Bug#962031: marked as done (kitemmodels: autopkgtest regression)
Your message dated Thu, 04 Jun 2020 07:18:56 + with message-id and subject line Bug#962031: fixed in kitemmodels 5.70.0-1.1 has caused the Debian Bug report #962031, regarding kitemmodels: 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.) -- 962031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kitemmodels Version: 5.70.0-1 Severity: serious kitemmodels is unable to migrate to testing due to a regression in its autopkgtests: | The following tests FAILED: |12 - kconcatenaterows_qml (Failed) |13 - ksortfilterproxymodel_qml (Failed) | make: *** [Makefile:133: test] Error 8 | dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2 | autopkgtest [10:12:16]: test testsuite: ---] | autopkgtest [10:12:16]: test testsuite: - - - - - - - - - - results - - - - - - - - - - | testsuiteFAIL non-zero exit status 25 | autopkgtest [10:12:16]: test testsuite: - - - - - - - - - - stderr - - - - - - - - - - | Errors while running CTest | make: *** [Makefile:133: test] Error 8 | dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2 See https://ci.debian.net/data/autopkgtest/testing/amd64/k/kitemmodels/5717127/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: kitemmodels Source-Version: 5.70.0-1.1 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of kitemmodels, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kitemmodels 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, 04 Jun 2020 08:24:22 +0200 Source: kitemmodels Architecture: source Version: 5.70.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 962031 Changes: kitemmodels (5.70.0-1.1) unstable; urgency=medium . * Team upload. * Run the test suite at build time: - add the xauth, xvfb, and qml-module-qtquick-controls build dependencies - run dh_auto_test using xvfb-run, as a display is needed * Drop the 'testsuite' autopkgtest, as it does not test the installed packages. (Closes: #962031) * Remove the unused debian/meta/ stuff. Checksums-Sha1: a47b7732154b7ddd8f4af18b98fe0bf82ff212ef 2766 kitemmodels_5.70.0-1.1.dsc f157af13a88b482694362004026abacf4a5c1422 12560 kitemmodels_5.70.0-1.1.debian.tar.xz f025479d6b1e92f09b0405e5566108ed708571b4 12938 kitemmodels_5.70.0-1.1_source.buildinfo Checksums-Sha256: 9d36a9162131d1ee5b2e82ac1eb81ac4026a849347739b00237787cc34b48057 2766 kitemmodels_5.70.0-1.1.dsc c70128504112b45f87728f948aff741b705ddb2cd7913f581b000bae00e55e43 12560 kitemmodels_5.70.0-1.1.debian.tar.xz 3daeb385a6d9cbb0490366398b9ce66fe91d6c8b5aa213850bb0f22eb4a978d7 12938 kitemmodels_5.70.0-1.1_source.buildinfo Files: 96dacf5533d37c9d31713a02a199e0da 2766 libs optional kitemmodels_5.70.0-1.1.dsc 7787ba02c9c69fa339878f14403ac503 12560 libs optional kitemmodels_5.70.0-1.1.debian.tar.xz d4b9ede0f3310bf87c986c3ab7ccde91 12938 libs optional kitemmodels_5.70.0-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl7YnDgACgkQLRkciEOx P01I/A/9GRTBmZLcEiIstpUClk/MX3ES0jG0v7/o5se8j/ppggoHlLE41VEngzA3 7MMm9qhRDnIOWlmhvBlleCopogHS3YZSBaLe1InaShP7i5+xbEKXMCzU0huGUMbz c+5NdVspk6FP/Udqtq5df4okr1uydHdTa66rgCZWAyTE0xg+UAV3EFYACTU+dWmv SwLA0gxPkqmYv5P9WiqEeBZie4sfMgUIa9lu0ntEUdhO1MzfLEphSg2pnhgkOUOW ty5i+LlxEL5t74e+BLPMCap35FBLFo62krtcR/DzC8d9fobsAaE4r9ZjMCbhGSVv gxr0sYmLUIomid8q2YWU39m0cvnltJ3Tkb+akfGVqqNSF/32fnWOV5n2ceQ38Y0Q NcEx/2Edw5qICsHqL5/6iKozsvykp0RWGm5eM2cpXJNmqideWkiY/XwUUSb5ZGSm 0rRAfg+cc6cEOuutvUHvaed+Fdsegfwi/ka/If8EV6HGpK76E8mgIAGBIwvlutgF NEwqRmHrneG9JGWDY1jNXQD7a6lL8yQTeYBFB7E1c+E7whVUSGSYYaopMuJn2X+a qfEa8hCDwdC+97VfoLjHtCubL9QXF3uDFKUENoS/rHnWzaf2TPyHatseIz1Njg1H
Processed: block 962167 with 962168
Processing commands for cont...@bugs.debian.org: > block 962167 with 962168 Bug #962167 [ftp.debian.org] RM: yui3 -- ROM; unmaintained 962167 was not blocked by any bugs. 962167 was not blocking any bugs. Added blocking bug(s) of 962167: 962168 > thanks Stopping processing here. Please contact me if you need assistance. -- 962167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962168: loggerhead: Depends on yui3 which is going to be removed
Source: loggerhead Severity: serious Hi, as explained one year ago ([1] without any response), yui3 is going to be removed (#962167). Please remove dependency to this library (libjs-yui3-min). As yui3 never entered in testing due to DFSG problems, I chose to set severity to serious here. Cheers, Xavier [1]: https://alioth-lists.debian.net/pipermail/pkg-bazaar-maint/2019-August/008343.html [1]: https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2019-August/034865.html
