Bug#1000303: liboqs: not yet ready for testing or stable
Source: liboqs Severity: serious The upstream wishes to keep the package out of stable distributions for now, until the NIST Post-Quantum Cryptography standardization project reaches its conclusion. For the time being the package may be used for prototyping and evaluation in unstable. Andrius
Bug#997878: marked as done (python-click breaks python-softlayer autopkgtest: 'NoneType' object is not iterable)
Your message dated Sun, 21 Nov 2021 06:34:03 +
with message-id
and subject line Bug#997878: fixed in python-softlayer 5.9.7-1
has caused the Debian Bug report #997878,
regarding python-click breaks python-softlayer autopkgtest: 'NoneType' object
is not iterable
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.)
--
997878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-click, python-softlayer
Control: found -1 python-click/8.0.2-1
Control: found -1 python-softlayer/5.8.5-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-click the autopkgtest of python-softlayer
fails in testing when that autopkgtest is run with the binary packages
of python-click from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
python-click from testing8.0.2-1
python-softlayer from testing5.8.5-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-click 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-click
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-softlayer/16215050/log.gz
=== FAILURES
===
___ VirtCreateTests.test_create_like
___
'NoneType' object is not iterable
During handling of the above exception, another exception occurred:
NOTE: Incompatible Exception Representation, displaying natively:
testtools.testresult.real._StringException: Traceback (most recent call
last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1346, in patched
return func(*newargs, **newkeywargs)
File
"/tmp/autopkgtest-lxc.st1ir0ft/downtmp/build.Zrk/src/tests/CLI/modules/vs/vs_create_tests.py",
line 370, in test_create_like
self.assert_called_with('SoftLayer_Virtual_Guest',
'generateOrderTemplate', args=args)
File
"/tmp/autopkgtest-lxc.st1ir0ft/downtmp/build.Zrk/src/SoftLayer/testing/__init__.py",
line 144, in assert_called_with
raise AssertionError('%s::%s was not called with given properties: %s'
AssertionError: SoftLayer_Virtual_Guest::generateOrderTemplate was not
called with given properties: {'args': ({'datacenter': {'name':
'dal05'}, 'domain': 'test.sftlyr.ws', 'hourlyBillingFlag': True,
'hostname': 'vs-test-like', 'startCpus': 2, 'maxMemory': 1024,
'localDiskFlag': False, 'operatingSystemReferenceCode': 'UBUNTU_LATEST',
'networkComponents': [{'maxSpeed': 100}],
'supplementalCreateObjectOptions': {'bootMode': None}},)}
- Captured stderr call
-
CRITICAL:root:SoftLayer_Virtual_Guest::generateOrderTemplate property
mismatch, args: expected=({'datacenter': {'name': 'dal05'}, 'domain':
'test.sftlyr.ws', 'hourlyBillingFlag': True, 'hostname': 'vs-test-like',
'startCpus': 2, 'maxMemory': 1024, 'localDiskFlag': False,
'operatingSystemReferenceCode': 'UBUNTU_LATEST', 'networkComponents':
[{'maxSpeed': 100}], 'supplementalCreateObjectOptions': {'bootMode':
None}},); actual=({'startCpus': 2, 'maxMemory': 1024, 'hostname':
'vs-test-like', 'domain': 'test.sftlyr.ws', 'localDiskFlag': False,
'hourlyBillingFlag': True, 'supplementalCreateObjectOptions':
{'bootMode': None}, 'operatingSystemReferenceCode': 'UBUNTU_LATEST',
'datacenter': {'name': 'dal05'}, 'networkComponents': [{'maxSpeed':
'100'}]},)
-- Captured log call
---
CRITICAL root:__init__.py:180
SoftLayer_Virtual_Guest::generateOrderTemplate property mismatch, args:
expected=({'datacenter': {'name': 'dal05'}, 'domain': 'test.sftlyr.ws',
'hourlyBillingFlag': True, 'hostname': 'vs-test-like', 'startCpus': 2,
'maxMemory': 1024, 'localDiskFlag': False,
'operatingSystemReferenceCode': 'UBUNTU_LATEST', 'networkComponents':
[{'maxSpeed': 100}], 'supplementalCreateObjectOptions': {'bootMode':
None}},); actual=({'startCpus': 2, 'maxMemory': 1024, 'hostname':
Bug#997878: marked as pending in python-softlayer
Control: tag -1 pending Hello, Bug #997878 in python-softlayer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-softlayer/-/commit/5ef385072e33191f61da0cae6e344ddf01ba916b New upstream release; Closes: #997878 (this message was generated automatically) -- Greetings https://bugs.debian.org/997878
Processed: Bug#997878 marked as pending in python-softlayer
Processing control commands: > tag -1 pending Bug #997878 [src:python-click, src:python-softlayer] python-click breaks python-softlayer autopkgtest: 'NoneType' object is not iterable Added tag(s) pending. -- 997878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999513 is serious, severity of 999516 is serious, severity of 999518 is serious ...
Processing commands for cont...@bugs.debian.org:
> #
> https://tracker.debian.org/news/1279078/accepted-matplotlib-350-1-source-into-unstable/
> severity 999513 serious
Bug #999513 [src:aplpy] aplpy: FTBFS with matplotlib 3.5 (in experimental):
ImportError: cannot import name 'ImageTk' from 'PIL'
(/usr/lib/python3/dist-packages/PIL/__init__.py)
Severity set to 'serious' from 'important'
> severity 999516 serious
Bug #999516 [src:python-ltfatpy] python-ltfatpy: FTBFS with matplotlib 3.5 (in
experimental): dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999518 serious
Bug #999518 [src:mplcursors] mplcursors: FTBFS with matplotlib 3.5 (in
experimental): dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999519 serious
Bug #999519 [src:xrayutilities] xrayutilities: FTBFS with matplotlib 3.5 (in
experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 -s
custom "--test-args={interpreter} {dir}/setup.py egg_info -e {build_dir}; cd
{build_dir}; {interpreter} -m unittest2 discover -v;" returned exit code 13
Severity set to 'serious' from 'important'
> severity 999520 serious
Bug #999520 [src:sphinx-gallery] sphinx-gallery: FTBFS with matplotlib 3.5 (in
experimental): SyntaxError: invalid syntax
Severity set to 'serious' from 'important'
> severity 999529 serious
Bug #999529 [src:seaborn] seaborn: FTBFS with matplotlib 3.5 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Severity set to 'serious' from 'important'
> severity 999531 serious
Bug #999531 [src:python-ase] python-ase: FTBFS with matplotlib 3.5 (in
experimental): dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999534 serious
Bug #999534 [src:python-bayespy] python-bayespy: FTBFS with matplotlib 3.5 (in
experimental): dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999537 serious
Bug #999537 [src:python-matplotlib-venn] python-matplotlib-venn: FTBFS with
matplotlib 3.5 (in experimental): dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999540 serious
Bug #999540 [src:qiskit-terra] qiskit-terra: FTBFS with matplotlib 3.5 (in
experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9
returned exit code 13
Severity set to 'serious' from 'important'
> severity 999541 serious
Bug #999541 [src:astroml] astroml: FTBFS with matplotlib 3.5 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Severity set to 'serious' from 'important'
> severity 999542 serious
Bug #999542 [src:topplot] topplot: FTBFS with matplotlib 3.5 (in experimental):
dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
code 13
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
999513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999513
999516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999516
999518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999518
999519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999519
999520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999520
999529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999529
999531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999531
999534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999534
999537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999537
999540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999540
999541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999541
999542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996126: marked as done (ruby-attr-encrypted: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1))
Your message dated Sun, 21 Nov 2021 03:48:31 + with message-id and subject line Bug#996126: fixed in ruby-attr-encrypted 3.1.0-4 has caused the Debian Bug report #996126, regarding ruby-attr-encrypted: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) 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.) -- 996126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-attr-encrypted Version: 3.1.0-3 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, ruby-attr-encrypted 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): > ArgumentError: wrong number of arguments (given 2, expected 1) > > /usr/share/rubygems-integration/all/gems/activemodel-6.0.3.7/lib/active_model/dirty.rb:169:in > `attribute_changed?' > /<>/lib/attr_encrypted/adapters/active_record.rb:63:in > `block in attr_encrypted' > /<>/test/active_record_test.rb:181:in > `test_should_create_changed_predicate' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 149 runs, 267 assertions, 0 failures, 1 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/active_record_test.rb" "test/attr_encrypted_test.rb" > "test/compatibility_test.rb" "test/legacy_active_record_test.rb" > "test/legacy_attr_encrypted_test.rb" "test/legacy_compatibility_test.rb" > "test/legacy_sequel_test.rb" "test/sequel_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-attr-encrypted/ruby-attr-encrypted_3.1.0-3+rebuild1633375395_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-attr-encrypted Source-Version: 3.1.0-4 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-attr-encrypted, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-attr-encrypted 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, 21 Nov 2021 04:21:44 +0100 Source: ruby-attr-encrypted Architecture: source Version: 3.1.0-4 Distribution: unstable
Bug#999538: pytables: diff for NMU version 3.6.1-5.1
Control: tags 999538 + patch
Control: tags 999538 + pending
Dear maintainer,
I've prepared an NMU for pytables (versioned as 3.6.1-5.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Also available as an MR:
https://salsa.debian.org/science-team/pytables/-/merge_requests/1
Regards,
SR
diff -Nru pytables-3.6.1/debian/changelog pytables-3.6.1/debian/changelog
--- pytables-3.6.1/debian/changelog 2021-09-28 02:05:13.0 -0400
+++ pytables-3.6.1/debian/changelog 2021-11-20 23:32:58.0 -0400
@@ -1,3 +1,12 @@
+pytables (3.6.1-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch: Fix FTBFS with numpy >= 1.20 (Closes: #999538)
+ * Patch: Fix FTBFS with Python 3.10.
+ * Install Python 3.10 C Extensions (2-digit minor version).
+
+ -- Stefano Rivera Sat, 20 Nov 2021 23:32:58 -0400
+
pytables (3.6.1-5) unstable; urgency=medium
* debian/control:
diff -Nru pytables-3.6.1/debian/patches/0010-Use-lowercase-float-int-as-numpy-dtype.patch pytables-3.6.1/debian/patches/0010-Use-lowercase-float-int-as-numpy-dtype.patch
--- pytables-3.6.1/debian/patches/0010-Use-lowercase-float-int-as-numpy-dtype.patch 1969-12-31 20:00:00.0 -0400
+++ pytables-3.6.1/debian/patches/0010-Use-lowercase-float-int-as-numpy-dtype.patch 2021-11-20 23:32:58.0 -0400
@@ -0,0 +1,176 @@
+From: =?utf-8?q?Zbigniew_J=C4=99drzejewski-Szmek?=
+Date: Sun, 24 Jan 2021 16:36:21 +0100
+Subject: Use lowercase float/int as numpy dtype
+
+Float64 is gone with numpy 1.20, which causes doctests to fail
+(https://bugzilla.redhat.com/show_bug.cgi?id=1914335).
+
+Similarly all uses of Float32, Int32 should be replaced by float32 and int32.
+
+>>> numpy.__version__
+'1.19.4'
+>>> [k for k in numpy.sctypeDict.keys() if str(k).lower().startswith('float')]
+['float16', 'Float16', 'float32', 'Float32', 'float64', 'Float64', 'float128', 'Float128', 'float_', 'float']
+
+>>> numpy.__version__
+'1.20.0rc2'
+>>> [k for k in numpy.sctypeDict.keys() if str(k).lower().startswith('float')]
+['float16', 'float32', 'float64', 'float128', 'float_', 'float']
+
+Bug-Upstream: https://github.com/PyTables/PyTables/issues/875
+Bug-Debian: https://bugs.debian.org/999538
+Origin: upstream, https://github.com/PyTables/PyTables/pull/862
+---
+ bench/bsddb-table-bench.py | 10 +-
+ bench/postgres-search-bench.py | 4 ++--
+ bench/pytables-search-bench.py | 6 +++---
+ bench/recarray2-test.py| 2 +-
+ bench/shelve-bench.py | 10 +-
+ bench/sqlite-search-bench.py | 4 ++--
+ tables/atom.py | 2 +-
+ 7 files changed, 19 insertions(+), 19 deletions(-)
+
+diff --git a/bench/bsddb-table-bench.py b/bench/bsddb-table-bench.py
+index dd9f875..a2e0236 100644
+--- a/bench/bsddb-table-bench.py
b/bench/bsddb-table-bench.py
+@@ -83,11 +83,11 @@ def createFile(filename, totalrows, recsize, verbose):
+ # Get the record object associated with the new table
+ if recsize == "big":
+ isrec = Big()
+-arr = np.array(np.arange(32), type=np.Float64)
+-arr2 = np.array(np.arange(32), type=np.Float64)
++arr = np.array(np.arange(32), type=np.float64)
++arr2 = np.array(np.arange(32), type=np.float64)
+ elif recsize == "medium":
+ isrec = Medium()
+-arr = np.array(np.arange(2), type=np.Float64)
++arr = np.array(np.arange(2), type=np.float64)
+ else:
+ isrec = Small()
+ # print d
+@@ -107,8 +107,8 @@ def createFile(filename, totalrows, recsize, verbose):
+ #d['TDCcount'] = i % 256
+ d['ADCcount'] = (i * 256) % (1 << 16)
+ if recsize == "big":
+-#d.float1 = np.array([i]*32, np.Float64)
+-#d.float2 = np.array([i**2]*32, np.Float64)
++#d.float1 = np.array([i]*32, np.float64)
++#d.float2 = np.array([i**2]*32, np.float64)
+ arr[0] = 1.1
+ d['float1'] = arr
+ arr2[0] = 2.2
+diff --git a/bench/postgres-search-bench.py b/bench/postgres-search-bench.py
+index d2c9f4f..7fe83f6 100644
+--- a/bench/postgres-search-bench.py
b/bench/postgres-search-bench.py
+@@ -15,11 +15,11 @@ def flatten(l):
+
+
+ def fill_arrays(start, stop):
+-col_i = numpy.arange(start, stop, type=numpy.Int32)
++col_i = numpy.arange(start, stop, type=numpy.int32)
+ if userandom:
+ col_j = numpy.random.uniform(0, nrows, size=[stop - start])
+ else:
+-col_j = numpy.array(col_i, type=numpy.Float64)
++col_j = numpy.array(col_i, type=numpy.float64)
+ return col_i, col_j
+
+ # Generator for ensure pytables benchmark compatibility
+diff --git a/bench/pytables-search-bench.py b/bench/pytables-search-bench.py
+index 726d30b..6417186 100644
+--- a/bench/pytables-search-bench.py
b/bench/pytables-search-bench.py
+@@ -37,11 +37,11 @@ def create_db(filename, nrows):
+ stop = (j + 1) * step
+ if stop > nrows:
+
Processed: pytables: diff for NMU version 3.6.1-5.1
Processing control commands:
> tags 999538 + patch
Bug #999538 [src:pytables] pytables: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
code 13
Added tag(s) patch.
> tags 999538 + pending
Bug #999538 [src:pytables] pytables: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
code 13
Added tag(s) pending.
--
999538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996126: marked as pending in ruby-attr-encrypted
Control: tag -1 pending Hello, Bug #996126 in ruby-attr-encrypted reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-attr-encrypted/-/commit/98da5fe243d0774be3f007c9217fc9e793e206ed Fix FTBFS by fixing Ruby 2.7/3.0 compatibility * d/patches/fix-ruby-3.0.patch: Add patch. - Fix support for Ruby 2.7 and its kwargs (closes: #996126). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996126
Processed: Bug#996126 marked as pending in ruby-attr-encrypted
Processing control commands: > tag -1 pending Bug #996126 [src:ruby-attr-encrypted] ruby-attr-encrypted: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Added tag(s) pending. -- 996126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996128: marked as done (ruby-awesome-print: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mArgumentError:[0m)
Your message dated Sun, 21 Nov 2021 03:18:47 + with message-id and subject line Bug#996128: fixed in ruby-awesome-print 1.9.2-1 has caused the Debian Bug report #996128, regarding ruby-awesome-print: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mArgumentError:[0m 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.) -- 996128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-awesome-print Version: 1.8.0-2 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, ruby-awesome-print 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): > ArgumentError: > tried to create Proc object without a block > # ./lib/awesome_print/formatters/base_formatter.rb:113:in `new' > # ./lib/awesome_print/formatters/base_formatter.rb:113:in `indented' > # ./lib/awesome_print/formatters/object_formatter.rb:44:in `block in > format' > # ./lib/awesome_print/formatters/object_formatter.rb:31:in `map' > # ./lib/awesome_print/formatters/object_formatter.rb:31:in `format' > # ./lib/awesome_print/formatter.rb:83:in `awesome_object' > # ./lib/awesome_print/formatter.rb:46:in `awesome_self' > # ./lib/awesome_print/formatter.rb:28:in `format' > # ./lib/awesome_print/inspector.rb:116:in `unnested' > # ./lib/awesome_print/inspector.rb:75:in `awesome' > # ./lib/awesome_print/core_ext/kernel.rb:10:in `ai' > # ./spec/objects_spec.rb:156:in `block (3 levels) in ' > > Finished in 0.21808 seconds (files took 0.74765 seconds to load) > 202 examples, 60 failures, 55 pending > > Failed examples: > > rspec ./spec/ext/ostruct_spec.rb:13 # AwesomePrint Ostruct extension plain > multiline > rspec ./spec/formats_spec.rb:16 # AwesomePrint Array plain multiline > rspec ./spec/formats_spec.rb:33 # AwesomePrint Array plain multiline without > index > rspec ./spec/formats_spec.rb:50 # AwesomePrint Array plain multiline indented > rspec ./spec/formats_spec.rb:67 # AwesomePrint Array plain multiline indented > without index > rspec ./spec/formats_spec.rb:88 # AwesomePrint Array colored multiline > (default) > rspec ./spec/formats_spec.rb:105 # AwesomePrint Array colored multiline > indented > rspec ./spec/formats_spec.rb:134 # AwesomePrint Nested Array plain multiline > rspec ./spec/formats_spec.rb:144 # AwesomePrint Nested Array plain multiline > without index > rspec ./spec/formats_spec.rb:165 # AwesomePrint Limited Output Array plain > limited output large > rspec ./spec/formats_spec.rb:179 # AwesomePrint Limited Output Array plain > limited output small > rspec ./spec/formats_spec.rb:191 # AwesomePrint Limited Output Array plain > limited output with 10 lines > rspec ./spec/formats_spec.rb:208 # AwesomePrint Limited Output Array plain > limited output with 11 lines > rspec ./spec/formats_spec.rb:233 # AwesomePrint Limited Output Hash plain > limited output > rspec ./spec/formats_spec.rb:258 # AwesomePrint Hash plain multiline > rspec ./spec/formats_spec.rb:274 # AwesomePrint Hash new hash syntax > rspec ./spec/formats_spec.rb:290 # AwesomePrint Hash plain multiline indented > rspec ./spec/formats_spec.rb:306 # AwesomePrint Hash plain single line > rspec ./spec/formats_spec.rb:310 # AwesomePrint Hash colored multiline > (default) > rspec ./spec/formats_spec.rb:326 # AwesomePrint Hash colored with new hash > syntax > rspec ./spec/formats_spec.rb:342 # AwesomePrint Hash colored multiline > indented > rspec ./spec/formats_spec.rb:358 # AwesomePrint Hash colored single line > rspec ./spec/formats_spec.rb:371 # AwesomePrint Nested Hash plain multiline > rspec ./spec/formats_spec.rb:379 # AwesomePrint Nested Hash plain single line > rspec ./spec/formats_spec.rb:390 # AwesomePrint Hash with several keys plain > multiline > rspec ./spec/formats_spec.rb:410 # AwesomePrint Hash with several keys plain > multiline with sorted keys > rspec ./spec/formats_spec.rb:429 # AwesomePrint Negative options[:indent] > hash keys must be left aligned > rspec ./spec/formats_spec.rb:441 # AwesomePrint Negative options[:indent] > nested hash keys should be indented (array of hashes) > rspec ./spec/formats_spec.rb:460 # AwesomePrint Negative options[:indent] > nested hash keys should be indented
Processed: tagging 996126
Processing commands for cont...@bugs.debian.org: > # https://github.com/attr-encrypted/attr_encrypted/pull/383/files > tags 996126 + patch Bug #996126 [src:ruby-attr-encrypted] ruby-attr-encrypted: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 996126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996128: marked as pending in ruby-awesome-print
Control: tag -1 pending Hello, Bug #996128 in ruby-awesome-print reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-awesome-print/-/commit/4b5ff87b83ad5c1fc0deb31f0c72edbc09f2a529 ruby-awesome-print (1.9.2-1) UNRELEASED * New upstream release. - Provides compatbility with Ruby 3.0 (closes: #996128). (this message was generated automatically) -- Greetings https://bugs.debian.org/996128
Processed: Bug#996128 marked as pending in ruby-awesome-print
Processing control commands: > tag -1 pending Bug #996128 [src:ruby-awesome-print] ruby-awesome-print: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mArgumentError:[0m Added tag(s) pending. -- 996128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996121: marked as done (ruby-acts-as-tree: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/associations/builder/as
Your message dated Sun, 21 Nov 2021 02:36:18 +
with message-id
and subject line Bug#996121: fixed in ruby-acts-as-tree 2.9.1-1
has caused the Debian Bug report #996121,
regarding ruby-acts-as-tree: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
/usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/associations/builder/association.rb:51:in
`build_scope': undefined method `arity' for {:class_name=>"LevelMixin",
:primary_key=>"id", :foreign_key=>"parent_id", :counter_cache=>nil,
:touch=>false, :inverse_of=>:children, :optional=>true}:Hash (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.)
--
996121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-acts-as-tree
Version: 2.8.0-1.1
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, ruby-acts-as-tree 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):
> /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/associations/builder/association.rb:51:in
> `build_scope': undefined method `arity' for {:class_name=>"LevelMixin",
> :primary_key=>"id", :foreign_key=>"parent_id", :counter_cache=>nil,
> :touch=>false, :inverse_of=>:children, :optional=>true}:Hash (NoMethodError)
> from
> /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/associations/builder/association.rb:45:in
> `create_reflection'
> from
> /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/associations/builder/association.rb:30:in
> `build'
> from
> /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/associations.rb:1658:in
> `belongs_to'
> from
> /<>/debian/ruby-acts-as-tree/usr/lib/ruby/vendor_ruby/acts_as_tree.rb:93:in
> `acts_as_tree'
> from /<>/test/acts_as_tree_test.rb:86:in
> `'
> from /<>/test/acts_as_tree_test.rb:84:in `'
> from
> :85:in
> `require'
> from
> :85:in
> `require'
> from -e:1:in `block in '
> from -e:1:in `each'
> from -e:1:in `'
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-acts-as-tree/ruby-acts-as-tree_2.8.0-1.1+rebuild1633375114_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-acts-as-tree
Source-Version: 2.9.1-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-acts-as-tree, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-acts-as-tree
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, 21 Nov 2021 03:09:14 +0100
Source: ruby-acts-as-tree
Architecture: source
Version: 2.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996121
Changes:
ruby-acts-as-tree (2.9.1-1) unstable; urgency=medium
.
* Team upload.
* New upstream version.
- Provides Ruby 2.7 and Rails 6 compatibility (closes: #996121).
.
[ Debian Janitor ]
* Bump debhelper from old 11 to 13.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Update watch file format version to 4.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Massive update.
* d/rules: Use gem installation layout and check dependencies.
* d/watch: Use gemwatch URL.
* d/upstream/metadata: Add YAML syntax and Archive and
Bug#996119: marked as done (ruby-activerecord-nulldb-adapter: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Employee.create)
Your message dated Sun, 21 Nov 2021 02:36:11 + with message-id and subject line Bug#996119: fixed in ruby-activerecord-nulldb-adapter 0.8.0-1 has caused the Debian Bug report #996119, regarding ruby-activerecord-nulldb-adapter: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Employee.create 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.) -- 996119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-activerecord-nulldb-adapter Version: 0.4.0-1 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, ruby-activerecord-nulldb-adapter 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): > Failure/Error: Employee.create > > ActiveModel::MissingAttributeError: > can't write unknown attribute `id` > # > /usr/share/rubygems-integration/all/gems/activemodel-6.0.3.7/lib/active_model/attribute.rb:206:in > `with_value_from_database' > # > /usr/share/rubygems-integration/all/gems/activemodel-6.0.3.7/lib/active_model/attribute_set.rb:49:in > `write_from_user' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/attribute_methods/write.rb:43:in > `_write_attribute' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/attribute_methods/primary_key.rb:24:in > `id=' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/persistence.rb:936:in > `_create_record' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/counter_cache.rb:166:in > `_create_record' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/locking/optimistic.rb:70:in > `_create_record' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/attribute_methods/dirty.rb:211:in > `_create_record' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/callbacks.rb:331:in > `block in _create_record' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/callbacks.rb:101:in > `run_callbacks' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/callbacks.rb:825:in > `_run_create_callbacks' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/callbacks.rb:331:in > `_create_record' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/timestamp.rb:110:in > `_create_record' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/persistence.rb:905:in > `create_or_update' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/callbacks.rb:327:in > `block in create_or_update' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/callbacks.rb:135:in > `run_callbacks' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/callbacks.rb:825:in > `_run_save_callbacks' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/callbacks.rb:327:in > `create_or_update' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/timestamp.rb:128:in > `create_or_update' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/persistence.rb:470:in > `save' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/validations.rb:47:in > `save' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/transactions.rb:314:in > `block in save' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/transactions.rb:375:in > `block in with_transaction_returning_status' > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/connection_adapters/abstract/database_statements.rb:280:in > `block in transaction' > # >
Bug#984338: marked as done (slic3r-prusa: ftbfs with GCC-11)
Your message dated Sun, 21 Nov 2021 02:36:33 + with message-id and subject line Bug#984338: fixed in slic3r-prusa 2.3.3+dfsg-2 has caused the Debian Bug report #984338, regarding slic3r-prusa: 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.) -- 984338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:slic3r-prusa Version: 2.3.0+dfsg-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/slic3r-prusa_2.3.0+dfsg-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 1365 | for (const std::pair : enum_keys_map) | ^~~ /<>/src/libslic3r/Config.hpp:1365:53: note: use non-reference type ‘const std::pair, int>’ to make the copy explicit or ‘const std::pair, int>&’ to prevent copying /<>/src/libslic3r/Config.hpp: In instantiation of ‘static const t_config_enum_names& Slic3r::ConfigOptionEnum::get_enum_names() [with T = Slic3r::PrinterTechnology; Slic3r::t_config_enum_names = std::vector >]’: /<>/src/libslic3r/Config.hpp:1334:80: required from ‘std::string Slic3r::ConfigOptionEnum::serialize() const [with T = Slic3r::PrinterTechnology; std::string = std::__cxx11::basic_string]’ /<>/src/libslic3r/Config.hpp:1332:17: required from here /<>/src/libslic3r/Config.hpp:1361:53: warning: loop variable ‘kvp’ of type ‘const std::pair, int>&’ binds to a temporary constructed from type ‘const std::pair, int>’ [-Wrange-loop-construct] 1361 | for (const std::pair : enum_keys_map) | ^~~ /<>/src/libslic3r/Config.hpp:1361:53: note: use non-reference type ‘const std::pair, int>’ to make the copy explicit or ‘const std::pair, int>&’ to prevent copying /<>/src/libslic3r/Config.hpp:1365:53: warning: loop variable ‘kvp’ of type ‘const std::pair, int>&’ binds to a temporary constructed from type ‘const std::pair, int>’ [-Wrange-loop-construct] 1365 | for (const std::pair : enum_keys_map) | ^~~ /<>/src/libslic3r/Config.hpp:1365:53: note: use non-reference type ‘const std::pair, int>’ to make the copy explicit or ‘const std::pair, int>&’ to prevent copying [ 99%] Linking CXX executable prusa-slicer cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/PrusaSlicer.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fext-numeric-literals -Wall -Wno-reorder -pthread -O3 -DNDEBUG -Wl,-z,relro CMakeFiles/PrusaSlicer.dir/PrusaSlicer.cpp.o -o prusa-slicer libslic3r/liblibslic3r.a -ldl -lstdc++ slic3r/liblibslic3r_gui.a -ldl libslic3r/liblibslic3r.a libnest2d/liblibnest2d.a /usr/lib/x86_64-linux-gnu/libnlopt.so admesh/libadmesh.a miniz/libminiz_static.a /usr/lib/x86_64-linux-gnu/libboost_log.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_locale.so.1.74.0
Bug#1000287: marked as done (python-tornado FTBFS with Python 3.10)
Your message dated Sun, 21 Nov 2021 02:34:05 + with message-id and subject line Bug#1000287: fixed in python-tornado 6.1.0-2 has caused the Debian Bug report #1000287, regarding python-tornado FTBFS with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-tornado Version: 6.1.0-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/package.php?p=python-tornado ... == ERROR: test_asyncio_accessor (tornado.test.asyncio_test.AnyThreadEventLoopPolicyTest) -- Traceback (most recent call last): File "/<>/tornado/test/asyncio_test.py", line 187, in test_asyncio_accessor self.run_policy_test(asyncio.get_event_loop, asyncio.AbstractEventLoop) File "/<>/tornado/test/asyncio_test.py", line 184, in run_policy_test self.executor.submit(lambda: asyncio.get_event_loop().close()).result() # type: ignore File "/usr/lib/python3.10/concurrent/futures/_base.py", line 445, in result return self.__get_result() File "/usr/lib/python3.10/concurrent/futures/_base.py", line 390, in __get_result raise self._exception File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/<>/tornado/test/asyncio_test.py", line 184, in self.executor.submit(lambda: asyncio.get_event_loop().close()).result() # type: ignore DeprecationWarning: There is no current event loop ... --- End Message --- --- Begin Message --- Source: python-tornado Source-Version: 6.1.0-2 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-tornado, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-tornado package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Nov 2021 22:10:29 -0400 Source: python-tornado Architecture: source Version: 6.1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1000287 Changes: python-tornado (6.1.0-2) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. * Patch: Ignore known DeprecationWarnings in Python 3.10 (Closes: #1000287) . [ Debian Janitor ] * Update standards version to 4.5.1, no changes needed. Checksums-Sha1: e718f50e6101a499e0c0591d27af69e2881da4bf 1947 python-tornado_6.1.0-2.dsc a6607ed27bd838381baf991c18825905c6995ec7 9844 python-tornado_6.1.0-2.debian.tar.xz 8692cf647e641ee0a664f3144c8be582adb4efab 7406 python-tornado_6.1.0-2_source.buildinfo Checksums-Sha256: 7dde2ad2f75cf86aa7f5eb3e295d69681593bc32b75a32cf5e2683a4e87eb67f 1947 python-tornado_6.1.0-2.dsc 0483b14f4d8fc57795c43c1c43acc8ad0ef72fb05b25fd07d878e1cc647975d4 9844 python-tornado_6.1.0-2.debian.tar.xz 9c625e101207227603aad9b8369236a51bc686a8dd93f6dbf8e3229af7bca65e 7406 python-tornado_6.1.0-2_source.buildinfo Files: f982951ebaadd75c6ce4ae47c357c656 1947 web optional python-tornado_6.1.0-2.dsc e359a1156496eebcb104f3e3771c96f2 9844 web optional python-tornado_6.1.0-2.debian.tar.xz 4f71ea30a39c1f4bfa0d8afc0c4e31ef 7406 web optional python-tornado_6.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYZmqvBQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2AxzAPsEqVf68VQJSI+MfX6L39hkHxkiV/vV xHDbVtQZt2AbfAD+K4kT9HrzKy93koJZ/OhafNgnMxGvLqzoCfx0wxhoWgI= =Zbmu -END PGP SIGNATURE End Message ---
Processed: Bug#1000287 marked as pending in python-tornado
Processing control commands: > tag -1 pending Bug #1000287 [src:python-tornado] python-tornado FTBFS with Python 3.10 Added tag(s) pending. -- 1000287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000287: marked as pending in python-tornado
Control: tag -1 pending Hello, Bug #1000287 in python-tornado reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-tornado/-/commit/ac00f18d061cf0cbb0abf9b1fb53456302d3cdde Patch: Ignore known DeprecationWarnings in Python 3.10 (Closes: #1000287) (this message was generated automatically) -- Greetings https://bugs.debian.org/1000287
Bug#996119: marked as pending in ruby-activerecord-nulldb-adapter
Control: tag -1 pending
Hello,
Bug #996119 in ruby-activerecord-nulldb-adapter reported by you has been fixed
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ruby-team/ruby-activerecord-nulldb-adapter/-/commit/e15ee7c2458c63f5d4d7bcba737f94868ea7e1c0
Update packaging files
* d/control (Standards-Version): Bump to 4.6.0.
(Build-Depends): Bump to ruby-activerecord >= 2:6.1 (closes: #996119).
(Depends): Add ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/rules: Use gem installation layout and install changelog.
* d/upstream/metadata: Add Archive and Changelog fields.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996119
Processed: Bug#996119 marked as pending in ruby-activerecord-nulldb-adapter
Processing control commands: > tag -1 pending Bug #996119 [src:ruby-activerecord-nulldb-adapter] ruby-activerecord-nulldb-adapter: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Employee.create Added tag(s) pending. -- 996119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: user reproducible-bui...@lists.alioth.debian.org, usertagging 997541, tagging 997541
Processing commands for cont...@bugs.debian.org: > user reproducible-bui...@lists.alioth.debian.org Setting user to reproducible-bui...@lists.alioth.debian.org (was p...@debian.org). > usertags 997541 - patch Usertags were: ftbfs patch. Usertags are now: ftbfs. > tags 997541 + patch Bug #997541 [src:oldsys-preseed] oldsys-preseed: FTBFS: Running test misc/hostname... ./do-test: line 17: tempfile: command not found Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 997541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000265: marked as done (typo in fix for CVE-2021-21996 breaks file.managed on stretch)
Your message dated Sun, 21 Nov 2021 01:41:47 +0100 with message-id <7f29ec6be4db55571badb591100056bedd73cd2a.ca...@debian.org> and subject line Re: typo in fix for CVE-2021-21996 breaks file.managed on stretch has caused the Debian Bug report #1000265, regarding typo in fix for CVE-2021-21996 breaks file.managed on stretch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: salt-common Version: 2016.11.2+ds-1+deb9u8 Severity: grave The patch for 994016 in the /usr/lib/python2.7/dist-packages/salt/fileclient.py file included: +# clean_path returns an empty string if the check fails +root_path = salt.utils.path.join(cachedir, "extrn_files", saltenv, netloc) which might work for newer versions of salt, but in stretch that has to be salt.utils.path_join(...) as the salt.utils.path module didn't exist yet. As-is, the security update for CVE-2021-21996 makes file.managed states fail with: Unable to manage file: 'module' object has no attribute 'path' which makes salt on stretch pretty much unusable. -- Jamie Heilman http://audible.transient.net/~jamie/ --- End Message --- --- Begin Message --- Version: 2016.11.2+ds-1+deb9u9 signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#997496: marked as done (typer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sun, 21 Nov 2021 00:34:52 +
with message-id
and subject line Bug#997496: fixed in typer 0.4.0-1
has caused the Debian Bug report #997496,
regarding typer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: typer
Version: 0.3.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> === short test summary info
>
> FAILED tests/test_prog_name.py::test_custom_prog_name
> ERROR docs_src/testing/app01/test_main.py
> ERROR docs_src/testing/app02/test_main.py
> ERROR docs_src/testing/app03/test_main.py
> ERROR tests/test_others.py
> ERROR tests/test_completion/test_completion.py
> ERROR tests/test_completion/test_completion_complete.py
> ERROR tests/test_completion/test_completion_complete_no_help.py
> ERROR tests/test_completion/test_completion_install.py
> ERROR tests/test_completion/test_completion_show.py
> ERROR tests/test_tutorial/test_arguments/test_default/test_tutorial001.py
> ERROR tests/test_tutorial/test_arguments/test_default/test_tutorial002.py
> ERROR tests/test_tutorial/test_arguments/test_envvar/test_tutorial001.py
> ERROR tests/test_tutorial/test_arguments/test_envvar/test_tutorial002.py
> ERROR tests/test_tutorial/test_arguments/test_envvar/test_tutorial003.py
> ERROR tests/test_tutorial/test_arguments/test_help/test_tutorial001.py
> ERROR tests/test_tutorial/test_arguments/test_help/test_tutorial002.py
> ERROR tests/test_tutorial/test_arguments/test_help/test_tutorial003.py
> ERROR tests/test_tutorial/test_arguments/test_help/test_tutorial004.py
> ERROR tests/test_tutorial/test_arguments/test_help/test_tutorial005.py
> ERROR tests/test_tutorial/test_arguments/test_help/test_tutorial006.py
> ERROR tests/test_tutorial/test_arguments/test_help/test_tutorial007.py
> ERROR tests/test_tutorial/test_arguments/test_optional/test_tutorial001.py
> ERROR tests/test_tutorial/test_arguments/test_optional/test_tutorial002.py
> ERROR tests/test_tutorial/test_commands/test_arguments/test_tutorial001.py
> ERROR tests/test_tutorial/test_commands/test_callback/test_tutorial001.py
> ERROR tests/test_tutorial/test_commands/test_callback/test_tutorial002.py
> ERROR tests/test_tutorial/test_commands/test_callback/test_tutorial003.py
> ERROR tests/test_tutorial/test_commands/test_callback/test_tutorial004.py
> ERROR tests/test_tutorial/test_commands/test_context/test_tutorial001.py
> ERROR tests/test_tutorial/test_commands/test_context/test_tutorial002.py
> ERROR tests/test_tutorial/test_commands/test_context/test_tutorial003.py
> ERROR tests/test_tutorial/test_commands/test_context/test_tutorial004.py
> ERROR tests/test_tutorial/test_commands/test_help/test_tutorial001.py
> ERROR tests/test_tutorial/test_commands/test_help/test_tutorial002.py
> ERROR tests/test_tutorial/test_commands/test_index/test_tutorial001.py
> ERROR tests/test_tutorial/test_commands/test_index/test_tutorial002.py
> ERROR tests/test_tutorial/test_commands/test_name/test_tutorial001.py
> ERROR
> tests/test_tutorial/test_commands/test_one_or_multiple/test_tutorial001.py
> ERROR
> tests/test_tutorial/test_commands/test_one_or_multiple/test_tutorial002.py
> ERROR tests/test_tutorial/test_commands/test_options/test_tutorial001.py
> ERROR tests/test_tutorial/test_first_steps/test_tutorial001.py
> ERROR tests/test_tutorial/test_first_steps/test_tutorial002.py
> ERROR tests/test_tutorial/test_first_steps/test_tutorial003.py
> ERROR tests/test_tutorial/test_first_steps/test_tutorial004.py
> ERROR tests/test_tutorial/test_first_steps/test_tutorial005.py
> ERROR tests/test_tutorial/test_first_steps/test_tutorial006.py
> ERROR
> tests/test_tutorial/test_multiple_values/test_arguments_with_multiple_values/test_tutorial001.py
> ERROR
> tests/test_tutorial/test_multiple_values/test_arguments_with_multiple_values/test_tutorial002.py
> ERROR
> tests/test_tutorial/test_multiple_values/test_multiple_options/test_tutorial001.py
> ERROR
> tests/test_tutorial/test_multiple_values/test_multiple_options/test_tutorial002.py
> ERROR
> tests/test_tutorial/test_multiple_values/test_options_with_multiple_values/test_tutorial001.py
> ERROR
Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1
Package: jackd2 Version: 1.9.19~dfsg-2 Severity: grave X-Debbugs-Cc: it9...@gmail.com Apparently there is something wrong with Jack and dbus. Also reported here: https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ Find below the jack server logs. 00:41:32.228 Resetta le statistiche. 00:41:32.269 Connessioni di ALSA cambiate. 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = File o directory non esistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace Sun Nov 21 00:41:47 2021: Starting jack server... Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with priority 10 Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self connect requests" Cannot connect to server socket err = File o directory non esistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock Sun Nov 21 00:41:47 2021: Device reservation request with priority 2147483647 denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1) Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 error : Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1 Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be acquired... Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 Sun Nov 21 00:41:47 2021: ERROR: Failed to open server Sun Nov 21 00:41:48 2021: Saving settings to "/home/it9exm/.config/jack/conf.xml" ... 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione fallita. - Impossibile connettersi al server JACK. Controlla la finestra dei messaggi per maggiori informazioni. Cannot connect to server socket err = File o directory non esistente Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 jackd2 depends on: ii debconf [debconf-2.0] 1.5.79 ii libasound2 1.2.5.1-1 ii libc6 2.32-4 ii libdbus-1-31.12.20-3 ii libexpat1 2.4.1-3 ii libgcc-s1 11.2.0-10 ii libjack-jackd2-0 1.9.19~dfsg-2 ii libreadline8 8.1-2 ii libsamplerate0 0.2.2-1 ii libsndfile11.0.31-2 ii libstdc++6 11.2.0-10 ii libsystemd0249.6-2 ii libzita-alsa-pcmi0 0.3.2-2 ii libzita-resampler1 1.8.0-2 ii python33.9.8-1 ii python3-dbus 1.2.18-3 Versions of packages jackd2 recommends: ii jackd2-firewire 1.9.19~dfsg-2 ii libpam-modules 1.4.0-10 ii qjackctl 0.9.5-1 Versions of packages jackd2 suggests: pn jack-tools pn meterbridge -- debconf information: * jackd/tweak_rt_limits: true
Bug#996780: gnome-boxes: Systematic system freeze few seconds after launching a Windows WM
Are you possibly using a NVIDIA driver? Asking because of this: https://github.com/NVIDIA/egl-wayland/issues/27#issuecomment-951725683 -- Cheers, Gunnar Hjalmarsson
Bug#998108: reopening 998108
On Sat, 2021-11-20 at 15:30 -0800, Josh Triplett wrote: > I'm still experiencing this bug regularly, with complete browser UI > freezes that require killing and restarting Firefox. Hm perhaps something else? At least I haven't suffered from that particular issue since 94.0-2. Cheers, Chris.
Bug#998108: reopening 998108
reopen 998108 94.0-2 thanks I'm still experiencing this bug regularly, with complete browser UI freezes that require killing and restarting Firefox. WebGL or video seems to trigger it more often, as does opening a new tab. Browsing on an existing tab doesn't tend to trigger it.
Bug#1000292: pyhst2: FTBFS against Python 3.10
Source: pyhst2
Version: 2020c-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
2020c-3 FTBFS since Python 3.10 got added as a supported version:
[
creating build
creating build/temp.linux-x86_64-3.10
creating build/temp.linux-x86_64-3.10/PyHST
creating build/temp.linux-x86_64-3.10/PyHST/Cspace
compile options: '-I/usr/include
-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/openmpi/
-I/usr/include/hdf5/serial/ -I/usr/include/python3.10 -c'
extra options: 'gcc'
EXTRA {'gcc': ['-fPIC', '-fopenmp', '-g', '-std=c99', '-Wall']}
mpicc: PyHST/Cspace/CCspace.c
EXTRA {'gcc': ['-fPIC', '-fopenmp', '-g', '-std=c99', '-Wall']}
mpicc: PyHST/Cspace/Cspace.c
EXTRA {'gcc': ['-fPIC', '-fopenmp', '-g', '-std=c99', '-Wall']}
mpicc: PyHST/Cspace/cpyutils.c
EXTRA {'gcc': ['-fPIC', '-fopenmp', '-g', '-std=c99', '-Wall']}
mpicc: PyHST/Cspace/pyhst_nnfbp.c
EXTRA {'gcc': ['-fPIC', '-fopenmp', '-g', '-std=c99', '-Wall']}
mpicc: PyHST/Cspace/edftools.c
EXTRA {'gcc': ['-fPIC', '-fopenmp', '-g', '-std=c99', '-Wall']}
mpicc: PyHST/Cspace/cpu_main.c
PyHST/Cspace/Cspace.c:33:9: fatal error: Python.h: No such file or directory
33 | #include"Python.h"
| ^~
compilation terminated.
PyHST/Cspace/cpyutils.c:33:9: fatal error: Python.h: No such file or directory
33 | #include"Python.h"
| ^~
compilation terminated.
[...]
Andreas
pyhst2.sid.build.gz
Description: application/gzip
Processed: tagging 1000263, fixed 982737 in 0.3.1-1, fixed 979170 in 2.31.1-1, fixed 981574 in 1.1.90-1 ...
Processing commands for cont...@bugs.debian.org:
> tags 1000263 + sid bookworm
Bug #1000263 [tt-rss] package broken after php8 upgrade
Added tag(s) sid and bookworm.
> fixed 982737 0.3.1-1
Bug #982737 {Done: Sebastien Bacher } [src:gnome-autoar]
gnome-autoar: CVE-2020-36241
Marked as fixed in versions gnome-autoar/0.3.1-1.
> fixed 979170 2.31.1-1
Bug #979170 {Done: Alberto Garcia } [src:webkit2gtk]
webkit2gtk: please reduce Build-Depends
Marked as fixed in versions webkit2gtk/2.31.1-1.
> fixed 981574 1.1.90-1
Bug #981574 {Done: Arnaud Ferraris } [libhandy-1]
Wrong screen resolution selected in gnome-control-center
There is no source info for the package 'libhandy-1' at version '1.1.90-1' with
architecture ''
Unable to make a source version for version '1.1.90-1'
Marked as fixed in versions 1.1.90-1.
> fixed 941294 3.31.90-1
Bug #941294 {Done: Simon McVittie } [gnome-sound-recorder]
gnome-sound-recorder: Gnome-sound-recorder crashes when tab or shift+tab is
pressed twice
Marked as fixed in versions gnome-sound-recorder/3.31.90-1.
> notfound 881879 201.3-1
Bug #881879 {Done: Jonas Smedegaard } [sugar-browse-activity]
sugar-browse-activity: does not start, missing collabwrapper
No longer marked as found in versions sugar-browse-activity/201.3-1.
> fixed 954955 4.0.3-1
Bug #954955 {Done: =?utf-8?q?David_Pr=C3=A9vot?= }
[phpunit-comparator] phpunit-comparator: FTBFS from test failure due to warning
about typo in test case
Marked as fixed in versions phpunit-comparator/4.0.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000263
881879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881879
941294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941294
954955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954955
979170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979170
981574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981574
982737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000265: typo in fix for CVE-2021-21996 breaks file.managed on stretch
On Sat, 20 Nov 2021 16:46:34 + Jamie Heilman wrote: > Package: salt-common > Version: 2016.11.2+ds-1+deb9u8 > Severity: grave > > The patch for 994016 in the > /usr/lib/python2.7/dist-packages/salt/fileclient.py file included: > > + # clean_path returns an empty string if the check fails > + root_path = salt.utils.path.join(cachedir, "extrn_files", saltenv, netloc) > > which might work for newer versions of salt, but in stretch that has > to be salt.utils.path_join(...) as the salt.utils.path module didn't > exist yet. As-is, the security update for CVE-2021-21996 makes > file.managed states fail with: > > Unable to manage file: 'module' object has no attribute 'path' > > which makes salt on stretch pretty much unusable. Thanks for the report. I wonder why the tests didn't catch that problem. I will address this with the next upload of salt. Regards, Markus signature.asc Description: This is a digitally signed message part
Bug#999904: marked as done (Uncoordinated split of debugedit package out of src:rpm)
Your message dated Sun, 21 Nov 2021 00:22:57 +0200 with message-id and subject line Re: Bug#04: Uncoordinated split of debugedit package out of src:rpm has caused the Debian Bug report #04, regarding Uncoordinated split of debugedit package out of src:rpm 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.) -- 04: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=04 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debugedit,rpm Severity: serious Tags: sid bookworm Hello, debugedit has been split out of the src:rpm package, but src:rpm is still building the package as well. In addition to that, rpm package has a strong versioned dependency against debugedit (debugedit (= 4.16.1.2+dfsg1-3)) which means that rpm cannot be installed anymore. We need to keep this package out of testing until this is resolved Kind regards, Laurent Bigonville -- 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.14.0-4-amd64 (SMP w/8 CPU threads) 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 --- End Message --- --- Begin Message --- Version: 4.17.0+dfsg1-1 On Sun, Nov 21, 2021 at 12:22:10AM +0200, Peter Pentchev wrote: > Version: 4.17.0+dfsg1-1 > > On Thu, Nov 18, 2021 at 12:19:10PM +0200, Peter Pentchev wrote: > > control: tag -1 + confirmed pending > > > > On Thu, Nov 18, 2021 at 09:45:06AM +0100, Laurent Bigonville wrote: > > > Source: debugedit,rpm > > > Severity: serious > > > Tags: sid bookworm > > > > > > Hello, > > > > > > debugedit has been split out of the src:rpm package, but src:rpm is > > > still building the package as well. > > > > > > In addition to that, rpm package has a strong versioned dependency > > > against debugedit (debugedit (= 4.16.1.2+dfsg1-3)) which means that rpm > > > cannot be installed anymore. > > > > > > We need to keep this package out of testing until this is resolved > > > > FTR, it has not been completely uncoordinated, there is an ongoing > > discussion on the RPM packaging team's mailing list where Matthias > > asked about our plans to upgrade rpm to 4.17 and I confirmed that > > there is work in progress and it will most probably be done in > > the next couple of days. > > > > Still, thanks for filing this bug for the purpose of keeping the new > > version of debugedit out of testing for the present. > > Right, and of course I forgot to close this bug in the 4.17.0+dfsg1-1 > changelog entry. > > Thanks again for filing it! I am asleep, am I not... I did mean to send this to -done, honest! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature --- End Message ---
Bug#999904: Uncoordinated split of debugedit package out of src:rpm
Version: 4.17.0+dfsg1-1 On Thu, Nov 18, 2021 at 12:19:10PM +0200, Peter Pentchev wrote: > control: tag -1 + confirmed pending > > On Thu, Nov 18, 2021 at 09:45:06AM +0100, Laurent Bigonville wrote: > > Source: debugedit,rpm > > Severity: serious > > Tags: sid bookworm > > > > Hello, > > > > debugedit has been split out of the src:rpm package, but src:rpm is > > still building the package as well. > > > > In addition to that, rpm package has a strong versioned dependency > > against debugedit (debugedit (= 4.16.1.2+dfsg1-3)) which means that rpm > > cannot be installed anymore. > > > > We need to keep this package out of testing until this is resolved > > FTR, it has not been completely uncoordinated, there is an ongoing > discussion on the RPM packaging team's mailing list where Matthias > asked about our plans to upgrade rpm to 4.17 and I confirmed that > there is work in progress and it will most probably be done in > the next couple of days. > > Still, thanks for filing this bug for the purpose of keeping the new > version of debugedit out of testing for the present. Right, and of course I forgot to close this bug in the 4.17.0+dfsg1-1 changelog entry. Thanks again for filing it! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#1000210: [regression] uscan die: filenamemangle failed
OK, let's do that -- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
Bug#1000210: [regression] uscan die: filenamemangle failed
This is not the problem here really. It's the different matching base. Together with the previous versification I also verified that such filenamemangle (like systemd's) don't match anymore. That's equally problematic (if not more!) than the program exiting with an error. I can agree however you want that it's a bad design, but that has been the specification since the start and it can't change without a format bump. I plan to revert Hugh's commit in the next days to solve this, reopening the previous bug and pending a better fix. On Sat, 20 Nov 2021, 11:02 pm Yadd, wrote: > Le 20/11/2021 à 13:36, Mattia Rizzolo a écrit : > > On Sat, Nov 20, 2021 at 01:14:23PM +0100, Yadd wrote: > >> Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : > >>> So, effectively, the change broke the specification. > >> > >> It looks like the specification was not good. A filename isn't an URL > > > > Be that as it may, we can't break something like that without a version > > bump, IMHO. > > > > So we need a different fix for #993585. > > > > Either way, I think it's unrelated to your discovery that it could > > potentially overwrite a file, isn't it? > > We could perhaps just warn for now on bad filenamemangle >
Bug#987468: marked as done (rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev)
Your message dated Sat, 20 Nov 2021 22:07:06 + with message-id and subject line Bug#999816: fixed in rpm 4.17.0+dfsg1-1 has caused the Debian Bug report #999816, regarding rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev 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.) -- 999816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rpm Version: 4.16.1.2+dfsg1-0.6 Severity: important Tags: sid bookworm User: selinux-de...@lists.alioth.debian.org Usertags: selinux Hello, src:rpm build-depends against libsepol1-dev and libsemanage1-dev but this seems useless, only libselinux1-dev is actually needed. Both libsepol and libsemanage bumps their soname in the upcoming release and that will require a sourceful upload of rpm anyway. Kind regards, Laurent Bigonville -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN 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 --- End Message --- --- Begin Message --- Source: rpm Source-Version: 4.17.0+dfsg1-1 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of rpm, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated rpm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Nov 2021 23:45:50 +0200 Source: rpm Architecture: source Version: 4.17.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: RPM packaging team Changed-By: Peter Pentchev Closes: 915849 999816 Changes: rpm (4.17.0+dfsg1-1) unstable; urgency=medium . [ Peter Pentchev ] * Team upload. * Switch the build dependency to the unversioned libsepol-dev and libsemanage-dev, since libsepol1-dev and libsemanage1-dev are now gone. Closes: #999816 * Add the usr-bin patch to fix the rpm.daily script. * Teach the watch file about ftp.osuosl.org. * Bump the watch file format version to 4 with no changes. * Declare compliance with Debian Policy 4.6.0 with no changes. * Add Build-Depends-Package to the symbols files. * Drop the --as-needed flag, it is on by default now. * Add Rules-Requires-Root: no to the source control stanza. * Update Michal Čihař's debian/* copyright notice. * Add copyright notices for myself and Matthias Klose. * Rename manpage-has-errors-from-man to groff-message. * Drop some obsolete Lintian overrides. * Drop some trailing whitespace in a package description. * Add an autopkgtest for rpm and rpmbuild. * Bump the debhelper compat level to 13 and drop the dh_missing invocation with the --fail-missing option, this is the default now. * Use execute_after_* debhelper targets. * Use debian/clean instead of a rules file target. * Explicitly pass the paths to some tools to fix mismatches between packages built on usrmerged vs. non-usrmerged systems. Closes: #915849 * New upstream version: - drop the CVE-2021-3421-CVE-2021-20271 and CVE-2021-20266 patches, they were taken from upstream - update the Lua build dependency to version 5.3 - drop the 0012-pythondistdeps.py-Use-python3-in-shebang patch, the Python tools were moved to a separate source package - drop the debugedit-trunk and gcc-dwarf5 patches, debugedit was moved to a separate source package - drop the hide-symbols patch, it was accepted upstream - do not install the fileattrs, brp-python*, and pythondistdeps tools, they were moved to a separate source package - update the list of tools that we do not let the configure script
Bug#999816: marked as done (rpm - build-depends on removed package.)
Your message dated Sat, 20 Nov 2021 22:07:06 + with message-id and subject line Bug#999816: fixed in rpm 4.17.0+dfsg1-1 has caused the Debian Bug report #999816, regarding rpm - build-depends on removed package. 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.) -- 999816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rpm Version: 4.16.1.2+dfsg1-3 Tags: bookworm, sid Severity: serious rpm build-depends on libsepol1-dev which is no longer built by the libsepol source package. The package is completely gone from testing, in unstable it is still present as a cruft package, but is not usable for building cryptsetup because the current version of libselinux1-dev conflicts with it. I suspect (but have not tested) that you need to change your build-dependency to libsepol-dev. --- End Message --- --- Begin Message --- Source: rpm Source-Version: 4.17.0+dfsg1-1 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of rpm, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated rpm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Nov 2021 23:45:50 +0200 Source: rpm Architecture: source Version: 4.17.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: RPM packaging team Changed-By: Peter Pentchev Closes: 915849 999816 Changes: rpm (4.17.0+dfsg1-1) unstable; urgency=medium . [ Peter Pentchev ] * Team upload. * Switch the build dependency to the unversioned libsepol-dev and libsemanage-dev, since libsepol1-dev and libsemanage1-dev are now gone. Closes: #999816 * Add the usr-bin patch to fix the rpm.daily script. * Teach the watch file about ftp.osuosl.org. * Bump the watch file format version to 4 with no changes. * Declare compliance with Debian Policy 4.6.0 with no changes. * Add Build-Depends-Package to the symbols files. * Drop the --as-needed flag, it is on by default now. * Add Rules-Requires-Root: no to the source control stanza. * Update Michal Čihař's debian/* copyright notice. * Add copyright notices for myself and Matthias Klose. * Rename manpage-has-errors-from-man to groff-message. * Drop some obsolete Lintian overrides. * Drop some trailing whitespace in a package description. * Add an autopkgtest for rpm and rpmbuild. * Bump the debhelper compat level to 13 and drop the dh_missing invocation with the --fail-missing option, this is the default now. * Use execute_after_* debhelper targets. * Use debian/clean instead of a rules file target. * Explicitly pass the paths to some tools to fix mismatches between packages built on usrmerged vs. non-usrmerged systems. Closes: #915849 * New upstream version: - drop the CVE-2021-3421-CVE-2021-20271 and CVE-2021-20266 patches, they were taken from upstream - update the Lua build dependency to version 5.3 - drop the 0012-pythondistdeps.py-Use-python3-in-shebang patch, the Python tools were moved to a separate source package - drop the debugedit-trunk and gcc-dwarf5 patches, debugedit was moved to a separate source package - drop the hide-symbols patch, it was accepted upstream - do not install the fileattrs, brp-python*, and pythondistdeps tools, they were moved to a separate source package - update the list of tools that we do not let the configure script autodetect for usrmerge-related reasons - drop the debugedit binary package and its associated files, it has moved to a separate source package - reflect the doc/ -> docs/ move in debian/rpm.docs, too - override three source-is-missing Lintian warnings for some test suite files; the sources are in another directory - update the library symbols files, dropping several obsolete functions from a mostly internal-use library; no packages in the Debian archive reference the dropped symbols -
Bug#984120: marked as done (fcoe-utils: ftbfs with GCC-11)
Your message dated Sat, 20 Nov 2021 22:03:40 + with message-id and subject line Bug#984120: fixed in fcoe-utils 1.0.34-1 has caused the Debian Bug report #984120, regarding fcoe-utils: 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.) -- 984120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fcoe-utils Version: 1.0.33+git20200925.848bcc6-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/fcoe-utils_1.0.33+git20200925.848bcc6-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports the include directive... yes (GNU style) checking whether make supports nested variables... yes checking dependency style of gcc... none checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking for ranlib... ranlib checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for lldpad >= 0.9.46... yes checking for pciaccess... yes checking for pkg-config... (cached) /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating fcoe-utils.spec config.status: creating include/fcoe_utils_version.h config.status: executing depfiles commands make[1]: Leaving directory '/<>' dh_auto_build make -j4 make[1]: Entering directory '/<>' gcc -DPACKAGE_NAME=\"fcoe-utils\" -DPACKAGE_TARNAME=\"fcoe-utils\" -DPACKAGE_VERSION=\"1.0.33\" -DPACKAGE_STRING=\"fcoe-utils\ 1.0.33\" -DPACKAGE_BUGREPORT=\"fcoe-de...@open-fcoe.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"fcoe-utils\" -DVERSION=\"1.0.33\" -I. -I./include -I./include -DSYSCONFDIR="\"/etc\"" -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wformat=2 -Werror -Wextra -Wmissing-prototypes -Wstrict-prototypes -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o fcoeadm-fcoeadm.o `test -f 'fcoeadm.c' || echo './'`fcoeadm.c gcc -DPACKAGE_NAME=\"fcoe-utils\" -DPACKAGE_TARNAME=\"fcoe-utils\" -DPACKAGE_VERSION=\"1.0.33\" -DPACKAGE_STRING=\"fcoe-utils\ 1.0.33\" -DPACKAGE_BUGREPORT=\"fcoe-de...@open-fcoe.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"fcoe-utils\" -DVERSION=\"1.0.33\" -I. -I./include -I./include -DSYSCONFDIR="\"/etc\"" -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wformat=2 -Werror -Wextra -Wmissing-prototypes -Wstrict-prototypes -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o fcoeadm-fcoeadm_display.o `test -f 'fcoeadm_display.c' || echo './'`fcoeadm_display.c gcc -DPACKAGE_NAME=\"fcoe-utils\"
Bug#1000210: [regression] uscan die: filenamemangle failed
Le 20/11/2021 à 13:36, Mattia Rizzolo a écrit : > On Sat, Nov 20, 2021 at 01:14:23PM +0100, Yadd wrote: >> Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : >>> So, effectively, the change broke the specification. >> >> It looks like the specification was not good. A filename isn't an URL > > Be that as it may, we can't break something like that without a version > bump, IMHO. > > So we need a different fix for #993585. > > Either way, I think it's unrelated to your discovery that it could > potentially overwrite a file, isn't it? We could perhaps just warn for now on bad filenamemangle
Bug#917829: marked as done (python-intbitset: FTBFS when built with dpkg-buildpackage -A)
Your message dated Sat, 20 Nov 2021 21:54:07 +
with message-id
and subject line Bug#917829: fixed in python-intbitset 2.3.0-3.2
has caused the Debian Bug report #917829,
regarding python-intbitset: FTBFS when built with dpkg-buildpackage -A
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.)
--
917829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-intbitset
Version: 2.3.0-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster with dpkg-buildpackage -A but it failed:
[...]
debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config
running config
I: pybuild base:217: python3.7 setup.py config
running config
debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
python3 setup.py build_sphinx
running build_sphinx
creating /<>/docs/_build
[... snipped ...]
curexc_value
intbitset/intbitset.c:14775:22: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_traceback'; did you mean 'curexc_traceback'?
tmp_tb = tstate->exc_traceback;
^
curexc_traceback
intbitset/intbitset.c:14776:13: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_type'; did you mean 'curexc_type'?
tstate->exc_type = type;
^~~~
curexc_type
intbitset/intbitset.c:14777:13: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_value'; did you mean 'curexc_value'?
tstate->exc_value = value;
^
curexc_value
intbitset/intbitset.c:14778:13: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_traceback'; did you mean 'curexc_traceback'?
tstate->exc_traceback = tb;
^
curexc_traceback
intbitset/intbitset.c: In function '__Pyx__GetException':
intbitset/intbitset.c:14833:24: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_type'; did you mean 'curexc_type'?
tmp_type = tstate->exc_type;
^~~~
curexc_type
intbitset/intbitset.c:14834:25: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_value'; did you mean 'curexc_value'?
tmp_value = tstate->exc_value;
^
curexc_value
intbitset/intbitset.c:14835:22: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_traceback'; did you mean 'curexc_traceback'?
tmp_tb = tstate->exc_traceback;
^
curexc_traceback
intbitset/intbitset.c:14836:13: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_type'; did you mean 'curexc_type'?
tstate->exc_type = local_type;
^~~~
curexc_type
intbitset/intbitset.c:14837:13: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_value'; did you mean 'curexc_value'?
tstate->exc_value = local_value;
^
curexc_value
intbitset/intbitset.c:14838:13: error: 'PyThreadState' {aka 'struct _ts'} has
no member named 'exc_traceback'; did you mean 'curexc_traceback'?
tstate->exc_traceback = local_tb;
^
curexc_traceback
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: install: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py install --root /<>/debian/tmp
dh_auto_install: pybuild --install --test-nose -i python{version} -p 3.7
--dest-dir /<>/debian/tmp returned exit code 13
make: *** [debian/rules:4: binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
This used to work ok 257 days ago according to buildd.debian.org, but not
anymore.
Everything I know is that "dpkg-buildpackage -A" fails while plain
"dpkg-buildpackage" works.
In case it helps, this stopped working in buster sometime between 2018-12-11
and 2018-12-23
I would try splitting dh_auto_install into dh_auto_install-arch and
Bug#997135: marked as done (abydos: FTBFS: You must configure the bibtex_bibfiles setting)
Your message dated Sat, 20 Nov 2021 21:48:46 + with message-id and subject line Bug#997135: fixed in abydos 0.5.0+git20201231.344346a-4 has caused the Debian Bug report #997135, regarding abydos: FTBFS: You must configure the bibtex_bibfiles setting 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.) -- 997135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abydos Version: 0.5.0+git20201231.344346a-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/docs' > sphinx-build -b html -d _build/doctrees -D latex_elements.papersize=letter . > _build/html > Running Sphinx v4.2.0 > loading translations [en]... done > making output directory... done > > Extension error: > You must configure the bibtex_bibfiles setting > make[2]: *** [Makefile:55: html] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/abydos_0.5.0+git20201231.344346a-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: abydos Source-Version: 0.5.0+git20201231.344346a-4 Done: Julian Gilbey We believe that the bug you reported is fixed in the latest version of abydos, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey (supplier of updated abydos 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, 20 Nov 2021 19:11:06 + Source: abydos Architecture: source Version: 0.5.0+git20201231.344346a-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Julian Gilbey Closes: 987180 997135 Changes: abydos (0.5.0+git20201231.344346a-4) unstable; urgency=medium . [ Julian Gilbey ] * Remove Otto from uploaders * Remove PDF from documentation package as unnecessary bloat; this incidentally closes a bug (Closes: #997135) * d/watch: fix package name * Add autopkgtest * Update remote/local MathJax handling for new version of Sphinx . [ Diego M. Rodriguez ] * d/control: update homepage and add metadata (Closes: #987180) Checksums-Sha1: fe163048d8522256ddb04a2c5f9cc16c1f310eca 2491 abydos_0.5.0+git20201231.344346a-4.dsc ba1cc5c361d804e7b625b58729f2e0f03a67d9f5 5568 abydos_0.5.0+git20201231.344346a-4.debian.tar.xz 269729adbd48f0d789dc5aa7487d10953f5fb417 8703 abydos_0.5.0+git20201231.344346a-4_amd64.buildinfo Checksums-Sha256: d0a08723457d1f9dfd6ccafbc6b283793f5d01d3a5864dc85c883700af9e6827 2491 abydos_0.5.0+git20201231.344346a-4.dsc b3abdbdbd4eaa43cab98da7534804c4707700489ccdf004368b14b878e79ca3b 5568 abydos_0.5.0+git20201231.344346a-4.debian.tar.xz 75e041ce8fd37d0b0af06fdc470f1d5421bb56929d6a8b84b55b06fd2fd5f29f 8703 abydos_0.5.0+git20201231.344346a-4_amd64.buildinfo Files: 7d85b5a3af522d488f60d36cf3fe00c9 2491 python optional abydos_0.5.0+git20201231.344346a-4.dsc 42d4ee32b818ecf36386266d356cfee3 5568 python optional abydos_0.5.0+git20201231.344346a-4.debian.tar.xz b5d2bf0e293ef97f4c18ef24fe09c1de 8703 python optional abydos_0.5.0+git20201231.344346a-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmGZZloPHGpkZ0BkZWJp YW4ub3JnAAoJEGlcQpMWwHv++r0QAJcv7KQPhZgwY1YA9QFJ1atb+hjVxzc3akD8 eSdhPyzL0tEl9HLNuOAJs6P7xr3ETJfScqnAZu4QYBAvCHZbzPf2qH6NBOG2BHJk vqAkNAq+GWa9r3o5bbVy2c4czU0RH/JT4OwmY2LZ5KRCXI1cCslnHI+jk9QzlH8J 5wUu0ExC1KBa6dkoTcgIszYH4uLLEQc/YkQMgcFJtaihc8XcQnzaIjqNAIk812vB zSIEw7Odg+6IbgtX8puGWRBzqmkStxO9/iUvJUFMV0HLxjnaL5oz/+iFRJEgYLTP
Bug#1000287: python-tornado FTBFS with Python 3.10
Source: python-tornado Version: 6.1.0-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/package.php?p=python-tornado ... == ERROR: test_asyncio_accessor (tornado.test.asyncio_test.AnyThreadEventLoopPolicyTest) -- Traceback (most recent call last): File "/<>/tornado/test/asyncio_test.py", line 187, in test_asyncio_accessor self.run_policy_test(asyncio.get_event_loop, asyncio.AbstractEventLoop) File "/<>/tornado/test/asyncio_test.py", line 184, in run_policy_test self.executor.submit(lambda: asyncio.get_event_loop().close()).result() # type: ignore File "/usr/lib/python3.10/concurrent/futures/_base.py", line 445, in result return self.__get_result() File "/usr/lib/python3.10/concurrent/futures/_base.py", line 390, in __get_result raise self._exception File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/<>/tornado/test/asyncio_test.py", line 184, in self.executor.submit(lambda: asyncio.get_event_loop().close()).result() # type: ignore DeprecationWarning: There is no current event loop ...
Bug#999398: marked as done (zodbpickle ftbfs with Python 3.10 (test failures))
Your message dated Sat, 20 Nov 2021 20:47:08 + with message-id and subject line Bug#999398: fixed in zodbpickle 2.2.0-1 has caused the Debian Bug report #999398, regarding zodbpickle ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zodbpickle Version: 1.0-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 zodbpickle ftbfs with python3-defaults from experimental: [...] I: pybuild base:237: python3.10 setup.py test running test WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. running egg_info writing src/zodbpickle.egg-info/PKG-INFO writing dependency_links to src/zodbpickle.egg-info/dependency_links.txt writing requirements to src/zodbpickle.egg-info/requires.txt writing top-level names to src/zodbpickle.egg-info/top_level.txt reading manifest file 'src/zodbpickle.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.dll' found anywhere in distribution warning: no previously-included files matching '*.pyc' found anywhere in distribution warning: no previously-included files matching '*.pyo' found anywhere in distribution warning: no previously-included files matching '*.so' found anywhere in distribution adding license file 'LICENSE.txt' writing manifest file 'src/zodbpickle.egg-info/SOURCES.txt' running build_ext copying /<>/.pybuild/cpython3_3.10_zodbpickle/build/zodbpickle/_pickle.cpython-310-x86_64-linux-gnu.so -> src/zodbpickle Traceback (most recent call last): File "/<>/setup.py", line 43, in setup( File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 153, in setup return distutils.core.setup(**attrs) File "/usr/lib/python3.10/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib/python3.10/distutils/dist.py", line 966, in run_commands self.run_command(cmd) File "/usr/lib/python3.10/distutils/dist.py", line 985, in run_command cmd_obj.run() File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 223, in run self.run_tests() File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 226, in run_tests test = unittest.main( File "/usr/lib/python3.10/unittest/main.py", line 100, in __init__ self.parseArgs(argv) File "/usr/lib/python3.10/unittest/main.py", line 147, in parseArgs self.createTests() File "/usr/lib/python3.10/unittest/main.py", line 158, in createTests self.test = self.testLoader.loadTestsFromNames(self.testNames, File "/usr/lib/python3.10/unittest/loader.py", line 220, in loadTestsFromNames suites = [self.loadTestsFromName(name, module) for name in names] File "/usr/lib/python3.10/unittest/loader.py", line 220, in suites = [self.loadTestsFromName(name, module) for name in names] File "/usr/lib/python3.10/unittest/loader.py", line 205, in loadTestsFromName test = obj() File "/<>/src/zodbpickle/tests/test_pickle.py", line 27, in test_suite from .test_pickle_3 import test_suite File "/<>/src/zodbpickle/tests/test_pickle_3.py", line 7, in from .pickletester_3 import AbstractPickleTests File "/<>/src/zodbpickle/tests/pickletester_3.py", line 10, in from test.support import ( ImportError: cannot import name 'TESTFN' from 'test.support' (/usr/lib/python3.10/test/support/__init__.py) E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1: python3.10 setup.py test --- End Message --- --- Begin Message --- Source: zodbpickle Source-Version: 2.2.0-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of zodbpickle, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated zodbpickle 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
Bug#999402: marked as done (pyasn ftbfs with Python 3.10 (test failures))
Your message dated Sat, 20 Nov 2021 20:39:24 + with message-id and subject line Bug#999402: fixed in pyasn 1.6.1-3 has caused the Debian Bug report #999402, regarding pyasn ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyasn Version: 1.6.1-2 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 pyasn ftbfs with python3-defaults from experimental: [...] I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_pyasn/build; python3.10 -m nose -v tests Checks compatibility of PyASN 1.2 results with current pyasn for all 2014 ipasn dbs . ... SKIPPING - Python 2 or PyASN 1.2 not present ... ok Failure: FileNotFoundError ([Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.10_pyasn/build/tests/../data/ipasn_20140513.dat.gz') ... ERROR Tests pyasn.mrtx.parse_mrt_file() - converts a full (TD1) RIB file, and compares ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx.parse_mrt_file() - converts a full (TD2) RIB file, and compares ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx.parse_mrt_file() - converts a full (TD2) RIB file with IPv6; ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx internal classes by converting start of an RIB6 TD2 file (IPv6) ... ERROR Tests pyasn.mrtx internal classes by converting start of an RIB TD1 file ... ERROR Tests pyasn.mrtx internal classes by converting start of an RIB TD2 file ... ERROR Tests pyasn.mrtx.parse_mrt_file() with repeated prefixes causing errros (bug #39) ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx.parse_mrt_file() with routeviews WIDE archive TD1 (bug #42) ... SKIPPING - full dump doesn't exist.ok Tests pyasn.mrtx.parse_mrt_file() with skip_record_on_error set to True ... ERROR Tests pyasn.mrtx.parse_mrt_file() with skip_record_on_error set to default(False); ... ERROR Failure: FileNotFoundError ([Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.10_pyasn/build/tests/../data/ipasn_20140513.dat.gz') ... ERROR == ERROR: Failure: FileNotFoundError ([Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.10_pyasn/build/tests/../data/ipasn_20140513.dat.gz') -- 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.10/imp.py", line 235, in load_module return load_source(name, filename, file) File "/usr/lib/python3.10/imp.py", line 172, in load_source module = _load(spec) File "", line 719, in _load File "", line 688, in _load_unlocked File "", line 883, in exec_module File "", line 241, in _call_with_frames_removed File "/<>/.pybuild/cpython3_3.10_pyasn/build/tests/test_comparative.py", line 39, in class TestCorrectness(TestCase): File "/<>/.pybuild/cpython3_3.10_pyasn/build/tests/test_comparative.py", line 40, in TestCorrectness asndb = pyasn.pyasn(IPASN_DB_PATH) File "/<>/.pybuild/cpython3_3.10_pyasn/build/pyasn/__init__.py", line 64, in __init__ f = gzip.open(ipasn_file, 'rt') # Py2.6 doesn't support 'with' for gzip File "/usr/lib/python3.10/gzip.py", line 58, in open binary_file = GzipFile(filename, gz_mode, compresslevel) File "/usr/lib/python3.10/gzip.py", line 174, in __init__ fileobj = self.myfileobj = builtins.open(filename, mode or 'rb') FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.10_pyasn/build/tests/../data/ipasn_20140513.dat.gz' == ERROR: Tests pyasn.mrtx internal classes by converting start of an RIB6 TD2 file (IPv6) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.10_pyasn/build/tests/test_mrtx.py", line 309, in test_mrt6_table_dump_v2 f = BZ2File(RIB6_TD2_PARTDUMP,
Bug#1000269: marked as done (python3-cxx-dev lacks support for Python 3.10)
Your message dated Sat, 20 Nov 2021 20:39:29 + with message-id and subject line Bug#1000269: fixed in pycxx 7.1.4-0.2 has caused the Debian Bug report #1000269, regarding python3-cxx-dev lacks support for Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-cxx-dev Version: 7.1.4-0.1 Severity: serious Tags: ftbfs bookworm sid Control: affects -1 src:pysvn https://buildd.debian.org/status/logs.php?pkg=pysvn=1.9.12-2%2Bb1 ... debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' set -e && for i in 3.10 3.9; do \ cd /<>/Source; python$i setup.py configure \ --pycxx-src-dir=/usr/share/python$i/CXX \ --pycxx-dir=/usr/include/python$i \ --svn-lib-dir=/usr/lib/x86_64-linux-gnu \ --apr-inc-dir=/usr/include/apr-1.0 \ --apu-inc-dir=/usr/include/apr-1.0 \ --apr-lib-dir=/usr/lib/x86_64-linux-gnu \ --fixed-module-name \ --platform=linux ; \ mv /<>/Source/Makefile /<>/Source/MakefilePy$i ; \ done Info: Configure for python 3.10.0 in exec_prefix /usr Debian lib directory %s /usr/lib/x86_64-linux-gnu Error: Cannot find PyCXX include CXX/Version.hxx - use --pycxx-dir make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 1 --- End Message --- --- Begin Message --- Source: pycxx Source-Version: 7.1.4-0.2 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of pycxx, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated pycxx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Nov 2021 20:16:01 + Source: pycxx Built-For-Profiles: noudeb Architecture: source Version: 7.1.4-0.2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Graham Inggs Closes: 1000269 Changes: pycxx (7.1.4-0.2) unstable; urgency=medium . * Non-maintainer upload * No-change rebuild to add Python 3.10 as supported version (Closes: #1000269) Checksums-Sha1: e27fa0abd63f24eb1379b5fe0598446dd4948375 2083 pycxx_7.1.4-0.2.dsc 1e72d82df583563d79c1900dde1b4b02265f7e9d 8436 pycxx_7.1.4-0.2.debian.tar.xz Checksums-Sha256: eec0116e20fdf1387747a92184fe4f05b0751a12d5487d21c6ba87d13c03f0ec 2083 pycxx_7.1.4-0.2.dsc 2de37a69d152c335f6daa0facac6c88e00222ce7d7c147a21ec37df1e175e305 8436 pycxx_7.1.4-0.2.debian.tar.xz Files: bbafabc342742838675b6f003ed1f294 2083 python optional pycxx_7.1.4-0.2.dsc ccd2650c545b236585c38ece55713fc9 8436 python optional pycxx_7.1.4-0.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmGZWJkACgkQr8/sjmac 4cIVFA/+NMXeWdf5iVYkdnY9IfitMpyhNcQ6bsB87TJ932Yo8AXqJtlvx7ZCOjuu KSO9+G+/rJOGg7TusHKb9KLnuI9oD1NkW4dWGOVSqLioghE+HSGGmWjwluqOfjlp SLDaCbrteXojscv2Jf9Ld1IIjxZLt8F5OCdSp8EiHyLvDr3DfQqXuh54ycGcIMkB dd+uLgtc3Jnn6PgFDgDmfTLeIlBoS/Ub9kJ+CYN0kqz03+3Sx+PX3RlMunLUpfPZ XEznX0Z4SfbAIrFmOhEV30XpdDX5oXnWDMtvXtkLT7K1JDsaUmvT6VECoB7lrqtI qYkst8a9PPCM6RK6dlqE+9n7BqLWeEFMFg5ZmPaYVPLfBGBh4bKhxNdot5kp1VdL sekUKjIFlNrmP6gZCA+n4C0dnL05s2H1twWOMLHLcohBwigckCDmZzm9GF7Tynm8 QPqaA3V1hcYQ/c3a0SRdOEN38MOfMu97wqdtJG4Z0zhYq3JRX9rgAGBaoGmWTJwH 6OwBF3U80RAIbBEMRYT0gggLE5w3DILdBqNmDSnrszFPs5wEWA6Mfdummx7f0SVe HqlC8KdYK6XV/dnZqYLZs2LeA/+wJRHQC9wdDA+dJylBoEnAh49yV/mshFX+jilP e8hnvSX32IBZBwZxTDCRCdXxGbo1l/mA6kWB/dDSkFDPJnOivbA= =g1ek -END PGP SIGNATURE End Message ---
Bug#999626: marked as done (maxima-emacs: fails to install with xemacs21)
Your message dated Sat, 20 Nov 2021 20:37:38 +
with message-id
and subject line Bug#999626: fixed in maxima 5.45.1-5
has caused the Debian Bug report #999626,
regarding maxima-emacs: fails to install with xemacs21
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.)
--
999626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maxima-emacs
Version: 5.45.1-4
Severity: serious
Hi,
maxima-emacs fails to install if xemacs21 is installed:
Setting up maxima-emacs (5.45.1-4) ...
Install emacsen-common for xemacs21
emacsen-common: Handling install of emacsen flavor xemacs21
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Compiling /usr/share/xemacs21/site-lisp/debian-startup.el...
Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc
Done
Install maxima-emacs for xemacs21
install/maxima: Handling install for emacsen flavor xemacs21
Compiling /usr/share/xemacs21/site-lisp/maxima/bookmode.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/bookmode.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/emaxima.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/emaxima.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/imath.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/maxima/imath.el:
!! File error (("Cannot open load file" "cl-lib"))
>>Error occurred processing imath.el: Cannot open load file: cl-lib
Compiling
/usr/share/xemacs21/site-lisp/maxima/imaxima-autoconf-variables.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/imaxima-autoconf-variables.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/imaxima.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/maxima/imaxima.el:
** misplaced interactive spec: (interactive)
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
Wrote /usr/share/xemacs21/site-lisp/maxima/imaxima.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/maxima-font-lock.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/maxima-font-lock.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/maxima.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/maxima.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/mylatex.ltx.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/mylatex.ltx.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/setup-imaxima-imath.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/setup-imaxima-imath.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/smart-complete.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/smart-complete.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/sshell.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/sshell.elc
Done
ERROR: install script from maxima-emacs package failed
dpkg: error processing package maxima-emacs (--configure):
installed maxima-emacs package post-installation script subprocess returned
error exit status 1
Andreas
maxima-emacs=5.45.1-4_xemacs21.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: maxima
Source-Version: 5.45.1-5
Done: Camm Maguire
We believe that the bug you reported is fixed in the latest version of
maxima, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Camm Maguire (supplier of updated maxima 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, 20 Nov 2021 19:42:43 +
Source: maxima
Architecture: source
Version: 5.45.1-5
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire
Changed-By: Camm Maguire
Closes: 999626
Changes:
maxima (5.45.1-5) unstable; urgency=medium
.
* Bug fix: "fails to install with xemacs21", thanks to Andreas Beckmann
(Closes: #999626).
Checksums-Sha1:
8124720038d35529931cfa5d8236fe4f7eb5c28f 2146 maxima_5.45.1-5.dsc
Processed: severity of 1000279 is serious
Processing commands for cont...@bugs.debian.org: > severity 1000279 serious Bug #1000279 [src:openscap] FTBFS: CMake Error: Unknown argument --enable-perl Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 999816 src:rpm Bug #999816 [rpm] rpm - build-depends on removed package. Bug reassigned from package 'rpm' to 'src:rpm'. No longer marked as found in versions rpm/4.16.1.2+dfsg1-3. Ignoring request to alter fixed versions of bug #999816 to the same values previously set > forcemerge 987468 999816 Bug #987468 [src:rpm] rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev Bug #999816 [src:rpm] rpm - build-depends on removed package. 998067 was blocked by: 999342 998634 987468 929484 998633 998067 was not blocking any bugs. Added blocking bug(s) of 998067: 999816 Marked as found in versions rpm/4.16.1.2+dfsg1-0.6. Merged 987468 999816 > tags 987468 ftbfs Bug #987468 [src:rpm] rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev Bug #999816 [src:rpm] rpm - build-depends on removed package. Added tag(s) ftbfs. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 987468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987468 998067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998067 999816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#999398 marked as pending in zodbpickle
Processing control commands: > tag -1 pending Bug #999398 [src:zodbpickle] zodbpickle ftbfs with Python 3.10 (test failures) Added tag(s) pending. -- 999398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999398: marked as pending in zodbpickle
Control: tag -1 pending Hello, Bug #999398 in zodbpickle reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/zodbpickle/-/commit/98630ec7a0c2e78c645f0352ec35e77d17ab73ff New upstream release. Supports Python 3.10 (Closes: #999398) (this message was generated automatically) -- Greetings https://bugs.debian.org/999398
Bug#1000274: py7zr FTBFS with python 3.10
Source: py7zr
Version: 0.11.3+dfsg-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/logs.php?pkg=py7zr=0.11.3%2Bdfsg-1%2Bb1
...
= test session starts ==
platform linux -- Python 3.10.0+, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
benchmark: 3.2.2 (defaults: timer=time.perf_counter disable_gc=False
min_rounds=5 min_time=0.05 max_time=1.0 calibration_precision=10
warmup=False warmup_iterations=10)
rootdir: /<>, configfile: tox.ini
plugins: cov-3.0.0, benchmark-3.2.2
collected 268 items / 12 deselected / 256 selected
tests/test_archive.py ...ss [ 11%]
tests/test_basic.py .F. [ 26%]
tests/test_benchmark.py .. [ 28%]
tests/test_concurrent.py . [ 29%]
tests/test_encryption.py s.. [ 35%]
tests/test_extra_codecs.py ....s.[ 43%]
tests/test_extract.py ..s. [ 60%]
tests/test_info.py ..[ 67%]
tests/test_misc.py ss.. [ 69%]
tests/test_unit.py . [ 90%]
...s.[ 98%]
tests/test_win32compat.py ...s [100%]
=== FAILURES ===
test_cli_help _
capsys = <_pytest.capture.CaptureFixture object at 0x7f1529a9ee60>
@pytest.mark.cli
def test_cli_help(capsys):
expected = 'usage: py7zr [-h] [--version] {l,x,c,a,t,i}
...\n\npy7zr\n\noptional arguments:\n -h, --help'
cli = py7zr.cli.Cli()
with pytest.raises(SystemExit):
cli.run(["-h"])
out, err = capsys.readouterr()
> assert out.startswith(expected)
E AssertionError: assert False
E+ where False = ('usage: py7zr [-h] [--version] {l,x,c,a,t,i}
...\n\npy7zr\n\noptional arguments:\n -h, --help')
E+where = 'usage: py7zr [-h] [--version] {l,x,c,a,t,i}
...\n\npy7zr\n\noptions:\n -h, --help show this help message and exi...s
of archive\n t : Test integrity of archive\n
x : eXtract files with full paths\n'.startswith
/<>/tests/test_basic.py:174: AssertionError
...
Bug#996303: marked as done (ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error:)
Your message dated Sat, 20 Nov 2021 19:19:40 +
with message-id
and subject line Bug#996303: fixed in ruby-json-jwt 1.11.0-2
has caused the Debian Bug report #996303,
regarding ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error:
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.)
--
996303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-json-jwt
Version: 1.11.0-1
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, ruby-json-jwt 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):
> Failure/Error:
>jws_blank.to_json(syntax: :flattened).should == {
> protected: Base64.urlsafe_encode64(jws_blank.header.to_json,
> padding: false),
> payload: '',
> signature: Base64.urlsafe_encode64('', padding: false)
>}.to_json
>
>expected:
> "{\"protected\":\"eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9\",\"payload\":\"\",\"signature\":\"\"}"
> got: "{}" (using ==)
> # ./spec/json/jws_spec.rb:429:in `block (7 levels) in '
>
> Finished in 1.98 seconds (files took 2.47 seconds to load)
> 360 examples, 8 failures, 6 pending
>
> Failed examples:
>
> rspec ./spec/json/jws_spec.rb:356 # JSON::JWS#to_json when syntax option
> given when general should return General JWS JSON Serialization
> rspec ./spec/json/jws_spec.rb:366 # JSON::JWS#to_json when syntax option
> given when general with blank payload should return General JWS JSON
> Serialization
> rspec ./spec/json/jws_spec.rb:378 # JSON::JWS#to_json when syntax option
> given when general when not signed yet should not fail
> rspec ./spec/json/jws_spec.rb:388 # JSON::JWS#to_json when syntax option
> given when general when not signed yet with blank payload should not fail
> rspec ./spec/json/jws_spec.rb:402 # JSON::JWS#to_json when syntax option
> given when flattened should return Flattened JWS JSON Serialization
> rspec ./spec/json/jws_spec.rb:410 # JSON::JWS#to_json when syntax option
> given when flattened with blank payload should return Flattened JWS JSON
> Serialization
> rspec ./spec/json/jws_spec.rb:420 # JSON::JWS#to_json when syntax option
> given when flattened when not signed yet should not fail
> rspec ./spec/json/jws_spec.rb:428 # JSON::JWS#to_json when syntax option
> given when flattened when not signed yet with blank payload should not fail
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-json-jwt/ruby-json-jwt_1.11.0-1+rebuild1633384555_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-json-jwt
Source-Version: 1.11.0-2
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-json-jwt, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-json-jwt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 20 Nov 2021 20:03:47 +0100
Source: ruby-json-jwt
Architecture: source
Version: 1.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996303
Changes:
ruby-json-jwt (1.11.0-2) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.
.
[ Daniel
Processed: Bug#996303 marked as pending in ruby-json-jwt
Processing control commands: > tag -1 pending Bug #996303 [src:ruby-json-jwt] ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Added tag(s) pending. -- 996303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996303: marked as pending in ruby-json-jwt
Control: tag -1 pending
Hello,
Bug #996303 in ruby-json-jwt reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ruby-team/ruby-json-jwt/-/commit/6ecae09c727dbb05924661c016b725a2c0567afb
Update packaging files
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Require ruby-activesupport >= 6.1 (closes: #996303).
(Depends): Use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/rules: Use gem installation layout.
* d/watch: Update file.
* d/upstream/metadata: Add Archive field.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996303
Bug#997246: marked as done (opensaml: FTBFS: add_reference.hpp:27:16: error: forming reference to qualified function type ‘opensaml::saml2::Attribute*() const noexcept’)
Your message dated Sat, 20 Nov 2021 19:03:35 + with message-id and subject line Bug#997246: fixed in opensaml 3.2.1-1 has caused the Debian Bug report #997246, regarding opensaml: FTBFS: add_reference.hpp:27:16: error: forming reference to qualified function type ‘opensaml::saml2::Attribute*() const noexcept’ 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.) -- 997246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opensaml Version: 3.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. > -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -pthread -pthread -pthread > -I/usr/include/x86_64-linux-gnu -pthread -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o > saml2/metadata/impl/libsaml_la-EntityRoleMetadataFilter.lo `test -f > 'saml2/metadata/impl/EntityRoleMetadataFilter.cpp' || echo > './'`saml2/metadata/impl/EntityRoleMetadataFilter.cpp > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -W -pthread -pthread -pthread > -I/usr/include/x86_64-linux-gnu -pthread -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c saml2/metadata/impl/EntityRoleMetadataFilter.cpp > -fPIC -DPIC -o saml2/metadata/impl/.libs/libsaml_la-EntityRoleMetadataFilter.o > saml2/metadata/impl/EntityAttributesEntityMatcher.cpp: In function > ‘opensaml::saml2md::EntityMatcher* > opensaml::saml2md::EntityAttributesEntityMatcherFactory(const > xercesc_3_2::DOMElement* const&, bool)’: > saml2/metadata/impl/EntityAttributesEntityMatcher.cpp:69:109: warning: unused > parameter ‘deprecationSupport’ [-Wunused-parameter] >69 | EntityMatcher* SAML_DLLLOCAL > EntityAttributesEntityMatcherFactory(const DOMElement* const & e, bool > deprecationSupport) > | > ~^~ > saml2/metadata/impl/EntityAttributesEntityMatcher.cpp: In constructor > ‘opensaml::saml2md::EntityAttributesEntityMatcher::EntityAttributesEntityMatcher(const > xercesc_3_2::DOMElement*)’: > saml2/metadata/impl/EntityAttributesEntityMatcher.cpp:93:9: warning: > ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' > instead [-Wdeprecated-declarations] >93 | auto_ptr > nval(AttributeValueBuilder::buildAttributeValue()); > | ^~~~ > In file included from /usr/include/c++/11/memory:76, > from /usr/include/boost/smart_ptr/scoped_ptr.hpp:22, > from /usr/include/boost/scoped_ptr.hpp:13, > from ./internal.h:50, > from > saml2/metadata/impl/EntityAttributesEntityMatcher.cpp:27: > /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here >57 | template class auto_ptr; > |^~~~ > In file included from > /usr/include/boost/type_traits/add_lvalue_reference.hpp:9, > from /usr/include/boost/type_traits/is_convertible.hpp:30, > from /usr/include/boost/iterator/iterator_categories.hpp:19, > from /usr/include/boost/iterator/iterator_adaptor.hpp:14, > from /usr/include/boost/iterator/indirect_iterator.hpp:10, > from > saml2/metadata/impl/EntityAttributesEntityMatcher.cpp:33: > /usr/include/boost/type_traits/add_reference.hpp: In instantiation of ‘struct > boost::detail::add_reference_impl noexcept>’: > /usr/include/boost/type_traits/add_reference.hpp:42:64: required from > ‘struct boost::add_reference’ > /usr/include/boost/lambda/detail/function_adaptors.hpp:262:12: required > from ‘class boost::lambda::function_adaptor (boost::shared_ptr::*)() const > noexcept>::sig (boost::shared_ptr::*)() const noexcept, > boost::tuples::cons&, > boost::tuples::null_type> > >’ > /usr/include/boost/lambda/detail/return_type_traits.hpp:238:63: required > from ‘struct boost::lambda::detail::get_sig (boost::shared_ptr::*)() const noexcept, > boost::tuples::cons (boost::shared_ptr::*)() const noexcept, > boost::tuples::cons&, > boost::tuples::null_type> > >’ > /usr/include/boost/lambda/detail/return_type_traits.hpp:259:16: required > from ‘struct boost::lambda::return_type_N, >
Processed: teach bts the right meta info
Processing commands for cont...@bugs.debian.org:
> reassign 995358 src:ruby-graphql 1.11.8-2
Bug #995358 {Done: Daniel Leidert } [src:ruby-graphql]
ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant
GraphQL::StaticValidation::Validator::Timeout
Ignoring request to reassign bug #995358 to the same package
Bug #995358 {Done: Daniel Leidert } [src:ruby-graphql]
ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant
GraphQL::StaticValidation::Validator::Timeout
Ignoring request to alter found versions of bug #995358 to the same values
previously set
> fixed 995358 1.11.8-3
Bug #995358 {Done: Daniel Leidert } [src:ruby-graphql]
ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant
GraphQL::StaticValidation::Validator::Timeout
Ignoring request to alter fixed versions of bug #995358 to the same values
previously set
> affects 995358 src:ruby-batch-loader
Bug #995358 {Done: Daniel Leidert } [src:ruby-graphql]
ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant
GraphQL::StaticValidation::Validator::Timeout
Added indication that 995358 affects src:ruby-batch-loader
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
995358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000271: jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937']
Source: jupyter-client, dask.distributed
Control: found -1 jupyter-client/7.0.6-2
Control: found -1 dask.distributed/2021.09.1+ds.1-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of jupyter-client the autopkgtest of
dask.distributed fails in testing when that autopkgtest is run with the
binary packages of jupyter-client from unstable. It passes on arm64 and
ppc64el when run with only packages from testing. In tabular form:
passfail
jupyter-client from testing7.0.6-2
dask.distributed from testing2021.09.1+ds.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 jupyter-client 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=jupyter-client
https://ci.debian.net/data/autopkgtest/testing/arm64/d/dask.distributed/16840880/log.gz
=== FAILURES
===
[31m[1m test_gather_failing_cnn_error
_[0m
outer_args = (), kwargs = {}, result = None
coro = ._..test_func..coro
at 0x0c67d550>
[37m@functools[39;49;00m.wraps(func)
[94mdef[39;49;00m [92mtest_func[39;49;00m(*outer_args, **kwargs):
result = [94mNone[39;49;00m
workers = []
[94mwith[39;49;00m clean(timeout=active_rpc_timeout,
**clean_kwargs) [94mas[39;49;00m loop:
[94masync[39;49;00m [94mdef[39;49;00m
[92mcoro[39;49;00m():
[94mwith[39;49;00m dask.config.set(config):
s = [94mFalse[39;49;00m
[94mfor[39;49;00m _ [95min[39;49;00m
[96mrange[39;49;00m([94m60[39;49;00m):
[94mtry[39;49;00m:
s, ws = [94mawait[39;49;00m start_cluster(
nthreads,
scheduler,
loop,
security=security,
Worker=Worker,
scheduler_kwargs=scheduler_kwargs,
worker_kwargs=worker_kwargs,
)
[94mexcept[39;49;00m
[96mException[39;49;00m [94mas[39;49;00m e:
logger.error(
[33m"[39;49;00m[33mFailed to start
gen_cluster: [39;49;00m[33m"[39;49;00m
[33mf[39;49;00m[33m"[39;49;00m[33m{[39;49;00me.[91m__class__[39;49;00m.[91m__name__[39;49;00m[33m}[39;49;00m[33m:
[39;49;00m[33m{[39;49;00me[33m}[39;49;00m[33m;
retrying[39;49;00m[33m"[39;49;00m,
exc_info=[94mTrue[39;49;00m,
)
[94mawait[39;49;00m
asyncio.sleep([94m1[39;49;00m)
[94melse[39;49;00m:
workers[:] = ws
args = [s] + workers
[94mbreak[39;49;00m
[94mif[39;49;00m s [95mis[39;49;00m
[94mFalse[39;49;00m:
[94mraise[39;49;00m
[96mException[39;49;00m([33m"[39;49;00m[33mCould not start
cluster[39;49;00m[33m"[39;49;00m)
[94mif[39;49;00m client:
c = [94mawait[39;49;00m Client(
s.address,
loop=loop,
security=security,
asynchronous=[94mTrue[39;49;00m,
**client_kwargs,
)
args = [c] + args
[94mtry[39;49;00m:
future = func(*args, *outer_args, **kwargs)
future = asyncio.wait_for(future, timeout)
result = [94mawait[39;49;00m future
[94mif[39;49;00m s.validate:
s.validate_state()
[94mfinally[39;49;00m:
[94mif[39;49;00m client [95mand[39;49;00m
c.status [95mnot[39;49;00m [95min[39;49;00m
([33m"[39;49;00m[33mclosing[39;49;00m[33m"[39;49;00m,
[33m"[39;49;00m[33mclosed[39;49;00m[33m"[39;49;00m):
[94mawait[39;49;00m
c._close(fast=s.status == Status.closed)
[94mawait[39;49;00m
Processed: jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937']
Processing control commands: > found -1 jupyter-client/7.0.6-2 Bug #1000271 [src:jupyter-client, src:dask.distributed] jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937'] Marked as found in versions jupyter-client/7.0.6-2. > found -1 dask.distributed/2021.09.1+ds.1-2 Bug #1000271 [src:jupyter-client, src:dask.distributed] jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937'] Marked as found in versions dask.distributed/2021.09.1+ds.1-2. -- 1000271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908017: marked as done (network-manager-iodine FTBFS with glib 2.58)
Your message dated Sat, 20 Nov 2021 18:19:10 + with message-id and subject line Bug#908017: fixed in network-manager-iodine 1.2.0-3.1 has caused the Debian Bug report #908017, regarding network-manager-iodine FTBFS with glib 2.58 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.) -- 908017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: network-manager-iodine Version: 1.2.0-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/network-manager-iodine.html ... nm-iodine-service.c: In function 'nm_iodine_plugin_class_init': nm-iodine-service.c:618:2: error: 'g_type_class_add_private' is deprecated [-Werror=deprecated-declarations] g_type_class_add_private (object_class, sizeof (NMIodinePluginPrivate)); ^~~~ In file included from /usr/include/glib-2.0/gobject/gobject.h:24, from /usr/include/glib-2.0/gobject/gbinding.h:29, from /usr/include/glib-2.0/glib-object.h:23, from /usr/include/glib-2.0/gio/gioenums.h:28, from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/libnm/nm-types.h:24, from /usr/include/libnm/nm-object.h:29, from /usr/include/libnm/nm-access-point.h:29, from /usr/include/libnm/NetworkManager.h:26, from nm-iodine-service.c:45: /usr/include/glib-2.0/gobject/gtype.h:1303:10: note: declared here void g_type_class_add_private (gpointerg_class, ^~~~ cc1: all warnings being treated as errors make[3]: *** [Makefile:470: nm-iodine-service.o] Error 1 --- End Message --- --- Begin Message --- Source: network-manager-iodine Source-Version: 1.2.0-3.1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of network-manager-iodine, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated network-manager-iodine package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Nov 2021 12:37:25 -0500 Source: network-manager-iodine Architecture: source Version: 1.2.0-3.1 Distribution: unstable Urgency: high Maintainer: Guido Günther Changed-By: Boyuan Yang Closes: 908017 Changes: network-manager-iodine (1.2.0-3.1) unstable; urgency=high . * Non-maintainer upload. * debian/control: Set Vcs-* fields to use git packaging repo under Salsa Debian Group. They previously point to upstream development repo that do not contain any packaging information. * Apply patch from Ubuntu: (Closes: #908017) . [ Logan Rosen ] * d/rules: Set --enable-more-warnings to "yes" so that it doesn't default to "error," which turns every warning into an error and causes an FTBFS due to deprecated declarations. Checksums-Sha1: b477b507c8e3522c018163953890e8e414795eff 2243 network-manager-iodine_1.2.0-3.1.dsc 21e2746d488b6e5071f7b24a27eb845e1560af0e 70783 network-manager-iodine_1.2.0.orig.tar.gz 032805b7b2c5328915b764ed217e9ea864a1f160 5796 network-manager-iodine_1.2.0-3.1.debian.tar.xz 5714867746bfb60ee68d11b8b1b7364724edb65f 15628 network-manager-iodine_1.2.0-3.1_amd64.buildinfo Checksums-Sha256: 10a04bd58cff6bf4e0fdc36bb584d0874164393793b0e5b865fbfce12f655c53 2243 network-manager-iodine_1.2.0-3.1.dsc 01d9cd2ef419028f96ce98fa57c724ca75790585e5ec1a17e9e743c1da504e67 70783 network-manager-iodine_1.2.0.orig.tar.gz abb3729ef64783bd426ae71ee66d6d5e1f6c4a6685fa79f077f062e0c4c751c5 5796 network-manager-iodine_1.2.0-3.1.debian.tar.xz 99aa82b996583827af88821df133f90c26eaf5f1c0faf44a83d9bac97855fa9a 15628 network-manager-iodine_1.2.0-3.1_amd64.buildinfo Files: 2354cc861d3f7ff5b7b56aa64502ee57 2243 net optional network-manager-iodine_1.2.0-3.1.dsc 71ed1e21664107f2eaf4c89762cdd9a8 70783 net optional network-manager-iodine_1.2.0.orig.tar.gz
Bug#997757: marked as done (kxd: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules')
Your message dated Sat, 20 Nov 2021 18:05:34 + with message-id and subject line Bug#997757: fixed in kxd 0.15-3 has caused the Debian Bug report #997757, regarding kxd: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules' 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.) -- 997757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kxd Version: 0.15-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > go build -o ./out/kxd ./kxd > go build --tags netgo -a -o ./out/kxc ./kxc > go build -o ./out/kxgencert ./kxgencert > go: go.mod file not found in current directory or any parent directory; see > 'go help modules' > make[1]: *** [Makefile:17: kxc] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/kxd_0.15-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: kxd Source-Version: 0.15-3 Done: Alberto Bertogli We believe that the bug you reported is fixed in the latest version of kxd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Bertogli (supplier of updated kxd 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, 20 Nov 2021 16:55:41 + Source: kxd Architecture: source Version: 0.15-3 Distribution: unstable Urgency: medium Maintainer: Maximiliano Curia Changed-By: Alberto Bertogli Closes: 997757 Changes: kxd (0.15-3) unstable; urgency=medium . * Add modules information (Closes: #997757) Checksums-Sha1: 32c335d0d1b42976cda91b91f14a29953bf4fcec 1348 kxd_0.15-3.dsc 10162b5d9af7cac043e472c4f39de0b788c857ff 4920 kxd_0.15-3.debian.tar.xz 3aa66225fc8c7fc71b87acb0cd4916600f7549d4 6318 kxd_0.15-3_amd64.buildinfo Checksums-Sha256: 2a6523554054c318ce53da40d090f010154c7cb17ab00f4c892d3516e4e1ed54 1348 kxd_0.15-3.dsc 3c4bc17dffbc67e1e0db2d4871847d296abef4abee9b5f07201d8a65beba66aa 4920 kxd_0.15-3.debian.tar.xz da73aee18828594ec74336cbf815d20d8d45e09b38877ecbf2e2e92d86f6d946 6318 kxd_0.15-3_amd64.buildinfo Files: 0d43571be937ec1b855e68a4ed7571db 1348 net optional kxd_0.15-3.dsc 3ee970a151833545a1572d1e81908dcb 4920 net optional kxd_0.15-3.debian.tar.xz 1d3e983db5f4e2408650c208be03a53e 6318 net optional kxd_0.15-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iIYEARYIAC4WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCYZky9hAcemhzakBkZWJp YW4ub3JnAAoJEH9E+iXqVRTLzp4A/R5dNLe/0QLJeYmZUA4Bwbgo4NKtm3kSPd3I DXcsl76rAP48nfxmi+oiMKZk7dHAm1kywHf6mVTWXPdsWjDo45FzAA== =ZwX0 -END PGP SIGNATURE End Message ---
Bug#997721: marked as done (postgresql-semver: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)
Your message dated Sat, 20 Nov 2021 18:00:09 +
with message-id
and subject line Bug#997721: fixed in postgresql-semver 0.31.2-1
has caused the Debian Bug report #997721,
regarding postgresql-semver: FTBFS: Error: debian/control needs updating from
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)
--
997721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-semver
Version: 0.31.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package postgresql-semver
> dpkg-buildpackage: info: source version 0.31.1-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Felix Lechner
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2021-09-27 20:01:37.0 +
> +++ debian/control.ZO45zn 2021-10-23 06:29:04.950729454 +
> @@ -11,9 +11,9 @@
> Vcs-Git: https://salsa.debian.org/lechner/postgresql-semver.git
> Homepage: https://pgxn.org/dist/semver/doc/semver.html
>
> -Package: postgresql-13-semver
> +Package: postgresql-14-semver
> Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14
> Description: Semantic version number type for PostgreSQL
> This library contains a single PostgreSQL extension for a data type
> called 'semver'. It implements the version number format described
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [/usr/share/postgresql-common/pgxs_debian_control.mk:9:
> debian/control] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/postgresql-semver_0.31.1-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: postgresql-semver
Source-Version: 0.31.2-1
Done: Felix Lechner
We believe that the bug you reported is fixed in the latest version of
postgresql-semver, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Felix Lechner (supplier of updated
postgresql-semver package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 03 Nov 2021 09:20:04 -0700
Source: postgresql-semver
Binary: postgresql-14-semver postgresql-14-semver-dbgsym
Architecture: source amd64
Version: 0.31.2-1
Distribution: unstable
Urgency: medium
Maintainer: Felix Lechner
Changed-By: Felix Lechner
Description:
postgresql-14-semver - Semantic version number type for PostgreSQL
Closes: 997721
Changes:
postgresql-semver (0.31.2-1) unstable; urgency=medium
.
[Christoph Berg]
* Use `dh --with pgxs_loop` for simpler d/rules; also runs tests at build
time (MR !1).
.
[Felix Lechner]
* New upstream version.
* Update d/control with 'pg_buildext updatecontrol'. (Closes: #997721)
* Drop two patches previously cherry-picked from upstream:
- 0001-Use-INT32_MAX-instead-of-INT_MAX.patch
- 0002-Handle-errors-from-strtol.patch
* Place instructions for the upstream (orig) tarball in d/README.Debian.
Checksums-Sha1:
Bug#999376: marked as done (python-gmpy2 ftbfs with Python 3.10)
On 11/19/21 1:45 PM, Debian Bug Tracking System wrote: Your message dated Fri, 19 Nov 2021 21:40:53 + with message-id and subject line Bug#999376: fixed in python-gmpy2 2.1.0~b5-1 has caused the Debian Bug report #999376, regarding python-gmpy2 ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) Sorry, I was in an arm sling after shoulder surgery and unable to easily type on my home computer, so I hadn't gotten a chance to update this yet. I was about to do so and see you beat me to it. Thank you!
Bug#1000269: python3-cxx-dev lacks support for Python 3.10
Package: python3-cxx-dev Version: 7.1.4-0.1 Severity: serious Tags: ftbfs bookworm sid Control: affects -1 src:pysvn https://buildd.debian.org/status/logs.php?pkg=pysvn=1.9.12-2%2Bb1 ... debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' set -e && for i in 3.10 3.9; do \ cd /<>/Source; python$i setup.py configure \ --pycxx-src-dir=/usr/share/python$i/CXX \ --pycxx-dir=/usr/include/python$i \ --svn-lib-dir=/usr/lib/x86_64-linux-gnu \ --apr-inc-dir=/usr/include/apr-1.0 \ --apu-inc-dir=/usr/include/apr-1.0 \ --apr-lib-dir=/usr/lib/x86_64-linux-gnu \ --fixed-module-name \ --platform=linux ; \ mv /<>/Source/Makefile /<>/Source/MakefilePy$i ; \ done Info: Configure for python 3.10.0 in exec_prefix /usr Debian lib directory %s /usr/lib/x86_64-linux-gnu Error: Cannot find PyCXX include CXX/Version.hxx - use --pycxx-dir make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 1
Processed: python3-cxx-dev lacks support for Python 3.10
Processing control commands: > affects -1 src:pysvn Bug #1000269 [python3-cxx-dev] python3-cxx-dev lacks support for Python 3.10 Added indication that 1000269 affects src:pysvn -- 1000269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000268: ros-ros-comm FTBFS on IPV6-only buildds
Source: ros-ros-comm
Version: 1.15.13+ds1-5
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=ros-ros-comm=amd64=1.15.13%2Bds1-5%2Bb1=1637417945=0
...
[roswtf.rosunit-roswtf_command_line_online/test_cmd_help][passed]
[roswtf.rosunit-roswtf_command_line_online/test_offline][FAILURE]---
False is not true : CMD[roswtf] OUTPUT[Package: roswtf
]
stderr[Traceback (most recent call last):
File "/<>/.pybuild/cpython3_3.10/build/devel/bin/roswtf", line
15, in
exec(compile(fh.read(), python_script, 'exec'), context)
File "/<>/utilities/roswtf/scripts/roswtf", line 35, in
roswtf.roswtf_main()
File "", line 89, in roswtf_main
File "", line 175, in _roswtf_main
File "/<>/utilities/roswtf/src/roswtf/network.py", line 120, in
wtf_check
error_rule(r, r[0](ctx), ctx)
File "/<>/utilities/roswtf/src/roswtf/network.py", line 54, in
ip_check
resolved_ips = [host[4][0] for host in
socket.getaddrinfo(socket.gethostname(), 0, socket.AF_INET, 0, socket.SOL_TCP)]
File "/usr/lib/python3.9/socket.py", line 954, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -5] No address associated with hostname
]
File "/usr/lib/python3.9/unittest/case.py", line 59, in testPartExecutor
yield
File "/usr/lib/python3.9/unittest/case.py", line 592, in run
self._callTestMethod(testMethod)
File "/usr/lib/python3.9/unittest/case.py", line 550, in _callTestMethod
method()
File
"/<>/utilities/roswtf/test/check_roswtf_command_line_online.py",
line 120, in test_offline
self._check_output([cmd], output.decode(), err.decode())
File
"/<>/utilities/roswtf/test/check_roswtf_command_line_online.py",
line 130, in _check_output
self.assert_(
File "/usr/lib/python3.9/unittest/case.py", line 1335, in deprecated_func
return original_func(*args, **kwargs)
File "/usr/lib/python3.9/unittest/case.py", line 688, in assertTrue
raise self.failureException(msg)
SUMMARY
[1;31m * RESULT: FAIL[0m
* TESTS: 2
* ERRORS: 0
[1;31m * FAILURES: 1[0m
...
dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9"
--before-test "PYTHONPATH={build_dir}/build/devel/lib/python*/dist-packages
make -C {build_dir} run_tests" --after-test "catkin_test_results {build_dir}"
returned exit code 13
make[1]: *** [debian/rules:21: override_dh_auto_test] Error 25
Processed: Bug#997757 marked as pending in kxd
Processing control commands: > tag -1 pending Bug #997757 [src:kxd] kxd: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules' Added tag(s) pending. -- 997757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997757: marked as pending in kxd
Control: tag -1 pending Hello, Bug #997757 in kxd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/kxd/-/commit/060e537f720f6d2b7e3210bce867b774041fd727 Add modules information Cherry-pick commit e5b1abe3b from upstream, which includes modules information so that kxd can build with new Go compilers that require this. Closes: #997757 (this message was generated automatically) -- Greetings https://bugs.debian.org/997757
Bug#1000265: typo in fix for CVE-2021-21996 breaks file.managed on stretch
Package: salt-common Version: 2016.11.2+ds-1+deb9u8 Severity: grave The patch for 994016 in the /usr/lib/python2.7/dist-packages/salt/fileclient.py file included: +# clean_path returns an empty string if the check fails +root_path = salt.utils.path.join(cachedir, "extrn_files", saltenv, netloc) which might work for newer versions of salt, but in stretch that has to be salt.utils.path_join(...) as the salt.utils.path module didn't exist yet. As-is, the security update for CVE-2021-21996 makes file.managed states fail with: Unable to manage file: 'module' object has no attribute 'path' which makes salt on stretch pretty much unusable. -- Jamie Heilman http://audible.transient.net/~jamie/
Bug#1000263: package broken after php8 upgrade
Package: tt-rss
Version: 21~git20210204.b4cbc79+dfsg-1
Severity: serious
Since upgrade from php packages 7.4 to 8.1, tt-rss is unusable. Logs
contain several occurrences of:
[Sat Nov 20 17:11:06.950555 2021] [php:error] [pid 2895803] [client
127.0.0.1:40988] PHP Fatal error: Uncaught ValueError:
mb_convert_encoding(): Argument #2 ($to_encoding) must be a valid
encoding, "" given in
/usr/share/php/php-php-gettext/gettext.inc:181\nStack trace:\n#0
/usr/share/php/php-php-gettext/gettext.inc(181):
mb_convert_encoding()\n#1
/usr/share/php/php-php-gettext/gettext.inc(278): _encode()\n#2
/usr/share/php/php-php-gettext/gettext.inc(285): _gettext()\n#3
/usr/share/tt-rss/www/include/functions.php(102): __()\n#4
/usr/share/tt-rss/www/include/functions.php(141): get_translations()\n#5
/usr/share/tt-rss/www/classes/userhelper.php(124): startup_gettext()\n#6
/usr/share/tt-rss/www/index.php(31): UserHelper::login_sequence()\n#7
{main}\n thrown in /usr/share/php/php-php-gettext/gettext.inc on line 181
I'm not sure if the culprit is tt-rss or php-php-gettext package.
On https://www.php.net/manual/en/function.mb-convert-encoding.php:
8.0.0 mb_convert_encoding() will now throw a ValueError when
to_encoding is passed an invalid encoding.
So, it really is a misusage of mb_convert_encoding() either by tt-rss or
by php-php-gettext.
php-php-gettext: 1.0.12-4
Bug#1000210: [regression] uscan die: filenamemangle failed
Le 20/11/2021 à 13:36, Mattia Rizzolo a écrit : > On Sat, Nov 20, 2021 at 01:14:23PM +0100, Yadd wrote: >> Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : >>> So, effectively, the change broke the specification. >> >> It looks like the specification was not good. A filename isn't an URL > > Be that as it may, we can't break something like that without a version > bump, IMHO. > > So we need a different fix for #993585. > > Either way, I think it's unrelated to your discovery that it could > potentially overwrite a file, isn't it? Sure, I had this bug for a while without understanding what happens until rouca found it
Bug#999397: marked as done (siphashc ftbfs with Python 3.10 (test failures))
Your message dated Sat, 20 Nov 2021 13:55:30 +
with message-id
and subject line Bug#999397: fixed in siphashc 2.1-0.1
has caused the Debian Bug report #999397,
regarding siphashc ftbfs with Python 3.10 (test failures)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
999397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: siphashc
Version: 1.2-1
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
siphashc ftbfs with python3-defaults from experimental:
[...]
==
ERROR: test_errors (test_siphashc.TestSiphashC)
Test error handling.
--
Traceback (most recent call last):
File "/<>/test_siphashc.py", line 20, in test_errors
siphash('not long enough', 'a')
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
==
ERROR: test_hash (test_siphashc.TestSiphashC)
Test simple hashing.
--
Traceback (most recent call last):
File "/<>/test_siphashc.py", line 11, in test_hash
result = siphash('sixteencharstrng', 'i need a hash of this')
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
==
ERROR: test_reference_vectors (test_siphashc.TestSiphashC)
Test reference vectors.
--
Traceback (most recent call last):
File "/<>/test_siphashc.py", line 55, in test_reference_vectors
self.assertEqual(siphash(k, message), vectors[i])
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
--
Ran 3 tests in 0.002s
FAILED (errors=3)
Test failed:
error: Test failed:
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1:
python3.10 setup.py test
--- End Message ---
--- Begin Message ---
Source: siphashc
Source-Version: 2.1-0.1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
siphashc, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated siphashc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 20 Nov 2021 09:17:18 -0400
Source: siphashc
Architecture: source
Version: 2.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Ana Rodríguez López
Changed-By: Stefano Rivera
Closes: 999397
Changes:
siphashc (2.1-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
* New upstream release.
- Supports Python 3.10. (Closes: #999397)
* Add watch file.
* Update copyright years.
Checksums-Sha1:
af2e65ff0f005c2fc69cd5f2b1b6c83aae1f6f13 1342 siphashc_2.1-0.1.dsc
900c428733f307766a371825bb7b85980a6095b2 11408 siphashc_2.1.orig.tar.gz
2af9c9ff70b95e507776c31f74a6c91abf41370e 2068 siphashc_2.1-0.1.debian.tar.xz
1ce9390410445d54e91fc508a9eaa61678a911b2 6027 siphashc_2.1-0.1_source.buildinfo
Checksums-Sha256:
193c88800a7da049e6bda9345ae94c7eaf1389ac17e8a5f058b4ed0f1cc6243f 1342
siphashc_2.1-0.1.dsc
e6a9da952d684a52cb797dff7a96639bad2bdb779e4856158aa294618d505fbe 11408
siphashc_2.1.orig.tar.gz
04b8cba9ac4b757f6581734db517354dbba553f3995a3d5b2d8de7e2686d2e71 2068
siphashc_2.1-0.1.debian.tar.xz
42b1a9528a39285135a511dad60079ed55c7d9f4437e66d11fd761922ed96658 6027
siphashc_2.1-0.1_source.buildinfo
Files:
33c972003ed412d1fa26cf31c223c473 1342 python optional siphashc_2.1-0.1.dsc
d1003d1d2ee2cf4e4b251dd38e3cff02 11408 python optional siphashc_2.1.orig.tar.gz
f9c6f22920e174aff1b70ea2aef08809 2068 python optional
siphashc_2.1-0.1.debian.tar.xz
54cf4a68ddbb282852c8c5836afec135 6027 python optional
siphashc_2.1-0.1_source.buildinfo
-BEGIN PGP SIGNATURE-
Bug#999397: siphashc: diff for NMU version 2.1-0.1
Control: tags 999397 + patch
Dear maintainer,
I've prepared an NMU for siphashc (versioned as 2.1-0.1). The diff
is attached to this message.
Regards.
SR
diff -Nru siphashc-1.2/appveyor.yml siphashc-2.1/appveyor.yml
--- siphashc-1.2/appveyor.yml 2018-10-04 06:47:17.0 -0400
+++ siphashc-2.1/appveyor.yml 1969-12-31 20:00:00.0 -0400
@@ -1,33 +0,0 @@
-version: "{build}"
-
-clone_depth: 100
-
-environment:
- matrix:
-- PYTHON: "C:\\Python27"
-- PYTHON: "C:\\Python33"
-- PYTHON: "C:\\Python34"
-- PYTHON: "C:\\Python35"
-- PYTHON: "C:\\Python36"
-- PYTHON: "C:\\Python36-x64"
-
-install:
- - "SET PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%"
- # We need wheel installed to build wheels
- - "python.exe -m pip install wheel"
-
-build_script:
- # Build the compiled extension
- - "python setup.py build"
-
-test_script:
- # Run the project tests
-- "python setup.py test"
-- "python benchmark.py"
-
-after_test:
- - "python.exe setup.py bdist_wheel"
-
-artifacts:
- # bdist_wheel puts your built wheel in the dist directory
- - path: dist\*
diff -Nru siphashc-1.2/benchmark.py siphashc-2.1/benchmark.py
--- siphashc-1.2/benchmark.py 2018-10-04 06:47:17.0 -0400
+++ siphashc-2.1/benchmark.py 2020-09-02 04:05:03.0 -0400
@@ -1,17 +1,17 @@
#!/usr/bin/env python
-"""Simple timing benchmark.
+"""
+Simple timing benchmark.
+
+Used for testing possible regressions when changing code.
+"""
-Used for testing possible regressions when changing code."""
-from __future__ import print_function
import timeit
-print('Benchmark (short):')
-print(timeit.timeit(
-"siphash('0123456789ABCDEF', 'a')",
-"from siphashc import siphash"
-))
-print('Benchmark (long):')
-print(timeit.timeit(
-"siphash('0123456789ABCDEF', 'a' * 1000)",
-"from siphashc import siphash"
-))
+print("Benchmark (short):")
+print(timeit.timeit("siphash('0123456789ABCDEF', 'a')", "from siphashc import siphash"))
+print("Benchmark (long):")
+print(
+timeit.timeit(
+"siphash('0123456789ABCDEF', 'a' * 1000)", "from siphashc import siphash"
+)
+)
diff -Nru siphashc-1.2/CHANGES.rst siphashc-2.1/CHANGES.rst
--- siphashc-1.2/CHANGES.rst 2018-10-04 06:47:17.0 -0400
+++ siphashc-2.1/CHANGES.rst 2020-09-02 04:05:03.0 -0400
@@ -1,6 +1,22 @@
Changes
===
+2.1
+---
+
+* Fixed publishing wheels in pypi.org.
+
+2.0
+---
+
+* Dropped support for Python 2.
+
+1.3
+---
+
+* Changed license to ISC.
+* Fixed depreciation warning on Python 3.8.
+
1.2
---
diff -Nru siphashc-1.2/debian/changelog siphashc-2.1/debian/changelog
--- siphashc-1.2/debian/changelog 2019-01-25 13:02:55.0 -0400
+++ siphashc-2.1/debian/changelog 2021-11-20 09:10:26.0 -0400
@@ -1,3 +1,11 @@
+siphashc (2.1-0.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * New upstream release.
+ * Add watch file.
+
+ -- Stefano Rivera Sat, 20 Nov 2021 09:10:26 -0400
+
siphashc (1.2-1) unstable; urgency=medium
* Initial release (Closes: #892182)
diff -Nru siphashc-1.2/debian/watch siphashc-2.1/debian/watch
--- siphashc-1.2/debian/watch 1969-12-31 20:00:00.0 -0400
+++ siphashc-2.1/debian/watch 2021-11-20 09:08:43.0 -0400
@@ -0,0 +1,4 @@
+version=4
+opts="filenamemangle=s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%@PACKAGE@-$1.tar.gz%" \
+ https://github.com/WeblateOrg/siphashc/tags \
+ (?:.*?/)?v?(\d[\d.]*)\.tar\.gz
diff -Nru siphashc-1.2/.github/dependabot.yml siphashc-2.1/.github/dependabot.yml
--- siphashc-1.2/.github/dependabot.yml 1969-12-31 20:00:00.0 -0400
+++ siphashc-2.1/.github/dependabot.yml 2020-09-02 04:05:03.0 -0400
@@ -0,0 +1,17 @@
+# This file is generated in https://github.com/WeblateOrg/meta/
+version: 2
+updates:
+ - package-ecosystem: github-actions
+directory: /
+schedule:
+ interval: daily
+labels:
+ - dependencies
+ - automerge
+ - package-ecosystem: pip
+directory: /
+schedule:
+ interval: daily
+labels:
+ - dependencies
+ - automerge
diff -Nru siphashc-1.2/.github/FUNDING.yml siphashc-2.1/.github/FUNDING.yml
--- siphashc-1.2/.github/FUNDING.yml 1969-12-31 20:00:00.0 -0400
+++ siphashc-2.1/.github/FUNDING.yml 2020-09-02 04:05:03.0 -0400
@@ -0,0 +1,4 @@
+# This file is maintained in https://github.com/WeblateOrg/meta/
+github: [nijel]
+custom: https://weblate.org/donate/
+liberapay: Weblate
diff -Nru siphashc-1.2/.github/.kodiak.toml siphashc-2.1/.github/.kodiak.toml
--- siphashc-1.2/.github/.kodiak.toml 1969-12-31 20:00:00.0 -0400
+++ siphashc-2.1/.github/.kodiak.toml 2020-09-02 04:05:03.0 -0400
@@ -0,0 +1,9 @@
+# This file is maintained in https://github.com/WeblateOrg/meta/
+# Configuration for https://kodiakhq.com/
+version = 1
+
+[merge]
+method = "rebase"
+
+[update]
+ignored_usernames = ["dependabot", "weblate"]
diff -Nru siphashc-1.2/.github/labels.yml siphashc-2.1/.github/labels.yml
--- siphashc-1.2/.github/labels.yml 1969-12-31
Processed: siphashc: diff for NMU version 2.1-0.1
Processing control commands: > tags 999397 + patch Bug #999397 [src:siphashc] siphashc ftbfs with Python 3.10 (test failures) Added tag(s) patch. -- 999397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999395: marked as done (python-zstd ftbfs with Python 3.10 (test failures))
Your message dated Sat, 20 Nov 2021 12:48:59 + with message-id and subject line Bug#999395: fixed in python-zstd 1.5.0.2-1 has caused the Debian Bug report #999395, regarding python-zstd ftbfs with Python 3.10 (test failures) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-zstd Version: 1.4.5.1-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python-zstd ftbfs with python3-defaults from experimental: [...] == ERROR: test_compression_default_level (tests.test_compress.TestZSTD) -- Traceback (most recent call last): File "/<>/tests/test_compress.py", line 19, in test_compression_default_level BaseTestZSTD.helper_compression_default_level(self) File "/<>/tests/base.py", line 71, in helper_compression_default_level CDATA = zstd.compress(tDATA) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_compression_default_level_default (tests.test_compress.TestZSTD) -- Traceback (most recent call last): File "/<>/tests/test_compress.py", line 25, in test_compression_default_level_default BaseTestZSTD.helper_compression_default_level_default(self) File "/<>/tests/base.py", line 79, in helper_compression_default_level_default CDATA = zstd.compress(tDATA) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_compression_default_level_zero (tests.test_compress.TestZSTD) -- Traceback (most recent call last): File "/<>/tests/test_compress.py", line 22, in test_compression_default_level_zero BaseTestZSTD.helper_compression_default_level_zero(self) File "/<>/tests/base.py", line 75, in helper_compression_default_level_zero CDATA = zstd.compress(tDATA) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_compression_level1 (tests.test_compress.TestZSTD) -- Traceback (most recent call last): File "/<>/tests/test_compress.py", line 48, in test_compression_level1 BaseTestZSTD.helper_compression_level1(self) File "/<>/tests/base.py", line 119, in helper_compression_level1 self.assertEqual(DATA, zstd.decompress(zstd.compress(DATA, 1))) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_compression_level20 (tests.test_compress.TestZSTD) -- Traceback (most recent call last): File "/<>/tests/test_compress.py", line 54, in test_compression_level20 BaseTestZSTD.helper_compression_level20(self) File "/<>/tests/base.py", line 133, in helper_compression_level20 self.assertEqual(DATA, zstd.decompress(zstd.compress(DATA, 20))) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_compression_level6 (tests.test_compress.TestZSTD) -- Traceback (most recent call last): File "/<>/tests/test_compress.py", line 51, in test_compression_level6 BaseTestZSTD.helper_compression_level6(self) File "/<>/tests/base.py", line 126, in helper_compression_level6 self.assertEqual(DATA, zstd.decompress(zstd.compress(DATA, 6))) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_compression_multi_thread_many (tests.test_compress.TestZSTD) -- Traceback (most recent call last): File "/<>/tests/test_compress.py", line 40, in test_compression_multi_thread_many BaseTestZSTD.helper_compression_multi_thread_many(self) File "/<>/tests/base.py", line 104, in helper_compression_multi_thread_many CDATA = zstd.compress(tDATA, 6, 16) SystemError: PY_SSIZE_T_CLEAN macro must be
Processed: Bug#998528 marked as pending in file-roller
Processing control commands: > tag -1 pending Bug #998528 [src:file-roller] file-roller: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "magic" Added tag(s) pending. -- 998528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998528: marked as pending in file-roller
Control: tag -1 pending Hello, Bug #998528 in file-roller reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/file-roller/-/commit/30206544c02e1e62318696e3c9d6446e27a502b0 Remove use of libmagic (upstream dropped support) The magic configure option no longer exists and now causes a failure to build from source. Relevant upstream commits: commit 067036301b0a0bdadacc24823faff4d7001cf4c6 Author: Jasper Lievisse Adriaanse Date: Sun Jan 6 14:06:04 2019 +0100 Remove libmagic leftovers from ab34e3f7 commit ab34e3f765183136c3e548f180751ffe5efd3860 Author: Paolo Bacchilega Date: Mon Aug 20 12:26:52 2018 +0200 removed use of magic to detect the mime type from content magic doesn't detect zip files from content, which is very important to us. Closes: #998528 (this message was generated automatically) -- Greetings https://bugs.debian.org/998528
Bug#1000210: [regression] uscan die: filenamemangle failed
On Sat, Nov 20, 2021 at 01:14:23PM +0100, Yadd wrote: > Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : > > So, effectively, the change broke the specification. > > It looks like the specification was not good. A filename isn't an URL Be that as it may, we can't break something like that without a version bump, IMHO. So we need a different fix for #993585. Either way, I think it's unrelated to your discovery that it could potentially overwrite a file, isn't it? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1000210: [regression] uscan die: filenamemangle failed
Le 20/11/2021 à 12:23, Mattia Rizzolo a écrit : > Yadd: > > Looking better, I think we do have a small problem here: > > On Fri, Nov 19, 2021 at 08:16:37PM +0100, Michael Biebl wrote: >> uscan info: Looking at $base = >> https://github.com/systemd/systemd-stable/tags with >> $filepattern = .*/v?(\d\S*)\.tar\.gz found >> $newfile = >> https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz >> $newversion = 249.7 >> $lastversion = 249.6 >> uscan info: Matching target for downloadurlmangle: >> https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz >> uscan info: Upstream URL(+tag) to download is identified as >> https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz >> uscan info: Matching target for filenamemangle: v249.7.tar.gz >> uscan die: filenamemangle failed for v249.7.tar.gz at >> /usr/share/perl5/Devscripts/Uscan/Output.pm line 60. > ... >> uscan info: Looking at $base = >> https://github.com/systemd/systemd-stable/tags with >> $filepattern = .*/v?(\d\S*)\.tar\.gz found >> $newfile = >> https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz >> $newversion = 249.7 >> $lastversion = 249.6 >> uscan info: Matching target for downloadurlmangle: >> https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz >> uscan info: Upstream URL(+tag) to download is identified as >> https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz >> uscan info: Matching target for filenamemangle: >> https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz >> uscan info: Filename (filenamemangled) for downloaded file: >> systemd-249.7.tar.gz > > > I went to better read the relevant documentation: > >filenamemangle=rules >Generate the upstream tarball filename from the selected href >string if matching-pattern can extract the latest upstream >version from the selected href string. Otherwise, >generate the upstream tarball filename from its full URL >string and set the missing from the generated >upstream tarball filename. > > That text is very confusing to me, but it does say that the rules, in > some cases, are matched against the full URL. > > In particular, it means that any matching-pattern that has ".*" as > leading characters will most likely have a full URL here to match > against. > > > So, effectively, the change broke the specification. It looks like the specification was not good. A filename isn't an URL > This apparently came as a result to https://bugs.debian.org/993585 - > which was really complaining about pgpsigurlmangle but it ended up > affecting filenamemangle too. > > In fact, I believe reverting 9e65c07737425748e396291d9c20442d11b0641b > fixes this bug, but probably reopens that other one.
Bug#1000210: [regression] uscan die: filenamemangle failed
Yadd: Looking better, I think we do have a small problem here: On Fri, Nov 19, 2021 at 08:16:37PM +0100, Michael Biebl wrote: > uscan info: Looking at $base = https://github.com/systemd/systemd-stable/tags > with > $filepattern = .*/v?(\d\S*)\.tar\.gz found > $newfile = > https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz > $newversion = 249.7 > $lastversion = 249.6 > uscan info: Matching target for downloadurlmangle: > https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz > uscan info: Upstream URL(+tag) to download is identified as > https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz > uscan info: Matching target for filenamemangle: v249.7.tar.gz > uscan die: filenamemangle failed for v249.7.tar.gz at > /usr/share/perl5/Devscripts/Uscan/Output.pm line 60. ... > uscan info: Looking at $base = https://github.com/systemd/systemd-stable/tags > with > $filepattern = .*/v?(\d\S*)\.tar\.gz found > $newfile = > https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz > $newversion = 249.7 > $lastversion = 249.6 > uscan info: Matching target for downloadurlmangle: > https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz > uscan info: Upstream URL(+tag) to download is identified as > https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz > uscan info: Matching target for filenamemangle: > https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz > uscan info: Filename (filenamemangled) for downloaded file: > systemd-249.7.tar.gz I went to better read the relevant documentation: filenamemangle=rules Generate the upstream tarball filename from the selected href string if matching-pattern can extract the latest upstream version from the selected href string. Otherwise, generate the upstream tarball filename from its full URL string and set the missing from the generated upstream tarball filename. That text is very confusing to me, but it does say that the rules, in some cases, are matched against the full URL. In particular, it means that any matching-pattern that has ".*" as leading characters will most likely have a full URL here to match against. So, effectively, the change broke the specification. This apparently came as a result to https://bugs.debian.org/993585 - which was really complaining about pgpsigurlmangle but it ended up affecting filenamemangle too. In fact, I believe reverting 9e65c07737425748e396291d9c20442d11b0641b fixes this bug, but probably reopens that other one. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#998395: marked as done (FTBFS: very wrong python dependency)
Your message dated Sat, 20 Nov 2021 09:18:57 + with message-id and subject line Bug#998395: fixed in google-auth-httplib2 0.1.0-2 has caused the Debian Bug report #998395, regarding FTBFS: very wrong python 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.) -- 998395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: assimp Version: 5.0.1~ds0-3 Tags: patch Control: clone -1 -2 Control: retitle -2 rules-require-build-prerequisite gives bogus advice Control: reassign -2 lintian Control: severity -2 important Control: tags -2 - patch Control: affects -2 src:assimp User: debian-cr...@lists.debian.org Usertags: ftcbfs X-Debbugs-Cc: debhel...@packages.debian.org X-Debbugs-Cc: debian-cr...@lists.debian.org assimp fails to cross build from source. It attempts to build a python module, but it ultimately fails doing so. While inspecting this, I discovered that assimp "Build-Depends: python3:any | python3-all:any | python3-dev:any | python3-all-dev:any | dh-sequence-python3". This is wrong on so many levels. For starters, sbuild ignores any alternative in unstable, so in practice, this happens to become "python3:any". Any other alternative is simply ignored and shouldn't be there. Then, issuing a dependency on python3-dev:any without libpython3-dev is practically never correct. That could be a separate lintian tag, but that's not too bad here as python3-dev isn't needed. Either you go python3-dev or you go python3-dev:any, libpython3-dev or you have a very special and unusual use case that I have never encountered anywhere. Also listing dh-sequence-python3 there is bogus. You already added "--with python3" in debian/rules. This is duplicate at best. Either should be dropped, but enabling a dh-addon in an alternative is clearly not right, and debhelper should likely fail hard when encountering that. Niels, do you agree? I wondered how one would come up with such a strange dependency and asked #debian-mentors for help. Kindly, a user named "itd" pointed me at the lintian tag rules-require-build-prerequisite, which very likely is the cause for this. Please disable the tag right now as it does more harm than good. While the tag isn't bad per-se, the advice it gives misleads users and produces broken packages. I request hiding or disabling it now and then figuring out what it really should say. Back to assimp. I looked into this to make it cross buildable, right? And it was failing in Python-ish stuff. So why do we actually build the Python module? Did I say module? It's not an extension? No, it isn't. And we really don't have to build it in an arch-only build. So the key to making assimp cross buildable is to make an arch-only build fully skip the Python stuff. And once you do that, you don't care about :any annotations anymore as those are practically irrelevant in Build-Depends-Indep. So I've attached a patch for assimp to fix the cross build and the strange build dependency. Please consider applying it. Helmut diff --minimal -Nru assimp-5.0.1~ds0/debian/changelog assimp-5.0.1~ds0/debian/changelog --- assimp-5.0.1~ds0/debian/changelog 2021-10-06 09:02:14.0 +0200 +++ assimp-5.0.1~ds0/debian/changelog 2021-10-08 20:49:28.0 +0200 @@ -1,3 +1,15 @@ +assimp (5.0.1~ds0-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix python build dependency. (Closes: #-1) ++ Alternatives in Build-Depends are ignored. ++ Enable the python3 dh addon once only. ++ Build python module in indep build only. ++ Move python Build-Depends to B-D-I. ++ Drop the :any nonsense. + + -- Helmut Grohne Fri, 08 Oct 2021 20:49:28 +0200 + assimp (5.0.1~ds0-3) unstable; urgency=medium [ Debian Janitor ] diff --minimal -Nru assimp-5.0.1~ds0/debian/control assimp-5.0.1~ds0/debian/control --- assimp-5.0.1~ds0/debian/control 2021-10-06 09:02:14.0 +0200 +++ assimp-5.0.1~ds0/debian/control 2021-10-08 20:49:28.0 +0200 @@ -15,8 +15,10 @@ libstb-dev, libutfcpp-dev, zlib1g-dev | libz-dev, - python3:any | python3-all:any | python3-dev:any | python3-all-dev:any | dh-sequence-python3, doxygen, +Build-Depends-Indep: + dh-sequence-python3, + python3, Rules-Requires-Root: no Vcs-Git: https://salsa.debian.org/debian/assimp.git Vcs-Browser: https://salsa.debian.org/debian/assimp diff --minimal -Nru assimp-5.0.1~ds0/debian/rules assimp-5.0.1~ds0/debian/rules --- assimp-5.0.1~ds0/debian/rules 2021-10-06 09:02:14.0 +0200 +++ assimp-5.0.1~ds0/debian/rules
Bug#1000255: mpv: autopkgtest failures
Source: mpv Version: 0.34.0-1 Severity: serious Hello, the last version 0.34.0 is regressed on arm64 armhf and probably other architectures. Look, e.g. https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-mpv/16812363/log.gz (Reading database ... 16518 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [18:11:22]: test unittests: [--- === python3.9 === Segmentation fault autopkgtest [18:11:43]: test unittests: ---] autopkgtest [18:11:43]: test unittests: - - - - - - - - - - results - - - - - - - - - - unittestsFAIL non-zero exit status 139 autopkgtest [18:11:43]: summary unittestsFAIL non-zero exit status 139 I don't know which update triggered the regression, if the program itself or something else in the toolchain. Can you please have a look? https://ci.debian.net/packages/p/python-mpv/testing/arm64/ thanks Gianfranco
Processed (with 2 errors): severity of 987468 is serious, forcibly merging 987468 999816, tagging 987468
Processing commands for cont...@bugs.debian.org: > severity 987468 serious Bug #987468 [src:rpm] rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev Severity set to 'serious' from 'important' > forcemerge 987468 999816 Bug #987468 [src:rpm] rpm: Please drop the build-dependencies against libsepol1-dev and libsemanage1-dev Unable to merge bugs because: package of #999816 is 'rpm' not 'src:rpm' Failed to forcibly merge 987468: Did not alter merged bugs. > tags 987468 + pending Failed to alter tags of Bug 987468: failed to get lock on /srv/bugs.debian.org/spool/lock/987468 -- Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. Unable to lock /srv/bugs.debian.org/spool/lock/987468 Resource temporarily unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692. at /usr/local/lib/site_perl/Debbugs/Common.pm line 650. > thanks Stopping processing here. Please contact me if you need assistance. -- 987468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987468 999816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
