Processed: Re: crashes immediately at start
Processing control commands: > severity -1 grave Bug #1010269 [wine-development] crashes immediately at start Severity set to 'grave' from 'normal' > affects -1 src:dxvk Bug #1010269 [wine-development] crashes immediately at start Added indication that 1010269 affects src:dxvk -- 1010269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010429: marked as done (gddrescue: autopkgtest regression)
Your message dated Mon, 02 May 2022 06:03:49 + with message-id and subject line Bug#1010429: fixed in gddrescue 1.26-2 has caused the Debian Bug report #1010429, regarding gddrescue: autopkgtest regression 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.) -- 1010429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gddrescue Version: 1.26-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of gddrescue the autopkgtest of gddrescue fails in testing when that autopkgtest is run with the binary packages of gddrescue from unstable. It passes when run with only packages from testing. In tabular form: passfail gddrescue from testing1.26-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from gddrescue/1.26-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=gddrescue https://ci.debian.net/data/autopkgtest/testing/amd64/g/gddrescue/21266348/log.gz 1+0 records in 1+0 records out 10485760 bytes (10 MB, 10 MiB) copied, 0.0754896 s, 139 MB/s GNU ddrescue 1.26 Press Ctrl-C to interrupt [A[A[A[A[A[A ipos:0 B, non-trimmed:0 B, current rate: 0 B/s opos:0 B, non-scraped:0 B, average rate: 0 B/s non-tried: 10485 kB, bad-sector:0 B,error rate: 0 B/s rescued:0 B, bad areas:0,run time: 0s pct rescued:0.00%, read errors:0, remaining time: n/a time since last successful read: n/a Copying non-tried blocks... Pass 1 (forwards) [A[A[A[A[A[A ipos: 10420 kB, non-trimmed:0 B, current rate: 0 B/s opos: 10420 kB, non-scraped:0 B, average rate: 0 B/s non-tried:0 B, bad-sector:0 B,error rate: 0 B/s rescued: 10485 kB, bad areas:0,run time: 0s pct rescued: 100.00%, read errors:0, remaining time: n/a time since last successful read: n/a Copying non-tried blocks... Pass 1 (forwards) [A[A[A[A[A[A ipos: 10420 kB, non-trimmed:0 B, current rate: 10485 kB/s opos: 10420 kB, non-scraped:0 B, average rate: 10485 kB/s non-tried:0 B, bad-sector:0 B,error rate: 0 B/s rescued: 10485 kB, bad areas:0,run time: 0s pct rescued: 100.00%, read errors:0, remaining time: n/a time since last successful read: n/a Finishedautopkgtest [22:12:17]: test clone-file OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gddrescue Source-Version: 1.26-2 Done: Michael Prokop We believe that the bug you reported is fixed in the latest version of gddrescue, 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. Michael Prokop (supplier of updated gddrescue 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: Mon, 02 May 2022 07:40:13 +0200 Source: gddrescue Architecture: source Version: 1.26-2 Distribution: unstable Urgency: medium Maintainer: Michael Prokop Changed-By: Michael Prokop Closes: 10
Bug#1010429: gddrescue: autopkgtest regression
* Paul Gevers [Sun May 01, 2022 at 02:39:15PM +0200]: > With a recent upload of gddrescue the autopkgtest of gddrescue fails in > testing when that autopkgtest is run with the binary packages of gddrescue > from unstable. It passes when run with only packages from testing. In > tabular form: [...] > Currently this regression is blocking the migration to testing [1]. Can you > please investigate the situation and fix it? [...] Indeed, I could reproduce the issue and just uploaded a new version, which is supposed to fix the issue. Thanks for reporting it, Paul, appreciated! regards -mika- signature.asc Description: PGP signature
Bug#1004511: luajit SEGFAULTS on ppc64el
Hi, On 24-04-2022 12:00, Paul Gevers wrote: On Sat, 29 Jan 2022 19:32:53 +0100 Paul Gevers wrote: With a recent upload of luajit the autopkgtest of knot-resolver fails in testing when that autopkgtest is run with the binary packages of luajit from unstable. It passes when run with only packages from testing. In tabular form: knot-resolver has been removed from testing due to this bug report, but can't migrate back because a newer version fails to build on ppc64el. Also other reverse dependencies of luajit show SEGFAULT in their autopkgtest on ppc64el, so this seems a problem in luajit. Unfortunately (Release Team member opinion) luajit is a key package so can't be trivially removed. Can you (maintainer and ppc64el porters) please have a look? If this issue is difficult to fix, how about removing luajit from ppc64el? I noticed that the only reverse (build) dependent key package of luajit (src:efl) already switched to plain lua on ppc64el (probably because of this issue). Paul OpenPGP_signature Description: OpenPGP digital signature
Processed (with 2 errors): Re: mdtraj: autopkgtest timeout on arm64 (downloading pdb file?)
Processing control commands: > severity -1 serious Bug #1009079 [src:mdtraj] mdtraj: autopkgtest timeout on arm64 (downloading pdb file?) Severity set to 'serious' from 'important' > user debian...@lists.debian.org Unknown command or malformed arguments to command. > usertag -1 flaky needs-internet Unknown command or malformed arguments to command. -- 1009079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997742: marked as done (pyrlp: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(sys.path)? (conf.py, line 22))
Your message dated Mon, 02 May 2022 05:04:39 + with message-id and subject line Bug#997742: fixed in pyrlp 0.5.1-3 has caused the Debian Bug report #997742, regarding pyrlp: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(sys.path)? (conf.py, line 22) 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.) -- 997742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyrlp Version: 0.5.1-1.2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/__init__.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/utils_py2.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/lazy.py -> /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/codec.py -> /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/exceptions.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/utils.py -> /<>/.pybuild/cpython3_3.9_rlp/build/rlp > copying rlp/utils_py3.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp > creating /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/__init__.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/raw.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/lists.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/binary.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > copying rlp/sedes/big_endian_int.py -> > /<>/.pybuild/cpython3_3.9_rlp/build/rlp/sedes > running egg_info > creating rlp.egg-info > writing rlp.egg-info/PKG-INFO > writing dependency_links to rlp.egg-info/dependency_links.txt > writing top-level names to rlp.egg-info/top_level.txt > writing manifest file 'rlp.egg-info/SOURCES.txt' > reading manifest file 'rlp.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > adding license file 'LICENSE' > writing manifest file 'rlp.egg-info/SOURCES.txt' > sphinx-build -N -bhtml docs/ \ > docs/_build/html/ > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: Missing parentheses in > call to 'print'. Did you mean print(sys.path)? (conf.py, line 22) > > make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pyrlp_0.5.1-1.2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: pyrlp Source-Version: 0.5.1-3 Done: Ben Finney We believe that the bug you reported is fixed in the latest version of pyrlp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Finney (supplier of updated pyrlp 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: Mon, 02 May 2022 14:42:24 +1000 Source: pyrlp Architecture: source Version: 0.5.1-3 Distribution: unstable Urgency: medium Maintainer: Ben Finney Changed-By: Ben Finney Closes: 997742 Changes: pyrlp (0.5.1-3) unstable; urgency=medium . * Update UScan configuration for changes in upstream
Bug#1010453: closed by Debian FTP Masters (reply to Doug Torrance ) (Bug#1010453: fixed in macaulay2 1.19.1+ds-9)
Hi, On 02-05-2022 02:39, Debian Bug Tracking System wrote: macaulay2 (1.19.1+ds-9) unstable; urgency=medium . * debian/tests/control - Mark package-tests as flaky since it regularly times out on armhf (Closes: #1010453). Hmmm. May I recommend something else? Marking autopkgtests that regularly time out is a solution that has a relative high price on the infrastructure. These tests are still run (until they time out), while they don't influencing migration of any package if the package contain more than one autopkgtest. Marking tests flaky is nearly only useful if a human is regularly going to look at the results and does something with it. To be honest, I'm not expecting that here (but let me know if I'm making a wrong assumption here). Instead, I recommend to not run the test at all on armhf if we're going to ignore the result there (successful runs also take long), but use it normally on all other architectures. There's the "Architecture" field available in debian/tests/control that can be used to achieve that in a correct way. It understands the regular syntax so "!armhf" should suffice. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1010453: marked as done (macaulay2: autopkgtest regularly times out on armhf)
Your message dated Mon, 02 May 2022 00:34:22 + with message-id and subject line Bug#1010453: fixed in macaulay2 1.19.1+ds-9 has caused the Debian Bug report #1010453, regarding macaulay2: autopkgtest regularly times out on armhf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1010453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: macaulay2 Version: 1.19.1+ds-4 Severity: serious User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), I looked at the results of the autopkgtest of you package because it was showing up as a regression for the upload of gcc-12. I noticed that the test regularly fails on armhf due to a timeout (single tests time out after 2:47h). Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/m/macaulay2/testing/armhf/ https://ci.debian.net/data/autopkgtest/testing/armhf/m/macaulay2/21279489/log.gz Resultants ** -- capturing check(0, "Resultants") -- 3.22647 seconds elapsed -- capturing check(1, "Resultants") -- 0.404634 seconds elapsed -- capturing check(2, "Resultants") -- 0.45 seconds elapsed -- capturing check(3, "Resultants") -- 0.250109 seconds elapsed -- capturing check(4, "Resultants") -- 1.8931 seconds elapsed -- capturing check(5, "Resultants") -- 5.54243 seconds elapsed -- capturing check(6, "Resultants") -- 1.13514 seconds elapsed -- capturing check(7, "Resultants") -- 0.194144 seconds elapsed -- capturing check(8, "Resultants") -- 1782.82 seconds elapsed -- capturing check(9, "Resultants") -- 0.0857801 seconds elapsed -- capturing check(10, "Resultants") autopkgtest [15:02:55]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.lbtzbotc/downtmp/build.htM/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.lbtzbotc/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.lbtzbotc/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=160; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; touch /tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-stdout /tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-stderr; bash -ec 'M2 --check 3' 2> >(tee -a /tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-stdout);" (kind: test) autopkgtest [15:02:55]: test package-tests: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: macaulay2 Source-Version: 1.19.1+ds-9 Done: Doug Torrance We believe that the bug you reported is fixed in the latest version of macaulay2, 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. Doug Torrance (supplier of updated macaulay2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 May 2022 20:14:15 -0400 Source: macaulay2
Bug#984083: marked as done (lasi: ftbfs with GCC-11)
Your message dated Sun, 01 May 2022 23:06:01 + with message-id and subject line Bug#984083: fixed in lasi 1.1.0-3 has caused the Debian Bug report #984083, regarding lasi: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lasi Version: 1.1.0-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/lasi_1.1.0-2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] cmake_policy(SET CMP0003 NEW) endif(COMMAND cmake_policy) as early as possible but after the most recent call to cmake_minimum_required or cmake_policy(VERSION). This warning appears because target "example2" links to some libraries for which the linker must search: pango-1.0, gobject-2.0, glib-2.0, harfbuzz, pangoft2-1.0, pango-1.0 gobject-2.0, glib-2.0, harfbuzz, fontconfig, freetype, freetype, pango-1.0 gobject-2.0, glib-2.0, harfbuzz, pangoft2-1.0, pango-1.0, gobject-2.0 glib-2.0, harfbuzz, pangoft2-1.0, fontconfig, freetype, m and other libraries with known full path: /<>/obj-x86_64-linux-gnu/src/libLASi.so.0.0.1 CMake is adding directories in the second list to the linker search path in case they are needed to find libraries from the first list (for backwards compatibility with CMake 2.4). Set policy CMP0003 to OLD or NEW to enable or disable this behavior explicitly. Run "cmake --help-policy CMP0003" for more information. This warning is for project developers. Use -Wno-dev to suppress it. -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_C_COMPILER CMAKE_C_FLAGS -- Build files have been written to: /<>/obj-x86_64-linux-gnu /usr/bin/make -C obj-x86_64-linux-gnu make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks /usr/bin/make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/make -f CMakeFiles/documentation.dir/build.make CMakeFiles/documentation.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/documentation.dir/DependInfo.cmake --color= Scanning dependencies of target documentation make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' /usr/bin/make -f CMakeFiles/documentation.dir/build.make CMakeFiles/documentation.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make[3]: Nothing to be done for 'CMakeFiles/documentation.dir/build'. make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 15%] Built target documentation /usr/bin/make -f src/CMakeFiles/LASi.dir/build.make src/CMakeFiles/LASi.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /
Bug#1000271: marked as done (jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937'])
Your message dated Sun, 01 May 2022 21:33:23 +
with message-id
and subject line Bug#1000271: fixed in jupyter-client 7.3.0-1
has caused the Debian Bug report #1000271,
regarding jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers
don't have promised key: ['tcp://127.0.0.1:33937']
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.)
--
1000271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-client, dask.distributed
Control: found -1 jupyter-client/7.0.6-2
Control: found -1 dask.distributed/2021.09.1+ds.1-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of jupyter-client the autopkgtest of
dask.distributed fails in testing when that autopkgtest is run with the
binary packages of jupyter-client from unstable. It passes on arm64 and
ppc64el when run with only packages from testing. In tabular form:
passfail
jupyter-client from testing7.0.6-2
dask.distributed from testing2021.09.1+ds.1-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of jupyter-client to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=jupyter-client
https://ci.debian.net/data/autopkgtest/testing/arm64/d/dask.distributed/16840880/log.gz
=== FAILURES
===
[31m[1m test_gather_failing_cnn_error
_[0m
outer_args = (), kwargs = {}, result = None
coro = ._..test_func..coro
at 0x0c67d550>
[37m@functools[39;49;00m.wraps(func)
[94mdef[39;49;00m [92mtest_func[39;49;00m(*outer_args, **kwargs):
result = [94mNone[39;49;00m
workers = []
[94mwith[39;49;00m clean(timeout=active_rpc_timeout,
**clean_kwargs) [94mas[39;49;00m loop:
[94masync[39;49;00m [94mdef[39;49;00m
[92mcoro[39;49;00m():
[94mwith[39;49;00m dask.config.set(config):
s = [94mFalse[39;49;00m
[94mfor[39;49;00m _ [95min[39;49;00m
[96mrange[39;49;00m([94m60[39;49;00m):
[94mtry[39;49;00m:
s, ws = [94mawait[39;49;00m start_cluster(
nthreads,
scheduler,
loop,
security=security,
Worker=Worker,
scheduler_kwargs=scheduler_kwargs,
worker_kwargs=worker_kwargs,
)
[94mexcept[39;49;00m
[96mException[39;49;00m [94mas[39;49;00m e:
logger.error(
[33m"[39;49;00m[33mFailed to start
gen_cluster: [39;49;00m[33m"[39;49;00m
[33mf[39;49;00m[33m"[39;49;00m[33m{[39;49;00me.[91m__class__[39;49;00m.[91m__name__[39;49;00m[33m}[39;49;00m[33m:
[39;49;00m[33m{[39;49;00me[33m}[39;49;00m[33m;
retrying[39;49;00m[33m"[39;49;00m,
exc_info=[94mTrue[39;49;00m,
)
[94mawait[39;49;00m
asyncio.sleep([94m1[39;49;00m)
[94melse[39;49;00m:
workers[:] = ws
args = [s] + workers
[94mbreak[39;49;00m
[94mif[39;49;00m s [95mis[39;49;00m
[94mFalse[39;49;00m:
[94mraise[39;49;00m
[96mException[39;49;00m([33m"[39;49;00m[33mCould not start
cluster[39;49;00m[33m"[39;49;00m)
[94mif[39;49;00m client:
c = [94mawait[39;49;00m Client(
s.address,
loop=loop,
security=security,
asynchronous=[94mTrue[39;4
Processed: affects 984865
Processing commands for cont...@bugs.debian.org: > affects 984865 src:rust-kmon Bug #984865 [src:rust-tui] rust-tui: depends on multiple unavailable packages Ignoring request to set affects of bug 984865 to the same value previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 984865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 984865
Processing commands for cont...@bugs.debian.org: > tags 984865 + ftbfs Bug #984865 [src:rust-tui] rust-tui: depends on multiple unavailable packages Ignoring request to alter tags of bug #984865 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 984865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 984865
Processing commands for cont...@bugs.debian.org: > affects 984865 src:rust-kmon Bug #984865 [src:rust-tui] rust-tui: depends on multiple unavailable packages Added indication that 984865 affects src:rust-kmon > thanks Stopping processing here. Please contact me if you need assistance. -- 984865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 984865
Processing commands for cont...@bugs.debian.org: > tags 984865 + ftbfs Bug #984865 [src:rust-tui] rust-tui: depends on multiple unavailable packages Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 984865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1000271 marked as pending in jupyter-client
Processing control commands: > tag -1 pending Bug #1000271 [src:jupyter-client, src:dask.distributed] jupyter-client breaks dask.distributed autopkgtest: ERROR - Workers don't have promised key: ['tcp://127.0.0.1:33937'] Added tag(s) pending. -- 1000271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000271: marked as pending in jupyter-client
Control: tag -1 pending Hello, Bug #1000271 in jupyter-client 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/jupyter-client/-/commit/9b99a7b77dc73f3cd288dcc191b75a400b031079 Checked dask.distributed builds with this (Closes: #1000271) (this message was generated automatically) -- Greetings https://bugs.debian.org/1000271
Bug#1010454: docker.io: FTBFS on s390x: === FAIL: daemon/logger TestCopierWithSized (0.00s)
Source: docker.io Version: 20.10.14+dfsg1-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=docker.io&arch=s390x&ver=20.10.14%2Bdfsg1-1%2Bb1&stamp=1651435487&raw=0 === SKIP: volume/local TestCreateWithOpts (0.00s) local_test.go:182: os.Getuid() != 0: requires mounts === Failed === FAIL: daemon/logger TestCopierWithSized/With_RingLogger (0.00s) copier_test.go:265: invalid character 'L' after object key:value pair --- FAIL: TestCopierWithSized/With_RingLogger (0.00s) === FAIL: daemon/logger TestCopierWithSized (0.00s) DONE 2203 tests, 120 skipped, 2 failures in 158.855s make[1]: *** [debian/rules:128: override_dh_auto_test] Error 1 Cheers -- Sebastian Ramacher
Bug#1010453: macaulay2: autopkgtest regularly times out on armhf
Source: macaulay2 Version: 1.19.1+ds-4 Severity: serious User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), I looked at the results of the autopkgtest of you package because it was showing up as a regression for the upload of gcc-12. I noticed that the test regularly fails on armhf due to a timeout (single tests time out after 2:47h). Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/m/macaulay2/testing/armhf/ https://ci.debian.net/data/autopkgtest/testing/armhf/m/macaulay2/21279489/log.gz Resultants ** -- capturing check(0, "Resultants") -- 3.22647 seconds elapsed -- capturing check(1, "Resultants") -- 0.404634 seconds elapsed -- capturing check(2, "Resultants") -- 0.45 seconds elapsed -- capturing check(3, "Resultants") -- 0.250109 seconds elapsed -- capturing check(4, "Resultants") -- 1.8931 seconds elapsed -- capturing check(5, "Resultants") -- 5.54243 seconds elapsed -- capturing check(6, "Resultants") -- 1.13514 seconds elapsed -- capturing check(7, "Resultants") -- 0.194144 seconds elapsed -- capturing check(8, "Resultants") -- 1782.82 seconds elapsed -- capturing check(9, "Resultants") -- 0.0857801 seconds elapsed -- capturing check(10, "Resultants") autopkgtest [15:02:55]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.lbtzbotc/downtmp/build.htM/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.lbtzbotc/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.lbtzbotc/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=160; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; touch /tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-stdout /tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-stderr; bash -ec 'M2 --check 3' 2> >(tee -a /tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.lbtzbotc/downtmp/package-tests-stdout);" (kind: test) autopkgtest [15:02:55]: test package-tests: ---] OpenPGP_signature Description: OpenPGP digital signature
Processed: severity of 1005382 is serious
Processing commands for cont...@bugs.debian.org: > severity 1005382 serious Bug #1005382 [gitlab-ci-multi-runner] "couldn't load configuration template file: Near line 1 (last key parsed '-'): expected key separator '=', but got ',' instead" Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1005382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1005382
Processing commands for cont...@bugs.debian.org: > tags 1005382 + ftbfs Bug #1005382 [gitlab-ci-multi-runner] "couldn't load configuration template file: Near line 1 (last key parsed '-'): expected key separator '=', but got ',' instead" Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010452: gitlab-ci-multi-runner: FTBFS: test failure
Source: gitlab-ci-multi-runner Version: 13.3.1+dfsg-4 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org gitlab-ci-multi-runner FTBFS: === RUN TestRmFile/pwsh integration_tests.go:15: pwsh failed exec: "pwsh": executable file not found in $PATH --- PASS: TestRmFile (0.01s) --- PASS: TestRmFile/bash (0.01s) --- SKIP: TestRmFile/cmd (0.00s) --- SKIP: TestRmFile/powershell (0.00s) --- SKIP: TestRmFile/pwsh (0.00s) PASS ok gitlab.com/gitlab-org/gitlab-runner/shells 0.074s ? gitlab.com/gitlab-org/gitlab-runner/shells/shellstest [no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 4 -ldflags "-X gitlab.com/gitlab-org/gitlab-runner/common.VERSION=13.3.1 -X gitlab.com/gitlab-org/gitlab-runner/common.REVISION=13.3.1" gitlab.com/gitlab-org/gitlab-runner gitlab.com/gitlab-org/gitlab-runner/apps/gitlab-runner-helper gitlab.com/gitlab-org/gitlab-runner/cache gitlab.com/gitlab-org/gitlab-runner/cache/gcs gitlab.com/gitlab-org/gitlab-runner/cache/s3 gitlab.com/gitlab-org/gitlab-runner/commands gitlab.com/gitlab-org/gitlab-runner/commands/helpers gitlab.com/gitlab-org/gitlab-runner/common gitlab.com/gitlab-org/gitlab-runner/common/buildtest gitlab.com/gitlab-org/gitlab-runner/executors gitlab.com/gitlab-org/gitlab-runner/executors/custom gitlab.com/gitlab-org/gitlab-runner/executors/custom/api gitlab.com/gitlab-org/gitlab-runner/executors/custom/command gitlab.com/gitlab-org/gitlab-runner/executors/docker gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/labels gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/networks gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/volumes gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/volumes/parser gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/volumes/permission gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/wait gitlab.com/gitlab-org/gitlab-runner/executors/docker/machine gitlab.com/gitlab-org/gitlab-runner/executors/parallels gitlab.com/gitlab-org/gitlab-runner/executors/shell gitlab.com/gitlab-org/gitlab-runner/executors/ssh gitlab.com/gitlab-org/gitlab-runner/executors/virtualbox gitlab.com/gitlab-org/gitlab-runner/helpers gitlab.com/gitlab-org/gitlab-runner/helpers/archives gitlab.com/gitlab-org/gitlab-runner/helpers/certificate gitlab.com/gitlab-org/gitlab-runner/helpers/cli gitlab.com/gitlab-org/gitlab-runner/helpers/container/helperimage gitlab.com/gitlab-org/gitlab-runner/helpers/container/services gitlab.com/gitlab-org/gitlab-runner/helpers/container/services/test gitlab.com/gitlab-org/gitlab-runner/helpers/container/windows gitlab.com/gitlab-org/gitlab-runner/helpers/dns gitlab.com/gitlab-org/gitlab-runner/helpers/dns/test gitlab.com/gitlab-org/gitlab-runner/helpers/docker gitlab.com/gitlab-org/gitlab-runner/helpers/docker/auth gitlab.com/gitlab-org/gitlab-runner/helpers/docker/errors gitlab.com/gitlab-org/gitlab-runner/helpers/docker/test gitlab.com/gitlab-org/gitlab-runner/helpers/featureflags gitlab.com/gitlab-org/gitlab-runner/helpers/gitlab_ci_yaml_parser gitlab.com/gitlab-org/gitlab-runner/helpers/parallels gitlab.com/gitlab-org/gitlab-runner/helpers/path gitlab.com/gitlab-org/gitlab-runner/helpers/process gitlab.com/gitlab-org/gitlab-runner/helpers/prometheus gitlab.com/gitlab-org/gitlab-runner/helpers/retry gitlab.com/gitlab-org/gitlab-runner/helpers/sentry gitlab.com/gitlab-org/gitlab-runner/helpers/service gitlab.com/gitlab-org/gitlab-runner/helpers/service/mocks gitlab.com/gitlab-org/gitlab-runner/helpers/ssh gitlab.com/gitlab-org/gitlab-runner/helpers/test gitlab.com/gitlab-org/gitlab-runner/helpers/timeperiod gitlab.com/gitlab-org/gitlab-runner/helpers/tls gitlab.com/gitlab-org/gitlab-runner/helpers/tls/ca_chain gitlab.com/gitlab-org/gitlab-runner/helpers/trace gitlab.com/gitlab-org/gitlab-runner/helpers/url gitlab.com/gitlab-org/gitlab-runner/helpers/virtualbox gitlab.com/gitlab-org/gitlab-runner/log gitlab.com/gitlab-org/gitlab-runner/log/test gitlab.com/gitlab-org/gitlab-runner/network gitlab.com/gitlab-org/gitlab-runner/referees gitlab.com/gitlab-org/gitlab-runner/session gitlab.com/gitlab-org/gitlab-runner/session/proxy gitlab.com/gitlab-org/gitlab-runner/session/terminal gitlab.com/gitlab-org/gitlab-runner/shells gitlab.com/gitlab-org/gitlab-runner/shells/shellstest returned exit code 1 make[1]: *** [debian/rules:54: override_dh_auto_test] Error 25 See https://buildd.debian.org/status/fetch.php?pkg=gitlab-ci-multi-runner&arch=amd64&ver=13.3.1%2Bdfsg-4%2Bb7&stamp=1651436612&raw=0 Cheers -- Sebastian Ramacher
Bug#1010451: gdb-avr: Missing build dependency on libgmp-dev
Source: gdb-avr Version: 7.7-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gdb-avr&ver=7.7-5%2Bb1 ... checking for libgmp... no configure: error: GMP is missing or unusable make[1]: *** [Makefile:9783: configure-gdb] Error 1 make[1]: Leaving directory '/<>/build' make: *** [debian/rules:46: configure-stamp] Error 2
Bug#1004847: marked as done (nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814)
Your message dated Sun, 01 May 2022 19:57:33 + with message-id and subject line Bug#1004847: fixed in nvidia-graphics-drivers 470.103.01-3~deb11u1 has caused the Debian Bug report #1004847, regarding nvidia-graphics-drivers: CVE-2022-21813, CVE-2022-21814 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.) -- 1004847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-21813, CVE-2022-21814 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-21813, CVE-2022-21814 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-21813, CVE-2022-21814 Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-21813, CVE-2022-21814 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-21813, CVE-2022-21814 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-21813, CVE-2022-21814 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 450.51-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5312 CVE‑2022‑21813 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel driver, where improper handling of insufficient permissions or privileges may allow an unprivileged local user limited write access to protected memory, which can lead to denial of service. CVE‑2022‑21814 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel driver package, where improper handling of insufficient permissions or privileges may allow an unprivileged local user limited write access to protected memory, which can lead to denial of service. Driver Branch CVE IDs Addressed R510, R470 CVE-2022-21813, CVE-2022-21814 Andreas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers Source-Version: 470.103.01-3~deb11u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers 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: Sun, 20 Mar 2022 21:38:19 +0100 Source: nvidia-graphics-drivers Architecture: source Version: 470.103.01-3~deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 987216 989069 989885 991351 992057 994633 994860 994942 994971 995271 996031 996164 996468 996595 996763 999670 1004847 1005311 Changes: nvidia-graphics-drivers (470.103.01-3~deb11u1) bullseye; urgency=medium . * Rebuild for bullseye. * Temporarily disable building libnvidia-nvvm4 to avoid NEW. . nvidia-graphics-drivers (470.103.01-3) unstable; urgency=medium . * dkms.conf: Use a BUILD_EXCLUSIVE equivalent hack to skip building for -rt kernels, not supported upstream (510.54-1). * Declare Testsuite: autopkgtest-pkg-dkms (510.54-1). * nvidia-detect: Drop support for Tesla 460 drivers (EoL). . nvidia-graphics-drivers (470.103.01-2) unstable; urgency=medium . * Add xorg-video-abi-25 (Xorg Xserver 21) as alternative dependency. (Closes: #1005311) * nvidia-detect: Add support for (Tesla) 470 drivers in bullseye. . nvidia-graphics-drivers (470.103.01-1) unstable; ur
Bug#1010276: parasail: compiles something extra (or less) depending on the CPU features available
Am Sun, May 01, 2022 at 01:27:39PM +0200 schrieb Étienne Mollier: > Thank you for the clarification. In any case, I believe the mv > makes a random static library disappear, so I'll replace by cp. > This is looking like a safe maneuver. Uh, that's actually true and should for sure have been a cp. :-( > I'm sorting all three issues then. As always, thanks a lot Andreas. -- http://fam-tille.de
Bug#1008375: marked as done (apertium-crh-tur: FTBFS: configure: error: You don't have lrx-comp installed)
Your message dated Sun, 1 May 2022 21:40:57 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008375, regarding apertium-crh-tur: FTBFS: configure: error: You don't have lrx-comp installed 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.) -- 1008375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-crh-tur Version: 0.3.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for hfst-lexc... /usr/bin/hfst-lexc > checking for hfst-twolc... /usr/bin/hfst-twolc > checking for cg-comp... /usr/bin/cg-comp > checking for cg-proc... /usr/bin/cg-proc > checking for lrx-comp... false > configure: error: You don't have lrx-comp installed > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-crh-tur_0.3.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008364: marked as done (apertium-urd-hin: FTBFS: configure: error: You don't have lrx-comp installed.)
Your message dated Sun, 1 May 2022 21:40:57 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008364, regarding apertium-urd-hin: FTBFS: configure: error: You don't have lrx-comp installed. 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.) -- 1008364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-urd-hin Version: 0.1.0~r64379-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.3.0... yes > checking for cg-comp... /usr/bin/cg-comp > checking for lrx-comp... no > configure: error: You don't have lrx-comp installed. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-urd-hin_0.1.0~r64379-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008330: marked as done (apertium-spa: FTBFS: configure: error: You don't have lrx-comp installed)
Your message dated Sun, 1 May 2022 21:40:57 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008330, regarding apertium-spa: FTBFS: configure: error: You don't have lrx-comp installed 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.) -- 1008330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-spa Version: 1.1.0~r79716-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for lttoolbox >= 3.3.2... yes > checking for lt-print... /usr/bin/lt-print > checking for cg-comp... /usr/bin/cg-comp > checking for cg-proc... /usr/bin/cg-proc > checking for lrx-comp... false > configure: error: You don't have lrx-comp installed > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-spa_1.1.0~r79716-2.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1010164: marked as done (fails autopkgtest against Octave 7)
Your message dated Sun, 01 May 2022 19:34:03 + with message-id and subject line Bug#1010164: fixed in bart 0.7.00-3 has caused the Debian Bug report #1010164, regarding fails autopkgtest against Octave 7 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.) -- 1010164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: octave-bart Version: 0.7.00-2 Severity: serious Tags: patch Control: block 1009865 by -1 Dear Maintainer, The autopkgtest for octave-bart fails against octave 7.1.0-2 recently uploaded to unstable. See: https://ci.debian.net/data/autopkgtest/testing/amd64/b/bart/21135046/log.gz The problem comes from a message that is printed to stderr: error: ignoring const execution_exception& while preparing to exit This message only appears when running the autopkgtest in a dedicated chroot as done on the DebCI infrastructure. I wasn’t able to reproduce it in other contexts, and I could not figure out what causes it. Since this message is essentially harmless, and given that the test passes otherwise, I would suggest to simply add the “allow-stderr” keyword to “Restrictions” in the octave-integration stanza of debian/tests/control. Thanks for your work, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org --- End Message --- --- Begin Message --- Source: bart Source-Version: 0.7.00-3 Done: Martin Uecker We believe that the bug you reported is fixed in the latest version of bart, 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. Martin Uecker (supplier of updated bart package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 31 Dec 2021 10:31:15 +0100 Source: bart Architecture: source Version: 0.7.00-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Martin Uecker Closes: 1010164 Changes: bart (0.7.00-3) unstable; urgency=medium . * Turn off parallel build for determinism. * Arm the unit tests on s390x. * On Debian never use git version. * Workaround for octave bug in integration test. (Closes: #1010164) Checksums-Sha1: 75ed514937bce185bf9aa84b28037823d1df3f38 2164 bart_0.7.00-3.dsc e94f02a350c5b22be0f40a939fd8d1edcf459961 17724 bart_0.7.00-3.debian.tar.xz 64fd7335dc7a8bb476642746f7b62f3618cf1532 7124 bart_0.7.00-3_amd64.buildinfo Checksums-Sha256: 3df79969f4bd4369ba6125c908894a89c27a5afa2d9c8c4c0ad70f5e270f05eb 2164 bart_0.7.00-3.dsc e27381d0501736a3664a03931334429cc31e8e4c4c388a074c06296d2aca1404 17724 bart_0.7.00-3.debian.tar.xz 64b8ef4b361a8db6071d4fda466d05358ff5449b62f47273ae713bd803ed850f 7124 bart_0.7.00-3_amd64.buildinfo Files: fe31a1403a6608931f4ad8ab1ca45579 2164 science optional bart_0.7.00-3.dsc eef0b350ae8470df7ef354a68f34f9cd 17724 science optional bart_0.7.00-3.debian.tar.xz 47f0e122bb330c0c46c8ccecb548bf23 7124 science optional bart_0.7.00-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmJu24ARHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHheg//Rz4O6cxMS8hdsTgf2tBag0KBagRldMJS Nk30saiz6fX5kwtMVFNX2Z35E1YMGyS1SS4YL4dsAbwawzIfn7mqcGdjSXa6W0Fe h98XSMNtSUpJmNFIvBXMOS6Su+wdp2szi01ub7ZpGBVRCV3me/tOAZC49ob532Xg lsQS6yGTw23RpHSHwGRNS4+LVZjN5q1TLXX9PxPBW1OTKCCQPbs9It6kPZBmdDeF XHUpRNsTrp+zgapHdxrsZ8L89GRWKshkFacnt67i6LyDlNH42/Ng1H0/IV89F9be UCTYoZvfPggrd6nJqHha9ZkYI3YdpIWJcSwf2UViaaIM5RoMVkL+S2nkwvOfsjSQ 1WUWQzqClo00mZF3Nu07fyWqS4o+GDOzn5tIp77QnkG2Oumcy2EHMtWg2/9jC5BI 31YHd8jZb6yJ/4zOHp8DM+exNhGkI8C35PvgGnK19cG3KV5hs8vwgJLL5MsYqNI1 i6wyD3atLiQSkrcS8TKG408oNx8DqtnHRn93X+Lsto37/XhmDlN2hyQR3FDwPs7K aePpWo7UaUJE7jEr9oKdlvWlL7G0eZs3AHKP8vYFblmeZfXX/l0ypEzhXZeQRQGr dF0VjM8kF+362NUYqfqibNIPUmo1Z2vH6ZZcfr1FPiGbWKug8CO2+clBeDlTpoXT HQAEvHOYzy8= =u1nW -END PGP SIGNATURE End Message ---
Bug#1008378: marked as done (apertium-spa-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:31:31 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008378, regarding apertium-spa-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-spa-cat Version: 2.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > make[1]: *** [debian/rules:17: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-spa-cat_2.2.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008331: marked as done (apertium-fra-frp: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not met)
Your message dated Sun, 1 May 2022 21:31:31 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008331, regarding apertium-fra-frp: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not met 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.) -- 1008331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-fra-frp Version: 1.0.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.0... yes > checking for lttoolbox >= 3.5.3... yes > checking for cg3 >= 1.3.2... yes > checking for apertium-lex-tools >= 0.2.6... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-fra-frp_1.0.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008390: marked as done (apertium-nno-nob: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008390, regarding apertium-nno-nob: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-nno-nob Version: 1.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-nno-nob_1.3.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008389: marked as done (apertium-spa-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008389, regarding apertium-spa-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met 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.) -- 1008389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-spa-ita Version: 0.2.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for apertium-lex-tools >= 0.2.7... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > make[1]: *** [debian/rules:17: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-spa-ita_0.2.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008388: marked as done (apertium-swe-nor: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008388, regarding apertium-swe-nor: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-swe-nor Version: 0.3.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-swe-nor_0.3.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008373: marked as done (apertium-hbs-eng: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008373, regarding apertium-hbs-eng: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not met 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.) -- 1008373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-hbs-eng Version: 0.5.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.0... yes > checking for apertium-lex-tools >= 0.2.6... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-hbs-eng_0.5.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008363: marked as done (apertium-por-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008363, regarding apertium-por-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not met 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.) -- 1008363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-por-cat Version: 0.10.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.1... yes > checking for lttoolbox >= 3.5.1... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.3... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-por-cat_0.10.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008371: marked as done (apertium-pol-szl: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008371, regarding apertium-pol-szl: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-pol-szl Version: 0.2.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-pol-szl_0.2.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008370: marked as done (apertium-bel-rus: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008370, regarding apertium-bel-rus: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not met 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.) -- 1008370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-bel-rus Version: 0.2.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.1... yes > checking for lttoolbox >= 3.5.1... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.3... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-bel-rus_0.2.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008367: marked as done (apertium-swe-dan: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008367, regarding apertium-swe-dan: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-swe-dan Version: 0.8.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-swe-dan_0.8.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008365: marked as done (apertium-arg-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008365, regarding apertium-arg-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met 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.) -- 1008365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-arg-cat Version: 0.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for apertium-lex-tools >= 0.2.7... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-arg-cat_0.2.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008362: marked as done (apertium-dan-nor: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008362, regarding apertium-dan-nor: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-dan-nor Version: 1.4.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-dan-nor_1.4.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008359: marked as done (apertium-fra-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008359, regarding apertium-fra-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not met 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.) -- 1008359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-fra-cat Version: 1.9.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.1... yes > checking for lttoolbox >= 3.5.1... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.3... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.3) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-fra-cat_1.9.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008353: marked as done (apertium-cat-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008353, regarding apertium-cat-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-cat-ita Version: 0.2.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-cat-ita_0.2.1-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008335: marked as done (apertium-hbs-slv: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008335, regarding apertium-hbs-slv: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not met 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.) -- 1008335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-hbs-slv Version: 0.5.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for apertium-lex-tools >= 0.2.6... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-hbs-slv_0.5.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008347: marked as done (apertium-es-gl: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008347, regarding apertium-es-gl: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met 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.) -- 1008347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-es-gl Version: 1.0.9-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for apertium-lex-tools >= 0.2.7... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > make[1]: *** [debian/rules:17: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-es-gl_1.0.9-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008339: marked as done (apertium-eng-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008339, regarding apertium-eng-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-eng-cat Version: 1.0.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-eng-cat_1.0.1-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008341: marked as done (apertium-srd-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008341, regarding apertium-srd-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met 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.) -- 1008341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-srd-ita Version: 1.1.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for lttoolbox >= 3.5.3... yes > checking for cg3 >= 1.3.2... yes > checking for apertium-lex-tools >= 0.2.7... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-srd-ita_1.1.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008346: marked as done (apertium-rus-ukr: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008346, regarding apertium-rus-ukr: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not met 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.) -- 1008346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-rus-ukr Version: 0.2.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for apertium-lex-tools >= 0.2.6... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.6) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-rus-ukr_0.2.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008334: marked as done (apertium-oci-fra: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008334, regarding apertium-oci-fra: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-oci-fra Version: 0.3.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-oci-fra_0.3.0-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008333: marked as done (apertium-afr-nld: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008333, regarding apertium-afr-nld: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1008333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-afr-nld Version: 0.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-afr-nld_0.3.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008332: marked as done (apertium-cat-srd: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008332, regarding apertium-cat-srd: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met 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.) -- 1008332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-cat-srd Version: 1.1.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for apertium-lex-tools >= 0.2.7... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-cat-srd_1.1.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1008329: marked as done (apertium-spa-arg: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)
Your message dated Sun, 1 May 2022 21:16:16 +0200 with message-id and subject line Closing transient build errors has caused the Debian Bug report #1008329, regarding apertium-spa-arg: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met 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.) -- 1008329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-spa-arg Version: 0.5.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for apertium-lex-tools >= 0.2.7... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > make[1]: *** [debian/rules:20: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2022/03/26/apertium-spa-arg_0.5.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Given that a usable apertium-lex-tools is now in unstable, these bugs no longer apply. -- Tino Didriksen --- End Message ---
Bug#1010287: marked as done (perl-openssl-defaults: generated substvar should not end in a newline)
Your message dated Sun, 01 May 2022 19:04:18 + with message-id and subject line Bug#1010287: fixed in perl-openssl-defaults 6 has caused the Debian Bug report #1010287, regarding perl-openssl-defaults: generated substvar should not end in a newline 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.) -- 1010287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libnet-ssleay-perl Version: 1.92-1 Severity: serious >From my build log: ... dh_installdocs -a dh_installchangelogs -a dh_installexamples -a dh_installman -a dh_perl -a dh_perl_openssl -a dh_link -a dh_strip_nondeterminism -a dh_compress -a dh_fixperms -a dh_missing -a dh_dwz -a dh_strip -a dh_makeshlibs -a dh_shlibdeps -a dpkg-shlibdeps: error: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2 dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/libnet-ssleay-perl.substvars debian/libnet-ssleay-perl/usr/lib/x86_64-linux-gnu/perl5/5.34/auto/Net/SSLeay/SSLeay.so returned exit code 255 dh_shlibdeps: error: Aborting due to earlier error make: *** [debian/rules:6: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Looking at the file it's complaining about, debian/libnet-ssleay-perl.substvars contains: perl:Depends=perl, perl-openssl-abi-1.1 , perlapi-5.34.0 (My best guess would be that this is a bug in perl-openssl-defaults / dh_perl_openssl, but it's just a guess...) -- Daniel Schepler --- End Message --- --- Begin Message --- Source: perl-openssl-defaults Source-Version: 6 Done: Niko Tyni We believe that the bug you reported is fixed in the latest version of perl-openssl-defaults, 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. Niko Tyni (supplier of updated perl-openssl-defaults 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: Sun, 01 May 2022 21:47:34 +0300 Source: perl-openssl-defaults Architecture: source Version: 6 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Niko Tyni Closes: 1010287 Changes: perl-openssl-defaults (6) unstable; urgency=medium . [ Debian Janitor ] * Remove constraints unnecessary since stretch: + perl-openssl-defaults: Drop versioned constraint on libcrypt-openssl-bignum-perl, libcrypt-openssl-dsa-perl, libcrypt-openssl-pkcs10-perl, libcrypt-openssl-pkcs12-perl, libcrypt-openssl-rsa-perl, libcrypt-openssl-x509-perl, libcrypt-smime-perl, libcrypt-ssleay-perl and libnet-ssleay-perl in Breaks. * Bump debhelper from old 12 to 13. * Update standards version to 4.6.0, no changes needed. . [ Niko Tyni ] * dh_perl_openssl: remove trailing newline from substvar (Closes: #1010287) * Recommend debhelper, which is the normal way to use this package. Checksums-Sha1: 6dcdc864ff261c8eb34588027da06f36ccb0c878 1798 perl-openssl-defaults_6.dsc b89f323ddf117fc6144b4d86172ffbef319078cb 4704 perl-openssl-defaults_6.tar.xz 917a7882520e4dc71d43b7a83a2a1e218e4e1fa7 6003 perl-openssl-defaults_6_source.buildinfo Checksums-Sha256: 0afc6abf58f5379bdac54ce1ef68354d685c0cabc65fae8ef13f6cdd2b5c6114 1798 perl-openssl-defaults_6.dsc b7c15e5c0c4262ab0fc236b9c6ee2938250a6a90abb9589ce984b8b893511cb5 4704 perl-openssl-defaults_6.tar.xz c810f4ed6c30ba8629626a928d5f1a6f636434073420b3324632a2e31991df59 6003 perl-openssl-defaults_6_source.buildinfo Files: 3c5628f585bca96bd7ebc02434a9d95a 1798 perl optional perl-openssl-defaults_6.dsc 2e1c5ac699455e69978df7d7bdc35ffc 4704 perl optional perl-openssl-defaults_6.tar.xz 3b3836e84d5c1152857b63cf8b06cf33 6003 perl optional perl-openssl-defaults_6_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAmJu1goRHG50eW5pQGRl Ymlhbi5vcmcACgkQLsD/s7cwGx/Sxg/+IRudfUs4jZ/UQZEbzYWuDzoAHKu8DReq 7zVUJbEIv02MQpyPGWSOvxYOJoozh407/Fd8VO8NBJDeiCGYdDpy0ow78/8Lxxwr +yYPmGlLVS3A6QtOyR6vg7fWM6ckWLSV8QbXiBERkSLApYwawBB04U5tfGApjDfo PnJH5WJLf4ytVqx5gVUBeu
Processed: nodejs 14.19 hangs on mipsel/mips64el when building qtwebengine frontend with rollup and terser plugin
Processing control commands: > fixed -1 nodejs/16.14.2+dfsg-1 Bug #1010446 [nodejs] nodejs 14.19 hangs on mipsel/mips64el when building qtwebengine frontend with rollup and terser plugin Marked as fixed in versions nodejs/16.14.2+dfsg-1. -- 1010446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010446: nodejs 14.19 hangs on mipsel/mips64el when building qtwebengine frontend with rollup and terser plugin
Package: nodejs Version: 16.13.2+really14.19.1~dfsg-6 Severity: serious Control: fixed -1 nodejs/16.14.2+dfsg-1 Affects: src:qtwebengine-opensource-src Dear nodejs maintainers, Currently qtwebengine-opensource-src FTBFS on mipsel and mips64el: https://buildd.debian.org/status/logs.php?pkg=qtwebengine-opensource-src&ver=5.15.8%2Bdfsg-1%2Bb2&arch=mips64el This started happening after nodejs was upgraded from 12.22 to 14.19, and it does not happen with 16.14 from experimental. Here are the steps to reproduce this bug (qtwebengine is huge, I tried to make the test case smaller): # apt install nodejs rollup node-rollup-plugin-terser $ wget https://mitya57.me/nodejs/front_end.tar.xz $ tar xJf front_end.tar.xz $ cd front_end $ nodejs /usr/bin/rollup --plugin terser --config rollup.config.js --input timeline_model/timeline_model.prebundle.js On eller porter box, with nodejs 16.14 this command succeeds in ~11 seconds. With nodejs 14.19, it hangs and does not finish in an hour. With 16.14 it prints a warning about circular dependency, but it's just a warning, not an error (the build still succeeds). I see there is a transition to new nodejs planned (#1010438), but I am still filing this bug for documentation purposes and with RC severity, as requested by Sebastian Ramacher. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1009041: marked as done (guile-git: FTBFS with libgit2 1.3.0)
Your message dated Sun, 01 May 2022 18:18:59 + with message-id and subject line Bug#1009041: fixed in guile-git 0.5.2-4 has caused the Debian Bug report #1009041, regarding guile-git: FTBFS with libgit2 1.3.0 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.) -- 1009041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: guile-git Version: 0.5.2-3 Severity: important X-Debbugs-Cc: mdbi...@disroot.org Dear Maintainer, guile-git was found to fail to build during a test rebuild with libgit2 1.3.0 in unstable. Attaching the build logs as well. Relevant part(hopefully) : FAIL: tests/proxy = test-name: clone with HTTPS proxy location: /<>/tests/proxy.scm:95 source: + (test-equal + "clone with HTTPS proxy" + '(CONNECT "example.org:443") + (clone-through-proxy + "https://example.org/example.git";)) expected-value: (CONNECT "example.org:443") actual-value: #f actual-error: + (match-error "match" "no matching pattern" #f) result: FAIL Testsuite summary for Guile-Git 0.5.2 # TOTAL: 105 # PASS: 99 # SKIP: 5 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log make[4]: *** [Makefile:995: test-suite.log] Error 1 make[4]: Leaving directory '/<>/debian/build/guile-3.0' make[3]: *** [Makefile:1103: check-TESTS] Error 2 make[3]: Leaving directory '/<>/debian/build/guile-3.0' make[2]: *** [Makefile:1310: check-am] Error 2 make[2]: Leaving directory '/<>/debian/build/guile-3.0' dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check VERBOSE=1 returned exit code 2 Regards, rmb -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages guile-git depends on: pn guile-3.0 pn guile-bytestructures pn libgit2-dev guile-git recommends no packages. guile-git suggests no packages. sbuild (Debian sbuild) 0.83.0 (05 February 2022) on debian +==+ | guile-git 0.5.2-3 (amd64)Wed, 06 Apr 2022 08:11:52 + | +==+ Package: guile-git Version: 0.5.2-3 Source Version: 0.5.2-3 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-f5883bae-d291-496f-8c38-fa96825ba363' with '<>' I: NOTICE: Log filtering will replace 'build/guile-git-sKgUdC/resolver-t3okJ6' with '<>' +--+ | Update chroot| +--+ Get:1 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ InRelease Ign:1 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ InRelease Get:2 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ Release [954 B] Get:2 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ Release [954 B] Get:3 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ Release.gpg Ign:3 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ Release.gpg Get:4 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ Packages [1243 B] Err:4 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ Packages Could not open file /build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive/./Packages - open (13: Permission denied) Get:4 file:/build/guile-git-sKgUdC/resolver-Rfn1kQ/apt_archive ./ Packages [3269 B] Get:5 http://ftp.us.debian.org/debian unstable InRelease [165 kB] Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB] Get:7 http://deb.debian.org/debian experimental/main amd64 Packages [3
Processed: Re: python3.10 breaks yade autopkgtest on i386: Segmentation fault
Processing control commands: > reassign -1 src:yade Bug #1009739 [src:python3.10, src:yade] python3.10 breaks yade autopkgtest on i386: Segmentation fault Bug reassigned from package 'src:python3.10, src:yade' to 'src:yade'. No longer marked as found in versions yade/2022.01a-7 and python3.10/3.10.4-3. Ignoring request to alter fixed versions of bug #1009739 to the same values previously set -- 1009739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009739: python3.10 breaks yade autopkgtest on i386: Segmentation fault
Control: reassign -1 src:yade yade was removed from testing, and also is not installable on i386. Reassigning until we can investigate if that's a Python issue.
Bug#984203: marked as done (libpgf: ftbfs with GCC-11)
Your message dated Sun, 01 May 2022 18:00:11 +
with message-id
and subject line Bug#984203: fixed in libpgf 7.21.7+ds-1
has caused the Debian Bug report #984203,
regarding libpgf: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
984203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpgf
Version: 6.14.12-3.2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libpgf_6.14.12-3.2_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
483 | #define THROW_ throw(IOException)
|^
Decoder.cpp:75:68: note: in expansion of macro ‘THROW_’
75 |bool useOMP, bool skipUserData)
THROW_
|
^~
../include/PGFplatform.h:483:16: error: ISO C++17 does not allow dynamic
exception specifications
483 | #define THROW_ throw(IOException)
|^
Decoder.cpp:232:67: note: in expansion of macro ‘THROW_’
232 | UINT32 CDecoder::ReadEncodedData(UINT8* target, UINT32 len) const
THROW_ {
| ^~
../include/PGFplatform.h:483:16: error: ISO C++17 does not allow dynamic
exception specifications
483 | #define THROW_ throw(IOException)
|^
Decoder.cpp:252:106: note: in expansion of macro ‘THROW_’
252 | void CDecoder::Partition(CSubband* band, int quantParam, int width, int
height, int startPos, int pitch) THROW_ {
|
^~
../include/PGFplatform.h:483:16: error: ISO C++17 does not allow dynamic
exception specifications
483 | #define THROW_ throw(IOException)
|^
Decoder.cpp:319:91: note: in expansion of macro ‘THROW_’
319 | void CDecoder::DecodeInterleaved(CWaveletTransform* wtChannel, int
level, int quantParam) THROW_ {
|
^~
../include/PGFplatform.h:483:16: error: ISO C++17 does not allow dynamic
exception specifications
483 | #define THROW_ throw(IOException)
|^
Decoder.cpp:435:36: note: in expansion of macro ‘THROW_’
435 | void CDecoder::Skip(UINT64 offset) THROW_ {
|^~
../include/PGFplatform.h:483:16: error: ISO C++17 does not allow dynamic
exception specifications
483 | #define THROW_ throw(IOException)
|^
Decoder.cpp:448:80: note: in expansion of macro ‘THROW_’
448 | void CDecoder::DequantizeValue(CSubband* band, UINT32 bandPos, int
quantParam) THROW_ {
|
^~
../include/PGFplatform.h:483:16: error: ISO C++17 does not allow dynamic
exception specifications
483 | #define THROW_ throw(IOException)
|^
Decoder.cpp:463:35: note: in expansion of macro ‘THROW_’
463 | void CDecode
Processed: Re: Bug#1009041: guile-git: FTBFS with libgit2 1.3.0
Processing control commands: > forwarded 1009041 https://gitlab.com/guile-git/guile-git/-/issues/23 Bug #1009041 [guile-git] guile-git: FTBFS with libgit2 1.3.0 Set Bug forwarded-to-address to 'https://gitlab.com/guile-git/guile-git/-/issues/23'. -- 1009041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009041: guile-git: FTBFS with libgit2 1.3.0
Control: forwarded 1009041 https://gitlab.com/guile-git/guile-git/-/issues/23 On 2022-04-06, Mohammed Bilal wrote: > guile-git was found to fail to build during a test rebuild with > libgit2 1.3.0 in unstable. Attaching the build logs as well. > > Relevant part(hopefully) : > > FAIL: tests/proxy > = > > test-name: clone with HTTPS proxy > location: /<>/tests/proxy.scm:95 > source: > + (test-equal > + "clone with HTTPS proxy" > + '(CONNECT "example.org:443") > + (clone-through-proxy > + "https://example.org/example.git";)) > expected-value: (CONNECT "example.org:443") > actual-value: #f > actual-error: > + (match-error "match" "no matching pattern" #f) > result: FAIL There is a bug report and merge request upstream that fixes this issue: https://gitlab.com/guile-git/guile-git/-/issues/23 https://gitlab.com/guile-git/guile-git/-/merge_requests/32 And I can confirm they fix the issue in Debian's packaging as well. Will upload a fix shortly. live well, vagrant signature.asc Description: PGP signature
Bug#1009888: [Pkg-rust-maintainers] Bug#1009888: rust-h2, existing version is badly broken, new upstream needs new package
On 01/05/2022 14:00, Fabian Grünbichler wrote: currently progress is blocked on - itoa/serde_json transition (anybody working actively on that?) I just uploaded the new itoa to experimental and took a quick look through the reverse dependencies. rust-cssparser - already broken and not in testing. rust-csv - built/tested fine after patching to use itoa 1, upstream also has an unreleased change switching to itoa1 with no code changes. rust-http - fixed version in debcargo-conf (semver breaking, but all rdeps are broken right now anyway) rust-hyper - already broken and not in testing. rust-num-format - already broken and not in testing. rust-serde-json - fixed version in debcargo-conf (not semver breaking) rust-serde-urlencoded - fixed upstream (semver breaking, but all rdeps are broken right now anyway) rust-time - fixed upstream (not semver breaking) I'm not seeing any reason not to go ahead with pushing this to unstable, anyone have any comments before I go ahead?
Bug#1010432: debian-edu-config: autopkgtest regression: update-mime: not found
[ Paul Gevers, 2022-05-01 ] > It seems that with the fix for bug #1010102 you either picked the > wrong Depends of two, or you forgot to update the postinst for the > change as update-mime lives in mailcap. AFAICT calling update-mime in d-e-c.postinst is unneeded since the obsolete debian-edu-mailcap file has been removed, see commit 2aaa1adf: https://salsa.debian.org/debian-edu/debian-edu-config/-/commit/2aaa1adfac0f1ea63520bd884c2c48c674b51e3c and commit 24f26f25: https://salsa.debian.org/debian-edu/debian-edu-config/-/commit/24f26f2552cdc62e5b580cac4d7e40a6f973c326 The update-mime call should be removed from the postinst script. The Depends on mime-support had been added in 2004 due to moving the mailcap file and calling update-mime in d-e-c.postinst, see commit 91550cf1: https://salsa.debian.org/debian-edu/debian-edu-config/-/commit/91550cf1d35774f10cc9989f16038eeabf95e86b IMO d-e-config neither needs media-types nor mailcap as dependencies, please check. Wolfgang signature.asc Description: PGP signature
Processed: close FTBFS bug
Processing commands for cont...@bugs.debian.org: > fixed 999066 0.1.2.0-5 Bug #999066 [src:tmexpand] tmexpand: missing required debian/rules targets build-arch and/or build-indep The source 'tmexpand' and version '0.1.2.0-5' do not appear to match any binary packages Marked as fixed in versions tmexpand/0.1.2.0-5. > close 999066 Bug #999066 [src:tmexpand] tmexpand: missing required debian/rules targets build-arch and/or build-indep Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 999066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010164: fails autopkgtest against Octave 7
On Mon, 25 Apr 2022 17:23:25 +0200 =?utf-8?q?S=C3=A9bastien_Villemot?= wrote: > Package: octave-bart > Version: 0.7.00-2 > Severity: serious > Tags: patch > Control: block 1009865 by -1 > > Dear Maintainer, > > The autopkgtest for octave-bart fails against octave 7.1.0-2 recently uploaded > to unstable. See: > https://ci.debian.net/data/autopkgtest/testing/amd64/b/bart/21135046/log.gz > > The problem comes from a message that is printed to stderr: > > error: ignoring const execution_exception& while preparing to exit > > This message only appears when running the autopkgtest in a dedicated chroot > as > done on the DebCI infrastructure. I wasn’t able to reproduce it in other > contexts, and I could not figure out what causes it. > > Since this message is essentially harmless, and given that the test passes > otherwise, I would suggest to simply add the “allow-stderr” keyword to > “Restrictions” in the octave-integration stanza of debian/tests/control. I am happy to do this if this is necessary, but isn't this obviously caused by a bug in octave? Martin
Bug#1010428: marked as done (twine: autopkgtest needs update for new version of python-readme-renderer: error message changed)
Your message dated Sun, 01 May 2022 15:20:08 +
with message-id
and subject line Bug#1010428: fixed in twine 4.0.0-3
has caused the Debian Bug report #1010428,
regarding twine: autopkgtest needs update for new version of
python-readme-renderer: error message changed
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.)
--
1010428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twine
Version: 4.0.0-2
Severity: serious
X-Debbugs-CC: python-readme-rende...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-readme-renderer
Dear maintainer(s),
With a recent upload of python-readme-renderer the autopkgtest of twine
fails in testing when that autopkgtest is run with the binary packages
of python-readme-renderer from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python-readme-renderer from testing35.0-1
twine from testing4.0.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report. After a very
brief inspection, it seems the test captures an error message and
expects it to remain unchanged.
Currently this regression is blocking the migration of
python-readme-renderer to testing [1]. Of course, python-readme-renderer
shouldn't just break your autopkgtest (or even worse, your package), but
it seems to me that the change in python-readme-renderer was intended
and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-readme-renderer
should really add a versioned Breaks on the unfixed version of (one of
your) package(s). Note: the Breaks is nice even if the issue is only in
the autopkgtest as it helps the migration software to figure out the
right versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-readme-renderer
https://ci.debian.net/data/autopkgtest/testing/amd64/t/twine/21263820/log.gz
__ test_fails_rst_no_content
___
tmp_path =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_fails_rst_no_content0')
capsys = <_pytest.capture.CaptureFixture object at 0x7fe0218f5210>
caplog = <_pytest.logging.LogCaptureFixture object at 0x7fe0218f7eb0>
def test_fails_rst_no_content(tmp_path, capsys, caplog):
sdist = build_sdist(
tmp_path,
{
"setup.cfg": (
"""
[metadata]
name = test-package
version = 0.0.1
long_description = file:README.rst
long_description_content_type = text/x-rst
"""
),
"README.rst": (
"""
test-package
"""
),
},
)
assert check.check([sdist])
assert capsys.readouterr().out == f"Checking {sdist}: FAILED\n"
> assert caplog.record_tuples == [
(
"twine.commands.check",
logging.ERROR,
"`long_description` has syntax errors in markup "
"and would not be rendered on PyPI.\n",
),
]
E AssertionError: assert [('twine.comm...RST source.')] ==
[('twine.comm... on PyPI.\n')]
E At index 0 diff: ('twine.commands.check', 40,
'`long_description` has syntax errors in markup and would not be
rendered on PyPI.\nNo content rendered from RST source.') !=
('twine.commands.check', 40, '`long_description` has syntax errors in
markup and would not be rendered on PyPI.\n')
E Use -v to get the full diff
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: twine
Source-Version: 4.0.0-3
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
twine, 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
Processed: Bug#1010428 marked as pending in twine
Processing control commands: > tag -1 pending Bug #1010428 [src:twine] twine: autopkgtest needs update for new version of python-readme-renderer: error message changed Added tag(s) pending. -- 1010428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010428: marked as pending in twine
Control: tag -1 pending Hello, Bug #1010428 in twine 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/twine/-/commit/8e043effc84790c579657a31787f9aebc153a8d3 Patch: Support (and require) python3-readme-renderer (>= 35). (Closes: #1010428) (this message was generated automatically) -- Greetings https://bugs.debian.org/1010428
Bug#1003463: Functionally broken with current PHP
Le 01/05/2022 à 15:29, Christoph Biedl a écrit : Control: tag 1003463 confirmed Roman Lebedev wrote... Package: arcanist Version: 0~git20200925-2 Severity: grave @Sylvestre, as previously mentioned in IRC (possibly got lost), I am considering rebasing the src:phabricator package to the latest git commit in the respective upstream repositories. Please let me know what you think about this - or feel free to do it on your own. Christoph Sure, many thanks :) S
Processed: Increase severity - FTBFS with libgit 1.3
Processing commands for cont...@bugs.debian.org: > severity 1009041 serious Bug #1009041 [guile-git] guile-git: FTBFS with libgit2 1.3.0 Severity set to 'serious' from 'important' > severity 1009029 serious Bug #1009029 [julia] julia: FTBFS with libgit2 1.3.0 Severity set to 'serious' from 'important' > severity 1009019 serious Bug #1009019 [libgit2-glib-1.0-0] libgit2-glib-1.0-0: FTBFS with libgit2 1.3.0 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1009019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009019 1009029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009029 1009041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Increase severity 1009017
Processing commands for cont...@bugs.debian.org: > severity 1009017 serious Bug #1009017 [src:criterion] criterion: FTBFS with libgit2 1.3.0 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1009017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999050: marked as done (cldump: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sun, 01 May 2022 13:48:46 +
with message-id
and subject line Bug#999050: fixed in cldump 0.11~dfsg-5
has caused the Debian Bug report #999050,
regarding cldump: missing required debian/rules targets build-arch and/or
build-indep
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.)
--
999050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cldump
Version: 0.11~dfsg-4
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep
Dear maintainer,
Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.
This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.
Best,
Lucas
--- End Message ---
--- Begin Message ---
Source: cldump
Source-Version: 0.11~dfsg-5
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
cldump, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated cldump package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 01 May 2022 18:54:24 +0530
Source: cldump
Architecture: source
Version: 0.11~dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Nilesh Patra
Closes: 960293 999050
Changes:
cldump (0.11~dfsg-5) unstable; urgency=medium
.
* QA upload.
* Modernize packaging
- Bump Standards-Version to 4.6.0 (no changes needed)
- Switch from archaic d/rules to modern debhelper based one
(Closes: #999050, #960293)
- Remove un-needed d/dirs
- Add d/{install,examples,manpages} to install binary,
example and manpage
- Add "Rules-Requires-Root: no"
Checksums-Sha1:
78d120cfa8fc2061466322054cb68cbdb2e4c856 1730 cldump_0.11~dfsg-5.dsc
4ff5ae15b518b4933f523a970d83128a4160c551 2492 cldump_0.11~dfsg-5.debian.tar.xz
34d808d8ac5a092e0217ed49e1f4f0fbc81b0b40 5973
cldump_0.11~dfsg-5_amd64.buildinfo
Checksums-Sha256:
ea908289f1ab9084775c9b7275ee732a3705d06f518138290c9bfc6770190b66 1730
cldump_0.11~dfsg-5.dsc
d12e730ee63c0bed8b0e85ed94979ece0b0b2eda32c5c88851375d41ace18b31 2492
cldump_0.11~dfsg-5.debian.tar.xz
d51ba4cdb76f3df1a0280c08ef1cc7e1390f85360c988580dd01b39f4a9f7192 5973
cldump_0.11~dfsg-5_amd64.buildinfo
Files:
368c38f2eec8d7a8d41a50f89dd528fd 1730 misc optional cldump_0.11~dfsg-5.dsc
ee861f4409fd696a4c5a7655c90a57d5 2492 misc optional
cldump_0.11~dfsg-5.debian.tar.xz
a9a7e7b152321d177cdff6b2ff985b16 5973 misc optional
cldump_0.11~dfsg-5_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmJujfISHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxGi8P+gPDzruApUqEs1mHmlvwy9QCpC9g0KOJ
ng3t0NDS1JKGhGWF4qF1TTmMpBm++D7R39acvysvjf5q4+Yh+055+bXn6MQBq1R7
8K5TrP3GHsuIxllSlbf+w8Baau5SgwVnFcZOEnNJl77w8bk6XDV36YFPwRCdL9US
gfBGIgVr7QSxUtYFsAsGhw85RoyCP0dsDb6vJdjLmhZXMROb5KU/LOKesSD+SCOt
79XuAyqnrRO8FPnpc9kFzcHdcC4/7a2iBWfUEcQ0K9xUc/o1TylXqmZ4QLlzv8Bs
OsOOOSaSl8ilLWjKLM0cqYK78ohI6GierapIlsraZZ5xxgubHSt1/uWEAkjbMgpa
6fvf7QyUtG48DNfsFbrJY5sC9VQIBnNiVeiXM/kfsGLCKEq4zxUNbv08BNme++AY
DREXy5faIuAVqUkg9aFJQsCDaSwf71xqxc3swHXF/zb2yk7uiakyZ6zhZtwGT8Fu
wg2mpTY3joiCSSF2TXW+hmjCZNIbKeVvlbtovJxCCd8qf2KIQNnYUbDLEzLIWACJ
bFOgFmkQjQ2F1YruotD/cmV4p8AuBAXDXgWHrSErT0z7lTUa6CkubPCSxOottOCZ
6LM0K7BgpVeuZOquY+foni7U9Lv2Cw/MwFJemDQjPKcuSq+KsNWyqPi8xdKkGU7V
soKuj86fniin
=dBd6
-END PGP SIGNATURE End Message ---
Bug#1003463: Functionally broken with current PHP
Control: tag 1003463 confirmed Roman Lebedev wrote... > Package: arcanist > Version: 0~git20200925-2 > Severity: grave @Sylvestre, as previously mentioned in IRC (possibly got lost), I am considering rebasing the src:phabricator package to the latest git commit in the respective upstream repositories. Please let me know what you think about this - or feel free to do it on your own. Christoph signature.asc Description: PGP signature
Processed: Re: Bug#1003463: Functionally broken with current PHP
Processing control commands: > tag 1003463 confirmed Bug #1003463 [arcanist] Functionally broken with current PHP Added tag(s) confirmed. -- 1003463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010276: parasail: compiles something extra (or less) depending on the CPU features available
Am Sun, May 01, 2022 at 02:09:21PM +0200 schrieb Étienne Mollier: > > Note that `sort` is locale dependant, so if that's really the proper way > > to do it (tbh doing find|head feels *very* brittle to me… it's probably > > better if you can think of a better way to achieve whatever that piece > > of code is doing), remember to prepend LC_ALL=C.UTF-8 to the sort call. > > True, thanks for the reminder! As I tried to express the lib*.a file is thrown away afterwards - may be even some touch would do the trick. d-shlibmove simply needs some libparasail.a - no other magic behind this. Kind regards Andreas. -- http://fam-tille.de
Bug#1009888: [Pkg-rust-maintainers] Bug#1009888: rust-h2, existing version is badly broken, new upstream needs new package
On April 20, 2022 11:39 am, Fabian Grünbichler wrote: > On April 20, 2022 12:33 am, Peter Michael Green wrote: >> Package: rust-h2 >> Version: 0.1.26-1 >> X-debbugs-cc: d...@jones.dk >> >> I noticed that Jonas had set a number of bugs about broken rust packages as >> blockers of 900928, so I decided to take a look at some of them. I fixed up >> bytemuck, image and related packages. >> >> I then started looking at reqwest which lead me to h2 (which has been broken >> since the tokio 1.x transition but noone ever got around to filing a >> bug) which >> lead me to http which jonas recently NMU'd. >> >> I feel I need to comment on the technical details of the NMU, I should >> preface >> this by saying that I don't think it's unreasonable to 0-day NMU a minimal >> fix for a long term RC issue, even if (as was not the case here but was the >> case for some of the other NMUs noone ever bothered to actually file the >> RC bug). >> >> However, this NMU did considerably more than just add a minimal fix for >> the rc issue. Most painfullly, the "orig" tarball for the new upstream >> version >> appears to have been derived from upstream git rather than from crates.io >> and this breaks our workflow. If you are going to 0-day stuff please keep >> your uploads minimal. If you want to do more invasive NMUs please give >> the maintainers a chance to respond. >> >> Fortunately it seems the answer is to move to an even newer upstream >> version. The only reverse dependencies of rust-http seem to be the >> h2/hyper stack which badly needs an update to move away from tokio >> 0.x. I have already committed the http update to debcargo-conf and may >> upload it at some point. >> >> Unfortunately moving back up the stack I ran into another issue. h2 and >> hyper have grown a new dependency on tracing. While I am I am happy to >> help with fixing existing rust packages, I am reluctant to take >> responsibility >> for a new package unless it's something I personally use. >> >> So this is where I personally tap out on h2/hyper until/unless someone >> packages tracing. > > we use this stack (h2/hyper) downstream, I can take care of it over the > coming weeks. tracing is unfortunately still rather in-flux, so it will > likely see frequent upgrades. okay, just pushed the following to debcargo-conf: - update of hyper - update of httparse - update of http-body - switch of http to iota 1.x currently progress is blocked on - itoa/serde_json transition (anybody working actively on that?) - tracing being uploaded (capitol?) - tower-service being uploaded (NEW, RFS, please upload!) once all of the above is in the archive, the current version of h2 also builds fine ;)
Bug#1010432: debian-edu-config: autopkgtest regression: update-mime: not found
Source: debian-edu-config Version: 2.12.21 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of debian-edu-config the autopkgtest of debian-edu-config fails in testing when that autopkgtest is run with the binary packages of debian-edu-config from unstable. It passes when run with only packages from testing. In tabular form: passfail debian-edu-config from testing2.12.21 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems that with the fix for bug #1010102 you either picked the wrong Depends of two, or you forgot to update the postinst for the change as update-mime lives in mailcap. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=debian-edu-config https://ci.debian.net/data/autopkgtest/testing/amd64/d/debian-edu-config/21269049/log.gz Setting up debian-edu-config (2.12.21) ... On branch master nothing to commit, working tree clean /var/lib/dpkg/info/debian-edu-config.postinst: 55: update-mime: not found dpkg: error processing package debian-edu-config (--configure): installed debian-edu-config package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of debian-edu-install: debian-edu-install depends on debian-edu-config; however: Package debian-edu-config is not configured yet. dpkg: error processing package debian-edu-install (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of autopkgtest-satdep: autopkgtest-satdep depends on debian-edu-install; however: Package debian-edu-install is not configured yet. dpkg: error processing package autopkgtest-satdep (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: debian-edu-config debian-edu-install autopkgtest-satdep E: Sub-process /usr/bin/dpkg returned an error code (1) OpenPGP_signature Description: OpenPGP digital signature
Bug#1010431: ensmallen: autopkgtest regression on i386: 2.101206341 == Approx( 2.0 )
Source: ensmallen Version: 2.19.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of ensmallen the autopkgtest of ensmallen fails in testing on i386 when that autopkgtest is run with the binary packages of ensmallen from unstable. It passes when run with only packages from testing. In tabular form: passfail ensmallen from testing2.19.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ensmallen https://ci.debian.net/data/autopkgtest/testing/i386/e/ensmallen/21265784/log.gz ~~~ ensmallen-test-aFtbnG is a Catch v2.13.9 host application. Run with -? for options --- CNEHimmelblauFunctionTest --- tests/cne_test.cpp:94 ... tests/cne_test.cpp:103: FAILED: REQUIRE( coordinates(1) == Approx(2.0).margin(0.1) ) with expansion: 2.101206341 == Approx( 2.0 ) 0.000 s: CNEHimmelblauFunctionTest OpenPGP_signature Description: OpenPGP digital signature
Processed: tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile'
Processing control commands: > found -1 tifffile/20220426-1 Bug #1010430 [src:tifffile, src:skimage] tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile' Marked as found in versions tifffile/20220426-1. > found -1 skimage/0.18.3-2 Bug #1010430 [src:tifffile, src:skimage] tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile' Marked as found in versions skimage/0.18.3-2. -- 1010430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010430: tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile'
Source: tifffile, skimage
Control: found -1 tifffile/20220426-1
Control: found -1 skimage/0.18.3-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of tifffile the autopkgtest of skimage fails in
testing when that autopkgtest is run with the binary packages of
tifffile from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
tifffile from testing20220426-1
skimagefrom testing0.18.3-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of tifffile to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=tifffile
https://ci.debian.net/data/autopkgtest/testing/amd64/s/skimage/21268058/log.gz
___ test_tifffile_kwarg_passthrough
def test_tifffile_kwarg_passthrough ():
img = imread(fetch('data/multipage.tif'), key=[1],
multifile=False, multifile_close=True, fastij=True,
is_ome=True)
/usr/lib/python3/dist-packages/skimage/io/tests/test_tifffile.py:41: _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ /usr/lib/python3/dist-packages/skimage/io/_io.py:48: in imread
img = call_plugin('imread', fname, plugin=plugin, **plugin_args)
/usr/lib/python3/dist-packages/skimage/io/manage_plugins.py:207: in
call_plugin
return func(*args, **kwargs)
/usr/lib/python3/dist-packages/skimage/io/_plugins/tifffile_plugin.py:30: in
imread
return tifffile_imread(fname, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
files = '/usr/lib/python3/dist-packages/skimage/data/../data/multipage.tif'
aszarr = False
kwargs = {'fastij': True, 'key': [1], 'multifile': False,
'multifile_close': True}
kwargs_file = {'is_ome': True}, kwargs_seq = {}
tif =
def imread(
files: str
| os.PathLike
| FileHandle
| BinaryIO
| Sequence[str | os.PathLike]
| None = None,
*,
aszarr: bool = False,
**kwargs,
) -> numpy.ndarray | ZarrTiffStore | ZarrFileSequenceStore:
"""Return image data from TIFF file(s) as numpy array or zarr
storage.
Refer to the TiffFile and TiffSequence classes and their
asarray
functions for documentation.
Parameters
--
files : path-like, binary stream, or sequence
File name, seekable binary stream, glob pattern, or sequence of
file names. May be None (default) if 'container' is specified.
aszarr : bool
If True, return file sequences, series, or single pages as
zarr storage instead of numpy array (experimental).
**kwargs
Optional extra arguments.
Parameters 'name', 'offset', 'size', and 'is_' flags are
passed to
TiffFile or TiffSequence.imread.
Parameters 'imread', 'container', 'sort', 'pattern',
'axesorder',
and 'categories' are passed to TiffSequence.
Other parameters are passed to the asarray or aszarr functions.
The first image series in the file is returned if no
arguments are
provided.
Returns
---
numpy.ndarray or zarr storage
Image data from the specified pages.
Zarr storage instances must be closed after use.
See TiffPage.asarray for operations that are applied (or not)
to the raw data stored in the file.
"""
kwargs_file = parse_kwargs(
kwargs,
'name',
'offset',
'size',
# private
'_multifile',
'_useframes',
# is_flags
*(key for key in kwargs if key[:3] == 'is_'),
)
kwargs_seq = parse_kwargs(
kwargs,
'imread',
'container',
'sort',
'pattern',
'axesorder',
'categories',
)
if kwargs_seq.get('container', None) is None:
if isinstance(files, str) and ('*' in files or '?' in files):
files = glob.glob(files)
if not files:
raise ValueError('no files found')
if (
isinstance(files, collections.abc.Sequence)
and not isinstance(files, str)
and len(files) == 1
Bug#1009261: Evolution bwrap problem - may fail to print or hang in startup
Dear developers, I have the same issue in my machine (Debian Bullseye Stable with Gnome 3.38): Evolution doesn't start at all. But I could add that this issue affects also Gnome Online Accounts. To have it working we have to launch WEBKIT_FORCE_SANDBOX=0 gnome-control-center online-accounts Thank you very much, Domenico
Bug#1010429: gddrescue: autopkgtest regression
Source: gddrescue Version: 1.26-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of gddrescue the autopkgtest of gddrescue fails in testing when that autopkgtest is run with the binary packages of gddrescue from unstable. It passes when run with only packages from testing. In tabular form: passfail gddrescue from testing1.26-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from gddrescue/1.26-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=gddrescue https://ci.debian.net/data/autopkgtest/testing/amd64/g/gddrescue/21266348/log.gz 1+0 records in 1+0 records out 10485760 bytes (10 MB, 10 MiB) copied, 0.0754896 s, 139 MB/s GNU ddrescue 1.26 Press Ctrl-C to interrupt [A[A[A[A[A[A ipos:0 B, non-trimmed:0 B, current rate: 0 B/s opos:0 B, non-scraped:0 B, average rate: 0 B/s non-tried: 10485 kB, bad-sector:0 B,error rate: 0 B/s rescued:0 B, bad areas:0,run time: 0s pct rescued:0.00%, read errors:0, remaining time: n/a time since last successful read: n/a Copying non-tried blocks... Pass 1 (forwards) [A[A[A[A[A[A ipos: 10420 kB, non-trimmed:0 B, current rate: 0 B/s opos: 10420 kB, non-scraped:0 B, average rate: 0 B/s non-tried:0 B, bad-sector:0 B,error rate: 0 B/s rescued: 10485 kB, bad areas:0,run time: 0s pct rescued: 100.00%, read errors:0, remaining time: n/a time since last successful read: n/a Copying non-tried blocks... Pass 1 (forwards) [A[A[A[A[A[A ipos: 10420 kB, non-trimmed:0 B, current rate: 10485 kB/s opos: 10420 kB, non-scraped:0 B, average rate: 10485 kB/s non-tried:0 B, bad-sector:0 B,error rate: 0 B/s rescued: 10485 kB, bad areas:0,run time: 0s pct rescued: 100.00%, read errors:0, remaining time: n/a time since last successful read: n/a Finishedautopkgtest [22:12:17]: test clone-file OpenPGP_signature Description: OpenPGP digital signature
Bug#1010428: twine: autopkgtest needs update for new version of python-readme-renderer: error message changed
Source: twine
Version: 4.0.0-2
Severity: serious
X-Debbugs-CC: python-readme-rende...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-readme-renderer
Dear maintainer(s),
With a recent upload of python-readme-renderer the autopkgtest of twine
fails in testing when that autopkgtest is run with the binary packages
of python-readme-renderer from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
python-readme-renderer from testing35.0-1
twine from testing4.0.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report. After a very
brief inspection, it seems the test captures an error message and
expects it to remain unchanged.
Currently this regression is blocking the migration of
python-readme-renderer to testing [1]. Of course, python-readme-renderer
shouldn't just break your autopkgtest (or even worse, your package), but
it seems to me that the change in python-readme-renderer was intended
and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-readme-renderer
should really add a versioned Breaks on the unfixed version of (one of
your) package(s). Note: the Breaks is nice even if the issue is only in
the autopkgtest as it helps the migration software to figure out the
right versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-readme-renderer
https://ci.debian.net/data/autopkgtest/testing/amd64/t/twine/21263820/log.gz
__ test_fails_rst_no_content
___
tmp_path =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_fails_rst_no_content0')
capsys = <_pytest.capture.CaptureFixture object at 0x7fe0218f5210>
caplog = <_pytest.logging.LogCaptureFixture object at 0x7fe0218f7eb0>
def test_fails_rst_no_content(tmp_path, capsys, caplog):
sdist = build_sdist(
tmp_path,
{
"setup.cfg": (
"""
[metadata]
name = test-package
version = 0.0.1
long_description = file:README.rst
long_description_content_type = text/x-rst
"""
),
"README.rst": (
"""
test-package
"""
),
},
)
assert check.check([sdist])
assert capsys.readouterr().out == f"Checking {sdist}: FAILED\n"
> assert caplog.record_tuples == [
(
"twine.commands.check",
logging.ERROR,
"`long_description` has syntax errors in markup "
"and would not be rendered on PyPI.\n",
),
]
E AssertionError: assert [('twine.comm...RST source.')] ==
[('twine.comm... on PyPI.\n')]
E At index 0 diff: ('twine.commands.check', 40,
'`long_description` has syntax errors in markup and would not be
rendered on PyPI.\nNo content rendered from RST source.') !=
('twine.commands.check', 40, '`long_description` has syntax errors in
markup and would not be rendered on PyPI.\n')
E Use -v to get the full diff
OpenPGP_signature
Description: OpenPGP digital signature
Processed: twine: autopkgtest needs update for new version of python-readme-renderer: error message changed
Processing control commands: > affects -1 src:python-readme-renderer Bug #1010428 [src:twine] twine: autopkgtest needs update for new version of python-readme-renderer: error message changed Added indication that 1010428 affects src:python-readme-renderer -- 1010428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010276: marked as done (parasail: compiles something extra (or less) depending on the CPU features available)
Your message dated Sun, 01 May 2022 12:34:17 + with message-id and subject line Bug#1010276: fixed in parasail 2.5+dfsg-4 has caused the Debian Bug report #1010276, regarding parasail: compiles something extra (or less) depending on the CPU features available to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1010276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: parasail Version: 2.5+dfsg-3 Severity: serious User: reproducible-bui...@lists.alioth.debian.org Usertags: cpu Hi! While working on the “reproducible builds” effort [1], we have noticed that your package "parasail" doesn't build reproducibly. In fact, it seems that depending on the type of CPU it builds on, sometimes there are slightly different files. For example, on an i386 system: - usr/lib/i386-linux-gnu/libparasail_novec_table.a - usr/lib/i386-linux-gnu/libparasail_sse41_rowcol.a - usr/lib/i386-linux-gnu/libparasail_avx2_table.a or in an amrhf system: - usr/lib/arm-linux-gnueabihf/libparasail_novec.a - usr/lib/arm-linux-gnueabihf/libparasail_novec_rowcol.a sometimes are there or not. I'll have to remember you that building differently depending on the CPU features of the build host is not allowed by Policy. Furthermore, I notice that amongst the i386 build, there are files such as - usr/lib/i386-linux-gnu/libparasail_sse2.a - usr/lib/i386-linux-gnu/libparasail_sse41.a that makes me wonder if the program is unconditially using SSE instructions on i386, that would be a baseline violation; but since I haven't verified if those features are used unconditially I'm not filing this report about this, however please do check. [1]: https://wiki.debian.org/ReproducibleBuilds -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: parasail Source-Version: 2.5+dfsg-4 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of parasail, 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. Étienne Mollier (supplier of updated parasail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 May 2022 13:27:24 +0200 Source: parasail Architecture: source Version: 2.5+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1010276 Changes: parasail (2.5+dfsg-4) unstable; urgency=medium . * Team upload. * d/rules: temporarily disable Neon support for Arm due to FTBFS. * Add vectorization.patch: fix SIMD compiler support detection with -Wall. * d/rules: disable amd64 only simd extension on i386. * d/rules: cp a library instead of mv; fix random static library disappearing from the build. (Closes: #1010276) * d/rules: flag false positive blhc warnings in configure output. Checksums-Sha1: 9e3657b40289cee5df410ec922e35d2b10293813 2302 parasail_2.5+dfsg-4.dsc c903c0e0b90f39e24cbd2159ad242f9fc39255b2 45540 parasail_2.5+dfsg-4.debian.tar.xz Checksums-Sha256: c0f0d41f55a410305af38efc5fe318182e71ca71ea669a47696d06b3701dab2b 2302 parasail_2.5+dfsg-4.dsc b00b997320c2f35c1e3195d52c7959180f503e6dfe7effeac5c88b4967f86cff 45540 parasail_2.5+dfsg-4.debian.tar.xz Files: 8d9db8119b68f213a77114c1dc6b 2302 science optional parasail_2.5+dfsg-4.dsc ab5b98a50d4305775fdaac01c0b16320 45540 science optional parasail_2.5+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmJud/EUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqhEQ//RTfpXlp8cE9CS0WVuH2VCcKyJuMB Ra0OS4YRa3Vv7iUd/FBr/umbJqSacWjZFLffjp1LBQyLUzEvJJSHeHy/Q7ihagzg 9SlDPZ84+pI9kc1Gbfx39i63anULrMzWy0NOtqRXuYubvx0lspPt4ezkSCLYjx1
Processed: Re: Bug#1010287: libnet-ssleay-perl: FTBFS: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2
Processing control commands: > reassign -1 perl-openssl-defaults 5 Bug #1010287 [src:libnet-ssleay-perl] libnet-ssleay-perl: FTBFS: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2 Bug reassigned from package 'src:libnet-ssleay-perl' to 'perl-openssl-defaults'. No longer marked as found in versions libnet-ssleay-perl/1.92-1. Ignoring request to alter fixed versions of bug #1010287 to the same values previously set Bug #1010287 [perl-openssl-defaults] libnet-ssleay-perl: FTBFS: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2 Marked as found in versions perl-openssl-defaults/5. > tag -1 sid bookworm Bug #1010287 [perl-openssl-defaults] libnet-ssleay-perl: FTBFS: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2 Added tag(s) bookworm and sid. > retitle -1 perl-openssl-defaults: generated substvar should not end in a > newline Bug #1010287 [perl-openssl-defaults] libnet-ssleay-perl: FTBFS: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2 Changed Bug title to 'perl-openssl-defaults: generated substvar should not end in a newline' from 'libnet-ssleay-perl: FTBFS: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2'. > affects -1 src:libnet-ssleay-perl Bug #1010287 [perl-openssl-defaults] perl-openssl-defaults: generated substvar should not end in a newline Added indication that 1010287 affects src:libnet-ssleay-perl -- 1010287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010287: libnet-ssleay-perl: FTBFS: bad line in substvars file debian/libnet-ssleay-perl.substvars at line 2
Control: reassign -1 perl-openssl-defaults 5 Control: tag -1 sid bookworm Control: retitle -1 perl-openssl-defaults: generated substvar should not end in a newline Control: affects -1 src:libnet-ssleay-perl On Wed, Apr 27, 2022 at 03:28:06PM -0700, Daniel Schepler wrote: > Source: libnet-ssleay-perl > Version: 1.92-1 > Severity: serious > dpkg-shlibdeps: error: bad line in substvars file > debian/libnet-ssleay-perl.substvars at line 2 > dh_shlibdeps: error: dpkg-shlibdeps > -Tdebian/libnet-ssleay-perl.substvars > debian/libnet-ssleay-perl/usr/lib/x86_64-linux-gnu/perl5/5.34/auto/Net/SSLeay/SSLeay.so > returned exit code 255 > Looking at the file it's complaining about, > debian/libnet-ssleay-perl.substvars contains: > > perl:Depends=perl, perl-openssl-abi-1.1 > , perlapi-5.34.0 > > (My best guess would be that this is a bug in perl-openssl-defaults / > dh_perl_openssl, but it's just a guess...) Thanks. Looks like Debian::Debhelper::Dh_Lib::addsubstvar no longer strips newlines from substvar values. I think it regressed with debhelper 13.7, probably https://salsa.debian.org/debian/debhelper/-/commit/99892be481c1dd06d9866854a2c14e6a70ae12b7 That said, I think this should be fixed in perl-openssl-defaults by not putting the newline there in the first place. Copying Niels; you might want to restore the newline handling if there are other affected addsubstvar users. If not, I wonder if debhelper should Break perl-openssl-defaults (<= 5) once we have fixed this. -- Niko Tyni nt...@debian.org
Bug#1010276: [Debian-med-packaging] Bug#1010276: parasail: compiles something extra (or less) depending on the CPU features available
On Sun, May 01, 2022 at 10:50:16AM +0200, Étienne Mollier wrote: > Upstream implements run time > CPU detection to avoid baseline violation on older CPU. Great! Thank you for confirming this bit. I figured it might be the case, but I didn't verify it myself (as I noted in my first email). > So I identified three todo items: > 1. address reproducibility issue likely caused by find|head; Note that `sort` is locale dependant, so if that's really the proper way to do it (tbh doing find|head feels *very* brittle to me… it's probably better if you can think of a better way to achieve whatever that piece of code is doing), remember to prepend LC_ALL=C.UTF-8 to the sort call. > 2. fix avx512 support for amd64 architecture; > 3. disable execessive build artifacts for i386 architecture. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#1009460: marked as done (python-marathon: FTBFS: FAILED tests/test_model_event.py::MarathonEventTest::test_marathon_event - At...)
Your message dated Sun, 01 May 2022 10:51:21 + with message-id and subject line Bug#1009460: fixed in python-marathon 0.13.0-4 has caused the Debian Bug report #1009460, regarding python-marathon: FTBFS: FAILED tests/test_model_event.py::MarathonEventTest::test_marathon_event - At... 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.) -- 1009460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-marathon Version: 0.13.0-3 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 '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > for i in 3.9 3.10 ; do \ > python3 setup.py install -f --install-layout=deb > --root=/<>/debian/tmp ; \ > done > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > creating build > creating build/lib > creating build/lib/marathon > copying marathon/__init__.py -> build/lib/marathon > copying marathon/util.py -> build/lib/marathon > copying marathon/exceptions.py -> build/lib/marathon > copying marathon/client.py -> build/lib/marathon > creating build/lib/marathon/models > copying marathon/models/__init__.py -> build/lib/marathon/models > copying marathon/models/events.py -> build/lib/marathon/models > copying marathon/models/queue.py -> build/lib/marathon/models > copying marathon/models/constraint.py -> build/lib/marathon/models > copying marathon/models/app.py -> build/lib/marathon/models > copying marathon/models/base.py -> build/lib/marathon/models > copying marathon/models/endpoint.py -> build/lib/marathon/models > copying marathon/models/task.py -> build/lib/marathon/models > copying marathon/models/container.py -> build/lib/marathon/models > copying marathon/models/group.py -> build/lib/marathon/models > copying marathon/models/deployment.py -> build/lib/marathon/models > copying marathon/models/info.py -> build/lib/marathon/models > running install_lib > creating /<>/debian/tmp > creating /<>/debian/tmp/usr > creating /<>/debian/tmp/usr/lib > creating /<>/debian/tmp/usr/lib/python3 > creating /<>/debian/tmp/usr/lib/python3/dist-packages > creating /<>/debian/tmp/usr/lib/python3/dist-packages/marathon > copying build/lib/marathon/__init__.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon > copying build/lib/marathon/util.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon > copying build/lib/marathon/exceptions.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon > copying build/lib/marathon/client.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon > creating > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/__init__.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/events.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/queue.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/constraint.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/app.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/base.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/endpoint.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/task.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/container.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/group.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/deployment.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > copying build/lib/marathon/models/info.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/models > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/marathon/__init__.p
Processed: Bug#1009460 marked as pending in python-marathon
Processing control commands: > tag -1 pending Bug #1009460 [src:python-marathon] python-marathon: FTBFS: FAILED tests/test_model_event.py::MarathonEventTest::test_marathon_event - At... Added tag(s) pending. -- 1009460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009460: marked as pending in python-marathon
Control: tag -1 pending Hello, Bug #1009460 in python-marathon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-marathon/-/commit/e9ed42a371c40590a9a2ce79e02f539e29b33d59 Add iterable-import-from-collections.abc.patch (Closes: #1009460). (this message was generated automatically) -- Greetings https://bugs.debian.org/1009460
Bug#1010421: gir-to-d: FTBFS with ldc 1.29
Source: gir-to-d Version: 0.22.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org gir-to-d FTBFS with ldc 1.29: FAILED: girtod ldc2 -of=girtod girtod.p/source_girtod.d.o girtod.p/source_gtd_DefReader.d.o girtod.p/source_gtd_GlibTypes.d.o girtod.p/source_gtd_GirAlias.d.o girtod.p/source_gtd_GirConstant.d.o girtod.p/source_gtd_GirEnum.d.o girtod.p/source_gtd_GirField.d.o girtod.p/source_gtd_GirFunction.d.o girtod.p/source_gtd_GirPackage.d.o girtod.p/source_gtd_GirStruct.d.o girtod.p/source_gtd_GirType.d.o girtod.p/source_gtd_GirVersion.d.o girtod.p/source_gtd_GirWrapper.d.o girtod.p/source_gtd_IndentedStringBuilder.d.o girtod.p/source_gtd_Log.d.o girtod.p/source_gtd_LinkedHasMap.d.o girtod.p/source_gtd_WrapException.d.o girtod.p/source_gtd_XMLReader.d.o -L=--allow-shlib-undefined -link-defaultlib-shared -L=-z -L=relro -O -g -release -wi /usr/bin/ld: girtod.p/source_gtd_GirPackage.d.o: in function `_D3gtd12LinkedHasMap__T13LinkedHashMapTAyaTCQBq11GirFunctionQnZQBo4Node11__xopEqualsMxFKxSQDkQDj__TQCyTQCmTQCmZQDkQBwZb': /<>/obj-x86_64-linux-gnu/../source/gtd/LinkedHasMap.d:27: undefined reference to `_D6object__T8opEqualsTxC3gtd11GirFunctionQnTxQwZQBkFxQBexQBiZb' collect2: error: ld returned 1 exit status Error: /usr/bin/cc failed with status: 1 ninja: build stopped: subcommand failed. dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v returned exit code 1 make: *** [debian/rules:8: build-arch] Error 25 See https://buildd.debian.org/status/fetch.php?pkg=gir-to-d&arch=amd64&ver=0.22.0-1%2Bb2&stamp=1651217636&raw=0 Cheers -- Sebastian Ramacher
Processed: mark as fixed in experimental too.
Processing commands for cont...@bugs.debian.org:
> close 984913 0.3.51-1
Bug #984913 {Done: Peter Michael Green }
[src:rust-backtrace] librust-backtrace+rustc-dep-of-std-dev: depends on
unavailable librust-cfg-if-0.1+rustc-dep-of-std-dev
Marked as fixed in versions rust-backtrace/0.3.51-1.
Bug #984913 {Done: Peter Michael Green }
[src:rust-backtrace] librust-backtrace+rustc-dep-of-std-dev: depends on
unavailable librust-cfg-if-0.1+rustc-dep-of-std-dev
Bug 984913 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010276: Bug#1010276: parasail: compiles something extra (or less) depending on the CPU features available
Hi Étienne, Am Sun, May 01, 2022 at 10:50:16AM +0200 schrieb Étienne Mollier: > I'm still looking up this issue, but I wrap up a status to clear > my mind. > > To me, the main topic of the bug is the reproducibility issue[1] > observed on i386, but other architectures may be affected. The > difference is of one *.a file, and after looking up the d/rules > file, this seems to be caused by the assumption that find sorts > in a predictable way in the recipe below, which is not the case: > > override_dh_install: > dh_install > mv `find .libs -name "libparasail*.a" | head -n1` > debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libparasail.a > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include usr \ > --movedev "debian/tmp/usr/lib/*/pkgconfig/*.pc" > usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig \ > debian/tmp/usr/lib/*/*.so > rm debian/libparasail-dev/usr/lib/$(DEB_HOST_MULTIARCH)/libparasail.a > dh_install -p libparasail-dev .libs/*.a usr/lib/$(DEB_HOST_MULTIARCH) > find debian -name "lib*.la" -delete > > I would welcome thoughts on the intent of this part of the code, > because I'm not sure which .a is the one that is supposed to be > selected. If the content is not that important, then maybe it > is just a matter of putting a `sort` between the `find` and the > `head` in the `mv` command. Thanks for having a look into this. I think it does not matter much wgat file is copied here since it is removed afterwadrs inside the rm statement. It was just a trick to make d-shlibmove not complaining about a missing libparasail.a file which is provided that way. Later in the `dh_install -p` statement simply all *.a files are copied by keeping their names whatever it might be. > [1]: > https://tests.reproducible-builds.org/debian/dbdtxt/unstable/i386/parasail_2.5+dfsg-3.diffoscope.txt.gz > > Mattia Rizzolo, on 2022-04-27: > > In fact, it seems that depending on the type of CPU it builds on, > > sometimes there are slightly different files. For example, on an i386 > > system: > > - usr/lib/i386-linux-gnu/libparasail_novec_table.a > > - usr/lib/i386-linux-gnu/libparasail_sse41_rowcol.a > > - usr/lib/i386-linux-gnu/libparasail_avx2_table.a > > or in an amrhf system: > > - usr/lib/arm-linux-gnueabihf/libparasail_novec.a > > - usr/lib/arm-linux-gnueabihf/libparasail_novec_rowcol.a > > sometimes are there or not. > > While I agree it is an error to build binaries to target > specific CPU when doing large scale distribution, in the case of > parasail, this is actually normal. Upstream implements run time > CPU detection to avoid baseline violation on older CPU. After > building the package with avx2 support, I could run the > autopkgtest suite on a generic x86_64 virtual machine (no avx2, > no sse4) without an illegal instruction crash. From the > README.md file in parasail source code: > > >> parasail uses CPU dispatching at runtime to correctly select > >> the appropriate implementation for the highest level of > >> instruction set supported. > > Interestingly, while trying to understand the variability of > build result, I noticed that we were missing builds for avx512 > instruction set, which seems to stem from ./configure failure to > recognize the option due to warnings occurring in the sample > code when -Wall build option is in use. That's probably worth > forwarding upstream. Thanks for noticing this. > > Furthermore, I notice that amongst the i386 build, there are files such > > as > > - usr/lib/i386-linux-gnu/libparasail_sse2.a > > - usr/lib/i386-linux-gnu/libparasail_sse41.a > > that makes me wonder if the program is unconditially using SSE > > instructions on i386, that would be a baseline violation; but since I > > haven't verified if those features are used unconditially I'm not filing > > this report about this, however please do check. > > On the i386 build, I also see avx2 builds, and I would tend to > think those extensions were never implemented on i386, so I > guess it wouldn't hurt, and would reduce resource consumption on > build machines in the process, that these variants are actually > not built. It should be a matter of just passing --disable-avx2 > and similar to the configure step when targeting i386 host > architecture. ACK. > So I identified three todo items: > 1. address reproducibility issue likely caused by find|head; As I tried to explain this theory is not really plausible. > 2. fix avx512 support for amd64 architecture; This would be great. > 3. disable execessive build artifacts for i386 architecture. My guess is this will rather lead to solving the reproducibly issue. > Thanks Mattia for your work on the reproducible build effort, > these issues may not have been caught otherwise! +1 > Have a nice day, :) +1 Kind regards Andreas. -- http:
Bug#1005978: marked as done (Please migrate away from dpatch)
Your message dated Sun, 01 May 2022 07:18:54 + with message-id and subject line Bug#1005978: fixed in vdk2 2.4.0-5.6 has caused the Debian Bug report #1005978, regarding Please migrate away from dpatch 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.) -- 1005978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdk2 Version: 2.4.0-5.5 Severity: serious dpatch is deprecated and will be removed before the bookworm release. Please migrate to source format 3.0 (quilt) instead. --- End Message --- --- Begin Message --- Source: vdk2 Source-Version: 2.4.0-5.6 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of vdk2, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated vdk2 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, 16 Apr 2022 02:36:51 -0300 Source: vdk2 Architecture: source Version: 2.4.0-5.6 Distribution: unstable Urgency: medium Maintainer: Michael Vogt Changed-By: Joao Eriberto Mota Filho Closes: 1005978 Changes: vdk2 (2.4.0-5.6) unstable; urgency=medium . * Non-maintainer upload. * Migrated to DebSrc 3.0. Consequently: - debian/clean: created to remove a file generated from the build. - debian/control: dropped dpatch from Build-Depends field. - debian/patches/01_old_changes.patch: created to group all old direct changes from 1.0 format. - debian/source/options: created to ignore changes in config.guess and config.sub. - Closes: #1005978 Checksums-Sha1: 5410d658bf5d489a85b256aa051eb3a4d177b6bc 1993 vdk2_2.4.0-5.6.dsc b5e25ce01451ff31dc64df9fcf080085364e39bc 73508 vdk2_2.4.0-5.6.debian.tar.xz 107569d2937145d0b3fa05792b086e5c860c5173 10888 vdk2_2.4.0-5.6_source.buildinfo Checksums-Sha256: b600bf7c3cb30195b17d75ec20d38b28b194df904d0111a7abe0cbbe1a4f26c5 1993 vdk2_2.4.0-5.6.dsc bc0bd78abd7581457055295e4de0a9f75034a720eb773c3a473bb291dc8dcff9 73508 vdk2_2.4.0-5.6.debian.tar.xz 92ec521e75e94a60ae3d2f4fef4552a73679ea5ff62821cd6cf70f3a0bf5590e 10888 vdk2_2.4.0-5.6_source.buildinfo Files: d3f0c30f7488ae7a7e7e16f5e2d09ffd 1993 libs optional vdk2_2.4.0-5.6.dsc 93ccf81c50e332fb88e2b6e0b06d37b0 73508 libs optional vdk2_2.4.0-5.6.debian.tar.xz 4d640c2d4dbecd14103adc1b16fadb78 10888 libs optional vdk2_2.4.0-5.6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJaXr8ACgkQ3mO5xwTr 6e/cgQ/5Aabp7WpXKd7fM3Y++TI9mZWhJfsiNMzRHfDnVStA3g8qsQgs783/QCSv wmdP2YPQQgzJPykxNokxtjLuN9Co/Wu3Z5UOZ+cmbJR7TLq8SizKfY7mUFHo8bnv HVq6DI7ULjmqqyZqjXCCAknDoLHKw+9BdvIVjUKSckR6e8Oc8gzCk/1l8B7BWBf4 jkoWMkG2sE4OgLRsm+KVlTCPIJP/G57KP54C4b57n7xJEo8uhBEvEgINQzDAxacS lda1Ult/neOHYBJBe4VsOm0OpPTh1YtZfNSDalOjMArTb5BJ6F6lfopENkOWHBIx O4ExoO6HdmFGSyKxvYsPz5hrvOZzJp3tS8FAKZQgMahjCO6HaGwA94LwE3Cn+NT5 PjhnMTKa2wnQM4DAc0oe1OB8Tzt1mHnxLDbnoQdhRzmg5uGR0f/XuaVarBmdcT4r goaaddezs8ihMvI42QJ2QfFl+Uy1G6U9Pk1i8e/d7fwn2fwXIvbtqbQipahPP3f7 mMA/pX6oiGO9kE4ffyjgNQ2TyysxnykjKCSWVXgVkVf0WxQexq7pS7CUyj3mqfq5 yZ0RmmtIontw6w/91w2jr3/TdTFM1qbuk0uY0b3PpDo5kTTdSpTJbcP5sgY3OJr1 h2eELzCt9a/ECv48RdhrHLKMW/OnIn6Jw/mZGNpP3oOgWWGD1c0= =KdHj -END PGP SIGNATURE End Message ---
