Bug#997466: marked as done (texext: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sun, 05 Jun 2022 05:18:58 +
with message-id
and subject line Bug#997466: fixed in texext 0.6.7-1
has caused the Debian Bug report #997466,
regarding texext: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: texext
Version: 0.6.6-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):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_texext/build/texext
> copying texext/__init__.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext
> copying texext/math_dollar.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext
> copying texext/_version.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext
> copying texext/mathcode.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext
> creating /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/test_mathdollar.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/for_docstrings.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/test_plotdirective.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/conftest.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/test_custom_plotdirective.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/test_tinypages.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/test_docstrings.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> copying texext/tests/test_custom_plotcontext.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests
> creating
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/tinypages
> copying texext/tests/tinypages/some_math.rst ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/tinypages
> copying texext/tests/tinypages/index.rst ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/tinypages
> copying texext/tests/tinypages/conf.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/tinypages
> creating
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/tinypages/_static
> copying texext/tests/tinypages/_static/README.txt ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/tinypages/_static
> creating
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/plotdirective
> copying texext/tests/plotdirective/index.rst ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/plotdirective
> copying texext/tests/plotdirective/plot_and_math.rst ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/plotdirective
> copying texext/tests/plotdirective/conf.py ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/plotdirective
> creating
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/plotdirective/_static
> copying texext/tests/plotdirective/_static/README.txt ->
> /<>/.pybuild/cpython3_3.9_texext/build/texext/tests/plotdirective/_static
> UPDATING
> /<>/.pybuild/cpython3_3.9_texext/build/texext/_version.py
> set /<>/.pybuild/cpython3_3.9_texext/build/texext/_version.py to
> '0.6.6'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_texext/build;
> python3.9 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>
> collected 17 items
>
> texext/tests/test_custom_plotcontext.py [
> 23%]
> texext/tests/test_custom_plotdirective.py .. [
> 35%]
> texext/tests/test_docstrings.py F. [
> 47%]
> texext/tests/test_mathdollar.py .
Bug#997466: marked as pending in texext
Control: tag -1 pending Hello, Bug #997466 in texext 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/texext/-/commit/50e726029ed3aac3b661d2ee58bf54836a8090a0 New upstream release; Closes: #997466 (this message was generated automatically) -- Greetings https://bugs.debian.org/997466
Processed: Bug#997466 marked as pending in texext
Processing control commands:
> tag -1 pending
Bug #997466 [src:texext] texext: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.
--
997466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1012083 important Bug #1012083 [src:quickfix] quickfix FTBFS on riscv64 Severity set to 'important' from 'serious' > user debian-ri...@lists.debian.org Setting user to debian-ri...@lists.debian.org (was ab.bea...@gmail.com). > usertags 1012083 + riscv64 There were no usertags set. Usertags are now: riscv64. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1012181 important Bug #1012181 [src:ldc] ldc ftbfs on riscv64 Severity set to 'important' from 'serious' > user debian-ri...@lists.debian.org Setting user to debian-ri...@lists.debian.org (was ab.bea...@gmail.com). > usertags 1012181 + riscv64 There were no usertags set. Usertags are now: riscv64. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: linuxinfo FTBFS on riscv64
Processing control commands: > severity -1 important Bug #1012077 [linuxinfo] linuxinfo FTBFS on riscv64 Severity set to 'important' from 'serious' -- 1012077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012077: linuxinfo FTBFS on riscv64
Control: severity -1 important On Sun, 29 May 2022 14:45:29 -0400 Alan Beadle wrote: > Package: linuxinfo > Severity: serious > Tags: ftbfs patch upstream > Justification: fails to build from source ... > linuxinfo currently fails to build on riscv64 Please note that FTBFS bugs on unofficial non-release arches like riscv64 are not RC and so should only be filed at important severity. Please note that bugs in specific Debian architectures should be usertagged properly and XCCed to the architecture mailing list. Thanks for xiao sheng wen(肖盛文) for fixing this particular bug. https://wiki.debian.org/Teams/Debbugs/ArchitectureTags https://www.debian.org/Bugs/Reporting#xcc -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible
Control: tags -1 = moreinfo unreproducible Hi Lucas, Thank you for reaching out. I've been looking into this report and am a bit confused. I'm trying to reproduce it on my laptop, but it builds just fine for me. Can you please help me understand why it would fail on your end? -- regards, Reinhard
Processed: golang-github-opencontainers-runtime-tools: FTBFS unreproducible
Processing control commands: > tags -1 = moreinfo unreproducible Bug #1011875 [src:golang-github-opencontainers-runtime-tools] golang-github-opencontainers-runtime-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/opencontainers/runtime-tools/api/socket github.com/opencontainers/runtime-tools/cgroups github.com/opencontainers/runtime-tools/error github.com/opencontainers/runtime-tools/filepath github.com/opencontainers/runtime-tools/generate github.com/opencontainers/runtime-tools/generate/seccomp github.com/opencontainers/runtime-tools/specerror github.com/opencontainers/runtime-tools/validate returned exit code 1 Added tag(s) moreinfo and unreproducible; removed tag(s) ftbfs. -- 1011875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1006505
Processing commands for cont...@bugs.debian.org: > tags 1006505 + fixed-upstream Bug #1006505 [src:libsecp256k1] libsecp256k1: FTBFS with OpenSSL 3.0 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006127: marked as done (wireless-regdb stable policy)
Your message dated Sat, 04 Jun 2022 23:20:06 + with message-id and subject line Bug#1006127: fixed in wireless-regdb 2022.04.08-1 has caused the Debian Bug report #1006127, regarding wireless-regdb stable policy 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.) -- 1006127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wireless-regdb Version: 2021.08.28-1 Severity: grave Dear Maintainer wireless-regdb stores regulation information for various regions. It's importatnt to keep it updated on every system to ensure legal compliance on user's system. For example, China resctrcted transmission power for 5150 - 5350 MHz to 20 dBm, while the version in stable is still using the old 23 dBm limitation. System running stable can be accused violation of laws. Thus this package needs to be a part of security update to all stable release to prevent legal issues for users. Thanks. - Jiaxun --- End Message --- --- Begin Message --- Source: wireless-regdb Source-Version: 2022.04.08-1 Done: Ben Hutchings We believe that the bug you reported is fixed in the latest version of wireless-regdb, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated wireless-regdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Jun 2022 23:59:01 +0100 Source: wireless-regdb Architecture: source Version: 2022.04.08-1 Distribution: unstable Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 973551 1004347 1006127 Changes: wireless-regdb (2022.04.08-1) unstable; urgency=medium . * New upstream version: - Raise DFS TX power limit to 250 mW (24 dBm) for the US - Update regulatory rules for Croatia (HR) on 6GHz - Update regulatory rules for France (FR) on 6 and 60 GHz - add support for US S1G channels - add 802.11ah bands to world regulatory domain - Update regulatory rules for Spain (ES) on 6GHz - Update regulatory rules for South Korea (KR) - Update regulatory rules for China (CN) (Closes: #1006127) - Update regulatory rules for the Netherlands (NL) on 6GHz - Update regulatory rules for Israel (IL) - Update regulatory rules for Australia (AU) * d/salsa-ci.yml: Add CI configuration for salsa.debian.org * Remove support for loading through crda (Closes: #973551, #1004347) * d/.gitignore: Ignore another debhelper temporary file Checksums-Sha1: 7e156c5e458f82534b716e240dfe95cf1294d44d 2196 wireless-regdb_2022.04.08-1.dsc d8f47782be2621f8de5f26cf143bef4e24a5a69f 26308 wireless-regdb_2022.04.08.orig.tar.xz 1bbcd5ca6a45673131db6c9222a2073ebef83baf 16588 wireless-regdb_2022.04.08-1.debian.tar.xz fb75ce5ab3f612dd75f3f08755af3e1987bdcad0 6441 wireless-regdb_2022.04.08-1_amd64.buildinfo Checksums-Sha256: 1e71ae94862d127bc3ec7f23f52b894dcdccea71f714cfafb154033e67d60159 2196 wireless-regdb_2022.04.08-1.dsc 884ba2e3c1e8b98762b6dc25ff60b5ec75c8d33a39e019b3ed4aa615491460d3 26308 wireless-regdb_2022.04.08.orig.tar.xz 0e5e9983fb526e8c8a71fcb6fe9b7f9ea01c9121d0c89d5985a96a7636b9a721 16588 wireless-regdb_2022.04.08-1.debian.tar.xz a71bc9cc8a4849c4accab47332eb2b21a57f6f9dc0180d9215e23377e334258e 6441 wireless-regdb_2022.04.08-1_amd64.buildinfo Files: fab5c3a32143ce395ebb23449724c287 2196 net optional wireless-regdb_2022.04.08-1.dsc 902f51139e78a1d05bef76371ebc07fa 26308 net optional wireless-regdb_2022.04.08.orig.tar.xz 35e5813535c181b8cf053c9d7aa00d9b 16588 net optional wireless-regdb_2022.04.08-1.debian.tar.xz 8105f9dbbefadc9006c1a9c884d5111e 6441 net optional wireless-regdb_2022.04.08-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAmKb5RAACgkQ57/I7JWG EQkGxRAAuFSyf7qBkUNZKk33yQqDD8sIixgmuhNDQ4as9n+XB+YSmBQE8CIKpLj2 bKLZuhUze/4Rlt6q8aFD/p/fCQTP2YKmGOJnm14uRXBTTxeGCdc0zBW/tZnWgZBe BBOejaQXKcMIf5Xb7HoheL4WmJLAvwbO3Oh6FezQaWXeWhmhdij1bRTQ7i1P++QC sq7b/qPdTL6tXliiWiIdTjASaKfH32yYVHzp6lcrWX8RqsC4IryXqaarKbDcjgk5
Bug#1012120: libwww-dict-leo-org-perl: does not connect anymore
On Sat, 04 Jun 2022 14:54:12 +0200, Axel Beckert wrote: > I also checked what close() returns. It is actually "undef". Also > IO::Socket::SSL does not document any return value for close(). So the > return code is actually not meant to mean anything. Thanks for investigating this further! > Additionally the POD also states on close(): > > The default behavior is thus to only send a close notify but not > wait for the close notify of the peer. If this is required > "SSL_fast_shutdown" need to be explicitly set to false. > > So it also does have nothing on which a success or failure could be > determined. > > So IMHO we can and should just drop that "or die()". Full ack. > Will do Thanks for adding the fix and uploading! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1012338: librust-rusty-fork-dev: depends on missing package
Package: librust-rusty-fork-dev Version: 0.2.1-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKbwB4ACgkQLHwxRsGg ASEoGA//b2R5GdaZDryLmWjZOwI0tWvI69I6tkDijERZBq/cJqQZJUobn+yKhPY4 pIyzHZC/bN/kmuboTmKG2m0f5LpG5nyNauWK3ovxVP/AM/283lL/mOhXbCX2JGvo bUXIfFefX63bRTmh0Ce3xVu3xKOMlaM9pNu7nVXSgsmaRo2nICtEpuK2lz+Sgxe2 igo4iCbpxu/BbgIs0cgb1Qfzb7AQbZpZpuL3ygeA2uzsZmU80omKhz1byYIPRyFV tF1XCOebeXkGHlChICe7wPGMpDj5fO0HrQsYfVVsgvTE1lAecDRfvViABKZwI+JP oQqlGDERCrEoWFFDuM+1hjNNE80SwWtozpX8t+wwdPe7nV4om6kF5HG9QWcUhgNb HE+1yMEhoKi284N4fIdn7Zcva0JIeFrEby6HVtyNCEAJUuKKdCaDmgCyvLLUmEMP 8YX7xkn4NTyQ1Kcq9nKg4bJ6wGSd241YBuZNk7Iv+K5dtprgeOx+KxikjoTz2GRZ 1vg6WDMqT0Dmhaf6W6bcP6sGItpxu26sQG8/YNOhvmaviddhuOtMsDT0CAGDjAPL lBQah/3sHy+ANf9t+lOEdZ9a1YX6Yk/5ofsgF1lJA4PkKg9abTHjhVQ+BBArKWiD zXcgI01C+KC/gLC+YDxx7KnvFzhCaeIVF6S8TVKqBPPjfaxBwkY= =UADZ -END PGP SIGNATURE-
Bug#1012169: marked as done (cataclysm-dda: test-game intermittently fails with various different messages)
Your message dated Sat, 04 Jun 2022 19:34:16 + with message-id and subject line Bug#1012169: fixed in cataclysm-dda 0.F-3-4 has caused the Debian Bug report #1012169, regarding cataclysm-dda: test-game intermittently fails with various different messages 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.) -- 1012169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cataclysm-dda Version: 0.F-3-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky The autopkgtest for cataclysm-dda seems to be intermittently failing on multiple architectures. When testing a proposed update to a package it depends on (such as libsdl2 or unifont), the test failure is assumed to be a regression in the updated package, which can delay or prevent testing migration. For example, when tried on arm64 on 2022-05-28 21:23:19 UTC with src:unifont from unstable, it failed with: > An error has occurred! Written below is the error report: > --- > DEBUG: ERROR: Could not put plastic bottle (sealed) > clean water > (bottle_plastic) into inventory. Check if the profession (sheltered_survivor) > has enough space. but when retried with the same package set on 2022-05-29 22:13:21 UTC, it passed. Similarly, on i386 there have been several recent failures that succeeded when retried: https://ci.debian.net/packages/c/cataclysm-dda/testing/i386/ including this one while trying to test a new revision of libsdl2: > An error has occurred! Written below is the error report: > --- > DEBUG: Bad add_spawn(mon_zombie, 1, -10, 4) > FUNCTION : void map::add_spawn(const mtype_id&, int, const tripoint&, bool, >int, int, const string&, const spawn_data&) const > FILE : src/mapgen.cpp > LINE : 5356 > VERSION : 0.F-3 > --- > See /home/debci/.config/cataclysm-dda/debug.log for a full stack backtrace If possible, please make this test-case more reliable. Alternatively, if it is known not to be reliable enough to act as a QA gate, please mark it with "Restrictions: flaky" in debian/tests/control so that it does not have a negative impact on other packages. Thanks, smcv --- End Message --- --- Begin Message --- Source: cataclysm-dda Source-Version: 0.F-3-4 Done: Reiner Herrmann We believe that the bug you reported is fixed in the latest version of cataclysm-dda, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated cataclysm-dda package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Jun 2022 20:57:10 +0200 Source: cataclysm-dda Architecture: source Version: 0.F-3-4 Distribution: unstable Urgency: medium Maintainer: Reiner Herrmann Changed-By: Reiner Herrmann Closes: 1012169 Changes: cataclysm-dda (0.F-3-4) unstable; urgency=medium . * Mark autopkgtest as flaky, as it fails intermittently. (Closes: #1012169) * Mark two functions as unused to fix build errors on hurd. * Bump Standards-Version to 4.6.1. Checksums-Sha1: 86b754af7f2b39b31168327e5ba90b37a2d19d10 2233 cataclysm-dda_0.F-3-4.dsc a2ee7661380c3e24ee91239d1b2d1c9dbf57a034 25632 cataclysm-dda_0.F-3-4.debian.tar.xz 7936db52d3e057738b93548be4adce865d03 6295 cataclysm-dda_0.F-3-4_source.buildinfo Checksums-Sha256: bc7eaa558c4fee955b339a9f909e300dcd8ecd8936d7baf05e33805aa8ec9d16 2233 cataclysm-dda_0.F-3-4.dsc da575159d4ebae87dc42bc8f7a2b742be239b28ebf47d420f2d8c8a5b13ecf71 25632 cataclysm-dda_0.F-3-4.debian.tar.xz bd4c823eec31a2d42b7ab801c7a0e05db766306eb24924402a10575905778a80 6295 cataclysm-dda_0.F-3-4_source.buildinfo Files: c4ff6a1a8aa8ec8d882250ccaf10e8be 2233 games optional cataclysm-dda_0.F-3-4.dsc d1458db8923e5aa0bda1d4d399b8c89e 25632 games optional cataclysm-dda_0.F-3-4.debian.tar.xz 4e7cf97fb8d5e03962fdd36e354d11b9 6295 games optional
Bug#1011914: lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1
Thanks for the report. I can't reproduce this, though.
The code in question is this:
/*
* Get the host name and its IP address. Convert the IP address to
dotted
* ASCII form.
*/
if (gethostname(hnm, sizeof(hnm) - 1)) {
cem = "ERROR!!! can't get this host's name";
goto print_errno;
}
hnm[sizeof(hnm) - 1] = '\0';
if (!(hp = gethostbyname(hnm))) {
(void) snprintf(buf, bufl - 1, "ERROR!!! can't get IP address
for %s",
hnm);
buf[bufl - 1] = '\0';
It seems like gethostbyname() is failing, which presumably is a
misconfiguration on the part of the build host (probably something in
/etc/hosts?). I'm pretty sure local hostname forward and reverse
lookups don't violate policy 4.9 "required targets must not attempt
network access, except, via the loopback interface", but correct me if
I'm wrong.
I've attached the build log and the diff between our build logs, just
in case that's helpful (although you're using sbuild and I'm not, so
the diff isn't very readable).
On Thu, May 26, 2022 at 21:09, Lucas Nussbaum wrote:
Basic test:
LTbasic ... OK
Standard tests:
LTnlink ... OK
LTsock ... ERROR!!! can't get IP address for ip-10-84-234-90
Errno 0: Success
LTszoff ... OK
LTunix ... OK
Failed tests: 1
[...]
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
dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: source package lsof
dpkg-buildpackage: info: source version 4.95.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Andres Salomon
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
debian/rules clean
dh clean
rm -f debian/lsof.debhelper.log
debian/rules override_dh_auto_clean
make[1]: Entering directory '/lsof-4.95.0'
dh_auto_clean
make -j16 clean
make[2]: Entering directory '/lsof-4.95.0'
rm -f Makefile.bak lsof a.out core errs lint.out tags *.o version.h
rm -f machine.h.old new_machine.h
(cd lib; make -f Makefile.skel clean)
make[3]: Entering directory '/lsof-4.95.0/lib'
rm -f liblsof.a ckkv.o cvfs.o dvch.o fino.o isfn.o lkud.o pdvn.o prfp.o ptti.o
rdev.o regex.o rmnt.o rnam.o rnch.o rnmh.o snpf.o errs Makefile.bak a.out core
make[3]: Leaving directory '/lsof-4.95.0/lib'
(cd tests; make clean)
make[3]: Entering directory '/lsof-4.95.0/tests'
rm -f LTbasic LTnlink LTsock LTszoff LTunix LTbigf LTdnlc LTlock *.o *.err
*.out config.LT*
make[3]: Leaving directory '/lsof-4.95.0/tests'
(cd dialects/linux/tests; make clean)
make[3]: Entering directory '/lsof-4.95.0/dialects/linux/tests'
rm -f epoll eventfd mq_fork mq_open pidfd pipe pty ux open_with_flags *.o
make[3]: Leaving directory '/lsof-4.95.0/dialects/linux/tests'
make[2]: Leaving directory '/lsof-4.95.0'
rm -f dfile.c dlsof.h dmnt.c dnode.c dproc.c dproto.h dsock.c dstore.c
machine.h Makefile
rm -f lib/Makefile
cd tests && make clean && cd -
make[2]: Entering directory '/lsof-4.95.0/tests'
rm -f LTbasic LTnlink LTsock LTszoff LTunix LTbigf LTdnlc LTlock *.o *.err
*.out config.LT*
make[2]: Leaving directory '/lsof-4.95.0/tests'
/lsof-4.95.0
rm -f tests/config.cc tests/config.cflags tests/config.ldflags tests/configxobj
make[1]: Leaving directory '/lsof-4.95.0'
dh_clean
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f -- debian/lsof.substvars debian/files
rm -fr -- debian/lsof/ debian/tmp/
find . \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path
.\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o
-type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
\)
dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building lsof using existing ./lsof_4.95.0.orig.tar.bz2
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building lsof in lsof_4.95.0-1.debian.tar.xz
dpkg-source: info: building lsof in lsof_4.95.0-1.dsc
debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/lsof-4.95.0'
/Configure -n linux
Testing C library type with cc ... done
The C library type is glibc, version "-DGLIBCV=233".
rm -f ddev.c dfile.c dlsof.h dmnt.c dnode*.c dproc.c dproto.h dsock.c dstore.c
dzfs.h kernelbase.h machine.h machine.h.old new_machine.h __lseek.s Makefile
Makefile.zfs ./tests/config.cflags
rm -f ./tests/config.cc
Bug#1012336: dcm2niix: autopkgtest failure on s390x: 1 computed checksum did NOT match
Source: dcm2niix Version: 1.0.20211006-4 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package dcm2niix, great. However, it fails on s390x. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. Please be aware that s390x is a big-endian system, so if you are calculating md5sum checksums of generated files, I wouldn't be surprised if they are different by design. 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=dcm2niix https://ci.debian.net/data/autopkgtest/testing/s390x/d/dcm2niix/22051251/log.gz Chris Rorden's dcm2niiX version v1.0.20211006 (JP2:OpenJPEG) GCC11.3.0 (64-bit Linux) Found 85 DICOM file(s) Convert 85 DICOM as data/data_pasl_2d_20181218130847_3 (72x72x20x85) Conversion required 0.063600 seconds (0.047731 for core code). [93m[1mRunning Tests[0m data/data_pasl_2d_20181218130847_3.json: OK data/data_pasl_2d_20181218130847_3.nii: FAILED md5sum: WARNING: 1 computed checksum did NOT match autopkgtest [00:00:05]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature
Bug#1010066: prayer: Depends on private functions that are hidden with tidy 5.8
tisdag 31 maj 2022 kl. 16:11:03 CEST skrev Trent W. Buck: > https://sources.debian.org/src/prayer/1.3.5-dfsg1-8/session/html_secure_tid > y.c/#L274-L334 > https://api.html-tidy.org/tidy/tidylib_api_5.8.0/group__parser__h.html#ga46 > 769d54f0a1bcfd801d60c34eb563e7 > > Is it sufficient to simply change "prvTidyDiscardElement to > "TY_DiscardElement"? > > The TY_DiscardElement docs say "TY_Private". > Does that mean "you're not allowed to call this, either"? You mean TY_(DiscardElement)? TY_() is simply a macro that prepends "prvTidy" to the function name, but it's internal, which is why Prayer called it as prTidyDiscardElement(). What changed, however, is that those internal functions are now hidden so you _can't_ link them. At the same time, there is a public version now, tidyDiscardElement(), but there is no public tidyAddAttribute(), which is where we get stuck. > If so, we can build prayer without tidy at all. > Prayer will then use an older in-house HTML sanitizer: > > https://sources.debian.org/src/prayer/1.3.5-dfsg1-8/Config/?hl=16#L16 > > https://sources.debian.org/src/prayer/1.3.5-dfsg1-8/session/Makefile/#L27-L > 35 Well, not automatically. It's not bundled with the Prayer source. I don't know if it can be found anywhere. > The whole purpose of html_secure*.c is to "safely" embed an attacker's > untrusted HTML (the email) inside trusted HTML (the webmail app). > The code predates things like Content-Security-Policy (added circa 2013), > so it's probably *NEVER* safe, regardless of whether tidy is or isn't used. > > Prayer is abandoned upstream since the 201x's. > I can't find a direct citation, but here's the last time the "homepage" > existed: > > https://web.archive.org/web/20161129034822/http://www-uxsup.csx.cam.ac.uk:8 > 0/~dpc22/prayer/ > https://web.archive.org/web/20130701184507/http://www-uxsup.csx.cam.ac.uk/% > 7Edpc22/ Yeah, it may be time to let Prayer go. It's not exactly modern, and I don't even use it myself. -- Magnus Holmgrenholmg...@debian.org Debian Developer
Processed: astroquery: Autopkgtests failure due to trying to write to /usr/lib
Processing commands for cont...@bugs.debian.org:
> notfound 1012125 astroquery/0.4.1+dfsg-7
Bug #1012125 {Done: Vincent Prat } [src:astroquery]
astroquery: Autopkgtests failure due to trying to write to /usr/lib
No longer marked as found in versions astroquery/0.4.1+dfsg-7.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1012125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1012120: marked as done (libwww-dict-leo-org-perl: does not connect anymore)
Your message dated Sat, 04 Jun 2022 14:50:23 + with message-id and subject line Bug#1012120: fixed in libwww-dict-leo-org-perl 2.02-3 has caused the Debian Bug report #1012120, regarding libwww-dict-leo-org-perl: does not connect anymore 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.) -- 1012120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwww-dict-leo-org-perl Version: 2.02-2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: stephanlach...@debian.org, gre...@debian.org The package does not seem to work anymore. Calling it results in `Connection failed:` with no further information. Tested on multiple networks and machines. A debug log is given below. Probably an upstream issue. Cheers, Stephan Debug log: $ leo --debug test %DEBUG: connecting to site: dict.leo.org port 443 %DEBUG: GET /dictQuery/m-vocab/ende/query.xml?lp=ende=test HTTP/1.0 Connection failed: $ -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libwww-dict-leo-org-perl depends on: ii libio-socket-ssl-perl 2.074-2 ii liburi-encode-perl 1.1.1-1 ii libxml-simple-perl 2.25-1 ii perl 5.34.0-4 libwww-dict-leo-org-perl recommends no packages. libwww-dict-leo-org-perl suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libwww-dict-leo-org-perl Source-Version: 2.02-3 Done: Axel Beckert We believe that the bug you reported is fixed in the latest version of libwww-dict-leo-org-perl, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated libwww-dict-leo-org-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Jun 2022 16:19:58 +0200 Source: libwww-dict-leo-org-perl Architecture: source Version: 2.02-3 Distribution: unstable Urgency: high Maintainer: Debian Perl Group Changed-By: Axel Beckert Closes: 1012120 Changes: libwww-dict-leo-org-perl (2.02-3) unstable; urgency=high . * Add patch to show also HTTP headers in debug output. * Add patch to fix sending of the User-Agent header. (Fixes upstream RT bug report #131931.) * Add patch to no more check the return value of "close()", there is nothing it could indicate and there's no return code documented in IO::Socket::SSL(3) either. (Closes: #1012120) * Add myself to Uploaders. * Declare compliance with Debian Policy 4.6.1. (No changes needed.) * Bump debhelper-compat to 13. * Update packaging copyright years in debian/copyright and add myself. Checksums-Sha1: a6e8fcc9fde0cc3d32c798a99ad35ceafc16ff07 2301 libwww-dict-leo-org-perl_2.02-3.dsc d029e510a527f49d227ef0b2bdc20d3a32b7b2f5 4108 libwww-dict-leo-org-perl_2.02-3.debian.tar.xz f420db5667666c12d42fad54d4cdfcfffbae96d6 6285 libwww-dict-leo-org-perl_2.02-3_source.buildinfo Checksums-Sha256: f31961c4a556229a9e0479859cd5d40aff9ff1cd75fbcdb76cd7c97161660710 2301 libwww-dict-leo-org-perl_2.02-3.dsc 566a9c1fbd7ddeab97eb8bc367930b777fb04bfd4678bcbd0617bd740b38cd77 4108 libwww-dict-leo-org-perl_2.02-3.debian.tar.xz 603d5afcfa28d334d28c69265523e4b2419bd856d067d4c48a63a6e05bd11c85 6285 libwww-dict-leo-org-perl_2.02-3_source.buildinfo Files: c381071c9104affd24b2b17e9663111e 2301 perl optional libwww-dict-leo-org-perl_2.02-3.dsc e1026debf54a49c9be7d1d65d407beb1 4108 perl optional libwww-dict-leo-org-perl_2.02-3.debian.tar.xz 6cf59fc2870921b3c963d31ccaf7a007 6285 perl optional libwww-dict-leo-org-perl_2.02-3_source.buildinfo
Processed: Bug#1012120 marked as pending in libwww-dict-leo-org-perl
Processing control commands: > tag -1 pending Bug #1012120 [libwww-dict-leo-org-perl] libwww-dict-leo-org-perl: does not connect anymore Ignoring request to alter tags of bug #1012120 to the same tags previously set -- 1012120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012120: marked as pending in libwww-dict-leo-org-perl
Control: tag -1 pending Hello, Bug #1012120 in libwww-dict-leo-org-perl 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/perl-team/modules/packages/libwww-dict-leo-org-perl/-/commit/b313afa554f2d7d884cc61eb94e385ae316d2b7a Add patch to no more check the return value of "close()" There is nothing it could indicate and there's no return code documented in IO::Socket::SSL(3) either. Closes: #1012120 (this message was generated automatically) -- Greetings https://bugs.debian.org/1012120
Bug#1012077: linuxinfo FTBFS on riscv64
Hello Alan, On Sat, Jun 04, 2022 at 08:52:40AM -0400, Alan Beadle wrote: > It looks like this will always be a complex issue on RISC-V since > there is such a variety of manufacturers. However I think the > following would be the best approach. > > First, if there is a uarch field, use that since it will describe the > design of the cores present, such as Sifive's U74-MC which can be > licensed to other manufacturers, in a similar way to ARM core IP. > > If there isn't a uarch field, try to use the "model name" field if it > is present, since on the C910 this seems to replace the uarch field > (C910 is a core). > > Finally, if neither of those fields exist, the isa field might be ok > but I would add "unknown core" to the output. The letters at the end > of the isa field indicate which instruction set extensions are > present. (i for basic integer support, a for atomics, v for vector, > etc) So it is useful info, but it is vendor-generic for the most part. Ok, implented this. Thanks! I'll release the new version in the next days and then feedback is highly welcome (as I cannot try it out myself). Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#1012120: libwww-dict-leo-org-perl: does not connect anymore
Control: tag -1 + pending Hi, just run into this, too. gregor herrmann wrote: > Control: tag + confirmed bookworm sid Indeed, it still works on Debian 11 Bullseye, so it is clearly no change on the server side. (Which is reverse-proxied at Cloudflare and Cloudflare known to be quite easy on blocking specific user agents. And there seem to be User-Agent header related issues, too: https://rt.cpan.org/Public/Bug/Display.html?id=131931 — so that and the ancient "HTTP/1.0" were my first guesses for potential causes.) > A bit of debugging in the code shows that the "only" problem is > > 216 close $conn or die "Connection failed: $!\n"; > > in /usr/share/perl5/WWW/Dict/Leo/Org.pm. If I change the die() to a > warn() or comment out the line, everything works. Interesting, thanks! > I have no idea why "close $conn" fails, it might be related to > changes in OpenSSL3 and/or IO::Socket::SSL ($conn = new > IO::Socket::SSL(...)). -- $conn->close() fails as well without any > further information. I suspect OpenSSL3 as well because that was quite a bump in changes. Nevertheless, IO::Socket::SSL is inbetween, so I looked at its documentation. From the IO::Socket::SSL POD: IO::Socket::SSL tries to emulate the usual socket behavior as good as possible, but full emulation can not be done. Specifically a read on the SSL socket might also result in a write on the TCP socket or a write on the SSL socket might result in a read on the TCP socket. Also "accept" and close on the SSL socket will result in writing and reading data to the TCP socket too. Especially the hidden writes might result in a connection reset if the underlying TCP socket is already closed by the peer. Unless signal PIPE is explicitly handled by the application this will usually result in the application crashing. It is thus recommended to explicitly IGNORE signal PIPE so that the errors get propagated as EPIPE instead of causing a crash of the application. Tried that, but it didn't help. I also checked what close() returns. It is actually "undef". Also IO::Socket::SSL does not document any return value for close(). So the return code is actually not meant to mean anything. Additionally the POD also states on close(): The default behavior is thus to only send a close notify but not wait for the close notify of the peer. If this is required "SSL_fast_shutdown" need to be explicitly set to false. So it also does have nothing on which a success or failure could be determined. So IMHO we can and should just drop that "or die()". Will do and also add some more debug output to be easier able to debug such issues. Will also use that debug output to debug and possibly fix https://rt.cpan.org/Public/Bug/Display.html?id=131931 Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE signature.asc Description: PGP signature
Processed: Re: Bug#1012120: libwww-dict-leo-org-perl: does not connect anymore
Processing control commands: > tag -1 + pending Bug #1012120 [libwww-dict-leo-org-perl] libwww-dict-leo-org-perl: does not connect anymore Added tag(s) pending. -- 1012120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012077: linuxinfo FTBFS on riscv64
Hi Helge, It looks like this will always be a complex issue on RISC-V since there is such a variety of manufacturers. However I think the following would be the best approach. First, if there is a uarch field, use that since it will describe the design of the cores present, such as Sifive's U74-MC which can be licensed to other manufacturers, in a similar way to ARM core IP. If there isn't a uarch field, try to use the "model name" field if it is present, since on the C910 this seems to replace the uarch field (C910 is a core). Finally, if neither of those fields exist, the isa field might be ok but I would add "unknown core" to the output. The letters at the end of the isa field indicate which instruction set extensions are present. (i for basic integer support, a for atomics, v for vector, etc) So it is useful info, but it is vendor-generic for the most part. -Alan
Bug#1012275: closing 1012275
❦ 3 June 2022 20:48 +02, Salvatore Bonaccorso: > close 1012275 101.0-1 Unfortunately, Firefox is not buildable due to depending on a version of Cargo not available in unstable. -- Don't diddle code to make it faster - find a better algorithm. - The Elements of Programming Style (Kernighan & Plauger)
Bug#1006581: xmltooling: FTBFS with OpenSSL 3.0
On Mon, 23 May 2022 01:00:26 +0300 Adrian Bunk wrote: The segmentation fault looks fixed with the dependencies rebuilt with OpenSSL 3.0, but the test still fails: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xmltooling.html You can find the explanation for the tests failing in Ubuntu bug https://bugs.launchpad.net/ubuntu/+source/xmltooling/+bug/1957166 They handled it by replacing a certificate using RC2 with one using 3DES and disabled overwriting the cert by a download in the tests.
Bug#1012077: linuxinfo FTBFS on riscv64
Hello Alan,
hello Bo,
hello Xiao,
hello Tienhock,
I have preliminary support for riscv now locally. However, there is a
design question:
How would you put riscv processors into families? On x86, thats done
be vendor and some marketing label ("AMD" and "Ryzen"). On Alpha,
that's the model (i.e. generation).
Looking at the cpuinfos you send me, I think the field "isa" is the
suitable one. Is this correct?
If so, what should linuxinfo write:
rv64imafdc → ???
rv64imafdcsu → ???
any other?
Some (but not all) cpuinfo also carry the field uarch. But since this
is not always present, it doesn't look like a good candidate.
Greetings
Helge
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
Bug#1006575: NMU: sbsigntool: FTBFS with OpenSSL 3.0
Thanks Bastian! On Sat, Jun 04, 2022 at 01:46:49PM +0200, Bastian Germann wrote: >Ubuntu has the patches to fix this and another OpenSSL 3.0 error. >I have attached the debdiff that I have just uploaded to DELAYED/10. >diff -Nru sbsigntool-0.9.4/debian/changelog sbsigntool-0.9.4/debian/changelog >--- sbsigntool-0.9.4/debian/changelog 2021-09-14 06:39:01.0 + >+++ sbsigntool-0.9.4/debian/changelog 2022-06-04 11:37:27.0 + >@@ -1,3 +1,14 @@ >+sbsigntool (0.9.4-3.1) unstable; urgency=medium >+ >+ * Non-maintainer upload >+ >+ [ Simon Chopin ] >+ * Disable -Werror on deprecation warnings for the OpenSSL transition >+(Closes: #1006575) >+ * Apply patch to fix the OpenSSL3 build (LP: #1946193) >+ >+ -- Bastian Germann Sat, 04 Jun 2022 11:37:27 + >+ > sbsigntool (0.9.4-3) unstable; urgency=medium > > * Team upload >diff -Nru sbsigntool-0.9.4/debian/patches/OpenSSL3.patch >sbsigntool-0.9.4/debian/patches/OpenSSL3.patch >--- sbsigntool-0.9.4/debian/patches/OpenSSL3.patch 1970-01-01 >00:00:00.0 + >+++ sbsigntool-0.9.4/debian/patches/OpenSSL3.patch 2022-06-04 >11:36:45.0 + >@@ -0,0 +1,32 @@ >+Subject: Fix openssl-3.0 issue involving ASN1 xxx_it >+From: Jeremi Piotrowski >+Origin: https://groups.io/g/sbsigntools/message/54 >+ >+Use ASN1_ITEM_rptr() instead of taking the address of IDC_PEID_it. >+ >+openssl-3.0 changed the type of TYPE_it from `const ASN1_ITEM TYPE_it` to >+`const ASN1_ITEM *TYPE_it(void)`. This was previously hidden behind >+OPENSSL_EXPORT_VAR_AS_FUNCTION but in 3.0 only the function version is >+available. This change should have been transparent to the application, but >+only if the `ASN1_ITEM_rptr()` macro is used. >+ >+This change passes `make check` with both openssl 1.1 and 3.0. >+ >+Signed-off-by: Jeremi Piotrowski >+--- >+ src/idc.c | 2 +- >+ 1 file changed, 1 insertion(+), 1 deletion(-) >+ >+diff --git a/src/idc.c b/src/idc.c >+index 6d87bd4..0a82218 100644 >+--- a/src/idc.c > b/src/idc.c >+@@ -189,7 +189,7 @@ int IDC_set(PKCS7 *p7, PKCS7_SIGNER_INFO *si, struct >image *image) >+ >+ idc->data->type = OBJ_nid2obj(peid_nid); >+ idc->data->value = ASN1_TYPE_new(); >+- type_set_sequence(image, idc->data->value, peid, _PEID_it); >++ type_set_sequence(image, idc->data->value, peid, >ASN1_ITEM_rptr(IDC_PEID)); >+ >+ idc->digest->alg->parameter = ASN1_TYPE_new(); >+ idc->digest->alg->algorithm = OBJ_nid2obj(NID_sha256); >diff -Nru sbsigntool-0.9.4/debian/patches/series >sbsigntool-0.9.4/debian/patches/series >--- sbsigntool-0.9.4/debian/patches/series 2021-09-14 06:39:01.0 >+ >+++ sbsigntool-0.9.4/debian/patches/series 2022-06-04 11:36:09.0 >+ >@@ -1,3 +1,4 @@ > sbsign_check_write_return.patch > fix-efi-arch-detection.patch > 0001-sbsigntool-add-support-for-RISC-V-images.patch >+OpenSSL3.patch >diff -Nru sbsigntool-0.9.4/debian/rules sbsigntool-0.9.4/debian/rules >--- sbsigntool-0.9.4/debian/rules 2021-09-14 06:39:01.0 + >+++ sbsigntool-0.9.4/debian/rules 2022-06-04 11:37:18.0 + >@@ -4,6 +4,7 @@ > include /usr/share/dpkg/architecture.mk > include /usr/share/dpkg/pkg-info.mk > >+export DEB_CFLAGS_MAINT_APPEND=-Wno-error=deprecated-declarations > > # Uncomment this to turn on verbose mode. > export DH_VERBOSE=1 -- Steve McIntyre, Cambridge, UK.st...@einval.com "This dress doesn't reverse." -- Alden Spiess
Bug#1006575: NMU: sbsigntool: FTBFS with OpenSSL 3.0
Ubuntu has the patches to fix this and another OpenSSL 3.0 error. I have attached the debdiff that I have just uploaded to DELAYED/10.diff -Nru sbsigntool-0.9.4/debian/changelog sbsigntool-0.9.4/debian/changelog --- sbsigntool-0.9.4/debian/changelog 2021-09-14 06:39:01.0 + +++ sbsigntool-0.9.4/debian/changelog 2022-06-04 11:37:27.0 + @@ -1,3 +1,14 @@ +sbsigntool (0.9.4-3.1) unstable; urgency=medium + + * Non-maintainer upload + + [ Simon Chopin ] + * Disable -Werror on deprecation warnings for the OpenSSL transition +(Closes: #1006575) + * Apply patch to fix the OpenSSL3 build (LP: #1946193) + + -- Bastian Germann Sat, 04 Jun 2022 11:37:27 + + sbsigntool (0.9.4-3) unstable; urgency=medium * Team upload diff -Nru sbsigntool-0.9.4/debian/patches/OpenSSL3.patch sbsigntool-0.9.4/debian/patches/OpenSSL3.patch --- sbsigntool-0.9.4/debian/patches/OpenSSL3.patch 1970-01-01 00:00:00.0 + +++ sbsigntool-0.9.4/debian/patches/OpenSSL3.patch 2022-06-04 11:36:45.0 + @@ -0,0 +1,32 @@ +Subject: Fix openssl-3.0 issue involving ASN1 xxx_it +From: Jeremi Piotrowski +Origin: https://groups.io/g/sbsigntools/message/54 + +Use ASN1_ITEM_rptr() instead of taking the address of IDC_PEID_it. + +openssl-3.0 changed the type of TYPE_it from `const ASN1_ITEM TYPE_it` to +`const ASN1_ITEM *TYPE_it(void)`. This was previously hidden behind +OPENSSL_EXPORT_VAR_AS_FUNCTION but in 3.0 only the function version is +available. This change should have been transparent to the application, but +only if the `ASN1_ITEM_rptr()` macro is used. + +This change passes `make check` with both openssl 1.1 and 3.0. + +Signed-off-by: Jeremi Piotrowski +--- + src/idc.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/src/idc.c b/src/idc.c +index 6d87bd4..0a82218 100644 +--- a/src/idc.c b/src/idc.c +@@ -189,7 +189,7 @@ int IDC_set(PKCS7 *p7, PKCS7_SIGNER_INFO *si, struct image *image) + + idc->data->type = OBJ_nid2obj(peid_nid); + idc->data->value = ASN1_TYPE_new(); +- type_set_sequence(image, idc->data->value, peid, _PEID_it); ++ type_set_sequence(image, idc->data->value, peid, ASN1_ITEM_rptr(IDC_PEID)); + + idc->digest->alg->parameter = ASN1_TYPE_new(); + idc->digest->alg->algorithm = OBJ_nid2obj(NID_sha256); diff -Nru sbsigntool-0.9.4/debian/patches/series sbsigntool-0.9.4/debian/patches/series --- sbsigntool-0.9.4/debian/patches/series 2021-09-14 06:39:01.0 + +++ sbsigntool-0.9.4/debian/patches/series 2022-06-04 11:36:09.0 + @@ -1,3 +1,4 @@ sbsign_check_write_return.patch fix-efi-arch-detection.patch 0001-sbsigntool-add-support-for-RISC-V-images.patch +OpenSSL3.patch diff -Nru sbsigntool-0.9.4/debian/rules sbsigntool-0.9.4/debian/rules --- sbsigntool-0.9.4/debian/rules 2021-09-14 06:39:01.0 + +++ sbsigntool-0.9.4/debian/rules 2022-06-04 11:37:18.0 + @@ -4,6 +4,7 @@ include /usr/share/dpkg/architecture.mk include /usr/share/dpkg/pkg-info.mk +export DEB_CFLAGS_MAINT_APPEND=-Wno-error=deprecated-declarations # Uncomment this to turn on verbose mode. export DH_VERBOSE=1
Bug#1008776: marked as done (intel-media-va-driver: Segmentation fault with gstreamer based applications)
Your message dated Sat, 04 Jun 2022 11:04:55 + with message-id and subject line Bug#1008776: fixed in intel-media-driver 22.4.2+dfsg1-2 has caused the Debian Bug report #1008776, regarding intel-media-va-driver: Segmentation fault with gstreamer based applications 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.) -- 1008776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: intel-media-va-driver Version: 22.3.0+dfsg1-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: kai.weber+deb...@glorybox.de Dear Maintainer, since a recent update (can not excalty determine the date) gstreamer based applications like totem or gst-play-1.0 itself segfault on video files. Removing intel-media-va-driver resolves the issue. Installing intel-media-va-driver-non-free resolves the issue. Attached is a backtrace. I have no experience getting backtraces. This one was achieved after install the intel-media-va-driver-dbgsym package and running $ export DEBUGINFOD_URLS="https://debuginfod.debian.net; $ gdb --args gst-play-1.0 /home/kai/Downloads/pony.mp4 --videosink=glimagesink Thread 14 "qtdemux0:sink" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffb77fe640 (LWP 22147)] 0x7fffb5f906be in KernelDll_AllocateStates (pKernelBin=, uKernelSize=0, pFcPatchCache=0x0, uFcPatchCacheSize=, pDefaultRules=0x0, ModifyFunctionPointers=0x0) at ./media_driver/agnostic/common/vp/kdll/hal_kerneldll.c:2791 Download failed: Invalid argument. Continuing without source file ./obj-x86_64-linux-gnu/media_driver/./media_driver/agnostic/common/vp/kdll/hal_kerneldll.c. 2791./media_driver/agnostic/common/vp/kdll/hal_kerneldll.c: No such file or directory. (gdb) set logging file backtrace.log (gdb) set logging on Copying output to backtrace.log. (gdb) bt ... (gdb) set logging off Done logging to backtrace.log. (gdb) quit -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages intel-media-va-driver depends on: ii libc6 2.33-7 ii libgcc-s1 12-20220319-1 ii libigdgmm12 22.1.2+ds1-1 ii libstdc++6 12-20220319-1 ii libva2 [libva-driver-abi-1.14] 2.14.0-1 intel-media-va-driver recommends no packages. intel-media-va-driver suggests no packages. -- no debconf information #0 0x7fffb5f906be in KernelDll_AllocateStates (pKernelBin=, uKernelSize=0, pFcPatchCache=0x0, uFcPatchCacheSize=, pDefaultRules=0x0, ModifyFunctionPointers=0x0) at ./media_driver/agnostic/common/vp/kdll/hal_kerneldll.c:2791 #1 0x7fffb5f82028 in VphalRenderer::Initialize (this=0x7fffa813d480, pSettings=0x7fffb77fae80, isApoEnabled=) at ./media_driver/agnostic/common/vp/hal/vphal_renderer.cpp:1418 #2 0x7fffb5f67a89 in VphalState::Allocate (this=0x7fffa8123e50, pVpHalSettings=0x7fffb77fae80) at ./media_driver/agnostic/common/vp/hal/vphal.cpp:201 #3 0x7fffb61848a2 in DdiVp_InitVpHal (pVpCtx=0x7fffa812add0) at ./media_driver/linux/common/vp/ddi/media_libva_vp.c:1811 #4 0x7fffb6189460 in DdiVp_InitCtx (pVaDrvCtx=, pVpCtx=0x7fffa812add0) at ./media_driver/linux/common/vp/ddi/media_libva_vp.c:1671 #5 0x7fffb618985e in DdiVp_CreateContext (pVaDrvCtx=pVaDrvCtx@entry=0x7fffa8081e20, vaConfigID=vaConfigID@entry=0, iWidth=iWidth@entry=0, iHeight=iHeight@entry=0, iFlag=iFlag@entry=0, vaSurfIDs=vaSurfIDs@entry=0x0, iNumSurfs=0, pVaCtxID=0x7fffb77fb1ac) at ./media_driver/linux/common/vp/ddi/media_libva_vp.c:3291 #6 0x7fffb6147be2 in DdiMedia_PutImage (ctx=0x7fffa8081e20, surface=0, image=, src_x=0, src_y=0, src_width=64, src_height=64, dest_x=0, dest_y=0, dest_width=64, dest_height=64) at ./media_driver/linux/common/ddi/media_libva.cpp:5535 #7 0x7fffd425521c in vaPutImage () from /lib/x86_64-linux-gnu/libva.so.2 #8 0x7fffd42def8d in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so #9 0x7fffd429d686 in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so #10 0x7fffd42a480e in ?? () from
Processed (with 1 error): llvm-toolchain-12 soon to be removed from testing but we like to remove -11 too
Processing commands for cont...@bugs.debian.org:
> retitle 1000932 Please upgrade to llvm-toolchain-13 or 14
Bug #1000932 [src:doxygen] doxygen: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from 'doxygen:
Please upgrade to llvm-toolchain-12 or 13'.
> merge 1000891 1000927
Bug #1000891 [src:creduce] creduce: Please upgrade to llvm-toolchain-12 or 13
Unable to merge bugs because:
blocks of #1000927 is '1000941' not '974789'
Failed to merge 1000891: Did not alter merged bugs.
> retitle 1000927 Please upgrade to llvm-toolchain-13 or 14
Bug #1000927 [src:creduce] creduce: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from 'creduce:
Please upgrade to llvm-toolchain-12 or 13'.
> retitle 1000929 Please upgrade to llvm-toolchain-13 or 14
Bug #1000929 [src:ghc] ghc: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from 'ghc:
Please upgrade to llvm-toolchain-12 or 13'.
> retitle 1000917 Please upgrade to llvm-toolchain-13 or 14
Bug #1000917 [src:libclc] libclc: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from 'libclc:
Please upgrade to llvm-toolchain-12 or 13'.
> clone 1012183 -1
Bug #1012183 {Done: Andreas Beckmann }
[src:intel-vc-intrinsics] intel-vc-intrinsics: please migrate to other llvm
version for building
Bug 1012183 cloned as bug 1012329
> reopen -1
Bug #1012329 {Done: Andreas Beckmann }
[src:intel-vc-intrinsics] intel-vc-intrinsics: please migrate to other llvm
version for building
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions intel-vc-intrinsics/0.4.2-2.
> severity -1 important
Bug #1012329 [src:intel-vc-intrinsics] intel-vc-intrinsics: please migrate to
other llvm version for building
Severity set to 'important' from 'serious'
> retitle -1 Please upgrade to llvm-toolchain-13 or 14
Bug #1012329 [src:intel-vc-intrinsics] intel-vc-intrinsics: please migrate to
other llvm version for building
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from
'intel-vc-intrinsics: please migrate to other llvm version for building'.
> retitle 1000922 Please upgrade to llvm-toolchain-13 or 14
Bug #1000922 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from
'llvmlite: Please upgrade to llvm-toolchain-12 or 13'.
> retitle 1001317 Please upgrade to llvm-toolchain-13 or 14
Bug #1001317 [src:pocl] pocl: switch to llvm-toolchain-13
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from 'pocl:
switch to llvm-toolchain-13'.
> retitle 1004883 Please upgrade to llvm-toolchain-13 or 14
Bug #1004883 [src:intel-graphics-compiler] intel-graphics-compiler: switch to
llvm-toolchain-13
Changed Bug title to 'Please upgrade to llvm-toolchain-13 or 14' from
'intel-graphics-compiler: switch to llvm-toolchain-13'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000891
1000917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000917
1000922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000922
1000927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000927
1000929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000929
1000932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000932
1001317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001317
1004883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004883
1012183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012183
1012329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found
Processing commands for cont...@bugs.debian.org: > found 1006511 5.9.1+dfsg-2 Bug #1006511 [src:net-snmp] net-snmp: FTBFS with OpenSSL 3.0 The source 'net-snmp' and version '5.9.1+dfsg-2' do not appear to match any binary packages Marked as found in versions net-snmp/5.9.1+dfsg-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 1006511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: libsecp256k1: FTBFS with OpenSSL 3.0
Processing control commands: > forwarded -1 https://github.com/bitcoin-core/secp256k1/pull/983 Bug #1006505 [src:libsecp256k1] libsecp256k1: FTBFS with OpenSSL 3.0 Set Bug forwarded-to-address to 'https://github.com/bitcoin-core/secp256k1/pull/983'. -- 1006505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006505: libsecp256k1: FTBFS with OpenSSL 3.0
Control: forwarded -1 https://github.com/bitcoin-core/secp256k1/pull/983 The failing tests are now dropped. Please just import a newer version.
Processed: fixed version
Processing commands for cont...@bugs.debian.org: > fixed 1006022 5.6.4-1 Bug #1006022 [src:puma] puma: flaky tests Marked as fixed in versions puma/5.6.4-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1006022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012022: marked as done (fenics-basix: FTBFS during separate binary-indep build)
Your message dated Sat, 04 Jun 2022 10:03:54 + with message-id and subject line Bug#1012022: fixed in fenics-basix 0.4.2-1exp2 has caused the Debian Bug report #1012022, regarding fenics-basix: FTBFS during separate binary-indep build 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.) -- 1012022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fenics-basix Version: 0.4.0-1exp1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, fenics-basix/experimental FTBFS while performing a separate binary-indep build as would be done by the buildds. You can do that manually with dpkg-builpackage -A. [...] debian/rules execute_before_dh_install-indep make[1]: Entering directory '/build/fenics-basix-0.4.0' py3versions: no X-Python3-Version in control file, using supported versions LD_LIBRARY_PATH=/build/fenics-basix-0.4.0/debian/tmp/usr/lib/x86_64-linux-gnu PYTHONPATH=/build/fenics-basix-0.4.0/debian/python3-basix/usr/lib/python3.10/dist-packages: /usr/bin/make -C doc/python html make[2]: Entering directory '/build/fenics-basix-0.4.0/doc/python' Running Sphinx v4.5.0 Configuration error: There is a programmable error in your configuration file: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/config.py", line 332, in eval_config_file exec(code, namespace) File "/build/fenics-basix-0.4.0/doc/python/source/conf.py", line 10, in import basix ModuleNotFoundError: No module named 'basix' make[2]: *** [Makefile:20: html] Error 2 make[2]: Leaving directory '/build/fenics-basix-0.4.0/doc/python' make[1]: *** [debian/rules:71: execute_before_dh_install-indep] Error 2 make[1]: Leaving directory '/build/fenics-basix-0.4.0' make: *** [debian/rules:42: binary-indep] Error 2 Andreas fenics-basix_0.4.0-1exp1_indep.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: fenics-basix Source-Version: 0.4.2-1exp2 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of fenics-basix, 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 1012...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated fenics-basix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jun 2022 11:13:03 +0200 Source: fenics-basix Architecture: source Version: 0.4.2-1exp2 Distribution: experimental Urgency: medium Maintainer: Debian Science Team Changed-By: Drew Parsons Closes: 1012022 Changes: fenics-basix (0.4.2-1exp2) experimental; urgency=medium . * build python module also in arch-indep builds to enable doc build Closes: #1012022. Checksums-Sha1: b2943cc8010f235ffbb4802502e7ce353b04f846 2816 fenics-basix_0.4.2-1exp2.dsc f21f7fe7a9212b57a71f62910bfd69327bbae88e 9056 fenics-basix_0.4.2-1exp2.debian.tar.xz Checksums-Sha256: 8f43df78b0a4110a5b11a450f28c36f69e6dddfbbc961974c1c2919794a0dd1d 2816 fenics-basix_0.4.2-1exp2.dsc ba36e712a50eea06e5d1e7da98475f276dff04102fd3fb2d83079084ea116a2d 9056 fenics-basix_0.4.2-1exp2.debian.tar.xz Files: 2cb93b8a61a79cc302bdddc47c7cd013 2816 python optional fenics-basix_0.4.2-1exp2.dsc 9e466e4238573293dad31728d77b427c 9056 python optional fenics-basix_0.4.2-1exp2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmKbKroACgkQVz7x5L1a Afp5GA//UlUF+UYZbTHa1Ad62FliEHTQxFsPTdQ8OwMKN4y2cZ6GaTm8RSzlnwCK 4i/LLr4/Xkus199YRmulTILWloWjizRemRbNxX0EmyOYopkYTxmuWIFsjFaEsJfb YzU4z4iuhXnqEhvetz8NiI/uN9sLg5ENDaMcd9eq6+oF35UDWvnLxaf+mtj9qkJf lmrPd1YZ3G9oQhVx+s2ar28iNNmZrvrKaa+XsiGZVQBVgrYJiTYHse255hsYA30V 6LLXNFGzxvNnrJfaIkNToxWO/uS9H7YSDjpnVLbBuTCRkLyDWqiV8SxaqjGm9sln TeJBeoRYzAsP0oo9NYdP11zXsvYNaxbi/X50NxvYvi1/mc/HQSJozgSsv+OL/Re6 zqpw4OwL7vR9bqE97irZJUe90lkDqHAQiubMLnFGR7dBKckxxHIu6wYeF2KVPf/1 FuL7OSgMmNWwxJ+Y1RrjSRlx2CX2Br4QyouScLBXtXOjhQROhTSZ30FfMbDmFN/2 U8sfg6/K/AqqRRgGwezVNLSprnneuEfTWPj97JUYkKr9PBNFjqfwBdGzfW2x1y4u fe+h4kmbvJYDl9iOcuATZqhjiYrgzh7gej/k+F2sTkIrMsCja4QsRs8qMMSZFZLK
Bug#980023: petri-foo: FTBFS with GCC 10
The last release which contained petri-foo was stretch and upstream is going nowhere. I suggest to file a RM bug and if nobody reacts on this I am going to file one in a month.
Bug#1011807: marked as done (twitter-bootstrap4: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1)
Your message dated Sat, 04 Jun 2022 09:34:44 +
with message-id
and subject line Bug#1011807: fixed in twitter-bootstrap4 4.6.1+dfsg1-2
has caused the Debian Bug report #1011807,
regarding twitter-bootstrap4: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_build] Error 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1011807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twitter-bootstrap4
Version: 4.6.1+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 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 '/<>'
> mkdir -p dist/css dist/js dist/tmp
> sassc --sourcemap=auto scss/bootstrap.scss dist/tmp/bootstrap.css
> sassc --sourcemap=auto scss/bootstrap-grid.scss dist/tmp/bootstrap-grid.css
> sassc --sourcemap=auto scss/bootstrap-reboot.scss
> dist/tmp/bootstrap-reboot.css
> node debian/postcss.js
>
> Replace Autoprefixer browsers option to Browserslist config.
> Use browserslist key in package.json or .browserslistrc file.
>
> Using browsers option can cause errors. Browserslist config can
> be used for Babel, Autoprefixer, postcss-normalize and other tools.
>
> If you really need to use option, rename it to overrideBrowserslist.
>
> Learn more at:
> https://github.com/browserslist/browserslist#readme
> https://twitter.com/browserslist
>
>
> node:internal/errors:464
> ErrorCaptureStackTrace(err);
> ^
>
> TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string
> or an instance of Buffer, TypedArray, or DataView. Received an instance of
> SourceMapGenerator
> at Object.writeFile (node:fs:2110:5)
> at node:internal/util:360:7
> at new Promise ()
> at Object.writeFile (node:internal/util:346:12)
> at /<>/debian/postcss.js:40:32 {
> code: 'ERR_INVALID_ARG_TYPE'
> }
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/05/25/twitter-bootstrap4_4.6.1+dfsg1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: twitter-bootstrap4
Source-Version: 4.6.1+dfsg1-2
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
twitter-bootstrap4, 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 1011...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated twitter-bootstrap4 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 04 Jun 2022 11:19:52 +0200
Source: twitter-bootstrap4
Binary: libjs-bootstrap4
Architecture: source all
Version: 4.6.1+dfsg1-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Description:
libjs-bootstrap4 - HTML, CSS and JS framework
Closes: 1011807
Changes:
twitter-bootstrap4 (4.6.1+dfsg1-2) experimental; urgency=medium
.
* Team upload
* Replace custom postcss.js by use of node-postcss-cli (Closes: #1011807)
Checksums-Sha1:
7454761205d262b8fa26491298e335a11bbd8102 2348
twitter-bootstrap4_4.6.1+dfsg1-2.dsc
578c3f7f6e6021f5ca91cdb26315c3bdfb0c96d5 18940
twitter-bootstrap4_4.6.1+dfsg1-2.debian.tar.xz
77255dfa86fc34c8daad392c3f1d8280cb78cf5b 526432
Bug#907691: marked as done (petri-foo: License incompatibility: links with OpenSSL)
Your message dated Sat, 4 Jun 2022 11:32:44 +0200 with message-id and subject line Re: petri-foo: License incompatibility: links with OpenSSL has caused the Debian Bug report #907691, regarding petri-foo: License incompatibility: links with OpenSSL 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.) -- 907691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: petri-foo Version: 0.1.87-4 Severity: serious This package is licensed under GPLv2 only but links with the OpenSSL library which makes it impossible for distribution as the licenses are incompatible. See https://www.gnu.org/licenses/license-list.html#OpenSSL https://people.gnome.org/~markmc/openssl-and-the-gpl.html You either have to ask the copyright holders to release it under GPL + OpenSSL exception or modify it to link with another cryptographic library such as GnuTLS. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages petri-foo depends on: ii libart-2.0-2 2.3.21-3 ii libasound21.1.6-1 ii libatk1.0-0 2.28.1-1 ii libc6 2.27-5 ii libcairo2 1.15.12-1 ii libfontconfig12.13.0-5 ii libfreetype6 2.8.1-2 ii libgdk-pixbuf2.0-02.36.12-2 ii libglib2.0-0 2.56.1-2 ii libgnomecanvas2-0 2.30.3-3 ii libgtk2.0-0 2.24.32-3 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2 ii liblo70.29-1 ii libpango-1.0-01.42.4-2 ii libpangocairo-1.0-0 1.42.4-2 ii libpangoft2-1.0-0 1.42.4-2 ii libpangoxft-1.0-0 1.42.4-2 ii libsamplerate00.1.9-2 ii libsndfile1 1.0.28-4 ii libssl1.1 1.1.1~~pre9-1 ii libxml2 2.9.4+dfsg1-7+b1 petri-foo recommends no packages. petri-foo suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 35297--- End Message ---
Bug#1011807: marked as pending in twitter-bootstrap4
Control: tag -1 pending Hello, Bug #1011807 in twitter-bootstrap4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/twitter-bootstrap4/-/commit/f28f7b3b6bb3466aff95bb13f6cc22a7e44507f6 Replace custom postcss.js by use of node-postcss-cli Closes: #1011807 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011807
Processed: Bug#1011807 marked as pending in twitter-bootstrap4
Processing control commands: > tag -1 pending Bug #1011807 [src:twitter-bootstrap4] twitter-bootstrap4: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1011807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012252: marked as done (debhelper: execute_after not executed for binary-indep build)
Your message dated Sat, 04 Jun 2022 11:10:04 +0200 with message-id <0fbe05e56c699b78bd9fb9b2098d4...@debian.org> and subject line Re: Bug#1012252: debhelper: execute_after not executed for binary-indep build has caused the Debian Bug report #1012252, regarding debhelper: execute_after not executed for binary-indep build 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.) -- 1012252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debhelper Version: 13.7.1 Severity: Serious Justification: FTBFS Control: block 1012022 by -1 fenics-basix 0.4.2-1exp1 is currently failing to build in a binary-indep build, see https://buildd.debian.org/status/logs.php?pkg=fenics-basix=all The problem occurs when building docs in an execute_before_dh_install-indep rule. The doc build (via sphinx) expects the basix python module to have been built. The rules file is available at https://tracker.debian.org/media/packages/f/fenics-basix/rules-0.4.2-1exp1 The python module build is supposed to have been performed already in an execute_after_dh_auto_install rule (after dh_auto_install has put the libbasix.so shared library in place). We can see in the binary-indep log at https://buildd.debian.org/status/fetch.php?pkg=fenics-basix=all=0.4.2-1exp1=1654102080=0 that libbasix.so did get built by the override_dh_auto_build rule, and got installed by dh_auto_install -i. But after dh_auto_install -i, the next rule that gets run is execute_before_dh_install-indep. execute_after_dh_auto_install never gets run. This doesn't meet the intention of the rules file. execute_after_dh_auto_install should be run after dh_auto_install, with or without the -i flag, shouldn't it? In particular, dh --no-act indicates it should have been executed: $ dh binary-indep --no-act dh_testroot -i dh_prep -i dh_installdirs -i dh_auto_install -i debian/rules execute_after_dh_auto_install debian/rules execute_before_dh_install-indep dh_install -i dh_installdocs -i ... So it looks like a bug in dh during actual execution, that the execute_after_dh_auto_install rule is not getting executed. This bug is blocking #1012022, which is Severity: serious (FTBFS), hence I'm marking this bug Severity: serious (FTBFS) to match. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debhelper depends on: ii autotools-dev20220109.1 ii dh-autoreconf20 ii dh-strip-nondeterminism 1.13.0-1 ii dpkg 1.21.8 ii dpkg-dev 1.21.8 ii dwz 0.14-1 ii file 1:5.41-4 ii libdebhelper-perl13.7.1 ii libdpkg-perl 1.21.8 ii man-db 2.10.2-1 ii perl 5.34.0-4 ii po-debconf 1.0.21+nmu1 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 2.202201 -- no debconf information --- End Message --- --- Begin Message --- On 2022-06-04 09:17, Niels Thykier wrote: Control: tags -1 moreinfo Drew Parsons: fenics-basix 0.4.2-1exp1 is currently failing to build in a binary-indep build, see https://buildd.debian.org/status/logs.php?pkg=fenics-basix=all ... The bug report contains inconsistent information. The bug report says and includes a dh --no-act that implies there is a rule called "execute_after_dh_auto_install" in debian/rules. However, the rules files provided via "https://tracker.debian.org/media/packages/f/fenics-basix/rules-0.4.2-1exp1; does *not* have that rule. Instead it has the "execute_after_dh_auto_install-arch" rule, which would explain a lot of the issues you are reporting. You're absolutely right. I thought I had checked that. I had removed the -arch locally but got confused about which release I put that change into. I apologize for the distraction. Drew--- End Message ---
Bug#1012326: python-jenkinsapi: build-depends on pylint3
Source: python-jenkinsapi Version: 0.3.11-5 Severity: serious Usertags: edos-uninstallable Hi, python-jenkinsapi build-depends on pylint3 but that package only exists in stable and older stable releases. -Ralf.
Processed: Re: Bug#1012252: debhelper: execute_after not executed for binary-indep build
Processing control commands: > tags -1 moreinfo Bug #1012252 [debhelper] debhelper: execute_after not executed for binary-indep build Added tag(s) moreinfo. -- 1012252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012252: debhelper: execute_after not executed for binary-indep build
Control: tags -1 moreinfo Drew Parsons: > Package: debhelper > Version: 13.7.1 > Severity: Serious > Justification: FTBFS > Control: block 1012022 by -1 > > fenics-basix 0.4.2-1exp1 is currently failing to build in a > binary-indep build, see > https://buildd.debian.org/status/logs.php?pkg=fenics-basix=all > > The problem occurs when building docs in an > execute_before_dh_install-indep rule. The doc build (via sphinx) > expects the basix python module to have been built. The rules file is > available at > https://tracker.debian.org/media/packages/f/fenics-basix/rules-0.4.2-1exp1 > > The python module build is supposed to have been performed already in > an execute_after_dh_auto_install rule (after dh_auto_install has put > the libbasix.so shared library in place). > > We can see in the binary-indep log at > https://buildd.debian.org/status/fetch.php?pkg=fenics-basix=all=0.4.2-1exp1=1654102080=0 > that libbasix.so did get built by the override_dh_auto_build rule, and > got installed by dh_auto_install -i. > > But after dh_auto_install -i, the next rule that gets run is > execute_before_dh_install-indep. execute_after_dh_auto_install never > gets run. > > This doesn't meet the intention of the rules file. > execute_after_dh_auto_install should be run after dh_auto_install, > with or without the -i flag, shouldn't it? > > In particular, dh --no-act indicates it should have been executed: > > $ dh binary-indep --no-act >dh_testroot -i >dh_prep -i >dh_installdirs -i >dh_auto_install -i >debian/rules execute_after_dh_auto_install >debian/rules execute_before_dh_install-indep >dh_install -i >dh_installdocs -i >... > > > So it looks like a bug in dh during actual execution, that the > execute_after_dh_auto_install rule is not getting executed. > > This bug is blocking #1012022, which is Severity: serious (FTBFS), > hence I'm marking this bug Severity: serious (FTBFS) to match. > > > [...] Hi, The bug report contains inconsistent information. The bug report says and includes a dh --no-act that implies there is a rule called "execute_after_dh_auto_install" in debian/rules. However, the rules files provided via "https://tracker.debian.org/media/packages/f/fenics-basix/rules-0.4.2-1exp1; does *not* have that rule. Instead it has the "execute_after_dh_auto_install-arch" rule, which would explain a lot of the issues you are reporting. If you have linked to the wrong debian/rules file, then please provide an updated link. Thanks, ~Niels
Processed: Re: Bug#1012252: debhelper: execute_after not executed for binary-indep build
Processing control commands: > tags -1 moreinfo Bug #1012252 [debhelper] debhelper: execute_after not executed for binary-indep build Ignoring request to alter tags of bug #1012252 to the same tags previously set -- 1012252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ITP: node-postcss-cli -- Command-line client for node-postcss
Processing control commands: > block 1011807 by -1 Bug #1011807 [src:twitter-bootstrap4] twitter-bootstrap4: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 1011807 was not blocked by any bugs. 1011807 was not blocking any bugs. Added blocking bug(s) of 1011807: 1012324 -- 1011807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011807 1012324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009391: marked as done (pytango: FTBFS: TypeError: entry_points() got an unexpected keyword argument 'group')
Your message dated Sat, 04 Jun 2022 09:09:11 +0200
with message-id <363ebdfb34e00c9effad54c8c364a...@debian.org>
and subject line (pas d'objet)
has caused the Debian Bug report #1009391,
regarding pytango: FTBFS: TypeError: entry_points() got an unexpected keyword
argument 'group'
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.)
--
1009391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytango
Version: 9.3.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- -s custom --build-args="PYTHONPATH={build_dir} {interpreter}
> -m sphinx -N -bhtml doc build/html"
> I: pybuild base:239:
> PYTHONPATH=/<>/.pybuild/cpython3_3.9_tango/build python3.9 -m
> sphinx -N -bhtml doc build/html
> Running Sphinx v4.5.0
> Mocking tango._tango extension module
> Building documentation for PyTango 9.3.3
> Using PyTango from: /<>/tango
> making output directory... done
>
> Exception occurred:
> File "/usr/lib/python3/dist-packages/sphinx/theming.py", line 199, in
> load_external_theme
> theme_entry_points = entry_points(group='sphinx.html_themes')
> TypeError: entry_points() got an unexpected keyword argument 'group'
> The full traceback has been saved in /tmp/sphinx-err-frm2k8yi.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> . Thanks!
> E: pybuild pybuild:369: build: plugin custom failed with: exit code=2:
> PYTHONPATH=/<>/.pybuild/cpython3_3.9_tango/build python3.9 -m
> sphinx -N -bhtml doc build/html
> I: pybuild base:239:
> PYTHONPATH=/<>/.pybuild/cpython3_3.10_tango/build python3.10 -m
> sphinx -N -bhtml doc build/html
> Running Sphinx v4.5.0
> Mocking tango._tango extension module
> Building documentation for PyTango 9.3.3
> Using PyTango from: /<>/tango
> loading intersphinx inventory from http://docs.python.org/dev/objects.inv...
> loading intersphinx inventory from
> http://docs.scipy.org/doc/scipy/reference/objects.inv...
> loading intersphinx inventory from
> http://docs.scipy.org/doc/numpy/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.scipy.org/doc/scipy/reference/objects.inv'
> not fetchable due to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://docs.scipy.org/doc/scipy/reference/objects.inv (Caused by
> ProxyError('Cannot connect to proxy.',
> NewConnectionError(' 0x7f003ae71840>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> loading intersphinx inventory from
> http://ipython.org/ipython-doc/stable/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.scipy.org/doc/numpy/objects.inv' not
> fetchable due to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://docs.scipy.org/doc/numpy/objects.inv (Caused by ProxyError('Cannot
> connect to proxy.', NewConnectionError(' object at 0x7f003ae72860>: Failed to establish a new connection: [Errno 111]
> Connection refused')))
> loading intersphinx inventory from
> http://api.mongodb.org/python/current/objects.inv...
> loading intersphinx inventory from
> http://couchdb-python.readthedocs.io/en/latest/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.python.org/dev/objects.inv' not fetchable
> due to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://docs.python.org/dev/objects.inv (Caused by ProxyError('Cannot connect
> to proxy.', NewConnectionError(' 0x7f003ae71f60>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://ipython.org/ipython-doc/stable/objects.inv' not
> fetchable due to :
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
> http://ipython.org/ipython-doc/stable/objects.inv (Caused by
> ProxyError('Cannot connect to proxy.',
>
Bug#1010408: marked as done (ftbfs: Error: Failed to find "global.fs = fs;" in Go JS shim code)
Your message dated Sat, 04 Jun 2022 07:03:51 + with message-id and subject line Bug#1010408: fixed in golang-github-evanw-esbuild 0.14.36-1 has caused the Debian Bug report #1010408, regarding ftbfs: Error: Failed to find "global.fs = fs;" in Go JS shim code 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.) -- 1010408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-evanw-esbuild Version: 0.14.25-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, your package FTBFS, however a trivial upstream update fixes it (took me a minute to rebuild it). Jérémy. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: golang-github-evanw-esbuild Source-Version: 0.14.36-1 Done: Anthony Fok We believe that the bug you reported is fixed in the latest version of golang-github-evanw-esbuild, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok (supplier of updated golang-github-evanw-esbuild package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Jun 2022 00:32:24 -0600 Source: golang-github-evanw-esbuild Architecture: source Version: 0.14.36-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Anthony Fok Closes: 1010408 Changes: golang-github-evanw-esbuild (0.14.36-1) unstable; urgency=medium . * New upstream version 0.14.36 (Closes: #1010408) * Switch from Built-Using to Static-Built-Using in debian/control * Update esbuild(1) man page to 0.14.36 Checksums-Sha1: fb15ef22c0483a71cf1faf2e086eda7dd6bc519c 2510 golang-github-evanw-esbuild_0.14.36-1.dsc d923f762948e9f486ebc69e63a3401e149fd232a 1599445 golang-github-evanw-esbuild_0.14.36.orig.tar.gz a59bd02538f3c0d9a81e5ad30faf4dd506e2feb5 7888 golang-github-evanw-esbuild_0.14.36-1.debian.tar.xz 4a52d1e61b803d7a253be7d794d145ac4e0bcf69 11830 golang-github-evanw-esbuild_0.14.36-1_amd64.buildinfo Checksums-Sha256: 75806971abdd62aad7db58748dffa94f637dc15668e545fd1375308f911d0f95 2510 golang-github-evanw-esbuild_0.14.36-1.dsc 77391e246289755537ce4b5412bb4da80671c884d8cb52d2380a6d8b8f8117a5 1599445 golang-github-evanw-esbuild_0.14.36.orig.tar.gz 371d2ae3be8d1f6a3bc294b59d4f8df9e390946755d2163367b17c8f4c3a3a4d 7888 golang-github-evanw-esbuild_0.14.36-1.debian.tar.xz 1c6faec60a4ce646c9e41b044ddf73887f5e95bcf53cb8d21ee4cf0d29981d32 11830 golang-github-evanw-esbuild_0.14.36-1_amd64.buildinfo Files: d7e4a5544a78b1d29e7490b4deb6eeda 2510 golang optional golang-github-evanw-esbuild_0.14.36-1.dsc 5700b71490a821e29282c5ff4eb60904 1599445 golang optional golang-github-evanw-esbuild_0.14.36.orig.tar.gz 78cec595ce69568895b89dbbc4b65635 7888 golang optional golang-github-evanw-esbuild_0.14.36-1.debian.tar.xz ef5c767398c6a3935be436828c844f08 11830 golang optional golang-github-evanw-esbuild_0.14.36-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmKa/ZgQHGZva2FAZGVi aWFuLm9yZwAKCRDqJQC0EsWaz2JTD/4z7uPsUZfP3A7dSrRVyvsgQYH8jUcn2Exq GVGl3RIH+CmIFSyLEVwlDWj+b/iyQWwGEepLMwrHii5FIoczS+EXbePgXS06ya1v 6D2PDSnnbqZs7WZIA/sttkysBANeoZw9tR7d5Wt9PWfCHp8OpXeqErt+nlJ+ekt3 7uljoz2nfuS5KEuVkPSR7kx5Cv2h52vB/bYnr3NdoqmNyawvKakMLajx3kel4Nu+ o3eCj9PkRXSwgZmpmiUWLTbQGd1GlhoLpqE5X1r1wtTmcuFiQevKAPx9YTwLwfjo jqzc580Y0qaVoO3iL6wlVjfkDZBR/bvDVN7hVk3vvqbma9ubyS4UgrhNHMsYUjaF 2cPFzmSq7EsNVsxZqtkOwARgyjzbtnfWwWLakjC12rpC4a+nQeKiuvXGi33IqEo1 L57EQEK3gGQFCKoqn/0uBw+FkXbYFOUZU9Gff6ecBPoQKFE0iqoSQ0l/Ts8K5/Rn
Bug#1011795: marked as done (node-fastcgi: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 2)
Your message dated Sat, 04 Jun 2022 07:03:56 +
with message-id
and subject line Bug#1011795: fixed in node-fastcgi 1.3.3-7
has caused the Debian Bug report #1011795,
regarding node-fastcgi: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 2
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.)
--
1011795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-fastcgi
Version: 1.3.3-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../debian/tests/test_modules/cgi-env node_modules/cgi-env
> ln -s ../debian/tests/test_modules/fastcgi-parser
> node_modules/fastcgi-parser
> ln -s ../debian/tests/test_modules/fcgi-handler
> node_modules/fcgi-handler
> ln -s ../debian/tests/test_modules/fcgi-stream node_modules/fcgi-stream
> ln -s ../debian/tests/test_modules/request node_modules/request
> ln -s ../. node_modules/node-fastcgi
> /bin/sh -ex debian/tests/pkg-js/test
> + mocha --exit ./test/mocha/integration
>
>
> echo Server
> cgi app listen on socket:/<>/test/mocha/integration/Sock11306
> (node:912080) [DEP0005] DeprecationWarning: Buffer() is deprecated due to
> security and usability issues. Please use the Buffer.alloc(),
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> undefined should answer with the request (50ms)
> undefined should answer with the request data
> undefined should answer with the request querystring
> 1) should answer with the request auth
> 2) should answer with correct request header names
>
> multiwrite Server
> cgi app listen on socket:/<>/test/mocha/integration/Sock21203
> undefined should answer with the expected response
>
> multiwrite Server (no content-length)
> cgi app listen on socket:/<>/test/mocha/integration/Sock31885
> undefined should answer with the expected response
>
>
> 5 passing (107ms)
> 2 failing
>
> 1) echo Server
>should answer with the request auth:
> Uncaught AssertionError: expected { _eventsCount: 3, …(15) } to have
> nested property 'headers.authorization'
> at Request._callback (test/mocha/integration/echo.js:189:41)
> at Request.self.callback
> (debian/tests/test_modules/request/request.js:185:22)
> at Request.emit (node:events:526:28)
> at Request.
> (debian/tests/test_modules/request/request.js:1161:10)
> at Request.emit (node:events:526:28)
> at IncomingMessage.
> (debian/tests/test_modules/request/request.js:1083:12)
> at Object.onceWrapper (node:events:645:28)
> at IncomingMessage.emit (node:events:538:35)
> at endReadableNT (node:internal/streams/readable:1345:12)
> at processTicksAndRejections (node:internal/process/task_queues:83:21)
>
> 2) echo Server
>should answer with correct request header names:
> Uncaught AssertionError: expected { _eventsCount: 3, …(15) } to have
> nested property 'headers.x-testhdr'
> at Request._callback (test/mocha/integration/echo.js:215:41)
> at Request.self.callback
> (debian/tests/test_modules/request/request.js:185:22)
> at Request.emit (node:events:526:28)
> at Request.
> (debian/tests/test_modules/request/request.js:1161:10)
> at Request.emit (node:events:526:28)
> at IncomingMessage.
> (debian/tests/test_modules/request/request.js:1083:12)
> at Object.onceWrapper (node:events:645:28)
> at IncomingMessage.emit (node:events:538:35)
> at endReadableNT (node:internal/streams/readable:1345:12)
> at processTicksAndRejections (node:internal/process/task_queues:83:21)
>
>
>
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 2
The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-fastcgi_1.3.3-6_unstable.log
All bugs filed during this archive rebuild are listed at:
Bug#1010408: ftbfs: Error: Failed to find "global.fs = fs;" in Go JS shim code
Hi Jérémy,
Thank you for your report!
On Sat, Apr 30, 2022 at 2:39 PM Jérémy Lal wrote:
> Source: golang-github-evanw-esbuild
> Version: 0.14.25-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the
past)
>
> your package FTBFS, however a trivial upstream update fixes it (took me a
minute to rebuild it).
I'd like to provide a bit more context:
esbuild v0.14.25 started FTBFS when golang-1.18 became the default in
Debian on about 2022-03-22.
The actual FTBFS error looks something like this:
=
debian/rules execute_after_dh_auto_build-arch
make[1]: Entering directory '/<>'
ln -s _build/bin/esbuild .
# Generate npm/esbuild/*
node scripts/esbuild.js ./esbuild --neutral
# Generate npm/esbuild-wasm/*
GOPATH=/<>/_build GOCACHE=/<>/_build/go-build \
node scripts/esbuild.js ./esbuild --wasm
/<>/scripts/esbuild.js:110
if (wasm_exec_js.indexOf(toReplace) === -1) throw new Error(`Failed to
find ${JSON.stringify(toReplace)} in Go JS shim code`);
^
Error: Failed to find "global.fs = fs;" in Go JS shim code
at replace (/<>/scripts/esbuild.js:110:55)
at Object.exports.buildWasmLib
(/<>/scripts/esbuild.js:113:3)
at Object. (/<>/scripts/esbuild.js:366:52)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js
(node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain]
(node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47
make[1]: *** [debian/rules:25: execute_after_dh_auto_build-arch] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:17: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
=
This was apparently fixed in the upstream commit
-
https://github.com/evanw/esbuild/commit/517f77fa11da2287b4f63680cee9544be1f88c76
which was released upstream as v0.14.28 on 2022-03-25.
