Bug#1000586: marked as done (dcmstack: (autopkgtest) needs update for python3.10: No module named 'numpy.core._multiarray_umath')
Your message dated Sat, 4 Dec 2021 08:50:24 +0100 with message-id and subject line [Advent bug squashing] Bug is fixed due to upload of recent numpy has caused the Debian Bug report #1000586, regarding dcmstack: (autopkgtest) needs update for python3.10: No module named 'numpy.core._multiarray_umath' 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.) -- 1000586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dcmstack Version: 0.8-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3-defaults Dear maintainer(s), With a recent upload of python3-defaults the autopkgtest of dcmstack fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.9.8-1 dcmstack from testing0.8-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists what's new in Python2.10, it may help to identify what needs to be updated. Additionally I was told that you may be missing a call to dh_numpy3 somewhere. 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=python3-defaults https://ci.debian.net/data/autopkgtest/testing/arm64/d/dcmstack/16984530/log.gz Testing with python3.10 in /tmp/autopkgtest-lxc.n5nw69fn/downtmp/autopkgtest_tmp: = test session starts == platform linux -- Python 3.10.0+, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- /usr/bin/python3.10 cachedir: .pytest_cache rootdir: /tmp/autopkgtest-lxc.n5nw69fn/downtmp/autopkgtest_tmp collecting ... collected 0 items / 4 errors ERRORS __ ERROR collecting test/test_cli.py ___ ImportError while importing test module '/tmp/autopkgtest-lxc.n5nw69fn/downtmp/autopkgtest_tmp/test/test_cli.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3/dist-packages/numpy/core/__init__.py:22: in from . import multiarray /usr/lib/python3/dist-packages/numpy/core/multiarray.py:12: in from . import overrides /usr/lib/python3/dist-packages/numpy/core/overrides.py:7: in from numpy.core._multiarray_umath import ( E ModuleNotFoundError: No module named 'numpy.core._multiarray_umath' During handling of the above exception, another exception occurred: /usr/lib/python3.10/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) test/test_cli.py:6: in import numpy as np /usr/lib/python3/dist-packages/numpy/__init__.py:140: in from . import core /usr/lib/python3/dist-packages/numpy/core/__init__.py:48: in raise ImportError(msg) E ImportError: E E IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE! E E Importing the numpy C-extensions failed. This error can happen for E many reasons, often due to issues with your setup or how NumPy was E installed. E E We have compiled some common reasons and troubleshooting tips at: E E https://numpy.org/devdocs/user/troubleshooting-importerror.html E E Please note and check the following: E E * The Python version is: Python3.10 from "/usr/bin/python3.10" E * The NumPy version is: "1.19.5" E E and make sure that they are the versions you expect. E Please carefully study the documentation linked above for further help. E E Original error was: No module named 'numpy.core._multiarray_umath' ERROR collecting test/test_dcmmeta.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.n5nw69fn/downtmp/autopkgtest_tmp/test/test_dcmmeta.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3/dist-packages/numpy/core/__init__.py:22: in from . import multiarray /usr/lib/python3/dist-packages/numpy/core/multiarray.py:12: in from . import overrides /us
Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'
Hi Robert, thanks a lot for your analysis. Am Fri, Dec 03, 2021 at 03:36:40PM -0800 schrieb Robert J. Hijmans: > Andreas, > > The background of this problem is the change in dependency between "raster" > and "terra". "terra" was dependent on "raster"; now it is the other way > around. This change was made in terra 1.4-07, 1.4-09 and 1.4-11 that were > released between 2021-10-05 and 2021-10-11, and in raster 3.5-2 > (2021-10-11). > > In the attachment I show the behavior of `library(satellite)` with the > raster package prior to 2021-10-11, with the current versions, and for > possible intermediate steps. It shows that you can get the warnings you see > if you have current versions of terra/raster but an old version of > satellite. > > From what I can tell from this log: > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-satellite/16823806/log.gz > you are using satellite_1.0.4 and raster_3.5-2 (current versions), and > terra_1.4-11 (the current version is 1.4-22; but 1.4-11 should be OK). > > Is it possible that your session is actually loading satellite_1.0.2? I do not think so since you see: Get:1 http://deb.debian.org/debian testing/main r-cran-satellite 1.0.4-1 (dsc) [2,198 B] so this is the version that is testet. Kind regards Andreas. > On Tue, Nov 30, 2021 at 12:48 AM Andreas Tille wrote: > > > Control: forwarded -1 Robert J. Hijmans , Florian > > Detsch > > Control: tags -1 upstream > > Control: tags -1 help > > > > Hi Robert and Florian, > > > > I'm contacting you as the maintainers or raster and satellite. As you > > can see below in the Debian packaged versions of these packages some > > conflict was raised in the test of satellite after the latest version of > > raster was uploaded. > > > > I'm perfectly aware that the packages are tested on CRAN and thus I > > assume that possibly some special circumstances in the Debian packaged > > version might lead to the issue that is reported in the bug below. I > > wonder whether you can give some hints how to solve the conflict in the > > test (at the very end of this mail). > > > > Thanks a lot for your help > > > > Andreas. > > > > Am Sun, Nov 21, 2021 at 09:24:52PM +0100 schrieb Paul Gevers: > > > Source: r-cran-raster, r-cran-satellite > > > Control: found -1 r-cran-raster/3.5-2-1 > > > Control: found -1 r-cran-satellite/1.0.4-1 > > > Severity: serious > > > Tags: sid bookworm > > > X-Debbugs-CC: debian...@lists.debian.org > > > User: debian...@lists.debian.org > > > Usertags: breaks needs-update > > > > > > Dear maintainer(s), > > > > > > With a recent upload of r-cran-raster the autopkgtest of r-cran-satellite > > > fails in testing when that autopkgtest is run with the binary packages of > > > r-cran-raster from unstable. It passes when run with only packages from > > > testing. In tabular form: > > > > > >passfail > > > r-cran-raster from testing3.5-2-1 > > > r-cran-satellite from testing1.0.4-1 > > > all others from testingfrom testing > > > > > > I copied some of the output at the bottom of this report. > > > > > > Currently this regression is blocking the migration of r-cran-raster to > > > testing [1]. Due to the nature of this issue, I filed this bug report > > > against both packages. Can you please investigate the situation and > > reassign > > > the bug to the right package? > > > > > > More information about this bug and the reason for filing it can be > > found on > > > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > > > > > Paul > > > > > > [1] https://qa.debian.org/excuses.php?package=r-cran-raster > > > > > > > > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-satellite/16823806/log.gz > > > > > > BEGIN TEST testthat.R > > > > > > R version 4.1.2 (2021-11-01) -- "Bird Hippie" > > > Copyright (C) 2021 The R Foundation for Statistical Computing > > > Platform: x86_64-pc-linux-gnu (64-bit) > > > > > > R is free software and comes with ABSOLUTELY NO WARRANTY. > > > You are welcome to redistribute it under certain conditions. > > > Type 'license()' or 'licence()' for distribution details. > > > > > > R is a collaborative project with many contributors. > > > Type 'contributors()' for more information and > > > 'citation()' on how to cite R or R packages in publications. > > > > > > Type 'demo()' for some demos, 'help()' for on-line help, or > > > 'help.start()' for an HTML browser interface to help. > > > Type 'q()' to quit R. > > > > > > > library(testthat) > > > > library(satellite) > > > Loading required package: raster > > > Loading required package: sp > > > code for methods in class "Rcpp_SpatCategories" was not checked for > > > suspicious field assignments (recommended package 'codetools' not > > > available?) > > > code for methods in class "Rcpp_SpatCategories" was not checked for > > > suspicious field assignments (recommended package 'codetools' not > > > available
Bug#998481: marked as done (ruby-puppet-syntax: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so)
Your message dated Sat, 04 Dec 2021 06:48:45 + with message-id and subject line Bug#984082: fixed in leatherman 1.12.1+dfsg-1.2 has caused the Debian Bug report #984082, regarding ruby-puppet-syntax: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so 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.) -- 984082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-puppet-syntax Version: 3.1.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cannot load such file -- libfacter.so > # ./lib/puppet-syntax/templates.rb:2:in `' > # ./lib/puppet-syntax.rb:3:in `' > # ./spec/spec_helper.rb:2:in `' > # ./spec/puppet-syntax_spec.rb:1:in `' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- libfacter.so > # ./lib/puppet-syntax/templates.rb:2:in `' > No examples found. > > Finished in 0.4 seconds (files took 0.17447 seconds to load) > 0 examples, 0 failures, 5 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available from: http://qa-logs.debian.net/2021/11/04/ruby-puppet-syntax_3.1.0-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: leatherman Source-Version: 1.12.1+dfsg-1.2 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of leatherman, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated leatherman package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Dec 2021 07:26:29 +0100 Source: leatherman Architecture: source Version: 1.12.1+dfsg-1.2 Distribution: unstable Urgency: medium Maintainer: Puppet Package Maintainers Changed-By: Daniel Leidert Closes: 984082 Changes: leatherman (1.12.1+dfsg-1.2) unstable; urgency=medium . * Non-maintainer upload. * d/patches/update-code-to-compile-with-new-compilers.patch: Add patch. - Fix FTBFS with GCC 11 by upstream patch (closes: #984082). * d/patches/series: Add new patch. Checksums-Sha1: 5f3d21bc0496d192216e992e5fa3d2f2736e2cf1 2382 leatherman_1.12.1+dfsg-1.2.dsc 42a7cd13b033291e9a8224d03c9d5c9903910828 7332 leatherman_1.12.1+dfsg-1.2.debian.tar.xz ff09548db58f35db92efe71aaadab120a60c3bbd 9206 leatherman_1.12.1+dfsg-1.2_amd64.buildinfo Checksums-Sha256: 3e8754fb7c5063e4ac3ff4d0d4bc81e5a86aa616f17eebe6cab67acc81dc33e0 2382 leatherman_1.12.1+dfsg-1.2.dsc 29506d9ebfc5d2a173c7e7bfc40c774ded128e6e92e000f5f48fc6c7a03ca599 7332 leatherman_1.12.1+dfsg-1.2.debian.tar.xz 032c1ffb86f7ca17f7638c47c9e48fda563dde424a5d8dbdff28ffe9d0c4b5a7 9206 leatherman_1.12.1+dfsg-1.2_amd64.buildinfo Files: c84cff7e5ad5f0d6511a7174b40cf3f3 2382 libs optional leatherman_1.12.1+dfsg-1.2.dsc 95c676a713ed5c9087454bd57c7d97b3 7332 libs optional leatherman_1.12.1+dfsg-1.2.debian.tar.xz 0d98ed21d01dc38fa9c46f650460b266 9206 libs optional leatherman_1.12.1+dfsg-1.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGrC+EACgkQS80FZ8KW 0F2aZg/9H2pVfKSwvueIs+gGCmkh3M2yHIF5UJtoKhzp7
Bug#984082: marked as done (leatherman: ftbfs with GCC-11)
Your message dated Sat, 04 Dec 2021 06:48:45 + with message-id and subject line Bug#984082: fixed in leatherman 1.12.1+dfsg-1.2 has caused the Debian Bug report #984082, regarding leatherman: 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.) -- 984082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:leatherman Version: 1.12.1+dfsg-1.1 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/leatherman_1.12.1+dfsg-1.1_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. [...] Scanning dependencies of target libtest1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f dynamic_library/CMakeFiles/libtest1.dir/build.make dynamic_library/CMakeFiles/libtest1.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 14%] Building CXX object dynamic_library/CMakeFiles/libtest1.dir/tests/test-lib/hello.cc.o cd /<>/obj-x86_64-linux-gnu/dynamic_library && /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DLEATHERMAN_LOCALE_INSTALL=\"/usr/share/locale\" -DLEATHERMAN_LOGGING_LINE_NUMBERS -DLEATHERMAN_LOGGING_NAMESPACE=\"leatherman.dynamic_library\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/<>/obj-x86_64-linux-gnu\" -DPROJECT_NAME=\"leatherman\" -Dlibtest1_EXPORTS -I/<>/nowide/inc -I/<>/logging/inc -I/<>/util/inc -I/<>/locale/inc -I/<>/dynamic_library/inc -Wno-maybe-uninitialized -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/libtest1.dir/tests/test-lib/hello.cc.o -c /<>/dynamic_library/tests/test-lib/hello.cc [ 15%] Linking CXX shared library ../../lib/libmock_curl.so cd /<>/obj-x86_64-linux-gnu/curl/tests && /usr/bin/cmake -E cmake_link_script CMakeFiles/mock_curl.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -Wno-maybe-uninitialized -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -shared -Wl,-soname,libmock_curl.so -o ../../lib/libmock_curl.so CMakeFiles/mock_curl.dir/mock_curl.cc.o make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 15%] Built target mock_curl make -f dynamic_library/CMakeFiles/libtest.dir/build.make dynamic_library/CMakeFiles/libtest.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/dynamic_library /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/dynamic_library /<>/obj-x86_64-linux-gnu/dynamic_library/CMakeFiles/libtest.dir/DependInfo.cmake --color= Dependee "/<>/obj-x86_64-linux-gnu/dynamic_library/CMakeFiles/libtest.dir/DependInfo.cmake" is newer than depender "/<>/obj-x86_64-linux-gnu/dynamic_library/CMakeFiles/libtest.dir/depend.internal". Dependee "/<>/obj-x86_64-linux-gnu/dynamic_library/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/<>/obj-x86_64-linux-gnu/dynamic_library/CMakeFiles/libtest.dir/depend.internal". Scanning dependencies of target libtest make[3]: Leaving
Bug#984116: marked as done (facter: ftbfs with GCC-11)
Your message dated Sat, 04 Dec 2021 06:48:45 + with message-id and subject line Bug#984082: fixed in leatherman 1.12.1+dfsg-1.2 has caused the Debian Bug report #984082, regarding facter: 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.) -- 984082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:facter Version: 3.14.12-1 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/facter_3.14.12-1_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. [...] [ 24%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/facts/resolvers/zpool_resolver.cc.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DHAS_LTH_EXPAND -DHAS_LTH_GET_INT -DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/<>/obj-x86_64-linux-gnu\" -DPROJECT_NAME=\"FACTER\" -DUSE_BLKID -DUSE_CPPHOCON -DUSE_CURL -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/<>/lib/inc -Wextra -std=c++11 -Wall -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -Werror -Wno-maybe-uninitialized -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/libfactersrc.dir/src/facts/resolvers/zpool_resolver.cc.o -c /<>/lib/src/facts/resolvers/zpool_resolver.cc [ 25%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/facts/resolvers/zone_resolver.cc.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DHAS_LTH_EXPAND -DHAS_LTH_GET_INT -DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/<>/obj-x86_64-linux-gnu\" -DPROJECT_NAME=\"FACTER\" -DUSE_BLKID -DUSE_CPPHOCON -DUSE_CURL -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/<>/lib/inc -Wextra -std=c++11 -Wall -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -Werror -Wno-maybe-uninitialized -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/libfactersrc.dir/src/facts/resolvers/zone_resolver.cc.o -c /<>/lib/src/facts/resolvers/zone_resolver.cc [ 26%] Building CXX object lib/CMakeFiles/libfactersrc.dir/src/facts/resolvers/zfs_resolver.cc.o cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DHAS_LTH_EXPAND -DHAS_LTH_GET_INT -DLEATHERMAN_I18N -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/<>/obj-x86_64-linux-gnu\" -DPROJECT_NAME=\"FACTER\" -DUSE_BLKID -DUSE_CPPHOCON -DUSE_CURL -DUSE_OPENSSL -DUSE_YAMLCPP -Dlibfacter_EXPORTS -I/<>/lib/inc -Wextra -std=c++11 -Wall -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -Werror -Wno-maybe-uninitialized -g -O2 -f
Bug#997363: libtorrent-rasterbar: FTBFS: configure: error: *** A compiler with support for C++17 language features is required.
Control: tags -1 + patch [Stefano Rivera] > Presumably resolved in 2.0.0 in NEW, that doesn't use autoconf any more. Perhaps, but as NEW processing these days take a long time, as a user of the library I would prefer a fix for 1.2.14-1 in the mean time. The easiest fix seem to be to bypass the c++ standard detector which fail in configure.ac, causing the problematic test for C++17, while both C++11 and C++14 would work, by adding --with-cxx-standard=14 like this: --- rules.orig 2021-12-04 07:42:25.578757615 +0100 +++ rules 2021-12-04 07:37:18.662074573 +0100 @@ -13,7 +13,8 @@ PYTHON3=$(shell py3versions -vr) ALLPY=$(PYTHON3) -CONFIGURE_ARGS = --with-libiconv --with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) +CONFIGURE_ARGS = --with-libiconv --with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \ + --with-cxx-standard=14 %: dh $@ --with python3 It would also help a lot if the next upload is a source only upload. -- Happy hacking Petter Reinholdtsen
Processed: Re: Bug#997363: libtorrent-rasterbar: FTBFS: configure: error: *** A compiler with support for C++17 language features is required.
Processing control commands: > tags -1 + patch Bug #997363 [src:libtorrent-rasterbar] libtorrent-rasterbar: FTBFS: configure: error: *** A compiler with support for C++17 language features is required. Added tag(s) patch. -- 997363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998579: marked as done (gnome-connections: build-time tests access internet)
Your message dated Sat, 04 Dec 2021 02:34:34 +
with message-id
and subject line Bug#998579: fixed in gnome-connections 41.2-1
has caused the Debian Bug report #998579,
regarding gnome-connections: build-time tests access internet
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.)
--
998579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-connections
Version: 41.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.60.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-connections
> Project version: 41.1
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10)
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.37
> Vala compiler for the host machine: valac (valac 0.54.2)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Configuring config.h.in using configuration
> Program /usr/bin/meson found: YES (/usr/bin/meson)
> Configuring org.gnome.Connections.desktop.in using configuration
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Configuring org.gnome.Connections.service using configuration
> Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas)
> Library config found: YES
> Library m found: YES
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.70.0
> Run-time dependency gtk+-3.0 found: YES 3.24.30
> Run-time dependency gtk-vnc-2.0 found: YES 1.0.0
> Run-time dependency libhandy-1 found: YES 1.4.0
> Run-time dependency libxml-2.0 found: YES 2.9.12
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency gtk-frdp-0.1 found: NO (tried pkgconfig and cmake)
>
> Executing subproject gtk-frdp
>
> gtk-frdp| Project name: gtk-frdp
> gtk-frdp| Project version: 0.1.0
> gtk-frdp| C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian
> 11.2.0-10) 11.2.0")
> gtk-frdp| C linker for the host machine: cc ld.bfd 2.37
> gtk-frdp| Vala compiler for the host machine: valac (valac 0.54.2)
> gtk-frdp| Configuring gtk-frdp-config.h using configuration
> gtk-frdp| WARNING: Project targeting '>= 0.40.0' but tried to use feature
> introduced in '0.50.0': install arg in configure_file.
> gtk-frdp| Configuring gtk-frdp-version.h using configuration
> gtk-frdp| Run-time dependency winpr2 found: YES 2.3.0
> gtk-frdp| Run-time dependency freerdp2 found: YES 2.3.0
> gtk-frdp| Dependency gio-2.0 found: YES 2.70.0 (cached)
> gtk-frdp| Dependency gtk+-3.0 found: YES 3.24.30 (cached)
> gtk-frdp| Library m found: YES
> gtk-frdp| Run-time dependency gobject-introspection-1.0 found: YES 1.70.0
> gtk-frdp| Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> gtk-frdp| Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
> gtk-frdp| Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> gtk-frdp| Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
> gtk-frdp| Program vapigen found: YES (/usr/bin/vapigen)
> gtk-frdp| Build targets in project: 9
> gtk-frdp| WARNING: Project specifies a minimum meson_version '>= 0.40.0' but
> uses features which were added in newer versions:
> gtk-frdp| * 0.50.0: {'install arg in configure_file'}
> gtk-frdp| Subproject gtk-frdp finished.
>
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> Program build-aux/meson/postinstall.py found: YES
> (/<>/build-aux/meson/postinstall.py)
> Build targets in project: 56
>
> gnome-connections 41.1
>
> Subprojects
> gtk-frdp : YES 2 warnings
>
> User defined options
> buildtype: plain
> libdir : lib/x86_64-linux-gnu
> localstatedir: /var
> prefix : /usr
> sysconfdir : /etc
> wrap_mode: nodownload
>
> Found ninja-1.10.1 at /usr/bin/ninja
>dh_auto_build
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
> [1/76] /usr/bin/meson --i
Processed: Bug#998579 marked as pending in gnome-connections
Processing control commands: > tag -1 pending Bug #998579 [src:gnome-connections] gnome-connections: build-time tests access internet Added tag(s) pending. -- 998579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998579: marked as pending in gnome-connections
Control: tag -1 pending Hello, Bug #998579 in gnome-connections 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/gnome-team/gnome-connections/-/commit/51e1cc395bcfd84925ea6b6cff79414f154c71ea New upstream release Closes: #998579 (this message was generated automatically) -- Greetings https://bugs.debian.org/998579
Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'
Andreas, The background of this problem is the change in dependency between "raster" and "terra". "terra" was dependent on "raster"; now it is the other way around. This change was made in terra 1.4-07, 1.4-09 and 1.4-11 that were released between 2021-10-05 and 2021-10-11, and in raster 3.5-2 (2021-10-11). In the attachment I show the behavior of `library(satellite)` with the raster package prior to 2021-10-11, with the current versions, and for possible intermediate steps. It shows that you can get the warnings you see if you have current versions of terra/raster but an old version of satellite. >From what I can tell from this log: https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-satellite/16823806/log.gz you are using satellite_1.0.4 and raster_3.5-2 (current versions), and terra_1.4-11 (the current version is 1.4-22; but 1.4-11 should be OK). Is it possible that your session is actually loading satellite_1.0.2? Hope this helps, Robert On Tue, Nov 30, 2021 at 12:48 AM Andreas Tille wrote: > Control: forwarded -1 Robert J. Hijmans , Florian > Detsch > Control: tags -1 upstream > Control: tags -1 help > > Hi Robert and Florian, > > I'm contacting you as the maintainers or raster and satellite. As you > can see below in the Debian packaged versions of these packages some > conflict was raised in the test of satellite after the latest version of > raster was uploaded. > > I'm perfectly aware that the packages are tested on CRAN and thus I > assume that possibly some special circumstances in the Debian packaged > version might lead to the issue that is reported in the bug below. I > wonder whether you can give some hints how to solve the conflict in the > test (at the very end of this mail). > > Thanks a lot for your help > > Andreas. > > Am Sun, Nov 21, 2021 at 09:24:52PM +0100 schrieb Paul Gevers: > > Source: r-cran-raster, r-cran-satellite > > Control: found -1 r-cran-raster/3.5-2-1 > > Control: found -1 r-cran-satellite/1.0.4-1 > > Severity: serious > > Tags: sid bookworm > > X-Debbugs-CC: debian...@lists.debian.org > > User: debian...@lists.debian.org > > Usertags: breaks needs-update > > > > Dear maintainer(s), > > > > With a recent upload of r-cran-raster the autopkgtest of r-cran-satellite > > fails in testing when that autopkgtest is run with the binary packages of > > r-cran-raster from unstable. It passes when run with only packages from > > testing. In tabular form: > > > >passfail > > r-cran-raster from testing3.5-2-1 > > r-cran-satellite from testing1.0.4-1 > > all others from testingfrom testing > > > > I copied some of the output at the bottom of this report. > > > > Currently this regression is blocking the migration of r-cran-raster to > > testing [1]. Due to the nature of this issue, I filed this bug report > > against both packages. Can you please investigate the situation and > reassign > > the bug to the right package? > > > > More information about this bug and the reason for filing it can be > found on > > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > > > Paul > > > > [1] https://qa.debian.org/excuses.php?package=r-cran-raster > > > > > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-satellite/16823806/log.gz > > > > BEGIN TEST testthat.R > > > > R version 4.1.2 (2021-11-01) -- "Bird Hippie" > > Copyright (C) 2021 The R Foundation for Statistical Computing > > Platform: x86_64-pc-linux-gnu (64-bit) > > > > R is free software and comes with ABSOLUTELY NO WARRANTY. > > You are welcome to redistribute it under certain conditions. > > Type 'license()' or 'licence()' for distribution details. > > > > R is a collaborative project with many contributors. > > Type 'contributors()' for more information and > > 'citation()' on how to cite R or R packages in publications. > > > > Type 'demo()' for some demos, 'help()' for on-line help, or > > 'help.start()' for an HTML browser interface to help. > > Type 'q()' to quit R. > > > > > library(testthat) > > > library(satellite) > > Loading required package: raster > > Loading required package: sp > > code for methods in class "Rcpp_SpatCategories" was not checked for > > suspicious field assignments (recommended package 'codetools' not > > available?) > > code for methods in class "Rcpp_SpatCategories" was not checked for > > suspicious field assignments (recommended package 'codetools' not > > available?) > > code for methods in class "Rcpp_SpatDataFrame" was not checked for > > suspicious field assignments (recommended package 'codetools' not > > available?) > > code for methods in class "Rcpp_SpatDataFrame" was not checked for > > suspicious field assignments (recommended package 'codetools' not > > available?) > > code for methods in class "Rcpp_SpatExtent" was not checked for > suspicious > > field assignments (recommended package 'codetools' not available?) > > code for methods in class "Rcpp_Sp
Bug#1001016: Sadly 2.9.2 is also too old...
Hi, sadly I still get the messages with 2.9.2. I upgraded all my machines to this version to be sure I don't get warnings about an old client on one machine on another newer client. The message box appeared promptly on start of telegram-desktop and reappears every couple of minutes. This clearly signals urgentness :-(. Apparently something fresher is needed, like e.g. the aforementioned 3.1.1 . Thank you in advance! Ralf -- 72 61 6c 66 40 73 74 72 : 63 6d 70 2e 64 65 0a r...@strcmp.de.
Processed: Re: Bug#1000239: Rescue system won't find root partition, but insists on /usr
Processing control commands: > severity -1 normal Bug #1000239 [debian-installer] Rescue system won't find root partition, but insists on /usr Severity set to 'normal' from 'serious' -- 1000239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000239: Rescue system won't find root partition, but insists on /usr
Control: severity -1 normal On Fri, Dec 03, 2021 at 04:08:24PM -0500, Nicholas D Steeves wrote: > Steps I used to try to reproduce: > > 1. Downloaded debian-testing-amd64-netinst.iso2021-12-03 16:21 408M > 2. Installed to EFI-enabled qemu eg: >kvm -bios /usr/share/ovmf/bios.bin -m 2G \ >-hda debian-separate-usr-sda.raw \ >-cdrom debian-testing-amd64-netinst.iso > 3. Guided partitioning with separate /home, then changed the mount point >to /usr. Partition layout is: > sda1: ESP fat32 > sda2: /ext4 > sda3: swap swap > sda4: /usr ext4 /usr as separate partition is not provided as option. So, why do you select it? Sorry, but pointing the gun at your foot and firing is not the smartest idea. Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0
Bug#1000930: marked as done (faust: FTBFS with llvm-toolchain-13)
Your message dated Fri, 03 Dec 2021 21:48:53 + with message-id and subject line Bug#1000930: fixed in faust 2.37.3~ds0-1 has caused the Debian Bug report #1000930, regarding faust: FTBFS with llvm-toolchain-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: faust Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -13 (or -12). Bookworm won't ship with llvm-toolchain-11 llvm-defaults is now pointing to -13. Thanks, Sylvestre --- End Message --- --- Begin Message --- Source: faust Source-Version: 2.37.3~ds0-1 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of faust, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated faust package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 03 Dec 2021 11:38:24 +0100 Source: faust Architecture: source Version: 2.37.3~ds0-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1000930 Changes: faust (2.37.3~ds0-1) unstable; urgency=medium . * New upstream version 2.37.3~ds0 * (Closes: #1000930) * Refresh patches * Add patch to silence internal invocation of 'which' * Add patch to fix inkscape invocation * B-D on ruby:any (it needs to run on the build host) * Tighten lintian overrides * Updated d/copyright * Regenerated d/copyright_hints Checksums-Sha1: c97b0759ef251c550f1749d46247f0727add1a27 2358 faust_2.37.3~ds0-1.dsc c8177e75977480bcf42beb8e3251ea9ac58dcd09 41033596 faust_2.37.3~ds0.orig.tar.xz f2f129a1a61948c908d0c81de8a8f7bfce362ba2 92336 faust_2.37.3~ds0-1.debian.tar.xz Checksums-Sha256: 6131e49b0c60c3c2d08cf6abf3a817b4f0b7b701ad3de67719217a6d711a8fa2 2358 faust_2.37.3~ds0-1.dsc a700f5bbc5833cded926dbf89c25856abc20575ea69adc23bd16114daa604791 41033596 faust_2.37.3~ds0.orig.tar.xz 6e95d2152c67c233c7bef95e04ae8e1e685d44285613a2f9ecfba68c3387e74f 92336 faust_2.37.3~ds0-1.debian.tar.xz Files: 3e2eeb7ac881466f660ce472e74ed51e 2358 sound optional faust_2.37.3~ds0-1.dsc 7197776ce1e2becbc3f6f597004fa2c2 41033596 sound optional faust_2.37.3~ds0.orig.tar.xz 35493ba8a4ba1ab72d36dd0e582f2c07 92336 sound optional faust_2.37.3~ds0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmGqjIUWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+OzuD/oCHxQROoA5dsq/VVBtjRrWbItQ UPqcTkfRHgPhOMJM49HR/s6zdlCkYvIkAs6JOqSkaFuHXsWrc60asyYhDdG4/Tly wotoumMrAflc/6KRwFUSqelWumnRAW+ycHWw4B6TX26VKxARwxKcpHYH4LINNfrf cA6YDSAeDExEtpUpOZCaWsgoa7DyCoL0QBkMrNyWFyszi6hCoR+eZ4csXHtot9ea 4ZWrCM2SvwP92xtBUQPPjvDlT/svb40jVUiSmuGkh6ulmPvX1vq5ff6dHbTgbFm7 IweHPJUxCk3srUGSFTZFviLYshNvrxstiYtQ0c0CKI5s/MnupMO2IdgBOYHpoUn3 d5gQeM52L6YNstSmWGPrs5QslPE92QPbl9iXJrhCu3sh3KSGUOIf6T5PaD0+EdCw mqwGHqVHWbQf7B/osiNNDjh7KtPYNeICIal+Q5U1dxKzjzf5JaeU1QsvDuys6Hjm D/SL4ogFtXWGNrw4kMllDYKMR2o3H1G5qzXixyMOdz8wqo1tW9PsN1Dfo2wKQSdA bFc0SbEXfmNbqFzbTpU82zek5JO7fZ0TQI5gQLVvXYn+K1tb2RpQo2o6VTcbF/9w RxmyM6J3hddYxti9AUQamu5uAt9wwjfETKwM0CY/awmxn+AEJ02Wi4NbTObTMp+7 uHD9HZ08wHGMVa1Xxg== =E2/k -END PGP SIGNATURE End Message ---
Processed: tagging 1000239
Processing commands for cont...@bugs.debian.org: > tags 1000239 = confirmed Bug #1000239 [debian-installer] Rescue system won't find root partition, but insists on /usr Added tag(s) confirmed; removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 998485
Processing commands for cont...@bugs.debian.org: > tags 998485 + pending Bug #998485 [src:gjiten] gjiten: FTBFS: configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 998485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > unblock 998481 by 984082 Bug #998481 [src:ruby-puppet-syntax] ruby-puppet-syntax: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so 998481 was blocked by: 984082 984116 998481 was not blocking any bugs. Removed blocking bug(s) of 998481: 984116 and 984082 > reassign 998481 src:leatherman Bug #998481 [src:ruby-puppet-syntax] ruby-puppet-syntax: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so Bug reassigned from package 'src:ruby-puppet-syntax' to 'src:leatherman'. No longer marked as found in versions ruby-puppet-syntax/3.1.0-1. Ignoring request to alter fixed versions of bug #998481 to the same values previously set > forcemerge 984082 998481 Bug #984082 [src:leatherman] leatherman: ftbfs with GCC-11 Bug #984116 [src:leatherman] facter: ftbfs with GCC-11 Bug #998481 [src:leatherman] ruby-puppet-syntax: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so 998509 was blocked by: 984116 984082 998509 was not blocking any bugs. Added blocking bug(s) of 998509: 998481 998488 was blocked by: 984082 984116 998488 was not blocking any bugs. Added blocking bug(s) of 998488: 998481 998494 was blocked by: 984116 984082 998494 was not blocking any bugs. Added blocking bug(s) of 998494: 998481 998506 was blocked by: 984116 984082 998506 was not blocking any bugs. Added blocking bug(s) of 998506: 998481 Added indication that 998481 affects src:facter Marked as found in versions leatherman/1.12.1+dfsg-1.1. Bug #984116 [src:leatherman] facter: ftbfs with GCC-11 Merged 984082 984116 998481 > affects 984082 src:ruby-puppet-syntax Bug #984082 [src:leatherman] leatherman: ftbfs with GCC-11 Bug #984116 [src:leatherman] facter: ftbfs with GCC-11 Bug #998481 [src:leatherman] ruby-puppet-syntax: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so Added indication that 984082 affects src:ruby-puppet-syntax Added indication that 984116 affects src:ruby-puppet-syntax Added indication that 998481 affects src:ruby-puppet-syntax > thanks Stopping processing here. Please contact me if you need assistance. -- 984082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984082 984116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984116 998481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998481 998488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998488 998494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998494 998506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998506 998509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 998478
Processing commands for cont...@bugs.debian.org: > tags 998478 + pending Bug #998478 [src:httest] httest: FTBFS: configure.ac:13: error: AM_INIT_AUTOMAKE expanded multiple times Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 998478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998108: firefox freezes shortly after start
I just had one occasion of the "freezing" problem... but it was the first time since we got 94.0-2. Also it didn't occur short after start, but quite some time after browsing the very same websites. But the symptoms were as described in message #15 (i.e. that loading wheel). So there may be still some issue left (or it might be something new/unrelated). Cheers, Chris.
Processed (with 1 error): Re: Bug#1000239: Rescue system won't find root partition, but insists on /usr
Processing control commands: > severity -1 serious Bug #1000239 [debian-installer] Rescue system won't find root partition, but insists on /usr Severity set to 'serious' from 'normal' > tags = confirmed Unknown command or malformed arguments to command. -- 1000239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997375: marked as done (patroni: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')
Your message dated Fri, 03 Dec 2021 21:12:50 +0100
with message-id
and subject line Re: Bug#997375: patroni: FTBFS: AttributeError: 'Sphinx'
object has no attribute 'add_stylesheet'
has caused the Debian Bug report #997375,
regarding patroni: 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.)
--
997375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: patroni
Version: 2.1.1-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[2]: Entering directory '/<>/docs'
> Running Sphinx v4.2.0
> making output directory... done
>
> Exception occurred:
> File "/<>/docs/conf.py", line 207, in setup
> app.add_stylesheet("custom.css")
> AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
> The full traceback has been saved in /tmp/sphinx-err-_4z08vb0.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> . Thanks!
> make[2]: *** [Makefile:20: html] Error 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/patroni_2.1.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,
Am Samstag, dem 23.10.2021 um 21:50 +0200 schrieb Lucas Nussbaum:
> Source: patroni
> Version: 2.1.1-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[2]: Entering directory '/<>/docs'
> > Running Sphinx v4.2.0
> > making output directory... done
> >
> > Exception occurred:
> > File "/<>/docs/conf.py", line 207, in setup
> > app.add_stylesheet("custom.css")
> > AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
> > The full traceback has been saved in /tmp/sphinx-err-_4z08vb0.log,
> > if you want to report the issue to the developers.
> > Please also report this if it was a user error, so that a better
> > error message can be provided next time.
> > A bug report can be filed in the tracker at
> > . Thanks!
> > make[2]: *** [Makefile:20: html] Error 2
This got fixed with the latest 2.1.2-1 upload, but I didn't realize
this was the case, so I missed to add the bug closing tag.
Michael
--
Michael Banck
Teamleiter PostgreSQL-Team
Projektleiter
Tel.: +49 2166 9901-171
E-Mail: michael.ba...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Geoff Richardson, Peter Lilley
Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz--- End Message ---
Processed: found 997683 in 0.0.6-3, tagging 997683, tagging 1001020, affects 997884
Processing commands for cont...@bugs.debian.org:
> found 997683 0.0.6-3
Bug #997683 {Done: kpcyrd } [src:rust-dfrs] rust-dfrs: FTBFS
because of a recent upload
Marked as found in versions rust-dfrs/0.0.6-3.
> tags 997683 + sid bookworm
Bug #997683 {Done: kpcyrd } [src:rust-dfrs] rust-dfrs: FTBFS
because of a recent upload
Added tag(s) bookworm and sid.
> tags 1001020 + sid bookworm
Bug #1001020 [src:python-anndata] python-anndata: FTBFS with sklearn 1.0.1-1:
ModuleNotFoundError: No module named 'sklearn.utils.testing'
Added tag(s) sid and bookworm.
> affects 997884 - 1 0.12.1-4
Bug #997884 {Done: Étienne Mollier } [src:libgclib]
libgclib breaks cdbfasta autopkgtest: ABI breakage?
Removed indication that 997884 affects 0.12.1-4
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001020
997683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997683
997884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1001075: openscap-common: missing Breaks+Replaces: libopenscap8 (<< 1.3.5)
Package: openscap-common Version: 1.3.5-0.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../openscap-common_1.3.5-0.1_all.deb ... Unpacking openscap-common (1.3.5-0.1) ... dpkg: error processing archive /var/cache/apt/archives/openscap-common_1.3.5-0.1_all.deb (--unpack): trying to overwrite '/usr/share/openscap/cpe/README', which is also in package libopenscap8 1.3.4-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/openscap-common_1.3.5-0.1_all.deb cheers, Andreas libopenscap8=1.3.4-1_openscap-common=1.3.5-0.1.log.gz Description: application/gzip
Processed: severity of 1000727 is serious
Processing commands for cont...@bugs.debian.org: > severity 1000727 serious Bug #1000727 [python3-joypy] joypy: FTBFS with pandas 1.3: ImportError: cannot import name '_subplots' from 'pandas.plotting._matplotlib.tools' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 996237 with 996451
Processing commands for cont...@bugs.debian.org:
> block 996237 with 996451
Bug #996237 {Done: Lucas Kanashiro } [src:ruby-gsl]
ruby-gsl: FTBFS with ruby3.0: include/rb_gsl_common.h:29:1: error: unknown type
name ‘EXTERN’
996237 was not blocked by any bugs.
996237 was not blocking any bugs.
Added blocking bug(s) of 996237: 996451
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable
Hi, ok, your mail arrived while I wrote my last one and I only saw it after sending. I am upgrading to 2.9.2+ds-1~bpo11+1 now -- one machine is done, the others will follow (the messages in the 'Telegram' channel confusingly also appear in the up-to-date iOS app so I will have to update all clients). I think I will see tomorrow or in the next couple of days if I still get these messages. Or faster -- the message box appeared again, maybe it is set every couple of minutes? Wasn't there a similar problem with firefox where a solution was worked out to follow upstream more closely? Thank you so far! Ralf On Fri, Dec 03, 2021 at 08:11:10PM +0300, Nicholas Guriev wrote: > Hello! > > Could you test version 2.9.2 from backports? Does the message appear > there? > For a backports guide see: https://backports.debian.org/Instructions/ > > If even this version is considered ancient, I could backport 3.1.1 from > testing. I am sure it still is working. > > From what I know, versions older that 3.1.1 are unable to operate for > newly registered users whose UIDs do not fit signed 32bit. However, the > older versions continue to work for already existing users. > > As a maintainer I can only offer you to switch to backports repository. > Release managers do not happy with huge updates after Debian freeze. > Telegram team in their turn is primarily focused on implementing new > features. The goals seem contradictory, and users stuck between a rock > and a hard place. > -- 72 61 6c 66 40 73 74 72 : 63 6d 70 2e 64 65 0a r...@strcmp.de.
Bug#1001016: More messages -- seems to be urgent
Hi, I got the message "Please update your app to the latest version. The version you are using is out of date and will stop working soon." again. Twice. First in the 'Telegram' channel, than in a message box. Obviously it is very urgent and the package will stop working completely for all users in a couple of days. I ask again if this is fully thought through. The Telegram people know the version in Debian 11.1 is 2.6.1 and 11.1 is relatively fresh -- this is public knowledge, after all. Don't they care about their users? How can they kick out users of stable distros and not at least offer a workaround? Why do they say 'please upgrade' (in an annoying way) if they know I have no upgrading options? For me the desktop version is why I use Telegram and not Signal or Threema. Asked from the other perspective, what are the Debian plans to follow Telegram's forced client upgrades? Ralf -- 72 61 6c 66 40 73 74 72 : 63 6d 70 2e 64 65 0a r...@strcmp.de.
Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable
Hello! Could you test version 2.9.2 from backports? Does the message appear there? For a backports guide see: https://backports.debian.org/Instructions/ If even this version is considered ancient, I could backport 3.1.1 from testing. I am sure it still is working. From what I know, versions older that 3.1.1 are unable to operate for newly registered users whose UIDs do not fit signed 32bit. However, the older versions continue to work for already existing users. As a maintainer I can only offer you to switch to backports repository. Release managers do not happy with huge updates after Debian freeze. Telegram team in their turn is primarily focused on implementing new features. The goals seem contradictory, and users stuck between a rock and a hard place. signature.asc Description: This is a digitally signed message part
Bug#1000423: marked as done (python-biom-format: FTBFS with Python 3.10 - Test failures)
Your message dated Fri, 03 Dec 2021 16:49:05 + with message-id and subject line Bug#1000423: fixed in python-biom-format 2.1.10-3 has caused the Debian Bug report #1000423, regarding python-biom-format: FTBFS with Python 3.10 - Test failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-biom-format Version: 2.1.10-2 Severity: serious Tags: upstream Justification: FTBFS Block -1 with 1000422 python-biom-format FTBFS with Python 3.10: === short test summary info ERROR biom/tests/test_err.py ERROR biom/tests/test_parse.py ERROR biom/tests/test_table.py ERROR biom/tests/test_util.py ERROR biom/tests/test_cli/test_add_metadata.py ERROR biom/tests/test_cli/test_show_install_info.py ERROR biom/tests/test_cli/test_subset_table.py ERROR biom/tests/test_cli/test_summarize_table.py ERROR biom/tests/test_cli/test_table_converter.py ERROR biom/tests/test_cli/test_table_normalizer.py ERROR biom/tests/test_cli/test_uc_processor.py ERROR biom/tests/test_cli/test_validate_table.py !!! Interrupted: 12 errors during collection !!! == 12 errors in 2.27s == E: pybuild pybuild:354: test: plugin distutils failed with: exit code=2: cd /<>/.pybuild/cpython3_3.10_biom-format/build; python3.10 -m pytest See: https://buildd.debian.org/status/fetch.php?pkg=python-biom-format&arch=amd64&ver=2.1.10-2%2Bb1&stamp=1637570066&raw=0 I adapted an upstream patch, in https://salsa.debian.org/med-team/python-biom-format/-/merge_requests/1 But it still doesn't build because we need pandas, first. SR --- End Message --- --- Begin Message --- Source: python-biom-format Source-Version: 2.1.10-3 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of python-biom-format, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated python-biom-format package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Dec 2021 16:21:56 + Source: python-biom-format Built-For-Profiles: noudeb Architecture: source Version: 2.1.10-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Graham Inggs Closes: 1000423 Changes: python-biom-format (2.1.10-3) unstable; urgency=medium . * Team upload . [ Stefano Rivera ] * Patch: Python 3.10 support. (Closes: #1000423) . [ Andreas Tille ] * Ignore one failing test Checksums-Sha1: e8cec89f3a74dde63c85695c006e0421fdbc75a9 2571 python-biom-format_2.1.10-3.dsc f50c7de754819016d6ec7c68f1d0d8d6338e4bb1 26908 python-biom-format_2.1.10-3.debian.tar.xz Checksums-Sha256: c9a80ee3f71353df8e37bec944efe55058d72ec2260ac2d017122fcfa2aec1f0 2571 python-biom-format_2.1.10-3.dsc 34216c2ff91781e279459b5da72b1023bf91beeede70154ff58792442a725e1b 26908 python-biom-format_2.1.10-3.debian.tar.xz Files: be74fd8f4d1f7fa8495bb78eec7c7bc9 2571 python optional python-biom-format_2.1.10-3.dsc 84f92418919e5fc90412c0401975f9ad 26908 python optional python-biom-format_2.1.10-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmGqRkYACgkQr8/sjmac 4cLWOA/+Ka6Evr/NrPgnVXtShWV0QgK8vuDZIr0RZO94+S74F4eQK+asjP/itZ0E ESS2S4zvBcRZbP/JOSACFmp/v+jFO079K4132dP3kzsLNZL4IDzcssLITDxXx2fL c7B0PCMilb9HERyqh7FKTvsydrNXmeQsTybkdpV3jqDheMQ6XlNQcEi+76mdv7lv MjehxOX56sbVJkvCBns5s+1CYPjP7NIDp2UX4g9oJrPlGNNE3wiEq9r9mTXeGxOb pr7bzt1f+2RQh7HTGh6mSCnrNuOZ7KqukW9pMii44nIo/tu9etRgy2RHAOdwXgZu WFP5YjCq+0FuillDcXhmjH4uLh9DA2gugcrf9EbJhJ9vozgxfcyDoZBlqiifirlO aOVnAu3yG7eCAx8I1xl6WaekPtBZDBxaLa3cMbweqW8VEFxaWPIH8dpZa45shOQy 9CKJx/f7/sHlgVrT0faAORW4vkn3mWypMaqah85a4XWocdmUISTq3N7OcYxpfyeU wLWIb6IefDtP/dKzl42fuUcR0Q5Fa2kvB09fioTEOOqqLGIcFLPo/nPgLIfh6IqE 3fu8UZp91G3B2FQDDqsdtxx7WFEh5+jUIsOtyGUWMq0nza6M5IhYvB1L+k4geSQh 8u1ujDFRzLoD/yy5Mgv1xsmzPI6Wy1qmI7XGRJTf6xNTgREl0Tk= =tslJ
Bug#999533: matplotlib: python3-pil.imagetk should be Depends
control: severity -1 normal > > This is not a bug in cartopy, matplotlib tries to use ImageTk but the > > package is not installed. > > > > python3-matplotlib only Recommends python3-pil.imagetk, this should be a > > Depends. > > This issue is still present in matplotlib (3.5.0-2) and affects several > packages. These should not have to add python3-pil.imagetk to their > build dependencies because matplotlib does not pull it in. this is done on purpose, so that people can switch backend and remove the underlying package without causing apt to want to remove also python3-matplotlib. All the backend packages are in Recommends for a reason. If you need a different backend during build, please set the backend rcparams accordingly during your package build.
Processed: Re: matplotlib: python3-pil.imagetk should be Depends
Processing control commands: > severity -1 normal Bug #999533 [src:matplotlib] matplotlib: python3-pil.imagetk should be Depends Severity set to 'normal' from 'serious' -- 999533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001070: command-not-found: crashes when entering an unknown command
Package: command-not-found Version: 20.10.1-1 Severity: grave Justification: renders package unusable See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917455 Bug #917455 was closed with: Marked as fixed in versions 20.10.1-1 This is *NOT* the case! After upgrading to bullseye, which includes command-not-found 20.10.1-1, the bug is there again! % foo Sorry, command-not-found has crashed! Please file a bug report at: http://www.debian.org/Bugs/Reporting Please include the following information with the report: command-not-found version: 0.3 Python version: 3.9.2 final 0 Distributor ID: Debian Description:Debian GNU/Linux 11 (bullseye) Release:11 Codename: bullseye Exception information: unable to open database file Traceback (most recent call last): File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in crash_guard callback() File "/usr/lib/command-not-found", line 90, in main cnf = CommandNotFound.CommandNotFound(options.data_dir) File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 79, in __init__ self.db = SqliteDatabase(dbpath) File "/usr/share/command-not-found/CommandNotFound/db/db.py", line 12, in __init__ self.con = sqlite3.connect(filename) sqlite3.OperationalError: unable to open database file The temporary fix still works: sudo chmod 644 /var/lib/command-not-found/commands.db But after the next update, the permissions are set wrong again. The actual fix is (and probably always has been) to set in /sbin/update-command-not-found: os.umask (0o022) I see no trace of this having been done. In fact, there's no occurrence of "umask" anywhere in the sources (including Debian patches) -- except for debian/changelog!??? (And a much older changelog entry anyway.) So it doesn't seem this bug was actually ever fixed.
Bug#999523: marked as done (python-skbio: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Fri, 03 Dec 2021 16:03:49 +
with message-id
and subject line Bug#999523: fixed in python-skbio 0.5.6-6
has caused the Debian Bug report #999523,
regarding python-skbio: FTBFS with numpy 1.21 (in experimental): dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit
code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
999523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-skbio
Version: 0.5.6-5
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-numpy121
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64, using numpy 1.21 currently in experimental. This version
will soon be uploaded to unstable.
If you have questions about this, please contact Sandro Tosi
.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> echo No testing for the -doc package
> No testing for the -doc package
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild -Npython-skbio-doc
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_skbio/build;
> python3.9 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>
> collected 2348 items
>
> skbio/alignment/tests/test_pairwise.py . [
> 1%]
> skbio/alignment/tests/test_ssw.py ...[
> 2%]
> skbio/alignment/tests/test_tabular_msa.py .. [
> 3%]
> [
> 6%]
> [
> 9%]
> [
> 12%]
> [
> 15%]
> [
> 18%]
> [
> 19%]
> skbio/diversity/alpha/tests/test_ace.py .. [
> 19%]
> skbio/diversity/alpha/tests/test_base.py [
> 20%]
> skbio/diversity/alpha/tests/test_chao1.py ...[
> 20%]
> skbio/diversity/alpha/tests/test_faith_pd.py [
> 20%]
> skbio/diversity/alpha/tests/test_gini.py ... [
> 21%]
> skbio/diversity/alpha/tests/test_lladser.py [
> 21%]
> skbio/diversity/beta/tests/test_unifrac.py [
> 22%]
> skbio/diversity/tests/test_block.py ... [
> 23%]
> skbio/diversity/tests/test_driver.py .. [
> 24%]
> skbio/diversity/tests/test_util.py ..[
> 25%]
> skbio/io/format/tests/test_base.py [
> 26%]
> skbio/io/format/tests/test_blast6.py ... [
> 26%]
> skbio/io/format/tests/test_blast7.py .. [
> 27%]
> skbio/io/format/tests/test_clustal.py . [
> 28%]
> skbio/io/format/tests/test_embl.py ... [
> 29%]
> skbio/io/format/tests/test_emptyfile.py .. [
> 29%]
> skbio/io/format/tests/test_fasta.py [
> 30%]
> skbio/io/format/tests/test_fastq.py ... [
> 30%]
> skbio/io/format/tests/test_genbank.py . [
> 31%]
> skbio/io/format/tests/test_gff3.py [
> 32%]
> skbio/io/format/tests/test_lsmat.py ... [
> 33%]
> skbio/io/format/tests/test_newick.py ... [
> 33%]
> skbio/io/format/tests/test_ordination.py . [
> 33%]
> skbio/io/format/tests/test_phylip.py ... [
> 33%]
> skbio/io/format/tests/test_qseq.py ..[
> 34%]
> skbio/io/format/tests/test_sequence_feature_vocabulary.py [
> 34%]
> skbio/io/format/tests/test_stockholm.py [
> 35%]
> ... [
> 37%]
> skbio/io/tes
Bug#992676: marked as done (scipy breaks python-skbio autopkgtest: Unsupported dtype object)
Your message dated Fri, 03 Dec 2021 16:03:49 +
with message-id
and subject line Bug#992676: fixed in python-skbio 0.5.6-6
has caused the Debian Bug report #992676,
regarding scipy breaks python-skbio autopkgtest: Unsupported dtype object
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.)
--
992676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scipy, python-skbio
Control: found -1 scipy/1.7.1-1
Control: found -1 python-skbio/0.5.6-4
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of scipy the autopkgtest of python-skbio fails in
testing when that autopkgtest is run with the binary packages of scipy
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
scipy from testing1.7.1-1
python-skbio from testing0.5.6-4
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of scipy to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=scipy
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-skbio/14750991/log.gz
=== FAILURES
===
testPERMDISP.test_centroids_eq_groups
_
self =
def test_centroids_eq_groups(self):
exp = [[1.2886811963240687, 1.890538910062923, 1.490527658097728],
[2.17349240061718, 2.3192679626679946, 2.028338553903792]]
exp_stat, _ = f_oneway(*exp)
dm = pcoa(self.eq_mat)
dm = dm.samples
> obs = _compute_groups(dm, 'centroid', self.grouping_eq)
skbio/stats/distance/tests/test_permdisp.py:121:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
skbio/stats/distance/_permdisp.py:251: in _compute_groups
groups.append(cdist(df.values[:, :-1], [centroids.loc[label].values],
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
XA = array([[-1.7249342172942905, 0.4245950661770306, -0.4421150498378117,
-0.8800986337268075, 0.0, 0.0],
[... [-1.813911896152713, 0.25012463135432966, 0.42415638246654996,
0.9643046100830307, 0.0, 0.0]], dtype=object)
XB = array([[-1.19938106, -0.22670737, -0.50629061, 0.0977458 , 0.
,
0.]])
metric = 'euclidean', out = None, kwargs = {}, s = (3, 6), sB = (1, 6),
mA = 3
mB = 1, n = 6, mstr = 'euclidean'
def cdist(XA, XB, metric='euclidean', *, out=None, **kwargs):
"""
Compute distance between each pair of the two collections of inputs.
See Notes for common calling conventions.
Parameters
--
XA : array_like
An :math:`m_A` by :math:`n` array of :math:`m_A`
original observations in an :math:`n`-dimensional space.
Inputs are converted to float type.
XB : array_like
An :math:`m_B` by :math:`n` array of :math:`m_B`
original observations in an :math:`n`-dimensional space.
Inputs are converted to float type.
metric : str or callable, optional
The distance metric to use. If a string, the distance
function can be
'braycurtis', 'canberra', 'chebyshev', 'cityblock',
'correlation',
'cosine', 'dice', 'euclidean', 'hamming', 'jaccard',
'jensenshannon',
'kulsinski', 'mahalanobis', 'matching', 'minkowski',
'rogerstanimoto',
'russellrao', 'seuclidean', 'sokalmichener', 'sokalsneath',
'sqeuclidean', 'wminkowski', 'yule'.
**kwargs : dict, optional
Extra arguments to `metric`: refer to each metric
documentation for a
list of all possible arguments.
Some possible arguments:
p : scalar
The p-norm to apply for Minkowski, weighted and unweighted.
Default: 2.
w : array_like
The weight vector for metrics that support weights (e.g.,
Minkowski).
Bug#1000864: marked as done (python-skbio: FTBFS with Python 3.10)
Your message dated Fri, 03 Dec 2021 16:03:49 + with message-id and subject line Bug#1000864: fixed in python-skbio 0.5.6-6 has caused the Debian Bug report #1000864, regarding python-skbio: FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-skbio Version: 0.5.6-5 Severity: serious Tags: ftbfs patch User: debian-pyt...@lists.debian.org Usertags: python3.10 Hi Maintainer Now that scikit-learn has at least built on amd64 [1], we can now see a new failure in python-skbio [2]. I have copied part of the log below. This is due to .c files in the upstream tarball being generated by an old version of cython. The solution is to add cython3 as a build-dependency and regenerate the .c files at build time. I've attached a patch that does this. Regards Graham [1] https://buildd.debian.org/status/package.php?p=scikit-learn [2] https://buildd.debian.org/status/package.php?p=python-skbio&suite=sid skbio/alignment/_ssw_wrapper.c: In function ‘__pyx_tp_dealloc_5skbio_9alignment_12_ssw_wrapper_AlignmentStructure’: skbio/alignment/_ssw_wrapper.c:10363:5: error: lvalue required as increment operand 10363 | ++Py_REFCNT(o); | ^~ skbio/alignment/_ssw_wrapper.c:10365:5: error: lvalue required as decrement operand 10365 | --Py_REFCNT(o); | ^~ skbio/alignment/_ssw_wrapper.c: In function ‘__pyx_tp_dealloc_5skbio_9alignment_12_ssw_wrapper_StripedSmithWaterman’: skbio/alignment/_ssw_wrapper.c:10570:5: error: lvalue required as increment operand 10570 | ++Py_REFCNT(o); | ^~ skbio/alignment/_ssw_wrapper.c:10572:5: error: lvalue required as decrement operand 10572 | --Py_REFCNT(o); | ^~ skbio/alignment/_ssw_wrapper.c: In function ‘__Pyx_ParseOptionalKeywords’: skbio/alignment/_ssw_wrapper.c:12453:21: warning: ‘_PyUnicode_get_wstr_length’ is deprecated [-Wdeprecated-declarations] 12453 | (PyUnicode_GET_SIZE(**name) != PyUnicode_GET_SIZE(key)) ? 1 : | ^ cythonize.debdiff Description: Binary data --- End Message --- --- Begin Message --- Source: python-skbio Source-Version: 0.5.6-6 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of python-skbio, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated python-skbio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Dec 2021 15:24:18 + Source: python-skbio Built-For-Profiles: noudeb Architecture: source Version: 0.5.6-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Graham Inggs Closes: 992676 999523 1000864 Changes: python-skbio (0.5.6-6) unstable; urgency=medium . * Team upload . [ Andreas Tille ] * Remove Tim Booth from Uploaders (Thanks to Tim for all his work) . [ Graham Inggs ] * Regenerate the .c files at build time by cython3 Closes: #1000864 * Cherry-pick upstream commit to fix dtypes and warnings Closes: #992676, #999523 * Drop skip_tests_failung_due_to_scipy.patch, no longer needed Checksums-Sha1: ea9e3878dc91008ed433d4dd08079299a8f01148 2791 python-skbio_0.5.6-6.dsc 3a9b8252acc525d4edd890745d4948e66b2c516a 17264 python-skbio_0.5.6-6.debian.tar.xz Checksums-Sha256: 5126f17930952bb22f1b670fee47ccbae72043f9015634d09804e2f4cf99734b 2791 python-skbio_0.5.6-6.dsc f929e306ae57b4c225e5ebf59e33560fd541945990d92384ce19794ca630bad3 17264 python-skbio_0.5.6-6.debian.tar.xz Files: 0d56ac95d6d992f02d8337160b535be1 2791 python optional python-skbio_0.5.6-6.dsc cb4873534abc61011837d27a50ce920a 17264 python optional python-skbio_0.5.6-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmGqOMIACgkQr8/sjmac 4cJoDxAAnD3jAgCgcwFEfxEB7Har0Wm24rwb+6xauZ3SvFw+4AL1XcdmhR9JcMt3 2EnEwL+ybAry/3QYDGLX0LSSfiInVHok6T92uipZqPhZrSwaROPBVZsphSlLk688 KRmFzzvuWrLlM9/A3R90iroHzE+k3w
Bug#1000953: c-blosc: FTBFS on mips64el
ons. 1. des. 2021 kl. 11:39 skrev Bastian Germann : > > Source: c-blosc > Severity: serious > Version: 1.21.1+ds2-1 > > The build fails on mips64el with: > > 98% tests passed, 35 tests failed out of 1651 > > Total Test time (real) = 452.24 sec > > The following tests FAILED: > 1 - test_api (Failed) > 2 - test_bitshuffle_leftovers (Failed) > 270 - test_compressor (Failed) > 672 - test_noinit (Failed) > 673 - test_nolock (Failed) > 674 - test_nthreads (Failed) > 1606 - test_compat_blosc-1.11.1-blosclz.cdata (Failed) > 1607 - test_compat_blosc-1.11.1-lz4.cdata (Failed) > 1608 - test_compat_blosc-1.11.1-lz4hc.cdata (Failed) > 1609 - test_compat_blosc-1.11.1-snappy.cdata (Failed) > 1610 - test_compat_blosc-1.11.1-zlib.cdata (Failed) > 1611 - test_compat_blosc-1.11.1-zstd.cdata (Failed) > 1612 - test_compat_blosc-1.14.0-blosclz.cdata (Failed) > 1613 - test_compat_blosc-1.14.0-lz4.cdata (Failed) > 1614 - test_compat_blosc-1.14.0-lz4hc.cdata (Failed) > 1615 - test_compat_blosc-1.14.0-snappy.cdata (Failed) > 1616 - test_compat_blosc-1.14.0-zlib.cdata (Failed) > 1617 - test_compat_blosc-1.14.0-zstd.cdata (Failed) > 1618 - test_compat_blosc-1.18.0-blosclz-bitshuffle.cdata (Failed) > 1619 - test_compat_blosc-1.18.0-blosclz.cdata (Failed) > 1620 - test_compat_blosc-1.18.0-lz4-bitshuffle.cdata (Failed) > 1621 - test_compat_blosc-1.18.0-lz4.cdata (Failed) > 1622 - test_compat_blosc-1.18.0-lz4hc.cdata (Failed) > 1623 - test_compat_blosc-1.18.0-zlib.cdata (Failed) > 1624 - test_compat_blosc-1.18.0-zstd.cdata (Failed) > 1625 - test_compat_blosc-1.3.0-blosclz.cdata (Failed) > 1626 - test_compat_blosc-1.3.0-lz4.cdata (Failed) > 1627 - test_compat_blosc-1.3.0-lz4hc.cdata (Failed) > 1628 - test_compat_blosc-1.3.0-snappy.cdata (Failed) > 1629 - test_compat_blosc-1.3.0-zlib.cdata (Failed) > 1630 - test_compat_blosc-1.7.0-blosclz.cdata (Failed) > 1631 - test_compat_blosc-1.7.0-lz4.cdata (Failed) > 1632 - test_compat_blosc-1.7.0-lz4hc.cdata (Failed) > 1633 - test_compat_blosc-1.7.0-snappy.cdata (Failed) > 1634 - test_compat_blosc-1.7.0-zlib.cdata (Failed) > Errors while running CTest > make[1]: *** [Makefile:94: test] Error 8 > make[1]: Leaving directory '/<>/obj-mips64el-linux-gnuabi64' > dh_auto_test: error: cd obj-mips64el-linux-gnuabi64 && make -j4 test > ARGS\+=--verbose ARGS\+=-j4 returned exit code 2 > I believe it's related to cmake and the recently updated package. The previous version of c-blosc (1.21.1+ds1-1) uploaded 2021-10-08 used cmake with version 3.21.3-4, it built successfully. Building c-blosc with the current version of cmake fails, as does the earlier versions of c-blosc, I tested 1.17.1+ds1-1, 1.20.1+ds1-2 and 1.21.1+ds1-1. What's strange is that it's only on mips64el the testsuite fails, none of the other architectures seems to be affected. I have yet to discover where the fault lies, if it's cmake itself or the CMakeLists.txt in c-blosc. The solution to make the testsuite succeed is to override the cmake flag provided by debhelper '-DCMAKE_BUILD_TYPE=None' Changing this to 'Release' is enough to make the testsuite succeed. Regards, Håvard
Processed: sorting libstatgen & minimac4 bugs (and maybe unconfuse #996409)
Processing commands for cont...@bugs.debian.org:
> # minimac4 currently affected by #1000475 instead
> reopen 996409
Bug #996409 {Done: Andreas Tille } [src:libstatgen,
src:minimac4] libstatgen breaks minimac4 autopkgtest: Segmentation fault
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions minimac4/1.0.2-3.
> reassign 996409 src:libstatgen 1.0.15-1
Bug #996409 [src:libstatgen, src:minimac4] libstatgen breaks minimac4
autopkgtest: Segmentation fault
Bug reassigned from package 'src:libstatgen, src:minimac4' to 'src:libstatgen'.
No longer marked as found in versions libstatgen/1.0.15-1 and minimac4/1.0.2-2.
Ignoring request to alter fixed versions of bug #996409 to the same values
previously set
Bug #996409 [src:libstatgen] libstatgen breaks minimac4 autopkgtest:
Segmentation fault
Marked as found in versions libstatgen/1.0.15-1.
> # libstatgen pending in new with introduction of libstatgen1
> tags 996409 + pending
Bug #996409 [src:libstatgen] libstatgen breaks minimac4 autopkgtest:
Segmentation fault
Added tag(s) pending.
> # minimac4 pending upload of libstatgen; rebuild against
> # libstatgen1 should fix the bug.
> tags 1000475 + pending
Bug #1000475 [src:minimac4] minimac4: autopkgtest regression: *** stack
smashing detected ***: terminated
Added tag(s) pending.
> thank you
Stopping processing here.
Please contact me if you need assistance.
--
1000475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000475
996409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1001067: synaptic: Crushing when searching. Error: Segmentation Fault
Package: synaptic Version: 0.90.2 Severity: grave Tags: a11y Justification: renders package unusable X-Debbugs-Cc: merambo...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? It happened after the installation of the makedeb package * What exactly did you do (or not do) that was effective (or ineffective)? After discovering the problem i uninstalled makedeb with apt and all its dependencies but nothing changed * What was the outcome of this action? nothing * What outcome did you expect instead? to make it work again *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 synaptic depends on: ii hicolor-icon-theme 0.17-2 ii libapt-pkg6.0 2.2.4 ii libc6 2.31-13+deb11u2 ii libept1.6.0 1.2.1 ii libgcc-s1 10.2.1-6 ii libgdk-pixbuf2.0-0 2.40.2-2 ii libglib2.0-02.66.8-1 ii libgtk-3-0 3.24.24-4 ii libpango-1.0-0 1.46.2-3 ii libstdc++6 10.2.1-6 ii libvte-2.91-0 0.62.3-1 ii libxapian30 1.4.18-3 ii policykit-1 0.105-31 Versions of packages synaptic recommends: ii libgtk3-perl 0.038-1 ii xdg-utils 1.1.3-4.1 Versions of packages synaptic suggests: ii apt-xapian-index 0.52 ii deborphan1.7.33 ii dwww 1.14 ii menu 2.1.48 ii software-properties-gtk 0.96.20.2-2.1 ii tasksel 3.68 -- no debconf information
Bug#1001046: todoman: crashes on startup
]] Tollef Fog Heen > I have no idea what's wrong here, except «it used to work» (as in, > yesterday, but that update included, amongst many others, an update from > python3-click 7.1.2-1 to 8.0.2-1, so based on the backtrace, maybe > relevant?) fwiw, duwngrading to 7.1.2-1 makes todoman not break again, so looks like both a bug in todoman for not supporting python3-click, and a missing Breaks (or API bump) in python3-click. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Processed: Re: Bug#1000577: abyss: autopkgtest regression on armhf and i386: Floating point exception
Processing control commands: > tags -1 upstream Bug #1000577 [src:abyss] abyss: autopkgtest regression on armhf and i386: Floating point exception Added tag(s) upstream. > forwarded -1 https://github.com/bcgsc/abyss/issues/384 Bug #1000577 [src:abyss] abyss: autopkgtest regression on armhf and i386: Floating point exception Set Bug forwarded-to-address to 'https://github.com/bcgsc/abyss/issues/384'. -- 1000577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000577: abyss: autopkgtest regression on armhf and i386: Floating point exception
Control: tags -1 upstream Control: forwarded -1 https://github.com/bcgsc/abyss/issues/384
Bug#999626: [Maxima-discuss] maxima-emacs: fails to install with xemacs21
El mié, 1 dic 2021 a las 16:53, Camm Maguire () escribió: > > Greetings! Am uploading a fix for now. cl-lib for xemacs21 can be > found in the mmm-mode package. Other change is that image-map needs to > be nil if not bound. Quite a few byte-compilation warnings in both > flavors, suppressed on install, but maintainers might want to look at > cleaning these up. HI, Camm, Thanks for taking care of this. Note that for this to work well maxima-emacs must explicitly depend on mmm-mode package. Dependency on emacs | mmm-mode will make xemacs compilation fail (no cl-lib found) if Emacs and XEmacs are installed, but not mmm-mode (possible with current dependencies). Regards, -- Agustin
Bug#1001057: grub2: hold 2.06 in unstable for now
Package: grub2 Version: 2.06-2 Severity: serious Justification: maintainer says so GRUB 2.06 is a pretty big change over 2.04. I'd like to hold this in unstable for a while longer to let things shake out before we allow it to move to testing. -- Colin Watson (he/him) [cjwat...@debian.org]
Bug#993350: [sane-devel] Epson Perfection1640 and the epson2 backend: summary
Hi, > 1) This started out with focus problems. >I appear to have confirmed that the 1640 accepts, but ignores, focus >commands, so the current version of the backend >(commit 3b47d1d26a73054b7138759fa7af57ed6c8e8e35 (HEAD -> master, > origin/master, origin/HEAD) >with dev->focusSupport = SANE_FALSE is correct. Thanks for confirming! > 2) The > --film-type Positive Film|Negative Film|Positive Slide|Negative Slide >includes the Slide options which I suspect are not available on >the 1640SU. They result in something like invalid parameter messages. Confirmed. I can reproduce this with my 1640SU. I don't really know where the "Slide" come from or what they actually do. I need to dig in a little further. In about two weeks, I can also double check if a 12000XL does support the "Slide" options. > 3) There is a failure to transfer larger scans: perhaps a counter >overflowing. So a significant bug. I still need to reproduce this one. But I'd think this is easy to reproduce. > 4) Using xsane, and [cancel]ing during a scan fails. It is usually >necessary to restart the 1640. I have only mentioned this bug in >passing in previous messages. I had this, too, on my 1640SU. I seem to recall that it worked fine on the 12000XL. I'll cross-check this as well. > I hope this is helpful in following the earlier messages, especially > the first few when things were not so clear. Thanks again for your investigations! Much appreciated! Kind regards, Wolfram signature.asc Description: PGP signature
Processed: FTBFS on i386
Processing control commands: > fixed -1 firefox-esr/91.3.0esr-2 Bug #994799 [firefox-esr] FTBFS on i386 Marked as fixed in versions firefox-esr/91.3.0esr-2; no longer marked as fixed in versions firefox-esr/91.3.0esr-2. -- 994799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939763: marked as done (sphinxsearch: Still maintained (same version since stretch)?)
Your message dated Fri, 03 Dec 2021 10:07:02 + with message-id and subject line Bug#939763: fixed in sphinxsearch 2.2.11-5 has caused the Debian Bug report #939763, regarding sphinxsearch: Still maintained (same version since stretch)? 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.) -- 939763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sphinxsearch Severity: important Hi While checking another issue I noticed that sphinxsearch is at 2.2.11 since stretch and was never updated to as well more recent 3.x version. It has unsafe defaults in sample files with listener listening to 0.0.0.0, cf. #939762. Is sphinxsearch still of use or should it be removed from unstable and not included in bullseye? Regards, Salvatore --- End Message --- --- Begin Message --- Source: sphinxsearch Source-Version: 2.2.11-5 Done: Andrej Shadura We believe that the bug you reported is fixed in the latest version of sphinxsearch, 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 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated sphinxsearch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 03 Dec 2021 10:41:03 +0100 Source: sphinxsearch Architecture: source Version: 2.2.11-5 Distribution: unstable Urgency: medium Maintainer: Andrej Shadura Changed-By: Andrej Shadura Closes: 656326 772370 861262 871944 939763 Changes: sphinxsearch (2.2.11-5) unstable; urgency=medium . * New maintainer (Closes: #939763). * Add gbp.conf. * Convert copyright file to machine-readable format. * Add exclusions for current and future releases. * Simplify the init script (Closes: #861262, #772370, #656326). * Fix the crontab user (Closes: #656326). * Update the sample/minimal conf files to match installation paths. * Don't install an extra copy of the configuration sample. * debian/copyright: use spaces rather than tabs to start continuation lines. * Set Standards-Version: 4.6.0. * Drop B-D on dh-autoreconf, autotools-dev and adduser. * Enable re2 support. * Move the example.sql to /usr/share/doc (Closes: #871944). Checksums-Sha1: 8bac5c0abc5e0fccd053f8951695c1821d5cada3 1453 sphinxsearch_2.2.11-5.dsc 2f581af4f6e7fd051e4d31a580225d35801126e4 16816 sphinxsearch_2.2.11-5.debian.tar.xz Checksums-Sha256: e02f2339e87ff419ed86ac676ecc178b0c8bbde78fc83b6fe50df9213d331bfa 1453 sphinxsearch_2.2.11-5.dsc 560d216482ef2f96d2f1570abbe112e4984758dc28008155b9b703ef860c7eed 16816 sphinxsearch_2.2.11-5.debian.tar.xz Files: d4b1ac04a5e83c3670219106706feb39 1453 misc optional sphinxsearch_2.2.11-5.dsc 870bc8f3c0b711f7276265e7c336c99c 16816 misc optional sphinxsearch_2.2.11-5.debian.tar.xz -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCYanpSQAKCRDoRGtKyMdy YfyXAP9cLvrBstyzrkWFSGqSuitY5DfxKvQRCd4Lt2LPOhMQnAEA4h5eAJ56U+vr klFVv/KBHCsbPweDegj2TJ6YIS+Fiwg= =QxDx -END PGP SIGNATURE End Message ---
Bug#994193: iptstate FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]
Hi, Chris, any chance that we get iptstate 2.2.7 in Debian? It's no longer available in Debian/testing. Thanks! regards -mika- * Phil Dibowitz [Sat Oct 16, 2021 at 02:27:09PM -0700]: > Got 2.2.7 out the door. > > Can someone who's a DD do the honors? > > On 9/13/21 6:33 AM, Helmut Grohne wrote: > > Source: iptstate > > Version: 2.2.6-1 > > Severity: serious > > Tags: ftbfs > > > > iptstate fails to build from source in unstable. A build ends as > > follows: > > > > | g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > > -Wformat -Werror=format-security iptstate.cc -o iptstate -lncurses > > -lnetfilter_conntrack > > | iptstate.cc: In function ‘void get_input(WINDOW*, std::string&, const > > string&, const flags_t&)’: > > | iptstate.cc:685:30: error: format not a string literal and no format > > arguments [-Werror=format-security] > > | 685 | wprintw(cmd, prompt.c_str()); > > | | ^ > > | iptstate.cc: In function ‘void c_warn(WINDOW*, const string&, const > > flags_t&)’: > > | iptstate.cc:750:32: error: format not a string literal and no format > > arguments [-Werror=format-security] > > | 750 | wprintw(warn, warning.c_str()); > > | |^ > > | iptstate.cc: In function ‘int conntrack_hook(nf_conntrack_msg_type, > > nf_conntrack*, void*)’: > > | iptstate.cc:1002:30: warning: ‘:’ directive output may be truncated > > writing 1 byte into a region of size between 0 and 5 [-Wformat-truncation=] > > | 1002 | snprintf(ttlc,11, "%3i:%02i:%02i", hours, minutes, seconds); > > | | ^ > > | iptstate.cc:1002:21: note: directive argument in the range [-59, 59] > > | 1002 | snprintf(ttlc,11, "%3i:%02i:%02i", hours, minutes, seconds); > > | | ^~~ > > | iptstate.cc:1002:11: note: ‘snprintf’ output between 10 and 16 bytes into > > a destination of size 11 > > | 1002 | snprintf(ttlc,11, "%3i:%02i:%02i", hours, minutes, seconds); > > | | ^~~ > > | cc1plus: some warnings being treated as errors > > | make[1]: *** [Makefile:34: iptstate] Error 1 > > | make[1]: Leaving directory '/<>' > > | dh_auto_build: error: make -j1 returned exit code 2 > > | make: *** [debian/rules:4: build] Error 25 > > | dpkg-buildpackage: error: debian/rules build subprocess returned exit > > status 2 > > > > Helmut > > > > > -- > Phil Dibowitz p...@ipom.com > Open Source software and tech docsInsanity Palace of Metallica > http://www.phildev.net/ http://www.ipom.com/ > > "Be who you are and say what you feel, because those who mind don't > matter and those who matter don't mind." > - Dr. Seuss signature.asc Description: PGP signature
Processed: FTBFS on i386
Processing control commands: > fixed -1 firefox-esr/91.3.0esr-2 Bug #994799 [firefox-esr] FTBFS on i386 Marked as fixed in versions firefox-esr/91.3.0esr-2; no longer marked as fixed in versions firefox-esr/91.3.0esr-2. -- 994799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994799: FTBFS on i386
Control: fixed -1 firefox-esr/91.3.0esr-2 I think this bug can be closed. A newer version builds on i386.
Processed: FTBFS on i386
Processing control commands: > fixed -1 firefox-esr/91.3.0esr-2 Bug #994799 [firefox-esr] FTBFS on i386 Marked as fixed in versions firefox-esr/91.3.0esr-2. -- 994799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992442: marked as done (bzip2: Use tempfile in /usr/bin/bzexe, which is no longer available)
Your message dated Fri, 03 Dec 2021 09:04:00 + with message-id and subject line Bug#992442: fixed in bzip2 1.0.8-5 has caused the Debian Bug report #992442, regarding bzip2: Use tempfile in /usr/bin/bzexe, which is no longer available 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.) -- 992442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bzip2 Severity: grave Version: 1.0.8-4 Control: tags -1 sid X-Debbugs-CC: santi...@debian.org santi...@debian.org Dear Debian bzip2 package maintainers, As discussed in https://bugs.debian.org/992396 , the tempfile command has been removed from debianutils package. However, it looks like the bzexe command provided by Debian still uses it: https://sources.debian.org/src/bzip2/1.0.8-4/debian/bzexe/#L123 set -C umask=`umask` umask 77 tmpfile=`tempfile -p gztmp -d /tmp` || exit 1 Please consider switching to mktemp(1) provided by GNU coreutils. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: bzip2 Source-Version: 1.0.8-5 Done: Anthony Fok We believe that the bug you reported is fixed in the latest version of bzip2, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok (supplier of updated bzip2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 03 Dec 2021 01:32:51 -0700 Source: bzip2 Architecture: source Version: 1.0.8-5 Distribution: unstable Urgency: medium Maintainer: Anibal Monsalve Salazar Changed-By: Anthony Fok Closes: 992442 Changes: bzip2 (1.0.8-5) unstable; urgency=medium . [ Gianfranco Costamagna ] * Make tests cross-test-friendly * Add build-essential to test dependencies . [ Santiago Ruano Rincón ] * debian/tests/compare: get expected result from diff * Use mktemp in bzexe instead of the no longer available tempfile (Closes: #992442) * Add debian/tests/bzexe-test . [ Anthony Fok ] * Apply "cme fix dpkg" fixes with some manual tweaks: - Reorganize debian/control fields - Update debhelper-compat to (= 13) - Bump Standards-Version to 4.6.0 (no change) - Remove "Build-Depends: dpkg-dev (>= 1.16.0)", and from bzip2-doc "Depends: dpkg (>= 1.15.4) | install-info" which are no longer necessary - Remove leading '/' from path in debian/libbz2-dev.install Checksums-Sha1: 7cf547dfce50d0e14ad57d73daa334c3f25bc1c1 2206 bzip2_1.0.8-5.dsc a5cb36a3535f07f70a9143542ba918e8c032763e 26787 bzip2_1.0.8-5.debian.tar.bz2 2b8e787a485f8819f725595b27fb2a0434d1e5c2 8506 bzip2_1.0.8-5_amd64.buildinfo Checksums-Sha256: ed9c40f4de3f9e064535e15eac1c61a0f606763db98f4579dbc04067b94a8944 2206 bzip2_1.0.8-5.dsc d68c6eba11d70e14319e24ef1451880a03023b2b75364646adb117086db36039 26787 bzip2_1.0.8-5.debian.tar.bz2 09e7e8d1feb1a13ca7855cf0257fb79f0c12a27d39e860930472fb7ffcdbbe7b 8506 bzip2_1.0.8-5_amd64.buildinfo Files: 3a60737e029d24c66772ac17fc31561f 2206 utils important bzip2_1.0.8-5.dsc 343ef1f61095c9c352d555642bd91196 26787 utils important bzip2_1.0.8-5.debian.tar.bz2 50487df5936701a33f0b695a408d2b53 8506 utils important bzip2_1.0.8-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmGp1u4QHGZva2FAZGVi aWFuLm9yZwAKCRDqJQC0EsWaz7FtD/wLEQAVJo6sP76G4/JvLQ4whbwWMmL6lJDs kXNcZQjpp/CZ0AStqwT4EKJYgkLImVksvsFt72Xzw7UMe1gODtIflgsBQ8LEGX8N lKlXW2re5bYltA+K9acOK2cnxu90uVXHgNHxTS5ncJb18/GgtzttIz9x1dNxTf+j s1lSfurl7mHuCCFnSxhIF4HnsWXsUuWWrFgrGpQT5NVIHIKjgSIfBR9Mi1FNkhNQ UbhEbrxe/ey097cWF8jGz6PQcAmXnfoP3owJvzhlmcbQuSyJA7spPP4ppQx3e3qP qhNfmRR4M7z6WchEW3yqivuTWAlr/Rlh+RrkjUvCMVnH7Z4eeaqlpQ44QIBZzGx/ 3QfD7BqpowieKZbg5TwFRVtxLNlZx37O6ex6cATA6aULnkROkDJ9e00opwkZVlgR 2gLmJlZ1Za2mNbuvcHcaR2xvZ7wuRO/UfYuGwcyM7weTG976KhGSaQvKap4JRi/c lINhztJ3x5osheioELPZ1oAzojK8Tv694LjlWaWHMeZY+TDNUlsINOoQ6do8XGAz uK6pJEUk0LoLG8MT0Xhk1iNF7zEri2ANHhK375agUFsw0gWPWmaZ
Processed: found 999533 in matplotlib/3.5.0-1
Processing commands for cont...@bugs.debian.org: > found 999533 matplotlib/3.5.0-1 Bug #999533 [src:matplotlib] matplotlib: python3-pil.imagetk should be Depends Marked as found in versions matplotlib/3.5.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 999533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999533 is serious, tagging 999533
Processing commands for cont...@bugs.debian.org: > severity 999533 serious Bug #999533 [src:matplotlib] matplotlib: python3-pil.imagetk should be Depends Severity set to 'serious' from 'important' > tags 999533 + ftbfs Bug #999533 [src:matplotlib] matplotlib: python3-pil.imagetk should be Depends Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 999533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure
> > Could you elaborate why? I cannot see much of a difference in these > > when it comes to the topic at hand. Doesn't set[ug]id set all ids > > to > > the given one? > > No, it only sets one of the three (real, effective and saved) uid/gid > to the given one; setres[ug]id() is the one that sets them all. Actually I think that's only correct if you're running under a non-root uid. If your effective uid is 0 all uids will be set to the given value and thus there is no way back for the application to be root again. As I understand it, this is the POSIX way. Anyway, I'm going to prepare a patch. Thanks, Michael -- Michael Meskes Michael at Fam-Meskes dot De Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org
