Bug#1057865: reproject ftbfs with Python 3.12
Control: forwarded -1 https://github.com/astropy/reproject/issues/414 Control: reassign -1 python3-astropy-healpix 1.0.0-1 Control: affects -1 src:reproject Control: tags -1 +pending This bug isn't in reproject, but in astropy-healpix and slided through the CI tests there. A solution was found upstream (https://github.com/astropy/astropy-healpix/pull/208) and will be uploaded ASAP.
Processed: Re: reproject ftbfs with Python 3.12
Processing control commands: > forwarded -1 https://github.com/astropy/reproject/issues/414 Bug #1057865 [src:reproject] reproject ftbfs with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/astropy/reproject/issues/414'. > reassign -1 python3-astropy-healpix 1.0.0-1 Bug #1057865 [src:reproject] reproject ftbfs with Python 3.12 Bug reassigned from package 'src:reproject' to 'python3-astropy-healpix'. No longer marked as found in versions reproject/0.13.0-1. Ignoring request to alter fixed versions of bug #1057865 to the same values previously set Bug #1057865 [python3-astropy-healpix] reproject ftbfs with Python 3.12 Marked as found in versions astropy-healpix/1.0.0-1. > affects -1 src:reproject Bug #1057865 [python3-astropy-healpix] reproject ftbfs with Python 3.12 Added indication that 1057865 affects src:reproject > tags -1 +pending Bug #1057865 [python3-astropy-healpix] reproject ftbfs with Python 3.12 Added tag(s) pending. -- 1057865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1058522 + moreinfo Bug #1058522 [src:dired-du] dired-du: FTBFS: make[1]: *** [Makefile:8: test] Error 1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058522: (no subject)
Hi, Hmmm... strange. I cannot reproduce this. I tried to (1) run tests locally with dh_elpa_test, (2) run tests locally as autopkgtest supposed to with dh_elpa_test --autopkgtest, (3) run tests during build from scratch under sbuild, (4) run tests with autopkgtest under sbuild. Tests were successful everywhere. Guess, it is a false positive, but will keep the bug report open for some time. Cheers! Lev
Bug#1057967: Fixed - Was: Re: Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable
Le Mon, Dec 11, 2023 at 02:55:50AM +0100, Kevin Price a écrit : > When booting 6.1.0-15, my physical amd64/bookworm/gnome computer > misbehaves in many ways, rendering it largely unusable. With kernels up > to 6.1.0-13, and even briefly with the otherwise broken 6.1.0-14, all of > this seemed fine. > FWIW, I experienced the same kind of behaviour, linked to a broken wifi with rtl88x2bu DKMS driver. Fixed now with: linux-image-6.1.0-16-amd64-unsigned 6.1.67-1 $ uname -a Linux pcpapa 6.1.0-16-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.67-1 (2023-12-12) x86_64 GNU/Linux Thanks a lot. Best regards, -- Olivier BERGER (OpenPGP: 4096R/7C5BB6A5) http://www.olivierberger.com/weblog/
Bug#1056426: marked as done (mistral-dashboard's autopkg tests fail with Python 3.12)
Your message dated Wed, 13 Dec 2023 08:25:28 +0100 with message-id and subject line Issue was in eventlet has caused the Debian Bug report #1056426, regarding mistral-dashboard's autopkg tests fail with Python 3.12 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.) -- 1056426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mistral-dashboard Version: 17.0.0-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 374s running install_egg_info 374s Copying mistral_dashboard.egg-info to /tmp/autopkgtest.pLcwrL/build.MZb/src/debian/tmp/usr/lib/python3/dist-packages/mistral_dashboard-17.0.0.egg-info 374s Skipping SOURCES.txt 374s running install_scripts 374s + CURDIR 374s /tmp/autopkgtest.pLcwrL/build.MZb/src/debian/tests/unittests: 11: CURDIR: not found 374s + PYTHONPATH=/debian/tmp/usr/lib/python3/dist-packages http_proxy=127.0.0.1:9 https_proxy=127.0.0.9:9 HTTP_PROXY=127.0.0.1:9 HTTPS_PROXY=127.0.0.1:9 DJANGO_SETTINGS_MODULE=mistraldashboard.test.settings PYTHON=python3.12 python3.12 -m coverage run manage.py test mistraldashboard --settings=mistraldashboard.test.settings 376s Traceback (most recent call last): 376s File "/tmp/autopkgtest.pLcwrL/build.MZb/src/manage.py", line 23, in 376s execute_from_command_line(sys.argv) 376s File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 442, in execute_from_command_line 376s utility.execute() 376s File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 382, in execute 376s settings.INSTALLED_APPS 376s File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 102, in __getattr__ 376s self._setup(name) 376s File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 89, in _setup 376s self._wrapped = Settings(settings_module) 376s ^ 376s File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 217, in __init__ 376s mod = importlib.import_module(self.SETTINGS_MODULE) 376s ^ 376s File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module 376s return _bootstrap._gcd_import(name[level:], package, level) 376s 376s File "", line 1381, in _gcd_import 376s File "", line 1354, in _find_and_load 376s File "", line 1325, in _find_and_load_unlocked 376s File "", line 929, in _load_unlocked 376s File "", line 994, in exec_module 376s File "", line 488, in _call_with_frames_removed 376s File "/tmp/autopkgtest.pLcwrL/build.MZb/src/mistraldashboard/test/settings.py", line 17, in 376s from openstack_dashboard.test.settings import * # noqa 376s ^^^ 376s File "/usr/lib/python3/dist-packages/openstack_dashboard/test/settings.py", line 18, in 376s from horizon.utils import secret_key 376s File "/usr/lib/python3/dist-packages/horizon/utils/secret_key.py", line 21, in 376s from oslo_concurrency import lockutils 376s File "/usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py", line 37, in 376s import eventlet 376s File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line 17, in 376s from eventlet import convenience 376s File "/usr/lib/python3/dist-packages/eventlet/convenience.py", line 7, in 376s from eventlet.green import socket 376s File "/usr/lib/python3/dist-packages/eventlet/green/socket.py", line 21, in 376s from eventlet.support import greendns 376s File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 45, in 376s from eventlet.green import ssl 376s File "/usr/lib/python3/dist-packages/eventlet/green/ssl.py", line 25, in 376s _original_wrap_socket = __ssl.wrap_socket 376s ^ 376s AttributeError: module 'ssl' has no attribute 'wrap_socket' 376s autopkgtest [18:30:53]: test unittests: ---] --- End Message --- --- Begin Message --- Hi, The bug was in eventlet, fixed in 0.33.3-2.1. Cheers, Thomas Goirand--- End Message ---
Bug#1058284: marked as done (wmtv: FTBFS: configure: error: Package requirements (libv4l1) were not met)
Your message dated Wed, 13 Dec 2023 07:08:15 + with message-id and subject line Bug#1058284: fixed in v4l-utils 1.26.1-2 has caused the Debian Bug report #1058284, regarding wmtv: FTBFS: configure: error: Package requirements (libv4l1) 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.) -- 1058284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wmtv Version: 0.6.7-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for xext... yes > checking for xpm... yes > checking for xxf86dga... yes > checking for xxf86vm... yes > checking for libv4l1... no > configure: error: Package requirements (libv4l1) were not met > > Package 'libjpeg', required by 'libv4lconvert', not 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 libv4l1_CFLAGS > and libv4l1_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/2023/12/12/wmtv_0.6.7-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: v4l-utils Source-Version: 1.26.1-2 Done: Gregor Jasny We believe that the bug you reported is fixed in the latest version of v4l-utils, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gregor Jasny (supplier of updated v4l-utils 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: Tue, 12 Dec 2023 23:06:08 +0100 Source: v4l-utils Architecture: source Version: 1.26.1-2 Distribution: unstable Urgency: medium Maintainer: Gregor Jasny Changed-By: Gregor Jasny Closes: 1014887 1057247 1058284 Changes: v4l-utils (1.26.1-2) unstable; urgency=medium . [ Chris Hofstaedtler ] * Lookup udev install directory from udev.pc (Closes: #1057247) . [ Jeremy Sowden ] * d/control: add missing dependencies to -dev packages (Closes: #1058284) . [ Gregor Jasny ] * Import latest 1.26.1 upstream release (Closes: #1014887) Checksums-Sha1: 4319a22c37471f41462d0c1de91f4cca7fccecfa 3238 v4l-utils_1.26.1-2.dsc b2abb01e2522a65f1ed5f0e792ea0a6657fb161a 1192312 v4l-utils_1.26.1.orig.tar.xz cc0d8b04e6daa2078d3de21cd65448f8a1c40094 833 v4l-utils_1.26.1.orig.tar.xz.asc 0dfcbfd444c8fb9853fb161cc756fac5b9077375 22784 v4l-utils_1.26.1-2.debian.tar.xz 2754ca85245108bc71732fc55d5a1c9f7fb1355e 17942 v4l-utils_1.26.1-2_arm64.buildinfo Checksums-Sha256: 6bd4c7143c2cd50a8e5df4049504fa5416debf1401137b3dc12a00ed07693393 3238 v4l-utils_1.26.1-2.dsc 4a71608c0ef7df2931176989e6d32b445c0bdc1030a2376d929c8ca6e550ec4e 1192312 v4l-utils_1.26.1.orig.tar.xz 1b1360d428f2e8154dce5f454efb01a22c1b5bbdcf2572e658db0e64f8bfc5b7 833 v4l-utils_1.26.1.orig.tar.xz.asc 74b5510de71ba0fd1efe53f5d5fd7e6af367e399ed73eb76de9a61a1835c4ca1 22784 v4l-utils_1.26.1-
Bug#1056723: marked as done (rabbitmq-server: CVE-2023-46118)
Your message dated Wed, 13 Dec 2023 07:04:51 + with message-id and subject line Bug#1056723: fixed in rabbitmq-server 3.8.9-3+deb11u1 has caused the Debian Bug report #1056723, regarding rabbitmq-server: CVE-2023-46118 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.) -- 1056723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rabbitmq-server Version: 3.10.8-2 Severity: important Tags: security upstream Forwarded: https://github.com/rabbitmq/rabbitmq-server/pull/9708 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for rabbitmq-server. CVE-2023-46118[0]: | RabbitMQ is a multi-protocol messaging and streaming broker. HTTP | API did not enforce an HTTP request body limit, making it vulnerable | for denial of service (DoS) attacks with very large messages. An | authenticated user with sufficient credentials can publish a very | large messages over the HTTP API and cause target node to be | terminated by an "out-of-memory killer"-like mechanism. This | vulnerability has been patched in versions 3.11.24 and 3.12.7. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-46118 https://www.cve.org/CVERecord?id=CVE-2023-46118 [1] https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w6cq-9cf4-gqpg [2] https://github.com/rabbitmq/rabbitmq-server/pull/9708 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: rabbitmq-server Source-Version: 3.8.9-3+deb11u1 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of rabbitmq-server, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated rabbitmq-server 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, 27 Nov 2023 09:21:56 +0100 Source: rabbitmq-server Architecture: source Version: 3.8.9-3+deb11u1 Distribution: bullseye-security Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1056723 Changes: rabbitmq-server (3.8.9-3+deb11u1) bullseye-security; urgency=medium . * CVE-2023-46118: Denial of Service by publishing large messages over the HTTP API. Applied upstream patches that introduce a limit of 10MB: - Reduce_default_HTTP_API_request_body_size_limit_to_10_MiB.patch - Introduce_HTTP_request_body_limit_for_definition_uploads.patch (Closes: #1056723). Checksums-Sha1: 8079f2ea54548419a6883cbcc52c5eb88fe41410 2696 rabbitmq-server_3.8.9-3+deb11u1.dsc dc945062816536124f0c2d6ac32d15c61d0b2f2a 3074468 rabbitmq-server_3.8.9.orig.tar.xz cea2ca8c33db72c6fe2ddc3fd3d4b1b4ab79d841 24012 rabbitmq-server_3.8.9-3+deb11u1.debian.tar.xz 97146e1140a47b954eb35d05016ce05c05e37f85 8789 rabbitmq-server_3.8.9-3+deb11u1_amd64.buildinfo Checksums-Sha256: 01868179878a56c64c08ef930c5b52e587be486390481c7d40f05ab6b246aae8 2696 rabbitmq-server_3.8.9-3+deb11u1.dsc 1b4b764e2f1af29b464b3354f85d360fd505a1b10cb7155fc90816921315452c 3074468 rabbitmq-server_3.8.9.orig.tar.xz 0aa4eb763150e458df6e2cb51ab22bc3dd51e0193f9cac8e020476bafb13a5f4 24012 rabbitmq-server_3.8.9-3+deb11u1.debian.tar.xz 6b4445c57c8a2c587fb4b834105aae25f7811c3ccf7c1ef7ae759f85c4a3b6bd 8789 rabbitmq-server_3.8.9-3+deb11u1_amd64.buildinfo Files: d9c7f16e6248b7d939c968ba47c78330 2696 net optional rabbitmq-server_3.8.9-3+deb11u1.dsc 15ac61eb000efd9c76c11fd886dd8035 3074468 net optional rabbitmq-server_3.8.9.orig.tar.xz e80b2d92d560e86cb36c20622cb7ba23 24012 net optional rabbitmq-server_3.8.9-3+deb11u1.debian.tar.xz b03514a546c8129e840701802c88370b 8789 net optional rabbitmq-server_3.8.9-3+deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmVoO/YACgkQ1BatFaxr Q/4JKw/+NWiD8SWGtRh9FXi28Q0DJyEsMaMkhRcQKng
Bug#1053769: marked as done (nghttp2: CVE-2023-44487)
Your message dated Wed, 13 Dec 2023 07:04:40 + with message-id and subject line Bug#1053769: fixed in nghttp2 1.43.0-1+deb11u1 has caused the Debian Bug report #1053769, regarding nghttp2: CVE-2023-44487 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.) -- 1053769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nghttp2 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for nghttp2. CVE-2023-44487[0]: | The HTTP/2 protocol allows a denial of service (server resource | consumption) because request cancellation can reset many streams | quickly, as exploited in the wild in August through October 2023. https://github.com/nghttp2/nghttp2/security/advisories/GHSA-vx74-f528-fxqg https://github.com/nghttp2/nghttp2/pull/1961 https://github.com/nghttp2/nghttp2/commit/72b4af6143681f528f1d237b21a9a7aee1738832 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: nghttp2 Source-Version: 1.43.0-1+deb11u1 Done: Moritz Mühlenhoff We believe that the bug you reported is fixed in the latest version of nghttp2, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Mühlenhoff (supplier of updated nghttp2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 24 Nov 2023 15:47:19 +0100 Source: nghttp2 Architecture: source Version: 1.43.0-1+deb11u1 Distribution: bullseye-security Urgency: medium Maintainer: Tomasz Buchert Changed-By: Moritz Mühlenhoff Closes: 1053769 Changes: nghttp2 (1.43.0-1+deb11u1) bullseye-security; urgency=medium . * CVE-2023-44487 (Closes: #1053769) Checksums-Sha1: 750d1086144556a6eda95d8cc5249d7e9d925de1 2555 nghttp2_1.43.0-1+deb11u1.dsc cf95821d4f5afe5b69911eb98fb1f4681c8c86d0 4521786 nghttp2_1.43.0.orig.tar.bz2 4a07939c82b2e6893fe19c681b9a8f5b99105880 21832 nghttp2_1.43.0-1+deb11u1.debian.tar.xz 5edbf6cbc4f246223e8e466a67a01156b75e7b38 11429 nghttp2_1.43.0-1+deb11u1_amd64.buildinfo Checksums-Sha256: 358a1e471de2d30bec289012577d91932f329b437ce5ee8d5c4b67b054b133d9 2555 nghttp2_1.43.0-1+deb11u1.dsc 556f24653397c71ebb8270b3c5e5507f0893e6eac2c6eeda6be2ecf6e1f50f62 4521786 nghttp2_1.43.0.orig.tar.bz2 b391becc0718fdc415d2f966d577a864f996068e828ce803600d34b0bf03baf2 21832 nghttp2_1.43.0-1+deb11u1.debian.tar.xz 47d7891604e6b501d3d74e8a90e3527c724636d1e8b7c2545ac4398543088d7c 11429 nghttp2_1.43.0-1+deb11u1_amd64.buildinfo Files: c93a49a2b30ae49bafaf5927a01fe86a 2555 httpd optional nghttp2_1.43.0-1+deb11u1.dsc d7d7d01fd9c5d30c2960ae4349e6b6b7 4521786 httpd optional nghttp2_1.43.0.orig.tar.bz2 0161fdba3fd82d13ae21ae43e8b42513 21832 httpd optional nghttp2_1.43.0-1+deb11u1.debian.tar.xz 8b36e5b205d0f8deda031e16406a1371 11429 httpd optional nghttp2_1.43.0-1+deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmVguK0ACgkQEMKTtsN8 Tjbx9hAAjjqEDCSyhJW0SMPYuNC0wEFkWFk5WjeROA5nk7/CrP9Kq6Xlhtawvbcc ovj00ny1FGR30UNwnn9uDr+DxpT5jOwlrEPYAVqYAlttRQpi+MvEBAoZp08L+Nl0 zVfz5OWsmVzz1WoZi1P0aF4U5ACEgUNMI+/CuwTwpq5ifETlsHMEeGHB0A7+UH5h KJ1fCKIZM6dvNhzH3rqf9AD3Ep+Fhyc+1pa51FnsXmhvz+Rajs7U7CtxXrz27eC1 yBXdtpPPamujAO0He/jyFu5qDLZ15b8SdVXb6ldOWO/S1EdGDn3VJ/bAC+1qCtZj oJfTJJjVVJYtpf9Uvpv9madi8wiHwMpzq9AMk0H/NV2SaWgvR+2lG0VQOYq0sUkL cikKkUQm9SgOnRWVhqttz4LmLedERSVpGPr+mhpSUOfxqoqI7wm+T5oJaloPYOnk 9+sKaDowY59aslPitwZyF4bl4xKwaeLRByp0qVKl0RttFb3EVMeVuTQXfXFcS67T fWrlyN8FwYZVA7i0Jp/XLahN9ZQoZatL8iY1fO9iDze+erU+TzxIPppuJ6rHn0Zx zHwui+v4aJA+6vi3oWoatHSWsO9mvshmF5ZNGPigxYVPISHiNoJPJEUs4cq4tg39 rmk8UGxMWEaan5SuqZC3zyAvchPq0NnQytoa+haT27u31exk4M4= =oIM3 -END PGP SIGNATURE End Message ---
Processed: 1058379 affects compyle
Processing commands for cont...@bugs.debian.org:
> affects 1058379 + src:compyle
Bug #1058379 [src:cython] compyle: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added indication that 1058379 affects src:compyle
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1056102: marked as done (gst-plugins-bad1.0: CVE-2023-44429: AV1 codec parser buffer overflow)
Your message dated Wed, 13 Dec 2023 07:02:34 + with message-id and subject line Bug#1056102: fixed in gst-plugins-bad1.0 1.18.4-3+deb11u3 has caused the Debian Bug report #1056102, regarding gst-plugins-bad1.0: CVE-2023-44429: AV1 codec parser buffer overflow 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.) -- 1056102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gst-plugins-bad1.0 Version: 1.22.4-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for gst-plugins-bad1.0. CVE-2023-44429[0]: | AV1 codec parser buffer overflow If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-44429 https://www.cve.org/CVERecord?id=CVE-2023-44429 [1] https://gstreamer.freedesktop.org/security/sa-2023-0009.html [2] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/b76a801f57353b893c344025cac56413140fca6d Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: gst-plugins-bad1.0 Source-Version: 1.18.4-3+deb11u3 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of gst-plugins-bad1.0, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated gst-plugins-bad1.0 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: Tue, 21 Nov 2023 20:33:07 +0100 Source: gst-plugins-bad1.0 Architecture: source Version: 1.18.4-3+deb11u3 Distribution: bullseye-security Urgency: high Maintainer: Maintainers of GStreamer packages Changed-By: Salvatore Bonaccorso Closes: 1056101 1056102 Changes: gst-plugins-bad1.0 (1.18.4-3+deb11u3) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * codecparsers: av1: Clip max tile rows and cols values (CVE-2023-44429) (Closes: #1056102) * mxfdemux: Store GstMXFDemuxEssenceTrack in their own fixed allocation (CVE-2023-6) (Closes: #1056101) Checksums-Sha1: 27641d9eaef46903952106896d14c2c32ba2a4e2 5791 gst-plugins-bad1.0_1.18.4-3+deb11u3.dsc 93f3bf57842d7fa3d5e369de34679cb4f284deb6 37308 gst-plugins-bad1.0_1.18.4-3+deb11u3.debian.tar.xz e3cc4da36ee77c610a95a85eee1d77c7d0002c47 7460 gst-plugins-bad1.0_1.18.4-3+deb11u3_source.buildinfo Checksums-Sha256: d0bdabaa255f65ef06e7fb737c179ae8e4e3003812c7d1af1710f025f63b02c8 5791 gst-plugins-bad1.0_1.18.4-3+deb11u3.dsc 013275e3ce4a6e31b6c50bfbaf81c937dc54fca20b9e652a87cc9bd965ad841d 37308 gst-plugins-bad1.0_1.18.4-3+deb11u3.debian.tar.xz a05ab4d280d4e0dde4962da9d35c5fcd6164deae4c436e6209a54dfbf0e73972 7460 gst-plugins-bad1.0_1.18.4-3+deb11u3_source.buildinfo Files: 81a0b66d6c429ea09ab7d26f4bc90532 5791 libs optional gst-plugins-bad1.0_1.18.4-3+deb11u3.dsc df84a4c357284ef44ecce9346e5ade0f 37308 libs optional gst-plugins-bad1.0_1.18.4-3+deb11u3.debian.tar.xz d5376c3c77c62dbe78e2261c46ba0be4 7460 libs optional gst-plugins-bad1.0_1.18.4-3+deb11u3_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmVdBiZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EfiAP/jVIBaFEllnmjap6N4xZ/HAXsmRy+FSw RUL9F+AyM+cZGKczxyagBM8raALmGW4JhO+jOf3f7ASaINtnhFXrKiBXcVP6Sjq0 D6ONa7qPew6pPALPTFfBVvLil+DN82rs8tog0RxiG0FawilwVnVvzImILVgHiBvW 8HUL4yJjdwzB4vgltb1HHsb5caSi1mdVBr3JD+KCO2aaUYx5pOJcLarVrWyrJo2W RjHvUixmvTNT44/0iYSCmxaE3hEhSoBHMg7YVOc5SZCqYcxc2dsPJQeqqhQxxnvC +rmKxOBOrxhgFE2AcYudgcWUD7EKFlZgDAb6JH8C6nP13+mIT2+4PjK9YRKn95Tc k9EARtGqwU/eXaFRVU5B6BYfjNRJYLm6dH23BmoC/XyhqlYY482dUAXal8EeUhz7 Gj1rv/wTIKLlwfw5TrHw3k/bcVzHb1hwYGBEJeWRvnKu8dAwJkdZgs3ToJZiILgU 3TvrJCTFdfYXYbdP2qctzFQCgq0nkwE5V5FJzesklyrGlToEZPM+F4
Bug#1056101: marked as done (gst-plugins-bad1.0: CVE-2023-44446: MXF demuxer use-after-free)
Your message dated Wed, 13 Dec 2023 07:02:34 + with message-id and subject line Bug#1056101: fixed in gst-plugins-bad1.0 1.18.4-3+deb11u3 has caused the Debian Bug report #1056101, regarding gst-plugins-bad1.0: CVE-2023-6: MXF demuxer use-after-free 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.) -- 1056101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gst-plugins-bad1.0 Version: 1.22.4-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for gst-plugins-bad1.0. CVE-2023-6[0]: | MXF demuxer use-after-free If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-6 https://www.cve.org/CVERecord?id=CVE-2023-6 [1] https://gstreamer.freedesktop.org/security/sa-2023-0010.html [2] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/5635 [3] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/7dfaa57b6f9b55f17ffe824bd8988bb71ae11353 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: gst-plugins-bad1.0 Source-Version: 1.18.4-3+deb11u3 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of gst-plugins-bad1.0, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated gst-plugins-bad1.0 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: Tue, 21 Nov 2023 20:33:07 +0100 Source: gst-plugins-bad1.0 Architecture: source Version: 1.18.4-3+deb11u3 Distribution: bullseye-security Urgency: high Maintainer: Maintainers of GStreamer packages Changed-By: Salvatore Bonaccorso Closes: 1056101 1056102 Changes: gst-plugins-bad1.0 (1.18.4-3+deb11u3) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * codecparsers: av1: Clip max tile rows and cols values (CVE-2023-44429) (Closes: #1056102) * mxfdemux: Store GstMXFDemuxEssenceTrack in their own fixed allocation (CVE-2023-6) (Closes: #1056101) Checksums-Sha1: 27641d9eaef46903952106896d14c2c32ba2a4e2 5791 gst-plugins-bad1.0_1.18.4-3+deb11u3.dsc 93f3bf57842d7fa3d5e369de34679cb4f284deb6 37308 gst-plugins-bad1.0_1.18.4-3+deb11u3.debian.tar.xz e3cc4da36ee77c610a95a85eee1d77c7d0002c47 7460 gst-plugins-bad1.0_1.18.4-3+deb11u3_source.buildinfo Checksums-Sha256: d0bdabaa255f65ef06e7fb737c179ae8e4e3003812c7d1af1710f025f63b02c8 5791 gst-plugins-bad1.0_1.18.4-3+deb11u3.dsc 013275e3ce4a6e31b6c50bfbaf81c937dc54fca20b9e652a87cc9bd965ad841d 37308 gst-plugins-bad1.0_1.18.4-3+deb11u3.debian.tar.xz a05ab4d280d4e0dde4962da9d35c5fcd6164deae4c436e6209a54dfbf0e73972 7460 gst-plugins-bad1.0_1.18.4-3+deb11u3_source.buildinfo Files: 81a0b66d6c429ea09ab7d26f4bc90532 5791 libs optional gst-plugins-bad1.0_1.18.4-3+deb11u3.dsc df84a4c357284ef44ecce9346e5ade0f 37308 libs optional gst-plugins-bad1.0_1.18.4-3+deb11u3.debian.tar.xz d5376c3c77c62dbe78e2261c46ba0be4 7460 libs optional gst-plugins-bad1.0_1.18.4-3+deb11u3_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmVdBiZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EfiAP/jVIBaFEllnmjap6N4xZ/HAXsmRy+FSw RUL9F+AyM+cZGKczxyagBM8raALmGW4JhO+jOf3f7ASaINtnhFXrKiBXcVP6Sjq0 D6ONa7qPew6pPALPTFfBVvLil+DN82rs8tog0RxiG0FawilwVnVvzImILVgHiBvW 8HUL4yJjdwzB4vgltb1HHsb5caSi1mdVBr3JD+KCO2aaUYx5pOJcLarVrWyrJo2W RjHvUixmvTNT44/0iYSCmxaE3hEhSoBHMg7YVOc5SZCqYcxc2dsPJQeqqhQxxnvC +rmKxOBOrxhgFE2AcYudgcWUD7EKFlZgDAb6JH8C6nP13+mIT2+4PjK9YRKn95Tc k9EARtGqwU/eXaFRVU5B6BYfjNRJYLm6dH23BmoC/XyhqlYY482dUAXal8EeUhz7 Gj1rv/wTIKLlwfw5TrHw3k/bcVzHb1hwYGBEJeWRvnKu8dAwJkdZgs
Bug#1055984: marked as done (gimp: CVE-2023-44441 CVE-2023-44442 CVE-2023-44443 CVE-2023-44444)
Your message dated Wed, 13 Dec 2023 07:02:25 + with message-id and subject line Bug#1055984: fixed in gimp 2.10.22-4+deb11u1 has caused the Debian Bug report #1055984, regarding gimp: CVE-2023-1 CVE-2023-2 CVE-2023-3 CVE-2023-4 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.) -- 1055984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gimp Version: 2.10.34-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for gimp. CVE-2023-1[0]: | GIMP DDS File Parsing Heap-based Buffer Overflow Remote Code Execution | Vulnerability CVE-2023-2[1]: | GIMP PSD File Parsing Heap-based Buffer Overflow Remote Code Execution | Vulnerability CVE-2023-3[2]: | GIMP PSP File Parsing Integer Overflow Remote Code Execution | Vulnerability CVE-2023-4[3]: | GIMP PSP File Parsing Off-By-One Remote Code Execution Vulnerability If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-1 https://www.cve.org/CVERecord?id=CVE-2023-1 [1] https://security-tracker.debian.org/tracker/CVE-2023-2 https://www.cve.org/CVERecord?id=CVE-2023-2 [2] https://security-tracker.debian.org/tracker/CVE-2023-3 https://www.cve.org/CVERecord?id=CVE-2023-3 [3] https://security-tracker.debian.org/tracker/CVE-2023-4 https://www.cve.org/CVERecord?id=CVE-2023-4 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: gimp Source-Version: 2.10.22-4+deb11u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of gimp, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated gimp 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, 18 Nov 2023 20:41:31 +0100 Source: gimp Architecture: source Version: 2.10.22-4+deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Debian GNOME Maintainers Changed-By: Salvatore Bonaccorso Closes: 1055984 Changes: gimp (2.10.22-4+deb11u1) bullseye-security; urgency=high . * Non-maintainer upload by the Security Team. * plug-ins: Fix vulnerabilities in file-psp (CVE-2023-3, CVE-2023-4) (Closes: #1055984) * plug-ins: Fix vulnerability in file-psd (CVE-2023-2) (Closes: #1055984) * plug-ins: Fix DDS vulnerability (ZDI-CAN-22093) (CVE-2023-1) (Closes: #1055984) * plug-ins: Fix DDS import regression * plug-ins: Additional fixes for DDS Import Checksums-Sha1: 9ae076d0c9645d4f71be421bc290654d95e022e3 3625 gimp_2.10.22-4+deb11u1.dsc da1687341e846fef784485511809da2988cb8200 33152226 gimp_2.10.22.orig.tar.bz2 d65420556464d27d631819a19b5965535106bf7a 61372 gimp_2.10.22-4+deb11u1.debian.tar.xz af832d7784f482da70e69fcfef44bfbc8666385e 7236 gimp_2.10.22-4+deb11u1_source.buildinfo Checksums-Sha256: 3d96cf7688404d776d4f11cfe8de20ed369ca87ccf6a9d7b936c05ca9bcf76bb 3625 gimp_2.10.22-4+deb11u1.dsc 2db84b57f3778d80b3466d7c21a21d22e315c7b062de2883cbaaeda9a0f618bb 33152226 gimp_2.10.22.orig.tar.bz2 358fd6ced49f6c94196c81d915bd90a7e14ad57ea5a4511e97c73966f9912d56 61372 gimp_2.10.22-4+deb11u1.debian.tar.xz 1557eea87acef754aa887b292f30d6721b5d42455b0056d278998e6ebafdc750 7236 gimp_2.10.22-4+deb11u1_source.buildinfo Files: d36ec73563b488eb1d0dacf700a17133 3625 graphics optional gimp_2.10.22-4+deb11u1.dsc 9d559ba6f039da033754f1d62a91cc39 33152226 graphics optional gimp_2.10.22.orig.tar.bz2 dca8567128cc5dadfa1e7378e4c1adaa 61372 graphics optional gimp_2.10.22-4+deb11u1.debian.tar.xz 712d96870cc8a275661c9e0f57f35a1b 7236 graphics optional gimp_2.10.22-4+deb11u1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QF
Bug#1055962: marked as done (intel-microcode: CVE-2023-23583: INTEL-SA-00950)
Your message dated Wed, 13 Dec 2023 07:02:49 + with message-id and subject line Bug#1055962: fixed in intel-microcode 3.20231114.1~deb11u1 has caused the Debian Bug report #1055962, regarding intel-microcode: CVE-2023-23583: INTEL-SA-00950 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.) -- 1055962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: intel-microcode Version: 3.20230808.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.20230808.1~deb12u1 Control: found -1 3.20230808.1~deb11u1 Hi, The following vulnerability was published for intel-microcode. CVE-2023-23583[0]: | Sequence of processor instructions leads to unexpected behavior for | some Intel(R) Processors may allow an authenticated user to | potentially enable escalation of privilege and/or information | disclosure and/or denial of service via local access. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-23583 https://www.cve.org/CVERecord?id=CVE-2023-23583 [1] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00950.html Regards, Salvatore --- End Message --- --- Begin Message --- Source: intel-microcode Source-Version: 3.20231114.1~deb11u1 Done: Henrique de Moraes Holschuh We believe that the bug you reported is fixed in the latest version of intel-microcode, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Henrique de Moraes Holschuh (supplier of updated intel-microcode 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, 18 Nov 2023 16:47:51 -0300 Source: intel-microcode Architecture: source Version: 3.20231114.1~deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique de Moraes Holschuh Closes: 1055962 Changes: intel-microcode (3.20231114.1~deb11u1) bullseye-security; urgency=high . * Backport to Debian Bullseye * debian/control: revert non-free-firmware change . intel-microcode (3.20231114.1) unstable; urgency=medium . * New upstream microcode datafile 20231114 (closes: #1055962) Mitigations for "reptar", INTEL-SA-00950 (CVE-2023-23583) Sequence of processor instructions leads to unexpected behavior for some Intel(R) Processors, may allow an authenticated user to potentially enable escalation of privilege and/or information disclosure and/or denial of service via local access. Note: "reptar" on 4th gen Xeon Scalable (sig 0x806f8 pfm 0x87), 12th gen Core mobile (sig 0x906a4 pfm 0x80), 13th gen Core desktop (sig 0xb0671 pfm 0x01) were already mitigated by a previous microcode update. * Fixes for unspecified functional issues * Updated microcodes: sig 0x000606a6, pf_mask 0x87, 2023-09-01, rev 0xd0003b9, size 299008 sig 0x000606c1, pf_mask 0x10, 2023-09-08, rev 0x1000268, size 290816 sig 0x000706e5, pf_mask 0x80, 2023-09-03, rev 0x00c2, size 113664 sig 0x000806c1, pf_mask 0x80, 2023-09-07, rev 0x00b4, size 111616 sig 0x000806c2, pf_mask 0xc2, 2023-09-07, rev 0x0034, size 98304 sig 0x000806d1, pf_mask 0xc2, 2023-09-07, rev 0x004e, size 104448 sig 0x000806f8, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0, size 572416 sig 0x000806f8, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f7, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f6, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f5, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f4, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f8, pf_mask 0x10, 2023-06-26, rev 0x2c000290, size 605184 sig 0x000806f8, pf_mask 0x10, 2023-06-26, rev 0x2c000290 sig 0x000806f6, pf_mask 0x10, 2023-06-26, rev 0x2c000290 sig 0x000806f5, pf_mask 0x10, 2023-06-26, rev 0x2c000290 sig 0x0
Bug#1055566: marked as pending in mod-wsgi
Control: tag -1 pending Hello, Bug #1055566 in mod-wsgi 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/mod-wsgi/-/commit/8e1e89ad1d81447e63c5cdf2ffab69d14ce3f4fd Fix build with python 3.12 Closes: #1055566 (this message was generated automatically) -- Greetings https://bugs.debian.org/1055566
Processed: Bug#1055566 marked as pending in mod-wsgi
Processing control commands: > tag -1 pending Bug #1055566 [src:mod-wsgi] mod-wsgi ftbfs with Python 3.12 Added tag(s) pending. -- 1055566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassign 1058379
Processing commands for cont...@bugs.debian.org:
> reassign 1058379 src:cython
Bug #1058379 [src:compyle] compyle: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Bug reassigned from package 'src:compyle' to 'src:cython'.
No longer marked as found in versions compyle/0.8.1-5.
Ignoring request to alter fixed versions of bug #1058379 to the same values
previously set
> found 1058379 cython/0.29.36-3.1
Bug #1058379 [src:cython] compyle: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Marked as found in versions cython/0.29.36-3.1.
> affects + src:compyle
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058575: glogic: Fails to start due AttributeError
Package: glogic
Version: 2.6-6
Severity: serious
Dear Maintainer,
qlogic isn't usable any more in unstable and testing.
It fails to start as a calling of a Python function raises a
AttributeError.
$ glogic
/usr/lib/python3/dist-packages/glogic/MainFrame.py:4: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk',
'4.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, Gdk, GdkPixbuf
Traceback (most recent call last):
File "/usr/bin/glogic", line 20, in
from glogic.MainFrame import MainFrame
File "/usr/lib/python3/dist-packages/glogic/MainFrame.py", line 18, in
themed_icons = Gtk.IconTheme.get_default()
^
AttributeError: type object 'IconTheme' has no attribute 'get_default'
Rgards
Carsten
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages glogic depends on:
ii gir1.2-gtk-3.03.24.38-6
ii python3 3.11.4-5+b1
ii python3-gi3.46.0-1+b1
ii python3-gi-cairo 3.46.0-1+b1
glogic recommends no packages.
Versions of packages glogic suggests:
ii fonts-liberation 1:2.1.5-3
-- no debconf information
Bug#1057165: libitext-java: FTBFS with bouncycastle 1.77
On Thu, Nov 30, 2023 at 10:47:18PM +0100, Markus Koschany wrote: > Source: libitext-java > Version: 2.1.7-14 > Severity: serious > Tags: ftbfs sid > User: a...@debian.org > Usertags: bouncycastle-1.77 > X-Debbugs-Cc: a...@debian.org > > Dear maintainer, > > libitext-java fails to build from source with bouncycastle 1.77. The reason > is the removal of long deprecated methods. The (hopefully) relevant > error message from the build log. I have added a patch to address the FTBFS. Unfortunately, this package doesn't run tests and getting them working is going to take some effort. The patch is straight-forward. It eliminates usage of a few long-deprecated classes in favor of their replacements, or uses some factory-like methods to instantiate objects. However, it would be nice to have at least some sort of runtime checks before uploading, which may take me a few days. I have pushed the changes to the repo if anyone is ready to move ahead with an upload. If not, I will try to upload by early next week. Thanks, tony signature.asc Description: PGP signature
Bug#1057165: marked as pending in libitext-java
Control: tag -1 pending Hello, Bug #1057165 in libitext-java 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/java-team/libitext-java/-/commit/82e6f29bde6ce5dc5393b4161a9496e2ce7ddda6 Add patch for BouncyCastle 1.77 (Closes: #1057165) (this message was generated automatically) -- Greetings https://bugs.debian.org/1057165
Processed: Bug#1057165 marked as pending in libitext-java
Processing control commands: > tag -1 pending Bug #1057165 [src:libitext-java] libitext-java: FTBFS with bouncycastle 1.77 Bug #1058346 [src:libitext-java] libitext-java: FTBFS: [javac] /<>/core/com/lowagie/text/pdf/PdfPKCS7.java:88: error: cannot find symbol Added tag(s) pending. Added tag(s) pending. -- 1057165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057165 1058346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1058515
Processing commands for cont...@bugs.debian.org: > close 1058515 Bug #1058515 [src:node-rollup] node-rollup: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1058515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1058523
Processing commands for cont...@bugs.debian.org: > close 1058523 Bug #1058523 [src:node-babel7] node-babel7: FTBFS: ln: failed to create symbolic link 'node_modules/@babel/helper-string-parser/babel-helper-string-parser': Permission denied Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1058523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057843: (no subject)
If it helps people, this is what I did on systems that automatically had rebooted into the problematic kernel. First, I uninstalled the 6.1.0-14 kernel and rebooted back into 6.1.0-13. Then I used `last` to identify the time between the problematic reboot into 6.1.0-14 and the deliberate reboot (back in to 6.1.0-13) This showed me that the 'problem time' was between 2023-12-10 06:00:00 and 2023-12-10 19:00:00 (UTC). >From there, I ran the followin gcommand to show me all files that were >modified more or less between that time. I ignore a bunch of things I don't >care about such as /var/log and other volatile parts of the filesystem. find / -type f -newermt "2023-12-10 05:59:00" \! -newermt "2023-12-10 19:00:00" | egrep -v "/proc|/run|/sys|/var/log" At least this gave me a somewhat small subset of files to manually check, which made it feel less daunting. Naturally it depends on your filesystem what files might've changed. I was fortunate that none of the client applications I use, seem to use O_DIRECT, so I found no corrupted files (so far). Note that use of O_DIRECT is not a system-wide setting (e.g not one in /etc/fstab for the ext4 filesystem), it's something that each application can choose to use when working with files. For example, I have changed MySQL's innodb_flush_method to be O_DIRECT in the past (for performance), but it's not the default. Out of the box, things like postgresql use fsync (not direct IO) by default. I used some tools like 'git fsck' in git repositories that had changed during my 'problematic' time, and there were no issues - hopefully git does not use O_DIRECT. I have not been able to find any definitive list of programs that use O_DIRECT out-of-the box. Maybe someone else will come up with such a list (if there even *are* programs that do so). As others have said here, things like fsck won't likely help you, unfortunately. The nature of the bug is not one that corrupts the journaling/filesystem structure, it is more about the *contents* of the file, which fsck can't comment on. Finally, I wanted to note: if you did `apt purge linux-image-6.1.0-14-amd64`, you might need to `apt install linux-image-amd64` (the meta package) before you can successfully pick up the new linux-image-6.1.0-15-amd64 automatically as a dependency (say, when doing apt update; apt dist-upgrade). At least, I needed to, as I think the purge automatically removed the meta package, leaving me with no *automatic* upgrade to the new kernel via those commands. Good luck!
Bug#1058535: libhinawa: FTBFS: make: *** [debian/rules:8: binary] Error 25
On Tue, 12 Dec 2023 21:51:47 +0100
Lucas Nussbaum wrote:
> Source: libhinawa
> Version: 4.0.0-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231212 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
snip
[15/15] /usr/bin/gi-docgen generate --no-namespace-dir
--config=doc/hinawa.toml --output-dir=doc/hinawa
--content-dir=/<>/doc src/Hinawa-4.0.gir
> FAILED: doc/hinawa
> /usr/bin/gi-docgen generate --no-namespace-dir
> --config=doc/hinawa.toml --output-dir=doc/hinawa
> --content-dir=/<>/doc src/Hinawa-4.0.gir WARNING:
> Section domains raised Invalid version: '2.5.' INFO: Loading config
> file: doc/hinawa.toml
It need a patch somthing like:
+diff --git a/src/hinawa_enum_types.h b/src/hinawa_enum_types.h
+index 1687046..a1c1ebf 100644
+--- a/src/hinawa_enum_types.h
b/src/hinawa_enum_types.h
+@@ -98,7 +98,7 @@ typedef enum {
+ * A set of error code for [struct@GLib.Error] for operations in
[class@FwReq].
+ * The actual value is equivalent to [enum@FwRcode].
+ *
+- * Since: 2.5.
++ * Since: 2.5
+ */
+ typedef enum {
+ HINAWA_FW_REQ_ERROR_CONFLICT_ERROR =
HINAWA_FW_RCODE_CONFLICT_ERROR,
Processed: notfixed 1052974 in gap-polymaking/0.8.7-1
Processing commands for cont...@bugs.debian.org:
> notfixed 1052974 gap-polymaking/0.8.7-1
Bug #1052974 {Done: Joachim Zobel } [src:gap-hapcryst]
gap-hapcryst: FTBFS: polymake: ERROR:
"/usr/share/polymake/perllib/Polymake/Core/CPlusPlus.pm", line 1785: Can't load
shared module /usr/lib/polymake/lib/ideal.so: libsingular-Singular-4.3.1.so:
cannot open shared object file: No such file or directory
No longer marked as fixed in versions gap-polymaking/0.8.7-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058537: marked as done (node-node-pty: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1)
Your message dated Wed, 13 Dec 2023 04:34:15 + with message-id and subject line Bug#1058537: fixed in node-node-pty 1.0.0+ds1+~6.3.0-1 has caused the Debian Bug report #1058537, regarding node-node-pty: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1058537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-node-pty Version: 1.0.0+~6.3.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/@types/mocha -> /usr/share/nodejs/@types/mocha > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Link node_modules/ps-list -> ../ps-list >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > tsc -b ./src/tsconfig.json > src/windowsPtyAgent.ts(243,20): error TS2345: Argument of type 'Timer' is not > assignable to parameter of type 'string | number | Timeout | undefined'. > Property '[Symbol.dispose]' is missing in type 'Timer' but required in type > 'Timeout'. > make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/node-node-pty_1.0.0+~6.3.0-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: node-node-pty Source-Version: 1.0.0+ds1+~6.3.0-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-node-pty, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-node-pty package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Dec 2023 06:43:33 +0400 Source: node-node-pty Architecture: source Version: 1.0.0+ds1+~6.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1058537 Changes: node-node-pty (1.0.0+ds1+~6.3.0-1) unstable; urgency=medium . * Exclude ps-list/fastlist.exe from import and repack * Update tsc patch (Closes: #1058537) Checksums-Sha1: 45fd48b7a1350dc0181170764986e2b9cdb36841 2479 node-node-pty_1.0.0+ds1+~6.3.0-1.dsc c6ccb631fb3f03d2cbbbeda2d451cf1abf9e27e3 3436 node-node-pty_1.0.0+ds1+~6.3.0.orig-ps-list.tar.gz 2e461fd5fa31cd0e5935ae744b449fc359c8f06e 266471 node-node-pty_1.0.0+ds1+~6.3.0.orig.tar.gz af9e6876a177df18175e5542fcca53aec7f2e5fd 4400 node-node-pty_1.0.0+ds1+~6.3.0-1.debian.tar.xz Checksums-Sha256: 2cf9c0eddc990631f845ac074942e45358b467166ddcb24feb58ffe8098d0011 2479 node-node-pty_1.0.0+ds1+~6.3.0-1.dsc 411dcf73548a69031972828729b230e4f2849f2a93c89e474125747756927c54 3436 node-node-pty_1.0.0+ds1+~6.3.0.orig-ps-list.tar.gz 96e6a71b83a6984d97f86f07313a52580ce7529204784558b5a4ca8cde6b62
Bug#1058542: marked as done (node-ytdl-core: FTBFS: make: *** [debian/rules:8: binary] Error 25)
Your message dated Wed, 13 Dec 2023 04:34:58 + with message-id and subject line Bug#1058542: fixed in node-ytdl-core 4.11.2+dfsg+~cs4.10.8-2 has caused the Debian Bug report #1058542, regarding node-ytdl-core: FTBFS: make: *** [debian/rules:8: binary] Error 25 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.) -- 1058542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-ytdl-core Version: 4.11.2+dfsg+~cs4.10.8-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Link ./node_modules/@types/sax -> /usr/share/nodejs/@types/sax > Link node_modules/m3u8stream -> ../m3u8stream > Link node_modules/miniget -> ../miniget > Link m3u8stream/node_modules/miniget -> ../../miniget >dh_auto_build --buildsystem=nodejs > Found debian/nodejs/miniget/build > cd ./miniget && sh -ex ../debian/nodejs/miniget/build > + tsc -p tsconfig.build.json > src/index.ts(310,18): error TS2769: No overload matches this call. > Overload 1 of 2, '(timeoutId: string | number | Timeout | undefined): > void', gave the following error. > Argument of type 'Timer' is not assignable to parameter of type 'string | > number | Timeout | undefined'. > Property '[Symbol.dispose]' is missing in type 'Timer' but required in > type 'Timeout'. > Overload 2 of 2, '(id: number | undefined): void', gave the following error. > Argument of type 'Timer' is not assignable to parameter of type 'number'. > dh_auto_build: error: cd ./miniget && sh -ex ../debian/nodejs/miniget/build > returned exit code 2 > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/node-ytdl-core_4.11.2+dfsg+~cs4.10.8-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: node-ytdl-core Source-Version: 4.11.2+dfsg+~cs4.10.8-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-ytdl-core, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-ytdl-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Dec 2023 06:23:57 +0400 Source: node-ytdl-core Architecture: source Version: 4.11.2+dfsg+~cs4.10.8-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1058542 Changes: node-ytdl-core (4.11.2+dfsg+~cs4.10.8-2) unstable; urgency=medium . * Team upload * Update lintian override info format in d/source/lintian-overrides on line 2 * Update standards version to 4.6.2, no changes needed * Add
Bug#1058541: marked as done (node-redis: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2)
Your message dated Wed, 13 Dec 2023 04:34:30 + with message-id and subject line Bug#1058541: fixed in node-redis 4.5.1+~1.1.2-2 has caused the Debian Bug report #1058541, regarding node-redis: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1058541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-redis Version: 4.5.1+~1.1.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd packages/client && tsc > lib/client/index.ts(359,22): error TS2345: Argument of type 'Timer | > undefined' is not assignable to parameter of type 'string | number | Timeout > | undefined'. > Type 'Timer' is not assignable to type 'string | number | Timeout | > undefined'. > Property '[Symbol.dispose]' is missing in type 'Timer' but required in > type 'Timeout'. > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/12/12/node-redis_4.5.1+~1.1.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: node-redis Source-Version: 4.5.1+~1.1.2-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-redis, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-redis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Dec 2023 06:36:11 +0400 Source: node-redis Architecture: source Version: 4.5.1+~1.1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1058541 Changes: node-redis (4.5.1+~1.1.2-2) unstable; urgency=medium . * Set upstream metadata fields: Bug-Database, Repository-Browse * Update standards version to 4.6.2, no changes needed * Update tsc patch (Closes: #1058541) Checksums-Sha1: 4d38f72a1ea958ee6e31dc589076c8302ffe568f 2464 node-redis_4.5.1+~1.1.2-2.dsc 4ba617fc94a604225f71fde9e74eff342591f70a 6276 node-redis_4.5.1+~1.1.2-2.debian.tar.xz Checksums-Sha256: 177be2998c665687b19b4801623c0bc82362b038be0db0969a87c0057fda653e 2464 node-redis_4.5.1+~1.1.2-2.dsc cece38cb7b489ceb9c6133ef2161051e2b5a4a0d12cfd72d399a603ff1abbafa 6276 node-redis_4.5.1+~1.1.2-2.debian.tar.xz Files: 0010aa63030eda8cbab606b6f871abb3 2464 javascript optional node-redis_4.5.1+~1.1.2-2.dsc df28810d53f97f37d5a65210ebd100d7 6276 javascript optional node-redis_4.5.1+~1.1.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmV5L/UACgkQ9tdMp8mZ 7umUPw//QnqL3YqJho+O7LihP6fFFJS6JnvC/HK6rSQ6aQZksYlbJ+pL8ACwUdE4 4UlAm6Ioe+Jwy26FmHlbGK+MtxUnMzq8ejAgbPitPGjyP28d3N8R/HkzJgQChStB KRKr9bLRLRm1HnJIk/tc7ZRRLQheB30Tz/kNiU7FgTS4v+wi06OmnJUiHilLB99Y qUbX4g9rHSllFdD/1jUFC
Bug#1058534: marked as done (node-rollup-plugin-node-polyfills: FTBFS: make: *** [debian/rules:8: binary] Error 25)
Your message dated Wed, 13 Dec 2023 04:34:48 + with message-id and subject line Bug#1058534: fixed in node-rollup-plugin-node-polyfills 0.2.1+dfsg+~0.11.0-2 has caused the Debian Bug report #1058534, regarding node-rollup-plugin-node-polyfills: FTBFS: make: *** [debian/rules:8: binary] Error 25 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.) -- 1058534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-rollup-plugin-node-polyfills Version: 0.2.1+dfsg+~0.11.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/concat-stream -> /usr/share/nodejs/concat-stream > Link ./node_modules/core-util-is -> /usr/share/nodejs/core-util-is > Link ./node_modules/crypto-browserify -> /usr/share/nodejs/crypto-browserify > Link ./node_modules/errno -> /usr/share/nodejs/errno > Link ./node_modules/immediate -> /usr/share/nodejs/immediate > Link ./node_modules/inherits -> /usr/share/nodejs/inherits > Link ./node_modules/isarray -> /usr/share/nodejs/isarray > Link ./node_modules/@rollup/plugin-inject -> > /usr/share/nodejs/@rollup/plugin-inject > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Link ./node_modules/xtend -> /usr/share/nodejs/xtend > Link node_modules/rollup-plugin-polyfill-node -> > ../rollup-plugin-polyfill-node > Link node_modules/abstract-leveldown -> > ../debian/build_modules/abstract-leveldown > Link node_modules/browserify-fs -> ../debian/build_modules/browserify-fs > Link node_modules/buffer-es6 -> ../debian/build_modules/buffer-es6 > Link node_modules/deferred-leveldown -> > ../debian/build_modules/deferred-leveldown > Link node_modules/fwd-stream -> ../debian/build_modules/fwd-stream > Link node_modules/level-blobs -> ../debian/build_modules/level-blobs > Link node_modules/level-errors -> ../debian/build_modules/level-errors > Link node_modules/level-filesystem -> ../debian/build_modules/level-filesystem > Link node_modules/level-iterator-stream -> > ../debian/build_modules/level-iterator-stream > Link node_modules/level-js -> ../debian/build_modules/level-js > Link node_modules/level-peek -> ../debian/build_modules/level-peek > Link node_modules/level-post -> ../debian/build_modules/level-post > Link node_modules/level-sublevel -> ../debian/build_modules/level-sublevel > Link node_modules/level-supports -> ../debian/build_modules/level-supports > Link node_modules/levelup -> ../debian/build_modules/levelup > Link node_modules/looper -> ../debian/build_modules/looper > Link node_modules/ltgt -> ../debian/build_modules/ltgt > Link node_modules/octal -> ../debian/build_modules/octal > Link node_modules/process-es6 -> ../debian/build_modules/process-es6 > Link node_modules/pull-cat -> ../debian/build_modules/pull-cat > Link node_modules/pull-level -> ../debian/build_modules/pull-level > Link node_modules/pull-live -> ../debian/build_modules/pull-live > Link node_modules/pull-pushable -> ../debian/build_modules/pull-pushable > Link node_modules/pull-stream -> ../debian/build_modules/pull-stream > Link node_modules/pull-window -> ../debian/build_modules/pull-window > Link node_modules/safer-buffer -> ../debian/build_modules/safer-buffer > Link node_modules/stream-to-pull-stream -> > ../debian/build_modules/stream-to-pull-stream >dh_auto_build --buildsystem=nodejs > Found debian/nodejs/rollup-plugin-polyfill-node/build > cd ./rollup-plugin-polyfill-node && sh -ex > ../debian/nodejs/rollup-plugin-polyfill-node/build > + node scripts/build-constants.js > + node scripts/build-polyfills.js > + node scripts/collect-polyfills.js > + tsc -p . > + rollup -c > [36m > [1mlib/index.js[22m → [1mdist/es, dist/[22m...[39m > [32mcreated [1mdist/es, dist/[22m in [1m252ms[22m[39m > + rollup lib/index.js -f cjs -o dist/index.js > [36m > [1mlib/index.js[22m → [1mdist/index.js[22m...[39m > [1m[33m(!) Unresolved dependencies[39m
Bug#1058518: marked as done (node-es-module-lexer: FTBFS: make[1]: *** [debian/rules:11: src/lexer.js] Error 2)
Your message dated Wed, 13 Dec 2023 04:34:04 + with message-id and subject line Bug#1058518: fixed in node-es-module-lexer 1.1.0+dfsg-3 has caused the Debian Bug report #1058518, regarding node-es-module-lexer: FTBFS: make[1]: *** [debian/rules:11: src/lexer.js] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1058518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-es-module-lexer Version: 1.1.0+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > tsc -m es2015 src/lexer.ts > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(325,84): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(326,85): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(327,85): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(328,84): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(330,22): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(336,35): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(337,35): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(338,32): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(339,39): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(340,42): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(341,35): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(342,38): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(343,34): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution' option to 'node', or to add aliases to the 'paths' option? > ../../../usr/share/nodejs/@types/node/ts4.8/globals.d.ts(344,37): error > TS2792: Cannot find module 'undici-types'. Did you mean to set the > 'moduleResolution&#x
Bug#1058507: marked as done (node-regexpp: FTBFS: make[1]: *** [debian/rules:30: override_dh_auto_build] Error 1)
Your message dated Wed, 13 Dec 2023 04:34:37 +
with message-id
and subject line Bug#1058507: fixed in node-regexpp 3.2.0-5
has caused the Debian Bug report #1058507,
regarding node-regexpp: FTBFS: make[1]: *** [debian/rules:30:
override_dh_auto_build] Error 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-regexpp
Version: 3.2.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cmark-gfm README.md > README.html
> cmark-gfm --to plaintext README.md > README.txt
> tsc --module es2015
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m325[0m:[93m84[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m325[0m type _Request = typeof globalThis extends { onmessage:
> any } ? {} : import("undici-types").Request;
> [7m [0m [91m
> ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m326[0m:[93m85[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m326[0m type _Response = typeof globalThis extends { onmessage:
> any } ? {} : import("undici-types").Response;
> [7m [0m [91m
>~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m327[0m:[93m85[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m327[0m type _FormData = typeof globalThis extends { onmessage:
> any } ? {} : import("undici-types").FormData;
> [7m [0m [91m
>~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m328[0m:[93m84[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m328[0m type _Headers = typeof globalThis extends { onmessage:
> any } ? {} : import("undici-types").Headers;
> [7m [0m [91m
> ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m330[0m:[93m22[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m330[0m : import("undici-types").RequestInit;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m336[0m:[93m35[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m336[0m type RequestInfo = import("undici-types").RequestInfo;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m337[0m:[93m35[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m337[0m type HeadersInit = import("undici-types").HeadersInit;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m338[0m:[93m32[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or its
> corresponding type declarations.
>
> [7m338[0m type BodyInit = import("undici-types").BodyInit;
> [7m [0m [91m ~~[0m
>
> [96mnode_modules/@types/node/ts4.8/globals.d.ts[0m:[93m339[0m:[93m39[0m
> - [91merror[0m[90m TS2307: [0mCannot find module 'undici-types' or
Processed: fixed 1052974 in gap-hapcryst/0.1.15-3
Processing commands for cont...@bugs.debian.org:
> fixed 1052974 gap-hapcryst/0.1.15-3
Bug #1052974 {Done: Joachim Zobel } [src:gap-hapcryst]
gap-hapcryst: FTBFS: polymake: ERROR:
"/usr/share/polymake/perllib/Polymake/Core/CPlusPlus.pm", line 1785: Can't load
shared module /usr/lib/polymake/lib/ideal.so: libsingular-Singular-4.3.1.so:
cannot open shared object file: No such file or directory
Marked as fixed in versions gap-hapcryst/0.1.15-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042625: marked as done (pympress: FTBFS with Sphinx 7.1, docutils 0.20: PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent')
Your message dated Wed, 13 Dec 2023 04:04:55 + with message-id and subject line Bug#1042625: fixed in pympress 1.8.4-1 has caused the Debian Bug report #1042625, regarding pympress: FTBFS with Sphinx 7.1, docutils 0.20: PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent' 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.) -- 1042625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pympress Version: 1.7.1-3 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, pympress fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:240: /usr/bin/python3 setup.py build > Using setuptools.setup(): > running build > running build_py > running compile_catalog > 151 of 255 messages (59%) translated in > pympress/share/locale/pl/LC_MESSAGES/pympress.po > compiling catalog pympress/share/locale/pl/LC_MESSAGES/pympress.po to > pympress/share/locale/pl/LC_MESSAGES/pympress.mo > 195 of 255 messages (76%) translated in > pympress/share/locale/es/LC_MESSAGES/pympress.po > compiling catalog pympress/share/locale/es/LC_MESSAGES/pympress.po to > pympress/share/locale/es/LC_MESSAGES/pympress.mo > 251 of 255 messages (98%) translated in > pympress/share/locale/fr/LC_MESSAGES/pympress.po > compiling catalog pympress/share/locale/fr/LC_MESSAGES/pympress.po to > pympress/share/locale/fr/LC_MESSAGES/pympress.mo > 166 of 255 messages (65%) translated in > pympress/share/locale/de/LC_MESSAGES/pympress.po > compiling catalog pympress/share/locale/de/LC_MESSAGES/pympress.po to > pympress/share/locale/de/LC_MESSAGES/pympress.mo > 197 of 255 messages (77%) translated in > pympress/share/locale/cs/LC_MESSAGES/pympress.po > compiling catalog pympress/share/locale/cs/LC_MESSAGES/pympress.po to > pympress/share/locale/cs/LC_MESSAGES/pympress.mo > creating /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/app.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/document.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/dialog.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/builder.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/ui.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/__main__.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/__init__.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/pointer.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/surfacecache.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/editable_label.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/util.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/config.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/extras.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/talk_time.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > copying pympress/scribble.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress > creating > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/media_overlays > copying pympress/media_overlays/base.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/media_overlays > copying pympress/media_overlays/__init__.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/media_overlays > copying pympress/media_overlays/vlc_backend.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/media_overlays > copying pympress/media_overlays/gif_backend.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/media_overlays > copying pympress/media_overlays/gst_backend.py -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/media_overlays > creating /<>/.pybuild/cpython3_3.11_pympress/build/pympress/share > copying pympress/share/defaults.conf -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/share > creating > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/share/xml > copying pympress/share/xml/shortcuts.glade -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/share/xml > copying pympress/share/xml/layout_dialog.glade -> > /<>/.pybuild/cpython3_3.11_pympress/build/pympress/share/xml > copying pympress/shar
Bug#1058144: marked as done (libiio: FTBFS: make[1]: *** [debian/rules:31: override_dh_auto_install] Error 1)
Your message dated Wed, 13 Dec 2023 03:35:02 + with message-id and subject line Bug#1058144: fixed in libiio 0.25-4 has caused the Debian Bug report #1058144, regarding libiio: FTBFS: make[1]: *** [debian/rules:31: override_dh_auto_install] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1058144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libiio Version: 0.25-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/build' > make[3]: Nothing to be done for 'preinstall'. > make[3]: Leaving directory '/<>/build' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/libiio.pc > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libiio.so.0.25 > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libiio.so.0 > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libiio.so > -- Installing: /<>/debian/tmp/usr/include/iio.h > -- Installing: /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25 > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/genindex.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/search.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/forkme_right_darkblue_121621.png > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/searchtools.js > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/language_data.js > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/plus.png > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/alabaster.css > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/basic.css > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/minus.png > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/sphinx_highlight.js > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/file.png > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/doctools.js > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/documentation_options.js > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/custom.css > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_static/pygments.css > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/.nojekyll > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/.buildinfo > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/index.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/iio_readdev.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/iio_info.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/examples.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/trigger.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/searchindex.js > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/iio_attr.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/device.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/iio_writedev.html > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_sources > -- Installing: > /<>/debian/tmp/usr/share/doc/libiio0-doc/v0.25/python/_sources/examples.rst.txt &
Processed: tagging 1058547
Processing commands for cont...@bugs.debian.org: > tags 1058547 - pending Bug #1058547 [src:node-globby] node-globby: FTBFS: make: *** [debian/rules:8: binary] Error 25 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058547: marked as pending in node-globby
Control: tag -1 pending Hello, Bug #1058547 in node-globby reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-globby/-/commit/579c4942c926587b6c703f20ed7382bb713b89a0 Fix build links Closes: #1058547 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058547
Processed: Bug#1058547 marked as pending in node-globby
Processing control commands: > tag -1 pending Bug #1058547 [src:node-globby] node-globby: FTBFS: make: *** [debian/rules:8: binary] Error 25 Added tag(s) pending. -- 1058547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058529: marked as pending in node-csstype
Control: tag -1 pending Hello, Bug #1058529 in node-csstype reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-csstype/-/commit/9a6c0a75f3ea271fe7c40a5cafd17ffd2691451d Add tsc patch CLoses: #1058529 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058529
Processed: Bug#1058529 marked as pending in node-csstype
Processing control commands: > tag -1 pending Bug #1058529 [src:node-csstype] node-csstype: FTBFS: make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1058529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1058507 marked as pending in node-regexpp
Processing control commands: > tag -1 pending Bug #1058507 [src:node-regexpp] node-regexpp: FTBFS: make[1]: *** [debian/rules:30: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1058507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058507: marked as pending in node-regexpp
Control: tag -1 pending Hello, Bug #1058507 in node-regexpp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-regexpp/-/commit/7f74a551ad90394228e9058780011c90e05d05e4 Add missing link to undici-types Closes: #1058507 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058507
Processed: Bug#1058518 marked as pending in node-es-module-lexer
Processing control commands: > tag -1 pending Bug #1058518 [src:node-es-module-lexer] node-es-module-lexer: FTBFS: make[1]: *** [debian/rules:11: src/lexer.js] Error 2 Added tag(s) pending. -- 1058518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058518: marked as pending in node-es-module-lexer
Control: tag -1 pending Hello, Bug #1058518 in node-es-module-lexer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-es-module-lexer/-/commit/e99127d3937586b5b43bf2f63df44f83e99806c2 Update build command Closes: #1058518 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058518
Processed: Bug#1058537 marked as pending in node-node-pty
Processing control commands: > tag -1 pending Bug #1058537 [src:node-node-pty] node-node-pty: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1058537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058537: marked as pending in node-node-pty
Control: tag -1 pending Hello, Bug #1058537 in node-node-pty reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-node-pty/-/commit/4ad978b488ae4201ecc1746332cf261df35144a9 Update tsc patch Closes: #1058537 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058537
Processed: Bug#1058541 marked as pending in node-redis
Processing control commands: > tag -1 pending Bug #1058541 [src:node-redis] node-redis: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 Added tag(s) pending. -- 1058541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058541: marked as pending in node-redis
Control: tag -1 pending Hello, Bug #1058541 in node-redis reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-redis/-/commit/95175b798368daf1c57690a4d3ceacc53de6abcd Update tsc patch Closes: #1058541 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058541
Bug#1054823: starlette: FTBFS: tests failed
The build failure is due to the library python3-httpx. This library uses python3-rfc3986, it's been upgraded lately [1], and it's now causing the breakage. There's a discussion about this issue upstream [2]. If we bump src:httpx to version 0.24.0, the dependency on python3-rfc3986 goes away, and the problem will be fixed. Looking at src:httpx now: Debian has 0.23.3-1, we need at least 0.24, and upstream is at 0.25.2. $ build-rdeps python3-httpx Reverse Build-depends in main: -- aioxmlrpc asgi-csrf asgi-lifespan dnspython fastapi greenbone-feed-sync nala ormar pontos python-a2wsgi python-authlib python-cobra python-duckpy python-falcon python-gvm python-tiny-proxy python-truststore python-uvicorn sqlmodel starlette Since I'm not involved in Python packaging, I don't feel comfortable doing this upgrade. Best, Arnaud [1]: https://tracker.debian.org/pkg/python-rfc3986 [2]: https://github.com/encode/starlette/discussions/1879 On Fri, 27 Oct 2023 21:48:44 +0200 Lucas Nussbaum wrote: > Source: starlette > Version: 0.31.1-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231027 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > debian/rules build > > dh build --with python3 --buildsystem=pybuild > > dh_update_autotools_config -O--buildsystem=pybuild > > dh_autoreconf -O--buildsystem=pybuild > > dh_auto_configure -O--buildsystem=pybuild > > dh_auto_build -O--buildsystem=pybuild > > I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" module > > I: pybuild base:310: python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11_starlette > > * Building wheel... > > Successfully built starlette-0.31.1-py3-none-any.whl > > I: pybuild plugin_pyproject:122: Unpacking wheel built for python3.11 with "installer" module > > dh_auto_test -O--buildsystem=pybuild > > I: pybuild base:310: cd /<>/.pybuild/cpython3_3.11_starlette/build; python3.11 -m pytest tests > > = test session starts == > > platform linux -- Python 3.11.6, pytest-7.4.3, pluggy-1.3.0 > > rootdir: /<>/.pybuild/cpython3_3.11_starlette/build > > configfile: pyproject.toml > > plugins: anyio-3.7.0 > > collected 420 items > > > > tests/test__utils.py .. [ 1%] > > tests/test_applications.py .FF.FFF..F.FFF..F. [ 7%] > > tests/test_authentication.py .FF.FF [ 9%] > > tests/test_background.py [ 10%] > > tests/test_concurrency.py .F [ 10%] > > tests/test_config.py [ 11%] > > tests/test_convertors.py FFF [ 12%] > > tests/test_datastructures.py .. [ 17%] > > tests/test_endpoints.py FFF... [ 19%] > > tests/test_exceptions.py .FF.F [ 22%] > > tests/test_formparsers.py ..F [ 31%] > > tests/test_requests.py FFF...FFF.FF.F.FF. [ 41%] > > tests/test_responses.py FF. [ 48%] > > tests/test_routing.py FF..FF.FF.FF.F.F.FF..F.F.F..FFF..FFF.. [ 60%] > > .. [ 60%] > > tests/test_schemas.py .F [ 61%] > > tests/test_staticfiles.py FFF.FFF.FF.. [ 68%] > > tests/test_status.py .. [ 68%] > > tests/test_templates.py ..F.FF [ 71%] > > tests/test_testclient.py F.F..FF.FFF [ 76%] > > tests/test_websockets.py [ 84%] > > tests/middleware/test_base.py FF....FF..FF [ 89%] > > tests/middleware/test_cors.py FFF [ 93%] > > tests/middleware/test_errors.py .F [ 94%] > > tests/middleware/test_gzip.py F [ 95%] -- Arnaud Rebillout / OffSec / Kali Linux Developer
Processed: Bug#1058534 marked as pending in node-rollup-plugin-node-polyfills
Processing control commands: > tag -1 pending Bug #1058534 [src:node-rollup-plugin-node-polyfills] node-rollup-plugin-node-polyfills: FTBFS: make: *** [debian/rules:8: binary] Error 25 Added tag(s) pending. -- 1058534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058534: marked as pending in node-rollup-plugin-node-polyfills
Control: tag -1 pending Hello, Bug #1058534 in node-rollup-plugin-node-polyfills reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-node-polyfills/-/commit/b3121dc29d5fc7e7a69763b08e2f88fdc9221c63 Update build Closes: #1058534 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058534
Processed: Bug#1058542 marked as pending in node-ytdl-core
Processing control commands: > tag -1 pending Bug #1058542 [src:node-ytdl-core] node-ytdl-core: FTBFS: make: *** [debian/rules:8: binary] Error 25 Added tag(s) pending. -- 1058542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058542: marked as pending in node-ytdl-core
Control: tag -1 pending Hello, Bug #1058542 in node-ytdl-core reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-ytdl-core/-/commit/737662559833d74271c842624692a2d7689e4ab1 Add tsc patch Closes: #1058542 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058542
Bug#1058330: marked as done (pycurl: FTBFS: make[1]: *** [debian/rules:37: override_dh_auto_test] Error 2)
Your message dated Wed, 13 Dec 2023 01:57:42 +
with message-id
and subject line Bug#1058330: fixed in pycurl 7.45.2-7
has caused the Debian Bug report #1058330,
regarding pycurl: FTBFS: make[1]: *** [debian/rules:37: override_dh_auto_test]
Error 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycurl
Version: 7.45.2-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/tests/fake-curl/libcurl'
> `curl-config --cc` -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection `curl-config --cflags` -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -shared -fPIC \
> -Wl,-soname,with_gnutls.so -o with_gnutls.so with_gnutls.c
> `curl-config --cc` -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection `curl-config --cflags` -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -shared -fPIC \
> -Wl,-soname,with_nss.so -o with_nss.so with_nss.c
> `curl-config --cc` -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection `curl-config --cflags` -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -shared -fPIC \
> -Wl,-soname,with_openssl.so -o with_openssl.so with_openssl.c
> `curl-config --cc` -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection `curl-config --cflags` -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -shared -fPIC \
> -Wl,-soname,with_unknown_ssl.so -o with_unknown_ssl.so
> with_unknown_ssl.c
> `curl-config --cc` -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection `curl-config --cflags` -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -shared -fPIC \
> -Wl,-soname,without_ssl.so -o without_ssl.so without_ssl.c
> make[3]: Leaving directory '/<>/tests/fake-curl/libcurl'
> ./tests/run.sh
> + test -n python3.12
> + test -n python3.12 -m pytest
> + mkdir -p tests/tmp
> + python3.12 -V
> + awk {print $2}
> + awk -F. {print $1}
> + export PYTHONMAJOR=3
> + python3.12 -V
> + awk {print $2}
> + awk -F. {print $2}
> + export PYTHONMINOR=12
> + ls -d build/lib.linux-x86_64-cpython-312
> + export PYTHONPATH=build/lib.linux-x86_64-cpython-312:
> + extra_attrs=
> + test = true
> + python3.12 -c import pycurl; print(pycurl.version)
> PycURL/7.45.2 libcurl/8.5.0 GnuTLS/3.8.2 zlib/1.3 brotli/1.1.0 zstd/1.5.5
> libidn2/2.3.4 libpsl/0.21.2 (+libidn2/2.3.4) libssh2/1.11.0 nghttp2/1.58.0
> librtmp/2.3 OpenLDAP/2.5.13
> + python3.12 -m pytest -v
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 --
> /usr/bin/python3.12
> cachedir: .pytest_cache
> rootdir: /<>
> configfile: pytest.ini
> plugins: flaky-3.7.0
> collecting ... collected 429 items / 4 deselected / 425 selected
>
> tests/cadata_test.py::CaCertsTest::test_request_with_verifypeer SKIPPED [
> 0%]
> tests/cadata_test.py::CaCertsTest::test_set_ca_certs_bogus_type SKIPPED [
> 0%]
> tests/cadata_test.py::CaCertsTest::test_set_ca_certs_bytes SKIPPED (...) [
> 0%]
> tests/certinfo_test.py::CertinfoTest::test_certinfo_option PASSED[
> 0%]
> tests/certinfo_test.py::CertinfoTest::test_getinfo_raw_certinfo SKIPPED [
> 1%]
> tests/certinfo_test.py::CertinfoTest::test_request_with_certinfo SKIPPED [
> 1%]
> tests/certinfo_test.py::CertinfoTest::test_request_without_certinfo PASSED [
> 1%]
> tests/close_socket_cb_test.py::CloseSocketCbTest::test_closesocketfunction_bogus_return
> PASSED [ 1%]
> tests/close_socket_cb_test.py::CloseSocketCbTest::test_closesocketfunction_fail
> PASSED [ 2%]
> tests/clo
Processed: Bug#1058330 marked as pending in pycurl
Processing control commands: > tag -1 pending Bug #1058330 [src:pycurl] pycurl: FTBFS: make[1]: *** [debian/rules:37: override_dh_auto_test] Error 2 Added tag(s) pending. -- 1058330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058330: marked as pending in pycurl
Control: tag -1 pending Hello, Bug #1058330 in pycurl 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/pycurl/-/commit/a9b7081be4e4951ffccc04e23cef98a76fcf3380 Skip one more test to fix FTBFS with curl 8.5.0 (Closes: #1058330) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058330
Bug#1058273: gpredict: FTBFS: dh_install: error: missing files, aborting
tony mancill writes: > So this is very possibly a bug in libreoffice-writer-nogui. Sure seems like it. My guess would be that what files go in what libreoffice binary packages got refactored somehow? Not sure what the point of the nogui package is if it can't be used here any more. [shrug] I don't have any time to chase this right now. Bdale signature.asc Description: PGP signature
Bug#1057613: shed: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Hi. This is from Alex Sisson, the upstream author: Hi, there's a version to test from https://codeberg.org/alexs/shed , dev branch, please give that a quick test and if you're happy with that and I'll make a 1.16 release. Thanks.
Processed: forcibly merging 1057171 1058533
Processing commands for cont...@bugs.debian.org:
> forcemerge 1057171 1058533
Bug #1057171 {Done: tony mancill } [src:libitext5-java]
libitext5-java: FTBFS with bouncycastle 1.77
Bug #1058533 [src:libitext5-java] libitext5-java: FTBFS: [ERROR]
/<>/itext/src/main/java/com/itextpdf/text/pdf/security/PdfPKCS7.java:[1287,48]
cannot find symbol
Marked Bug as done
Owner recorded as tony mancill .
Marked as fixed in versions libitext5-java/5.5.13.3-3.
Merged 1057171 1058533
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1057171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057171
1058533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058313: marked as done (openpyxl: FTBFS: make[1]: *** [debian/rules:26: python-test3.11] Error 1)
Your message dated Tue, 12 Dec 2023 23:21:01 + with message-id and subject line Bug#1058313: fixed in openpyxl 3.1.2+dfsg-5 has caused the Debian Bug report #1058313, regarding openpyxl: FTBFS: make[1]: *** [debian/rules:26: python-test3.11] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1058313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openpyxl Version: 3.1.2+dfsg-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cp -n debian/conditional-formatting.xlsx openpyxl/formatting/tests/data > cp -n debian/complex-styles.xlsx openpyxl/reader/tests/data > LC_ALL=C.UTF-8 python3.12 /usr/bin/py.test-3 openpyxl > = test session starts > == > platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 > rootdir: /<> > configfile: pytest.ini > collected 2513 items > > openpyxl/cell/tests/test_cell.py .sx [ > 1%] > ...s [ > 2%] > openpyxl/cell/tests/test_read_only.py . [ > 2%] > openpyxl/cell/tests/test_rich_text.py . [ > 3%] > openpyxl/cell/tests/test_text.py [ > 3%] > openpyxl/cell/tests/test_writer.py . [ > 5%] > .. [ > 6%] > openpyxl/chart/tests/test_3d.py [ > 6%] > openpyxl/chart/tests/test_area_chart.py .[ > 6%] > openpyxl/chart/tests/test_axis.py . [ > 7%] > openpyxl/chart/tests/test_bar_chart.py ..[ > 7%] > openpyxl/chart/tests/test_bubble_chart.py .. [ > 7%] > openpyxl/chart/tests/test_chart.py ..[ > 8%] > openpyxl/chart/tests/test_chartspace.py [ > 8%] > openpyxl/chart/tests/test_data_source.py .. [ > 9%] > openpyxl/chart/tests/test_error_bar.py ..[ > 9%] > openpyxl/chart/tests/test_label.py [ > 9%] > openpyxl/chart/tests/test_layout.py ... [ > 9%] > openpyxl/chart/tests/test_legend.py [ > 9%] > openpyxl/chart/tests/test_line_chart.py .[ > 9%] > openpyxl/chart/tests/test_marker.py [ > 10%] > openpyxl/chart/tests/test_picture.py .. [ > 10%] > openpyxl/chart/tests/test_pie_chart.py . [ > 10%] > openpyxl/chart/tests/test_pivot.py [ > 10%] > openpyxl/chart/tests/test_plotarea.py [ > 11%] > openpyxl/chart/tests/test_print.py [ > 11%] > openpyxl/chart/tests/test_radar_chart.py .. [ > 11%] > openpyxl/chart/tests/test_reader.py ... [ > 11%] > openpyxl/chart/tests/test_reference.py ..[ > 11%] > openpyxl/chart/tests/test_scatter_chart.py ..[ > 11%] > openpyxl/chart/tests/test_series.py .[ > 12%] > openpyxl/chart/tests/test_series_factory.py ... [ > 12%] > openpyxl/chart/tests/test_shapes.py .. [ > 12%] > openpyxl/chart/tests/test_stock_chart.py .. [ > 12%] > openpyxl/chart/tests/test_surface_chart.py [ > 13%] > openpyxl/chart/tests/test_text.py . [ > 13%] > openpyxl/chart/tests/test_title.py ... [ > 13%] >
Bug#1055844: marked as done (pandas: Build-Depends on python3-xarray which is not in testing)
Your message dated Tue, 12 Dec 2023 23:21:21 + with message-id and subject line Bug#1055844: fixed in pandas 1.5.3+dfsg-10 has caused the Debian Bug report #1055844, regarding pandas: Build-Depends on python3-xarray which is not in testing 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.) -- 1055844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pandas Version: 1.5.3+dfsg-6 Severity: serious Tags: ftbfs Hi Maintainer pandas has a build-dependency on python3-xarray which is no longer in testing. Please drop this build-dependency or help get python3-xarray back into testing. Regards Graham --- End Message --- --- Begin Message --- Source: pandas Source-Version: 1.5.3+dfsg-10 Done: Rebecca N. Palmer We believe that the bug you reported is fixed in the latest version of pandas, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rebecca N. Palmer (supplier of updated pandas 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: Tue, 12 Dec 2023 20:04:41 + Source: pandas Architecture: source Version: 1.5.3+dfsg-10 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Rebecca N. Palmer Closes: 1055844 1058468 Changes: pandas (1.5.3+dfsg-10) unstable; urgency=medium . * Temporarily drop numba and xarray test-depends (skipping tests). (Closes: #1058468, #1055844) Checksums-Sha1: 74ac9b75e5704f6788892c9bf9c7a42bb8065afa 4740 pandas_1.5.3+dfsg-10.dsc fb2febf8b79b97519b86969cef81f6de5f969435 76916 pandas_1.5.3+dfsg-10.debian.tar.xz d7fe7ec5f0a6e1490b94f9c2d73e0ff8be559cae 6631 pandas_1.5.3+dfsg-10_source.buildinfo Checksums-Sha256: ba9284065a814a8b3f7a97629ac21fa6a243c453164becf42b776753946084b2 4740 pandas_1.5.3+dfsg-10.dsc cd7e8fb8db33b370c9043a67d0454e42c2b0278f972fbded6777e1e164489a03 76916 pandas_1.5.3+dfsg-10.debian.tar.xz 96aa33a72ea83c80282a96d69993751153872f697257fd933232b418df7bec0f 6631 pandas_1.5.3+dfsg-10_source.buildinfo Files: f83d588cc1be9efc02a77802b04d219a 4740 python optional pandas_1.5.3+dfsg-10.dsc 2721e877bd329a30cde10f27fbe803a4 76916 python optional pandas_1.5.3+dfsg-10.debian.tar.xz 1d60d6d4d3fc423275df4c4b1f6573cf 6631 python optional pandas_1.5.3+dfsg-10_source.buildinfo -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAmV44a4YHHJlYmVjY2Ff cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJmcIcP/jfP3pm0lNy4vee7YnjF20DZ dDh3WDJIdjm9Yeg6jMAckD035ovY6gS4rtO89TwkgTaGOOcrE/I40mAlR1bM3oXf fm9Eeuz6WLggFimDuj6GmdbmIcG74TELxCqZ+wEFXarRNkB9mwZUOJwWse9zYD/9 nWlYwiPwgyT6mASzPJwsHRFqSTRSH+c9Q9f3GAr6Dl9BGAqY49QtnpnjLZbByUEq mU10sGZtClVDw8o+si3r1/DD9z8FUkWt07QbHBoclXlTrMeTRttO8miZerJdUX74 bEwAJKmYHH3j5M6f2LDgKQCGqZP+fTnJxfRYLWXfAqwkJVHsZ9Fvr/nN8nnt7XV+ f49Vq5F68gXbcbrXiRxUZTLHUsntNoKdVsQYVAIppnafW3veqW45yRMlLKMT95x7 fua8pEZC72BtJNqrPlP0em+q+z2H/w9bNf19tQG7aqAl0M3/mxxeBA67xyXHvB4+ /mtXP7oWlVqjInYZ3oJeGs8rQ93kuQ7JVCIpPl2fnoklnJhMEl9j7OVMym0qEjp7 9VLexvA8DhKpEy/qTV9Qcw5yQoAgP50b5sV28vIqaIUaqIaTDPwVrFKEXbrrvlS/ /iBGm3m4AImx/CiAww+JyRztQl5etZemVcw6sjlPPpS+ITuLCk7xamG+1KAzL3J0 R3T5WKNpxaBf8keHAUiT =Sc+u -END PGP SIGNATURE End Message ---
Bug#1058284: marked as done (wmtv: FTBFS: configure: error: Package requirements (libv4l1) were not met)
Your message dated Tue, 12 Dec 2023 22:59:41 + with message-id and subject line Bug#1058284: fixed in v4l-utils 1.26.1-1 has caused the Debian Bug report #1058284, regarding wmtv: FTBFS: configure: error: Package requirements (libv4l1) 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.) -- 1058284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wmtv Version: 0.6.7-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for xext... yes > checking for xpm... yes > checking for xxf86dga... yes > checking for xxf86vm... yes > checking for libv4l1... no > configure: error: Package requirements (libv4l1) were not met > > Package 'libjpeg', required by 'libv4lconvert', not 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 libv4l1_CFLAGS > and libv4l1_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/2023/12/12/wmtv_0.6.7-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: v4l-utils Source-Version: 1.26.1-1 Done: Gregor Jasny We believe that the bug you reported is fixed in the latest version of v4l-utils, 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 1058...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gregor Jasny (supplier of updated v4l-utils 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: Tue, 12 Dec 2023 23:06:08 +0100 Source: v4l-utils Architecture: source Version: 1.26.1-1 Distribution: experimental Urgency: medium Maintainer: Gregor Jasny Changed-By: Gregor Jasny Closes: 1014887 1057247 1058284 Changes: v4l-utils (1.26.1-1) experimental; urgency=medium . [ Chris Hofstaedtler ] * Lookup udev install directory from udev.pc (Closes: #1057247) . [ Jeremy Sowden ] * d/control: add missing dependencies to -dev packages (Closes: #1058284) . [ Gregor Jasny ] * Import latest 1.26.1 upstream release (Closes: #1014887) Checksums-Sha1: e0d0376588a2052f9ac2de84a53094fc23965c3a 3238 v4l-utils_1.26.1-1.dsc b2abb01e2522a65f1ed5f0e792ea0a6657fb161a 1192312 v4l-utils_1.26.1.orig.tar.xz cc0d8b04e6daa2078d3de21cd65448f8a1c40094 833 v4l-utils_1.26.1.orig.tar.xz.asc 9c6ccee4668d6ae9c33fd64da04b134f1f203038 22792 v4l-utils_1.26.1-1.debian.tar.xz a974159c0b46d4876a4b5485033bc15e1d05fac6 17946 v4l-utils_1.26.1-1_arm64.buildinfo Checksums-Sha256: 01b904fd1a952b9522da1256c11386f15e1850b524454dfedc6d5b3842e1f9ef 3238 v4l-utils_1.26.1-1.dsc 4a71608c0ef7df2931176989e6d32b445c0bdc1030a2376d929c8ca6e550ec4e 1192312 v4l-utils_1.26.1.orig.tar.xz 1b1360d428f2e8154dce5f454efb01a22c1b5bbdcf2572e658db0e64f8bfc5b7 833 v4l-utils_1.26.1.orig.tar.xz.asc f1b6a968aecb49a07ecaf2b307e7e507058005d6f2162973299db9a2e2a46443 22792 v4l-uti
Bug#1058272: marked as done (omemo-dr: FTBFS: curve25519/curve25519module.c:3:10: fatal error: Python.h: No such file or directory)
Your message dated Tue, 12 Dec 2023 22:52:59 + with message-id and subject line Bug#1058272: fixed in omemo-dr 1.0.1-2 has caused the Debian Bug report #1058272, regarding omemo-dr: FTBFS: curve25519/curve25519module.c:3:10: fatal error: Python.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1058272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: omemo-dr Version: 1.0.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 > -Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -Icurve25519/curve/ed25519/nacl_includes -Icurve25519/curve/ed25519/additions > -Icurve25519/curve/ed25519 -I/usr/include/python3.12 -c > curve25519/curve25519module.c -o > build/temp.linux-x86_64-cpython-312/curve25519/curve25519module.o > curve25519/curve25519module.c:3:10: fatal error: Python.h: No such file or > directory > 3 | #include > | ^~ > compilation terminated. > error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 > > ERROR Backend subprocess exited when trying to invoke build_wheel > E: pybuild pybuild:395: build: plugin pyproject failed with: exit code=1: > python3.12 -m build --skip-dependency-check --no-isolation --wheel --outdir > /<>/.pybuild/cpython3_3.12_omemo-dr > I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build" > module > I: pybuild base:310: python3.11 -m build --skip-dependency-check > --no-isolation --wheel --outdir > /<>/.pybuild/cpython3_3.11_omemo-dr > * Building wheel... > running bdist_wheel > running build > running build_py > creating build/lib.linux-x86_64-cpython-311 > creating build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/sessioncipher.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/session_manager.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/structs.py -> build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/__init__.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/exceptions.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/const.py -> build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/identitykey.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/sessionbuilder.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/observable.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/aes.py -> build/lib.linux-x86_64-cpython-311/omemo_dr > copying src/omemo_dr/identitykeypair.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr > creating build/lib.linux-x86_64-cpython-311/omemo_dr/kdf > copying src/omemo_dr/kdf/__init__.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/kdf > copying src/omemo_dr/kdf/derivedmessagesecrets.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/kdf > copying src/omemo_dr/kdf/messagekeys.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/kdf > copying src/omemo_dr/kdf/derivedrootsecrets.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/kdf > copying src/omemo_dr/kdf/hkdf.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/kdf > creating build/lib.linux-x86_64-cpython-311/omemo_dr/protocol > copying src/omemo_dr/protocol/__init__.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/protocol > copying src/omemo_dr/protocol/prekeywhispermessage.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/protocol > copying src/omemo_dr/protocol/omemo_pb2.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/protocol > copying src/omemo_dr/protocol/whisper_pb2.py -> > build/lib.linux-x86_64-cpython-311/omemo_dr/protocol > copyin
Processed: fixed 1058523 in 7.20.15+ds1+~cs214.269.168-6
Processing commands for cont...@bugs.debian.org: > fixed 1058523 7.20.15+ds1+~cs214.269.168-6 Bug #1058523 [src:node-babel7] node-babel7: FTBFS: ln: failed to create symbolic link 'node_modules/@babel/helper-string-parser/babel-helper-string-parser': Permission denied Marked as fixed in versions node-babel7/7.20.15+ds1+~cs214.269.168-6. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056233: marked as done (cinder's autopkg tests fail with Python 3.12)
Your message dated Tue, 12 Dec 2023 22:49:48 + with message-id and subject line Bug#1056233: fixed in cinder 2:23.0.0-4 has caused the Debian Bug report #1056233, regarding cinder's autopkg tests fail with Python 3.12 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.) -- 1056233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cinder Version: 2:23.0.0-3 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 cinder's autopkg tests fail with Python 3.12: [...] 672s autopkgtest [18:29:44]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import cinder; print(cinder)" ; done 672s autopkgtest [18:29:44]: test autodep8-python3: [--- 672s Testing with python3.12: 672s Traceback (most recent call last): 672s File "", line 1, in 672s File "/usr/lib/python3/dist-packages/cinder/__init__.py", line 21, in 672s import eventlet # noqa 672s ^^^ 672s File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line 17, in 672s from eventlet import convenience 672s File "/usr/lib/python3/dist-packages/eventlet/convenience.py", line 161, in 672s from eventlet.green import ssl 672s File "/usr/lib/python3/dist-packages/eventlet/green/ssl.py", line 25, in 672s _original_wrap_socket = __ssl.wrap_socket 672s ^ 672s AttributeError: module 'ssl' has no attribute 'wrap_socket' --- End Message --- --- Begin Message --- Source: cinder Source-Version: 2:23.0.0-4 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of cinder, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated cinder 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, 04 Dec 2023 17:56:41 +0100 Source: cinder Architecture: source Version: 2:23.0.0-4 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1056233 Changes: cinder (2:23.0.0-4) unstable; urgency=medium . * Add add-params-thin_provisioning-equal-one.patch. * Add Fix_invalid_assert_calls.patch. (Closes: #1056233). Checksums-Sha1: 6644de7b59304e71ea8f9d06405c6af2b8819a3d 4163 cinder_23.0.0-4.dsc a143c8f1590f04a4312bb6b1ef4f3a6b0ce36518 53196 cinder_23.0.0-4.debian.tar.xz 09418421acf9e2f406eef36d9af3c1a124dfa0b9 20561 cinder_23.0.0-4_amd64.buildinfo Checksums-Sha256: d2fa19b2b10cebd4106f67a36b152b8d4fb700183393a1d1a329339624cb3254 4163 cinder_23.0.0-4.dsc fd588272fabc03a96a34e016a1297c342add5ed98b34149d0583e95da3504d0d 53196 cinder_23.0.0-4.debian.tar.xz 32d2afb0c6a69e6baeeca7a4effcf84e0b9ace55fa8019ceffe9fcb72496040f 20561 cinder_23.0.0-4_amd64.buildinfo Files: 5e767dc5e2a8ba7634d1934b4bf36a03 4163 net optional cinder_23.0.0-4.dsc b6c63ce611925495b97b551a8c5cd6f4 53196 net optional cinder_23.0.0-4.debian.tar.xz e4581a0e3ba134d5877af58f6b595bcb 20561 net optional cinder_23.0.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmV42mAACgkQ1BatFaxr Q/5mog//RQeIpIil2NG//deV4CTbXyMZeHqMxTc0Jc2aKm5x6Gw0H9xS4NOOUSqG TqHut1T0t4UZXlAm1Llcl7xRl7pJ0z0mPuhFJIPEAYrKA65rEgCDa1EBhvrEIisF 1T0qW0PfoVUDWaOLMnOW1V5Zpod0mpkMlLGjxZDnliEogR/UbLBG3ecVh4FWtaNF l7kzzW8dsoZvTlDHEI/onaHRSc8B+axCejj05MWQttciceiUtfEBEEI/FIVrXqtq c8JAqcx2wtIZJqy10jIMb+GiGufwNxX1gful2Qr9MOgx4aVsZ+tPgsYgncv6I3FY qp4EsT5f3i0OH5RPYiW7brCmbQ0cVv8yHi7vflAKSOVqgJk7pIYZeYYm4PLV/VtN eCtIu0l1JJfBQzS4m5PLAjKHYbfMAO5rPzhXnsDmAeB/S7xMYqNErQa4h2/8v0lF u4Um5P8qAiiNwFmgGVFfOY9PZYcgoo5n2TRkTB0bf/pLR1uiC9bW9Y1qasSSJPha qT/onVXrJ/Tshbzmtp7poUr4CBhdXGak70pp4k6gKY5Zx53pyTqDQSFkwMnd6gxt +Hc10ftkMJOSeSt9Ip6cpZg5GU2R24wqv6CsoS5EozCISBANtcCSzE/M7eYe7GjE BVgkTyydBMLBRUhmWWW8JOA4Di/MGLFxXsL/2X8a9FDMW81TlLw= =Hy58 -END PGP SIGNATURE End Message ---
Processed: fixed 1058515 in 3.29.4-3
Processing commands for cont...@bugs.debian.org: > fixed 1058515 3.29.4-3 Bug #1058515 [src:node-rollup] node-rollup: FTBFS: make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 Marked as fixed in versions node-rollup/3.29.4-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058273: gpredict: FTBFS: dh_install: error: missing files, aborting
On Tue, Dec 12, 2023 at 09:35:44AM +0100, Lucas Nussbaum wrote: > Source: gpredict > Version: 2.3-115-g0f3beb6-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231212 ftbfs-trixie It feels slightly icky because it pulls in a much larger set of build-deps, but this FTBFS is easily fixed by relaxing the B-D-I on libreoffice-writer-nogui to libreoffice-writer. So this is very possibly a bug in libreoffice-writer-nogui. I went ahead and pushed a patch to packaging repo. If someone feels strongly about keeping the build-deps small for this arch-all package and sticking with libreoffice-writer-nogui, you can reproduce by starting with a clean chroot and running this bit of the build: soffice --writer --headless --convert-to pdf doc/um/gpredict-user-manual.odt And adding build-deps until you no longer get this error. Error: source file could not be loaded I will try to take another look at it before uploading. Cheers, tony
Processed: Bug#1058273 marked as pending in gpredict
Processing control commands: > tag -1 pending Bug #1058273 [src:gpredict] gpredict: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 1058273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058273: marked as pending in gpredict
Control: tag -1 pending Hello, Bug #1058273 in gpredict reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-hamradio-team/gpredict/-/commit/d328dfc309849afad975e9eb44e7096c970bc67a Build-dep on libreoffice-writer (Closes: #1058273) (this message was generated automatically) -- Greetings https://bugs.debian.org/1058273
Processed: Bug#1056233 marked as pending in cinder
Processing control commands: > tag -1 pending Bug #1056233 [src:cinder] cinder's autopkg tests fail with Python 3.12 Added tag(s) pending. -- 1056233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1057587 marked as pending in obs-studio
Processing control commands: > tag -1 pending Bug #1057587 [src:obs-studio] obs-studio: FTBFS: error: ‘av_stream_get_side_data’ is deprecated [-Werror=deprecated-declarations] Added tag(s) pending. -- 1057587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057587: marked as pending in obs-studio
Control: tag -1 pending Hello, Bug #1057587 in obs-studio 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/multimedia-team/obs-studio/-/commit/27325f6dbe9683ea3a1f29481a469fbf5ef46f4d Treat deprecated-declarations as warnings (not as errors) Closes: #1057587 (this message was generated automatically) -- Greetings https://bugs.debian.org/1057587
Bug#1056233: marked as pending in cinder
Control: tag -1 pending Hello, Bug #1056233 in cinder 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/services/cinder/-/commit/9b7f398b1d03a0696aa69150f10fc3f5d8d30714 Add Fix_invalid_assert_calls.patch. (Closes: #1056233). (this message was generated automatically) -- Greetings https://bugs.debian.org/1056233
Processed: Bug#1058284 marked as pending in libv4l
Processing control commands: > tag -1 pending Bug #1058284 [v4l-utils] wmtv: FTBFS: configure: error: Package requirements (libv4l1) were not met Added tag(s) pending. -- 1058284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058284: marked as pending in libv4l
Control: tag -1 pending Hello, Bug #1058284 in libv4l reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/libv4l/-/commit/3fb81cc29850441028d86d7904e144a90bb59dba d/control: add missing dependencies to -dev packages libv4lconvert.pc privately requires libjpeg, and libdvbv5.pc privately requires libudev, but the -dev packages omit these dependencies, which can lead to transitive build failures. For example, wmtv requires libv4l1, which privately requires lib4l2, which privately requires libv4lconvert, which privately requires libjpeg, which may not be installed, and so, even though wmtv does not itself require libjpeg, we get: configure: error: Package requirements (libv4l1) were not met: Package 'libjpeg', required by 'libv4lconvert', not 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 libv4l1_CFLAGS and libv4l1_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Add the missing dependencies. Closes: #1058284 Signed-off-by: Jeremy Sowden (this message was generated automatically) -- Greetings https://bugs.debian.org/1058284
Bug#1056236: marked as done (cloudkitty's autopkg tests fail with Python 3.12)
Your message dated Tue, 12 Dec 2023 22:59:10 +0100
with message-id <1107e43a-861e-429e-93d2-4a3ba234e...@debian.org>
and subject line Issue was in Eventlet
has caused the Debian Bug report #1056236,
regarding cloudkitty's autopkg tests fail with Python 3.12
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.)
--
1056236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cloudkitty
Version: 19.0.0-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
cloudkitty's autopkg tests fail with Python 3.12:
[...]
345s + PYTHON=python3.12 stestr run --parallel --subunit
cloudkitty\.tests\.(?!(.*collectors\.test_prometheus.*|.*storage\.v1\.test_hybrid_storage.*|.*test_hacking\.HackingTestCase\.test_logging_with_tuple_argument.*|storage\.v2\.test_storage_unit\.StorageUnitTest\.test_get_total_one_scope_one_period.*|test_storage_state\.StateManagerTest\.test_get_state_does_update_columns|test_storage_state\.StateManagerTest\.test_get_state_no_column_update|.*storage\.v1\.test_storage\.StorageTotalTest\.test_get_total_without_filter_but_timestamp.*))
345s + subunit2pyunit
345s WARNING: --no-py2 is deprecated, and always on.
345s ===> Testing with python (python3)
346s /usr/lib/python3/dist-packages/pytz/__init__.py:30: SyntaxWarning:
invalid escape sequence '\s'
346s match = re.match("^#\s*version\s*([0-9a-z]*)\s*$", line)
347s
347s =
347s Failures during discovery
347s =
347s --- import errors ---
347s Failed to import test module: cloudkitty.tests
347s Traceback (most recent call last):
347s File "/usr/lib/python3.12/unittest/loader.py", line 427, in
_find_test_path
347s package = self._get_module_from_name(name)
347s
347s File "/usr/lib/python3.12/unittest/loader.py", line 337, in
_get_module_from_name
347s __import__(name)
347s File
"/tmp/autopkgtest.6aTqLp/build.uWH/src/cloudkitty/tests/__init__.py",
line 28, in
347s from cloudkitty import rating
347s File "/tmp/autopkgtest.6aTqLp/build.
347s --
347s Ran 0 tests in 1.767s
347s
347s OK
347s uWH/src/cloudkitty/rating/__init__.py", line 23, in
347s from cloudkitty import messaging
347s File
"/tmp/autopkgtest.6aTqLp/build.uWH/src/cloudkitty/messaging.py", line
17, in
347s import oslo_messaging
347s File "/usr/lib/python3/dist-packages/oslo_messaging/__init__.py",
line 17, in
347s from .notify import *
347s File
"/usr/lib/python3/dist-packages/oslo_messaging/notify/__init__.py", line
28, in
347s from .listener import *
347s File
"/usr/lib/python3/dist-packages/oslo_messaging/notify/listener.py", line
140, in
347s from oslo_messaging import server as msg_server
347s File "/usr/lib/python3/dist-packages/oslo_messaging/server.py",
line 27, in
347s from oslo_service import service
347s File "/usr/lib/python3/dist-packages/oslo_service/service.py",
line 35, in
347s import eventlet
347s File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line
17, in
347s from eventlet import convenience
347s File "/usr/lib/python3/dist-packages/eventlet/convenience.py",
line 7, in
347s from eventlet.green import socket
347s File "/usr/lib/python3/dist-packages/eventlet/green/socket.py",
line 21, in
347s from eventlet.support import greendns
347s File
"/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 45,
in
347s from eventlet.green import ssl
347s File "/usr/lib/python3/dist-packages/eventlet/green/ssl.py", line
25, in
347s _original_wrap_socket = __ssl.wrap_socket
347s ^
347s AttributeError: module 'ssl' has no attribute 'wrap_socket'
347s
347s
347s The above traceback was encountered during test discovery which
imports all the found test modules in the specified test_path.
347s + stestr slowest
348s autopkgtest [18:24:23]: test unittests: ---]
348s autopkgtest [18:24:23]: test unittests: - - - - - - - - - -
results - - - - - - - - - -
348s unittestsFAIL non-zero exit status 3
--- End Message ---
--- Begin Message ---
Hi,
The issue was in python3-eventlet, fixed in version 0.33.3-2.1.
Cheers,
Thomas Goirand (zigo)--- End Message ---
Bug#1056233: Issue isn't what's described
Hi, The issue described in this bug report is invalid, however, there was another one which I just fixed (adding Fix_invalid_assert_calls.patch). I'll use the same bug report then. Cheers, Thomas Goirand (zigo)
Bug#1058306: marked as done (python-yappi: FTBFS: yappi/_yappi.c:240:18: error: invalid use of incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’})
Your message dated Tue, 12 Dec 2023 22:46:08 +0100
with message-id
and subject line Fixed already
has caused the Debian Bug report #1058306,
regarding python-yappi: FTBFS: yappi/_yappi.c:240:18: error: invalid use of
incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’}
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.)
--
1058306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-yappi
Version: 1.4.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2
> -Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DLIB_RT_AVAILABLE=1
> -I/usr/include/python3.12 -c yappi/_yappi.c -o
> build/temp.linux-x86_64-cpython-312/yappi/_yappi.o
> yappi/_yappi.c: In function ‘IS_SUSPENDED’:
> yappi/_yappi.c:240:18: error: invalid use of incomplete typedef
> ‘PyFrameObject’ {aka ‘struct _frame’}
> 240 | return (frame->f_stacktop != NULL);
> | ^~
> yappi/_yappi.c: In function ‘_code2pit’:
> yappi/_yappi.c:697:29: error: ‘PyCodeObject’ has no member named
> ‘co_varnames’; did you mean ‘co_names’?
> 697 | co_varnames = cobj->co_varnames;
> | ^~~
> | co_names
> yappi/_yappi.c: In function ‘IS_SUSPENDED’:
> yappi/_yappi.c:242:1: warning: control reaches end of non-void function
> [-Wreturn-type]
> 242 | }
> | ^
> error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
> make[1]: *** [debian/rules:16: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-yappi_1.4.0-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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 ---
Hi,
This was fixed in version 1.4.0-3.
Cheers,
Thomas Goirand (zigo)--- End Message ---
Bug#1058210: marked as done (python-scciclient: FTBFS: ModuleNotFoundError: No module named 'asyncore')
Your message dated Tue, 12 Dec 2023 22:41:36 +0100 with message-id <2f11481f-3e11-459b-a04c-45d839b92...@debian.org> and subject line Issue was in python3-pysnmp-lextudio has caused the Debian Bug report #1058210, regarding python-scciclient: FTBFS: ModuleNotFoundError: No module named 'asyncore' 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.) -- 1058210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-scciclient Version: 0.15.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie 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 > pkgos-dh_auto_test --no-py2 > 'scciclient\.tests\.irmc\.(?!(.*test_scci\.SCCITestCase\.test_get_report_ok.*))' > + PKGOS_TEST_PARALLEL=yes > + PKGOS_TEST_SERIAL=no > + PYTHONS=disabled > + PYTHON3S=disabled > + TEST_PARALLEL_OPT=--parallel > + TEST_SERIAL_OPT= > + echo WARNING: --no-py2 is deprecated, and always on. > WARNING: --no-py2 is deprecated, and always on. > + shift > + py3versions -vr > + PYTHON3S=3.12 3.11 > + [ yes = no ] > + [ no = yes ] > + [ 3.12 = disabled ] > + echo 3.12 > + cut -d. -f1 > + PYMAJOR=3 > + echo ===> Testing with python (python3) > ===> Testing with python (python3) > + pwd > + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ] > + [ -e .stestr.conf ] > + [ -x /usr/bin/python3-stestr ] > + STESTR=stestr > + rm -rf .stestr > + PYTHON=python3.12 stestr run --parallel --subunit > scciclient\.tests\.irmc\.(?!(.*test_scci\.SCCITestCase\.test_get_report_ok.*)) > + subunit2pyunit > /<>/scciclient/tests/irmc/test_elcm.py:2311: SyntaxWarning: > invalid escape sequence '\/' > "Start": "2018\/03\/19 12:28:03", > /<>/scciclient/tests/irmc/test_elcm.py:2369: SyntaxWarning: > invalid escape sequence '\/' > '@date': '2018\/03\/12 15:10:00', > /<>/scciclient/tests/irmc/test_elcm.py:2374: SyntaxWarning: > invalid escape sequence '\/' > '@date': '2018\/03\/19 09:40:03', > > = > Failures during discovery > = > --- import errors --- > Failed to import test module: scciclient.tests.irmc.test_elcm > Traceback (most recent call last): > File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path > module = self._get_module_from_name(name) > > File "/usr/lib/python3.12/unittest/loader.py", line 337, in > _get_module_from_name > __import__(name) > File "/<>/scciclient/tests/irmc/test_elcm.py", line 26, in > > from scciclient.irmc import elcm > File "/<>/scciclient/irmc/__init__.py", line 15, in > from . import elcm # noqa > ^^ > File "/<>/scciclient/irmc/elcm.py", line 26, in > from scciclient.irmc import scci > File "/<>/scciclient/irmc/scci.py", line 28, in > from scciclient.irmc import snmp > File "/<>/scciclient/irmc/snmp.py", line 16, in > from pysnmp import hlapi as snmp > File "/usr/lib/python3/dist-packages/pysnmp/hlapi/__init__.py", line 10, in > > from pysnmp.hlapi import auth > File "/usr/lib/python3/dist-packages/pysnmp/hlapi/auth.py", line 7, in > > from pysnmp.entity import config > File "/usr/lib/python3/dist-packages/pysnmp/entity/config.py", line 8, in > > from pysnmp.carrier.asyncore.dgram import udp, udp6, unix > File "/usr/lib/python3/dist-packages/pysnmp/carrier/asyncore/dgram/udp.py", > line 9, in > from pysnmp.carrier.asyncore.dgram.base import DgramSocketTransport > File > "/usr/lib/python3/dist-packages/pysnmp/carrier/asyncore/dgram/base.py", line > 10, in > from pysnmp.carrier.asyncore.base import AbstractSocketTransport > File "/usr/lib/python3/dist-packages/pysnmp
Bug#1058117: marked as done (python-oslo.log: FTBFS: ModuleNotFoundError: No module named 'asyncore')
Your message dated Tue, 12 Dec 2023 21:21:35 + with message-id and subject line Bug#1058117: fixed in python-oslo.log 5.3.0-3 has caused the Debian Bug report #1058117, regarding python-oslo.log: FTBFS: ModuleNotFoundError: No module named 'asyncore' 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.) -- 1058117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-oslo.log Version: 5.3.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie 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 > pkgos-dh_auto_install --no-py2 --in-tmp > + PKGOS_IN_TMP=no > + echo WARNING: --no-py2 is deprecated and always on. > WARNING: --no-py2 is deprecated and always on. > + shift > + PKGOS_IN_TMP=yes > + shift > + dpkg-parsechangelog -SSource > + SRC_PKG_NAME=python-oslo.log > + echo python-oslo.log > + sed s/python-// > + PY_MODULE_NAME=oslo.log > + py3versions -vr > + PYTHON3S=3.12 3.11 > + [ yes = yes ] > + TARGET_DIR=tmp > + pwd > + python3.12 setup.py install --install-layout=deb --root > /<>/debian/tmp > /usr/lib/python3/dist-packages/setuptools/__init__.py:84: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > dist.fetch_build_eggs(dist.setup_requires) > /usr/lib/python3/dist-packages/setuptools/command/develop.py:40: > EasyInstallDeprecationWarning: easy_install command is deprecated. > !! > > > > Please avoid running ``setup.py`` and ``easy_install``. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://github.com/pypa/setuptools/issues/917 for details. > > > > !! > easy_install.initialize_options(self) > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > running install > [pbr] Generating AUTHORS > [pbr] AUTHORS complete (0.0s) > running build > running build_py > creating build > creating build/lib > creating build/lib/oslo_log > creating build/lib/oslo_log/tests > creating build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/__init__.py -> build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/test_rate_limit.py -> > build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/test_versionutils.py -> > build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/test_helpers.py -> build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/test_convert_json.py -> > build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/test_formatters.py -> > build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/test_pipe_mutex.py -> > build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/test_log.py -> build/lib/oslo_log/tests/unit > copying oslo_log/tests/unit/test_custom_loghandler.py -> > build/lib/oslo_log/tests/unit > creating build/lib/oslo_log/fixture > copying oslo_log/fixture/__init__.
Bug#1058145: marked as done (python-proliantutils: FTBFS: ModuleNotFoundError: No module named 'asyncore')
Your message dated Tue, 12 Dec 2023 21:21:43 + with message-id and subject line Bug#1058145: fixed in python-proliantutils 2.16.0-3 has caused the Debian Bug report #1058145, regarding python-proliantutils: FTBFS: ModuleNotFoundError: No module named 'asyncore' 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.) -- 1058145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-proliantutils Version: 2.16.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie 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 > pkgos-dh_auto_install --no-py2 > + PKGOS_IN_TMP=no > + echo WARNING: --no-py2 is deprecated and always on. > WARNING: --no-py2 is deprecated and always on. > + shift > + dpkg-parsechangelog -SSource > + SRC_PKG_NAME=python-proliantutils > + echo python-proliantutils > + sed s/python-// > + PY_MODULE_NAME=proliantutils > + py3versions -vr > + PYTHON3S=3.12 3.11 > + [ no = yes ] > + TARGET_DIR=python3-proliantutils > + pwd > + python3.12 setup.py install --install-layout=deb --root > /<>/debian/python3-proliantutils > /usr/lib/python3/dist-packages/setuptools/dist.py:744: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'description-file' will not be supported in > future > versions. Please use the underscore name 'description_file' instead. > > This deprecation is overdue, please update your project and remove > deprecated > calls to avoid build errors in the future. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > opt = self.warn_dash_deprecation(opt, section) > /usr/lib/python3/dist-packages/setuptools/dist.py:744: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'author-email' will not be supported in future > versions. Please use the underscore name 'author_email' instead. > > This deprecation is overdue, please update your project and remove > deprecated > calls to avoid build errors in the future. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > opt = self.warn_dash_deprecation(opt, section) > /usr/lib/python3/dist-packages/setuptools/dist.py:744: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'home-page' will not be supported in future > versions. Please use the underscore name 'home_page' instead. > > This deprecation is overdue, please update your project and remove > deprecated > calls to avoid build errors in the future. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > opt = self.warn_dash_deprecation(opt, section) > /usr/lib/python3/dist-packages/setuptools/dist.py:744: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'python-requires' will not be supported in > future > versions. Please use the underscore name 'python_requires' instead. > > Thi
Bug#1058184: marked as done (python-taskflow: FTBFS: ModuleNotFoundError: No module named 'asyncore')
Your message dated Tue, 12 Dec 2023 21:21:59 + with message-id and subject line Bug#1058184: fixed in python-taskflow 5.4.0-2 has caused the Debian Bug report #1058184, regarding python-taskflow: FTBFS: ModuleNotFoundError: No module named 'asyncore' 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.) -- 1058184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-taskflow Version: 5.4.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie 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.12 3.11 ; do \ > python3 setup.py install -f --install-layout=deb > --root=/<>/debian/tmp ; \ > done > /usr/lib/python3/dist-packages/setuptools/__init__.py:84: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > dist.fetch_build_eggs(dist.setup_requires) > /usr/lib/python3/dist-packages/setuptools/command/develop.py:40: > EasyInstallDeprecationWarning: easy_install command is deprecated. > !! > > > > Please avoid running ``setup.py`` and ``easy_install``. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://github.com/pypa/setuptools/issues/917 for details. > > > > !! > easy_install.initialize_options(self) > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > running install > [pbr] Generating AUTHORS > [pbr] AUTHORS complete (0.0s) > running build > running build_py > creating build > creating build/lib > creating build/lib/taskflow > creating build/lib/taskflow/tests > copying taskflow/tests/utils.py -> build/lib/taskflow/tests > copying taskflow/tests/__init__.py -> build/lib/taskflow/tests > copying taskflow/tests/test_examples.py -> build/lib/taskflow/tests > copying taskflow/tests/fixtures.py -> build/lib/taskflow/tests > creating build/lib/taskflow/conductors > copying taskflow/conductors/__init__.py -> build/lib/taskflow/conductors > copying taskflow/conductors/base.py -> build/lib/taskflow/conductors > creating build/lib/taskflow/conductors/backends > copying taskflow/conductors/backends/__init__.py -> > build/lib/taskflow/conductors/backends > copying taskflow/conductors/backends/impl_executor.py -> > build/lib/taskflow/conductors/backends > copying taskflow/conductors/backends/impl_blocking.py -> > build/lib/taskflow/conductors/backends > copying taskflow/conductors/backends/impl_nonblocking.py -> > build/lib/taskflow/conductors/backends > creating build/lib/taskflow/utils > copying taskflow/utils/schema_utils.py -> build/lib/taskflow/utils > copying taskflow/utils/iter_utils.py -> build/lib/taskflow/utils > copying taskflow/utils/__init__.py -> build/lib/taskflow/utils > copying taskflow/utils/threading_utils.py -> build/lib/taskflow/utils > copying taskflow/utils/banner.py -> build/lib/taskflow/util
Processed: Bug#1058145 marked as pending in python-proliantutils
Processing control commands: > tag -1 pending Bug #1058145 [src:python-proliantutils] python-proliantutils: FTBFS: ModuleNotFoundError: No module named 'asyncore' Added tag(s) pending. -- 1058145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058145: marked as pending in python-proliantutils
Control: tag -1 pending Hello, Bug #1058145 in python-proliantutils 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-proliantutils/-/commit/f62d53376161f296fff129e242205408e04c7326 Added python3-pyasyncore as (build-)depends (Closes: #1058145). (this message was generated automatically) -- Greetings https://bugs.debian.org/1058145
Processed: Bug#1058117 marked as pending in python-oslo.log
Processing control commands: > tag -1 pending Bug #1058117 [src:python-oslo.log] python-oslo.log: FTBFS: ModuleNotFoundError: No module named 'asyncore' Added tag(s) pending. -- 1058117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058117: marked as pending in python-oslo.log
Control: tag -1 pending Hello, Bug #1058117 in python-oslo.log 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/oslo/python-oslo.log/-/commit/f7a7d04d6b930085487350366cafe79c12db16aa Added python3-pyasyncore as (build-)depends (Closes: #1058117). (this message was generated automatically) -- Greetings https://bugs.debian.org/1058117
Processed: tagging 1058514
Processing commands for cont...@bugs.debian.org: > tags 1058514 + upstream Bug #1058514 [src:liblouisutdml] liblouisutdml: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1058514 is forwarded to https://github.com/liblouis/liblouisutdml/issues/103
Processing commands for cont...@bugs.debian.org: > forwarded 1058514 https://github.com/liblouis/liblouisutdml/issues/103 Bug #1058514 [src:liblouisutdml] liblouisutdml: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/liblouis/liblouisutdml/issues/103'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058409: marked as done (python-pytest-benchmark: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Tue, 12 Dec 2023 20:54:56 +
with message-id
and subject line Bug#1058409: fixed in python-pytest-benchmark 4.0.0-3
has caused the Debian Bug report #1058409,
regarding python-pytest-benchmark: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pytest-benchmark
Version: 4.0.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.12 with "build"
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_pytest-benchmark
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/pytest_benchmark
> copying src/pytest_benchmark/utils.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/compat.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/__init__.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/session.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/stats.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/logger.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/plugin.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/hookspec.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/__main__.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/fixture.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/timers.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/csv.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/table.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/cli.py -> build/lib/pytest_benchmark
> copying src/pytest_benchmark/histogram.py -> build/lib/pytest_benchmark
> creating build/lib/pytest_benchmark/storage
> copying src/pytest_benchmark/storage/elasticsearch.py ->
> build/lib/pytest_benchmark/storage
> copying src/pytest_benchmark/storage/__init__.py ->
> build/lib/pytest_benchmark/storage
> copying src/pytest_benchmark/storage/file.py ->
> build/lib/pytest_benchmark/storage
> running egg_info
> creating src/pytest_benchmark.egg-info
> writing src/pytest_benchmark.egg-info/PKG-INFO
> writing dependency_links to src/pytest_benchmark.egg-info/dependency_links.txt
> writing entry points to src/pytest_benchmark.egg-info/entry_points.txt
> writing requirements to src/pytest_benchmark.egg-info/requires.txt
> writing top-level names to src/pytest_benchmark.egg-info/top_level.txt
> writing manifest file 'src/pytest_benchmark.egg-info/SOURCES.txt'
> reading manifest file 'src/pytest_benchmark.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.py[cod]' found anywhere in
> distribution
> warning: no previously-included files matching '__pycache__/*' found anywhere
> in distribution
> warning: no previously-included files matching '*.so' found anywhere in
> distribution
> warning: no previously-included files matching '*.dylib' found anywhere in
> distribution
> adding license file 'LICENSE'
> adding license file 'AUTHORS.rst'
> writing manifest file 'src/pytest_benchmark.egg-info/SOURCES.txt'
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/pytest_benchmark
> copying build/lib/pytest_benchmark/utils.py ->
Bug#1058356: marked as done (python-testfixtures: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Tue, 12 Dec 2023 20:55:06 +
with message-id
and subject line Bug#1058356: fixed in python-testfixtures 7.2.2-2
has caused the Debian Bug report #1058356,
regarding python-testfixtures: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-testfixtures
Version: 7.2.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
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 plugin_pyproject:110: Building wheel for python3.12 with "build"
> module
> I: pybuild base:310: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_testfixtures
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/testfixtures
> copying testfixtures/utils.py -> build/lib/testfixtures
> copying testfixtures/compat.py -> build/lib/testfixtures
> copying testfixtures/__init__.py -> build/lib/testfixtures
> copying testfixtures/logcapture.py -> build/lib/testfixtures
> copying testfixtures/popen.py -> build/lib/testfixtures
> copying testfixtures/sybil.py -> build/lib/testfixtures
> copying testfixtures/datetime.py -> build/lib/testfixtures
> copying testfixtures/comparison.py -> build/lib/testfixtures
> copying testfixtures/outputcapture.py -> build/lib/testfixtures
> copying testfixtures/django.py -> build/lib/testfixtures
> copying testfixtures/rmtree.py -> build/lib/testfixtures
> copying testfixtures/resolve.py -> build/lib/testfixtures
> copying testfixtures/shouldraise.py -> build/lib/testfixtures
> copying testfixtures/tempdirectory.py -> build/lib/testfixtures
> copying testfixtures/shouldwarn.py -> build/lib/testfixtures
> copying testfixtures/twisted.py -> build/lib/testfixtures
> copying testfixtures/components.py -> build/lib/testfixtures
> copying testfixtures/replace.py -> build/lib/testfixtures
> copying testfixtures/mock.py -> build/lib/testfixtures
> creating build/lib/testfixtures/tests
> copying testfixtures/tests/test_mappingcomparison.py ->
> build/lib/testfixtures/tests
> copying testfixtures/tests/test_diff.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_components.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_outputcapture.py ->
> build/lib/testfixtures/tests
> copying testfixtures/tests/__init__.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_time.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_stringcomparison.py ->
> build/lib/testfixtures/tests
> copying testfixtures/tests/sample3.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_wrap.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_replace.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_should_raise.py ->
> build/lib/testfixtures/tests
> copying testfixtures/tests/test_generator.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_rangecomparison.py ->
> build/lib/testfixtures/tests
> copying testfixtures/tests/test_compare.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_comparison.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_replacer.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_logcapture.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_popen.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/sample1.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/sample2.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_mock.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_tempdir.py -> build/lib/testfixtures/tests
> copying testfixtures/tests/test_twisted.py -> build/lib/testfixtures/tests
> copying te
Bug#1056507: marked as done (python-testfixtures autopkg tests fail with Python 3.12)
Your message dated Tue, 12 Dec 2023 20:55:06 +
with message-id
and subject line Bug#1056507: fixed in python-testfixtures 7.2.2-2
has caused the Debian Bug report #1056507,
regarding python-testfixtures autopkg tests fail with Python 3.12
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.)
--
1056507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-testfixtures
Version: 7.2.2-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-testfixtures autopkg tests fail with Python 3.12:
[...]
233s === FAILURES
===
233s __ TempDirectoryTests.test_as_path_relative_sequence
___
233s
233s self = testMethod=test_as_path_relative_sequence>
233s
233s def test_as_path_relative_sequence(self):
233s with TempDirectory(encoding='ascii') as d:
233s > compare(d.as_path(('foo', 'bar')),
expected=Path(d.path) / 'foo' / 'bar', strict=True)
233s E AssertionError: PosixPath not as expected:
233s E
233s E attributes differ:
233s E '_raw_paths': ['/tmp/tmpmv5f4rio', 'foo', 'bar']
(expected) != ['/tmp/tmpmv5f4rio/foo/bar'] (actual)
233s E
233s E While comparing ._raw_paths: sequence not as expected:
233s E
233s E same:
233s E []
233s E
233s E expected:
233s E ['/tmp/tmpmv5f4rio', 'foo', 'bar']
233s E
233s E actual:
233s E ['/tmp/tmpmv5f4rio/foo/bar']
233s E
233s E While comparing ._raw_paths[0]:
233s E '/tmp/tmpmv5f4rio' (expected)
233s E !=
233s E '/tmp/tmpmv5f4rio/foo/bar' (actual)
233s
233s
/usr/lib/python3/dist-packages/testfixtures/tests/test_tempdirectory.py:313:
AssertionError
233s ___ TempDirectoryTests.test_as_path_relative_string
233s
233s self = testMethod=test_as_path_relative_string>
233s
233s def test_as_path_relative_string(self):
233s with TempDirectory(encoding='ascii') as d:
233s > compare(d.as_path('foo/bar'), expected=Path(d.path) /
'foo' / 'bar', strict=True)
233s E AssertionError: PosixPath not as expected:
233s E
233s E attributes differ:
233s E '_raw_paths': ['/tmp/tmpzu22wvdh', 'foo', 'bar']
(expected) != ['/tmp/tmpzu22wvdh/foo/bar'] (actual)
233s E
233s E While comparing ._raw_paths: sequence not as expected:
233s E
233s E same:
233s E []
233s E
233s E expected:
233s E ['/tmp/tmpzu22wvdh', 'foo', 'bar']
233s E
233s E actual:
233s E ['/tmp/tmpzu22wvdh/foo/bar']
233s E
233s E While comparing ._raw_paths[0]:
233s E '/tmp/tmpzu22wvdh' (expected)
233s E !=
233s E '/tmp/tmpzu22wvdh/foo/bar' (actual)
233s
233s
/usr/lib/python3/dist-packages/testfixtures/tests/test_tempdirectory.py:309:
AssertionError
233s === warnings summary
===
233s
../../../usr/lib/python3/dist-packages/testfixtures/tests/test_compare.py:710
233s
/usr/lib/python3/dist-packages/testfixtures/tests/test_compare.py:710:
SyntaxWarning: invalid escape sequence '\('
233s "\(1, 2, 3\) \(<(class|type) 'tuple'>\) \(expected\) != "
233s
233s
../../../usr/lib/python3/dist-packages/testfixtures/tests/test_compare.py:712
233s
/usr/lib/python3/dist-packages/testfixtures/tests/test_compare.py:712:
SyntaxWarning: invalid escape sequence '\('
233s "\(<(class|type) 'generator'>\) \(actual\)"
233s
233s
../../../usr/lib/python3/dist-packages/testfixtures/tests/test_compare.py:748
233s
/usr/lib/python3/dist-packages/testfixtures/tests/test_compare.py:748:
SyntaxWarning: invalid escape sequence '\('
233s "range\(1, 4\) \(<(class|type) 'x?range'>\) != "
233s
233s
../../../usr/lib/python3/dist-packages/testfixtures/tests/test_compare.py:750
233s
/usr/lib/python3/dist-packages/testfixtures/tests/test_compare.py:750:
SyntaxWarning: invalid escape sequence '\('
233s "\(<(class|type) 'generator'>\)"
233s
233s
../../../usr/lib/python3/dist-packages/testfixtures/tests/test_stringcomparison.py:10
233s
/usr/lib/python3/dist-packages/testfixtures/tests/test_stringcomparison.py:10:
SyntaxWarning: invalid escape sequence '\d'
233s self.assertTrue('on 40220' == S('on \d+'))
233s
233s
../../../usr/lib/python3/dist-packages/testfixtures/tests/test_stringcomparison.py:13
233s
/usr/lib/python
Bug#1058554: skimage: FTBFS: intersphinx inventory './_intersphinx/sklearn-objects.inv' not fetchable due to : [Errno 2] No such file or directory: '/<>/doc/sou
Source: skimage Version: 0.22.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > python3.11 tools/build_modref_templates.py > outdir: > 19 files written > Build API docs...done. > python3.11 -m sphinx -b html -d build/doctrees -D mathjax_path=MathJax.js > source build/html > Running Sphinx v7.2.6 > /usr/lib/python3/dist-packages/sphinx_gallery/sphinx_compatibility.py:71: > RemovedInSphinx80Warning: > > The alias 'sphinx.util.status_iterator' is deprecated, use > 'sphinx.util.display.status_iterator' instead. Check CHANGES for Sphinx API > modifications. > > making output directory... done > [autosummary] generating autosummary for: about/code_of_conduct.md, > about/index.rst, about/report_handling_manual.rst, about/values.md, > api/api.rst, api/skimage.color.rst, api/skimage.data.rst, > api/skimage.draw.rst, api/skimage.exposure.rst, api/skimage.feature.rst, ..., > user_guide/index.rst, user_guide/install.rst, user_guide/numpy_images.rst, > user_guide/plugins.rst, user_guide/transforming_image_data.rst, > user_guide/tutorial_parallelization.rst, > user_guide/tutorial_segmentation.rst, user_guide/tutorials.rst, > user_guide/video.rst, user_guide/visualization.rst > loading intersphinx inventory from > /usr/share/doc/python3.9/html/objects.inv... > loading intersphinx inventory from ./_intersphinx/numpy-objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory '/usr/share/doc/python3.9/html/objects.inv' not > fetchable due to : [Errno 2] No such file or > directory: '/usr/share/doc/python3.9/html/objects.inv' > loading intersphinx inventory from ./_intersphinx/scipy-objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory './_intersphinx/scipy-objects.inv' not fetchable due to > : [Errno 2] No such file or directory: > '/<>/doc/source/./_intersphinx/scipy-objects.inv' > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory './_intersphinx/numpy-objects.inv' not fetchable due to > : [Errno 2] No such file or directory: > '/<>/doc/source/./_intersphinx/numpy-objects.inv' > loading intersphinx inventory from ./_intersphinx/sklearn-objects.inv... > loading intersphinx inventory from https://matplotlib.org/objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory './_intersphinx/sklearn-objects.inv' not fetchable due > to : [Errno 2] No such file or directory: > '/<>/doc/source/./_intersphinx/sklearn-objects.inv' > intersphinx inventory has moved: https://matplotlib.org/objects.inv -> > https://matplotlib.org/stable/objects.inv > generating gallery... > Using Sphinx-Gallery to convert rst text blocks to markdown for .ipynb files. > generating gallery for auto_examples... > generating gallery for auto_examples/data... > [2Kgenerating gallery for auto_examples/numpy_operations... [ 25%] > plot_camera_numpy.py > [2Kgenerating gallery for auto_examples/numpy_operations... [ 50%] > plot_structuring_elements.py > [2Kgenerating gallery for auto_examples/numpy_operations... [ 75%] > plot_view_as_blocks.py > [2Kgenerating gallery for auto_examples/numpy_operations... [100%] > plot_footprint_decompositions.py > > [2Kgenerating gallery for auto_examples/color_exposure... [ 11%] > plot_rgb_to_gray.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 22%] > plot_rgb_to_hsv.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 33%] > plot_histogram_matching.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 44%] > plot_adapt_rgb.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 56%] > plot_ihc_color_separation.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 67%] > plot_regional_maxima.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 78%] > plot_log_gamma.py > [2Kgenerating gallery for auto_examples/color_exposure... [ 89%] > plot_equalize.py > [2Kgenerating gallery for auto_examples/color_exposure... [100%] > plot_tinting_grayscale_images.py > > [2Kgenerating gallery for auto_examples/edges... [ 8%] plot_contours.py > [2Kgenerating gallery for auto_examples/edges... [ 15%] plot_convex_hull.py > [2Kgenerating gallery for auto_examples/edges... [ 23%] plot_c
Bug#1058558: seqkit: FTBFS: make: *** [debian/rules:8: binary] Error 25
Source: seqkit Version: 2.3.1+ds-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=golang --with=golang --builddirectory=build # > --sourcedirectory=seqkit >dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=build >dh_autoreconf -O--buildsystem=golang -O--builddirectory=build >dh_auto_configure -O--buildsystem=golang -O--builddirectory=build >dh_auto_build -O--buildsystem=golang -O--builddirectory=build > cd build && go install -trimpath -v -p 8 > github.com/shenwei356/seqkit/benchmark github.com/shenwei356/seqkit/seqkit > github.com/shenwei356/seqkit/seqkit/cmd > src/github.com/shenwei356/seqkit/seqkit/cmd/pair.go:32:2: cannot find package > "github.com/pkg/errors" in any of: > /usr/lib/go-1.21/src/github.com/pkg/errors (from $GOROOT) > /<>/build/src/github.com/pkg/errors (from $GOPATH) > dh_auto_build: error: cd build && go install -trimpath -v -p 8 > github.com/shenwei356/seqkit/benchmark github.com/shenwei356/seqkit/seqkit > github.com/shenwei356/seqkit/seqkit/cmd returned exit code 1 > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/12/12/seqkit_2.3.1+ds-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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.
Bug#1058557: msolve: FTBFS: ! LaTeX Error: Unknown option 'hyperef' for package xcolor.
Source: msolve
Version: 0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd doc && pdflatex msolve-tutorial && \
> biber msolve-tutorial && \
> pdflatex msolve-tutorial && \
> pdflatex msolve-tutorial
> This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./msolve-tutorial.tex
> LaTeX2e <2023-11-01>
> L3 programming layer <2023-11-09>
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls
> Document Class: scrartcl 2023/07/07 v3.41 KOMA-Script document class (article)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlogo.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize11pt.clo)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifpdf.sty
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def)
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/locale/en/babel-english.tex)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amscls/amsthm.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xpatch/xpatch.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def))
> (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
>
> Package xcolor Warning: Package option `usenames' is obsolete and ignored on
> in
> put line 266.
>
>
> ! LaTeX Error: Unknown option 'hyperef' for package xcolor.
>
> For immediate help type H .
> ...
>
> l.266 \edef
>\Gin@driver{\Gin@driver}
> ?
> ! Emergency stop.
> ...
>
> l.266 \edef
>\Gin@driver{\Gin@driver}
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on msolve-tutorial.log.
> make[1]: *** [debian/rules:13: execute_after_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/msolve_0.6.1-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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.
Bug#1058556: binutils-or1k-elf: FTBFS: make[1]: *** [debian/rules:29: src] Error 1
Source: binutils-or1k-elf Version: 1.0.9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary -Dsrc -Bbld >debian/rules execute_before_dh_update_autotools_config > make[1]: Entering directory '/<>' > tar -xf /usr/src/binutils/binutils-*.tar.xz --transform='s|[^/]*|src|' > patch -dsrc -p1 < 0001-readelf-typos-in-user-messages.patch > patching file binutils/readelf.c > Reversed (or previously applied) patch detected! Assume -R? [n] > Apply anyway? [n] > Skipping patch. > 2 out of 2 hunks ignored -- saving rejects to file binutils/readelf.c.rej > make[1]: *** [debian/rules:29: src] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/binutils-or1k-elf_1.0.9_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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.
Bug#1058555: parallel: FTBFS: /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or directory
Source: parallel Version: 20221122+ds-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/src' > rm "/<>/debian/parallel/usr/bin"/sem || true > rm: cannot remove '/<>/debian/parallel/usr/bin/sem': No such > file or directory > ln -s parallel "/<>/debian/parallel/usr/bin"/sem > make[4]: Leaving directory '/<>/src' > Error: source file could not be loaded > /usr/bin/mkdir -p '/<>/debian/parallel/usr/share/doc/parallel' > /usr/bin/install -c -m 644 parallel.html env_parallel.html sem.html sql.html > niceload.html parallel_examples.html parallel_tutorial.html > parallel_book.html parallel_design.html parallel_alternatives.html > parcat.html parset.html parsort.html parallel.texi env_parallel.texi sem.texi > sql.texi niceload.texi parallel_examples.texi parallel_tutorial.texi > parallel_book.texi parallel_design.texi parallel_alternatives.texi > parcat.texi parset.texi parsort.texi parallel.rst env_parallel.rst sem.rst > sql.rst niceload.rst parallel_examples.rst parallel_tutorial.rst > parallel_book.rst parallel_design.rst parallel_alternatives.rst parcat.rst > parset.rst parsort.rst parallel.pdf > '/<>/debian/parallel/usr/share/doc/parallel' > /usr/bin/install -c -m 644 env_parallel.pdf sem.pdf sql.pdf niceload.pdf > parallel_examples.pdf parallel_tutorial.pdf parallel_book.pdf > parallel_design.pdf parallel_alternatives.pdf parcat.pdf parset.pdf > parsort.pdf ./parallel_cheat_bw.pdf parallel_options_map.pdf > '/<>/debian/parallel/usr/share/doc/parallel' > /usr/bin/install: cannot stat './parallel_cheat_bw.pdf': No such file or > directory > make[3]: *** [Makefile:459: install-docDATA] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/parallel_20221122+ds-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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.
Bug#1058553: node-js-sdsl: FTBFS: TypeError: Cannot set property constructor of [object Object] which has only a getter
Source: node-js-sdsl
Version: 4.1.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> debian/build_modules/ttypescript/bin/tsc src/index.ts --downlevelIteration
> --declaration --module commonjs --target es5 --outDir dist/cjs
> /<>/debian/build_modules/ttypescript/lib/loadTypescript.js:13
> function __() { this.constructor = d; }
> ^
>
> TypeError: Cannot set property constructor of [object Object] which has only
> a getter
> at new __
> (/<>/debian/build_modules/ttypescript/lib/loadTypescript.js:13:42)
> at __extends
> (/<>/debian/build_modules/ttypescript/lib/loadTypescript.js:14:84)
> at
> /<>/debian/build_modules/ttypescript/lib/loadTypescript.js:65:5
> at Object.
> (/<>/debian/build_modules/ttypescript/lib/loadTypescript.js:100:2)
> at Module._compile (node:internal/modules/cjs/loader:1356:14)
> at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
> at Module.load (node:internal/modules/cjs/loader:1197:32)
> at Module._load (node:internal/modules/cjs/loader:1013:12)
> at Module.require (node:internal/modules/cjs/loader:1225:19)
> at require (node:internal/modules/helpers:177:18)
>
> Node.js v18.19.0
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/node-js-sdsl_4.1.4-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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.
Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input
Source: science.js
Version: 1.9.3+dfsg-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> cat src/core/core.js src/core/ascending.js src/core/constants.js
> src/core/expm1.js src/core/functor.js src/core/hypot.js src/core/quadratic.js
> src/core/zeroes.js >> science.core.js
> cat src/lin/lin.js src/lin/decompose.js src/lin/cross.js src/lin/dot.js
> src/lin/length.js src/lin/normalize.js src/lin/determinant.js
> src/lin/gaussjordan.js src/lin/inverse.js src/lin/multiply.js
> src/lin/transpose.js src/lin/tridag.js >> science.lin.js
> cat src/stats/stats.js src/stats/bandwidth.js src/stats/distance.js
> src/stats/erf.js src/stats/phi.js src/stats/kernel.js src/stats/kde.js
> src/stats/kmeans.js src/stats/hcluster.js src/stats/iqr.js src/stats/loess.js
> src/stats/mean.js src/stats/median.js src/stats/mode.js
> src/stats/quantiles.js src/stats/variance.js src/stats/distribution.js
> src/stats/distribution/gaussian.js >> science.stats.js
> cat science.core.js science.lin.js science.stats.js >> science.v1.js
> uglifyjs < science.v1.js > science.v1.min.js
> node src/package.js > package.json
> node:internal/modules/package_json_reader:92
> throw error;
> ^
>
> SyntaxError: Error parsing /<>/package.json: Unexpected end of
> JSON input
> at parse ()
> at read (node:internal/modules/package_json_reader:79:16)
> at readPackage (node:internal/modules/package_json_reader:140:10)
> at readPackageScope (node:internal/modules/package_json_reader:157:19)
> at shouldUseESMLoader (node:internal/modules/run_main:77:15)
> at Function.executeUserEntryPoint [as runMain]
> (node:internal/modules/run_main:122:24)
> at node:internal/main/run_main_module:28:49 {
> path: '/<>/package.json'
> }
>
> Node.js v18.19.0
> make[2]: *** [Makefile:80: package.json] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/science.js_1.9.3+dfsg-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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.
Bug#1058551: git-buildpackage: FTBFS: make[2]: *** [Makefile:22: syntax-check] Error 1
Source: git-buildpackage Version: 0.9.32 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make > make[2]: Entering directory '/<>' > flake8 > ./tests/02_test_upstream_source_tar_unpack.py:58:20: E721 do not compare > types, for exact checks use `is` / `is not`, for instance checks use > `isinstance()` > make[2]: *** [Makefile:22: syntax-check] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/git-buildpackage_0.9.32_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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.
Bug#1058550: autopkgtest: FTBFS: make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1
Source: autopkgtest Version: 5.31.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231212 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > if type pyflakes3 >/dev/null 2>&1; then tests/pyflakes; else echo "pyflakes3 > not available, skipping"; fi > /<>/lib/autopkgtest_qemu.py:48:1: 'typing.List' imported but > unused > /<>/lib/testdesc.py:29:1: 'typing.Dict' imported but unused > /<>/lib/testdesc.py:29:1: 'typing.FrozenSet' imported but unused > /<>/lib/testdesc.py:29:1: 'typing.Union' imported but unused > /<>/tools/autopkgtest-build-qemu:41:1: 'typing.Any' imported but > unused > make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/12/12/autopkgtest_5.31.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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.
