Bug#1072136: marked as done (puddletag: FTBFS: dh_sphinxdoc: error: debian/python-behave-doc/usr/share/doc/python-behave-doc/html/_static/js/jquery-1.12.4.min.js is missing)
Your message dated Tue, 25 Jun 2024 05:49:54 + with message-id and subject line Bug#1072136: fixed in puddletag 2.4.0-1 has caused the Debian Bug report #1072136, regarding puddletag: FTBFS: dh_sphinxdoc: error: debian/python-behave-doc/usr/share/doc/python-behave-doc/html/_static/js/jquery-1.12.4.min.js is missing 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.) -- 1072136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:puddletag Version: 2.3.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --with python3,sphinxdoc --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:129: Building wheel for python3.11 with "build" module I: pybuild base:311: python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11 * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/puddlestuff copying puddlestuff/findfunc.py -> build/lib/puddlestuff copying puddlestuff/logger.py -> build/lib/puddlestuff copying puddlestuff/helperwin.py -> build/lib/puddlestuff copying puddlestuff/funcprint.py -> build/lib/puddlestuff copying puddlestuff/pluginloader.py -> build/lib/puddlestuff copying puddlestuff/about.py -> build/lib/puddlestuff copying puddlestuff/puddletag.py -> build/lib/puddlestuff copying puddlestuff/resource.py -> build/lib/puddlestuff copying puddlestuff/audio_filter.py -> build/lib/puddlestuff copying puddlestuff/translations.py -> build/lib/puddlestuff copying puddlestuff/constants.py -> build/lib/puddlestuff copying puddlestuff/actiondlg.py -> build/lib/puddlestuff copying puddlestuff/puddlesettings.py -> build/lib/puddlestuff copying puddlestuff/action_shortcuts.py -> build/lib/puddlestuff copying puddlestuff/functions.py -> build/lib/puddlestuff copying puddlestuff/shortcutsettings.py -> build/lib/puddlestuff copying puddlestuff/musiclib.py -> build/lib/puddlestuff copying puddlestuff/util.py -> build/lib/puddlestuff copying puddlestuff/m3u.py -> build/lib/puddlestuff copying puddlestuff/genres.py -> build/lib/puddlestuff copying puddlestuff/tagmodel.py -> build/lib/puddlestuff copying puddlestuff/loadshortcuts.py -> build/lib/puddlestuff copying puddlestuff/functions_dialogs.py -> build/lib/puddlestuff copying puddlestuff/puddleobjects.py -> build/lib/puddlestuff copying puddlestuff/__init__.py -> build/lib/puddlestuff copying puddlestuff/confirmations.py -> build/lib/puddlestuff creating build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/releasewidget.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/patterncombo.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/funcs.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/teststuff.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/artwork.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/action_dialogs.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/logdialog.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/tagsources.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/tagtools.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/previews.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/dirview.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/tagpanel.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/storedtags.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/__init__.py -> build/lib/puddlestuff/mainwin copying puddlestuff/mainwin/filterwin.py -> build/lib/puddlestuff/mainwin creating build/lib/puddlestuff/libraries copying puddlestuff/libraries/rhythmbox.py -> build/lib/puddlestuff/libraries copying puddlestuff/libraries/quodlibetlib.py -> build/lib/puddlestuff/libraries copying puddlestuff/libraries/__init__.py -> build/lib/puddlestuff/libraries creating build/lib/puddlestuff/audioinfo copying puddlestuff/audioinfo/wma.py -> build/lib/puddlestuff/audioinfo copying puddlestuff/audioinfo/apev2.py -> build/lib/puddlestuff/audioinfo copying puddlestuff/audioinfo/id3.py -> build/lib/puddlestuff/audioinfo copying
Bug#1072315: marked as done (puddletag 2.3.0-1)
Your message dated Tue, 25 Jun 2024 05:49:54 + with message-id and subject line Bug#1070971: fixed in puddletag 2.4.0-1 has caused the Debian Bug report #1070971, regarding puddletag 2.3.0-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.) -- 1070971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: puddletag Version: 2.3.0-1 Hello maintainer, puddletag won't run: ## [23:58:50] kkadmin@kk-6x3600:~> puddletag puddletag Version: 2.3.0 Locale: de_DE Traceback (most recent call last): File "/usr/bin/puddletag", line 352, in from puddlestuff.puddletag import MainWin File "/usr/lib/python3/dist-packages/puddlestuff/puddletag.py", line 14, in from . import mainwin File "/usr/lib/python3/dist-packages/puddlestuff/mainwin/__init__.py", line 4, in from . import dirview File "/usr/lib/python3/dist-packages/puddlestuff/mainwin/dirview.py", line 12, in from ..tagmodel import has_previews File "/usr/lib/python3/dist-packages/puddlestuff/tagmodel.py", line 32, in from .audio_filter import parse as filter_audio File "/usr/lib/python3/dist-packages/puddlestuff/audio_filter.py", line 183, in bool_expr.enablePackrat() File "/usr/lib/python3/dist-packages/pyparsing/util.py", line 265, in _inner return fn(*args, **kwargs) ^^^ File "/usr/lib/python3/dist-packages/pyparsing/core.py", line 1132, in enable_packrat ParserElement.packrat_cache = _FifoCache(cache_size_limit) # type: ignore[assignment] File "/usr/lib/python3/dist-packages/pyparsing/util.py", line 105, in __init__ keyring = [object()] * size ~~~^~ TypeError: can't multiply sequence by non-int of type 'Forward' [23:58:55] kkadmin@kk-6x3600:~> #--# After downgrading the python3-pyparsing package from version 3.1.2-1 to version 3.1.1-1 puddletag is running again. Greets klak --- End Message --- --- Begin Message --- Source: puddletag Source-Version: 2.4.0-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of puddletag, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated puddletag 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, 25 Jun 2024 01:25:25 -0400 Source: puddletag Architecture: source Version: 2.4.0-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 1070971 1072136 Changes: puddletag (2.4.0-1) unstable; urgency=medium . * New upstream release; Closes: #1070971, #1072136 * debian/control - bump Standards-Version to 4.6.2 (no changes needed) Checksums-Sha1: 3e0f5e761f3cf5706b9fad91d091f0b27fa94645 1950 puddletag_2.4.0-1.dsc 4b25348552085907434277420af9dd17aed75dd7 11440400 puddletag_2.4.0.orig.tar.xz b8f3fe0186b0194026840e1387a6f22a94f28638 4852 puddletag_2.4.0-1.debian.tar.xz 19bd02d5fbbc53dbb9c2103899bc9dbd3100e5d0 7568 puddletag_2.4.0-1_source.buildinfo Checksums-Sha256: 6db17f88032c27fb9d6cbfca027d10096bebb8457d8ad344dcde0d3bd4d06e93 1950 puddletag_2.4.0-1.dsc f335303bcc7596c15ebd0f0564875a8922dd78a3445b057e712f5c2d0391830d 11440400 puddletag_2.4.0.orig.tar.xz e6df40438a968c3c22b8945df9a9a851f570cb4bd2cd5c36071d14b4e984b0de 4852 puddletag_2.4.0-1.debian.tar.xz 04539ce7a7111e847a79e1514b3506e073020360d51bae9d55bf93c5b1de1a2c 7568 puddletag_2.4.0-1_source.buildinfo Files: aaac90f310685e5b8e19446eb66afed1 1950 sound optional puddletag_2.4.0-1.dsc 406256287f117f0ab8da44154b87840b 11440400 sound optional puddletag_2.4.0.orig.tar.xz 1c643762ca9a11c768a7b9a2fa4959cd 4852 sound optional puddletag_2.4.0-1.debian.tar.xz 01fedbbecc448d5f9c70078af23c1f79 7568 sound optional puddletag_2.4.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmZ6VNsACgkQh588mTgB qU8T+w//WgZCYdPE6zO6Ir4rVbfcpJM0+ZIdHMZP3CpZ4845T0LhyHIFA9guGe7c f/j420dD2T4i0RCFTfDxgsBcALjXfFUjsBiQLVf9yEFwzRb6hytpISxuC6Rh70NK
Bug#1070971: marked as done (puddletag: Puddletag fails to start after upgrading python3-pyparsing to 3.1.2-1 (+ workaround))
Your message dated Tue, 25 Jun 2024 05:49:54 + with message-id and subject line Bug#1070971: fixed in puddletag 2.4.0-1 has caused the Debian Bug report #1070971, regarding puddletag: Puddletag fails to start after upgrading python3-pyparsing to 3.1.2-1 (+ workaround) 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.) -- 1070971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: puddletag Version: 2.3.0-1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The new version of python3-pyparsing will prevent puddletag from running. See https://github.com/puddletag/puddletag/issues/884 However, it can be fixed by adding "ParserElement.enable_packrat()" to line 6 of /usr/lib/python3/dist-packages/puddlestuff/audio_filter.py as described here: https://github.com/puddletag/puddletag/pull/880 -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages puddletag depends on: ii libjs-sphinxdoc 7.2.6-7 ii python3 3.11.8-1 ii python3-acoustid1.3.0-1 ii python3-audioread 3.0.1-1 ii python3-certifi 2023.11.17-1 ii python3-charset-normalizer 3.3.2-1 ii python3-configobj 5.0.8-3 ii python3-idna3.6-2 ii python3-lxml5.2.1-1 ii python3-mutagen 1.46.0-2 ii python3-pyparsing 3.1.2-1 ii python3-pyqt5 5.15.10+dfsg-1+b1 ii python3-pyqt5.qtsvg 5.15.10+dfsg-1+b1 ii python3-pyqt5.sip 12.13.0-1+b1 ii python3-requests2.31.0+dfsg-1 ii python3-six 1.16.0-6 ii python3-unidecode 1.3.8-1 ii python3-urllib3 1.26.18-2 Versions of packages puddletag recommends: ii libchromaprint-tools 1.5.1-5 ii python3-levenshtein 0.25.1-3 Versions of packages puddletag suggests: pn quodlibet -- no debconf information --- End Message --- --- Begin Message --- Source: puddletag Source-Version: 2.4.0-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of puddletag, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated puddletag 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, 25 Jun 2024 01:25:25 -0400 Source: puddletag Architecture: source Version: 2.4.0-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 1070971 1072136 Changes: puddletag (2.4.0-1) unstable; urgency=medium . * New upstream release; Closes: #1070971, #1072136 * debian/control - bump Standards-Version to 4.6.2 (no changes needed) Checksums-Sha1: 3e0f5e761f3cf5706b9fad91d091f0b27fa94645 1950 puddletag_2.4.0-1.dsc 4b25348552085907434277420af9dd17aed75dd7 11440400 puddletag_2.4.0.orig.tar.xz b8f3fe0186b0194026840e1387a6f22a94f28638 4852 puddletag_2.4.0-1.debian.tar.xz 19bd02d5fbbc53dbb9c2103899bc9dbd3100e5d0 7568 puddletag_2.4.0-1_source.buildinfo Checksums-Sha256: 6db17f88032c27fb9d6cbfca027d10096bebb8457d8ad344dcde0d3bd4d06e93 1950 puddletag_2.4.0-1.dsc f335303bcc7596c15ebd0f0564875a8922dd78a3445b057e712f5c2d0391830d 11440400 puddletag_2.4.0.orig.tar.xz e6df40438a968c3c22b8945df9a9a851f570cb4bd2cd5c36071d14b4e984b0de 4852 puddletag_2.4.0-1.debian.tar.xz 04539ce7a7111e847a79e1514b3506e073020360d51bae9d55bf93c5b1de1a2c 7568 puddletag_2.4.0-1_source.buildinfo Files: aaac90f310685e5b8e19446eb66afed1 1950 sound optional puddletag_2.4.0-1.dsc 406256287f117f0ab8da44154b87840b 11440400 sound optional puddletag_2.4.0.orig.tar.xz 1c643762ca9a11c768a7b9a2fa4959cd 4852 sound optional
Processed: tagging 1074228
Processing commands for cont...@bugs.debian.org: > tags 1074228 + confirmed pending Bug #1074228 [odoo] odoo: CVE-2024-4367 – Arbitrary JavaScript execution in PDF.js Added tag(s) pending and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1074235 is forwarded to https://github.com/cvc5/cvc5/issues/10813, tagging 1074235 ...
Processing commands for cont...@bugs.debian.org: > forwarded 1074235 https://github.com/cvc5/cvc5/issues/10813 Bug #1074235 [src:cvc5] cvc5: CVE-2024-37794 CVE-2024-37795 Set Bug forwarded-to-address to 'https://github.com/cvc5/cvc5/issues/10813'. > tags 1074235 + upstream Bug #1074235 [src:cvc5] cvc5: CVE-2024-37794 CVE-2024-37795 Added tag(s) upstream. > tags 1074228 + upstream Bug #1074228 [odoo] odoo: CVE-2024-4367 – Arbitrary JavaScript execution in PDF.js Added tag(s) upstream. > tags 1074233 + upstream Bug #1074233 [src:slic3r-prusa] slic3r-prusa: CVE-2024-24686 CVE-2024-24685 CVE-2024-24684 CVE-2024-24584 CVE-2024-24583 CVE-2024-23951 CVE-2024-23950 CVE-2024-23949 CVE-2024-23948 CVE-2024-23947 CVE-2024-22181 CVE-2023-49600 CVE-2023-35953 CVE-2023-35952 CVE-2023-35951 CVE-2023-35950 CVE-2023-35949 Added tag(s) upstream. > tags 1074234 + upstream Bug #1074234 [src:scikit-learn] scikit-learn: CVE-2024-5206 Added tag(s) upstream. > tags 1074236 + upstream Bug #1074236 [src:node-ws] node-ws: CVE-2024-37890 Added tag(s) upstream. > forwarded 1074236 https://github.com/websockets/ws/issues/2230 Bug #1074236 [src:node-ws] node-ws: CVE-2024-37890 Set Bug forwarded-to-address to 'https://github.com/websockets/ws/issues/2230'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074228 1074233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074233 1074234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074234 1074235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074235 1074236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074136: marked as done (org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331))
Your message dated Tue, 25 Jun 2024 03:04:42 + with message-id and subject line Bug#1074136: fixed in org-mode 9.7.5+dfsg-1 has caused the Debian Bug report #1074136, regarding org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331) 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.) -- 1074136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: org-mode Version: 9.6.28+dfsg-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: clone -1 -2 Control: reassign -2 src:emacs 1:29.3+1-3 Hi There is a new vulnerability in Emacs Org mode. Details: https://www.openwall.com/lists/oss-security/2024/06/23/1 Upstream fix (in org-mode); https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f4cc61636947b5c2f0afc67174dd369fe3277aa8 Regards, Salvatore --- End Message --- --- Begin Message --- Source: org-mode Source-Version: 9.7.5+dfsg-1 Done: Nicholas D Steeves We believe that the bug you reported is fixed in the latest version of org-mode, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas D Steeves (supplier of updated org-mode 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: Mon, 24 Jun 2024 22:43:31 -0400 Source: org-mode Architecture: source Version: 9.7.5+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team Changed-By: Nicholas D Steeves Closes: 1074136 Changes: org-mode (9.7.5+dfsg-1) unstable; urgency=medium . * New upstream release that resolves CVE-2024-39331 (Closes: #1074136). * Rebase quilt series onto this release: - Drop 10-shebang.patch (unused) - Drop 20-links-unescaping.patch (unused) - Drop 0002-default-to-xprintidle.patch (merged upstream) * Migrate to debhelper-compat 13. * Declare Rules-Requires-Root: no. * Override "package-does-not-install-examples" and provide justification in debian/source/lintian-overrides. * Update my copyright years. * Declare Standards-Version: 4.7.0 (no changes required). Checksums-Sha1: ef9d22a4e61ef3b2271659d894d5c1ae05311abe 2014 org-mode_9.7.5+dfsg-1.dsc f830ed96f9346dc488ea6be1dcfbdc1015035497 1388780 org-mode_9.7.5+dfsg.orig.tar.xz 40ba525ab7909e0853523e8fb7633323b44e2bc0 16600 org-mode_9.7.5+dfsg-1.debian.tar.xz 04e413e24620a23c140a0e539b15f4f0f2220ba3 8255 org-mode_9.7.5+dfsg-1_amd64.buildinfo Checksums-Sha256: 4dc50fc2b71edfe31e869586029adc42d38a3509b7eb69fab89d30aaddc5edec 2014 org-mode_9.7.5+dfsg-1.dsc 0934da007a271c1bedc747c0f472448604e894de663cfd9b1822eacdacb87ac8 1388780 org-mode_9.7.5+dfsg.orig.tar.xz 1ef5c15eb50ef5a0cbd7878811ecb7093d9e8275b07dd80284f2a35daff6a7b7 16600 org-mode_9.7.5+dfsg-1.debian.tar.xz 35c35a2916b16917c6e18388f791ee863af505ce4f736d6359b5318a68b9ca44 8255 org-mode_9.7.5+dfsg-1_amd64.buildinfo Files: be4d3f704653197cf3d8d10393c9bb5a 2014 lisp optional org-mode_9.7.5+dfsg-1.dsc d95f9ee19d42b34566cc87df6d21c912 1388780 lisp optional org-mode_9.7.5+dfsg.orig.tar.xz 865218bb577b47b63e0cf3f0dd1f1c13 16600 lisp optional org-mode_9.7.5+dfsg-1.debian.tar.xz 733318d8f1585faed8ce460d36c1f92e 8255 lisp optional org-mode_9.7.5+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmZ6MU0ACgkQWogwR199 EGGcbw//bAVbUnruH15cXhW8T3rs4pALaawzwnGefTJclrr2QKjNgF15LSpbaxCu QnrXRBqSgIAd7wwK0DNriDU4zTcIMqBZIWJ0SEJM9/i9uW5FV50nr7kBlPfu23a7 HpgYdQlij3lOtDb+TVVQ97cyEzSC4O6iOHHNiAK38rK9t/TimLgKPhTxl2K8i1sN AniGuqnRB0n9p2ZGlXv/WROKwiImufuzqyO7S2iqFE0qqphpaTBPteB/XvNKPY7D qyKF06TwiqIVqwxy8z/kQy6hxFZ1/dVw5oir66P13Am3UDNPUyGE5k6T7g5IfmXn ugmfPz4rkj8BIP00ss79Q0zpFb9NYN1JMBu6VXmGBs7fURFHYO6xqj7BQtxZfTpu KkmPI7m9O8DpFWaM1l1L8pMw5S7NGnIFpvshfhATZgP5D54tSoLX5hiAguQYoY36 xuH0KGnjzsiSQNtSykwT84lrSL3vGOcP0Tf7OK9QwwSOALf0BCVHa9dIZ9BTyctJ 3uQutTdAYZ+HxkrGAfe2w43OMVoz4LXpldFGKn30fa7oIWQoWEgS7XuN1/jYxB4p vCHxb7xPEePgwGqoROtUw/J5oGJXnef1LpAQzpZL5XLqZJyEpjnf8m3vJN1LqSxb
Bug#1074243: sccache - please remove build-dependency on librust-counted-array-0.1+default-dev
Package: sccache Version: 0.8.1-3 Severity: serious x-debbugs-cc: n...@sail.ng sccache build-depends on librust-counted-array-0.1+default-dev which was recently removed from Debian. The removal request was filed by Blair Noctis who gave the reasoning. Please kindly remove rust-counted-array from unstable. It didn't see maintenance upstream for a long time, and is no longer used by other packages, either upstream or in Debian. Thank you. Investigating deeper, it seems that sccache replaced the counted-array crate with a simplified internal implementation a couple of years ago but the Debian package still has a build-dependency on it. I was able to succesfully test-build sccache with the build-dependency removed.
Bug#1074241: opensnitch can no longer be built on ppc64el.
Package: opensnitch Severity: serious Justification: rc policy - packages must be buildable within the same release. The build-dependencies for opensnitch are no longer satisfiable on ppc64el, because bpfcc no longer supports that architecture. package: opensnitch version: 1.5.8.1-1 architecture: any,all type: src status: broken reasons: - missing: pkg: package: golang-github-iovisor-gobpf-dev version: 0.2.0-6 architecture: all unsat-dependency: libbpfcc-dev:ppc64el depchains: - depchain: - package: opensnitch version: 1.5.8.1-1 architecture: any,all type: src depends: golang-github-iovisor-gobpf-dev:ppc64el Either this needs to be dealt with somehow such that opensnitch can be built on ppc64el again, or the ppc64el binaries for opensnitch need to be removed.
Bug#1074137: marked as done (org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331))
Your message dated Tue, 25 Jun 2024 01:04:54 + with message-id and subject line Bug#1074137: fixed in emacs 1:29.4+1-1 has caused the Debian Bug report #1074137, regarding org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331) 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.) -- 1074137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: org-mode Version: 9.6.28+dfsg-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: clone -1 -2 Control: reassign -2 src:emacs 1:29.3+1-3 Hi There is a new vulnerability in Emacs Org mode. Details: https://www.openwall.com/lists/oss-security/2024/06/23/1 Upstream fix (in org-mode); https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f4cc61636947b5c2f0afc67174dd369fe3277aa8 Regards, Salvatore --- End Message --- --- Begin Message --- Source: emacs Source-Version: 1:29.4+1-1 Done: Rob Browning We believe that the bug you reported is fixed in the latest version of emacs, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rob Browning (supplier of updated emacs 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, 24 Jun 2024 19:34:05 -0500 Source: emacs Architecture: source Version: 1:29.4+1-1 Distribution: unstable Urgency: medium Maintainer: Rob Browning Changed-By: Rob Browning Closes: 1074137 Changes: emacs (1:29.4+1-1) unstable; urgency=medium . * Merge upstream version 29.4. (Closes: 1074137) * Update debian/copyright for 29.4. Checksums-Sha1: c7d30866b705c8cdb7c826d3197e4b00828c1706 3132 emacs_29.4+1-1.dsc 004e7aa61b44ce33634eb1085299d206a90ad425 29301440 emacs_29.4+1.orig.tar.xz 03ac1694de1d5d24f32d2503b1e0d834b762a7ce 66228 emacs_29.4+1-1.debian.tar.xz Checksums-Sha256: ae2326af2af49f6279a394f5e90feaa27e37ab7ba11ef599e284b443588fc3d3 3132 emacs_29.4+1-1.dsc eef69e3a3c2098f9b41e0b284406ecc815373aafa5f7e2acdc99214a9bf34061 29301440 emacs_29.4+1.orig.tar.xz 0ce67a5df85a4ba505d469e6bee8c794476849f8bcd4b682cbed8810bb39cf31 66228 emacs_29.4+1-1.debian.tar.xz Files: e28374e9d298b2cb3c92c937334a4399 3132 editors optional emacs_29.4+1-1.dsc ec9687fa8d0c6bdd36a2b239b08e2116 29301440 editors optional emacs_29.4+1.orig.tar.xz 884dec9454f5b4cceb64857839d491cb 66228 editors optional emacs_29.4+1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEPTFSABe5ruOuhW+97vEWxVpaQvEFAmZ6EnoVHHJsYkBkZWZh dWx0dmFsdWUub3JnAAoJEO7xFsVaWkLxPRkP/2g7jhUbUlrLCsvo84qkUd4PSmvo FkrImH41ynfG3cs53aM4jFovTKgQXzoeDdUQp+kCVj0RjdGE2cj8w8qh/nMnuI6/ LN0rIuOC0enr1RMUv+g1zLpmCyxtTifTfiGw9413D4tBPtcBZpoeJudTTDE+jNYW KeBGtLLhkUErdOAWamyS2GW3660g5B0339lT+8A2Pj9idjYrdR1fdlfdHcNl0aS3 TPLUmwQ8a/UdfnkuYcDu814JblhWGpp8B+Oct+lyjn6moQ1y95ecGIlbvGvzjWwi E6UM1lr/ISNxtHc5rOgbKz0dvpvhpn3N6HtlAnrMahD0i4yw/qKvabBd0G+EiAf8 AB8aFTO2aCZ+kzgMMg6PdIjMDLvweMMscOigqbUtoldhFaYMaN/pBshQOBtF+Hmo M3/Yp5WxtXGfISlqrnAbwq7l+nFIpwuhK7kwGAqzBeTzUiHJfpZ3gyEswdlqT+fc O/upvVo1Hg84veMpIR9j8bPFGV1GwhD0Y01j80sdqsYRPhJEB9oB0Z3YwEt2miSL XfOuITx66kY3KHFGpCcLkJJoYup1V8yMbnyWZcyCI1HIg8tHCIzBAH59DTKx1tkq e7iUwg7RlpTuGJSXIZcD2EVqRTUTIBIPVljzcJ31QM5SfQE4tkW/T6cvMbWUlvpx 3mFc+CZvRRtsDLLx =M9kw -END PGP SIGNATURE- pgpZ_xfemz8aY.pgp Description: PGP signature --- End Message ---
Bug#1074085: marked as done (python3-proto-plus missing Breaks+Replaces with nanopb)
Your message dated Tue, 25 Jun 2024 00:50:05 + with message-id and subject line Bug#1074085: fixed in python-proto-plus 1.24.0-1 has caused the Debian Bug report #1074085, regarding python3-proto-plus missing Breaks+Replaces with nanopb 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.) -- 1074085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-proto-plus Version: 1.23.0-3 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + nanopb Hi, we're almost done with the file conflict between python3-proto-plus and nanopb. Thanks for taking the time to work on a proper solution. Now the python3-proto-plus package still shares files with the nanopb package in trixie and this breaks smooth upgrades. We really are taking over files now. When you upgrade python3-proto-plus and have nanopb installed, nanopb should be upgraded as well to avoid that file conflict. Thus please add: Breaks: nanopb (<< 0.4.8-2~) Replaces: nanopb (<< 0.4.8-2~) Helmut --- End Message --- --- Begin Message --- Source: python-proto-plus Source-Version: 1.24.0-1 Done: Yogeswaran Umasankar We believe that the bug you reported is fixed in the latest version of python-proto-plus, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yogeswaran Umasankar (supplier of updated python-proto-plus 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: Mon, 24 Jun 2024 20:00:00 + Source: python-proto-plus Architecture: source Version: 1.24.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Yogeswaran Umasankar Closes: 1074085 Changes: python-proto-plus (1.24.0-1) unstable; urgency=medium . * Updated to new upstream version 1.24.0. * d/control: Added Breaks: and Replaces: in the package python3-proto-plus. (Closes: #1074085) Checksums-Sha1: 095690e0d6a0608c4b2c4b5d17bd8a17defef921 2375 python-proto-plus_1.24.0-1.dsc 161a5b3bc4d852741de8cc87a101ea545152afd8 100401 python-proto-plus_1.24.0.orig.tar.gz 625fc90538f5a804a2c4efb120bc98c9926905f5 4420 python-proto-plus_1.24.0-1.debian.tar.xz fde48450de0037234d1c7ff383cc7e8509871585 8037 python-proto-plus_1.24.0-1_arm64.buildinfo Checksums-Sha256: 49fddf746d5e57610fefe071b95be2d4fd9ab8d24f2ffe7bf5ae780b8766786f 2375 python-proto-plus_1.24.0-1.dsc 680e3e8db383c05bd5a225186b96a3958bfc1addcaea84505d36644f7863822e 100401 python-proto-plus_1.24.0.orig.tar.gz b25804ada1fa379137321ac8770a0a32b38049d5753d8b6dd17817d180725916 4420 python-proto-plus_1.24.0-1.debian.tar.xz e84b691303971601e27b3e0d43af892919804764154ed51d9f746d85aab3b9a6 8037 python-proto-plus_1.24.0-1_arm64.buildinfo Files: 51d113f9595ca4ad7e8ae51740c0bdc8 2375 python optional python-proto-plus_1.24.0-1.dsc fd2d0395d522e0d7bcc796e96db13266 100401 python optional python-proto-plus_1.24.0.orig.tar.gz 4e9bc9db583bc6678593a9d027e4f1ad 4420 python optional python-proto-plus_1.24.0-1.debian.tar.xz d4a9cddd2c64a4a7e34cf8eaf9dea9e5 8037 python optional python-proto-plus_1.24.0-1_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/qLi99g13V/he2oYtIOKvyeCVXsFAmZ6EJIACgkQtIOKvyeC VXuFkxAA2E8yWgkZtC6x2LoYDsYa/pdROwpjtlzgjeN8rmDpnBPOyACsKXIsaRUY pmi9wqn2ucJEXkDYFKoY/Q6eDnJHx9yGgxw1uRZ50vyOLNKvBzqHYk4bAiQbvD31 fX2kywgJuM1E4txtLdmmktT+daRYgSBtn375/g9I2j9Tbzo1OaJL6VqZ+GVcstmE jUshFzd+f1C6aH6YUvlVgZb5jUCG5Vifj3SuhBiWZCJQO+qZqEOJg9miyP8HrPcC aaLqf/KPQ2oBXDIplEhkHyL1KRqzHvvQy86o2087tID9awoAeZots+nSwds2lkdw JoTGD2Jyp1RwdYuDosu8WEHKZmVnvr20qua8usby70HHE7uL9adNdOz3eXSmhV6d UoVqp372sXtzj3+jS4AbLMZmL8rCAKs8qJj0hxXTpdNVsY+vEdnPSzR3VDUYrL5h dVk/E25ECeReXIRF8Jtn0+WMeKrxDWGR+sq59ADEPNco2UuNvhUwcXwATedlgxzV wP3VUny+uGwz5RBvL3DbwzNtzc4oBu723Sg90k4wuLn1jP0O637/BumBNXWssjHA moCBG4XYqXhrG8zUWnjRGAjdsFLDkxeVFbja5rEBp+n1WNYRTlLurTRRmgNT/LAN BITphUn21JvzmE/obA1o5bUoHJ3XAcpuwav+zsz4ixu+Cjz8OFo= =ifjN -END PGP SIGNATURE- pgpODXJSYB9Le.pgp Description: PGP signature --- End Message ---
Bug#1074216: marked as done (kitty FTBFS with Python 3.12 as default)
Your message dated Mon, 24 Jun 2024 23:50:51 +
with message-id
and subject line Bug#1074216: fixed in kitty 0.35.2-1
has caused the Debian Bug report #1074216,
regarding kitty FTBFS with Python 3.12 as default
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.)
--
1074216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kitty
Version: 0.35.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=kitty=0.35.1-1%2Bb1
...
==
FAIL: test_ssh_leading_data (kitty_tests.ssh.SSHKitten.test_ssh_leading_data)
(sh='python3')
--
Traceback (most recent call last):
File "/<>/kitty/launcher/../../kitty_tests/ssh.py", line 167, in
test_ssh_leading_data
self.ae(pty.screen_contents(), 'UNTAR_DONE\nld:before_tarfile')
pty =
script = 'print("ld:" + leading_data.decode("ascii")); raise SystemExit(0);'
self =
sh = 'python3'
tdir = '/tmp/tmpj2ma30as'
AssertionError: 'bootstrap.py:214: DeprecationWarning: Pyt[180 chars]file' !=
'UNTAR_DONE\nld:before_tarfile'
- bootstrap.py:214: DeprecationWarning: Python 3.14 will, by default, filter
extra
- cted tar archives and reject files or modify their metadata. Use the filter
argu
- ment to control this behavior.
UNTAR_DONE
ld:before_tarfile
--
Ran 144 tests in 68.976s
FAILED (failures=1, skipped=2)
[31mError[39m: Some tests failed!
make[1]: *** [debian/rules:60: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: kitty
Source-Version: 0.35.2-1
Done: Maytham Alsudany
We believe that the bug you reported is fixed in the latest version of
kitty, 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 1074...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Maytham Alsudany (supplier of updated kitty 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: Mon, 24 Jun 2024 23:12:10 +0800
Source: kitty
Architecture: source
Version: 0.35.2-1
Distribution: unstable
Urgency: medium
Maintainer: Nilesh Patra
Changed-By: Maytham Alsudany
Closes: 1074216
Changes:
kitty (0.35.2-1) unstable; urgency=medium
.
* New upstream version 0.35.2 (Closes: #1074216)
Checksums-Sha1:
33aff1043791158ce637767a8b5cac79165789a2 3229 kitty_0.35.2-1.dsc
330ff139845c095c446a0c29d5ea876fc35baf7e 8116620 kitty_0.35.2.orig.tar.gz
f0dc3b86d27d3276d6350d5708676c3f52840eb5 43984 kitty_0.35.2-1.debian.tar.xz
356254c51586cdcbe64b74240690c62bbb87fceb 16504 kitty_0.35.2-1_amd64.buildinfo
Checksums-Sha256:
50529abc3724d07262f77aac5e538166f59c0dceee1655caf50487266576fcb2 3229
kitty_0.35.2-1.dsc
35ecf63999a056ff691abab94a6f82328f4e432c8e229a69d02c25466be4398f 8116620
kitty_0.35.2.orig.tar.gz
4ad3183d5cfb6b529d9f6f213e62546115e3f9925a5429f0cbf0fcafed05af62 43984
kitty_0.35.2-1.debian.tar.xz
7c1246a040a0e9949b2c8671acf315ba2151946427996754043fddafb75d6874 16504
kitty_0.35.2-1_amd64.buildinfo
Files:
9f6697ce9ab6eade9194e29a86278c7f 3229 x11 optional kitty_0.35.2-1.dsc
40e65f06ff161b1379f4133d7d43daa8 8116620 x11 optional kitty_0.35.2.orig.tar.gz
f4030a5591153422ae0c387313461c69 43984 x11 optional
kitty_0.35.2-1.debian.tar.xz
3a9ff68f40dac7259cd4f66321a86203 16504 x11 optional
kitty_0.35.2-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJMBAEBCgA2FiEESl/RzRFQh8wD3DXB1ZeJcgbF8H8FAmZ6ANoYHG1heXRoYTh0
aGVkZXZAZ21haWwuY29tAAoJENWXiXIGxfB/P6YP+wR+1UwfTFYDX6P99pfaO1HE
FuorlW463BbcEpkJQhUwNi8StOciFD2XBaH3KQj7iMevwgq8L0o05RrufJjiQjk+
lTAwaqSKl68ISk2KxmSGSTpTuAS3tjuIQnE9pEFA3Dv+jMvK3+skwk8ZKklixQOn
mGRVagE9ylYeyYfbG0Ldm+1cdpc/K16ZHg1LBWz5l84ZpihlHIfVaU+rb8qugt+n
CHks5jIYavERjdqn2cvAj2mqBToU8UZdHqqjeJYzOXnGYL+7z32dd8dBQoQAFThU
1eyyumz3Diz/s95Jw2BLcrWCL1LUOpu/HQWNRN7JjpNgaJPHZW7kLjUK1633VUlx
sywphb1YlG+YiCelbaUIt+neLvPaW6nJkscqpyn/mB1gg9nMYsltM4TcNAAgoz3k
JAYQCTJmv6K6S8J6ybd1c2Y9C5oEpeJqh5U0tWH/f2hHmYZn1k/ssZ+8cSHwzZtY
Bug#1074165: marked as done (libkscreenlocker6 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet)
Your message dated Mon, 24 Jun 2024 23:20:21 + with message-id and subject line Bug#1074165: fixed in kscreenlocker 6.1.0-2 has caused the Debian Bug report #1074165, regarding libkscreenlocker6 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet 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.) -- 1074165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libkscreenlocker6 Version: 6.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libkscreenlocker5 libkscreenlocker6 has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet is contained in the packages * libkscreenlocker5 * 5.20.5-1+deb11u1 as present in bullseye * 5.27.11-1 as present in trixie|unstable * 5.27.5-2 as present in bookworm * libkscreenlocker6/6.1.0-1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: kscreenlocker Source-Version: 6.1.0-2 Done: Patrick Franz We believe that the bug you reported is fixed in the latest version of kscreenlocker, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Franz (supplier of updated kscreenlocker 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, 25 Jun 2024 00:49:04 +0200 Source: kscreenlocker Architecture: source Version: 6.1.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Closes: 1074165 Changes: kscreenlocker (6.1.0-2) experimental; urgency=medium . [ Patrick Franz ] * Add missing Breaks+Replaces for libkscreenlocker6 against libkscreenlocker5 (Closes: #1074165). * Removes the Breaks against kwin-common. To be evaluated. Checksums-Sha1: e8e55b8845591c5268feeb21312a4465fc237f57 3233 kscreenlocker_6.1.0-2.dsc a5e0bb4378f41950a01079f136b083c433b42c98 20104 kscreenlocker_6.1.0-2.debian.tar.xz 34b943cc022c391660b4f47696879d3e4348f5fb 13036 kscreenlocker_6.1.0-2_source.buildinfo Checksums-Sha256: 49fd4b9ed3869a5287cad21d34c6279ba7c589b2c2b8d68c1817386f41ca1f5b 3233 kscreenlocker_6.1.0-2.dsc f16e3d9c668a0a90c80cb16d42657f3ac5e9deeb40170c48086650a3e1b13acd 20104 kscreenlocker_6.1.0-2.debian.tar.xz 3da98d7b6d2032f74f53084715b32777ad17d6b94b19036c96f1800a54df2aef 13036 kscreenlocker_6.1.0-2_source.buildinfo Files: e735866670a5a2528866dd26445b0982 3233 libs optional kscreenlocker_6.1.0-2.dsc e42abac4aeff2c9545814a3f0579df53 20104 libs optional kscreenlocker_6.1.0-2.debian.tar.xz 7d0430fe458d78fa1e6b3ffc17e98f44 13036 libs optional kscreenlocker_6.1.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmZ59/MACgkQnp96YDB3 /laoMQ//dfWtclbPQSY6rb+K93sOVZZOmqDmGRIJsLsASJYAEL2pYXIP7yICt19q TgsgdEpN+A8Cy5LChPnEj55TJ2hKnCxUV3skEabcqCfqSL8919xQdcj+wwtzBEBl 2goDFiFnu66BHnFj12p4EOtHcSlWgyII76RaMkpd9qVGdGiHwc3/2cQ4518VJvtN W679eZAdoctXDdP2U/2sK6KO4FZPzgLrFtn/CtlXTEtkiiq6CAKMjXks/oLrLhJc nF6JnbhxrElg7tlBJscfzxLy1FxCAfLMx7dGEC2k51VGRU7J3Yuo2eNpAPBS8WEs pRvIaZJGhW+WiQVIAuN3o321Or2FmQsoGeo4RF3FKOOBB21CL5G5LmeRHH233F5J 7N2zD3dWgDc1hkwEC0HBkG5wnhKItatFaYAriVESXkr8jqln8qXtwigXfll73D7Z iUcCLih5JffqvnRrRWCioXUg4W24+m04u0/5fMTO9MsR5QjQl48bMKc1zDTfCDwN mRT7TBG7KR1R3DYV00gAUB1T0YR8wK4bYuPVFJLQ5yzbSOKsMmCgQqZtVHLmhA4L t2nY4XIw94o/M0l/8/UuGGqUSC8IHQdygRDhiFwN6SoJlrQ5ytBQpfEdYIjSseGL
Bug#1073831: marked as done (xfsdump:FATAL ERROR: could not find a current XFS handle library)
Your message dated Mon, 24 Jun 2024 22:57:54 + with message-id and subject line Bug#1073831: fixed in xfsprogs 6.8.0-2.2 has caused the Debian Bug report #1073831, regarding xfsdump:FATAL ERROR: could not find a current XFS handle library 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.) -- 1073831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xfsdump Version: 3.1.11-0.2 Severity: serious Dear Maintainer, now xfsdump has one ftbfs issue[0]: ``` checking for uuid_compare... no checking for uuid_compare in -luuid... yes checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking for pthread_mutex_init in -lpthread... yes checking ncurses.h usability... yes checking ncurses.h presence... yes checking for ncurses.h... yes checking for initscr in -lncurses... yes checking for bad glibc/ncurses header interaction... ok checking xfs/xfs.h usability... yes checking xfs/xfs.h presence... yes checking for xfs/xfs.h... yes checking xfs/handle.h usability... yes checking xfs/handle.h presence... yes checking for xfs/handle.h... yes checking for open_by_fshandle in -lhandle... no FATAL ERROR: could not find a current XFS handle library. Install or upgrade the XFS library package. Alternatively, run "make install-dev" from the xfsprogs source. make[1]: *** [Makefile:78: include/builddefs] Error 1 ``` The full buildd log please to see [1]. [0]: https://buildd.debian.org/status/package.php?p=xfsdump [1]: https://buildd.debian.org/status/fetch.php?pkg=xfsdump=riscv64=3.1.11-0.2=1718694953=0 -- Regards, -- Bo YU signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: xfsprogs Source-Version: 6.8.0-2.2 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of xfsprogs, 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 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated xfsprogs 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: Wed, 19 Jun 2024 23:33:58 +0200 Source: xfsprogs Architecture: source Version: 6.8.0-2.2 Distribution: unstable Urgency: medium Maintainer: XFS Development Team Changed-By: Chris Hofstaedtler Closes: 1073831 Changes: xfsprogs (6.8.0-2.2) unstable; urgency=medium . * Non-maintainer upload. * Fix installation of files into xfslibs-dev (Closes: #1073831) Checksums-Sha1: d684bac728187bcc2b7098eae5ffbcd8dc9050cf 2192 xfsprogs_6.8.0-2.2.dsc f2c3de94afbce3281d1cf2cb0e01d091e0a767a6 14676 xfsprogs_6.8.0-2.2.debian.tar.xz 09b62b733552d58fafbed0cb63d6dd59b62aa676 7459 xfsprogs_6.8.0-2.2_arm64.buildinfo Checksums-Sha256: f0a6efe3c078b23cbb5f340a096e2850942778e77af1389c08e0d6026e50e91b 2192 xfsprogs_6.8.0-2.2.dsc 2e778d52565ef6c3691b483545e0c226c513049f9fe2d3553bd52dd1cefed1af 14676 xfsprogs_6.8.0-2.2.debian.tar.xz e6b0bcd7104d8576a47483db25ea572cf89447e928828a077d038e396c9e7519 7459 xfsprogs_6.8.0-2.2_arm64.buildinfo Files: fb5563c0996268f7600741f1ab3408fe 2192 admin optional xfsprogs_6.8.0-2.2.dsc a63a8fe47b7095b46f0a0bf8682d1251 14676 admin optional xfsprogs_6.8.0-2.2.debian.tar.xz ba5172afe40fbac73990db0c18712a75 7459 admin optional xfsprogs_6.8.0-2.2_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmZzVkkACgkQXBPW25MF LgNmIw//VMGQjxhHC0SjSU8s66PETN5Q0etCW82y76pDl6Lek/UuFhKteAUvudCw YJU0XR3X7k1LF6K/m/63ucSxq7HDx22Ce+GoICTcyqbbvwTm924p/GoQ9Tk0YLUu wkoYjEBUBnHLcDbNfJBy5vESmUvnh48rfBkp/mfGHmSUx/y1mFpYpVpmSi9edSuj 6YFFIW3mzYX5bPwA7a/PTIcCmncsWUapn1PYCWBkOBf48rvD2p7Gv5g2rO3YfYZ+ m3eRS8+UiTSZ0PJ0A5kHbaNdqDsHeJoaF5VeEEvqYfYEyYcq+Ud5y5HC5cGngapO INtp02mXzWBPKjGuIyo3kY2H1SXRQbr3IbmxxblN4v2FwWApx4psaL33k0OEyCSc gQEekkfKdkkLhnLiSUfk4L4rvfvW7ZI5O3KZIuO6h+NGrWyfJb4lkON6Puq4J/JB /awJFaM1l7thCUVWltBOI8IpWsJGjiI3AOLyAM91DD0GiNQE5KiZVPm4qPAsoR/3 LCyF/0ydzfVTS21dJPbpBWPxKK1s39I04HRN11ncr9++dF5efh0CejLdp3AuNPAt ykwaOnhE8tcE0Nh0WMNsNHMKbsj+5BN4XV5d6AmIzw6wwtSphXOC34XI4MUwFp//
Processed: Bug#1074165 marked as pending in kscreenlocker
Processing control commands: > tag -1 pending Bug #1074165 [libkscreenlocker6] libkscreenlocker6 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet Added tag(s) pending. -- 1074165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073931: marked as done (composer: security update broke feature branches)
Your message dated Mon, 24 Jun 2024 22:47:25 + with message-id and subject line Bug#1073931: fixed in composer 2.0.9-2+deb11u4 has caused the Debian Bug report #1073931, regarding composer: security update broke feature branches 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.) -- 1073931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: composer Version: 2.0.9-2+deb11u3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: h...@users.noreply.github.com, t...@security.debian.org Dear Maintainer, yesterday unattended-upgrades installed version 2.0.9-2+deb11u3 composer including security fixes for bugs #1073125 and #1073126. Unfortunately, patch backporting introduces a major issue, so that any feature branch (branch not in master|main|latest|next|current|support|tip|trunk|default|develop) of a git repository checkout is unable to run composer install with the following error: ``` PHP Fatal error: Uncaught TypeError: Argument 1 passed to Symfony\Component\Process\Process::fromShellCommandline() must be of the type string, array given, called in /usr/share/php/Composer/Util/ProcessExecutor.php on line 112 and defined in /usr/share/php/Symfony/Component/Process/Process.php:193 Stack trace: #0 /usr/share/php/Composer/Util/ProcessExecutor.php(112): Symfony\Component\Process\Process::fromShellCommandline() #1 /usr/share/php/Composer/Util/ProcessExecutor.php(65): Composer\Util\ProcessExecutor->doExecute() #2 /usr/share/php/Composer/Package/Version/VersionGuesser.php(279): Composer\Util\ProcessExecutor->execute() #3 /usr/share/php/Composer/Package/Version/VersionGuesser.php(161): Composer\Package\Version\VersionGuesser->guessFeatureVersion() #4 /usr/share/php/Composer/Package/Version/VersionGuesser.php(71): Composer\Package\Version\VersionGuesser->guessGitVersion() #5 /usr/share/php/Composer/Package/Loader/RootPackageLoader.php(81): Composer\Package\Version\VersionGuesser->guessVersion() #6 /usr/share/php/Com in /usr/share/php/Symfony/Component/Process/Process.php on line 193 ``` It seems the backporting didn't properly test or notice that applying upstreams security fixes did turn some string values into arrays [1, 2] which aren't compatible with the string signature of the symfony/process version you ship. Simple reproducer: Run composer install on the checkout of the feature-branch of https://github.com/htto/debian-oldstable-composer This basically broke all our feature branches' composer installation, locally and in any CI/CD pipeline. I hope this gets adressed quickly. Kind regards Heiko [1] https://sources.debian.org/patches/composer/2.0.9-2%2Bdeb11u3/0016-Merge-pull-request-from-GHSA-47f6-5gq3-vx9c.patch/#L22 [2] https://sources.debian.org/patches/composer/2.0.9-2%2Bdeb11u3/0015-Merge-pull-request-from-GHSA-v9qv-c7wm-wgmf.patch/#L43 -- System Information: Debian Release: 11.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages composer depends on: ii jsonlint 1.8.3-2 ii php-cli 2:7.4+76 ii php-common 2:76 ii php-composer-ca-bundle 1.2.9-1 ii php-composer-semver 3.2.4-2 ii php-composer-spdx-licenses 1.5.5-2 ii php-composer-xdebug-handler 1.4.5-1 ii php-json-schema 5.2.10-2 ii php-psr-log 1.1.3-2 ii php-react-promise2.7.0-2 ii php-symfony-console 4.4.19+dfsg-2+deb11u4 ii php-symfony-filesystem 4.4.19+dfsg-2+deb11u4 ii php-symfony-finder 4.4.19+dfsg-2+deb11u4 ii php-symfony-process 4.4.19+dfsg-2+deb11u4 ii php7.4-cli [php-cli] 7.4.33-1+deb11u5 Versions of packages composer recommends: ii git1:2.30.2-1+deb11u2 ii unzip 6.0-26+deb11u1 Versions of packages composer suggests: pn fossil pn mercurial ii php-zip 2:7.4+76 ii php7.4-zip [php-zip] 7.4.33-1+deb11u5 pn subversion -- no debconf information --- End Message --- --- Begin Message --- Source: composer Source-Version: 2.0.9-2+deb11u4 Done: David Prévot We believe that the bug you reported is fixed in the latest version of composer, which is due to be installed in the Debian FTP archive. A summary of the changes between
Bug#1074165: marked as pending in kscreenlocker
Control: tag -1 pending Hello, Bug #1074165 in kscreenlocker 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/qt-kde-team/kde/kscreenlocker/-/commit/162ac2ad16ae8167a59793dcf8921898788f846c Add missing Breaks+Replaces for libkscreenlocker6 against libkscreenlocker5 (Closes: #1074165). (this message was generated automatically) -- Greetings https://bugs.debian.org/1074165
Bug#1051564: marked as done (stk: FTBFS with RtAudio 6)
Your message dated Mon, 24 Jun 2024 22:06:52 +
with message-id
and subject line Bug#1051564: fixed in stk 5.0.1+dfsg-1
has caused the Debian Bug report #1051564,
regarding stk: FTBFS with RtAudio 6
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.)
--
1051564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stk
Version: 4.6.2+dfsg-2
Severity: important
Tags: ftbfs patch
Dear Maintainer,
stk ftbfs with RtAudio 6 (as currently found in experimental):
a small excerpt from the build-logs:
```
RtWvOut.cpp:110:11: error: ‘RtAudioError’ does not name a type; did you mean
‘RtAudioErrorType’?
110 | catch ( RtAudioError ) {
| ^~~~
| RtAudioErrorType
RtWvOut.cpp:111:18: error: ‘error’ was not declared in this scope; did you mean
‘perror’?
111 | handleError( error.what(), StkError::AUDIO_SYSTEM );
| ^
| perror
make[3]: *** [Makefile:79: RtWvOut.o] Error 1
make[3]: *** Waiting for unfinished jobs
RtWvIn.cpp: In constructor ‘stk::RtWvIn::RtWvIn(unsigned int, stk::StkFloat,
int, int, int)’:
RtWvIn.cpp:89:11: error: ‘RtAudioError’ does not name a type; did you mean
‘RtAudioErrorType’?
89 | catch ( RtAudioError ) {
| ^~~~
| RtAudioErrorType
RtWvIn.cpp:90:18: error: ‘error’ was not declared in this scope; did you mean
‘perror’?
90 | handleError( error.what(), StkError::AUDIO_SYSTEM );
| ^
| perror
```
attached is a patch that fixes the FTBFS (but is otherwise untested).
no debdiff this time, sorry.
cheers.
Description: Fix FTBFS with RtAudio 6
replace try/catch with checking error-codes
Author: IOhannes m zmölnig
Origin: Debian
Forwarded: no
Last-Update: 2023-09-09
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: stk-4.6.2+dfsg/src/RtWvIn.cpp
===
--- stk-4.6.2+dfsg.orig/src/RtWvIn.cpp
+++ stk-4.6.2+dfsg/src/RtWvIn.cpp
@@ -83,11 +83,8 @@ RtWvIn :: RtWvIn( unsigned int nChannels
unsigned int size = bufferFrames;
RtAudioFormat format = ( sizeof(StkFloat) == 8 ) ? RTAUDIO_FLOAT64 :
RTAUDIO_FLOAT32;
- try {
-adc_.openStream( NULL, , format, (unsigned
int)Stk::sampleRate(), , , (void *)this );
- }
- catch ( RtAudioError ) {
-handleError( error.what(), StkError::AUDIO_SYSTEM );
+ if(adc_.openStream( NULL, , format, (unsigned
int)Stk::sampleRate(), , , (void *)this )) {
+handleError(adc_.getErrorText(), StkError::AUDIO_SYSTEM );
}
data_.resize( size * nBuffers, nChannels );
Index: stk-4.6.2+dfsg/src/RtWvOut.cpp
===
--- stk-4.6.2+dfsg.orig/src/RtWvOut.cpp
+++ stk-4.6.2+dfsg/src/RtWvOut.cpp
@@ -104,11 +104,8 @@ RtWvOut :: RtWvOut( unsigned int nChanne
RtAudioFormat format = ( sizeof(StkFloat) == 8 ) ? RTAUDIO_FLOAT64 :
RTAUDIO_FLOAT32;
// Open a stream and set the callback function.
- try {
-dac_.openStream( , NULL, format, (unsigned
int)Stk::sampleRate(), , , (void *)this );
- }
- catch ( RtAudioError ) {
-handleError( error.what(), StkError::AUDIO_SYSTEM );
+ if(dac_.openStream( , NULL, format, (unsigned
int)Stk::sampleRate(), , , (void *)this )) {
+handleError( dac_.getErrorText(), StkError::AUDIO_SYSTEM );
}
data_.resize( size * nBuffers, nChannels );
Index: stk-4.6.2+dfsg/projects/demo/demo.cpp
===
--- stk-4.6.2+dfsg.orig/projects/demo/demo.cpp
+++ stk-4.6.2+dfsg/projects/demo/demo.cpp
@@ -259,11 +259,8 @@ int main( int argc, char *argv[] )
parameters.deviceId = dac.getDefaultOutputDevice();
parameters.nChannels = data.channels;
unsigned int bufferFrames = RT_BUFFER_SIZE;
-try {
- dac.openStream( , NULL, format, (unsigned
int)Stk::sampleRate(), , , (void *) );
-}
-catch ( RtAudioError& error ) {
- error.printMessage();
+if(dac.openStream( , NULL, format, (unsigned
int)Stk::sampleRate(), , , (void *) )) {
+ std::cerr << dac.getErrorText() << std::endl;
goto cleanup;
}
}
@@ -279,11 +276,8 @@ int main( int argc, char *argv[] )
// If realtime output, set our callback function and start the dac.
#if defined(__STK_REALTIME__)
if ( data.realtime ) {
-try {
- dac.startStream();
-}
-catch ( RtAudioError ) {
- error.printMessage();
+if(dac.startStream()) {
Processed: merging 1069317 1074226
Processing commands for cont...@bugs.debian.org: > merge 1069317 1074226 Bug #1069317 [libvamp-hostsdk3v5] FTBFS: tests failed Bug #1074226 [libvamp-hostsdk3v5] sonic-visualiser: FTBFS on armel/armhf Added tag(s) pending. Merged 1069317 1074226 > thanks Stopping processing here. Please contact me if you need assistance. -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 1074226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1074226
Processing commands for cont...@bugs.debian.org: > affects 1074226 sonic-visualiser Bug #1074226 [libvamp-hostsdk3v5] sonic-visualiser: FTBFS on armel/armhf Added indication that 1074226 affects sonic-visualiser > thanks Stopping processing here. Please contact me if you need assistance. -- 1074226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070450: marked as done (qm-dsp: autopkgtest regression on arm64, ppc64el and s390x)
Your message dated Mon, 24 Jun 2024 21:47:13 +
with message-id
and subject line Bug#1070450: fixed in qm-dsp 1.7.1-9
has caused the Debian Bug report #1070450,
regarding qm-dsp: autopkgtest regression on arm64, ppc64el and s390x
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.)
--
1070450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qm-dsp
Version: 1.7.1-8
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
qm-dsp currently fails to migrate due to autopkgtest failures on arm64,
ppc64el and s390x.
https://ci.debian.net/packages/q/qm-dsp/testing/arm64/46236204/
112s for t in test-mathutilities test-window test-fft test-pvoc test-resampler
test-medianfilter; do echo "Running $t"; valgrind -q ./"$t" || exit 1; done
112s Running test-mathutilities
114s Running 11 test cases...
114s
114s ␛[1;32;49m*** No errors detected
114s ␛[0;39;49mRunning test-window
115s Running 9 test cases...
115s
115s ␛[1;32;49m*** No errors detected
115s ␛[0;39;49mRunning test-fft
116s Running 21 test cases...
116s
116s ␛[1;32;49m*** No errors detected
117s ␛[0;39;49mRunning test-pvoc
118s Running 2 test cases...
118s TestPhaseVocoder.cpp(188): ␛[1;31;49merror: in "TestFFT/overlapping":
absolute value of phase[cmp_i] - phaseExpected2[cmp_i]{1.5297327490291485e-07}
exceeds 9.9995e-08␛[0;39;49m
118s TestPhaseVocoder.cpp(191): ␛[1;31;49merror: in "TestFFT/overlapping":
absolute value of unw[cmp_i] - unwExpected2[cmp_i]{1.5297327493613011e-07}
exceeds 9.9995e-08␛[0;39;49m
118s
118s ␛[1;31;49m*** 2 failures are detected in the test module "Master Test
Suite"
118s ␛[0;39;49mmake: *** [Makefile:13: all] Error 1
I've added a hint to get the t64 changes into testing.
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: qm-dsp
Source-Version: 1.7.1-9
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
qm-dsp, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
qm-dsp 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, 24 Jun 2024 22:36:56 +0200
Source: qm-dsp
Architecture: source
Version: 1.7.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 1070450
Changes:
qm-dsp (1.7.1-9) unstable; urgency=medium
.
* Slightly relax float-equality test in testsuite (Closes: #1070450)
* Bump standards version to 4.7.0
Checksums-Sha1:
706675a66f0c97274e2896c3a2068d941212a842 2373 qm-dsp_1.7.1-9.dsc
47938c313d1a92c850aa8c75dcca64f565c13e33 8044 qm-dsp_1.7.1-9.debian.tar.xz
Checksums-Sha256:
4b6289638ba032f52e6d369af663e752a6910531b53e3cac535abefef5352965 2373
qm-dsp_1.7.1-9.dsc
54707552bac5a37b7146c3f1f8c851c8e326c5314280d29bc056daf03bdec3e9 8044
qm-dsp_1.7.1-9.debian.tar.xz
Files:
85362b36b52f380b4dcdd512bd599638 2373 sound optional qm-dsp_1.7.1-9.dsc
e1e9b2aa8bd0b47352ee74494999eb3e 8044 sound optional
qm-dsp_1.7.1-9.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmZ52aUWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+OFYEACVD9TL2LggztCBdX6HkEzAcEEA
8IItkp2n9S/+Lnk6j5CvBldb2gQDuzhTA6UIMrqt0DzHNKB9m2RxVlWvfs+BqaWL
NuE5jTApc8J3szoi7L0Sjz6Newi/DG+Fbo2xISy/cPhVdeBIgakJ94avSVhADc7g
giPSHbfYJ5HLOLmuUPs1enCCvxzMoS1UwcwkJgQOKXTmHOEDGL19AE9cNOy1gBtL
9dK+s1TddY19f2T0RoVSVTIWvBofhYD6NXqksvxXrZj2eOzvSmoO7fS4dJmKqyq3
wVn/ywvPMF6y/FRLUPW9E5FuEOI9RQxWixk8+LYmOhHZt9nHc+ZrU4PJGYOF4NQP
E4WA4yQklSn7xY0NUw/NwI7p5BAzmRv3Zqs486t1ntNC0a9UI66Bb6zJ61lj25lV
oXqn0iHihcHol726EfuJohv+N2w3YcTfVmfh0nKauDDXHJ3fwM0nmMX1y4FRK6bg
RAOrd+S4InMZJBr884cJmhMlrCUzjQivZanLWQnhmZzQCS2r9nZ3Z9Qq+FSfSsxp
GyvkRb9epTbY24d9k4yRHmqlP//St7y4N5QI2DVB94n6lGfjQMasSqZNfacIDIMQ
ZT0NttyEO4/xI2tgjunegu874abVeU3OzI7zJ82PeM0oK8N27xdOSbBaz1e2QCgu
WYG3qdK6ReP13qVkOg==
=q/zi
-END PGP SIGNATURE-
pgpX8XbQsJNp6.pgp
Description: PGP signature
--- End Message
Bug#1070447: marked as done (sdpa: dependency generation does not account for t64 changes)
Your message dated Mon, 24 Jun 2024 21:49:00 +
with message-id
and subject line Bug#1070447: fixed in sdpa 7.3.18-1
has caused the Debian Bug report #1070447,
regarding sdpa: dependency generation does not account for t64 changes
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.)
--
1070447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sdpa
Version: 7.3.16+dfsg-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Dependencies on libmumps-seq are produced using ${mumps-seq:Version}
which does not include the changes from the t64 transition. Please adopt
the dependency generation accordingly.
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: sdpa
Source-Version: 7.3.18-1
Done: Makoto Yamashita
We believe that the bug you reported is fixed in the latest version of
sdpa, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Makoto Yamashita (supplier of updated sdpa
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, 08 May 2024 09:00:00 +0900
Source: sdpa
Architecture: source
Version: 7.3.18-1
Distribution: unstable
Urgency: low
Maintainer: Makoto Yamashita
Changed-By: Makoto Yamashita
Closes: 1070447
Changes:
sdpa (7.3.18-1) unstable; urgency=low
.
* New upstream
+ Change MUMPS from 5.5.1 to 5.6.2 (Closes: 1070447)
* Update Standards-Version to 4.7.0
.
[ Bastian Germann ]
* Build with compiler dpkg flags
* Add missing BSD-3-clause license
Checksums-Sha1:
c01340f0552e52359c8302c3a84521e75c4941a1 1743 sdpa_7.3.18-1.dsc
24b54d0ae0f1db90fd934ce641814b4a219a6f12 304833 sdpa_7.3.18.orig.tar.gz
d6d08facc2626cbb3ef25effc78485bf15794ccc 5828 sdpa_7.3.18-1.debian.tar.xz
fee63ea6009d5c0635e2efc6e4c4e0cd46542f01 16068 sdpa_7.3.18-1_source.buildinfo
Checksums-Sha256:
efa88a09f4dc589d6a2494c8052eff13040f4065bd27c7c5951f01deafb02b46 1743
sdpa_7.3.18-1.dsc
6fe0cb81ce731345180787c90e3ffdda19184ec67bc7b9d0f80d87c420cb5647 304833
sdpa_7.3.18.orig.tar.gz
159b14935cd6a80e31df34e521c1754889c5fd196b6d9f243de800a1a36b2403 5828
sdpa_7.3.18-1.debian.tar.xz
f2eb7f8186061ad21854d37e2e29eacdc7303bd76123992e46b92bcd6da52718 16068
sdpa_7.3.18-1_source.buildinfo
Files:
a5a56901660ff408aaa52290bf228831 1743 math optional sdpa_7.3.18-1.dsc
ec67c6514156aca67793b9b15400712f 304833 math optional sdpa_7.3.18.orig.tar.gz
207c623ea5b97a07e5cf7797d64d8958 5828 math optional sdpa_7.3.18-1.debian.tar.xz
7e921b5665ee984fa3a2bb5b1892e9fe 16068 math optional
sdpa_7.3.18-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmZ54ScQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFNBBC/9TwbKxVpxYxVSOu5Vgd8SMfHxVbD1ZXjCs
XJzi59b5CnDBio9JCYrgnqCoa7ydKTiN603aA4QTEPNibhk3NE0I9yz80fwLZtPF
c6/dZPgIXY+s6zpXi/mjG3IxBtSo5w9IBOo1+OTk84SaDWrqjS7OSH7mDGBVbrT6
dRoXxWkFxKsdELXOrgYZa3FM/QRivgjl+mbWnCgVaNcyiWFw3OtKSJPBPgR/cgt8
GL+r35NZe0ADpHfEWrkzRwmcVaG36eDHQ2tAlcboQ4yRTcWDsi6xkkTbaoVjZCGR
sWv8Vl6mMtmip1L0i/SkUgo03l3aNOXjewYzglntzeXw1E5dJxMM8ubx0LozyN57
schYDyyxJ73u/XWD42qHNMf8caeMAPm+BK5xE5hmdQXJdTHOT3HhTH9GnsANwcF/
ulzkd/ebCGK1u9cMoEHvc9SighuoDjEIgOQbmeCI3gGvRURJekJ10pe0xJTQNP7k
fcpAaZpZxnsMaShsu5nE+vZqOiBYtRk=
=9Hgl
-END PGP SIGNATURE-
pgpp_NH0mCjtc.pgp
Description: PGP signature
--- End Message ---
Bug#1059672: marked as done (syndication-domination: autopkgtest failure with Python 3.12)
Your message dated Mon, 24 Jun 2024 21:49:45 + with message-id and subject line Bug#1059672: fixed in syndication-domination 1.0-3 has caused the Debian Bug report #1059672, regarding syndication-domination: autopkgtest failure 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.) -- 1059672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: syndication-domination Version: 1.0-2 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer syndication-domination's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/s/syndication-domination/testing/amd64/ 24s autopkgtest [20:10:09]: test autodep8-python3: [--- 24s Testing with python3.12: 24s Traceback (most recent call last): 24s File "", line 1, in 24s ModuleNotFoundError: No module named 'syndom' 24s autopkgtest [20:10:09]: test autodep8-python3: ---] --- End Message --- --- Begin Message --- Source: syndication-domination Source-Version: 1.0-3 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of syndication-domination, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated syndication-domination 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: Mon, 24 Jun 2024 16:43:39 -0400 Source: syndication-domination Built-For-Profiles: noudeb Architecture: source Version: 1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jeremy Bícha Closes: 1059672 Changes: syndication-domination (1.0-3) unstable; urgency=medium . [ Jeremy Bícha ] * Add patch to facilitate building with alternative python3 versions * Build for all suppported Python3 versions (Closes: #1059672) . [ Andreas Tille ] * Switch Build-Depends: libpython3-dev → python3-all-dev Checksums-Sha1: 9d4ff3985456b692ab788cb82fb59b4cfe9afbc2 2214 syndication-domination_1.0-3.dsc 535ba1aa9c175c2d923510aa91b1ed6824771a15 14512 syndication-domination_1.0-3.debian.tar.xz 82683d9df08939ca76fd2bbb01886699fd68c5c7 7650 syndication-domination_1.0-3_source.buildinfo Checksums-Sha256: a6ee3ab30157e0941edb4a1a8f31b6e005e7fdf8342aed79db510040e08f3cc9 2214 syndication-domination_1.0-3.dsc 49acc397a55370179c1bc9d365fee0792a34a05a5d3f756dfbf63ac18c295aff 14512 syndication-domination_1.0-3.debian.tar.xz 97f6655398f1bc7f6481ce81cbabcb99f32df9a1fea0282762f88f46771091da 7650 syndication-domination_1.0-3_source.buildinfo Files: 174248a9407102fb526d49b26d00ccec 2214 devel optional syndication-domination_1.0-3.dsc bb0160b3fc2ce490f22c9166ace90bf3 14512 devel optional syndication-domination_1.0-3.debian.tar.xz 8539e2a83012f242f728355291561b86 7650 devel optional syndication-domination_1.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmZ52ssACgkQ5mx3Wuv+ bH1kyxAAviiiS76wvmGkBTjXTenO1U2TELleFq4dpBdzXzXFgwXqTHjD/RL+02k7 NkFxtpsA2G6LW9xc5W7xJpe1hHjTs1NYCH/Av9Yn03AGZ7XEXT7PxLOWFcX3sxON G+m2M4LvXvGGmyuHNh84e/34W6CIwjFE9OzdycMkFfWLdDi3zyOuBcNQjC60PBPZ LEfYKaMjGRbDJCpQxZKZUeXP/tEQQYX/Wowi49vT2uATgK9TqZ0XQ7VGqMm7JyJE rS3TJSNcZ3DRxS04tmaSok8EWSDnt//aVLrRLDPHv9Y/98tVvT2NSFUloFy71fep G1bF9LLHnVR2KRB9rZfOO6RoeKI738cNIzRdueSA/Nu21y9Z0fvUSRFG9ISF9cUB hpVSjpXNcGew68ylb9t4mGO5VI6Cxj29RQQMtpMCBV2af8AZuxQuxRdA//XekxTj eYyHqqfBAI9vpEsb3mbwThecJnj4XOtNNgXFbmBdghdDOnuA7T84ToPvobY5c+zD ScKHwDep9YlaPhC3DLSSiXcZH9I0UPOaYo43mTbf1ugQiyzwQB76gH/R7DqBmAWZ SCG+HhOYxyf1E7asAcVZhIU2Q9k2tGdu0d5oH51vWrhV5EuGS8q0AeWQmS/Vlj5a kmSORYaa8sgzbU1h7UaSv3b0eqtnqkCWgZ77a0/F5uC5iHnrEw0= =pLgI -END PGP SIGNATURE- pgp4EAscEgK5O.pgp Description: PGP signature --- End Message ---
Processed: reassign 1074226 to libvamp-hostsdk3v5
Processing commands for cont...@bugs.debian.org: > reassign 1074226 libvamp-hostsdk3v5 Bug #1074226 [sonic-visualiser] sonic-visualiser: FTBFS on armel/armhf Bug reassigned from package 'sonic-visualiser' to 'libvamp-hostsdk3v5'. No longer marked as found in versions sonic-visualiser/4.5.2-2. Ignoring request to alter fixed versions of bug #1074226 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1074226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merging 1069317 1074226
Processing commands for cont...@bugs.debian.org: > merge 1069317 1074226 Bug #1069317 [libvamp-hostsdk3v5] FTBFS: tests failed Unable to merge bugs because: affects of #1074226 is '' not 'sonic-visualiser' Failed to merge 1069317: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 1074226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1069317 to libvamp-hostsdk3v5
Processing commands for cont...@bugs.debian.org: > reassign 1069317 libvamp-hostsdk3v5 Bug #1069317 [libvamp-sdk2v5] FTBFS: tests failed Bug reassigned from package 'libvamp-sdk2v5' to 'libvamp-hostsdk3v5'. Ignoring request to alter found versions of bug #1069317 to the same values previously set Ignoring request to alter fixed versions of bug #1069317 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1069317
Processing commands for cont...@bugs.debian.org: > affects 1069317 sonic-visualiser Bug #1069317 [libvamp-sdk2v5] FTBFS: tests failed Added indication that 1069317 affects sonic-visualiser > thanks Stopping processing here. Please contact me if you need assistance. -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072934: shadowsocks-libev: Consider removing the package
On Mon, 10 Jun 2024 11:55:30 -0400 Boyuan Yang wrote: > Following the previous communication in March, I am considering to take action > and remove related packages in the ss-libev ecosystem. Package > shadowsocks-libev > will be removed together with simple-obfs. Hi Boyuan, I don't know what previous communication you are referring to, but I support your proposal! shadowsocks-libev has been deprecated upstream for quite a while in favour of shadowsocks-rust, and while this isn't an issue for me personally, the fact that the package builds only with MbedTLS 2.x and fails to build with 3.6 (which I'm trying to transition to) kinda bothers me. Hence, if there were reasons to remove shadowsocks-libev from the archive, now there is one more :) Thanks again for your efforts! Bye.
Bug#1073560: Reverting "xshared: Print protocol numbers if --numeric was given" breaks firewalld autopkgtest
Looping in Eric (firewalld upstream), to make him aware of this issue
and gather his input.
Michael
Am 17.06.24 um 22:16 schrieb Jeremy Sowden:
On 2024-06-17, at 15:57:05 +0200, Michael Biebl wrote:
Source: iptables
Version: 1.8.10-4
Severity: serious
The cherry-pick of the commit 34f085b1607364f4eaded1140060dcaf965a2649
Revert "xshared: Print protocol numbers if --numeric was given" breaks
firewalld, as seen in
https://ci.debian.net/packages/f/firewalld/testing/amd64/47810213/
firewalld is very susceptible to changes of the output and command
line interface of iptables. See an older issue
https://github.com/firewalld/firewalld/issues/1112
Filing with RC severity, so the package doesn't migrate to testing
(the debci results should prevent that, but this is just to make
doubly sure)
This change of iptables afaics has landed in a stable release
(bookworm). Do we really want to revert it again and make all users of
--numeric have to update again?
Hi. Let me explain my understanding of the current situation. I appre-
ciate that you probably know most of this already, but I just want to
avoid any confusion.
Upstream made a change that affected the output of protocols in listings
in the presence of the `--numeric` flag. Previously, they were still
output by name, after the change they were output by number. This was
released upstream in 1.8.9 and made its way into Bookworm.
This change broke stuff. As a result of a bug-report:
https://bugzilla.netfilter.org/show_bug.cgi?id=1729
upstream reverted the change in commit 34f085b16073 ("Revert "xshared:
Print protocol numbers if --numeric was given""). This is where things
currently stand upstream: in the next release (1.8.11), the original
behaviour will be restored.
A report was also created in the BTS:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067733
In response, I applied the upstream commit and uploaded it to unstable.
I have a draft bookworm-pu bug-report that I had intended to send
requesting that this change go into Bookworm to minimize the time before
the old behaviour is restored. Obviously, I will hold off while we
discuss this. :)
What do you propose? The firewalld test-suite was updated to work with
the new output; however, other tools were not, and upstream reverted the
change because there were no compelling reasons for it and it had caused
breakage in those tools. As things stand, the old behaviour will be re-
stored. Would you rather wait for the next upstream release? Are you
suggesting that we ask upstream to revert 34f085b16073? Or do you have
something else in mind?
J.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processed: retitle 1072131 to swiftlang FTBFS with glibc 2.38
Processing commands for cont...@bugs.debian.org: > retitle 1072131 swiftlang FTBFS with glibc 2.38 Bug #1072131 [src:swiftlang] swiftlang: FTBFS: swift-corelibs-foundation/CoreFoundation/Base.subproj/CoreFoundation_Prefix.h:194:1: error: static declaration of 'strlcpy' follows non-static declaration Changed Bug title to 'swiftlang FTBFS with glibc 2.38' from 'swiftlang: FTBFS: swift-corelibs-foundation/CoreFoundation/Base.subproj/CoreFoundation_Prefix.h:194:1: error: static declaration of 'strlcpy' follows non-static declaration'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073128: [Pkg-clamav-devel] Bug#1073128: clamav: unaligned access on armhf architecture
On 2024-06-13 09:34:14 [+0200], Gianfranco Costamagna wrote:
> Hello, in Ubuntu, where the kernel is configured to forbid unaligned accesses
> on armhf, the package FTBFS
> (this should be reproducible also on some Debian buildd machines, this is why
> I'm reporting as serious severity)
Isn't ARMv6+ double of unaligned access? armhf requires VFP so that
should be something later. Or am I wrong here?
> example of failure:
> https://launchpadlibrarian.net/734963041/buildlog_ubuntu-oracular-armhf.clamav_1.3.1+dfsg-3ubuntu1_BUILDING.txt.gz
…
> The following patch makes sure the unaligned access is fixed:
>
> Description: resolve armhf failure to build from source.
Instead of arguing with me, you could forward it directly to upstream
and give a pointer to apply whatever upsteams did.
> Author: Vladimir Petko
> --- a/libclamav/special.c
> +++ b/libclamav/special.c
> @@ -48,7 +48,8 @@
>
> int cli_check_mydoom_log(cli_ctx *ctx)
> {
> -const uint32_t *record;
> +const uint32_t record[16];
> +const uint32_t mask = 0x;
please get rid of mask and add your data pointer here.
> uint32_t check, key;
> fmap_t *map = ctx->fmap;
> unsigned int blocks = map->len / (8 * 4);
> @@ -59,14 +60,20 @@
> if (blocks > 5)
> blocks = 5;
>
> -record = fmap_need_off_once(map, 0, 8 * 4 * blocks);
> -if (!record)
> +// returns unaligned memory block
> +const char* data = fmap_need_off_once(map, 0, 8 * 4 * blocks);
> +if (!data)
> return CL_CLEAN;
> +
> while (blocks) { /* This wasn't probably intended but that's what the
> current code does anyway */
> -if (record[--blocks] == 0x)
> +unsigned int offset = --blocks;
> +offset *=sizeof(uint32_t);
> +// safe (but slow) on unaligned memory
> +if (!memcmp([offset], , sizeof(uint32_t)))
> return CL_CLEAN;
something like
| while (blocks) { /* This wasn't probably intended but that's what the
current code does anyway */
| uint32_t local;
|
| memcpy(, [--blocks * sizeof(uint32_t)], sizeof(uint32_t));
| if (local == 0x)
| return CL_CLEAN;
I am halfway tempted to suggest a packed-wrapper but this would be best
to consult upstream first.
> }
> -
> +// copy into aligned array to perform bit operations
> +memcpy(record, data, sizeof(record));
> key = ~be32_to_host(record[0]);
> check = (be32_to_host(record[1]) ^ key) +
> (be32_to_host(record[2]) ^ key) +
Sebastian
Bug#1074228: odoo: CVE-2024-4367 – Arbitrary JavaScript execution in PDF.js
Package: odoo Version: 14.0.0+dfsg.2-7+deb11u1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: t...@debian.org, Debian Security Team Hi, See details of vulnerability at: https://codeanlabs.com/blog/research/cve-2024-4367-arbitrary-js-execution-in-pdf-js/ Note that I am not currently using the Debian version of the Odoo package, but I noticed this issue when investigating the possibility of switching from the Odoo-provided package. All versions currently in Debian seem to be affected by this, as they embed version 2.2.228 of PDFjs: https://sources.debian.org/src/odoo/14.0.0%2Bdfsg.2-7%2Bdeb11u1/addons/web/static/lib/pdfjs/build/pdf.js/#L126 https://sources.debian.org/src/odoo/16.0.0%2Bdfsg.2-2/addons/web/static/lib/pdfjs/build/pdf.js/#L126 This vulnerability has been corrected in 4.2.67, alternatively there seems to be a simple workaround described in: https://github.com/mozilla/pdf.js/discussions/18168 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.12-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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
Bug#1074145: marked as done (numexpr FTBFS with more than 8 cores)
Your message dated Mon, 24 Jun 2024 19:28:10 +
with message-id
and subject line Bug#1074145: fixed in numexpr 2.10.1-2
has caused the Debian Bug report #1074145,
regarding numexpr FTBFS with more than 8 cores
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.)
--
1074145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numexpr
Version: 2.10.1-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/pydata/numexpr/issues/490
https://buildd.debian.org/status/fetch.php?pkg=numexpr=loong64=2.10.1-1=1719162095=0
https://buildd.debian.org/status/fetch.php?pkg=numexpr=powerpc=2.10.1-1=1719162022=0
...
==
ERROR: test_max_threads_unset
(numexpr.tests.test_numexpr.test_threading_config.test_max_threads_unset)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.11_numexpr/build/numexpr/tests/test_numexpr.py",
line 1134, in test_max_threads_unset
subprocess.check_call([sys.executable, '-c', script])
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3.11', '-c', "import
os\nif 'NUMEXPR_MAX_THREADS' in os.environ:
os.environ.pop('NUMEXPR_MAX_THREADS')\nif 'OMP_NUM_THREADS' in os.environ:
os.environ.pop('OMP_NUM_THREADS')\nimport numexpr\nassert(numexpr.nthreads <=
8)\nexit(0)"]' returned non-zero exit status 1.
--
Ran 5538 tests in 7.326s
FAILED (errors=1)
...
--- End Message ---
--- Begin Message ---
Source: numexpr
Source-Version: 2.10.1-2
Done: Antonio Valentino
We believe that the bug you reported is fixed in the latest version of
numexpr, 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 1074...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Valentino (supplier of updated numexpr
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: Mon, 24 Jun 2024 18:25:24 +
Source: numexpr
Architecture: source
Version: 2.10.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Antonio Valentino
Closes: 1074145
Changes:
numexpr (2.10.1-2) unstable; urgency=medium
.
* debian/patches:
- New 0002-Fix-test_max_threads_unset.patch (Closes: #1074145).
Checksums-Sha1:
4b3c1b2610bac79dffe8bf2b7c23f89a128e4fda 2255 numexpr_2.10.1-2.dsc
f0f4934bbc77ffc347362041e74595c2edc2f378 8388 numexpr_2.10.1-2.debian.tar.xz
8ed50eb9def2f0a0f324e30af2562410ce52daf7 7654 numexpr_2.10.1-2_amd64.buildinfo
Checksums-Sha256:
8cdfded26f631ceeb4fff095603f314f55fc40f44c3a1d067634d6f8af1a0cbb 2255
numexpr_2.10.1-2.dsc
7bea9973ee036020ef9a19cc55fb288258d647192524284da6d8e78665b96138 8388
numexpr_2.10.1-2.debian.tar.xz
7bb79a6770ddefcaf14b010c15d1cbcb189f52d255575d621af739c234298368 7654
numexpr_2.10.1-2_amd64.buildinfo
Files:
d5f2c05bd12959acdfab859e18ce7069 2255 python optional numexpr_2.10.1-2.dsc
1b1e6a6a7c8d041328ef5502962a6079 8388 python optional
numexpr_2.10.1-2.debian.tar.xz
861ac97170faf60c0092de5f2e78908b 7654 python optional
numexpr_2.10.1-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJRBAEBCgA7FiEEO3DyCaX/1okDxHLF6/SKslePmBIFAmZ5u1gdHGFudG9uaW8u
dmFsZW50aW5vQHRpc2NhbGkuaXQACgkQ6/SKslePmBIstQ/+Jd9iDL+NY7VYArZS
8P3tWWv6uFqC0YuwVlHmfXEgxle9V8apOZUh7e8r3DyqT0yOylWoDXKmO7iV1vMb
tNOz5a1ptM5HN28wIhcCsM+9O28XKAGFIomet4VKodyhiAd3B/6Nc/t0SUw3kmSp
/foYkBFUWkSm/DN1/mE2bS2+fr721m5KCdbZ798XSpO5+8+Yp4O3hugqoAmHowyF
FAFn+dU0pwxPR9qnzKpAeB1QhimdDA/3CAyRXe/Geo3y/OyIXBLRpiWc2qPH45z0
FKsN6vOX3VE/KdvgbqWzLQR2q8CdVnE69vWi38sZ6mH+j2hojMxCEF4QDl9LBY7T
ChzRrf6n+3/V+Rw5ALmopWGznUjMmPVs5r4DibuFFQqW99r4+TiAUI4FMlprl1H+
zD75/mwjGNp5CD/Q80zW20Z/v4iHj/uppylwTRwzxMiesc89Nnk3SA4uYo1CHkE6
LS6BQo16fubPcD00ixHhVpPMYrf6Wytk6+tdj5cHWhe7r6V4Kcs3lmXkF9Evelte
L9oUbUMpK07vWF+UmQAaZ5xFUzTYxHqF45ylrQ1fqJu1VXRLKRQcqXmUA/xgiYwd
Processed: [bts-link] source package pgtt
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package pgtt > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1073801 (http://bugs.debian.org/1073801) > # Bug title: postgresql-16-pgtt: ships > /usr/share/doc/postgresql-doc-16/extension/README.md.gz > # * https://github.com/darold/pgtt/pull/51 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1073801 + fixed-upstream Bug #1073801 [postgresql-16-pgtt] postgresql-16-pgtt: ships /usr/share/doc/postgresql-doc-16/extension/README.md.gz Added tag(s) fixed-upstream. > usertags 1073801 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1073801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074227: goldencheetah: Unsatisfiable build-dependencies
Package: goldencheetah Version: 1:3.5-5 Severity: serious X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package has unsatisfiable build-dependencies, specifically libqt5widgets5 and libqt5concurrent5. These packages have been superseded by libqt5widgets5t64 and libqt5concurrent5t64 respectively. Build-depending on them is neither necessary nor recommended as the corresponding packages are pulled automatically by qtbase5-dev. -- Regards Patrick Franz
Bug#1074226: sonic-visualiser: FTBFS on armel/armhf
Package: sonic-visualiser Version: 4.5.2-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package FTBFS on armel/armhf is therefore stuck on unsatisfiable dependencies. See https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser=armel=4.5.2-2%2Bb3=1713251413=0 and https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser=armhf=4.5.2-2%2Bb3=1713249425=0 -- Regards Patrick Franz
Bug#1074224: crossfire FTBFS with Python 3.12 as default
Source: crossfire
Version: 1.75.0-6
Severity: serious
Tags: ftbfs
Forwarded:
https://sourceforge.net/p/crossfire/crossfire-server/ci/472dd26ac74419baa0e6373cb04e095437e994c6/
https://buildd.debian.org/status/fetch.php?pkg=crossfire=arm64=1.75.0-6%2Bb3=1719233376=0
...
cfpython_archetype.c:136:5: note: (near initialization for
‘Crossfire_ArchetypeType.tp_vectorcall_offset’)
cjson.c: In function ‘encode_unicode’:
cjson.c:700:9: error: implicit declaration of function ‘PyUnicode_AS_UNICODE’;
did you mean ‘PyUnicode_AsUCS4’? [-Werror=implicit-function-declaration]
700 | s = PyUnicode_AS_UNICODE(unicode);
| ^~~~
| PyUnicode_AsUCS4
cjson.c:700:7: warning: assignment to ‘Py_UNICODE *’ {aka ‘unsigned int *’}
from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
700 | s = PyUnicode_AS_UNICODE(unicode);
| ^
cjson.c:701:12: error: implicit declaration of function ‘PyUnicode_GET_SIZE’;
did you mean ‘PyDict_GET_SIZE’? [-Werror=implicit-function-declaration]
701 | size = PyUnicode_GET_SIZE(unicode);
|^~
|PyDict_GET_SIZE
...
Processed: tagging 1074220
Processing commands for cont...@bugs.debian.org: > tags 1074220 + patch Bug #1074220 [src:scribus] scribus: Fails to build with Python 3.12 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1074220 is forwarded to https://github.com/scribusproject/scribus/commit/065459990d1fe097d4339653c7ba600cc3547523
Processing commands for cont...@bugs.debian.org: > forwarded 1074220 > https://github.com/scribusproject/scribus/commit/065459990d1fe097d4339653c7ba600cc3547523 Bug #1074220 [src:scribus] scribus: Fails to build with Python 3.12 Set Bug forwarded-to-address to 'https://github.com/scribusproject/scribus/commit/065459990d1fe097d4339653c7ba600cc3547523'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1062022 marked as pending in dcmtk
Processing control commands: > tag -1 pending Bug #1062022 [src:dcmtk] dcmtk: NMU diff for 64-bit time_t transition Added tag(s) pending. -- 1062022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1062022: marked as pending in dcmtk
Control: tag -1 pending Hello, Bug #1062022 in dcmtk reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/dcmtk/-/commit/d24b828b56a7c7bc8a03d4ebdaab6c9baf60293f Rename libraries for 64-bit time_t transition. Closes: #1062022 Signed-off-by: Étienne Mollier (this message was generated automatically) -- Greetings https://bugs.debian.org/1062022
Bug#1074222: pycorrfit FTBFS with Python 3.12 as default
Source: pycorrfit
Version: 1.1.7+dfsg-2
Severity: serious
Tags: ftbfs trixie sid
https://buildd.debian.org/status/logs.php?pkg=pycorrfit=1.1.7%2Bdfsg-2%2Bb2
...
running egg_info
/usr/lib/python3/dist-packages/setuptools/command/egg_info.py:131:
SetuptoolsDeprecationWarning: Invalid version: 'unknown'.
!!
Version 'unknown' is not valid according to PEP 440.
Please make sure to specify a valid version for your package.
Also note that future releases of setuptools may halt the build process
if an invalid version is given.
This deprecation is overdue, please update your project and remove
deprecated
calls to avoid build errors in the future.
See https://peps.python.org/pep-0440/ for details.
!!
return _normalization.best_effort_version(tagged)
Traceback (most recent call last):
File "/<>/setup.py", line 54, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py",
line 131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318,
in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
65, in run
self.build_package_data()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
161, in build_package_data
for target, srcfile in self._get_package_data_output_mapping():
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
153, in _get_package_data_output_mapping
for package, src_dir, build_dir, filenames in self.data_files:
^^^
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
74, in __getattr__
self.data_files = self._get_data_files()
^^
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
86, in _get_data_files
self.analyze_manifest()
File "/usr/lib/python3/dist-packages/setuptools/command/build_py.py", line
183, in analyze_manifest
self.run_command('egg_info')
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318,
in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
987, in run_command
cmd_obj.ensure_finalized()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111,
in ensure_finalized
self.finalize_options()
File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py", line
225, in finalize_options
parsed_version = packaging.version.Version(self.egg_version)
^^^
File
"/usr/lib/python3/dist-packages/setuptools/_vendor/packaging/version.py", line
198, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
setuptools.extern.packaging.version.InvalidVersion: Invalid version: 'unknown'
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p 3.12 returned exit
code 13
make[1]: *** [debian/rules:49: override_dh_auto_build] Error 25
Bug#1026957: (no subject)
Hi, I'm raising the severity to serious as the explicit dependency to libqt6core6 causes the package to have unsatisfiable dependencies. The package libqt6core6 has been superseded by libqt6core6t64. And as already mentioned, these explicit dependencies to the Qt libraries should not be needed. -- Med vänliga hälsningar Patrick Franz
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1026957 serious Bug #1026957 [src:mozillavpn] mozillavpn: Multiple packaging issues Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 1026957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: magic-wormhole: Fails to build with Python 3.12
Processing control commands: > severity -1 serious Bug #1073069 [src:magic-wormhole] magic-wormhole: Fails to build with Python 3.12 Severity set to 'serious' from 'important' -- 1073069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070208: openttd: cmake licensing concern for openttd 14.0 source package
Hi James, > The relevant CMake file addition was sourced[1] from the LLVM codebase, which > is licensed under a variant of the Apache 2.0 license with some exception > clauses added for the LLVM project. This is not yet documented in the source > package. Thanks for pointing this out. It turns out I've failed to update the copyright file for some other included code as well. I'm preparing an upload to fix this now. > To explain my reasoning: On balance I'd prefer opening a serious-severity bug > to prevent migration (that could later be reduced in severity) than to allow > the package transition while being aware of a potential problem. Yes, makes sense! Gr. Matthijs signature.asc Description: PGP signature
Bug#1074221: morph-browser: FTBFS on mips64el
Package: morph-browser Version: 1.1.0+dfsg-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package fails to build on mips64el and can therefore not migrate to testing. See https://buildd.debian.org/status/fetch.php?pkg=morph-browser=mips64el=1.1.0%2Bdfsg-2=1716667926=0 -- Regards Patrick Franz
Bug#1074220: scribus: Fails to build with Python 3.12
Source: scribus Version: 1.5.8+dfsg-5 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 scribus fails to build with Python 3.12. In Ubuntu, this was fixed by updating scribus to 1.6.1 (and now 1.6.2). Build log excerpt -- /<>/scribus/plugins/scriptplugin/cmdgetsetprop.cpp: In function ‘PyObject* scribus_setproperty(PyObject*, PyObject*, PyObject*)’: /<>/scribus/plugins/scriptplugin/cmdgetsetprop.cpp:413:84: error: ‘PyUnicode_AS_UNICODE’ was not declared in this scope; did you mean ‘PyUnicode_AsUCS4’? 413 | const unsigned short * ucs2Data = (const unsigned short *) PyUnicode_AS_UNICODE(objValue); | ^~~~ | PyUnicode_AsUCS4 /<>/scribus/plugins/scriptplugin/cmdgetsetprop.cpp:433:84: error: ‘PyUnicode_AS_UNICODE’ was not declared in this scope; did you mean ‘PyUnicode_AsUCS4’? 433 | const unsigned short * utf16Data = (const unsigned short *)PyUnicode_AS_UNICODE(objValue); | ^~~~ | PyUnicode_AsUCS4 make[3]: *** [scribus/plugins/scriptplugin/CMakeFiles/scriptplugin.dir/build.make:173: scribus/plugins/scriptplugin/CMakeFiles/scriptplugin.dir/cmdgetsetprop.cpp.o] Error 1 Full build logs https://buildd.debian.org/status/package.php?p=scribus Thank you, Jeremy Bícha
Bug#1074219: eln: Build-Depends on unsatisfiable dependencies on armel/mips64el/ppc64el/s390x
Package: eln Version: 1.5.4-1 Severity: serious X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package build-depends on qt6-pdf-dev, qml6-module-qtwebengine-controlsdelegates and qml6-module-qtwebengine on armel/mips64el/ppc64el/s390x. However, these packages only exist on amd64/arm64/armhf/i386. This prevents the packages from being built on these architectures and thus from migrating to testing. -- Regards Patrick Franz
Processed: bug 1074112 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=31924
Processing commands for cont...@bugs.debian.org: > forwarded 1074112 https://sourceware.org/bugzilla/show_bug.cgi?id=31924 Bug #1074112 [src:binutils] [arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=31924'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074218: dogecoin: FTBFS because of symbol errors
Package: dogecoin Version: 1.14.7-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, the package FTBFS on amd64 due to symbol errors. See https://buildd.debian.org/status/fetch.php?pkg=dogecoin=amd64=1.14.7-1=1716846348=0 -- Regards Patrick Franz
Processed: Re: onboard: failing build tests
Processing control commands: > retitle -1 onboard: failing build tests Bug #1071098 [onboard] Onboard: FTBFS on riscv64 due to test failed Changed Bug title to 'onboard: failing build tests' from 'Onboard: FTBFS on riscv64 due to test failed'. > severity -1 serious Bug #1071098 [onboard] onboard: failing build tests Severity set to 'serious' from 'important' > tags -1 -patch Bug #1071098 [onboard] onboard: failing build tests Removed tag(s) patch. -- 1071098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1074136 to org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331) ...
Processing commands for cont...@bugs.debian.org: > retitle 1074136 org-link-expand-abbrev: Do not evaluate arbitrary unsafe > Elisp code (CVE-2024-39331) Bug #1074136 [src:org-mode] org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code Changed Bug title to 'org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331)' from 'org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code'. > retitle 1074137 org-link-expand-abbrev: Do not evaluate arbitrary unsafe > Elisp code (CVE-2024-39331) Bug #1074137 [src:emacs] org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code Changed Bug title to 'org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331)' from 'org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074136 1074137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074216: kitty FTBFS with Python 3.12 as default
Source: kitty
Version: 0.35.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=kitty=0.35.1-1%2Bb1
...
==
FAIL: test_ssh_leading_data (kitty_tests.ssh.SSHKitten.test_ssh_leading_data)
(sh='python3')
--
Traceback (most recent call last):
File "/<>/kitty/launcher/../../kitty_tests/ssh.py", line 167, in
test_ssh_leading_data
self.ae(pty.screen_contents(), 'UNTAR_DONE\nld:before_tarfile')
pty =
script = 'print("ld:" + leading_data.decode("ascii")); raise SystemExit(0);'
self =
sh = 'python3'
tdir = '/tmp/tmpj2ma30as'
AssertionError: 'bootstrap.py:214: DeprecationWarning: Pyt[180 chars]file' !=
'UNTAR_DONE\nld:before_tarfile'
- bootstrap.py:214: DeprecationWarning: Python 3.14 will, by default, filter
extra
- cted tar archives and reject files or modify their metadata. Use the filter
argu
- ment to control this behavior.
UNTAR_DONE
ld:before_tarfile
--
Ran 144 tests in 68.976s
FAILED (failures=1, skipped=2)
[31mError[39m: Some tests failed!
make[1]: *** [debian/rules:60: override_dh_auto_test] Error 1
Bug#1066086: marked as done (maxima-emacs: maxima-emacs again not installable with xemacs21)
Your message dated Mon, 24 Jun 2024 16:56:24 + with message-id and subject line Bug#1066086: fixed in maxima 5.47.0-3 has caused the Debian Bug report #1066086, regarding maxima-emacs: maxima-emacs again not installable with xemacs21 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: maxima-emacs,xemacs21 Severity: normal Dear Maintainers, Seems that [#969410] maxima-emacs: maxima-emacs 5.44 does not work with XEmacs [#999626] maxima-emacs: fails to install with xemacs21 are back, since mmm-mode-el dropped xemacs21 support and no longer provides cl-lib. I am including xemacs1 package in case maintainer wants to add something. I see some possible approaches, 1) Drop xemacs21 support from maxima-emacs. I proposed a patch in #999626, should need more test and should probably be updated. 2) Create something like a xemacs21-compat-el package containing cl-lib and may be other compatibility stuff. 3) Include cl-lib somewhere in Debian xemacs21 package as a Debian feature. 4) Include cl-lib in maxima-emacs for local use. Opinions? Regards, -- Agustin --- End Message --- --- Begin Message --- Source: maxima Source-Version: 5.47.0-3 Done: Camm Maguire We believe that the bug you reported is fixed in the latest version of maxima, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Camm Maguire (supplier of updated maxima package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Jun 2024 11:10:13 -0400 Source: maxima Architecture: source Version: 5.47.0-3 Distribution: unstable Urgency: high Maintainer: Camm Maguire Changed-By: Camm Maguire Closes: 1066086 Changes: maxima (5.47.0-3) unstable; urgency=high . * Bug fix: "maxima-emacs again not installable with xemacs21", thanks to Agustin Martin (Closes: #1066086). Checksums-Sha1: ccf3ec69a07244485f5bd6e867ccd2b365f9dcbf 2126 maxima_5.47.0-3.dsc 6db42c7e101fb597a5f6d2e0e61809d9ca1037de 1773492 maxima_5.47.0-3.debian.tar.xz ea4e0f9f380065638559f5de078bd9d300888020 9092 maxima_5.47.0-3_source.buildinfo Checksums-Sha256: 4a21d4c41a408306cd77018978bcedfa653784b379753e0ca2969a3ba069afb9 2126 maxima_5.47.0-3.dsc ad5866b87c775235eb332213adffa0dd2f0cebb2899d700ba0179b5f15e9b563 1773492 maxima_5.47.0-3.debian.tar.xz 9e3edfdf7f7e79302ed3160c8c5ca77c5c8d97fcd595ceb8e0e73e6af39f3a0a 9092 maxima_5.47.0-3_source.buildinfo Files: f315f6e6f154cb26b8931dd55bba1563 2126 math optional maxima_5.47.0-3.dsc e27c35f3e68c2cd23e2f20b9d56c45a3 1773492 math optional maxima_5.47.0-3.debian.tar.xz 7a421a6322a5480bd556b3e5c91fe669 9092 math optional maxima_5.47.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAmZ5mm4ACgkQuEXOUQ+b cU1hfw/+M0UP9u9QBqoybYpDRaPBvW+tZFo+elL3OAd9NYlEVJRuezUpm0qpRvFB wHO7rKHr9lBm5WKUnnl5woC73GRE5uCSCKGtW7zOTp1YNYEJEx6Kqg0NMkBuyRLu 45iOaSrAvFqfPOcqA9D02EUGAl6DBeLYX7t7K64hOEPw93X73T2yJQKN+smf7lxO SEB5W6cVEZ/Qs+i2XXjZLL8lOxNY2MLdbR3aYRVLWzIlvMqeYwre5WwcApEZ12GZ hBpg/KNKBF6gaozbkRTfFRRXwst+p2a/y04xePAAAq95sYsBEa3+1tWvHErfpsFA 3qWjP/K6Vy4Yk0bHQQ0siNoOWiQc/OuMqmJJ0Y7giIgVjJbOT3jHcmq7+ExC1VVq T8RU/8GcerVxjsi6g8nRmwf2SZtLXy3Xk6dFv3XeIybPlqRRu7EhJ9DesoBHWE1O K40AeGuXbof9ObO8uPZBgFTHt79UPv3bw9E/LAlU99vM2vsDJfleewE9hmi3p7rv 2vvHRhuwNqF/BA1hot9sFid8+jJHbaIC392Ybz1C3xuYoHEDT7q1MSGLWv3/DjzL coSXa7qovimF8xQ/aJgWRegUYc7Wf5ZIc9m7h3R3d7OYWyGpTNQZ8N9phxmlyyky F5FlE8EGq31fAcsStFxxAg1pfcw6Qxj/RyzTfF7DrquZxRfgKrI= =hLvN -END PGP SIGNATURE- pgp8MtRmjON1R.pgp Description: PGP signature --- End Message ---
Bug#1069575: marked as done (FTBFS in experimental)
Your message dated Mon, 24 Jun 2024 17:42:54 +0200 with message-id <171924377436.255930.4424760604575176...@auryn.jones.dk> and subject line Re: Bug#1069575: FTBFS in experimental has caused the Debian Bug report #1069575, regarding FTBFS in experimental 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.) -- 1069575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-async-process Version: 1.7.0-4 Severity: important Tags: ftbfs X-Debbugs-Cc: jbi...@debian.org, werdah...@riseup.net -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Jonas, asnyc-process currently fail to build in experimental: = error[E0599]: the method `next` exists for reference ``, but its trait bounds were not satisfied --> src/lib.rs:313:33 | 313 | ().next().await; | method cannot be called on `` due to unsatisfied trait bounds --> /usr/src/rustc-1.70.0/library/std/src/sync/mutex.rs:175:1 | = note: doesn't satisfy `_: Stream` | = note: doesn't satisfy `std::sync::Mutex: StreamExt` | = note: the following trait bounds were not satisfied: `::sync::Mutex: futures_lite::Stream` which is required by `::sync::Mutex: StreamExt` `std::sync::Mutex: futures_lite::Stream` which is required by `std::sync::Mutex: StreamExt` error[E0599]: no function or associated item named `new` found for struct `EventListener` in the current scope --> src/lib.rs:513:43 | 513 | let listener = EventListener::new(); | ^^^ function or associated item not found in `EventListener` error[E0277]: the `?` operator can only be applied to values that implement `Try` --> src/lib.rs:307:30 | 307 | signals: Mutex::new(Signals::new([SIGCHLD]))?, | the `?` operator cannot be applied to type `std::sync::Mutex>` | = help: the trait `Try` is not implemented for `std::sync::Mutex>` Some errors have detailed explanations: E0277, E0599. For more information about an error, try `rustc --explain E0277`. error: could not compile `async-process` due to 3 previous errors warning: build failed, waiting for other jobs to finish... dh_auto_test: error: env DEB_BUILDDIR= /<>/debian/dh-cargo/bin/cargo test returned exit code 101 make: *** [debian/rules:9: binary-indep] Error 25 == I didn't have time to investigate this yet. I'd appreciate it if you coud take a look at this as it is blocking the event-listener-transition. best, werdahias - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-2-amd64 (SMP w/16 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: OpenRC (via /run/openrc), PID 1: init LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmYkCxcVHHdlcmRhaGlh c0ByaXNldXAubmV0AAoJEBi9EGs7bFR1EhMQAKe69jDJ2+e+DEaWDfSgVhgXW8je WQ8U4WHhk38rIaKfZmxem3GfQZWj+WSeRCY07E2JHurgci82iCzKw3mp1hnAZeoV DsMsKQlNQmMnrNCk+vYgb0zjv65KN9iDjcZwuCOwm7Qy8v3N6yRru8yzHs7GsJEH tJgcUjo6lAi3MuDm0Znl35vrBvhU/oNLMUqVWb3I4Rv9/woeHllXvZtxx9Nfz7Rj ltzkLWTFbrWS1bWBCVLS3heJ980wuS9hVb+s9YYtkcy6FZDWUUZGQZ4nNKZBwAhf 5krwZMhsMTF3h22e+61wE4wIpbCVTBsWICROTXQeQLtwiWRqknFRdHOVfX8XfWSG VxGx60Zw076tRtzrZ3DvXJvztt3eKSK3pEv+ZtQjwDiQQDjpUUQyMafeMa6wHd8y Xm0AhQK4zCDHwntnHjnCUVDLp9JU1DxnUCx1CE98Iarhv5p1PUyXLRC3IXqmbvbe zbumMaKgiEkXabA1FaUJpgO5E871B1Dcod+EC8nQi5KlVGnhK8E85qY2Z/2W4wKz 1veTg1ZKKRsuaveZx6Dhn0sB0mwJVrLfgLc4kBcvtjkoFPOeA+vpPY+Rp0NAY4CJ K5as+DJyRHSNFkj23e/dvNKYQlHAfzfYIDRI5EI/gZ71c0hzrRZSJe+5Qg95I7SP EWU2XUhf6aFUO3Rc =vZWi -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 2.2.3-1 Quoting Matthias Geiger (2024-06-24 14:21:14) > On Wed, 19 Jun 2024 20:04:26 +0200 Jonas Smedegaard wrote: > > > > > > > I packaged async-signal; it's awaiting a NEW trip. > > > > Great! > > > async-signal migrated to testing; I'd appreciate it if you could test if > re-enabling async-signal fixes this bug. This was fixed with release 2.2.3-1. If for some *different* reason the same package fails to build, then please report as a separate issue (not
Processed: Bug#1069317 marked as pending in vamp-plugin-sdk
Processing control commands: > tag -1 pending Bug #1069317 [libvamp-sdk2v5] FTBFS: tests failed Added tag(s) pending. -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069317: marked as pending in vamp-plugin-sdk
Control: tag -1 pending Hello, Bug #1069317 in vamp-plugin-sdk 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/vamp-plugin-sdk/-/commit/1d51c2afc810254f5bc640d1d7bfd289aa5d8e58 Rename libraries for 64-bit time_t transition. Closes: #1069317 (this message was generated automatically) -- Greetings https://bugs.debian.org/1069317
Bug#1058104: astropy-helpers: FTBFS: ModuleNotFoundError: No module named 'imp'
Hi Boyuan Yang, On 14.06.24 19:50, Boyuan Yang wrote: -> % build-rdeps python3-astropy-helpers Reverse Build-depends in unstable/main: astroquery hipspy Found a total of 2 reverse build-depend(s) for python3-astropy-helpers. Two reverse-dependencies exist, and both of them are not having active upstream development. You are also listed as the uploader for them. If you believe that this issue will not be fixed upstream, please review the current status of these packages and determine how to proceed. Thanks! Hipspy is currently unmaintained upstream RC buggy in Debian. Since it seems not really abandoned upstream, I still keep it in unstable, having some hope that maintenance will resume at some future point. If they re-start, the will need to migrate from astropy-helpers in any case, so I'd keep the state here as it is. Removing astropy-helpers is therefore not a problem here. For astroquery, I am not an uploader; however I will have a look how to update it (it is team maintained anyway). They didn't have the resources to migrate away from astropy-helpers yet, and they come with an updated local copy of it (because it is abandoned upstream). Using this copy would be the way to go here; it is in any case only temporary, and it will be the only package that somehow uses astropy-helpers for some time. Updating Debian's astropy-helpers instead would not worth the effort, and would also send wrong signals to the users to use a clearly abandoned package. Astroquery is still actively maintained on Github; the last commit was 4 days ago. The development is very close to astropy, so I am confident about the future removal of astropy-helpers from astroquery. I hope that helps to answer your questions? After I team-updated astroquery, I will write an removal request for astropy-helpers. Best Ole
Bug#1069317: FTBFS: tests failed
On closer inspection, this seems to be a bug in vamp, rather than
sonic-visualiser.
E.g. consider the following example program:
```C++
#include "vamp-hostsdk/RealTime.h"
#include
#include
int main() {
Vamp::RealTime t1 = Vamp::RealTime(0, 5);
struct timeval tv;
tv.tv_sec = 0; tv.tv_usec = 50;
Vamp::RealTime t2 = Vamp::RealTime::fromTimeval(tv);
std::cout << "RealTime(0, ONE_BILLION/2) = " << t1 << std::endl;
std::cout << "RealTime::fromTimeval(0, ONE_MILLION/2) = " << t2 <<
std::endl;
if (t1 != t2)
return 1;
return 0;
}
```
And run with:
```sh
g++ test.cpp -o test $(pkg-config --cflags --libs vamp-hostsdk)
./test || echo oops
```
On amd64, this will output
```
RealTime(0, ONE_BILLION/2) = 0.5R
RealTime::fromTimeval(0, ONE_MILLION/2) = 0.5R
```
whereas on armhf, you get
```
RealTime(0, ONE_BILLION/2) = 0.5R
RealTime::fromTimeval(0, ONE_MILLION/2) = 0.0R
oops
```
so obviously RealTime::fromTimeval() is broken on armhf.
gdmasr
IOhannes
OpenPGP_signature.asc
Description: OpenPGP digital signature
Processed: reassign 1069317 to libvamp-sdk2v5
Processing commands for cont...@bugs.debian.org: > reassign 1069317 libvamp-sdk2v5 Bug #1069317 [src:sonic-visualiser] FTBFS: tests failed Bug reassigned from package 'src:sonic-visualiser' to 'libvamp-sdk2v5'. No longer marked as found in versions sonic-visualiser/4.5.2-2. Ignoring request to alter fixed versions of bug #1069317 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069575: FTBFS in experimental
On Wed, 19 Jun 2024 20:04:26 +0200 Jonas Smedegaard wrote: > > > > > I packaged async-signal; it's awaiting a NEW trip. > > Great! > async-signal migrated to testing; I'd appreciate it if you could test if re-enabling async-signal fixes this bug. best, werdahias
Bug#1051564: marked as done (stk: FTBFS with RtAudio 6)
Your message dated Mon, 24 Jun 2024 12:03:00 +
with message-id
and subject line Bug#1051564: fixed in stk 5.0.1+dfsg-1~exp
has caused the Debian Bug report #1051564,
regarding stk: FTBFS with RtAudio 6
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.)
--
1051564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stk
Version: 4.6.2+dfsg-2
Severity: important
Tags: ftbfs patch
Dear Maintainer,
stk ftbfs with RtAudio 6 (as currently found in experimental):
a small excerpt from the build-logs:
```
RtWvOut.cpp:110:11: error: ‘RtAudioError’ does not name a type; did you mean
‘RtAudioErrorType’?
110 | catch ( RtAudioError ) {
| ^~~~
| RtAudioErrorType
RtWvOut.cpp:111:18: error: ‘error’ was not declared in this scope; did you mean
‘perror’?
111 | handleError( error.what(), StkError::AUDIO_SYSTEM );
| ^
| perror
make[3]: *** [Makefile:79: RtWvOut.o] Error 1
make[3]: *** Waiting for unfinished jobs
RtWvIn.cpp: In constructor ‘stk::RtWvIn::RtWvIn(unsigned int, stk::StkFloat,
int, int, int)’:
RtWvIn.cpp:89:11: error: ‘RtAudioError’ does not name a type; did you mean
‘RtAudioErrorType’?
89 | catch ( RtAudioError ) {
| ^~~~
| RtAudioErrorType
RtWvIn.cpp:90:18: error: ‘error’ was not declared in this scope; did you mean
‘perror’?
90 | handleError( error.what(), StkError::AUDIO_SYSTEM );
| ^
| perror
```
attached is a patch that fixes the FTBFS (but is otherwise untested).
no debdiff this time, sorry.
cheers.
Description: Fix FTBFS with RtAudio 6
replace try/catch with checking error-codes
Author: IOhannes m zmölnig
Origin: Debian
Forwarded: no
Last-Update: 2023-09-09
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: stk-4.6.2+dfsg/src/RtWvIn.cpp
===
--- stk-4.6.2+dfsg.orig/src/RtWvIn.cpp
+++ stk-4.6.2+dfsg/src/RtWvIn.cpp
@@ -83,11 +83,8 @@ RtWvIn :: RtWvIn( unsigned int nChannels
unsigned int size = bufferFrames;
RtAudioFormat format = ( sizeof(StkFloat) == 8 ) ? RTAUDIO_FLOAT64 :
RTAUDIO_FLOAT32;
- try {
-adc_.openStream( NULL, , format, (unsigned
int)Stk::sampleRate(), , , (void *)this );
- }
- catch ( RtAudioError ) {
-handleError( error.what(), StkError::AUDIO_SYSTEM );
+ if(adc_.openStream( NULL, , format, (unsigned
int)Stk::sampleRate(), , , (void *)this )) {
+handleError(adc_.getErrorText(), StkError::AUDIO_SYSTEM );
}
data_.resize( size * nBuffers, nChannels );
Index: stk-4.6.2+dfsg/src/RtWvOut.cpp
===
--- stk-4.6.2+dfsg.orig/src/RtWvOut.cpp
+++ stk-4.6.2+dfsg/src/RtWvOut.cpp
@@ -104,11 +104,8 @@ RtWvOut :: RtWvOut( unsigned int nChanne
RtAudioFormat format = ( sizeof(StkFloat) == 8 ) ? RTAUDIO_FLOAT64 :
RTAUDIO_FLOAT32;
// Open a stream and set the callback function.
- try {
-dac_.openStream( , NULL, format, (unsigned
int)Stk::sampleRate(), , , (void *)this );
- }
- catch ( RtAudioError ) {
-handleError( error.what(), StkError::AUDIO_SYSTEM );
+ if(dac_.openStream( , NULL, format, (unsigned
int)Stk::sampleRate(), , , (void *)this )) {
+handleError( dac_.getErrorText(), StkError::AUDIO_SYSTEM );
}
data_.resize( size * nBuffers, nChannels );
Index: stk-4.6.2+dfsg/projects/demo/demo.cpp
===
--- stk-4.6.2+dfsg.orig/projects/demo/demo.cpp
+++ stk-4.6.2+dfsg/projects/demo/demo.cpp
@@ -259,11 +259,8 @@ int main( int argc, char *argv[] )
parameters.deviceId = dac.getDefaultOutputDevice();
parameters.nChannels = data.channels;
unsigned int bufferFrames = RT_BUFFER_SIZE;
-try {
- dac.openStream( , NULL, format, (unsigned
int)Stk::sampleRate(), , , (void *) );
-}
-catch ( RtAudioError& error ) {
- error.printMessage();
+if(dac.openStream( , NULL, format, (unsigned
int)Stk::sampleRate(), , , (void *) )) {
+ std::cerr << dac.getErrorText() << std::endl;
goto cleanup;
}
}
@@ -279,11 +276,8 @@ int main( int argc, char *argv[] )
// If realtime output, set our callback function and start the dac.
#if defined(__STK_REALTIME__)
if ( data.realtime ) {
-try {
- dac.startStream();
-}
-catch ( RtAudioError ) {
- error.printMessage();
+
Bug#1070450: marked as pending in qm-dsp
Control: tag -1 pending Hello, Bug #1070450 in qm-dsp 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/qm-dsp/-/commit/7570560b9f05d23651e50d9044bd0cb713190fed Slightly relax float-equality test in testsuite Closes: #1070450 (this message was generated automatically) -- Greetings https://bugs.debian.org/1070450
Processed: Bug#1070450 marked as pending in qm-dsp
Processing control commands: > tag -1 pending Bug #1070450 [src:qm-dsp] qm-dsp: autopkgtest regression on arm64, ppc64el and s390x Added tag(s) pending. -- 1070450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070450 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074175: netkit-rwho: remove for trixie?
Source: netkit-rwho Version: 0.17-15 Severity: serious rwho(d) is a design from a different time, when networks were trusted, and so on. It seems to me, we should and could stop shipping it for trixie. I'm raising this bug now, to: 1) establish awareness 2) auto-rm it from trixie 3) give people time to chime in / secure replacements to show up After a while I intend to clone this bug to ftp.debian.org for removal from unstable. Chris
Bug#1073178: awscli: please update awsci and/or botocore to support urllib3 2.x
Looks like the system botocore has the fix, bit there's another one bundled with awscli that doesn't - and that's the one being used: /usr/lib/python3/dist-packages/awscli/botocore/httpsession.py /usr/lib/python3/dist-packages/botocore/httpsession.py: So looks like we need to remove the botocore bundled with awscli, i tried simply renaming /usr/lib/python3/dist-packages/awscli/botocore but then it seems awscli couldn't find the system botocore: Traceback (most recent call last): File "/usr/bin/aws", line 19, in import awscli.clidriver File "/usr/lib/python3/dist-packages/awscli/clidriver.py", line 21, in import botocore.session ModuleNotFoundError: No module named 'botocore' So something is hardcoded to look inside awscli i guess? Simply copying httpsession.py from the system botocore to the awscli one fixes this error but I'm not sure we want to just do that. On Wed, 19 Jun 2024 09:07:42 +0200 Gregor Riepl wrote: > that leads here: https://github.com/aws/aws-cli/issues/7905 > "cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl_'" > > https://github.com/boto/botocore/pull/2924/files It's not mentioned in the changelog, but this commit was already included in 1.29.123: https://github.com/boto/botocore/compare/1.29.122...1.29.123 Debian sid has 1.34.46, so I'm not entirely sure why it's still broken? -- Simon John
Bug#1060591: marked as done (btrfsd: Please switch Build-Depends to systemd-dev)
Your message dated Mon, 24 Jun 2024 10:48:57 + with message-id and subject line Bug#1060591: fixed in btrfsd 0.2.2-1 has caused the Debian Bug report #1060591, regarding btrfsd: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1060591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: btrfsd Version: 0.2.1-1 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package btrfsd declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Source: btrfsd Source-Version: 0.2.2-1 Done: Matthias Klumpp We believe that the bug you reported is fixed in the latest version of btrfsd, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klumpp (supplier of updated btrfsd 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, 24 Jun 2024 12:21:42 +0200 Source: btrfsd Architecture: source Version: 0.2.2-1 Distribution: unstable Urgency: medium Maintainer: Matthias Klumpp Changed-By: Matthias Klumpp Closes: 1060591 1063812 Changes: btrfsd (0.2.2-1) unstable; urgency=medium . * New upstream version: 0.2.2 - Only run all tasks once per filesystem (Closes: #1063812) * Add systemd-dev to build dependencies (Closes: #1060591) Checksums-Sha1: fef7f54e62e430f47a841e9866476d404101fac3 1942 btrfsd_0.2.2-1.dsc c949daf8718fad0d56e9e51709049ba265bf9aaf 38379 btrfsd_0.2.2.orig.tar.gz a63c41762fef9548fe07eef83d15d1dc983e8711 2160 btrfsd_0.2.2-1.debian.tar.xz 756e9934dd42a9be1c4271e3e028d204647d3464 8949 btrfsd_0.2.2-1_source.buildinfo Checksums-Sha256: 399d1408555260c69e7f317d11339a70b43186142a976246bd5aafd1bc8b7532 1942 btrfsd_0.2.2-1.dsc 3046f8397b70bd83d151fb856767af32f9145747f8bd5e238db5f8740d0ff348 38379 btrfsd_0.2.2.orig.tar.gz 1a1928aeed0452e7c4e0b63ddb2c5ae672deee1a73cb1b76376b1fee18cb80cf 2160 btrfsd_0.2.2-1.debian.tar.xz 5d0fd38940794b6053b16f051e638964a4891291d28567249e1bbbd44800c175 8949 btrfsd_0.2.2-1_source.buildinfo Files: ba4a4833608ec6879cb66b0fcc1e0b8a 1942 admin optional btrfsd_0.2.2-1.dsc 4a5d6eee209f67994a53392a17e79b70 38379 admin optional btrfsd_0.2.2.orig.tar.gz 69d6878ae5d45208c0ff7f99faca4180 2160 admin optional btrfsd_0.2.2-1.debian.tar.xz ea93c31d3a459dc91afcee8ff5717832 8949 admin optional btrfsd_0.2.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAmZ5SmIPHG1ha0BkZWJp YW4ub3JnAAoJEElMil+/TezrLqIP/jZ7gwTaEMxmaLgn0OqWW37VsFihYlhF/41/ InNNq3fCVqYMU/SVai9W2jG1cppyLeiN0wMNlBPgyiWZEiglR5o4WgElPzqxMqVr 9X1vO3IOaz8AsjL2atw6B94ZVYZMSRp8xaupFGmSsW2sftoZnmBXRYzjIwpl+1Za
Processed: bug 1057599 is forwarded to https://github.com/repoze/repoze.sphinx.autointerface/issues/21
Processing commands for cont...@bugs.debian.org:
> forwarded 1057599
> https://github.com/repoze/repoze.sphinx.autointerface/issues/21
Bug #1057599 {Done: Colin Watson }
[src:python-repoze.sphinx.autointerface] python-repoze.sphinx.autointerface:
FTBFS: ERROR: test_all_members
Set Bug forwarded-to-address to
'https://github.com/repoze/repoze.sphinx.autointerface/issues/21'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1057599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057599: marked as done (python-repoze.sphinx.autointerface: FTBFS: ERROR: test_all_members)
Your message dated Mon, 24 Jun 2024 10:34:36 + with message-id and subject line Bug#1057599: fixed in python-repoze.sphinx.autointerface 1.0.0-2 has caused the Debian Bug report #1057599, regarding python-repoze.sphinx.autointerface: FTBFS: ERROR: test_all_members 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.) -- 1057599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-repoze.sphinx.autointerface Version: 1.0.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:310: python3.12 setup.py config /usr/lib/python3/dist-packages/setuptools/dist.py:946: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) running config I: pybuild base:310: python3.11 setup.py config /usr/lib/python3/dist-packages/setuptools/dist.py:946: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:310: /usr/bin/python3.12 setup.py build /usr/lib/python3/dist-packages/setuptools/dist.py:946: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. !! ep.load()(self, ep.name, value) running build running build_py creating /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze copying repoze/__init__.py -> /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze creating /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze/sphinx copying repoze/sphinx/__init__.py -> /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze/sphinx copying repoze/sphinx/autointerface.py -> /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze/sphinx creating /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze/sphinx/tests copying repoze/sphinx/tests/__init__.py -> /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze/sphinx/tests copying repoze/sphinx/tests/test_autointerface.py -> /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze/sphinx/tests copying repoze/sphinx/tests/util.py -> /<>/.pybuild/cpython3_3.12_repoze.sphinx.autointerface/build/repoze/sphinx/tests running egg_info creating repoze.sphinx.autointerface.egg-info writing repoze.sphinx.autointerface.egg-info/PKG-INFO writing dependency_links to repoze.sphinx.autointerface.egg-info/dependency_links.txt writing namespace_packages to repoze.sphinx.autointerface.egg-info/namespace_packages.txt writing requirements to repoze.sphinx.autointerface.egg-info/requires.txt writing top-level names to repoze.sphinx.autointerface.egg-info/top_level.txt writing manifest file 'repoze.sphinx.autointerface.egg-info/SOURCES.txt' reading manifest file 'repoze.sphinx.autointerface.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '.travis.yml' warning: no directories found matching '.github' warning: no previously-included files matching '__pycache__' found
Processed: Bug#1057599 marked as pending in python-repoze.sphinx.autointerface
Processing control commands: > tag -1 pending Bug #1057599 [src:python-repoze.sphinx.autointerface] python-repoze.sphinx.autointerface: FTBFS: ERROR: test_all_members Added tag(s) pending. -- 1057599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057599: marked as pending in python-repoze.sphinx.autointerface
Control: tag -1 pending Hello, Bug #1057599 in python-repoze.sphinx.autointerface reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-repoze.sphinx.autointerface/-/commit/23fd649ca35193891d8b38294463fffc95cf9f0b Fix tests with Sphinx 7.2.x Closes: #1057599 (this message was generated automatically) -- Greetings https://bugs.debian.org/1057599
Bug#1073996: marked as done (twisted: autopkgtest fails on test_flatten: "builtins.KeyError: 'root'")
Your message dated Mon, 24 Jun 2024 10:04:47 + with message-id and subject line Bug#1073996: fixed in twisted 24.3.0-2 has caused the Debian Bug report #1073996, regarding twisted: autopkgtest fails on test_flatten: "builtins.KeyError: 'root'" 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.) -- 1073996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: twisted Version: 24.3.0-1 Severity: serious Tags: patch Justification: 6a X-Debbugs-Cc: florent.jacq...@canonical.com Hello there, Following some removal from Python itself, the following started to appear in autopkgtest: 2993s --- --- 2993s File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1999, in _inlineCallbacks 2993s result = context.run( 2993s File "/usr/lib/python3/dist-packages/twisted/python/failure.py", line 519, in throwExceptionIntoGenerator 2993s return g.throw(self.value.with_traceback(self.tb)) 2993s File "/usr/lib/python3/dist-packages/twisted/web/_flatten.py", line 435, in _flattenTree 2993s roots.append(frame.f_locals["root"]) 2993s builtins.KeyError: 'root' This is fixed upstream in https://github.com/twisted/twisted/pull/12213 I've cherry-picked the needed changes in a patch. I'll send a debdiff with everything shortly. -- System Information: Debian Release: trixie/sid APT prefers oracular APT policy: (500, 'oracular'), (400, 'oracular-proposed'), (200, 'noble-updates'), (200, 'noble'), (200, 'jammy-updates'), (200, 'jammy') Architecture: amd64 (x86_64) Kernel: Linux 6.8.0-31-generic (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 From: Florent 'Skia' Jacquet Date: Fri, 21 Jun 2024 12:06:48 +0200 Subject: Test: Fix twisted.web.test.test_flatten Following some removal from Python itself, the following started to appear in autopkgtest: 2993s --- --- 2993s File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1999, in _inlineCallbacks 2993s result = context.run( 2993s File "/usr/lib/python3/dist-packages/twisted/python/failure.py", line 519, in throwExceptionIntoGenerator 2993s return g.throw(self.value.with_traceback(self.tb)) 2993s File "/usr/lib/python3/dist-packages/twisted/web/_flatten.py", line 435, in _flattenTree 2993s roots.append(frame.f_locals["root"]) 2993s builtins.KeyError: 'root' This is fixed upstream in https://github.com/twisted/twisted/pull/12213 This patch is a cherry-pick of the needed changes, and can probably be dropped next release. --- a/src/twisted/web/_flatten.py +++ b/src/twisted/web/_flatten.py @@ -428,11 +427,11 @@ except StopIteration: stack.pop() except Exception as e: -stack.pop() roots = [] for generator in stack: -roots.append(generator.gi_frame.f_locals["root"]) -roots.append(frame.f_locals["root"]) +if generator.gi_frame is not None: +roots.append(generator.gi_frame.f_locals["root"]) +stack.pop() raise FlattenerError(e, roots, extract_tb(exc_info()[2])) else: stack.append(element) --- End Message --- --- Begin Message --- Source: twisted Source-Version: 24.3.0-2 Done: Florent 'Skia' Jacquet We believe that the bug you reported is fixed in the latest version of twisted, 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 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florent 'Skia' Jacquet (supplier of updated twisted 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, 24 Jun 2024 10:50:35 +0100 Source: twisted Architecture: source Version: 24.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Florent 'Skia' Jacquet Closes: 1073996 Changes: twisted (24.3.0-2)
Processed: Bug#1073996 marked as pending in twisted
Processing control commands: > tag -1 pending Bug #1073996 [src:twisted] twisted: autopkgtest fails on test_flatten: "builtins.KeyError: 'root'" Added tag(s) pending. -- 1073996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073996: marked as pending in twisted
Control: tag -1 pending Hello, Bug #1073996 in twisted 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/twisted/-/commit/144b7904d2836e46877be780b57707cf3fed590b Patch: fix test_flatten in autopkgtest Closes: #1073996 (this message was generated automatically) -- Greetings https://bugs.debian.org/1073996
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 1071470 2.7.5~rc1+dfsg-1
Bug #1071470 {Done: Tobias Frost } [src:slic3r-prusa]
src:slic3r-prusa: FTBFS with opencasacade 7.8.1
Marked as fixed in versions slic3r-prusa/2.7.5~rc1+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1071470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066750: marked as done (pydantic: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Mon, 24 Jun 2024 09:04:50 +
with message-id
and subject line Bug#1066750: fixed in pydantic 1.10.17-1
has caused the Debian Bug report #1066750,
regarding pydantic: 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.)
--
1066750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pydantic
Version: 1.10.14-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 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=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config
> Compiling pydantic/__init__.py because it changed.
> Compiling pydantic/_hypothesis_plugin.py because it changed.
> Compiling pydantic/annotated_types.py because it changed.
> Compiling pydantic/class_validators.py because it changed.
> Compiling pydantic/color.py because it changed.
> Compiling pydantic/config.py because it changed.
> Compiling pydantic/dataclasses.py because it changed.
> Compiling pydantic/datetime_parse.py because it changed.
> Compiling pydantic/decorator.py because it changed.
> Compiling pydantic/env_settings.py because it changed.
> Compiling pydantic/error_wrappers.py because it changed.
> Compiling pydantic/errors.py because it changed.
> Compiling pydantic/fields.py because it changed.
> Compiling pydantic/json.py because it changed.
> Compiling pydantic/main.py because it changed.
> Compiling pydantic/mypy.py because it changed.
> Compiling pydantic/networks.py because it changed.
> Compiling pydantic/parse.py because it changed.
> Compiling pydantic/schema.py because it changed.
> Compiling pydantic/tools.py because it changed.
> Compiling pydantic/types.py because it changed.
> Compiling pydantic/typing.py because it changed.
> Compiling pydantic/utils.py because it changed.
> Compiling pydantic/validators.py because it changed.
> Compiling pydantic/version.py because it changed.
> [ 1/25] Cythonizing pydantic/__init__.py
> [ 2/25] Cythonizing pydantic/_hypothesis_plugin.py
> [ 3/25] Cythonizing pydantic/annotated_types.py
> [ 4/25] Cythonizing pydantic/class_validators.py
> [ 5/25] Cythonizing pydantic/color.py
> [ 6/25] Cythonizing pydantic/config.py
> [ 7/25] Cythonizing pydantic/dataclasses.py
> [ 8/25] Cythonizing pydantic/datetime_parse.py
> [ 9/25] Cythonizing pydantic/decorator.py
> [10/25] Cythonizing pydantic/env_settings.py
> [11/25] Cythonizing pydantic/error_wrappers.py
> [12/25] Cythonizing pydantic/errors.py
> [13/25] Cythonizing pydantic/fields.py
> [14/25] Cythonizing pydantic/json.py
> [15/25] Cythonizing pydantic/main.py
> [16/25] Cythonizing pydantic/mypy.py
> [17/25] Cythonizing pydantic/networks.py
> [18/25] Cythonizing pydantic/parse.py
> [19/25] Cythonizing pydantic/schema.py
> [20/25] Cythonizing pydantic/tools.py
> [21/25] Cythonizing pydantic/types.py
> [22/25] Cythonizing pydantic/typing.py
> [23/25] Cythonizing pydantic/utils.py
> [24/25] Cythonizing pydantic/validators.py
> [25/25] Cythonizing pydantic/version.py
> running config
> I: pybuild base:305: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/utils.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/generics.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/__init__.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/tools.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/version.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/annotated_types.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/main.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/fields.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/parse.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/color.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying pydantic/decorator.py ->
> /<>/.pybuild/cpython3_3.12/build/pydantic
> copying
Processed: Bug#1066750 marked as pending in pydantic
Processing control commands:
> tag -1 pending
Bug #1066750 [src:pydantic] pydantic: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.
--
1066750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1066750: marked as pending in pydantic
Control: tag -1 pending Hello, Bug #1066750 in pydantic 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/pydantic/-/commit/a297d655f24048c13c3d94fe24c39a2d7bc0a7dd Fix `test_assert_raises_validation_error` with pytest-8 (#8995) (#9024) Closes: #1066750 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066750
Bug#1064737: marked as done (python3-defaults: FTBFS: make: *** [debian/rules:64: stamp-doc-policy] Error 1)
Your message dated Mon, 24 Jun 2024 08:49:14 + with message-id and subject line Bug#1064737: fixed in python3-defaults 3.12.2-1 has caused the Debian Bug report #1064737, regarding python3-defaults: FTBFS: make: *** [debian/rules:64: stamp-doc-policy] 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.) -- 1064737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python3-defaults Version: 3.11.6-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 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 '/<>/policy' > Running Sphinx v7.2.6 > making output directory... done > WARNING: html_static_path entry '_static' does not exist > building [mo]: targets for 0 po files that are out of date > writing output... > building [singlehtml]: all documents > updating environment: [new config] 12 added, 0 changed, 0 removed > [2Kreading sources... [ 8%] build-dependencies > [2Kreading sources... [ 17%] copyright > [2Kreading sources... [ 25%] embedded-python > [2Kreading sources... [ 33%] index > [2Kreading sources... [ 42%] interpreter > [2Kreading sources... [ 50%] locally-installed-python > [2Kreading sources... [ 58%] packaged-modules > [2Kreading sources... [ 67%] packaging-tools > [2Kreading sources... [ 75%] python-programs > [2Kreading sources... [ 83%] python3 > [2Kreading sources... [ 92%] this-document > [2Kreading sources... [100%] upgrade-procedure > > looking for now-outdated files... none found > pickling environment... done > checking consistency... done > preparing documents... done > assembling single document... copyright python3 interpreter packaged-modules > python-programs embedded-python locally-installed-python build-dependencies > packaging-tools upgrade-procedure this-document done > writing... done > writing additional files... done > copying static files... done > copying extra files... done > dumping object inventory... done > build succeeded, 1 warning. > > The HTML page is in _build/singlehtml. > make[1]: Leaving directory '/<>/policy' > ( \ > echo 'The HTML version of the Debian Python Policy can be found in the > python3-dev package'; \ > html2text -utf8 -style pretty policy/_build/singlehtml/index.html; \ > ) > policy/_build/python-policy.txt > Unrecognized command line option "-style", try "-help". > make: *** [debian/rules:64: stamp-doc-policy] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/02/24/python3-defaults_3.11.6-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: python3-defaults Source-Version: 3.12.2-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python3-defaults, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python3-defaults package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Jun 2024 10:23:35 +0200 Source: python3-defaults Architecture: source Version: 3.12.2-1 Distribution: unstable Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 1064737 1070728 Changes: python3-defaults (3.12.2-1) unstable;
Processed: bug 1069361 is forwarded to https://gitlab.gnome.org/GNOME/libgweather/-/merge_requests/311
Processing commands for cont...@bugs.debian.org: > forwarded 1069361 > https://gitlab.gnome.org/GNOME/libgweather/-/merge_requests/311 Bug #1069361 [src:libgweather4] libgweather4: FTBFS on arm64: Location 'Greenland' has invalid timezone 'America/Godthab' Bug #1073464 [src:libgweather4] libgweather4: FTBFS: # GLib-GIO-DEBUG: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could not connect: No such file or directory Ignoring request to change the forwarded-to-address of bug#1069361 to the same value Ignoring request to change the forwarded-to-address of bug#1073464 to the same value > thanks Stopping processing here. Please contact me if you need assistance. -- 1069361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069361 1073464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061732: marked as done (aspcud: depends on RC buggy gringo)
Your message dated Mon, 24 Jun 2024 15:58:44 +0800 with message-id and subject line close the bug has caused the Debian Bug report #1061732, regarding aspcud: depends on RC buggy gringo 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.) -- 1061732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aspcud Version: 1:1.9.6-2 Severity: serious Tags: sid trixie Hi Maintainer aspcud has a dependency on gringo which has been RC buggy [1] since October 2023. I'm filing this bug because aspcud is considered a "key package" [2] due to a dependency in apt-cudf, and as such, does not receive notifications of RC bugs in its dependencies. Regards Graham [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054688 [2] https://release.debian.org/key-packages.html --- End Message --- --- Begin Message --- Hi, I think we can close the bug safely because #1054688 has been addressed. Please reopen it if there is any issue. [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054688--- End Message ---
