Bug#1006735: marked as done (phpunit breaks symfony autopkgtest: rounding differences)
Your message dated Mon, 07 Mar 2022 00:22:30 + with message-id and subject line Bug#1006735: fixed in symfony 5.4.6+dfsg-1 has caused the Debian Bug report #1006735, regarding phpunit breaks symfony autopkgtest: rounding differences 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.) -- 1006735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpunit, symfony Control: found -1 phpunit/9.5.14-1 Control: found -1 symfony/5.4.4+dfsg-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of phpunit the autopkgtest of symfony fails in testing when that autopkgtest is run with the binary packages of phpunit from unstable. It passes when run with only packages from testing. In tabular form: passfail phpunitfrom testing9.5.14-1 symfonyfrom testing5.4.4+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of phpunit to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=phpunit https://ci.debian.net/data/autopkgtest/testing/amd64/s/symfony/19683263/log.gz There was 1 failure: 1) Symfony\Component\Stopwatch\Tests\StopwatchPeriodTest::testGetDuration with data set #5 (2, 3.14, true, 1.14) Failed asserting that 1.1401 is identical to 1.14. /tmp/autopkgtest-lxc.r3mmdasj/downtmp/build.1YM/src/src/Symfony/Component/Stopwatch/Tests/StopwatchPeriodTest.php:43 [37;41mFAILURES![0m [37;41mTests: 48[0m[37;41m, Assertions: 79[0m[37;41m, Failures: 1[0m[37;41m.[0m [41mKO[0m src/Symfony/Component/Stopwatch OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: symfony Source-Version: 5.4.6+dfsg-1 Done: David Prévot We believe that the bug you reported is fixed in the latest version of symfony, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot (supplier of updated symfony package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 06 Mar 2022 22:17:14 +0100 Source: symfony Architecture: source Version: 5.4.6+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: David Prévot Closes: 1006735 Changes: symfony (5.4.6+dfsg-1) unstable; urgency=medium . [ Fabien Potencier ] * Update VERSION for 5.4.6 (Fixing expected PHPUnit output, Closes: #1006735) . [ David Prévot ] * Document blank image used for tests Checksums-Sha1: c46ac9b502b8e6514bc4bdaa295d5b82b53c4144 13258 symfony_5.4.6+dfsg-1.dsc e75d01df5279e30513342baff962457506a15df2 4787336 symfony_5.4.6+dfsg.orig.tar.xz ed2f8a9c1f71b908d05aa50a6ef8885b6c0ea2bd 53560 symfony_5.4.6+dfsg-1.debian.tar.xz bbc5ee3a32ddec88927d2213e7341f82e069f8d7 52879 symfony_5.4.6+dfsg-1_amd64.buildinfo Checksums-Sha256: d14abf723dc1655934868b890597c1539bf649a14d7bd4d370ca9ab42e3d5515 13258 symfony_5.4.6+dfsg-1.dsc 1368ad65bd1b71c8162bfcaffbd50ee74b194917a029fef36d2ca76fdc833341 4787336 symfony_5.4.6+dfsg.orig.tar.xz 305f7fb4fcf1593e3fa3a2473fcf862623b65f9681c894dc8cadb7ba22833279 53560 symfony_5.4.6+dfsg-1.debian.tar.xz d0439f76233313a76fd90f55bbf800f7f514a64027f9d272db66d3560086648e 52879 symfony_5.4.6+dfsg-1_amd64.buildinfo Files: 6044c8ffd7997f0d79052ad4eeae2c0f 13258 php optional symfony_5.4.6+dfsg-1.dsc 0556f78103117786fb177818f029558e 4787336 php optional symfony_5.4.6+dfsg.orig.tar.xz c2e382a28199980fb17af96c659eaa92 53560 php optional symfony_5.4.6+dfsg-1.debian.tar.xz
Bug#1006734: marked as done (phpunit breaks php-symfony-polyfill autopkgtest: rounding differences)
Your message dated Mon, 07 Mar 2022 00:22:08 + with message-id and subject line Bug#1006734: fixed in php-symfony-polyfill 1.25.0-1 has caused the Debian Bug report #1006734, regarding phpunit breaks php-symfony-polyfill autopkgtest: rounding differences 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.) -- 1006734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phpunit, php-symfony-polyfill Control: found -1 phpunit/9.5.14-1 Control: found -1 php-symfony-polyfill/1.24.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of phpunit the autopkgtest of php-symfony-polyfill fails in testing when that autopkgtest is run with the binary packages of phpunit from unstable. It passes when run with only packages from testing. In tabular form: passfail phpunitfrom testing9.5.14-1 php-symfony-polyfill from testing1.24.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of phpunit to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=phpunit https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-symfony-polyfill/19690406/log.gz There were 4 failures: 1) Symfony\Polyfill\Tests\Php80\Php80Test::testFdiv with data set #0 (3.3, '10', '3') Failed asserting that 3.3335 is identical to 3.3. /tmp/autopkgtest-lxc.k0pkoihi/downtmp/build.exE/src/tests/Php80/Php80Test.php:35 2) Symfony\Polyfill\Tests\Php80\Php80Test::testFdiv with data set #1 (3.3, 10.0, 3.0) Failed asserting that 3.3335 is identical to 3.3. /tmp/autopkgtest-lxc.k0pkoihi/downtmp/build.exE/src/tests/Php80/Php80Test.php:35 3) Symfony\Polyfill\Tests\Php80\Php80Test::testFdiv with data set #0 (3.3, '10', '3') Failed asserting that 3.3335 is identical to 3.3. /tmp/autopkgtest-lxc.k0pkoihi/downtmp/build.exE/src/tests/Php80/Php80Test.php:35 4) Symfony\Polyfill\Tests\Php80\Php80Test::testFdiv with data set #1 (3.3, 10.0, 3.0) Failed asserting that 3.3335 is identical to 3.3. /tmp/autopkgtest-lxc.k0pkoihi/downtmp/build.exE/src/tests/Php80/Php80Test.php:35 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: php-symfony-polyfill Source-Version: 1.25.0-1 Done: David Prévot We believe that the bug you reported is fixed in the latest version of php-symfony-polyfill, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot (supplier of updated php-symfony-polyfill package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Mar 2022 00:32:13 +0100 Source: php-symfony-polyfill Architecture: source Version: 1.25.0-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: David Prévot Closes: 1006734 Changes: php-symfony-polyfill (1.25.0-1) unstable; urgency=medium . [ Nicolas Grekas ] * [Php80] Fix test for fdiv() (Closes: #1006734) Checksums-Sha1: f3cc1447d576e5e2aba06fa82f4cd4b2b3afaa8c 3560 php-symfony-polyfill_1.25.0-1.dsc 86c34c888970aa6f617697e5efaec745a1fd179b 1190057 php-symfony-polyfill_1.25.0.orig.tar.gz 62bbcd55c67b8b5fc1b9e54f2e45edb049d76077 8536 php-symfony-polyfill_1.25.0-1.debian.tar.xz db9867556afe70f64128c73bacbcae8c6510e655 13874 php-symfony-polyfill_1.25.0-1_amd64.buildinfo Checksums-Sha256:
Processed: limit source to symfony, tagging 1006735
Processing commands for cont...@bugs.debian.org: > limit source symfony Limiting to bugs with field 'source' containing at least one of 'symfony' Limit currently set to 'source':'symfony' > tags 1006735 + pending Bug #1006735 [src:phpunit, src:symfony] phpunit breaks symfony autopkgtest: rounding differences Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to php-symfony-polyfill, tagging 1006734
Processing commands for cont...@bugs.debian.org: > limit source php-symfony-polyfill Limiting to bugs with field 'source' containing at least one of 'php-symfony-polyfill' Limit currently set to 'source':'php-symfony-polyfill' > tags 1006734 + pending Bug #1006734 [src:phpunit, src:php-symfony-polyfill] phpunit breaks php-symfony-polyfill autopkgtest: rounding differences Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006537: marked as done (dask: autopkgtest failure on 32 bit, mismatch in size of data structure.)
Your message dated Sun, 06 Mar 2022 20:39:19 + with message-id and subject line Bug#1006537: fixed in dask 2022.01.0+dfsg-2 has caused the Debian Bug report #1006537, regarding dask: autopkgtest failure on 32 bit, mismatch in size of data structure. 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.) -- 1006537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dask Version: 2022.01.0+dfsg-1 Severity: serious The autopkgtest for dask is once-again failing on 32-bit architectures, this is blocking the fix for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005962 from migrating to testing. > assert buf.getvalue() == expected E assert " E Int64Index: 4 entries, 0 to 3 E Data columns (total 3 columns): E# Column Non-Null Count Dtype E --- -- -- - E0 x 4 non-null int64 E1 y 4 non-null category... E E ...Full output truncated (7 lines hidden), use '-vv' to show /usr/lib/python3/dist-packages/dask/dataframe/tests/test_dataframe.py:3612: AssertionError I think the most likely explanation is that the memory usage of the data structure is indeed lower on 32-bit architectures and that this does not indicate a bug. As such I have prepared a patch that adjusts the expected result in the test based on the pointer size on the current architecture. diff -Nru dask-2022.01.0+dfsg/debian/changelog dask-2022.01.0+dfsg/debian/changelog --- dask-2022.01.0+dfsg/debian/changelog2022-02-21 01:11:53.0 + +++ dask-2022.01.0+dfsg/debian/changelog2022-02-27 07:27:00.0 + @@ -1,3 +1,11 @@ +dask (2022.01.0+dfsg-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Adjust test_dataframe.py for different data structure sizes on 32-bit +architectures. + + -- Peter Michael Green Sun, 27 Feb 2022 07:27:00 + + dask (2022.01.0+dfsg-1) unstable; urgency=medium * New upstream release diff -Nru dask-2022.01.0+dfsg/debian/patches/series dask-2022.01.0+dfsg/debian/patches/series --- dask-2022.01.0+dfsg/debian/patches/series 2022-02-20 22:18:36.0 + +++ dask-2022.01.0+dfsg/debian/patches/series 2022-02-27 07:27:00.0 + @@ -9,3 +9,4 @@ use-youtube-nocookie.patch reproducible-config-autofunction.patch 32bit-comatibility.patch +test-dataframe-32-bit.patch diff -Nru dask-2022.01.0+dfsg/debian/patches/test-dataframe-32-bit.patch dask-2022.01.0+dfsg/debian/patches/test-dataframe-32-bit.patch --- dask-2022.01.0+dfsg/debian/patches/test-dataframe-32-bit.patch 1970-01-01 00:00:00.0 + +++ dask-2022.01.0+dfsg/debian/patches/test-dataframe-32-bit.patch 2022-02-27 07:27:00.0 + @@ -0,0 +1,25 @@ +Description: Adjust test_dataframe.py for different data structure sizes on 32-bit architectures. +Author: Peter Michael Green + +Index: dask-2022.01.0+dfsg/dask/dataframe/tests/test_dataframe.py +=== +--- dask-2022.01.0+dfsg.orig/dask/dataframe/tests/test_dataframe.py dask-2022.01.0+dfsg/dask/dataframe/tests/test_dataframe.py +@@ -3597,6 +3597,8 @@ def test_categorize_info(): + # Verbose=False + buf = StringIO() + ddf.info(buf=buf, verbose=True) ++pointersize = np.array([0],dtype=np.uintp).itemsize ++bytecount = 128 + pointersize * 46 + expected = ( + "\n" + "Int64Index: 4 entries, 0 to 3\n" +@@ -3607,7 +3609,7 @@ def test_categorize_info(): + " 1 y 4 non-null category\n" + " 2 z 4 non-null object\n" + "dtypes: category(1), object(1), int64(1)\n" +-"memory usage: 496.0 bytes\n" ++"memory usage: "+str(bytecount)+".0 bytes\n" + ) + assert buf.getvalue() == expected + --- End Message --- --- Begin Message --- Source: dask Source-Version: 2022.01.0+dfsg-2 Done: Diane Trout We believe that the bug you reported is fixed in the latest version of dask, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Diane Trout (supplier of updated dask package) (This message was generated automatically at
Bug#1005149: marked as done (ansible: misbuilds with two supported Python versions)
Your message dated Sun, 06 Mar 2022 20:34:22 + with message-id and subject line Bug#1005149: fixed in ansible 5.4.0-1 has caused the Debian Bug report #1005149, regarding ansible: misbuilds with two supported Python versions 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.) -- 1005149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dh-python Version: 5.20220119 Severity: normal Dear Maintainer, While building ansible version 2.10.7+merged+base+2.10.8+dfsg-1 with python 3.10 I have noticed that /usr/lib/python3.10/dist-packages/ansible is not properly cleaned out. These builds are successfully cleaning out /usr/lib/python3.9/dist-packages/ansible/. This results in broken symbolic links and failing autopkgtests with python 3.10. Thank you, William --- End Message --- --- Begin Message --- Source: ansible Source-Version: 5.4.0-1 Done: Lee Garrett We believe that the bug you reported is fixed in the latest version of ansible, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lee Garrett (supplier of updated ansible package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 06 Mar 2022 20:05:44 +0100 Source: ansible Architecture: source Version: 5.4.0-1 Distribution: unstable Urgency: medium Maintainer: Lee Garrett Changed-By: Lee Garrett Closes: 1005149 Changes: ansible (5.4.0-1) unstable; urgency=medium . * New upstream release. * Release to unstable. * Switch build-dep from python3-all to python3 (Closes: #1005149) Checksums-Sha1: 98d6f46fbbe09e50247cad5a1d353ea29d397a4b 3128 ansible_5.4.0-1.dsc 37ae30edffc6f74a24d5257f58f5b2a9cc154c14 38255326 ansible_5.4.0.orig.tar.gz fa87bd3977e97f4feab58018e7003db760f96ebf 866 ansible_5.4.0.orig.tar.gz.asc a386a146f309530c52746dc7b86b4693898756b4 28236 ansible_5.4.0-1.debian.tar.xz 0b61d16c5a4187be0ecf2a08c530c991507194e6 7676 ansible_5.4.0-1_amd64.buildinfo Checksums-Sha256: 3d13f247692de9a539229ed0cd60f2c9c455cfa7c4bf40c51c34e8a000d7ec9d 3128 ansible_5.4.0-1.dsc 2f0ecbd8a3232e520bf3e3bc23f40dda60b9ce7924ca194bd35f4de4027100fc 38255326 ansible_5.4.0.orig.tar.gz a599ad807218a89230d8bc4e836a8bd557a2bee46e9fb6290b8e4ff4610cf523 866 ansible_5.4.0.orig.tar.gz.asc f7d8b655e5670d033eff4fc9673f33af544f93c76f255970aa0adac1f0848c03 28236 ansible_5.4.0-1.debian.tar.xz a3747aa185cf2227b6f6581d9c63b0db6fe8070e1d6db98a8e91a14ff121d40b 7676 ansible_5.4.0-1_amd64.buildinfo Files: ec4ed46d88cad277f5f57917f89bc121 3128 admin optional ansible_5.4.0-1.dsc b831330f9d36e637924935d25bc33e07 38255326 admin optional ansible_5.4.0.orig.tar.gz a60b21e2749513c20754af385e834f7c 866 admin optional ansible_5.4.0.orig.tar.gz.asc dda3bc25923632d4ed4ab4247f144cc4 28236 admin optional ansible_5.4.0-1.debian.tar.xz b0b512cb7beaf47393ec7309ea475cc4 7676 admin optional ansible_5.4.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQQzBAEBCgAdFiEE2EfGJRCpwv8kLOAs1gShxII+4PgFAmIlDgIACgkQ1gShxII+ 4PjY9x/6AvKtCY7oI1YgQ60TaPM8o/IM1VYBz7NtLIjn/11OHj1lQ28NBhYPBHhl V1N484lijfmEx46+z7MIdjUNRF2NC1a122bWLljDi/3MSxTWROlKLCAQfD1PlrLJ GN14FMqLO8ZMXrbdR5o4nGrjITtibjGO91cPSw5L9T6h1dR++HxOGL+5MFaOPvfH Zbam9NkO4rZHwB/puWvteWUgtjYDFyplY4nMrKb6Qqbzz4je7NOAsHiHaRvQ1zVr J7sLuGopSiTXhT7AA8ddNCXKmUQ+mBZ7Rx8+DNBcSUiAGplRwalR9V7K5QV+jb3Y nDG6qGniGJNlg+Nvp/5LnjBkY/4KJru6DK/dhNnzsMf3a+Qm/2qjLF4ZwNQbg2Pn w0j+xndu7H8NEp+BOEnk669i+/P19S0TuAxB4HHT7CMA/vADNVBaPxc/Zc/lszzw i1A4Q9kPb3Yxj3bt4nb5IceXOzzaaU/PDOCHUhLI/s5TXDpw3kLbrLwiyIs6iSIl 8f8kTa5M9lb9473bNn9oFsizHakrdeu3IMULhy4qOPDgSSuoxiu4y27h04yy4GD6 YZHQg9kXPLz53EncW0VPcCoOD91+ujGh+n18zHXu4JhTv8CDPpf67PaVbDI3AU/7 /ctUL5+UPk9XFAsrWc1nobN0SUlWbSP5xcqajEbJJT6FHQg/4ZZuTaaYedWv9TLh A8qodKkPPGvgzXKctSeb91tgS47NPjIc+0/DDbRrmaQCfkyuxXQyaApGSF5nfvcG zc6i8NOjO9FBX3di9k3PiIeKh3aAq+8GM/DdQlc85LuLlqU03vaicd9xRWGtl3r/ EQVMlBAtG1TnE5oSKTYjvf4g0pFGKn7j58fIBBsLjpq/n6gC7joNFfl6mLMOiN/K jNaB13vJQoFI8QULMcxAEQV2C+QbDVP4OUrgGjX0iSP4PLqgQ2T0vtPMhMQX6xHQ 2SeNPqwpXDLm0CkNbpFdN13/tuPG4iQvc05pzcpI5TfqDnmnAlj0SyRKuSdY05c6
Bug#1006850: python-munch: autopkgtest regression: No module named 'pkg_resources'
Source: python-munch Version: 2.5.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-munch the autopkgtest of python-munch fails in testing when that autopkgtest is run with the binary packages of python-munch from unstable. It passes when run with only packages from testing. In tabular form: passfail python-munch from testing2.5.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python-munch https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-munch/19770649/log.gz Testing with python3.10: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/munch/__init__.py", line 24, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' autopkgtest [22:55:12]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Processed: cups breaks python-cups autopkgtest
Processing control commands: > found -1 cups/2.4.1op1-1 Bug #1006849 [src:cups, src:python-cups] cups breaks python-cups autopkgtest Marked as found in versions cups/2.4.1op1-1. > found -1 python-cups/2.0.1-5 Bug #1006849 [src:cups, src:python-cups] cups breaks python-cups autopkgtest Marked as found in versions python-cups/2.0.1-5. -- 1006849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006849: cups breaks python-cups autopkgtest
Source: cups, python-cups Control: found -1 cups/2.4.1op1-1 Control: found -1 python-cups/2.0.1-5 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of cups the autopkgtest of python-cups fails in testing when that autopkgtest is run with the binary packages of cups from unstable. It passes when run with only packages from testing. In tabular form: passfail cups from testing2.4.1op1-1 python-cupsfrom testing2.0.1-5 all others from testingfrom testing I copied some of the output at the bottom of this report. Unfortunately the output is rather dense, I have no clue what goes wrong. Currently this regression is blocking the migration of cups to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=cups https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-cups/19783617/log.gz - Create printer test-printer1 - Interrupted (or finished), delete test printers: done. autopkgtest [14:11:08]: test testscripts OpenPGP_signature Description: OpenPGP digital signature
Bug#1001040: marked as done (ansible-core: No such file or directory: '/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py')
Your message dated Sun, 06 Mar 2022 19:03:36 + with message-id and subject line Bug#1001040: fixed in ansible-core 2.12.3-1 has caused the Debian Bug report #1001040, regarding ansible-core: No such file or directory: '/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py' 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.) -- 1001040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ansible-core Version: 2.12.0-1 Severity: important Dear maintainer, while upgrading ansible-core from 2.11.6-1 to 2.12.0-1, I get the following error during postinst: > Setting up ansible-core (2.12.0-1) ... > [Errno 2] No such file or directory: > '/usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py'dpkg: > error processing package ansible-core (--configure): > installed ansible-core package post-installation script subprocess returned > error exit status 1 Because of this error the package stays unconfigured. $ ls -l /usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py lrwxrwxrwx 1 root root 13 Nov 18 13:42 /usr/lib/python3.10/dist-packages/ansible/module_utils/ansible_release.py -> ../release.py $ ls -l /usr/lib/python3.10/dist-packages/ansible/release.py ls: cannot access '/usr/lib/python3.10/dist-packages/ansible/release.py': No such file or directory Kind regards, Reiner signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ansible-core Source-Version: 2.12.3-1 Done: Lee Garrett We believe that the bug you reported is fixed in the latest version of ansible-core, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lee Garrett (supplier of updated ansible-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 06 Mar 2022 18:39:56 +0100 Source: ansible-core Architecture: source Version: 2.12.3-1 Distribution: unstable Urgency: medium Maintainer: Lee Garrett Changed-By: Lee Garrett Closes: 1001040 Changes: ansible-core (2.12.3-1) unstable; urgency=medium . * New upstream release * Switch build-dep from python3-all to python3 (Closes: #1001040) Checksums-Sha1: fe8295434593397f550976d9e59f17a7fc8ce96e 2927 ansible-core_2.12.3-1.dsc 7a52a3ee605f591e87aa7e8d3e4324984ef98dcd 7757271 ansible-core_2.12.3.orig.tar.gz 819452f2137881b3cb6e0e3d24571a64e4ea07ca 18584 ansible-core_2.12.3-1.debian.tar.xz cd28289549a1ed56353ca023132a89cb39a96922 7533 ansible-core_2.12.3-1_amd64.buildinfo Checksums-Sha256: de7c8b8db0ee8b006add43c4b5fe44f5b65b1947d0cca8daadddb9d63d737b83 2927 ansible-core_2.12.3-1.dsc 8a135a9f74c97cab67759293744ad34350f719523e8bd9bb9008df4cf953af20 7757271 ansible-core_2.12.3.orig.tar.gz b99f08c52ea0302c35e84f85d1ae04297e83940b47d2d78dbe2b0126023fd85a 18584 ansible-core_2.12.3-1.debian.tar.xz e76161fc58d09c15e91e4066ad61cf2dfea2702df24bad2169a8582dca9882cf 7533 ansible-core_2.12.3-1_amd64.buildinfo Files: 002459944fffccd6040529f77eb7a736 2927 admin optional ansible-core_2.12.3-1.dsc d9a00e9f033d7b43ebd43fb9db9c4f3b 7757271 admin optional ansible-core_2.12.3.orig.tar.gz 73f9971a5c41515b68553c69ffe6e640 18584 admin optional ansible-core_2.12.3-1.debian.tar.xz 6216ec6dd15c52a6c3658c31ebe29a39 7533 admin optional ansible-core_2.12.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQQzBAEBCgAdFiEE2EfGJRCpwv8kLOAs1gShxII+4PgFAmIk//IACgkQ1gShxII+ 4PjQeiAAigbBfLgefxw10CgeHjqCRo0qWI4XZuSIGTQN79mHjFcNf/WGQZU6vED6 gVnezRhYABtjTfgLO37MdUxg4qd5f5JxmAKf3T45VTswIcvnY3WDwsSI0E+sEGR8 elS3gGgiQzxYAgYR2o/Q56rH91Ncm0GxXl9/20nrkOKcECibA3xniDo96jZlh7Ku qvpuVnuIOOjbhnouWalrRF7Tf2W/ziIouJVMsCkNYQ4SJfuyP7lREQMw5nIX/hs4 A9kVUgwPwYmA83PMpGFDKJJqqnQ+/zNp6A7IM8H4oApuIJ/N5w6FRATLZxRuzhdV xs8pBTVhJ77eQkxkU1EwzMYSGZD1U7p69N10MhctS8t/mOqSYnf9xFvoZWVNiZMC UyAJA3RO4e5CVVgGDwss9/5To5h2NJhfQg9cHLqkiG5+uaI17wXf+gBBSDg1g8m0 vKQrHYO+8gO9bhr2sunaVcYaEKW0SGsuNeYkBh22ATDadSwPJ2c25EERctx/0Sw6 haaO1+WJeonr0Fs/Vv1S9IPXqC36+VKberv5t3qJSYNx0w9y+MEu4v9dLKBLL564
Processed: tagging 1006642, bug 1006642 is forwarded to https://gitlab.com/postmarketOS/osk-sdl/-/issues/143
Processing commands for cont...@bugs.debian.org: > tags 1006642 + upstream Bug #1006642 [src:osk-sdl] osk-sdl: autopkgtest failure (with gcc-12) Added tag(s) upstream. > forwarded 1006642 https://gitlab.com/postmarketOS/osk-sdl/-/issues/143 Bug #1006642 [src:osk-sdl] osk-sdl: autopkgtest failure (with gcc-12) Set Bug forwarded-to-address to 'https://gitlab.com/postmarketOS/osk-sdl/-/issues/143'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006056: marked as done (git-filter-repo: FTBFS: t9390-filter-repo.sh failed)
Your message dated Sun, 06 Mar 2022 17:05:11 +
with message-id
and subject line Bug#1006056: fixed in git-filter-repo 2.34.0-2
has caused the Debian Bug report #1006056,
regarding git-filter-repo: FTBFS: t9390-filter-repo.sh failed
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.)
--
1006056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-filter-repo
Version: 2.34.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> t/run_tests
>
>
> == t9390-filter-repo.sh ==
> ok 1 - check: basic -> basic-filename using '--path filename'
> ok 2 - check: basic -> basic-twenty using '--path twenty'
> ok 3 - check: basic -> basic-ten using '--path ten'
> ok 4 - check: basic -> basic-numbers using '--path ten --path twenty'
> ok 5 - check: basic -> basic-filename using '--invert-paths --path-glob t*en*'
> ok 6 - check: basic -> basic-numbers using '--invert-paths --path-regex
> f.*e.*e'
> ok 7 - check: basic -> basic-mailmap using '--mailmap ../t9390/sample-mailmap'
> ok 8 - check: basic -> basic-replace using '--replace-text
> ../t9390/sample-replace'
> ok 9 - check: basic -> basic-message using '--replace-message
> ../t9390/sample-message'
> ok 10 - check: empty -> empty-keepme using '--path keepme'
> not ok 11 - check: empty -> more-empty-keepme using '--path keepme
> --prune-empty=always --prune-degenerate=always'
> #
> # # Clean up from previous run
> # git pack-refs --all &&
> # rm .git/packed-refs &&
> #
> # # Run the example
> # cat $DATA/$INPUT | git filter-repo --stdin --quiet
> --force --replace-refs delete-no-add "${REST[@]}" &&
> #
> # # Compare the resulting repo to expected value
> # git fast-export --use-done-feature --all >compare &&
> # test_cmp $DATA/$OUTPUT compare
> #
> not ok 12 - check: empty -> less-empty-keepme using '--path keepme
> --prune-empty=never --prune-degenerate=never'
> #
> # # Clean up from previous run
> # git pack-refs --all &&
> # rm .git/packed-refs &&
> #
> # # Run the example
> # cat $DATA/$INPUT | git filter-repo --stdin --quiet
> --force --replace-refs delete-no-add "${REST[@]}" &&
> #
> # # Compare the resulting repo to expected value
> # git fast-export --use-done-feature --all >compare &&
> # test_cmp $DATA/$OUTPUT compare
> #
> ok 13 - check: degenerate -> degenerate-keepme using '--path moduleA/keepme'
> ok 14 - check: degenerate -> degenerate-moduleA using '--path moduleA'
> ok 15 - check: degenerate -> degenerate-globme using '--path-glob *me'
> ok 16 - check: degenerate -> degenerate-keepme-noff using '--path
> moduleA/keepme --no-ff'
> ok 17 - check: unusual -> unusual-filtered using '--path '
> ok 18 - check: unusual -> unusual-mailmap using '--mailmap
> ../t9390/sample-mailmap'
> ok 19 - --path-rename sequences/tiny:sequences/small
> ok 20 - --path-rename sequences:numbers
> ok 21 - --path-rename-prefix values:numbers
> ok 22 - --path-rename squashing
> ok 23 - --path-rename inability to squash
> ok 24 - --paths-from-file
> ok 25 - Mixing filtering and renaming paths, not enough filters
> ok 26 - Mixing filtering and renaming paths, enough filters
> ok 27 - Mixing filtering and to-subdirectory-filter
> ok 28 - --tag-rename
> ok 29 - tag of tag before relevant portion of history
> ok 30 - --subdirectory-filter
> ok 31 - --subdirectory-filter with trailing slash
> ok 32 - --to-subdirectory-filter
> ok 33 - --use-base-name
> ok 34 - refs/replace/ to skip a parent
> ok 35 - refs/replace/ to add more initial history
> ok 36 - creation/deletion/updating of replace refs
> ok 37 - --debug
> ok 38 - --dry-run
> ok 39 - --dry-run --debug
> ok 40 - --dry-run --stdin
> ok 41 - --analyze
> ok 42 - --analyze --report-dir
> ok 43 - --replace-text all options
> ok 44 - --replace-text binary zero_byte-0_char
> ok 45 - --replace-text binary zero_byte-no_0_char
> ok 46 - --replace-text text-file no_zero_byte-zero_char
> ok 47 - --strip-blobs-bigger-than
> ok 48 - --strip-blobs-with-ids
> ok 49 - commit message rewrite
> ok 50 - commit hash unchanged if
Processed: Bug#1006056 marked as pending in git-filter-repo
Processing control commands: > tag -1 pending Bug #1006056 [src:git-filter-repo] git-filter-repo: FTBFS: t9390-filter-repo.sh failed Added tag(s) pending. -- 1006056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006056: marked as pending in git-filter-repo
Control: tag -1 pending Hello, Bug #1006056 in git-filter-repo 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/git-filter-repo/-/commit/9615f50e7ee4656442daf2b690e0769c275aa5e9 Patch: Update expected test results for git 2.35. (Closes: #1006056) (this message was generated automatically) -- Greetings https://bugs.debian.org/1006056
Bug#1006330: marked as done (broken by python3-distro 1.7.0-1)
Your message dated Sun, 06 Mar 2022 16:34:30 +
with message-id
and subject line Bug#1006330: fixed in python-mitogen 0.3.1-3
has caused the Debian Bug report #1006330,
regarding broken by python3-distro 1.7.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1006330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ansible-mitogen
Version: 0.3.1-2
Severity: grave
Tags: upstream
Works with 1.6.0-2, is totally broken with 1.7.0-1.
[mux 685121] 14:38:50.354759 D mitogen: PkgutilMethod(): loading
'ansible.module_utils.distro' using
<_frozen_importlib_external.SourceFileLoader object at 0x7fa6329f7700> failed:
loader for distro cannot handle ansible.module_utils.distro
[mux 685121] 14:38:50.354915 D mitogen:
_get_module_via_sys_modules('ansible.module_utils.distro') ->
[mux 685121] 14:38:50.355021 D mitogen:
sys.modules['ansible.module_utils.distro'].__name__ is incorrect, assuming this
is a hacky module alias and ignoring it. Got 'distro', module object:
[mux 685121] 14:38:50.355142 D mitogen: ParentEnumerationMethod():
'ansible.module_utils.distro' is PKG_DIRECTORY:
'/usr/lib/python3/dist-packages/ansible/module_utils/distro/__init__.py'
...
[mux 685121] 14:38:51.209954 D mitogen: SysModulesMethod():
sys.modules['ansible.module_utils.distro._distro'] absent or not a regular
module
[mux 685121] 14:38:51.210217 D mitogen: ParentEnumerationMethod():
imp.find_module('_distro', [['/usr/lib/python3/dist-packages/distro']]) -> No
module named '_distro'
[mux 685121] 14:38:51.210346 D mitogen:
get_module_source('ansible.module_utils.distro._distro'): cannot find source
[mux 685121] 14:38:51.210449 D mitogen.responder: could not find source for
'ansible.module_utils.distro._distro'
[mux 685121] 14:38:51.210566 D mitogen.responder: sending
ansible.module_utils.distro._distro (0.05 KiB) to ssh.proxy.glacom.eu
[mux 685121] 14:38:51.224181 D mitogen.importer.[ssh.proxy.glacom.eu]:
received ansible.module_utils.distro._distro
...
[mux 685121] 14:38:51.232206 D mitogen: MitogenProtocol(unix_client.685155):
disconnecting
The full traceback is:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/ansible/executor/task_executor.py", line
158, in run
res = self._execute()
File "/usr/lib/python3/dist-packages/ansible/executor/task_executor.py", line
663, in _execute
result = self._handler.run(task_vars=variables)
File "/usr/lib/python3/dist-packages/ansible_mitogen/mixins.py", line 144, in
run
return super(ActionModuleMixin, self).run(tmp, task_vars)
File "/usr/lib/python3/dist-packages/ansible/plugins/action/normal.py", line
47, in run
result = merge_hash(result, self._execute_module(task_vars=task_vars,
wrap_async=wrap_async))
File "/usr/lib/python3/dist-packages/ansible_mitogen/mixins.py", line 374, in
_execute_module
self._set_temp_file_args(module_args, wrap_async)
File "/usr/lib/python3/dist-packages/ansible_mitogen/mixins.py", line 353, in
_set_temp_file_args
self._connection.get_good_temp_dir()
File "/usr/lib/python3/dist-packages/ansible_mitogen/connection.py", line
817, in get_good_temp_dir
self._connect()
File "/usr/lib/python3/dist-packages/ansible_mitogen/connection.py", line
839, in _connect
self._connect_stack(stack)
File "/usr/lib/python3/dist-packages/ansible_mitogen/connection.py", line
786, in _connect_stack
dct = mitogen.service.call(
File "/usr/lib/python3/dist-packages/mitogen/service.py", line 126, in call
return call_context.call_service(service_name, method_name, **kwargs)
File "/usr/lib/python3/dist-packages/mitogen/core.py", line 2284, in
call_service
return recv.get().unpickle()
File "/usr/lib/python3/dist-packages/mitogen/core.py", line 963, in unpickle
raise obj
mitogen.core.CallError: builtins.ModuleNotFoundError: The Mitogen master
process was unable to serve 'ansible.module_utils.distro._distro'. It may be a
native Python extension, or it may be missing entirely. Check the importer
debug logs on the master for more information.
File "", line 3669, in _dispatch_one
File "", line 3656, in _parse_request
File "", line 668, in import_module
File "", line 1516, in load_module
File "master:/usr/lib/python3/dist-packages/ansible_mitogen/target.py", line
85, in
import ansible_mitogen.runner
File "", line 1516, in load_module
File "master:/usr/lib/python3/dist-packages/ansible_mitogen/runner.py", line
85, in
import ansible.module_utils.basic
File "",
Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)
Hi Lev, On 06-03-2022 11:30, dogs...@riseup.net wrote: As I can see, there is only one reverse build-dependency on swi-prolog apart from eye and logol, that is ppl. It is a C++ library providing SWI-Prolog interface. I tried to build it against swi-prolog from unstable on amd64 porterbox and the build was successful (including tests, which are unfortunately not autopkgtest-ready). Is this enough to say the ABI change doesn't effect ppl? Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Set bug blocking
Processing commands for cont...@bugs.debian.org: > block 1006754 by 1006840 Bug #1006754 [theli] theli tries to use swarp from suckless-tools instead of SWarp from swarp 1006754 was not blocked by any bugs. 1006754 was not blocking any bugs. Added blocking bug(s) of 1006754: 1006840 > thanks Stopping processing here. Please contact me if you need assistance. -- 1006754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: suckless-tools: Please remove "provides: swarp"
Processing control commands: > tags -1 patch Bug #1006840 [suckless-tools] suckless-tools: Please remove "provides: swarp" Added tag(s) patch. > affects -1 theli swarp cpl-plugin-visir Bug #1006840 [suckless-tools] suckless-tools: Please remove "provides: swarp" Added indication that 1006840 affects theli, swarp, and cpl-plugin-visir -- 1006840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006840: suckless-tools: Please remove "provides: swarp"
Package: suckless-tools
Version: 46-1
Severity: serious
Control: tags -1 patch
Control: affects -1 theli swarp cpl-plugin-visir
Dear maintainer,
suckless-tools has the following packages listed as "Provides":
dmenu, lsw, slock, sprop, sselp, ssid, swarp, tabbed, wmname, xssstate
"swarp" however is (since 2013) a complete different package, with
different uses: it provides a tool to process astronomical images. As
the file name of the executable conflicts between the two packages, the
executable in the swarp package is not called /usr/bin/SWarp (the
original spelling of the astronomical tool).
However, the binary package is called "swarp", and the "Provides" of
suckless-tools conflicts with this. This runs into a problem when one
has "swarp" as a dependency, which is the case for theli and
cpl-plugin-visir. If suckless-tools was installed before theli or
cpl-plugin-visir are installed, the required "swarp" package is not
going to be installed, resulting in unusable packages. This is the
reason I made this bug RC.
Could you please remove the "swarp" provides from suckless-tools? In
Debian, the "swarp" Provides of suckless-tools is not used at all (and
would also make problems because of this).
For convenience, a patch is applied.
Best regards
OleFrom 3344c9297ebd4009efab61b28a1db60eb0f86997 Mon Sep 17 00:00:00 2001
From: Ole Streicher
Date: Sun, 6 Mar 2022 16:30:42 +0100
Subject: [PATCH] Don't provide "swarp"
This is in conflict with the "swarp" package.
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 81ded25..56f24ce 100644
--- a/debian/control
+++ b/debian/control
@@ -26,7 +26,7 @@ Depends:
${shlibs:Depends},
libcap2-bin [linux-any],
Suggests: dwm, stterm, surf
-Provides: dmenu, lsw, slock, sprop, sselp, ssid, swarp, tabbed, wmname, xssstate
+Provides: dmenu, lsw, slock, sprop, sselp, ssid, tabbed, wmname, xssstate
Description: simple commands for minimalistic window managers
This package provides simple commands designed to be used with a minimalistic
window manager like dwm but they can be useful in scripts regardless of the
--
2.34.1
Bug#1005669: marked as done (binutils-or1k-elf: FTBFS: autoreconf2.69: 'configure.ac' or 'configure.in' is required)
Your message dated Sun, 06 Mar 2022 14:48:34 + with message-id and subject line Bug#1005669: fixed in binutils-or1k-elf 1.0.3 has caused the Debian Bug report #1005669, regarding binutils-or1k-elf: FTBFS: autoreconf2.69: 'configure.ac' or 'configure.in' is required 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.) -- 1005669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-or1k-elf Version: 1.0.2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_autoreconf -D. autoreconf2.69 -- -f -i -v `debian/autoreconf` > autoreconf2.69: Entering directory `src' > autoreconf2.69: configure.ac: not using Gettext > autoreconf2.69: running: aclocal --force > autoreconf2.69: configure.ac: tracing > autoreconf2.69: configure.ac: not using Libtool > autoreconf2.69: running: /usr/bin/autoconf2.69 --force > autoreconf2.69: configure.ac: not using Autoheader > autoreconf2.69: configure.ac: not using Automake > autoreconf2.69: Leaving directory `src' > autoreconf2.69: Entering directory `src/bfd' > autoreconf2.69: running: aclocal --force -I . -I .. -I ../config > autoreconf2.69: running: libtoolize --copy --force > libtoolize: putting auxiliary files in '..'. > libtoolize: copying file '../ltmain.sh' > libtoolize: putting macros in '.'. > libtoolize: copying file './libtool.m4' > libtoolize: copying file './ltoptions.m4' > libtoolize: copying file './ltsugar.m4' > libtoolize: copying file './ltversion.m4' > libtoolize: copying file './lt~obsolete.m4' > libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac and > libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. > autoreconf2.69: running: /usr/bin/autoheader2.69 --force > autoreconf2.69: running: automake --add-missing --copy --force-missing > configure.ac:38: installing '../compile' > configure.ac:26: installing '../missing' > Makefile.am: installing '../depcomp' > autoreconf2.69: Leaving directory `src/bfd' > autoreconf2.69: Entering directory `src/binutils' > autoreconf2.69: running: aclocal --force -I .. -I ../config -I ../bfd > libtoolize: putting auxiliary files in '..'. > libtoolize: copying file '../ltmain.sh' > libtoolize: putting macros in '..'. > libtoolize: copying file '../libtool.m4' > libtoolize: copying file '../ltoptions.m4' > libtoolize: copying file '../ltsugar.m4' > libtoolize: copying file '../ltversion.m4' > libtoolize: copying file '../lt~obsolete.m4' > libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([..])' to configure.ac, > libtoolize: and rerunning libtoolize and aclocal. > libtoolize: 'AC_PROG_RANLIB' is rendered obsolete by 'LT_INIT' > configure.ac:30: installing '../compile' > configure.ac:27: installing '../missing' > Makefile.am: installing '../depcomp' > autoreconf2.69: Leaving directory `src/binutils' > autoreconf2.69: 'configure.ac' or 'configure.in' is required > dh_autoreconf: error: autoreconf2.69 -f -i -v src src/bfd src/binutils > src/etc src/gas src/gold src/gprof src/intl src/ld src/libctf src/opcodes > returned exit code 1 > make[1]: *** [debian/rules:34: override_dh_autoreconf] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/02/12/binutils-or1k-elf_1.0.2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: binutils-or1k-elf Source-Version: 1.0.3 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of binutils-or1k-elf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated
Bug#1004870: python-xarray: autopkgtest regression on s390x
Hi Graham, Could you please share the steps to reproduce the issue. As when I am trying to reproduce I ran into different problem of segmentation fault. Below are the steps that I followed. 1. Install python3-xarray on debian on s390x arch. 2. cd /usr/lib/python3/dist-packages/xarray 3. python3 -m pytest tests/ -vvv For now I am debugging the segmentation fault, however just wanted to validate the steps to reproduce. Thanks, Rajendra - Original message -From: "Graham Inggs" To: "Rajendra Kharat1" , 1004...@bugs.debian.org, debian-s...@lists.debian.orgCc:Subject: [EXTERNAL] Re: Bug#1004870: python-xarray: autopkgtest regression on s390xDate: Wed, Feb 16, 2022 4:39 PM Hi RajendraThanks for taking a look!Unfortunately, that cannot be the solution, as that commit is alreadypresent in the version of pandas in the archive [1].RegardsGraham[1] https://salsa.debian.org/science-team/pandas/-/blob/debian/pandas/core/arrays/datetimelike.py#L462 On Sun, 13 Feb 2022 at 15:14, Rajendra Kharat1 wrote:>> Hi Graham,>> This issue is again specific to no proper handling for bug endian environment.>> There is a fix from pandas library maintainers for this issue.>> https://github.com/pandas-dev/pandas/pull/40116 >> Please find the link above and check if this resolves your issue.>> Thanks,> Rajendra>>> - Original message -> From: Rajendra Kharat1/India/Contr/IBM> To: gin...@debian.org, 1004...@bugs.debian.org> Cc: sub...@bugs.debian.org> Subject: Re: [EXTERNAL] Bug#1004870: python-xarray: autopkgtest regression on s390x> Date: Thu, Feb 3, 2022 3:34 PM>> We are having a look. Will check and update.>> Thanks,> Rajendra
Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)
Paul Gevers писал 2022-03-06 01:09:
> Hi Lev,
>
> On 04-03-2022 11:42, dogs...@riseup.net wrote:
>>> Do you confirm that this ABI change doesn't effect the other reverse
>>> build dependencies of src:swi-prolog? If that's the case I'm fine with
>>> removing the block. But I'm afraid (without checking from my side)
>>> that the other package don't have the right virtual ABI package in
>>> their dependencies. If they do, wouldn't they need a rebuild too?
>>
>> New upstream version of eye was uploaded the same day as new version
>> of swi-prolog (in fact, after swi-prolog), and its autopkgtests pass
>> with swi-prolog in unstable (on amd64, and these are "not a regression"
>> on other architectures; they never were successful since at least Nov
>> 2019, as I can see).
>>
>> And eye already does this:
>>
>> Package: eye
>> Depends:
>> swi-prolog-nox,
>> swi-prolog-abi-${prolog:ABI},
>> ${misc:Depends}
>
> I already mentioned `eye` explicitly in my earlier messages, I wasn't
> worried about it. Please comment on the other reverse build
> dependencies (apart from eye and logol).
As I can see, there is only one reverse build-dependency on swi-prolog
apart from eye and logol, that is ppl. It is a C++ library providing
SWI-Prolog interface. I tried to build it against swi-prolog from
unstable on amd64 porterbox and the build was successful (including
tests, which are unfortunately not autopkgtest-ready).
Regards,
Lev
Processed: libwebp: diff for NMU version 1.2.1-7.1
Processing control commands: > tags 1006009 + pending Bug #1006009 [libwebp7] qtimageformats-opensource-src: FTBFS on mipsel: test failure Ignoring request to alter tags of bug #1006009 to the same tags previously set > tags 1006110 + pending Bug #1006110 [libwebp7] graphicsmagick: FTBFS on mipsel: test failure Ignoring request to alter tags of bug #1006110 to the same tags previously set -- 1006009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006009 1006110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libwebp: diff for NMU version 1.2.1-7.1
Processing control commands: > tags 1006009 + pending Bug #1006009 [libwebp7] qtimageformats-opensource-src: FTBFS on mipsel: test failure Added tag(s) pending. > tags 1006110 + pending Bug #1006110 [libwebp7] graphicsmagick: FTBFS on mipsel: test failure Added tag(s) pending. -- 1006009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006009 1006110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006009: libwebp: diff for NMU version 1.2.1-7.1
Control: tags 1006009 + pending
Control: tags 1006110 + pending
Dear maintainer,
I've prepared an NMU for libwebp (versioned as 1.2.1-7.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru libwebp-1.2.1/debian/changelog libwebp-1.2.1/debian/changelog
--- libwebp-1.2.1/debian/changelog 2022-02-16 20:02:28.0 +0100
+++ libwebp-1.2.1/debian/changelog 2022-03-06 11:12:08.0 +0100
@@ -1,3 +1,10 @@
+libwebp (1.2.1-7.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply upstream fix for mipsel regression (Closes: #1006009, 1006110)
+
+ -- Sebastian Ramacher Sun, 06 Mar 2022 11:12:08 +0100
+
libwebp (1.2.1-7) unstable; urgency=medium
* No changes; uploading to unstable as part of soname transition.
diff -Nru libwebp-1.2.1/debian/pachtes/0001-Fix-lossless-encoding-for-MIPS.patch libwebp-1.2.1/debian/pachtes/0001-Fix-lossless-encoding-for-MIPS.patch
--- libwebp-1.2.1/debian/pachtes/0001-Fix-lossless-encoding-for-MIPS.patch 1970-01-01 01:00:00.0 +0100
+++ libwebp-1.2.1/debian/pachtes/0001-Fix-lossless-encoding-for-MIPS.patch 2022-03-06 11:10:27.0 +0100
@@ -0,0 +1,47 @@
+From e4cbcdd2b5ff33a64f97fe49d67fb56f915657e8 Mon Sep 17 00:00:00 2001
+From: Vincent Rabaud
+Date: Tue, 1 Mar 2022 13:38:29 +0100
+Subject: [PATCH 1/2] Fix lossless encoding for MIPS.
+
+Bug: webp:558
+Change-Id: I3d3ddb64ed26a8d8ff5664664c5f20f6eadfeb4f
+---
+ src/dsp/lossless_enc_mips32.c | 8
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/src/dsp/lossless_enc_mips32.c b/src/dsp/lossless_enc_mips32.c
+index 0412a093..99630517 100644
+--- a/src/dsp/lossless_enc_mips32.c
b/src/dsp/lossless_enc_mips32.c
+@@ -347,24 +347,24 @@ static void GetCombinedEntropyUnrefined_MIPS32(const uint32_t X[],
+ static void AddVector_MIPS32(const uint32_t* pa, const uint32_t* pb,
+ uint32_t* pout, int size) {
+ uint32_t temp0, temp1, temp2, temp3, temp4, temp5, temp6, temp7;
+- const uint32_t end = ((size) / 4) * 4;
++ const int end = ((size) / 4) * 4;
+ const uint32_t* const LoopEnd = pa + end;
+ int i;
+ ASM_START
+ ADD_TO_OUT(0, 4, 8, 12, 1, pa, pb, pout)
+ ASM_END_0
+- for (i = end; i < size; ++i) pout[i] = pa[i] + pb[i];
++ for (i = 0; i < size - end; ++i) pout[i] = pa[i] + pb[i];
+ }
+
+ static void AddVectorEq_MIPS32(const uint32_t* pa, uint32_t* pout, int size) {
+ uint32_t temp0, temp1, temp2, temp3, temp4, temp5, temp6, temp7;
+- const uint32_t end = ((size) / 4) * 4;
++ const int end = ((size) / 4) * 4;
+ const uint32_t* const LoopEnd = pa + end;
+ int i;
+ ASM_START
+ ADD_TO_OUT(0, 4, 8, 12, 0, pa, pout, pout)
+ ASM_END_1
+- for (i = end; i < size; ++i) pout[i] += pa[i];
++ for (i = 0; i < size - end; ++i) pout[i] += pa[i];
+ }
+
+ #undef ASM_END_1
+--
+2.35.1
+
diff -Nru libwebp-1.2.1/debian/pachtes/series libwebp-1.2.1/debian/pachtes/series
--- libwebp-1.2.1/debian/pachtes/series 1970-01-01 01:00:00.0 +0100
+++ libwebp-1.2.1/debian/pachtes/series 2022-03-06 11:11:12.0 +0100
@@ -0,0 +1 @@
+0001-Fix-lossless-encoding-for-MIPS.patch
signature.asc
Description: PGP signature
