Processed: Re: Bug#967084: golang-1.14: FTBFS with gcc-10 on arm64
Processing control commands: > forwarded -1 https://github.com/golang/go/issues/39466 Bug #967084 [golang-1.14] golang-1.14: FTBFS with gcc-10 on arm64 Set Bug forwarded-to-address to 'https://github.com/golang/go/issues/39466'. > clone -1 -2 Bug #967084 [golang-1.14] golang-1.14: FTBFS with gcc-10 on arm64 Bug 967084 cloned as bug 967085 > reassign -2 src:golang-1.15 1.15~rc1-1 Bug #967085 [golang-1.14] golang-1.14: FTBFS with gcc-10 on arm64 Bug reassigned from package 'golang-1.14' to 'src:golang-1.15'. No longer marked as found in versions golang-1.14/1.14.6-1. Ignoring request to alter fixed versions of bug #967085 to the same values previously set Bug #967085 [src:golang-1.15] golang-1.14: FTBFS with gcc-10 on arm64 Marked as found in versions golang-1.15/1.15~rc1-1. > retitle -2 golang-1.15: FTBFS with gcc-10 on arm64 Bug #967085 [src:golang-1.15] golang-1.14: FTBFS with gcc-10 on arm64 Changed Bug title to 'golang-1.15: FTBFS with gcc-10 on arm64' from 'golang-1.14: FTBFS with gcc-10 on arm64'. -- 967084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967084 967085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967084: golang-1.14: FTBFS with gcc-10 on arm64
Control: forwarded -1 https://github.com/golang/go/issues/39466 Control: clone -1 -2 Control: reassign -2 src:golang-1.15 1.15~rc1-1 Control: retitle -2 golang-1.15: FTBFS with gcc-10 on arm64 clone again.. -- Shengjing Zhu
Bug#967084: golang-1.14: FTBFS with gcc-10 on arm64
Package: golang-1.14 Version: 1.14.6-1 Severity: serious Justification: ftbfs Control: forwarded -1 https://github.com/golang/go/issues/39466 Control: clone -1 -2 Control: reassign -2 src:golang-1.15 1.15~rc1-1 Control: retitle -2 golang-1.15: FTBFS with gcc-10 on arm64 # misc/cgo/test.test libgcc(.text): unknown symbol __aarch64_have_lse_atomics FAILmisc/cgo/test [build failed] 2020/08/03 19:38:58 Failed: exit status 2 https://buildd.debian.org/status/fetch.php?pkg=golang-1.14=arm64=1.14.6-1=1596483860=0
Processed: tagging 967039
Processing commands for cont...@bugs.debian.org: > tags 967039 + pending Bug #967039 [src:spamassassin] spamassassin: Unversioned Python removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 967039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957977: xfce4-sensors-plugin: ftbfs with GCC-10
control: tags -1 fixed-upstream Hi, It seems that it was already fixed in upstream: Here is the commit: https://gitlab.xfce.org/panel-plugins/xfce4-sensors-plugin/-/commit/108ffac9eac23a5d87f142e36d162d62be0619e2
Processed: Re: xfce4-sensors-plugin: ftbfs with GCC-10
Processing control commands: > tags -1 fixed-upstream Bug #957977 [src:xfce4-sensors-plugin] xfce4-sensors-plugin: ftbfs with GCC-10 Added tag(s) fixed-upstream. -- 957977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957261: marked as done (gdome2: ftbfs with GCC-10)
Your message dated Tue, 04 Aug 2020 03:48:24 + with message-id and subject line Bug#957261: fixed in gdome2 0.8.1+debian-7 has caused the Debian Bug report #957261, regarding gdome2: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gdome2 Version: 0.8.1+debian-6 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/gdome2_0.8.1+debian-6_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] make[4]: Entering directory '/<>/libgdome' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdome -I../libgdome/gdomecore -I../libgdome/events -I../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT gdome.lo -MD -MP -MF .deps/gdome.Tpo -c -o gdome.lo gdome.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdome -I../libgdome/gdomecore -I../libgdome/events -I../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT gdome.lo -MD -MP -MF .deps/gdome.Tpo -c gdome.c -fPIC -DPIC -o .libs/gdome.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdome -I../libgdome/gdomecore -I../libgdome/events -I../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT gdome.lo -MD -MP -MF .deps/gdome.Tpo -c gdome.c -o gdome.o >/dev/null 2>&1 mv -f .deps/gdome.Tpo .deps/gdome.Plo /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdome -I../libgdome/gdomecore -I../libgdome/events -I../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT gdome-events.lo -MD -MP -MF .deps/gdome-events.Tpo -c -o gdome-events.lo gdome-events.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdome -I../libgdome/gdomecore -I../libgdome/events -I../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT gdome-events.lo -MD -MP -MF .deps/gdome-events.Tpo -c gdome-events.c -fPIC -DPIC -o .libs/gdome-events.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdome -I../libgdome/gdomecore -I../libgdome/events -I../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT gdome-events.lo -MD -MP -MF .deps/gdome-events.Tpo -c gdome-events.c -o gdome-events.o >/dev/null 2>&1 mv -f .deps/gdome-events.Tpo .deps/gdome-events.Plo /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdome -I../libgdome/gdomecore -I../libgdome/events -I../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT gdome-xpath.lo -MD -MP -MF .deps/gdome-xpath.Tpo -c -o gdome-xpath.lo gdome-xpath.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdome -I../libgdome/gdomecore -I../libgdome/events -I../libgdome/xpath -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -ansi -g -O2 -MT gdome-xpath.lo -MD -MP -MF .deps/gdome-xpath.Tpo -c gdome-xpath.c -fPIC -DPIC -o .libs/gdome-xpath.o
Bug#966958: marked as done (lacme: FTBFS: The extension smart is not supported for man)
Your message dated Tue, 04 Aug 2020 00:33:31 + with message-id and subject line Bug#966958: fixed in lacme 0.6.1-1 has caused the Debian Bug report #966958, regarding lacme: FTBFS: The extension smart is not supported for man 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.) -- 966958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lacme Version: 0.6-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm -vf lacme-accountd.1 lacme.1 > make[1]: Leaving directory '/<>' >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building lacme using existing ./lacme_0.6.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building lacme in lacme_0.6-3.debian.tar.xz > dpkg-source: info: building lacme in lacme_0.6-3.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure >dh_auto_build > make -j4 "INSTALL=install --strip-program=true" > make[1]: Entering directory '/<>' > The extension smart is not supported for man > The extension smart is not supported for man > make[1]: *** [Makefile:7: lacme-accountd.1] Error 23 The full build log is available from: http://qa-logs.debian.net/2020/08/02/lacme_0.6-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: lacme Source-Version: 0.6.1-1 Done: Guilhem Moulin We believe that the bug you reported is fixed in the latest version of lacme, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin (supplier of updated lacme 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, 04 Aug 2020 01:43:05 +0200 Source: lacme Architecture: source Version: 0.6.1-1 Distribution: unstable Urgency: medium Maintainer: Guilhem Moulin Changed-By: Guilhem Moulin Closes: 955767 966958 Changes: lacme (0.6.1-1) unstable; urgency=medium . * New upstream release. Closes: #955767, #966958. + Default listening socket for the webserver component is now /run/lacme-www.socket. (It was previously under the legacy directory /var/run.) * debian/*: Adapt to new build system. * debian/control: Bump debhelper compatibility level to 13. Checksums-Sha1: 9fb46b5bb8b439765d6a139f8d4e37012729427a 1852 lacme_0.6.1-1.dsc a8cd9e76d4ad254f62b7b7fcedac15b0f8f5876a 46617 lacme_0.6.1.orig.tar.gz 69675ec2501194b5f61400ad414a597d03ae5fe1 3712 lacme_0.6.1-1.debian.tar.xz 58aaabf7af1ee1b41af82464cea33a1dfd94f8a9 5607 lacme_0.6.1-1_amd64.buildinfo Checksums-Sha256: d9b3a4ed841eb640dfbce42f5435aaa87f344d84ec9d683b59ce89a9cefffd3f 1852 lacme_0.6.1-1.dsc 4db22a3dd5551e87972cd09acbf86060a171ce80ceba2bcd0af4b77648c1e150 46617 lacme_0.6.1.orig.tar.gz fa1292f856217512ec9b285cca69f3ca3efa4055fa9d73a6728a8ad053fe 3712 lacme_0.6.1-1.debian.tar.xz b5bdb1af1e60537f57e17f13a95ffccb0a07b021c9abe7cc89fdb023a326b590 5607 lacme_0.6.1-1_amd64.buildinfo Files: b5084bbf340373635f15e354dd635a27 1852 utils optional lacme_0.6.1-1.dsc 1f8c5614d5c07f693e0d1f28fd5093de 46617 utils optional lacme_0.6.1.orig.tar.gz 03799edf03082eb119f96ef453c1ba3c 3712 utils optional lacme_0.6.1-1.debian.tar.xz 3dc8b451864b90edcd264dc26e271ca4 5607 utils optional lacme_0.6.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAl8ooSQACgkQ05pJnDwh
Processed: Re: Bug#967039: marked as done (spamassassin: Unversioned Python removal in sid/bullseye)
Processing control commands:
> reopen -1
Bug #967039 {Done: Noah Meyerhans } [src:spamassassin]
spamassassin: Unversioned Python removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions spamassassin/3.4.5~pre1-2 and
spamassassin/4.0.0~0.0svn1879217-2.
--
967039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#967039: marked as done (spamassassin: Unversioned Python removal in sid/bullseye)
Control: reopen -1 This isn't actually resolved. The usage of python is still unversioned (that is, the tests invoke /usr/bin/python, rather than python3, which still fails). The tests really have no need at all to use python. Since spamassassassin is a perl project, it'd be reasonable to reimplement them in that; OTOH, since the tests are quite simple, it'd be reasonable to reimplement them in bash. Either way, the unversioned python issue is still present. I'll work on a more complete fix.
Bug#967039: marked as done (spamassassin: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 03 Aug 2020 23:19:11 + with message-id and subject line Bug#967039: fixed in spamassassin 4.0.0~0.0svn1879217-2 has caused the Debian Bug report #967039, regarding spamassassin: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spamassassin Version: 3.4.5~pre1-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned see https://ci.debian.net/data/autopkgtest/testing/amd64/s/spamassassin/6517590/log.gz Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: spamassassin Source-Version: 4.0.0~0.0svn1879217-2 Done: Noah Meyerhans We believe that the bug you reported is fixed in the latest version of spamassassin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated spamassassin 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, 03 Aug 2020 15:58:43 -0700 Source: spamassassin Architecture: source Version: 4.0.0~0.0svn1879217-2 Distribution: experimental Urgency: medium Maintainer: Noah Meyerhans Changed-By: Noah Meyerhans Closes: 967039 Changes: spamassassin (4.0.0~0.0svn1879217-2) experimental; urgency=medium . * Update python dependencies to support the python2 removal effort (Closes: #967039) Checksums-Sha1: dbc5d17eb39ea992f9f356a269cf0b84d50c1c23 2308 spamassassin_4.0.0~0.0svn1879217-2.dsc 615401cb1fe98ce645670978591af7ea707f6613 44192 spamassassin_4.0.0~0.0svn1879217-2.debian.tar.xz b621ce44df0b12953c57ade7c10d8896c3ceb1d3 5749 spamassassin_4.0.0~0.0svn1879217-2_source.buildinfo Checksums-Sha256: 662bcb5f670873f05f74a028d28ac4353d58a3ec6cff7254778c7ed39ef91cf2 2308 spamassassin_4.0.0~0.0svn1879217-2.dsc 0b500f9b85af9d02894ef970c42e70e23b1e654de0f4f8cc624b136e8b12b8b5 44192 spamassassin_4.0.0~0.0svn1879217-2.debian.tar.xz aecd7161cd479659e2d018a4d5575900ad17a3762ea8a5ce7bff5dbbfd326a1b 5749 spamassassin_4.0.0~0.0svn1879217-2_source.buildinfo Files: 0d07db27335aa08dda36220901d787ea 2308 mail optional spamassassin_4.0.0~0.0svn1879217-2.dsc a55b038201c16b268de70f4f57268e7b 44192 mail optional spamassassin_4.0.0~0.0svn1879217-2.debian.tar.xz d06d4d8fd829d985a20ee81b59bba79c 5749 mail optional spamassassin_4.0.0~0.0svn1879217-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE65xaF5r2LDCTz+zyV68+Bn2yWDMFAl8omgsRHG5vYWhtQGRl Ymlhbi5vcmcACgkQV68+Bn2yWDPGBA//dZc6fFve2Xd2QZeSihw7E0AMuYuN1Pk/ UyKfo6l/Srg+Jv7EOQLk4/vs+cgL09p4uPhNydzinNtz5ya4Bn9OGmH4xPgDwZ2s G+MJ3V/3/gL/KNo6eQ9+JAoo+4YECfD5VsxYTG43G7rplbiqPmSZyXlxghdInSAg F97BcpCj3oSNke/pmuWQrz/7mIEegFHa48+j3QPM6nmU7xvFRiNge7rr3ZconvA3 wAl154WjQPodzzMqiq6jNKG44i8HzSdAGQ02QlAM3hqKkRltG6Teb96BstUAm9Qd Jk33AWCgoC7kCPig5Dfx9prZ0b/WyZgF/8Kr9tcAwbiL1Yovpk39lVLjbT22fFsO r+0PinZ+tbvGHDJqBja5yjNtuKcKhWZgxYscP+Zj9c2rtLnPAp6N+s0oT02jKBGn jquHt3F3ddp5XIwS9jePvOLdT7oLzkuz1kUCY8ae2AXpNFU+5YZyp39sUrWBXIcX
Bug#967039: marked as done (spamassassin: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 03 Aug 2020 22:49:13 + with message-id and subject line Bug#967039: fixed in spamassassin 3.4.5~pre1-2 has caused the Debian Bug report #967039, regarding spamassassin: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spamassassin Version: 3.4.5~pre1-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned see https://ci.debian.net/data/autopkgtest/testing/amd64/s/spamassassin/6517590/log.gz Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: spamassassin Source-Version: 3.4.5~pre1-2 Done: Noah Meyerhans We believe that the bug you reported is fixed in the latest version of spamassassin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Noah Meyerhans (supplier of updated spamassassin 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, 03 Aug 2020 15:44:52 -0700 Source: spamassassin Architecture: source Version: 3.4.5~pre1-2 Distribution: unstable Urgency: medium Maintainer: Noah Meyerhans Changed-By: Noah Meyerhans Closes: 967039 Changes: spamassassin (3.4.5~pre1-2) unstable; urgency=medium . * Update python dependencies to support the python2 removal effort (Closes: #967039) * Import a number of bug fixes from upstream's 3.4 branch that haven't yet made it into a pre-release snapshot Checksums-Sha1: 4bbbac9d4f6d122bcc7d33df0025b1079d47cc3e 2248 spamassassin_3.4.5~pre1-2.dsc ae2829dee33e15c6a95457bb1eb42642bad2673f 45996 spamassassin_3.4.5~pre1-2.debian.tar.xz b753910f5ab5004808c174411c20f330f49f99fd 5713 spamassassin_3.4.5~pre1-2_source.buildinfo Checksums-Sha256: 464148cb0eec2c82283cef2481b5edaa9b53cf79da4ed0ce64ba96c0e39c9236 2248 spamassassin_3.4.5~pre1-2.dsc 05788cdea243a8425e83d2e82f4c34fcc1902aa4f15f334f724d424106e53a66 45996 spamassassin_3.4.5~pre1-2.debian.tar.xz 7cdd5860cb8e13e4168df32816f4b8a0d94bb71afada08f5dee765c199ab31e8 5713 spamassassin_3.4.5~pre1-2_source.buildinfo Files: 31c67f4a47a7d6d4b477abdc433c3149 2248 mail optional spamassassin_3.4.5~pre1-2.dsc df5d4a8c876eb5a614ffdb0ab5d228d3 45996 mail optional spamassassin_3.4.5~pre1-2.debian.tar.xz c4caeacd8772e84aefd6e5c4338a0038 5713 mail optional spamassassin_3.4.5~pre1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE65xaF5r2LDCTz+zyV68+Bn2yWDMFAl8ok9QRHG5vYWhtQGRl Ymlhbi5vcmcACgkQV68+Bn2yWDOp/Q/9FZO/uuHDerfctrxfQD4+DMnEa+CKVnRt 61xTtRa42VdYOr88pKYtX0yCDEXSeU8l2jlqDHAPt6g5s71e09oVst0Cos1trKdB llZhnCrPFBk8A2G3PQ0/1+jZfP3GBZgMy151Ea97t7J5xXFenemS6ADbVcNaTPZg bhbqJicN1drlB5qJMfUmA6PZkCCb7KgqzJUWaHQf/H9g0hieivaYzvK2LMuVkt5J tS7sZrYJ6gaSUDf8VVQJLgarfBDb1n1duN9Z2YStuyLV0FRRG9ZWO+Vu2KxunVGQ kb4Cu6zo4GzPKbFrx1aBl5PyYUKrn3h/0Y40z5F2u8ui/crfXn8QJJ12QOESgz6t REPh8+98ocYNpb0c2BcI1eH/73VAeqXm4jhw2+XzE6C4DXhuqPPRff8MMeMOKG4R 1MiXp+J688UylM/JVfmDNodS5wIONykkVq29JBoR/Yd6ar0jxCI0Hp9ENIk2id7c IOduMCbJV2MZOFF8JGYK0es+ZCrBqED1edVYJZUaLwQ4athkjdG7r+e2Hp7ZsDpM
Bug#967078: scilab,scilab-cli: both ship /usr/share/applications/scilab-cli.desktop etc.
Followup-For: Bug #967078 Actualy there are more files in both packages: usr/share/applications/scilab-cli.desktop usr/share/icons/hicolor/16x16/apps/scilab.png usr/share/icons/hicolor/16x16/apps/scinotes.png usr/share/icons/hicolor/16x16/apps/xcos.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-bin.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-cos.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-cosf.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-dem.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-graph.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-sav.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-sce.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-sci.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-sod.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-tst.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-xcos.png usr/share/icons/hicolor/16x16/mimetypes/application-x-scilab-zcos.png usr/share/icons/hicolor/24x24/apps/scilab.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-bin.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-cos.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-cosf.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-dem.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-graph.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-sav.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-sce.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-sci.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-sod.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-tst.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-xcos.png usr/share/icons/hicolor/24x24/mimetypes/application-x-scilab-zcos.png usr/share/icons/hicolor/256x256/apps/puffin.png usr/share/icons/hicolor/256x256/apps/scilab.png usr/share/icons/hicolor/256x256/apps/scinotes.png usr/share/icons/hicolor/256x256/apps/xcos.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-bin.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-cos.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-cosf.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-dem.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-graph.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-sav.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-sce.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-sci.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-sod.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-tst.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-xcos.png usr/share/icons/hicolor/256x256/mimetypes/application-x-scilab-zcos.png usr/share/icons/hicolor/32x32/apps/scilab.png usr/share/icons/hicolor/32x32/apps/scinotes.png usr/share/icons/hicolor/32x32/apps/xcos.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-bin.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-cos.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-cosf.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-dem.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-graph.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-sav.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-sce.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-sci.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-sod.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-tst.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-xcos.png usr/share/icons/hicolor/32x32/mimetypes/application-x-scilab-zcos.png usr/share/icons/hicolor/48x48/apps/scilab.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-bin.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-cos.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-cosf.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-dem.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-graph.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-sav.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-sce.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-sci.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-sod.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-tst.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-xcos.png usr/share/icons/hicolor/48x48/mimetypes/application-x-scilab-zcos.png usr/share/mime/packages/scilab.xml Andreas
Bug#967078: scilab,scilab-cli: both ship /usr/share/applications/scilab-cli.desktop
Package: scilab,scilab-cli Version: 6.1.0+dfsg1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package scilab. Preparing to unpack .../238-scilab_6.1.0+dfsg1-5_all.deb ... Unpacking scilab (6.1.0+dfsg1-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-yQvaJu/238-scilab_6.1.0+dfsg1-5_all.deb (--unpack): trying to overwrite '/usr/share/applications/scilab-cli.desktop', which is also in package scilab-cli 6.1.0+dfsg1-5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-yQvaJu/238-scilab_6.1.0+dfsg1-5_all.deb cheers, Andreas scilab=6.1.0+dfsg1-5_scilab-cli=6.1.0+dfsg1-5.log.gz Description: application/gzip
Bug#966823: python2-doc: trying to overwrite '/usr/share/doc/python2/README.Debian', which is also in package python2 2.7.17-2
Followup-For: Bug #966823 Hi, actually both python2 and python2-doc (both version 2.7.18-1) ship /usr/share/doc/python2/README.Debian Andreas
Bug#966965: dune-grid-glue: FTBFS: terminate called after throwing an instance of 'Dune::Exception'
Control: tag -1 + upstream Lucas Nussbaum writes: > Source: dune-grid-glue > Version: 2.7.0-2 >> what(): Dune::Exception >> [eh:/<>/dune/grid-glue/test/ringcommtest.cc:24]: MPI ERROR -- >> MPI_ERR_TAG: invalid tag >> what(): Dune::Exception >> [eh:/<>/dune/grid-glue/test/ringcommtest.cc:24]: MPI ERROR -- >> MPI_ERR_TAG: invalid tag The is probably caused by `int tag = 12345678;` in the code while OpenMPI might have a lower limit, see [1]. [1]: https://github.com/open-mpi/ompi/issues/6940 Ansgar
Bug#966874: marked as done (wims: FTBFS: ld: match.o:./wims/src/Misc/symtext/symtext.h:105: multiple definition of `nextpool'; compile.o:./wims/src/Misc/symtext/symtext.h:105: first defined here)
Your message dated Mon, 03 Aug 2020 21:49:03 + with message-id and subject line Bug#966874: fixed in wims 1:4.17b+svn13454~dfsg1-4 has caused the Debian Bug report #966874, regarding wims: FTBFS: ld: match.o:./wims/src/Misc/symtext/symtext.h:105: multiple definition of `nextpool'; compile.o:./wims/src/Misc/symtext/symtext.h:105: first defined here 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.) -- 966874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wims Version: 1:4.17b+svn13454~dfsg1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 > -Wl,-z,relro compile.o match.o suffix.o translate.o symtext.o -L../../../lib > -lwims -lm -o symtext > /usr/bin/ld: match.o:./wims/src/Misc/symtext/symtext.h:105: multiple > definition of `nextpool'; compile.o:./wims/src/Misc/symtext/symtext.h:105: > first defined here > /usr/bin/ld: match.o:./wims/src/Misc/symtext/symtext.h:105: multiple > definition of `nexttag'; compile.o:./wims/src/Misc/symtext/symtext.h:105: > first defined here > /usr/bin/ld: match.o:./wims/src/Misc/symtext/symtext.h:96: multiple > definition of `diccnt'; compile.o:./wims/src/Misc/symtext/symtext.h:96: first > defined here > /usr/bin/ld: match.o:./wims/src/Misc/symtext/symtext.h:95: multiple > definition of `macrodic'; compile.o:./wims/src/Misc/symtext/symtext.h:95: > first defined here > /usr/bin/ld: match.o:./wims/src/Misc/symtext/symtext.h:95: multiple > definition of `transdic'; compile.o:./wims/src/Misc/symtext/symtext.h:95: > first defined here > /usr/bin/ld: suffix.o:./wims/src/Misc/symtext/symtext.h:105: multiple > definition of `nexttag'; compile.o:./wims/src/Misc/symtext/symtext.h:105: > first defined here > /usr/bin/ld: suffix.o:./wims/src/Misc/symtext/symtext.h:105: multiple > definition of `nextpool'; compile.o:./wims/src/Misc/symtext/symtext.h:105: > first defined here > /usr/bin/ld: suffix.o:./wims/src/Misc/symtext/symtext.h:96: multiple > definition of `diccnt'; compile.o:./wims/src/Misc/symtext/symtext.h:96: first > defined here > /usr/bin/ld: suffix.o:./wims/src/Misc/symtext/symtext.h:95: multiple > definition of `macrodic'; compile.o:./wims/src/Misc/symtext/symtext.h:95: > first defined here > /usr/bin/ld: suffix.o:./wims/src/Misc/symtext/symtext.h:95: multiple > definition of `transdic'; compile.o:./wims/src/Misc/symtext/symtext.h:95: > first defined here > /usr/bin/ld: translate.o:./wims/src/Misc/symtext/symtext.h:96: multiple > definition of `diccnt'; compile.o:./wims/src/Misc/symtext/symtext.h:96: first > defined here > /usr/bin/ld: translate.o:./wims/src/Misc/symtext/symtext.h:105: multiple > definition of `nexttag'; compile.o:./wims/src/Misc/symtext/symtext.h:105: > first defined here > /usr/bin/ld: translate.o:./wims/src/Misc/symtext/symtext.h:105: multiple > definition of `nextpool'; compile.o:./wims/src/Misc/symtext/symtext.h:105: > first defined here > /usr/bin/ld: translate.o:./wims/src/Misc/symtext/symtext.h:95: multiple > definition of `macrodic'; compile.o:./wims/src/Misc/symtext/symtext.h:95: > first defined here > /usr/bin/ld: translate.o:./wims/src/Misc/symtext/symtext.h:95: multiple > definition of `transdic'; compile.o:./wims/src/Misc/symtext/symtext.h:95: > first defined here > /usr/bin/ld: symtext.o:./wims/src/Misc/symtext/symtext.h:96: multiple > definition of `diccnt'; compile.o:./wims/src/Misc/symtext/symtext.h:96: first > defined here > /usr/bin/ld: symtext.o:./wims/src/Misc/symtext/symtext.h:95: multiple > definition of `transdic'; compile.o:./wims/src/Misc/symtext/symtext.h:95: > first defined here > /usr/bin/ld: symtext.o:./wims/src/Misc/symtext/symtext.h:95: multiple > definition of `macrodic'; compile.o:./wims/src/Misc/symtext/symtext.h:95: > first defined here > /usr/bin/ld: symtext.o:./wims/src/Misc/symtext/symtext.h:105: multiple > definition of `nexttag'; compile.o:./wims/src/Misc/symtext/symtext.h:105: > first defined here > /usr/bin/ld: symtext.o:./wims/src/Misc/symtext/symtext.h:105: multiple > definition of `nextpool'; compile.o:./wims/src/Misc/symtext/symtext.h:105: > first defined here > collect2: error: ld returned 1 exit status The full build log is available from:
Processed: Re: Bug#966965: dune-grid-glue: FTBFS: terminate called after throwing an instance of 'Dune::Exception'
Processing control commands: > tag -1 + upstream Bug #966965 [src:dune-grid-glue] dune-grid-glue: FTBFS: terminate called after throwing an instance of 'Dune::Exception' Added tag(s) upstream. -- 966965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967036: marked as pending in pycparser
Control: tag -1 pending Hello, Bug #967036 in pycparser reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/pycparser/-/commit/2912906cf0358f0ea8a7365d5010ac354c20593b Depend on the python2 binary package for the 2.7 interpreter. (Closes: #967036) (this message was generated automatically) -- Greetings https://bugs.debian.org/967036
Processed: tagging 967039
Processing commands for cont...@bugs.debian.org: > tags 967039 + pending Bug #967039 [src:spamassassin] spamassassin: Unversioned Python removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 967039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#967036 marked as pending in pycparser
Processing control commands: > tag -1 pending Bug #967036 [src:pycparser] pycparser: Unversioned Python removal in sid/bullseye Added tag(s) pending. -- 967036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#967034 marked as pending in ply
Processing control commands: > tag -1 pending Bug #967034 [src:ply] passenger: Unversioned Python removal in sid/bullseye Added tag(s) pending. -- 967034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967034: marked as pending in ply
Control: tag -1 pending Hello, Bug #967034 in ply reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/ply/-/commit/04e62bd07184abba34549c70413b0bbf01b51b52 Depend on the python2 binary package for the 2.7 interpreter. (Closes: #967034) (this message was generated automatically) -- Greetings https://bugs.debian.org/967034
Bug#966952: marked as done (python-virtualenv: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Mon, 03 Aug 2020 21:34:02 +
with message-id
and subject line Bug#966952: fixed in python-virtualenv 20.0.29+ds-1
has caused the Debian Bug report #966952,
regarding python-virtualenv: FTBFS: dpkg-buildpackage: error: dpkg-source -b .
subprocess returned exit status 2
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.)
--
966952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-virtualenv
Version: 20.0.27+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-virtualenv
> dpkg-buildpackage: info: source version 20.0.27+ds-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Stefano Rivera
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> pybuild --clean -i python{version} -p 3.8
> D: pybuild pybuild:560: version: 4.20200315
> D: pybuild pybuild:561: ['/usr/bin/pybuild', '--clean', '-i',
> 'python{version}', '-p', '3.8']
> D: pybuild pybuild:36: cfg: Namespace(after_build=None, after_clean=None,
> after_configure=None, after_install=None, after_test=None, before_build=None,
> before_clean=None, before_configure=None, before_install=None,
> before_test=None, build_args=None, build_only=False, clean_args=None,
> clean_only=True, configure_args=None, configure_only=False,
> custom_tests=False, destdir='debian/tmp', detect_only=False,
> dir='/<>', disable=None, ext_destdir=None,
> ext_pattern='\\.so(\\.[^/]*)?$', ext_sub_pattern=None, ext_sub_repl=None,
> install_args=None, install_dir=None, install_only=False,
> interpreter=['python{version}'], list_systems=False, name='virtualenv',
> print_args=None, quiet=False, really_quiet=False, system=None,
> test_args=None, test_nose=False, test_nose2=False, test_only=False,
> test_pytest=False, test_tox=False, verbose=True, versions=['3.8'])
> D: pybuild __init__:36: cannot initialize 'cmake' plugin
> Traceback (most recent call last):
> File "/usr/share/dh-python/dhpython/build/__init__.py", line 32, in
> module.BuildSystem.is_usable()
> File "/usr/share/dh-python/dhpython/build/base.py", line 120, in is_usable
> raise Exception("missing command: %s" % command)
> Exception: missing command: cmake
> D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
> D: pybuild pybuild:131: detected build system: distutils (certainty: 61%)
> D: pybuild plugin_distutils:56: pydistutils config file:
> [clean]
> all=1
> [build]
> build-lib=/<>/.pybuild/cpython3_3.8_virtualenv/build
> [install]
> force=1
> install-layout=deb
> install-scripts=$base/bin
> install-lib=/usr/lib/python3.8/dist-packages
> prefix=/usr
> [easy_install]
> allow_hosts=None
>
> I: pybuild base:217: python3.8 setup.py clean
> D: pybuild tools:232: invoking: python3.8 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.8_virtualenv/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
> rm -rf .pybuild/
> find . -name \*.pyc -exec rm {} \;
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> rm -f debian/debhelper-build-stamp
> rm -rf debian/.debhelper/
> rm -f -- debian/python3-virtualenv.substvars
> debian/virtualenv.substvars debian/files
> rm -fr -- debian/python3-virtualenv/ debian/tmp/ debian/virtualenv/
> find . \( \( \
> \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o
> -type f -a \
> \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
> \) -exec rm -f {} + \) -o \
> \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
> \)
> dpkg-source -b .
> dpkg-source: info: using
Bug#957906: marked as done (varconf: ftbfs with GCC-10)
Your message dated Mon, 03 Aug 2020 21:34:49 + with message-id and subject line Bug#957906: fixed in varconf 1.0.1-7 has caused the Debian Bug report #957906, regarding varconf: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:varconf Version: 1.0.1-6 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/varconf_1.0.1-6_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] _ZN7varconf6Config10getCmdlineEiPPcNS_5ScopeE@Base 0.6.7 _ZN7varconf6Config10getSectionERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.6.7 @@ -80,7 +80,7 @@ _ZNK7varconf7VarBase7is_boolEv@Base 0.6.7 _ZNK7varconf7VarBase9is_doubleEv@Base 0.6.7 _ZNK7varconf7VarBase9is_stringEv@Base 0.6.7 - (optional=GCC8_removed)_ZNK7varconf7VarBasecvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev@Base 0.6.7 +#MISSING: 1.0.1-6# (optional=GCC8_removed)_ZNK7varconf7VarBasecvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev@Base 0.6.7 _ZNK7varconf7VarBasecvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcv@Base 1.0.1-4~ _ZNK7varconf7VarBasecvbEv@Base 0.6.7 _ZNK7varconf7VarBasecvdEv@Base 0.6.7 @@ -89,40 +89,40 @@ _ZNK7varconf8VarArray7is_boolEv@Base 0.6.7 _ZNK7varconf8VarArray9is_doubleEv@Base 0.6.7 _ZNK7varconf8VarArray9is_stringEv@Base 0.6.7 - (optional=GCC8_removed)_ZNK7varconf8VarArraycvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev@Base 0.6.7 +#MISSING: 1.0.1-6# (optional=GCC8_removed)_ZNK7varconf8VarArraycvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev@Base 0.6.7 _ZNK7varconf8VarArraycvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcv@Base 1.0.1-4~ _ZNK7varconf8VarArraycvbEv@Base 0.6.7 _ZNK7varconf8VarArraycvdEv@Base 0.6.7 _ZNK7varconf8VarArraycviEv@Base 0.6.7 (optional=inline)_ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7varconf8VariableEESt10_Select1stISA_ESt4lessIS5_ESaISA_EE4findERS7_@Base 0.6.7 (optional=inline)_ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_St3mapIS5_N7varconf8VariableESt4lessIS5_ESaIS6_IS7_SA_St10_Select1stISG_ESC_SaISG_EE4findERS7_@Base 0.6.7 - (optional=inline)_ZNSt12_Vector_baseIN7varconf8VariableESaIS1_EED1Ev@Base 0.6.7 - (optional=inline)_ZNSt12_Vector_baseIN7varconf8VariableESaIS1_EED2Ev@Base 0.6.7 +#MISSING: 1.0.1-6# (optional=inline)_ZNSt12_Vector_baseIN7varconf8VariableESaIS1_EED1Ev@Base 0.6.7 +#MISSING: 1.0.1-6# (optional=inline)_ZNSt12_Vector_baseIN7varconf8VariableESaIS1_EED2Ev@Base 0.6.7 (regex)_ZNSt6vectorIN7varconf8VariableESaIS1_EE17_M_default_appendE[mj]@Base 1.0.1 - (optional=GCC8_added)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base 1.0.1-6~ - (optional=GCC8_added)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base 1.0.1-6~ +#MISSING: 1.0.1-6# (optional=GCC8_added)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base 1.0.1-6~ +#MISSING: 1.0.1-6# (optional=GCC8_added)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base 1.0.1-6~
Processed: Re: python-biopython: FTBFS: AssertionError: 0.018551002172574885 != 0.0194 within 4 places (0.00084899782742511518 difference)
Processing control commands: > tags -1 fixed-upstream Bug #966928 [src:python-biopython] python-biopython: FTBFS: AssertionError: 0.018551002172574885 != 0.0194 within 4 places (0.00084899782742511518 difference) Added tag(s) fixed-upstream. -- 966928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966928: python-biopython: FTBFS: AssertionError: 0.018551002172574885 != 0.0194 within 4 places (0.00084899782742511518 difference)
Control: tags -1 fixed-upstream Good day, Looking to upstream issue tracker, the problem has been hit as well and seems triggered by the update past Scipy 1.5.0. Here are the details of the issue, and the fix implemented by zruan: https://github.com/biopython/biopython/issues/2993 https://github.com/biopython/biopython/pull/2998 This test failure will thus most likely be solved with the next upstream version of biopython. Thanks for having caught that issue. Kind Regards, -- Étienne Mollier Old rsa/3072: 5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d New rsa/4096: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/12, please excuse my verbosity. signature.asc Description: PGP signature
Bug#966952: marked as pending in python-virtualenv
Control: tag -1 pending Hello, Bug #966952 in python-virtualenv reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-virtualenv/-/commit/43bcfd6dd128b80610c45035954316cab886cfa8 Replace 0003-Add-ds-to-version.patch with just deleting version.py on clean. It is written during build. (Closes: #966952) (this message was generated automatically) -- Greetings https://bugs.debian.org/966952
Processed: Bug#966952 marked as pending in python-virtualenv
Processing control commands: > tag -1 pending Bug #966952 [src:python-virtualenv] python-virtualenv: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 966952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966954: marked as done (libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 03 Aug 2020 21:04:25 + with message-id and subject line Bug#966954: fixed in libstatgen 1.0.14-7 has caused the Debian Bug report #966954, regarding libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 966954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libstatgen Version: 1.0.14-6 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p debian/libstatgen-dev/usr/include/libStatGen/ > cp -L include/* debian/libstatgen-dev/usr/include/libStatGen/ > ln -s libStatGen.so.0 libStatGen.so > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-a \ > libStatGen.so > Library package automatic movement utility > set -e > install -d -m 755 debian/libstatgen-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libstatgen0/usr/lib/x86_64-linux-gnu > mv ./libStatGen.la debian/libstatgen-dev/usr/lib/x86_64-linux-gnu || true > mv ./libStatGen.so debian/libstatgen-dev/usr/lib/x86_64-linux-gnu > mv /<>/libStatGen.so.0 > debian/libstatgen0/usr/lib/x86_64-linux-gnu > PKGDEV=libstatgen-dev > PKGSHL=libstatgen0 > mv: cannot stat './libStatGen.la': No such file or directory > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz >dh_strip >dh_makeshlibs > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libstatgen0/DEBIAN/symbols doesn't match > completely debian/libstatgen0.symbols > --- debian/libstatgen0.symbols (libstatgen0_1.0.14-6_amd64) > +++ dpkg-gensymbols9PvTtz 2020-08-02 17:21:28.397069852 + > @@ -393,7 +393,7 @@ > (c++)"GzipHeader::readHeader(_IO_FILE*)@Base" 1.0.14 > (c++)"GzipHeader::~GzipHeader()@Base" 1.0.14 > (c++)"IndexBase::IndexBase()@Base" 1.0.14 > - (c++)"IndexBase::Reference::reset()@Base" 1.0.14 > +#MISSING: 1.0.14-6# (c++)"IndexBase::Reference::reset()@Base" 1.0.14 > (c++)"IndexBase::getBinsForRegion(unsigned int, unsigned int, bool*)@Base" > 1.0.14 > (c++)"IndexBase::getMinOffsetFromLinearIndex(int, unsigned int, unsigned > long&) const@Base" 1.0.14 > (c++)"IndexBase::getNumRefs() const@Base" 1.0.14 > @@ -557,7 +557,7 @@ > (c++)"MemoryMap::prefetch()@Base" 1.0.14 > (c++)"MemoryMap::test()@Base" 1.0.14 > (c++)"MemoryMap::~MemoryMap()@Base" 1.0.14 > - (c++)"MemoryMapArray &(unsigned int PackedAccess_1Bit(char*, unsigned int)), &(void > PackedAssign_1Bit(char*, unsigned int, unsigned int)), > &(Packed1BitElementCount2Bytes(unsigned int)), > MemoryMapArrayHeader>::create(char const*, unsigned int, int)@Base" 1.0.14 > +#MISSING: 1.0.14-6# (c++)"MemoryMapArray 289273u, 20090109u, &(unsigned int PackedAccess_1Bit(char*, > unsigned int)), &(void PackedAssign_1Bit(char*, unsigned int, unsigned > int)), &(Packed1BitElementCount2Bytes(unsigned int)), > MemoryMapArrayHeader>::create(char const*, unsigned int, int)@Base" 1.0.14 > (c++)"MemoryMapArray &(unsigned int PackedAccess_4Bit(char*, unsigned int)), &(void > PackedAssign_4Bit(char*, unsigned int, unsigned int)), > &(Packed4BitElementCount2Bytes(unsigned int)), > genomeSequenceMmapHeader>::open(char const*, int)@Base" 1.0.14 > (c++)"MemoryMapArray &(unsigned int PackedAccess_4Bit(char*, unsigned int)), &(void > PackedAssign_4Bit(char*, unsigned int, unsigned int)), > &(Packed4BitElementCount2Bytes(unsigned int)), > genomeSequenceMmapHeader>::~MemoryMapArray()@Base" 1.0.14 > (c++)"MemoryMapArrayHeader::debugPrint(_IO_FILE*)@Base" 1.0.14 > @@ -1629,7 +1629,24 @@ > (c++)"VectorFunc::VectorFunc(double (*)(Vector&))@Base" 1.0.14 > (c++)"VectorFunc::~VectorFunc()@Base" 1.0.14 > _ZN11MiniDeflate14OutputLiteralsERPhiS1_RiP8_IO_FILE@Base 1.0.14 > - >
Bug#966951: libpeas: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1
On Mon, 03 Aug 2020 at 13:09:55 +0100, Simon McVittie wrote: > I've confirmed that this succeeds in a pure bullseye chroot and fails if > I upgrade meson (only) to the version from unstable. I'm not completely > sure whether this is a straightforward regression in meson, or whether > libpeas is holding it wrong. > > It seems that what is meant to happen here is that the libpeas build > system builds tests/libpeas/introspection/*.[ch] into a shared library, > introspects them, and uses the generated introspection data during the > build-time tests. > > With meson 0.54.3-1, I get: > > obj-x86_64-linux-gnu/tests/libpeas/introspection/Introspection-1.0.typelib > obj-x86_64-linux-gnu/tests/libpeas/introspection/Introspection-1.0.gir > > With 0.55.0-2, the introspection data (typelib and GIR XML) isn't generated. Bisection says this regressed in b1e3440e "ninjabackend: Treat GNOME gir/typelib as libraries" - or maybe it's a pre-existing bug in libpeas exposed by that commit, it isn't clear to me which. smcv
Bug#966881: openafs: FTBFS: ld: vlib.a(volume.o):./src/vol/volume.c:128: multiple definition of `vol_io_params'; ihandle.o:./src/vol/ihandle.c:81: first defined here
tags 966881 fixed-upstream thanks On Mon, Aug 03, 2020 at 10:04:57AM +0200, Lucas Nussbaum wrote: > Source: openafs > Version: 1.8.6-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200802 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > gcc -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu/heimdal > > -L/usr/lib/x86_64-linux-gnu/heimdal -g -O -Damd64_linux26 > > -DFSSYNC_BUILD_SERVER -DFSSYNC_BUILD_CLIENT -g -O2 > > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -g -O -I/<>/src/config > > -I/<>/include -I. -I. -I/usr/include/heimdal -o volscan > > volscan-main.o vol-info.o physio.o ihandle.o \ > > /<>/lib/libcmd.a vlib.a /<>/lib/util.a > > /<>/lib/libdir.a /<>/lib/librx.a > > /<>/lib/libafshcrypto_lwp.a /<>/lib/liblwp.a > > /<>/lib/libsys.a /<>/lib/libacl.a > > /<>/lib/libopr.a -lroken -lresolv > > /usr/bin/ld: vlib.a(volume.o):./src/vol/volume.c:128: multiple definition > > of `vol_io_params'; ihandle.o:./src/vol/ihandle.c:81: first defined here > > /usr/bin/ld: vlib.a(daemon_com.o):./src/vol/daemon_com.c:49: multiple > > definition of `V_BreakVolumeCallbacks'; > > vlib.a(fssync-server.o):./src/vol/fssync-server.c:83: first defined here > > gcc -fPIC -g -O2 -fdebug-prefix-map=/<>=. > > -fstack-protector-strong -Wformat -Werror=format-security -g -O > > -I/<>/src/config -I/<>/include -I. -I. > > -I/usr/include/heimdal -o X11windows.o -c X11windows.c > > collect2: error: ld returned 1 exit status Looks like fallout from -fcommon being on by default, and is fixed in upstream (to appear in 1.8.7). We can pull in the relevant patches until then, of course. -Ben
Processed: Re: Bug#966881: openafs: FTBFS: ld: vlib.a(volume.o):./src/vol/volume.c:128: multiple definition of `vol_io_params'; ihandle.o:./src/vol/ihandle.c:81: first defined here
Processing commands for cont...@bugs.debian.org: > tags 966881 fixed-upstream Bug #966881 [src:openafs] openafs: FTBFS: ld: vlib.a(volume.o):./src/vol/volume.c:128: multiple definition of `vol_io_params'; ihandle.o:./src/vol/ihandle.c:81: first defined here Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 966881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966706: marked as done (sparse: /usr/bin/sindex is already provided by biosquid)
Your message dated Mon, 03 Aug 2020 20:48:37 +
with message-id
and subject line Bug#966706: fixed in sparse 0.6.2-2
has caused the Debian Bug report #966706,
regarding sparse: /usr/bin/sindex is already provided by biosquid
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.)
--
966706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sparse
Version: 0.6.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
These files are new in sparse 0.6.2-1, but were already provided by
biosquid since the very first upload in 2006:
/usr/bin/sindex
/usr/share/man/man1/sindex.1.gz
>From the attached log (scroll to the bottom...):
Selecting previously unselected package sparse.
Preparing to unpack .../33-sparse_0.6.2-1_amd64.deb ...
Unpacking sparse (0.6.2-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-sVYzFi/33-sparse_0.6.2-1_amd64.deb (--unpack):
trying to overwrite '/usr/bin/sindex', which is also in package biosquid
1.9g+cvs20050121-11
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/tmp/apt-dpkg-install-sVYzFi/33-sparse_0.6.2-1_amd64.deb
cheers,
Andreas
biosquid=1.9g+cvs20050121-11_sparse=0.6.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sparse
Source-Version: 0.6.2-2
Done: =?utf-8?q?Uwe_Kleine-K=C3=B6nig?=
We believe that the bug you reported is fixed in the latest version of
sparse, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Uwe Kleine-König (supplier of updated sparse 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, 03 Aug 2020 21:30:52 +0200
Source: sparse
Architecture: source
Version: 0.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Uwe Kleine-König
Changed-By: Uwe Kleine-König
Closes: 966706
Changes:
sparse (0.6.2-2) unstable; urgency=medium
.
* Cherry pick patches from upstream to fix various warnings:
- cc651aa7b6a0 ("gensel: remove unneeded test/uninitialized warning")
- eb6779f6f621 ("generic: fix missing inlining of generic expression")
- 5bbebae38be8 ("fix build on Hurd which doesn't define PATH_MAX")
* Drop installing sindex which conflicts with biosquid (Closes: #966706)
* Switch to gtk-3
Checksums-Sha1:
4b5d8828a9f87bae9d5ece2d1bb6806062328933 1601 sparse_0.6.2-2.dsc
26ced5900c84316e1f41b284c8b2945a1adeb140 9176 sparse_0.6.2-2.debian.tar.xz
8ad773a7f505fbd1cae98cdaa13238e7cc9a4355 14123 sparse_0.6.2-2_amd64.buildinfo
Checksums-Sha256:
f65acc47edbe38febf653895d54228e7b883e2365140e21a3675609b702fc331 1601
sparse_0.6.2-2.dsc
a388878c6992a7eaca56a9ee0b85ad13def7cc29bf51d0bdfa687708653babbf 9176
sparse_0.6.2-2.debian.tar.xz
ca8ff4274796d3d2d176e7cd08a4bfc8939b4651d26501f5b0655bdbc04c7663 14123
sparse_0.6.2-2_amd64.buildinfo
Files:
719f0d57528407c4d52ef68aec504d32 1601 devel optional sparse_0.6.2-2.dsc
eb63dfcf549e00ff8c1e5b84fbf6dbd0 9176 devel optional
sparse_0.6.2-2.debian.tar.xz
087500a1a8733e0205d5e7a2eec6783d 14123 devel optional
sparse_0.6.2-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEEfnIqFpAYrP8+dKQLwfwUeK3K7AkFAl8ocvgACgkQwfwUeK3K
7An39wgAgbGLa8g4gieYcb4aCW/Jwv0g11Kf7nk43ikScg++tHqe28Vp4Tu3ikQP
aBw/gxOyaTPxGjQvUIT6eVrAnHeibW/0MlQE1PGlHr3ox9I0tfOEISSHUOIrxcUV
MBTf5cZ5G/+qvBp+P7nKin7Hf3s/GvSTfWSo555o8RudPfMt6itSJcUdqV7vuurR
Nm9ezIumvRParkBPfGdK1Jb+qTQA81TGqg7ofgc8+hDv4k3DUfidsGgvwS4AcqdV
DPxsRSyoYP0R9o/Loj6BIlreGdH3e/IR7r9OJHW6Hi/DN1c1tC0hR2Ye5Iph/IFT
oo9vrLOwJugy/cRbzOjcb9GaFQVjfQ==
=wzDN
-END PGP SIGNATURE End Message ---
Processed: Re: Bug#966854: iagno: FTBFS: ../src/perfs-tests-generator.vala:45.16-45.20: error: The name `Posix' does not exist in the context of `PerfsTestsGenerator.handle_local_options'
Processing control commands: > reassign -1 iagno 1:3.36.2-1 Bug #966854 [meson] iagno: FTBFS: ../src/perfs-tests-generator.vala:45.16-45.20: error: The name `Posix' does not exist in the context of `PerfsTestsGenerator.handle_local_options' Bug reassigned from package 'meson' to 'iagno'. No longer marked as found in versions meson/0.55.0-2. Ignoring request to alter fixed versions of bug #966854 to the same values previously set Bug #966854 [iagno] iagno: FTBFS: ../src/perfs-tests-generator.vala:45.16-45.20: error: The name `Posix' does not exist in the context of `PerfsTestsGenerator.handle_local_options' Marked as found in versions iagno/1:3.36.2-1. > forwarded -1 https://gitlab.gnome.org/GNOME/iagno/-/issues/16 Bug #966854 [iagno] iagno: FTBFS: ../src/perfs-tests-generator.vala:45.16-45.20: error: The name `Posix' does not exist in the context of `PerfsTestsGenerator.handle_local_options' Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/iagno/-/issues/16'. > tags -1 + fixed-upstream patch Bug #966854 [iagno] iagno: FTBFS: ../src/perfs-tests-generator.vala:45.16-45.20: error: The name `Posix' does not exist in the context of `PerfsTestsGenerator.handle_local_options' Added tag(s) patch and fixed-upstream. -- 966854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966854: iagno: FTBFS: ../src/perfs-tests-generator.vala:45.16-45.20: error: The name `Posix' does not exist in the context of `PerfsTestsGenerator.handle_local_options'
Control: reassign -1 iagno 1:3.36.2-1 Control: forwarded -1 https://gitlab.gnome.org/GNOME/iagno/-/issues/16 Control: tags -1 + fixed-upstream patch On Mon, 03 Aug 2020 at 12:43:37 +0100, Simon McVittie wrote: > In the failing build (on bullseye but with unstable's meson), the failing > command seems to be: > > valac -C --pkg gio-2.0 --color=always --directory > src/iagno-perfs-tests-generator.p --basedir ../src > --enable-experimental-non-null ../src/vapi/config.vapi > ../src/perfs-tests-generator.vala ../src/computer-player.vala > ../src/computer-reversi.vala ../src/game.vala ../src/player.vala > > In the successful build (on pure bullseye) the corresponding command seems > to be this: > > [8/47] valac -C --pkg posix --pkg gio-2.0 --color=always --directory > src/25a6634@@iagno-perfs-tests-generator@exe --basedir ../src > --enable-experimental-non-null ../src/vapi/config.vapi > ../src/perfs-tests-generator.vala ../src/computer-player.vala > ../src/computer-reversi.vala ../src/game.vala ../src/player.vala > > so it seems meson 0.55.0 has stopped passing "--pkg posix" to valac On closer inspection this seems to be a pre-existing bug in iagno that was exposed by a meson bugfix. Bisecting meson indicates that the build failure is triggered by 7195c0ee "compilers: Fix accidental coredata mutations". Two executables in iagno use the Posix module: iagno-perfs-tests-generator, and the iagno game itself. However, only the iagno game itself has the required posix_dependency. I think previously, the meson bug fixed in 7195c0ee might have made that dependency leak into the other dependency list. The patch is to add the missing dependency: https://gitlab.gnome.org/GNOME/iagno/-/commit/0100bab269f2102f24a6e41202b931da1b6e8dc5 smcv
Bug#967007: Now dependencies are satisfied
On Tue, Aug 4, 2020 at 00:25, Pirate Praveen wrote: This was fixed in ruby-webpacker 4.2.2-3. Now the autopkgtest is passing. It took almost a whole day to troubleshoot and fix this. with ruby-webpacker 4.2.2-3 and ruby-webdrivers 4.4.1-1 in NEW, passed as local debs, Run options: --seed 51583 # Running: ... Finished in 18.984631s, 0.3687 runs/s, 0.4741 assertions/s. 7 runs, 9 assertions, 0 failures, 0 errors, 0 skips autopkgtest [01:19:44]: test newapp: ---] autopkgtest [01:19:44]: test newapp: - - - - - - - - - - results - - - - - - - - - - newapp PASS I have pushed the changes to 'newapp-autopkgtest` branch as I don't want to block further changes in master till we get ruby-webpacker and ruby-webdrivers in the archive.
Bug#966869: nfs-ganesha: FTBFS with GCC-10
Hi, I submitted a merge request here to fix this FTBFS: https://salsa.debian.org/debian/nfs-ganesha/-/merge_requests/2 Thanks in advance for considering this patch! -- Lucas Kanashiro
Bug#957178: marked as done (eris: ftbfs with GCC-10)
Your message dated Mon, 03 Aug 2020 19:48:31 + with message-id and subject line Bug#957178: fixed in eris 1.3.23-8 has caused the Debian Bug report #957178, regarding eris: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:eris Version: 1.3.23-7 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/eris_1.3.23-7_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6EntityEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 1.3.23 - (optional=GCC8_added)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23-7~ +#MISSING: 1.3.23-7# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6EntityEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 1.3.23 +#MISSING: 1.3.23-7# (optional=GCC8_added)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23-7~ _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base 1.3.23 (optional=certain_64b_arches)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base 1.3.23 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base 1.3.23 - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 1.3.23 +#MISSING: 1.3.23-7# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6PersonEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 1.3.23 (optional=certain_64b_arches)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6RouterEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE11equal_rangeERS7_@Base 1.3.23 - (optional=GCC8_added)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6RouterEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23-7~ +#MISSING: 1.3.23-7# (optional=GCC8_added)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN4Eris6RouterEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESM_IJESt17_Rb_tree_iteratorISB_ESt23_Rb_tree_const_iteratorISB_EDpOT_@Base 1.3.23-7~
Bug#966963: marked as done (igraph: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 03 Aug 2020 19:33:27 +
with message-id
and subject line Bug#966963: fixed in igraph 0.8.2+ds-2
has caused the Debian Bug report #966963,
regarding igraph: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output below
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.)
--
966963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: igraph
Version: 0.8.2+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_fixperms
> find debian \( -name "*.xml" -o -name "*.c" \) -exec chmod -x \{\} \;
> make[1]: Leaving directory '/<>'
>dh_missing
> dh_missing: warning: usr/lib/x86_64-linux-gnu/libigraph.la exists in
> debian/tmp but is not installed to anywhere
> The following debhelper tools have reported what they installed (with
> files per package)
>* dh_install: libigraph-dev (0), libigraph-examples (1), libigraph1 (0)
>* dh_installdocs: libigraph-dev (0), libigraph-examples (0),
> libigraph1 (0)
> If the missing files are installed by another tool, please file a bug
> against it.
> When filing the report, if the tool is not part of debhelper itself,
> please reference the
> "Logging helpers and dh_missing" section from the "PROGRAMMING" guide
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
> Be sure to test with dpkg-buildpackage -A/-B as the results may vary
> when only a subset is built
> If the omission is intentional or no other helper can take care of this
> consider adding the
> paths to debian/not-installed.
>
> Remember to be careful with paths containing "x86_64-linux-gnu", where
> you might need to
> use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
> debian/not-installed
> to ensure it works on all architectures (see #961104).
>dh_dwz
>dh_strip
>dh_makeshlibs
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
> file: see diff output below
> dpkg-gensymbols: warning: debian/libigraph1/DEBIAN/symbols doesn't match
> completely debian/libigraph1.symbols.amd64
> --- debian/libigraph1.symbols.amd64 (libigraph1_0.8.2+ds-1_amd64)
> +++ dpkg-gensymbolsEhE5ap 2020-08-02 16:50:36.637402947 +
> @@ -61,7 +61,7 @@
> _ZN15DL_Indexed_ListIP5NNodeE3GetEm@Base 0.7.1
> _ZN15DL_Indexed_ListIP5NNodeE7pDeleteEP6DLItemIS1_E@Base 0.7.1
> _ZN15DL_Indexed_ListIP5NNodeEC1Ev@Base 0.7.1
> - _ZN15DL_Indexed_ListIPjE4PushES0_@Base 0.7.1
> +#MISSING: 0.8.2+ds-1# _ZN15DL_Indexed_ListIPjE4PushES0_@Base 0.7.1
> _ZN15DL_Indexed_ListIPjEC1Ev@Base 0.7.1
> _ZN3drl11DensityGrid10GetDensityEffb@Base 0.7.1
> _ZN3drl11DensityGrid12fineSubtractERNS_4NodeE@Base 0.7.1
> @@ -753,6 +753,8 @@
> _ZN9HugeArrayIPS_IdEE3SetEm@Base 0.7.1
> _ZN9HugeArrayIdE3SetEm@Base 0.7.1
> _ZN9HugeArrayIiE3SetEm@Base 0.7.1
> + _ZN9HugeArrayIiED1Ev@Base 0.8.2+ds-1
> + _ZN9HugeArrayIiED2Ev@Base 0.8.2+ds-1
> _ZNK5bliss13AbstractGraph15is_automorphismERKSt6vectorIjSaIjEE@Base 0.8.0
> _ZNK5bliss5Graph12is_equitableEv@Base 0.8.0
> _ZNK5bliss5Graph15is_automorphismERKSt6vectorIjSaIjEE@Base 0.8.0
> @@ -773,10 +775,10 @@
> _ZNSt13_Bvector_baseISaIbEE13_M_deallocateEv@Base 0.7.1
>
> _ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIP7vd_pairSt6vectorIS2_SaIS2_S2_EC1ES7_l@Base
> 0.8.0
>
> _ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIP7vd_pairSt6vectorIS2_SaIS2_S2_EC2ES7_l@Base
> 0.8.0
> -
> _ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIP8vbd_pairSt6vectorIS2_SaIS2_S2_EC1ES7_l@Base
> 0.8.0
> -
> _ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIP8vbd_pairSt6vectorIS2_SaIS2_S2_EC2ES7_l@Base
> 0.8.0
> -
> _ZNSt3_V28__rotateIN9__gnu_cxx17__normal_iteratorIP7vd_pairSt6vectorIS3_SaIS3_EET_S9_S9_S9_St26random_access_iterator_tag@Base
> 0.8.0
> -
> _ZNSt3_V28__rotateIN9__gnu_cxx17__normal_iteratorIP8vbd_pairSt6vectorIS3_SaIS3_EET_S9_S9_S9_St26random_access_iterator_tag@Base
> 0.8.0
> +#MISSING: 0.8.2+ds-1#
> _ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIP8vbd_pairSt6vectorIS2_SaIS2_S2_EC1ES7_l@Base
>
Bug#966937: marked as done (interimap: FTBFS: The extension smart is not supported for man)
Your message dated Mon, 03 Aug 2020 19:33:33 + with message-id and subject line Bug#966937: fixed in interimap 0.5.2-1 has caused the Debian Bug report #966937, regarding interimap: FTBFS: The extension smart is not supported for man 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.) -- 966937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: interimap Version: 0.5.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > pandoc -f markdown -t json -- "doc/interimap.1.md" | ./pandoc2man.jq | pandoc > -s -f json -t man+smart -o "doc/interimap.1" > pandoc -f markdown -t json -- "doc/pullimap.1.md" | ./pandoc2man.jq | pandoc > -s -f json -t man+smart -o "doc/pullimap.1" > ThTeh exet exetnsieonsino snm asmrat irst niots nostup psuoprpteodrt efdor > f orma nm > an > make[1]: *** [Makefile:16: doc/pullimap.1] Error 23 The full build log is available from: http://qa-logs.debian.net/2020/08/02/interimap_0.5.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: interimap Source-Version: 0.5.2-1 Done: Guilhem Moulin We believe that the bug you reported is fixed in the latest version of interimap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin (supplier of updated interimap 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, 03 Aug 2020 20:56:37 +0200 Source: interimap Architecture: source Version: 0.5.2-1 Distribution: unstable Urgency: medium Maintainer: Guilhem Moulin Changed-By: Guilhem Moulin Closes: 966937 Changes: interimap (0.5.2-1) unstable; urgency=medium . * New upstream release. Closes: #966937. Checksums-Sha1: c8a4e1911ba0f1b8e00c16d2f7ede1271a8f4c30 2182 interimap_0.5.2-1.dsc 0a29d937c7d9b8622c7b1a7f21607a0ab9d7a031 129167 interimap_0.5.2.orig.tar.gz 8d8558d919aafa6fbc85c34f152c5b721c775fc8 4944 interimap_0.5.2-1.debian.tar.xz 967fb6e346a64dac26f9a89fbe28cfacd430866a 6800 interimap_0.5.2-1_amd64.buildinfo Checksums-Sha256: f87fcc7277d24820a6d1ee55b6d9dcad0ca514811dd4b1f1ca68516dfe16b0f9 2182 interimap_0.5.2-1.dsc ba38d3c3233fb399dc4ec687b543886732e3910a35a6c19937161c882c48d3ea 129167 interimap_0.5.2.orig.tar.gz 321a0d5dfb8ceb32f71b8838998cb1d694936bb28bcb6b376e665846ae3eadfb 4944 interimap_0.5.2-1.debian.tar.xz a8a0f1163148c6248946ceb4a7f4980b7d8c0ee1bfee5b895a63d487e2af2bff 6800 interimap_0.5.2-1_amd64.buildinfo Files: b41973fa984267d1681260472d26741c 2182 mail optional interimap_0.5.2-1.dsc 2d6903d74da3237edb3634345fd4d4e8 129167 mail optional interimap_0.5.2.orig.tar.gz f27e8c5715fc8f684d1c731e8e338792 4944 mail optional interimap_0.5.2-1.debian.tar.xz 9b839df301baab27432a16885a19dde3 6800 mail optional interimap_0.5.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAl8oXkEACgkQ05pJnDwh pVIpAA//UXlRV1qyP0RhTxPloJmzaotsGyLNdlrfX1H4bSKjHdhH3YR06ihlEqMv XhozcGFW+/AW2IxHlujf5RrFMX8JJ1u9VXBLkpfaQnueXNIvk1b9CHlN/Jw56Fq5 P6ISpRrK9+QrROOrgtDPiMTA6MjFK8G+LDHQRmWlNpdvuk5XsVtp6VI4ZVEJi9nu wzVS14fvIj8+BFnjXY2Y7zNxKfYnW9qOpR+wNUokFNiUGpzVe7uHw1D+NlTXzAip CSL8QVCtXWBXYqPbntio+jTW91nYcCPKojLoEUx/C6COveMDa5ck5AX7/mYiideS P/HBRxTLRXBDeHNDXwVv7bn2xeBimolHquOPwAxYRRzhk89BmCcZ0B7FfapLyl12 yJ4wbA6si5DhSh2Fl5MeHmGTTsDDJXdVgeALWwiNjQD6P38EEcXqjjUz86ml/ky6 i0qfQc6V6X7l26JXdBEmJ46qMOGrtmKzvjalPA7vtoQvKly7R/xB2jyGAxlHpHLx P2zbWyMTKlXthTILxk4cdc3jUBaPSjDKoHrLVkTkO2dhk7LFaOmToUL6oabKbEqX
Processed: Bug#957028 marked as pending in axmail
Processing control commands: > tag -1 pending Bug #957028 [src:axmail] axmail: ftbfs with GCC-10 Added tag(s) pending. -- 957028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957028: marked as pending in axmail
Control: tag -1 pending Hello, Bug #957028 in axmail reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-hamradio-team/axmail/-/commit/b991ffe6d121c27eb19d670ce7a34c30eb3a1df3 Fix build failure with gcc 10. (Closes: #957028) (this message was generated automatically) -- Greetings https://bugs.debian.org/957028
Bug#967063: ruby-faye: CVE-2020-15134
Source: ruby-faye Version: 1.2.4-1 Severity: grave Tags: security upstream Forwarded: https://github.com/faye/faye/issues/524 X-Debbugs-Cc: Debian Security Team Hi, The following vulnerability was published for ruby-faye. CVE-2020-15134[0]: | Faye before version 1.4.0, there is a lack of certification validation | in TLS handshakes. Faye uses em-http-request and faye-websocket in the | Ruby version of its client. Those libraries both use the | `EM::Connection#start_tls` method in EventMachine to implement the TLS | handshake whenever a `wss:` URL is used for the connection. This | method does not implement certificate verification by default, meaning | that it does not check that the server presents a valid and trusted | TLS certificate for the expected hostname. That means that any | `https:` or `wss:` connection made using these libraries is vulnerable | to a man-in-the-middle attack, since it does not confirm the identity | of the server it is connected to. The first request a Faye client | makes is always sent via normal HTTP, but later messages may be sent | via WebSocket. Therefore it is vulnerable to the same problem that | these underlying libraries are, and we needed both libraries to | support TLS verification before Faye could claim to do the same. Your | client would still be insecure if its initial HTTPS request was | verified, but later WebSocket connections were not. This is fixed in | Faye v1.4.0, which enables verification by default. For further | background information on this issue, please see the referenced GitHub | Advisory. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-15134 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15134 [1] https://github.com/faye/faye/security/advisories/GHSA-3q49-h8f9-9fr9 [2] https://github.com/faye/faye/issues/524 [3] https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/ Regards, Salvatore
Bug#967061: ruby-faye-websocket: CVE-2020-15133
Source: ruby-faye-websocket Version: 0.10.7-1 Severity: grave Tags: security upstream X-Debbugs-Cc: Debian Security Team Hi, The following vulnerability was published for ruby-faye-websocket. CVE-2020-15133[0]: | In faye-websocket before version 0.11.0, there is a lack of | certification validation in TLS handshakes. The | `Faye::WebSocket::Client` class uses the `EM::Connection#start_tls` | method in EventMachine to implement the TLS handshake whenever a | `wss:` URL is used for the connection. This method does not implement | certificate verification by default, meaning that it does not check | that the server presents a valid and trusted TLS certificate for the | expected hostname. That means that any `wss:` connection made using | this library is vulnerable to a man-in-the-middle attack, since it | does not confirm the identity of the server it is connected to. For | further background information on this issue, please see the | referenced GitHub Advisory. Upgrading `faye-websocket` to v0.11.0 is | recommended. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-15133 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15133 [1] https://github.com/faye/faye-websocket-ruby/security/advisories/GHSA-2v5c-755p-p4gv [2] https://github.com/faye/faye-websocket-ruby/pull/129 [3] https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/ Regards, Salvatore
Bug#961814: Debian Bugs information: logs for Bug#961814
Thanks! Will incorporate in the next upload.
Processed: Re: Now dependencies are satisfied
Processing control commands: > tags -1 pending Bug #967007 [rails] rails: package new gem dependencies for autopkgtests Added tag(s) pending. -- 967007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966875: [Aptitude-devel] Bug#966875: aptitude: FTBFS: ../../../../src/generic/views/download_progress.cc:49:11: error: no match for ‘operator<<’ (operand types are ‘std::ostream’ {aka ‘std::basic_
Hi Lucas, thanks for the bug report. I first thought this seems to have changed with gcc 10.2 instead 10.1 since I had gcc 10 as default locally for quite while before it became default. But at least my last local 0.8.13-1 build was done with still gcc 9. Also verified that it's not just an issue between gcc 10.1 and 10.2 by downgrading gcc-10 and friends to 10.1.0-6 from testing: Didn't fix this. So it might be a general FTBFS with gcc 10 — although I'm surprised this didn't came up earlier. Lucas Nussbaum wrote: > Relevant part (hopefully): Seems to boil down to these: → fgrep "no known conversion" ../aptitude_0.8.13-2_amd64.build | sort -u ../../../../src/generic/views/download_progress.cc:47:89: note: no known conversion for argument 2 from ‘const char [10]’ to ‘const aptitude::views::download_progress::file_progress&’ ../../../../src/generic/views/download_progress.cc:47:89: note: no known conversion for argument 2 from ‘const char [17]’ to ‘const aptitude::views::download_progress::file_progress&’ ../../../../src/generic/views/download_progress.cc:47:89: note: no known conversion for argument 2 from ‘const char [18]’ to ‘const aptitude::views::download_progress::file_progress&’ ../../../../src/generic/views/download_progress.cc:47:89: note: no known conversion for argument 2 from ‘const char [2]’ to ‘const aptitude::views::download_progress::file_progress&’ ../../../../src/generic/views/download_progress.cc:47:89: note: no known conversion for argument 2 from ‘const char [3]’ to ‘const aptitude::views::download_progress::file_progress&’ ../../../../src/generic/views/download_progress.cc:47:89: note: no known conversion for argument 2 from ‘const char [6]’ to ‘const aptitude::views::download_progress::file_progress&’ ../../../../src/generic/views/download_progress.cc:47:89: note: no known conversion for argument 2 from ‘const char [7]’ to ‘const aptitude::views::download_progress::file_progress&’ ../../../../src/generic/views/download_progress.cc:47:89: note: no known conversion for argument 2 from ‘const long unsigned int’ to ‘const aptitude::views::download_progress::file_progress&’ ../../../../src/generic/views/download_progress.cc:97:63: note: no known conversion for argument 2 from ‘const char [18]’ to ‘const aptitude::views::download_progress::status&’ ../../../../src/generic/views/download_progress.cc:97:63: note: no known conversion for argument 2 from ‘const char [2]’ to ‘const aptitude::views::download_progress::status&’ ../../../../src/generic/views/download_progress.cc:97:63: note: no known conversion for argument 2 from ‘const char [3]’ to ‘const aptitude::views::download_progress::status&’ ../../../../src/generic/views/download_progress.h:271:63: note: no known conversion for argument 2 from ‘const char [10]’ to ‘const aptitude::views::download_progress::status&’ ../../../../src/generic/views/download_progress.h:271:63: note: no known conversion for argument 2 from ‘const char [17]’ to ‘const aptitude::views::download_progress::status&’ ../../../../src/generic/views/download_progress.h:271:63: note: no known conversion for argument 2 from ‘const char [2]’ to ‘const aptitude::views::download_progress::status&’ ../../../../src/generic/views/download_progress.h:271:63: note: no known conversion for argument 2 from ‘const char [6]’ to ‘const aptitude::views::download_progress::status&’ ../../../../src/generic/views/download_progress.h:271:63: note: no known conversion for argument 2 from ‘const char [7]’ to ‘const aptitude::views::download_progress::status&’ ../../../../src/generic/views/download_progress.h:271:63: note: no known conversion for argument 2 from ‘const long unsigned int’ to ‘const aptitude::views::download_progress::status&’ And this seems to be the hints what might help: → fgrep "candidate" ../aptitude_0.8.13-2_amd64.build | sort -u ../../../../src/generic/views/download_progress.cc:47:19: note: candidate: ‘std::ostream& aptitude::views::operator<<(std::ostream&, const aptitude::views::download_progress::file_progress&)’ ../../../../src/generic/views/download_progress.cc:96:19: note: candidate: ‘std::ostream& aptitude::views::operator<<(std::ostream&, const aptitude::views::download_progress::status&)’ ../../../../src/generic/views/download_progress.h:270:19: note: candidate: ‘std::ostream& aptitude::views::operator<<(std::ostream&, const aptitude::views::download_progress::status&)’ /usr/include/c++/10/bits/basic_string.h:6458:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, const std::__cxx11::basic_string<_CharT, _Traits, _Allocator>&)’ /usr/include/c++/10/bits/shared_ptr.h:69:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, const std::__shared_ptr<_Tp, _Lp>&)’ /usr/include/c++/10/cstddef:125:5: note: candidate: ‘template constexpr
Bug#967007: Now dependencies are satisfied
Control: tags -1 pending On Mon, Aug 3, 2020 at 23:31, Pirate Praveen wrote: After skipping check for nodejs and yarn version checks in ruby-webpacker, I get this error. This looks like a bug in ruby-webpacker, it may be missing the required files in the binary package. This was fixed in ruby-webpacker 4.2.2-3. Now the autopkgtest is passing. It took almost a whole day to troubleshoot and fix this.
Bug#966974: marked as done (whitedb: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)
Your message dated Mon, 03 Aug 2020 18:04:24 + with message-id and subject line Bug#957932: fixed in whitedb 0.7.3+git200711-1 has caused the Debian Bug report #957932, regarding whitedb: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 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.) -- 957932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: whitedb Version: 0.7.3-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>' > FAIL: Test/common.test > SKIP: Test/log.test > = >WhiteDB 0.7.3: ./test-suite.log > = > > # TOTAL: 2 > # PASS: 0 > # SKIP: 1 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: Test/common > = > > > Showing db segment information > == > mark 1232319011 > size 80 > free 152960 > initialadr 0x7f09ae34c010 > key 0 > segment header size 46568 > subarea array size 64 > > datarec_area > - > varlength > last_subarea_index 0 > subarea nr 0 > size 8192 > offset46568 > alignedsize 8192 > alignedoffset 46568 > bucket nr 288 at offset 4432 > contains dv at offset 46600 with size 8131(8128) and end 54728 > > longstr_area > - > varlength > last_subarea_index 0 > subarea nr 0 > size 8192 > offset54760 > alignedsize 8192 > alignedoffset 54760 > bucket nr 288 at offset 8832 > contains dv at offset 54792 with size 8131(8128) and end 62920 > > listcell_area > - > fixedlength with objlength 16 bytes > freelist 62952 > freelist len 512 > last_subarea_index 0 > subarea nr 0 > size 8192 > offset62952 > alignedsize 8192 > alignedoffset 62952 > > shortstr_area > - > fixedlength with objlength 32 bytes > freelist 71144 > freelist len 256 > last_subarea_index 0 > subarea nr 0 > size 8192 > offset71144 > alignedsize 8192 > alignedoffset 71144 > > word_area > - > fixedlength with objlength 8 bytes > freelist 79336 > freelist len 1024 > last_subarea_index 0 > subarea nr 0 > size 8192 > offset79336 > alignedsize 8192 > alignedoffset 79336 > > doubleword_area > - > fixedlength with objlength 16 bytes > freelist 87528 > freelist len 512 > last_subarea_index 0 > subarea nr 0 > size 8192 > offset87528 > alignedsize 8192 > alignedoffset 87528 > > tnode_area > - > fixedlength with objlength 128 bytes > freelist 95720 > freelist len 64 > last_subarea_index 0 > subarea nr 0 > size 8192 > offset95720 > alignedsize 8192 > alignedoffset 95720 > > checking datarec area > --- > checking dv: bucket nr 288 at offset 4432 > contains dv at offset 46600 with size 8131(8128) and end 54728 > usedcount 0 > usedbytesrealcount 0 > usedbyteswantedcount 0 > freecount 0 > freebytescount 0 > dvcount 1 > dvbytescount 8128 > > area test passed ok > > checking longstr area > --- > checking dv: bucket nr 288 at offset 8832 > contains dv at offset 54792 with size 8131(8128) and end 62920 > usedcount 0 > usedbytesrealcount 0 > usedbyteswantedcount 0 > freecount 0 > freebytescount 0 > dvcount 1 > dvbytescount 8128 > > area test passed ok > > whole test passed ok > * check_datatype_writeread starts > checking null enc/dec > checking char enc/dec for j 0, value 'p' > checking char enc/dec for j 1, value ' ' > checking int enc/dec for j 0, value 0 > checking int enc/dec for j 1, value 100 > checking int enc/dec for j 2, value -50 > checking int enc/dec for j 3, value 100200 > checking double enc/dec for j 0, value 0.00e+00 > checking double enc/dec for j 1, value 1.00e+03 > checking double enc/dec for j 2, value 4.567800e-01 > checking double enc/dec for j 3, value -4.599100e+01 > checking date enc/dec for j 0, value 1 > checking date enc/dec for j 1, value 733773 > checking date enc/dec for j 2, value 733892 > checking date enc/dec for j 3, value 219 > checking building dates from vectors for j 0, expected value 1 > checking building dates from vectors for j 1, expected value 733773 > checking building dates from vectors for j 2,
Bug#957932: marked as done (whitedb: ftbfs with GCC-10)
Your message dated Mon, 03 Aug 2020 18:04:24 + with message-id and subject line Bug#957932: fixed in whitedb 0.7.3+git200711-1 has caused the Debian Bug report #957932, regarding whitedb: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:whitedb Version: 0.7.3-4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/whitedb_0.7.3-4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking fixpoint enc/dec for j 2, value 790.345600 checking fixpoint enc/dec for j 3, value -799.789100 checking fixpoint enc/dec for j 4, value 0.002346 checking str enc/dec for j 0, value "abc", extra "(null)" checking str enc/dec for j 1, value "abcdefghijklmnop", extra "(null)" checking str enc/dec for j 2, value "1234567890123456789012345678901234567890", extra "op12345" checking str enc/dec for j 3, value "", extra "asdasdasdsd" checking str enc/dec for j 4, value "", extra "(null)" checking xmlliteral enc/dec for j 0, value "ffoo", extra "bar:we" checking xmlliteral enc/dec for j 1, value "ffooASASASasaasweerrtttyyuuu", extra "bar:weasdasdasdasdasdasdasdasdasdasdasdasdasddas" checking uri enc/dec for j 0, value "dasdasdasd", extra "" checking uri enc/dec for j 1, value "dasdasdasd12345678901234567890", extra "fofofofof" checking blob enc/dec for j 0, len 10 extra "type1" checking blob enc/dec for j 1, len 200 extra "type2" checking blob enc/dec for j 2, len 10 extra "(null)" checking rec creation, content read/write for j 0, length 0 checking rec creation, content read/write for j 1, length 1 checking rec creation, content read/write for j 2, length 2 checking rec creation, content read/write for j 3, length 3 checking rec creation, content read/write for j 4, length 4 checking rec creation, content read/write for j 5, length 5 checking rec creation, content read/write for j 6, length 100 checking rec creation, content read/write for j 7, length 101 checking rec creation, content read/write for j 8, length 1 checking rec creation, content read/write for j 9, length 10001 checking var enc/dec for j 0, value 0 checking var enc/dec for j 1, value 999882 checking decoding data that doesn't fit the decode buffer (expecting some errors) * check_datatype_writeread ended without errors * testing string parsing parsing string: "" parsing string: " " check_parse_encode: expected value " ", got "�,6 " * Quick test failed ** FAIL Test/common.test (exit status: 1) SKIP: Test/log == logging disabled, skipping checks * Log test succeeded ** SKIP Test/log.test (exit status: 77) Testsuite summary for WhiteDB 0.7.3 # TOTAL: 2 # PASS: 0 # SKIP: 1 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log make[4]: *** [Makefile:818: test-suite.log] Error 1 make[4]: Leaving directory '/<>' make[3]: *** [Makefile:926: check-TESTS] Error 2 make[3]: Leaving directory '/<>' make[2]: *** [Makefile:1150: check-am] Error 2 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:703:
Processed: tagging 966875
Processing commands for cont...@bugs.debian.org:
> tags 966875 + confirmed
Bug #966875 [src:aptitude] aptitude: FTBFS:
../../../../src/generic/views/download_progress.cc:49:11: error: no match for
‘operator<<’ (operand types are ‘std::ostream’ {aka ‘std::basic_ostream’}
and ‘const char [17]’)
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:python-murano-pkg-check
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-murano-pkg-check > # 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 #963398 (http://bugs.debian.org/963398) > # Bug title: python-murano-pkg-check: FTBFS with mock 4.x > # * https://bugs.launchpad.net/bugs/1885431 > # * remote status changed: In-Progress -> Fix-Released > # * closed upstream > tags 963398 + fixed-upstream Bug #963398 [src:python-murano-pkg-check] python-murano-pkg-check: FTBFS with mock 4.x Added tag(s) fixed-upstream. > usertags 963398 - status-In-Progress Usertags were: status-In-Progress. Usertags are now: . > usertags 963398 + status-Fix-Released There were no usertags set. Usertags are now: status-Fix-Released. > thanks Stopping processing here. Please contact me if you need assistance. -- 963398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 966933 to silx
Processing commands for cont...@bugs.debian.org: > reassign 966933 silx Bug #966933 [src:pyfai] pyfai: FTBFS: RuntimeError: Fail to generate 'pyFAI-drawmask' man documentation Bug reassigned from package 'src:pyfai' to 'silx'. No longer marked as found in versions pyfai/0.19.0+dfsg1-3. Ignoring request to alter fixed versions of bug #966933 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 966933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967007: Now dependencies are satisfied
On Mon, Aug 3, 2020 at 21:43, Pirate Praveen wrote: This seems strange as rails metapackage has a dependency on webpack, and yarnpkg which should pull nodejs. After skipping check for nodejs and yarn version checks in ruby-webpacker, I get this error. This looks like a bug in ruby-webpacker, it may be missing the required files in the binary package. + rake --trace webpacker:install ** Invoke webpacker:install (first_time) ** Invoke webpacker:check_node (first_time) ** Execute webpacker:check_node Node.js version is v12.18.2 ** Invoke webpacker:check_yarn (first_time) ** Execute webpacker:check_yarn Yarn version is 1.22.4 ** Execute webpacker:install identical config/webpacker.yml Copying webpack core config exist config/webpack identical config/webpack/development.js identical config/webpack/environment.js identical config/webpack/production.js identical config/webpack/test.js Copying postcss.config.js to app root directory identical postcss.config.js Copying babel.config.js to app root directory identical babel.config.js Copying .browserslistrc to app root directory rails aborted! Thor::Error: Could not find "/usr/share/rubygems-integration/all/gems/webpacker-4.2.2/lib/install/config/.browserslistrc" in any of your source paths.
Processed: reassign 966933 to silx
Processing commands for cont...@bugs.debian.org: > reassign 966933 silx Bug #966933 [silx] pyfai: FTBFS: RuntimeError: Fail to generate 'pyFAI-drawmask' man documentation Ignoring request to reassign bug #966933 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 966933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957151: drbd-utils: ftbfs with GCC-10
Hi, I submitted a merge request here to fix the FTBFS with GCC-10: https://salsa.debian.org/ha-team/drbd-utils/-/merge_requests/6 Thanks for considering the patch! -- Lucas Kanashiro
Bug#966924: marked as done (pylint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)
Your message dated Mon, 3 Aug 2020 13:36:46 -0400
with message-id
and subject line Re: Bug#966924: pylint: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.8 returned exit code 13
has caused the Debian Bug report #966924,
regarding pylint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.8 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pylint
Version: 2.5.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> tests/lint/unittest_lint.py:551:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> pylint/lint/run.py:344: in __init__
> linter.check(args)
> pylint/lint/pylinter.py:870: in check
> self._check_files(
> pylint/lint/pylinter.py:904: in _check_files
> self._check_file(get_ast, check_astroid_module, name, filepath, modname)
> pylint/lint/pylinter.py:930: in _check_file
> check_astroid_module(ast_node)
> pylint/lint/pylinter.py:1062: in check_astroid_module
> retval = self._check_astroid_module(
> pylint/lint/pylinter.py:1107: in _check_astroid_module
> walker.walk(ast_node)
> pylint/utils/ast_walker.py:77: in walk
> callback(astroid)
> pylint/checkers/imports.py:550: in leave_module
> std_imports, ext_imports, loc_imports = self._check_imports_order(node)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self = Checker 'imports' (responsible for 'E0401', 'E0402', 'R0401', 'W0401',
> 'W0402', 'W0404', 'W0406', 'W0407', 'W0410', 'C0410', 'C0411', 'C0412',
> 'C0413', 'C0414', 'C0415')
> _module_node =
>
> def _check_imports_order(self, _module_node):
> """Checks imports of module `node` are grouped by category
>
> Imports must follow this order: standard, 3rd party, local
> """
> std_imports = []
> third_party_imports = []
> first_party_imports = []
> # need of a list that holds third or first party ordered import
> external_imports = []
> local_imports = []
> third_party_not_ignored = []
> first_party_not_ignored = []
> local_not_ignored = []
> > isort_obj = isort.SortImports(
> file_contents="",
> known_third_party=self.config.known_third_party,
> known_standard_library=self.config.known_standard_library,
> )
> E AttributeError: module 'isort' has no attribute 'SortImports'
>
> pylint/checkers/imports.py:712: AttributeError
> _ test_analyze_explicit_script
> _
>
> linter = Checker 'master' (responsible for 'F0001', 'F0002', 'F0010',
> 'I0001', 'I0010', 'I0011', 'I0013', 'I0020', 'I0021', 'I0022', 'E0001',
> 'E0011', 'E0012')
>
> def test_analyze_explicit_script(linter):
> linter.set_reporter(testutils.TestReporter())
> > linter.check(os.path.join(DATA_DIR, "ascript"))
>
> tests/lint/unittest_lint.py:573:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> pylint/lint/pylinter.py:870: in check
> self._check_files(
> pylint/lint/pylinter.py:904: in _check_files
> self._check_file(get_ast, check_astroid_module, name, filepath, modname)
> pylint/lint/pylinter.py:930: in _check_file
> check_astroid_module(ast_node)
> pylint/lint/pylinter.py:1062: in check_astroid_module
> retval = self._check_astroid_module(
> pylint/lint/pylinter.py:1107: in _check_astroid_module
> walker.walk(ast_node)
> pylint/utils/ast_walker.py:77: in walk
> callback(astroid)
> pylint/checkers/imports.py:550: in leave_module
> std_imports, ext_imports, loc_imports = self._check_imports_order(node)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self = Checker 'imports' (responsible for 'E0401', 'E0402', 'R0401', 'W0401',
> 'W0402', 'W0404', 'W0406', 'W0407', 'W0410', 'C0410', 'C0411', 'C0412',
> 'C0413', 'C0414', 'C0415')
> _module_node =
>
> def _check_imports_order(self, _module_node):
> """Checks imports of module `node` are grouped by category
>
> Imports must follow this order: standard, 3rd party, local
> """
> std_imports = []
>
Bug#961814: Debian Bugs information: logs for Bug#961814
On Mon, Aug 3, 2020 at 8:30 AM Shengjing Zhu wrote: > If I read the comments in upstream issue correctly, it will be solved in 2 > months (they said 6 months later at April). What's the urgent thing we need > to address in this two months? > I realized that podman 2.0 requires this newer version of protobuf. I've changed podman to vendor the sources for now. Urgency is in the eye of the beholder, I guess. It just seems weird to me to not be able to use this package until this bug is addressed. -rt
Bug#937490: pynifti: Python2 removal in sid/bullseye
On Mon, Aug 03, 2020 at 07:39:12AM +0200, Michael Hanke wrote: > Hi, > > On Sun, Aug 2, 2020, 23:47 Moritz Mühlenhoff wrote: > > > On Fri, Jul 10, 2020 at 01:08:44PM +0200, Andreas Tille wrote: > > > On Mon, Jun 29, 2020 at 08:37:58PM +0200, Moritz Mühlenhoff wrote: > > > > On Fri, Aug 30, 2019 at 07:34:39AM +, Matthias Klose wrote: > > > > > > > > The upstream homepage states > > > > > > > > | PyNIfTI is no longer actively developed. At has been > > > > | superseded by NiBabel -- a pure-Python package that > > > > | provides everything that PyNIfTI could do, and a lot more. > > > > > > > > Given that nibabel is packaged, let's simply remove pynifti? > > > > > > Same answer from my side as for mrtrix - from my point of > > > view it can go. > > > > Michael/Yaroslav, ping. Ack to remove pynifti from your end? > > Yes, it can go. Thx. Ack, I've just filed an RM bug. Cheers, Moritz
Processed: fixed in salsa
Processing commands for cont...@bugs.debian.org: > merge 966712 967024 Bug #966712 [src:statsmodels] statsmodels: debci tests fail Bug #966712 [src:statsmodels] statsmodels: debci tests fail Added tag(s) ftbfs, bullseye, and sid. Bug #967024 [src:statsmodels] statsmodels: FTBFS: tests failed Added tag(s) fixed-upstream and patch. Merged 966712 967024 > tags 966712 + pending Bug #966712 [src:statsmodels] statsmodels: debci tests fail Bug #967024 [src:statsmodels] statsmodels: FTBFS: tests failed Added tag(s) pending. Added tag(s) pending. > tags 966393 + pending Bug #966393 [src:pandas] pandas: FTBFS: TypeError: use() got an unexpected keyword argument 'warn' Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 966393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966393 966712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966712 967024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945673: closed by Debian FTP Masters (reply to Vincent Bernat ) (Bug#966735: fixed in fvwm-crystal 3.4.1+dfsg-2)
Adrian, now people are closing these bugs thinking they are handling the py2unversioned requests while they are also closing the py2removal bugs, because you decided to merge them! While your intentions may have been good, this was a mistake (as the 2 requests are *not* the same) that will cause great consequences in tracking and handling the py2removal process. Now please: unmerge all the bugs you merged; close the ones that need to be closed and leave the ones still pending open; next time make sure to coordinate further action on the python2 removal process with debian-python@ first Regards, Sandro On Mon, Aug 3, 2020 at 3:21 AM Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the src:fvwm-crystal package: > > #945673: fvwm-crystal: Python2 removal in sid/bullseye > > It has been closed by Debian FTP Masters > (reply to Vincent Bernat ). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters > (reply to Vincent Bernat > ) by > replying to this email. > > > -- > 966735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966735 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded message -- > From: Debian FTP Masters > To: 966735-cl...@bugs.debian.org > Cc: > Bcc: > Date: Mon, 03 Aug 2020 07:18:57 + > Subject: Bug#966735: fixed in fvwm-crystal 3.4.1+dfsg-2 > Source: fvwm-crystal > Source-Version: 3.4.1+dfsg-2 > Done: Vincent Bernat > > We believe that the bug you reported is fixed in the latest version of > fvwm-crystal, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 966...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Vincent Bernat (supplier of updated fvwm-crystal package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Format: 1.8 > Date: Mon, 03 Aug 2020 08:19:33 +0200 > Source: fvwm-crystal > Architecture: source > Version: 3.4.1+dfsg-2 > Distribution: unstable > Urgency: medium > Maintainer: Vincent Bernat > Changed-By: Vincent Bernat > Closes: 966735 > Changes: > fvwm-crystal (3.4.1+dfsg-2) unstable; urgency=medium > . >* d/control: B-D on python2 (Closes: #966735) >* d/control: use debhelper-compat >* d/NEWS: rename from d/NEWS.Debian to d/NEWS >* d/control: update Vcs-* fields >* d/lintian: remove unused overrides >* d/NEWS: fix versions > Checksums-Sha1: > 5ff090b87289858f3698cf77db5569fd286e3ab5 1976 fvwm-crystal_3.4.1+dfsg-2.dsc > 3dddca9fe374bead4a9c4a8d6bfb726b6e3a9f4a 5452811 > fvwm-crystal_3.4.1+dfsg.orig.tar.gz > 3bf38052669fc15a37a0aae502a1cba40dc64fe1 10312 > fvwm-crystal_3.4.1+dfsg-2.debian.tar.xz > 9e4b0f36ce25a0259c6d1239da6c24a6139a6470 6079 > fvwm-crystal_3.4.1+dfsg-2_amd64.buildinfo > Checksums-Sha256: > 752723b94db598ba4ac9196ba2e9e3ebf5d4b72ba764f937c7665abf5d473593 1976 > fvwm-crystal_3.4.1+dfsg-2.dsc > 7f0c2fe738d6c3ef37834a051baeafc5170feb9b10b1fb3ee0472727e574d6e4 5452811 > fvwm-crystal_3.4.1+dfsg.orig.tar.gz > 5871097d52d67a81dbaa26fd5c99ec1c1e203e747ab5568ce674673f68ae453f 10312 > fvwm-crystal_3.4.1+dfsg-2.debian.tar.xz > cfea15a2d05698f1b637ce2efa19e420a5ab191ae5d58056d1cee49a21677595 6079 > fvwm-crystal_3.4.1+dfsg-2_amd64.buildinfo > Files: > 7b8798dfa1afc44c1513a504c9c71deb 1976 x11 optional > fvwm-crystal_3.4.1+dfsg-2.dsc > b6d0bae13067d6422388ba25bbaa55f9 5452811 x11 optional > fvwm-crystal_3.4.1+dfsg.orig.tar.gz > 4086fa2d763c785d4ee9ce284cbe5cbc 10312 x11 optional > fvwm-crystal_3.4.1+dfsg-2.debian.tar.xz > 0d30296045e833d262b839790c17ffc5 6079 x11 optional > fvwm-crystal_3.4.1+dfsg-2_amd64.buildinfo > > -BEGIN PGP SIGNATURE- > > iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl8ntv4SHGJlcm5hdEBk > ZWJpYW4ub3JnAAoJEJWkL+g1NSX5MC4P/RY9Y14OtcX0K29DW11ilVmqXVTiSbFU > z5POkTIL3whKWpHRg/ZQbYrkDEwfJAlsuA83s5ZCH0NY1Xcj5BG0wxH509Qrcora > nQpXGINbq9nHpU1GH1QBobVI0aC4ZqHqpNuKcvAPnGlhR9nEeckq9OO00LELwjPN > 70PK37kvYZZl8PQ9eA/3qyvTPrBwshtVzSnWtRHRRxq0VsJAWcBlVOi/lMA89m+i > 8LS7d2gtP1DPd2NKIx8waKGUX4trgGxH2Bak555IvE94AYQiqi8QJ5DNGe5wXYOD > fBydh/MZcDSVxnnoNgeVOiZsJZHOP525iEO4/SQdesDx8fLX2PneVXB4rPRASp5U > YM6knUq1enrFINEc4wpiM4qMnC1ZsugeHFLdWu+/tFwwZaPa6+g6/9/eVtQ53OrL > 1Xc/YyB3EKCKJcq3iSIVuStvBP511UE3H3JZNxhyT+6/IlbvjOfXw0Rw64tKgkUF > 0uzUXRvrK/NoHn+YFxNkxXJManHtiicYg5du5Tg2ebm25J+IMFkHvMxPbs5GF5LG >
Bug#966828: emacs: Fatal error 11: Segmentation fault
Control: reassign -1 libx11-6 Control: forcemerge 966691 -1 Control: affects 966691 emacs On Mon, Aug 03, 2020 at 01:23:59PM +0900, Winter Metasequoia wrote: > FYI. I just encountered similar situation, but downgrading libx11-6 > from 2:1.6.10-1 to 2:1.6.9-2+b1 > emacs has been recovered. I hope someone confirms this. Yes, this is a bug that is fixed in libx11-6 2:1.6.10-3. cu Adrian
Processed: Re: Bug#966828: emacs: Fatal error 11: Segmentation fault
Processing control commands:
> reassign -1 libx11-6
Bug #966828 [emacs] emacs: Fatal error 11: Segmentation fault
Bug reassigned from package 'emacs' to 'libx11-6'.
No longer marked as found in versions emacs/1:26.3+1-2.
Ignoring request to alter fixed versions of bug #966828 to the same values
previously set
> forcemerge 966691 -1
Bug #966691 {Done: Julien Cristau } [libx11-6] emacs-gtk:
Segmentation fault with libx11-6 v. 2:1.6.10-1
Bug #966696 {Done: Julien Cristau } [libx11-6] emacs
Segmentation fault
Bug #966812 {Done: Julian Taylor } [libx11-6]
keepass2: Keepass2 crashes at startup after system update
Bug #966696 {Done: Julien Cristau } [libx11-6] emacs
Segmentation fault
Removed indication that 966696 affects emacs-gtk and keepass2
Added indication that 966696 affects keepass2,emacs-gtk
Removed indication that 966691 affects keepass2 and emacs-gtk
Added indication that 966691 affects keepass2,emacs-gtk
Removed indication that 966812 affects emacs-gtk and keepass2
Added indication that 966812 affects keepass2,emacs-gtk
Bug #966828 [libx11-6] emacs: Fatal error 11: Segmentation fault
Marked Bug as done
Added indication that 966828 affects keepass2,emacs-gtk
The source libx11 and version 2:1.6.10-2 do not appear to match any binary
packages
Marked as fixed in versions libx11/2:1.6.10-2.
Marked as found in versions emacs/1:26.3+1-2 and libx11/2:1.6.10-1.
Bug #966812 {Done: Julian Taylor } [libx11-6]
keepass2: Keepass2 crashes at startup after system update
Merged 966691 966696 966812 966828
> affects 966691 emacs
Bug #966691 {Done: Julien Cristau } [libx11-6] emacs-gtk:
Segmentation fault with libx11-6 v. 2:1.6.10-1
Bug #966696 {Done: Julien Cristau } [libx11-6] emacs
Segmentation fault
Bug #966812 {Done: Julian Taylor } [libx11-6]
keepass2: Keepass2 crashes at startup after system update
Bug #966828 {Done: Julien Cristau } [libx11-6] emacs:
Fatal error 11: Segmentation fault
Added indication that 966691 affects emacs
Added indication that 966696 affects emacs
Added indication that 966812 affects emacs
Added indication that 966828 affects emacs
--
966691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966691
966696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966696
966812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966812
966828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#967007: Now dependencies are satisfied
On Mon, Aug 3, 2020 at 20:12, Pirate Praveen wrote: Once ruby-webpacker and ruby-webdrivers clears NEW creating new rails app will work. Now some tests for the newly created app fails. I think running rails webpacker:install will fix it. + rails webpacker:install Warning: Running `gem pristine --all` to regenerate your installed gemspecs (and deleting then reinstalling your bundle if you use bundle --path) will improve the startup performance of Spring. Node.js not installed. Please download and install Node.js https://nodejs.org/en/download/ This seems strange as rails metapackage has a dependency on webpack, and yarnpkg which should pull nodejs.
Processed: forcibly merging 966691 966812, affects 966691
Processing commands for cont...@bugs.debian.org:
> forcemerge 966691 966812
Bug #966691 {Done: Julien Cristau } [libx11-6] emacs-gtk:
Segmentation fault with libx11-6 v. 2:1.6.10-1
Bug #966696 {Done: Julien Cristau } [libx11-6] emacs
Segmentation fault
Bug #966812 {Done: Julian Taylor } [libx11-6]
keepass2: Keepass2 crashes at startup after system update
Added indication that 966812 affects emacs-gtk
The source libx11 and version 2:1.6.10-2 do not appear to match any binary
packages
Marked as fixed in versions libx11/2:1.6.10-2.
Marked as found in versions emacs/1:26.3+1-2 and libx11/2:1.6.10-1.
Bug #966696 {Done: Julien Cristau } [libx11-6] emacs
Segmentation fault
Marked as found in versions emacs/1:26.3+1-2.
Ignoring request to alter found versions of bug #966691 to the same values
previously set
Merged 966691 966696 966812
> affects 966691 + keepass2
Bug #966691 {Done: Julien Cristau } [libx11-6] emacs-gtk:
Segmentation fault with libx11-6 v. 2:1.6.10-1
Bug #966696 {Done: Julien Cristau } [libx11-6] emacs
Segmentation fault
Bug #966812 {Done: Julian Taylor } [libx11-6]
keepass2: Keepass2 crashes at startup after system update
Added indication that 966691 affects keepass2
Added indication that 966696 affects keepass2
Added indication that 966812 affects keepass2
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966691
966696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966696
966812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: nvtv: diff for NMU version 0.4.7-8.1
Processing control commands: > tags 957620 + patch Bug #957620 [src:nvtv] nvtv: ftbfs with GCC-10 Added tag(s) patch. > tags 957620 + pending Bug #957620 [src:nvtv] nvtv: ftbfs with GCC-10 Added tag(s) pending. -- 957620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957620: nvtv: diff for NMU version 0.4.7-8.1
Control: tags 957620 + patch Control: tags 957620 + pending Dear maintainer, I've prepared an NMU for nvtv (versioned as 0.4.7-8.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru nvtv-0.4.7/debian/changelog nvtv-0.4.7/debian/changelog --- nvtv-0.4.7/debian/changelog 2012-09-02 02:46:52.0 +0100 +++ nvtv-0.4.7/debian/changelog 2020-08-03 16:30:37.0 +0100 @@ -1,3 +1,10 @@ +nvtv (0.4.7-8.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-10. (Closes: #957620) + + -- Sudip Mukherjee Mon, 03 Aug 2020 16:30:37 +0100 + nvtv (0.4.7-8) unstable; urgency=low * Updated standards. diff -Nru nvtv-0.4.7/debian/patches/fix_ftbfs.patch nvtv-0.4.7/debian/patches/fix_ftbfs.patch --- nvtv-0.4.7/debian/patches/fix_ftbfs.patch 1970-01-01 01:00:00.0 +0100 +++ nvtv-0.4.7/debian/patches/fix_ftbfs.patch 2020-08-03 16:30:14.0 +0100 @@ -0,0 +1,80 @@ +Description: Fix ftbfs with GCC-10. + +Author: Sudip Mukherjee +Bug-Debian: https://bugs.debian.org/957620 +Forwarded: no + +--- + +--- nvtv-0.4.7.orig/src/data_cx.c nvtv-0.4.7/src/data_cx.c +@@ -33,6 +33,19 @@ + #include "data_cx.h" + #include "data_nv.h" + ++TVCxRegs cx_ntsc_xbox; /* XBox BIOS */ ++ ++TVCxRegs cx_ntsc_small_a; /* Mode 10, hoc=15.11 voc=14.81 */ ++TVCxRegs cx_ntsc_normal_a; /* Mode 26, hoc=11.97 voc=11.93 */ ++TVCxRegs cx_ntsc_tiny_a; /* Mode 42, hoc=18.04 voc=18.11 */ ++TVCxRegs cx_ntsc_small_b; /* Mode 18, hoc=13.79 voc=13.58 */ ++TVCxRegs cx_ntsc_tiny_b; /* Mode 34, hoc=19.26 voc=19.34 */ ++TVCxRegs cx_ntsc_mini_b; /* Mode 40, hoc=15.59 voc=15.64 */ ++ ++TVCxRegs cx_pal_small_a; /* Mode 11, hoc=13.44 voc=14.24 */ ++TVCxRegs cx_pal_mini_a;/* Mode 43, hoc=16.20 voc=16.67 */ ++ ++ + /* CX NTSC */ + + /* FIXME I do not know if all XBoxes have the CX encoder. For now, we +--- nvtv-0.4.7.orig/src/data_cx.h nvtv-0.4.7/src/data_cx.h +@@ -37,16 +37,16 @@ void data_setup_cx (TVSettings *s, TVReg + + void data_secam_cx (TVCxRegs *r); + +-TVCxRegs cx_ntsc_xbox; /* XBox BIOS */ ++extern TVCxRegs cx_ntsc_xbox; /* XBox BIOS */ + +-TVCxRegs cx_ntsc_small_a; /* Mode 10, hoc=15.11 voc=14.81 */ +-TVCxRegs cx_ntsc_normal_a; /* Mode 26, hoc=11.97 voc=11.93 */ +-TVCxRegs cx_ntsc_tiny_a; /* Mode 42, hoc=18.04 voc=18.11 */ +-TVCxRegs cx_ntsc_small_b; /* Mode 18, hoc=13.79 voc=13.58 */ +-TVCxRegs cx_ntsc_tiny_b; /* Mode 34, hoc=19.26 voc=19.34 */ +-TVCxRegs cx_ntsc_mini_b; /* Mode 40, hoc=15.59 voc=15.64 */ ++extern TVCxRegs cx_ntsc_small_a; /* Mode 10, hoc=15.11 voc=14.81 */ ++extern TVCxRegs cx_ntsc_normal_a; /* Mode 26, hoc=11.97 voc=11.93 */ ++extern TVCxRegs cx_ntsc_tiny_a; /* Mode 42, hoc=18.04 voc=18.11 */ ++extern TVCxRegs cx_ntsc_small_b; /* Mode 18, hoc=13.79 voc=13.58 */ ++extern TVCxRegs cx_ntsc_tiny_b; /* Mode 34, hoc=19.26 voc=19.34 */ ++extern TVCxRegs cx_ntsc_mini_b; /* Mode 40, hoc=15.59 voc=15.64 */ + +-TVCxRegs cx_pal_small_a; /* Mode 11, hoc=13.44 voc=14.24 */ +-TVCxRegs cx_pal_mini_a;/* Mode 43, hoc=16.20 voc=16.67 */ ++extern TVCxRegs cx_pal_small_a; /* Mode 11, hoc=13.44 voc=14.24 */ ++extern TVCxRegs cx_pal_mini_a;/* Mode 43, hoc=16.20 voc=16.67 */ + + #endif /* _DATA_CX_H */ +--- nvtv-0.4.7.orig/src/nvtv.c nvtv-0.4.7/src/nvtv.c +@@ -117,6 +117,8 @@ int opt_pci_func = -1; + + TVSettings opt_set; + ++int opt_tv_bus, opt_tv_addr; ++ + static const char *short_options = "?12bcdf:ghlmno:pqr:s:tw:A:C:FNPS:T:W:X"; + + static struct option long_options[] = +--- nvtv-0.4.7.orig/src/nvtv.h nvtv-0.4.7/src/nvtv.h +@@ -58,7 +58,7 @@ extern TVConnect opt_connect;/* use + extern TVSettings opt_set; + + extern TVChip opt_tv_chip; /* use if != TV_NO_CHIP */ +-int opt_tv_bus, opt_tv_addr; /* use if == TV_CHIP_BY_ADDR */ ++extern int opt_tv_bus, opt_tv_addr; /* use if == TV_CHIP_BY_ADDR */ + + #if HAVE_X + extern Window opt_window;/* use if != None */ diff -Nru nvtv-0.4.7/debian/patches/series nvtv-0.4.7/debian/patches/series --- nvtv-0.4.7/debian/patches/series2012-09-01 18:30:48.0 +0100 +++ nvtv-0.4.7/debian/patches/series2020-08-03 16:24:25.0 +0100 @@ -3,3 +3,4 @@ 003_Gnu.patch 004_makefile 005_autotools.patch +fix_ftbfs.patch
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org:
> reassign 966812 libx11-6
Bug #966812 {Done: Julian Taylor } [keepass2]
keepass2: Keepass2 crashes at startup after system update
Bug reassigned from package 'keepass2' to 'libx11-6'.
No longer marked as found in versions keepass2/2.45+dfsg-1.
Ignoring request to alter fixed versions of bug #966812 to the same values
previously set
> merge 966691 966812
Bug #966691 {Done: Julien Cristau } [libx11-6] emacs-gtk:
Segmentation fault with libx11-6 v. 2:1.6.10-1
Bug #966696 {Done: Julien Cristau } [libx11-6] emacs
Segmentation fault
Unable to merge bugs because:
affects of #966812 is '' not 'emacs-gtk'
Failed to merge 966691: Did not alter merged bugs.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
966691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966691
966696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966696
966812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#908694: marked as done (album-data: please remove dependency on libjs-swfobject, which is going away)
Your message dated Mon, 03 Aug 2020 15:33:29 + with message-id and subject line Bug#908694: fixed in album-data 4.05-7.1 has caused the Debian Bug report #908694, regarding album-data: please remove dependency on libjs-swfobject, which is going away to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 908694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: album-data version: 4.05-7 severity: serious Control: block 900106 by -1 Hi, Please remove the dependency on libjs-swfobject, which is scheduled to be removed from buster. See https://bugs.debian.org/900106 for more info. Cheers, Ivo --- End Message --- --- Begin Message --- Source: album-data Source-Version: 4.05-7.1 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of album-data, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated album-data package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 01 Aug 2020 15:43:30 +0100 Source: album-data Architecture: source Version: 4.05-7.1 Distribution: unstable Urgency: medium Maintainer: Salvo 'LtWorf' Tomaselli Changed-By: Sudip Mukherjee Closes: 908694 Changes: album-data (4.05-7.1) unstable; urgency=medium . * Non-maintainer upload. * Removed dependency on libjs-swfobject. (Closes: #908694) - Upstream has confirmed. (See: #964105) Checksums-Sha1: 5ca671d814a375fbd9dcd3d41dc57ad4febbeb4e 1892 album-data_4.05-7.1.dsc 8051ae9fddc13880546a95e34bf6eba1cd2e898b 16108 album-data_4.05-7.1.debian.tar.xz ebaef94cd6955cc3fb9e63583e7aebbcdb3dbe7b 5417 album-data_4.05-7.1_amd64.buildinfo Checksums-Sha256: 2fe2d01d7bb32e22a466201e143a31e43623a30b9c6db9f4eb3ad710faa812d4 1892 album-data_4.05-7.1.dsc f4157e307d21d5d9122904a0e71b8253a688596232e43d7f56ae50d96b461d99 16108 album-data_4.05-7.1.debian.tar.xz b333eddcea75d0fb0fe85f53d0a11c04864f57322a28448f051832ae5134cd97 5417 album-data_4.05-7.1_amd64.buildinfo Files: 6d555d7c2f348578e2cc5f5a1fe311e8 1892 non-free/web extra album-data_4.05-7.1.dsc e85191167669cbc901f29c32f23ddcde 16108 non-free/web extra album-data_4.05-7.1.debian.tar.xz 5854095d1b3d789e696845fc2d019d83 5417 non-free/web extra album-data_4.05-7.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl8lgegACgkQR5mjUUbR KzXcQw//QTWNRwwsS9uKeOxdJkeDo6Tr2YsgOb69NkL4WWrqEt0DjdD3t/Sizwhb 55QPIFd8KgtdXRHXiOkA0XCNxZKrpMEx+y7ybEvlaEnyH4rvQ6YHIpiWkn3wIkxH SyrL07V6al7GQSz2IE6IFj0Hh1E30ooABlwaFaISHNeTpzrBchAfbSCRZUYc5cQH ExOwgtIKkIHKtZALyuG/Fceb3PBIzYUSHmNha9lcjAe08xoGey21boFV0DGWROOk dmkl7SJHQ40SMuJs3bYnjpuiThb5SA0tyPyEHff2CPuYNnz7/Xx/w00eKjCaEpmu 0nwyxQZD1axDycDvluptkTvjJ8D339jqusiuzj8A7JwlTsiX19zalahDrM4PaCu4 gEbC+sEUTJFtY0ldqdQqedhFyyNyWh27NR7lZ5viu/JiuRctyYzLlNQzH3aJVyPs 7giSsbXWSzY/2UtfQmgX7Qc0oAT+1PIX4kQj4Mi1/wDP730x8Bwt91wl2poL3BOA sph4bKiccC/E9pWq5Zsz6eB1W8VHIbQBIKumOHscysWre4TKj9faMAnDn3rsKCJP cRM03hpMtuEdqZ06ePAdCf3XoIHGZ6VlnUQXDq3+q5Cw0JyDhibCvw1SnNrWMr+7 Figfs33bvRj8PTz56Q+fHIXJduipu1lFXjbxsRXKRTRJsIWqLxU= =7K+8 -END PGP SIGNATURE End Message ---
Bug#947265: marked as done (python3-lmfit: ships /usr/lib/python3/dist-packages/examples/*)
Your message dated Mon, 03 Aug 2020 15:34:09 + with message-id and subject line Bug#947265: fixed in lmfit-py 1.0.1-1 has caused the Debian Bug report #947265, regarding python3-lmfit: ships /usr/lib/python3/dist-packages/examples/* 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.) -- 947265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-lmfit Version: 1.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, python3-lmfit ships files with generic names at the generic location /usr/lib/python3/dist-packages/examples/ causing file clashes (e.g. on README.txt) with other packages doing the same wrong thing. Moving this to /usr/lib/python3/dist-packages/examples/lmfit/ should probably be OK. Andreas --- End Message --- --- Begin Message --- Source: lmfit-py Source-Version: 1.0.1-1 Done: =?utf-8?q?Picca_Fr=C3=A9d=C3=A9ric-Emmanuel?= We believe that the bug you reported is fixed in the latest version of lmfit-py, 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 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Picca Frédéric-Emmanuel (supplier of updated lmfit-py 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, 03 Aug 2020 11:21:26 +0200 Source: lmfit-py Architecture: source Version: 1.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Picca Frédéric-Emmanuel Closes: 947265 Changes: lmfit-py (1.0.1-1) unstable; urgency=medium . [ Debian Janitor ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Picca Frédéric-Emmanuel ] * New upstream version 1.0.1 * d/control: Added Rules-Requires-Root: no * d/control: Standards-Verion bumped to 4.3.0 (nothing to do) * d/rules: examples was not meant to be installed (Closes: #947265) * d/rules: Build the documentation * d/tests/control: Now it works. Checksums-Sha1: e470f990cd6fb5b854922b9f6c09754fc3c28ae1 2586 lmfit-py_1.0.1-1.dsc ef4337a6c647058dfad609a0ee4ca024bf1ec7c8 258368 lmfit-py_1.0.1.orig.tar.gz 0ebccd7b74c8b11709481c048b8ea05cf930d23b 7088 lmfit-py_1.0.1-1.debian.tar.xz Checksums-Sha256: 2207bb9f9db9a0cd1ce6b3b06e5c40a4835d4679afd972b9669322d7b0c6188f 2586 lmfit-py_1.0.1-1.dsc d249eb756899360f4d2a544c9458f47fc8f765ac22c09e099530585fd64e286e 258368 lmfit-py_1.0.1.orig.tar.gz 1178c05d5b2b078239172692ba929b3920f0135ce69b1fe0922b9ab3e8826329 7088 lmfit-py_1.0.1-1.debian.tar.xz Files: 86b1e3cee5bf16277275b3e59b1b233e 2586 science optional lmfit-py_1.0.1-1.dsc c2b2e5c4f5a43c0760b28308d3028e98 258368 science optional lmfit-py_1.0.1.orig.tar.gz c700f94e5cb1ddf8e612d2bb5cef90eb 7088 science optional lmfit-py_1.0.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAl8oKscRHHBpY2NhQGRl Ymlhbi5vcmcACgkQW/VOXhK5ALvOORAAgOopwGHUpNQJvgITg6ATFNWAjC5ltzpJ eYtS5Y1Xr4ye5OL0aRVzEXTCOyig3gMsiAXOK9AfuEBRa4Sh4AoCHoY0LzkrEnTB bwcXfQrUQAIGUKxbnljUqaO4EGeJC7cnaoflcZMEcTgE9xkllXT/2Gkqgq6qNrPK os6We2joQhYZriAfiH0e3d4bbgQcTNoF/bpgrUkB9qZpGsScgnF+qR9Z8oD+sYBt GBJ9dYrJf8s03sH4Awe++qGsJ3eY28oykq48MnLWO6ehXr+VUfhYAVJaIiJ2ylmh Xv2qNRbOSPbFzDrDxk+LnZxZ+dVeNMcHpzKSgMvruwCe68DBlWi79891bI6Z9Ji8 Z4JkWbBdBPRQpsiNlOJBhbd5CsI+yhNpvLvR6U4EsuIqfxgR3AUcnPK0PmbfBslK /yL5vS9ODkwIHFyHAU08gCUMaJ2YVArSAMyGWXsYoFuxQFILHvRtRKSg5nvo9Qny qEeLSyH9+K5m6hhL5KEqlYGV8yRsgDmghuWjOf+DayIsMV/AwBcnE1y7GwOOU5zb 2yHtFaMSm34SDpwdKreUqVOVEZuYKoTRmH01IjXUi0L2EJvay1eQ0n/WNzRR/R/M 4+ouubA8kWsunqNgLagTCp/KU1kgZpRREIvfI3vKylRU8GaQM1+d6Mg7EbEOI2Cf o9mvkB/MnC0= =1aAH -END PGP SIGNATURE End Message ---
Bug#966812: marked as done (keepass2: Keepass2 crashes at startup after system update)
Your message dated Mon, 3 Aug 2020 17:31:33 +0200 with message-id <67a5f2c1-1415-e09a-5e5f-e9caecb76...@googlemail.com> and subject line Re: Bug#966812: keepass2: Keepass2 crashes at startup after system update has caused the Debian Bug report #966812, regarding keepass2: Keepass2 crashes at startup after system update to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: keepass2 Version: 2.45+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, After update my system packages, keepas2 stops working. It simply crashes at startup. Maybe is something related to libc6 with mono. I'm attaching the crash report below to check if the problem is with current keepass packages or it is something with mono runtime. Best regards, Adilson adilsond@r2d2:~$ keepass2 free(): double free detected in tcache 2 = Native Crash Reporting = Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. = = Native stacktrace: = 0x5609cf35fa15 - /usr/bin/cli : (null) 0x5609cf35fdac - /usr/bin/cli : (null) 0x5609cf30d605 - /usr/bin/cli : (null) 0x5609cf35efef - /usr/bin/cli : (null) 0x7fe6925bc140 - /lib/x86_64-linux-gnu/libpthread.so.0 : (null) 0x7fe692404cb1 - /lib/x86_64-linux-gnu/libc.so.6 : gsignal 0x7fe6923ee537 - /lib/x86_64-linux-gnu/libc.so.6 : abort 0x7fe692447728 - /lib/x86_64-linux-gnu/libc.so.6 : (null) 0x7fe69244ea1a - /lib/x86_64-linux-gnu/libc.so.6 : (null) 0x7fe692450015 - /lib/x86_64-linux-gnu/libc.so.6 : (null) 0x4179d31e - Unknown = Telemetry Dumper: = Pkilling 0x7fe67a30a700 from 0x7fe6923c4780 Could not exec mono-hang-watchdog, expected on path '/etc/../bin/mono-hang-watchdog' (errno 2) Pkilling 0x7fe679f08700 from 0x7fe6923c4780 Pkilling 0x7fe6794fe700 from 0x7fe6923c4780 Pkilling 0x7fe67a109700 from 0x7fe6923c4780 Pkilling 0x7fe679d07700 from 0x7fe6923c4780 Pkilling 0x7fe6792fd700 from 0x7fe6923c4780 Pkilling 0x7fe682803700 from 0x7fe6923c4780 Entering thread summarizer pause from 0x7fe6923c4780 Finished thread summarizer pause from 0x7fe6923c4780. Waiting for dumping threads to resume = External Debugger Dump: = [New LWP 9824] [New LWP 9825] [New LWP 9831] [New LWP 9832] [New LWP 9833] [New LWP 9834] [New LWP 9836] [New LWP 9837] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fe6924941c7 in wait4 () from /lib/x86_64-linux-gnu/libc.so.6 Id Target Id Frame * 1Thread 0x7fe6923c4780 (LWP 9823) "cli" 0x7fe6924941c7 in wait4 () from /lib/x86_64-linux-gnu/libc.so.6 2Thread 0x7fe684bff700 (LWP 9824) "SGen worker" 0x7fe6925b77b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 3Thread 0x7fe682803700 (LWP 9825) "Finalizer" 0x7fe6925ba174 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 4Thread 0x7fe67a30a700 (LWP 9831) "cli" 0x7fe6925bb1bf in accept () from /lib/x86_64-linux-gnu/libpthread.so.0 5Thread 0x7fe67a109700 (LWP 9832) "cli" 0x7fe6925b7ad8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 6Thread 0x7fe679f08700 (LWP 9833) "Thread Pool Wor" 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 7Thread 0x7fe679d07700 (LWP 9834) "Thread Pool Wor" 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 8Thread 0x7fe6794fe700 (LWP 9836) "Thread Pool Wor" 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 9
Bug#966575: Requested information about affected system (four disks, raid1, crypt)
Hi all, I just recovered my system (supermicro server) from this and thought I would share in case it is helpful. 1. Number of disks: 4 2. Filesystem setup This is a raid1 setup with crypted lvm. Grub is installed in MBR of /dev/sda # fdisk -l Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: Samsung SSD 850 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x953049db Device BootStart End Sectors Size Id Type /dev/sda1 *2048585727583680 285M fd Linux raid autodetect /dev/sda2 585728 39647231 39061504 18.6G fd Linux raid autodetect /dev/sda3 39647232 918552575 878905344 419.1G fd Linux raid autodetect Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10JPLX-00M Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x38784402 Device Boot StartEndSectors Size Id Type /dev/sdc12048 1953525167 1953523120 931.5G 83 Linux Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10JPLX-00M Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xa1da09f8 Device Boot StartEndSectors Size Id Type /dev/sdd12048 1953525167 1953523120 931.5G 83 Linux Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: Samsung SSD 850 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1efcfd6f Device BootStart End Sectors Size Id Type /dev/sdb1 *2048585727583680 285M fd Linux raid autodetect /dev/sdb2 585728 39647231 39061504 18.6G fd Linux raid autodetect /dev/sdb3 39647232 918552575 878905344 419.1G fd Linux raid autodetect Disk /dev/md0: 284.7 MiB, 298516480 bytes, 583040 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md2: 419 GiB, 449865318400 bytes, 878643200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md1: 18.6 GiB, 19982712832 bytes, 39028736 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md3: 931.4 GiB, 169595136 bytes, 1953260928 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mapper/md1_crypt: 18.6 GiB, 19980615680 bytes, 39024640 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/vg0-root: 9.3 GiB, 220736 bytes, 19529728 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/vg0-usr: 4.7 GiB, 4999610368 bytes, 9764864 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/vg0-var: 4.7 GiB, 4978638848 bytes, 9723904 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/md2_crypt: 419 GiB, 449863221248 bytes, 878639104 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes [bunch of lvms for vms] 3. History of the system I installed jessie on this server in 2015 and remotely upgraded to stretch and then to buster. # uname -a Linux X 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/Linux As with others, I was able to boot into d-i rescue mode and reinstall grub and then it booted fine. I hope this helps. It was definitely a surprise to find the server unbootable at 1am this morning! Thanks for all the work! -Devin
Bug#966475: marked as done (rspamd ftbfs with gcc-10)
Your message dated Mon, 03 Aug 2020 15:19:36 + with message-id and subject line Bug#966475: fixed in rspamd 2.5-3 has caused the Debian Bug report #966475, regarding rspamd ftbfs with gcc-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rspamd Version: 2.5-2 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy ubuntu-patch Dear maintainers, In Ubuntu, we've found that rspamd fails to build from source with the current toolchain due to a missing C++ include file. The attached patch fixes the build failure in unstable. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru rspamd-2.5/debian/patches/gcc10-ftbfs.patch rspamd-2.5/debian/patches/gcc10-ftbfs.patch --- rspamd-2.5/debian/patches/gcc10-ftbfs.patch 1969-12-31 16:00:00.0 -0800 +++ rspamd-2.5/debian/patches/gcc10-ftbfs.patch 2020-07-28 16:51:48.0 -0700 @@ -0,0 +1,16 @@ +Description: fix ftbfs with gcc 10 due to missing C++ header include +Author: Steve Langasek +Last-Update: 2020-07-28 + +Index: rspamd-2.5/contrib/replxx/src/io.cxx +=== +--- rspamd-2.5.orig/contrib/replxx/src/io.cxx rspamd-2.5/contrib/replxx/src/io.cxx +@@ -3,6 +3,7 @@ + #include + #include + #include ++#include + + #ifdef _WIN32 + diff -Nru rspamd-2.5/debian/patches/series rspamd-2.5/debian/patches/series --- rspamd-2.5/debian/patches/series2020-05-01 07:40:43.0 -0700 +++ rspamd-2.5/debian/patches/series2020-07-28 16:49:55.0 -0700 @@ -3,3 +3,4 @@ 0004-drop-js-scripts-packaged-by-Debian.patch 0006-do-not-install-fonts-packaged-by-Debian.patch 0007-license-problem-convert-utf-code.patch +gcc10-ftbfs.patch --- End Message --- --- Begin Message --- Source: rspamd Source-Version: 2.5-3 Done: Sebastien Badia We believe that the bug you reported is fixed in the latest version of rspamd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Badia (supplier of updated rspamd 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, 03 Aug 2020 16:56:40 +0200 Source: rspamd Architecture: source Version: 2.5-3 Distribution: unstable Urgency: medium Maintainer: Sebastien Badia Changed-By: Sebastien Badia Closes: 966475 Changes: rspamd (2.5-3) unstable; urgency=medium . * d/patches: + Fix ftbfs with gcc 10, Thanks Steve (Closes: #966475) + Added forwarded tags (according new lintian checks) Checksums-Sha1: 4bf8e87e514b8172627dd09d4352045d8cfa7775 2324 rspamd_2.5-3.dsc 9a155a47d4e3824d5154a124a197984a01fdfa52 240808 rspamd_2.5-3.debian.tar.xz 58da19acc3df980c58a52284a8e5eee03790d509 6362 rspamd_2.5-3_source.buildinfo Checksums-Sha256: 12ca9959e51092ab0c05948978a899f91b9aae8e0354502d8f747639a3e68594 2324 rspamd_2.5-3.dsc 319e7155ac2db4ccd0fc98ada5bb37d2c0be7b16d7248f582043855e12bfc9c5 240808 rspamd_2.5-3.debian.tar.xz a7b0515f0c43446f8e0d02240e4700e5df48677468c7674d6aac69c930911d2d 6362 rspamd_2.5-3_source.buildinfo Files: 282a7bd5231d8c794de5196a754c8b92 2324 mail optional rspamd_2.5-3.dsc 113f2196a69b3d3eacc2e9f63d85b863 240808 mail optional rspamd_2.5-3.debian.tar.xz db7c9e72f476234e377c261ec1edd56f 6362 mail optional rspamd_2.5-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAl8oJ2UACgkQhxbORhSk UtjXvQ/+PQGYfKiWnaUe5dR6JCix0/VU1rCHilVl71gz2rh9xeeO6WJUxl6mwL0L hUEcfBG51utO163ANCoMlu1DPp1y475uaZdclNY5KGVOjdLG9Paepu/fNj/thPM4 QsnWK5v4tHZOk0Jiltv3X/gGF20C7Li/fErocrFkEUHt3tlA5STYlfifwJOJRinA wvJj33wca/wLVvnCaroqZmpDYXJsjdlTeDsmDxPydMa38UdEbg9i432UqWNt+ADi
Bug#966953: marked as done (qttools-opensource-src: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 03 Aug 2020 15:19:30 +
with message-id
and subject line Bug#966953: fixed in qttools-opensource-src 5.14.2-3
has caused the Debian Bug report #966953,
regarding qttools-opensource-src: FTBFS: dpkg-gensymbols: error: some symbols
or patterns disappeared in the symbols file: see diff output below
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.)
--
966953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qttools-opensource-src
Version: 5.14.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_missing --fail-missing
> make[1]: Leaving directory '/<>'
>dh_dwz
>dh_strip
>dh_makeshlibs
> dpkg-gensymbols: warning: debian/libqt5designer5/DEBIAN/symbols doesn't match
> completely debian/libqt5designer5.symbols
> --- debian/libqt5designer5.symbols (libqt5designer5_5.14.2-2_amd64)
> +++ dpkg-gensymbolsdj0GkM 2020-08-02 17:15:03.012823459 +
> @@ -2482,8 +2482,8 @@
> _ZN8DomSlots4readER16QXmlStreamReader@Qt_5 5.6.0~beta
> _ZN8DomSlotsD1Ev@Qt_5 5.6.0~beta
> _ZN8DomSlotsD2Ev@Qt_5 5.6.0~beta
> -
> (optional=templinst)_ZN8QVariant8setValueIN18qdesigner_internal22PropertySheetEnumValueEEEvRKT_@Qt_5
> 5.14.1
> -
> (optional=templinst)_ZN8QVariant8setValueIN18qdesigner_internal22PropertySheetFlagValueEEEvRKT_@Qt_5
> 5.14.1
> +#MISSING: 5.14.2-2#
> (optional=templinst)_ZN8QVariant8setValueIN18qdesigner_internal22PropertySheetEnumValueEEEvRKT_@Qt_5
> 5.14.1
> +#MISSING: 5.14.2-2#
> (optional=templinst)_ZN8QVariant8setValueIN18qdesigner_internal22PropertySheetFlagValueEEEvRKT_@Qt_5
> 5.14.1
> _ZN9DomAction18setElementPropertyERK5QListIP11DomPropertyE@Qt_5 5.6.0~beta
> _ZN9DomAction19setElementAttributeERK5QListIP11DomPropertyE@Qt_5 5.6.0~beta
> _ZN9DomAction4readER16QXmlStreamReader@Qt_5 5.6.0~beta
> @@ -3195,8 +3195,8 @@
> _ZNK9DomSpacer5writeER16QXmlStreamWriterRK7QString@Qt_5 5.6.0~beta
> _ZNK9DomString5writeER16QXmlStreamWriterRK7QString@Qt_5 5.6.0~beta
> _ZNK9DomWidget5writeER16QXmlStreamWriterRK7QString@Qt_5 5.6.0~beta
> -
> (optional=templinst)_ZNSt3_V28__rotateIPiEET_S2_S2_S2_St26random_access_iterator_tag@Qt_5
> 5.6.0~beta
> -
> (optional=templinst|subst)_ZSt17__rotate_adaptiveIPiS0_{ssize_t}ET_S1_S1_S1_T1_S2_T0_S2_@Qt_5
> 5.6.0~beta
> +#MISSING: 5.14.2-2#
> (optional=templinst)_ZNSt3_V28__rotateIPiEET_S2_S2_S2_St26random_access_iterator_tag@Qt_5
> 5.6.0~beta
> +#MISSING: 5.14.2-2#
> (optional=templinst|subst)_ZSt17__rotate_adaptiveIPiS0_{ssize_t}ET_S1_S1_S1_T1_S2_T0_S2_@Qt_5
> 5.6.0~beta
> (optional=templinst|arch=armel armhf hurd-i386 i386 kfreebsd-i386 m68k mips
> mipsel powerpc
> powerpcspe)_ZSt4swapIN8QVariant7PrivateEENSt9enable_ifIXsrSt6__and_IJSt6__not_ISt15__is_tuple_likeIT_EESt21is_move_constructibleIS6_ESt18is_move_assignableIS6_EEE5valueEvE4typeERS6_SG_@Qt_5
> 5.9.1
> _ZTI12QFormBuilder@Qt_5 5.6.0~beta
> _ZTI12QTextBuilder@Qt_5 5.6.0~beta
> dpkg-gensymbols: warning: debian/libqt5designercomponents5/DEBIAN/symbols
> doesn't match completely debian/libqt5designercomponents5.symbols
> --- debian/libqt5designercomponents5.symbols
> (libqt5designercomponents5_5.14.2-2_amd64)
> +++ dpkg-gensymbolsq329Wk 2020-08-02 17:15:03.260822356 +
> @@ -11,7 +11,7 @@
>
> _ZN19QDesignerComponents20createResourceEditorEP28QDesignerFormEditorInterfaceP7QWidget@Qt_5_PRIVATE_API
> 5.6.0~beta
>
> _ZN19QDesignerComponents21createObjectInspectorEP28QDesignerFormEditorInterfaceP7QWidget@Qt_5_PRIVATE_API
> 5.6.0~beta
>
> _ZN19QDesignerComponents22createSignalSlotEditorEP28QDesignerFormEditorInterfaceP7QWidget@Qt_5_PRIVATE_API
> 5.6.0~beta
> - (optional=templinst|arch=amd64 arm64 mips64el ppc64 ppc64el s390x
> sparc64)_ZN8QVariant8setValueI8QPaletteEEvRKT_@Qt_5_PRIVATE_API 5.14.1
> +#MISSING: 5.14.2-2# (optional=templinst|arch=amd64 arm64 mips64el ppc64
> ppc64el s390x sparc64)_ZN8QVariant8setValueI8QPaletteEEvRKT_@Qt_5_PRIVATE_API
> 5.14.1
> (optional=templinst|arch=!amd64 !arm64 !armel !armhf !i386 !mipsel
> !powerpc)_ZN8QVariant8setValueIN18qdesigner_internal22PropertySheetEnumValueEEEvRKT_@Qt_5_PRIVATE_API
> 5.14.1
> (optional=templinst|arch=armel armhf hurd-i386 i386 kfreebsd-i386 m68k mips
> mipsel powerpc
>
Bug#966475: rspamd ftbfs with gcc-10
On Tue, Jul 28, 2020 at 05:48:23PM (-0700), Steve Langasek wrote: > Package: rspamd > Version: 2.5-2 > Severity: serious > Tags: patch > Justification: ftbfs > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu groovy ubuntu-patch > > Dear maintainers, > > In Ubuntu, we've found that rspamd fails to build from source with the > current toolchain due to a missing C++ include file. The attached patch > fixes the build failure in unstable. Hello Steve, Many thanks for this patch/follow-up, 2.5-3 just uploaded. Have a good day, Seb signature.asc Description: PGP signature
Bug#967010: apache2: last debian 10.4 , last apache avail from repo hangs on install (and start phase)
Package: apache2 Version: 2.4.38-3+deb10u3 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? package installing * What exactly did you do (or not do) that was effective (or ineffective)? apt-get install apache2 * What was the outcome of this action? packages did not start * What outcome did you expect instead? packages will start ok I have fresh debian 10 install, OS after full upgrade with: `apt-get upgrade` and `apt-get dist-upgrade` I want to install apache2 packages, it hang on install (on post-install phase when apache starts): (*my findings why is below) apt-get install apache2 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apache2-bin apache2-data apache2-utils libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libbrotli1 libjansson4 liblua5.2-0 Suggested packages: apache2-doc apache2-suexec-pristine | apache2-suexec-custom The following NEW packages will be installed: apache2 apache2-bin apache2-data apache2-utils libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libbrotli1 libjansson4 liblua5.2-0 0 upgraded, 11 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/2,606 kB of archives. After this operation, 8,885 kB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package libapr1:amd64. (Reading database ... 85650 files and directories currently installed.) Preparing to unpack .../00-libapr1_1.6.5-1+b1_amd64.deb ... Unpacking libapr1:amd64 (1.6.5-1+b1) ... Selecting previously unselected package libaprutil1:amd64. Preparing to unpack .../01-libaprutil1_1.6.1-4_amd64.deb ... Unpacking libaprutil1:amd64 (1.6.1-4) ... Selecting previously unselected package libaprutil1-dbd-sqlite3:amd64. Preparing to unpack .../02-libaprutil1-dbd-sqlite3_1.6.1-4_amd64.deb ... Unpacking libaprutil1-dbd-sqlite3:amd64 (1.6.1-4) ... Selecting previously unselected package libaprutil1-ldap:amd64. Preparing to unpack .../03-libaprutil1-ldap_1.6.1-4_amd64.deb ... Unpacking libaprutil1-ldap:amd64 (1.6.1-4) ... Selecting previously unselected package libbrotli1:amd64. Preparing to unpack .../04-libbrotli1_1.0.7-2_amd64.deb ... Unpacking libbrotli1:amd64 (1.0.7-2) ... Selecting previously unselected package libjansson4:amd64. Preparing to unpack .../05-libjansson4_2.12-1_amd64.deb ... Unpacking libjansson4:amd64 (2.12-1) ... Selecting previously unselected package liblua5.2-0:amd64. Preparing to unpack .../06-liblua5.2-0_5.2.4-1.1+b2_amd64.deb ... Unpacking liblua5.2-0:amd64 (5.2.4-1.1+b2) ... Selecting previously unselected package apache2-bin. Preparing to unpack .../07-apache2-bin_2.4.38-3+deb10u3_amd64.deb ... Unpacking apache2-bin (2.4.38-3+deb10u3) ... Selecting previously unselected package apache2-data. Preparing to unpack .../08-apache2-data_2.4.38-3+deb10u3_all.deb ... Unpacking apache2-data (2.4.38-3+deb10u3) ... Selecting previously unselected package apache2-utils. Preparing to unpack .../09-apache2-utils_2.4.38-3+deb10u3_amd64.deb ... Unpacking apache2-utils (2.4.38-3+deb10u3) ... Selecting previously unselected package apache2. Preparing to unpack .../10-apache2_2.4.38-3+deb10u3_amd64.deb ... Unpacking apache2 (2.4.38-3+deb10u3) ... Setting up libbrotli1:amd64 (1.0.7-2) ... Setting up libapr1:amd64 (1.6.5-1+b1) ... Setting up libjansson4:amd64 (2.12-1) ... Setting up liblua5.2-0:amd64 (5.2.4-1.1+b2) ... Setting up apache2-data (2.4.38-3+deb10u3) ... Setting up libaprutil1:amd64 (1.6.1-4) ... Setting up libaprutil1-ldap:amd64 (1.6.1-4) ... Setting up libaprutil1-dbd-sqlite3:amd64 (1.6.1-4) ... Setting up apache2-utils (2.4.38-3+deb10u3) ... Setting up apache2-bin (2.4.38-3+deb10u3) ... Setting up apache2 (2.4.38-3+deb10u3) ... Enabling module mpm_event. Enabling module authz_core. Enabling module authz_host. Enabling module authn_core. Enabling module auth_basic. Enabling module access_compat. Enabling module authn_file. Enabling module authz_user. Enabling module alias. Enabling module dir. Enabling module autoindex. Enabling module env. Enabling module mime. Enabling module negotiation. Enabling module setenvif. Enabling module filter. Enabling module deflate. Enabling module status. Enabling module reqtimeout. Enabling conf charset. Enabling conf localized-error-pages. Enabling conf other-vhosts-access-log. Enabling conf security. Enabling conf serve-cgi-bin. Enabling site 000-default. Created symlink /etc/systemd/system/multi-user.target.wants/apache2.service → /etc/systemd/system/apache2.service. Created symlink /etc/systemd/system/multi-user.target.wants/apache-htcacheclean.service → /lib/systemd/system/apache-htcacheclean.service. here it hangs. and after some time Job for apache2.service failed because a timeout was exceeded. See "systemctl status apache2.service" and "journalctl -xe" for details. invoke-rc.d:
Bug#967041: marked as done (Please build without lablgtksourceview2)
Your message dated Mon, 03 Aug 2020 15:03:57 + with message-id and subject line Bug#967041: fixed in lablgtk-extras 1.6-2 has caused the Debian Bug report #967041, regarding Please build without lablgtksourceview2 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.) -- 967041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lablgtk-extras Version: 1.6-1 Severity: serious Tags: upstream Dear Maintainer, Please port lablgtk-extras to lablgtk3. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911166 . Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: lablgtk-extras Source-Version: 1.6-2 Done: =?utf-8?q?St=C3=A9phane_Glondu?= We believe that the bug you reported is fixed in the latest version of lablgtk-extras, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated lablgtk-extras 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, 03 Aug 2020 16:51:22 +0200 Source: lablgtk-extras Architecture: source Version: 1.6-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 967041 Changes: lablgtk-extras (1.6-2) unstable; urgency=medium . * Build without lablgtksourceview2 (Closes: #967041) * Bump debhelper compat level to 13 * Bump Standards-Version to 4.5.0 Checksums-Sha1: 0fc550abb3d6f87c9e27ffd55bedcaff0e723973 1963 lablgtk-extras_1.6-2.dsc d7400da36f7d555cf79eb27bd009946a30f722ad 3640 lablgtk-extras_1.6-2.debian.tar.xz Checksums-Sha256: c0a5929dc3f2cde29139087c2e7975ef4923ab6004ee9c7a88e9860c17a9e246 1963 lablgtk-extras_1.6-2.dsc 81b3bc926e4a48a0a812419c37f24353b44df0930057a6d85f5e960a5c7ba256 3640 lablgtk-extras_1.6-2.debian.tar.xz Files: c5ac06446fb963fce7c77b4b2fa8c4da 1963 ocaml optional lablgtk-extras_1.6-2.dsc 7111f2c2de82d993f9eda2ad90f229ea 3640 ocaml optional lablgtk-extras_1.6-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl8oJJ8ACgkQIbju8bGJ MIH6TAgAqotvQTVP9r/RC2g92xlxt6u4O6Jya8GoGX2EwIjbkkWvgg2KKKdYGnMo 62NDo/rgCqbJup391izVDa227I4bSZ/+1qiixALuB9ITih6mUMHS9pQaozDwwW6c LAZ8/aGb8Ho1+e/MrYTTx467OL+NKa0uzM9/kJkNcLgtmEqJ+RFOlWoQTl5hL/Eb 9ECC8Mi3sKMhGovxb96Sg3W6b1KHclxP+ozXT+bFsNG1hElJLL09n2kbtXzGG+sk ChiiICRfLpmn5WPc+ZsfzSkTNZ37vdG3oWCCA7O77wRtsJM7zEjbZDL5fz8hoJX4 3TZnARC4RNEmY9IMbTr+njQjJ9nn9w== =vJki -END PGP SIGNATURE End Message ---
Bug#967041: marked as pending in lablgtk-extras
Control: tag -1 pending Hello, Bug #967041 in lablgtk-extras reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ocaml-team/lablgtk-extras/-/commit/253e8fea2afde4e797616fd2860e166e0b800f7b Build without lablgtksourceview2 (Closes: #967041) (this message was generated automatically) -- Greetings https://bugs.debian.org/967041
Processed: Bug#967041 marked as pending in lablgtk-extras
Processing control commands: > tag -1 pending Bug #967041 [src:lablgtk-extras] Please build without lablgtksourceview2 Added tag(s) pending. -- 967041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [request-tracker-maintainers] Bug#967017: request-tracker4: FTBFS: can't exec /usr/bin/gpg
Processing control commands: > retitle -1 request-tracker4: FTBFS: GPG test failures Bug #967017 [src:request-tracker4] request-tracker4: FTBFS: missing dependencies Changed Bug title to 'request-tracker4: FTBFS: GPG test failures' from 'request-tracker4: FTBFS: missing dependencies'. -- 967017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966812: keepass2: Keepass2 crashes at startup after system update
Em seg., 3 de ago. de 2020 às 06:15, Adrian Bunk escreveu: > On Sun, Aug 02, 2020 at 02:15:53PM -0300, Adilson dos Santos Dantas wrote: > > Package: keepass2 > > Version: 2.45+dfsg-1 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > After update my system packages, keepas2 stops working. It simply > crashes at > > startup. Maybe is something related to libc6 with mono. I'm attaching > the crash > > report below to check if the problem is with current keepass packages or > it is > > something with mono runtime. > >... > > Versions of packages keepass2 depends on: > >... > > ii libx11-6 2:1.6.10-1 > >... > > Does upgrading libx11-6 to 2:1.6.10-3 fix your problem? > Yes, it does. I tested it with two machines now and it stopped crashing after libx11-6 upgrade. Thank you! > > cu > Adrian > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#967017: [request-tracker-maintainers] Bug#967017: request-tracker4: FTBFS: can't exec /usr/bin/gpg
Control: retitle -1 request-tracker4: FTBFS: GPG test failures On Mon, Aug 03, 2020 at 02:05:16PM +0200, Lucas Nussbaum wrote: > Source: request-tracker4 > Version: 4.4.4-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200802 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Relevant log extract is [18290] [Sun Aug 2 17:07:59 2020] [warning]: Can't exec "/usr/bin/gpg": No such file or directory at /usr/share/perl5/GnuPG/Interface.pm line 349. (/<>/lib/RT/Test.pm:716) exec() error: No such file or directory at /usr/share/perl5/GnuPG/Interface.pm line 349. BEGIN failed--compilation aborted at t/crypt/gnupg/attachments-in-db.t line 10. [18287] [Sun Aug 2 17:07:59 2020] [warning]: Use of uninitialized value $line in pattern match (m//) at /usr/share/perl5/GnuPG/Interface.pm line 822. (/<>/lib/RT/Test.pm:716) [18287] [Sun Aug 2 17:07:59 2020] [warning]: Use of uninitialized value $a in split at /usr/share/perl5/GnuPG/Interface.pm line 836. (/<>/lib/RT/Test.pm:716) [18287] [Sun Aug 2 17:07:59 2020] [warning]: Use of uninitialized value $a in split at /usr/share/perl5/GnuPG/Interface.pm line 836. (/<>/lib/RT/Test.pm:716) GnuPG Version 1.4 or 2.2+ required at /<>/lib/RT/Crypt/GnuPG.pm line 1851. BEGIN failed--compilation aborted at t/crypt/gnupg/attachments-in-db.t line 10. ... This seems related to changes in libgnupg-interface-perl, which on the face of it is ignoring the instruction to use 'gpg1' (configured via the test_gnupg_interface_gpg1.diff patch). I can't immediately see why that's happening but it seems related to the recent changes libgnupg-interface-perl. Andrew, any clues? Dominic.
Bug#966990: marked as done (xidle: FTBFS: env: ‘pmake’: No such file or directory)
Your message dated Mon, 3 Aug 2020 14:38:33 + (UTC) with message-id and subject line Re: Bug#966990: xidle: FTBFS: env: ‘pmake’: No such file or directory has caused the Debian Bug report #966990, regarding xidle: FTBFS: env: ‘pmake’: 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.) -- 966990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xidle Version: 20161031 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh_testdir > env LC_ALL=C CC='cc' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2 ' CFLAGS='-g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wextra -Wformat' LDFLAGS='-Wl,-z,relro > -Wl,-z,now -Wl,--as-needed' pmake NOGCCERROR=1 cleandir > env: ‘pmake’: No such file or directory > make: *** [debian/rules:41: clean] Error 127 The full build log is available from: http://qa-logs.debian.net/2020/08/02/xidle_20161031_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 20200802 >During a rebuild of all packages in sid, your package failed to build Already seen and fixed yesterday. This was caused by #966824 in pmake, but due to the recent bmake incompatibility changes I had to touch the build system anyway and took the chance to update everything. Thanks anyway, //mirabilos -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (389 (415) bugs: 1 RC, 264 (283) I, 124 (131) M, 0 F) ‣ src:dash (90 (105) bugs: 0 RC, 48 (52) I, 42 (53) M, 0 F) ‣ src:mksh (0 bugs: 0 RC, 0 I, 0 M, 0 F) dash has two RC bugs they just closed because they don’t care about quality…--- End Message ---
Bug#967007: Now dependencies are satisfied
Once ruby-webpacker and ruby-webdrivers clears NEW creating new rails app will work. Now some tests for the newly created app fails. I think running rails webpacker:install will fix it. + rake test /usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:115: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filters/node_filter.rb:9: warning: The called method `initialize' is defined here /usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:19: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:111: warning: The called method `add_filter' is defined here /usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:115: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filters/base.rb:7: warning: The called method `initialize' is defined here /usr/lib/ruby/vendor_ruby/capybara/selector/selector.rb:361: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filters/locator_filter.rb:9: warning: The called method `initialize' is defined here /usr/lib/ruby/vendor_ruby/capybara/selector/filters/locator_filter.rb:10: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filters/node_filter.rb:9: warning: The called method `initialize' is defined here DEPRECATION WARNING: Single arity template handlers are deprecated. Template handlers must now accept two parameters, the view object and the source for the view object. Change: >> JbuilderHandler.call(template) To: >> JbuilderHandler.call(template, source) (called from block (2 levels) in at /usr/lib/ruby/vendor_ruby/jbuilder/railtie.rb:8) RAILS_ENV=test environment is not defined in config/webpacker.yml, falling back to production environment /usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:115: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filters/node_filter.rb:9: warning: The called method `initialize' is defined here /usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:19: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:111: warning: The called method `add_filter' is defined here /usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:115: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filters/base.rb:7: warning: The called method `initialize' is defined here /usr/lib/ruby/vendor_ruby/capybara/selector/selector.rb:361: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filters/locator_filter.rb:9: warning: The called method `initialize' is defined here /usr/lib/ruby/vendor_ruby/capybara/selector/filters/locator_filter.rb:10: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/lib/ruby/vendor_ruby/capybara/selector/filters/node_filter.rb:9: warning: The called method `initialize' is defined here DEPRECATION WARNING: Single arity template handlers are deprecated. Template handlers must now accept two parameters, the view object and the source for the view object. Change: >> JbuilderHandler.call(template) To: >> JbuilderHandler.call(template, source) (called from block (2 levels) in at /usr/lib/ruby/vendor_ruby/jbuilder/railtie.rb:8) RAILS_ENV=test environment is not defined in config/webpacker.yml, falling back to production environment Run options: --seed 61677 # Running: ...E Error: ProductsControllerTest#test_should_get_edit: ActionView::Template::Error: Webpacker configuration file not found /tmp/autopkgtest-lxc.60lhwj6z/downtmp/autopkgtest_tmp/foo/config/webpacker.yml. Please run rails webpacker:install Error: No such file or directory @ rb_sysopen - /tmp/autopkgtest-lxc.60lhwj6z/downtmp/autopkgtest_tmp/foo/config/webpacker.yml app/views/layouts/application.html.erb:9 test/controllers/products_controller_test.rb:32:in `block in ' rails test test/controllers/products_controller_test.rb:31 E Error: ProductsControllerTest#test_should_get_new: ActionView::Template::Error: Webpacker configuration file not found /tmp/autopkgtest-lxc.60lhwj6z/downtmp/autopkgtest_tmp/foo/config/webpacker.yml. Please run rails webpacker:install Error: No such file or directory @ rb_sysopen -
Processed: forcibly merging 966763 967043
Processing commands for cont...@bugs.debian.org: > forcemerge 966763 967043 Bug #966763 [src:mod-wsgi] mod-wsgi: Unversioned Python removal in sid/bullseye Bug #967043 [src:mod-wsgi] mod-wsgi: Unversioned Python removal in sid/bullseye Merged 966763 967043 > thanks Stopping processing here. Please contact me if you need assistance. -- 966763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966763 967043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957597: marked as done (netkit-ftp-ssl: ftbfs with GCC-10)
Your message dated Mon, 03 Aug 2020 14:35:16 + with message-id and subject line Bug#957597: fixed in netkit-ftp-ssl 0.17.34+0.2-5 has caused the Debian Bug report #957597, regarding netkit-ftp-ssl: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:netkit-ftp-ssl Version: 0.17.34+0.2-4.1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/netkit-ftp-ssl_0.17.34+0.2-4.1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_SYSCONFDIR -- Build files have been written to: /<>/obj-x86_64-linux-gnu dh_auto_build -O--buildsystem=cmake cd obj-x86_64-linux-gnu && make -j4 make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f ftp/CMakeFiles/ftp-ssl.dir/build.make ftp/CMakeFiles/ftp-ssl.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/ftp /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/ftp /<>/obj-x86_64-linux-gnu/ftp/CMakeFiles/ftp-ssl.dir/DependInfo.cmake --color= Scanning dependencies of target ftp-ssl make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f ftp/CMakeFiles/ftp-ssl.dir/build.make ftp/CMakeFiles/ftp-ssl.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 28%] Building C object ftp/CMakeFiles/ftp-ssl.dir/cmds.c.o [ 28%] Building C object ftp/CMakeFiles/ftp-ssl.dir/ftp.c.o [ 57%] Building C object ftp/CMakeFiles/ftp-ssl.dir/cmdtab.c.o [ 57%] Building C object ftp/CMakeFiles/ftp-ssl.dir/domacro.c.o cd /<>/obj-x86_64-linux-gnu/ftp && /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D__USE_EDITLINE__ -DUSE_SSL -DBUILD_SSL_CLIENT -o CMakeFiles/ftp-ssl.dir/ftp.c.o -c /<>/ftp/ftp.c cd /<>/obj-x86_64-linux-gnu/ftp && /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D__USE_EDITLINE__ -DUSE_SSL -DBUILD_SSL_CLIENT -o CMakeFiles/ftp-ssl.dir/cmds.c.o -c /<>/ftp/cmds.c cd /<>/obj-x86_64-linux-gnu/ftp && /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D__USE_EDITLINE__ -DUSE_SSL -DBUILD_SSL_CLIENT -o CMakeFiles/ftp-ssl.dir/domacro.c.o -c /<>/ftp/domacro.c cd /<>/obj-x86_64-linux-gnu/ftp && /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D__USE_EDITLINE__ -DUSE_SSL -DBUILD_SSL_CLIENT -o CMakeFiles/ftp-ssl.dir/cmdtab.c.o
Processed: Bug#967032 marked as pending in nodejs
Processing control commands: > tag -1 pending Bug #967032 [src:nodejs] nodejs: Unversioned Python removal in sid/bullseye Added tag(s) pending. -- 967032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967032: marked as pending in nodejs
Control: tag -1 pending Hello, Bug #967032 in nodejs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/nodejs/-/commit/c4ac95d66030edd3c98d8ff389da73b66a732378 B-D python3 (Closes: #967032) (this message was generated automatically) -- Greetings https://bugs.debian.org/967032
Processed: unblock 911166 with 966595, bug 967041 is not forwarded
Processing commands for cont...@bugs.debian.org: > unblock 911166 with 966595 Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Bullseye 911166 was blocked by: 885685 885675 885678 911164 890456 911167 885681 885677 885676 967041 966595 911166 was not blocking any bugs. Removed blocking bug(s) of 911166: 966595 > notforwarded 967041 Bug #967041 [src:lablgtk-extras] Please build without lablgtksourceview2 Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 911166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911166 967041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 966853 is forwarded to https://github.com/gophernicus/gophernicus/issues/80
Processing commands for cont...@bugs.debian.org: > forwarded 966853 https://github.com/gophernicus/gophernicus/issues/80 Bug #966853 [src:gophernicus] gophernicus: FTBFS: ld: file.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here Set Bug forwarded-to-address to 'https://github.com/gophernicus/gophernicus/issues/80'. > thanks Stopping processing here. Please contact me if you need assistance. -- 966853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: mark the dnscache poisoning attack as fixed
Processing commands for cont...@bugs.debian.org: > package djbdns Limiting to bugs with field 'package' containing at least one of 'djbdns' Limit currently set to 'package':'djbdns' > fixed 516394 1:1.05-10 Bug #516394 [djbdns] [security]: Rapid DNS Poisoning in dnscache There is no source info for the package 'djbdns' at version '1:1.05-10' with architecture '' Unable to make a source version for version '1:1.05-10' Marked as fixed in versions 1:1.05-10. > thanks Stopping processing here. Please contact me if you need assistance. -- 516394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 966595, severity of 966595 is important
Processing commands for cont...@bugs.debian.org: > tags 966595 - ftbfs Bug #966595 [src:lablgtk-extras] Please port to lablgtk3 Removed tag(s) ftbfs. > severity 966595 important Bug #966595 [src:lablgtk-extras] Please port to lablgtk3 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 966595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967043: mod-wsgi: Unversioned Python removal in sid/bullseye
Package: src:mod-wsgi Version: 4.6.8-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned see https://ci.debian.net/data/autopkgtest/testing/amd64/m/mod-wsgi/6517578/log.gz Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list.
Processed: ITP: ruby-webdrivers -- Easy download and use of browser drivers
Processing control commands: > block 967007 by -1 Bug #967007 [rails] rails: package new gem dependencies for autopkgtests 967007 was blocked by: 930918 967031 967007 was not blocking any bugs. Added blocking bug(s) of 967007: 967042 -- 967007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967007 967042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cloning 966595, retitle -1 to Please build without lablgtksourceview2
Processing commands for cont...@bugs.debian.org: > clone 966595 -1 Bug #966595 [src:lablgtk-extras] Please port to lablgtk3 Bug 966595 cloned as bug 967041 911166 was blocked by: 885681 890456 911167 885675 885676 885677 966595 885685 911164 885678 911166 was not blocking any bugs. Added blocking bug(s) of 911166: 967041 > retitle -1 Please build without lablgtksourceview2 Bug #967041 [src:lablgtk-extras] Please port to lablgtk3 Changed Bug title to 'Please build without lablgtksourceview2' from 'Please port to lablgtk3'. > thanks Stopping processing here. Please contact me if you need assistance. -- 911166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911166 966595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966595 967041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967040: abinit: Unversioned Python removal in sid/bullseye
Package: src:abinit Version: 8.10.3-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned see https://ci.debian.net/data/autopkgtest/testing/amd64/a/abinit/6517569/log.gz Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list.
Bug#967039: spamassassin: Unversioned Python removal in sid/bullseye
Package: src:spamassassin Version: 3.4.5~pre1-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned see https://ci.debian.net/data/autopkgtest/testing/amd64/s/spamassassin/6517590/log.gz Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list.
Bug#966922: libnitrokey: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
This is probably a result of a new GCC version. C++ symbols can be painful to manage. This will be trivial to update the next time I update the package. Scott K On August 3, 2020 9:15:16 AM UTC, Szczepan Zalega | Nitrokey wrote: >On 8/3/20 10:41 AM, Lucas Nussbaum wrote: >> (optional=templinst|arch=!amd64 !arm64 !x32) >> (optional=templinst) > >Hi! > >As far as I see the problem comes from the listing format difference, >not the actual symbol change. > >E.g.: >``` >- (optional=templinst|arch=!amd64 !arm64 >!x32)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE65ERKNS0_14DeviceResponseILS2_65ENS0_12EmptyPayload24status_translate_commandB5cxx11Ei@Base >3.5 >+ >(optional=templinst)_ZN8nitrokey5proto17ResponseDissectorILNS0_9CommandIDE65ERKNS0_14DeviceResponseILS2_65ENS0_12EmptyPayload24status_translate_commandB5cxx11Ei@Base >3.5 >```
Bug#516394: removal of djbdns ?
On Sun, Aug 02, 2020 at 10:28:04PM +0200, Moritz Mühlenhoff wrote: > Hi Peter, > > On Mon, Jul 27, 2020 at 05:20:23PM +0300, Peter Pentchev wrote: > > Now... related to that. I am not sure whether Moritz Muehlenhoff, when > > reopening this bug, was aware of the fact that Dmitry Bogatov included > > two patches from Jeff King that address the cache poisoning attack - > > and actually, the patches were mentioned in this bug log by Matija Nalis > > back in 2010. Moritz, is it possible that you had missed the inclusion > > of these two patches, or do you believe that they, by themselves, are > > still not enough to address this problem? If so, that would indeed be > > kind of unfortunate, since it is my impression that these particular > > patches are considered the best way to handle this among users of > > Prof. Bernstein's software. > > I only reopened the bug since there was a discussion on debian-devel about > the fact that bugs in removed-and-then-reintroduced packages don't get > automatically reopened and remembered that long-standing bug. The changelog > made by Dmitry Bogatov doesn't mention it either. If that specific bug is > believed to be fixed by these two patches, then I trust you on that. So > feel free to mark the bug as closed in 1:1.05-10, then. Thanks for your reply! Yes, I think I will do that, since IMHO the problem is indeed mitigated as much as possible by these patches. > The fact that djbdns has no active upstream is a different concern, though, > especially in the wake of the whole qmail disaster. Following it, Georgi > Guninski > raised a few issues on oss-security e.g. > (https://www.openwall.com/lists/oss-security/2020/06/01/1) and without an > active upstream noone ever addressed or investigated them. Ah, I wasn't aware of this thread, thanks for pointing it out! I will reply to his last message, since one of the problems is nonexistent and the other one is not really exploitable except in a very narrow, specific case (the "make a CDB file" routines are only used by the tools that create the tinydns/axfrdns/rbldns data files, they are never invoked with any network input, so the only problem scenario would be somebody, e.g. a hosting provider, using automated tools to create a CDB file that is very, very, very close to the 4 GB limit, and not noticing that the file is very close to the (well-documented) limit in time. But, yeah, I may look at other uses of alloc() in the djbdns source code... and I do kind of get your point in general, not about this specific case. I think that Prof. Bernstein considers djbdns to be feature-complete and bug-free, at least in his own understanding of both these terms; I think that if any really serious problems should appear, he will comment on them. Unfortunately, this leaves the maintainers of djbdns in the various packaging systems with the responsibility to evaluate and mitigate things that he does not really consider to be really serious problems, you are right about that. Well, all I can say is that I have really liked djbdns ever since it first came out (I was already using qmail, daemontools, and other pieces of Prof. Bernstein's software; I have since moved on to replacements for most of them, but I still find the djbdns command-line query tools easier to use in most cases, usually only falling back to a fully-fledged hundred-character dig command line), and I will try my best to keep it usable in Debian. Again, thanks for your work on this bug, both before and now, and sorry that this reply came out a bit longer than I intended... G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
