Processed: Bug#1009168: gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability
Processing commands for cont...@bugs.debian.org: > owner 1009168 ! Bug #1009168 [src:gzip] gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability Owner recorded as Milan Kupcevic . > thanks Stopping processing here. Please contact me if you need assistance. -- 1009168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009205: marked as done (zope.testing: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr)
Your message dated Sat, 09 Apr 2022 07:05:29 +0200 with message-id <985ccae75b9a0cee2e6adbefa09ed...@pfft.no> and subject line Re: zope.testing: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr has caused the Debian Bug report #1009205, regarding zope.testing: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr 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.) -- 1009205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.testing Version: 4.9-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of zope.testing 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.10.4-1 zope.testing from testing4.9-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The test output a deprecation warning to stderr. autopkgtest by default fails on that, unless the allow-stderr restriction is added to the test definition. 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 Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/z/zope.testing/20695044/log.gz :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead Running tests at level 1 Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Running: /usr/lib/python3/dist-packages/zope/testing/module.txt /usr/lib/python3/dist-packages/zope/testing/loggingsupport.txt /usr/lib/python3/dist-packages/zope/testing/renormalizing.txt /usr/lib/python3/dist-packages/zope/testing/setupstack.txt /usr/lib/python3/dist-packages/zope/testing/wait.txt /usr/lib/python3/dist-packages/zope/testing/doctestcase.txt test_input_ellipsis (zope.testing.test_renormalizing.Exception2To3) test_input_empty (zope.testing.test_renormalizing.Exception2To3) test_input_last_line_not_dotted_name (zope.testing.test_renormalizing.Exception2To3) test_input_spaces (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_ascii_dots (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_ascii_no_dots (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_ellipsis (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_not_identifier (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_unicode_dots (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_unicode_no_dots (zope.testing.test_renormalizing.Exception2To3) test_last_line_empty (zope.testing.test_renormalizing.Exception2To3) test_no_colon_in_first_word (zope.testing.test_renormalizing.Exception2To3) test_no_dots_in_name (zope.testing.test_renormalizing.Exception2To3) test_strip_dottedname (zope.testing.test_renormalizing.Exception2To3) test_strip_dottedname_without_exception_arguments (zope.testing.test_renormalizing.Exception2To3) Ran 21 tests with 0 failures, 0 errors and 0 skipped in 0.149 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. autopkgtest [17:10:37]: test all-3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: zope.testing Version: 4.10-1 With the latest upload I added "Restrictions: allow-stderr" to gloss over this deprecation warning. The autopkgtest now correctly tests against multiple Python versions, so these things gets picked
Bug#943251: marked as done (ruby-license-finder: Python2 removal in sid/bullseye)
Your message dated Sat, 09 Apr 2022 03:04:11 + with message-id and subject line Bug#943251: fixed in ruby-license-finder 7.0.1-1 has caused the Debian Bug report #943251, regarding ruby-license-finder: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-license-finder Version: 2.1.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: ruby-license-finder Source-Version: 7.0.1-1 Done: TANIGUCHI Takaki We believe that the bug you reported is fixed in the latest version of ruby-license-finder, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated ruby-license-finder package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Apr 2022 11:59:23 +0900 Source: ruby-license-finder Architecture: source Version: 7.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: TANIGUCHI Takaki Closes: 880324 895358 943251 Changes: ruby-license-finder (7.0.1-1) unstable; urgency=medium . * Team upload. . [ Utkarsh Gupta ] * Add salsa-ci.yml . [ Cédric Boutillier ] * Update team name * Add .gitattributes to keep unwanted files out of the source package . [ TANIGUCHI Takaki ] * New upstream version 7.0.1 - Fix FTBFS (Closes: #880324) - Remove python2 dependency (Closes: #943251) * d/control: - Update python from 2 to 3 - add ruby-tomlrb to B-D - Add ruby-with-env to B-D - Update Vcs-* to salsa - Drop obsolete ruby-interpretter from Depends - Add package managers to Suggests (Closes: #895358) - Remove unneed Build-Depends. * d/patches: - Remove useless patches. - embed python file path * Bump debian-compat to 13 * Bump
Bug#880324: marked as done (ruby-license-finder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect { action_items }.to raise_error(SystemExit))
Your message dated Sat, 09 Apr 2022 03:04:11 +
with message-id
and subject line Bug#880324: fixed in ruby-license-finder 7.0.1-1
has caused the Debian Bug report #880324,
regarding ruby-license-finder: FTBFS: ERROR: Test "ruby2.3" failed:
Failure/Error: expect { action_items }.to raise_error(SystemExit)
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.)
--
880324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-license-finder
Version: 2.1.2-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> Failure/Error: expect { action_items }.to raise_error(SystemExit)
>
> expected SystemExit, got # 'mime-types (< 3.0)' in any of the gem sources listed in your Gemfile.> with
> backtrace:
> # ./lib/license_finder/package_managers/bundler.rb:41:in
> `gem_details'
> # ./lib/license_finder/package_managers/bundler.rb:34:in `details'
> # ./lib/license_finder/package_managers/bundler.rb:13:in
> `current_packages'
> # ./lib/license_finder/package_manager.rb:60:in
> `current_packages_with_relations'
> # ./lib/license_finder/package_manager.rb:23:in `each'
> # ./lib/license_finder/package_manager.rb:23:in `flat_map'
> # ./lib/license_finder/package_manager.rb:23:in `current_packages'
> # ./lib/license_finder/core.rb:63:in `current_packages'
> # ./lib/license_finder/core.rb:58:in `decision_applier'
> # ./lib/license_finder/cli/main.rb:36:in `action_items'
> # ./spec/lib/license_finder/cli/main_spec.rb:183:in `action_items'
> # ./spec/lib/license_finder/cli/main_spec.rb:204:in `block (6
> levels) in '
> # ./spec/lib/license_finder/cli/main_spec.rb:204:in `block (5
> levels) in '
> # ./spec/support/stdout_helpers.rb:19:in `capture_stdout'
> # ./spec/lib/license_finder/cli/main_spec.rb:203:in `block (4
> levels) in '
> # ./spec/lib/license_finder/cli/main_spec.rb:204:in `block (5 levels)
> in '
> # ./spec/support/stdout_helpers.rb:19:in `capture_stdout'
> # ./spec/lib/license_finder/cli/main_spec.rb:203:in `block (4 levels)
> in '
>
> Finished in 2.33 seconds (files took 1.19 seconds to load)
> 502 examples, 14 failures
>
> Failed examples:
>
> rspec ./spec/lib/license_finder/cli/main_spec.rb:25 #
> LicenseFinder::CLI::Main default checks for action items
> rspec ./spec/lib/license_finder/cli/main_spec.rb:81 #
> LicenseFinder::CLI::Main#report reports acknowleged dependencies
> rspec ./spec/lib/license_finder/cli/main_spec.rb:85 #
> LicenseFinder::CLI::Main#report will output a specific format
> rspec ./spec/lib/license_finder/cli/main_spec.rb:91 #
> LicenseFinder::CLI::Main#report will output a custom csv
> rspec ./spec/lib/license_finder/cli/main_spec.rb:100 #
> LicenseFinder::CLI::Main#report when the package is a nuget package will
> includes package_manager for csv report
> rspec ./spec/lib/license_finder/cli/main_spec.rb:115 #
> LicenseFinder::CLI::Main#report in html reports when the project has a name
> should show the project name
> rspec ./spec/lib/license_finder/cli/main_spec.rb:123 #
> LicenseFinder::CLI::Main#report in html reports when the project has no name
> should default to the directory name
> rspec ./spec/lib/license_finder/cli/main_spec.rb:130 #
> LicenseFinder::CLI::Main#report when the --save option is passed calls report
> method and calls save_report
> rspec ./spec/lib/license_finder/cli/main_spec.rb:139 #
> LicenseFinder::CLI::Main#report when the --save option is passed when file
> name is not specified (--save) creates report that is called the default file
> name
> rspec ./spec/lib/license_finder/cli/main_spec.rb:158 #
> LicenseFinder::CLI::Main#report when the --save option is passed when file
> name is specified (--save='FILENAME') saves with a specified file name
> rspec ./spec/lib/license_finder/cli/main_spec.rb:169 #
> LicenseFinder::CLI::Main#report when the --save option is not passed calls
> report method and does not call save_report
> rspec ./spec/lib/license_finder/cli/main_spec.rb:210 #
> LicenseFinder::CLI::Main#action_items reports that all dependencies are
> approved
> rspec ./spec/lib/license_finder/cli/main_spec.rb:189 #
> LicenseFinder::CLI::Main#action_items with unapproved
Bug#984373: marked as done (ucommon: ftbfs with GCC-11)
Your message dated Sat, 09 Apr 2022 01:33:47 +
with message-id
and subject line Bug#984373: fixed in ucommon 7.0.1-0.1
has caused the Debian Bug report #984373,
regarding ucommon: 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.)
--
984373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ucommon
Version: 7.0.0-19
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/ucommon_7.0.0-19_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.
[...]
from /usr/include/c++/11/bits/shared_ptr.h:53,
from /usr/include/c++/11/memory:77,
from ../inc/ucommon/platform.h:32,
from ../ucommon-config.h:323,
from tcp.cpp:40:
/usr/include/c++/11/exception:106:8: note: declared here
106 | bool uncaught_exception() _GLIBCXX_USE_NOEXCEPT __attribute__
((__pure__));
|^~
tcp.cpp:486:58: warning: ‘throw’ will always call ‘terminate’ [-Wterminate]
486 | catch( ... ) { if ( ! std::uncaught_exception()) throw;};
| ^
tcp.cpp:486:58: note: in C++11 destructors default to ‘noexcept’
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-I../inc -Wno-long-long -pthread -fno-check-new -finline -fvisibility=hidden -g
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c socket.cpp -o socket.o >/dev/null 2>&1
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-I../inc -Wno-long-long -pthread -fno-check-new -finline -fvisibility=hidden -g
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c address.cpp -o address.o >/dev/null 2>&1
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-I../inc -Wno-long-long -pthread -fno-check-new -finline -fvisibility=hidden -g
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c udp.cpp -o udp.o >/dev/null 2>&1
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-I../inc -Wno-long-long -pthread -fno-check-new -finline -fvisibility=hidden -g
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c tcp.cpp -o tcp.o >/dev/null 2>&1
/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I..
-Wdate-time -D_FORTIFY_SOURCE=2 -I../inc -Wno-long-long -pthread -fno-check-new
-finline -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -c -o dccp.lo dccp.cpp
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-I../inc -Wno-long-long -pthread -fno-check-new -finline -fvisibility=hidden -g
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c dccp.cpp -fPIC -DPIC -o .libs/dccp.o
/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I..
-Wdate-time -D_FORTIFY_SOURCE=2 -I../inc
Bug#1008739: marked as done (python-pyaudio: FTBFS with Python 3.10 as default)
Your message dated Fri, 08 Apr 2022 23:19:12 +
with message-id
and subject line Bug#1008739: fixed in python-pyaudio 0.2.11-1.4
has caused the Debian Bug report #1008739,
regarding python-pyaudio: FTBFS with Python 3.10 as default
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.)
--
1008739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyaudio
Version: 0.2.11-1.3
Severity: serious
Tags: ftbfs patch bookworm sid
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
As can be seen on reproducible builds [1], python-pyaudio FTBFS with
Python 3.10 as the default version. I've copied what I hope is the
relevant part of the log below.
I've also attached a patch that works for me.
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/rb-pkg/python-pyaudio.html
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-g -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2
-ffile-prefix-map=/build/1st/python-pyaudio-0.2.11=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2
build/temp.linux-x86_64-3.10/src/_portaudiomodule.o -lportaudio -o
build/lib.linux-x86_64-3.10/_portaudio.cpython-310-x86_64-linux-gnu.so
touch build/lib.linux-x86_64-3.1/build
touch: cannot touch 'build/lib.linux-x86_64-3.1/build': No such file
or directory
make[2]: *** [Makefile:39: build/lib.linux-x86_64-3.1/build] Error 1
Description: Adjust Makefile for Python 3.10
import get_platform() from sysconfig instead of distutils
support Python with 2-digit minor version
Author: Graham Inggs
Last-Update: 2022-03-31
--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@
BUILD_ARGS ?=
SPHINX ?= sphinx-build
DOCS_OUTPUT=docs/
-PYTHON_BUILD_DIR:=$(shell $(PYTHON) -c "import distutils.util; import sys; print(distutils.util.get_platform() + '-' + sys.version[0:3])")
+PYTHON_BUILD_DIR:=$(shell $(PYTHON) -c "import sysconfig; import sys; print(sysconfig.get_platform() + '-' + ('%d.%d' % sys.version_info[:2]))")
BUILD_DIR:=lib.$(PYTHON_BUILD_DIR)
BUILD_STAMP:=$(BUILD_DIR)/build
SRCFILES := src/*.c src/*.h src/*.py
--- End Message ---
--- Begin Message ---
Source: python-pyaudio
Source-Version: 0.2.11-1.4
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-pyaudio, 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 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated python-pyaudio
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: Sun, 03 Apr 2022 18:12:25 -0400
Source: python-pyaudio
Architecture: source
Version: 0.2.11-1.4
Distribution: unstable
Urgency: medium
Maintainer: Hubert Pham
Changed-By: Stefano Rivera
Closes: 1008739
Changes:
python-pyaudio (0.2.11-1.4) unstable; urgency=medium
.
* Non-maintainer upload.
* Python 3.10 support. (Closes: #1008739)
Checksums-Sha1:
615892f9a15a75307a9cafd4dfe0d51c954dc268 1602 python-pyaudio_0.2.11-1.4.dsc
3db37fbc60896f9dc089d4add2354967674783f1 4284
python-pyaudio_0.2.11-1.4.debian.tar.xz
affd36970def14d2a602d5dd58f1a45f47b557ec 7233
python-pyaudio_0.2.11-1.4_source.buildinfo
Checksums-Sha256:
9f6d9826a911938b1222baafe69468cd4daa119bd6feca99a78f975a3bbecb07 1602
python-pyaudio_0.2.11-1.4.dsc
14de53f2117e8a380aeac9d533fcc4725a16d76555fa3d8271bf559ee21ea5fd 4284
python-pyaudio_0.2.11-1.4.debian.tar.xz
9b3fcbf225291c608522e82254146eb82c66a0571b3355a393ab8c1d3c29e7fb 7233
python-pyaudio_0.2.11-1.4_source.buildinfo
Files:
2ced6580f1cd0ac968410ccf982ce4ed 1602 python optional
python-pyaudio_0.2.11-1.4.dsc
58e2daa6490fc38510794016e02acb67 4284 python optional
python-pyaudio_0.2.11-1.4.debian.tar.xz
b4cbf3b5d14603f68eb9855208d46ad0 7233 python optional
python-pyaudio_0.2.11-1.4_source.buildinfo
-BEGIN PGP SIGNATURE-
iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYkoigxQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2PP9AQCR7phYHTFRlRe1hbzi1xP15NyJktmI
Amn4qt8FyHhWHQD+Pcj9/ApwaZvfL2EEOKAfN5qek+uG/EPLlTnSx0rymQ8=
=PI4g
-END PGP
Bug#1003907: fails to successfully associate
Hi Am 08.04.22 um 10:11 schrieb Michael Biebl: Am 08.04.22 um 09:56 schrieb Andrej Shadura: I noticed you uploaded the workaround to Debian, and it’s about to migrate to testing — how about downgrading the bug from release-critical? Assuming that it actually helps. Once NM is in testing for a couple of days, feel free to close the bug report. Hm, you could add a versioned Breaks against network-manager to ensure you have at least NM 1.36.4-2 together with wpasupplicant 2.10. I'll leave that up to you. Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#965444: marked as done (byacc-j: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Fri, 08 Apr 2022 20:33:56 + with message-id and subject line Bug#965444: fixed in byacc-j 1.15-1.1 has caused the Debian Bug report #965444, regarding byacc-j: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: byacc-j Version: 1.15-1 Severity: normal Usertags: compat-5-6-removal Hi, The package byacc-j uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: byacc-j Source-Version: 1.15-1.1 Done: Marcos Talau We believe that the bug you reported is fixed in the latest version of byacc-j, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcos Talau (supplier of updated byacc-j 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, 08 Apr 2022 13:55:53 -0300 Source: byacc-j Architecture: source Version: 1.15-1.1 Distribution: unstable Urgency: medium Maintainer: Ludovic Claude Changed-By: Marcos Talau Closes: 965444 Changes: byacc-j (1.15-1.1) unstable; urgency=medium . * Non-maintainer upload. * Update debhelper version from 6 to 7 (Closes: #965444). Consequently: - debian/compat: Bump debhelper compat level from 6 to 7. - debian/control: Change debhelper version from 6 to 7 in Build-Depends. Checksums-Sha1: 1ba9b8646ec8c8993c456074f294b1793d3b0800 1803 byacc-j_1.15-1.1.dsc 131542974136af8486f85b4e47a4329b81decf99 4344 byacc-j_1.15-1.1.diff.gz 516da5deed9a72751a47f243430bc5886cb91761 6510 byacc-j_1.15-1.1_source.buildinfo Checksums-Sha256: 1624819a709c665dedba6d762d54e443f7b38eea94bf9a5f8b981923c3a9430a 1803 byacc-j_1.15-1.1.dsc 05df79db22152e796685c2ecee9d7e4cea5e5f905a851bd261bb59365114d7d4 4344 byacc-j_1.15-1.1.diff.gz 25ac42811f06a3647662db213c9f3c819b0092a947efd00d9c0b7cb7e93b36ec 6510 byacc-j_1.15-1.1_source.buildinfo Files: b50712e19319f0ff8ef0ffc468615f4c 1803 devel extra byacc-j_1.15-1.1.dsc 11f8036d4904c66980664cb66cf3ef25 4344 devel extra byacc-j_1.15-1.1.diff.gz 8b96f4da4bd5db9c92c65c0f0b14154f 6510 devel extra byacc-j_1.15-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJQle0ACgkQ3mO5xwTr 6e+wbQ/+IrcHmVCccL6HjpN7JrZRQh8Wse6pe62nnlSSfyGSxykFjGO6NmPqfgXW j9rVrpd6A/+atQCzINwMLnHfBy2dBGkKEMBBFjyqE0i9MsuwHgs3qbS75KS9NliE hKPs/sZjsVLHSDGRf9k84rzxV6C4vONu5C+2/4XGfrCFmMreR2Qc3pqo14a4TbxR 8CkHqzcs6v/MzzQn3w+X5MoCAMVUpGHbu8JIVbDpCfBT83kp5Qb+Cxyl1CfzJPD5 VUwHDj7mUnTes3ocaKRvnZn6UpoWR3fqpyHcBIAqxYTMQEd0sxD5yDq7XToLrEn9 /BXyu3nzoIxcqwrcYWdBmLMiUxWqaal4/93aDBu3zQzV6YyC9cKRr09/c7PHjgTT j+s1fsSfqjYl+Fu5o3AK8vBYSrCnLbRqNiOJUo2Vvmy5JHAdbnnBCsiTDnXe5x1+ IHWCqGZ3d6OaBj+zXrXmQUHevj46s4UWTukWTrWXIGFiVZ2BVD/NfqlrXFslrjUp WdbXsJMnd/6yqaKxGuZ5uiRfQ+AaYhIjTq504+OqhNxwxYWse0K/dAXr1+S4tkAm G8UF/TKN7faDzMluAgaGMljlnaIw9W43NsgcqhUVtJdQg0cH8PXbgklOhE+AcnBf DNJsDjU0CecxgPGND3xKzrAP78ckFJVjoLywl8dOGAccEdVIfos= =cSvW -END PGP
Bug#1009209: isc-dhcp-server: dhcpd is not starting due to stale pid file
Package: isc-dhcp-server Severity: grave Tags: patch X-Debbugs-Cc: none, H.-Dirk Schmitt In /etc/init.d/isc-dhcp-server the daemon start is inhibited if a pid file is existing. The content is not checked. So a stale pidfile hinder the start and has to be resolved manually. deb-patch Description: Binary data -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (600, 'stable-updates'), (600, 'stable-security'), (600, 'stable'), (500, 'oldstable-updates'), (490, 'focal-updates'), (490, 'focal-security'), (490, 'focal'), (200, 'testing'), (99, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE=de_DE:de:en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --
Processed: ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array
Processing control commands: > found -1 ruby-i18n/1.10.0-1 Bug #1009208 [src:ruby-i18n, src:ruby-faker] ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array Marked as found in versions ruby-i18n/1.10.0-1. > found -1 ruby-faker/1.9.1-3 Bug #1009208 [src:ruby-i18n, src:ruby-faker] ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array Marked as found in versions ruby-faker/1.9.1-3. -- 1009208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009208: ruby-i18n breaks ruby-faker autopkgtest: FrozenError: can't modify frozen Array
Source: ruby-i18n, ruby-faker Control: found -1 ruby-i18n/1.10.0-1 Control: found -1 ruby-faker/1.9.1-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of ruby-i18n the autopkgtest of ruby-faker fails in testing when that autopkgtest is run with the binary packages of ruby-i18n from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-i18n from testing1.10.0-1 ruby-faker from testing1.9.1-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 ruby-i18n 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=ruby-i18n https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-faker/20675518/log.gz TestFakerCoffee: test_blend_name: E === Error: test_blend_name(TestFakerCoffee): FrozenError: can't modify frozen Array: ["Summer", "Holiday", "Jacked", "Joe", "Express", "Reg's", "Split", "Spilt", "Chocolate", "Dark", "Veranda", "Major", "Bluebery", "American", "Huggy", "Wake-up", "Morning", "Evening", "Winter", "Captain's", "Thanksgiving", "Seattle", "Brooklyn", "Café", "Blacktop", "Pumpkin-spice", "Good-morning", "Postmodern", "The Captain's", "The", "Cascara", "Melty", "Heart", "Goodbye", "Hello", "Street", "Red", "Blue", "Green", "Strong", "KrebStar", "Kreb-Full-o"] /tmp/autopkgtest-lxc.g__r9hf1/downtmp/build.mfV/src/test/test_faker_coffee.rb:13:in `concat' /tmp/autopkgtest-lxc.g__r9hf1/downtmp/build.mfV/src/test/test_faker_coffee.rb:13:in `setup' === : (0.001053) test_notes: E === Error: test_notes(TestFakerCoffee): FrozenError: can't modify frozen Array: ["Summer", "Holiday", "Jacked", "Joe", "Express", "Reg's", "Split", "Spilt", "Chocolate", "Dark", "Veranda", "Major", "Bluebery", "American", "Huggy", "Wake-up", "Morning", "Evening", "Winter", "Captain's", "Thanksgiving", "Seattle", "Brooklyn", "Café", "Blacktop", "Pumpkin-spice", "Good-morning", "Postmodern", "The Captain's", "The", "Cascara", "Melty", "Heart", "Goodbye", "Hello", "Street", "Red", "Blue", "Green", "Strong", "KrebStar", "Kreb-Full-o"] /tmp/autopkgtest-lxc.g__r9hf1/downtmp/build.mfV/src/test/test_faker_coffee.rb:13:in `concat' /tmp/autopkgtest-lxc.g__r9hf1/downtmp/build.mfV/src/test/test_faker_coffee.rb:13:in `setup' === : (0.000827) test_origin: E === Error: test_origin(TestFakerCoffee): FrozenError: can't modify frozen Array: ["Summer", "Holiday", "Jacked", "Joe", "Express", "Reg's", "Split", "Spilt", "Chocolate", "Dark", "Veranda", "Major", "Bluebery", "American", "Huggy", "Wake-up", "Morning", "Evening", "Winter", "Captain's", "Thanksgiving", "Seattle", "Brooklyn", "Café", "Blacktop", "Pumpkin-spice", "Good-morning", "Postmodern", "The Captain's", "The", "Cascara", "Melty", "Heart", "Goodbye", "Hello", "Street", "Red", "Blue", "Green", "Strong", "KrebStar", "Kreb-Full-o"] /tmp/autopkgtest-lxc.g__r9hf1/downtmp/build.mfV/src/test/test_faker_coffee.rb:13:in `concat' /tmp/autopkgtest-lxc.g__r9hf1/downtmp/build.mfV/src/test/test_faker_coffee.rb:13:in `setup' === : (0.000886) test_variety: E === Error: test_variety(TestFakerCoffee): FrozenError: can't modify frozen Array: ["Summer", "Holiday", "Jacked", "Joe", "Express", "Reg's", "Split", "Spilt", "Chocolate", "Dark", "Veranda", "Major", "Bluebery", "American", "Huggy", "Wake-up", "Morning", "Evening", "Winter", "Captain's", "Thanksgiving", "Seattle", "Brooklyn", "Café", "Blacktop", "Pumpkin-spice", "Good-morning", "Postmodern", "The Captain's", "The", "Cascara", "Melty", "Heart", "Goodbye", "Hello", "Street", "Red", "Blue", "Green", "Strong", "KrebStar", "Kreb-Full-o"] /tmp/autopkgtest-lxc.g__r9hf1/downtmp/build.mfV/src/test/test_faker_coffee.rb:13:in `concat'
Processed: python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri'
Processing control commands: > found -1 python-websockets/10.2-1 Bug #1009207 [src:python-websockets, src:python-hbmqtt] python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri' Marked as found in versions python-websockets/10.2-1. > found -1 python-hbmqtt/0.9.6-1.2 Bug #1009207 [src:python-websockets, src:python-hbmqtt] python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri' Marked as found in versions python-hbmqtt/0.9.6-1.2. -- 1009207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009207: python-websockets breaks python-hbmqtt autopkgtest: cannot import name 'InvalidURI' from 'websockets.uri'
Source: python-websockets, python-hbmqtt Control: found -1 python-websockets/10.2-1 Control: found -1 python-hbmqtt/0.9.6-1.2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of python-websockets the autopkgtest of python-hbmqtt fails in testing when that autopkgtest is run with the binary packages of python-websockets from unstable. It passes when run with only packages from testing. In tabular form: passfail python-websockets from testing10.2-1 python-hbmqtt from testing0.9.6-1.2 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 python-websockets 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=python-websockets https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-hbmqtt/20680286/log.gz ..EE == ERROR: Failure: ImportError (cannot import name 'InvalidURI' from 'websockets.uri' (/usr/lib/python3/dist-packages/websockets/uri.py)) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in loadTestsFromName module = self.importer.importFromPath( File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.9/imp.py", line 234, in load_module return load_source(name, filename, file) File "/usr/lib/python3.9/imp.py", line 171, in load_source module = _load(spec) File "", line 711, in _load File "", line 680, in _load_unlocked File "", line 850, in exec_module File "", line 228, in _call_with_frames_removed File "/tmp/autopkgtest-lxc.2lsi273v/downtmp/build.QiD/src/tests/test_broker.py", line 21, in from hbmqtt.client import MQTTClient, ConnectException File "/tmp/autopkgtest-lxc.2lsi273v/downtmp/build.QiD/src/hbmqtt/client.py", line 21, in from websockets.uri import InvalidURI ImportError: cannot import name 'InvalidURI' from 'websockets.uri' (/usr/lib/python3/dist-packages/websockets/uri.py) == ERROR: Failure: ImportError (cannot import name 'InvalidURI' from 'websockets.uri' (/usr/lib/python3/dist-packages/websockets/uri.py)) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest raise self.exc_val.with_traceback(self.tb) File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in loadTestsFromName module = self.importer.importFromPath( File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/usr/lib/python3.9/imp.py", line 234, in load_module return load_source(name, filename, file) File "/usr/lib/python3.9/imp.py", line 171, in load_source module = _load(spec) File "", line 711, in _load File "", line 680, in _load_unlocked File "", line 850, in exec_module File "", line 228, in _call_with_frames_removed File "/tmp/autopkgtest-lxc.2lsi273v/downtmp/build.QiD/src/tests/test_client.py", line 8, in from hbmqtt.client import MQTTClient, ConnectException File "/tmp/autopkgtest-lxc.2lsi273v/downtmp/build.QiD/src/hbmqtt/client.py", line 21, in from websockets.uri import InvalidURI ImportError: cannot import name 'InvalidURI' from 'websockets.uri' (/usr/lib/python3/dist-packages/websockets/uri.py) -- Ran 64 tests in 1.074s FAILED (errors=2) autopkgtest [01:10:11]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Bug#1009206: snek: autopkgtest regression: ../ports/qemu-riscv/snek-riscv: not found
Source: snek Version: 1.8-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of snek the autopkgtest of snek fails in testing when that autopkgtest is run with the binary packages of snek from unstable. It passes when run with only packages from testing. In tabular form: passfail snek from testing1.8-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 to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=snek https://ci.debian.net/data/autopkgtest/testing/amd64/s/snek/20675520/log.gz make: Entering directory '/tmp/autopkgtest-lxc.6neckhwq/downtmp/build.sEx/src/test' Running test pass-andor.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-list.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-dict.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-equal_is.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-float.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-for-array.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-for-range.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-for-string.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-for-break.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-for-nested.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-global.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-if.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-int.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-math.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-nan.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-op.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-random.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-range.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-slice.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-while.py. pass python3 pass snek pass snek-arm /bin/sh: 6: ../ports/qemu-riscv/snek-riscv: not found * snek-riscv fail * Running test pass-while-break.py. pass python3 pass snek pass snek-arm /bin/sh: 6:
Processed: zope.testing: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr
Processing control commands: > affects -1 src:python3-defaults Bug #1009205 [src:zope.testing] zope.testing: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr Added indication that 1009205 affects src:python3-defaults -- 1009205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009205: zope.testing: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr
Source: zope.testing Version: 4.9-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of zope.testing 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.10.4-1 zope.testing from testing4.9-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The test output a deprecation warning to stderr. autopkgtest by default fails on that, unless the allow-stderr restriction is added to the test definition. 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 Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/z/zope.testing/20695044/log.gz :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives :1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead Running tests at level 1 Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Running: /usr/lib/python3/dist-packages/zope/testing/module.txt /usr/lib/python3/dist-packages/zope/testing/loggingsupport.txt /usr/lib/python3/dist-packages/zope/testing/renormalizing.txt /usr/lib/python3/dist-packages/zope/testing/setupstack.txt /usr/lib/python3/dist-packages/zope/testing/wait.txt /usr/lib/python3/dist-packages/zope/testing/doctestcase.txt test_input_ellipsis (zope.testing.test_renormalizing.Exception2To3) test_input_empty (zope.testing.test_renormalizing.Exception2To3) test_input_last_line_not_dotted_name (zope.testing.test_renormalizing.Exception2To3) test_input_spaces (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_ascii_dots (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_ascii_no_dots (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_ellipsis (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_not_identifier (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_unicode_dots (zope.testing.test_renormalizing.Exception2To3) test_is_dotted_name_unicode_no_dots (zope.testing.test_renormalizing.Exception2To3) test_last_line_empty (zope.testing.test_renormalizing.Exception2To3) test_no_colon_in_first_word (zope.testing.test_renormalizing.Exception2To3) test_no_dots_in_name (zope.testing.test_renormalizing.Exception2To3) test_strip_dottedname (zope.testing.test_renormalizing.Exception2To3) test_strip_dottedname_without_exception_arguments (zope.testing.test_renormalizing.Exception2To3) Ran 21 tests with 0 failures, 0 errors and 0 skipped in 0.149 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. autopkgtest [17:10:37]: test all-3 OpenPGP_signature Description: OpenPGP digital signature
Processed: vdirsyncer: (autopkgtest) needs update for python3.10: python3.9: command not found
Processing control commands: > affects -1 src:python3-defaults Bug #1009204 [src:vdirsyncer] vdirsyncer: (autopkgtest) needs update for python3.10: python3.9: command not found Added indication that 1009204 affects src:python3-defaults -- 1009204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009204: vdirsyncer: (autopkgtest) needs update for python3.10: python3.9: command not found
Source: vdirsyncer Version: 0.18.0-6 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of vdirsyncer 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.10.4-1 vdirsyncer from testing0.18.0-6 all others from testingfrom testing I copied some of the output at the bottom of this report. Seems like you are hard-coding the python version in your test without ensuring that that version is installed. Please don't hard-code the python version. 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 Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/v/vdirsyncer/20695042/log.gz bash: line 1: python3.9: command not found autopkgtest [17:10:36]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Processed: unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr
Processing control commands: > affects -1 src:python3-defaults Bug #1009203 [src:unicycler] unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr Added indication that 1009203 affects src:python3-defaults -- 1009203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009203: unicycler: (autopkgtest) needs update for python3.10: fails on deprecation warning on stderr
Source: unicycler Version: 0.4.8+dfsg-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of unicycler 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.10.4-1 unicycler from testing0.4.8+dfsg-2 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 Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/u/unicycler/20675511/log.gz Error: SPAdes encountered an error: /usr/lib/spades/bin/spades.py:13: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives OpenPGP_signature Description: OpenPGP digital signature
Bug#1009202: typer: (autopkgtest) needs update for python3.10: fails on deprecation warning
Source: typer Version: 0.4.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of typer 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.10.4-1 typer from testing0.4.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The test output a deprecation warning to stderr. autopkgtest by default fails on that, unless the allow-stderr restriction is added to the test definition. 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 Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/t/typer/20676193/log.gz /usr/lib/python3/dist-packages/pytest_sugar.py:168: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives from distutils.version import LooseVersion /usr/lib/python3/dist-packages/pytest_sugar.py:168: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives from distutils.version import LooseVersion OpenPGP_signature Description: OpenPGP digital signature
Processed: typer: (autopkgtest) needs update for python3.10: fails on deprecation warning
Processing control commands: > affects -1 src:python3-defaults Bug #1009202 [src:typer] typer: (autopkgtest) needs update for python3.10: fails on deprecation warning Added indication that 1009202 affects src:python3-defaults -- 1009202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009201: toil: (autopkgtest) needs update for python3.10: No such file or directory: 'python3.9'
Source: toil
Version: 5.6.0-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of making python3.10 the default Python
versions [0]. With a recent upload of python3-defaults the autopkgtest
of toil 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.10.4-1
toil from testing5.6.0-5
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 Python3.10, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1006836
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/t/toil/20695041/log.gz
=== FAILURES
===
___ ToilDebugFileTest.testFetchJobStoreFiles
___
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/toil/test/utils/toilDebugTest.py", line
31, in setUp
subprocess.check_call([python,
os.path.abspath('src/toil/test/utils/ABCWorkflowDebug/debugWorkflow.py')])
File "/usr/lib/python3.10/subprocess.py", line 364, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib/python3.10/subprocess.py", line 345, in call
with Popen(*popenargs, **kwargs) as p:
File "/usr/lib/python3.10/subprocess.py", line 966, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.10/subprocess.py", line 1842, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'python3.9'
Captured stdout setup
-
[TEST]
toil.test.utils.toilDebugTest.ToilDebugFileTest:testFetchJobStoreFiles
(Apr 08 2022 17:25:05:962381 PDT)
__ ToilDebugFileTest.testFetchJobStoreFilesWSymlinks
___
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/toil/test/utils/toilDebugTest.py", line
31, in setUp
subprocess.check_call([python,
os.path.abspath('src/toil/test/utils/ABCWorkflowDebug/debugWorkflow.py')])
File "/usr/lib/python3.10/subprocess.py", line 364, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib/python3.10/subprocess.py", line 345, in call
with Popen(*popenargs, **kwargs) as p:
File "/usr/lib/python3.10/subprocess.py", line 966, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.10/subprocess.py", line 1842, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'python3.9'
Captured stdout setup
-
[TEST]
toil.test.utils.toilDebugTest.ToilDebugFileTest:testFetchJobStoreFilesWSymlinks
(Apr 08 2022 17:25:05:967075 PDT)
__ UtilsTest.testGetPIDStatus
__
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/toil/test/utils/utilsTest.py",
line 297, in testGetPIDStatus
wf = subprocess.Popen(self.sort_workflow_cmd)
File "/usr/lib/python3.10/subprocess.py", line 966, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.10/subprocess.py", line 1842, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'python3.9'
Captured stdout setup
-
[TEST] toil.test.utils.utilsTest.UtilsTest:testGetPIDStatus (Apr 08 2022
17:25:07:984146 PDT)
-- Captured log call
---
INFO toil.test:__init__.py:109 Setting up
toil.test.utils.utilsTest.UtilsTest.testGetPIDStatus ...
INFO toil.test:__init__.py:114 Tore down
toil.test.utils.utilsTest.UtilsTest.testGetPIDStatus
_ UtilsTest.testGetStatusFailedToilWF
__
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/toil/test/utils/utilsTest.py",
line 314, in testGetStatusFailedToilWF
wf = subprocess.Popen(self.sort_workflow_cmd + ['--badWorker=1'])
Processed: toil: (autopkgtest) needs update for python3.10: No such file or directory: 'python3.9'
Processing control commands: > affects -1 src:python3-defaults Bug #1009201 [src:toil] toil: (autopkgtest) needs update for python3.10: No such file or directory: 'python3.9' Added indication that 1009201 affects src:python3-defaults -- 1009201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: FTBFS is RC
Processing commands for cont...@bugs.debian.org: > severity 1005028 serious Bug #1005028 [pyx3] pyx3: fix t1 extension with Python 3.10 Severity set to 'serious' from 'normal' > tag 1005028 ftbfs Bug #1005028 [pyx3] pyx3: fix t1 extension with Python 3.10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009200: pytorch: (autopkgtest) needs update for python3.10: 'float' object cannot be interpreted as an integer
Source: pytorch
Version: 1.8.1-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of making python3.10 the default Python
versions [0]. With a recent upload of python3-defaults the autopkgtest
of pytorch 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.10.4-1
pytorchfrom testing1.8.1-5
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 Python3.10, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1006836
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytorch/20675875/log.gz
=== FAILURES
===
TestDistributions.test_invalid_parameter_broadcasting
_
self = testMethod=test_invalid_parameter_broadcasting>
def test_invalid_parameter_broadcasting(self):
# invalid broadcasting cases; should throw error
# example type (distribution class, distribution params)
invalid_examples = [
(Normal, {
'loc': torch.tensor([[0, 0]]),
'scale': torch.tensor([1, 1, 1, 1])
}),
(Normal, {
'loc': torch.tensor([[[0, 0, 0], [0, 0, 0]]]),
'scale': torch.tensor([1, 1])
}),
(FisherSnedecor, {
'df1': torch.tensor([1, 1]),
'df2': torch.tensor([1, 1, 1]),
}),
(Gumbel, {
'loc': torch.tensor([[0, 0]]),
'scale': torch.tensor([1, 1, 1, 1])
}),
(Gumbel, {
'loc': torch.tensor([[[0, 0, 0], [0, 0, 0]]]),
'scale': torch.tensor([1, 1])
}),
(Gamma, {
'concentration': torch.tensor([0, 0]),
'rate': torch.tensor([1, 1, 1])
}),
(Kumaraswamy, {
'concentration1': torch.tensor([[1, 1]]),
'concentration0': torch.tensor([1, 1, 1, 1])
}),
(Kumaraswamy, {
'concentration1': torch.tensor([[[1, 1, 1], [1, 1, 1]]]),
'concentration0': torch.tensor([1, 1])
}),
(Laplace, {
'loc': torch.tensor([0, 0]),
'scale': torch.tensor([1, 1, 1])
}),
(Pareto, {
'scale': torch.tensor([1, 1]),
'alpha': torch.tensor([1, 1, 1])
}),
(StudentT, {
'df': torch.tensor([1, 1]),
'scale': torch.tensor([1, 1, 1])
}),
(StudentT, {
'df': torch.tensor([1, 1]),
'loc': torch.tensor([1, 1, 1])
})
]
for dist, kwargs in invalid_examples:
self.assertRaises(RuntimeError, dist, **kwargs)
distributions/test_distributions.py:2871: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/torch/distributions/studentT.py:45: in
__init__
self.df, self.loc, self.scale = broadcast_all(df, loc, scale)
/usr/lib/python3/dist-packages/torch/distributions/utils.py:37: in
broadcast_all
new_values = [v if isinstance(v, torch.Tensor) or
has_torch_function((v,)) else torch.tensor(v, **options)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
new_values = [v if isinstance(v, torch.Tensor) or has_torch_function((v,))
else torch.tensor(v, **options)
for v in values]
E TypeError: 'float' object cannot be interpreted as an integer
/usr/lib/python3/dist-packages/torch/distributions/utils.py:37: TypeError
=== warnings summary
===
../../../../../../usr/lib/python3/dist-packages/torch/testing/_internal/common_cuda.py:9
/usr/lib/python3/dist-packages/torch/testing/_internal/common_cuda.py:9:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
from distutils.version import LooseVersion
test/distributions/test_distributions.py::TestJit::test_cdf
Processed: pytorch: (autopkgtest) needs update for python3.10: 'float' object cannot be interpreted as an integer
Processing control commands: > affects -1 src:python3-defaults Bug #1009200 [src:pytorch] pytorch: (autopkgtest) needs update for python3.10: 'float' object cannot be interpreted as an integer Added indication that 1009200 affects src:python3-defaults -- 1009200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009199: src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf
Source: tcpreplay Version: 4.3.4-1 Severity: serious Control: close -1 4.4.0-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:tcpreplay has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails to build from source on armhf where it built successfully in the past. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=tcpreplay OpenPGP_signature Description: OpenPGP digital signature
Processed: src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf
Processing control commands: > close -1 4.4.0-1 Bug #1009199 [src:tcpreplay] src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf Marked as fixed in versions tcpreplay/4.4.0-1. Bug #1009199 [src:tcpreplay] src:tcpreplay: fails to migrate to testing for too long: ftbfs on armhf Marked Bug as done -- 1009199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009097: meson: (autopkgtest) needs update for python3.10: MesonVersionMismatchException.__init__() missing 1 required positional argument: 'current_version'
Hi
On 08-04-2022 19:53, Jussi Pakkanen wrote:
On Thu, 7 Apr 2022 at 11:36, Paul Gevers wrote:
I copied some of the output at the bottom of this report. I noticed that
there is a new version of meson in unstable, it fails too, but in a
different way.
Can you provide the logs for that?
e.g.
https://ci.debian.net/data/autopkgtest/unstable/amd64/m/meson/20672106/log.gz
Traceback (most recent call last):
File "/usr/bin/meson", line 29, in
sys.exit(mesonmain.main())
File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line
269, in main
return run(sys.argv[1:], launcher)
File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line
260, in run
return CommandLineParser().run(args)
File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line
151, in run
return options.run_func(options)
File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 301,
in run
app.generate()
File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 185,
in generate
self._generate(env)
File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 229,
in _generate
intr.run()
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreter/interpreter.py",
line 2698, in run
super().run()
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 149, in run
self.evaluate_codeblock(self.ast, start=1)
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 174, in evaluate_codeblock
raise e
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 167, in evaluate_codeblock
self.evaluate_statement(cur)
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 190, in evaluate_statement
return self.evaluate_if(cur)
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 273, in evaluate_if
self.evaluate_codeblock(i.block)
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 174, in evaluate_codeblock
raise e
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 167, in evaluate_codeblock
self.evaluate_statement(cur)
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 180, in evaluate_statement
return self.function_call(cur)
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py",
line 455, in function_call
res = func(node, func_args, kwargs)
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/decorators.py",
line 73, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
File
"/usr/lib/python3/dist-packages/mesonbuild/interpreter/interpreter.py",
line 1322, in func_error
raise InterpreterException('Problem encountered: ' + '
'.join(args_str))
mesonbuild.interpreterbase.exceptions.InterpreterException: Problem
encountered: Python3 purelib path seems invalid?
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Processed: severity of 1009167 is grave, severity of 1009168 is grave
Processing commands for cont...@bugs.debian.org: > severity 1009167 grave Bug #1009167 [src:xz-utils] xz-utils: CVE-2022-1271: xzgrep: arbitrary-file-write vulnerability Severity set to 'grave' from 'important' > severity 1009168 grave Bug #1009168 [src:gzip] gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1009167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009167 1009168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009097: meson: (autopkgtest) needs update for python3.10: MesonVersionMismatchException.__init__() missing 1 required positional argument: 'current_version'
On Thu, 7 Apr 2022 at 11:36, Paul Gevers wrote: > I copied some of the output at the bottom of this report. I noticed that > there is a new version of meson in unstable, it fails too, but in a > different way. Can you provide the logs for that? I have looked at the error message and it makes zero sense. It's complaining about a missing argument to a constructor but grepping says that every place we create said classes we pass two arguments. In fact it seems like something goes wrong in Python's serialisation/deserialisation code. In fact I have a vague suspicion that the underlying issue might be the same as for #1004107. Sadly nobody has managed to reproduce either of those. If one could run a full distro built with tsan, this issue would probably reveal itself fairly quickly.
Bug#1008755: marked as done (optlang/interface.py unusable with python3.10)
Your message dated Fri, 08 Apr 2022 17:48:48 + with message-id and subject line Bug#1008755: fixed in optlang 1.5.2-1 has caused the Debian Bug report #1008755, regarding optlang/interface.py unusable with python3.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.) -- 1008755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: optlang Version: 1.4.4-2 Severity: serious Tags: patch upstream Justification: RT Dear Fellow Maintainer, While addressing failure to build from source in libsbml, I noticed that python-cobra, one of its reverse dependencies, had autopkgtest regressions: its test suite failed to run, raising the following error: self = , stuff = [] sloppy = False def add(self, stuff, sloppy=False): """Add variables and constraints. Parameters -- stuff : iterable, Variable, Constraint Either an iterable containing variables and constraints or a single variable or constraint. sloppy : bool Check constraints for variables that are not part of the model yet. Returns --- None """ if self._pending_modifications.toggle == 'remove': self.update() self._pending_modifications.toggle = 'add' > if isinstance(stuff, collections.Iterable): E AttributeError: module 'collections' has no attribute 'Iterable' /usr/lib/python3/dist-packages/optlang/interface.py:1358: AttributeError The full log is available on ci.debian.net[1]. This turned out to be caused by optlang. Using the patch in attachment, I worked around the issue, and autopkgtest of python-cobra went back on tracks on my side. [1]: https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cobra/20469873/log.gz Thanks for maintaining optlang! Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/11, please excuse my verbosity. On air: It Bites - The Last Escape Description: call collections.abc.Iterables instead of collections.Iterables This allows the module to operate properly when using python3.10. Author: Étienne Mollier Forwarded: no Last-Update: 2022-03-31 --- This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ --- optlang-1.4.4.orig/optlang/interface.py +++ optlang-1.4.4/optlang/interface.py @@ -1355,7 +1355,7 @@ if self._pending_modifications.toggle == 'remove': self.update() self._pending_modifications.toggle = 'add' -if isinstance(stuff, collections.Iterable): +if isinstance(stuff, collections.abc.Iterable): for elem in stuff: self.add(elem, sloppy=sloppy) elif isinstance(stuff, Variable): @@ -1404,7 +1404,7 @@ self._pending_modifications.rm_var.append(stuff) elif isinstance(stuff, Constraint): self._pending_modifications.rm_constr.append(stuff) -elif isinstance(stuff, collections.Iterable): +elif isinstance(stuff, collections.abc.Iterable): for elem in stuff: self.remove(elem) elif isinstance(stuff, Objective): signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: optlang Source-Version: 1.5.2-1 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of optlang, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated optlang 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, 08 Apr 2022 19:23:13 +0200 Source: optlang Architecture: source Version: 1.5.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Étienne Mollier
Bug#1009188: github link
github link : https://github.com/OpenPrinting/ipp-usb/issues/48
Bug#1009192: marked as done (node-autoprefixer build is broken due to missing text-encoding dependency)
Your message dated Fri, 08 Apr 2022 15:49:54 + with message-id and subject line Bug#1009192: fixed in node-autoprefixer 10.4.2.0+dfsg1+~cs24.7.3-3 has caused the Debian Bug report #1009192, regarding node-autoprefixer build is broken due to missing text-encoding dependency 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.) -- 1009192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-autoprefixer Severity: serious Version: 10.4.2.0+dfsg1+~cs24.7.3-1 Justification: broken build makes it unusable from build log https://buildd.debian.org/status/fetch.php?pkg=node-autoprefixer=all=10.4.2.0%2Bdfsg1%2B%7Ecs24.7.3-2=1645260584=0 [1mautoprefixer.js[22m → [1m../vendor/autoprefixer.js[22m...[39m [1m[33m(!) Plugin replace: @rollup/plugin-replace: 'preventAssignment' currently defaults to false. It is recommended to set this option to `true`, as the next major version will default this option to `true`.[39m[22m [1m[33m(!) Unresolved dependencies[39m[22m [90mhttps://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency[39m [1mtext-encoding[22m (imported by ./../../../usr/share/nodejs/whatwg-url/lib/encoding.js) [1m[33m(!) Missing global variable name[39m[22m Use output.globals to specify browser global variable names corresponding to external modules [1mtext-encoding[22m (guessing 'textEncoding') [32mcreated [1m../vendor/autoprefixer.js[22m in [1m11.5s[22m[39m Broken build noticed in gitlab package. --- End Message --- --- Begin Message --- Source: node-autoprefixer Source-Version: 10.4.2.0+dfsg1+~cs24.7.3-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-autoprefixer, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-autoprefixer 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, 08 Apr 2022 17:36:55 +0200 Source: node-autoprefixer Architecture: source Version: 10.4.2.0+dfsg1+~cs24.7.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1009192 Changes: node-autoprefixer (10.4.2.0+dfsg1+~cs24.7.3-3) unstable; urgency=medium . * Team upload * Add missing build dependency to node-text-encoding. Thanks to Pirate Praveen (Closes: #1009192) Checksums-Sha1: 54c69e462de9ec3d00c78ba496a68e78f83fbabb 3915 node-autoprefixer_10.4.2.0+dfsg1+~cs24.7.3-3.dsc 198ea568b6a6d9b619a6606e126fb1103b7b952c 5724 node-autoprefixer_10.4.2.0+dfsg1+~cs24.7.3-3.debian.tar.xz Checksums-Sha256: b26583f13c01581b77d33cd69a9a18455ccdd5e1bc27802a6afefe5660161d97 3915 node-autoprefixer_10.4.2.0+dfsg1+~cs24.7.3-3.dsc 631ede14dd1f588262b8ac3d61a58e754b03145e3d5174f07def64379e3b815e 5724 node-autoprefixer_10.4.2.0+dfsg1+~cs24.7.3-3.debian.tar.xz Files: 8ec1b1eababe79f062f18e189e9dca4a 3915 javascript optional node-autoprefixer_10.4.2.0+dfsg1+~cs24.7.3-3.dsc 2e32c1bdcbad1a248029c6d6d1e99a30 5724 javascript optional node-autoprefixer_10.4.2.0+dfsg1+~cs24.7.3-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJQVv0ACgkQ9tdMp8mZ 7ukuGA/+OELQgou06BrRVycK652NM75hnu6PwBkQXhk2n/BiAFzwRbh8xNdhRS5i UzOKxIXL/C2tOTTwL7DsPd/EPVidxooSb1tSXBEhB3PkOK779MvZDrALRbugAp6+ Heask8A386GUwqOebh0PVTVEOGP2N3cC+ZsigOSXiSrO0dxn7rkCukfAD+lR9XrN ddYR4OoMb+oYJovF4P1dVYK/8HqoXljBfbM6E5ApuxL+i5dpnsbVtLV66fWgxxJc WOM6FE+7+i4rSBpzK5vWDUKZxUbD+VHtrfhs1MXgfRz/XCFGFIzzIIJgX+cH3++l FzvAlXZ2hQKMMCTuu1GhqA/JL4p2mzVer9XnV60DrAtqW5XuMHFUvrQa2Pj7Q5fZ Raf/RT4MIxit25LOlfaSmPhxPfqM9irSMUE7Wo2LOLTB4pubt/IaqE6O8Z6at9Pg 8UoZ7R5SHJy0WKg25pv50lYDDKGYHQw/uAF4unMBSREdNPQxIzTKwD4KufJLQ6w2 uGhOzZlvIQ8nPtFLzeNnirrfc1axGKpFQ2XPFWdbsBbgeXN4dhw6Y+egovgsiePO cUbBAE3ZB7d8WyLllU8kXnn6DqVaFXgD8oBpFBKSfs8x/qZr6FdVfnk/vpnb1NZv t7HPlm517TPKr1gtGc1OiX5lxNJghng4b8sr82eEFwAdjnn1dbA= =TAKV -END PGP SIGNATURE End Message ---
Processed: Bug#1009192 marked as pending in node-autoprefixer
Processing control commands: > tag -1 pending Bug #1009192 [src:node-autoprefixer] node-autoprefixer build is broken due to missing text-encoding dependency Added tag(s) pending. -- 1009192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009192: marked as pending in node-autoprefixer
Control: tag -1 pending Hello, Bug #1009192 in node-autoprefixer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-autoprefixer/-/commit/d5e280aa0d8964d9fe8bb5c68ade62b873b91c26 Add missing build dependency to node-text-encoding, Thanks to Pirate praveen Closes: #1009192 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009192
Bug#1009090: marked as done (aiofiles: (autopkgtest) needs update for python3.10: fails on deprecation warning)
Your message dated Fri, 08 Apr 2022 15:18:51 + with message-id and subject line Bug#1009090: fixed in aiofiles 0.8.0-3 has caused the Debian Bug report #1009090, regarding aiofiles: (autopkgtest) needs update for python3.10: fails on deprecation warning 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.) -- 1009090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aiofiles Version: 0.8.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of aiofiles 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.10.4-1 aiofiles from testing0.8.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. The test output a deprecation warning to stderr. autopkgtest by default fails on that, unless the allow-stderr restriction is added to the test definition. 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 Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/a/aiofiles/20646393/log.gz /tmp/autopkgtest-lxc.tojb2bz2/downtmp/build.eCZ/src/debian/tests/runtest.py:13: DeprecationWarning: There is no current event loop event_loop = asyncio.get_event_loop() autopkgtest [06:10:09]: test runtest.py OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: aiofiles Source-Version: 0.8.0-3 Done: David Steele We believe that the bug you reported is fixed in the latest version of aiofiles, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Steele (supplier of updated aiofiles 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, 08 Apr 2022 10:59:54 -0400 Source: aiofiles Architecture: source Version: 0.8.0-3 Distribution: unstable Urgency: medium Maintainer: David Steele Changed-By: David Steele Closes: 1009090 Changes: aiofiles (0.8.0-3) unstable; urgency=medium . * Fix deprecation warnings (Closes: #1009090). Checksums-Sha1: bc7982cc8d742771d7d2fd151e93e3adfdde86c2 2063 aiofiles_0.8.0-3.dsc 6e3867a8a69e78a50a069c806b23615102449718 3128 aiofiles_0.8.0-3.debian.tar.xz c4aaca1da2185f298cbeee4948a04f425695f3dd 6884 aiofiles_0.8.0-3_source.buildinfo Checksums-Sha256: 5fc0f66fc0fedb964c9c6653843c55eb236e3e803d1a6e0dd875c9ed25e3ebf8 2063 aiofiles_0.8.0-3.dsc cebcc2e59a504b1ccb64a928b3f4d4eae92085a9e9367cb4774ba6161b224404 3128 aiofiles_0.8.0-3.debian.tar.xz 6cb28ad823d09c62bbf243abc39235b1e5bb793ed173e97d34bdf900383318fb 6884 aiofiles_0.8.0-3_source.buildinfo Files: 5c8815b6887f2afaebaed9b88094ab29 2063 python optional aiofiles_0.8.0-3.dsc 511fc9c8a0240014ccaa044ffa220946 3128 python optional aiofiles_0.8.0-3.debian.tar.xz 98fd119ecf5e6794363d3227c89b79d8 6884 python optional aiofiles_0.8.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEi4SQsUoAbTYxHS3FCVnEo9z4n78FAmJQT4USHHN0ZWVsZUBk ZWJpYW4ub3JnAAoJEAlZxKPc+J+/hhwP/jDFit//soK8/7YIsPrX02l6D6wc4qir ssRYCeK3qjAgK6kauQ9OU5CDY3joIVeVj74tbKwz7EIYWbl6+i7fZ4Qr+C0l5xUR tRs3c/nvn+mRDZrFhBu9AyfGoY+vjGv1LIz6MvuP5wUGcPT9wk0CYnzFUfWLnV17
Bug#1009188: ipp-usb is not ready for this device
Package: ipp-usb Version: 0.9.20-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: compte.perso.de-al...@bbox.fr first , like it began with the update of dpkg , i thought it was a dpkg bug , but , it did not . (guillem jover , bts) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008716 so , i thought to cups . like the problem is with my printer . https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008997 now , it appears that the problem is with ipp-usb . (brian potkin, bts) i hope that brian potkin saw very well . i'm in trouble . i wonder if the diagnostic is exact ? i mentionned the error message . i don't know what to do ? temporary downgrade ? i' m on bookworm sid and on bullseye stable , cups / ipp-usb is perfectly good . my printer is well recognized and fully fonctionnal . on sid , hplip has never worked and now ipp-usb fails . so i cannot print at all . no scanner too . can you help me ? i also post on github , like it has been suggested to me . now , i'm waiting . thanks for your advices and your help . friendly , respectfuly . alain . -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'testing'), (100, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ipp-usb depends on: ii avahi-daemon 0.8-5 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libc6 2.33-7 ii libusb-1.0-0 2:1.0.25-1 ipp-usb recommends no packages. ipp-usb suggests no packages. -- no debconf information
Bug#1009183: FTBFS in sid: “Error: The configuration option 'pages' was removed from MkDocs”
Source: nlopt Version: 2.7.1-3 Severity: serious Tags: ftbfs Dear Maintainer, nlopt currently fails to build in sid. A build log is attached. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org nlopt_2.7.1-3_amd64-2022-04-08T12:00:38Z.build.gz Description: application/gzip
Bug#1007829: marked as done (arptables - Fails to install: Too many levels of symbolic links)
Your message dated Fri, 08 Apr 2022 11:20:00 + with message-id and subject line Bug#1007829: fixed in arptables 0.0.5-3.1 has caused the Debian Bug report #1007829, regarding arptables - Fails to install: Too many levels of symbolic links 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.) -- 1007829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arptables Version: 0.0.5-3 Severity: grave arptables fails to install, using dpkg 1.21.2: | Unpacking arptables (0.0.5-3) ... | Setting up arptables (0.0.5-3) ... | update-alternatives: using /usr/sbin/arptables-legacy to provide /usr/sbin/arptables (arptables) in auto mode | update-alternatives: error: cannot stat file '/usr/sbin/arptables': Too many levels of symbolic links | dpkg: error processing package arptables (--configure): | installed arptables package post-installation script subprocess returned error exit status 2 | Processing triggers for man-db (2.10.1-1) ... | Errors were encountered while processing: | arptables | E: Sub-process /usr/bin/dpkg returned an error code (1) In the end we have some self-links: | lrwxrwxrwx 1 root root19 Mar 17 12:32 /usr/sbin/arptables -> /usr/sbin/arptables | lrwxrwxrwx 1 root root27 Mar 17 12:32 /usr/sbin/arptables-restore -> /usr/sbin/arptables-restore | lrwxrwxrwx 1 root root24 Mar 17 12:32 /usr/sbin/arptables-save -> /usr/sbin/arptables-save Bastian -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-3-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages arptables depends on: ii libc6 2.33-7 arptables recommends no packages. arptables suggests no packages. --- End Message --- --- Begin Message --- Source: arptables Source-Version: 0.0.5-3.1 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of arptables, 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 1007...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated arptables package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 06 Apr 2022 10:31:00 +0200 Source: arptables Architecture: source Version: 0.0.5-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter Packaging Team Changed-By: Thomas Goirand Closes: 1007829 Changes: arptables (0.0.5-3.1) unstable; urgency=medium . * Non-maintainer upload. * Do not install /sbin/* compat symlink, cleans them if they are still present (Closes: #1007829). Checksums-Sha1: 3f0cd4b0410a17051b04193de17c433ef04bcdac 1996 arptables_0.0.5-3.1.dsc a8128d21d543fdfa8282b0c4812fbcd299e2c8ed 5508 arptables_0.0.5-3.1.debian.tar.xz 309d03f526ac28dd452b38a92ae91cc704f958ca 6200 arptables_0.0.5-3.1_amd64.buildinfo Checksums-Sha256: 85d1af1513020177d64508078d6b9379ef9b90438cd212442be40446a1c47e3d 1996 arptables_0.0.5-3.1.dsc e6d99d4e2e56acf04fa75a39725ceee62927daabfae287a4c5419877587a67b3 5508 arptables_0.0.5-3.1.debian.tar.xz 02c3956e45a3cc3793bd4763fee44d0f80d30191554fd51e4a993bf7f999ed2d 6200 arptables_0.0.5-3.1_amd64.buildinfo Files: dacf0c36f154d76b133de4abf729e5bc 1996 net optional arptables_0.0.5-3.1.dsc 6150998e60c71324ae9f2cbdc43e0d28 5508 net optional arptables_0.0.5-3.1.debian.tar.xz fc22fb06243b3e0c61bc9e6b9fbf9b14 6200 net optional arptables_0.0.5-3.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmJNWl0ACgkQ1BatFaxr Q/5M8Q/+LphZbh26OK+KC2PPLlwHAh+LZJuXaskpI/Zw08gchSf6CpggYHeIh44C 1Df9DQBTkZGIokNM8fVEBvi8vnGPmEjxQmpc+TQIDwjcNDlPojDjQ2RSY0r2VAAh LWyahq+PpcyfShE05oHtgMXN3lhtgHiq260GcWMas/MgnjgOSwJ+qA0Zgcoz0+mK wZ6vheBq4t3ykuXg7s56skXXD81AToPZ0V6sxlTUnfCryn6Tv3pZhqbl0GjLs2FK jHThepsG6S1TKB14UjZuML6IAA68ieMlbKUfjJu6tPxNlfZw4WDBvhgWG2jtewIG
Bug#1009110: marked as done (pysurfer: (autopkgtest) needs update for python3.10: cannot import name 'Sequence' from 'collections')
Your message dated Fri, 08 Apr 2022 10:19:29 + with message-id and subject line Bug#1009110: fixed in pysurfer 0.11.0-3 has caused the Debian Bug report #1009110, regarding pysurfer: (autopkgtest) needs update for python3.10: cannot import name 'Sequence' from 'collections' 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.) -- 1009110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pysurfer Version: 0.11.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of pysurfer 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.10.4-1 pysurfer from testing0.11.0-2 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 Python3.10, it may help to identify what needs to be updated. https://docs.python.org/3.9/library/collections.html says: """ Deprecated since version 3.3, will be removed in version 3.10: Moved Collections Abstract Base Classes to the collections.abc module. For backwards compatibility, they continue to be visible in this module through Python 3.9. """ Time to move on. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/pysurfer/20663038/log.gz = test session starts == platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0 -- /usr/bin/python3 cachedir: .pytest_cache rootdir: /tmp/autopkgtest-lxc.v2wopsdx/downtmp/autopkgtest_tmp collecting ... collected 0 items / 2 errors ERRORS _ ERROR collecting tests/test_utils.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.v2wopsdx/downtmp/autopkgtest_tmp/tests/test_utils.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.10/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_utils.py:9: in from surfer import utils /usr/lib/python3/dist-packages/surfer/__init__.py:1: in from .viz import Brain, TimeViewer # noqa /usr/lib/python3/dist-packages/surfer/viz.py:25: in from . import utils, io /usr/lib/python3/dist-packages/surfer/utils.py:1: in from collections import Sequence E ImportError: cannot import name 'Sequence' from 'collections' (/usr/lib/python3.10/collections/__init__.py) __ ERROR collecting tests/test_viz.py __ ImportError while importing test module '/tmp/autopkgtest-lxc.v2wopsdx/downtmp/autopkgtest_tmp/tests/test_viz.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.10/importlib/__init__.py:126: in import_module return _bootstrap._gcd_import(name[level:], package, level) tests/test_viz.py:15: in from surfer import Brain, io, utils /usr/lib/python3/dist-packages/surfer/__init__.py:1: in from .viz import Brain, TimeViewer # noqa /usr/lib/python3/dist-packages/surfer/viz.py:25: in from . import utils, io /usr/lib/python3/dist-packages/surfer/utils.py:1: in from collections import Sequence E ImportError: cannot import name 'Sequence' from 'collections' (/usr/lib/python3.10/collections/__init__.py) === warnings summary === tests/test_utils.py:1 /tmp/autopkgtest-lxc.v2wopsdx/downtmp/autopkgtest_tmp/tests/test_utils.py:1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for
Processed: Bug#1009110 marked as pending in pysurfer
Processing control commands: > tag -1 pending Bug #1009110 [src:pysurfer] pysurfer: (autopkgtest) needs update for python3.10: cannot import name 'Sequence' from 'collections' Added tag(s) pending. -- 1009110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009110: marked as pending in pysurfer
Control: tag -1 pending Hello, Bug #1009110 in pysurfer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/pysurfer/-/commit/d8f327c0516eaa75669f5deaa7e18d7cdf7cd90d Add python3.10.patch to fix collections import Closes: #1009110 (this message was generated automatically) -- Greetings https://bugs.debian.org/1009110
Bug#1003907: fails to successfully associate
Am 08.04.22 um 09:56 schrieb Andrej Shadura: Hi, On Mon, 4 Apr 2022, at 10:47, Michael Biebl wrote: That said, there might be a workaround available in NetworkManager I filed https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/964 and a potential fix is now available in https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1175 Thanks Beniamino and Thomas! Andrew, could we keep this bug report at RC until we have a fix? Even if the fix means a workaround in NM. I noticed you uploaded the workaround to Debian, and it’s about to migrate to testing — how about downgrading the bug from release-critical? Assuming that it actually helps. Once NM is in testing for a couple of days, feel free to close the bug report. Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1003907: fails to successfully associate
Hi, On Mon, 4 Apr 2022, at 10:47, Michael Biebl wrote: > That said, there might be a workaround available in NetworkManager > I filed > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/964 > and a potential fix is now available in > > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1175 > > Thanks Beniamino and Thomas! > > > Andrew, could we keep this bug report at RC until we have a fix? > Even if the fix means a workaround in NM. I noticed you uploaded the workaround to Debian, and it’s about to migrate to testing — how about downgrading the bug from release-critical? Assuming that it actually helps. -- Cheers, Andrej
Bug#1009175: marked as done (python3-samba package trying to replace file owned by samba one (dckeytab))
Your message dated Fri, 08 Apr 2022 07:33:48 + with message-id and subject line Bug#1009175: fixed in samba 2:4.16.0+dfsg-3 has caused the Debian Bug report #1009175, regarding python3-samba package trying to replace file owned by samba one (dckeytab) 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.) -- 1009175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-samba Version: 2:4.16.0+dfsg-2 Severity: serious Hello, When updating my system this morning, I got the following error: Préparation du dépaquetage de .../03-python3-samba_2%3a4.16.0+dfsg-2_amd64.deb ... Dépaquetage de python3-samba (2:4.16.0+dfsg-2) sur (2:4.13.14+dfsg-1+b3) ... dpkg: erreur de traitement de l'archive /tmp/apt-dpkg-install-pB0IcL/03-python3-samba_2%3a4.16.0+dfsg-2_amd64.deb (--unpack) : tentative de remplacement de « /usr/lib/python3/dist-packages/samba/dckeytab.cpython-310-x86_64-linux-gnu.so », qui appartient aussi au paquet samba 2:4.13.14+dfsg-1+b3 dpkg-deb: erreur: coller subprocess was killed by signal (Relais brisé (pipe)) Apparently the dckeytab.cpython-310-x86_64-linux-gnu.so file moved from the samba package to the python3-samba without the proper Breaks/Replaces -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages python3-samba depends on: ii libbsd0 0.11.6-1 ii libc6 2.33-7 ii libgnutls30 3.7.3-4+b1 ii libldb2 2:2.5.0+smb-2+samba4.16.0+dfsg ii libpython3.10 3.10.4-3 ii libtalloc2 2.3.3-3+b1 ii libtevent0 0.11.0-1 ii libwbclient02:4.16.0+dfsg-2 ii python3 3.10.4-1 ii python3-ldb 2:2.5.0+smb-2+samba4.16.0+dfsg ii python3-talloc 2.3.3-3+b1 ii python3-tdb 1.4.6-2+b1 ii samba-libs 2:4.16.0+dfsg-2 Versions of packages python3-samba recommends: ii python3-gpg 1.16.0-1.2 python3-samba suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: samba Source-Version: 2:4.16.0+dfsg-3 Done: Michael Tokarev We believe that the bug you reported is fixed in the latest version of samba, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated samba 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, 08 Apr 2022 10:18:23 +0300 Source: samba Architecture: source Version: 2:4.16.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Samba Maintainers Changed-By: Michael Tokarev Closes: 1009175 Changes: samba (2:4.16.0+dfsg-3) unstable; urgency=medium . * d/control: comment out the selftest-mode build deps for now * d/control: forgotten python3-samba:Replaces against samba package too, not just samba-libs, when moving dckeytab python lib (Closes: #1009175) Checksums-Sha1: 4b41efa0607fadbe10f0bec7d23fd8eb7f76e19c 4294 samba_4.16.0+dfsg-3.dsc bf22b7c453b7951a01a4dbf939ffb42b16ef94f2 260688 samba_4.16.0+dfsg-3.debian.tar.xz c42f3771fe63ed53b1bdb8d242fe460846cadf3c 6015 samba_4.16.0+dfsg-3_source.buildinfo Checksums-Sha256: b015067dff383f76fb855e43f8f65db35804bab657dd745da7184d1cdf09a122 4294 samba_4.16.0+dfsg-3.dsc 1aa242fd26f9ffb8a6ccb43568080acce84cd811d719c3ce6ccb7d2559bcacbd 260688 samba_4.16.0+dfsg-3.debian.tar.xz 4ca6289776722a05905332024d1c4fdaaef244ae3da71f56c512ad1136a3f59f 6015 samba_4.16.0+dfsg-3_source.buildinfo Files: 39efdf288cacd7c418d1430e7ba7d2f7 4294 net optional samba_4.16.0+dfsg-3.dsc 2426306177914422e021a0438abced3c 260688 net optional samba_4.16.0+dfsg-3.debian.tar.xz 65c84c02955ea5b1e3329e0bcf6d5d6a 6015
Bug#1009175: python3-samba package trying to replace file owned by samba one (dckeytab)
Package: python3-samba Version: 2:4.16.0+dfsg-2 Severity: serious Hello, When updating my system this morning, I got the following error: Préparation du dépaquetage de .../03-python3-samba_2%3a4.16.0+dfsg-2_amd64.deb ... Dépaquetage de python3-samba (2:4.16.0+dfsg-2) sur (2:4.13.14+dfsg-1+b3) ... dpkg: erreur de traitement de l'archive /tmp/apt-dpkg-install-pB0IcL/03-python3-samba_2%3a4.16.0+dfsg-2_amd64.deb (--unpack) : tentative de remplacement de « /usr/lib/python3/dist-packages/samba/dckeytab.cpython-310-x86_64-linux-gnu.so », qui appartient aussi au paquet samba 2:4.13.14+dfsg-1+b3 dpkg-deb: erreur: coller subprocess was killed by signal (Relais brisé (pipe)) Apparently the dckeytab.cpython-310-x86_64-linux-gnu.so file moved from the samba package to the python3-samba without the proper Breaks/Replaces -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages python3-samba depends on: ii libbsd0 0.11.6-1 ii libc6 2.33-7 ii libgnutls30 3.7.3-4+b1 ii libldb2 2:2.5.0+smb-2+samba4.16.0+dfsg ii libpython3.10 3.10.4-3 ii libtalloc2 2.3.3-3+b1 ii libtevent0 0.11.0-1 ii libwbclient02:4.16.0+dfsg-2 ii python3 3.10.4-1 ii python3-ldb 2:2.5.0+smb-2+samba4.16.0+dfsg ii python3-talloc 2.3.3-3+b1 ii python3-tdb 1.4.6-2+b1 ii samba-libs 2:4.16.0+dfsg-2 Versions of packages python3-samba recommends: ii python3-gpg 1.16.0-1.2 python3-samba suggests no packages. -- no debconf information
Bug#1009173: libradare2-5.0.0: Missing (or maybe misnamed) shared objects make cutter not work
Package: libradare2-5.0.0 Version: 5.5.0+dfsg-1 Severity: grave X-Debbugs-Cc: Dima Kogan Hi. I have the latest radare2-cutter installed (1.12.0-1). It does this: $ Cutter Cutter: error while loading shared libraries: libr_core.so.5.0.0: cannot open shared object file: No such file or directory $ ldd `which Cutter` ... libr_core.so.5.0.0 => not found libr_fs.so.5.0.0 => not found libr_debug.so.5.0.0 => not found ... So the Cutter tool is looking for the radare2 libraries version 5.0.0. This package is called "libradare2-5.0.0", so it's a reasonable expectation to find those libraries there. As expected, radare2-cutter has Depends: libradare2-5.0.0 But this package doesn't contain those libraries. It has instead $ dpkg -L libradare2-5.0.0 | grep libr_ /usr/lib/x86_64-linux-gnu/libr_anal.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_asm.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_bin.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_bp.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_config.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_cons.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_core.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_crypto.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_debug.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_egg.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_flag.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_fs.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_hash.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_io.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_lang.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_magic.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_main.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_parse.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_reg.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_search.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_socket.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_syscall.so.5.5.0 /usr/lib/x86_64-linux-gnu/libr_util.so.5.5.0 I.e. it has packages version 5.5.0, not 5.0.0. I'm filing this bug here and not against radare2-cutter, because THIS package has "5.0.0" in the package name and "5.5.0" in the filenames. Thanks -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'testing'), (500, 'unstable-debug'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf-8, LC_CTYPE=en_US.utf-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf-8), LANGUAGE=en_US.utf-8 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libradare2-5.0.0 depends on: ii libc6 2.33-1 ii libcapstone4 4.0.2-5 ii liblz4-1 1.9.3-2 ii libmagic1 1:5.41-2 ii libradare2-common 5.5.0+dfsg-1 ii libuv1 1.42.0-1 ii libxxhash0 0.8.0-2 ii libzip41.7.3-1 ii zlib1g 1:1.2.11.dfsg-2 libradare2-5.0.0 recommends no packages. libradare2-5.0.0 suggests no packages. -- no debconf information
Bug#996114: marked as done (atig: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:)
Your message dated Fri, 08 Apr 2022 06:33:45 + with message-id and subject line Bug#996114: fixed in atig 0.6.1-7 has caused the Debian Bug report #996114, regarding atig: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError: 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.) -- 996114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: atig Version: 0.6.1-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, atig was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > NoMethodError: >undefined method `rstrip' for URI:Module > # ./lib/atig/ofilter/short_url.rb:34:in `block in short_urls' > # ./lib/atig/ofilter/short_url.rb:33:in `gsub' > # ./lib/atig/ofilter/short_url.rb:33:in `short_urls' > # ./lib/atig/ofilter/short_url.rb:18:in `call' > # ./spec/ofilter/short_url_spec.rb:72:in `block (2 levels) in (required)>' > > Top 10 slowest examples (5.52 seconds, 81.4% of total time): > Atig::Db::Statuses should cleanup > 4.68 seconds ./spec/db/statuses_spec.rb:174 > Atig::Db::Statuses should have uniq tid/sid when removed > 0.10701 seconds ./spec/db/statuses_spec.rb:164 > Atig::Db::Statuses should remove by id > 0.09703 seconds ./spec/db/statuses_spec.rb:159 > Atig::Db::Statuses should have unique tid > 0.09698 seconds ./spec/db/statuses_spec.rb:73 > Atig::Db::Statuses should call listeners > 0.09557 seconds ./spec/db/statuses_spec.rb:41 > Atig::Db::Statuses should not contain duplicate > 0.08973 seconds ./spec/db/statuses_spec.rb:56 > Atig::Db::Statuses should be found by id > 0.08836 seconds ./spec/db/statuses_spec.rb:64 > Atig::Db::Statuses should be found by tid > 0.08785 seconds ./spec/db/statuses_spec.rb:114 > Atig::Db::Statuses should be found all > 0.08773 seconds ./spec/db/statuses_spec.rb:83 > Atig::Db::Statuses should be found by user > 0.08682 seconds ./spec/db/statuses_spec.rb:118 > > Top 10 slowest example groups: > Atig::Db::Statuses > 0.39621 seconds average (5.94 seconds / 15 examples) > ./spec/db/statuses_spec.rb:6 > Atig::Db::Lists > 0.03312 seconds average (0.33123 seconds / 10 examples) > ./spec/db/lists_spec.rb:5 > Atig::Db::Followings when updated users > 0.03086 seconds average (0.30862 seconds / 10 examples) > ./spec/db/followings_spec.rb:20 > Atig::Db::Followings when it is empty > 0.01675 seconds average (0.01675 seconds / 1 example) > ./spec/db/followings_spec.rb:5 > Atig::OFilter::EscapeUrl > 0.00924 seconds average (0.01848 seconds / 2 examples) > ./spec/ofilter/escape_url_spec.rb:9 > Atig::Command::Favorite > 0.00507 seconds average (0.02536 seconds / 5 examples) > ./spec/command/favorite_spec.rb:5 > Atig::Command::Autofix > 0.00423 seconds average (0.00846 seconds / 2 examples) > ./spec/command/autofix_spec.rb:5 > Atig::Command::Destroy when remove recently tweet > 0.00284 seconds average (0.00851 seconds / 3 examples) > ./spec/command/destroy_spec.rb:21 > Atig::Command::Thread > 0.00218 seconds average (0.01524 seconds / 7 examples) > ./spec/command/thread_spec.rb:5 > Atig::Command::Status > 0.00181 seconds average (0.01087 seconds / 6 examples) > ./spec/command/status_spec.rb:5 > > Finished in 6.78 seconds (files took 0.38496 seconds to load) > 182 examples, 5 failures > > Failed examples: > > rspec ./spec/ofilter/escape_url_spec.rb:26 # Atig::OFilter::EscapeUrl escape > only url > rspec ./spec/ofilter/short_url_spec.rb:17 # Atig::OFilter::ShortUrl when > no-login bitly should shorten url by bitly > rspec ./spec/ofilter/short_url_spec.rb:35 # Atig::OFilter::ShortUrl when > no-login bitly with size should only shorten large url > rspec ./spec/ofilter/short_url_spec.rb:53 # Atig::OFilter::ShortUrl when > login bitly should only shorten large url > rspec ./spec/ofilter/short_url_spec.rb:71 # Atig::OFilter::ShortUrl when > login bitly with size should only shorten large url > > /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
