Bug#960131: marked as done (swi-prolog: flaky autopkgtest: test set "file" ... aborted)
Your message dated Fri, 12 Jun 2020 10:35:37 +0500 with message-id <87bllo7snq.fsf@localhost> and subject line has caused the Debian Bug report #960131, regarding swi-prolog: flaky autopkgtest: test set "file" ... aborted 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.) -- 960131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: swi-prolog Version: 8.1.29+dfsg-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), You package has an autopkgtest, great. However, it seems to regularly fail [1] on both amd64 and arm64. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Please either fix the test to be more robust, or use the "flaky" restriction for the offending test until a solution has been found. I copied the output at the bottom of this report. All the failing tests that I inspected look like it. I'll have the migration software ignore the results of your autopkgtest until this bug is fixed. Paul [1] https://ci.debian.net/user/britney/jobs?package=swi-prolog https://ci.debian.net/data/autopkgtest/testing/amd64/s/swi-prolog/5373683/log.gz Running test set "file" (2329).(2332).(2335).(2338).(2341).(2343).(2346).(2348).(2350).(2353).(2357)[Thread 1 (main) at Fri May 8 15:26:09 2020] /build/swi-prolog-Chg12z/swi-prolog-8.1.29+dfsg/src/os/pl-os.c:1093: deleteCanonicalDir: Assertion failed: 0 C-stack trace labeled "assert_fail": [0] PL_strtod() at ??:? [0x7f51fc9d36f1] [1] __assert_fail() at ??:? [0x7f51fc991e16] [2] PL_get_file_nameW() at ??:? [0x7f51fc9bd6a0] [3] PL_get_file_nameW() at ??:? [0x7f51fc9bdba9] [4] PL_get_file_nameW() at ??:? [0x7f51fc9bde80] [5] FreeMemory() at ??:? [0x7f51fc9bee4b] [6] PopTty() at ??:? [0x7f51fc9c0307] [7] PL_get_file_name() at ??:? [0x7f51fc9bb48f] [8] PL_next_solution() at ??:? [0x7f51fc907836] [9] pl_skip_list3_va() at ??:? [0x7f51fc9465cf] [10] pl_skip_list3_va() at ??:? [0x7f51fc946e3b] [11] PL_initialise() at ??:? [0x7f51fc989a9c] [12] /usr/bin/swipl(+0x10a7) [0x55ca1e9350a7] [13] __libc_start_main() at ??:? [0x7f51fc71be0b] [14] /usr/bin/swipl(+0x10fa) [0x55ca1e9350fa] Aborted signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi, buggy verison of swi-prolog was substituted with new 8.2.0+dfsg-2 both in unstable and testing, so I'm closing the bug report. Cheers! Lev--- End Message ---
Bug#962399: marked as done (vmdb2 FTBFS: help2man: can't get `--help' info from vmdb2)
Your message dated Fri, 12 Jun 2020 05:18:41 + with message-id and subject line Bug#962399: fixed in vmdb2 0.16-2 has caused the Debian Bug report #962399, regarding vmdb2 FTBFS: help2man: can't get `--help' info from vmdb2 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.) -- 962399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vmdb2 Version: 0.16-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=vmdb2=all=0.16-1=1591514624=0 ... debian/rules override_dh_installman make[1]: Entering directory '/<>' [ ! -e vmdb2.1 ] help2man -N vmdb2 -i debian/vmdb2.1.in > debian/vmdb2.1 help2man: can't get `--help' info from vmdb2 Try `--no-discard-stderr' if option outputs to stderr make[1]: *** [debian/rules:18: override_dh_installman] Error 127 --- End Message --- --- Begin Message --- Source: vmdb2 Source-Version: 0.16-2 Done: Gunnar Wolf We believe that the bug you reported is fixed in the latest version of vmdb2, 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. Gunnar Wolf (supplier of updated vmdb2 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, 12 Jun 2020 00:00:36 -0500 Source: vmdb2 Architecture: source Version: 0.16-2 Distribution: unstable Urgency: medium Maintainer: Gunnar Wolf Changed-By: Gunnar Wolf Closes: 962399 Changes: vmdb2 (0.16-2) unstable; urgency=medium . * Run vmdb2 for help2man from the local build path, don't assume it to be in the path (Closes: #962399) Checksums-Sha1: 70b6c04aa9cab2c2cb5302b3a4ea81926422d6b9 1404 vmdb2_0.16-2.dsc 5cacbbd961565d08b870834a177b6942a7d12225 3320 vmdb2_0.16-2.debian.tar.xz b7fb087caa58d36e41becbffd249ab4f845a027b 10636 vmdb2_0.16-2_source.buildinfo Checksums-Sha256: dac1a345aa24446aca435bf97e218556d51b5526cac5367b7e248db87dcb4891 1404 vmdb2_0.16-2.dsc 4e046328d7ba1ee17b04eaa89ebe36f9334cdf8bade3776e51598dfabf295894 3320 vmdb2_0.16-2.debian.tar.xz fe64bbb539aa11bf7ea3fd2e09b97882b7b75dfa4d4308128cdd7c72ba2c7b58 10636 vmdb2_0.16-2_source.buildinfo Files: 02c778b726bb5f407e1dd7521d9610e8 1404 admin optional vmdb2_0.16-2.dsc 526098c89734bc8101c4e47fece8aa3d 3320 admin optional vmdb2_0.16-2.debian.tar.xz 533687722d860420c67249310f7c48d4 10636 admin optional vmdb2_0.16-2_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQRgswk9lhCOXLlxQu/i9jtDU/RZiQUCXuMMWQAKCRDi9jtDU/RZ ifo6AQDVrAIJlC2HPfz0hjzDuiEHeUgMimJOVlH4t9mSQ4tDygD/cCaN02sUSUjA 8sS3GgbYGFuP/PB1IKI3WoYWuC0MnQY= =5/Nr -END PGP SIGNATURE End Message ---
Bug#962685: wordpress 5.4.2 security release
Hi Craig, On Fri, Jun 12, 2020 at 09:40:34AM +1000, Craig Small wrote: > Source: wordpress > Version: 5.4.1+dfsg1-1 > Severity: grave > Tags: security upstream > Justification: user security hole > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > WordPress 5.4.2 is out and fixes the following vulnerabilities: [...] Thanks for filling the bugreport about those, added tracking in the security-tracker correspondigly. Are you requesting CVEs for those? Regards, Salvatore
Processed: severity of 962681 is important
Processing commands for cont...@bugs.debian.org: > severity 962681 important Bug #962681 [linux] battery drain during system shutdown Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 962681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952499: marked as done (python-csa: needs a source-only upload)
Your message dated Fri, 12 Jun 2020 04:03:34 + with message-id and subject line Bug#952499: fixed in python-csa 0.1.12-1.1 has caused the Debian Bug report #952499, regarding python-csa: needs a source-only upload 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.) -- 952499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-csa Version: 0.1.10-1 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing, please make a source-only upload so your package can migrate. --- End Message --- --- Begin Message --- Source: python-csa Source-Version: 0.1.12-1.1 Done: Carlos Henrique Lima Melara We believe that the bug you reported is fixed in the latest version of python-csa, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carlos Henrique Lima Melara (supplier of updated python-csa 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, 08 Jun 2020 23:31:08 -0300 Source: python-csa Architecture: source Version: 0.1.12-1.1 Distribution: unstable Urgency: medium Maintainer: Mikael Djurfeldt Changed-By: Carlos Henrique Lima Melara Closes: 952499 Changes: python-csa (0.1.12-1.1) unstable; urgency=medium . * Non-maintainer upload. * Source-only upload. (Closes: #952499) Checksums-Sha1: aee73ec1ce771e3e1b2e7576ba316b37f98c4beb 1827 python-csa_0.1.12-1.1.dsc 71f136d264cf465a11a92e6835df15828e84cd72 2024 python-csa_0.1.12-1.1.debian.tar.xz 303416f3f4d164f092d5ae72c37ed82d2d920469 6420 python-csa_0.1.12-1.1_source.buildinfo Checksums-Sha256: 4b2620e7dc3ac9b0bba170617076fcb201f507c0ee0f748ee9495e33f1804e03 1827 python-csa_0.1.12-1.1.dsc e6a272e45d4e42bfbf4986380f0d74363a5ec21c36c7c69ac19d93ddf4e02b35 2024 python-csa_0.1.12-1.1.debian.tar.xz 0d3ccfe74325291834892851c2be3c44bb0351e5fa57f849d527dfc67c64439b 6420 python-csa_0.1.12-1.1_source.buildinfo Files: c265cfae547d52dcc25c88c763604da2 1827 python optional python-csa_0.1.12-1.1.dsc 894a412135274fa696cd7098d57c073a 2024 python optional python-csa_0.1.12-1.1.debian.tar.xz c7d2a780c9269cb4e911c54ed8d2f89c 6420 python optional python-csa_0.1.12-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl7fAeEACgkQ3mO5xwTr 6e8Vlw/9FL8pq8If4pOEvCtZjDTPSvapesaptZ4t2aPSajGBa8RWf1hQqS9C8HT4 zzXj0TagoLbfpYd4fO92NbOhrhPfvKnVo03p2x8JxUAWCONmCmWoC0hdESacQPnQ 4ZpsTtwTAWQuCA+S6LQuE/8zYmD3RWjStd5c5ScaFRFyXpXx2YQtI+ajQqc3+Inx J91b4fse8ISYQXn3iE7z3PDLtumedAR8qipBznPINU9gRwxe0JPxaMXNidWCayVr iDafakJlNQLk29doMfZlTDXucboMBKtfDazOUQB8Fc5POeFjm6eRcdMLnMAjkafL cB14SDzKOIUcgzmxJmhNQ74tCZi+TggkCJy5VmOqsTVLBnLu92YWLPELFcgCSraV GlcQZGFQKRoknhkBCTWz8NNCeCEubkCecH7oYFXlJZZN1l8+jpp4rWy0hh7RT9S9 jq2QDrbLS/4eyU62GgBYmbY6rXSLyzzxcS6TRUULR/xw9xOe9g/u1pltJ+I0z2wb ITnaABJVhpufsjd4z+XWYLALZrQbkcQQOJI8DkkcGu8ad8RA2zenRpEbs8P8fCOw dcBpmYqDBOJF7EqGL6G6IDv5Wt2oaToUQ0peey5Mten9zqU8nDNrusDpGonlDWw3 G+lPq11uh7MgKbteF9TioN4ioIYj0M9lq6HsNdy5jcxyW8dpPWw= =ZEQs -END PGP SIGNATURE End Message ---
Bug#962673: marked as done (cunit: autopkgtest failure: stdio.h: No such file or directory)
Your message dated Fri, 12 Jun 2020 02:48:31 + with message-id and subject line Bug#962673: fixed in cunit 2.1-3-dfsg-2.3 has caused the Debian Bug report #962673, regarding cunit: autopkgtest failure: stdio.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cunit Version: 2.1-3-dfsg-2.2 Severity: serious Autopkgtest fails since last NMU with the following messages: autopkgtest [17:33:49]: test test.sh: [--- debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found autopkgtest [17:33:49]: test test.sh: ---] autopkgtest [17:33:49]: test test.sh: - - - - - - - - - - results - - - - - - - - - - test.sh FAIL non-zero exit status 127 autopkgtest [17:33:50]: test test.sh: - - - - - - - - - - stderr - - - - - - - - - - debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found autopkgtest [17:33:50]: summary test.sh FAIL non-zero exit status 127 The release team has announced [1] that failing autopkgtest are now considered RC in testing. The full log from autopkgtest is availble here[2]. [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html [2] https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cunit/5861880/log.gz Regards, Eriberto --- End Message --- --- Begin Message --- Source: cunit Source-Version: 2.1-3-dfsg-2.3 Done: Regis Fernandes Gontijo We believe that the bug you reported is fixed in the latest version of cunit, 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. Regis Fernandes Gontijo (supplier of updated cunit 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, 11 Jun 2020 22:15:43 + Source: cunit Architecture: source Version: 2.1-3-dfsg-2.3 Distribution: unstable Urgency: medium Maintainer: Azat Khuzhin Changed-By: Regis Fernandes Gontijo Closes: 962673 Changes: cunit (2.1-3-dfsg-2.3) unstable; urgency=medium . * Non-maintainer upload. * Fixed broken dependendy on libc6-dev for CI test. (Closes: #962673) Checksums-Sha1: dcfaa7937b9d1d52bb55ab00139422deb3c85bf3 2214 cunit_2.1-3-dfsg-2.3.dsc 82d6a5505ff318ba1cd11e75b6e867a2bfef07d0 7412 cunit_2.1-3-dfsg-2.3.debian.tar.xz b8505c72f1a13a10b42834128825239c72ff990c 5445 cunit_2.1-3-dfsg-2.3_source.buildinfo Checksums-Sha256: f01e157274ae979213831479f97d3454c179988495006940100634f63b2efe02 2214 cunit_2.1-3-dfsg-2.3.dsc 2a9c0e39796b71364a98dbb4a8e3dbf12d7050ce22c880227fae94f9e551c6d4 7412 cunit_2.1-3-dfsg-2.3.debian.tar.xz 09af407a9f6f9096c0efa3b6bd39cb72df32b4da1736f982fce8186867484c7e 5445 cunit_2.1-3-dfsg-2.3_source.buildinfo Files: 36acdb34a38f564eef86c6686440fd5b 2214 libs optional cunit_2.1-3-dfsg-2.3.dsc 51a471c5c9729461f0aa15d49084274d 7412 libs optional cunit_2.1-3-dfsg-2.3.debian.tar.xz 0edd23d80739b50f508e50d4628d43c7 5445 libs optional
Bug#925672: marked as done (efivar: ftbfs with GCC-9)
Your message dated Fri, 12 Jun 2020 02:33:28 + with message-id and subject line Bug#925672: fixed in efivar 37-2.1 has caused the Debian Bug report #925672, regarding efivar: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 925672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:efivar Version: 37-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/efivar_37-2_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] Check disk space Sufficient free space for build User Environment APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/sbuild-nonexistent LANG=en_US.UTF-8 LC_ALL=POSIX LOGNAME=user42 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-5140e265-439a-4f86-8475-7ce1ea65e9fa SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - dpkg-buildpackage: info: source package efivar dpkg-buildpackage: info: source version 37-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Steve McIntyre <93...@debian.org> dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean make -j1 clean make[1]: Entering directory '/<>' /bin/sh: 1: [[: not found make[2]: Entering directory '/<>/src' cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -flto -I/<>/src/include/ -specs=/<>/gcc.specs -L. -Wl,-z,relro -Wl,-z,muldefs -Wdate-time -D_FORTIFY_SOURCE=2 -DEFIVAR_BUILD_ENVIRONMENT -o makeguids makeguids.c guid.c -ldl In file included from efivar.h:30, from makeguids.c:30: dp.h: In function 'format_vendor_helper': dp.h:118:37: error: taking address of packed member of 'struct ' may result in an unaligned pointer value [-Werror=address-of-packed-member] 118 | format_guid(buf, size, off, label, >hw_vendor.vendor_guid); | ^~ dp.h:74:25: note: in definition of macro 'format_guid' 74 | _rc = efi_guid_to_str(guid, &_guidstr); \ | ^~~~ cc1: all warnings being treated as errors In file included from efivar.h:30, from guid.c:27: dp.h: In function 'format_vendor_helper': dp.h:118:37: error: taking address of packed member of 'struct ' may result in an unaligned pointer value [-Werror=address-of-packed-member] 118 | format_guid(buf, size, off, label, >hw_vendor.vendor_guid); | ^~ dp.h:74:25: note: in definition of macro 'format_guid' 74 | _rc = efi_guid_to_str(guid, &_guidstr); \ | ^~~~ cc1: all warnings being treated as errors make[2]: *** [/<>/Make.rules:13: makeguids] Error 1 make[2]: Leaving directory '/<>/src' make[1]: *** [Makefile:49: clean] Error 2 make[1]: Leaving directory '/<>' dh_auto_clean: make -j1 clean returned exit code
Bug#962606: marked as done (csound: Build-depends on removed package ttf-dejavu)
Your message dated Fri, 12 Jun 2020 00:33:34 + with message-id and subject line Bug#962606: fixed in csound 1:6.14.0~dfsg-6 has caused the Debian Bug report #962606, regarding csound: Build-depends on removed package ttf-dejavu 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.) -- 962606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: csound Severity: grave Version: 1:6.14.0~dfsg-5 X-Debbugs-CC: fsate...@debian.org forrest.cah...@gmail.com Dear Debian csound maintainers, Your package csound build-depends on package ttf-dejavu, which is a transitional package that has been removed since the upload of fonts- dejavu/2.37-2. Please adjust the build-dependency information and use package name fonts-dejavu. Please note that ttf-dejavu and fonts-dejavu provides the fonts under *different* paths. Please review your package and make sure that the hardcoded paths (if any) have been updated accordingly. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: csound Source-Version: 1:6.14.0~dfsg-6 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of csound, 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. Boyuan Yang (supplier of updated csound 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, 11 Jun 2020 19:55:19 -0400 Source: csound Architecture: source Version: 1:6.14.0~dfsg-6 Distribution: unstable Urgency: high Maintainer: Debian Multimedia Maintainers Changed-By: Boyuan Yang Closes: 962606 Changes: csound (1:6.14.0~dfsg-6) unstable; urgency=high . * Team upload. * debian/control: Replace removed dependency package ttf-dejavu with real patch fonts-dejavu. (Closes: #962606) Checksums-Sha1: 68abaf2e022f047b31564c2d032efd9543e82d85 3172 csound_6.14.0~dfsg-6.dsc 9009e3d0b198c2e216df4a6ff781d2839968d82c 33440 csound_6.14.0~dfsg-6.debian.tar.xz cf9d127af0841303b11c9c4e20b104af49f12f48 21230 csound_6.14.0~dfsg-6_amd64.buildinfo Checksums-Sha256: 289102580f00c52b48bc3362487c2eb9596cd72707326904f37f10ab8b7b0419 3172 csound_6.14.0~dfsg-6.dsc 0733b3be9a416cbd7b1f6643d38b632a7f2b5bc4b2922f7f42590140a2215465 33440 csound_6.14.0~dfsg-6.debian.tar.xz 5e0dcc0ba55ddd80f7d2bd259d3e755319fe77dced04644768140685e865085a 21230 csound_6.14.0~dfsg-6_amd64.buildinfo Files: e34738d2a771859561855e38242bd914 3172 sound optional csound_6.14.0~dfsg-6.dsc 7427fdcc06af79a52c185bb396bb580e 33440 sound optional csound_6.14.0~dfsg-6.debian.tar.xz d4a8d12a71c9d4574c5778c5b07ac3b9 21230 sound optional csound_6.14.0~dfsg-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl7ixsYACgkQwpPntGGC Ws4zWw/+L+rr4WRkBfjaKy+s4ywaDTJMPmQKlXWm4BqVb2hwIog4pEv5YDU71SNY rEC2GQZixS8bUoYjQ3PXli1fZ5sY+qPZjUHra/DZDfRmBd97GzuMc4uE2pCjlLDw zk3Pz81+dbxNIu9gVfs7yxhv4N07Lq/qvOFI7ci9VCyfauPo7ej0B2fSNU5FqrTf 0DszVFvrVHGHDXd6YBWlkvD87bzYb+ApN1ZiiCbDliOD/WsjDfyJ4u/RPYjE1lmc Z2JFMmGawBNBdi3267Evqw9W//gzcSUeOkK2Xl5zuiSj4YDaEzYLKPoAVY6z4vMB 1sLpoqRCIx2LWQLQTOYq4nEW1MfvHMvt2rR/xbPnjUoeQFUNjp3VFP7zF5t5AucL XUqWCeD/c2RCxbBrNxSiLS1ONavsCcCt8dQlYXPp5BIEreaKn9itDd/1KGPbnbx+ YY0rmtBJj+DrAlDVy/Fxoam72q9w6XH9tfgckIQzZfb8y5ePH9dCSi/ePGJ8i+Gk IZu+n6kn8/VusupcJajIUVNfyE2L1SdWMSSS5etMAZkGgnndErbzD8Igz1RQt3bc y1XDVbN9pIHujfPVxevQWy0kl9af+j7VnLJPS+vIPDpRebtdnicETI5LTAUOPIu7 FbBNNWdhSRhfnPjXvpRYcJ4H10oKyUXLD9OoXGrQTJfy2ko7kpQ= =46mF -END PGP SIGNATURE End Message ---
Bug#958450: 83 available upstream
Upstream is asking me to use version 83 when reporting bugs.
Bug#962685: wordpress 5.4.2 security release
Source: wordpress Version: 5.4.1+dfsg1-1 Severity: grave Tags: security upstream Justification: user security hole -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 WordPress 5.4.2 is out and fixes the following vulnerabilities: Props to Sam Thomas (jazzy2fives) for finding an XSS issue where authenticated users with low privileges are able to add JavaScript to posts in the block editor. https://core.trac.wordpress.org/changeset/47948 All releases Props to Luigi – (gubello.me) for discovering an XSS issue where authenticated users with upload permissions are able to add JavaScript to media files. https://core.trac.wordpress.org/changeset/47947 (I think) All releases Props to Ben Bidner of the WordPress Security Team for finding an open redirect issue in wp_validate_redirect(). https://core.trac.wordpress.org/changeset/47949 All releases Props to Nrimo Ing Pandum for finding an authenticated XSS issue via theme uploads. https://core.trac.wordpress.org/changeset/47950 All releases Props to Simon Scannell of RIPS Technologies for finding an issue where set-screen-option can be misused by plugins leading to privilege escalation. https://core.trac.wordpress.org/changeset/47951 All releases Props to Carolina Nymark for discovering an issue where comments from password-protected posts and pages could be displayed under certain conditions. https://core.trac.wordpress.org/changeset/47984 All releases There is also a fix for unmoderated comments visible to indexers which will be backported. WordPress say its not a security issue, but seems like you are getting the site to do something that it shouldn't. https://make.wordpress.org/core/2020/06/09/wordpress-5-4-2-prevent-unmoderated-comments-from-search-engine-indexation/ https://core.trac.wordpress.org/ticket/49956 https://core.trac.wordpress.org/changeset/47887 https://core.trac.wordpress.org/changeset/47889 Present: 5.4 only (5.1 onwards, see the ticket) - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAl7iwOsSHGNzbWFsbEBk ZWJpYW4ub3JnAAoJEAIhZsD/PITjYIAP/R+4+bSwUXz0IPSijvsH4PkIICe3k1wj dBSgFWWjFcVyYZwbpQ5SqgyspGG5aFhQPNWiSAvv0BILWY///jbPmsSoqz0s58xC QcjBkUiif1GDZq60IaA8igy2eotD90FQxr8Y16iDFSbkC0U3x4sV1UW3WlDEyxnW ILRusFo8m0L9J+rTQUxu0SGHK4WM2nvCGNp1U3l5/JreKZxlLIeoy+y44GsCPktn 8wDIqZ91bUpfhUcyL7BZu7g94cUnC8RhZxX//TiVYlH54pXneascPuedZAGV/qi6 0TMTuSvdPd9/pKtKhCo2jUb70CRWiP4r3QDgRM7oqcx8jLaLvBcvWmaAQjpc6eZB jgRX6HAEkm2CVFor4VtwRH/726RLLm34IokYnXU74Wp+LVjtXIYMLoP/fkbEvJW4 ClrMMEUe/+bkWLmWu6iGdbNM325eFsTvkDOngCNV/g/lsEp5gzHZwCwzL+0J21ds /KglCuE+BRn4XSCCxOEU+HS7EM8A+NWrO95elryeVE2SRQb/11F8s6TkIMMMqFPD B4m8+J5Ooj7LzS3dErVuXlOOVX0YXFVOL6AThfitW9SHOn37NmRsvOuSJCySKdI6 60A7WJvuH460JcpASDSR4XoJpBy+NnAkA4uTJ9ihlLKbZBkhy+vS/E/6M73yL9Aw QCZSPwT6j/lX =E8qn -END PGP SIGNATURE-
Bug#960421: marked as done (libpwiz: FTBFS with boost 1.71)
Your message dated Thu, 11 Jun 2020 23:19:25 + with message-id and subject line Bug#960421: fixed in libpwiz 3.0.18342-3 has caused the Debian Bug report #960421, regarding libpwiz: 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.) -- 960421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpwiz Version: 3.0.18432-2 Severity: important User: team+bo...@tracker.debian.org Usertags: boost1.71 libpwiz fails to build with boost 1.71. See https://people.debian.org/~gio/boost_migration/libpwiz.log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: libpwiz Source-Version: 3.0.18342-3 Done: Filippo Rusconi We believe that the bug you reported is fixed in the latest version of libpwiz, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Filippo Rusconi (supplier of updated libpwiz 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, 11 Jun 2020 23:29:40 +0200 Source: libpwiz Architecture: source Version: 3.0.18342-3 Distribution: unstable Urgency: low Maintainer: The Debichem Group Changed-By: Filippo Rusconi Closes: 960421 Changes: libpwiz (3.0.18342-3) unstable; urgency=low . * Add patch by Dimitri John Ledkov forwarded by Adrian Bunk (thanks to both of them) Closes: #960421. . The fix is about the new gcc/boost fail to cast tribool to bool, force it. . * Standards-Version: 4.5.0. Checksums-Sha1: 26d9cece3f7a83d9757353bf0f828f3c7dbdb71c 2597 libpwiz_3.0.18342-3.dsc 50cf826fa25642bfe354dbffe9544050c8671c95 20420 libpwiz_3.0.18342-3.debian.tar.xz 6f0374b76c11aa486e2006866e9b1534cfb1f87b 10318 libpwiz_3.0.18342-3_amd64.buildinfo Checksums-Sha256: 4b4cb52bf1cc13ee96a62c99082ab4fdd714de777f11bfff04951386b4c49c36 2597 libpwiz_3.0.18342-3.dsc dc3d7fb38bbe81b043794f470f67439ee4db5499728f8005e46f0b2e610ff8e4 20420 libpwiz_3.0.18342-3.debian.tar.xz fae40524b440abf068b3873efa45ff5c007075a4c05694b9e7e650911f716a7c 10318 libpwiz_3.0.18342-3_amd64.buildinfo Files: 98edecf47b521ab048f693eb37dff0ec 2597 libs optional libpwiz_3.0.18342-3.dsc c4af0541e19ea2b3a6f7ff09b7233e30 20420 libs optional libpwiz_3.0.18342-3.debian.tar.xz f7bd69920632c7ae784a4a5c37386757 10318 libs optional libpwiz_3.0.18342-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEsFMwThfW1Bndm0ZRQatITXaUz0IFAl7it+oACgkQQatITXaU z0Kuvw//a4nZTmHBKY8ATsXpnovSCh6eI1rFfMSKOiypGWNd+t4ZpTbfbqrQFwlw sS75i31Ujxft5Oc5sLCgHSCtydsIceX6FW2Jns5nh6kcrojiKCBml3TlLE6NgZ7c /ocR+gV/7D8cWpKbsCEvWPTICu8qvsUoBGaYzippEkdQJK6CX+Rps/HLKiTARbCG fOvQbRPj+Tg2mH9txzf65GhzBkhR+Stvyjpz/eH7Ws7nt/bdh5P286liEcvUnWr1 etZefL0ZFMyMg4DcZx+uzAvSvKbRpOXl+fVkWIoExL92gdIdNfy+uCDKwrZvvS6p HprBTNNSux2L6B0RigoiT9M8ql18ZIfXEyrOf/WjQZU0UE6yuSviQPOtwmxBpxI7 YmpkWyt8MHN2WPOHcLW0plHp6VqxaxVx84vS/tsh6cJuNBOWASuedQuI1NQFFHi5 Tg2TjKAnUwF0ie+S9ajI37J1EZxbCY73lb2sz1nfRhB7qVdnHoz5S4fjzUhTxD9d 9ThDQVHJ6Ww00bt31YOnowAlHkrXYJBU79HDchz+o4YewYw3c8B7LeSl+U6cIzvA E957XQzc/y3NCWvQE/ccgr2n2o3DYGtL4Dhp/4jC03bljeinH+INEF+N+5MRuGSX WREAGTMES/ScliTKHW9c+39xT0/LYQ4Er6lmmJWeWCMQgVvnPXU= =HyB3 -END PGP SIGNATURE End Message ---
Bug#935614: libinfinity: FTBFS on all architectures
tag 935614 + patch
thanks
Hello,
Thank you for looking into this issue.
The problem is due to reliance on particular ordering when iterating
hash table in tests. The bug is triggered by a minor tweak to hash table
algorithm in glib.
I proposed two patches on the upstream issue to fix the problem. They
are also attached here. They are alternate approaches and any one of
them will fix the problem. If the upstream takes time to fix, please
consider applying one of the patches to Debian as infinoted is currently
not available in Debian/FreedomBox testing.
Thanks,
--
Sunil
From ebe92d9d97dc21b82225c6a7977adf87dd00f799 Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa
Date: Thu, 11 Jun 2020 15:00:34 -0700
Subject: [PATCH] Iterate user table in a sorted way, fix tests with latest
glib
This is primarily to help test cases which assume that the adopted algorithm
prioritizes the users in the exact reverse order they appear in the test
cases (and get inserted into the session in reverse order). With older glib
version, the five users being inserted happened to return the order expected by
the tests. With latest glib, due to a minor tweak in hashing strategy, the
insertion leads to unsorted list leading to failed tests.
In addition, GHashTable makes no guarantees about the stability of items when
iterating multiple times. Since the algorithm is sensitive to order of users, it
is best to return users in an order that is consistent over multiple calls and
stable over insert/remove operations.
This patch maintains a sorted list of user ids and uses it for iteration.
Closes: #22.
Signed-off-by: Sunil Mohan Adapa
---
libinfinity/common/inf-user-table.c | 51 -
1 file changed, 28 insertions(+), 23 deletions(-)
diff --git a/libinfinity/common/inf-user-table.c b/libinfinity/common/inf-user-table.c
index 11b06b4..cb44ef5 100644
--- a/libinfinity/common/inf-user-table.c
+++ b/libinfinity/common/inf-user-table.c
@@ -36,15 +36,11 @@
* users within the session.
*/
-typedef struct _InfUserTableForeachUserData InfUserTableForeachUserData;
-struct _InfUserTableForeachUserData {
- InfUserTableForeachUserFunc func;
- gpointer user_data;
-};
-
typedef struct _InfUserTablePrivate InfUserTablePrivate;
struct _InfUserTablePrivate {
GHashTable* table;
+ /* To be able to iterate users in sorted order */
+ GSList* user_ids;
/* TODO: It would be smarter to map the hash table to a helper struct
* which stores the user availability, locality and the InfUser object */
GSList* availables;
@@ -179,15 +175,11 @@ inf_user_table_lookup_user_by_name_func(gpointer key,
return FALSE;
}
-static void
-inf_user_table_foreach_user_func(gpointer key,
- gpointer value,
- gpointer user_data)
+static gint
+inf_user_ids_list_sort_compare_func(gconstpointer a,
+gconstpointer b)
{
- InfUserTableForeachUserData* data;
- data = (InfUserTableForeachUserData*)user_data;
-
- data->func(INF_USER(value), data->user_data);
+ return GPOINTER_TO_UINT(a) - GPOINTER_TO_UINT(b);
}
static void
@@ -197,6 +189,7 @@ inf_user_table_init(InfUserTable* user_table)
priv = INF_USER_TABLE_PRIVATE(user_table);
priv->table = g_hash_table_new_full(NULL, NULL, NULL, NULL);
+ priv->user_ids = NULL;
priv->availables = NULL;
priv->locals = NULL;
}
@@ -216,6 +209,9 @@ inf_user_table_dispose(GObject* object)
g_slist_free(priv->availables);
priv->availables = NULL;
+ g_slist_free(priv->user_ids);
+ priv->user_ids = NULL;
+
g_hash_table_foreach(
priv->table,
inf_user_table_dispose_foreach_func,
@@ -256,6 +252,12 @@ inf_user_table_add_user_handler(InfUserTable* user_table,
g_hash_table_insert(priv->table, GUINT_TO_POINTER(id), user);
g_object_ref(user);
+ priv->user_ids = g_slist_insert_sorted(
+priv->user_ids,
+GUINT_TO_POINTER(id),
+inf_user_ids_list_sort_compare_func
+ );
+
g_signal_connect(
G_OBJECT(user),
"notify::status",
@@ -314,6 +316,8 @@ inf_user_table_remove_user_handler(InfUserTable* user_table,
);
}
+ priv->user_ids = g_slist_remove(priv->user_ids, GUINT_TO_POINTER(id));
+
inf_user_table_unref_user(user_table, user);
g_assert(g_hash_table_lookup(priv->table, GUINT_TO_POINTER(id)) == user);
g_hash_table_remove(priv->table, GUINT_TO_POINTER(id));
@@ -646,21 +650,22 @@ inf_user_table_foreach_user(InfUserTable* user_table,
gpointer user_data)
{
InfUserTablePrivate* priv;
- InfUserTableForeachUserData data;
+ InfUser* user;
+ GSList* item;
+
+ guint user_id;
g_return_if_fail(INF_IS_USER_TABLE(user_table));
g_return_if_fail(func != NULL);
priv = INF_USER_TABLE_PRIVATE(user_table);
- data.func = func;
- data.user_data = user_data;
-
- g_hash_table_foreach(
-priv->table,
-inf_user_table_foreach_user_func,
-
- );
+ for(item = priv->user_ids; item !=
Processed: Re: libinfinity: FTBFS on all architectures
Processing commands for cont...@bugs.debian.org: > tag 935614 + patch Bug #935614 [src:libinfinity] libinfinity: FTBFS on all architectures Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 935614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962100: python-memprof: Fix for autopkg tests
Package: python-memprof Version: 0.3.6-2 Followup-For: Bug #962100 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy ubuntu-patch Dear Maintainer, I've discovered a fix which allows the autopkg tests to pass. In Ubuntu, the attached patch was applied to achieve the following: * Properly import getsize so autopkg tests pass. (Closes: #962100) Thanks for considering the patch. diff -Nru python-memprof-0.3.6/debian/patches/import-pyx.patch python-memprof-0.3.6/debian/patches/import-pyx.patch --- python-memprof-0.3.6/debian/patches/import-pyx.patch1969-12-31 16:00:00.0 -0800 +++ python-memprof-0.3.6/debian/patches/import-pyx.patch2020-06-11 13:08:25.0 -0700 @@ -0,0 +1,20 @@ +Description: Properly import getsize for autopkgtests +Author: Brian Murray +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962100 +Last-Update: 2020-06-11 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +Index: python-memprof-0.3.6/memprof/memprof.py +=== +--- python-memprof-0.3.6.orig/memprof/memprof.py python-memprof-0.3.6/memprof/memprof.py +@@ -21,6 +21,9 @@ import time + import argparse + import types + ++import pyximport ++pyximport.install() ++ + from .mp_utils import * # noqa + from .getsize import getSize, isInteresting + diff -Nru python-memprof-0.3.6/debian/patches/series python-memprof-0.3.6/debian/patches/series --- python-memprof-0.3.6/debian/patches/series 2020-01-18 15:17:53.0 -0800 +++ python-memprof-0.3.6/debian/patches/series 2020-06-11 13:06:46.0 -0700 @@ -1 +1,2 @@ deb_specific__dont_require_argparse.patch +import-pyx.patch
Bug#962254: NFS(v4) broken at 4.19.118-2
Bit more experimentation on this issue. I tried a very small C program meant to create files with fewer permissions bits set. This succeeded which strengthens the theory of the umask getting ignored. I haven't seen anything hinting whether this is more a client or server issue. I can speculate perhaps somewhere between 4.9 and 4.15 the NFS client code stepped closer to proper the "proper" 4.2 protocol. If a corresponding NFS server was slow at getting merged, what we're seeing could happen. Alternatively someone was trying to get a Linux NFS v4.2 client to work better with a different NFS v4.2 server, so they fixed Linux's NFS v4.2 client. Yet they failed to test with Linux's v4.2 server. This though is speculation. All I can say is sometime between kernels 4.9 and 4.15, NFS v4.2 got broken. There are hints this is related to handling of umask. -- (\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/) \BS (| ehem+sig...@m5p.com PGP 87145445 |) / \_CS\ | _ -O #include O- _ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Bug#962533: mlpack FTBFS on mips64el: relocation truncated to fit
Adrian Bunk 于 2020年6月9日周二 下午11:18写道： > Source: mlpack > Version: 3.3.1-1 > Severity: serious > Tags: ftbfs > > It seems Boost 1.67 -> 1.71 increased something: > > > https://buildd.debian.org/status/fetch.php?pkg=mlpack=mips64el=3.3.1-1%2Bb1=1591444281=0 > > ... > /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -Wextra -ftemplate-depth=1000 > -Wno-unused-function -O3 -fopenmp -Wl,-z,relro -Wl,-z,now -rdynamic > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o -o ../../../../bin/mlpack_cf > -Wl,-rpath,/<>/obj-mips64el-linux-gnuabi64/lib: > ../../../../lib/libmlpack.so.3.3 /usr/lib/libarmadillo.so > /usr/lib/mips64el-linux-gnuabi64/libboost_program_options.so > /usr/lib/mips64el-linux-gnuabi64/libboost_unit_test_framework.so > /usr/lib/mips64el-linux-gnuabi64/libboost_serialization.so -lpthread > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function > `std::basic_ostream >& std::operator<< std::char_traits, std::allocator >(std::basic_ostream std::char_traits >&, std::__cxx11::basic_string std::char_traits, std::allocator > const&)': > /usr/include/c++/9/bits/basic_string.h:6421:(.text+0x300): relocation > truncated to fit: R_MIPS_CALL16 against `std::basic_ostream std::char_traits >& std::__ostream_insert std::char_traits >(std::basic_ostream > >&, char const*, long)@@GLIBCXX_3.4.9' > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function `void > std::__cxx11::basic_string, > std::allocator >::_M_construct(char*, char*, > std::forward_iterator_tag)': > /usr/include/c++/9/bits/basic_string.tcc:219:(.text+0x760): relocation > truncated to fit: R_MIPS_CALL16 against `std::__cxx11::basic_string std::char_traits, std::allocator >::_M_create(unsigned long&, > unsigned long)@@GLIBCXX_3.4.21' > /usr/include/c++/9/bits/basic_string.tcc:233:(.text+0x7c0): relocation > truncated to fit: R_MIPS_CALL16 against `__stack_chk_fail@@GLIBC_2.4' > /usr/include/c++/9/bits/basic_string.tcc:212:(.text+0x7d0): relocation > truncated to fit: R_MIPS_CALL16 against `std::__throw_logic_error(char > const*)@@GLIBCXX_3.4' > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function > `__gnu_cxx::new_allocator std::char_traits, std::allocator > >::allocate(unsigned long, > void const*)': > /usr/include/c++/9/ext/new_allocator.h:114:(.text+0xb34): relocation > truncated to fit: R_MIPS_CALL16 against `operator new(unsigned > long)@@GLIBCXX_3.4' > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function > `std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > >::_S_check_init_len(unsigned long, > std::allocator, > std::allocator > > const&)': > /usr/include/c++/9/bits/stl_vector.h:1767:(.text+0xbc4): relocation > truncated to fit: R_MIPS_CALL16 against `std::__throw_length_error(char > const*)@@GLIBCXX_3.4' > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function > `std::__cxx11::basic_string, > std::allocator >* > std::__uninitialized_copy::__uninit_copy std::char_traits, std::allocator > const*, > std::__cxx11::basic_string, > std::allocator >*>(std::__cxx11::basic_string std::char_traits, std::allocator > const*, > std::__cxx11::basic_string, > std::allocator > const*, std::__cxx11::basic_string std::char_traits, std::allocator >*)': > /usr/include/c++/9/bits/stl_uninitialized.h:86:(.text+0xbd0): relocation > truncated to fit: R_MIPS_CALL16 against `__cxa_begin_catch@@CXXABI_1.3' > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function `void > std::_Destroy_aux::__destroy std::char_traits, std::allocator > >*>(std::__cxx11::basic_string, > std::allocator >*, std::__cxx11::basic_string std::char_traits, std::allocator >*)': > /usr/include/c++/9/bits/stl_construct.h:107:(.text+0xbe0): relocation > truncated to fit: R_MIPS_CALL16 against `__cxa_rethrow@@CXXABI_1.3' > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function > `std::_Vector_base, > std::allocator >, std::allocator std::char_traits, std::allocator > > > >::_M_deallocate(std::__cxx11::basic_string, > std::allocator >*, unsigned long)': > /usr/include/c++/9/bits/stl_vector.h:350:(.text+0xbf8): relocation > truncated to fit: R_MIPS_CALL16 against `operator > delete(void*)@@GLIBCXX_3.4' > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function > `__gnu_cxx::new_allocator std::char_traits, std::allocator > >::~new_allocator()': > /usr/include/c++/9/ext/new_allocator.h:89:(.text+0xc04): relocation > truncated to fit: R_MIPS_CALL16 against `_Unwind_Resume@@GCC_3.0' > CMakeFiles/mlpack_cf.dir/cf_main.cpp.o: in function > `std::__cxx11::basic_string, > std::allocator >::_M_dispose()': > /usr/include/c++/9/bits/basic_string.h:231:(.text+0xc1c): additional > relocation overflows omitted from the output > just add -mxgot to cxxflags. there are 2 type of GOT in mips: one use fewer insn while has a length limitaion; another uses more insns while has a big address space support. collect2: error: ld returned 1 exit status > make[4]: *** >
Bug#961536: openmw FTBFS with openscenegraph 3.6.5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Sebastian, On 2020-06-11 at 20:28, sramac...@debian.org wrote: > Hi Bret > > The build on mipsel failed: > https://buildd.debian.org/status/fetch.php?pkg=openmw=mipsel=0.46.0-1=1591883193=0 > > It's missing -latomic. But I'm wondiering if it really makes sense to > build the package on mips*. Is anyone able to play games on mips? > > Cheers > -- > Sebastian Ramacher That's not that big of a loss, 32-bit mips can only address 2GiB of memory per process anyway. I would assume the moment you load Morrowind and its expansions that it would quickly run out of memory anyway. I added mipsel to the same list as armel and armhf. Cheers, Bret -BEGIN PGP SIGNATURE- Version: FlowCrypt 7.7.9 Gmail Encryption Comment: Seamlessly send and receive encrypted email wsFcBAEBCAAGBQJe4qd+AAoJEMI3e31YTLkwmW4P/1BPe4E4RK0Vw0pdSQf5 Fyq1iQt2Xb73Y9swL3pCKdx5/3QuV+JmTgL7o563Je2KG78SvoiQr0nXeAp6 zE7ZuNUEtuWd5GSzxSvbidGv8FXyNOseiy2JqZEUkUX278Ezir5XFwBaX2na xfobOjoIR+y61A7C/z/0saoYL53u71RRxuCrkKKGya+FLkOYyuM98Xb2EnNI I0yEVqoxCjgWD4fgKeveSHfpMBV+loeXqcWVmuNoKRrc0Ln1LkwtzMvNKOKw XA4wYwlX1aY1miVzcCBqm6QVBNDvxprtfQCi/gcC3CYSHgV/P0a/U2nYDOcw EQsr6W+AF0NpZIBBTZHVK6wDvUIrHqtDaA8vrB67qeAmb56Rea1z9OsSvfmj gZWREmHAkp0P1YdpLu6kPwTk/xnVOaPg+G+VwTQUzx1Gizir+gmp87T3wHGx I7cfiF4QHw8HJb0E/lSo9EKvYUv01hsRw0zfAgdfC2i0x1oSa+VoaASkfldE wJdq+9SDykFGQKWEXnU2lR0K6FHpnJqdu/WFYVLLSObdB97NUn57yG0DL8vj AcaeWrL2d8GoLZ990OFYACzJvXjgOgCg+0RA8GmkRMtFH6sCQ/fK4TPqaB0/ 2EECPawnAiSs6Pey/SB4hjvXntJqd3FmtYW9yDBcAU8FELIlJTFxvkgz5tl2 4CuP =seRY -END PGP SIGNATURE-
Bug#960760: marked as done (tree-puzzle FTBFS on !amd64: test failures)
Your message dated Thu, 11 Jun 2020 21:34:45 + with message-id and subject line Bug#960760: fixed in tree-puzzle 5.3~rc16+dfsg-3 has caused the Debian Bug report #960760, regarding tree-puzzle FTBFS on !amd64: test failures 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.) -- 960760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tree-puzzle Version: 5.3~rc16+dfsg-1 Severity: serious Tags: ftbfs Based on the "Important remark" below, test failures shouldn't be fatal. This would also make them not suitable for autopkgtest. https://buildd.debian.org/status/package.php?p=tree-puzzle=sid ... FAIL: qp-hky-rhet-nucl == Testing: nucleotide data, HKY, rate heterogeneity, quartet puzzling (qp-hky-rhet-nucl) 327c327 < Dasyurus 3 0.1 0.00268 11 0.07879 0.07178 --- > Dasyurus 3 0.1 0.00141 11 0.07879 0.07178 FAIL qp-hky-rhet-nucl.test (exit status: 1) FAIL: qp-hky-rhet-clock-nucl Testing: nucleotide data, HKY, clock, rate heterogeneity, quartet puzzling (qp-hky-rhet-clock-nucl) 327c327 < Dasyurus 3 0.1 0.00268 11 0.07879 0.07178 --- > Dasyurus 3 0.1 0.00141 11 0.07879 0.07178 FAIL qp-hky-rhet-clock-nucl.test (exit status: 1) FAIL: qp-jtt-rhet-prot == Testing: protein data, JTT, rate heterogeneity, quartet puzzling (qp-jtt-rhet-prot) 295c295 < HBA_HUMAN 3 0.01975 0.02293 10 0.74671 0.14184 --- > HBA_HUMAN 3 0.01975 0.02294 10 0.74671 0.14184 FAIL qp-jtt-rhet-prot.test (exit status: 1) FAIL: qp-jtt-rhet-clock-prot Testing: protein data, JTT, clock, rate heterogeneity, quartet puzzling (qp-jtt-rhet-clock-prot) 295c295 < HBA_HUMAN 3 0.01975 0.02293 10 0.74671 0.14184 --- > HBA_HUMAN 3 0.01975 0.02294 10 0.74671 0.14184 FAIL qp-jtt-rhet-clock-prot.test (exit status: 1) FAIL: ut-pure-prot == Testing: protein data, default model, user tree evaluation (ut-pure-prot) 178c178 < HBB_HORSE 2 0.12686 0.03876 9 0.1 0.00105 --- > HBB_HORSE 2 0.12686 0.03876 9 0.1 0.00100 218c218 < HBB_HUMAN 1 0.04915 0.03158 8 0.28347 0.08777 --- > HBB_HUMAN 1 0.04915 0.03158 8 0.28347 0.08778 258c258 < HBB_HORSE 2 0.12653 0.03874 9 0.12334 0.15663 --- > HBB_HORSE 2 0.12653 0.03874 9 0.12334 0.15661 FAIL ut-pure-prot.test (exit status: 1) FAIL: cons-pure-prot Testing: protein data, default model, consensus construction (cons-pure-prot) 230c230 < HBB_HUMAN 1 0.04834 0.03148 8 0.28040 0.08745 --- > HBB_HUMAN 1 0.04834 0.03148 8 0.28040 0.08746 FAIL cons-pure-prot.test (exit status: 1) SKIP: build-remark == *** *** !!! Important remark !!! *** *** Please note that only the output file *.puzzle is checked *** for identity. The overall precision reached in the program *** is heavily dependent on the compiler as well as the optimization *** level (-O) used to compile the executable. *** Hence, even if tests are marked as failed this might just be *** due to differences in less significant digits caused by rounding *** errors from less acurate computations for the sake of faster *** running times. (If you want to be sure about this please refer *** to your compiler's manual!) *** *** Please check the output file differences which are printed during the tests. *** The template files which the results are checked against have been *** generated with TREE-PUZZLE 5.2 compiled with GCC version 3.3-20030226 *** and default compiler flags '-g -O2' and using the SPRNG random number *** generator. *** SKIP build-remark (exit status: 77) Testsuite summary for tree-puzzle 5.3.rc16 # TOTAL: 19 # PASS: 11 # SKIP: 2 # XFAIL: 0 # FAIL: 6 # XPASS: 0 # ERROR: 0 See tests/test-suite.log make[5]: *** [Makefile:563: test-suite.log] Error 1 make[5]: Leaving directory '/<>/tests' --- End Message --- --- Begin Message --- Source: tree-puzzle Source-Version: 5.3~rc16+dfsg-3 Done: Pranav Ballaney We believe that the bug you reported is fixed in the latest
Bug#960758: marked as done (libcamera FTBFS: missing boost build dependencies)
Your message dated Thu, 11 Jun 2020 21:18:37 + with message-id and subject line Bug#960758: fixed in libcamera 0~git20200513+924778e-1.1 has caused the Debian Bug report #960758, regarding libcamera FTBFS: missing boost build dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcamera Version: 0~git20200513+924778e-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=libcamera=sid ... Program openssl found: YES (/usr/bin/openssl) Library atomic found: YES Library dl found: YES Library gnutls found: YES Did not find pkg-config by name 'pkg-config' Found Pkg-config: NO Did not find CMake 'cmake' Found CMake: NO Run-time dependency libudev found: NO (tried pkgconfig and cmake) Run-time dependency threads found: YES Run-time dependency Boost found: NO ../src/ipa/raspberrypi/meson.build:5:0: ERROR: Dependency "boost" not found --- End Message --- --- Begin Message --- Source: libcamera Source-Version: 0~git20200513+924778e-1.1 Done: Luis Paulo Linares We believe that the bug you reported is fixed in the latest version of libcamera, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luis Paulo Linares (supplier of updated libcamera package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 09 Jun 2020 13:08:13 -0300 Source: libcamera Architecture: source Version: 0~git20200513+924778e-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Luis Paulo Linares Closes: 960758 Changes: libcamera (0~git20200513+924778e-1.1) unstable; urgency=medium . * Non-maintainer upload. * debian/control: added libboost-dev to Build-Depends field to avoid a FTBFS. Thanks to Logan Rosen . (Closes: #960758) Checksums-Sha1: e04396e4461ff01e1053762023669dea58e5c424 2410 libcamera_0~git20200513+924778e-1.1.dsc a4b8fead575597bbe5a4dddc14105d891e1cc87c 7936 libcamera_0~git20200513+924778e-1.1.debian.tar.xz f5c9e7dc0453aafc924ea4c10ac954ed87171e72 7554 libcamera_0~git20200513+924778e-1.1_source.buildinfo Checksums-Sha256: 5e1833f1278a0bc63ab1d8ab49a6a441aad9758acb2fa99965ea42c651cef27e 2410 libcamera_0~git20200513+924778e-1.1.dsc ca8102281a1ae49f7ecc781041eff2cddceee1aa737c89f7beced589842d3204 7936 libcamera_0~git20200513+924778e-1.1.debian.tar.xz 885fbfb9fdb7eff85c20e36c1c0d1d5626a7ab0f44d2ba1fc10252724ef16e17 7554 libcamera_0~git20200513+924778e-1.1_source.buildinfo Files: 88d318766188d8cd5927c3b92ede9854 2410 libs optional libcamera_0~git20200513+924778e-1.1.dsc 43363572ac42ac5f0a87de86f1a2879c 7936 libs optional libcamera_0~git20200513+924778e-1.1.debian.tar.xz 7c357fcf1b55bec066e7817d5eb9b9e9 7554 libs optional libcamera_0~git20200513+924778e-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl7f9+wACgkQ3mO5xwTr 6e+5hQ/+JMZCUogjo0SBve0CxjxlJ+TjvSE6UI24C8z3g/2X/4uLLH4cEXPoTjFU 2q8FGBu1GsDzxofxgCoLZspogqq3PaPcge31rsh74v4xttKORlBcmuHs54d2MbEh e0CgxV7FWsfTbAgdR1V83zQ+c1/LcpMcY/bjqtERNZBb04LSs2Mp/raPdlQJR9zQ 09bXfXnCi4L0mIlcxdHpCGlHUZZsJGnRhgcp+GGCAVJJcuFlufbPsLfprxnFbGuV 0zAyWgTZmF+7I38/WjVh6sgU625TfwWHvF+e0qIph5Kn8V8bQlTgSSymOT8gOV9U PrBL35vglNUsizTWWbvPvMc/Y4ktjtp2NGPdUQIsHi8Q/g/2JzVQf3lpdf1BVxeV LYCYagH41O6Z8yN90Fa751RbR7pTA/aOvk+SvwISiZn+N3RhHO2fRnt0VzCnbuwL WCxag+vJ9P46nJFeiY7DF0l6IbTkcOPr2kdvBr+QRhReHuoyMQjYeyUECl2YXS/0 l9MABO3Qff19HnetLZrKYgPt43l9Ju0x1YcckeXkROEn5AptuMfAIumxtN2KFUIE h6i6Sq+RkUOZjiKyVxn6LagF3rpvfAhuz9vbSOAong3nA6IpfcfWvhPMOX0qA7wf /kPSOSfqbnItptzBcgNIlsN6UIi40E//MdxdIK3cL3cjdiPkzGI= =KAMp -END PGP SIGNATURE End Message ---
Bug#962681: battery drain during system shutdown
Package: linux Version: 4.19.0-4 + Severity: grave A regression was introduced in 4.13-rc1(Mainline) and newer kernels. This regression caused battery drain during system suspend, hibernation or shutdown for some PCI devices that are not allowed by user space to wake up the system from sleep (or power off). It has been fixed in the upstream kernel, but still present in buster and bullseye. Kindly patch the debian kernel. https://patchwork.kernel.org/patch/10387667/ Thanks, Gopal.
Bug#962680: janus: CVE-2020-13898 CVE-2020-13899 CVE-2020-13900 CVE-2020-13901
Source: janus Version: 0.10.0-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/meetecho/janus-gateway/pull/2214 Hi, The following vulnerabilities were published for janus. CVE-2020-13898[0]: | An issue was discovered in janus-gateway (aka Janus WebRTC Server) | through 0.10.0. janus_sdp_process in sdp.c has a NULL pointer | dereference. CVE-2020-13899[1]: | An issue was discovered in janus-gateway (aka Janus WebRTC Server) | through 0.10.0. janus_process_incoming_request in janus.c discloses | information from uninitialized stack memory. CVE-2020-13900[2]: | An issue was discovered in janus-gateway (aka Janus WebRTC Server) | through 0.10.0. janus_sdp_preparse in sdp.c has a NULL pointer | dereference. CVE-2020-13901[3]: | An issue was discovered in janus-gateway (aka Janus WebRTC Server) | through 0.10.0. janus_sdp_merge in sdp.c has a stack-based buffer | overflow. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-13898 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13898 [1] https://security-tracker.debian.org/tracker/CVE-2020-13899 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13899 [2] https://security-tracker.debian.org/tracker/CVE-2020-13900 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13900 [3] https://security-tracker.debian.org/tracker/CVE-2020-13901 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13901 [4] https://github.com/meetecho/janus-gateway/pull/2214 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#961536: openmw FTBFS with openscenegraph 3.6.5
Hi Bret On 2020-06-11 02:36:15 -0700, bret curtis wrote: > Hello Sebastian, > On 2020-06-11 at 09:11, sramac...@debian.org wrote: > > Hi bret > > > > On 2020-06-09 18:28:02 +0200, bret curtis wrote: > > > OpenMW 0.46 has been released and I've uploaded it here, it just > > > someone kind and just to review and upload. :) > > > > > > https://salsa.debian.org/games-team/openmw > > > > > > Once uploaded and built, this bug should be closed. > > > > Thanks, uploaded with the alternative build dependencies on > > openscenegraph reversed (patch attached). The buildds only consider the > > first alternative and openscenegraph-3.4 is no longer in the archive. > > > > In d/rules, the dh_missing call should be placed in an override for > > dh_missing. > > > > Cheers > > -- > > Sebastian Ramacher > > That's great news, and that's fine. Thanks! OSG 3.4 is only there for > launchpad PPA reasons as one of our last releases against 3.4. Moving > forward to 0.47 we'll target 3.6 exclusively and drop support for OSG 3.4 > so I'll drop that eventually from control. The build on mipsel failed: https://buildd.debian.org/status/fetch.php?pkg=openmw=mipsel=0.46.0-1=1591883193=0 It's missing -latomic. But I'm wondiering if it really makes sense to build the package on mips*. Is anyone able to play games on mips? > I have a question about getting OpenMW out of 'contrib' and into 'main'. > What exactly is holding us up? > > We have an example-suite (our own game for lack of a better name) that can > be run with OpenMW, would it be better to package this along with OpenMW or > package it up as something new and put a depend on OpenMW for it? I'm not involved in games packaging at all. I'd try to get some feedback on the Debian games list (debian-devel-ga...@lists.debian.org). Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: tagging 936832, tagging 962616, tagging 943322, found 962596 in 20200601~deb10u1 ...
Processing commands for cont...@bugs.debian.org:
> tags 936832 + experimental
Bug #936832 {Done: =?utf-8?q?Santiago_Ruano_Rinc=C3=B3n?=
} [src:ldns] ldns: Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 962616 - sid bullseye
Bug #962616 [src:webkit2gtk] webkit2gtk: FTBFS on mipsel
Removed tag(s) bullseye and sid.
> tags 943322 + sid bullseye
Bug #943322 [python3-llvmlite] llvmlite lags behind upstream verison; blocks
Numba update
Added tag(s) sid and bullseye.
> found 962596 20200601~deb10u1
Bug #962596 [ca-certificates] ca-certificates: Removal of GeoTrust Global CA
requires investigation
Marked as found in versions ca-certificates/20200601~deb10u1.
> found 962596 20200601~deb9u1
Bug #962596 [ca-certificates] ca-certificates: Removal of GeoTrust Global CA
requires investigation
Marked as found in versions ca-certificates/20200601~deb9u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936832
943322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943322
962596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962596
962616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fix meta data
Processing commands for cont...@bugs.debian.org:
> # the bts/britney combination doesn't consider the current source
> # package as fixing this bug
> reassign 959409 src:pbcopper 1.4.0+dfsg-1
Bug #959409 {Done: Andreas Tille } [libpbcopper1.3.0]
pbcopper breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared
object file: No such file or directory
Bug reassigned from package 'libpbcopper1.3.0' to 'src:pbcopper'.
No longer marked as found in versions pbcopper/1.4.0+dfsg-1.
No longer marked as fixed in versions pbcopper/1.6.0+dfsg-2.
Bug #959409 {Done: Andreas Tille } [src:pbcopper] pbcopper
breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared object
file: No such file or directory
Marked as found in versions pbcopper/1.4.0+dfsg-1.
> fixed 959409 1.6.0+dfsg-2
Bug #959409 {Done: Andreas Tille } [src:pbcopper] pbcopper
breaks pbbam (autopkgtest): libpbcopper.so.1.3.0: cannot open shared object
file: No such file or directory
Marked as fixed in versions pbcopper/1.6.0+dfsg-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
959409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#962673: cunit: autopkgtest failure: stdio.h: No such file or directory
Source: cunit Version: 2.1-3-dfsg-2.2 Severity: serious Autopkgtest fails since last NMU with the following messages: autopkgtest [17:33:49]: test test.sh: [--- debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found autopkgtest [17:33:49]: test test.sh: ---] autopkgtest [17:33:49]: test test.sh: - - - - - - - - - - results - - - - - - - - - - test.sh FAIL non-zero exit status 127 autopkgtest [17:33:50]: test test.sh: - - - - - - - - - - stderr - - - - - - - - - - debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found debian/tests/test.c:1:10: fatal error: stdio.h: No such file or directory 1 | #include | ^ compilation terminated. /tmp/autopkgtest-lxc.m92mckta/downtmp/build.vSN/src/debian/tests/test.sh: 8: /tmp/autopkgtest-lxc.m92mckta/downtmp/autopkgtest_tmp/test: not found autopkgtest [17:33:50]: summary test.sh FAIL non-zero exit status 127 The release team has announced [1] that failing autopkgtest are now considered RC in testing. The full log from autopkgtest is availble here[2]. [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html [2] https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cunit/5861880/log.gz Regards, Eriberto
Bug#940093: marked as done (radicale 1.1.1: --export-storage option missing)
Your message dated Thu, 11 Jun 2020 20:17:31 +0200 with message-id <159189945107.4184237.2610750283687514...@auryn.jones.dk> and subject line Re: Bug#940093: radicale 1.1.1: --export-storage option missing has caused the Debian Bug report #940093, regarding radicale 1.1.1: --export-storage option missing 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.) -- 940093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: radicale Version: 1.1.1+20160115-4 Severity: normal Dear Maintainer, I was trying to migrate calendars from 1.1.1 version to 2.x while upgrading to buster following the documentation migration path (https://radicale.org/1to2/). While running radicale with --export-storage option, it lead to the following error : "radicale: error: no such option: --export-storage" Indeed, this option doesn't exist in __main__.py inside radicale package. I also grep export-storage into the package dir, without any result. I also tried to run a newer version of radicale (1.1.6) in a virtual environment. This option seems to be absent too. Maybe it should be reported directly to radicale developpment team too. I hope someone could fix this. Regards, -- System Information: Debian Release: 9.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages radicale depends on: ii adduser 3.115 ii python 2.7.13-2 ii python-radicale 1.1.1+20160115-4 radicale recommends no packages. Versions of packages radicale suggests: pn apache2-utils pn courier-authdaemon pn python-dulwich pn python-ldap pn python-pampy pn python-passlib ii python-requests 2.12.4-1 pn python-sqlalchemy -- Configuration Files: /etc/radicale/config changed: [server] hosts = 0.0.0.0:5232 max_connections = 50 max_content_length = 2000 timeout = 30 [storage] filesystem_folder = /home/fab/collections type = filesystem -- no debconf information --- End Message --- --- Begin Message --- Version: 2.0.0~rc1-1 Quoting Jonas Smedegaard (2019-09-12 12:47:57) > Quoting Fabrice Meyer (2019-09-12 12:05:51) > > I was trying to migrate calendars from 1.1.1 version to 2.x while > > upgrading to buster following the documentation migration path > > (https://radicale.org/1to2/). > > You have two options: > > a) Follow only upstream migration documentation > b) Follow the Debian migration notes While this issue did not get fixed in Buster, it is "fixed" in newer releases. Closing as such. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature --- End Message ---
Bug#962643: cunit: broken NMU does FTBFS
All right with build now! \o/ However, I can see the CI tests failing again and we will need a new NMU. We will work over it now (using Salsa to approve the local changes in tests). I will open a bug. Em qui., 11 de jun. de 2020 às 13:22, Adrian Bunk escreveu: > > Something unrelated missing on your list: > debdiff between previous and current binary packages. > Both file differences and dependency differences are worth checking. Added, thanks! > > > We are in a local sprint. We are monitoring all builds to prevent > > issues. We are 17 people working around several issues. > >... > > Ah, I already wondered about all the Brazilian names in > https://ftp-master.debian.org/deferred.html Yes. We are 14 collaborators and 3 sponsors. > I hope I did not come across as unfriendly, more than 100k unwanted LOC > in the debdiff was just a shock while still drinking my wake-up black tea. I understand you first impressions and I know your nice work around Debian. You're welcome. Cheers, Eriberto
Bug#962645: qbittorrent-nox: Qbittorrent-nox is barely usable after the upgrade to 4.2.4-1+b1
Package: qbittorrent-nox Version: 4.2.4-1+b1 Followup-For: Bug #962645 The same thing happens on the gui version of qbittorrent, at least on amd64! The torrent is added as usual, it downloads as it should and once it is done, qbittorrent crashes with the following output https://paste.debian.net/1151639/ -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qbittorrent-nox depends on: ii libc6 2.30-8 ii libgcc-s1 10.1.0-3 ii libqt5core5a5.12.5+dfsg-10+b1 ii libqt5network5 5.12.5+dfsg-10+b1 ii libqt5xml5 5.12.5+dfsg-10+b1 ii libssl1.1 1.1.1g-1 ii libstdc++6 10.1.0-3 ii libtorrent-rasterbar10 1.2.5-1+b1 ii zlib1g 1:1.2.11.dfsg-2 qbittorrent-nox recommends no packages. Versions of packages qbittorrent-nox suggests: pn qbittorrent-dbg -- no debconf information
Processed: [bts-link] source package src:svgpp
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:svgpp > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #960426 (http://bugs.debian.org/960426) > # Bug title: svgpp: FTBFS with boost 1.71 > # * https://github.com/svgpp/svgpp/issues/79 > # * remote status changed: (?) -> closed > # * closed upstream > tags 960426 + fixed-upstream Bug #960426 [src:svgpp] svgpp: FTBFS with boost 1.71 Added tag(s) fixed-upstream. > usertags 960426 + status-closed There were no usertags set. Usertags are now: status-closed. > 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: [bts-link] source package meson
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package meson > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #960877 (http://bugs.debian.org/960877) > # Bug title: meson 0.54.2-1 breaks bali-phy build > # * https://github.com/mesonbuild/meson/issues/7221 > # * remote status changed: open -> closed > # * closed upstream > tags 960877 + fixed-upstream Bug #960877 [meson] meson 0.54.2-1 breaks bali-phy build Bug #962092 [meson] meson: Link with static lib instead of shared one with boost 1.71 Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 960877 - status-open Usertags were: status-open. Usertags are now: . > usertags 960877 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #962092 (http://bugs.debian.org/962092) > # Bug title: meson: Link with static lib instead of shared one with boost 1.71 > # * https://github.com/mesonbuild/meson/issues/7221 > # * remote status changed: (?) -> closed > # * closed upstream > tags 962092 + fixed-upstream Bug #962092 [meson] meson: Link with static lib instead of shared one with boost 1.71 Bug #960877 [meson] meson 0.54.2-1 breaks bali-phy build Ignoring request to alter tags of bug #962092 to the same tags previously set Ignoring request to alter tags of bug #960877 to the same tags previously set > usertags 962092 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 960877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960877 962092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962596: ca-certificates: Removal of GeoTrust Global CA requires investigation
On 11/06/2020 18:34, Michael Borg wrote: > Yep I know but I cannot tell all my customers to run this workaround, some > of our users are not experienced at all The only thing I see here is > that I need to provide a hotfix ourselves. We cannot wait for days... You > are saying we cannot make an exception and push this fix ASAP? Pushing packages to Debian takes time. If you need something for today you need to fix it yourself. You can downgrade to the old version of the package ca-certificates or install the missed certificate manually This recipe allows to do that: wget --no-check-certificate -c https://www.geotrust.com/resources/root_certificates/certificates/GeoTrust_Global_CA.pem \ && mkdir /usr/local/share/ca-certificates/extra \ && mv GeoTrust_Global_CA.pem /usr/local/share/ca-certificates/extra/GeoTrust_Global_CA.crt \ && update-ca-certificates And when you upgrade to the fixed version of ca-certificates you can remove the directory /usr/local/share/ca-certificates/extra and run the command update-ca-certificates again. signature.asc Description: OpenPGP digital signature
Bug#962643: cunit: broken NMU does FTBFS
On Thu, Jun 11, 2020 at 11:45:45AM -0300, Eriberto wrote: >... > So, I did a double > check using my sponsor checklist[1], I ran debuild and cowbuilder. > After this I did a debuild -S and the trash inside debian/ was sent. > Sorry for this. > > [1] http://bit.ly/pkgcheck >... When I sponsor packages I am usually doing the -S at the start and won't touch the built source package afterwards - this is either being uploaded or rejected later. Something unrelated missing on your list: debdiff between previous and current binary packages. Both file differences and dependency differences are worth checking. > We are in a local sprint. We are monitoring all builds to prevent > issues. We are 17 people working around several issues. >... Ah, I already wondered about all the Brazilian names in https://ftp-master.debian.org/deferred.html > Thanks a lot for your help. I hope I did not come across as unfriendly, more than 100k unwanted LOC in the debdiff was just a shock while still drinking my wake-up black tea. > Cheers, > > Eriberto cu Adrian
Bug#960014: marked as done (libmath-gsl-perl: FTBFS with gsl 2.6)
Your message dated Thu, 11 Jun 2020 16:21:44 + with message-id and subject line Bug#960011: fixed in libmath-gsl-perl 0.41-1 has caused the Debian Bug report #960011, regarding libmath-gsl-perl: FTBFS with gsl 2.6 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.) -- 960011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmath-gsl-perl Version: 0.40-1 Severity: serious Tags: ftbfs bullseye sid Hi Maintainer In a recent rebuild for the gsl 2.6 transition, libmath-gsl-perl FTBFS on all architectures [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://buildd.debian.org/status/package.php?p=libmath-gsl-perl dh_auto_configure -a perl Build.PL --installdirs vendor --config "optimize=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now" Checking for GSL using gsl-config Found GSL 2.6 (via gsl-config) installed in /usr Checking if x86_64-linux-gnu-gcc supports "-Wall"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-sometimes-uninitialized"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-function"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-value"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-function"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-variable"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-gnu"...yes Checking if x86_64-linux-gnu-gcc supports "-g"...unsupported version: 2.6 at Build.PL line 80. yes dh_auto_configure: error: perl Build.PL --installdirs vendor --config "optimize=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now" returned exit code 25 --- End Message --- --- Begin Message --- Source: libmath-gsl-perl Source-Version: 0.41-1 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libmath-gsl-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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libmath-gsl-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: SHA512 Format: 1.8 Date: Thu, 11 Jun 2020 17:50:34 +0200 Source: libmath-gsl-perl Architecture: source Version: 0.41-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 960011 Changes: libmath-gsl-perl (0.41-1) unstable; urgency=medium . * Team upload. . * debian/control: update Build-Depends for cross builds. * debian/watch: use uscan version 4. * Update 'DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow' to '=+all'. . * Import upstream version 0.41. Fixes "FBTFS (unsupported version: 2.6 at Build.PL line 80)" (Closes: #960011) * Refresh 0002-Fixed-spelling-errors-in-man.patch. * Add more fixes to 0002-Fixed-spelling-errors-in-man.patch. * Declare compliance with Debian Policy 4.5.0. * Set Rules-Requires-Root: no. * Drop unneeded version constraints from (build) dependencies. * Annotate test-only build dependencies with . * Bump debhelper-compat to 13. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository- Browse. * Remove obsolete field Name from debian/upstream/metadata. * Add patch to do swig rebuild only for current GSL version. Checksums-Sha1: 536ac793673aa5753bee7b83935fb67ab90d927b 2582 libmath-gsl-perl_0.41-1.dsc d660183b0dc33cf3e578be08e8fdacdec857a4d8 21587821 libmath-gsl-perl_0.41.orig.tar.gz d380e68f2f939b79a448172adb0a9d58e1817fac 18724 libmath-gsl-perl_0.41-1.debian.tar.xz Checksums-Sha256: 941de802aac8835c01d28e1afd1fab713c5632cd91d8b0c146f6d066cd50c4a4 2582 libmath-gsl-perl_0.41-1.dsc
Bug#960011: marked as done (libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80))
Your message dated Thu, 11 Jun 2020 16:21:44 + with message-id and subject line Bug#960011: fixed in libmath-gsl-perl 0.41-1 has caused the Debian Bug report #960011, regarding libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80) 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.) -- 960011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmath-gsl-perl Version: 0.40-1 Severity: serious Justification: makes the package in question unusable or mostly so Control: block 959133 by -1 Dear Maintainer, Your package FTBFS during the gsl transition: dh build-arch dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure -a perl Build.PL --installdirs vendor --config "optimize=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now" Checking for GSL using gsl-config Found GSL 2.6 (via gsl-config) installed in /usr Checking if x86_64-linux-gnu-gcc supports "-Wall"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-sometimes-uninitialized"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-function"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-value"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-function"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-variable"...yes Checking if x86_64-linux-gnu-gcc supports "-Wno-gnu"...yes Checking if x86_64-linux-gnu-gcc supports "-g"...unsupported version: 2.6 at Build.PL line 80. yes dh_auto_configure: error: perl Build.PL --installdirs vendor --config "optimize=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now" returned exit code 25 make: *** [debian/rules:9: build-arch] Error 25 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 https://buildd.debian.org/status/fetch.php?pkg=libmath-gsl-perl=amd64=0.40-1%2Bb2=1588896435=0 Kind Regards, Bas --- End Message --- --- Begin Message --- Source: libmath-gsl-perl Source-Version: 0.41-1 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libmath-gsl-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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libmath-gsl-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: SHA512 Format: 1.8 Date: Thu, 11 Jun 2020 17:50:34 +0200 Source: libmath-gsl-perl Architecture: source Version: 0.41-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 960011 Changes: libmath-gsl-perl (0.41-1) unstable; urgency=medium . * Team upload. . * debian/control: update Build-Depends for cross builds. * debian/watch: use uscan version 4. * Update 'DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow' to '=+all'. . * Import upstream version 0.41. Fixes "FBTFS (unsupported version: 2.6 at Build.PL line 80)" (Closes: #960011) * Refresh 0002-Fixed-spelling-errors-in-man.patch. * Add more fixes to 0002-Fixed-spelling-errors-in-man.patch. * Declare compliance with Debian Policy 4.5.0. * Set Rules-Requires-Root: no. * Drop unneeded version constraints from (build) dependencies. * Annotate test-only build dependencies with . * Bump debhelper-compat to 13. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository- Browse. * Remove obsolete field Name from debian/upstream/metadata. * Add patch to do swig rebuild only for current GSL version. Checksums-Sha1: 536ac793673aa5753bee7b83935fb67ab90d927b 2582 libmath-gsl-perl_0.41-1.dsc d660183b0dc33cf3e578be08e8fdacdec857a4d8
Bug#962643: marked as done (cunit: broken NMU does FTBFS)
Your message dated Thu, 11 Jun 2020 15:48:46 + with message-id and subject line Bug#962643: fixed in cunit 2.1-3-dfsg-2.2 has caused the Debian Bug report #962643, regarding cunit: broken NMU does FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cunit Version: 2.1-3-dfsg-2.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=cunit=sid ... Making all in Framework make[6]: Entering directory '/<>/debian/build/CUnit/Sources/Framework' /bin/bash ../../../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -DRELEASE=@RELEASE@ -Wall -W -pedantic -Wshadow -ansi -I/<>/debian/build/CUnit/Headers -std=c99 -Wl,-z,relro -Wl,-z,defs -L/<>/debian/build/CUnit/Sources -o libcunitfmk.la CUError.lo MyMem.lo TestDB.lo TestRun.lo Util.lo -lc libtool: link: ar cr .libs/libcunitfmk.a .libs/CUError.o .libs/MyMem.o .libs/TestDB.o .libs/TestRun.o .libs/Util.o ar: .libs/CUError.o: No such file or directory make[6]: *** [Makefile:397: libcunitfmk.la] Error 1 I can reproduce the problem just by trying to build the package. The diffstat of this NMU is 510 files changed, 139791 insertions(+), 3 deletions(-) It is the responsibility of the sponsor (Cc'ed) to verify that sponsored uploads are not broken: https://wiki.debian.org/DebianMentorsFaq#What_is_the_process_for_sponsoring_a_package.3F --- End Message --- --- Begin Message --- Source: cunit Source-Version: 2.1-3-dfsg-2.2 Done: Regis Fernandes Gontijo We believe that the bug you reported is fixed in the latest version of cunit, 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. Regis Fernandes Gontijo (supplier of updated cunit 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, 11 Jun 2020 14:32:59 + Source: cunit Architecture: source Version: 2.1-3-dfsg-2.2 Distribution: unstable Urgency: medium Maintainer: Azat Khuzhin Changed-By: Regis Fernandes Gontijo Closes: 962643 Changes: cunit (2.1-3-dfsg-2.2) unstable; urgency=medium . * Non-maintainer upload. * Fixed cleanup of package tree to allow it build twice and avoid a FTBFS. Many thanks to Adrian Bunk. (Closes: #962643) Checksums-Sha1: 3b99e0e5ff9dfc4d8f2dc67887eccf95bd067f5c 2203 cunit_2.1-3-dfsg-2.2.dsc 0c0b15e96f3c9f6ac1d972a5747906179c59660d 7364 cunit_2.1-3-dfsg-2.2.debian.tar.xz 50ebe9a759cae1e8133c2e6a7472b17d77f123a4 5445 cunit_2.1-3-dfsg-2.2_source.buildinfo Checksums-Sha256: b6e440cabfa2ad9896f9ecc5b233f69a3dff4ba7b9593f47df4f81cd0c6ba5db 2203 cunit_2.1-3-dfsg-2.2.dsc f7f6399749f4993a29a8303876428fd3320ff572de5ed0df6a81b972d557aeea 7364 cunit_2.1-3-dfsg-2.2.debian.tar.xz 95bcf83e427ee43373f9ef761509b692f7693fe27e597b4d865aeab2f2567bad 5445 cunit_2.1-3-dfsg-2.2_source.buildinfo Files: b62520dc3d2b4a116b0baf574034cc84 2203 libs optional cunit_2.1-3-dfsg-2.2.dsc ea075c49cf57ebf96768119389dfce61 7364 libs optional cunit_2.1-3-dfsg-2.2.debian.tar.xz cf492e387186b54e31a56193079a89b8 5445 libs optional cunit_2.1-3-dfsg-2.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl7iT0IACgkQ3mO5xwTr 6e8XmxAAo8DbEHDReOs7IRIqs8I2BmU82mC01P0M1+vadXotFZbUVGEYIU+WC3Un 2pInYjv8B1NdJIOildiTgsffmp+63asSGFaeTRyV2Tf3t3WoIfvhbm9VQ9kJ6xCJ MFwBXMiaFvL8SQloROBB4lSHyvmmUQ9ingin1W0mVra3uIOBT9cLGvLH34hoo8/4 Yf4qROWgjtTJx+wx1WKx8FNFSC4mB+ktqOrxhqmJPJVRjj90IXnPomjImh8nyoIe UdQAWiJ3ZdMh2HcQ1gtRJeIVwLYruIRcuQ2I67S2i8bNVDT6+scI6zgalJlps0W9 qLsiuagnuStik1W6TSZxSi0C1OLkyyBx1BNajg9y7ryfHCdsQqeX7G0sRdvhTb06 2O26q4Jyp1Bpuqj3GJYirJCIDIoTEJLIfjtW9HvGuZw4mNW8ZRq0wENoEsI2OTV2 a9fFh9qmBZK+fbF6JrImmG6Ne5hspvTrLRRnXywHl5fnoZC1lFEM2bzOH7x1Ubo8 ae/vBsCr4ew4SlP7dcZB+7AOkrAfP21XHhJEi0dwM/ZDxNMXvhRDLP1oFEP/C3X3 zrgdV33i9V/0bPA1NtBuEV5ySK5xfdkdL/fo3Gbf1IUZMw5O3Lnvw+QOjR1OO5Eh BnZCuynqC7+6xr6ylcFrsRyPVReeq12zvIWW1q+iPEH5qKVv/Hc= =3fG/ -END PGP SIGNATURE End
Processed: Re: Bug#962596: ca-certificates: Removal of GeoTrust Global CA requires investigation
Processing control commands: > severity -1 serious Bug #962596 [ca-certificates] ca-certificates: Removal of GeoTrust Global CA requires investigation Severity set to 'serious' from 'important' > tags -1 + pending Bug #962596 [ca-certificates] ca-certificates: Removal of GeoTrust Global CA requires investigation Added tag(s) pending. > tags 942915 + pending Bug #942915 [src:ca-certificates] ca-certificates: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #942915 to the same tags previously set -- 942915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942915 962596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: llvmlite lags behind upstream verison; blocks Numba update
Processing control commands: > severity -1 serious Bug #943322 [python3-llvmlite] llvmlite lags behind upstream verison; blocks Numba update Severity set to 'serious' from 'normal' > block 962176 by -1 Bug #962176 [src:numba] numba: fails autopktest with numpy 1.18 962176 was not blocked by any bugs. 962176 was not blocking any bugs. Added blocking bug(s) of 962176: 943322 -- 943322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943322 962176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962643: cunit: broken NMU does FTBFS
Hi Adrian, how are you? Em qui., 11 de jun. de 2020 às 03:15, Adrian Bunk escreveu: > > On Thu, Jun 11, 2020 at 08:46:23AM +0300, Adrian Bunk wrote: > >... > > The diffstat of this NMU is > > 510 files changed, 139791 insertions(+), 3 deletions(-) > > > > It is the responsibility of the sponsor (Cc'ed) to verify that > > sponsored uploads are not broken: > > https://wiki.debian.org/DebianMentorsFaq#What_is_the_process_for_sponsoring_a_package.3F > > I have to take that back, it is actually likely that this went wrong on > the sponsor side due to verifying the package: > > The debdiff in #960715 looks OK. > > Building a source package for upload after having done a testbuild > can cause this kind of problems, when the source tree is not clean > many unwanted changes might end up in the new source package. Thanks a lot for your comments. The problem is caused by several files in directories created by package inside debian/ (build, build-ncurses e tmp-ncurses) and not cleaned by dh_clean. Initially, Regis did a fix for this but I asked him to remove it because an NMU should not modify some things in third-party packages (cleanup wasn't a RC target). So, I did a double check using my sponsor checklist[1], I ran debuild and cowbuilder. After this I did a debuild -S and the trash inside debian/ was sent. Sorry for this. [1] http://bit.ly/pkgcheck We are in a local sprint. We are monitoring all builds to prevent issues. We are 17 people working around several issues. Don't worry because this issue will be fixed today with a NMU without delay and with an override_dh_autoclean. Thanks a lot for your help. Cheers, Eriberto
Bug#962616: webkit2gtk: FTBFS on mipsel
On Thu, Jun 11, 2020 at 11:19:10AM +0300, Adrian Bunk wrote: > > > | Exception: gtkdoc-scangobj produced a non-zero return code 250 > > > | Command: > > > | gtkdoc-scangobj --module=webkit2gtk-4.0 > > > | Error output: > > > | > > > | > > > | ninja: build stopped: subcommand failed. > > > > I've seen this several times, and it seems to happen randomly, and > > only on mipsel. I haven't been able to reproduce it in a buildd. > > > > I suspect it's a bug in gtk-doc-tools ? > > It fails on the Loongson buildds but succeeds on the others, > and the problem started recently: > https://buildd.debian.org/status/logs.php?pkg=webkit2gtk=mipsel Ah, ok. FWIW I just built it again in eller.debian.org and everything went fine. Berto
Processed: libidn: diff for NMU version 1.33-2.3
Processing control commands: > tags 925746 + pending Bug #925746 [src:libidn] libidn: ftbfs with GCC-9 Added tag(s) pending. -- 925746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925746: libidn: diff for NMU version 1.33-2.3
Control: tags 925746 + pending Dear maintainer, I've prepared an NMU for libidn (versioned as 1.33-2.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer or cancel the NMU. I've uploaded to experimental and if this fix work fine i'll send a new upload to unstable. Regards, Marcelo S Mota diff -Nru libidn-1.33/debian/changelog libidn-1.33/debian/changelog --- libidn-1.33/debian/changelog2018-04-10 13:03:08.0 -0300 +++ libidn-1.33/debian/changelog2020-06-10 02:39:16.0 -0300 @@ -1,3 +1,12 @@ +libidn (1.33-2.3) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches/0005-Fix-link-failure.patch: added to fix build +failure with gnulibs's upstream patch. Thanks to Gianfranco Costamagna +. (Closes: #925746) + + -- Marcelo Soares Mota Wed, 10 Jun 2020 02:39:16 -0300 + libidn (1.33-2.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru libidn-1.33/debian/patches/0005-Fix-link-failure.patch libidn-1.33/debian/patches/0005-Fix-link-failure.patch --- libidn-1.33/debian/patches/0005-Fix-link-failure.patch 1969-12-31 21:00:00.0 -0300 +++ libidn-1.33/debian/patches/0005-Fix-link-failure.patch 2020-06-10 02:39:16.0 -0300 @@ -0,0 +1,19 @@ +Description: Fix link failure with gnulib's upstream patch +Author: Gianfranco Costamagna +Last-Update: 2019-03-20 +Bug-Debian: https://bugs.debian.org/925746 +Origin: https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=cca32830b57e91f837c01d15b8732f23ff97fc36 + +Index: libidn-1.33/lib/gltests/glthread/thread.h +=== +--- libidn-1.33.orig/lib/gltests/glthread/thread.h libidn-1.33/lib/gltests/glthread/thread.h +@@ -122,8 +122,6 @@ +call to foo(...) in the same function. To avoid this, we test the +address of a function in libpthread that we don't use. */ + +-# pragma weak pthread_create +- + # ifdef __clang__ + /* Without this, clang complains that pthread_sigmask is never declared. */ + # include diff -Nru libidn-1.33/debian/patches/series libidn-1.33/debian/patches/series --- libidn-1.33/debian/patches/series 2017-12-11 20:13:42.0 -0200 +++ libidn-1.33/debian/patches/series 2020-06-10 02:39:16.0 -0300 @@ -2,3 +2,4 @@ 0002-Update-intprops.h-for-gcc-7-compatibility.patch 0003-Increase-value-for-Wframe-larger-than-gcc-7.patch 0004-Update-Makefile.gdoc-to-use-GDOC_BIN-instead-of-hard.patch +0005-Fix-link-failure.patch
Processed: block 960495 with 949027
Processing commands for cont...@bugs.debian.org: > block 960495 with 949027 Bug #960495 [release.debian.org] transition: gdal 960495 was blocked by: 960369 953138 962641 960495 was not blocking any bugs. Added blocking bug(s) of 960495: 949027 > thanks Stopping processing here. Please contact me if you need assistance. -- 960495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 949027
Processing commands for cont...@bugs.debian.org: > tags 949027 + ftbfs Bug #949027 [src:node-srs] node-srs: uses old python to build Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 949027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: davical build depends on rst2pdf that might not be in bullseye
Processing control commands: > block 962651 by -1 Bug #962651 [rst2pdf] rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye 962651 was not blocked by any bugs. 962651 was blocking: 958362 Added blocking bug(s) of 962651: 962653 -- 962651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962651 962653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962653: davical build depends on rst2pdf that might not be in bullseye
Source: davical Version: 1.1.9.3-1 Severity: serious Control: block 962651 by -1 davical build depends on rst2pdf that might not be in bullseye due to #962651.
Bug#950127: marked as done (pyside2 fails all autopkg tests)
Your message dated Thu, 11 Jun 2020 10:00:41 + with message-id and subject line Bug#950127: fixed in pyside2 5.15.0-1~exp1 has caused the Debian Bug report #950127, regarding pyside2 fails all autopkg tests 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.) -- 950127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyside2 Version: 5.13.2-2.2 Severity: serious Tags: sid bullseye https://ci.debian.net/packages/p/pyside2/ [...] autopkgtest [09:55:16]: summary command1 FAIL non-zero exit status 127 command2 FAIL non-zero exit status 127 command3 FAIL non-zero exit status 127 command4 FAIL non-zero exit status 127 command5 FAIL non-zero exit status 127 command6 FAIL non-zero exit status 127 command7 FAIL non-zero exit status 127 command8 FAIL non-zero exit status 127 command9 FAIL non-zero exit status 127 command10FAIL non-zero exit status 127 command11FAIL non-zero exit status 127 command12FAIL non-zero exit status 127 command13FAIL non-zero exit status 127 command14FAIL non-zero exit status 127 command15FAIL non-zero exit status 127 command16FAIL non-zero exit status 127 command17FAIL non-zero exit status 127 command18FAIL non-zero exit status 127 command19FAIL non-zero exit status 127 command20FAIL non-zero exit status 127 command21FAIL non-zero exit status 127 command22FAIL non-zero exit status 127 command23FAIL non-zero exit status 127 command24FAIL non-zero exit status 127 command25FAIL non-zero exit status 127 command26FAIL non-zero exit status 127 command27FAIL non-zero exit status 127 command28FAIL non-zero exit status 127 command29FAIL non-zero exit status 127 command30FAIL non-zero exit status 127 command31FAIL non-zero exit status 127 command32FAIL non-zero exit status 127 command33FAIL non-zero exit status 127 command34FAIL non-zero exit status 127 command35FAIL non-zero exit status 127 command36FAIL non-zero exit status 127 command37FAIL non-zero exit status 127 command38FAIL non-zero exit status 127 command39FAIL non-zero exit status 127 command40FAIL non-zero exit status 127 --- End Message --- --- Begin Message --- Source: pyside2 Source-Version: 5.15.0-1~exp1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of pyside2, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated pyside2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jun 2020 14:48:45 +0200 Source: pyside2 Binary: libpyside2-dev libpyside2-py3-5.15 libpyside2-py3-5.15-dbgsym libshiboken2-dev libshiboken2-py3-5.15 libshiboken2-py3-5.15-dbgsym pyside2-tools pyside2-tools-dbgsym python-pyside2-doc python3-pyside2.qt3dcore python3-pyside2.qt3dcore-dbgsym python3-pyside2.qt3dinput python3-pyside2.qt3dinput-dbgsym python3-pyside2.qt3dlogic python3-pyside2.qt3dlogic-dbgsym python3-pyside2.qt3drender python3-pyside2.qt3drender-dbgsym python3-pyside2.qtcharts python3-pyside2.qtcharts-dbgsym python3-pyside2.qtconcurrent python3-pyside2.qtconcurrent-dbgsym python3-pyside2.qtcore python3-pyside2.qtcore-dbgsym python3-pyside2.qtdatavisualization python3-pyside2.qtdatavisualization-dbgsym python3-pyside2.qtgui python3-pyside2.qtgui-dbgsym python3-pyside2.qthelp python3-pyside2.qthelp-dbgsym python3-pyside2.qtlocation python3-pyside2.qtlocation-dbgsym python3-pyside2.qtmultimedia python3-pyside2.qtmultimedia-dbgsym python3-pyside2.qtmultimediawidgets python3-pyside2.qtmultimediawidgets-dbgsym
Bug#936832: marked as done (ldns: Python2 removal in sid/bullseye)
Your message dated Thu, 11 Jun 2020 10:00:11 + with message-id and subject line Bug#936832: fixed in ldns 1.7.1-1 has caused the Debian Bug report #936832, regarding ldns: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ldns Version: 1.7.0-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:ldns If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: ldns Source-Version: 1.7.1-1 Done: =?utf-8?q?Santiago_Ruano_Rinc=C3=B3n?= We believe that the bug you reported is fixed in the latest version of ldns, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Santiago Ruano Rincón (supplier of updated ldns package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Jun 2020 23:02:22 +0200 Source: ldns Binary: ldnsutils ldnsutils-dbgsym libldns-dev libldns3 libldns3-dbgsym python3-ldns python3-ldns-dbgsym Architecture: source amd64 Version: 1.7.1-1 Distribution: experimental Urgency: low Maintainer: Debian DNS Team Changed-By: Santiago Ruano Rincón Description: ldnsutils - ldns library for DNS programming libldns-dev - ldns library for DNS programming libldns3 - ldns library for DNS programming python3-ldns - Python3 bindings for the ldns library for DNS programming Closes: 929578 936832 945324 Changes: ldns (1.7.1-1) experimental; urgency=low . * Team upload. * New upstream version 1.7.1 - Fixes: libldns2: CDS/CDNSKEY RRs are signed with ZSK instead of KSK (Closes: #945324) * Remove no longer needed patches: - 0002-Check-parse-limit-before-t-increment.patch - 0003-bugfix-1257-Free-after-reallocing-to-0-size.patch -
Bug#949339: marked as done (libshiboken2-py3-5.14: missing Breaks+Replaces: libshiboken2-py3-5.13)
Your message dated Thu, 11 Jun 2020 10:00:40 + with message-id and subject line Bug#949339: fixed in pyside2 5.15.0-1~exp1 has caused the Debian Bug report #949339, regarding libshiboken2-py3-5.14: missing Breaks+Replaces: libshiboken2-py3-5.13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 949339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libshiboken2-py3-5.14 Version: 5.14.0-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libshiboken2-py3-5.14_5.14.0-1~exp1_amd64.deb ... Unpacking libshiboken2-py3-5.14 (5.14.0-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libshiboken2-py3-5.14_5.14.0-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/shiboken2/__init__.py', which is also in package libshiboken2-py3-5.13 5.13.2-2.2+b1 Errors were encountered while processing: /var/cache/apt/archives/libshiboken2-py3-5.14_5.14.0-1~exp1_amd64.deb dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) cheers, Andreas libshiboken2-py3-5.13=5.13.2-2.2+b1_libshiboken2-py3-5.14=5.14.0-1~exp1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: pyside2 Source-Version: 5.15.0-1~exp1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of pyside2, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated pyside2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jun 2020 14:48:45 +0200 Source: pyside2 Binary: libpyside2-dev libpyside2-py3-5.15 libpyside2-py3-5.15-dbgsym libshiboken2-dev libshiboken2-py3-5.15 libshiboken2-py3-5.15-dbgsym pyside2-tools pyside2-tools-dbgsym python-pyside2-doc python3-pyside2.qt3dcore python3-pyside2.qt3dcore-dbgsym python3-pyside2.qt3dinput python3-pyside2.qt3dinput-dbgsym python3-pyside2.qt3dlogic python3-pyside2.qt3dlogic-dbgsym python3-pyside2.qt3drender python3-pyside2.qt3drender-dbgsym python3-pyside2.qtcharts python3-pyside2.qtcharts-dbgsym python3-pyside2.qtconcurrent python3-pyside2.qtconcurrent-dbgsym python3-pyside2.qtcore python3-pyside2.qtcore-dbgsym python3-pyside2.qtdatavisualization python3-pyside2.qtdatavisualization-dbgsym python3-pyside2.qtgui python3-pyside2.qtgui-dbgsym python3-pyside2.qthelp python3-pyside2.qthelp-dbgsym python3-pyside2.qtlocation python3-pyside2.qtlocation-dbgsym python3-pyside2.qtmultimedia python3-pyside2.qtmultimedia-dbgsym python3-pyside2.qtmultimediawidgets python3-pyside2.qtmultimediawidgets-dbgsym python3-pyside2.qtnetwork python3-pyside2.qtnetwork-dbgsym python3-pyside2.qtopengl python3-pyside2.qtopengl-dbgsym python3-pyside2.qtopenglfunctions python3-pyside2.qtopenglfunctions-dbgsym python3-pyside2.qtpositioning python3-pyside2.qtpositioning-dbgsym python3-pyside2.qtprintsupport python3-pyside2.qtprintsupport-dbgsym python3-pyside2.qtqml python3-pyside2.qtqml-dbgsym python3-pyside2.qtquick python3-pyside2.qtquick-dbgsym python3-pyside2.qtquickwidgets python3-pyside2.qtquickwidgets-dbgsym python3-pyside2.qtscript python3-pyside2.qtscript-dbgsym python3-pyside2.qtscripttools python3-pyside2.qtscripttools-dbgsym python3-pyside2.qtscxml python3-pyside2.qtscxml-dbgsym python3-pyside2.qtsensors python3-pyside2.qtsensors-dbgsym python3-pyside2.qtsql python3-pyside2.qtsql-dbgsym python3-pyside2.qtsvg python3-pyside2.qtsvg-dbgsym python3-pyside2.qttest python3-pyside2.qttest-dbgsym
Bug#950126: marked as done (pyside2 ftbfs in experimental)
Your message dated Thu, 11 Jun 2020 10:00:41 + with message-id and subject line Bug#950126: fixed in pyside2 5.15.0-1~exp1 has caused the Debian Bug report #950126, regarding pyside2 ftbfs in experimental 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.) -- 950126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyside2 Version: 5.14.0-1~exp1 Severity: serious Tags: sid bullseye [...] (gui) [3295ms] Writing log files... [ESC[0;32mOKESC[0m] (gui) [3327ms] Running Source generator... qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primiti ve type 'int *' of argument 2 in function 'QAccessibleTextInterface::attributes(int offset, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 3 in function 'QAccessibleTextInterface::attrib utes(int offset, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 2 in function 'QAccessibleTextInterface::select ion(int selectionIndex, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 3 in function 'QAccessibleTextInterface::select ion(int selectionIndex, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 3 in function 'QAccessibleTextInterface::textAf terOffset(int offset, QAccessible::TextBoundaryType boundaryType, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 4 in function 'QAccessibleTextInterface::textAf terOffset(int offset, QAccessible::TextBoundaryType boundaryType, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 3 in function 'QAccessibleTextInterface::textAt Offset(int offset, QAccessible::TextBoundaryType boundaryType, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 4 in function 'QAccessibleTextInterface::textAt Offset(int offset, QAccessible::TextBoundaryType boundaryType, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 3 in function 'QAccessibleTextInterface::textBe foreOffset(int offset, QAccessible::TextBoundaryType boundaryType, int * startOffset, int * endOffset) const'. qt.shiboken: (gui) There's no user provided way (conversion rule, argument removal, custom code, etc) to handle the primitive type 'int *' of argument 4 in function 'QAccessibleTextInterface::textBe foreOffset(int offset, QAccessible::TextBoundaryType boundaryType, int * startOffset, int * endOffset) const'. /packages/tmp/p/pyside2-5.14.0/sources/pyside2/libpyside/signalmanager.cpp:56:10: fatal error: sbkstaticstrings.h: No such file or directory 56 | #include | ^~~~ compilation terminated. make[4]: *** [libpyside/CMakeFiles/pyside2.dir/build.make:96: libpyside/CMakeFiles/pyside2.dir/signalmanager.cpp.o] Error 1 make[4]: Leaving directory '/packages/tmp/p/pyside2-5.14.0/pyside3_build/py3.8-qt5.12.5-64bit-relwithdebinfo/pyside2' make[3]: *** [CMakeFiles/Makefile2:129: libpyside/CMakeFiles/pyside2.dir/all] Error 2 make[3]: *** Waiting for unfinished jobs --- End Message --- --- Begin Message --- Source: pyside2 Source-Version: 5.15.0-1~exp1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of pyside2, 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 950...@bugs.debian.org, and the maintainer will reopen the bug
Bug#962651: rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye
Package: rst2pdf Version: 0.97-2 Severity: serious Control: block 958362 by -1 rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye due to #958362.
Processed: rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye
Processing control commands: > block 958362 by -1 Bug #958362 [src:pdfrw] pdfrw: fails with python 3.7+ -- abandoned upstream 958362 was not blocked by any bugs. 958362 was not blocking any bugs. Added blocking bug(s) of 958362: 962651 -- 958362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958362 962651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#817954: Does this bug prevent firefox from entering backports also?
On Thu, 25 Jul 2019 12:10:45 +0200 Johannes Rohr wrote: > It would be great to have firefox (or the next firefox-esr) in > buster-backports, as it has important new functionality relevant for > privacy and data protection, such as the multi account containers > function. However, this bug prevents firefox from entering testing, > which in my understanding implies, that it cannot make it into backports > as well. Is there some way of getting an up-to-date firefox version into > stable? For now I work with the binary directly downloaded from > mozilla.org, but this is a kludge. > We have created https://fasttrack.debian.net for packages like this which cannot go with stable releases and hence blocked from entering testing and backports as well. Mike, Would you like to maintain firefox in buster-fasttrack? I'm part of the team that maintain this unofficial service and maintains gitlab there. If you are okay with the idea, but does not want to do the extra work, I'd be happy to maintain it in fasttrack. signature.asc Description: OpenPGP digital signature
Bug#958917: marked as done (openmw: random crashes)
Your message dated Thu, 11 Jun 2020 09:36:00 + with message-id and subject line Bug#958917: fixed in openmw 0.46.0-1 has caused the Debian Bug report #958917, regarding openmw: random crashes 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.) -- 958917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openmw Version: 0.45.0-4 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Nothing special. Easiest reproduction is starting a new game and saving a game 3-5 times in a row. * What exactly did you do (or not do) that was effective (or ineffective)? Disable all add-ons and starting again. * What was the outcome of this action? No difference. * What outcome did you expect instead? I expected a game to not crash randomly. The root cause was a bug in openscenegraph, that was recently fixed: #945875 I assume openmw must be rebuild and/or updated with openscenegraph 3.6.5+dfsg1-1 to fix crashes Upstream bug report: https://gitlab.com/OpenMW/openmw/issues/5205 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openmw depends on: ii libavcodec587:4.2.2-1+b1 ii libavformat58 7:4.2.2-1+b1 ii libavutil56 7:4.2.2-1+b1 ii libboost-filesystem1.67.0 1.67.0-17 ii libboost-program-options1.67.0 1.67.0-17 ii libboost-system1.67.0 1.67.0-17 ii libbullet2.88 2.88+dfsg-2+b1 ii libc6 2.30-4 ii libgcc-s1 [libgcc1] 10-20200418-1 ii libgcc1 1:10-20200418-1 ii libgl1 1.3.1-1 ii libmyguiengine3debian1v53.2.2+dfsg-2+b2 ii libopenal1 1:1.19.1-1+b1 ii libopenscenegraph1603.6.4+dfsg1-3+b11 ii libopenthreads213.6.4+dfsg1-3+b11 ii libsdl2-2.0-0 2.0.10+dfsg1-3 ii libstdc++6 10-20200418-1 ii libswresample3 7:4.2.2-1+b1 ii libswscale5 7:4.2.2-1+b1 ii libtinyxml2.6.2v5 2.6.2-4 ii openmw-data 0.45.0-4 Versions of packages openmw recommends: ii openmw-launcher 0.45.0-4 openmw suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: openmw Source-Version: 0.46.0-1 Done: Bret Curtis We believe that the bug you reported is fixed in the latest version of openmw, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bret Curtis (supplier of updated openmw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 09 Jun 2020 08:15:09 +0200 Source: openmw Architecture: source Version: 0.46.0-1 Distribution: unstable Urgency: low Maintainer: Bret Curtis Changed-By: Bret Curtis Closes: 958917 961536 Changes: openmw (0.46.0-1) unstable; urgency=low . [ Bret Curtis ] * Upstream release: OpenMW-0.46.0 (Closes: #958917, #961536) * Adjusted dep to use opensceneraph-3.4 if found, otherwise use openscenegraph >= 3.6.5 because earlier versions are broken. Checksums-Sha1: e7d8700226775f6c691f04fb234e4a8d471aa166 2494 openmw_0.46.0-1.dsc f57a87e06c641963d38663df398f882bcacd14de 5155004 openmw_0.46.0.orig.tar.gz 04565bd904a7c8c76c380537c9a17ac15ab1ea97 7748 openmw_0.46.0-1.debian.tar.xz Checksums-Sha256: 73d86235a4693104d6bee7b1502e06506ba996b3c0be421dbb8a97f3bfb1ad21 2494 openmw_0.46.0-1.dsc 07a35a8f15f67f5aa7210c2a307a6db5660a9b61fe34983c35b172c8671afd58 5155004
Bug#961536: openmw FTBFS with openscenegraph 3.6.5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Sebastian, On 2020-06-11 at 09:11, sramac...@debian.org wrote: > Hi bret > > On 2020-06-09 18:28:02 +0200, bret curtis wrote: > > OpenMW 0.46 has been released and I've uploaded it here, it just > > someone kind and just to review and upload. :) > > > > https://salsa.debian.org/games-team/openmw > > > > Once uploaded and built, this bug should be closed. > > Thanks, uploaded with the alternative build dependencies on > openscenegraph reversed (patch attached). The buildds only consider the > first alternative and openscenegraph-3.4 is no longer in the archive. > > In d/rules, the dh_missing call should be placed in an override for > dh_missing. > > Cheers > -- > Sebastian Ramacher That's great news, and that's fine. Thanks! OSG 3.4 is only there for launchpad PPA reasons as one of our last releases against 3.4. Moving forward to 0.47 we'll target 3.6 exclusively and drop support for OSG 3.4 so I'll drop that eventually from control. I have a question about getting OpenMW out of 'contrib' and into 'main'. What exactly is holding us up? We have an example-suite (our own game for lack of a better name) that can be run with OpenMW, would it be better to package this along with OpenMW or package it up as something new and put a depend on OpenMW for it? Cheers, Bret -BEGIN PGP SIGNATURE- Version: FlowCrypt 7.7.9 Gmail Encryption Comment: Seamlessly send and receive encrypted email wsFcBAEBCAAGBQJe4fsPAAoJEMI3e31YTLkwwekP/3NrQPwXR1fkLeagh9tR /npsMGO7ZNFIYf6Ds12PGYn6ZKX5moxfeWYe7fVWqouRROMpvr7WzBGy7Fgd KBKtLQuJLnOqPSJdWmX5dhlhgejKgeiVTMsp3fIZifl4TOyfp1qhNDjG04TD ybR0q5vq2K7MM+/az4pkp0tr/RDewP3YOMJ5vJpFMZWt7woCWrz28mKV91R8 b8CARV1VvOgPv5QBnm6DGIDD2lGTN3L9tl3wPrqbl4ezm+9SfI4sc/hgJm9a pRaKwTTjQj50A/ab+UOX+hvdNwhxArPLsnlI2pxaEXqnsulaLVsekQuvgHnV zPVS4WXshlhmke7G37nsMVXHladc5jk4OICKfRvRXDloTUJTM4OYCSICAaeE ZDtpNc0PynSfIlXH5yjCVpBSOBfBudbFQmW71AvoS4QV2gWZ1u8pIdLZshuK o0CgWQ6iSSeX5djpyz+h7CdPwYTEaVsVqkFbkT3zpmsMYZmAwpUMwHzGcO2s vu5buDWPeSy6926WT7r4DFwZ3X9+QMrkqPFxYq/hhzgsjrPEQ2mer+j/7A3F DW1ngp11cMdsZ8pqwvSfrm3fcdnUNA7mpWLgiw4vqlizRT+gf40hrUqtKkQ2 fACKNwpN43ZZv5G+kBfnkegD5bVuGRz5kMYBd/+FSpppxTavMiM7MtgHXuce LKUA =1r1d -END PGP SIGNATURE- 0xC2377B7D584CB930.asc Description: application/pgp-keys
Bug#961536: marked as done (openmw FTBFS with openscenegraph 3.6.5)
Your message dated Thu, 11 Jun 2020 09:36:00 +
with message-id
and subject line Bug#961536: fixed in openmw 0.46.0-1
has caused the Debian Bug report #961536,
regarding openmw FTBFS with openscenegraph 3.6.5
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.)
--
961536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmw
Version: 0.45.0-4
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=openmw=sid
...
/<>/apps/openmw/mwrender/sky.cpp: In member function
‘osg::ref_ptr
MWRender::Sun::createOcclusionQueryNode(osg::Group*, bool)’:
/<>/apps/openmw/mwrender/sky.cpp:560:69: error: passing ‘const
osg::QueryGeometry’ as ‘this’ argument discards qualifiers [-fpermissive]
560 | oqn->getQueryGeometry()->setDataVariance(osg::Object::STATIC);
| ^
In file included from /usr/include/osg/Matrixd:17,
from /usr/include/osg/Matrix:18,
from /usr/include/osg/Array:43,
from /usr/include/osg/Uniform:23,
from /<>/apps/openmw/mwrender/sky.hpp:11,
from /<>/apps/openmw/mwrender/sky.cpp:1:
/usr/include/osg/Object:228:21: note: in call to ‘void
osg::Object::setDataVariance(osg::Object::DataVariance)’
228 | inline void setDataVariance(DataVariance dv) { _dataVariance =
dv; }
| ^~~
/<>/apps/openmw/mwrender/sky.cpp:565:57: error: invalid conversion
from ‘const osg::Geometry*’ to ‘osg::Geometry*’ [-fpermissive]
565 | osg::Geometry* queryGeom = oqn->getQueryGeometry();
|~^~
| |
| const
osg::Geometry*
make[3]: *** [apps/openmw/CMakeFiles/openmw.dir/build.make:115:
apps/openmw/CMakeFiles/openmw.dir/mwrender/sky.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: openmw
Source-Version: 0.46.0-1
Done: Bret Curtis
We believe that the bug you reported is fixed in the latest version of
openmw, 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.
Bret Curtis (supplier of updated openmw package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 09 Jun 2020 08:15:09 +0200
Source: openmw
Architecture: source
Version: 0.46.0-1
Distribution: unstable
Urgency: low
Maintainer: Bret Curtis
Changed-By: Bret Curtis
Closes: 958917 961536
Changes:
openmw (0.46.0-1) unstable; urgency=low
.
[ Bret Curtis ]
* Upstream release: OpenMW-0.46.0 (Closes: #958917, #961536)
* Adjusted dep to use opensceneraph-3.4 if found, otherwise use
openscenegraph >= 3.6.5 because earlier versions are broken.
Checksums-Sha1:
e7d8700226775f6c691f04fb234e4a8d471aa166 2494 openmw_0.46.0-1.dsc
f57a87e06c641963d38663df398f882bcacd14de 5155004 openmw_0.46.0.orig.tar.gz
04565bd904a7c8c76c380537c9a17ac15ab1ea97 7748 openmw_0.46.0-1.debian.tar.xz
Checksums-Sha256:
73d86235a4693104d6bee7b1502e06506ba996b3c0be421dbb8a97f3bfb1ad21 2494
openmw_0.46.0-1.dsc
07a35a8f15f67f5aa7210c2a307a6db5660a9b61fe34983c35b172c8671afd58 5155004
openmw_0.46.0.orig.tar.gz
17ecf0d80f383b7a24a6e8c89ab25b3066b727316f2f2de28f57cb748856f57d 7748
openmw_0.46.0-1.debian.tar.xz
Files:
ec4b87457291cca0a670a5bd593e769b 2494 contrib/games optional
openmw_0.46.0-1.dsc
3a85106cac2728fcc16a0f9b682afb6b 5155004 contrib/games optional
openmw_0.46.0.orig.tar.gz
b8e2174bce93e9a5487c4b0f504e58a7 7748 contrib/games optional
openmw_0.46.0-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl7h9SIACgkQafL8UW6n
GZMZZQ//UYckAakHZHmdUfkDKylLL8Bg4KltgEvFFq5ElfvZZGB2ulNOHOyhdnXB
ozK5yIPcZs9igP8fPtLUzxcheD2rjzXeouNFZ3OMh9/fPREv4e5dLI0P19KB9/1Q
5LHOQPv2GSfSkPZ3WTyo0aI2CmeojNeUnVBtq5aEghoYQpJ73OGgWwqWvS0MMaWG
llr/gnyWVjz6PVR0wGGgOQ1nt5mRf2GWDt2gsKXrh7Frr9IqPRvxL5waGlciPPsE
Bug#961536: openmw FTBFS with openscenegraph 3.6.5
Hi bret On 2020-06-09 18:28:02 +0200, bret curtis wrote: > OpenMW 0.46 has been released and I've uploaded it here, it just > someone kind and just to review and upload. :) > > https://salsa.debian.org/games-team/openmw > > Once uploaded and built, this bug should be closed. Thanks, uploaded with the alternative build dependencies on openscenegraph reversed (patch attached). The buildds only consider the first alternative and openscenegraph-3.4 is no longer in the archive. In d/rules, the dh_missing call should be placed in an override for dh_missing. Cheers -- Sebastian Ramacher From 9a355585dafc1af83c2f6e8ef16476ff7b172714 Mon Sep 17 00:00:00 2001 From: Sebastian Ramacher Date: Thu, 11 Jun 2020 10:46:57 +0200 Subject: [PATCH] Fix order of alternative dependencies --- debian/control | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/control b/debian/control index f437310..36861ba 100644 --- a/debian/control +++ b/debian/control @@ -7,7 +7,7 @@ Build-Depends: debhelper-compat (= 12), cmake (>= 3) | cmake3, libboost-filesystem-dev, libboost-iostreams-dev, libboost-program-options-dev, libboost-thread-dev, libopenal-dev, libtinyxml-dev, libavcodec-dev, libavformat-dev, libavutil-dev, libswscale-dev, libswresample-dev, libsdl2-dev (>= 2.0.9), - libmygui-dev (>= 3.2.1), libunshield-dev, libopenscenegraph-3.4-dev | libopenscenegraph-dev (>= 3.6.5), + libmygui-dev (>= 3.2.1), libunshield-dev, libopenscenegraph-dev (>= 3.6.5) | libopenscenegraph-3.4-dev, libqt5opengl5-dev, libqt5opengl5-desktop-dev [armel armhf] Standards-Version: 4.3.0 Homepage: http://openmw.org -- 2.27.0 signature.asc Description: PGP signature
Bug#962518: cegui-mk2 FTBFS on mipsel/mips64el: symbol differences
On Tue, Jun 09, 2020 at 03:21:37PM -0400, Olek Wojnar wrote: > Any advice on this? I really want to do what's "right" and what's best for > this package and the greater Debian infrastructure but I wonder if > insisting on shipping symbols files is actually doing more harm than good. > (e.g. I'm sure the buildds don't appreciate the extra load...) Do a "good enough" procedure, because it is best for Debian if you do not burn out due to symbols. My 2 cents: Stop shipping symbol files. Their troubles outweight by far the benefits* and they make (C++) stuff incredible fragile. Even with the kde symbol helpers it is still a mess. I've been burnt by them countless times… You never know whether a subsequent upload, binNMU or toolchain change will break your build again. * I'd rather hack on other bugs than on doing constantly symbol file massages… Just my 2 cents, of course… YMMV… > -Olek
Bug#962616: webkit2gtk: FTBFS on mipsel
On Wed, Jun 10, 2020 at 08:46:21PM +0200, Alberto Garcia wrote: > On Wed, Jun 10, 2020 at 08:08:27PM +0200, Sebastian Ramacher wrote: > > | Exception: gtkdoc-scangobj produced a non-zero return code 250 > > | Command: > > | gtkdoc-scangobj --module=webkit2gtk-4.0 > > | Error output: > > | > > | > > | ninja: build stopped: subcommand failed. > > I've seen this several times, and it seems to happen randomly, and > only on mipsel. I haven't been able to reproduce it in a buildd. > > I suspect it's a bug in gtk-doc-tools ? It fails on the Loongson buildds but succeeds on the others, and the problem started recently: https://buildd.debian.org/status/logs.php?pkg=webkit2gtk=mipsel debian-mips is Cc'ed. > Berto cu Adrian
Bug#960500: marked as done (openvdb: FTBFS with boost 1.71)
Your message dated Thu, 11 Jun 2020 09:10:58 +0100 with message-id and subject line re: openvdb: FTBFS with boost 1.71 has caused the Debian Bug report #960500, regarding openvdb: 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.) -- 960500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openvdb Version: 7.0.0-3 Severity: important User: team+bo...@tracker.debian.org Usertags: boost1.71 openvdb fails to build with boost 1.71 as default: | -- Found Python: /usr/bin/python3.8) (found suitable version "3.8.3", minimum required is "3.7") | -- Found NumPy: /usr/lib/python3/dist-packages/numpy/core/include (found suitable version "1.18.4", minimum required is "1.12.1") | -- Found boost_python38 | CMake Error at openvdb/python/CMakeLists.txt:209 (message): | Unable to find boost_numpy38, boost_numpy3 or boost_numpy. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- openvdb fails to build with boost 1.71 as default: | -- Found Python: /usr/bin/python3.8) (found suitable version "3.8.3", minimum required is "3.7") | -- Found NumPy: /usr/lib/python3/dist-packages/numpy/core/include (found suitable version "1.18.4", minimum required is "1.12.1") | -- Found boost_python38 | CMake Error at openvdb/python/CMakeLists.txt:209 (message): | Unable to find boost_numpy38, boost_numpy3 or boost_numpy. It seems that the actual rebuilds of the package in debian were successful, so presumably either this was some artifact of the test-rebuild environment or some issue in another package that has been fixed since. --- End Message ---
Bug#954148: doit: diff for NMU version 0.31.1-3.3
The Debian BTS does not automatically Cc anyone except the maintainer, I only saw this message by chance. On Fri, May 29, 2020 at 01:02:33PM +0200, Iñaki Malerba wrote: >... > Thanks for the upload, but that change is not going to pass autopkgtests > (as it needs the dependencies for the tests), so it won't migrate. I > think it should not close the issue. >... The dependencies are not needed for tests that aren't run: -Tests: version, unittests +Tests: version > - ina cu Adrian
Bug#960073: Re: Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)【请注意，邮件由mity...@gmail.com代发】
Hi! Sorry for my late reply. I tried to exporting QT_XCB_GL_INTEGRATION=xcb_egl and it still reported an error. libglvnd-dev package was originally installed. Do you need other information? Thank you in advance. BRs //Zongli
Bug#959157: bug still there
Hi, This bug is still there: DKMS make.log for wireguard-1.0.20200520 for kernel 4.19.0-8-amd64 (x86_64) Thu 11 Jun 2020 08:42:36 AM CEST make: Entering directory '/usr/src/linux-headers-4.19.0-8-amd64' CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/main.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/noise.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/device.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/peer.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/timers.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/queueing.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/send.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/receive.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/socket.o CC [M] /var/lib/dkms/wireguard/1.0.20200520/build/peerlookup.o /var/lib/dkms/wireguard/1.0.20200520/build/socket.c: In function ‘send6’: /var/lib/dkms/wireguard/1.0.20200520/build/socket.c:139:20: error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup_flow’; did you mean ‘ipv6_dst_lookup’? dst = ipv6_stub->ipv6_dst_lookup_flow(sock_net(sock), sock, , ^~~~ ipv6_dst_lookup make[3]: *** [/usr/src/linux-headers-4.19.0-8-common/scripts/Makefile.build:308: /var/lib/dkms/wireguard/1.0.20200520/build/socket.o] Error 1 make[3]: *** Waiting for unfinished jobs make[2]: *** [/usr/src/linux-headers-4.19.0-8-common/Makefile:1537: _module_/var/lib/dkms/wireguard/1.0.20200520/build] Error 2 make[1]: *** [Makefile:146: sub-make] Error 2 make: *** [Makefile:8: all] Error 2 make: Leaving directory '/usr/src/linux-headers-4.19.0-8-amd64' # cat /etc/debian_version 10.4 # uname -r 4.19.0-8-amd64 Packages: ii wireguard 1.0.20200513-1~bpo10+1 all fast, modern, secure kernel VPN tunnel (metapackage) iF wireguard-dkms1.0.20200520-1~bpo10+1 all fast, modern, secure kernel VPN tunnel (DKMS version) ii wireguard-tools 1.0.20200513-1~bpo10+1 amd64fast, modern, secure kernel VPN tunnel (userland utilities) This is IMHO a serious problem, even because in buster repositories there is *no* alternative, older version available, Thanks, Stefano -- Stefano David, PhD
Processed: severity of 962629 is serious
Processing commands for cont...@bugs.debian.org: > severity 962629 serious Bug #962629 [rainloop] rainloop: Rainloop stores passwords in cleartext in logfile Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868190: gatling: diff for NMU version 0.13-6.1
Control: tags 868190 + pending Dear maintainer, I've prepared an NMU for gatling (versioned as 0.13-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer or cancel my upload. Regards, Fabio diff -Nru gatling-0.13/debian/changelog gatling-0.13/debian/changelog --- gatling-0.13/debian/changelog 2016-01-16 13:13:21.0 -0200 +++ gatling-0.13/debian/changelog 2020-06-08 22:41:54.0 -0300 @@ -1,3 +1,12 @@ +gatling (0.13-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * debian/patches/11-silently-ignore-uid-as-username-fix.patch: fix when using + -u parameter with username rather then a numeric user id. Thanks to Thomas + Kremer . (Closes: #868190) + + -- Fabio Dos Santos Mendes Mon, 08 Jun 2020 22:41:54 -0300 + gatling (0.13-6) unstable; urgency=medium * Added 10-mbedtls.patch to switch from polarssl to mbedtls, Sent from [ProtonMail](https://protonmail.ch), encrypted email based in Switzerland.
Bug#962253: marked as done (esys-particle: Broken section number in manpage)
Your message dated Thu, 11 Jun 2020 06:18:44 + with message-id and subject line Bug#962253: fixed in esys-particle 2.3.5+dfsg2-1 has caused the Debian Bug report #962253, regarding esys-particle: Broken section number in manpage 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.) -- 962253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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) ... --- End Message --- --- Begin Message --- Source: esys-particle Source-Version: 2.3.5+dfsg2-1 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of esys-particle, 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. Anton Gladky (supplier of updated esys-particle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jun 2020 22:57:41 +0200 Source: esys-particle Architecture: source Version: 2.3.5+dfsg2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Closes: 962253 Changes: esys-particle (2.3.5+dfsg2-1) unstable; urgency=medium . [ Adrian Bunk ] * [a2a3461] Fix the manpage section number. (Closes: #962253) . [ Anton Gladky ] * [79195f3] Set upstream metadata fields: Repository, Repository-Browse. * [bd11b4b] Drop unnecessary dependency on dh-autoreconf. * [9be1eac] Drop unnecessary dh arguments: --parallel * [994720f] Update standards version to 4.5.0, no changes needed. * [758e80e] Minor patch update * [2bf0c70] Add .gitlab-ci.yml * [08bdd6a] New upstream version 2.3.5+dfsg2 Checksums-Sha1: 38ff97351aaa0963f786835b13ac5f4e4d431919 2348 esys-particle_2.3.5+dfsg2-1.dsc f3070e5a3f6c01dc26a5e435a6422ed12fab6303 3790140 esys-particle_2.3.5+dfsg2.orig.tar.xz b913af0a9969ee130d402871cd41bddba47b3c13 565960 esys-particle_2.3.5+dfsg2-1.debian.tar.xz 636d23db236073fd363ca1919ed82f0d773a2819 18943 esys-particle_2.3.5+dfsg2-1_source.buildinfo Checksums-Sha256: 769fca8f525eb0621addc2fc0525db3849412b748e43b6c1b10e8983f6fc053b 2348 esys-particle_2.3.5+dfsg2-1.dsc ea2746adc860ee7febd410c5eaf97052ee8fbfd2577ed0eaa1ab2c45c297e585 3790140 esys-particle_2.3.5+dfsg2.orig.tar.xz 561d6b7cdc896f8c867f52f0b8bbbfe9094c2a51e92d09bdddf604008d277136 565960 esys-particle_2.3.5+dfsg2-1.debian.tar.xz ea45f5a515334fc25efbb5b5e0530a9fb79eb0ce33da5abfa60879c36bb5b9a5 18943 esys-particle_2.3.5+dfsg2-1_source.buildinfo Files: 70346d254823cf3f66366b4dc9ec161f 2348 science optional esys-particle_2.3.5+dfsg2-1.dsc 0f405f201b9780647994dc3cdf6f 3790140 science optional esys-particle_2.3.5+dfsg2.orig.tar.xz 3bf307ec17e139b07dcf6f1d941d9797 565960 science optional esys-particle_2.3.5+dfsg2-1.debian.tar.xz e623daa0a9eaffaf7daf203655caadd3 18943 science optional esys-particle_2.3.5+dfsg2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl7hyDEACgkQ0+Fzg8+n /wajUg/+OQmg4Vj9wKcqOU5vukzy/7f02WMCmzBMT5YWJg3Z7kFTD2SwslxqOlCc oWO/hyxfx8TcNDeTe/4a2ZjgThqpAd8nMiUTqtSUJ2SaRRpM2tFJ+3muuP1M3quF lWJadG6FnDdZBwI4QRHNHVD8QHRT/WjGJn97i7PzL4rmTv33OUi5pr1D7iVjNN3s TDnrba85CB3E2glLTeBrUjYp7sDUO1MrbJL+B8zaE7CW+eqWDqJot3iWCSk6ylWo DhB65O34zcEf5sifVGaAZdEf5FzlWN402GhFl9/54TYUuxbKRQ5p3ADjbEzf12iN
Bug#962643: cunit: broken NMU does FTBFS
On Thu, Jun 11, 2020 at 08:46:23AM +0300, Adrian Bunk wrote: >... > The diffstat of this NMU is > 510 files changed, 139791 insertions(+), 3 deletions(-) > > It is the responsibility of the sponsor (Cc'ed) to verify that > sponsored uploads are not broken: > https://wiki.debian.org/DebianMentorsFaq#What_is_the_process_for_sponsoring_a_package.3F I have to take that back, it is actually likely that this went wrong on the sponsor side due to verifying the package: The debdiff in #960715 looks OK. Building a source package for upload after having done a testbuild can cause this kind of problems, when the source tree is not clean many unwanted changes might end up in the new source package. cu Adrian
Bug#962158: lintian: New very problematic --fail-on default value
Felix Lechner wrote: > It would also give me more time to understand the possibly > unreasonable burden on Lintian users across Debian and the derivative > ecosystem. Simon may receive feedback from Ubuntu, a significant > derivative. If there are real problems, I am happy to discuss a > solution that reverts the default to Lintian's old setting. Without rehashing the details here, if Ubuntu's CI would prefer a different exit code, it would seem more sensible to keep the default the same and ask Ubuntu to specify a different --fail-on=. That would appear to limit require one change (and potential "fallout") to one place, and indeed in a place that has the ability to be changed. > Now the best course of action, I think, is to downgrade the severity > again to Guillem's original setting of 'important'. That will allow > the change to remain in testing. It is, after all, what the testing > distribution is for. Ah, yeah, I had forgotten about autoremovals. Sigh. > At the same time, the change was widely released two weeks ago. Simon > Quigley from Ubuntu announced it on debian-devel on May 25 [1], while > I advertised the change repeatedly on IRC and added a note to DevNews. Just as an aside, it feels like a slight stretch to assume that every Lintian user reads debian-devel, lurks on IRC or can be expected to come across this in another way. In the event that this default change stays, using the NEWS mechanism might be appropriate to explain concisely and exactly what a user may need to change (eg. "if you were relying on X, you should do Y".) We should also consider bumping the major version number of Lintian itself if we are strictly following the semver.org versioning scheme. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#962645: qbittorrent-nox: Qbittorrent-nox is barely usable after the upgrade to 4.2.4-1+b1
Package: qbittorrent-nox Version: 4.2.4-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, Qbittorrent-nox has become unusable on both amd64 and i386 since the last binary update (4.2.4-1 to 4.2.4-1+b1) which was 7 days ago. It worked as it should before that update, on both systems. On my amd64 system (testing + unstable with xorg). I add a torrent, it shows up on the list, it downloads as it should and when the download is complete, it crashes with this output https://paste.debian.net/1151529/ Exiting it with ctrl+c pops up this https://paste.debian.net/1151532/ On the i386 system (unstable without xorg), things are a bit different. Once it is started, this line comes up again and again until I exit it with ctrl+c Caught exception in void BitTorrent::Session::handleAlert(const libtorrent::alert*) : "std::bad_alloc" And once it exits, this comes up https://paste.debian.net/1151531/ -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qbittorrent-nox depends on: ii libc6 2.30-8 ii libgcc-s1 10.1.0-3 ii libqt5core5a5.12.5+dfsg-10+b1 ii libqt5network5 5.12.5+dfsg-10+b1 ii libqt5xml5 5.12.5+dfsg-10+b1 ii libssl1.1 1.1.1g-1 ii libstdc++6 10.1.0-3 ii libtorrent-rasterbar10 1.2.5-1+b1 ii zlib1g 1:1.2.11.dfsg-2 qbittorrent-nox recommends no packages. Versions of packages qbittorrent-nox suggests: pn qbittorrent-dbg -- no debconf information
