Bug#1060138: marked as done (vlc-plugin-bittorrent: track vlc plugin ABI)
Your message dated Fri, 12 Jan 2024 07:50:03 + with message-id and subject line Bug#1060138: fixed in vlc-plugin-bittorrent 2.15-1 has caused the Debian Bug report #1060138, regarding vlc-plugin-bittorrent: track vlc plugin ABI 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.) -- 1060138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vlc-plugin-bittorrent Version: 2.14-4 Severity: serious X-Debbugs-Cc: sramac...@debian.org vlc-plugin-bittorrrent fails to track VLC's plugin ABI. libvlccore9 provides a virtual package vlc-plugin-abi-$X which indicates the ABI that is currently supported by vlc. Please ensure that vlc-plugin-bittorrent also depends on the correct version. You can take the following bit from vlc-plugin-pipewire to produce the vlc:PluginABI substvar to use in debian/control: override_dh_gencontrol-arch: sed -n 's/^# define MODULE_SYMBOL \([0-9][_0-9a-z]*\)/-Vvlc:PluginABI=vlc-plugin-abi-\1/p' \ /usr/include/vlc/plugins/vlc_plugin.h | tr _ - | xargs dh_gencontrol -a -- Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: vlc-plugin-bittorrent Source-Version: 2.15-1 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of vlc-plugin-bittorrent, 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. Petter Reinholdtsen (supplier of updated vlc-plugin-bittorrent package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Jan 2024 08:34:49 +0100 Source: vlc-plugin-bittorrent Architecture: source Version: 2.15-1 Distribution: unstable Urgency: medium Maintainer: Petter Reinholdtsen Changed-By: Petter Reinholdtsen Closes: 1060138 Changes: vlc-plugin-bittorrent (2.15-1) unstable; urgency=medium . * New upstream version 2.15 * Corrected d/rules comment on $HOME setting. * Added VLC plugin API package relation to ensure VLC compatibility. (Closes: #1060138) Checksums-Sha1: 5d87a9c8b69f2c83098014f6a61c2ace2e8ce96b 2113 vlc-plugin-bittorrent_2.15-1.dsc 64fee796adf22a8a5b0ab5a58d06662d9c1e526c 283872 vlc-plugin-bittorrent_2.15.orig.tar.gz ebcb9624233c28306121c203eae2e6b4b53c98cc 4672 vlc-plugin-bittorrent_2.15-1.debian.tar.xz 2c06ad5cf601c96cb805e41d968fd3906a879a65 6955 vlc-plugin-bittorrent_2.15-1_source.buildinfo Checksums-Sha256: d04fa2f810628835021c5395a6314cb9d75ce9ec019103d06cadfff96bf45c08 2113 vlc-plugin-bittorrent_2.15-1.dsc 9958fa65f1ea12b11a2990fd25a0d6546e3bc5f6d9bf221774aa9178b00edaa5 283872 vlc-plugin-bittorrent_2.15.orig.tar.gz 21f351c8d4cf964c78bee3bddb03545328f3772b61ac4f0ccfb368718f81bf17 4672 vlc-plugin-bittorrent_2.15-1.debian.tar.xz 0a50dac4a926d31fc83f41fce7e08368466ca645922af4f29812f1e3d7c7082d 6955 vlc-plugin-bittorrent_2.15-1_source.buildinfo Files: 9c24a6e46e0408c35f48f18a45b6e3ea 2113 video optional vlc-plugin-bittorrent_2.15-1.dsc 4bd17a11fda2a1e95ca6df1f1af776d5 283872 video optional vlc-plugin-bittorrent_2.15.orig.tar.gz 660651a508514a3c8709915de5e10b97 4672 video optional vlc-plugin-bittorrent_2.15-1.debian.tar.xz 0b72cc230b090dabad7a46608ccc4b46 6955 video optional vlc-plugin-bittorrent_2.15-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmWg6+wACgkQgSgKoIe6 +w5ZtRAAsm9tbzGs19Kixl/cdLiqzgsaHkoURNXFgOCodRpCA9gaYQt7vI68l0Y0 G2/EBqM3k3QttMTnADuW3OZED8g2xsM1lZ3PZrQrG6onUKrM0oqBw5iFcgsU5ePk Ogq196xwh8V0HhAtFylDx2UnkgwClOvC2pgt3QtPgMTnMccOWUOeBye2+3aN8mEz 6ZDHBnWeRB2jsWmaxOfDqs49n4P5UUPT9ivp9JYjS73hGZ5UFZ9xtrx0tAujaewP 9BWVCGxlBLoDYKzL3EnlyfEnYN8iRNZh+Jhoo/Gxkdl1eIC3ffz80LGg1S87FtZh 7/f65nDdCz1Jh4oEeGTD/A5ApIUlHNQp2LFI9yqldQqPmwvBz6EMJJtBHjMhtEWF 0W50WbH0n8OgX8HnFfBiPBnq6iCM7Pdl5llTvU0MhPqgArFkHds0PRt5CWR0c5ML qVM5LjXpzJzwgFwwIR8SNIRv3obO3oNS1IdWRp8TN7N50CMab6CiDMgqxg3/DH0E vaDPGbdh60EnN5STwghDb33deVxboCYiOEf2sUcbeM3L+7tdrzjkUnqQMA7Hx4d0 TxoILna+B6aqTbENNikBgXmSHjmCy3BqEmB9eaP6Uj2/XgpyxwsmsviJ+HhraNdK vxPNGlZJcDo9W1qRsp9a2C97KJ4KyOw1Qj2Ix8bTMfmXNND60as= =vTZg -END
Processed: bug 1056522 is forwarded to https://github.com/Textualize/rich/pull/2968 ...
Processing commands for cont...@bugs.debian.org:
> forwarded 1056522 https://github.com/Textualize/rich/pull/2968
Bug #1056522 [src:rich] rich's autopkg tests fail with Python 3.12
Set Bug forwarded-to-address to 'https://github.com/Textualize/rich/pull/2968'.
> forwarded 1058314 https://github.com/Textualize/rich/pull/2968
Bug #1058314 [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/Textualize/rich/pull/2968'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056522
1058314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unblock 1055955 with 1042845 1040396
Processing commands for cont...@bugs.debian.org: > # only in sid > unblock 1055955 with 1042845 1040396 Bug #1055955 [release.debian.org] transition: perl 5.38 1055955 was blocked by: 1060653 1042844 1060323 1042845 1057318 1060456 1026046 1057424 1042853 1040396 1060458 1042521 1054793 1042525 1054776 1057270 1050451 1055955 was not blocking any bugs. Removed blocking bug(s) of 1055955: 1042845 and 1040396 > thanks Stopping processing here. Please contact me if you need assistance. -- 1055955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058301: resampy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
On Fri, 12 Jan 2024 08:07:41 +0100 s3v wrote: Dear Maintainer, > E If you are not working on Numba development, the original error was: 'cannot import name '_typeconv' from 'numba.core.typeconv' (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'. > E For help, please visit: > E > E https://numba.readthedocs.io/en/stable/user/faq.html#numba-could-not-be-imported This is issue was fixed in numba/0.58.1+dfsg-1 [1] actually in unstable and I've verified your package builds fine locally and autopkg tests pass as well. Kind Regards [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058301 Thanks a lot -- Antonio Valentino
Processed: block 1055955 with 1060653
Processing commands for cont...@bugs.debian.org: > block 1055955 with 1060653 Bug #1055955 [release.debian.org] transition: perl 5.38 1055955 was blocked by: 1057270 1050451 1042844 1042521 1060458 1042525 1054793 1042845 1057424 1026046 1060456 1042853 1040396 1057318 1060323 1054776 1055955 was not blocking any bugs. Added blocking bug(s) of 1055955: 1060653 > thanks Stopping processing here. Please contact me if you need assistance. -- 1055955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060653: os-autoinst: FTBFS on i386: t/01-test_needle.t failure
Source: os-autoinst Version: 4.6.1699947509.970d0609-1 Severity: serious Tags: ftbfs This package failed to build against Perl 5.38 in sid on i386 with three retries so far. The issue is currently a blocker for the ongoing Perl 5.38 transition. Latest log is at https://buildd.debian.org/status/fetch.php?pkg=os-autoinst=i386=4.6.1699947509.970d0609-1=1704966657=0 3: # Failed test 'found area is the original one too' 3: # at ./t/01-test_needle.t line 95. 3: # got: '944' 3: # expected: '108' 3: # Looks like you failed 1 test of 84. [...] 3: Test Summary Report 3: --- 3: ./t/01-test_needle.t (Wstat: 256 (exited 1) Tests: 84 Failed: 1) 3: Failed test: 16 3: Non-zero exit status: 1 3: Files=52, Tests=1222, 126 wallclock secs ( 0.68 usr 0.14 sys + 110.76 cusr 12.18 csys = 123.76 CPU) 3: Result: FAIL 3/3 Test #3: test-perl-testsuite ..***Failed 125.71 sec The following tests passed: test-installed-files test-doc-testapi-spellchecking 67% tests passed, 1 tests failed out of 3 Total Test time (real) = 126.44 sec The following tests FAILED: 3 - test-perl-testsuite (Failed) Errors while running CTest Output from these tests are in: /<>/build/Testing/Temporary/LastTest.log Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely. FAILED: CMakeFiles/check-pkg-build /<>/build/CMakeFiles/check-pkg-build cd /<>/build && /usr/bin/ctest -V -E test-local-.* ninja: build stopped: subcommand failed. make[1]: *** [debian/rules:46: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: binary-arch] Error 2 -- Niko Tyni nt...@debian.org
Bug#1058301: resampy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Dear Maintainer, > E If you are not working on Numba development, the original error was: > 'cannot import name '_typeconv' from 'numba.core.typeconv' > (/usr/lib/python3/dist-packages/numba/core/typeconv/__init__.py)'. > E For help, please visit: > E > E > https://numba.readthedocs.io/en/stable/user/faq.html#numba-could-not-be-imported This is issue was fixed in numba/0.58.1+dfsg-1 [1] actually in unstable and I've verified your package builds fine locally and autopkg tests pass as well. Kind Regards [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058301
Processed: [mutagen] Bug #1042647: forward to upstream fix
Processing commands for cont...@bugs.debian.org: > forwarded 1042647 > https://github.com/quodlibet/mutagen/commit/37b4e6bddc03e1f71542 Bug #1042647 [src:mutagen] mutagen: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting Set Bug forwarded-to-address to 'https://github.com/quodlibet/mutagen/commit/37b4e6bddc03e1f71542'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059040: libxml2: ABI change? (undefined references)
Rafael * Rene Engelhard [2023-12-25 23:48]: Hi, Am 25.12.23 um 22:57 schrieb Rene Engelhard: I didn't file it for the plain build issue. Nevertheless, if it broke so many projects you probably should do a full-fledged rebuild and send Well, mitigated by 2.12.3, but still. But again, this is completely off-topic to what I filed in this bug which is the ABI break. Which *maybe* could be ignored. Maybe one can do Breaks: after a rebuild (then you might get a problem inbetween only when in this case libreoffice is to be rebuilt. But here libreoffice fails its tests even). But not until one knows what is affected. *You* need to do a test as the library maintainer/the one who wants to update it, not me. The current issue has the potential of introducing a *huge* breakage in the distribution, due to the chain of (build-)dependencies. For instance, I tried to rebuild the plplot package in my up-to-date experimental chroot, in order to make it comply with the upcoming gnat-12 ⇒ gnat-13 transition. I ran into this, when trying to install the build-dependencies for plplot : $ pdebuild […] Setting up octave (8.4.0-1+b1) ... /usr/bin/octave-cli: symbol lookup error: /lib/libGraphicsMagick-Q16.so.3: undefined symbol: xmlNanoFTPInit, version LIBXML2_2.4.30 dpkg: error processing package octave (--configure): […] Errors were encountered while processing: octave E: Sub-process /usr/bin/dpkg returned an error code (1) If a new version of graphicsmagick were uploaded to experimental, then the problem would go away. Indeed, when the graphicsmagick package is rebuilt in experimental, the configure script does detect the absence of the xmlNanoFTPNewCtxt function in the libxml2 library (version 2.12.3+dfsg-0exp1) and disables the call to the xmlNanoFTP* functions. However, this rebuilt will not be automatically triggered without a bump in the SONAME version of libxml2. In summary, the introduction of version 2.12 of libxml2 in unstable will need a proper and coordinated transition. Best, Rafael Laboissière
Processed: bug 1058340 is forwarded to https://github.com/mkdocstrings/python/issues/121
Processing commands for cont...@bugs.debian.org:
> forwarded 1058340 https://github.com/mkdocstrings/python/issues/121
Bug #1058340 [src:mkdocstrings-python-handlers] mkdocstrings-python-handlers:
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
"3.12 3.11" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/mkdocstrings/python/issues/121'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060323: marked as done (libosp-dev: missing dependency on libosp5)
Your message dated Fri, 12 Jan 2024 04:35:14 + with message-id and subject line Bug#1060323: fixed in opensp 1.5.2-15 has caused the Debian Bug report #1060323, regarding libosp-dev: missing dependency on libosp5 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.) -- 1060323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libosp-dev Version: 1.5.2-14 Severity: serious Hi, the libosp-dev package in sid is missing a dependency on libosp5, leaving /usr/lib/libosp.so a dangling symlink and making at least libsgml-parser-opensp-perl (and probably other packages build-depending on libosp-dev) fail to build. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: opensp Source-Version: 1.5.2-15 Done: Neil Roeth We believe that the bug you reported is fixed in the latest version of opensp, 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. Neil Roeth (supplier of updated opensp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jan 2024 22:48:37 -0500 Source: opensp Architecture: source Version: 1.5.2-15 Distribution: unstable Urgency: medium Maintainer: Neil Roeth Changed-By: Neil Roeth Closes: 871755 1060323 Changes: opensp (1.5.2-15) unstable; urgency=medium . * Fixed missing dependencies for libosp-dev, thanks to Niko Tyni and Gregor Herrmann (Closes: #1060323). * Changed build dependency on jadetex to texlive-formats-extra, thanks to Norbert Preining (Closes: #871755). Checksums-Sha1: b06cdb83339e89f85d7b06c69bd57cae256967e2 1984 opensp_1.5.2-15.dsc 2d371d98c34701499617714333c5a38eed83582e 13640 opensp_1.5.2-15.debian.tar.xz ed8f909ba4d7c55efd294af6774cfc32d48ef409 9714 opensp_1.5.2-15_amd64.buildinfo Checksums-Sha256: e6ee403e7cc4eff51bb1fbb1185143944180430683f92e3f3cdc86ff697953d2 1984 opensp_1.5.2-15.dsc fe87833fc12bb917799af5734f3ef95a0d1794bd89e3bb5bb1b7d67cf33066ad 13640 opensp_1.5.2-15.debian.tar.xz d7a9c990b0556f17a6000d17a613187b171937355e2ca0857e5ad1a9b2124f82 9714 opensp_1.5.2-15_amd64.buildinfo Files: fd4bfe42e968846045ec51cf4febde8b 1984 text optional opensp_1.5.2-15.dsc c8b6e3be058678cdf30efbf4e1f87b9f 13640 text optional opensp_1.5.2-15.debian.tar.xz e45f1c9c96911281eadafe763ec413dd 9714 text optional opensp_1.5.2-15_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYdR7of/nqgLv7YjKNlwUCaSzpkAFAmWgvG8ACgkQNlwUCaSz pkCy8A/+OgJKFenQE1zo91r73S7Evro3uJr5n1Q/qHD3nEMG9znGmPgFKqjUtZfS sTslGBQwZnLITaz2jn8RABIbMrKK4/vWMro4fEXtsCuFVKHR6eyldJB3GFwsj1lu ogw0+2H4WPN5V0o3slYCoB1Rbj8QzB7XiOUCl2331fazqev3YggKQcp/jLmTfn1h RmTuIDQT9JngMrJ2VYEaY2qIvdYLCn2xtGILztEldxfgzO2zuMsnnvKdE6WsQPAo qBl1pwePos7qr83am90nP44U9zcR6QEoGkkIaA0cu1wzQfe4I2tAmjOL9Nk99lSV SQVM17dESgfJR0bt2Z+c+LZbD/Drf7CrK0LzZntdeZSckAcrzBZ10A2Dd5Pw0mbU 4h/c6c0FgGNBBl3iCVHYeGdZUazyxpgPEvLvzKRf4eL5TSUJuu+f6SvRd1UPDh0j mxmqACXJdS45gceY9jgsG6rDuoBSfgceGOufyn5XKi6gTjRzvc7KPKbF/E9mdxGR MlDK0bK5TTFOClvSGSdcGc/kpBoV09EHRrwgQxEDBegD39QGs9bMwP2K2c3bUI8I KiMkycCtFHBlMhIohv0fMvOwxCVKXzp8O7exOuDNs9uccI9xeDCMxXlR90J9RPX9 MZ6XMfaR3nceBLkEoig/Xklw18rByznfkPmzDEq7DuVbuQmlMdc= =C9qS -END PGP SIGNATURE End Message ---
Bug#1059634: marked as done (pythran: autopkgtest failure with Python 3.12)
Your message dated Fri, 12 Jan 2024 03:21:07 + with message-id and subject line Bug#1059634: fixed in pythran 0.14.0+ds-5 has caused the Debian Bug report #1059634, regarding pythran: 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.) -- 1059634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pythran Version: 0.14.0+ds-4 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer pythran'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/p/pythran/testing/amd64/ 51s ERRORS 51s ERROR collecting test_base.py _ 51s ImportError while importing test module '/tmp/autopkgtest-lxc.xw1rtk3i/downtmp/autopkgtest_tmp/pythran_tests/test_base.py'. 51s Hint: make sure your test modules/packages have valid Python names. 51s Traceback: 51s /usr/lib/python3/dist-packages/pythran/dist.py:17: in 51s from distutils.command.build_ext import build_ext as LegacyBuildExt 51s E ModuleNotFoundError: No module named 'distutils' 51s 51s During handling of the above exception, another exception occurred: 51s /usr/lib/python3.12/importlib/__init__.py:90: in import_module 51s return _bootstrap._gcd_import(name[level:], package, level) 51s __init__.py:29: in 51s from pythran import compile_pythrancode, spec_parser, load_specfile, frontend 51s /usr/lib/python3/dist-packages/pythran/__init__.py:127: in __getattr__ 51s import pythran.toolchain 51s /usr/lib/python3/dist-packages/pythran/toolchain.py:11: in 51s from pythran.dist import PythranExtension, PythranBuildExt 51s /usr/lib/python3/dist-packages/pythran/dist.py:19: in 51s from setuptools.command.build_ext import build_ext as LegacyBuildExt 51s E ModuleNotFoundError: No module named 'setuptools' --- End Message --- --- Begin Message --- Source: pythran Source-Version: 0.14.0+ds-5 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of pythran, 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. Drew Parsons (supplier of updated pythran package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Jan 2024 03:44:08 +0100 Source: pythran Architecture: source Version: 0.14.0+ds-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Drew Parsons Closes: 1059634 Changes: pythran (0.14.0+ds-5) unstable; urgency=medium . * Team upload. * python3-pythran Depends: python3-setuptools. No longer automatically included in python 3.12. Closes: #1059634. Checksums-Sha1: f63922a0b0f0e6ec7fae92a90b18f1402cc90e96 2505 pythran_0.14.0+ds-5.dsc 5602dfcd12b7329537f24b34ec731faff982df59 15720 pythran_0.14.0+ds-5.debian.tar.xz Checksums-Sha256: 87631756bec272258d7a3b3635d3fa756c5aaae1937f37b4714d34f074ee67d2 2505 pythran_0.14.0+ds-5.dsc e1a983a76648059f9e4141162b46475653663bd097d3a1ad120e64e995fbfd50 15720 pythran_0.14.0+ds-5.debian.tar.xz Files: 55dd40d500cc201f66e250c97906756e 2505 python optional pythran_0.14.0+ds-5.dsc c27035f39437a954bb71a0e849b2ed41 15720 python optional pythran_0.14.0+ds-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmWgqsoACgkQVz7x5L1a Afrpew/9E05JjzMQvTKSa7KsV7HX4gH6pVscKiCt0nWbnAswscKrqW7k1nr82N7J PHWQbNKdcWQCE/d4xCK4BaLGxb7bQXjEIpoOs7sE1aD9GjgRTmFmt0IFjae9NNRK Q9mhCm/RH2bIl8wTDDu4ucDX0RiAK51W1PDpUfZvq8sTP5HonCVf5bBf0OFv59N6 NsOiQItA9qYHFMw5WcJXIoR/QE4sHIbgzLW+NmFPfVbuiCl/mUS99C/9OyZSEn+9 QJq7y0wgVRB7yBzs8yinTq/XDmdSa5lR5Zn5mxkYvytCFhqoJ8qI/tXDe20G6rDi scQUOR22/uxuZO4q4LfveXmQSm6AfyND03wz12QTp9TOcCj1dg8TE995DNH+NAm7 y1KCMNvtyJfE36ktjGIzISCqilaL5f5v1NWuumYj3DTg73SMWsdMHarP9DRb2twd UvLDytkQgyPb0b5QKNFPn3v8OJWm5LJYnCrDJM+XxJayHeqa2/2Y6UJVX+NQ0sjd ZrvyxdP1gkJRJzkRoiBl+xeY/NIyiZln35W/kfBtHaD6hXnFYmLe352phUdan/u5
Processed: Bug#1059634 marked as pending in pythran
Processing control commands: > tag -1 pending Bug #1059634 [src:pythran] pythran: autopkgtest failure with Python 3.12 Added tag(s) pending. -- 1059634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059634: marked as pending in pythran
Control: tag -1 pending Hello, Bug #1059634 in pythran 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/pythran/-/commit/c05ed599007ee520c3b0d8817c3a692ff20d28b3 python3-pythran Depends: python3-setuptools No longer automatically included in python 3.12. Closes: #1059634. (this message was generated automatically) -- Greetings https://bugs.debian.org/1059634
Processed: Re: nautilus: tracker build test failure
Processing commands for cont...@bugs.debian.org: > severity 1050733 normal Bug #1050733 [src:nautilus] nautilus: tracker build test failure Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1050733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026046: marked as done (libdevel-mat-perl: FTBFS: test failures on some architectures)
Your message dated Fri, 12 Jan 2024 00:25:16 + with message-id and subject line Bug#1026046: fixed in libdevel-mat-perl 0.51-2 has caused the Debian Bug report #1026046, regarding libdevel-mat-perl: FTBFS: test failures on some architectures 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.) -- 1026046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdevel-mat-perl Version: 0.49-1 Severity: important Tags: upstream Forwarded: https://rt.cpan.org/Ticket/Display.html?id=134117 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 According to https://buildd.debian.org/status/package.php?p=libdevel-mat-perl the package has a test failure on at least i386 and mipsel64el but maybe the architectures are just random. There's also an upstream issue: https://rt.cpan.org/Ticket/Display.html?id=134117 And failures on CPAN testers: http://matrix.cpantesters.org/?dist=Devel-MAT+0.49 Can't call method "_more_saved" on an undefined value at /tmp/loop_over_bdir-419118-EAl5mw/Devel-MAT-0.49-0/blib/lib/Devel/MAT/Dumpfile.pm line 516. t/02contexts.t ... Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmOYxYpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZcZA//SA59AIkGQjYT5VXZfjSVE3DNBz8dFpA47iTHqUH5ftP8xxd4FWo/lhxq oT9gDUtm5EIDLhshJvanve87OeVSPhXbe6yOB2MZC8wAQCvp8HGgUSNffiL2kKsC KZBaiRM36f9ZRxDGoTMfqAC8IrVX5t8UW/TA3+UnYCVpDIOpODSyZL7Prgvzejpy cwLdTUVc1Jq8cS/0vrFk0MY+GbYAB3PXebdpn4glEsZOFJTvF4iQpmNA4i/e0j7S ePnL+P+EdUkc+OVPLuoXweFnvh2d91/uEIW4qeQn3aZ/UfvvSSaS2t+3Xrvpqx11 YaVCWS19/PQYTX2kYma78PRsGUAEkRmenZlcz0p2EE9JyUfbL27XQOhIO/GZl2+z d4yp7BL0eQK+h6rqoGzAm+FBWPxlIQaoI2epPK7r30zrlHJ+6RWdPn5P1QgYqT69 r12IbVCgc9VcId6DfUtT3oxdLjJBvEE/yEBA4qi9Lu7TB35rPHf4mbUKjUOrYmt1 kauvdo/DiGcxicJChzY0vjDJySAn5llmzzGMS32/OcC9sfvc83wpWMnoL/OkLmGx B7EEjg6IJRwRHGSSQgTnCCLLXZlW5fINXvxzwacFI3goCb5w7MX+TEKOvD7r1t6e UDFMTzSDB3u0/jdhwsRREdx10WRDVdkEeYoEzNgcmTLplauSQbA= =uyZh -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libdevel-mat-perl Source-Version: 0.51-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libdevel-mat-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libdevel-mat-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jan 2024 00:49:07 +0100 Source: libdevel-mat-perl Architecture: source Version: 0.51-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1026046 Changes: libdevel-mat-perl (0.51-2) unstable; urgency=medium . * Add rt134117.patch (patch from upstream in CPAN RT ticket). Hopefully closes: #1026046. * Update years of packaging copyright. Checksums-Sha1: 29bfedd441e605890b2dd01a68a986cafedecdcf 2885 libdevel-mat-perl_0.51-2.dsc d320fa851f4621d80efcb451fae0a1e6def4110e 2712 libdevel-mat-perl_0.51-2.debian.tar.xz Checksums-Sha256: ebee8cc0afb5e204fcea3b66bc5cde07a354c68f1876005b189d6317aafdb18c 2885 libdevel-mat-perl_0.51-2.dsc 9aade36f92d45d58f156201b88760cd3a4b611a20c16d151120081b9ddc1c6dc 2712 libdevel-mat-perl_0.51-2.debian.tar.xz Files: 7e2bda09cde3971d889bd731d1af17a6 2885 perl optional libdevel-mat-perl_0.51-2.dsc b889f8cdca6d646e0b06c6ba4cbf 2712 perl optional libdevel-mat-perl_0.51-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmWgf5NfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbiqQ/9H22yNE4C0ZihpJ9HJRKRuVU6wvPY2z+iEG5h2EDbRam8H/ArxqzoFJkV 4BTUk+ZRlafbiHq3SRY5ppGcz+ZCVSwRPefdNQrYoOeZ5z9BdpHRNKQp6xXm+7mi UsAM+jVAOzitZKRkHCSibrNau2hfz31aL/xowD9umRIykSUE2ODx0W/Pa4wQcPlq
Bug#1059978: rosegarden: team uploading and git committed changes
Hi Gianfranco On 08/01/2024 23:01, Gianfranco Costamagna wrote: I've prepared an Team upload for rosegarden (versioned as 1:22.12.1-2) and uploaded it to DELAYED/15. Please feel free to tell me if I should delay it longer. Excellent - many thanks for the patch, commit to git, and upload! cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#1033258: marked as done (upx-ucl: CVE-2023-23456)
Your message dated Thu, 11 Jan 2024 23:20:23 + with message-id and subject line Bug#1033258: fixed in upx-ucl 4.2.2-1 has caused the Debian Bug report #1033258, regarding upx-ucl: CVE-2023-23456 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.) -- 1033258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: upx-ucl X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for upx-ucl. CVE-2023-23456[0]: | A heap-based buffer overflow issue was discovered in UPX in | PackTmt::pack() in p_tmt.cpp file. The flow allows an attacker to | cause a denial of service (abort) via a crafted file. https://github.com/upx/upx/commit/510505a85cbe45e51fbd470f1aa8b02157c429d4 https://github.com/upx/upx/issues/632 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-23456 https://www.cve.org/CVERecord?id=CVE-2023-23456 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: upx-ucl Source-Version: 4.2.2-1 Done: Robert Luberda We believe that the bug you reported is fixed in the latest version of upx-ucl, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Luberda (supplier of updated upx-ucl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jan 2024 23:00:58 +0100 Source: upx-ucl Architecture: source Version: 4.2.2-1 Distribution: unstable Urgency: medium Maintainer: Robert Luberda Changed-By: Robert Luberda Closes: 1004137 1025053 1033258 Changes: upx-ucl (4.2.2-1) unstable; urgency=medium . * New upstream version (closes: #1025053): - fixes heap-based buffer overflow issue CVE-2023-23456 (closes: #1033258); - fixes segmentation fault issue CVE-2023-23457 (closes: #1033258); - fixes execution of compressed MIPS binaries (closes: #1004137); - unfortunately both zlib and ucl libraries are now embedded into the upx-ucl binary - this should be fixed in the future somehow. * Remove no longer needed patches 02-arm64-crashes.patch and 03-upstream-silence-compilation-warnings.patch. * Update debian/source/lintan-overrides in a try to disable its useless checks on debian/tests files (see: #1025452). * Update debian/rules for cmake that is now used by upstream. * Add new debian/test cases for the above CVE issues. * Update debian/copyright. * Update standards version to 4.6.2, no changes needed. Checksums-Sha1: 8efa9e19f6f0ef7d36adc92186b333dbb289a4e3 1884 upx-ucl_4.2.2-1.dsc b9144e18a250312576134eb8f21dfdd4044f 1275320 upx-ucl_4.2.2.orig.tar.xz c8758f77d3ffe29a0e1aa778607aaeec0640884f 64892 upx-ucl_4.2.2-1.debian.tar.xz 0ad0f3092efef8f2a1003ff41042b3e5fd90c75d 7370 upx-ucl_4.2.2-1_amd64.buildinfo Checksums-Sha256: 2e451b7dd95950cf32cbcf725c023bdd0dc5d774b4ff73fe947995b036148d3f 1884 upx-ucl_4.2.2-1.dsc 42ee0455eea610ef7ee732aa1f657b34a351ebcfa64a24c1e2a7aaec74c1e038 1275320 upx-ucl_4.2.2.orig.tar.xz ce1b366a4cacd4ffc6e15af0fc991c0086dffacc2149d43aa95e9fbcf2b6fa39 64892 upx-ucl_4.2.2-1.debian.tar.xz a0a95d630258205493c0e67a776364e9118ba09d4d9dcafb2457c250b2a26212 7370 upx-ucl_4.2.2-1_amd64.buildinfo Files: cbe142d0d840cc1f5ac6df6ca179b1e2 1884 utils optional upx-ucl_4.2.2-1.dsc 97ea082bc7240b8083316293e2be0e29 1275320 utils optional upx-ucl_4.2.2.orig.tar.xz 7db90a6a34a0cfcad9cb122776751afe 64892 utils optional upx-ucl_4.2.2-1.debian.tar.xz a03369152abbc41d68b66864f636c940 7370 utils optional upx-ucl_4.2.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEENeh2+rTTcy6TtNI3Yx3nVTvor9QFAmWgaRIACgkQYx3nVTvo r9Sz7hAAo36X1PtAgn4HjLtOze5Qy/546efLlMDJuPducDJ/mypydN3DiN6XsgaV wrkAK5aSEwj1+2VOjisA12Q9N1KNBFEXjEiVUur+S1Yhx0nsrH1Ll3cQkU6kKxZT v1YeO42BliPcUk1X36DcxGM3weJPukppUMOjLvrOAUKgA1VVY9dVYrvP8rNijKAI
Bug#1058517: dvdisaster: FTBFS: make[2]: *** [GNUmakefile:219: manual] Error 2
Control: forwarded -1 https://hg.jcea.es/dvdisaster/rev/03a51becc4c8 Please import this upstream patch to fix this.
Processed: Re: dvdisaster: FTBFS: make[2]: *** [GNUmakefile:219: manual] Error 2
Processing control commands: > forwarded -1 https://hg.jcea.es/dvdisaster/rev/03a51becc4c8 Bug #1058517 [src:dvdisaster] dvdisaster: FTBFS: make[2]: *** [GNUmakefile:219: manual] Error 2 Set Bug forwarded-to-address to 'https://hg.jcea.es/dvdisaster/rev/03a51becc4c8'. -- 1058517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059869: autopkgtest fails
Ping. It is now 1 week until this will auto-remove several packages. Please consider releasing and packaging the new release.
Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf
Hi Julian, On 2024-01-11 05:46, Julian Andres Klode wrote: > And there aren't any hard errors. We could zero initialize > those or add supressions to make things look nicer I suppose. Mmmh no, they are all actual errors as far as valgrind is concerned. The thing is, you're running valgrind without --error-exitcode. By doing so, the exit code of your tests is the exit code of apt-get, not of valgrind. Try this instead: (sid-amd64)root@ariel:~# valgrind --error-exitcode=1 apt-get update [...] ==308534== ERROR SUMMARY: 6 errors from 6 contexts (suppressed: 0 from 0) (sid-amd64)root@ariel:~# echo $? 1
Bug#1060458: perl-tk: FTBFS with Perl 5.38 on big-endian 64-bit: test failures
On Thu, 11 Jan 2024 21:29:50 +0200, Niko Tyni wrote: > This is currently a hard blocker for the ongoing Perl 5.38 transition as > perl-tk has quite a few reverse dependencies that are now uninstallable > on s390x. Georges, in case you don't find the time to upload a fixed package, I'm happy to do an NMU with Niko's patch to unblock the perl transition. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1052844: marked as done (deepdiff: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Thu, 11 Jan 2024 20:50:29 +
with message-id
and subject line Bug#1052844: fixed in deepdiff 6.7.1-1
has caused the Debian Bug report #1052844,
regarding deepdiff: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 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.)
--
1052844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepdiff
Version: 6.2.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 --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:291: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:291: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/deephash.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/model.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/serialization.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/base.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/distance.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/lfucache.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/search.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/diff.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/path.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/anyset.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/helper.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/operator.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/delta.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> copying deepdiff/commands.py ->
> /<>/.pybuild/cpython3_3.11/build/deepdiff
> running egg_info
> creating deepdiff.egg-info
> writing deepdiff.egg-info/PKG-INFO
> writing dependency_links to deepdiff.egg-info/dependency_links.txt
> writing entry points to deepdiff.egg-info/entry_points.txt
> writing requirements to deepdiff.egg-info/requires.txt
> writing top-level names to deepdiff.egg-info/top_level.txt
> writing manifest file 'deepdiff.egg-info/SOURCES.txt'
> reading manifest file 'deepdiff.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'AUTHORS'
> warning: no files found matching 'CHANGELOG'
> warning: no files found matching '*.rst'
> warning: no files found matching 'deepdiff/*.rst'
> warning: no previously-included files matching '__pycache__' found anywhere
> in distribution
> warning: no previously-included files matching '*.py[co]' found anywhere in
> distribution
> adding license file 'LICENSE'
> adding license file 'AUTHORS.md'
> writing manifest file 'deepdiff.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:291: cd /<>/.pybuild/cpython3_3.11/build;
> python3.11 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0
> rootdir: /<>/.pybuild/cpython3_3.11/build
> configfile: pytest.ini
> collected 752 items / 2 errors
>
> ERRORS
>
> ERROR collecting tests/test_command.py
>
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/tests/test_command.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_command.py:6: in
> from conftest import FIXTURES_DIR
> E ModuleNotFoundError: No module named 'conftest'
> _ ERROR collecting tests/test_serialization.py
> _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/tests/test_serialization.py'.
> Hint: make sure
Bug#1026046: FTBFS: test failures on some architectures
On Thu, 11 Jan 2024 21:50:33 +0200, Niko Tyni wrote: > Either it's gotten worse or it's just bad luck, but previously built > archs (armhf and armel) are now failing, making this release critical > and blocking the Perl 5.38 transition. I also noticed that the new failures are slightly different than the previous ones we (or the upstream ticket) mentioned, and I'm not sure this fallout is confined to specific architectures. > Guess we could just skip / ignore t/02context.t, or alternatively make > the build fail deterministically on the affected architectures and remove > the existing binaries... Luckily libdevel-mat-perl is no key package and has no reverse dependencies, so it can safely be removed from testing until upstream finds the time to look into this issue … Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1058414: python-itsdangerous: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Dear Maintainer, I've successfully built your package locally after commenting these lines [1]. I guess is safe to stop treating warning as errors for downstream users. Kind Regards [1] https://sources.debian.org/src/python-itsdangerous/2.1.2-3/setup.cfg/#L40-L41
Processed: Bug#1052849 marked as pending in python-pkginfo
Processing control commands:
> tag -1 pending
Bug #1052849 [src:python-pkginfo] python-pkginfo: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.
--
1052849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1052849: marked as pending in python-pkginfo
Control: tag -1 pending Hello, Bug #1052849 in python-pkginfo 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-pkginfo/-/commit/84978dbed4417cd40d3fc3eb04ee0385bdb5fe33 Run the build-time tests with tox, so that the package is installed. Closes: #1052849 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052849
Bug#1052849: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Hi Andreas (2024.01.11_17:48:43_+) > I've fixed the two other bugs in python-pkginfo and upgraded to latest > upstream. Unfortunately I have no clue about this issue. The test is expecting the module to be installed in the test environment. Either we could try harder to emulate that, or skip the tests. I committed a patch to run the test inside tox, which will install it in a virtualenv before running the test. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Processed: Re: importlib-resources: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11_importlib_resources/build/importlib_resources/tests/zipdat
Processing control commands: > tags -1 moreinfo Bug #1052903 [src:importlib-resources] importlib-resources: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11_importlib_resources/build/importlib_resources/tests/zipdata01/ziptestdata.zip' Added tag(s) moreinfo. > tags -1 unreproducible Bug #1052903 [src:importlib-resources] importlib-resources: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11_importlib_resources/build/importlib_resources/tests/zipdata01/ziptestdata.zip' Added tag(s) unreproducible. > severity -1 important Bug #1052903 [src:importlib-resources] importlib-resources: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11_importlib_resources/build/importlib_resources/tests/zipdata01/ziptestdata.zip' Severity set to 'important' from 'serious' -- 1052903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052903: importlib-resources: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11_importlib_resources/build/importlib_resources/tests/zipdata0
Control: tags -1 moreinfo Control: tags -1 unreproducible Control: severity -1 important Hi, I've tried to reproduce the issue but failed in my local pbuilder. May be that issue vanished somehow? Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#1026046: FTBFS: test failures on some architectures
Processing control commands: > found -1 0.51-1 Bug #1026046 [src:libdevel-mat-perl] libdevel-mat-perl: FTBFS: test failures on some architectures Marked as found in versions libdevel-mat-perl/0.51-1. > severity -1 serious Bug #1026046 [src:libdevel-mat-perl] libdevel-mat-perl: FTBFS: test failures on some architectures Severity set to 'serious' from 'important' > block 1055955 with -1 Bug #1055955 [release.debian.org] transition: perl 5.38 1055955 was blocked by: 1060458 1042525 1060323 1054776 1057270 1040396 1050451 1042845 1042521 1057424 1042853 1057318 1054793 1042844 1055955 was not blocking any bugs. Added blocking bug(s) of 1055955: 1026046 -- 1026046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026046 1055955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037883: vimix: ftbfs with GCC-13
This should be resolved with the current upstream release.
Bug#1060459: scalpel: Scalpel not working on Apple Silicon
Package: scalpel Version: 1.60-10 Severity: grave Tags: patch Justification: renders package unusable X-Debbugs-Cc: goldenrich...@gmail.com Dear Maintainer, * What led up to the situation? I am the author of Scalpel. Execution of Scalpel 1.60 (the version that is currently in the scalpel package on Debian et al) fails completely on VMs hosted on Apple Silicon because of some long-standing memory corruption bugs. It may also work incorrectly on other platforms. * What exactly did you do (or not do) that was effective (or ineffective)? I have placed updated source distros for Scalpel 1.60 as well as the newer (and more powerful) Scalpel 2.02 on GitHub via https://github.com/nolaforensix/scalpel-1.60 and https://github.com/nolaforensix/scalpel-2.02. My recommendation is to rebuild the 1.60 package from the updated source and also consdering adding 2.02. * What was the outcome of this action? Scalpel is broken and I fixed it :) * What outcome did you expect instead? N/A? -- System Information: Distributor ID: Kali Description:Kali GNU/Linux Rolling Release:2023.4 Codename: kali-rolling Architecture: x86_64 Kernel: Linux 6.5.0-kali3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages scalpel depends on: ii libc6 2.37-12 scalpel recommends no packages. scalpel suggests no packages. -- no debconf information
Processed: block 1055955 with 1060458
Processing commands for cont...@bugs.debian.org: > block 1055955 with 1060458 Bug #1055955 [release.debian.org] transition: perl 5.38 1055955 was blocked by: 1042844 1054776 1050451 1057318 1060323 1042845 1057270 1040396 1042853 1057424 1042525 1042521 1054793 1055955 was not blocking any bugs. Added blocking bug(s) of 1055955: 1060458 > thanks Stopping processing here. Please contact me if you need assistance. -- 1055955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060458: perl-tk: FTBFS with Perl 5.38 on big-endian 64-bit: test failures
Source: perl-tk
Version: 1:804.036+dfsg1-1
Severity: serious
Tags: ftbfs patch
User: debian-p...@lists.debian.org
Usertags: perl-5.38-transition
This package failed to build against Perl 5.38 on s390x, ppc64, sparc64,
and alpha.
This is because Perl upstream changed the implementation of SvPV() et
al., triggering a latent bug in perl-tk that bites on big endian 64-bit
architectures. The attached patch fixes this, see the commit message
for more detail. I've tested that it works on both s390x and amd64,
on Perl 5.36 (trixie) and 5.38 (sid).
Not sure why alpha is failing too, but it has a slightly different
failure mode. I suspect alignment issues.
This is currently a hard blocker for the ongoing Perl 5.38 transition as
perl-tk has quite a few reverse dependencies that are now uninstallable
on s390x.
# Failed test 'Creating Balloon widget'
# at t/balloon.t line 31.
# got: 'couldn't recognize image data at
/<>/blib/lib/Tk/Image.pm line 21.
# at /<>/blib/lib/Tk/Balloon.pm line 62.
# '
# expected: ''
[...]
Test Summary Report
---
t/balloon.t(Wstat: 512 (exited 2) Tests: 12 Failed: 11)
Failed tests: 2-12
Non-zero exit status: 2
Parse errors: Bad plan. You planned 14 tests but ran 12.
t/canvas.t (Wstat: 0 Tests: 166 Failed: 0)
TODO passed: 124
t/canvas2.t(Wstat: 65280 (exited 255) Tests: 0 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan. You planned 87 tests but ran 0.
t/listbox.t(Wstat: 0 Tests: 537 Failed: 0)
TODO passed: 320-322, 328, 502
t/photo.t (Wstat: 65280 (exited 255) Tests: 100 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan. You planned 111 tests but ran 100.
t/text.t (Wstat: 0 Tests: 415 Failed: 0)
TODO passed: 121
t/wm-tcl.t (Wstat: 0 Tests: 315 Failed: 0)
TODO passed: 86-87, 154-157, 164-165, 175-178, 221-224
237-239, 264-265, 275-276, 280-283
t/zzScrolled.t (Wstat: 0 Tests: 94 Failed: 0)
TODO passed: 52, 66, 80, 94
Files=76, Tests=4267, 36 wallclock secs ( 0.23 usr 0.05 sys + 6.02 cusr
0.69 csys = 6.99 CPU)
Result: FAIL
--
Niko Tyni nt...@debian.org
>From a26233c844c52f49ef9cca5f88dd9063aac60d0f Mon Sep 17 00:00:00 2001
From: Niko Tyni
Date: Thu, 11 Jan 2024 18:28:58 +
Subject: [PATCH] Fix STRLEN vs int pointer confusion in
Tcl_GetByteArrayFromObj()
Perl 5.37.2, more precisely commit
https://github.com/Perl/perl5/commit/1ef9039bccbfe64f47f201b6cfb7d6d23e0b08a7
changed the implementation of SvPV() et al., breaking t/balloon.t,
t/canvas2.t and t/photo.t on big-endian 64-bit architectures such as
ppc64 and s390x because StringMatchGIF() no longer recognized GIF files.
This is because Tcl_GetByteArrayFromObj() was calling SvPV() with an int
pointer instead of a correct STRLEN pointer, and the new implementation
is more sensitive to this: it assigns the pointers as-is, resulting in
the int pointer pointing at the wrong end of the 64-bit length.
Other functions taking a length pointer, at least Tcl_GetStringFromObj()
already seem to do things correctly, so presumably this is not a
systematic issue.
---
objGlue.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/objGlue.c b/objGlue.c
index d4927ea..dbd6a50 100644
--- a/objGlue.c
+++ b/objGlue.c
@@ -627,7 +627,10 @@ Tcl_GetByteArrayFromObj(Tcl_Obj * objPtr, int * lengthPtr)
sv_utf8_downgrade(objPtr, 0);
if (lengthPtr)
{
- return (unsigned char *) SvPV(objPtr, *lengthPtr);
+ STRLEN len;
+ unsigned char *s = SvPV(objPtr, len);
+ *lengthPtr = len;
+ return s;
}
else
{
--
2.30.2
Processed: Re: awscli: Please drop python-cryptography upper limit or increase it
Processing control commands: > tags -1 + patch Bug #1060455 [src:awscli] awscli: Please drop python-cryptography upper limit or increase it Added tag(s) patch. -- 1060455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060455: awscli: Please drop python-cryptography upper limit or increase it
Control: tags -1 + patch There is a diff at https://launchpad.net/ubuntu/+source/awscli/2.14.6-1ubuntu1 for this issue. You can ignore the build failure since that doesn't seem to currently affect Debian Unstable. Thank you, Jeremy Bícha
Bug#1060266: python3-ykman: Package uninstallable
Florian, I see you have a newer version of yubikey-manager staged in Salsa that would fix this RC bug. Could you either upload that version or upload a targeted fix for this issue? Thank you, Jeremy Bícha
Processed: [python-bottle] Bug #1058087: forward to upstream fix
Processing commands for cont...@bugs.debian.org: > forwarded 1058087 https://github.com/bottlepy/bottle/issues/1378 Bug #1058087 [src:python-bottle] python-bottle: FTBFS: ImportError: cannot import name 'test' from 'bottle.ext' (/<>/bottle.py) Set Bug forwarded-to-address to 'https://github.com/bottlepy/bottle/issues/1378'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055707: marked as done (python-acora fbfs with Python 3.12)
Your message dated Thu, 11 Jan 2024 19:05:57 +
with message-id
and subject line Bug#1055707: fixed in python-acora 2.4-0.1
has caused the Debian Bug report #1055707,
regarding python-acora fbfs 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.)
--
1055707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-acora
Version: 2.2-1.3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
python-acora fbfs with Python 3.12:
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:310: python3.12 setup.py config
Error compiling Cython file:
...
unsigned char
Py_UCS4
@cython.cdivision(True)
cdef inline _AcoraNodeStruct* _step_to_next_node(
^
acora/_cacora.pyx:698:48: Type is not specialized
WARNING: Generated .c files are missing, enabling Cython compilation
Building with Cython 3.0.5
Compiling acora/_acora.py because it changed.
Compiling acora/_cacora.pyx because it changed.
[1/2] Cythonizing acora/_acora.py
[2/2] Cythonizing acora/_cacora.pyx
Traceback (most recent call last):
File "/<>/setup.py", line 28, in
sys.argv.remove('--no-compile')
ValueError: list.remove(x): x not in list
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/setup.py", line 51, in
extensions = cythonize(extensions, annotate=True, language_level=3)
^^
File "/usr/lib/python3/dist-packages/Cython/Build/Dependencies.py",
line 1154, in cythonize
cythonize_one(*args)
File "/usr/lib/python3/dist-packages/Cython/Build/Dependencies.py",
line 1321, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: acora/_cacora.pyx
E: pybuild pybuild:395: configure: plugin distutils failed with: exit
code=1: python3.12 setup.py config
dh_auto_configure: error: pybuild --configure -i python{version} -p
"3.12 3.11" returned exit code 13
--- End Message ---
--- Begin Message ---
Source: python-acora
Source-Version: 2.4-0.1
Done: Bo YU
We believe that the bug you reported is fixed in the latest version of
python-acora, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bo YU (supplier of updated python-acora 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, 09 Jan 2024 09:52:46 +0800
Source: python-acora
Architecture: source
Version: 2.4-0.1
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen
Changed-By: Bo YU
Closes: 1055707 1056849
Changes:
python-acora (2.4-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
[ Bastian Germann ]
* Remove .git suffix from Vcs-Browser
.
[ Bo YU ]
* New upstream version 2.4. (Closes: #1056849, #1055707)
Checksums-Sha1:
b82df979d6d9a2ae5f3787468f3ed628d1ee7cf1 1779 python-acora_2.4-0.1.dsc
55c6812c15a57fb5fb36d43092c08ac3f6534393 266246 python-acora_2.4.orig.tar.gz
1144cc85b9b4b06e84a048b37ecb76cc2005d449 2672
python-acora_2.4-0.1.debian.tar.xz
8ce4f0afd2b5ae2de4753c40f868dc18aeba0e0f 6891
python-acora_2.4-0.1_source.buildinfo
Checksums-Sha256:
7d8d2c78454930d1081832d4b7a5a40f9c73488beea2125e0491da2abb65b286 1779
python-acora_2.4-0.1.dsc
15f1526a727a44a9f98ef4f8f1157885ba1f5e53d31d7a2f4c0b56a13c7e843b 266246
python-acora_2.4.orig.tar.gz
eb769aa46778ea969ebec1204cdd94314514e2ba1cee882fb91fe5abfa3b28dd 2672
python-acora_2.4-0.1.debian.tar.xz
ac657eb69df467e8ad56c60525aa6c6cbe1139c1b99417d395a2231cbc69b757 6891
python-acora_2.4-0.1_source.buildinfo
Files:
ed617e5e27414d4e086e8c64415efb59 1779 python optional python-acora_2.4-0.1.dsc
b4de657fa6e46c30bc091a52140803f9 266246 python optional
python-acora_2.4.orig.tar.gz
e7a948a64448e596489ed9ac3e40eefe 2672 python optional
Bug#1056849: marked as done (python-acora: ftbfs with cython 3.0.x)
Your message dated Thu, 11 Jan 2024 19:05:57 + with message-id and subject line Bug#1056849: fixed in python-acora 2.4-0.1 has caused the Debian Bug report #1056849, regarding python-acora: ftbfs with cython 3.0.x 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.) -- 1056849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-acora Version: 2.2-1.3 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: python-acora Source-Version: 2.4-0.1 Done: Bo YU We believe that the bug you reported is fixed in the latest version of python-acora, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bo YU (supplier of updated python-acora 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, 09 Jan 2024 09:52:46 +0800 Source: python-acora Architecture: source Version: 2.4-0.1 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Bo YU Closes: 1055707 1056849 Changes: python-acora (2.4-0.1) unstable; urgency=medium . * Non-maintainer upload. [ Bastian Germann ] * Remove .git suffix from Vcs-Browser . [ Bo YU ] * New upstream version 2.4. (Closes: #1056849, #1055707) Checksums-Sha1: b82df979d6d9a2ae5f3787468f3ed628d1ee7cf1 1779 python-acora_2.4-0.1.dsc 55c6812c15a57fb5fb36d43092c08ac3f6534393 266246 python-acora_2.4.orig.tar.gz 1144cc85b9b4b06e84a048b37ecb76cc2005d449 2672 python-acora_2.4-0.1.debian.tar.xz 8ce4f0afd2b5ae2de4753c40f868dc18aeba0e0f 6891 python-acora_2.4-0.1_source.buildinfo Checksums-Sha256: 7d8d2c78454930d1081832d4b7a5a40f9c73488beea2125e0491da2abb65b286 1779 python-acora_2.4-0.1.dsc 15f1526a727a44a9f98ef4f8f1157885ba1f5e53d31d7a2f4c0b56a13c7e843b 266246 python-acora_2.4.orig.tar.gz eb769aa46778ea969ebec1204cdd94314514e2ba1cee882fb91fe5abfa3b28dd 2672 python-acora_2.4-0.1.debian.tar.xz ac657eb69df467e8ad56c60525aa6c6cbe1139c1b99417d395a2231cbc69b757 6891 python-acora_2.4-0.1_source.buildinfo Files: ed617e5e27414d4e086e8c64415efb59 1779 python optional python-acora_2.4-0.1.dsc b4de657fa6e46c30bc091a52140803f9 266246 python optional python-acora_2.4.orig.tar.gz e7a948a64448e596489ed9ac3e40eefe 2672 python optional python-acora_2.4-0.1.debian.tar.xz bb9752f43dca6e5de2fc4a15461a16b7 6891 python optional python-acora_2.4-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmWgOOsQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFO89C/0RmTJ5wLZEA/AoBxf1h/p5AU3DNfxGp/8A hztbFHzptVn0vRp4ZI8nbztZZTmk9Z4qAtwo/u4/kFLbLPNqg+YOU+Sq+4oA/1yt Ej/FU3e/UDHD6a8Pe0YTGoaexOLmzSeoL8szNX0v7pQRxsL6o08qpF3TRyV0nXDT yLICkfE+m9LAStg6x8U4fDyfMP3hGeYL0bhBRuVoXvvY6hZ/wvxtr7yubYww7T87 z4wGdV9bOrm4QTy1mzd523em2C001CXzEI0sN2wseXGDCxd4+5FbXpWkLbYZ/jSK AaGPDQmLpA6WybplwFEpzP+UsGKlZdC8PS8bQFhh7nXiK8meCUE/lsUoFGVesDfu fPYjv8lLmsAkg+ov4kr4cBZQOg0aUpg25b7Sqg+K+VxU6f0pMvTZN3VShsLDdPgJ kxenTOO9zgxWriLSfgeqEiV8IZ0SDeyCiNYWvL7RO6WG4cwZzcPMZC95OvZIWOlV r/BxVsl130gxIKwFR5K1FtnCIGTpomQ= =W+El -END PGP SIGNATURE End Message ---
Processed: Re: python3-ykman: Package uninstallable
Processing control commands: > tags -1 patch upstream fixed-upstream Bug #1060266 [python3-ykman] python3-ykman: Package uninstallable Added tag(s) upstream, patch, and fixed-upstream. -- 1060266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060266: python3-ykman: Package uninstallable
Control: tags -1 patch upstream fixed-upstream Please adapt this upstream commit to fix this issue: https://github.com/Yubico/yubikey-manager/commit/4990bc2bc Thank you, Jeremy Bícha
Processed: awscli: Please drop python-cryptography upper limit or increase it
Processing control commands: > forwarded -1 https://github.com/aws/aws-cli/issues/5943 Bug #1060455 [src:awscli] awscli: Please drop python-cryptography upper limit or increase it Set Bug forwarded-to-address to 'https://github.com/aws/aws-cli/issues/5943'. -- 1060455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060455: awscli: Please drop python-cryptography upper limit or increase it
Source: awscli Version: 2.14.6-1 Severity: serious Control: forwarded -1 https://github.com/aws/aws-cli/issues/5943 awscli is not installable in Debian Unstable because python-cryptography has been updated to a newer version than permitted in awscli's dependencies. I recommend dropping the upper limit. Alternatively you could increase the limit to a higher version. Thank you, Jeremy Bícha
Bug#1055707: python-acora fbfs with Python 3.12
I am sponsoring a NMU that fixes this issue. The changes can be found in git.
Bug#1042663: marked as done (pygtkspellcheck: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Thu, 11 Jan 2024 18:04:48 +
with message-id
and subject line Bug#1042663: fixed in pygtkspellcheck 5.0.3-1
has caused the Debian Bug report #1042663,
regarding pygtkspellcheck: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid
command 'build_sphinx'
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.)
--
1042663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygtkspellcheck
Version: 4.0.5-3
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1
Hi,
pygtkspellcheck fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /<>/setup.py:21: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> import distutils.cmd
> /<>/src/gtkspellcheck/spellcheck.py:59: PyGIWarning: Gtk was
> imported without specifying a version first. Use gi.require_version('Gtk',
> '3.0') before import to ensure that the right version gets loaded.
> from gi.repository import Gtk as gtk
> /usr/lib/python3.11/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'install_requires'
> warnings.warn(msg)
> /usr/lib/python3.11/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'extras_require'
> warnings.warn(msg)
> build_sphinx command is unavailable, please install Sphinx to solve this
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/gtkspellcheck
> copying src/gtkspellcheck/oxt_extract.py ->
> /<>/.pybuild/cpython3_3.11/build/gtkspellcheck
> copying src/gtkspellcheck/spellcheck.py ->
> /<>/.pybuild/cpython3_3.11/build/gtkspellcheck
> copying src/gtkspellcheck/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/gtkspellcheck
> creating /<>/.pybuild/cpython3_3.11/build/pylocales
> copying src/pylocales/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/pylocales
> copying src/pylocales/locales.py ->
> /<>/.pybuild/cpython3_3.11/build/pylocales
> copying src/pylocales/locales.db ->
> /<>/.pybuild/cpython3_3.11/build/pylocales
> python3 setup.py build_sphinx
> /<>/setup.py:21: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> import distutils.cmd
> /<>/src/gtkspellcheck/spellcheck.py:59: PyGIWarning: Gtk was
> imported without specifying a version first. Use gi.require_version('Gtk',
> '3.0') before import to ensure that the right version gets loaded.
> from gi.repository import Gtk as gtk
> /usr/lib/python3.11/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'install_requires'
> warnings.warn(msg)
> /usr/lib/python3.11/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'extras_require'
> warnings.warn(msg)
> build_sphinx command is unavailable, please install Sphinx to solve this
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
>
> error: invalid command 'build_sphinx'
> make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/pygtkspellcheck_4.0.5-3_unstable_sphinx-exp.log
Please see [1] for Sphinx changelog and [2] for Docutils changelog.
Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.
Some notable changes in Sphinx 6 and Sphinx 7:
- Sphinx no longer includes jquery.js and underscore.js by default.
Please use python3-sphinxcontrib.jquery package if you are using a custom
template and it still needs jquery.
- The setup.py build_sphinx command was removed. Please instead call
sphinx-build or "python3 -m sphinx" directly.
- For packages using the extlinks extension, the caption should contain
exactly one "%s" placeholder (if caption is not None).
In case you have questions, please Cc sph...@packages.debian.org on reply.
[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]:
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]:
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis
All bugs filed during this archive rebuild are listed
Bug#1060449: completely wrong version number reported
Package: imapfilter Version: 1:2.8.2-1 Severity: serious The imapfilter package is listed as 2.8.2. However, the version reported is: $ /usr/bin/imapfilter -V IMAPFilter 2.7.1 Copyright (c) 2001-2020 Eleftherios Chatzimparmpas While this is mostly annoying, I've run into the following problem that was fixed in 2.7.4, according to upstream: $ imapfilter imapfilter: /usr/share/imapfilter/regex.lua:10: bad argument #1 to 'compile' (string expected, got nil) stack traceback: [C]: in ? [C]: in field 'compile' /usr/share/imapfilter/regex.lua:10: in metamethod 'index' /usr/share/imapfilter/regex.lua:21: in function 'regex_search' /usr/share/imapfilter/mailbox.lua:986: in function (...tail calls...) /usr/share/imapfilter/set.lua:598: in method 'match_from' /home/foo/.imapfilter/config.lua:20: in function 'foo' /home/foo/.imapfilter/config.lua:76: in main chunk This bug has definitely been fixed in 2.8.2 when rebuilt from upstream source using sid; it works exactly as expected. So, imagine my surprise when I found out the current sid package version has no relationship to version actually shipped -- I have no idea what's actually being provided making this package mostly unusable. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages imapfilter depends on: ii libc6 2.37-13 ii liblua5.4-0 5.4.6-2 ii libpcre2-8-0 10.42-4 ii libssl3 3.1.4-2 imapfilter recommends no packages. imapfilter suggests no packages. -- no debconf information
Processed: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Processing control commands:
> tags -1 help
Bug #1052849 [src:python-pkginfo] python-pkginfo: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) help.
--
1052849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1052849: [Help] Re: python-pkginfo: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Control: tags -1 help Hi, I've fixed the two other bugs in python-pkginfo and upgraded to latest upstream. Unfortunately I have no clue about this issue. Any idea what might be wrong here? Kind regards Andreas. -- http://fam-tille.de
Processed: Re: python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'
Processing control commands: > tags -1 pending Bug #1042599 [src:python-pkginfo] python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' Added tag(s) pending. > block -1 by 1052849 Bug #1042599 [src:python-pkginfo] python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 1042599 was not blocked by any bugs. 1042599 was not blocking any bugs. Added blocking bug(s) of 1042599: 1052849 -- 1042599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042599: python-pkginfo: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'
Control: tags -1 pending Control: block -1 by 1052849 -- http://fam-tille.de
Processed: [bts-link] source package src:numpydoc
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:numpydoc
> # 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 #1056431 (http://bugs.debian.org/1056431)
> # Bug title: numpydoc's autopkg tests fail with Python 3.12
> # * https://github.com/numpy/numpydoc/issues/512
> # * remote status changed: open -> closed
> # * closed upstream
> tags 1056431 + fixed-upstream
Bug #1056431 [src:numpydoc] numpydoc's autopkg tests fail with Python 3.12
Bug #1058407 [src:numpydoc] numpydoc: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 1056431 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1056431 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #1058407 (http://bugs.debian.org/1058407)
> # Bug title: numpydoc: FTBFS: dh_auto_test: error: pybuild --test
> --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
> # * https://github.com/numpy/numpydoc/issues/512
> # * remote status changed: open -> closed
> # * closed upstream
> tags 1058407 + fixed-upstream
Bug #1058407 [src:numpydoc] numpydoc: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Bug #1056431 [src:numpydoc] numpydoc's autopkg tests fail with Python 3.12
Ignoring request to alter tags of bug #1058407 to the same tags previously set
Ignoring request to alter tags of bug #1056431 to the same tags previously set
> usertags 1058407 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1058407 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056431
1058407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057935: ncurses-hexedit: diff for NMU version 0.9.7+orig-7.3
Control: tags 1057935 + pending
--
Dear maintainer,
I've prepared an NMU for ncurses-hexedit (versioned as 0.9.7+orig-7.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru ncurses-hexedit-0.9.7+orig/debian/changelog
ncurses-hexedit-0.9.7+orig/debian/changelog
--- ncurses-hexedit-0.9.7+orig/debian/changelog 2023-02-10 00:03:53.0
+
+++ ncurses-hexedit-0.9.7+orig/debian/changelog 2024-01-05 15:59:12.0
+
@@ -1,3 +1,11 @@
+ncurses-hexedit (0.9.7+orig-7.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * d/p/ncurses_ftbfs.patch:
+Stop using fields of opaque _WINDOW struct (Closes: #1057935)
+
+ -- Mate Kukri Fri, 05 Jan 2024 15:59:12 +
+
ncurses-hexedit (0.9.7+orig-7.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru ncurses-hexedit-0.9.7+orig/debian/patches/fix_ncurses_ftbfs.patch
ncurses-hexedit-0.9.7+orig/debian/patches/fix_ncurses_ftbfs.patch
--- ncurses-hexedit-0.9.7+orig/debian/patches/fix_ncurses_ftbfs.patch
1970-01-01 01:00:00.0 +0100
+++ ncurses-hexedit-0.9.7+orig/debian/patches/fix_ncurses_ftbfs.patch
2024-01-05 15:59:12.0 +
@@ -0,0 +1,175 @@
+Description: Stop using fields of opaque _WINDOW struct
+Author: Mate Kukri
+Last-Update: 2024-01-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/widgets.c
b/src/widgets.c
+@@ -99,11 +99,11 @@
+ case KEY_LEFT:
+ if (i > 0)
+ {
+- if (win->_curx > x)
++ if (getcurx(win) > x)
+/* not at left hand side */
+{
+ i--;
+- wmove (win, y, win->_curx - 1);
++ wmove (win, y, getcurx(win) - 1);
+}
+else if (i > 0)
+/* left hand side */
+@@ -128,11 +128,11 @@
+ }
+ break;
+ case KEY_RIGHT:
+-if (win->_curx < (x + max - 1))
++if (getcurx(win) < (x + max - 1))
+ /* not at right hand side */
+ {
+i++;
+- wmove (win, y, win->_curx + 1);
++ wmove (win, y, getcurx(win) + 1);
+ }
+ else if (i < len - 1)
+ /* right hand side */
+@@ -163,7 +163,7 @@
+ #endif
+ if (i > 0)
+ {
+- if (win->_curx > x)
++ if (getcurx(win) > x)
+/* not at left hand side */
+{
+ i--;
+@@ -172,7 +172,7 @@
+ for (n = i; n < len; n++)
+ *(str + n) = *(str + n + 1);
+ *(str + n) = 0;
+- oldx = win->_curx;
++ oldx = getcurx(win);
+ wmove (win, y, x);
+ for (n = left; n <= right; n++)
+ {
+@@ -209,8 +209,8 @@
+do_beep ();
+ break;
+ case SPACEBAR:
+-oldx = win->_curx;
+-if ((win->_curx < x + max - 1)
++oldx = getcurx(win);
++if ((getcurx(win) < x + max - 1)
+ && (i < len - 1) && (*(str + len - 1) <= ' '))
+ {
+for (n = len - 1; n > i; n--)
+@@ -230,7 +230,7 @@
+}
+wmove (win, y, oldx + 1);
+ }
+-else if ((win->_curx == x + max - 1)
++else if ((getcurx(win) == x + max - 1)
+ && (i < len - 1) && (*(str + len - 1) <= ' '))
+ {
+for (n = len - 1; n > i; n--)
+@@ -255,7 +255,7 @@
+}
+wmove (win, y, x + max - 1);
+ }
+-else if ((win->_curx == x + max - 1)
++else if ((getcurx(win) == x + max - 1)
+ && (i == len - 1))
+ {
+*(str + len - 1) = ' ';
+@@ -285,12 +285,12 @@
+ default: /* normal input */
+ if (isprintable (in))
+ {
+- if (win->_curx != (x + max - 1))
++ if (getcurx(win) != (x + max - 1))
+/* not at right hand side */
+{
+ *(str + i) = in;
+ i++;
+- oldx = win->_curx;
++ oldx = getcurx(win);
+ wmove (win, y, x);
+ for (n = left; n <= right; n++)
+ {
+--- a/src/file.c
b/src/file.c
+@@ -644,7 +644,7 @@
+ wprintw (Globals.wmain, "%s", trunc_file);
+ fp = fp->p;
+
+- for (result = Globals.wmain->_curx; result < COLS; result++)
++ for (result = getcurx(Globals.wmain); result < COLS; result++)
+ wprintw (Globals.wmain, " ");
+}
+
+--- a/src/misc.c
b/src/misc.c
+@@ -641,10 +641,8 @@
+if (!newlines)
+ die_horribly (NOT_ENOUGH_MEMORY, NULL);
+
+- Globals.wmain->_cury = cursor_y - 1;
+- Globals.wmain->_curx =
Processed: ncurses-hexedit: diff for NMU version 0.9.7+orig-7.3
Processing control commands:
> tags 1057935 + pending
Bug #1057935 [src:ncurses-hexedit] ncurses-hexedit: FTBFS: invalid use of
incomplete typedef ‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) pending.
--
1057935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058296: marked as done (ostree-push: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Thu, 11 Jan 2024 17:05:03 +
with message-id
and subject line Bug#1058296: fixed in ostree-push 1.0.1-4
has caused the Debian Bug report #1058296,
regarding ostree-push: 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.)
--
1058296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ostree-push
Version: 1.0.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> http_proxy= dh_auto_test
> I: pybuild base:310: cd
> /<>/.pybuild/cpython3_3.12_ostree-push/build; python3.12 -m
> pytest tests
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 --
> /usr/bin/python3.12
> cachedir: .pytest_cache
> rootdir: /<>
> configfile: pytest.ini
> collecting ... collected 87 items
>
> tests/test_full.py::test_no_commits PASSED [
> 1%]
> tests/test_full.py::test_basic PASSED[
> 2%]
> tests/test_full.py::test_dry_run PASSED [
> 3%]
> tests/test_full.py::test_scp_dest PASSED [
> 4%]
> tests/test_full.py::test_command_abspath PASSED [
> 5%]
> tests/test_push.py::TestRepoServer::test_missing PASSED [
> 6%]
> tests/test_push.py::TestRepoServer::test_non_context PASSED [
> 8%]
> tests/test_push.py::TestRepoServer::test_context PASSED [
> 9%]
> tests/test_push.py::TestRepoServer::test_pull PASSED [
> 10%]
> tests/test_push.py::TestSSHMultiplexer::test_socket_exists PASSED[
> 11%]
> tests/test_push.py::TestSSHMultiplexer::test_master_non_context PASSED [
> 12%]
> tests/test_push.py::TestSSHMultiplexer::test_master_context PASSED [
> 13%]
> tests/test_push.py::TestSSHMultiplexer::test_forward_port PASSED [
> 14%]
> tests/test_push.py::TestSSHMultiplexer::test_run PASSED [
> 16%]
> tests/test_push.py::TestPushRefs::test_no_refs PASSED[
> 17%]
> tests/test_push.py::TestPushRefs::test_refs PASSED [
> 18%]
> tests/test_push.py::TestPushRefs::test_missing_ref PASSED[
> 19%]
> tests/test_push.py::TestPushRefs::test_summary PASSED[
> 20%]
> tests/test_push.py::TestPushRefs::test_dry_run PASSED[
> 21%]
> tests/test_push.py::TestParseDest::test_bad_scheme PASSED[
> 22%]
> tests/test_push.py::TestParseDest::test_missing_repo PASSED [
> 24%]
> tests/test_push.py::TestParseDest::test_empty_dest PASSED[
> 25%]
> tests/test_push.py::TestParseDest::test_missing_host PASSED [
> 26%]
> tests/test_push.py::TestParseDest::test_invalid_host PASSED [
> 27%]
> tests/test_push.py::TestParseDest::test_invalid_port PASSED [
> 28%]
> tests/test_push.py::TestParseDest::test_good_dest PASSED [
> 29%]
> tests/test_push.py::TestArgParser::test_no_dest PASSED [
> 31%]
> tests/test_push.py::TestArgParser::test_defaults PASSED [
> 32%]
> tests/test_push.py::TestArgParser::test_dest PASSED [
> 33%]
> tests/test_push.py::TestArgParser::test_refs PASSED [
> 34%]
> tests/test_push.py::TestArgParser::test_port PASSED [
> 35%]
> tests/test_push.py::TestArgParser::test_port_and_dest_port PASSED[
> 36%]
> tests/test_push.py::TestArgParser::test_dry_run PASSED [
> 37%]
> tests/test_push.py::TestArgParser::test_log_level PASSED [
> 39%]
> tests/test_push.py::TestArgParser::test_repo PASSED [
> 40%]
> tests/test_push.py::TestArgParser::test_command PASSED [
> 41%]
> tests/test_push.py::TestArgParser::test_ssh_options PASSED [
> 42%]
> tests/test_receive.py::TestReceiveRepo::test_cleanup PASSED [
> 43%]
> tests/test_receive.py::TestReceiveRepo::test_get_commit_timestamp PASSED [
> 44%]
> tests/test_receive.py::TestReceiveRepo::test_is_flatpak_repo
Bug#1060377: marked as done (nut-modbus has an undeclared file conflict on /lib/nut/apc_modbus)
Your message dated Thu, 11 Jan 2024 16:50:08 + with message-id and subject line Bug#1060377: fixed in nut 2.8.1-3 has caused the Debian Bug report #1060377, regarding nut-modbus has an undeclared file conflict on /lib/nut/apc_modbus 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.) -- 1060377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nut-modbus Version: 2.8.1-2 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + nut-server nut-modbus has an undeclared file conflict. This may result in an unpack error from dpkg. The file /lib/nut/apc_modbus is contained in the packages * nut-modbus/2.8.1-2 as present in unstable * nut-server/2.8.1-1 as present in trixie 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: nut Source-Version: 2.8.1-3 Done: Laurent Bigonville We believe that the bug you reported is fixed in the latest version of nut, 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. Laurent Bigonville (supplier of updated nut package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jan 2024 17:01:16 +0100 Source: nut Architecture: source Version: 2.8.1-3 Distribution: unstable Urgency: medium Maintainer: Laurent Bigonville Changed-By: Laurent Bigonville Closes: 1060377 Changes: nut (2.8.1-3) unstable; urgency=medium . * debian/control: Add missing Breaks/Replaces on nut-modbus (Closes: #1060377) Checksums-Sha1: 8473d3b4bfe441e94f322310728b9b087489cfbb 3134 nut_2.8.1-3.dsc 6f669cd3dc4d99b6dd109b61f546fa22adaca665 73288 nut_2.8.1-3.debian.tar.xz a14aeabb4bd343eaaa794d1608fb435ffcd6d4c4 6752 nut_2.8.1-3_source.buildinfo Checksums-Sha256: afb8e4655bf40e3325005910a749a845563e6eb2cf3f25be75cb49bbc6435123 3134 nut_2.8.1-3.dsc 0314feea713029cabf1550789d4ffe600138dfc0d8c247fd767a27d768d37e1a 73288 nut_2.8.1-3.debian.tar.xz 746c414c2842087ed7b463dee6e4d46b6218ca2c320e0dcc7cdfa791e786c181 6752 nut_2.8.1-3_source.buildinfo Files: 1ad37e37909fe389ae17e7228cde267d 3134 admin optional nut_2.8.1-3.dsc 37539d0435d9f203529fcfe3a9a9337d 73288 admin optional nut_2.8.1-3.debian.tar.xz 3c8aab30b71d120468fc743adcccbcde 6752 admin optional nut_2.8.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAmWgFz4RHGJpZ29uQGRl Ymlhbi5vcmcACgkQH8WJHrqwQ9UtnAf/Z3GT9R/5McMrN6Hkjwhe0sBK0l2HdXma JMxejnU+1mHdlpA22ZI2E/gEPtxpwqh6QSdpH76KWsnn8flhiAlf/QKssPdqvVT+ XwzZrSuucqZoNf60WUIuRi1IcJaJKCZ1QZ/o7f1dnA2TYrnkoL387QBubRA7lwzd DXU19IgbvXC0YwrwoZwOnCsLLhadDFQ3eKZfzwZYb93Ayg8XVxZPgsle46Kl2Zkp NMk6cKKw7d9prkDQRvMDNPfGRGqXK1aza1GgREf8pLyGEbD7sjG7xI9DnGf5Frrs ht+j9+V8ZP+EjmotCMrcMvHKvp4GUYu3G9WQfri+K8GYQcNfkeDIqg== =+1ji -END PGP SIGNATURE End Message ---
Bug#1058296: marked as done (ostree-push: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Thu, 11 Jan 2024 16:50:16 +
with message-id
and subject line Bug#1058296: fixed in ostree-push 1.0.1-3
has caused the Debian Bug report #1058296,
regarding ostree-push: 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.)
--
1058296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ostree-push
Version: 1.0.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> http_proxy= dh_auto_test
> I: pybuild base:310: cd
> /<>/.pybuild/cpython3_3.12_ostree-push/build; python3.12 -m
> pytest tests
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 --
> /usr/bin/python3.12
> cachedir: .pytest_cache
> rootdir: /<>
> configfile: pytest.ini
> collecting ... collected 87 items
>
> tests/test_full.py::test_no_commits PASSED [
> 1%]
> tests/test_full.py::test_basic PASSED[
> 2%]
> tests/test_full.py::test_dry_run PASSED [
> 3%]
> tests/test_full.py::test_scp_dest PASSED [
> 4%]
> tests/test_full.py::test_command_abspath PASSED [
> 5%]
> tests/test_push.py::TestRepoServer::test_missing PASSED [
> 6%]
> tests/test_push.py::TestRepoServer::test_non_context PASSED [
> 8%]
> tests/test_push.py::TestRepoServer::test_context PASSED [
> 9%]
> tests/test_push.py::TestRepoServer::test_pull PASSED [
> 10%]
> tests/test_push.py::TestSSHMultiplexer::test_socket_exists PASSED[
> 11%]
> tests/test_push.py::TestSSHMultiplexer::test_master_non_context PASSED [
> 12%]
> tests/test_push.py::TestSSHMultiplexer::test_master_context PASSED [
> 13%]
> tests/test_push.py::TestSSHMultiplexer::test_forward_port PASSED [
> 14%]
> tests/test_push.py::TestSSHMultiplexer::test_run PASSED [
> 16%]
> tests/test_push.py::TestPushRefs::test_no_refs PASSED[
> 17%]
> tests/test_push.py::TestPushRefs::test_refs PASSED [
> 18%]
> tests/test_push.py::TestPushRefs::test_missing_ref PASSED[
> 19%]
> tests/test_push.py::TestPushRefs::test_summary PASSED[
> 20%]
> tests/test_push.py::TestPushRefs::test_dry_run PASSED[
> 21%]
> tests/test_push.py::TestParseDest::test_bad_scheme PASSED[
> 22%]
> tests/test_push.py::TestParseDest::test_missing_repo PASSED [
> 24%]
> tests/test_push.py::TestParseDest::test_empty_dest PASSED[
> 25%]
> tests/test_push.py::TestParseDest::test_missing_host PASSED [
> 26%]
> tests/test_push.py::TestParseDest::test_invalid_host PASSED [
> 27%]
> tests/test_push.py::TestParseDest::test_invalid_port PASSED [
> 28%]
> tests/test_push.py::TestParseDest::test_good_dest PASSED [
> 29%]
> tests/test_push.py::TestArgParser::test_no_dest PASSED [
> 31%]
> tests/test_push.py::TestArgParser::test_defaults PASSED [
> 32%]
> tests/test_push.py::TestArgParser::test_dest PASSED [
> 33%]
> tests/test_push.py::TestArgParser::test_refs PASSED [
> 34%]
> tests/test_push.py::TestArgParser::test_port PASSED [
> 35%]
> tests/test_push.py::TestArgParser::test_port_and_dest_port PASSED[
> 36%]
> tests/test_push.py::TestArgParser::test_dry_run PASSED [
> 37%]
> tests/test_push.py::TestArgParser::test_log_level PASSED [
> 39%]
> tests/test_push.py::TestArgParser::test_repo PASSED [
> 40%]
> tests/test_push.py::TestArgParser::test_command PASSED [
> 41%]
> tests/test_push.py::TestArgParser::test_ssh_options PASSED [
> 42%]
> tests/test_receive.py::TestReceiveRepo::test_cleanup PASSED [
> 43%]
> tests/test_receive.py::TestReceiveRepo::test_get_commit_timestamp PASSED [
> 44%]
> tests/test_receive.py::TestReceiveRepo::test_is_flatpak_repo
Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf
On Thu, Jan 11, 2024 at 03:53:17PM +0100, Emanuele Rocca wrote: > Hi Julian, > > On 2024-01-08 10:28, Julian Andres Klode wrote: > > (in Ubuntu we have partially recovered by disabling stack clash > > protection but it crashes on invalid writes there, I suppose we need > > to rebuild some more apt dependencies without the flag...). > > The 'invalid writes' issue seems unrelated to armhf and > stack-clash-protection, > I can reproduce it on my x86 workstation. It would be interesting to see if > once these problems are fixed valgrind on armhf still segfaults. > > (sid-amd64)root@ariel:~# valgrind apt-get update > ==194196== Memcheck, a memory error detector > ==194196== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. > ==194196== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info > ==194196== Command: apt-get update > ==194196== > Hit:1 http://127.0.0.1:3142/debian sid InRelease > ==194196== Conditional jump or move depends on uninitialised value(s) > ==194196==at 0x4A89B3B: pkgCache::ReMap(bool const&) (in > /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0) > [... more errors follow] The uninitialized values in ReMap are actually normal and correct behavior, not errors. It happens because we need to grow the array/map without having written all bytes of it first. The same applies to uninitalized bytes passed to write from pkgCacheFile::BuildCaches(), it's writing the partially initialized memory pool to the file. And there aren't any hard errors. We could zero initialize those or add supressions to make things look nicer I suppose. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1057930: cunit: diff for NMU version 2.1-3-dfsg-2.7
Control: tags 1057930 + pending
--
Dear maintainer,
I've prepared an NMU for cunit (versioned as 2.1-3-dfsg-2.7) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru cunit-2.1-3-dfsg/debian/changelog cunit-2.1-3-dfsg/debian/changelog
--- cunit-2.1-3-dfsg/debian/changelog 2023-04-01 07:01:17.0 +0100
+++ cunit-2.1-3-dfsg/debian/changelog 2024-01-11 16:36:37.0 +
@@ -1,3 +1,17 @@
+cunit (2.1-3-dfsg-2.7) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Mate Kukri ]
+ * d/p/curses_ftbfs.patch:
+Fix FTBFS caused by incorrect use of WINDOW. (Closes: #1057930)
+
+ [ Sudip Mukherjee ]
+ * Fixed the patch from Mate Kukri.
+- Thanks to Sven Joachim for pointing out getmaxx and getmaxy.
+
+ -- Sudip Mukherjee Thu, 11 Jan 2024 16:36:37
+
+
cunit (2.1-3-dfsg-2.6) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru cunit-2.1-3-dfsg/debian/patches/curses_ftbfs.patch
cunit-2.1-3-dfsg/debian/patches/curses_ftbfs.patch
--- cunit-2.1-3-dfsg/debian/patches/curses_ftbfs.patch 1970-01-01
01:00:00.0 +0100
+++ cunit-2.1-3-dfsg/debian/patches/curses_ftbfs.patch 2024-01-11
16:36:37.0 +
@@ -0,0 +1,52 @@
+Description: Use getters for accessing fields of opaque type WINDOW in Curses.c
+Author: Mate Kukri
+Last-Update: 2024-01-04
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/CUnit/Sources/Curses/Curses.c
b/CUnit/Sources/Curses/Curses.c
+@@ -256,10 +256,10 @@
+
+ start_color();
+
+- f_nLeft = application_windows.pMainWin->_begx;
+- f_nTop = application_windows.pMainWin->_begy;
+- f_nWidth = application_windows.pMainWin->_maxx;
+- f_nHeight = application_windows.pMainWin->_maxy;
++ f_nLeft = getbegx(application_windows.pMainWin);
++ f_nTop = getbegy(application_windows.pMainWin);
++ f_nWidth = getmaxx(application_windows.pMainWin) - 1;
++ f_nHeight = getmaxy(application_windows.pMainWin) - 1;
+
+ if (NULL == (application_windows.pTitleWin = newwin(3, f_nWidth, 0, 0))) {
+ goto title_fail;
+@@ -358,10 +358,10 @@
+ {
+ refresh();
+
+- f_nLeft = application_windows.pMainWin->_begx;
+- f_nTop = application_windows.pMainWin->_begy;
+- f_nWidth = application_windows.pMainWin->_maxx;
+- f_nHeight = application_windows.pMainWin->_maxy;
++ f_nLeft = getbegx(application_windows.pMainWin);
++ f_nTop = getbegy(application_windows.pMainWin);
++ f_nWidth = getmaxx(application_windows.pMainWin) - 1;
++ f_nHeight = getmaxy(application_windows.pMainWin) - 1;
+
+ refresh_title_window();
+ refresh_progress_window();
+@@ -907,10 +907,10 @@
+ pPad->uiColumns = uiCols;
+ pPad->uiPadRow = 0;
+ pPad->uiPadCol = 0;
+- pPad->uiWinLeft = application_windows.pDetailsWin->_begx + 1;
+- pPad->uiWinTop = application_windows.pDetailsWin->_begy + 1;
+- pPad->uiWinColumns = application_windows.pDetailsWin->_maxx - 2;
+- pPad->uiWinRows = application_windows.pDetailsWin->_maxy - 2;
++ pPad->uiWinLeft = getbegx(application_windows.pDetailsWin) + 1;
++ pPad->uiWinTop = getbegy(application_windows.pDetailsWin) + 1;
++ pPad->uiWinColumns = getmaxx(application_windows.pDetailsWin) - 3;
++ pPad->uiWinRows = getmaxy(application_windows.pDetailsWin) - 3;
+
+ bStatus = true;
+
diff -Nru cunit-2.1-3-dfsg/debian/patches/series
cunit-2.1-3-dfsg/debian/patches/series
--- cunit-2.1-3-dfsg/debian/patches/series 2023-03-31 14:53:05.0
+0100
+++ cunit-2.1-3-dfsg/debian/patches/series 2024-01-11 16:03:54.0
+
@@ -1,3 +1,4 @@
0003-fix-warnings-in-man.patch
0004-doc-intorduction-fix-links-to-headers-4K-in-size.patch
fix-string-format-errors-with-recent-ncu.patch
+curses_ftbfs.patch
Processed: cunit: diff for NMU version 2.1-3-dfsg-2.7
Processing control commands:
> tags 1057930 + pending
Bug #1057930 [src:cunit] cunit: FTBFS: invalid use of incomplete typedef
‘WINDOW’ {aka ‘struct _win_st’}
Added tag(s) pending.
--
1057930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060072: marked as done (RM: fheroes2-pkg -- RoQA; Replaced by DFSG-free fheroes2)
Your message dated Thu, 11 Jan 2024 17:11:58 +0100 with message-id and subject line duplicate RM request has caused the Debian Bug report #1060072, regarding RM: fheroes2-pkg -- RoQA; Replaced by DFSG-free fheroes2 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.) -- 1060072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fheroes-pkg Severity: serious Please file a removal bug for fheroes2-pkg. The fheroes2 package has just entered Debian main and should be considered the successor of this package. If nobody acts or comments on this suggestion, I am going to file a RM bug as soon as fheroes2-pkg is autoremoved from testing. --- End Message --- --- Begin Message --- done--- End Message ---
Bug#1058329: ipxe: FTBFS: arch/x86/core/patch_cf.S:26: Error: 64bit mode not supported on `i386'.
I was able to `make bin-x86_64-efi/ipxe.efi` by commenting out ".arch i386" (and sometimes i486 or i586) lines in various .S files under arch/x86/ The result netbooted fine and did the job. I assume something changed in the compiler or assembler at some point, so this is only a pointer in that direction, not a real fix. ..ciaran
Bug#1060440: marked as done (llvm-toolchain-17: 1:17.0.6-4 FTBFS on i386, armel)
Your message dated Thu, 11 Jan 2024 16:03:43 + with message-id and subject line Bug#1060440: fixed in llvm-toolchain-17 1:17.0.6-5 has caused the Debian Bug report #1060440, regarding llvm-toolchain-17: 1:17.0.6-4 FTBFS on i386, armel 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.) -- 1060440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-17 Version: 1:17.0.6-4 Severity: serious Tags: ftbfs pending Justification: fails to build from source (but built successfully in the past) Forwarded: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/130 llvm-toolchain-17_1:17.0.6-4 has a FTBFS issue on i386: https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-17=i386=1%3A17.0.6-4=1704824852=0 > dh_install: warning: Cannot find (any matches for) > "usr/lib/llvm-17/lib/clang/17/bin/hwasan_symbolize" (tried in ., debian/tmp) ... > dh_install: warning: Cannot find (any matches for) > "usr/lib/llvm-17/lib/clang/17*/lib/linux/liborc_rt*" (tried in ., debian/tmp) and an unrelated FTBFS on armel: https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-17=armel=1%3A17.0.6-4=1704818089=0 > In file included from > /<>/compiler-rt/lib/builtins/arm/sync_fetch_and_and_4.S:14: > /<>/compiler-rt/lib/builtins/arm/sync-ops.h:22:2: error: DMB is > only supported on ARMv6+ >22 | #error DMB is only supported on ARMv6+ It looks as though these are already known and already fixed in the packaging git repo. Thanks, smcv --- End Message --- --- Begin Message --- Source: llvm-toolchain-17 Source-Version: 1:17.0.6-5 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of llvm-toolchain-17, 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. Sylvestre Ledru (supplier of updated llvm-toolchain-17 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jan 2024 14:15:09 +0100 Source: llvm-toolchain-17 Architecture: source Version: 1:17.0.6-5 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 1060440 Changes: llvm-toolchain-17 (1:17.0.6-5) unstable; urgency=medium . [ Faidon Liambotis ] * Revert "Enable COMPILER_RT_BUILD_BUILTINS for armel" * Fix i386 FTBFS resulting from COMPILER_RT_DEFAULT_TARGET_ONLY (Closes: #1060440) Checksums-Sha1: 8ff20dee30ac231e44461f1c56e75618fdbb7044 8059 llvm-toolchain-17_17.0.6-5.dsc 7372e219121886e95bf681fa09e073bbc0734172 163240 llvm-toolchain-17_17.0.6-5.debian.tar.xz b348989612b3fa2d0c46af7b768b974142f3f6c8 36089 llvm-toolchain-17_17.0.6-5_amd64.buildinfo Checksums-Sha256: b6f57e9c216a5c796d97fcce71c018023350af866b9a7a0f3aa578218510d316 8059 llvm-toolchain-17_17.0.6-5.dsc c3f45187af27ad5eb84477a44473dee4852a1266e67959f9e3346d7d3edf6c42 163240 llvm-toolchain-17_17.0.6-5.debian.tar.xz 4b13499b3846827026081b75ee9acd2e243b48a79666ce6d2d55f2e39fb781c4 36089 llvm-toolchain-17_17.0.6-5_amd64.buildinfo Files: 4ace7c0cc926218757b1c0e2bb08e1e0 8059 devel optional llvm-toolchain-17_17.0.6-5.dsc 6a38fbfe7ae7b7b070f06b260f41eab3 163240 devel optional llvm-toolchain-17_17.0.6-5.debian.tar.xz 6899f75ea89a8ceeb7d99fc5bf8c20e4 36089 devel optional llvm-toolchain-17_17.0.6-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmWgCtIACgkQfmUo2nUv G+HRBA//Q2ygpJApIVnPf0sqSTDc3luAk4NFZGNG39YthEXSZTeCm1/EijqhuNxV sGYJ6znkk083bC1tvdsV4ZbZJ0y4ucC0mOSeSUgpHUm7XLbeOjomPaG7sdTWAi/2 I9+cw8r1jWDO1aX96dBA2N4yYkwFGZYuKGSelw2rhQRFUN1Nq73Va3DGZ+D30Jj0 Ub+tXqrYSlaaYbKeSpj+TyTD5uCnTY/Fww78zi7jbQLpGUDKxK/HI2d3a2bSOmQU 0MGQ6afy48XuCxQyDrVujaMwL9uMv4yeHeVthdw1T/T5xnnF3h5YSOi4jXsrH6m5 t3QwLHDJZCdSQHvnJeJtbGAVsx7wpwxSgsIqKXDhAnWcnLzEPwS/MyHYVMc8tJcG ZfaQGluXak7j4UMJaCj4Hbmhw94jfjocRm6w+QI82UzOUWUzwdNfRow6g3qaU9bc tVwGnd/5uHjyHF96ZG0YF7Lt87ezygK9MMJep5OCiDs7LB2X9Tjbm2tSpFdRbK/f d6KKEkSFxV3DaN/XmwvGIdQjwkQbG0BEFE456tZFXyrr6metlnFt4yay788KZam3
Bug#1058099: pyro4: FTBFS: AttributeError: 'CoreTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? debdiff for NMU
Hi Thomas, On Thu, Jan 11, 2024 at 4:57 PM Thomas Goirand wrote: > Please see attached diff to fix the issue. It's kind of trivial to fix, > as you may see... Could you please upload it to unstable ASAP, or allow > me to NMU this fix? I'll upload it ASAP. But what's your intention with keeping pyro4 in the archives? It is no longer developed and superseded with pyro5. Should be removed sooner than later. Regards, Laszlo/GCS
Bug#1060440: llvm-toolchain-17: 1:17.0.6-4 FTBFS on i386, armel
On Thu, Jan 11, 2024 at 01:02:47PM +, Simon McVittie wrote: > It looks as though these are already known and already fixed in the > packaging git repo. Correct. I introduced these breakages with a couple of recent MRs, and hopefully fixed them with #130. I asked Sylvestre to hold off until we have build logs from all (official) architectures, so that's why these aren't fixed in unstable yet. (mips64el and risv64 are still building, although mips64el has never built LLVM 17, and my changes are not expected to fix that.) Faidon
Bug#1058099: pyro4: FTBFS: AttributeError: 'CoreTests' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? debdiff for NMU
Hi Laszlo,
Please see attached diff to fix the issue. It's kind of trivial to fix,
as you may see... Could you please upload it to unstable ASAP, or allow
me to NMU this fix?
Cheers,
Thomas Goirand (zigo)diff -Nru pyro4-4.82/debian/changelog pyro4-4.82/debian/changelog
--- pyro4-4.82/debian/changelog 2023-11-06 17:31:51.0 +0100
+++ pyro4-4.82/debian/changelog 2024-01-11 16:43:48.0 +0100
@@ -1,3 +1,11 @@
+pyro4 (4.82-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS by adding a patch:
+- use-self.assertEqual-not-self.assertEquals.patch (Closes: #1058099).
+
+ -- Thomas Goirand Thu, 11 Jan 2024 16:43:48 +0100
+
pyro4 (4.82-3) unstable; urgency=medium
* Fix FTBFS with Sphinx 7.1 (closes: #1042648).
diff -Nru pyro4-4.82/debian/patches/series pyro4-4.82/debian/patches/series
--- pyro4-4.82/debian/patches/series2023-01-02 21:48:48.0 +0100
+++ pyro4-4.82/debian/patches/series2024-01-11 16:36:09.0 +0100
@@ -1,2 +1,3 @@
skip_networked_tests.patch
fix-ftbfs-python3.11.patch
+use-self.assertEqual-not-self.assertEquals.patch
diff -Nru
pyro4-4.82/debian/patches/use-self.assertEqual-not-self.assertEquals.patch
pyro4-4.82/debian/patches/use-self.assertEqual-not-self.assertEquals.patch
--- pyro4-4.82/debian/patches/use-self.assertEqual-not-self.assertEquals.patch
1970-01-01 01:00:00.0 +0100
+++ pyro4-4.82/debian/patches/use-self.assertEqual-not-self.assertEquals.patch
2024-01-11 16:39:05.0 +0100
@@ -0,0 +1,17 @@
+Description: Use self.assertEqual not self.assertEquals
+Author: Thomas Goirand
+Bug-Debian: https://bugs.debian.org/1058099
+Forwarded: no
+Last-Update: 2024-01-11
+
+--- pyro4-4.82.orig/tests/PyroTests/test_core.py
pyro4-4.82/tests/PyroTests/test_core.py
+@@ -359,7 +359,7 @@ class CoreTests(unittest.TestCase):
+ with self.assertRaises(Pyro4.errors.PyroError):
+ Pyro4.Proxy("test")
+ with Pyro4.Proxy("test", connected_socket=s1) as p:
+-self.assertEquals("<>:0",
p._pyroUri.location)
++self.assertEqual("<>:0",
p._pyroUri.location)
+ self.assertIsNotNone(p._pyroConnection)
+ p._pyroRelease()
+ self.assertIsNotNone(p._pyroConnection)
Bug#1060251: Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf
Hi Julian, On 2024-01-08 10:28, Julian Andres Klode wrote: > (in Ubuntu we have partially recovered by disabling stack clash > protection but it crashes on invalid writes there, I suppose we need > to rebuild some more apt dependencies without the flag...). The 'invalid writes' issue seems unrelated to armhf and stack-clash-protection, I can reproduce it on my x86 workstation. It would be interesting to see if once these problems are fixed valgrind on armhf still segfaults. (sid-amd64)root@ariel:~# valgrind apt-get update ==194196== Memcheck, a memory error detector ==194196== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==194196== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info ==194196== Command: apt-get update ==194196== Hit:1 http://127.0.0.1:3142/debian sid InRelease ==194196== Conditional jump or move depends on uninitialised value(s) ==194196==at 0x4A89B3B: pkgCache::ReMap(bool const&) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0) [... more errors follow]
Bug#1042700: marked as done (python-padme: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Thu, 11 Jan 2024 14:37:13 + with message-id and subject line Bug#1042700: fixed in python-padme 1.1.1-5 has caused the Debian Bug report #1042700, regarding python-padme: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 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.) -- 1042700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-padme Version: 1.1.1-4 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, python-padme fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build --buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_padme/build/padme > copying padme/tests.py -> > /<>/.pybuild/cpython3_3.11_padme/build/padme > copying padme/__init__.py -> > /<>/.pybuild/cpython3_3.11_padme/build/padme > running egg_info > writing padme.egg-info/PKG-INFO > writing dependency_links to padme.egg-info/dependency_links.txt > writing top-level names to padme.egg-info/top_level.txt > reading manifest file 'padme.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > adding license file 'COPYING' > adding license file 'COPYING.LESSER' > adding license file 'AUTHORS.rst' > writing manifest file 'padme.egg-info/SOURCES.txt' > python3 setup.py build_sphinx -b html > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: invalid command 'build_sphinx' > make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/python-padme_1.1.1-4_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects --- End Message --- --- Begin Message --- Source: python-padme Source-Version: 1.1.1-5 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of python-padme, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-padme package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jan 2024 14:46:02 +0100 Source: python-padme Architecture: source Version: 1.1.1-5 Distribution:
Bug#1053328: marked as done (pycryptodome: Baseline violation on i386 and test FTBFS on !x86)
Your message dated Thu, 11 Jan 2024 13:51:37 + with message-id and subject line Bug#1053328: fixed in pycryptodome 3.20.0+dfsg-1 has caused the Debian Bug report #1053328, regarding pycryptodome: Baseline violation on i386 and test FTBFS on !x86 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.) -- 1053328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pycryptodome Version: 3.18.0+dfsg1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=pycryptodome=3.18.0%2Bdfsg1-1 ... [ 1%] Building C object CMakeFiles/mont.dir/<>/src/mont.c.o cc: error: unrecognized command-line option ‘-mssse3’ cc: error: unrecognized command-line option ‘-mpclmul’ cc: error: unrecognized command-line option ‘-maes’ make[4]: *** [CMakeFiles/mont.dir/build.make:76: CMakeFiles/mont.dir/<>/src/mont.c.o] Error 1 - SSE is not part of the i386 baseline - trying to run the tests with "-mssse3 -mpclmul" FTBFS on !x86 (m68k and sh4 are building with nocheck) --- End Message --- --- Begin Message --- Source: pycryptodome Source-Version: 3.20.0+dfsg-1 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of pycryptodome, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated pycryptodome 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: Thu, 11 Jan 2024 14:32:40 +0100 Source: pycryptodome Built-For-Profiles: noudeb Architecture: source Version: 3.20.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Benjamin Drung Closes: 1053328 1056436 Launchpad-Bugs-Fixed: 2039968 Changes: pycryptodome (3.20.0+dfsg-1) unstable; urgency=medium . * Team upload. * New upstream release (Closes: #1056436) - C unit tests also run on non-x86 architectures (Closes: #1053328, LP: #2039968) * Drop patches applied upstream Checksums-Sha1: 3eba073ee489312b43331aa11c828d3df485c6a2 2300 pycryptodome_3.20.0+dfsg-1.dsc 8bcd1126199147257eb88a546f73de01a122268f 10883808 pycryptodome_3.20.0+dfsg.orig.tar.xz a025f3469de9964e34b8f7c1f0773652b585f7eb 11544 pycryptodome_3.20.0+dfsg-1.debian.tar.xz 118dccaa238c380dfc22ee0d464aa52f38fca585 9615 pycryptodome_3.20.0+dfsg-1_source.buildinfo Checksums-Sha256: 53369a241b4c64aa4d95c43e00792be22d1959a90d0dc074eddd3df78a4d74e4 2300 pycryptodome_3.20.0+dfsg-1.dsc f7d907ec53696f7559fb9a1b19d61f55f7aff053f3196be5bf8dff83bc049a16 10883808 pycryptodome_3.20.0+dfsg.orig.tar.xz bb120cbecaff71d5c0a465be74e40e1d1498ec751806b73d734feedda7d09404 11544 pycryptodome_3.20.0+dfsg-1.debian.tar.xz f293dd6724d1213d6e5578db3740119928473a377c9f4c56f41c990cc2a53e60 9615 pycryptodome_3.20.0+dfsg-1_source.buildinfo Files: d344d93b19f25c0437964f8a4373e029 2300 python optional pycryptodome_3.20.0+dfsg-1.dsc f10ab092b8ee362d9ee1e9aa3a2221d3 10883808 python optional pycryptodome_3.20.0+dfsg.orig.tar.xz 34e82e85459f99f549f988ec8745d468 11544 python optional pycryptodome_3.20.0+dfsg-1.debian.tar.xz 24f36de5f15a7ba786a69e1e217008d2 9615 python optional pycryptodome_3.20.0+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmWf734ACgkQFZ61xO/I d0y20RAAkSnH9qXaIMM29oGiRYiegVuDQxiptq5fRlb8ufagC4Lo214Smq299xZ0 gIzu0KdI6NAxRPyGbLPf78U3XSiEzWyye3lkoh/zKJmdHDWOpgOygzjTNa0SRG3D pS9yScjb4PqDhL5ofaLgyVHlZITNb2C4i2TvMzKpBMiIrDObCDuJWRSTIWLxKOAC K0jl8WNoQLXQKyNdb1O5wnlcjDthsqJvrS5o6Rb84GYsx9c8MPse7JGiebsV1FWp dQ+Mje9YTsNoMkn1DLdryCpmazIHUUBeGNXkgjXiZe/sQRLFfHdTPnHELFczqmgQ Ippmj3dSPgjky4Se+FDB2KMAhO1yB75MfjL+D/FuGfupFCeaiNY5OTwegX5ggp99 uxQx18o/WOeBOA6OUU4dycbS4fFOX+KtGbw/FudavzRcEaU1WPpgz/BMZEPQuySS icwwObtau1ixsJPVVqJq00LEx6MI6p5gbBcAQ1zE2NDiK5nRuhTctO5mjqfJ5R5a Smg63ktXtoqD4GWCsqzUVeD02p6lH3Rzc7DKmN5B6Tz8gOPKsFCIyXERnKOrBHm4 yVSJZJGENoAygxSUN5JRoQqoKUEicCSsw91U1HgFfjQ5Co9VGhFOFMjQ7XXH28e3 ELKtHRxDpPwVfhFMzrN9PhOyjL1bUo/+zxf7Boz5sDkN7WqNcCU= =ZhOJ -END PGP SIGNATURE End Message ---
Bug#1056436: marked as done (pycryptodome's autopkg tests fail with Python 3.12)
Your message dated Thu, 11 Jan 2024 13:51:37 +
with message-id
and subject line Bug#1056436: fixed in pycryptodome 3.20.0+dfsg-1
has caused the Debian Bug report #1056436,
regarding pycryptodome's autopkg tests fail with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1056436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pycryptodome
Version: 3.18.0+dfsg1-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
pycryptodome's autopkg tests fail with Python 3.12:
[...]
512s ==
512s ERROR: testInit2
(Cryptodome.SelfTest.Util.test_asn1.DerBitStringTests.testInit2)
512s --
512s Traceback (most recent call last):
512s File
"/usr/lib/python3/dist-packages/Cryptodome/SelfTest/Util/test_asn1.py",
line 655, in testInit2
512s self.assertEquals(der.encode(), b('\x03\x04\x00\x02\x01\x01'))
512s ^
512s AttributeError: 'DerBitStringTests' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
512s
512s ==
512s ERROR: testDecode1
(Cryptodome.SelfTest.Util.test_asn1.DerSetOfTests.testDecode1)
512s --
512s Traceback (most recent call last):
512s File
"/usr/lib/python3/dist-packages/Cryptodome/SelfTest/Util/test_asn1.py",
line 731, in testDecode1
512s self.assertEquals(len(der),0)
512s ^
512s AttributeError: 'DerSetOfTests' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
512s
512s ==
512s ERROR: testDecode2
(Cryptodome.SelfTest.Util.test_asn1.DerSetOfTests.testDecode2)
512s --
512s Traceback (most recent call last):
512s File
"/usr/lib/python3/dist-packages/Cryptodome/SelfTest/Util/test_asn1.py",
line 741, in testDecode2
512s self.assertEquals(len(der),2)
512s ^
512s AttributeError: 'DerSetOfTests' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
512s
512s ==
512s ERROR: testDecode4
(Cryptodome.SelfTest.Util.test_asn1.DerSetOfTests.testDecode4)
512s --
512s Traceback (most recent call last):
512s File
"/usr/lib/python3/dist-packages/Cryptodome/SelfTest/Util/test_asn1.py",
line 756, in testDecode4
512s self.assertEquals(der,
512s ^
512s AttributeError: 'DerSetOfTests' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
512s
512s ==
512s ERROR: testEncode1
(Cryptodome.SelfTest.Util.test_asn1.DerSetOfTests.testEncode1)
512s --
512s Traceback (most recent call last):
512s File
"/usr/lib/python3/dist-packages/Cryptodome/SelfTest/Util/test_asn1.py",
line 695, in testEncode1
512s self.assertEquals(der.encode(), b('1\x00'))
512s ^
512s AttributeError: 'DerSetOfTests' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
512s
512s ==
512s ERROR: testEncode2
(Cryptodome.SelfTest.Util.test_asn1.DerSetOfTests.testEncode2)
512s --
512s Traceback (most recent call last):
512s File
"/usr/lib/python3/dist-packages/Cryptodome/SelfTest/Util/test_asn1.py",
line 707, in testEncode2
512s self.assertEquals(der.encode(),
b('1\x08\x02\x02\x00\xff\x02\x02\x01\x80'))
512s ^
512s AttributeError: 'DerSetOfTests' object has no attribute
'assertEquals'. Did you mean: 'assertEqual'?
512s
512s ==
512s ERROR: testEncode4
(Cryptodome.SelfTest.Util.test_asn1.DerSetOfTests.testEncode4)
512s --
512s Traceback (most recent call last):
512s File
"/usr/lib/python3/dist-packages/Cryptodome/SelfTest/Util/test_asn1.py",
line 723, in testEncode4
512s self.assertEquals(der.encode(),
Bug#1042650: marked as done (python-whoosh: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Thu, 11 Jan 2024 13:51:46 + with message-id and subject line Bug#1042650: fixed in python-whoosh 2.7.4+git6-g9134ad92-8 has caused the Debian Bug report #1042650, regarding python-whoosh: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 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.) -- 1042650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-whoosh Version: 2.7.4+git6-g9134ad92-7 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, python-whoosh fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build --buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/searching.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/scoring.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/index.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/highlight.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/__init__.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/formats.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/fields.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/spelling.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/writing.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/compat.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/classify.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/reading.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/externalsort.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/collectors.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/columns.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/multiproc.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/legacy.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/sorting.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/idsets.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > copying src/whoosh/system.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh > creating /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/automata > copying src/whoosh/automata/nfa.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/automata > copying src/whoosh/automata/lev.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/automata > copying src/whoosh/automata/__init__.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/automata > copying src/whoosh/automata/glob.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/automata > copying src/whoosh/automata/fsa.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/automata > copying src/whoosh/automata/reg.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/automata > creating /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/codec > copying src/whoosh/codec/whoosh3.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/codec > copying src/whoosh/codec/base.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/codec > copying src/whoosh/codec/__init__.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/codec > copying src/whoosh/codec/memory.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/codec > copying src/whoosh/codec/plaintext.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/codec > creating /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/support > copying src/whoosh/support/charset.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/support > copying src/whoosh/support/levenshtein.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/support > copying src/whoosh/support/relativedelta.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/support > copying src/whoosh/support/bench.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/support > copying src/whoosh/support/__init__.py -> > /<>/.pybuild/cpython3_3.11_whoosh/build/whoosh/support > copying src/whoosh/support/base85.py -> >
Bug#1059875: RM: rJava [i386] -- RoM: FTBFS as i386 builds no longer maintained upstream
( Resending to now correctly-typed package r-cran-rcdklibs -- Dirk ) On 11 January 2024 at 07:09, Dirk Eddelbuettel wrote: | | Package: ftp.debian.org | Severity: normal | | The rJava package (source package 'rjava', binary package r-cran-rjava) no | longer builds on i386 as most of the world, including R and its CRAN network, | have moved on from i386. | | So I am requesting the removal of the i386 builds from testing so that the | package can migrate; it works and tests fine everywhere else. | | Four packages are listed as reverse depends (see below). I will have to | presumably 'climb the tree' and request removal of each of these and will | likely dues so in due course. For now, I am CCing the packages in question, | as well as the initial bug report #1059875. | | Dirk | | | $ ssh mirror.ftp-master.debian.org "dak rm -Rn rjava" | Will remove the following packages from unstable: | | r-cran-rjava | 1.0-6-1+b1 | i386 | r-cran-rjava | 1.0-10-1 | amd64, arm64, armel, armhf, mips64el, ppc64el, riscv64, s390x | rjava |1.0-6-1 | source | rjava | 1.0-10-1 | source | | Maintainer: Dirk Eddelbuettel | | --- Reason --- | | -- | | Checking reverse dependencies... | # Broken Depends: | libgoby-java: goby-java | r-cran-rcdk: r-cran-rcdk | r-cran-rcdklibs: r-cran-rcdklibs | | # Broken Build-Depends: | beast-mcmc: r-cran-rjava | libgoby-java: r-cran-rjava | r-cran-rcdk: r-cran-rjava | r-cran-rcdklibs: r-cran-rjava | | Dependency problem found. | | $ | | | -- | dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1059875: RM: rJava [i386] -- RoM: FTBFS as i386 builds no longer maintained upstream
Package: ftp.debian.org Severity: normal The rJava package (source package 'rjava', binary package r-cran-rjava) no longer builds on i386 as most of the world, including R and its CRAN network, have moved on from i386. So I am requesting the removal of the i386 builds from testing so that the package can migrate; it works and tests fine everywhere else. Four packages are listed as reverse depends (see below). I will have to presumably 'climb the tree' and request removal of each of these and will likely dues so in due course. For now, I am CCing the packages in question, as well as the initial bug report #1059875. Dirk $ ssh mirror.ftp-master.debian.org "dak rm -Rn rjava" Will remove the following packages from unstable: r-cran-rjava | 1.0-6-1+b1 | i386 r-cran-rjava | 1.0-10-1 | amd64, arm64, armel, armhf, mips64el, ppc64el, riscv64, s390x rjava |1.0-6-1 | source rjava | 1.0-10-1 | source Maintainer: Dirk Eddelbuettel --- Reason --- -- Checking reverse dependencies... # Broken Depends: libgoby-java: goby-java r-cran-rcdk: r-cran-rcdk r-cran-rcdklibs: r-cran-rcdklibs # Broken Build-Depends: beast-mcmc: r-cran-rjava libgoby-java: r-cran-rjava r-cran-rcdk: r-cran-rjava r-cran-rcdklibs: r-cran-rjava Dependency problem found. $ -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1060440: llvm-toolchain-17: 1:17.0.6-4 FTBFS on i386, armel
Source: llvm-toolchain-17 Version: 1:17.0.6-4 Severity: serious Tags: ftbfs pending Justification: fails to build from source (but built successfully in the past) Forwarded: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/130 llvm-toolchain-17_1:17.0.6-4 has a FTBFS issue on i386: https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-17=i386=1%3A17.0.6-4=1704824852=0 > dh_install: warning: Cannot find (any matches for) > "usr/lib/llvm-17/lib/clang/17/bin/hwasan_symbolize" (tried in ., debian/tmp) ... > dh_install: warning: Cannot find (any matches for) > "usr/lib/llvm-17/lib/clang/17*/lib/linux/liborc_rt*" (tried in ., debian/tmp) and an unrelated FTBFS on armel: https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-17=armel=1%3A17.0.6-4=1704818089=0 > In file included from > /<>/compiler-rt/lib/builtins/arm/sync_fetch_and_and_4.S:14: > /<>/compiler-rt/lib/builtins/arm/sync-ops.h:22:2: error: DMB is > only supported on ARMv6+ >22 | #error DMB is only supported on ARMv6+ It looks as though these are already known and already fixed in the packaging git repo. Thanks, smcv
Processed: found 1060429 in 2.1.0-1
Processing commands for cont...@bugs.debian.org: > found 1060429 2.1.0-1 Bug #1060429 [python-django-solo] solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py There is no source info for the package 'python-django-solo' at version '2.1.0-1' with architecture '' Unable to make a source version for version '2.1.0-1' Marked as found in versions 2.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: add patch
Processing control commands:
> tags -1 + patch
Bug #1058365 [python-jedi] python-lsp-server: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Added tag(s) patch.
--
1058365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058365: add patch
Control: tags -1 + patch patch at https://launchpadlibrarian.net/708712831/python-jedi_0.18.2-1_0.18.2-1ubuntu1.diff.gz
Processed: bug 1058296 is forwarded to https://github.com/dbnicholson/ostree-push/issues/16
Processing commands for cont...@bugs.debian.org:
> forwarded 1058296 https://github.com/dbnicholson/ostree-push/issues/16
Bug #1058296 [src:ostree-push] ostree-push: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/dbnicholson/ostree-push/issues/16'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058290: Kafka vs Six
This one line is a no-op under Python3 and can be removed > from kafka.vendor.six.moves import range I ll have a more torough look at home and use CodeSearch to locate vendored copies of six.py Greetings
Bug#1037852: Bug#1056886: May be new upstream version fixes this issue
Hi Emmanuel, Am Thu, Jan 11, 2024 at 05:57:03AM -0300 schrieb Emmanuel Arias: > Thanks for your work. Yes, two new dependency must be added to Debian. I > postponed all this work, until finish with python-cassandra-driver. I hope > take scalene in the next week. Just take your time. I simply was checking RC bugs with patch (which was the case for the cython3(-legacy) bug) to lend some helping hands. It turned out this was not that cheap ;-) > Thanks again, you make some steps for me :) Thanks to you for all your work Andreas. > Cheers, > Emmanuel > > El jue, 11 de ene de 2024, 05:33, Andreas Tille escribió: > > > Hi, > > > > I tried to check whether the new upstream version might fix gcc-13 / > > Python3.12 > > issues. I've pushed my work to Salsa but it needs new dependencies > > (at least https://github.com/emeryberger/Heap-Layers may be two more) > > and I gave up here since I have no specific interest in this package. Hope > > this might be helpful anyway. > > > > Kind regards > > Andreas. > > > > -- > > http://fam-tille.de > > > > -- http://fam-tille.de
Bug#1060434: ftbfs: usr/share/java/jansi1.jar is a symlink of a non-exist file jansi1-1.18.jar
Source: jansi1 Version: 1.18-3 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sweetyf...@deepin.org Hi, During a rebuild of jansi1, your package built successfully but contains a broken symlink. The symlink usr/share/java/jansi1.jar points to jansi1-1.18.jar but the target file does not exist. Thanks! Tianyu Chen @ deepin -- System Information: Distributor ID: Deepin Description:Deepin 23 Release:23 Codename: beige Architecture: x86_64 Kernel: Linux 6.6.7-amd64-desktop-hwe (SMP w/16 CPU threads; PREEMPT) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1060432: rpds-py ftbfs in unstable
Package: src:rpds-py Version: 0.12.0-2 Severity: serious Tags: sid trixie ftbfs rpds-py ftbfs in unstable, because of missing build dependencies: Issues preventing migration: ∙ ∙ rpds-py unsatisfiable Build-Depends(-Arch) on amd64: librust-archery-dev ∙ ∙ rpds-py unsatisfiable Build-Depends(-Arch) on amd64: librust-rpds-dev
Processed: found 1055494 in 1.2.1+dfsg-2, found 1056054 in 5.0.1-1, tagging 1022957 ...
Processing commands for cont...@bugs.debian.org: > found 1055494 1.2.1+dfsg-2 Bug #1055494 [clamav-doc] clamav-doc: missing Breaks+Replaces: clamav (<< 1.2) Marked as found in versions clamav/1.2.1+dfsg-2. > found 1056054 5.0.1-1 Bug #1056054 [openmpi-doc] openmpi-doc: /usr/share/man/man1/pterm.1.gz is already shipped by pterm Marked as found in versions openmpi/5.0.1-1. > tags 1022957 - patch pending Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package Removed tag(s) pending and patch. > reassign 1059590 src:nvidia-graphics-drivers Bug #1059590 [nvidia-graphics-drivers-tesla] [INTL:ro] Romanian debconf templates translation of "nvidia-graphics-drivers-tesla" Bug reassigned from package 'nvidia-graphics-drivers-tesla' to 'src:nvidia-graphics-drivers'. Ignoring request to alter found versions of bug #1059590 to the same values previously set Ignoring request to alter fixed versions of bug #1059590 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1022957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022957 1055494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055494 1056054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056054 1059590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: lowering severity, ignoring the problem for now
Processing control commands: > severity -1 important Bug #1058031 [src:pygame] pygame: FTBFS with Python 3.12 Severity set to 'important' from 'serious' -- 1058031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058031: lowering severity, ignoring the problem for now
Control: severity -1 important lowering the severity, ignoring the problem for now. The package is now built for 3.12.
Bug#1060149: src:extrepo: fails to migrate to testing for too long: autopkgtest regression
On Sun, Jan 07, 2024 at 08:19:40AM +0100, Paul Gevers wrote:
> Hi Wouter,
>
> On 06-01-2024 20:51, Wouter Verhelst wrote:
> > > The Release Team considers packages that are out-of-sync between testing
> > > and
> > > unstable for more than 30 days as having a Release Critical bug in testing
> > > [1]. Your package src:extrepo has been trying to migrate for 33 days [2].
> >
> > This should have been fixed with the recent upload of extrepo-offline-data?
>
> Doesn't that mean that there is a versioned relation or a Breaks needed
> somewhere?
Not really. The issue is that the old version of extrepo-offline-data
did not have the "debian_official" repository for trixie yet, and the
test tries to use that; and as of extrepo 0.12, the default is to enable
trixie, not bookworm.
Things work as expected, even with extrepo-offline-data, it's just that
the test suite expects a repository to be there which is not there
(yet).
I don't think that's worthy of a Breaks relationship, but it is an
oversight on my side.
To muddle the waters a bit more, I also uploaded extrepo 0.13 now, which
adds a few features, but the test is now failing because it got
entangled in the perl migration... I guess things will have to wait.
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
I will have a Tin-Actinium-Potassium mixture, thanks.
Bug#1037852: Bug#1056886: May be new upstream version fixes this issue
Hi Andreas, Thanks for your work. Yes, two new dependency must be added to Debian. I postponed all this work, until finish with python-cassandra-driver. I hope take scalene in the next week. Thanks again, you make some steps for me :) Cheers, Emmanuel El jue, 11 de ene de 2024, 05:33, Andreas Tille escribió: > Hi, > > I tried to check whether the new upstream version might fix gcc-13 / > Python3.12 > issues. I've pushed my work to Salsa but it needs new dependencies > (at least https://github.com/emeryberger/Heap-Layers may be two more) > and I gave up here since I have no specific interest in this package. Hope > this might be helpful anyway. > > Kind regards > Andreas. > > -- > http://fam-tille.de > >
Bug#1056877: marked as done (pyyaml: ftbfs with cython 3.0.x)
Your message dated Thu, 11 Jan 2024 08:36:38 + with message-id and subject line Bug#1056877: fixed in pyyaml 6.0.1-2 has caused the Debian Bug report #1056877, regarding pyyaml: ftbfs with cython 3.0.x 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.) -- 1056877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyyaml Version: 6.0.1-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: cython3 [This bug is targeted to the upcoming trixie release] The package fails to build in a test rebuild on at least arm64 with cython 3.0.5, but succeeds to build with cython 0.29.36. Please update the package to build with cython 3.0.5 (available in experimental). If the package cannot be built with cython 3.0.5, please change the build dependency from cython3 to cython3-legacy (available now in unstable). There is no replacement for cython3-dbg. Build logs building with cython 3.0.5 can be found at https://people.debian.org/~stefanor/cython3/cython-3.0.5/ See also https://lists.debian.org/debian-python/2023/11/msg00034.html --- End Message --- --- Begin Message --- Source: pyyaml Source-Version: 6.0.1-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of pyyaml, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated pyyaml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jan 2024 08:43:21 +0100 Source: pyyaml Architecture: source Version: 6.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Andreas Tille Closes: 1048163 1056877 Changes: pyyaml (6.0.1-2) unstable; urgency=medium . * Team upload. . [ Bas Couwenberg ] * Switch to cython3-legacy Closes: #1056877 . [ Andreas Tille ] * Fix clean target Closes: #1048163 * Standards-Version: 4.6.2 (routine-update) * Reorder sequence of d/control fields by cme (routine-update) * Remove trailing whitespace in debian/copyright (routine-update) * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update) * Add salsa-ci file (routine-update) * watch file standard 4 (routine-update) Checksums-Sha1: 673158df035cb93ba98bae7af115074b696bb912 2138 pyyaml_6.0.1-2.dsc abf3a965268a5cf809849472e285607cd314a8b0 8040 pyyaml_6.0.1-2.debian.tar.xz 9b3ebc338f9e89f932cf8786698c926dc0aed021 7925 pyyaml_6.0.1-2_amd64.buildinfo Checksums-Sha256: 6a692b97969dd245b08d5a0d64f2749450c222df97817c4b8cc255f87e405f94 2138 pyyaml_6.0.1-2.dsc 78412762a9e831e863c4e2cb30faa1076d00664e37756cf4c35e797a267de183 8040 pyyaml_6.0.1-2.debian.tar.xz 569be9950b8e552431814d513c2c2dc0bd4c808e75eecb3ae505b0c2c1e30ba7 7925 pyyaml_6.0.1-2_amd64.buildinfo Files: 395731e8c2d70c22e1ee8d548c958320 2138 python optional pyyaml_6.0.1-2.dsc e00f2805074748c1bff0a25fba21e38a 8040 python optional pyyaml_6.0.1-2.debian.tar.xz 1d958e443abc42c6c8ad64fac7da75e4 7925 python optional pyyaml_6.0.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmWfnToRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtH1KQ/9GdM3Et811OmjCh8kGhYZIgJ2r689gTix fOlkmqODquJHyXEU8K+hEw8mc08wgZv953kRuo4/CqQ2smNeeo7fPDfNeyxiyDST gxBmuFk7rQUhXfYj+1ovcQMXb/018mspkuLAhwzl+VmXVa5fllYDQSVoAttGmhg5 4W56X6ufbsQZoQQztZFXpXovZJp/txpHqmpx8HJbz9OkbV+HfbtayhOguYRmyqao bLT1fKR82Tfc3eF7AAayv0hmehNYfiN1asVEyEnZCfr7jNaxbwVveeAvnVd3zIbI seqvU3a+I4Vek78doqtNWRfy8FOX8UYSu3lp7o9yQoF6IKR2h5KL6OmAe7JN0ZHS q9PYtjhikxJoSJ1bQfR7uqxCRn3FdK3/ewkbemQvrmf9N+XaKn/Yh0NNJXCD3g+z NESWAQdY1ClIsSqwJi1JlPF8QUAmqg4OAt0A6dfTghWKivG9MO5HaG9or9BXUwGt yXdeBrx+VFE5vXC0IDQJ/e7RhYM+o57iNzdAFlajHRx6bQQKtH3bqlmWbNBjRcHo KHTK4/lrY0t/ZbqSH9mbaeEkJEedV8K3Co9u9n70t51dXPdSwRrEsfckghdZ7P+m gD5TgbvTPSjF4U2REn2jlLttZMs1VCD3NwTKd7LznYTBpDgiuFOZAhQUtc32Yjxf SAPGEOns6w4= =kxhy -END PGP SIGNATURE End Message ---
Bug#1037852: May be new upstream version fixes this issue
Hi, I tried to check whether the new upstream version might fix gcc-13 / Python3.12 issues. I've pushed my work to Salsa but it needs new dependencies (at least https://github.com/emeryberger/Heap-Layers may be two more) and I gave up here since I have no specific interest in this package. Hope this might be helpful anyway. Kind regards Andreas. -- http://fam-tille.de
