Processed: bts
Processing commands for cont...@bugs.debian.org: > block 996042 by 1000252 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 1000247 964170 1000244 1000251 1000248 1000242 1000246 1000243 1000245 1000249 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000252 > thanks Stopping processing here. Please contact me if you need assistance. -- 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ITP: decko -- useful Javascript decorators
Processing commands for cont...@bugs.debian.org: > owner 1000251 Daniel Baumann Bug #1000251 [wnpp] ITP: decko -- useful Javascript decorators Owner recorded as Daniel Baumann . > tag 1000251 pending Bug #1000251 [wnpp] ITP: decko -- useful Javascript decorators Added tag(s) pending. > block 996042 by 1000251 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 1000247 1000243 1000244 1000245 1000242 1000246 1000249 964170 1000248 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000251 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000251 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bts
Processing commands for cont...@bugs.debian.org: > block 996042 by 1000249 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 1000247 1000242 1000244 1000245 1000243 964170 1000246 1000248 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000249 > thanks Stopping processing here. Please contact me if you need assistance. -- 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Patch
Processing control commands: > tags -1 + patch Bug #984321 [src:ring] ring: ftbfs with GCC-11 Added tag(s) patch. -- 984321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bts
Processing commands for cont...@bugs.debian.org: > block 996042 by 1000247 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 964170 1000243 1000245 1000246 1000242 1000244 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000247 > block 996042 by 1000248 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 1000246 964170 1000243 1000245 1000244 1000247 1000242 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000248 > thanks Stopping processing here. Please contact me if you need assistance. -- 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bts
Processing commands for cont...@bugs.debian.org: > block 996042 by 1000246 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 1000243 1000242 1000245 1000244 964170 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000246 > thanks Stopping processing here. Please contact me if you need assistance. -- 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bts
Processing commands for cont...@bugs.debian.org: > block 996042 by 1000244 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 964170 1000243 1000242 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000244 > block 996042 by 1000245 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 1000242 1000243 1000244 964170 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000245 > thanks Stopping processing here. Please contact me if you need assistance. -- 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bts
Processing commands for cont...@bugs.debian.org: > unblock 1000242 by 996042 Bug #1000242 [node-css-loader] new upstream required for ttyd 1000242 was blocked by: 996042 1000242 was not blocking any bugs. Removed blocking bug(s) of 1000242: 996042 > block 996042 by 1000242 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 964170 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000242 > block 996042 by 1000243 Bug #996042 [ttyd] Missing sources for the html part 996042 was blocked by: 964170 1000242 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 1000243 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000242 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1000224 marked as pending in plastimatch
Processing control commands: > tag -1 pending Bug #1000224 [src:plastimatch] plastimatch: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. Added tag(s) pending. -- 1000224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000224: marked as pending in plastimatch
Control: tag -1 pending Hello, Bug #1000224 in plastimatch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/plastimatch/-/commit/4b0e11e975a2606d60c784ebd2fdd06faaba3b45 dcmtk 3.6.6 requires C++ >= 14 Closes: #1000224 (this message was generated automatically) -- Greetings https://bugs.debian.org/1000224
Processed: bts
Processing commands for cont...@bugs.debian.org: > block 1000242 by 996042 Bug #1000242 [node-css-loader] new upstream required for ttyd 1000242 was not blocked by any bugs. 1000242 was not blocking any bugs. Added blocking bug(s) of 1000242: 996042 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999515 is serious, severity of 999517 is serious, severity of 999522 is serious ...
Processing commands for cont...@bugs.debian.org:
> #
> https://tracker.debian.org/news/1278745/accepted-numpy-11214-2-source-into-unstable/
> severity 999515 serious
Bug #999515 [src:imbalanced-learn] imbalanced-learn: FTBFS with numpy 1.21 (in
experimental): dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999517 serious
Bug #999517 [src:qutip] qutip: FTBFS with numpy 1.21 (in experimental):
distutils.errors.DistutilsError: Command '['/usr/bin/python3.9', '-m', 'pip',
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpo4aol4ev',
'--quiet', 'numpy<1.20,>=1.16.6']' returned non-zero exit status 1.
Severity set to 'serious' from 'important'
> severity 999522 serious
Bug #999522 [src:brian] brian: FTBFS with numpy 1.21 (in experimental):
TypeError: logical_and() takes from 2 to 3 positional arguments but 1 were given
Severity set to 'serious' from 'important'
> severity 999523 serious
Bug #999523 [src:python-skbio] python-skbio: FTBFS with numpy 1.21 (in
experimental): dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999524 serious
Bug #999524 [src:python-language-server] python-language-server: FTBFS with
numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999525 serious
Bug #999525 [src:bmtk] bmtk: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Severity set to 'serious' from 'important'
> severity 999526 serious
Bug #999526 [src:mdp] mdp: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Severity set to 'serious' from 'important'
> severity 999527 serious
Bug #999527 [src:joblib] joblib: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Severity set to 'serious' from 'important'
> severity 999528 serious
Bug #999528 [src:scikit-learn] scikit-learn: FTBFS with numpy 1.21 (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 999530 serious
Bug #999530 [src:python-escript] python-escript: FTBFS with numpy 1.21 (in
experimental): ImportError: cannot import name 'griddata' from
'matplotlib.mlab' (/usr/lib/python3/dist-packages/matplotlib/mlab.py)
Severity set to 'serious' from 'important'
> severity 999532 serious
Bug #999532 [src:astroquery] astroquery: FTBFS with numpy 1.21 (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 999535 serious
Bug #999535 [src:python-ltfatpy] python-ltfatpy: FTBFS with numpy 1.21 (in
experimental): dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
Severity set to 'serious' from 'important'
> severity 999538 serious
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
Severity set to 'serious' from 'important'
> severity 999539 serious
Bug #999539 [src:python-quantities] python-quantities: FTBFS with numpy 1.21
(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.
--
999515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999515
999517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999517
999522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999522
999523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999523
999524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999524
999525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999525
999526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999526
999527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999527
999528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999528
999530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999530
999532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999532
999535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999535
999538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999538
999539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#995318: marked as done (numpy: Does not build from source in current unstable)
Your message dated Sat, 20 Nov 2021 05:03:34 + with message-id and subject line Bug#995318: fixed in numpy 1:1.21.4-2 has caused the Debian Bug report #995318, regarding numpy: Does not build from source in current unstable 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.) -- 995318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: numpy Version: 1:1.19.5-1 Severity: serious Tags: ftbfs Justification: FTBFS Hi, when trying to build numpy 1.19.5-1 in a recent sid chroot I get DISTUTILS.rst.txt:386: WARNING: Unparseable C cross-reference: '/**end repeat1**/' Invalid C declaration: Expected identifier in nested name. [error at 0] /**end repeat1**/ ^ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 280, in build_main app.build(args.force_all, filenames) File "/usr/lib/python3/dist-packages/sphinx/application.py", line 337, in build self.builder.build_update() File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 293, in build_update self.build(to_build, File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 357, in build self.write(docnames, list(updated_docnames), method) File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 531, in write self._write_serial(sorted(docnames)) File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 541, in _write_serial self.write_doc(docname, doctree) File "/usr/lib/python3/dist-packages/sphinx/builders/html/__init__.py", line 626, in write_doc self.docwriter.write(doctree, destination) File "/usr/lib/python3/dist-packages/docutils/writers/__init__.py", line 78, in write self.translate() File "/usr/lib/python3/dist-packages/sphinx/writers/html.py", line 70, in translate self.document.walkabout(visitor) File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 214, in walkabout if child.walkabout(visitor): File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 214, in walkabout if child.walkabout(visitor): File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 214, in walkabout if child.walkabout(visitor): [Previous line repeated 1 more time] File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 206, in walkabout visitor.dispatch_visit(self) File "/usr/lib/python3/dist-packages/sphinx/util/docutils.py", line 477, in dispatch_visit method(node) File "/usr/lib/python3/dist-packages/sphinx/writers/html5.py", line 417, in visit_literal_block highlighted = self.highlighter.highlight_block( File "/usr/lib/python3/dist-packages/sphinx/highlighting.py", line 149, in highlight_block lexer = self.get_lexer(source, lang, opts, force, location) File "/usr/lib/python3/dist-packages/sphinx/highlighting.py", line 127, in get_lexer lexer = lexer_classes[lang](**opts) TypeError: 'NumPyLexer' object is not callable Exception occurred: File "/usr/lib/python3/dist-packages/sphinx/highlighting.py", line 127, in get_lexer lexer = lexer_classes[lang](**opts) TypeError: 'NumPyLexer' object is not callable The full traceback has been saved in /tmp/sphinx-err-h3bd2cwr.log, if you want to report the issue to the developers. Please also report this if it was a user error, so that a better error message can be provided next time. Please see the attached full build log. Kind regards Andreas. -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled numpy_1.19.5-1.1_amd64.build.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: numpy Source-Version: 1:1.21.4-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of numpy, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution
Processed: Re: libjs-xterm: update to newer major release for bullseye
Processing commands for cont...@bugs.debian.org: > retitle 964170 new upstream (4.15) Bug #964170 [libjs-xterm] libjs-xterm: update to newer major release for bullseye Changed Bug title to 'new upstream (4.15)' from 'libjs-xterm: update to newer major release for bullseye'. > severity 964170 normal Bug #964170 [libjs-xterm] new upstream (4.15) Severity set to 'normal' from 'wishlist' > block 996042 by 964170 Bug #996042 [ttyd] Missing sources for the html part 996042 was not blocked by any bugs. 996042 was not blocking any bugs. Added blocking bug(s) of 996042: 964170 > thanks Stopping processing here. Please contact me if you need assistance. -- 964170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964170 996042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999373: marked as done (python-dmidcode ftbfs with Python 3.10 (test failures))
Your message dated Sat, 20 Nov 2021 03:51:02 + with message-id and subject line Bug#999373: fixed in python-dmidecode 3.12.2-13 has caused the Debian Bug report #999373, regarding python-dmidcode 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.) -- 999373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-dmidecode Version: 3.12.2-12 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python-dmidecode ftbfs with python3-defaults from experimental: [...] debian/rules override_dh_auto_test make[1]: Entering directory '/<>' set -e ;\ for python in python3.10 python3.9; do \ /usr/bin/make PY_BIN=$python -C unit-tests test; \ done make[2]: Entering directory '/<>/unit-tests' python3.10 unit -vv * Testing for command line version of dmidecode ...WARN * Running test as normal user, some tests will be skipped * Creation of temporary files...PASS * Importing module...FAIL No module named 'dmidecode' make[2]: *** [Makefile:4: test] Error 1 make[2]: Leaving directory '/<>/unit-tests' make[1]: *** [debian/rules:29: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: build] Error 2 the extension builds, but apparently isn't found by the tests. --- End Message --- --- Begin Message --- Source: python-dmidecode Source-Version: 3.12.2-13 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-dmidecode, 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 python-dmidecode package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Nov 2021 23:24:23 -0400 Source: python-dmidecode Architecture: source Version: 3.12.2-13 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Stefano Rivera Closes: 999373 Changes: python-dmidecode (3.12.2-13) unstable; urgency=medium . * Team upload. * Patch: Support Python 3.10's 2-digit minor version in the test runner. (Closes: #999373) Checksums-Sha1: 282a2751a6745e312491877334ad103119936de1 1604 python-dmidecode_3.12.2-13.dsc 25a4122e7fd5ca238c38dd76b475725c993ea652 7916 python-dmidecode_3.12.2-13.debian.tar.xz c0672f93e574a3b9010b20031f7a572490281bbf 6161 python-dmidecode_3.12.2-13_source.buildinfo Checksums-Sha256: 632fb64c848584a9943e115358e3b3ad88b1bdb791fda869dd53b91f77845e0b 1604 python-dmidecode_3.12.2-13.dsc 6c7a56e243a7655f1a3eca48feb257b0ceb659ed651a1ca23d0783e8eb39b08b 7916 python-dmidecode_3.12.2-13.debian.tar.xz de2430e1bf7b9ec8dafda92aaf4addd1e5042937737d6ec7714b8e474d1ec9b0 6161 python-dmidecode_3.12.2-13_source.buildinfo Files: 39313cef4ac457310fb87bd34b3ed72a 1604 python optional python-dmidecode_3.12.2-13.dsc aef410472bf444f5e9073bccb2bae7ee 7916 python optional python-dmidecode_3.12.2-13.debian.tar.xz 2e4b425ede078985b1bf4b13edacdc51 6161 python optional python-dmidecode_3.12.2-13_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYZhq3RQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2PgaAP48U/8OwSmXqlnqhhWHEBW+6+bYovC2 OsmPh1IOJgQ11QEAo42Ns4OO45FQGXgeQAfdQT3HFKs4hK5dDFC/S/UwAws= =NLF2 -END PGP SIGNATURE End Message ---
Bug#999385: marked as done (python-pyalsa ftbfs with Python 3.10)
Your message dated Sat, 20 Nov 2021 03:04:52 + with message-id and subject line Bug#999385: fixed in python-pyalsa 1.1.6-3 has caused the Debian Bug report #999385, regarding python-pyalsa 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.) -- 999385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pyalsa Version: 1.1.6-2 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python-pyalsa ftbfs with python3-defaults from experimental: x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.10 -c pyalsa/alsahcontrol.c -o build/temp.linux-x86_64-3.10/pyalsa/alsahcontrol.o In file included from /usr/include/python3.10/tupleobject.h:39, from /usr/include/python3.10/Python.h:91, from pyalsa/common.h:25, from pyalsa/alsahcontrol.c:22: pyalsa/alsahcontrol.c: In function ‘element_callback’: /usr/include/python3.10/cpython/tupleobject.h:26:36: error: void value not ignored as it ought to be 26 | #define PyTuple_SET_ITEM(op, i, v) ((void)(_PyTuple_CAST(op)->ob_item[i] = v)) |^ pyalsa/alsahcontrol.c:1546:21: note: in expansion of macro ‘PyTuple_SET_ITEM’ 1546 | if (PyTuple_SET_ITEM(t, 0, (PyObject *)pyhelem)) | ^~~~ error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 E: pybuild pybuild:354: build: plugin distutils failed with: exit code=1: /usr/bin/python3.10 setup.py build --- End Message --- --- Begin Message --- Source: python-pyalsa Source-Version: 1.1.6-3 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-pyalsa, 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 python-pyalsa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Nov 2021 22:38:05 -0400 Source: python-pyalsa Architecture: source Version: 1.1.6-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 999385 Changes: python-pyalsa (1.1.6-3) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. * Patch: Python 3.10 support (fix PyTuple_SET_ITEM() usage). (Closes: #999385) . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Debian Janitor ] * Bump debhelper from old 11 to 12. * Bump debhelper from old 12 to 13. Checksums-Sha1: cd5815b6f8186fb8f12f16fab32118f4e80b0af5 1479 python-pyalsa_1.1.6-3.dsc d57f0567ef6e11ac9ac80c53670909f452018e76 3276 python-pyalsa_1.1.6-3.debian.tar.xz 418acec2e71715868a0ac6409b348419692d9931 6137 python-pyalsa_1.1.6-3_source.buildinfo Checksums-Sha256: b34c7f00f5db489e5060c343f471267e5def9919b1a32307cb1827fd64ef0e86 1479 python-pyalsa_1.1.6-3.dsc 253ae327cdd751a9b2be9b4c3fad8986f9cb272f1bb44a1f7903a620b20a9cd8 3276 python-pyalsa_1.1.6-3.debian.tar.xz 306d43ad9342fc2db8411a36f4dcbeb4feafcdabc6b16e4e3b46c07a6e3cdf20 6137 python-pyalsa_1.1.6-3_source.buildinfo Files: 19fb1765bda36559a7bbf60ac6157b61 1479 python optional python-pyalsa_1.1.6-3.dsc 9750f354c02bdbaece49ef6238116952 3276 python optional python-pyalsa_1.1.6-3.debian.tar.xz ef16577951ddaa7b0fba1a4660fb6310 6137 python optional python-pyalsa_1.1.6-3_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYZhfrRQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2CBWAP4+Qg1k3W0svrVaLojpi+XBN7j++c06 OYHalYDiUG0LvAD/aYWJg7DNvl3oTU1LuyDbNE1vZ1LNOQgVj30DFEnCzgg= =0Vkq
Bug#999381: marked as done (python-pairix ftbfs with Python 3.10 (test failures))
Your message dated Sat, 20 Nov 2021 03:04:46 +
with message-id
and subject line Bug#999381: fixed in python-pairix 0.3.7-4.1
has caused the Debian Bug report #999381,
regarding python-pairix 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.)
--
999381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pairix
Version: 0.3.7-4
Severity: important
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10
python-pairix ftbfs with python3-defaults from experimental:
I: pybuild pybuild:285: cp -a /<>/samples
/<>/.pybuild/cpython3_3.10_pairix/build; cp -a
/<>/VERSION.txt
/<>/.pybuild/cpython3_3.10_pairix/build;
I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_pairix/build;
python3.10 -m pytest test
= test session starts ==
platform linux -- Python 3.10.0+, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /<>
collected 0 items / 2 errors
ERRORS
__ ERROR collecting .pybuild/cpython3_3.10_pairix/build/test/test_oldindex.py __
test/test_oldindex.py:180: in
class PairixTest(unittest.TestCase):
test/test_oldindex.py:181: in PairixTest
regions = read_vcf(TEST_FILE_1D)
test/test_oldindex.py:68: in read_vcf
for line in gzip.open(filename):
E ValueError: readline of closed file
_ ERROR collecting .pybuild/cpython3_3.10_pairix/build/test/test_oldindex2.py __
test/test_oldindex2.py:179: in
class PairixTest(unittest.TestCase):
test/test_oldindex2.py:180: in PairixTest
regions = read_vcf(TEST_FILE_1D)
test/test_oldindex2.py:67: in read_vcf
for line in gzip.open(filename):
E ValueError: readline of closed file
=== warnings summary ===
test/test_oldindex.py:58
/<>/.pybuild/cpython3_3.10_pairix/build/test/test_oldindex.py:58:
DeprecationWarning: invalid escape sequence '\s'
fields = line.rstrip().split('\s+')
test/test_oldindex2.py:57
/<>/.pybuild/cpython3_3.10_pairix/build/test/test_oldindex2.py:57:
DeprecationWarning: invalid escape sequence '\s'
fields = line.rstrip().split('\s+')
-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info
ERROR test/test_oldindex.py - ValueError: readline of closed file
ERROR test/test_oldindex2.py - ValueError: readline of closed file
!!! Interrupted: 2 errors during collection
2 warnings, 2 errors in 0.55s =
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=2: cd
/<>/.pybuild/cpython3_3.10_pairix/build; python3.10 -m pytest test
--- End Message ---
--- Begin Message ---
Source: python-pairix
Source-Version: 0.3.7-4.1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-pairix, 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 python-pairix package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 19 Nov 2021 22:23:41 -0400
Source: python-pairix
Architecture: source
Version: 0.3.7-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Stefano Rivera
Closes: 999381
Changes:
python-pairix (0.3.7-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Patch: Avoid tests failing under Python 3.10. (Closes: #999381)
Checksums-Sha1:
831319cdc2e50e3900507d5ef72764b639a4937d 1634 python-pairix_0.3.7-4.1.dsc
57259dc151c779bb8ddb2de067c7bbebb179f3bd 4600
python-pairix_0.3.7-4.1.debian.tar.xz
2091bb1eda25a164a01ad00026f03ced5132ae6d 6399
python-pairix_0.3.7-4.1_source.buildinfo
Checksums-Sha256:
42922ec9cc34216e145aac1b1253f1261c9fe91d33911bdd00572a0fa3d601a5 1634
python-pairix_0.3.7-4.1.dsc
8eda9ac507b6e51c981c75bae57e13b36b56160aa8181a41bcb6712e94641582 4600
Bug#999385: marked as pending in python-pyalsa
Control: tag -1 pending Hello, Bug #999385 in python-pyalsa 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-pyalsa/-/commit/cd02a79db2266553bcf515005ebc3e83df5c646c Patch: Python 3.10 support (fix PyTuple_SET_ITEM() usage). (Closes: #999385) (this message was generated automatically) -- Greetings https://bugs.debian.org/999385
Processed: Bug#999385 marked as pending in python-pyalsa
Processing control commands: > tag -1 pending Bug #999385 [src:python-pyalsa] python-pyalsa ftbfs with Python 3.10 Added tag(s) pending. -- 999385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999381: python-pairix: diff for NMU version 0.3.7-4.1
Control: tags 999381 + patch
Dear maintainer,
I've prepared an NMU for python-pairix (versioned as 0.3.7-4.1). The diff
is attached to this message.
Regards.
SR
diff -Nru python-pairix-0.3.7/debian/changelog python-pairix-0.3.7/debian/changelog
--- python-pairix-0.3.7/debian/changelog 2021-10-01 10:07:39.0 -0400
+++ python-pairix-0.3.7/debian/changelog 2021-11-19 22:21:23.0 -0400
@@ -1,3 +1,10 @@
+python-pairix (0.3.7-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Patch: Avoid tests failing under Python 3.10. (Closes: #999381)
+
+ -- Stefano Rivera Fri, 19 Nov 2021 22:21:23 -0400
+
python-pairix (0.3.7-4) unstable; urgency=medium
* Fix watchfile to detect new versions on github
diff -Nru python-pairix-0.3.7/debian/patches/python3.10 python-pairix-0.3.7/debian/patches/python3.10
--- python-pairix-0.3.7/debian/patches/python3.10 1969-12-31 20:00:00.0 -0400
+++ python-pairix-0.3.7/debian/patches/python3.10 2021-11-19 22:21:10.0 -0400
@@ -0,0 +1,330 @@
+Description: Avoid a Python3.10 regression in iterating GzipFiles
+ Open the file with a context manager, so we're holding onto a reference to it,
+ for the lifetime of the iteration.
+ This avoids hitting https://bugs.python.org/issue45475 which affects
+ python3.10 3.10.0-4 in Debian.
+
+Bug-Debian: https://bugs.debian.org/999381
+Bug-cpython: https://bugs.python.org/issue45475
+Forwarded: https://github.com/4dn-dcic/pairix/pull/71
+Author: Stefano Rivera
+--- a/test/test_oldindex.py
b/test/test_oldindex.py
+@@ -36,45 +36,48 @@
+ def get_header(filename, meta_char='#'):
+ """Read gzipped file and retrieve lines beginning with '#'."""
+ retval = []
+-for line in gzip.open(filename):
+-try:
+-line = line.decode('utf-8')
+-except AttributeError:
+-pass
+-if line.startswith(meta_char):
+-retval.append(line.rstrip())
++with gzip.open(filename) as f:
++for line in f:
++try:
++line = line.decode('utf-8')
++except AttributeError:
++pass
++if line.startswith(meta_char):
++retval.append(line.rstrip())
+ return retval
+
+
+ def get_chromsize(filename):
+ """Read gzipped file and retrieve chromsize."""
+ retval = []
+-for line in gzip.open(filename):
+-try:
+-line = line.decode('utf-8')
+-except AttributeError:
+-pass
+-if line.startswith('#chromsize: '):
+-fields = line.rstrip().split('\s+')
+-chrname = fields[1]
+-chrsize = fields[2]
+-retval.append([chrname, chrsize])
++with gzip.open(filename) as f:
++for line in f:
++try:
++line = line.decode('utf-8')
++except AttributeError:
++pass
++if line.startswith('#chromsize: '):
++fields = line.rstrip().split('\s+')
++chrname = fields[1]
++chrsize = fields[2]
++retval.append([chrname, chrsize])
+ return retval
+
+
+ def read_vcf(filename):
+ """Read a VCF file and return a list of [chrom, start, end] items."""
+ retval = []
+-for line in gzip.open(filename):
+-try:
+-line = line.decode('utf-8')
+-except AttributeError:
+-pass
+-fields = line.rstrip().split('\t')
+-chrom = fields[0]
+-start = fields[1]
+-end = fields[1]
+-retval.append([chrom, start, end])
++with gzip.open(filename) as f:
++for line in f:
++try:
++line = line.decode('utf-8')
++except AttributeError:
++pass
++fields = line.rstrip().split('\t')
++chrom = fields[0]
++start = fields[1]
++end = fields[1]
++retval.append([chrom, start, end])
+ return retval
+
+
+@@ -83,20 +86,21 @@
+ or undetermined. Do this by testing string values of """
+ is_juicer = False
+ is_4DN = False
+-for line in gzip.open(filename):
+-try:
+-line = line.decode('utf-8')
+-except AttributeError:
+-pass
+-fields = line.rstrip().split(delimiter)
+-if len(fields)>=6 and is_str(fields[2]) and is_str(fields[6]):
+-is_juicer = True
+-if is_str(fields[2]) and is_str(fields[4]):
+-is_4DN = True
+-if not is_juicer and is_4DN:
+-return '4DN'
+-elif is_juicer:
+-return 'juicer'
++with gzip.open(filename) as f:
++for line in f:
++try:
++line = line.decode('utf-8')
++except AttributeError:
++pass
++fields = line.rstrip().split(delimiter)
++if len(fields)>=6 and is_str(fields[2]) and is_str(fields[6]):
++is_juicer = True
++if
Processed: python-pairix: diff for NMU version 0.3.7-4.1
Processing control commands: > tags 999381 + patch Bug #999381 [src:python-pairix] python-pairix ftbfs with Python 3.10 (test failures) Added tag(s) patch. -- 999381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#999381: python-pairix ftbfs with Python 3.10 (test failures)
Processing control commands: > affects -1 python3.10 Bug #999381 [src:python-pairix] python-pairix ftbfs with Python 3.10 (test failures) Added indication that 999381 affects python3.10 -- 999381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999381: python-pairix ftbfs with Python 3.10 (test failures)
Control: affects -1 python3.10 Hi Matthias (2021.11.10_11:31:16_-0400) This looks like fallout from https://bugs.python.org/issue45475, a Python 3.10 regression. python-pairix is easily patched to avoid hitting the bug, though. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#1000237: pygame: FTBFS with python3.10
Package: pygame
Version: 1.9.6+dfsg-4
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Dear maintainers,
Now that python3.10 is a supported python version in unstable, pygame fails
to build from source.
I wasn't able to find a direct fix for these issues in the upstream git, so
I've prepared the attached patch instead. I've uploaded this patch to
Ubuntu to fix the failure in question. Please consider including it in
Debian as well.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pygame-1.9.6+dfsg/debian/patches/python-3.10.patch
pygame-1.9.6+dfsg/debian/patches/python-3.10.patch
--- pygame-1.9.6+dfsg/debian/patches/python-3.10.patch 1969-12-31
16:00:00.0 -0800
+++ pygame-1.9.6+dfsg/debian/patches/python-3.10.patch 2021-11-19
17:24:50.0 -0800
@@ -0,0 +1,115 @@
+Description: fix compatibility with python 3.10
+ Python 3.10 requires use of Py_ssize_t instead of int.
+ Also, certain math operations are now returning floats instead of ints,
+ so adjust.
+Author: Steve Langasek
+Last-Update: 2021-11-19
+
+Index: pygame-1.9.6+dfsg/src_c/mixer.c
+===
+--- pygame-1.9.6+dfsg.orig/src_c/mixer.c
pygame-1.9.6+dfsg/src_c/mixer.c
+@@ -24,6 +24,7 @@
+ * mixer module for pygame
+ */
+ #define PYGAMEAPI_MIXER_INTERNAL
++#define PY_SSIZE_T_CLEAN
+ #include "pygame.h"
+
+ #include "pgcompat.h"
+@@ -529,7 +530,7 @@
+ {
+ static char *kwids[] = {"frequency", "size", "channels",
+ "buffer","devicename", "allowedchanges",
NULL};
+-int dname_size = 0;
++Py_ssize_t dname_size = 0;
+
+ request_frequency = 0;
+ request_size = 0;
+Index: pygame-1.9.6+dfsg/src_c/sdlmain_osx.m
+===
+--- pygame-1.9.6+dfsg.orig/src_c/sdlmain_osx.m
pygame-1.9.6+dfsg/src_c/sdlmain_osx.m
+@@ -19,6 +19,7 @@
+
+ /* Mac OS X functions to accommodate the fact SDLMain.m is not included */
+
++#define PY_SSIZE_T_CLEAN
+ #include "pygame.h"
+
+ #include
+@@ -234,7 +235,7 @@
+ _InstallNSApplication(PyObject* self, PyObject* arg)
+ {
+ char* icon_data = NULL;
+-int data_len = 0;
++Py_ssize_t data_len = 0;
+ PYGPYGSDLApplicationDelegate *sdlApplicationDelegate = NULL;
+
+ NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
+Index: pygame-1.9.6+dfsg/src_c/overlay.c
+===
+--- pygame-1.9.6+dfsg.orig/src_c/overlay.c
pygame-1.9.6+dfsg/src_c/overlay.c
+@@ -23,6 +23,7 @@
+ * Dmitry Borisov
+ */
+
++#define PY_SSIZE_T_CLEAN
+ #include
+
+ #include "pygame.h"
+@@ -67,7 +68,8 @@
+ {
+ SDL_Rect cRect;
+ // Parse data params for frame
+-int ls_y, ls_u, ls_v, y;
++Py_ssize_t ls_y, ls_u, ls_v;
++int y;
+ unsigned char *src_y = 0, *src_u = 0, *src_v = 0;
+
+ if (PyTuple_Size(args)) {
+Index: pygame-1.9.6+dfsg/src_c/scrap.c
+===
+--- pygame-1.9.6+dfsg.orig/src_c/scrap.c
pygame-1.9.6+dfsg/src_c/scrap.c
+@@ -28,6 +28,7 @@
+
+ #include "SDL_syswm.h"
+
++#define PY_SSIZE_T_CLEAN
+ #include "scrap.h"
+
+ #include "pygame.h"
+@@ -276,7 +277,7 @@
+ static PyObject *
+ _scrap_put_scrap(PyObject *self, PyObject *args)
+ {
+-int scraplen;
++Py_ssize_t scraplen;
+ char *scrap = NULL;
+ char *scrap_type;
+ PyObject *tmp;
+Index: pygame-1.9.6+dfsg/src_py/sprite.py
+===
+--- pygame-1.9.6+dfsg.orig/src_py/sprite.py
pygame-1.9.6+dfsg/src_py/sprite.py
+@@ -1346,14 +1346,14 @@
+ leftrect = left.rect
+ width = leftrect.width
+ height = leftrect.height
+-leftrect = leftrect.inflate(width * ratio - width,
+-height * ratio - height)
++leftrect = leftrect.inflate(int(width * ratio - width),
++int(height * ratio - height))
+
+ rightrect = right.rect
+ width = rightrect.width
+ height = rightrect.height
+-rightrect = rightrect.inflate(width * ratio - width,
+- height * ratio - height)
++rightrect = rightrect.inflate(int(width * ratio - width),
++ int(height * ratio - height))
+
+ return leftrect.colliderect(rightrect)
+
diff -Nru pygame-1.9.6+dfsg/debian/patches/series
pygame-1.9.6+dfsg/debian/patches/series
--- pygame-1.9.6+dfsg/debian/patches/series 2020-10-18 08:08:21.0
-0700
+++
Bug#1000233: php-remctl lost its phpapi-20190902 dependency
Package: php-remctl Version: 3.17-1 Severity: serious Tags: bookworm sid After the src:remctl rebuild to add Python 3.10 as supported version, php-remctl lost its phpapi-20190902 dependency: Package: php-remctl Source: remctl Version: 3.17-1 Installed-Size: 109 Depends: php-common (>= 1:7.0+33~), phpapi-20190902, libc6 (>= 2.14), libremctl1 (>= 3.1) Package: php-remctl Source: remctl (3.17-1) Version: 3.17-1+b2 Installed-Size: 106 Depends: php-common (>= 1:7.0+33~), libc6 (>= 2.14), libremctl1 (>= 3.1) At first sight the contents of the 3.17-1+b2 package looks correct. There is no obvious build log difference between 3.17-1+b1 and 3.17-1+b2 (obvious for me, who knows nothing about PHP). Debian PHP Maintainers are in Cc.
Bug#996228: marked as done (ruby-ffaker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_ssn_with_from_to(TestSSNSE): ArgumentError: wrong number of arguments (given 4, expected 3))
Your message dated Fri, 19 Nov 2021 23:36:55 + with message-id and subject line Bug#996228: fixed in ruby-ffaker 2.13.0-3 has caused the Debian Bug report #996228, regarding ruby-ffaker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_ssn_with_from_to(TestSSNSE): ArgumentError: wrong number of arguments (given 4, expected 3) 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.) -- 996228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-ffaker Version: 2.13.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-ffaker 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): > Error: test_ssn_with_from_to(TestSSNSE): ArgumentError: wrong number of > arguments (given 4, expected 3) > /<>/test/helper.rb:48:in `assert_between' > /<>/test/helper.rb:62:in `block (3 levels) in > ' > /<>/test/helper.rb:55:in `block in assert_random' > /<>/test/helper.rb:54:in `times' > /<>/test/helper.rb:54:in `assert_random' > /<>/test/helper.rb:62:in `block (2 levels) in > ' > /<>/test/test_ssn_se.rb:35:in `test_ssn_with_from_to' > 32: from = Time.local(1980, 2, 28) > 33: to = Time.local(2000, 2, 28) > 34: > => 35: assert_random_between(from, to, exclude_end: true) do > 36: ssn = FFaker::SSNSE.ssn(from: from, to: to) > 37: year = ssn[0..3].to_i > 38: month = ssn[4..5].to_i > === > : (0.001016) > test_ssn_with_gender: .: (0.000317) > TestSemVer: > test_next: .: (0.000199) > test_next_is_deterministic: .: (0.016682) > TestSkill: > test_specialties: .: (0.000446) > test_specialties_is_deterministic: .: (0.000236) > test_specialty: .: (0.87) > test_specialty_is_deterministic:.: (0.000149) > test_tech_skill:.: (0.000202) > test_tech_skill_is_deterministic: .: (0.000144) > test_tech_skills: .: (0.87) > test_tech_skills_is_deterministic: .: (0.000148) > TestSportPL: > test_name: .: (0.000176) > test_name_is_deterministic: .: (0.000148) > test_summer:.: (0.87) > test_summer_is_deterministic: .: (0.000130) > test_winter:.: (0.86) > test_winter_is_deterministic: .: (0.000155) > TestSportUS: > test_name: .: (0.000324) > test_name_is_deterministic: .: (0.000151) > TestSports: > test_name: [name] is deprecated. > For US sports please use the SportUS module > .: (0.000318) > test_name_is_deterministic: [name] is deprecated. > For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > [name] is deprecated. For US sports please use the SportUS module > .: (0.000196) > TestString: > test_atom_plus: .: (0.000383) > test_atom_question: .: (0.000185) > test_atom_sets: .: (0.000272) > test_atom_star: .: (0.000268) > test_atoms: .: (0.000221) > test_braces:
Bug#996117: Update after uploading Rails 6.1
Am Samstag, dem 20.11.2021 um 00:18 +0100 schrieb Daniel Leidert: > With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of > errors like this: > > Failure: > ActionController::Serialization::ImplicitSerializerTest#test_render_array_using > _custom_root > [/<>/test/action_controller/serialization_test.rb:186]: > --- expected > +++ actual > @@ -1 +1 @@ > -"application/json" > +"application/json; charset=utf-8" > > > rails test /<>/test/action_controller/serialization_test.rb:181 > I think that this commit was supposed to fix this test issue: https://github.com/rails-api/active_model_serializers/commit/55a6b23cd84395029aa92605f8aae73f37f57c4a However, it doesn't work and this issue says that it has a different meaning: https://github.com/rails/rails/issues/40376 It is possible that this problem is unsolved at the moment. -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#1000231: ceres-solver: error: variable or field ‘it’ declared void
Source: ceres-solver Version: 1.14.0-14 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | In file included from /<>/internal/ceres/residual_block_test.cc:33: | /<>/internal/ceres/gtest/gtest.h: In instantiation of ‘void testing::internal::DefaultPrintTo(testing::internal::IsContainer, testing::internal::false_type, const C&, std::ostream*) [with C = Eigen::Matrix; testing::internal::IsContainer = int; testing::internal::false_type = testing::internal::bool_constant; std::ostream = std::basic_ostream]’: | /<>/internal/ceres/gtest/gtest.h:10546:17: required from ‘void testing::internal::PrintTo(const T&, std::ostream*) [with T = Eigen::Matrix; std::ostream = std::basic_ostream]’ | /<>/internal/ceres/gtest/gtest.h:10776:12: required from ‘static void testing::internal::UniversalPrinter::Print(const T&, std::ostream*) [with T = Eigen::Matrix; std::ostream = std::basic_ostream]’ | /<>/internal/ceres/gtest/gtest.h:10925:30: required from ‘void testing::internal::UniversalPrint(const T&, std::ostream*) [with T = Eigen::Matrix; std::ostream = std::basic_ostream]’ | /<>/internal/ceres/gtest/gtest.h:10853:19: required from ‘static void testing::internal::UniversalTersePrinter::Print(const T&, std::ostream*) [with T = Eigen::Matrix; std::ostream = std::basic_ostream]’ | /<>/internal/ceres/gtest/gtest.h:11051:44: required from ‘std::string testing::PrintToString(const T&) [with T = Eigen::Matrix; std::string = std::__cxx11::basic_string]’ | /<>/internal/ceres/gtest/gtest.h:10345:36: required from ‘static std::string testing::internal::FormatForComparison::Format(const ToPrint&) [with ToPrint = Eigen::Matrix; OtherOperand = Eigen::Matrix; std::string = std::__cxx11::basic_string]’ | /<>/internal/ceres/gtest/gtest.h:10420:45: required from ‘std::string testing::internal::FormatForComparisonFailureMessage(const T1&, const T2&) [with T1 = Eigen::Matrix; T2 = Eigen::Matrix; std::string = std::__cxx11::basic_string]’ | /<>/internal/ceres/gtest/gtest.h:19989:53: required from ‘testing::AssertionResult testing::internal::CmpHelperEQFailure(const char*, const char*, const T1&, const T2&) [with T1 = Eigen::Matrix; T2 = Eigen::Matrix]’ | /<>/internal/ceres/gtest/gtest.h:20006:28: required from ‘testing::AssertionResult testing::internal::CmpHelperEQ(const char*, const char*, const T1&, const T2&) [with T1 = Eigen::Matrix; T2 = Eigen::Matrix]’ | /<>/internal/ceres/gtest/gtest.h:20030:23: required from ‘static testing::AssertionResult testing::internal::EqHelper::Compare(const char*, const char*, const T1&, const T2&) [with T1 = Eigen::Matrix; T2 = Eigen::Matrix; bool lhs_is_null_literal = false]’ | /<>/internal/ceres/residual_block_test.cc:297:3: required from here | /<>/internal/ceres/gtest/gtest.h:10445:35: error: variable or field ‘it’ declared void | 10445 | for (typename C::const_iterator it = container.begin(); | | ^~ Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#996117: Update after uploading Rails 6.1
With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of errors like this: Failure: ActionController::Serialization::ImplicitSerializerTest#test_render_array_using_custom_root [/<>/test/action_controller/serialization_test.rb:186]: --- expected +++ actual @@ -1 +1 @@ -"application/json" +"application/json; charset=utf-8" rails test /<>/test/action_controller/serialization_test.rb:181 -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Processed: installing canberra-gtk-module doesn't help
Processing commands for cont...@bugs.debian.org: > severity 1000230 grave Bug #1000230 [screenruler] screenruler fails to start Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#996228 marked as pending in ruby-ffaker
Processing control commands: > tag -1 pending Bug #996228 [src:ruby-ffaker] ruby-ffaker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_ssn_with_from_to(TestSSNSE): ArgumentError: wrong number of arguments (given 4, expected 3) Added tag(s) pending. -- 996228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996228: marked as pending in ruby-ffaker
Control: tag -1 pending Hello, Bug #996228 in ruby-ffaker 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-ffaker/-/commit/a341b7e36f4f9bcbe855064914a9adf3b7490408 Add patch to fix FTBFS * d/patches/0003-Test-with-github-action-ruby-3-468.patch: Add patch. - Fix Ruby 3 compatibility (closes: #996228). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996228
Bug#996159: marked as done (ruby-batch-loader: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: result = schema.execute(query))
Your message dated Fri, 19 Nov 2021 23:05:44 +
with message-id
and subject line Bug#996159: fixed in ruby-batch-loader 2.0.1+dfsg-3
has caused the Debian Bug report #996159,
regarding ruby-batch-loader: FTBFS: ERROR: Test "ruby2.7" failed:
Failure/Error: result = schema.execute(query)
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.)
--
996159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-batch-loader
Version: 2.0.1+dfsg-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-batch-loader was found to fail to build in that situation.
This does not seem related to ruby3.0, but it would be nice to ensure
that the package also builds against ruby3.0. To do this locally, you
can install ruby-all-dev from experimental on an unstable system or
build chroot.
Relevant part (hopefully):
> Failure/Error: result = schema.execute(query)
>
> NameError:
>uninitialized constant GraphQL::StaticValidation::Validator::Timeout
> # /<>/spec/graphql_spec.rb:35:in `test'
> # /<>/spec/graphql_spec.rb:10:in `block (2 levels) in (required)>'
> # --
> # --- Caused by: ---
> # NameError:
> # uninitialized constant GraphQL::StaticValidation::Validator::Timeout
> # /<>/spec/graphql_spec.rb:35:in `test'
>
> Finished in 2.55 seconds (files took 0.36125 seconds to load)
> 31 examples, 2 failures
>
> Failed examples:
>
> rspec /<>/spec/graphql_spec.rb:14 # GraphQL integration resolves
> BatchLoader fields lazily with GraphQL Interpreter
> rspec /<>/spec/graphql_spec.rb:9 # GraphQL integration resolves
> BatchLoader fields lazily
>
> Randomized with seed 40838
>
> /usr/bin/ruby2.7
> -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 "ruby2.7" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-batch-loader/ruby-batch-loader_2.0.1+dfsg-2+rebuild1633375571_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-batch-loader
Source-Version: 2.0.1+dfsg-3
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-batch-loader, 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-batch-loader
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 19 Nov 2021 23:38:48 +0100
Source: ruby-batch-loader
Architecture: source
Version: 2.0.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996159
Changes:
ruby-batch-loader (2.0.1+dfsg-3) unstable; urgency=medium
.
* Team upload.
* d/control (Build-Depends): Adjust ruby-graphql version (closes: #996159).
(Depends): Remove ruby-graphql and rely on ${ruby:Depends}.
* d/copyright (Copyright): Add team.
* d/rules: Use gem installation layout.
* d/watch: Update file.
* d/upstream/metadata: Update some URLs.
Checksums-Sha1:
e2c75bb654e6e0a63c228208d392fa032a5c16aa 2192
ruby-batch-loader_2.0.1+dfsg-3.dsc
235544cca27141136475f555c2f4ef0cea7f9ab3 4036
ruby-batch-loader_2.0.1+dfsg-3.debian.tar.xz
7d01ecfd9d5a558cfc67f598aa7e9da8133eec91 10180
ruby-batch-loader_2.0.1+dfsg-3_amd64.buildinfo
Checksums-Sha256:
16d9fe1c05f67a198bebbb65fed2d12be664d8a5cf3d3e7433a7dfec5b1732a8 2192
ruby-batch-loader_2.0.1+dfsg-3.dsc
4f6716d5118d12f7ac24ec0c23507db6879d704529a4f689300d2094c7b89cc5 4036
ruby-batch-loader_2.0.1+dfsg-3.debian.tar.xz
d3c474f7c136ebe1ae619a41cb21a6241e0a1c0d51af08216926ce971b3e9336 10180
Bug#995358: marked as done (ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout)
Your message dated Fri, 19 Nov 2021 22:50:33 + with message-id and subject line Bug#995358: fixed in ruby-graphql 1.11.8-3 has caused the Debian Bug report #995358, regarding ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout 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.) -- 995358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-graphql, ruby-batch-loader Control: found -1 ruby-graphql/1.11.8-2 Control: found -1 ruby-batch-loader/2.0.1+dfsg-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 ruby-graphql the autopkgtest of ruby-batch-loader fails in testing when that autopkgtest is run with the binary packages of ruby-graphql from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-graphql from testing1.11.8-2 ruby-batch-loader from testing2.0.1+dfsg-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby-graphql to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-graphql https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-batch-loader/15624241/log.gz Failures: 1) GraphQL integration resolves BatchLoader fields lazily with GraphQL Interpreter Failure/Error: result = schema.execute(query) NameError: uninitialized constant GraphQL::StaticValidation::Validator::Timeout # ./spec/graphql_spec.rb:35:in `test' # ./spec/graphql_spec.rb:15:in `block (2 levels) in ' # -- # --- Caused by: --- # NameError: # uninitialized constant GraphQL::StaticValidation::Validator::Timeout # ./spec/graphql_spec.rb:35:in `test' 2) GraphQL integration resolves BatchLoader fields lazily Failure/Error: result = schema.execute(query) NameError: uninitialized constant GraphQL::StaticValidation::Validator::Timeout # ./spec/graphql_spec.rb:35:in `test' # ./spec/graphql_spec.rb:10:in `block (2 levels) in ' # -- # --- Caused by: --- # NameError: # uninitialized constant GraphQL::StaticValidation::Validator::Timeout # ./spec/graphql_spec.rb:35:in `test' Finished in 2.59 seconds (files took 0.62851 seconds to load) 31 examples, 2 failures Failed examples: rspec ./spec/graphql_spec.rb:14 # GraphQL integration resolves BatchLoader fields lazily with GraphQL Interpreter rspec ./spec/graphql_spec.rb:9 # GraphQL integration resolves BatchLoader fields lazily OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ruby-graphql Source-Version: 1.11.8-3 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-graphql, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-graphql package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Nov 2021 23:25:46 +0100 Source: ruby-graphql Architecture: source Version: 1.11.8-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 995358 Changes: ruby-graphql (1.11.8-3) unstable; urgency=medium . * Team upload. * d/copyright (Copyright): Update. * d/ruby-tests.rake.disabled: Re-add file, but wait with enabling tests. * d/rules: Use gem installation layout. *
Processed: Bug#996159 marked as pending in ruby-batch-loader
Processing control commands: > tag -1 pending Bug #996159 [src:ruby-batch-loader] ruby-batch-loader: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: result = schema.execute(query) Added tag(s) pending. -- 996159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996159: marked as pending in ruby-batch-loader
Control: tag -1 pending
Hello,
Bug #996159 in ruby-batch-loader 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-batch-loader/-/commit/df92d61337b44f2366b3c90e042fddcf47d6a86e
Update packaging files
* d/control (Build-Depends): Adjust ruby-graphql version (closes: #996159).
(Depends): Remove ruby-graphql and rely on ${ruby:Depends}.
* d/copyright (Copyright): Add team.
* d/rules: Use gem installation layout.
* d/watch: Update file.
* d/upstream/metadata: Update some URLs.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/996159
Bug#1000229: binary package is missing /usr/sbin/memlockd
Package: memlockd
Version: 1.3-2
Severity: grave
Hello!
The subject says it all: The package is missing the binary:
,
| oweh@ds9:~$ dpkg -L memlockd
| /.
| /etc
| /etc/default
| /etc/init.d
| /etc/init.d/memlockd
| /etc/memlockd.d
| /lib
| /lib/systemd
| /lib/systemd/system
| /lib/systemd/system/memlockd.service
| /usr
| /usr/sbin
| /usr/share
| /usr/share/doc
| /usr/share/doc/memlockd
| /usr/share/doc/memlockd/changelog.Debian.gz
| /usr/share/doc/memlockd/changelog.gz
| /usr/share/doc/memlockd/copyright
| /usr/share/man
| /usr/share/man/man8
| /etc/memlockd.cfg
| /etc/default/memlockd
`
Interestingly, when I rebuild the 1.3-2 source package locally, I get a
DEB with the daemon in it:
,
| oweh@ds9:/tmp/test$ ls -l from_archive/ rebuild/
| from_archive/:
| total 8
| -rw-r--r-- 1 oweh oweh 5732 13. Nov 16:27 memlockd_1.3-2_amd64.deb
|
| rebuild/:
| total 16
| -rw-r--r-- 1 oweh oweh 13432 19. Nov 22:58 memlockd_1.3-2_amd64.deb
`
,
| oweh@ds9:/tmp/test$ debdiff from_archive/memlockd_1.3-2_amd64.deb
rebuild/memlockd_1.3-2_amd64.deb
| [The following lists of changes regard files as different if they have
| different names, permissions or owners.]
|
| Files in second .deb but not in first
| -
| -rw-r--r-- root/root /etc/default/memlockd
| -rw-r--r-- root/root /etc/memlockd.cfg
| -rw-r--r-- root/root /usr/share/man/man8/memlockd.8.gz
| -rwxr-xr-x root/root /usr/sbin/memlockd
|
| Files in first .deb but not in second
| -
| -rw-r--r-- root/root /usr/share/doc/memlockd/changelog.gz
|
| Control files: lines which differ (wdiff format)
|
| Installed-Size: [-31-] {+56+}
`
The buildlog from the buildd also confirms the missing binary:
https://buildd.debian.org/status/fetch.php?pkg=memlockd=amd64=1.3-2=1636816430=0
Weird.
Grüße,
Sven.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages memlockd depends on:
ii adduser 3.118
memlockd recommends no packages.
memlockd suggests no packages.
-- debconf-show failed
Bug#995358: marked as pending in ruby-graphql
Control: tag -1 pending Hello, Bug #995358 in ruby-graphql 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-graphql/-/commit/68709ce9c8c544d7c9df4ff0206d7ca42cae54a4 Add patch to fix FTBFS in ruby-batch-loader * d/patches/Add-missing-require.patch: Add patch. - Fix NameError by adding missing require statement (closes: #995358). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/995358
Processed: Bug#995358 marked as pending in ruby-graphql
Processing control commands: > tag -1 pending Bug #995358 [src:ruby-graphql] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout Added tag(s) pending. -- 995358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000226: python-python-docx_0.8.11+dfsg1-2_all-buildd.changes REJECTED
Source: python-python-docx Version: 0.8.11+dfsg1-2 Severity: serious On 2021-11-19 17:49, Debian FTP Masters wrote: > > python3-python-docx_0.8.11+dfsg1-2_all.deb: Does not match binary in database. > > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Processed: tagging 995358
Processing commands for cont...@bugs.debian.org: > # > https://github.com/rmosolgo/graphql-ruby/commit/56abba472dbb48a1f8445d41f928bea72b5148e9.patch > tags 995358 + fixed-upstream patch Bug #995358 [src:ruby-graphql] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout Added tag(s) fixed-upstream and patch. > 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
Processed: block 996159 with 995358
Processing commands for cont...@bugs.debian.org: > block 996159 with 995358 Bug #996159 [src:ruby-batch-loader] ruby-batch-loader: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: result = schema.execute(query) 996159 was not blocked by any bugs. 996159 was not blocking any bugs. Added blocking bug(s) of 996159: 995358 > thanks Stopping processing here. Please contact me if you need assistance. -- 996159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 995358 to src:ruby-graphql
Processing commands for cont...@bugs.debian.org: > reassign 995358 src:ruby-graphql 1.11.8-2 Bug #995358 [src:ruby-batch-loader] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout Bug reassigned from package 'src:ruby-batch-loader' to 'src:ruby-graphql'. No longer marked as found in versions ruby-batch-loader/2.0.1+dfsg-2. Ignoring request to alter fixed versions of bug #995358 to the same values previously set Bug #995358 [src:ruby-graphql] ruby-graphql breaks ruby-batch-loader autopkgtest: uninitialized constant GraphQL::StaticValidation::Validator::Timeout Marked as found in versions ruby-graphql/1.11.8-2. > 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#996369: marked as done (ruby-responders: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Fri, 19 Nov 2021 22:09:49 + with message-id and subject line Bug#996369: fixed in ruby-responders 3.0.1-2 has caused the Debian Bug report #996369, regarding ruby-responders: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. 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.) -- 996369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-responders Version: 3.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-responders 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/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-responders/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"responders\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-responders/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test:." > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/action_controller/respond_with_api_test.rb" > "test/action_controller/respond_with_test.rb" > "test/action_controller/verify_requested_format_test.rb" > "test/responders/collection_responder_test.rb" > "test/responders/controller_method_test.rb" > "test/responders/flash_responder_test.rb" > "test/responders/http_cache_responder_test.rb" "test/test_helper.rb" -v > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/core_ext/hash/except.rb:12: > warning: method redefined; discarding old except > /usr/lib/ruby/vendor_ruby/tzinfo/ruby_core_support.rb:163: warning: > Object#taint is deprecated and will be removed in Ruby 3.2 > /usr/lib/ruby/vendor_ruby/tzinfo/ruby_core_support.rb:163: warning: > Object#tainted? is deprecated and will be removed in Ruby 3.2 > Run options: -v --seed 34640 > > # Running: > > ControllerMethodTest#test_foo_responder_gets_added = 0.04 s = . > ControllerMethodTest#test_bar_responder_gets_added = 0.00 s = . > NamespacedFlashResponderTest#test_sets_the_flash_message_based_on_the_current_controller > = 0.04 s = . > NamespacedFlashResponderTest#test_does_not_fallbacks_to_non_namespaced_controller_flash_message_if_disabled > = 0.01 s = . > NamespacedFlashResponderTest#test_fallbacks_to_non_namespaced_controller_flash_message > = 0.00 s = . > NamespacedFlashResponderTest#test_sets_the_flash_message_based_on_namespace_actions > = 0.00 s = . > NamespacedFlashResponderTest#test_does_not_fallbacks_to_namespaced_actions_if_disabled > = 0.00 s = . > VerifyRequestedFormatTest#test_strict_mode_calls_action_with_right_format = > 0.01 s = . > VerifyRequestedFormatTest#test_strict_mode_respects_only_option = 0.00 s = . > VerifyRequestedFormatTest#test_strict_mode_shouldnt_call_action = 0.00 s = . > HttpCacheResponderTest#test_does_not_set_cache_for_new_records = 0.00 s = . > HttpCacheResponderTest#test_does_not_use_cache_if_http_cache_is_false = 0.01 > s = . > HttpCacheResponderTest#test_work_with_an_empty_array = 0.02 s = . > HttpCacheResponderTest#test_works_for_nested_resources = 0.00 s = . > HttpCacheResponderTest#test_does_not_use_cache_unless_get_requests = 0.00 s = > . > HttpCacheResponderTest#test_returns_not_modified_if_return_is_cache_is_still_valid > = 0.00 s = . >
Processed: limit source to php-async-aws-core, tagging 995908
Processing commands for cont...@bugs.debian.org: > limit source php-async-aws-core Limiting to bugs with field 'source' containing at least one of 'php-async-aws-core' Limit currently set to 'source':'php-async-aws-core' > tags 995908 + pending Bug #995908 [src:php-async-aws-core] php-async-aws-core: unsatisfiable build-dependency Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 995908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000224: plastimatch: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them.
Source: plastimatch Version: 1.9.3+dfsg.1-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | cd /<>/obj-x86_64-linux-gnu/src/plastimatch/base && /usr/bin/c++ -DITK_IO_FACTORY_REGISTER_MANAGER -Dplmbase_EXPORTS -I/<>/src/plastimatch/base -I/<>/libs/itk-5.1.2 -I/<>/obj-x86_64-linux-gnu/src/plastimatch -I/<>/src/plastimatch/util/cuda -I/<>/src/plastimatch/util -I/<>/src/plastimatch/sys -I/<>/src/plastimatch/segment -I/<>/src/plastimatch/register/cuda -I/<>/src/plastimatch/register -I/<>/src/plastimatch/reconstruct/cuda -I/<>/src/plastimatch/reconstruct -I/<>/src/plastimatch/qt -I/<>/src/plastimatch/opencl -I/<>/src/plastimatch/cuda -I/<>/src/plastimatch/dose -I/<>/src/plastimatch/clp -I/<>/src/plastimatch/cli -I/<>/src/plastimatch -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/ITKFactoryRegistration -I/usr/include/hdf5/serial -I/usr/include/nifti -I/<>/libs/demons_itk_insight -I/<>/libs/demons_itk_insight/DiffeomorphicDemons -I/<>/libs/demons_itk_insight/FastSymmetricForces -I/<>/libs/demons_itk_insight/LOGDomainDemons -I/<>/libs/nSIFT -I/<>/libs/liblbfgs-1.9/include -I/<>/libs -I/<>/libs/ransac -I/<>/libs/ransac/Common -I/<>/libs/nkidecompress -I/<>/libs/devillard -isystem /usr/include/gdcm-3.0 -isystem /usr/include/ITK-4.13 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -Wno-cpp -Wreturn-type -std=gnu++11 -MD -MT src/plastimatch/base/CMakeFiles/plmbase.dir/beam_geometry.cxx.o -MF CMakeFiles/plmbase.dir/beam_geometry.cxx.o.d -o CMakeFiles/plmbase.dir/beam_geometry.cxx.o -c /<>/src/plastimatch/base/beam_geometry.cxx | In file included from /<>/src/plastimatch/base/dcmtk_config.h:16, | from /<>/src/plastimatch/base/metadata.h:12, | from /<>/src/plastimatch/base/astroid_dose.h:8, | from /<>/src/plastimatch/base/astroid_dose.cxx:7: | /usr/include/dcmtk/config/osconfig.h:1136:2: error: invalid preprocessing directive #errorDCMTK | 1136 | #error\ | | ^~ | 1137 | DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. | | ~ | In file included from /<>/src/plastimatch/base/dcmtk_config.h:16, | from /<>/src/plastimatch/base/metadata.h:12, | from /<>/src/plastimatch/base/plm_image.h:10, | from /<>/src/plastimatch/base/plm_image_header.h:12, | from /<>/src/plastimatch/base/bspline_header.cxx:7: | /usr/include/dcmtk/config/osconfig.h:1136:2: error: invalid preprocessing directive #errorDCMTK | 1136 | #error\ | | ^~ | 1137 | DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. | | ~ | In file included from /<>/src/plastimatch/base/dcmtk_config.h:16, | from /<>/src/plastimatch/base/metadata.h:12, | from /<>/src/plastimatch/base/plm_image.h:10, | from /<>/src/plastimatch/base/aperture.h:8, | from /<>/src/plastimatch/base/aperture.cxx:9: | /usr/include/dcmtk/config/osconfig.h:1136:2: error: invalid preprocessing directive #errorDCMTK | 1136 | #error\ | | ^~ | 1137 | DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. | | ~ | In file included from /<>/src/plastimatch/base/dcmtk_config.h:16, | from /<>/src/plastimatch/base/metadata.h:12, | from /<>/src/plastimatch/base/plm_image.h:10, | from /<>/src/plastimatch/base/beam_geometry.cxx:10: | /usr/include/dcmtk/config/osconfig.h:1136:2: error: invalid preprocessing directive #errorDCMTK | 1136 | #error\ | | ^~ | 1137 | DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. | | ~ | make[3]: *** [src/plastimatch/base/CMakeFiles/plmbase.dir/build.make:121: src/plastimatch/base/CMakeFiles/plmbase.dir/bspline_header.cxx.o] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=plastimatch=amd64=1.9.3%2Bdfsg.1-1%2Bb1=1637357564=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#1000222: orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them.
Source: orthanc Version: 1.9.7+dfsg-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_FILESYSTEM_VERSION=3 -DBOOST_HAS_FILESYSTEM_V3=1 -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOCALE_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DCIVETWEB_API="" -DCIVETWEB_HAS_DISABLE_KEEP_ALIVE=1 -DCIVETWEB_HAS_WEBDAV_WRITING=1 -DCIVETWEB_KEEP_ALIVE_TIMEOUT_SECONDS=1 -DDCMTK_DICTIONARY_DIR=\"/usr/share/libdcmtk16\" -DDCMTK_USE_EMBEDDED_DICTIONARIES=0 -DDCMTK_VERSION_NUMBER=366 -DHAVE_CONFIG_H=1 -DJSONCPP_DEPRECATED_STACK_LIMIT=5000 -DORTHANC_API_VERSION=15 -DORTHANC_BUILDING_FRAMEWORK_LIBRARY=1 -DORTHANC_DATABASE_VERSION=6 -DORTHANC_DEFAULT_DICOM_ENCODING=Encoding_Latin1 -DORTHANC_ENABLE_BASE64=1 -DORTHANC_ENABLE_CIVETWEB=1 -DORTHANC_ENABLE_CURL=1 -DORTHANC_ENABLE_DCMTK=1 -DORTHANC_ENABLE_DCMTK_JPEG=1 -DORTHANC_ENABLE_DCMTK_JPEG_LOSSLESS=1 -DORTHANC_ENABLE_DCMTK_NETWORKING=1 -DORTHANC_ENABLE_DCMTK_TRANSCODING=1 -DORTHANC_ENABLE_JPEG=1 -DORTHANC_ENABLE_LOCALE=1 -DORTHANC_ENABLE_LOGGING=1 -DORTHANC_ENABLE_LOGGING_STDIO=0 -DORTHANC_ENABLE_LUA=1 -DORTHANC_ENABLE_MD5=1 -DORTHANC_ENABLE_MONGOOSE=0 -DORTHANC_ENABLE_PKCS11=0 -DORTHANC_ENABLE_PNG=1 -DORTHANC_ENABLE_PUGIXML=1 -DORTHANC_ENABLE_SQLITE=1 -DORTHANC_ENABLE_SSL=1 -DORTHANC_ENABLE_ZLIB=1 -DORTHANC_MAXIMUM_TAG_LENGTH=256 -DORTHANC_SANDBOXED=0 -DORTHANC_SQLITE_VERSION=3036000 -DORTHANC_STATIC_ICU=0 -DORTHANC_VERSION=\"1.9.7\" -DORTHANC_VERSION_MAJOR=1 -DORTHANC_VERSION_MINOR=9 -DORTHANC_VERSION_REVISION=7 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -I/<>/BuildStaticFramework/AUTOGENERATED -I/usr/include/lua5.3 -I/usr/src/gtest -I/usr/include/jsoncpp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-long-long -Wno-variadic-macros -std=gnu++11 -fPIC -MD -MT CMakeFiles/OrthancFramework.dir/<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp.o -MF CMakeFiles/OrthancFramework.dir/<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp.o.d -o CMakeFiles/OrthancFramework.dir/<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp.o -c /<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp | In file included from /usr/include/dcmtk/dcmdata/dcdatset.h:26, | from /<>/OrthancFramework/Sources/DicomFormat/../DicomParsing/FromDcmtkBridge.h:30, | from /<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp:32: | /usr/include/dcmtk/config/osconfig.h:1136:2: error: invalid preprocessing directive #errorDCMTK | 1136 | #error\ | | ^~ | 1137 | DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them. | | ~ See https://buildd.debian.org/status/fetch.php?pkg=orthanc=amd64=1.9.7%2Bdfsg-1%2Bb1=1637357465=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#1000221: ginkgocadx: error: ‘OFIterator’ was not declared in this scope; did you mean ‘OF_error’?
Source: ginkgocadx
Version: 3.8.8-5
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
| cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++ -DAPIEXPORT
-DCURL_STATICLIB -DDCMTK_POST_20170228 -DGINKGO_ARCH_x86_64
-DGINKGO_CODENAME=\"\" -DGINKGO_VERSION=\"3.8.8\" -DHAVE_CONFIG_H
-DINTERNET_DIST -DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC
-DUSE_SYSTEM_SQLITE -DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64
-D__WXGTK__ -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)"
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)"
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)"
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)"
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)"
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKFactoryRegistration
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/libmount -I/usr/include/blkid
-I/<>/cadxcore/CADxCore -I/<>/cadxcore
-I/<>/cadxcore/vtk -I/<>/cadxcore/itk
-I/<>/cadxcore/wx -I/<>/cadxcore/wx/VTK
-I/<>/cadxcore/VTKInria3D
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0
-I/usr/include/vtk-6.3 -I/usr/lib/x86_64-linux-gnu/openmpi/include
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/include/hdf5/openmpi
-I/usr/include/libxml2 -isystem /usr/include/gdcm-3.0 -isystem
/usr/include/ITK-4.13 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC -MD -MT
cadxcore/CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomstoreassociation.cpp.o
-MF
CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomstoreassociation.cpp.o.d -o
CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomstoreassociation.cpp.o -c
/<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp
| /<>/cadxcore/main/controllers/dcmtk/dicomprintassociation.cpp:
In function ‘void DIMSE_printNStatusString(std::ostream&, int)’:
|
/<>/cadxcore/main/controllers/dcmtk/dicomprintassociation.cpp:160:14:
error: ‘STATUS_N_PRINT_BSB_Fail_PrintQueueFull’ was not declared in this
scope; did you mean ‘STATUS_N_PRINT_BFB_Fail_PrintQueueFull’?
| 160 | case STATUS_N_PRINT_BSB_Fail_PrintQueueFull:
| | ^~
| | STATUS_N_PRINT_BFB_Fail_PrintQueueFull
| make[3]: *** [cadxcore/CMakeFiles/CADxCore.dir/build.make:3873:
cadxcore/CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomprintassociation.cpp.o]
Error 1
| make[3]: *** Waiting for unfinished jobs
| /<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp:
In member function ‘void
GIL::DICOM::DicomStoreAssociation::Store(GIL::DICOM::DicomStoreAssociation::ListaRutas,
const GNC::GCS::Ptr&, std::string,
GNC::IProxyNotificadorProgreso*, GIL::DICOM::TipoTransferSyntaxEnvio)’:
|
/<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp:1047:38:
error: ‘OFIterator’ was not declared in this scope; did you mean ‘OF_error’?
| 1047 | for (OFIterator itsc
=sopClassUIDList.begin(); itsc != sopClassUIDList.end(); ++itsc) {
| | ^~
| | OF_error
|
/<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp:1047:57:
error: expected primary-expression before ‘>’ token
| 1047 | for (OFIterator itsc
=sopClassUIDList.begin(); itsc != sopClassUIDList.end(); ++itsc) {
| | ^
|
/<>/cadxcore/main/controllers/dcmtk/dicomstoreassociation.cpp:1047:59:
error: ‘itsc’ was not declared in this scope; did you mean ‘it’?
| 1047 | for (OFIterator itsc
=sopClassUIDList.begin(); itsc != sopClassUIDList.end(); ++itsc) {
| | ^~~~
| | it
| make[3]: *** [cadxcore/CMakeFiles/CADxCore.dir/build.make:3915:
cadxcore/CMakeFiles/CADxCore.dir/main/controllers/dcmtk/dicomstoreassociation.cpp.o]
Error 1
See
https://buildd.debian.org/status/fetch.php?pkg=ginkgocadx=amd64=3.8.8-5%2Bb2=1637356473=0
Cheers
--
Sebastian Ramacher
signature.asc
Bug#1000220: dicomscope: error: cannot bind non-const lvalue reference of type ‘std::__cxx11::list >::const_iterator&’ to an rvalue of type ‘std::__cxx11::list
Source: dicomscope Version: 3.6.0-22 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org | cd /<>/obj-x86_64-linux-gnu/interface/libsrc && /usr/bin/c++ -DHAVE_CONFIG_H -DHAVE_STRSTREAM_H -DNDEBUG -DjInterface_EXPORTS -I/<>/interface/include -I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux -I/usr/include/dcmtk/dcmpstat -I/usr/include/dcmtk/dcmsr -I/usr/include/dcmtk/dcmjpeg -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MT interface/libsrc/CMakeFiles/jInterface.dir/DSRImageValue.cpp.o -MF CMakeFiles/jInterface.dir/DSRImageValue.cpp.o.d -o CMakeFiles/jInterface.dir/DSRImageValue.cpp.o -c /<>/interface/libsrc/DSRImageValue.cpp | In file included from /usr/include/dcmtk/dcmsr/dsrscogr.h:30, | from /usr/include/dcmtk/dcmsr/dsrscovl.h:30, | from /usr/include/dcmtk/dcmsr/dsrcitem.h:33, | from /usr/include/dcmtk/dcmsr/dsrdocst.h:33, | from /usr/include/dcmtk/dcmsr/dsrdoctr.h:29, | from /usr/include/dcmtk/dcmsr/dsrdoc.h:29, | from /<>/interface/include/jInterface.h:49, | from /<>/interface/libsrc/DSRImageValue.cpp:39: | /usr/include/dcmtk/dcmsr/dsrtlist.h: In instantiation of ‘OFCondition DSRListOfItems::removeItem(size_t) [with T = int; size_t = long unsigned int]’: | /<>/interface/libsrc/DSRImageValue.cpp:313:49: required from here | /usr/include/dcmtk/dcmsr/dsrtlist.h:303:30: error: cannot bind non-const lvalue reference of type ‘std::__cxx11::list >::const_iterator&’ to an rvalue of type ‘std::__cxx11::list >::const_iterator’ | 303 | if (gotoItemPos(idx, iterator)) | | ^~~~ | In file included from /usr/include/c++/11/list:63, | from /usr/include/dcmtk/ofstd/oflist.h:56, | from /usr/include/dcmtk/ofstd/ofstd.h:28, | from /usr/include/dcmtk/ofstd/offile.h:30, | from /usr/include/dcmtk/dcmdata/dcistrma.h:28, | from /usr/include/dcmtk/dcmdata/dctk.h:30, | from /usr/include/dcmtk/dcmpstat/dcmpstat.h:27, | from /usr/include/dcmtk/dcmpstat/dvpstat.h:27, | from /usr/include/dcmtk/dcmpstat/dviface.h:32, | from /<>/interface/include/jInterface.h:42, | from /<>/interface/libsrc/DSRImageValue.cpp:39: | /usr/include/c++/11/bits/stl_list.h:286:7: note: after user-defined conversion: ‘std::_List_const_iterator< >::_List_const_iterator(const iterator&) [with _Tp = int; std::_List_const_iterator< >::iterator = std::_List_const_iterator::iterator]’ | 286 | _List_const_iterator(const iterator& __x) _GLIBCXX_NOEXCEPT | | ^~~~ | In file included from /usr/include/dcmtk/dcmsr/dsrscogr.h:30, | from /usr/include/dcmtk/dcmsr/dsrscovl.h:30, | from /usr/include/dcmtk/dcmsr/dsrcitem.h:33, | from /usr/include/dcmtk/dcmsr/dsrdocst.h:33, | from /usr/include/dcmtk/dcmsr/dsrdoctr.h:29, | from /usr/include/dcmtk/dcmsr/dsrdoc.h:29, | from /<>/interface/include/jInterface.h:49, | from /<>/interface/libsrc/DSRImageValue.cpp:39: | /usr/include/dcmtk/dcmsr/dsrtlist.h:320:64: note: initializing argument 2 of ‘OFBool DSRListOfItems::gotoItemPos(size_t, typename std::__cxx11::list::const_iterator&) const [with T = int; OFBool = bool; size_t = long unsigned int; typename std::__cxx11::list::const_iterator = std::__cxx11::list >::const_iterator]’ | 320 |OFLIST_TYPENAME OFListConstIterator(T) ) const | |^ | make[3]: *** [interface/libsrc/CMakeFiles/jInterface.dir/build.make:135: interface/libsrc/CMakeFiles/jInterface.dir/DSRImageValue.cpp.o] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=dicomscope=amd64=3.6.0-22%2Bb2=1637356191=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#999376: marked as done (python-gmpy2 ftbfs with Python 3.10)
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.) -- 999376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-gmpy2 Version: 2.1.0~b5-0.1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python-gmpy2 ftbfs with python3-defaults from experimental: x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I./src -I/usr/include/python3.10 -c src/gmpy2.c -o build/temp.linux-x86_64-3.10/src/gmpy2.o -DSHARED=1 In file included from src/gmpy2.c:461: src/gmpy2.h:446: warning: "Py_RETURN_NOTIMPLEMENTED" redefined 446 | #define Py_RETURN_NOTIMPLEMENTED \ | In file included from /usr/include/python3.10/Python.h:74, from src/gmpy2.c:445: /usr/include/python3.10/object.h:623: note: this is the location of the previous definition 623 | #define Py_RETURN_NOTIMPLEMENTED return Py_NewRef(Py_NotImplemented) | In file included from src/gmpy2.c:593: src/gmpy2_hash.c: In function ‘_mpfr_hash’: src/gmpy2_hash.c:150:20: error: ‘_PyHASH_NAN’ undeclared (first use in this function); did you mean ‘Py_IS_NAN’? 150 | return _PyHASH_NAN; |^~~ |Py_IS_NAN src/gmpy2_hash.c:150:20: note: each undeclared identifier is reported only once for each function it appears in error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 E: pybuild pybuild:354: build: plugin distutils failed with: exit code=1: /usr/bin/python3.10 setup.py build --- End Message --- --- Begin Message --- Source: python-gmpy2 Source-Version: 2.1.0~b5-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-gmpy2, 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 python-gmpy2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Nov 2021 17:17:30 -0400 Source: python-gmpy2 Architecture: source Version: 2.1.0~b5-1 Distribution: unstable Urgency: medium Maintainer: Martin Kelly Changed-By: Stefano Rivera Closes: 999376 Changes: python-gmpy2 (2.1.0~b5-1) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. * Patch: Python 3.10 support: Use _Py_HashPointer. (Closes: #999376) . [ Ondřej Nový ] * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Sandro Tosi ] * Use the new Debian Python Team contact name and address Checksums-Sha1: b17438295097a3b23665a3e95a830f1e4409a5c2 1658 python-gmpy2_2.1.0~b5-1.dsc 6276f6866bd1fd9587c52bf2ae1424b80c1c7ba4 5276 python-gmpy2_2.1.0~b5-1.debian.tar.xz b3b1cc354299834a4e22df55ac55887b01877cd8 6862 python-gmpy2_2.1.0~b5-1_source.buildinfo Checksums-Sha256: 86665a826e1f927f827faae7be5128df6c0f1810a645a3150d0bc8ad585b8b30 1658 python-gmpy2_2.1.0~b5-1.dsc fe5bf687954538961924a332729838299e782bf150c428cabf4f18f1ef2d5f93 5276 python-gmpy2_2.1.0~b5-1.debian.tar.xz 682b8dedb2ed473dbf31de68990d1804654b53975985ac095fa586b93d786bcf 6862 python-gmpy2_2.1.0~b5-1_source.buildinfo Files: 47322accd4970e293c884b46da484856 1658 python optional python-gmpy2_2.1.0~b5-1.dsc e50426b3c5184dd8426ca29503b7b87d 5276 python optional python-gmpy2_2.1.0~b5-1.debian.tar.xz fd8ec73f612f1fbdb75313d5afc9c376 6862 python optional python-gmpy2_2.1.0~b5-1_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYZgUghQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2GwuAQD4TyQoyA6oOwMszdd388mr+VCeMxvP
Processed: tagging 984233
Processing commands for cont...@bugs.debian.org:
> tags 984233 + ftbfs
Bug #984233 {Done: Alastair McKinstry } [src:mia] mia:
ftbfs with GCC-11
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999380: marked as done (python-lzo ftbfs with Python 3.10 (test failures))
Your message dated Fri, 19 Nov 2021 20:47:46 + with message-id and subject line Bug#999380: fixed in python-lzo 1.12-4 has caused the Debian Bug report #999380, regarding python-lzo 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.) -- 999380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-lzo Version: 1.12-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python-lzo ftbfs with python3-defaults from experimental: I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_lzo/build; python3.10 -m nose -v tests tests.test.test_version ... ok tests.test.test_lzo(b'',) ... ERROR tests.test.test_lzo(b'',) ... ERROR tests.test.test_lzo(b'abcabcabcabcabcabcabcabc',) ... ERROR tests.test.test_lzo(b'abcabcabcabcabcabcabcabc',) ... ERROR tests.test.test_lzo(b'abcabcabcabcabcabcabcabc', 9) ... ERROR tests.test.test_lzo(b'abcabcabcabcabcabcabcabc', 9) ... ERROR tests.test.test_lzo(b'',) ... ERROR tests.test.test_lzo(b'',) ... ERROR tests.test.test_lzo_big ... ERROR tests.test.test_lzo_raw_big ... ERROR == ERROR: tests.test.test_lzo(b'',) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/.pybuild/cpython3_3.10_lzo/build/tests/test.py", line 58, in gen a0 = lzo.adler32(src) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: tests.test.test_lzo(b'',) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/.pybuild/cpython3_3.10_lzo/build/tests/test.py", line 75, in gen_raw a0 = lzo.adler32(src) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: tests.test.test_lzo(b'abcabcabcabcabcabcabcabc',) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/.pybuild/cpython3_3.10_lzo/build/tests/test.py", line 58, in gen a0 = lzo.adler32(src) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: tests.test.test_lzo(b'abcabcabcabcabcabcabcabc',) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/.pybuild/cpython3_3.10_lzo/build/tests/test.py", line 75, in gen_raw a0 = lzo.adler32(src) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: tests.test.test_lzo(b'abcabcabcabcabcabcabcabc', 9) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/.pybuild/cpython3_3.10_lzo/build/tests/test.py", line 58, in gen a0 = lzo.adler32(src) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: tests.test.test_lzo(b'abcabcabcabcabcabcabcabc', 9) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/.pybuild/cpython3_3.10_lzo/build/tests/test.py", line 75, in gen_raw a0 = lzo.adler32(src) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: tests.test.test_lzo(b'',) -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg)
Processed: RM: pangox-compat -- RoQA; deprecated since 2012
Processing commands for cont...@bugs.debian.org: > reassign 947649 ftp.debian.org Bug #947649 [src:pangox-compat] pangox-compat: deprecated since 2012, unmaintained, should probably be removed Bug reassigned from package 'src:pangox-compat' to 'ftp.debian.org'. No longer marked as found in versions pangox-compat/0.0.2-5. Ignoring request to alter fixed versions of bug #947649 to the same values previously set > retitle 947649 RM: pangox-compat -- RoQA; deprecated since 2012 Bug #947649 [ftp.debian.org] pangox-compat: deprecated since 2012, unmaintained, should probably be removed Changed Bug title to 'RM: pangox-compat -- RoQA; deprecated since 2012' from 'pangox-compat: deprecated since 2012, unmaintained, should probably be removed'. > reassign 702011 ftp.debian.org Bug #702011 [src:gtkmathview] gtkmathview: uses pangox which is going away Bug reassigned from package 'src:gtkmathview' to 'ftp.debian.org'. No longer marked as found in versions gtkmathview/0.8.0-8. Ignoring request to alter fixed versions of bug #702011 to the same values previously set > retitle 702011 RM: gtkmathview -- RoQA; dead upstream Bug #702011 [ftp.debian.org] gtkmathview: uses pangox which is going away Changed Bug title to 'RM: gtkmathview -- RoQA; dead upstream' from 'gtkmathview: uses pangox which is going away'. > thanks Stopping processing here. Please contact me if you need assistance. -- 702011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702011 947649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000215: glusterfs: FTBFS on armel, armhf, mipsel
Source: glusterfs Version: 10.0-1.2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org, Christian Ehrhardt | libtool: link: gcc -Wall -I/usr/include/uuid -I/usr/include/tirpc -Wformat -Werror=format-security -Werror=implicit-function-declaration -flto -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -rdynamic -flto -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/gf_attach gf_attach.o -ltirpc ../../libglusterfs/src/.libs/libglusterfs.so ../../api/src/.libs/libgfapi.so ../../rpc/rpc-lib/src/.libs/libgfrpc.so ../../rpc/xdr/src/.libs/libgfxdr.so -lrt -ldl -lpthread -lcrypto | libtool: link: gcc -Wall -I/usr/include/uuid -I/usr/include/tirpc -Wformat -Werror=format-security -Werror=implicit-function-declaration -flto -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -rdynamic -flto -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/glusterfsd glusterfsd.o glusterfsd-mgmt.o -ltirpc ../../libglusterfs/src/.libs/libglusterfs.so ../../rpc/rpc-lib/src/.libs/libgfrpc.so ../../rpc/xdr/src/.libs/libgfxdr.so -lm -lrt -ldl -lpthread -lcrypto | /usr/bin/ld: ../../libglusterfs/src/.libs/libglusterfs.so: undefined reference to `_uatomic_link_error' | collect2: error: ld returned 1 exit status | make[4]: *** [Makefile:543: gf_attach] Error 1 | make[4]: *** Waiting for unfinished jobs | /usr/bin/ld: ../../libglusterfs/src/.libs/libglusterfs.so: undefined reference to `_uatomic_link_error' | collect2: error: ld returned 1 exit status | make[4]: *** [Makefile:547: glusterfsd] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=glusterfs=armel=10.0-1.2=1637143838=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#702011: gtkmathview: uses pangox which is going away
Hello, Le 19/11/2021 à 21:09, Paul Gevers a écrit : > Hi, > > On Fri, 01 Mar 2013 17:13:47 +0100 Emilio Pozuelo Monfort > wrote: >> gtkmathview uses pangox internally. pangox is no longer maintained >> and we want to remove it from Debian. Ideally gtkmathview should stop >> using pangox, perhaps by using one of the other pango backends. > > Unless you object (please CC me, I'm not subscribed), I am going to > ask ftp-master to remove pangox-compat from Debian in two weeks from > now. As gtkmathview has a build dependency on libpangox-1.0-dev it > would need to get removed too. > > Paul > Yeah, I think it is time to remove it. I didn't have any updates from upstream for years! Cheers S
Bug#702011: gtkmathview: uses pangox which is going away
Hi, On Fri, 01 Mar 2013 17:13:47 +0100 Emilio Pozuelo Monfort wrote: gtkmathview uses pangox internally. pangox is no longer maintained and we want to remove it from Debian. Ideally gtkmathview should stop using pangox, perhaps by using one of the other pango backends. Unless you object (please CC me, I'm not subscribed), I am going to ask ftp-master to remove pangox-compat from Debian in two weeks from now. As gtkmathview has a build dependency on libpangox-1.0-dev it would need to get removed too. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1000213: gcc-python-plugin: Don't use -Werror=deprecated-declarations
Package: gcc-python-plugin Version: 0.17-6 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Hello, The gcc-python-plugin package currently fails to build because the source uses functions that are deprecated in python3.9: gcc-python.c:791:24: error: ‘void PyEval_InitThreads()’ is deprecated [-Werror=deprecated-declarations] Since there is no upstream fix for this deprecation warning, it doesn't seem worth failing the build on, so I've prepared the attached patch to fix it. As a side effect, it fixes the fact that gcc-python-plugin was not previously using the cflags from dpkg-buildflags for the build, which seems kind of important! I've uploaded this patch to Ubuntu. Please consider including it in Debian as well. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru gcc-python-plugin-0.17/debian/rules gcc-python-plugin-0.17/debian/rules --- gcc-python-plugin-0.17/debian/rules 2020-02-20 05:15:45.0 -0800 +++ gcc-python-plugin-0.17/debian/rules 2021-11-19 11:24:09.0 -0800 @@ -14,6 +14,7 @@ INTERP = python3 python3-dbg # python python-dbg export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) +export CFLAGS := $(shell env DEB_CFLAGS_MAINT_APPEND=-Wno-error=deprecated-declarations dpkg-buildflags --get CFLAGS) build-arch: $(INTERP:%=build-stamp-%) build-indep: doc-stamp
Bug#999380: marked as pending in python-lzo
Control: tag -1 pending Hello, Bug #999380 in python-lzo 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-lzo/-/commit/12313fdb5ba010b4b31599916d1e82e22888cd43 Patch: Enable PY_SSIZE_T_CLEAN for Python 3.10 support. (Closes: #999380) (this message was generated automatically) -- Greetings https://bugs.debian.org/999380
Processed: fixed 999743 in 5.14.0-release-1
Processing commands for cont...@bugs.debian.org:
> fixed 999743 5.14.0-release-1
Bug #999743 {Done: Bastian Germann } [src:xfsprogs] xfsprogs
FTBFS: .gitcensus: No such file or directory
The source 'xfsprogs' and version '5.14.0-release-1' do not appear to match any
binary packages
Marked as fixed in versions xfsprogs/5.14.0-release-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
999743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#999380 marked as pending in python-lzo
Processing control commands: > tag -1 pending Bug #999380 [src:python-lzo] python-lzo ftbfs with Python 3.10 (test failures) Added tag(s) pending. -- 999380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000210: [regression] uscan die: filenamemangle failed
Package: devscripts Version: 2.21.5 Severity: serious Hi, since upgrading to devscrips 2.21.5, uscan fails when trying to run it for the systemd package: $ uscan --report --verbose uscan info: uscan (version 2.21.5) See uscan(1) for help uscan info: Scan watch files in . find: Dateisystemschleife erkannt; ‘./test/testdata’ ist ein Teil der gleichen Schleife wie ‘./test’. uscan info: Check debian/watch and debian/changelog in . uscan info: package="systemd" version="249.6-3" (as seen in debian/changelog) uscan info: package="systemd" version="249.6" (no epoch/revision) uscan info: Check debian/watch and debian/changelog in ./debian/patches uscan info: ./debian/changelog sets package="systemd" version="249.6" uscan info: Process watch file at: debian/watch package = systemd version = 249.6 pkg_dir = . uscan info: opts: uversionmangle=s/-rc/~rc/,filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/systemd-$1\.tar\.gz/ uscan info: line: https://github.com/systemd/systemd-stable/tags .*/v?(\d\S*)\.tar\.gz uscan info: Parsing uversionmangle=s/-rc/~rc/ uscan info: Parsing filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/systemd-$1\.tar\.gz/ uscan info: line: https://github.com/systemd/systemd-stable/tags .*/v?(\d\S*)\.tar\.gz uscan info: Last orig.tar.* tarball version (from debian/changelog): 249.6 uscan info: Last orig.tar.* tarball version (dversionmangled): 249.6 uscan info: Requesting URL: https://github.com/systemd/systemd-stable/tags uscan info: Matching pattern: (?:(?:https://github.com)?\/systemd\/systemd\-stable\/)?.*/v?(\d\S*)\.tar\.gz uscan info: Found the following matching hrefs on the web page (newest first): https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz (249.7) index=249.7-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.7.tar.gz (249.7) index=249.7-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.6.tar.gz (249.6) index=249.6-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.6.tar.gz (249.6) index=249.6-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.5.tar.gz (249.5) index=249.5-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.5.tar.gz (249.5) index=249.5-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.4.tar.gz (249.4) index=249.4-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.4.tar.gz (249.4) index=249.4-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.3.tar.gz (249.3) index=249.3-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249.3.tar.gz (249.3) index=249.3-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249-4.tar.gz (249-4) index=249-4-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v249-4.tar.gz (249-4) index=249-4-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v248.9.tar.gz (248.9) index=248.9-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v248.9.tar.gz (248.9) index=248.9-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v248.8.tar.gz (248.8) index=248.8-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v248.8.tar.gz (248.8) index=248.8-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v247.10.tar.gz (247.10) index=247.10-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v247.10.tar.gz (247.10) index=247.10-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v239-50.tar.gz (239-50) index=239-50-1 https://github.com/systemd/systemd-stable/archive/refs/tags/v239-50.tar.gz (239-50) index=239-50-1 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. Running uscan 2.21.4 succeeds: $ uscan --rename --verbose uscan info: uscan (version 2.21.4) See uscan(1) for help uscan info: Scan watch files in . find: File system loop detected; './test/testdata' is part of the same file system loop as './test'. uscan info: Check debian/watch and debian/changelog in . uscan info: package="systemd" version="249.6-3" (as seen in debian/changelog) uscan info: package="systemd" version="249.6" (no epoch/revision) uscan info: Check debian/watch and debian/changelog in ./debian/patches uscan info: ./debian/changelog sets package="systemd" version="249.6" uscan info: Process watch file
Bug#999376: marked as pending in python-gmpy2
Control: tag -1 pending Hello, Bug #999376 in python-gmpy2 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-gmpy2/-/commit/30777bba0f4b0266f06b078b3fb9f4b23405e92b Patch: Python 3.10 support: Use _Py_HashPointer. (Closes: #999376) (this message was generated automatically) -- Greetings https://bugs.debian.org/999376
Processed: Bug#999376 marked as pending in python-gmpy2
Processing control commands: > tag -1 pending Bug #999376 [src:python-gmpy2] python-gmpy2 ftbfs with Python 3.10 Added tag(s) pending. -- 999376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999760: marked as done (opencv: libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5)
Your message dated Fri, 19 Nov 2021 18:34:42 + with message-id and subject line Bug#999760: fixed in opencv 4.5.4+dfsg-4 has caused the Debian Bug report #999760, regarding opencv: libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5 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.) -- 999760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencv Version: 4.5.4+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid 'installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-core4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.5.4', which is also in package libopencv-core4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-flann4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_flann.so.4.5.4', which is also in package libopencv-flann4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-imgproc4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.5.4', which is also in package libopencv-imgproc4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-features2d4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_features2d.so.4.5.4', which is also in package libopencv-features2d4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-calib3d4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.4', which is also in package libopencv-calib3d4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb This seems to affect all libopencv-*4.5d packages. cheers, Andreas libopencv-core4.5=4.5.4+dfsg-1_libopencv-core4.5d=4.5.4+dfsg-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: opencv Source-Version: 4.5.4+dfsg-4 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of opencv, 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. Timo
Bug#999853: marked as done (src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf)
Your message dated Fri, 19 Nov 2021 17:33:36 + with message-id and subject line Bug#999853: fixed in boost1.74 1.74.0-13 has caused the Debian Bug report #999853, regarding src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf 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.) -- 999853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boost1.74 Version: 1.74.0-9 Severity: serious Control: close -1 1.74.0-12 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:boost1.74 has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails to build on armhf. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=boost1.74 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: boost1.74 Source-Version: 1.74.0-13 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of boost1.74, 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. Anton Gladky (supplier of updated boost1.74 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Nov 2021 15:23:15 +0100 Source: boost1.74 Architecture: source Version: 1.74.0-13 Distribution: unstable Urgency: medium Maintainer: Debian Boost Team Changed-By: Anton Gladky Closes: 999778 999853 Changes: boost1.74 (1.74.0-13) unstable; urgency=medium . [ Anton Gladky ] * Import fixes from Ubuntu * [fabaa30] Import upstream patch: fix asio compilation with -fno-rtti. (Closes: #999778) . [ Matthias Klose ] * [2098d38] Explicitly set fpu mode on armhf. (Closes: #999853) . [ Graham Inggs ] * [107cd01] Cherry-pick upstream commits: - Convert Python 3.1+ to use public C API for filenames - Replace private _Py_fopen() with public fopen(): private _Py_fopen() - Fix Python 3.10 (PEP-620) incompatibility . [ Gianfranco Costamagna ] * [7d6aad9] Cherry-pick upstream commits: Cherry-pick upstream commits: - e193f080c7d209516ac9b712fa0c50bb08026fa2.patch Fix regex to allow search for python3.10 too (fixes e.g. ros-image-common build) Checksums-Sha1: 86b7f32f7874884c6831c2083113781fc03de65d 9110 boost1.74_1.74.0-13.dsc 71855bb5e39eaac8cafac2cf8a5888c174ec6681 371680 boost1.74_1.74.0-13.debian.tar.xz 02d93376287f6b8d9dfe1db93b1082ce29e01e6c 11444 boost1.74_1.74.0-13_source.buildinfo Checksums-Sha256: 07a2637ae2a118d78472d90b8208b5c46e090dc2af67aca88485fb370e733850 9110 boost1.74_1.74.0-13.dsc 455b2b4db13f3ef39a98499d14d0c955b0c2745d0ecd39abbb5e87a3f3afc0f8 371680 boost1.74_1.74.0-13.debian.tar.xz
Bug#999743: marked as done (xfsprogs FTBFS: .gitcensus: No such file or directory)
Your message dated Fri, 19 Nov 2021 18:33:43 +0100 with message-id and subject line xfsprogs fix has caused the Debian Bug report #999743, regarding xfsprogs FTBFS: .gitcensus: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xfsprogs Version: 5.14.0-rc1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=xfsprogs=5.14.0-rc1-1 ... cat: .gitcensus: No such file or directory /bin/tar: .gitcensus: Cannot stat: No such file or directory /bin/tar: Exiting with failure status due to previous errors gmake[2]: *** [Makefile:187: xfsprogs-5.14.0-rc1.tar.gz] Error 2 --- End Message --- --- Begin Message --- Version: 5.14.0-1--- End Message ---
Bug#984384: marked as done (varconf: ftbfs with GCC-11)
Your message dated Fri, 19 Nov 2021 17:06:05 + with message-id and subject line Bug#984384: fixed in varconf 1.0.1-8 has caused the Debian Bug report #984384, regarding varconf: 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.) -- 984384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:varconf Version: 1.0.1-7 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/varconf_1.0.1-7_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 dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether g++ supports C++11 features by default... yes checking whether hidden visibility is supported... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for SIGC... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating varconf.spec config.status: creating mingw32-varconf.spec config.status: creating doc/Makefile config.status: creating doc/old/Makefile config.status: creating tests/Makefile config.status: creating varconf/Makefile config.status: creating varconf-1.0.pc config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands dh_auto_build make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in varconf make[3]: Entering directory '/<>/varconf' /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -Wall -DNDEBUG -DBUILDING_VARCONF_DSO -fvisibility=hidden -fvisibility-inlines-hidden -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o config.lo config.cpp /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -Wall -DNDEBUG -DBUILDING_VARCONF_DSO -fvisibility=hidden -fvisibility-inlines-hidden -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o parse_error.lo parse_error.cpp /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -Wall -DNDEBUG -DBUILDING_VARCONF_DSO -fvisibility=hidden -fvisibility-inlines-hidden -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o variable.lo variable.cpp /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -Wall -DNDEBUG -DBUILDING_VARCONF_DSO -fvisibility=hidden -fvisibility-inlines-hidden -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
Bug#999374: marked as done (python-gammu ftbfs with Python 3.10 (test failures))
Your message dated Fri, 19 Nov 2021 16:37:17 + with message-id and subject line Bug#999374: fixed in python-gammu 3.2.4-1 has caused the Debian Bug report #999374, regarding python-gammu 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.) -- 999374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-gammu Version: 2.12-2 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python-gammu ftbfs with python3-defaults from experimental: [...] == ERROR: test_decode (test.test_sms.PDUTest) -- Traceback (most recent call last): File "/<>/test/test_sms.py", line 64, in test_decode sms = gammu.DecodePDU(PDU_DATA) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_encode_gsm (test.test_sms.PDUTest) -- Traceback (most recent call last): File "/<>/test/test_sms.py", line 100, in test_encode_gsm self.do_smstest(smsinfo, GSM) File "/<>/test/test_sms.py", line 70, in do_smstest sms = gammu.EncodeSMS(smsinfo) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_encode_plain (test.test_sms.PDUTest) -- Traceback (most recent call last): File "/<>/test/test_sms.py", line 94, in test_encode_plain self.do_smstest(smsinfo, MESSAGE) File "/<>/test/test_sms.py", line 70, in do_smstest sms = gammu.EncodeSMS(smsinfo) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_encode_unicode (test.test_sms.PDUTest) -- Traceback (most recent call last): File "/<>/test/test_sms.py", line 107, in test_encode_unicode self.do_smstest(smsinfo, UNICODE) File "/<>/test/test_sms.py", line 70, in do_smstest sms = gammu.EncodeSMS(smsinfo) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_link (test.test_sms.PDUTest) -- Traceback (most recent call last): File "/<>/test/test_sms.py", line 116, in test_link sms = gammu.EncodeSMS(smsinfo) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_file (test.test_config.DebugTest) -- Traceback (most recent call last): File "/<>/test/test_config.py", line 113, in test_file self.check_operation(testfile.name, handle) File "/<>/test/test_config.py", line 99, in check_operation gammu.DecodePDU(PDU_DATA) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_filename (test.test_config.DebugTest) -- Traceback (most recent call last): File "/<>/test/test_config.py", line 123, in test_filename self.check_operation(testfile.name) File "/<>/test/test_config.py", line 99, in check_operation gammu.DecodePDU(PDU_DATA) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_none (test.test_config.DebugTest) -- Traceback (most recent call last): File "/<>/test/test_config.py", line 130, in test_none self.check_operation(None) File "/<>/test/test_config.py", line 99, in check_operation gammu.DecodePDU(PDU_DATA) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats == ERROR: test_nothing (test.test_config.DebugTest) -- Traceback (most recent call last): File "/<>/test/test_config.py", line 138, in test_nothing self.check_operation(None) File
Bug#997176: marked as done (pgmodeler: FTBFS: Project ERROR: libpq development package not found)
Your message dated Fri, 19 Nov 2021 17:12:52 +0100 with message-id and subject line Re: Bug#997176: pgmodeler: FTBFS: Project ERROR: libpq development package not found has caused the Debian Bug report #997176, regarding pgmodeler: FTBFS: Project ERROR: libpq development package not found 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.) -- 997176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pgmodeler Version: 0.9.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- CONFIG+=debug pgmodeler.pro > qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" > "QMAKE_CFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_DEBUG=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,--as-needed" > "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,--as-needed" QMAKE_STRIP=: PREFIX=/usr > CONFIG\+=debug pgmodeler.pro > Info: creating stash file /<>/.qmake.stash > Project WARNING: The subproject /<>/plugins/plugins.pro wasn't > found! pgModeler will be build without plugins. > Project WARNING: If you want to compile pgModeler with plugins make sure to > clone https://github.com/pgmodeler/plugins inside pgModeler's root folder and > rerun qmake. > Project ERROR: libpq development package not found > dh_auto_configure: error: qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" > "QMAKE_CFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_DEBUG=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,--as-needed" > "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,--as-needed" QMAKE_STRIP=: PREFIX=/usr > CONFIG\+=debug pgmodeler.pro returned exit code 3 > make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pgmodeler_0.9.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Control: reassign -1 libpq-dev Version: 14.1-1 Re: Lucas Nussbaum > > Project ERROR: libpq development package not found This was caused by PG14's libpq-dev now needing libssl-dev for `pkg-config --exists libpq` to work. Christoph--- End Message ---
Bug#999373: marked as pending in python-dmidecode
Control: tag -1 pending Hello, Bug #999373 in python-dmidecode 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-dmidecode/-/commit/c1fb5f162b0c0b967bd2497129c21eed747ea6d0 Patch: Support Python 3.10's 2-digit minor version in the test runner. (Closes: #999373) (this message was generated automatically) -- Greetings https://bugs.debian.org/999373
Processed: Bug#999373 marked as pending in python-dmidecode
Processing control commands: > tag -1 pending Bug #999373 [src:python-dmidecode] python-dmidcode ftbfs with Python 3.10 (test failures) Added tag(s) pending. -- 999373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999370: marked as done (pystemd ftbfs with Python 3.10)
Your message dated Fri, 19 Nov 2021 16:04:39 + with message-id and subject line Bug#999370: fixed in pystemd 0.7.0-5 has caused the Debian Bug report #999370, regarding pystemd 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.) -- 999370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pystemd Version: 0.7.0-4 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 psystemd ftbfs with python3-defaults from experimental: [...] x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.10 -c pystemd/dbuslib.c -o build/temp.linux-x86_64-3.10/pystemd/dbuslib.o pystemd/dbuslib.c: In function ‘__pyx_f_7pystemd_7dbuslib_11DbusMessage_get_priority’: pystemd/dbuslib.c:5672:3: warning: ‘sd_bus_message_get_priority’ is deprecated [-Wdeprecated-declarations] 5672 | (void)(sd_bus_message_get_priority(__pyx_v_self->_msg, (&__pyx_v_ret))); | ^ In file included from pystemd/dbuslib.c:616: /usr/include/systemd/sd-bus.h:277:5: note: declared here 277 | int sd_bus_message_get_priority(sd_bus_message *m, int64_t *priority) _sd_deprecated_; | ^~~ pystemd/dbuslib.c: In function ‘__pyx_tp_dealloc_7pystemd_7dbuslib_DbusMessage’: pystemd/dbuslib.c:14758:5: error: lvalue required as increment operand 14758 | ++Py_REFCNT(o); | ^~ pystemd/dbuslib.c:14760:5: error: lvalue required as decrement operand 14760 | --Py_REFCNT(o); | ^~ --- End Message --- --- Begin Message --- Source: pystemd Source-Version: 0.7.0-5 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of pystemd, 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 pystemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Nov 2021 11:42:17 -0400 Source: pystemd Architecture: source Version: 0.7.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 999370 Changes: pystemd (0.7.0-5) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. * Patch: Include dbusc.pxd, omitted from source tarball, to allow re-cythonization. Thanks Steve Langasek. * Re-cythonize source, fixing FTBFS with Python 3.10. (Closes: #999370) . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. Checksums-Sha1: 2026a48a3b912cfc6e7295fa3ca8178035fb8999 1559 pystemd_0.7.0-5.dsc 77dd55d7f792ce23fcfbadc9efb9dc344f68e7b6 4664 pystemd_0.7.0-5.debian.tar.xz fc26edc2201176558946f17f517838e94deed7c3 6063 pystemd_0.7.0-5_source.buildinfo Checksums-Sha256: 3ab49d6596fd72e8f6fb847d3b924d743ac1b39fb7d0adcd9f5fe9ff462cb08f 1559 pystemd_0.7.0-5.dsc 4ecd346d4f6d7aa979a6ea926673328d3f4de23d7fee2fde6c5bd5b9702bae5f 4664 pystemd_0.7.0-5.debian.tar.xz b585da0a2a780719eaeecc01d305e9f46ca1e0937004aefa2c18c6c5070dca7c 6063 pystemd_0.7.0-5_source.buildinfo Files: 85cb353b09f4c7609ae4d08166498509 1559 python optional pystemd_0.7.0-5.dsc 271b5c03b33420f190cacf80f4f4ff21 4664 python optional pystemd_0.7.0-5.debian.tar.xz 2b898038d4110e2ba9eb8159d85372ab 6063 python optional pystemd_0.7.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYZfGABQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2EGAAP0WCwtVYDwPaDi+n9KZi1c2jonjctnR ucvX6oHHoyD/1AEApOzMb32YDvmH1VPPIMDfcHCbMZnwMKy23mic3a2pxgw= =niPw -END PGP SIGNATURE End Message ---
Bug#997698: marked as done (pg-dirtyread: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)
Your message dated Fri, 19 Nov 2021 16:59:51 +0100
with message-id
and subject line Re: Bug#997698: pg-dirtyread: FTBFS: Error: debian/control
needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.
has caused the Debian Bug report #997698,
regarding pg-dirtyread: 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.)
--
997698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pg-dirtyread
Version: 2.3-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 '/<>'
> rm -f pg_dirtyread.so libpg_dirtyread.a libpg_dirtyread.pc
> rm -f pg_dirtyread.o dirtyread_tupconvert.o pg_dirtyread.bc
> dirtyread_tupconvert.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2020-10-19 09:11:52.0 +
> +++ debian/control.1cKEsI 2021-10-23 06:29:14.799095718 +
> @@ -9,9 +9,9 @@
> Vcs-Browser: https://github.com/ChristophBerg/pg_dirtyread
> Vcs-Git: https://github.com/ChristophBerg/pg_dirtyread.git
>
> -Package: postgresql-13-dirtyread
> +Package: postgresql-14-dirtyread
> Architecture: any
> -Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-13
> +Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-14
> Description: Read dead but unvacuumed tuples from a PostgreSQL relation
> The pg_dirtyread extension provides the ability to read dead but unvacuumed
> rows from a PostgreSQL relation.
> 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: *** [debian/rules:7: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pg-dirtyread_2.3-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 ---
Version: 2.4-1
Re: Lucas Nussbaum
> > 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.
Fixed in unstable.
Christoph--- End Message ---
Bug#1000204: pyfai: FTBFS if built using python3.10 (collections.MutableSets deprecated)
Package: pyfai Version: 0.20.0+dfsg1-4 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Dear Maintainer, collections.MutableSet was deprecated a long time ago and removed with python3.10. https://docs.python.org/3/whatsnew/3.10.html#removed https://bugs.python.org/issue37324 Using the old class name leads to autopkgtest failures such as this one: ``` == ERROR: test_import_all_modules (pyFAI.test.test_bug_regression.TestBugRegression) Try to import every single module in the package -- Traceback (most recent call last): File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 286, in test_import_all_modules raise err File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 271, in test_import_all_modules load_source(fqn, path) File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 78, in load_source spec.loader.exec_module(module) File "", line 883, in exec_module File "", line 241, in _call_with_frames_removed File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/utils/orderedset.py", line 30, in class OrderedSet(collections.MutableSet): AttributeError: module 'collections' has no attribute 'MutableSet' ``` In Ubuntu, the attached patch was applied to achieve the following: * Fix FTBFS with python3.10, due to deprecated collections.MutableSets Forwarded upstream: https://github.com/silx-kit/pyFAI/pull/1588 Thanks for considering the patch. Cheers, Lukas -- System Information: Debian Release: 11.0 APT prefers impish-updates APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 'impish'), (100, 'impish-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-20-generic (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru pyfai-0.20.0+dfsg1/debian/patches/python3.10-compat.patch pyfai-0.20.0+dfsg1/debian/patches/python3.10-compat.patch --- pyfai-0.20.0+dfsg1/debian/patches/python3.10-compat.patch 1970-01-01 01:00:00.0 +0100 +++ pyfai-0.20.0+dfsg1/debian/patches/python3.10-compat.patch 2021-11-19 16:51:28.0 +0100 @@ -0,0 +1,40 @@ +Description: Fix collections.MutableSets compat with python3.10 + collections.MutableSet was deprecated a long time ago and removed with python3.10. + https://docs.python.org/3/whatsnew/3.10.html#removed + https://bugs.python.org/issue37324 + + Using the old class name leads to test failures such as this one: + == + ERROR: test_import_all_modules (pyFAI.test.test_bug_regression.TestBugRegression) + Try to import every single module in the package + -- + Traceback (most recent call last): + File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 286, in test_import_all_modules + raise err + File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 271, in test_import_all_modules + load_source(fqn, path) + File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 78, in load_source + spec.loader.exec_module(module) + File "", line 883, in exec_module + File "", line 241, in _call_with_frames_removed + File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/utils/orderedset.py", line 30, in + class OrderedSet(collections.MutableSet): + AttributeError: module 'collections' has no attribute 'MutableSet' +Author: Lukas Märdian +Origin: vendor, Ubuntu +Bug: https://github.com/silx-kit/pyFAI/pull/1588 +Forwarded: https://github.com/silx-kit/pyFAI/pull/1588 +Last-Update: 2021-11-19 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- pyfai-0.20.0+dfsg1.orig/pyFAI/utils/orderedset.py pyfai-0.20.0+dfsg1/pyFAI/utils/orderedset.py +@@ -27,7 +27,7 @@ + import collections + + +-class OrderedSet(collections.MutableSet): ++class OrderedSet(collections.abc.MutableSet): + + def __init__(self, iterable=None): + self.end = end = [] diff -Nru pyfai-0.20.0+dfsg1/debian/patches/series pyfai-0.20.0+dfsg1/debian/patches/series --- pyfai-0.20.0+dfsg1/debian/patches/series2021-09-19
Bug#997378: marked as done (python-coverage: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')
Your message dated Fri, 19 Nov 2021 15:42:22 + with message-id and subject line Bug#997378: fixed in python-coverage 5.1+dfsg.1-2.1 has caused the Debian Bug report #997378, regarding python-coverage: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-coverage Version: 5.1+dfsg.1-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): > make[1]: Entering directory '/<>' > rm -f coverage/htmlfiles/jquery.isonscreen.js > dh_auto_build --buildsystem=pybuild > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/python.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/jsonreport.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/execfile.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/env.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/disposition.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/plugin_support.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/__init__.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/parser.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/__main__.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/html.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/cmdline.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/debug.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/optional.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/tomlconfig.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/misc.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/sqldata.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/results.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/annotate.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/plugin.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/backunittest.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/pytracer.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/inorout.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/data.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/version.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/config.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/multiproc.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/templite.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/context.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/phystokens.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/control.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/summary.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/report.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/bytecode.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/collector.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/numbits.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/xmlreport.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/backward.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > copying coverage/files.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage > creating > /<>/.pybuild/cpython3_3.9_coverage/build/coverage/fullcoverage > copying coverage/fullcoverage/encodings.py -> > /<>/.pybuild/cpython3_3.9_coverage/build/coverage/fullcoverage > running build_ext > building 'coverage.tracer' extension > creating build > creating build/temp.linux-x86_64-3.9 > creating
Bug#984242: marked as done (mpich: ftbfs with GCC-11)
Your message dated Fri, 19 Nov 2021 15:41:20 +
with message-id
and subject line Bug#984242: fixed in mpich 4.0~b1-1
has caused the Debian Bug report #984242,
regarding mpich: 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.)
--
984242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpich
Version: 3.4.1-3
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/mpich_3.4.1-3_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.
[...]
## --- ##
## File substitutions. ##
## --- ##
cc_shlib_conf='src/env/cc_shlib.conf'
cxx_shlib_conf=''
f77_shlib_conf='src/env/f77_shlib.conf'
fc_shlib_conf=''
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME "MPICH"
#define PACKAGE_TARNAME "mpich"
#define PACKAGE_VERSION "3.4.1"
#define PACKAGE_STRING "MPICH 3.4.1"
#define PACKAGE_BUGREPORT "disc...@mpich.org"
#define PACKAGE_URL "http://www.mpich.org/;
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define __EXTENSIONS__ 1
#define _ALL_SOURCE 1
#define _GNU_SOURCE 1
#define _POSIX_PTHREAD_SEMANTICS 1
#define _TANDEM_SOURCE 1
#define PACKAGE "mpich"
#define VERSION "3.4.1"
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
#define NEEDS_STRICT_ALIGNMENT 1
#define HAVE_ERROR_CHECKING MPID_ERROR_LEVEL_ALL
#define MPICH_ERROR_MSG_LEVEL MPICH_ERROR_MSG__ALL
#define HAVE_TAG_ERROR_BITS 1
#define HAVE_PRAGMA_WEAK 1
#define HAVE_WEAK_ATTRIBUTE 1
#define USE_WEAK_SYMBOLS 1
#define HAVE_MULTIPLE_PRAGMA_WEAK 1
#define HAVE_VISIBILITY 1
#define MPICH_THREAD_LEVEL MPI_THREAD_MULTIPLE
#define MPICH_IS_THREADED 1
#define MPICH_THREAD_GRANULARITY MPICH_THREAD_GRANULARITY__GLOBAL
#define MPICH_THREAD_REFCOUNT MPICH_REFCOUNT__NONE
#define HAVE_ROMIO 1
#define HAVE__FUNC__ /**/
#define HAVE__FUNCTION__ /**/
#define ENABLE_PVAR_NEM 0
#define ENABLE_PVAR_RECVQ 0
#define ENABLE_PVAR_RMA 0
#define ENABLE_PVAR_DIMS 0
#define HAVE_LONG_LONG 1
#define STDCALL
#define F77_NAME_LOWER_USCORE 1
#define HAVE_MPI_F_INIT_WORKS_WITH_C 1
configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --with-libfabric=/usr
--with-device=ch3 --with-pm=hydra --with-slurm=/usr --with-hwloc-prefix=/usr
--with-wrapper-dl-type=none --enable-shared --without-yaksa --prefix=/usr
--enable-fortran=all --disable-rpath --disable-wrapper-rpath
--sysconfdir=/etc/mpich --libdir=/usr/lib/x86_64-linux-gnu
--includedir=/usr/include/x86_64-linux-gnu/mpich --docdir=/usr/share/doc/mpich
CPPFLAGS= CFLAGS= CXXFLAGS= "FFLAGS=-O2 -ffile-prefix-map=/<>=.
Bug#997378: python-coverage: diff for NMU version 5.1+dfsg.1-2.1
Control: tags 997378 + patch
Dear maintainer,
I've prepared an NMU for python-coverage (versioned as 5.1+dfsg.1-2.1). The diff
is attached to this message.
Regards.
diff -Nru python-coverage-5.1+dfsg.1/debian/changelog python-coverage-5.1+dfsg.1/debian/changelog
--- python-coverage-5.1+dfsg.1/debian/changelog 2020-09-06 01:43:16.0 -0400
+++ python-coverage-5.1+dfsg.1/debian/changelog 2021-11-19 08:33:46.0 -0500
@@ -1,3 +1,10 @@
+python-coverage (5.1+dfsg.1-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * use add_css_file() instead of deprecated add_stylesheet(); closes: #997378.
+
+ -- Joseph Nahmias Fri, 19 Nov 2021 08:33:46 -0500
+
python-coverage (5.1+dfsg.1-2) unstable; urgency=medium
* The “Karl Karnadi” release.
diff -Nru python-coverage-5.1+dfsg.1/debian/patches/05.fix-add_stylesheet.patch python-coverage-5.1+dfsg.1/debian/patches/05.fix-add_stylesheet.patch
--- python-coverage-5.1+dfsg.1/debian/patches/05.fix-add_stylesheet.patch 1969-12-31 19:00:00.0 -0500
+++ python-coverage-5.1+dfsg.1/debian/patches/05.fix-add_stylesheet.patch 2021-11-19 08:31:49.0 -0500
@@ -0,0 +1,18 @@
+Description: use add_css_file() instead of deprecated add_stylesheet()
+Author: Joseph Nahmias
+Bug-debian: https://bugs.debian.org/997378
+Forwarded: not-needed
+Applied-Upstream: https://github.com/nedbat/coveragepy/commit/4859de2850f703207b0cab2ff6e7116a3e587b65
+Last-Update: 2021-11-19
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/doc/conf.py
b/doc/conf.py
+@@ -230,6 +230,6 @@ prerelease = bool(max(release).isalpha()
+
+ def setup(app):
+ """Configure Sphinx"""
+-app.add_stylesheet('coverage.css')
++app.add_css_file('coverage.css')
+ app.add_config_value('prerelease', False, 'env')
+ print("** Prerelease = %r" % prerelease)
diff -Nru python-coverage-5.1+dfsg.1/debian/patches/series python-coverage-5.1+dfsg.1/debian/patches/series
--- python-coverage-5.1+dfsg.1/debian/patches/series 2020-09-06 01:43:16.0 -0400
+++ python-coverage-5.1+dfsg.1/debian/patches/series 2021-11-19 08:32:28.0 -0500
@@ -2,3 +2,4 @@
02.rename-public-programs.patch
03.remove-hotkeys.patch
04.sphinx-add-code-path.patch
+05.fix-add_stylesheet.patch
Processed: python-coverage: diff for NMU version 5.1+dfsg.1-2.1
Processing control commands: > tags 997378 + patch Bug #997378 [src:python-coverage] python-coverage: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Added tag(s) patch. -- 997378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000175: marked as done (python3-lz4tools is empty)
Your message dated Fri, 19 Nov 2021 14:39:04 + with message-id and subject line Bug#1000175: fixed in lz4tools 1.3.1.1-5 has caused the Debian Bug report #1000175, regarding python3-lz4tools is empty 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.) -- 1000175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-lz4tools Version: 1.3.1.1-4 Severity: grave $ dpkg -L python3-lz4tools /. /usr /usr/share /usr/share/doc /usr/share/doc/python3-lz4tools /usr/share/doc/python3-lz4tools/changelog.Debian.gz /usr/share/doc/python3-lz4tools/copyright $ --- End Message --- --- Begin Message --- Source: lz4tools Source-Version: 1.3.1.1-5 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of lz4tools, 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. Thomas Goirand (supplier of updated lz4tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 19 Nov 2021 14:44:48 +0100 Source: lz4tools Architecture: source Version: 1.3.1.1-5 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1000175 Changes: lz4tools (1.3.1.1-5) unstable; urgency=medium . * Fix "python3-lz4tools is empty" (Closes: #1000175). Checksums-Sha1: 3770a6edc13115c98b01270ae5fecd41992367be 2111 lz4tools_1.3.1.1-5.dsc e70b8891e2a40d057734057be4475479fa10b62f 3656 lz4tools_1.3.1.1-5.debian.tar.xz 36cfdeb1d9cb2f745058b0d9c57dff91765c47cd 8118 lz4tools_1.3.1.1-5_amd64.buildinfo Checksums-Sha256: b27860b5da347b5b0479e534be4dc00b8e92474107d21bb3713751a1f9ac413b 2111 lz4tools_1.3.1.1-5.dsc 3be84687a4dc23c9741195eecaa8284cc492dc82997678343dfd60c6525ea389 3656 lz4tools_1.3.1.1-5.debian.tar.xz 8e9c7c1489375063312c7f534ed418685b46f61a8a376de48244aaf7d8b79de1 8118 lz4tools_1.3.1.1-5_amd64.buildinfo Files: 59b143ae5d4259988c296f03c23dc491 2111 python optional lz4tools_1.3.1.1-5.dsc 6ee1bb382f423a657fbd1766a346509e 3656 python optional lz4tools_1.3.1.1-5.debian.tar.xz eef65757a9a84bf9d61ce97ec9eadfd4 8118 python optional lz4tools_1.3.1.1-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmGXq+8ACgkQ1BatFaxr Q/6LSQ//fp7gMNue2Zr27dgOafLkhoXuXNpmRiRuYa6OgX2O4jafSzPy/0FuQsQm bQXanpwFneQ+VVS8zF04kjoA4R5JVv5ogLywPY3Bpox08lTZZ8dsO3f1OMbK6wV5 zbaee3xYqBp8m0QkuE4fL31xiWxDbmmIPdSD9pfGQcQg3jUk/BVnJsia/6/ypI79 FWY8znxoZypAvLt+CDGKqt7alJoEWCpH8bx1ilP+LOOA26KEzAs8FyIrMiupXX7Q hzSZG2T4WsPhP8V3Odn9WZuyXucRATG0J1Ae6vLmAFHPuUWC8s+y9b11nHmx/ktV 5/czbC84PAACzCfRHP31wSaQOs/QOZLmj8qtUgxql5PpdQNj5Y60ynNPVIC7Z1aj zuKFPg0wqDC08d5QcwzdAQcs8jXkU7YN+sGNGTqbYvjUAHAW/3eoBr3D3vkoTZhe +DJ8SbsgRkdagntP/lkKO+1QCQWwiRvxcTwhN8cy9aXNdPfNJk4k3xtRSQfeOpGa BJ1FiGcZ7wzjCqEH6QmpC4W+Nnuxk2xRiKfLrXpgZv0kzMhIOjut6DeRRaIiz9FZ M7G45EK6bc6HO/0uR9Je550Dd4iJG8IGsheGyOcM+Ymd8LsApwQfvunAszxLKs9W aSjHAbioagdsTMLMcMUTtw+Z9Ltv0doAJTw8zc+7p/3p7YNHBok= =Rh2J -END PGP SIGNATURE End Message ---
Bug#1000163: phast FTBFS: pcre.h: No such file or directory
Hi Adrian, Am Fri, Nov 19, 2021 at 03:26:39PM +0200 schrieb Adrian Bunk: > > Just for the sake of interest: If this would not have built in my own > > pbuilder chroot I would not have considered uploading. Well, I could > > have checked Salsa CI first but it seems my assumption "builds in > > pbuilder so it builds in autobuilders and CI" is wrong. Any idea how I > > can track down this? > > do you stil have the .buildinfor from this successful testbuild? Unfortunately not. > My first guess would be that it worked for you due to libpcre3-dev being > installed during the build for some reason. Yes, I also had the explanation that some other Build-Dependency might in turn had a dependency from libpcre3-dev and thus I was lured in that the build worked so easily. Its really hard to reproduce, thought. In any case I'm happy that I now have a libpcre2-dev solution that passes upstreams test suite (at least to the level where it was passing with libpcre3-dev). Thanks a lot for watching me and the helpful hints Andreas. -- http://fam-tille.de
Bug#1000175: marked as pending in magnum-ui
Control: tag -1 pending Hello, Bug #1000175 in magnum-ui 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/openstack-team/python/python-lz4tools/-/commit/735d350c6ececb35b8a019742d2033fdd7e80ec5 Fix "python3-lz4tools is empty" (Closes: #1000175). (this message was generated automatically) -- Greetings https://bugs.debian.org/1000175
Processed: Bug#1000175 marked as pending in magnum-ui
Processing control commands: > tag -1 pending Bug #1000175 [python3-lz4tools] python3-lz4tools is empty Added tag(s) pending. -- 1000175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000163: phast FTBFS: pcre.h: No such file or directory
On Fri, Nov 19, 2021 at 07:38:14AM +0100, Andreas Tille wrote: > Hi Adrian, Hi Andreas, > Am Thu, Nov 18, 2021 at 11:13:33PM +0200 schrieb Adrian Bunk: > > Source: phast > > Version: 1.6+dfsg-2 > > Severity: serious > > Tags: ftbfs > > > > https://buildd.debian.org/status/logs.php?pkg=phast=1.6%2Bdfsg-2 > > > > ... > > /<>/src/../include/phast/stringsplus.h:27:10: fatal error: > > pcre.h: No such file or directory > >27 | #include > > | ^~~~ > > compilation terminated. > > make[4]: *** [Makefile:13: phast_list_of_lists.o] Error 1 > > Just for the sake of interest: If this would not have built in my own > pbuilder chroot I would not have considered uploading. Well, I could > have checked Salsa CI first but it seems my assumption "builds in > pbuilder so it builds in autobuilders and CI" is wrong. Any idea how I > can track down this? do you stil have the .buildinfor from this successful testbuild? My first guess would be that it worked for you due to libpcre3-dev being installed during the build for some reason. > Kind regards > > Andreas. cu Adrian
Bug#1000165: marked as done (xdmf FTBFS with more than one supported python3 version)
Your message dated Fri, 19 Nov 2021 13:22:56 + with message-id and subject line Bug#1000165: fixed in xdmf 3.0+git20190531-10 has caused the Debian Bug report #1000165, regarding xdmf FTBFS with more than one supported python3 version 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.) -- 1000165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xdmf Version: 3.0+git20190531-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=xdmf=3.0%2Bgit20190531-8%2Bb1 ... dh_missing -a -O--buildsystem=cmake dh_missing: warning: usr/lib/python3.10/xdmf/Xdmf.py exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/Xdmf.py") dh_missing: warning: usr/lib/python3.10/xdmf/XdmfCore.py exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/XdmfCore.py") dh_missing: warning: usr/lib/python3.10/xdmf/XdmfUtils.py exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/XdmfUtils.py") dh_missing: warning: usr/lib/python3.10/xdmf/__Xdmf.so exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/__Xdmf.so") dh_missing: warning: usr/lib/python3.10/xdmf/__XdmfCore.so exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/__XdmfCore.so") dh_missing: warning: usr/lib/python3.10/xdmf/__XdmfUtils.so exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/__XdmfUtils.so") dh_missing: error: missing files, aborting --- End Message --- --- Begin Message --- Source: xdmf Source-Version: 3.0+git20190531-10 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of xdmf, 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. Alastair McKinstry (supplier of updated xdmf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 19 Nov 2021 09:30:08 + Source: xdmf Architecture: source Version: 3.0+git20190531-10 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1000165 Changes: xdmf (3.0+git20190531-10) unstable; urgency=medium . * Support python3.10 transition. Closes: #1000165 Checksums-Sha1: a21382512c07e33e7fa07f1516a503682aa9265c 2246 xdmf_3.0+git20190531-10.dsc 8dd558a5b1ef41055bb0608cc7fa1beb33cca7b3 11192 xdmf_3.0+git20190531-10.debian.tar.xz Checksums-Sha256: 8c3769ea907a4e712cdefb6a80d1ee2e0e8e04b84f18c083f77c25b269aae9a7 2246 xdmf_3.0+git20190531-10.dsc 008cf916faef761ea2319c70981b6509a7b90d7c1ba7d9f8ceac0b3b0ddc364d 11192 xdmf_3.0+git20190531-10.debian.tar.xz Files: 205f824761df14be486de5e700cf8704 2246 science optional xdmf_3.0+git20190531-10.dsc 9a8116fc24815db981ee831080be2cc3 11192 science optional xdmf_3.0+git20190531-10.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmGXn9wACgkQy+a7Tl2a 06UhXBAAj8Sdf8Q4haCNOWF0EvSDaQHMmUp7087b93nlVzwW0SiHahkHL8FKvQvl iodn8vPvSeOAPlKpZ0vH2aPdSWQE996Tax7k5XGtHu/pnO5Bb4cblxjAJJyrnEfD P8nQQQj3MdymOshsASYdR+vBzPaV2XTT2dXLFXqhU5sSgAOy0CN4YTBEU/lMiBks bBE4OiyFTrccoCrlpkeTKVPz2DvKhC8o3GtapeheBqIVNcQXKW6cmagrdQpaK1FS SNceBYN8nEj0SLpm0rmksebMjo9JH+AyCovUc5U0T9d1Yi2i8DCnULL225bl6vcy YsZ+GVE8v47griZXWb9ZVR7BTMkYpvrtKEzm/CDL5ZALKsNNTxDOKSY68b+r0IhL j5BtZEBwhllFuwXvMVT5kvLxDRCRxbYYWV0Ps5LGFIL4NnvigBGvp32hwmo++QKL j8ZH/G97d0zUQIqtRbpXYM+UbjlXEokDZnEsklL+2VA1dzwofiRFXWpR4Tk8fmRY NlacAuIBUvw8Vb9F7KfPJt81yo5e6hGnx/M+vbKw++Rc1yPxsbGd/wXk0s/LWlIa qUFczsAFxAVL0ueaS42+akCRzPgkSujDEpMpGytFBtWIF9Qx/+05PRxC9VXf42oz KSj+SM69XzfSaE5tw37BwJ6ZH0s0jjsw0nr/hyJnQy88G8ixvh0= =Ve+J -END PGP SIGNATURE End Message ---
Bug#1000163: marked as done (phast FTBFS: pcre.h: No such file or directory)
Your message dated Fri, 19 Nov 2021 13:21:17 + with message-id and subject line Bug#1000163: fixed in phast 1.6+dfsg-3 has caused the Debian Bug report #1000163, regarding phast FTBFS: pcre.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phast Version: 1.6+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=phast=1.6%2Bdfsg-2 ... /<>/src/../include/phast/stringsplus.h:27:10: fatal error: pcre.h: No such file or directory 27 | #include | ^~~~ compilation terminated. make[4]: *** [Makefile:13: phast_list_of_lists.o] Error 1 --- End Message --- --- Begin Message --- Source: phast Source-Version: 1.6+dfsg-3 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of phast, 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. Andreas Tille (supplier of updated phast package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Nov 2021 13:17:54 +0100 Source: phast Architecture: source Version: 1.6+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 100 1000163 Changes: phast (1.6+dfsg-3) unstable; urgency=medium . * Port to pcre2 Closes: #100, #1000163 Checksums-Sha1: dc4f4dbd858d6eeff0c85d2bc0d17dd7e08e33d1 2048 phast_1.6+dfsg-3.dsc b59881c299836be37bc9e5852454d786998b1e55 57668 phast_1.6+dfsg-3.debian.tar.xz ed0eec0a890c31ea17eb1871fa8823d537022a30 6492 phast_1.6+dfsg-3_amd64.buildinfo Checksums-Sha256: d961d6761663e45c8481fc8112b60d00218c03a93ca96d7746135b90140f8490 2048 phast_1.6+dfsg-3.dsc 95f5073ace91794c2f9bffcc725a73c4e1c7f8d754080ae5df622192c378b8b6 57668 phast_1.6+dfsg-3.debian.tar.xz df1dcaed9408d25fd3fc2fadbbf62ba39fbdd98502784df6c44149f420044fa9 6492 phast_1.6+dfsg-3_amd64.buildinfo Files: eb83d5700f8f3824ab62fde46bd16663 2048 science optional phast_1.6+dfsg-3.dsc 38cf28b61182cc39d4f63c4e951b70bb 57668 science optional phast_1.6+dfsg-3.debian.tar.xz 94c8ef52715224e7ebf5e35a9405f867 6492 science optional phast_1.6+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmGXntIRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFX9g//ZN6owkq/eOgoFGL1PEAQ1VQWJnaK70UV wt+D/zk8C9MnmOTChBamE/2iuk4ZxwwQcZljtHU3YWyHNVotjgdVT97uoIe9nmWT f8o0THvcuCKZsQcZ+QCXlDShLKINYExhBL/hJWqQa2OG18toyQfIcv0mvD4MTNsq jWqrNqSmPGtM1xZOxEYl9KzC8cQ70lQnLgXHRLYGZJKNAxT9TdPwfEAQD3V7yzG4 EXsKB+Lt3L3M7ukeOU3eHtS2kuAuF4VZBUzuapg4cQOao3capmff6IwL8/zNjtwY e4yag+O6BxrnINjkh/pwHXeq1uepK+OQcBZGY56GiU2hIZmpFK/b3mvMxd0UIW7n LmHuhJ3R7JBBkFCYvzolsqGPZPwh9m6pZxaEu1PfcVzaFLQOYXu+PosXZ94Qcg5Q 7wlvR2hGIj/2/1QS7dfAFApLPngRVR4GgzC3a+c1W5es4/R/jhHmuw187mOCujSD rTD3uABb07hpkNcnMD+TSBuwfaP5SuhlqrGPu0TEbMH3+Gsp1ftD6sg1HF+xgOVG 9flDoNKjZRRqLIa4wFws1h6wDK7xswyu2gbcjfKMdAMqPj48Ytbp6IFqP79q9z/A rRIjaEebeAYIRkmFS2SdcSHEwsGowNsBBuW4dBK/Gj9jrNYN+4WH+DA09neu08HL dts9UuLy9hQ= =Tvbg -END PGP SIGNATURE End Message ---
Bug#1000197: assimp: binary-any FTBFS
Source: assimp Version: 5.0.1~ds0-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=assimp=5.0.1~ds0-4 ... dh clean --buildsystem=cmake dh_auto_clean -O--buildsystem=cmake debian/rules execute_after_dh_auto_clean-arch make[1]: Entering directory '/<>' rm -rf doc/tmp/ make[1]: Leaving directory '/<>' debian/rules execute_after_dh_auto_clean-indep make[1]: Entering directory '/<>' dh_auto_clean --indep --buildsystem=pybuild -- \ -d port/PyAssimp/ dh_auto_clean: error: unable to load build system class 'pybuild': Can't locate Debian/Debhelper/Buildsystem/pybuild.pm in @INC (you may need to install the Debian::Debhelper::Buildsystem::pybuild module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at (eval 6) line 1. BEGIN failed--compilation aborted at (eval 6) line 1. make[1]: *** [debian/rules:73: execute_after_dh_auto_clean-indep] Error 25
Processed: bug 996303 is forwarded to https://github.com/nov/json-jwt/issues/96
Processing commands for cont...@bugs.debian.org: > forwarded 996303 https://github.com/nov/json-jwt/issues/96 Bug #996303 [src:ruby-json-jwt] ruby-json-jwt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Set Bug forwarded-to-address to 'https://github.com/nov/json-jwt/issues/96'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000188: python3.10: testsuite gets stuck in a loop on buildds
Source: python3.10 Version: 3.10.0-5 Severity: serious python3.10 testsuite regularly gets stuck in a loop on buildds with the following kind of output: | 186:53:00 load avg: 0.28 running: test_multiprocessing_fork (186 hour 45 min) Full builds logs are available there: https://buildd.debian.org/status/fetch.php?pkg=python3.10=all=3.10.0-5=1637323356=0 https://buildd.debian.org/status/fetch.php?pkg=python3.10=all=3.10.0-4=1637323645=0 https://buildd.debian.org/status/fetch.php?pkg=python3.10=all=3.10.0-2=1634123522=0
Bug#1000187: yubikey-manager: Exception when trying to add an oath account
Package: yubikey-manager Version: 4.0.0~a1-4 Severity: grave Justification: renders package unusable Dear Maintainer, $ ykman oath accounts add foo bar always results in AttributeError: 'OATH_TYPE' object has no attribute 'upper' The only way to prevent this is to explicitly pass both oath type and algorithm: $ ykman oath accounts -o TOTP -a SHA1 add foo bar -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (420, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yubikey-manager depends on: ii pcscd 1.9.1-1 ii python3 3.9.2-3 ii python3-click 7.1.2-1 ii python3-cryptography 3.3.2-1 ii python3-fido2 0.9.1-1 ii python3-ykman 4.0.0~a1-4 yubikey-manager recommends no packages. yubikey-manager suggests no packages. -- no debconf information
Processed: salt: #983632
Processing commands for cont...@bugs.debian.org:
> unarchive 983632
Bug #983632 {Done: Benjamin Drung } [src:salt]
salt: CVE-2020-28243 CVE-2020-28972 CVE-2020-35662 CVE-2021-3148 CVE-2021-3144
CVE-2021-25281 CVE-2021-25282 CVE-2021-25283 CVE-2021-25284 CVE-2021-3197
Unarchived Bug 983632
> fixed 983632 2018.3.4+dfsg1-6+deb10u3
Bug #983632 {Done: Benjamin Drung } [src:salt]
salt: CVE-2020-28243 CVE-2020-28972 CVE-2020-35662 CVE-2021-3148 CVE-2021-3144
CVE-2021-25281 CVE-2021-25282 CVE-2021-25283 CVE-2021-25284 CVE-2021-3197
Marked as fixed in versions salt/2018.3.4+dfsg1-6+deb10u3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
983632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): salt: Set fixed version for security vulnerabilities
Processing commands for cont...@bugs.debian.org:
> fixed 983632 2018.3.4+dfsg1-6+deb10u3
Failed to add fixed on 983632: Not altering archived bugs; see unarchive.
> fixed 994016 2018.3.4+dfsg1-6+deb10u3
Bug #994016 {Done: Benjamin Drung } [src:salt] salt:
CVE-2021-21996 CVE-2021-22004
Marked as fixed in versions salt/2018.3.4+dfsg1-6+deb10u3.
> fixed 987496 2018.3.4+dfsg1-6+deb10u3
Failed to add fixed on 987496: Not altering archived bugs; see unarchive.
> fixed 994016 3002.6+dfsg1-4+deb11u1
Bug #994016 {Done: Benjamin Drung } [src:salt] salt:
CVE-2021-21996 CVE-2021-22004
Marked as fixed in versions salt/3002.6+dfsg1-4+deb11u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000157: marked as done (pampi FTBFS: pyuic5: No such file or directory)
Your message dated Fri, 19 Nov 2021 10:33:40 + with message-id and subject line Bug#1000157: fixed in pampi 1.1+dfsg1-3 has caused the Debian Bug report #1000157, regarding pampi FTBFS: pyuic5: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pampi Version: 1.1+dfsg1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=pampi=all=1.1%2Bdfsg1-2=1637082767=0 ... make[3]: Entering directory '/<>/pampi/libs' pyuic5 main.ui -o ui_main.py make[3]: pyuic5: No such file or directory make[3]: *** [Makefile:11: ui_main.py] Error 127 --- End Message --- --- Begin Message --- Source: pampi Source-Version: 1.1+dfsg1-3 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of pampi, 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. Georges Khaznadar (supplier of updated pampi 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: Thu, 18 Nov 2021 20:50:20 +0100 Source: pampi Architecture: source Version: 1.1+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 1000157 Changes: pampi (1.1+dfsg1-3) unstable; urgency=medium . * added the build-dependencies pyqt5-dev-tools and qttools5-dev-tools; Closes: #1000157. * patched the file Makefile2 to ease the command pylupdate5, and added a build-dependency on locales for the same goal Checksums-Sha1: 782b0336fd23e5a88bc5fd865be935678fbf1491 1935 pampi_1.1+dfsg1-3.dsc 6c0dbc339671f571f909696485a6164ef86f9d6c 19556 pampi_1.1+dfsg1-3.debian.tar.xz 3e47489405fca14084df855fb98187edb6479a59 11161 pampi_1.1+dfsg1-3_source.buildinfo Checksums-Sha256: ecc6d5f4aa5b5e0724b74530fd38a033ab2392658d55797e4b65f33a351a3b2d 1935 pampi_1.1+dfsg1-3.dsc edcc802b5f6da6594e0e58f79622e7425ef835a630457241b1d34416607eb1c0 19556 pampi_1.1+dfsg1-3.debian.tar.xz 1a3ebf826724ed2f46bddfb6084b5896c302936cef5d7ad16bffec8c996dba4c 11161 pampi_1.1+dfsg1-3_source.buildinfo Files: a98bceaa50c79fd529a671dbb1779dfc 1935 text optional pampi_1.1+dfsg1-3.dsc 7bbff13414283737226e6bfee3fbd911 19556 text optional pampi_1.1+dfsg1-3.debian.tar.xz 1da94e5ca2f2e5d1bad7628817780f73 11161 text optional pampi_1.1+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmGXepwUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmclQ/+K0O7j0xXaRWP5dguI3mODuPujm8n jvMe4kAZLplLFBypAtupA8wKhVP7KgYF/bloSuJIZYkpTcwDTkTG+X0vswn38DGz g5tdg3os3/qDj5qHtG1UvCiWs/QuSnOqV0bk1QZwPMZfiV9wjzzF+pQCahMbPVz9 u6qLNo9qOL1IKtXUhMqlSEfNSSAyZuarG86ifsuYyDuJK0owrL2zbxLgPSoij1Wa 8EOJLCxyHzaW0zSK/INWpl3q0dAu0daAAgqnC2kQ3zf6njOZ4zGAU9D1UVc/xAdw rNTLvPWfdt2K6EUMNh10LzQYtu6pXpFS/S1drqktSg59zzLt41pMtQKmv3HKglNx oPh0QcuLuavPKgaC9D+KS8f6+elLfyA3yLG5BnSXnH/oLTuzB5GynXyDqiPxAV84 NH4rgVQiGjXMFL5dB6jHze0zA97/IeHGV9o9eS8+Jpcjol9tkamIR8j/29x0ce92 CQX6BxkOrX1+TTU4cpIsqWbZUe+lnI/+3xaSYucLYNZUlowFnYVyFSkzKHy318Gj 5APMXM2YBOSngnLk7YQJNb4Cr9HlFYE6W5zX7AvG7EfsgUng1AAbBsbC8HIakVGJ 0SgxtCLFBizipHfKScyDbYgKOmq380pw1EKtAQ/ENkbSW/7kpR1fjZ3fbMoQ+HbE LheqGbTpwXiDhgw= =ouvv -END PGP SIGNATURE End Message ---
Bug#984345: marked as done (sphde: ftbfs with GCC-11)
Your message dated Fri, 19 Nov 2021 10:18:39 + with message-id and subject line Bug#984345: fixed in sphde 1.4.0-3 has caused the Debian Bug report #984345, regarding sphde: 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.) -- 984345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sphde Version: 1.4.0-2 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/sphde_1.4.0-2_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 getcwd... yes checking for getpagesize... (cached) yes checking for gettimeofday... yes checking for memset... yes checking for munmap... yes checking for strerror... yes checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking whether to check for GCC pthread/shared inconsistencies... yes checking whether -pthread is sufficient with -shared... yes checking for printf in -lc... yes checking whether C compiler accepts -mhtm... no checking for doxygen... /usr/bin/doxygen checking for perl... /usr/bin/perl checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating examples/Makefile config.status: creating src/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands dh_auto_build make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wwrite-strings -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o sasutil.o sasutil.c /bin/bash ../libtool --tag=CC --silent --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -D__SASSIM__ -Wall -Werror -Wwrite-strings -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libsphde_la-sasshm.lo `test -f 'sasshm.c' || echo './'`sasshm.c /bin/bash ../libtool --tag=CC --silent --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -D__SASSIM__ -Wall -Werror -Wwrite-strings -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libsphde_la-sasmsync.lo `test -f 'sasmsync.c' || echo './'`sasmsync.c /bin/bash ../libtool --tag=CC --silent --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -D__SASSIM__ -Wall -Werror -Wwrite-strings -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o
Processed: Bug#1000182 marked as pending in python-jira
Processing control commands: > tag -1 pending Bug #1000182 [src:python-jira] python-jira: network access during the build Ignoring request to alter tags of bug #1000182 to the same tags previously set -- 1000182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000182: marked as pending in python-jira
Control: tag -1 pending Hello, Bug #1000182 in python-jira 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-jira/-/commit/e950de00d3016bc67499a250b3adec1a933f23e4 Import Debian changes 3.1.1-1 python-jira (3.1.1-1) unstable; urgency=medium . * Team upload. * Fix dh_python depends (lintian error) * Add Salsa CI * Update standards version * Disable intersphinx-mapping in documentation build to prevent network access during the build. (Closes: #1000182) * New upstream release. (this message was generated automatically) -- Greetings https://bugs.debian.org/1000182
Processed: Can dh_sphinxdoc disable intersphinx_mapping support?
Processing commands for cont...@bugs.debian.org: > tag 1000184 - pending Bug #1000184 [sphinx-common] sphinx-common: dh_sphinxdoc support for intersphinx_mapping causes network access despite proxy setting Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000184: Can dh_sphinxdoc disable intersphinx_mapping support?
tag 1000184 - pending thanks Does dh_sphinxdoc need to also disable https: or does intersphinx_mapping have to be patched out of every package using Sphinx? This will inevitably cause another difference between the upstream documentation and the packaged documentation, unless some sort of cache can be created. For python-jira and a number of other Python packages, the only solution for now is to patch out intersphinx support entirely. (Spotted via a reproducibility failure). -- Neil Williams = https://linux.codehelp.co.uk/ pgpxm_a1KGWuE.pgp Description: OpenPGP digital signature
Processed: clone 1000182
Processing commands for cont...@bugs.debian.org: > clone 1000182 -1 Bug #1000182 [src:python-jira] python-jira: network access during the build Bug 1000182 cloned as bug 1000184 > reassign -1 sphinx-common 4.2.0-5 Bug #1000184 [src:python-jira] python-jira: network access during the build Bug reassigned from package 'src:python-jira' to 'sphinx-common'. No longer marked as found in versions python-jira/2.0.0-1 and python-jira/3.0-1. Ignoring request to alter fixed versions of bug #1000184 to the same values previously set Bug #1000184 [sphinx-common] python-jira: network access during the build Marked as found in versions sphinx/4.2.0-5. > retitle -1 sphinx-common: dh_sphinxdoc support for intersphinx_mapping causes > network access despite proxy setting Bug #1000184 [sphinx-common] python-jira: network access during the build Changed Bug title to 'sphinx-common: dh_sphinxdoc support for intersphinx_mapping causes network access despite proxy setting' from 'python-jira: network access during the build'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000182 1000184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1000182 marked as pending in python-jira
Processing control commands: > tag -1 pending Bug #1000182 [src:python-jira] python-jira: network access during the build Added tag(s) pending. -- 1000182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000182: marked as pending in python-jira
Control: tag -1 pending Hello, Bug #1000182 in python-jira 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-jira/-/commit/5a65b90b606cf01c0a06c9105def01fdc62873ec Disable intersphinx-mapping in documentation build to prevent network access during the build. (Closes: #1000182) (this message was generated automatically) -- Greetings https://bugs.debian.org/1000182
