Processed: Re: Bug#998361: pam FTBFS
Processing control commands: > tags -1 + patch Bug #998361 [src:pam] pam FTBFS Added tag(s) patch. -- 998361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998361: pam FTBFS
Control: tags -1 + patch On Tue, Nov 02, 2021 at 10:11:40PM +0100, Johannes Schauer Marin Rodrigues wrote: > our CI runs for the DPKG_ROOT tests failed today because pam FTBFS. I > rebuilt pam locally in a fresh sbuild chroot without any modifications > and arrived at the same build failure. I attached the log. I also put > the error message at the end of this mail. Some investigation suggests > that for some reason PAM_USERTYPE_UIDMIN is set to the empty string by > configure. Also interestingly I was not able to reproduce this problem > by building the package outside of a chroot nor when building it under > mmdebstrap. The problem only shows when building it inside an sbuild > chroot. I thus suspect that it will also FTBFS on the buildds and mark > this bug as serious. I think this should be reproducible elsewhere. rebootstrap encounters it. It's a behaviour change in dash: if test x == x; then echo I am no longer executed with the new version; fi In any case, using == is never worked on dash. The attached patch fixes that bashism. Helmut --- pam-1.4.0.orig/configure.ac +++ pam-1.4.0/configure.ac @@ -658,19 +658,19 @@ dnl Get values for default uid ranges in login.defs used in pam_usertype dnl AC_ARG_WITH([uidmin], AS_HELP_STRING([--with-uidmin=],[default value for regular user min uid (1000)]), opt_uidmin=$withval) -if test x"$opt_uidmin" == x; then +if test x"$opt_uidmin" = x; then opt_uidmin=1000 fi AC_DEFINE_UNQUOTED(PAM_USERTYPE_UIDMIN, $opt_uidmin, [Minimum regular user uid.]) AC_ARG_WITH([sysuidmin], AS_HELP_STRING([--with-sysuidmin=],[default value for system user min uid (101)]), opt_sysuidmin=$withval) -if test x"$opt_sysuidmin" == x; then +if test x"$opt_sysuidmin" = x; then opt_sysuidmin=101 fi AC_DEFINE_UNQUOTED(PAM_USERTYPE_SYSUIDMIN, $opt_sysuidmin, [Minimum system user uid.]) AC_ARG_WITH([kerneloverflowuid], AS_HELP_STRING([--with-kernel-overflow-uid=],[kernel overflow uid, default (uint16_t)-2=65534]), opt_kerneloverflowuid=$withval) -if test x"$opt_kerneloverflowuid" == x; then +if test x"$opt_kerneloverflowuid" = x; then opt_kerneloverflowuid=65534 fi AC_DEFINE_UNQUOTED(PAM_USERTYPE_OVERFLOW_UID, $opt_kerneloverflowuid, [Kernel overflow uid.])
Bug#997031: marked as done (nvidia-cuda-gdb: cuda-gdb 'Segmentation fault' at startup if libpython2.7 is installed)
Your message dated Wed, 03 Nov 2021 05:08:37 + with message-id and subject line Bug#997031: fixed in nvidia-cuda-toolkit 11.3.1-5 has caused the Debian Bug report #997031, regarding nvidia-cuda-gdb: cuda-gdb 'Segmentation fault' at startup if libpython2.7 is installed 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.) -- 997031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvidia-cuda-gdb Version: 11.2.152~11.2.2-2~bpo10+1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (990, 'oldstable-updates'), (990, 'oldstable'), (500, 'oldoldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF8, LC_CTYPE=en_CA.UTF8 (charmap=UTF-8), LANGUAGE=en_CA.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nvidia-cuda-gdb depends on: ii libbabeltrace1 1.5.6-2+deb10u1 ii libc6 2.28-10 ii libexpat1 2.2.6-2+deb10u1 ii libgcc1 1:8.3.0-6 ii libipt2 2.0-2 ii liblzma55.2.4-1 ii libncursesw66.1+20181013-2+deb10u2 ii libpython3.73.7.3-2+deb10u3 ii libreadline77.0-5 ii libstdc++6 8.3.0-6 ii libtinfo6 6.1+20181013-2+deb10u2 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages nvidia-cuda-gdb recommends: ii nvidia-cuda-toolkit-doc 11.2.2-2~bpo10+1 nvidia-cuda-gdb suggests no packages. -- no debconf information (Upgrade from Buster unfortunately isn't possible until next summer, after the end of the academic Spring Term.) "gdb /usr/bin/cuda-gdb" and "strings /usr/bin/cuda-gdb" suggest that there's a hidden use of libpython2.7.so.1 which is failing. --- End Message --- --- Begin Message --- Source: nvidia-cuda-toolkit Source-Version: 11.3.1-5 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-cuda-toolkit, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-cuda-toolkit 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: Tue, 02 Nov 2021 18:01:18 +0100 Source: nvidia-cuda-toolkit Architecture: source Version: 11.3.1-5 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 995122 997031 Changes: nvidia-cuda-toolkit (11.3.1-5) unstable; urgency=medium . * cuda-gdb: Disable non-functional python support causing segmentation faults. (Closes: #997031) * Do not ship a spurious CMakeLists.txt below /usr/include/cuda. * Record upstream versions to detect non-monotonic cases. * Semi-automatically update version-prefixes in non-monotonic cases. * Symlink cuda.h into the shim tree /usr/lib/cuda. (Closes: #995122) * Update Lintian overrides. Checksums-Sha1: 7ec406f629af0b34fb498b5ed57fa46cd1d8278a 8637 nvidia-cuda-toolkit_11.3.1-5.dsc 9e80058c17c9f4b220cbb1e984223ca1ad6d6910 58596 nvidia-cuda-toolkit_11.3.1-5.debian.tar.xz 3b8fdb6c759bf265978a4a70818747ed5b23dd71 5859 nvidia-cuda-toolkit_11.3.1-5_source.buildinfo Checksums-Sha256: 88bff5fca741f9a732e219bac16483db206c8f1a79832307da3a5aff093b486b 8637 nvidia-cuda-toolkit_11.3.1-5.dsc 08ab4c1bb77a2a6d45574a4580b5c585dcc1d7e788e9f6bc02142a8acaee68e1 58596 nvidia-cuda-toolkit_11.3.1-5.debian.tar.xz 915e140df14e98fef09d0ef1fe7ca2b33d8726152ee241076fb804c92fc43e6e 5859 nvidia-cuda-toolkit_11.3.1-5_source.buildinfo Files: 521a1be4088800f0178213d1d700aab1 8637 non-free/libs optional nvidia-cuda-toolkit_11.3.1-5.dsc 6f442e8b1418be97d08cac8e0b3355b3 58596 non-free/libs optional nvidia-cuda-toolkit_11.3.1-5.debian.tar.xz cfabe5c3a76ff42acbcb982191796c5b 5859 non-free/libs optional nvidia-cuda-toolkit_11.3.1-5_source.buildinfo
Bug#997875: marked as done (astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions')
Your message dated Wed, 03 Nov 2021 04:03:43 + with message-id and subject line Bug#997875: fixed in astroid 2.8.4-1 has caused the Debian Bug report #997875, regarding astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions' 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.) -- 997875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: astroid Control: found -1 astroid/2.8.2-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Dear maintainer(s), With a recent upload of astroid the autopkgtest of pylint-flask fails in testing when that autopkgtest is run with the binary packages of astroid from unstable. It passes when run with only packages from testing. In tabular form: passfail astroidfrom testing2.8.2-1 pylint-flask from testing0.5-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Looking at the stack trace it seems to me that astroid is missing a dependency. Currently this regression is blocking the migration of astroid to testing [1]. Can you please investigate the situation and if I'm wrong reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=astroid https://ci.debian.net/data/autopkgtest/testing/amd64/p/pylint-flask/16213951/log.gz Testing with python3.9: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/pylint_flask/__init__.py", line 3, in from astroid import MANAGER File "/usr/lib/python3/dist-packages/astroid/__init__.py", line 51, in from astroid.nodes import node_classes, scoped_nodes File "/usr/lib/python3/dist-packages/astroid/nodes/__init__.py", line 27, in from astroid.nodes.node_classes import ( # pylint: disable=redefined-builtin (Ellipsis) File "/usr/lib/python3/dist-packages/astroid/nodes/node_classes.py", line 47, in from astroid import decorators, mixins, util File "/usr/lib/python3/dist-packages/astroid/decorators.py", line 36, in from typing_extensions import ParamSpec ModuleNotFoundError: No module named 'typing_extensions' autopkgtest [00:09:48]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: astroid Source-Version: 2.8.4-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of astroid, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated astroid 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: Tue, 02 Nov 2021 23:42:57 -0400 Source: astroid Architecture: source Version: 2.8.4-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 997875 Changes: astroid (2.8.4-1) unstable; urgency=medium . * New upstream release * debian/copyright - update upstream copyright info * debian/control - add typing-extensions to Depends; Closes: #997875 - bump Standards-Version to 4.6.0.1 (no changes needed) Checksums-Sha1: 4c29988f7cc469dc7379450dd38a90dd162470dc 2125 astroid_2.8.4-1.dsc 1cca44b3c9414384bd4512519ba551aa154a396c 301160 astroid_2.8.4.orig.tar.xz 9ccc8da999b91917d29f85e07e2589c53a763453 8660 astroid_2.8.4-1.debian.tar.xz 2d752e0e90de3f4c4c7aaf55a649a473ea997832 7028 astroid_2.8.4-1_source.buildinfo Checksums-Sha256: 494c5610ea8f3fb82b03db192c843251947fe1b104a1dc06d4b0c5c973b063a0 2125 astroid_2.8.4-1.dsc 99a6671a5991cba52cd98cf6b6545a2bb22cc3830acbcf23af9839cf461583f2 301160 astroid_2.8.4.orig.tar.xz 0cb28f058d49a13ce2708402328100df0054c6c1a7e53e9b541daf1b39491bae 8660 astroid_2.8.4-1.debian.tar.xz
Bug#997355: marked as done (pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions')
Your message dated Wed, 03 Nov 2021 04:03:43 + with message-id and subject line Bug#997875: fixed in astroid 2.8.4-1 has caused the Debian Bug report #997875, regarding pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions' 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.) -- 997875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pylint Version: 2.7.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > rm -f features.rst > PYTHONPATH=/<> python3 ./exts/pylint_features.py > Traceback (most recent call last): > File "/<>/doc/./exts/pylint_features.py", line 11, in > from pylint.lint import PyLinter > File "/<>/pylint/lint/__init__.py", line 75, in > from pylint.lint.parallel import check_parallel > File "/<>/pylint/lint/parallel.py", line 7, in > from pylint import reporters > File "/<>/pylint/reporters/__init__.py", line 24, in > from pylint import utils > File "/<>/pylint/utils/__init__.py", line 44, in > from pylint.utils.ast_walker import ASTWalker > File "/<>/pylint/utils/ast_walker.py", line 6, in > from astroid import nodes > File "/usr/lib/python3/dist-packages/astroid/__init__.py", line 51, in > > from astroid.nodes import node_classes, scoped_nodes > File "/usr/lib/python3/dist-packages/astroid/nodes/__init__.py", line 27, > in > from astroid.nodes.node_classes import ( # pylint: > disable=redefined-builtin (Ellipsis) > File "/usr/lib/python3/dist-packages/astroid/nodes/node_classes.py", line > 47, in > from astroid import decorators, mixins, util > File "/usr/lib/python3/dist-packages/astroid/decorators.py", line 36, in > > from typing_extensions import ParamSpec > ModuleNotFoundError: No module named 'typing_extensions' > make[2]: *** [Makefile:146: features.rst] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pylint_2.7.2-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: astroid Source-Version: 2.8.4-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of astroid, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated astroid 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: Tue, 02 Nov 2021 23:42:57 -0400 Source: astroid Architecture: source Version: 2.8.4-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 997875 Changes: astroid (2.8.4-1) unstable; urgency=medium . * New upstream release * debian/copyright - update upstream copyright info * debian/control - add typing-extensions to Depends; Closes: #997875 - bump Standards-Version to 4.6.0.1 (no changes needed) Checksums-Sha1: 4c29988f7cc469dc7379450dd38a90dd162470dc 2125 astroid_2.8.4-1.dsc 1cca44b3c9414384bd4512519ba551aa154a396c 301160 astroid_2.8.4.orig.tar.xz 9ccc8da999b91917d29f85e07e2589c53a763453 8660 astroid_2.8.4-1.debian.tar.xz 2d752e0e90de3f4c4c7aaf55a649a473ea997832 7028 astroid_2.8.4-1_source.buildinfo Checksums-Sha256: 494c5610ea8f3fb82b03db192c843251947fe1b104a1dc06d4b0c5c973b063a0 2125 astroid_2.8.4-1.dsc 99a6671a5991cba52cd98cf6b6545a2bb22cc3830acbcf23af9839cf461583f2 301160 astroid_2.8.4.orig.tar.xz 0cb28f058d49a13ce2708402328100df0054c6c1a7e53e9b541daf1b39491bae 8660
Processed: reassign 997355 to src:astroid, forcibly merging 997875 997355
Processing commands for cont...@bugs.debian.org: > reassign 997355 src:astroid Bug #997355 [astroid] pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions' Bug reassigned from package 'astroid' to 'src:astroid'. Ignoring request to alter found versions of bug #997355 to the same values previously set Ignoring request to alter fixed versions of bug #997355 to the same values previously set > forcemerge 997875 997355 Bug #997875 [src:astroid] astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions' Bug #997355 [src:astroid] pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions' Marked as found in versions astroid/2.8.2-1. Added tag(s) pending. Bug #997875 [src:astroid] astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions' Added tag(s) ftbfs. Merged 997355 997875 > thanks Stopping processing here. Please contact me if you need assistance. -- 997355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997355 997875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997875: marked as pending in astroid
Control: tag -1 pending Hello, Bug #997875 in astroid 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/packages/astroid/-/commit/b3ff29a78664a44d140c6ef5d6637befe74f5644 add typing-extensions to Depends; Closes: #997875 (this message was generated automatically) -- Greetings https://bugs.debian.org/997875
Processed (with 1 error): reassign 997355 to astroid, forcibly merging 997875 997355
Processing commands for cont...@bugs.debian.org: > reassign 997355 astroid Bug #997355 [src:pylint] pylint: FTBFS: ModuleNotFoundError: No module named 'typing_extensions' Bug reassigned from package 'src:pylint' to 'astroid'. No longer marked as found in versions pylint/2.7.2-3. Ignoring request to alter fixed versions of bug #997355 to the same values previously set > forcemerge 997875 997355 Bug #997875 [src:astroid] astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions' Unable to merge bugs because: package of #997355 is 'astroid' not 'src:astroid' Failed to forcibly merge 997875: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 997355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997355 997875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#997875 marked as pending in astroid
Processing control commands: > tag -1 pending Bug #997875 [src:astroid] astroid breaks pylint-flask autopkgtest: No module named 'typing_extensions' Added tag(s) pending. -- 997875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997232: marked as done (netperfmeter: FTBFS: cpustatus.cc:33:10: fatal error: sys/sysctl.h: No such file or directory)
Your message dated Wed, 03 Nov 2021 03:33:27 + with message-id and subject line Bug#997232: fixed in netperfmeter 1.9.1-1 has caused the Debian Bug report #997232, regarding netperfmeter: FTBFS: cpustatus.cc:33:10: fatal error: sys/sysctl.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netperfmeter Version: 1.8.6~rc2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd "/<>/obj-x86_64-linux-gnu/src" && /usr/bin/c++ -DHAVE_DCCP > -DHAVE_IEEE_FP -DHAVE_KERNEL_SCTP -DHAVE_MPTCP -DHAVE_NETINET_SCTP_H > -I"/<>/obj-x86_64-linux-gnu/src" -I"/<>/src" -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall > -Wno-unused-function -Wno-unused-parameter -Wno-overlength-strings > -Wno-array-bounds -Wno-address-of-packed-member -D_DEFAULT_SOURCE -DLINUX > -MD -MT src/CMakeFiles/netperfmeter.dir/cpustatus.cc.o -MF > CMakeFiles/netperfmeter.dir/cpustatus.cc.o.d -o > CMakeFiles/netperfmeter.dir/cpustatus.cc.o -c > "/<>/src/cpustatus.cc" > /<>/src/cpustatus.cc:33:10: fatal error: sys/sysctl.h: No such > file or directory >33 | #include > | ^~ > compilation terminated. > make[3]: *** [src/CMakeFiles/netperfmeter.dir/build.make:233: > src/CMakeFiles/netperfmeter.dir/cpustatus.cc.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/netperfmeter_1.8.6~rc2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: netperfmeter Source-Version: 1.9.1-1 Done: Thomas Dreibholz We believe that the bug you reported is fixed in the latest version of netperfmeter, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Dreibholz (supplier of updated netperfmeter 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, 01 Nov 2021 09:53:15 +0100 Source: netperfmeter Architecture: source Version: 1.9.1-1 Distribution: unstable Urgency: medium Maintainer: Thomas Dreibholz Changed-By: Thomas Dreibholz Closes: 997232 Changes: netperfmeter (1.9.1-1) unstable; urgency=medium . * New upstream release (Closes: #997232). * debian/control: Updated standards version to 4.6.0.1. Checksums-Sha1: 06b0ccbcb055200102ad8da34fe22e38b7fab45b 2205 netperfmeter_1.9.1-1.dsc 0c66d04131757e2f63975eefa76fc8f286aaa50e 284032 netperfmeter_1.9.1.orig.tar.xz 61b25276110bf674c23467c3050413efb130e6df 2913 netperfmeter_1.9.1.orig.tar.xz.asc 19b36784b2a346a64b1881a4251fdbd1332e85ab 77480 netperfmeter_1.9.1-1.debian.tar.xz 4ccb9ee8b53a71cb36c529392dbbc7e390a58d30 6323 netperfmeter_1.9.1-1_source.buildinfo Checksums-Sha256: 9eb62ee6507e15beb2e10fb9f635f67f4a37b16a81e6943b256372370eefe76b 2205 netperfmeter_1.9.1-1.dsc 98fec32acc5e8f1b4c0e60f9a2f967aa36563ae86cd01c08cc08dc6d539304fc 284032 netperfmeter_1.9.1.orig.tar.xz 860afe7d1d3496477ccdf75778f1e1d7a9eab2dd86e5f9eb38fd9b5dcac11eb7 2913 netperfmeter_1.9.1.orig.tar.xz.asc 27b2ee361bdc9cd2150fb7f2123c35f6e05eeb567814aec441e1d7a72a52d6a4 77480 netperfmeter_1.9.1-1.debian.tar.xz 23cad9a73dbacdfd746c2083c5ffa1ebf9e31a81471a988612dc74733f92b197 6323 netperfmeter_1.9.1-1_source.buildinfo Files: 5ce118fb3e0a08d0bf21eeeb22336711 2205 net optional netperfmeter_1.9.1-1.dsc 57f56ff4471d286f2f9bb5e2039de0ed 284032 net optional
Bug#997740: marked as done (python-pkginfo: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176))
Your message dated Wed, 03 Nov 2021 01:18:27 + with message-id and subject line Bug#997740: fixed in python-pkginfo 1.7.1-1 has caused the Debian Bug report #997740, regarding python-pkginfo: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176) 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.) -- 997740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pkginfo Version: 1.4.2-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build --buildsystem=pybuild > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/develop.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/__init__.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/_compat.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/index.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/commandline.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/sdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/bdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/distribution.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/installed.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/utils.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > copying pkginfo/wheel.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > creating /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/__init__.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_index.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_utils.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_wheel.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_develop.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_commandline.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_installed.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_sdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_bdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > copying pkginfo/tests/test_distribution.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > python3 setup.py build_sphinx > running build_sphinx > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: invalid syntax (conf.py, > line 176) > > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/python-pkginfo_1.4.2-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: python-pkginfo Source-Version: 1.7.1-1 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of python-pkginfo, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated python-pkginfo 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
Bug#998358: Subject: grepmail: autopkgtest doesn't do anything
Thanks a lot Paul. Really, in our machines the package is built and Makefile exists. I need to check some packages of mine. I think there are some tests around grepmail in upstream source. However, don't worry because this upload was a first work. Now, Marcos will package the new upstream release and he will fix this mistake. In a final action, he will send a SPU to fix a specific issue. Regards, Eriberto
Bug#998347: librust-bindgen+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7+default-dev
Source: rust-bindgen Followup-For: Bug #998347 That is not how rust Debian packaging works; your patch will get lost with the next upload of the autogenerated package. If you want your patch to not get lost, do it via the normal process: https://salsa.debian.org/rust-team/debcargo-conf/ -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (300, 'unstable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#998156: contains non-DFSG-free files
Henry is correct that the MLton compiler (the runtime, basis library implementation, and compiler proper) do not depend on ckit (or any of the (re)distributed SML/NJ libraries), the benchmarks, or on mlnlffigen, nor are those components required for using MLton (unless, of course, the program being compiled explicitly references them). If Debian wants to carve up the packages for MLton in a different way, then that seems fine, but I'm not inclined to do serious rearrangements of the GitHub repository or of the source releases that we (upstream) package. I appreciate the licensing issue, but consider it fairly low stakes for decades old code. Florian is correct that MLton has packaged mlnlffigen both out of convenience (as we have packaged mllex and mlyacc) for users and because MLton requires the tool to generate slightly different code. On Mon, Nov 1, 2021 at 3:55 PM Henry Cejtin wrote: > Your right, but I think (not on the basis of real knowledge) that > ml-nlffigen isn't used in either the compilation > of the MLton compiler, nor by the MLton compiler in compiling user > code. I thought that it was > for a MLton compiler user to use, and had been tweaked so that the > output was usable by MLton. > > I certainly could be wrong about this. >
Bug#984081: marked as done (lastz: ftbfs with GCC-11)
Your message dated Tue, 02 Nov 2021 22:48:56 + with message-id and subject line Bug#984081: fixed in lastz 1.04.15-2 has caused the Debian Bug report #984081, regarding lastz: ftbfs with GCC-11 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.) -- 984081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lastz Version: 1.04.03-4 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/lastz_1.04.03-4_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-stringop-truncation -O3 -Wall -Wextra -Werror -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DVERSION_MAJOR="\"1"\" -DVERSION_MINOR="\"04"\" -DVERSION_SUBMINOR="\"03"\" -DREVISION_DATE="\"20191114"\" -DSUBVERSION_REV="\""\" -Dscore_type=\'I\' diag_hash.c -o diag_hash.o gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-stringop-truncation -O3 -Wall -Wextra -Werror -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DVERSION_MAJOR="\"1"\" -DVERSION_MINOR="\"04"\" -DVERSION_SUBMINOR="\"03"\" -DREVISION_DATE="\"20191114"\" -DSUBVERSION_REV="\""\" -Dscore_type=\'I\' chain.c -o chain.o gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-stringop-truncation -O3 -Wall -Wextra -Werror -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DVERSION_MAJOR="\"1"\" -DVERSION_MINOR="\"04"\" -DVERSION_SUBMINOR="\"03"\" -DREVISION_DATE="\"20191114"\" -DSUBVERSION_REV="\""\" -Dscore_type=\'I\' gapped_extend.c -o gapped_extend.o gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-stringop-truncation -O3 -Wall -Wextra -Werror -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DVERSION_MAJOR="\"1"\" -DVERSION_MINOR="\"04"\" -DVERSION_SUBMINOR="\"03"\" -DREVISION_DATE="\"20191114"\" -DSUBVERSION_REV="\""\" -Dscore_type=\'I\' tweener.c -o tweener.o gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-stringop-truncation -O3 -Wall -Wextra -Werror -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DVERSION_MAJOR="\"1"\" -DVERSION_MINOR="\"04"\" -DVERSION_SUBMINOR="\"03"\" -DREVISION_DATE="\"20191114"\" -DSUBVERSION_REV="\""\" -Dscore_type=\'I\' masking.c -o masking.o gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-stringop-truncation -O3 -Wall -Wextra -Werror -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DVERSION_MAJOR="\"1"\" -DVERSION_MINOR="\"04"\" -DVERSION_SUBMINOR="\"03"\" -DREVISION_DATE="\"20191114"\" -DSUBVERSION_REV="\""\" -Dscore_type=\'I\' segment.c -o segment.o gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-stringop-truncation -O3 -Wall -Wextra -Werror -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DVERSION_MAJOR="\"1"\" -DVERSION_MINOR="\"04"\" -DVERSION_SUBMINOR="\"03"\" -DREVISION_DATE="\"20191114"\" -DSUBVERSION_REV="\""\" -Dscore_type=\'I\' edit_script.c -o edit_script.o
Bug#997713: marked as done (pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`)
Your message dated Tue, 02 Nov 2021 22:49:19 + with message-id and subject line Bug#997713: fixed in pushpin 1.32.2-2 has caused the Debian Bug report #997713, regarding pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"` 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.) -- 997713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pushpin Version: 1.32.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./configure --prefix=/usr --qtselect=5 --configdir=/etc > --extraconf="$QMAKE_BUILDFLAGS" --verbose > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > Configuring Pushpin ... > > PREFIX=/usr > BINDIR=/usr/bin > EX_QTDIR= > QC_EXTRACONF=QMAKE_CPPFLAGS *= -Wdate-time -D_FORTIFY_SOURCE=2 QMAKE_CFLAGS > *= -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > QMAKE_CXXFLAGS *= -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 QMAKE_LFLAGS *= -Wl,-z,relro -Wl,-z,now -Wl,--as-needed > QC_LIBDIR= > QC_CONFIGDIR=/etc > QC_RUNDIR= > QC_LOGDIR= > QC_DISABLE_cargo= > QC_DEFAULT_ENABLE_cargo= > > Verifying Qt build environment ... > running: /usr/bin/qtchooser -run-tool=qmake -qt=5 -query QT_INSTALL_BINS > running: "/usr/lib/qt5/bin/qmake" -query QT_VERSION > qmake found in /usr/lib/qt5/bin/qmake > /usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > makespec is > -> ok > conf command: [./configure] > conf path:[./configure] > srcdir: [/<>] > builddir: [/<>] > profile: [/<>/pushpin.pro] > qmake path: [/usr/lib/qt5/bin/qmake] > qmakespec:[] > make tool:[/usr/bin/gmake] > > Checking for Qt >= 5.2.0 ... yes > > * extra += APP_VERSION = 1.32.2 > * extra += LIBDIR = /usr/lib/pushpin > * extra += CONFIGDIR = /etc/pushpin > * extra += RUNDIR = /var/run/pushpin > * extra += LOGDIR = /var/log/pushpin > * INCLUDEPATH += $$PWD/src > * DEFINES += HAVE_CONFIG > Checking for libzmq >= 2.0 ... > * [pkg-config libzmq --exists] > * returned: 0 > * [pkg-config libzmq --atleast-version=2.0] > * returned: 0 > * [pkg-config libzmq --modversion] > 4.3.4 > * returned: 0 > * [pkg-config libzmq --libs] > -lzmq > * returned: 0 > * [pkg-config libzmq --cflags] > -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2 > * returned: 0 > * INCLUDEPATH += /usr/include/pgm-5.3 > * INCLUDEPATH += /usr/include/libxml2 > * LIBS += -lzmq > -> yes > Checking for cargo >= 1.34.0 ... > * [cargo version] > cargo 1.46.0 > * returned: 0 > * extra += CONFIG += use_cargo > -> yes > Info: creating stash file /<>/.qmake.stash > > Good, your configure finished. Now run /usr/bin/gmake. > > echo "CONFIG += debug" >>conf.pri > # Upstream Cargo.lock contains versions not valid for debian > rm Cargo.lock > # Upstream config.toml references vendored dependencies not part of the > debian package > rm .cargo/config.toml > cargo update > error: failed to select a version for the requirement `base64 = "^0.12"` > candidate versions found which didn't match: 0.13.0 > location searched: directory source `/usr/share/cargo/registry` (which is > replacing registry `https://github.com/rust-lang/crates.io-index`) > required by package `pushpin v1.32.2 (/<>)` > perhaps a crate was updated and forgotten to be re-vendored? > make[1]: *** [debian/rules:37: override_dh_auto_configure] Error 101 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pushpin_1.32.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: pushpin Source-Version: 1.32.2-2 Done: Jan Niehusmann We believe that the bug you reported is fixed in the latest version of
Bug#997772: python-cogent: FTBFS: You must configure the bibtex_bibfiles setting
Hi Andreas > > > Extension error: > > > You must configure the bibtex_bibfiles setting > > > make[2]: *** [Makefile:40: html] Error 2 this is sphinxcontrib-bibtex saying that you need to add the following to doc/conf.py: bibtex_bibfiles = "path/to/references.bib" However I can't see a .bib file anywhere in the source. I also can't see any code in the rst files or the docstrings that would actually use sphinxcontrib- bibtex so I'm not sure how this extension is actually used in these documents. Perhaps it isn't actually needed at all. cheers Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#998364: ruby-async-rspec: autopkgtest failures on armhf and i386
Source: ruby-async-rspec Version: 1.16.1-2 Severity: serious ruby-async-rspec is unable to migrate to testing due to autopkgtest failures on armhf and i386: Failures: | 1) RSpec::Memory on supported platform should not exceed specified size limit |Failure/Error: | expect do | "a" * 100_000 | end.to limit_allocations.of(String, size: 100_001) | | exceeded allocation limit: allocated 2 String instances, 99961 bytes, expected exactly 11 bytes See https://ci.debian.net/data/autopkgtest/testing/i386/r/ruby-async-rspec/16143499/log.gz Cheers -- Sebastian Ramacher
Processed: Bug#984081 marked as pending in lastz
Processing control commands: > tag -1 pending Bug #984081 [src:lastz] lastz: ftbfs with GCC-11 Added tag(s) pending. -- 984081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984081: marked as pending in lastz
Control: tag -1 pending Hello, Bug #984081 in lastz reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/lastz/-/commit/360023084b9af30835e9e7086d8ff2cac8d7eaea Add gcc11.patch Closes: #984081 (this message was generated automatically) -- Greetings https://bugs.debian.org/984081
Bug#997166: libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]
That link is the correct one. I was comparing to https://sources.debian.org/patches/libcdio/2.1.0-2/ncursesw.diff/ which is different so I may have this wrong. On Tue, Nov 2, 2021 at 5:47 PM Gabriel F. T. Gomes < gabr...@inconstante.net.br> wrote: > Hi, Rocky, > > On Tue, 2 Nov 2021 13:11:07 -0400 > Rocky Bernstein wrote: > > > > Hmm - as best as I can tell this patches things a little differently than > > what was done in the git codebase. > > That was not my intention. > > Actually, I don't understand why you say that. > > The patch that I backported to Debian is the one you mentioned in a > previous message, i.e.: > > https://savannah.gnu.org/patch/index.php?10130 > > What did I get wrong? > > Cheers, > Gabriel >
Bug#990224: [Pkg-pascal-devel] Bug#990224: leaves diversion after upgrade from sid to experimental
Hi Abou, On 02-11-2021 22:37, Abou Al Montacir wrote: > On Tue, 2021-11-02 at 21:22 +0100, Paul Gevers wrote: >> I don't follow at all. > Sorry, I don't catch what do you mean here, probably due to my non > native English. It means that I didn't understand everything you were saying as the problem at hand looked much simpler than your solution. I didn't understand why you needed the current or future solution, I am just trying to solve the actual bug in this report. > Did you not accept the new solution, or is my explanation above not > clear at all and confusing? I didn't try extremely hard to understand the real problem, but ... > If you don't like the new solution, it is fine with me. We can try to > fix the current one. Otherwise, please let me know and I can try to > explain it a bit more. If you come with a more elegant solution for the problem you try to tackle, I think we *still* need to solve this particular bug report as the problem is embedded in the package currently in testing. >> We're doing diversions in maintainer scripts and >> we forget to properly keep track of our diversions. > The list of diverted files is created automatically during the build > process in lazarus-src.preinst.[1] I know. > The very same list is created for lazarus-src.postrm.[2] Yes, but the list for 2.0.12 is apparently not the same and missing files compared to 2.0.10. >> With the new >> upstream version, apparently some files got dropped and the knowledge of >> the diversions got lost in the process. > This means that somehow, the lazarus-src.postrm was not called. Because 2.0.10 was upgraded to 2.0.12 and then 2.0.12 was removed. >> I think we can easily manually >> drop the diversions now by adding them here [1], while contemplating a >> saner and automated way of handling the underlying problem. > In the current case, lazarus-src.postrm is not called or is called but > does not fall in the list of tests we are doing (called with upgrade?). I understand the problem is that we first upgrade and then remove. The embedded list in 2.0.12 is not listing all files we had in 2.0.10. > However, in the past we did not remove the old lazarus when the new one > is installed (we were able to have 2.0.10 and 2.0.12). Now we allow this > only for major releases, not maintenance ones. You're confusing me. > So next time, soon, when > 2.2 will be there, the upgrade will not happen in the same way. > So if upgrading from 2.0.10 to 2.0.x we should remove diversions, but > not if we go to from 2.0.10 to 2.y with y > 0. > That was why I proposed to completely replace this mechanism with an > other one that let it handled automatically with dpkg, but maybe we can > just fix the logic in [3]. My point is that even if we replace the mechanism, we still need to remove the existing diversions from the version in testing, when upgrading to the version in unstable. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#997166: libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]
Hi, Rocky, On Tue, 2 Nov 2021 13:11:07 -0400 Rocky Bernstein wrote: > > Hmm - as best as I can tell this patches things a little differently than > what was done in the git codebase. That was not my intention. Actually, I don't understand why you say that. The patch that I backported to Debian is the one you mentioned in a previous message, i.e.: https://savannah.gnu.org/patch/index.php?10130 What did I get wrong? Cheers, Gabriel
Processed: closing 997809
Processing commands for cont...@bugs.debian.org: > close 997809 Bug #997809 [src:roundcube] roundcube: Delay migration into testing Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 997809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990224: leaves diversion after upgrade from sid to experimental
Hi Paul, On Tue, 2021-11-02 at 21:22 +0100, Paul Gevers wrote: > ... > I don't follow at all. Sorry, I don't catch what do you mean here, probably due to my non native English. Did you not accept the new solution, or is my explanation above not clear at all and confusing? If you don't like the new solution, it is fine with me. We can try to fix the current one. Otherwise, please let me know and I can try to explain it a bit more. > We're doing diversions in maintainer scripts and > we forget to properly keep track of our diversions. The list of diverted files is created automatically during the build process in lazarus-src.preinst.[1] The very same list is created for lazarus-src.postrm.[2] > With the new > upstream version, apparently some files got dropped and the knowledge of > the diversions got lost in the process. This means that somehow, the lazarus-src.postrm was not called. > I think we can easily manually > drop the diversions now by adding them here [1], while contemplating a > saner and automated way of handling the underlying problem. In the current case, lazarus-src.postrm is not called or is called but does not fall in the list of tests we are doing (called with upgrade?). However, in the past we did not remove the old lazarus when the new one is installed (we were able to have 2.0.10 and 2.0.12). Now we allow this only for major releases, not maintenance ones. So next time, soon, when 2.2 will be there, the upgrade will not happen in the same way. So if upgrading from 2.0.10 to 2.0.x we should remove diversions, but not if we go to from 2.0.10 to 2.y with y > 0. That was why I proposed to completely replace this mechanism with an other one that let it handled automatically with dpkg, but maybe we can just fix the logic in [3]. [1] https://salsa.debian.org/pascal-team/lazarus/-/blob/master/debian/rules#L411 [2] https://salsa.debian.org/pascal-team/lazarus/-/blob/master/debian/rules#L423 [3] https://salsa.debian.org/pascal-team/lazarus/-/blob/master/debian/lazarus-src.postrm.in#L7 -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#796536: marked as done (criu: package not yet ready for stable release / fast moving (blocking bug))
Your message dated Tue, 2 Nov 2021 22:29:42 +0100 with message-id and subject line Re: Bug#796536: criu: package not yet ready for stable release / fast moving (blocking bug) has caused the Debian Bug report #796536, regarding criu: package not yet ready for stable release / fast moving (blocking bug) 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.) -- 796536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: criu Version: 1.6-2 Severity: serious I'm filling this bug as blocking bug for criu for testing. Criu is by now still a fast moving project and at this point it is not yet ready to be effectively used in a stable release. --- End Message --- --- Begin Message --- On Sat, Aug 22, 2015 at 02:24:48PM +0200, Salvatore Bonaccorso wrote: > Source: criu > Version: 1.6-2 > Severity: serious > > I'm filling this bug as blocking bug for criu for testing. Criu is by > now still a fast moving project and at this point it is not yet ready > to be effectively used in a stable release. I'm now closing this blocking bug. We should probably now move forward and make it possible to have criu available in bookworm. Regards, Salvatore--- End Message ---
Processed: lastz ftbfs with gcc11 fixed upstream
Processing commands for cont...@bugs.debian.org: > # considering pushing a patch for this one, so it stops making noise > tags 984081 confirmed fixed-upstream Bug #984081 [src:lastz] lastz: ftbfs with GCC-11 Added tag(s) confirmed and fixed-upstream. > forwarded 984081 https://github.com/lastz/lastz/issues/42 Bug #984081 [src:lastz] lastz: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/lastz/lastz/issues/42'. > thank you Stopping processing here. Please contact me if you need assistance. -- 984081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998359: age fails reading passphrase-protected key files
Package: age Version: 1.0.0~rc1-2+b3 Severity: grave Justification: renders package unusable Dear Maintainer, this is how you can reproduce the bug: $ age-keygen | age -p > tmp/key.age Public key: age17sxjygr9yuvv7s5yd657gfw6v2c9597938ur2smug4u9fysrxdms2p9h0y Enter passphrase (leave empty to autogenerate a secure one): Using the autogenerated passphrase "dolphin-coffee-erase-table-denial-remain-orphan-gym-debris-episode". $ age -r age17sxjygr9yuvv7s5yd657gfw6v2c9597938ur2smug4u9fysrxdms2p9h0y -o /tmp/passwd.age /etc/passwd $ age -d -i tmp/key.age -o /tmp/passwd /tmp/passwd.age Error reading "tmp/key.age": failed to read "tmp/key.age": error at line 1: malformed secret key: separator '1' at invalid position: pos=20, len=21 [ Did age not do what you expected? Could an error be more useful? Tell us: https://filippo.io/age/report ] Being unable to use passphrase-protected key files renders this package unusable. This bug is not present in upstream v1.0.0. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/1 CPU thread) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages age depends on: ii libc6 2.31-13+deb11u2 age recommends no packages. age suggests no packages. -- no debconf information
Bug#996878: python3-prelude: python3 import prelude throws an ImportError exception
Hi, I tracked the issue down to https://sources.debian.org/patches/libprelude/5.2.0-4/025-Fix-PyIOBase_Type.patch Although the patch changes the content of bindings/python/libpreludecpp-python.i, swig is never called during the build to recreate _prelude.cxx. The final package therefore acts as if the patch had never been there in the first place. The attached patch for debian/rules ensures that the file gets regenerated. After applying the patch, the module can be imported. Due to the difference between the swig version initially used to build _prelude.cxx (4.0.1) and the one in Debian testing/sid (4.0.2), the diff output between both versions of _prelude.cxx is quite long (730 lines). However, I have been running with the patch for 24h and haven't seen any problem so far. Best regards, François --- debian/rules.bak 2021-08-25 20:53:39.0 +0200 +++ debian/rules 2021-11-02 21:19:43.102093735 +0100 @@ -53,7 +53,7 @@ ln -s /usr/share/gtk-doc/html/libprelude $(CURDIR)/debian/tmp/usr/share/doc/libprelude-doc/html install-python%: - cd bindings/python && python$* setup.py install --root $(CURDIR)/debian/tmp + cd bindings/python && make _prelude.cxx && python$* setup.py install --root $(CURDIR)/debian/tmp %: dh $@ $(DH_ADDONS)
Bug#998358: Subject: grepmail: autopkgtest doesn't do anything
Source: grepmail X-Debbugs-Cc: mar...@talau.info, eribe...@debian.org Version: 5.3104-1 Severity: serious Justification: RC policy Dear Marcos, Joao, I appreciate your attention to the orphaned package grepmail and the fact that you try to save it from removal from testing, but in the process you added and autopkgtest that doesn't do anything at all. I played around with it a tiny bit, and the reason it doesn't run anything is because dh_auto_test doesn't detect a known framework. Why dh_auto_test works during building is that during build a Makefile is generated in one of the steps before testing and dh_auto_test executes the test target in that. For this to work, the autopkgtest at least needs more of the Build-Depends, otherwise the test fails. I ran the following manually in the testbed after checking what code was actually run during the test on the buildd and it currently fails all tests: PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', 'blib/arch')" t/*.t Before fixing this, please ensure you're testing the as-installed binary instead of the code in the source tree, as the intention of autopkgtest is to test the package, not the source, as I believe you're not testing /usr/bin/grepmail Paul -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled OpenPGP_signature Description: OpenPGP digital signature
Bug#990224: lazarus-src-2.0: leaves diversion after upgrade from sid to experimental
Hi Abou, On 30-10-2021 12:25, Abou Al Montacir wrote: > The issue here is that LPK files are needed by binary libs (pascal units > / ppu) and source packages. > The right solution would be probably to move them into a separate > packages that is used by both source and binaries. > However, that ppu files are distributed not as a unique packages but > split into several ones. So this solution will require to double the > number or packages required to install full Lazarus installation. > > Another easier solution would be to make sources depend on binary or > binary depend on sources, but this is not something I like, even if, it > is true, that in order for Lazarus to show its all power, it needs the > sources to be installed. I don't follow at all. We're doing diversions in maintainer scripts and we forget to properly keep track of our diversions. With the new upstream version, apparently some files got dropped and the knowledge of the diversions got lost in the process. I think we can easily manually drop the diversions now by adding them here [1], while contemplating a saner and automated way of handling the underlying problem. Paul [1] https://salsa.debian.org/pascal-team/lazarus/-/blob/master/debian/lazarus-src.postrm.in#L9 OpenPGP_signature Description: OpenPGP digital signature
Bug#997066: marked as done (ceph: FTBFS: ld: ../../lib/libkv.a(LevelDBStore.cc.o):(.data.rel.ro._ZTI17CephLevelDBLogger[_ZTI17CephLevelDBLogger]+0x10): undefined reference to `typeinfo for leveldb::Lo
Your message dated Tue, 2 Nov 2021 21:16:25 +0100 with message-id and subject line Bug was in leveldb has caused the Debian Bug report #997066, regarding ceph: FTBFS: ld: ../../lib/libkv.a(LevelDBStore.cc.o):(.data.rel.ro._ZTI17CephLevelDBLogger[_ZTI17CephLevelDBLogger]+0x10): undefined reference to `typeinfo for leveldb::Logger' 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.) -- 997066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ceph Version: 14.2.21-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -Wtype-limits -Wignored-qualifiers -Winit-self > -Wpointer-arith -Werror=format-security -fno-strict-aliasing -fsigned-char > -Wno-unknown-pragmas -rdynamic -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -ftemplate-depth-1024 -Wnon-virtual-dtor > -Wno-unknown-pragmas -Wno-ignored-qualifiers -Wstrict-null-sentinel > -Woverloaded-virtual -fno-new-ttp-matching -U_FORTIFY_SOURCE > -D_FORTIFY_SOURCE=2 -fstack-protector-strong -fdiagnostics-color=auto > -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc > -fno-builtin-free -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -latomic -pie > CMakeFiles/ceph-bluestore-tool.dir/bluestore/bluestore_tool.cc.o -o > ../../bin/ceph-bluestore-tool > -Wl,-rpath,/<>/obj-x86_64-linux-gnu/lib: ../../lib/libos.a > ../../lib/libglobal.a ../../lib/libkv.a ../../lib/libheap_profiler.a > /usr/lib/x86_64-linux-gnu/libtcmalloc.so > /usr/lib/x86_64-linux-gnu/libleveldb.so ../rocksdb/librocksdb.a > /usr/lib/x86_64-linux-gnu/libsnappy.so /usr/lib/x86_64-linux-gnu/liblz4.so > /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libaio.so > /usr/lib/x86_64-linux-gnu/libfuse.so ../../lib/libceph-common.so.0 > ../../lib/libjson_spirit.a ../../lib/libcommon_utf8.a > ../../lib/liberasure_code.a ../../lib/libcrc32.a ../../lib/libarch.a > /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0 > /usr/lib/x86_64-linux-gnu/libboost_atomic.so.1.74.0 > /usr/lib/x86_64-linux-gnu/libboost_random.so.1.74.0 > /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0 > /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.74.0 > /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.74.0 > /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 > /usr/lib/x86_64-linux-gnu/libblkid.so /usr/lib/x86_64-linux-gnu/libssl3.so > /usr/lib/x86_64-linux-gnu/libsmime3.so /usr/lib/x86_64-linux-gnu/libnss3.so > /usr/lib/x86_64-linux-gnu/libnssutil3.so > /usr/lib/x86_64-linux-gnu/libplds4.so /usr/lib/x86_64-linux-gnu/libplc4.so > /usr/lib/x86_64-linux-gnu/libnspr4.so /usr/lib/x86_64-linux-gnu/libcrypto.so > -pthread /usr/lib/x86_64-linux-gnu/libudev.so > /usr/lib/x86_64-linux-gnu/libibverbs.so > /usr/lib/x86_64-linux-gnu/librdmacm.so -ldl -lrt -lresolv > /usr/bin/ld: > ../../lib/libkv.a(LevelDBStore.cc.o):(.data.rel.ro._ZTI17CephLevelDBLogger[_ZTI17CephLevelDBLogger]+0x10): > undefined reference to `typeinfo for leveldb::Logger' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2021/10/23/ceph_14.2.21-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi, The bug was in leveldb which removed support for RTTI. This was fixed. Cheers, Thomas Goirand (zigo)--- End Message ---
Processed: src:win32-loader: fails to migrate to testing for too long
Processing control commands: > close -1 0.10.5 Bug #998353 [src:win32-loader] src:win32-loader: fails to migrate to testing for too long Marked as fixed in versions win32-loader/0.10.5. Bug #998353 [src:win32-loader] src:win32-loader: fails to migrate to testing for too long Marked Bug as done -- 998353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998353: src:win32-loader: fails to migrate to testing for too long
Source: win32-loader Version: 0.10.4 Severity: serious Control: close -1 0.10.5 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The following template feels a bit weird for the somewhat special package that win32-loader is, but I leave it in this report nevertheless for some background. Can somebody please judge if win32-loader should migrate in the current state and take appropriate actions if so: contact ftp to process the package on their side and update bug 982838 (I wouldn't close it, but reuse it after migration) with the right meta info such that the bug doesn't block migration? If help is needed, please reach out to the Release Team. Template = The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:win32-loader has been trying to migrate for 62 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=win32-loader OpenPGP_signature Description: OpenPGP digital signature
Bug#998351: Should libdbd-sqlite2-perl be shipped in bookworm?
Package: libdbd-sqlite2-perl Severity: serious Tags: bookworm sid libdbd-sqlite2-perl uses a vendored copy of SQLite 2. SQLite 3 was released in 2004, and the the regular SQLite 2 package is no longer shipped since bullseye (see #607969).
Bug#997740: [Python-modules-team] Bug#997740: python-pkginfo: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 176)
HI, This bugs is fixed in the new upstream release [0] [0] https://bugs.launchpad.net/pkginfo/+bug/1933322 Cheers, Arias Emmanuel @eamanu yaerobi.com On Sun, Oct 24, 2021 at 9:34 AM Lucas Nussbaum wrote: > Source: python-pkginfo > Version: 1.4.2-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211023 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > dh_auto_build --buildsystem=pybuild > > I: pybuild base:232: /usr/bin/python3 setup.py build > > running build > > running build_py > > creating /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/develop.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/__init__.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/_compat.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/index.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/commandline.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/sdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/bdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/distribution.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/installed.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/utils.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > copying pkginfo/wheel.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo > > creating > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/__init__.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_index.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_utils.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_wheel.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_develop.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_commandline.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_installed.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_sdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_bdist.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > copying pkginfo/tests/test_distribution.py -> > /<>/.pybuild/cpython3_3.9_pkginfo/build/pkginfo/tests > > python3 setup.py build_sphinx > > running build_sphinx > > Running Sphinx v4.2.0 > > > > Configuration error: > > There is a syntax error in your configuration file: invalid syntax > (conf.py, line 176) > > > > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1 > > > The full build log is available from: > http://qa-logs.debian.net/2021/10/23/python-pkginfo_1.4.2-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! > > If you reassign this bug to another package, please marking it as > 'affects'-ing > this package. See https://www.debian.org/Bugs/server-control#affects > > If you fail to reproduce this, please provide a build log and diff it with > mine > so that we can identify if something relevant changed in the meantime. > > ___ > Python-modules-team mailing list > python-modules-t...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team >
Processed: rust-bindgen: diff for NMU version 0.59.1-1.1
Processing control commands:
> tags 998347 + patch
Bug #998347 {Done: Ximin Luo }
[librust-bindgen+env-logger-dev] librust-bindgen+env-logger-dev: uninstallable
- depends on non-existing package librust-env-logger-0.7+default-dev
Added tag(s) patch.
> tags 998347 + pending
Bug #998347 {Done: Ximin Luo }
[librust-bindgen+env-logger-dev] librust-bindgen+env-logger-dev: uninstallable
- depends on non-existing package librust-env-logger-0.7+default-dev
Added tag(s) pending.
--
998347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998347: rust-bindgen: diff for NMU version 0.59.1-1.1
Control: tags 998347 + patch
Control: tags 998347 + pending
Dear maintainer,
I've prepared an NMU for rust-bindgen (versioned as 0.59.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
- Jonas
diff -Nru rust-bindgen-0.59.1/debian/cargo-checksum.json
rust-bindgen-0.59.1/debian/cargo-checksum.json
--- rust-bindgen-0.59.1/debian/cargo-checksum.json 2021-08-22
17:37:34.0 +0200
+++ rust-bindgen-0.59.1/debian/cargo-checksum.json 2021-11-02
19:36:53.0 +0100
@@ -1 +1 @@
-{"package":"Could not get crate checksum","files":{}}
+{"package":"fcc1d4fdeaab48c213b8e18298928319326670fa2b6d0509e785b248fbfe49f1","files":{}}
diff -Nru rust-bindgen-0.59.1/debian/changelog
rust-bindgen-0.59.1/debian/changelog
--- rust-bindgen-0.59.1/debian/changelog2021-08-22 17:37:34.0
+0200
+++ rust-bindgen-0.59.1/debian/changelog2021-11-02 19:36:53.0
+0100
@@ -1,3 +1,13 @@
+rust-bindgen (0.59.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * add patch to relax dependency on Rust library env_logger,
+and update (build-)dependencies on librust-env-logger-*-dev;
+this closes: bug#998347
+ * fix Cargo.toml checksum hint file
+
+ -- Jonas Smedegaard Tue, 02 Nov 2021 19:36:53 +0100
+
rust-bindgen (0.59.1-1) unstable; urgency=medium
* Team upload.
diff -Nru rust-bindgen-0.59.1/debian/control rust-bindgen-0.59.1/debian/control
--- rust-bindgen-0.59.1/debian/control 2021-08-22 17:37:34.0 +0200
+++ rust-bindgen-0.59.1/debian/control 2021-11-02 19:35:53.0 +0100
@@ -11,7 +11,7 @@
librust-clang-sys-1+clang-6-0-dev,
librust-clang-sys-1+default-dev,
librust-clap-2+default-dev,
- librust-env-logger-0.7+default-dev,
+ librust-env-logger-0.9+default-dev,
librust-lazy-static-1+default-dev,
librust-lazycell-1+default-dev,
librust-log-0.4+default-dev,
@@ -134,7 +134,7 @@
Depends:
${misc:Depends},
librust-bindgen-dev (= ${binary:Version}),
- librust-env-logger-0.7+default-dev
+ librust-env-logger-0.9+default-dev
Provides:
librust-bindgen-0+env-logger-dev (= ${binary:Version}),
librust-bindgen-0.59+env-logger-dev (= ${binary:Version}),
@@ -164,7 +164,7 @@
Depends:
${misc:Depends},
librust-bindgen-dev (= ${binary:Version}),
- librust-env-logger-0.7+default-dev,
+ librust-env-logger-0.9+default-dev,
librust-log-0.4+default-dev
Provides:
librust-bindgen-0+logging-dev (= ${binary:Version}),
diff -Nru rust-bindgen-0.59.1/debian/patches/env_logger.patch
rust-bindgen-0.59.1/debian/patches/env_logger.patch
--- rust-bindgen-0.59.1/debian/patches/env_logger.patch 1970-01-01
01:00:00.0 +0100
+++ rust-bindgen-0.59.1/debian/patches/env_logger.patch 2021-11-02
19:35:18.0 +0100
@@ -0,0 +1,21 @@
+Description: relax dependency on env_logger
+ Debian has only a newer release of env_logger,
+ which apparently works just fine.
+ .
+ This patch relaxes dependency from only release 0.7.0
+ to accept any 0.7.x through 0.9.x releases.
+Author: Jonas Smedegaard
+Last-Update: 2021-11-02
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Cargo.toml
b/Cargo.toml
+@@ -49,7 +49,7 @@
+ optional = true
+
+ [dependencies.env_logger]
+-version = "0.7"
++version = ">= 0.7, < 0.10"
+ optional = true
+
+ [dependencies.lazy_static]
diff -Nru rust-bindgen-0.59.1/debian/patches/series
rust-bindgen-0.59.1/debian/patches/series
--- rust-bindgen-0.59.1/debian/patches/series 2021-08-22 17:37:34.0
+0200
+++ rust-bindgen-0.59.1/debian/patches/series 2021-11-02 19:33:53.0
+0100
@@ -1,2 +1,3 @@
disable-runtime.diff
lower-dep.diff
+env_logger.patch
Processed: rust-quickcheck: diff for NMU version 0.9.2-1.1
Processing control commands:
> tags 998345 + patch
Bug #998345 {Done: Ximin Luo }
[librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev:
uninstallable - depends on non-existing package librust-env-logger-0.7-dev
Added tag(s) patch.
> tags 998345 + pending
Bug #998345 {Done: Ximin Luo }
[librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev:
uninstallable - depends on non-existing package librust-env-logger-0.7-dev
Added tag(s) pending.
--
998345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998345: rust-quickcheck: diff for NMU version 0.9.2-1.1
Control: tags 998345 + patch
Control: tags 998345 + pending
Dear maintainer,
I've prepared an NMU for rust-quickcheck (versioned as 0.9.2-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
- Jonas
diff -Nru rust-quickcheck-0.9.2/debian/cargo-checksum.json
rust-quickcheck-0.9.2/debian/cargo-checksum.json
--- rust-quickcheck-0.9.2/debian/cargo-checksum.json2020-04-05
18:33:58.0 +0200
+++ rust-quickcheck-0.9.2/debian/cargo-checksum.json2021-11-02
19:18:33.0 +0100
@@ -1 +1 @@
-{"package":"a44883e74aa97ad63db83c4bf8ca490f02b2fc02f92575e720c8551e843c945f","files":{}}
+{"package":"694e95e04622ce811f75b6fe1c13da70fd5b98a9cbc4c55855cbb4a2e93879e1","files":{}}
diff -Nru rust-quickcheck-0.9.2/debian/changelog
rust-quickcheck-0.9.2/debian/changelog
--- rust-quickcheck-0.9.2/debian/changelog 2020-04-05 18:33:58.0
+0200
+++ rust-quickcheck-0.9.2/debian/changelog 2021-11-02 19:18:33.0
+0100
@@ -1,3 +1,13 @@
+rust-quickcheck (0.9.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * add patch to relax dependency on Rust library env_logger,
+update Cargo.toml checksum hint file,
+and update (build-)dependencies on librust-env-logger-*-dev;
+this closes: bug#998345
+
+ -- Jonas Smedegaard Tue, 02 Nov 2021 19:18:33 +0100
+
rust-quickcheck (0.9.2-1) unstable; urgency=medium
* Package quickcheck 0.9.2 from crates.io using debcargo 2.4.2
diff -Nru rust-quickcheck-0.9.2/debian/control
rust-quickcheck-0.9.2/debian/control
--- rust-quickcheck-0.9.2/debian/control2020-04-05 18:33:58.0
+0200
+++ rust-quickcheck-0.9.2/debian/control2021-11-02 19:18:33.0
+0100
@@ -6,8 +6,8 @@
cargo:native ,
rustc:native ,
libstd-rust-dev ,
- librust-env-logger-0.7+regex-dev ,
- librust-env-logger-0.7-dev ,
+ librust-env-logger-0.9+regex-dev ,
+ librust-env-logger-0.9-dev ,
librust-log-0.4+default-dev ,
librust-rand-0.7+default-dev ,
librust-rand-core-0.5+default-dev
@@ -68,7 +68,7 @@
Depends:
${misc:Depends},
librust-quickcheck-dev (= ${binary:Version}),
- librust-env-logger-0.7-dev
+ librust-env-logger-0.9-dev
Provides:
librust-quickcheck-0+env-logger-dev (= ${binary:Version}),
librust-quickcheck-0.9+env-logger-dev (= ${binary:Version}),
@@ -98,7 +98,7 @@
Depends:
${misc:Depends},
librust-quickcheck-dev (= ${binary:Version}),
- librust-env-logger-0.7+regex-dev
+ librust-env-logger-0.9+regex-dev
Provides:
librust-quickcheck-0+regex-dev (= ${binary:Version}),
librust-quickcheck-0.9+regex-dev (= ${binary:Version}),
@@ -113,7 +113,7 @@
Depends:
${misc:Depends},
librust-quickcheck-dev (= ${binary:Version}),
- librust-env-logger-0.7-dev,
+ librust-env-logger-0.9-dev,
librust-log-0.4+default-dev
Provides:
librust-quickcheck-0+use-logging-dev (= ${binary:Version}),
diff -Nru rust-quickcheck-0.9.2/debian/patches/env_logger.patch
rust-quickcheck-0.9.2/debian/patches/env_logger.patch
--- rust-quickcheck-0.9.2/debian/patches/env_logger.patch 1970-01-01
01:00:00.0 +0100
+++ rust-quickcheck-0.9.2/debian/patches/env_logger.patch 2021-11-02
19:18:33.0 +0100
@@ -0,0 +1,21 @@
+Description: relax dependency on env_logger
+ Debian has only a newer release of env_logger,
+ which apparently works just fine.
+ .
+ This patch relaxes dependency from only release 0.7.0
+ to accept any 0.7.x through 0.9.x releases.
+Author: Jonas Smedegaard
+Last-Update: 2021-11-02
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Cargo.toml
b/Cargo.toml
+@@ -28,7 +28,7 @@
+ [lib]
+ name = "quickcheck"
+ [dependencies.env_logger]
+-version = "0.7.0"
++version = ">= 0.7, < 0.10"
+ optional = true
+ default-features = false
+
diff -Nru rust-quickcheck-0.9.2/debian/patches/series
rust-quickcheck-0.9.2/debian/patches/series
--- rust-quickcheck-0.9.2/debian/patches/series 1970-01-01 01:00:00.0
+0100
+++ rust-quickcheck-0.9.2/debian/patches/series 2021-11-02 19:18:33.0
+0100
@@ -0,0 +1 @@
+env_logger.patch
Bug#998345: librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev
Source: rust-quickcheck Followup-For: Bug #998345 Control: close -1 > Correction: It is the binary package librust-quickcheck+env-logger-dev > which depends on librust-env-logger-0.7-dev. env-logger-0.7 is sitting in NEW. There is no action to take on this package, therefore closing. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (300, 'unstable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#998347: closing 998347
notfound 998347 0.59.1-1 close 998347 thanks env-logger-0.7 is sitting in NEW. There is no action to take on this package, therefore closing.
Bug#998345: closing 998345
close 998345 thanks See my previous message.
Processed: Re: librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev
Processing control commands:
> close -1
Bug #998345 {Done: Ximin Luo }
[librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev:
uninstallable - depends on non-existing package librust-env-logger-0.7-dev
Bug 998345 is already marked as done; not doing anything.
--
998345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 998347
Processing commands for cont...@bugs.debian.org: > notfound 998347 0.59.1-1 Bug #998347 [librust-bindgen+env-logger-dev] librust-bindgen+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7+default-dev No longer marked as found in versions rust-bindgen/0.59.1-1. > close 998347 Bug #998347 [librust-bindgen+env-logger-dev] librust-bindgen+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7+default-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 998347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998345: rust-quickcheck: invalid bug report
Source: rust-quickcheck
Followup-For: Bug #998345
Control: notfound -1 0.9.2-1
Control: close -1
Not sure how you came to this conclusion.
Package: librust-rand+std-dev
Provides:
librust-rand-0.7+default-dev (= ${binary:Version}),
$ sudo aptitude install librust-quickcheck-dev
[sudo] password for infinity0:
The following NEW packages will be installed:
librust-aho-corasick+std-dev{a} librust-aho-corasick-dev{a}
librust-atty-dev{a} librust-bitflags-dev{a} librust-cfg-if-0.1-dev{a}
librust-cloudabi+default-dev{a} librust-cloudabi-dev{a}
librust-env-logger+default-dev{a}
librust-env-logger+regex-dev{a} librust-env-logger-dev{a}
librust-getrandom-dev{a} librust-humantime-dev{a} librust-libc-dev{a}
librust-lock-api-dev{a} librust-log-dev{a} librust-memchr-dev{a}
librust-once-cell-dev{a}
librust-parking-lot-core-dev{a} librust-parking-lot-dev{a}
librust-ppv-lite86+default-dev{a} librust-ppv-lite86-dev{a}
librust-quickcheck+default-dev{a} librust-quickcheck+regex-dev{a}
librust-quickcheck+use-logging-dev{a}
librust-quickcheck-dev librust-rand+alloc-dev{a}
librust-rand+getrandom-dev{a} librust-rand+std-dev{a}
librust-rand-chacha+default-dev{a} librust-rand-chacha+std-dev{a}
librust-rand-chacha-dev{a}
librust-rand-core+getrandom-dev{a} librust-rand-core+std-dev{a}
librust-rand-core-dev{a} librust-rand-dev{a} librust-rand-hc-dev{a}
librust-redox-syscall-dev{a} librust-regex+default-dev{a}
librust-regex+perf-cache-dev{a}
librust-regex+perf-dev{a} librust-regex+perf-literal-dev{a}
librust-regex+unicode-age-dev{a} librust-regex+unicode-bool-dev{a}
librust-regex+unicode-case-dev{a} librust-regex+unicode-dev{a}
librust-regex+unicode-gencat-dev{a}
librust-regex+unicode-perl-dev{a} librust-regex+unicode-script-dev{a}
librust-regex+unicode-segment-dev{a} librust-regex-dev{a}
librust-regex-syntax+unicode-dev{a} librust-regex-syntax-dev{a}
librust-scopeguard-dev{a}
librust-smallvec-dev{a} librust-termcolor-dev{a} librust-thread-local-dev{a}
librust-winapi-dev{a} librust-winapi-i686-pc-windows-gnu-dev{a}
librust-winapi-util-dev{a} librust-winapi-x86-64-pc-windows-gnu-dev{a}
0 packages upgraded, 60 newly installed, 0 to remove and 220 not upgraded.
Need to get 1,394 kB/2,216 kB of archives. After unpacking 16.8 MB will be used.
Do you want to continue? [Y/n/?] ^C
exit code 130
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-security'), (300, 'unstable'), (100,
'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Processed: notfound 998345 in 0.9.2-1
Processing commands for cont...@bugs.debian.org: > notfound 998345 0.9.2-1 Bug #998345 [librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev Ignoring request to alter found versions of bug #998345 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 998345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 998345
Processing commands for cont...@bugs.debian.org: > close 998345 Bug #998345 [librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 998345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998345: librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev
Control: reassign -1 librust-quickcheck+env-logger-dev Control: retitle -1 librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev Quoting Jonas Smedegaard (2021-11-02 21:19:38) > The package librust-quickcheck-dev is uninstallable: It depends on > non-existing package librust-rand-0.7+default-dev. Correction: It is the binary package librust-quickcheck+env-logger-dev which depends on librust-env-logger-0.7-dev. Reassigining and retitling accordingly. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: Re: librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev
Processing control commands: > reassign -1 librust-quickcheck+env-logger-dev Bug #998345 [librust-quickcheck-dev] librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev Bug reassigned from package 'librust-quickcheck-dev' to 'librust-quickcheck+env-logger-dev'. No longer marked as found in versions rust-quickcheck/0.9.2-1. Ignoring request to alter fixed versions of bug #998345 to the same values previously set > retitle -1 librust-quickcheck+env-logger-dev: uninstallable - depends on > non-existing package librust-env-logger-0.7-dev Bug #998345 [librust-quickcheck+env-logger-dev] librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev Changed Bug title to 'librust-quickcheck+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7-dev' from 'librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev'. -- 998345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998347: librust-bindgen+env-logger-dev: uninstallable - depends on non-existing package librust-env-logger-0.7+default-dev
Package: librust-bindgen+env-logger-dev Version: 0.59.1-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package librust-bindgen+env-logger-dev is uninstallable: It depends on non-existing package librust-env-logger-0.7+default-dev. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmGBhtIACgkQLHwxRsGg ASHCNhAAhf8jim3wLxYeB+MKWtPeSJioYi/3UwnsZYlcRhs1IFfTnVml+HdmyDqb 2VnqMD7zOTOFfdphZFdVSlDrmyYpYz4kF1Mpp53NWMsIlRNfKPLHjlSg75gSqO10 /3P5TJFHI64XXXmVSSU/7OcGeeqRkzypEERlRVLvSABK4vjsoS9c0AIcEKTPhyiY 5bCxyVRPYxaB49EGswvOXrmbeZ0bvF5GS4/sRoZYRiKNNrBvxBRf997efxhlKRfo ZOqx95PfP/n1UktGjZbXlR2JJlqLn9hcGWSyVqzTcfwVaba9xbO3bJrCEeA6BhXG 9/s+Agz3RjTVydDkvW027M7oPXQM1bfTMNxehp3i06/A4XZIMHZeSZExa02LqLdv /EcdIpakiby8Om02sFCErk4KDAC4uFTqpE/V9y5HRpMdlN5h7+Xl/v6f2IL4lDru nuIV8ZwqfsVWZwE2NC2S8hCcAa0dvzyoH9hXyiw9cjL4OdL8jRbRtxla2c2XDhKW wepxW13e07VITHO2UeysysyeHTfOcLRgQzpeLsuHs6JcmI230mOplYwIM9c1lRRN 8Cu18h7/fVEAFjoCa8xDnnzFX+RqPlKo0GXO6AB9MPDWxzaSyuRBWN/r0wVDdff7 4tJCbYovoyGf+razDoez36eBlhNz8Twg74Zoxz+CDcoKME+Hz8s= =WdW1 -END PGP SIGNATURE-
Bug#997232: netperfmeter: FTBFS: cpustatus.cc:33:10: fatal error: sys/sysctl.h: No such file or directory
On Sat, 23 Oct 2021 21:18:54 +0200 Lucas Nussbaum wrote: Source: netperfmeter Version: 1.8.6~rc2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd "/<>/obj-x86_64-linux-gnu/src" && /usr/bin/c++ -DHAVE_DCCP -DHAVE_IEEE_FP -DHAVE_KERNEL_SCTP -DHAVE_MPTCP -DHAVE_NETINET_SCTP_H -I"/<>/obj-x86_64-linux-gnu/src" -I"/<>/src" -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unused-function -Wno-unused-parameter -Wno-overlength-strings -Wno-array-bounds -Wno-address-of-packed-member -D_DEFAULT_SOURCE -DLINUX -MD -MT src/CMakeFiles/netperfmeter.dir/cpustatus.cc.o -MF CMakeFiles/netperfmeter.dir/cpustatus.cc.o.d -o CMakeFiles/netperfmeter.dir/cpustatus.cc.o -c "/<>/src/cpustatus.cc" > /<>/src/cpustatus.cc:33:10: fatal error: sys/sysctl.h: No such file or directory >33 | #include > | ^~ > compilation terminated. > make[3]: *** [src/CMakeFiles/netperfmeter.dir/build.make:233: src/CMakeFiles/netperfmeter.dir/cpustatus.cc.o] Error 1 This should be fixed with https://github.com/dreibh/netperfmeter/commit/6f0a0864ca0d59960f12a1ad044b48ff532a1c4b. The maintainer provided a package for the latest version including that commit at https://mentors.debian.net/package/netperfmeter/
Bug#997977: marked as done (/lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe!)
Your message dated Tue, 02 Nov 2021 18:20:45 + with message-id and subject line Bug#997977: fixed in monopd 0.10.2-5 has caused the Debian Bug report #997977, regarding /lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe! 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.) -- 997977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: monopd Version: 0.10.2-4 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com, Debian Security Team Dear Maintainer, Recently upgraded from Buster to Bullseye. I'm not perusing "journalctl --boot" looking for errors and warnings and submitting bug reports as I tend to do after a Debian upgrade. One of the curious lines in my journal logs was /lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe! This does indeed appear to be a valid systemd warning. See commit at https://github.com/systemd/systemd/commit/bed0b7dfc0070e920d00c89d9a4fd4db8d974cf0 Marked as grave as per bug descriptions in the reportbug tool (introduces a security hole). Cheers, Jason -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages monopd depends on: ii libc6 2.31-13+deb11u2 ii libgcc-s1 10.2.1-6 ii libmuparser2v5 2.2.6.1+dfsg-1 ii libstdc++6 10.2.1-6 ii libsystemd0 247.3-6 ii lsb-base11.1.0 monopd recommends no packages. Versions of packages monopd suggests: ii gtkatlantic 0.6.3-1 --- End Message --- --- Begin Message --- Source: monopd Source-Version: 0.10.2-5 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of monopd, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated monopd 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, 02 Nov 2021 18:56:50 +0100 Source: monopd Architecture: source Version: 0.10.2-5 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Closes: 997977 Changes: monopd (0.10.2-5) unstable; urgency=medium . * Declare compliance with Debian Policy 4.6.0. * Use systemd's DynamicUser feature to sandbox monopd. Thanks to Jason L. Quinn for the report. (Closes: #997977) Checksums-Sha1: 56b945014eac6e548396408db5a649d90880ffde 2110 monopd_0.10.2-5.dsc 722a456ccfd48eae0bc99ebe1971c30f1ec9af42 19732 monopd_0.10.2-5.debian.tar.xz a73d94649e7edb86877d9aad46640dde469027f6 6242 monopd_0.10.2-5_amd64.buildinfo Checksums-Sha256: 7212b834d009922d2a13c3231a2b847824653e67295cca2964e10fb6ab0e40cd 2110 monopd_0.10.2-5.dsc 7189889e00264060b071136d71642e6ecb8f4f15d9dfe5f14fcfce43fa566388 19732 monopd_0.10.2-5.debian.tar.xz a6d46a17938603e09c6cd2e085d462a32d9f76f4a35489b45d4040ba0a74bb4a 6242 monopd_0.10.2-5_amd64.buildinfo Files: 87c737e1e6c2887a15469c2d0abc48f5 2110 games optional monopd_0.10.2-5.dsc 35955589dd261a53c089466ca85c7fcd 19732 games optional monopd_0.10.2-5.debian.tar.xz dd8fbfbe488867c7392d04c9ff47b14c 6242 games optional monopd_0.10.2-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmGBfFtfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkPuAP/3+kAo4tlxcVqCUxIVo6iCC6rABAv+F4Nfaf 8+KSeWW7vFDKCAMBy1+FQSY5wIo3Qa24pYwrkafanGxVQSLt+nsErJrcMofEdQSi FAgFWXjJpp7PhElaoJj9V4ViQSW4o3lvAUBoxxmT+Qi58gFeqG5vavb0IbpMKREU
Processed: Re: pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid.
Processing control commands: > tag -1 patch Bug #997630 [src:pygithub] pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid. Added tag(s) patch. -- 997630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997630: pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid.
Control: tag -1 patch From: Romain Porte Date: Tue, 2 Nov 2021 15:19:51 +0100 Subject: setup.py: remove 2to3 Should be dropped when package is updated, because latest upstream releases are not using this flag anymore. Forward: not-needed --- setup.py | 1 - 1 file changed, 1 deletion(-) diff --git a/setup.py b/setup.py index 47f3bf5..ce6d239 100755 --- a/setup.py +++ b/setup.py @@ -97,7 +97,6 @@ if __name__ == "__main__": "Topic :: Software Development", ], test_suite="tests.AllTests", -use_2to3=True, python_requires=">=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*", install_requires=[ "deprecated",
Bug#998295: marked as done (puma: 401 runs, 1086 assertions, 1 failures, 0 errors, 6 skips)
Your message dated Tue, 02 Nov 2021 18:06:11 + with message-id and subject line Bug#998295: fixed in puma 5.5.2-1 has caused the Debian Bug report #998295, regarding puma: 401 runs, 1086 assertions, 1 failures, 0 errors, 6 skips 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.) -- 998295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puma Version: 5.3.2-3 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org puma fails to build on amd64 and mips*el: | Errors & Failures: | | 1) Failure: | TestIntegrationSingle#test_hot_restart_does_not_drop_connections_threads [/<>/test/helpers/integration.rb:308]: | 0 unexpected_response | 3 refused | 0 read timeout | 0 reset | 997 success | 565 success after restart | 1 restart count | Expected no refused connections. | Expected: 0 | Actual: 3 | | 401 runs, 1086 assertions, 1 failures, 0 errors, 6 skips https://buildd.debian.org/status/fetch.php?pkg=puma=amd64=5.3.2-3%2Bb1=1635692756=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: puma Source-Version: 5.5.2-1 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of puma, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated puma 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: Tue, 02 Nov 2021 14:39:10 -0300 Source: puma Architecture: source Version: 5.5.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Closes: 998295 Changes: puma (5.5.2-1) unstable; urgency=medium . * Team upload * New upstream version 5.5.2 - Builds and tests fine again (Closes: #998295) * Add build-dependency on ruby-localhost * debian/rules: exclude several unnecessary files from installation Checksums-Sha1: 3acfd007c2dc716615921a8918cd77f7fbc90d8e 2087 puma_5.5.2-1.dsc 906aba53f7b3a0f5cd079daeb5f382390d57a1a0 302778 puma_5.5.2.orig.tar.gz 3314d55d986cf7eb665f0047a6d2671a51124b0f 8744 puma_5.5.2-1.debian.tar.xz 21879f38968fd2c5d65a0a89db7711899fea03ca 9669 puma_5.5.2-1_amd64.buildinfo Checksums-Sha256: 5849e166188ad920e86772eda6a3ee45530e9d21041b50189ef4998dd1d5e60e 2087 puma_5.5.2-1.dsc 2685cedc3ae2baf72121bd43a838d08f7a98d13c6b9ae7dadbf414e7bcc96998 302778 puma_5.5.2.orig.tar.gz b63dfda43aa86e0c6f27ed7afdc36770ff0187a26a3cebb5255e943d9fc345e8 8744 puma_5.5.2-1.debian.tar.xz 3eef4657bb5636c54cf5eaa5d8d92d4548362f138628fd0fb7faf1b231cc3a48 9669 puma_5.5.2-1_amd64.buildinfo Files: 8cd1c0d8e326daa78212f3871a5f99bf 2087 web optional puma_5.5.2-1.dsc 69da6e3c30ae7b398ea0a6e3e9865c0f 302778 web optional puma_5.5.2.orig.tar.gz 88f7b0304af74b501196690e633c82bf 8744 web optional puma_5.5.2-1.debian.tar.xz 92d0ce4c12e4d5eb58c643cdabe60944 9669 web optional puma_5.5.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmGBeaYACgkQ/A2xu81G C96c9g//YDB7yA4x6cGOztz+2UYS2brMHkyuubvlvFKcKlN7eAwa24Bfz/W3rxQh m/sJBpmyVGZok9DCWsZ8NRbyAWboA9eK2ue9GyhBQ9oPSEHQbsCURhSgbuWtoAP+ SG0bzTdJ/RguCha4rEz1l6DJUz1hCJzTK+MKe0y6+A2PeYdCff4bDR4ZOOhNOifn e+1EL4uC7bZ2JaPrccTM2Cn2EEfmBqEQi0fyQ4ADUCwmTlcd2EOLDCofWO2Ao+ny w7u1CllDls63ytveiJli+vjnBGzkamoIiqjciVh6TqEwcM8LIzyu5BuTHACIOhTb ao27Kwew7y4Eynnsgt4t33Oacr/qseSHqeOhUIrI48ht4RcVK/EwLhq9lrOPJlY3 lFm8gHcxVMyld9GR4B3yKxeccPgRhmemEmfyakmqoiM+gFP43Ci/EYl/GjPQSIxj oKwyUl8EUFPnW9biM1MWmomShGaYr3Mr16Ecm7j52Z56dIc39Spr/f1dclZCK2ys ZvqYO0JK8EJ3LpWAAM3vtb35eNoUbCRvfJwFPG6LtvVZ9o5lIYMi2u09YPyH49Aq Gck2vifS9tIILWMYPqbycAaQYJSQEZusq6/6fRLzltAFBBps0c1g8VetJdsi8+F3 IFrz/anMoP3bsKe+YyHXxWffVm/Mnc0ErNncW1PkQ8hfyl/wr8c= =aRDx -END PGP SIGNATURE End Message ---
Bug#997977: marked as pending in monopd
Control: tag -1 pending Hello, Bug #997977 in monopd 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/games-team/monopd/-/commit/adce4ee03253e6513209085aa0e0a54016296b8e Use systemd's DynamicUser feature to sandbox monopd. Closes: #997977 Thanks: Jason L. Quinn for the report. (this message was generated automatically) -- Greetings https://bugs.debian.org/997977
Processed: closing 998330
Processing commands for cont...@bugs.debian.org: > close 998330 2.4.0-2 Bug #998330 [src:cvise] cvise FTBFS: test failure Marked as fixed in versions cvise/2.4.0-2. Bug #998330 [src:cvise] cvise FTBFS: test failure Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 998330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#997977 marked as pending in monopd
Processing control commands: > tag -1 pending Bug #997977 [monopd] /lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe! Added tag(s) pending. -- 997977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998345: librust-quickcheck-dev: uninstallable - depends on non-existing package librust-rand-0.7+default-dev
Package: librust-quickcheck-dev Version: 0.9.2-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package librust-quickcheck-dev is uninstallable: It depends on non-existing package librust-rand-0.7+default-dev. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmGBnVoACgkQLHwxRsGg ASH7HA//c8tHgNDkxlXoZnpiYPMO3LNhe/SGPIoS3Z/fPBYZtP6BnVMzQgiR9yNh 3bfRJDJXVWc8GNWjF6erA5u2qXdcRfb3UdTvcHGUJb31HWS+QuCZAJG0mLiQC8PV zNe6cHSe0kVONl1ffDttNpWDOgXDUzD1yXzYBAtQ/jkN2WM1v/h5eByGGbaqL/nD bdJJGeinQVRIx9HHZDCCgpEJICcHWy9UyyI3pvnYgw0+CdBQzKld45XslRi3iDxs LoGhF8LrPI6R6O3gsVxTCAZ26DdARyjRSMoiF7Op+ZDrlxwy+Bxt9NBigau8p8VT TM57/7oI1EWgg6mW//uieVJABvC/dXUKQMowhwCqyQxLIBfnSGgyhLU1xGkdDGlV Pi/BHJr7FF9xEYeZOxKiTIaE0AVgzQm4VQ/Z1hhsRoYReFGzWXQpLaD1bojvlpgu lzGx/vBp1EF8ijGBwb1U0YAw+bQC/rJ/N8KJldnv7HB5hBX0HeFBK2WpILvX8vg2 sw97EiAxLeYCjLL79TwyQgwYXY2rxm64QY4fNzjdWhj0ZW/9D5e/shbbgIabFQPF JB7W4/Hy9q8zJOrzymkqEoaqi7KKD8QFFzrkOdZi21PK9ZxRImb4PjdOIa7RryTV wXcU4lKE2McFA0VCShjzBBq07if8ShFPYINAe23/iSKUl7H2VWg= =9KVa -END PGP SIGNATURE-
Bug#997701: marked as done (golang-github-mattn-go-runewidth: FTBFS: open /usr/share/unicode/emoji/emoji-data.txt: no such file or directory)
Your message dated Tue, 02 Nov 2021 17:19:21 + with message-id and subject line Bug#997701: fixed in golang-github-mattn-go-runewidth 0.0.13-2 has caused the Debian Bug report #997701, regarding golang-github-mattn-go-runewidth: FTBFS: open /usr/share/unicode/emoji/emoji-data.txt: 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.) -- 997701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-mattn-go-runewidth Version: 0.0.13-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm 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 golang-github-mattn-go-runewidth > dpkg-buildpackage: info: source version 0.0.13-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Anthony Fok > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --buildsystem=golang --with=golang --builddirectory=_build >dh_auto_clean -O--buildsystem=golang -O--builddirectory=_build >dh_autoreconf_clean -O--buildsystem=golang -O--builddirectory=_build >dh_clean -O--buildsystem=golang -O--builddirectory=_build > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building golang-github-mattn-go-runewidth using existing > ./golang-github-mattn-go-runewidth_0.0.13.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of file runewidth_table.go, use > --include-removal to override > dpkg-source: info: building golang-github-mattn-go-runewidth in > golang-github-mattn-go-runewidth_0.0.13-1.debian.tar.xz > dpkg-source: info: building golang-github-mattn-go-runewidth in > golang-github-mattn-go-runewidth_0.0.13-1.dsc > debian/rules binary > dh binary --buildsystem=golang --with=golang --builddirectory=_build >dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build >dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build >dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build >dh_auto_build -O--buildsystem=golang -O--builddirectory=_build > cd _build && go generate -v github.com/mattn/go-runewidth > src/github.com/mattn/go-runewidth/benchmark_test.go > src/github.com/mattn/go-runewidth/runewidth.go > 2021/10/23 07:42:24 open /usr/share/unicode/emoji/emoji-data.txt: no such > file or directory > exit status 1 > src/github.com/mattn/go-runewidth/runewidth.go:9: running "go": exit status 1 > dh_auto_build: error: cd _build && go generate -v > github.com/mattn/go-runewidth returned exit code 1 > make: *** [debian/rules:6: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/golang-github-mattn-go-runewidth_0.0.13-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: golang-github-mattn-go-runewidth Source-Version: 0.0.13-2 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of golang-github-mattn-go-runewidth, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated golang-github-mattn-go-runewidth package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 03 Nov 2021
Bug#997166: libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]
Hmm - as best as I can tell this patches things a little differently than what was done in the git codebase. It looks like this changes to use library ncursesw whereas change in git changes the source code and adjusts the source code so that the previous curses library is okay to use. I don't have an opinion on which is preferable, but I note that the mismatch might cause a problem down the line. On Tue, Nov 2, 2021 at 12:49 PM Gabriel F. T. Gomes < gabr...@inconstante.net.br> wrote: > Hi, Rocky, Lucas, > > Thanks for doing all the hard work of reporting and fixing the bug. > I have just uploaded a new version o libcdio with the fix. > > Cheers, > Gabriel >
Bug#997166: marked as done (libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 02 Nov 2021 17:07:06 + with message-id and subject line Bug#997166: fixed in libcdio 2.1.0-3 has caused the Debian Bug report #997166, regarding libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcdio Version: 2.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../lib/driver -I../include -I../include/ > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wbad-function-cast -Wcast-align > -Wchar-subscripts -Wdeclaration-after-statement -Wdisabled-optimization > -Wendif-labels -Winline -Wmissing-declarations -Wmissing-prototypes > -Wnested-externs -Wno-sign-compare -Wpointer-arith -Wshadow > -Wstrict-prototypes -Wundef -Wunused -Wwrite-strings -c -o mmc-tool.o > mmc-tool.c > cdda-player.c: In function ‘action’: > cdda-player.c:301:28: error: format not a string literal and no format > arguments [-Werror=format-security] > 301 | mvprintw(LINE_ACTION, 0, psz_action_line); > |^~~ > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wbad-function-cast -Wcast-align > -Wchar-subscripts -Wdeclaration-after-statement -Wdisabled-optimization > -Wendif-labels -Winline -Wmissing-declarations -Wmissing-prototypes > -Wnested-externs -Wno-sign-compare -Wpointer-arith -Wshadow > -Wstrict-prototypes -Wundef -Wunused -Wwrite-strings -Wl,-z,relro -Wl,-z,now > -o cd-drive cd-drive.o util.o getopt.o getopt1.o ../lib/iso9660/libiso9660.la > ../lib/driver/libcdio.la -lm > cdda-player.c: In function ‘display_tracks’: > cdda-player.c:1032:31: error: format not a string literal and no format > arguments [-Werror=format-security] > 1032 | mvprintw(i_line++, 0, line); > | ^~~~ > cdda-player.c:1035:31: error: format not a string literal and no format > arguments [-Werror=format-security] > 1035 | mvprintw(i_line++, 0, line); > | ^~~~ > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wbad-function-cast -Wcast-align > -Wchar-subscripts -Wdeclaration-after-statement -Wdisabled-optimization > -Wendif-labels -Winline -Wmissing-declarations -Wmissing-prototypes > -Wnested-externs -Wno-sign-compare -Wpointer-arith -Wshadow > -Wstrict-prototypes -Wundef -Wunused -Wwrite-strings -Wl,-z,relro -Wl,-z,now > -o cd-read cd-read.o util.o getopt.o getopt1.o ../lib/iso9660/libiso9660.la > ../lib/driver/libcdio.la -lm > libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall > -Wbad-function-cast -Wcast-align -Wchar-subscripts > -Wdeclaration-after-statement -Wdisabled-optimization -Wendif-labels -Winline > -Wmissing-declarations -Wmissing-prototypes -Wnested-externs > -Wno-sign-compare -Wpointer-arith -Wshadow -Wstrict-prototypes -Wundef > -Wunused -Wwrite-strings -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/cd-drive > cd-drive.o util.o getopt.o getopt1.o ../lib/iso9660/.libs/libiso9660.so > ../lib/driver/.libs/libcdio.so -lm > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wbad-function-cast -Wcast-align > -Wchar-subscripts -Wdeclaration-after-statement -Wdisabled-optimization > -Wendif-labels -Winline -Wmissing-declarations -Wmissing-prototypes > -Wnested-externs -Wno-sign-compare -Wpointer-arith -Wshadow > -Wstrict-prototypes -Wundef -Wunused -Wwrite-strings -Wl,-z,relro -Wl,-z,now > -o iso-info iso-info.o util.o getopt.o getopt1.o ../lib/udf/libudf.la > ../lib/iso9660/libiso9660.la ../lib/driver/libcdio.la -lm > libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall > -Wbad-function-cast -Wcast-align -Wchar-subscripts > -Wdeclaration-after-statement -Wdisabled-optimization -Wendif-labels -Winline >
Bug#997089: libreoffice: FTBFS: segfault in '/<>/instdir/sdk/examples/java/Inspector'
Hi, Am Thu, Oct 28, 2021 at 07:18:19PM +0200 schrieb Rene Engelhard: > And interestingly, (after rm'ing the stale unopkg lockfile..) it passed. > > Also after a new attempt with manual > > $ make clean && make subsequencheck > > in odk worked, too. > > > Just looks like a flaky test... (Even though I saw it the first time > here with this report..) And since then various test build on my laptop, both 7.3 and 7.2 worked, as did it on the buildd: https://buildd.debian.org/status/logs.php?pkg=libreoffice=all (alpha1-1 was a other breakage fixed in -2, -2 failed for an other reason) https://buildd.debian.org/status/logs.php?pkg=libreoffice=amd64 https://buildd.debian.org/status/logs.php?pkg=libreoffice=arm64 Can we close this? Regards, Rene
Bug#997166: libcdio: FTBFS: cdda-player.c:301:28: error: format not a string literal and no format arguments [-Werror=format-security]
Hi, Rocky, Lucas, Thanks for doing all the hard work of reporting and fixing the bug. I have just uploaded a new version o libcdio with the fix. Cheers, Gabriel
Bug#998109: python3-numpy: numpy.typing is missing
control: severity -1 important > This bug is blocking other python packages which require numpy 1.20, > (and use numpy.typing) so raising severity to serious. sorry but that's not how RC severity works, that's for policy violations, which in this case there are none. I understand you may want to see this fixed sooner rather than later, so maybe you can submit an MR against the numpy salsa repo to fix this? i'll then review, merge and upload as needed. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Processed: Re: Bug#998109: python3-numpy: numpy.typing is missing
Processing control commands: > severity -1 important Bug #998109 [python3-numpy] python3-numpy: numpy.typing is missing Severity set to 'important' from 'serious' -- 998109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998052: marked as done (ltt-control build depends liblttng-ust-dev (< 2.13.0~) but 2.13.0-2 is to be installed)
Your message dated Tue, 02 Nov 2021 16:33:51 + with message-id and subject line Bug#998052: fixed in ltt-control 2.13.1-1 has caused the Debian Bug report #998052, regarding ltt-control build depends liblttng-ust-dev (< 2.13.0~) but 2.13.0-2 is to be installed 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.) -- 998052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ltt-control Version: 2.12.3-1 Severity: serious Tags: ftbfs bookworm sid The following packages have unmet dependencies: builddeps:ltt-control : Depends: liblttng-ust-dev (< 2.13.0~) but 2.13.0-2 is to be installed --- End Message --- --- Begin Message --- Source: ltt-control Source-Version: 2.13.1-1 Done: Michael Jeanson We believe that the bug you reported is fixed in the latest version of ltt-control, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Jeanson (supplier of updated ltt-control 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, 02 Nov 2021 12:14:37 -0400 Source: ltt-control Architecture: source Version: 2.13.1-1 Distribution: unstable Urgency: medium Maintainer: Jon Bernard Changed-By: Michael Jeanson Closes: 998052 Changes: ltt-control (2.13.1-1) unstable; urgency=medium . * [787d6bd] Bump watch file version to 4 * [277511b] Update salsa-ci config * [7a3ba1d] New upstream version 2.13.1 (Closes: #998052) * [db9f6d7] Adjust builddeps for 2.13 * [c7075fc] Update symbols file for 2.13 * [ee7779b] Update to debhelper compat 12 * [a9c28b3] Update debian/copyright Checksums-Sha1: 477d2a0ff17a9c0cec0dd58e8d0ec6547712e59c 2645 ltt-control_2.13.1-1.dsc cc9446fadadefd19edf803c787d96e4b899d074e 1865368 ltt-control_2.13.1.orig.tar.bz2 bb992ffc86e6846e9599f59a5e5ff5cb09dad32e 833 ltt-control_2.13.1.orig.tar.bz2.asc f86f34e9d52d27c53ce087f638ab4c0db4b8ff90 21148 ltt-control_2.13.1-1.debian.tar.xz d8c83fd6958be0d7fe77625d1c1577b56627a25c 8700 ltt-control_2.13.1-1_source.buildinfo Checksums-Sha256: ee8674499fc8f14b133f9d0119efde564f9e735cd7c551adcacf3e9425aa029f 2645 ltt-control_2.13.1-1.dsc cfe6df7da831fc07fd07ce46b442c2ec1074c167af73f3a1b1d2fba0c453c8b5 1865368 ltt-control_2.13.1.orig.tar.bz2 09ecdb0b261272fbe841bfb59db2ad6bf1d53d6e519a2a88f7bc7b390d3ecff1 833 ltt-control_2.13.1.orig.tar.bz2.asc 9d9aa655dc9e974d411bb86dfca7853e149d19ec1739583414d2268c315299b3 21148 ltt-control_2.13.1-1.debian.tar.xz 70dd64714dc940ae9f069173e73cd7840b8253a1fab70f37279fa084d9d65c7f 8700 ltt-control_2.13.1-1_source.buildinfo Files: 73f55c927a4dd59b51508f6f4efdec01 2645 libs optional ltt-control_2.13.1-1.dsc aca6cf483f2957ccd24babb4a75c 1865368 libs optional ltt-control_2.13.1.orig.tar.bz2 06423da000b052ac72453a1629cf3f4f 833 libs optional ltt-control_2.13.1.orig.tar.bz2.asc 21e8b197faf087903ffdcd4d73fe6f40 21148 libs optional ltt-control_2.13.1-1.debian.tar.xz 7e27db73c289c6e404e983e140c595b8 8700 libs optional ltt-control_2.13.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEmGYkMkK2Qid54gtihlYfRSGA/P4FAmGBZEwUHG1qZWFuc29u QGRlYmlhbi5vcmcACgkQhlYfRSGA/P5o2RAAkX5gNqquTQlZ0B8lP0T+Ou/GlxLL 70GRS9PgA9D2WtMHd6FL0v+ylHb5GDsn8YVuvrU1jFa1OndAu2bVlXYyI1sSi7gQ gN/Ip2IogWMkXuPZZ4xw7QV7AwRrUF0Eli1F0rqo2zARNbjODSVWlumf3RMXFHuX XpmM5h/mD4YfLswJfb3mmGruDF3gyol7Xcaqo36kzB+dw7a+BY9nS0KQ3iHmRCPW KaRKqmY/5ZWrvbL/aNUb0ho+mh8dIdPi0ZjW4gNhkZwcbXyZPH1PO2exQsGd4DHg AC8cUi/8eEkqndvocH//qfjw/W3DebP/0DH5IGG6Mq2QTnHsuvCJ6aVP8EEWc3DT RzuLuyyF3LjWrVBiqowFfP36VVmbpgXfYqxuBlywXlSPGpgcbuEbY1zFMUybTdPL GfncMvxnX7XWLTe4f6/0baxFKu1N2OsWpDIIsnbrsYNs4JVbqBsm1YZY1P1QOHWb ft9SBu7IGK1yD6cKieByG+yhokrUOQ5cL/OGSuiGIpZ7BEs02fem7mR+SqKsz7cP zx53oY9rYdPRJL7l35k8pX8O+uHLiPz2t7H/0y1VP3UibFeaBB4mgCNc8iqOBIgE oMHXZBqUZuewFf5BjyM32CyYpm5t4IfSZwvvgyckuzO3h/IJb5IOT00govTvXQja sdZnrpwXJPzU8fw= =OUQ9 -END PGP SIGNATURE End Message ---
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Re: Sébastien Villemot > I am going to package cl-uax-15 and cl-global-vars (ITPs are marked as > blocking the present bug), and then upgrade cl-postmodern. That sounds excellent, merci! Christoph
Bug#997159: burp: FTBFS: src/client/monitor/status_client_ncurses.c:350:9: error: format not a string literal and no format arguments [-Werror=format-security]
I've temporarily disabled the format-security error: https://salsa.debian.org/debian/burp/-/commit/625692bd42884fbb97f132967e3c4e70430aaddf I will contact the developer to raise the issue. Thanks! On 23/10/21 21:05, Lucas Nussbaum wrote: Source: burp Version: 2.2.18-8 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): gcc -DHAVE_CONFIG_H -I. -I./src -fno-strict-aliasing -DSYSCONFDIR=\"/etc/burp\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_NCURSES_H=1 -c -o src/client/protocol2/main-backup_phase2.o `test -f 'src/client/protocol2/backup_phase2.c' || echo './'`src/client/protocol2/backup_phase2.c src/client/monitor/status_client_ncurses.c: In function ‘screen_header_ncurses’: src/client/monitor/status_client_ncurses.c:350:9: error: format not a string literal and no format arguments [-Werror=format-security] 350 | mvprintw(0, col-l-1, date); | ^~~~ src/client/monitor/status_client_ncurses.c: In function ‘update_screen_view_log’: src/client/monitor/status_client_ncurses.c:752:24: warning: ISO C forbids ‘return’ with expression, in function returning void [-Wpedantic] 752 | return update_screen_live_counters_w(sel, x, col); |^~ src/client/monitor/status_client_ncurses.c:738:13: note: declared here 738 | static void update_screen_view_log(struct sel *sel, int *x, int col, | ^~ gcc -DHAVE_CONFIG_H -I. -I./src -fno-strict-aliasing -DSYSCONFDIR=\"/etc/burp\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_NCURSES_H=1 -c -o src/client/protocol2/main-rabin_read.o `test -f 'src/client/protocol2/rabin_read.c' || echo './'`src/client/protocol2/rabin_read.c gcc -DHAVE_CONFIG_H -I. -I./src -fno-strict-aliasing -DSYSCONFDIR=\"/etc/burp\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_NCURSES_H=1 -c -o src/client/protocol2/main-restore.o `test -f 'src/client/protocol2/restore.c' || echo './'`src/client/protocol2/restore.c gcc -DHAVE_CONFIG_H -I. -I./src -fno-strict-aliasing -DSYSCONFDIR=\"/etc/burp\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_NCURSES_H=1 -c -o src/protocol1/main-handy.o `test -f 'src/protocol1/handy.c' || echo './'`src/protocol1/handy.c gcc -DHAVE_CONFIG_H -I. -I./src -fno-strict-aliasing -DSYSCONFDIR=\"/etc/burp\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_NCURSES_H=1 -c -o src/protocol1/main-msg.o `test -f 'src/protocol1/msg.c' || echo './'`src/protocol1/msg.c gcc -DHAVE_CONFIG_H -I. -I./src -fno-strict-aliasing -DSYSCONFDIR=\"/etc/burp\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DHAVE_NCURSES_H=1 -c -o src/protocol1/main-rs_buf.o `test -f 'src/protocol1/rs_buf.c' || echo './'`src/protocol1/rs_buf.c cc1: some warnings being treated as errors make[1]: *** [Makefile:4162: src/client/monitor/main-status_client_ncurses.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/burp_2.2.18-8_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. OpenPGP_signature Description: OpenPGP digital signature
Bug#980627: ruby-databojects-mysql
Am Dienstag, dem 02.11.2021 um 13:36 +0100 schrieb Daniel Leidert: > Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro: > > [..] > > * ruby-databojects-mysql > [..] Digging some more: This project has been archived upstream and the homepage points to https://rom-rb.org/ now, which has active repositories. These packages: * ruby-dataobjects * ruby-dataobjects-mysql * ruby-dataobjects-postgres * ruby-dataobjects-sqlite3 only relate to and depend on each other. They seem to be unused otherwise. I wonder if we should remove (RoM) them altogether. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Processed: tagging 979101
Processing commands for cont...@bugs.debian.org: > tags 979101 + fixed-upstream Bug #979101 [devtodo] Legally problematic GPL-3+ readline dependency Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 979101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998330: cvise FTBFS: test failure
Source: cvise
Version: 2.4.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=cvise=2.4.0-1
...
=== FAILURES ===
___ TestCvise.test_simple_reduction
self =
def test_simple_reduction(self):
> self.check_cvise('blocksort-part.c', '-c "gcc -c blocksort-part.c &&
> grep nextHi blocksort-part.c"',
['#define nextHi', '#define nextHi '])
tests/test_cvise.py:23:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tests/test_cvise.py:17: in check_cvise
subprocess.check_output(cmd, shell=True, encoding='utf8')
/usr/lib/python3.9/subprocess.py:424: in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
input = None, capture_output = False, timeout = None, check = True
popenargs = ('/<>/obj-x86_64-linux-gnu/tests/../cvise.py
blocksort-part.c -c "gcc -c blocksort-part.c && grep nextHi blocksort-part.c"',)
kwargs = {'encoding': 'utf8', 'shell': True, 'stdout': -1}
process = >/obj-x86_64-linu...>
stdout = '', stderr = None, retcode = 1
def run(*popenargs,
input=None, capture_output=False, timeout=None, check=False,
**kwargs):
"""Run command with arguments and return a CompletedProcess instance.
The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture
them.
If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return
code
in the returncode attribute, and output & stderr attributes if those
streams
were captured.
If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.
There is an optional argument "input", allowing you to
pass bytes or a string to the subprocess's stdin. If you use this
argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.
By default, all communication is in bytes, and therefore any "input"
should
be bytes, and the stdout and stderr will be bytes. If in text mode, any
"input" should be a string, and stdout and stderr will be strings
decoded
according to locale encoding, or by "encoding" if set. Text mode is
triggered by setting any of text, encoding, errors or
universal_newlines.
The other arguments are the same as for the Popen constructor.
"""
if input is not None:
if kwargs.get('stdin') is not None:
raise ValueError('stdin and input arguments may not both be
used.')
kwargs['stdin'] = PIPE
if capture_output:
if kwargs.get('stdout') is not None or kwargs.get('stderr') is not
None:
raise ValueError('stdout and stderr arguments may not be used '
'with capture_output.')
kwargs['stdout'] = PIPE
kwargs['stderr'] = PIPE
with Popen(*popenargs, **kwargs) as process:
try:
stdout, stderr = process.communicate(input, timeout=timeout)
except TimeoutExpired as exc:
process.kill()
if _mswindows:
# Windows accumulates the output in a single blocking
# read() call run on child threads, with the timeout
# being done in a join() on those threads. communicate()
# _after_ kill() is required to collect that and add it
# to the exception.
exc.stdout, exc.stderr = process.communicate()
else:
# POSIX _communicate already populated the output so
# far into the TimeoutExpired exception.
process.wait()
raise
except: # Including KeyboardInterrupt, communicate handled that.
process.kill()
# We don't call process.wait() as .__exit__ does that for us.
raise
retcode = process.poll()
if check and retcode:
> raise CalledProcessError(retcode, process.args,
output=stdout, stderr=stderr)
E subprocess.CalledProcessError: Command
'/<>/obj-x86_64-linux-gnu/tests/../cvise.py blocksort-part.c -c
"gcc -c blocksort-part.c && grep nextHi blocksort-part.c"' returned non-zero
exit status 1.
/usr/lib/python3.9/subprocess.py:528: CalledProcessError
- Captured stderr call
Bug#997209: marked as done (eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free')
Your message dated Tue, 02 Nov 2021 14:34:59 + with message-id and subject line Bug#997209: fixed in eegdev 0.2-6 has caused the Debian Bug report #997209, regarding eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free' 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.) -- 997209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eegdev Version: 0.2-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: library-usage/eegdev_acq.o: in function `main': > ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to > `rpl_free' > /usr/bin/ld: ./doc/examples/library-usage/eegdev_acq.c:215: undefined > reference to `rpl_free' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2021/10/23/eegdev_0.2-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: eegdev Source-Version: 0.2-6 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of eegdev, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated eegdev 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, 02 Nov 2021 19:40:44 +0530 Source: eegdev Architecture: source Version: 0.2-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 997209 Changes: eegdev (0.2-6) unstable; urgency=medium . * Team Upload. * Add patch to fix FTBFS with new autoconf (Closes: #997209) * Bump Standards-Version to 4.6.0 (no changes needed) Checksums-Sha1: e0565c59d4fa276af4dae7c4bdc0de07c0b826ee 2154 eegdev_0.2-6.dsc 609e99503b70295b7fb279872f1a594986bf6388 9964 eegdev_0.2-6.debian.tar.xz 90337c728943cbc4773d1b39a1f8082584e07a6c 7104 eegdev_0.2-6_amd64.buildinfo Checksums-Sha256: d316c258acde8bd15e87c9bbe2ede109861a72ecae266fc1e1b044a19de1e6b0 2154 eegdev_0.2-6.dsc c334abe24a70a0f221c36c4c127a741ae75d92b09dfe724560b7e4f56bc7ec97 9964 eegdev_0.2-6.debian.tar.xz 42513dc795e5b5ea6313258c182ee8dade75b977b2e40b362715fc56fabc8830 7104 eegdev_0.2-6_amd64.buildinfo Files: af3b34c97c811b03bdbce21b6e543dab 2154 libs optional eegdev_0.2-6.dsc 0f464e04d7efad1b9280fa1d5fbb3765 9964 libs optional eegdev_0.2-6.debian.tar.xz cb8cec9f8965d66ec02358892705f3da 7104 libs optional eegdev_0.2-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmGBSGISHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nx4nMP/RYRsk3o4/2lPR8qcUrMmAEnhG7qFz8a pO8ilIjDuNWwmCU5Tm2TtbksakeW0tAq9c2cNWFdRsZ6QovUb82t+WMiAVYYILZB 8QS9YGDFlBTcw+6Rbwh7124uyW9Brf5o26h/HDq9okk7WzeEk1xADTes+SBiMDw6 pBr46gcusLTXVS9S9OBq6QVnIFsraBY9d3NFvXcl95U1dyFxKWhLibjiDVDAyfyE d18c2yXxHqutDkuBAnM4XgTmahHYU2ZMqWphZq5TAp3LrOIq7UVrBJPXFpEgHo/v Lhq+Wp5GPoaqztjbcyTc3UUUJ5E9yEBgO6Rh5RYWLO6sOZ0gWL6fGIpOhkVgLG9I 7DhBz68snoqJ9aOvAYJiZIm07ZCB+MafEN8vZA/nz9Uan9a66aWjZzC0mtzRZwjd 6z/wAXk00eVfXZshuu3fCIc3NxxfYwsQ7u2i8H3265Vk0Ok46ROujkFj/smqJArJ MUD4z1atxFxDUDyuH9Kb4g12d/bGA44L8tQgJTHGFhIZTBcWtLAwluFdwv4bXQLM 0JpLPbGkZ3eemEYt8bSSFXMbRBZSCcePOIk1NRfMufIcNTcacTn0Ti81roce05KM WplsUwEf7CjHCaC318tYCEe9Q5QRAzQogYMuBDGFMJ+e9zQRh1FlMZc7XvWIUOEE 3O5XeVUwfVI6 =rDVz -END PGP SIGNATURE End Message ---
Processed: Bug#996311 marked as pending in ruby-lapack
Processing control commands: > tag -1 pending Bug #996311 [src:ruby-lapack] ruby-lapack: FTBFS: ERROR: Test "ruby2.7" failed. Added tag(s) pending. -- 996311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996311: marked as pending in ruby-lapack
Control: tag -1 pending Hello, Bug #996311 in ruby-lapack 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/ruby-team/ruby-lapack/-/commit/ce6d76af49290d7b29bb7fa191cd5a7d96e093f6 Update Depends: ruby-narray >= 0.6.1.2-4 (Closes: #996311) Signed-off-by: Youhei SASAKI (this message was generated automatically) -- Greetings https://bugs.debian.org/996311
Processed: Bug#997630 marked as pending in pygithub
Processing control commands: > tag -1 pending Bug #997630 [src:pygithub] pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid. Added tag(s) pending. -- 997630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997630: marked as pending in pygithub
Control: tag -1 pending Hello, Bug #997630 in pygithub 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/packages/pygithub/-/commit/ec504e851b797dde4be0dc13dc2db6f7e0d14e23 setup.py: remove 2to3 (Closes: #997630) (this message was generated automatically) -- Greetings https://bugs.debian.org/997630
Bug#997209: marked as pending in eegdev
Control: tag -1 pending Hello, Bug #997209 in eegdev reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/eegdev/-/commit/a7bdb9ff56bf49b12b982d8a19d56fbe08b59280 Add patch to fix FTBFS with new autoconf (Closes: #997209) (this message was generated automatically) -- Greetings https://bugs.debian.org/997209
Processed: Bug#997209 marked as pending in eegdev
Processing control commands: > tag -1 pending Bug #997209 [src:eegdev] eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free' Added tag(s) pending. -- 997209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997209: [Help needed] eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free'
Nilesh Patra writes: > I have no idea why it can not find free() -- looks like something changed > with new autotools. > I don't know much about autotools, and need help to figure out what might be > wrong -- would you have any pointers? These errors look like fallout from a new check: > checking whether free is known to preserve errno... no Please try patching doc/examples/Makefile.am to add $(top_builddir)/lib/libgnu.la to both eegdev_acq_LDADD and recinxdf_LDADD. (libeegdev incorporates rpl_free and other needed rpl_* functions with hidden visibility, so purely for its own use.) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#995021: osmnx: autopkgtest regression on armhf: iteration over a 0-d array
On Mon, 1 Nov 2021 20:49:58 +0100 Paul Gevers wrote: Hello Paul, Is this run on all cores? Our armhf worker has 160 cores, so you may be running into limits you didn't expect. I can reproduce the issue on my amd64 box by substituting mp.cpu_count() by 160 in the called function. We are progressing. Cheers, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B OpenPGP_signature Description: OpenPGP digital signature
Bug#995346:
Processed: severity of 986487 is serious, tagging 986487, found 997414 in 0.25+git20210925-1, tagging 997518 ...
Processing commands for cont...@bugs.debian.org: > severity 986487 serious Bug #986487 [caftools] caftools: FTBFS with glibc >= 2.32 Severity set to 'serious' from 'normal' > tags 986487 + sid bookworm ftbfs Bug #986487 [caftools] caftools: FTBFS with glibc >= 2.32 Added tag(s) sid, ftbfs, and bookworm. > found 997414 0.25+git20210925-1 Bug #997414 [src:debomatic] debomatic: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' Marked as found in versions debomatic/0.25+git20210925-1. > tags 997518 + experimental Bug #997518 [src:magit-forge-el] magit-forge-el: FTBFS: make[2]: *** No rule to make target '/usr/share/emacs/site-lisp/elpa-src/closql-1.0.6'. Stop. Added tag(s) experimental. > found 997518 0.3.0-1 Bug #997518 [src:magit-forge-el] magit-forge-el: FTBFS: make[2]: *** No rule to make target '/usr/share/emacs/site-lisp/elpa-src/closql-1.0.6'. Stop. Marked as found in versions magit-forge-el/0.3.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 986487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986487 997414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997414 997518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997729: marked as done (ghdl: FTBFS: Unhandled version llvm 11.1.0)
Your message dated Tue, 02 Nov 2021 12:51:16 + with message-id and subject line Bug#997729: fixed in ghdl 1.0.0+dfsg-5 has caused the Debian Bug report #997729, regarding ghdl: FTBFS: Unhandled version llvm 11.1.0 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.) -- 997729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghdl Version: 1.0.0+dfsg-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/builddir/mcode' > for d in ieee/v87 ieee/v93 ieee/v08 std/v87 std/v93 std/v08 src/ieee > src/ieee/v87 src/ieee/v93 src/ieee2008 src/std src/std/v87 src/std/v93 > src/std/v08 src/synopsys src/synopsys/v08 src/upf; do \ > mkdir -p lib/ghdl/mcode/$d; \ > done > make[2]: Leaving directory '/<>/builddir/mcode' > Generate ortho_code-x86-flags.ads > Generate elf_arch.ads > Generate ghdlsynth_maybe.ads > Generate default_paths.ads > > > Configuring with llvm backend > > if [ -n "1" ]; then \ > cd /<>/builddir/llvm; \ > ../../configure --srcdir=../.. --prefix=/usr \ > --libdir=lib/ghdl/llvm --incdir=lib/ghdl/include \ > --disable-libghdl --enable-gplcompat \ > --with-llvm-config; \ > fi > Build machine is: x86_64-linux-gnu > Unhandled version llvm 11.1.0 > make[1]: *** [debian/rules:77: override_dh_auto_configure] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/ghdl_1.0.0+dfsg-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ghdl Source-Version: 1.0.0+dfsg-5 Done: Jonathan McDowell We believe that the bug you reported is fixed in the latest version of ghdl, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan McDowell (supplier of updated ghdl 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, 02 Nov 2021 08:49:46 + Source: ghdl Architecture: source Version: 1.0.0+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Jonathan McDowell Closes: 997729 Changes: ghdl (1.0.0+dfsg-5) unstable; urgency=medium . * Add llvm11.1.0.patch to enable building with LLVM 11.1 (Closes: #997729) Checksums-Sha1: 3cd349c275448d0242041cb613afaaa6bb36d2a9 2571 ghdl_1.0.0+dfsg-5.dsc 2ccb4c522d2895e995d41d9b4685c6748ed96218 21496 ghdl_1.0.0+dfsg-5.debian.tar.xz fda66fe844c141e7efc3f0ae2180dd25e05c9139 9927 ghdl_1.0.0+dfsg-5_amd64.buildinfo Checksums-Sha256: 072027cd21362f5361717a98e0c49f21350a0f3654725e9b8f13abcf3205ec2b 2571 ghdl_1.0.0+dfsg-5.dsc adb09ca7ca37eabec70165e22e71f7e099b28064122e0a3a1d5dd9bb591f8adf 21496 ghdl_1.0.0+dfsg-5.debian.tar.xz c2ecd04d8abb980098eda21e52a57a871ad5768423d0b0434acc0d6d03af0421 9927 ghdl_1.0.0+dfsg-5_amd64.buildinfo Files: e26f5dd33857ce664402076b5cda308d 2571 electronics optional ghdl_1.0.0+dfsg-5.dsc 46d22278f190053d516034eb5b745b57 21496 electronics optional ghdl_1.0.0+dfsg-5.debian.tar.xz 975948bdcb7c3132474fe4cccd01 9927 electronics optional ghdl_1.0.0+dfsg-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE/S8txYRw4wP3eXWjSgDzSK903QIFAmGBMhsRHG5vb2RsZXNA ZWFydGgubGkACgkQSgDzSK903QKokg/+IoQcDHIYNre53hB0Rdahv5ffftunCh50 0gLjdvJ8ks/bOs8/llY96hfloZxkgKkPyFkzIwwv411muFsa+vH+GePjLb7zBZMl
Processed: Re: python3-numpy: numpy.typing is missing
Processing control commands: > severity -1 serious Bug #998109 [python3-numpy] python3-numpy: numpy.typing is missing Severity set to 'serious' from 'important' > affects -1 src:pygmsh src:python-meshplex Bug #998109 [python3-numpy] python3-numpy: numpy.typing is missing Added indication that 998109 affects src:pygmsh and src:python-meshplex -- 998109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997209: [Help needed] eegdev: FTBFS: ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free'
Hi all, On Sat, 23 Oct 2021 21:11:26 +0200 Lucas Nussbaum wrote: Source: eegdev Version: 0.2-5 Relevant part (hopefully): > /usr/bin/ld: library-usage/eegdev_acq.o: in function `main': > ./doc/examples/library-usage/eegdev_acq.c:214: undefined reference to `rpl_free' > /usr/bin/ld: ./doc/examples/library-usage/eegdev_acq.c:215: undefined reference to `rpl_free' > collect2: error: ld returned 1 exit status I have no idea why it can not find free() -- looks like something changed with new autotools. I don't know much about autotools, and need help to figure out what might be wrong -- would you have any pointers? Any help is appreciated. Nilesh OpenPGP_signature Description: OpenPGP digital signature
Bug#980627: ruby-databojects-mysql (was: [RFH] Fix FTBFSes to kick off the ruby3.0 transition)
Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro: [..] > * ruby-databojects-mysql [..] My finding so far is that the debian/start_mysqld_and_auto_install.sh scripts requires elevated permissions, but fakeroot is not enough: > + mysql_install_db --no-defaults --datadir=/tmp/tmp.BZtu29C6kk --force > --skip-name-resolve --user=root > chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': > Permission denied > Couldn't set an owner to > '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool'. > It must be root, the PAM authentication plugin doesn't work otherwise.. If I run the whole thing as root, it works (also if I run `sudo gbp buildpackage`). But I don't see a way to achieve this by default. I was reading the documentation about Rules-Requires-Root and DEB_GAIN_ROOT_CMD in our policy and also looked at the libpcap2 package. But all my attempts failed. As long as DEB_GAIN_ROOT_CMD is "fakeroot" (default; e.g. set when using Rules- Requires-Root: binary-targets or dpkg/target-subcommand) the above error appears. If try to set DEB_GAIN_ROOT_CMD to 'sudo -nE --' (as suggested in the policy) I either get "not found" or "requires a password" error (and I don't want to change my sudo policy). I also tried to set the setuid bit for debian/start_mysqld_and_auto_install.sh and I still get the above error. I don't have any other ideas. Maybe we can use mysql-sandbox? Maybe we have to avoid running mysql_install_db or use a fake .my.cnf? I don't know. PS: The autopkgtests need elevated permissions as well it seems (and also a running mysql server judging from the error message). HTH and regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#998296: marked as done (adios: autopktest failure)
Your message dated Tue, 02 Nov 2021 12:33:26 + with message-id and subject line Bug#998296: fixed in adios 1.13.1-30 has caused the Debian Bug report #998296, regarding adios: autopktest failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: adios Version: 1.13.1-29 Severity: serious X-Debbugs-Cc: sramac...@debian.org autopkgtests fail with: | Broken autopkgtest-satdep:amd64 Depends on libadios-mpi-dev:amd64 < none @un H > | Removing autopkgtest-satdep:amd64 because I can't find libadios-mpi-dev:amd64 See https://ci.debian.net/data/autopkgtest/testing/amd64/a/adios/16336328/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: adios Source-Version: 1.13.1-30 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of adios, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated adios 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: Tue, 02 Nov 2021 11:49:42 + Source: adios Architecture: source Version: 1.13.1-30 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 998296 Changes: adios (1.13.1-30) unstable; urgency=medium . * Ensure libadios-*-dev provide libadios-mpi-dev * Fix autopkgtest to work with libadios-openmpi-dev | libadios-mpi-dev Closes: #998296 Checksums-Sha1: 7c7d9050f7962d5f74026a656927a8cb1abd8b16 3138 adios_1.13.1-30.dsc 0d063f7745e5ad6aea1c24a515e0e6dcca2d2040 24120 adios_1.13.1-30.debian.tar.xz Checksums-Sha256: ce279658af1683537521dc5ec1a71538cb2667c2133a8ba5d83777fb813889d5 3138 adios_1.13.1-30.dsc cfcda2381efbd1a729b777fb01103c37c24dfd57c4eaa05f84d56cd2f7b7ade2 24120 adios_1.13.1-30.debian.tar.xz Files: 86fa2c5cf896322e41473e671e294054 3138 science optional adios_1.13.1-30.dsc 2e1106fd458fd0110e93cb893f7f32fc 24120 science optional adios_1.13.1-30.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmGBLOYACgkQy+a7Tl2a 06XhYQ/9Hgl7evWGnnjWtNXqulNzSMh3rp7AMqdRla4wNDClV1t/jETBWbsO+ud2 KyrRn4uFALbZ4fSoC9OtCWungbbKAdrS6p12SP64s3jHSpCdXE4FlWPkBo3LblRM 7YsirWpPaBSixCwy3Au5ktakeZ3kufa2tl0EKTWI3NbFmeKbxY45h5m6gYOwqiIu ZMlXzfHEP6/S182m2u+zmuykDSNOFphqpVzX3P3y7sOSSJqzMINM1jKzL4a4t3hk qOPRAfZxvrbPylaccrzPfQr13AaKHcuvS4AR/EvRLSLQH4GPYev3xNUjTytIbHGC 5pQ0WqSYBjGmjkhCKG3PTQ9QZ3CixKtC6wj/+NhbE2eLVmkzGy/HtDrpK3j4PpeI PR5tXVj8QtKbS+Z1aeQ1N2wPas6oRqssYx22LjsI/j0e/PmfkorpZ4wIry8kPoEB MUgwsSmBXCRnB6ia4w33Du+O55+M4MD2w0P6xrXj8WDdyP0CeWy52iCkXS5191AM 2n8BXgI0OKdvn+vqHB+eXC4cDYMGskAB+6YmimHChEmY+0peBBRBxzVIKH7XAVod s9mrZiNA6FSZJNQKKHZAinn5qSgFMG1F2m2bPUT/G5oKct6R7P0P9QJeWYpiKaRn 2Tj38wQKeNOXnPQZBLTVd9lpqw774y+8ysWDGUSYvMAh74AXlKw= =7+LZ -END PGP SIGNATURE End Message ---
Bug#997385: marked as done (pydicom: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')
Your message dated Tue, 02 Nov 2021 12:34:05 +
with message-id
and subject line Bug#997385: fixed in pydicom 2.0.0-2
has caused the Debian Bug report #997385,
regarding pydicom: FTBFS: AttributeError: 'Sphinx' object has no attribute
'add_stylesheet'
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.)
--
997385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pydicom
Version: 2.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> pybuild --build --test-pytest -i python{version} -p 3.9
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying dicom.py -> /<>/.pybuild/cpython3_3.9_pydicom/build
> creating /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/filereader.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/errors.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/_dicom_dict.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/__init__.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/uid.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/filebase.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/multival.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/misc.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/env_info.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/dataelem.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/dicomio.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/_uid_dict.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/compat.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/_version.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/tag.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/jsonrep.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/dataset.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/values.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/config.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/sequence.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/filewriter.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/_private_dict.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/datadict.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/valuerep.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/fileutil.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/_storage_sopclass_uids.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/charset.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/encaps.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> copying pydicom/dicomdir.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom
> creating
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/__init__.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/util.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/jpeg_ls_handler.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/numpy_handler.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/pillow_handler.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/gdcm_handler.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/pixel_data_handlers
> copying pydicom/pixel_data_handlers/rle_handler.py ->
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/pixel_data_handlers
> creating
> /<>/.pybuild/cpython3_3.9_pydicom/build/pydicom/overlay_data_handlers
> copying pydicom/overlay_data_handlers/__init__.py ->
>
Bug#998108: firefox freezes shortly after start
On Sat, 30 Oct 2021 15:04:01 +0200 Christoph Anton Mitterer wrote: > Since about yesterday (possibly since the rebuilt package came in) > firefox freezes shortly after being started. > There is no high CPU activity then, it just takes no input anymore > (no keyboard, no mouse clicks). > This also happens in --safe-mode. I'm encountering this as well. It happens slower if I just browse, and much much faster if I use something like WebGL.
Processed: Bug#997385 marked as pending in pydicom
Processing control commands: > tag -1 pending Bug #997385 [src:pydicom] pydicom: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Added tag(s) pending. -- 997385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997385: marked as pending in pydicom
Control: tag -1 pending Hello, Bug #997385 in pydicom reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/pydicom/-/commit/445ebd3931d2d77c15187bfc05465843474326ce Add patch to fix FTBFS (Closes: #997385) (this message was generated automatically) -- Greetings https://bugs.debian.org/997385
Processed: retitle 997484 to python3-sqlalchemy: Undeclared dependency on python3-greenlet!=0.4.17
Processing commands for cont...@bugs.debian.org: > retitle 997484 python3-sqlalchemy: Undeclared dependency on > python3-greenlet!=0.4.17 Bug #997484 [python3-sqlalchemy] python3-sqlalchemy: Undeclared dependency on python3-greenlet Changed Bug title to 'python3-sqlalchemy: Undeclared dependency on python3-greenlet!=0.4.17' from 'python3-sqlalchemy: Undeclared dependency on python3-greenlet'. > thanks Stopping processing here. Please contact me if you need assistance. -- 997484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995843: abook: complete d/copyright file
Hey Jochen, resolving would need to enhance the copyright file so that it fulfills all the required information. Bastian already did a good job and likely the patch provided should be sufficient for that. I haven't gotten around yet to upload that, but plan to do so in the next few days. I likely will move the packaging from my private git instance to salsa, and if you are still interested I can add you to the repository indeed. Thanks for your interest, Rhonda * Jochen Sprickerhof [2021-11-02 08:20:15 CET]: > Hi Rhonda, > > abook is marked for autoremoval in two days due to this bug, can you comment > on how to resolve it? > > I would be happy to help maintain abook, if you need help. > > Cheers Jochen > > * Bastian Germann [2021-10-13 14:40]: > > Control: tags -1 patch > > > > Hi, > > > > A copyright file for abook with the necessary fixes for this bug is > > enclosed. > > Please include it in a new package revision. > > > > Thanks, > > Bastian > > > Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ > > Upstream-Name: abook > > Upstream-Contact: Jaakko Heinonen > > Source: http://abook.sourceforge.net/ > > > > Files: * > > Copyright: 2005, Jaakko Heinonen > > Comment: No license version is specified for most of the code. > > Some GPL-2+ files make the project as a whole GPL-2+. > > License: GPL-2+ > > > > Files: abook.1 abookrc.5 > > Copyright: Alan Ford > > License: GPL-2+ > > > > Files: aclocal.m4 config.rpath Makefile.in m4/* > > Copyright: (see individual files) > > Comment: Some files come with the disclaimer, some do not. > > License: FSFULLR > > > > Files: config.guess config.sub > > Copyright: 1992-2013 Free Software Foundation, Inc. > > License: GPL-3+ with Autoconf exception > > > > Files: depcomp > > Copyright: 1999-2013 Free Software Foundation, Inc. > > License: GPL-2+ > > > > Files: getname.c > > Copyright: This code was taken from hypermail > > modified by Jaakko Heinonen > > . > > For strcpymax() function: > > Copyright (C) 1994, 1995 Enterprise Integration Technologies Corp. > > VeriFone Inc./Hewlett-Packard. All Rights Reserved. > > Comment: See https://bugs.debian.org/979098 for details on assuming GPL-2+ > > License: GPL-2+ > > > > Files: getopt* > > Copyright: 1987-1997 Free Software Foundation, Inc. > > License: LGPL-2+ > > > > Files: install-sh > > Copyright: 1994 X Consortium > > License: X11 > > > > Files: ldif.c > > Copyright: 1992-1996 Regents of the University of Michigan. > > Comment: adapted to use with abook by JH > > License: Michigan > > Redistribution and use in source and binary forms are permitted > > provided that this notice is preserved and that due credit is given > > to the University of Michigan at Ann Arbor. The name of the University > > may not be used to endorse or promote products derived from this > > software without specific prior written permission. This software > > is provided ``as is'' without express or implied warranty. > > > > Files: mbswidth.? > > Copyright: 2000-2002 Free Software Foundation, Inc. > > License: GPL-2+ > > > > Files: misc.c > > Copyright: Jaakko Heinonen > > 1994 Lars Wirzenius > > Comment: BSD-2-clause covers the getaline() function. > > License: GPL-2+ and BSD-2-clause > > > > Files: missing > > Copyright: 1996-2013 Free Software Foundation, Inc. > > License: GPL-2+ > > > > Files: po/fr.po po/it.po po/sv.po > > Copyright: 2005 Free Software Foundation, Inc. > > License: GPL-2+ > > > > Files: vcard.c > > Copyright: 2012, Raphaël Droz > > License: GPL-2+ > > > > Files: views.c > > Copyright: Cedric Duval > > License: GPL-2+ > > > > Files: xmalloc.c > > Copyright: 2005 Jaakko Heinonen > > License: BSD-2-clause > > > > Files: debian/* > > Copyright: 2000, Alan Ford > > 2003, Rhonda D'Vine > > 2015, Denis Briand > > License: WTFPLv2 > > > > License: GPL-2+ > >This program is free software; you can redistribute it and/or modify > >it under the terms of the GNU General Public License as published by > >the Free Software Foundation; either version 2 of the License, or > >(at your option) any later version. > >. > >This program is distributed in the hope that it will be useful, > >but WITHOUT ANY WARRANTY; without even the implied warranty of > >MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > >GNU General Public License for more details. > >. > >You should have received a copy of the GNU General Public License > >along with this program; if not, write to the Free Software > >Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, > >MA 02110-1301 USA. > >. > > On Debian GNU/Linux systems, the complete text of the GNU General > > Public License version 2 can be found in `/usr/share/common-licenses/GPL-2', > > later versions can be found in the same directory. > > > > License: GPL-3+ with Autoconf
Processed: Re: Bug#998126: pipewire-pulse-dbgsym: dbgsym files overlap between packages
Processing control commands: > tags -1 help Bug #998126 [src:pipewire] pipewire-pulse-dbgsym: dbgsym files overlap between packages Added tag(s) help. -- 998126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998126: pipewire-pulse-dbgsym: dbgsym files overlap between packages
Control: tags -1 help Hi, Le sam. 30 oct. 2021 à 21:09, Martin-Éric Racine a écrit : > > Selecting previously unselected package libpipewire-0.3-0-dbgsym:i386. > (Reading database ... 127295 files and directories currently installed.) > Preparing to unpack .../libpipewire-0.3-0-dbgsym_0.3.39-3_i386.deb ... > Unpacking libpipewire-0.3-0-dbgsym:i386 (0.3.39-3) ... > Selecting previously unselected package pipewire-bin-dbgsym. > Preparing to unpack .../pipewire-bin-dbgsym_0.3.39-3_i386.deb ... > Unpacking pipewire-bin-dbgsym (0.3.39-3) ... > Selecting previously unselected package pipewire-pulse-dbgsym. > Preparing to unpack .../pipewire-pulse-dbgsym_0.3.39-3_i386.deb ... > Unpacking pipewire-pulse-dbgsym (0.3.39-3) ... > dpkg: error processing archive > /var/cache/apt/archives/pipewire-pulse-dbgsym_0.3.39-3_i386.deb (--unpack): > trying to overwrite > '/usr/lib/debug/.build-id/cd/853193bbd003d08fa699c60b1be36cccb92034.debug', > which is also in package pipewire-bin-dbgsym 0.3.39-3 > Errors were encountered while processing: > /var/cache/apt/archives/pipewire-pulse-dbgsym_0.3.39-3_i386.deb > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) > I am not sure to understand why pipewire-bin-dbgsym and pipewire-pulse-dbgsym have overlapping files. Any hint how to solve this? Best, Dylan
Bug#997245: marked as done (lynkeos.app: FTBFS: MyImageAligner.m:851:16: error: too few arguments to function ‘dgesvd_’)
Your message dated Tue, 02 Nov 2021 11:49:41 + with message-id and subject line Bug#997245: fixed in lynkeos.app 3.4+dfsg1-3 has caused the Debian Bug report #997245, regarding lynkeos.app: FTBFS: MyImageAligner.m:851:16: error: too few arguments to function ‘dgesvd_’ 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.) -- 997245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lynkeos.app Version: 3.4+dfsg1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc /<>/application/GNUstep/../Sources/MyImageAlignerView.m -c \ > -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 > -DCURRENT_PROJECT_VERSION=340.0 -I. -I.. > -I/<>/application/GNUstep.. > -I/<>/application/GNUstep/../Sources > -I/<>/application/GNUstep/../ThreadConnectionSources > -I/<>/application/GNUstep/../ThirdPartySources/SMDoubleSlider > -DNO_FRAMEWORK_CHECK=1 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 > -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions > -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN > -DGSDIAGNOSE -Wno-import -g -O2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 > -Wno-unknown-pragmas -Wno-cpp -fconstant-string-class=NSConstantString -I. > -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ >-o obj/Lynkeos.obj/MyImageAlignerView.m.o > /<>/application/GNUstep/../Sources/MyImageAligner.m: In function > ‘-[MyImageAligner processItem:]’: > /<>/application/GNUstep/../Sources/MyImageAligner.m:851:16: > error: too few arguments to function ‘dgesvd_’ > 851 |dgesvd_(, , , , covariances, , > |^~~ > In file included from /usr/include/lapack.h:11, > from /usr/include/lapacke.h:36, > from > /<>/application/GNUstep/../Sources/MyImageAligner.m:29: > /usr/include/lapack.h:3377:6: note: declared here > 3377 | void LAPACK_dgesvd_base( > | ^~ > make[5]: *** [/usr/share/GNUstep/Makefiles/rules.make:515: > obj/Lynkeos.obj/MyImageAligner.m.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/lynkeos.app_3.4+dfsg1-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: lynkeos.app Source-Version: 3.4+dfsg1-3 Done: Yavor Doganov We believe that the bug you reported is fixed in the latest version of lynkeos.app, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov (supplier of updated lynkeos.app package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 27 Oct 2021 18:16:36 +0300 Source: lynkeos.app Architecture: source Version: 3.4+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian GNUstep maintainers Changed-By: Yavor Doganov Closes: 997245 Changes: lynkeos.app (3.4+dfsg1-3) unstable; urgency=medium . * debian/patches/gnustep-port.patch: Fix FTBFS with lapack/3.10.0 (Closes: #997245). * debian/control (Build-Depends): Remove libgnustep-gui-dev version requirement; satisfied in bullseye. (Breaks, Replaces): Remove; obsolete. (Standards-Version): Bump to 4.6.0; no changes needed. * debian/lynkeos.app-common.lintian-overrides: Remove breakout-link, reportedly unused now. Checksums-Sha1: bdc6922705e9607a213cf6466ac9a75bd875b7ef 2197 lynkeos.app_3.4+dfsg1-3.dsc dc37833ecdbfedb1c11c2c82d966b307ba83996b
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Hi Christoph, Le mercredi 06 octobre 2021 à 23:14 +0200, Christoph Berg a écrit : > Package: pgloader > Version: 3.6.2-1 > Severity: grave > Tags: ftbfs > > pgloader is currently not supporting PG14's new default of scram > authentication: > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/pgloader/15809976/log.gz > > KABOOM! > FATAL error: Failed to connect to pgsql at "localhost" (port 5433) as user > "postgres": 10 fell through ECASE expression. Wanted one of (0 2 3 4 5 6 7 8). > Date/time: 2021-10-06-16:12! > An unhandled error condition has been signalled: >Failed to connect to pgsql at "localhost" (port 5433) as user "postgres": > 10 fell through ECASE expression. Wanted one of (0 2 3 4 5 6 7 8). > > To fix this, cl-postmodern needs upgrading, but the new version > requires (at least) the yet-unpackaged "uax-15" and "global-vars" CL > modules. I am going to package cl-uax-15 and cl-global-vars (ITPs are marked as blocking the present bug), and then upgrade cl-postmodern. Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Processed: ITP: cl-global-vars -- efficient global variables in Common Lisp
Processing control commands: > block 995846 by -1 Bug #995846 [pgloader] FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14 995846 was blocked by: 998321 995846 was not blocking any bugs. Added blocking bug(s) of 995846: 998322 -- 995846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995846 998322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
