Package: src:python-django Version: 3:4.2.27-2 Tags: forky sid ftbfs User: [email protected] Usertags: gettext-0.26
Dear maintainer: During a rebuild of all packages in unstable using gettext 0.26 (yet to be uploaded for Debian), this package failed to build. Below you will find the last part of the build log (probably the most relevant part, but not necessarily). If required, the full build log is available here: https://people.debian.org/~sanvila/gettext/build-logs/ I've written this page to explain how to reproduce the problem: https://people.debian.org/~sanvila/gettext/ This bug will be raised to important once gettext is uploaded for experimental, and RC once gettext is uploaded for unstable, but I still don't know when I will be able to do that. If you fix this bug, it would help to have gettext in unstable sooner. About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages. If you cannot reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and add an affects on src:python-django, so that this is still visible in the BTS web page for this package. Thanks. -------------------------------------------------------------------------------- [...] test_empty_default_database (test_runner.tests.EmptyDefaultDatabaseTest.test_empty_default_database) An empty default database in settings does not raise an ImproperlyConfigured ... ok test_bad_test_runner (test_runner.tests.ManageCommandTests.test_bad_test_runner) ... ok test_custom_test_runner (test_runner.tests.ManageCommandTests.test_custom_test_runner) ... ok test_time_recorded (test_runner.tests.ManageCommandTests.test_time_recorded) ... ok test_run_checks_passes_and_teardown_raises (test_runner.tests.RunTestsExceptionHandlingTests.test_run_checks_passes_and_teardown_raises) Exceptions on teardown are surfaced if no exceptions happen during ... ok test_run_checks_raises (test_runner.tests.RunTestsExceptionHandlingTests.test_run_checks_raises) Teardown functions are run when run_checks() raises SystemCheckError. ... ok test_run_checks_raises_and_teardown_raises (test_runner.tests.RunTestsExceptionHandlingTests.test_run_checks_raises_and_teardown_raises) SystemCheckError is surfaced when run_checks() raises SystemCheckError ... ok ====================================================================== FAIL: test_msgfmt_error_including_non_ascii (i18n.test_compilation.CompilationErrorHandling.test_msgfmt_error_including_non_ascii) ---------------------------------------------------------------------- Traceback (most recent call last): File "/<<PKGBUILDDIR>>/tests/i18n/test_compilation.py", line 224, in test_msgfmt_error_including_non_ascii self.assertIn("' cannot start a field name", stderr.getvalue()) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AssertionError: "' cannot start a field name" not found in "Execution of msgfmt failed: /tmp/django__7khf47c/i18n_23u0gib5/commands/locale/ko/LC_MESSAGES/django.po:24: 'msgstr' is not a valid Python brace format string, unlike 'msgid'. Reason: In the directive number 0, a field name starts with a character that is not alphanumerical or underscore.\nmsgfmt: found 1 fatal error\n" ---------------------------------------------------------------------- Ran 16378 tests in 365.595s FAILED (failures=1, skipped=1288, expected failures=5) Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Destroying test database for alias 'other' ('file:memorydb_other?mode=memory&cache=shared')... Exception ignored while finalizing database connection <sqlite3.Connection object at 0x7fcd9af2b4c0>: ResourceWarning: unclosed database in <sqlite3.Connection object at 0x7fcd9af2b4c0> make[1]: *** [debian/rules:23: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:9: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2 --------------------------------------------------------------------------------
