[Python-modules-team] Bug#961079: marked as done (python-django-contact-form: FTBFS with Django 3.x)
Your message dated Fri, 10 Sep 2021 18:54:43 +0200 with message-id and subject line Re: Bug#961079: python-django-contact-form: FTBFS with Django 3.x has caused the Debian Bug report #961079, regarding python-django-contact-form: FTBFS with Django 3.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.) -- 961079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django-contact-form Version: 1.4.2-3 Severity: normal User: python-modules-t...@lists.alioth.debian.org Usertags: django-3.x Dear maintainer, The version of Django experimental is currently 3.0.6-1. I have built the 153 reverse-dependencies in unstable against this version and 114 of these build & pass their testsuite successfully. Unfortunately, python-django-contact-form fails to build. Please see: http://bugs.debian.org/960890 ... for more information. Please use this bug report for queries or questions regarding Django 3.x that are not specific to this particular package in order to reduce duplicated work across all of the bugs. […] == ERROR: contact_form.tests.test_forms (unittest.loader._FailedTest) -- ImportError: Failed to import test module: contact_form.tests.test_forms Traceback (most recent call last): File "/usr/lib/python3.8/unittest/loader.py", line 436, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.8/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/home/lamby/temp/cdt.20200517000949.P3c9Eukd7z.ags.lamby-debian-experimental.python3-django-contact-form/python-django-contact-form-1.4.2/contact_form/tests/test_forms.py", line 7, in from django.utils.six import text_type ModuleNotFoundError: No module named 'django.utils.six' […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- python-django-contact-form.1.4.2-3.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Version: 1.9-1 Forgotten to add this bug number to the changelog before 1.9-1 was uploaded ... but by the newer version this issue is gone. So closing this report by this email. Am Tue, May 19, 2020 at 09:35:59PM +0100 schrieb Chris Lamb: > Source: python-django-contact-form > Version: 1.4.2-3 > Severity: normal > User: python-modules-t...@lists.alioth.debian.org > Usertags: django-3.x > > Dear maintainer, > > The version of Django experimental is currently 3.0.6-1. I have built > the 153 reverse-dependencies in unstable against this version and 114 > of these build & pass their testsuite successfully. Unfortunately, > python-django-contact-form fails to build. Please see: > > http://bugs.debian.org/960890 > > ... for more information. Please use this bug report for queries > or questions regarding Django 3.x that are not specific to this > particular package in order to reduce duplicated work across all of > the bugs.--- End Message --- ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#974489: marked as done (python-iptables: autopkgtest must be marked superficial)
Your message dated Fri, 10 Sep 2021 16:33:45 + with message-id and subject line Bug#974489: fixed in python-iptables 1.0.0-2 has caused the Debian Bug report #974489, regarding python-iptables: autopkgtest must be marked superficial 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.) -- 974489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-iptables X-Debbugs-CC: elb...@debian.org Severity: important Usertags: superficialtest Dear Maintainer, It has been noticed that the autopkgtest in python-iptables is running a trivial command that does not provide significant test coverage: - import iptc Executing that command is considered to be a trivial test, which does not provide significant coverage for a package as a whole. But these tests are a useful way to detect regressions in dependencies and prevent them from breaking your package. However, it is important that we are realistic about the level of test coverage provided by these commands: most regressions cannot be detected in this way. So it is not appropriate for packages with only superficial tests to have the reduced migration time to migrate from unstable to testing as that means less opportunity for testing by users compared to the package with no tests. To support this, the keyword "Restrictions: superficial" has been defined [1]. Packages where all tests are marked with this keyword are not considered for the reduced migration age from unstable to testing, and will not be allowed to migrate automatically in later stages of the freeze [2]. Its always better to have more extensive testing than having superficial testing, which again is better than having no test. Please consider i) Adding a non-trivial test, and/or ii) Mark the trivial test with "Restrictions: superficial", similar to [3] or [4]. The Release Team has listed this issue in the list of Release Critical Issues for bullseye [5] and has mentioned that the test must be marked superficial if it is not testing one of its own installed binary packages in some way. As a result, the severity of this bug report might be increased to serious in future. [1] https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions [2] https://release.debian.org/bullseye/freeze_policy.html [3] https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468 [4] https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3 [5] https://release.debian.org/bullseye/rc_policy.txt -- Regards Sudip --- End Message --- --- Begin Message --- Source: python-iptables Source-Version: 1.0.0-2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of python-iptables, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated python-iptables 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, 10 Sep 2021 12:03:43 -0400 Source: python-iptables Architecture: source Version: 1.0.0-2 Distribution: unstable Urgency: high Maintainer: Debian Python Team Changed-By: Boyuan Yang Closes: 974489 Changes: python-iptables (1.0.0-2) unstable; urgency=high . * Team upload. . [ IOhannes m zmölnig (Debian/GNU) ] * debian/tests/control: Mark import-test as superficial. (Closes: #974489) . [ Michael Hudson-Doyle ] * debian/patches/0002-fix-locating-_xtables_libdir_with_glibc-2.32.patch: Add patch to fix behaviour with glibc 2.32+. . [ Boyuan Yang ] * Bump Standards-Version to 4.6.0. . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Debian Janitor ] * Set upstream metadata fields: Repository, Repository-Browse. Checksums-Sha1: f254bae80b91eaf630b1f0fc0f808e67b916e2bc 2174 python-iptables_1.0.0-2.dsc
[Python-modules-team] Bug#994047: python3-jupyter-sphinx-theme: Switch to myst-parser instead of recommonmark
Source: jupyter-sphinx-theme Version: 0.0.6+ds1-10 Severity: wishlist X-Debbugs-Cc: eam...@yaerobi.com,team+pyt...@tracker.debian.org Dear Maintainer, python3-jupyter-sphinx-theme currently Build-Depends or Depends on python3-recommonmark from recommonmark. This project is deprecated and upstream recommend the use of and MyST [0][1] (see ITP: #993553). Please switch to MyST-Parse (when is Ready). [0] https://github.com/readthedocs/recommonmark [1] https://github.com/executablebooks/MyST-Parser Cheers Emmanuel ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
