Bug#1064886: sqlite-utils: Fails with "ModuleNotFoundError"
Hi Sebastian, The click_default_group module is in the python3-click-default-group package, sqlite-utils depends on python3-click-default-group. Do you have python3-click-default-group installed? The module will be installed as /usr/lib/python3/dist-packages/click_default_group.py Do you have this file on your system? Cheers, -- Edward
Bug#1053267: hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no write intent on file)
Thanks for the updated patch. I've uploaded a new version of hickle with it.
Bug#1053267: hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no write intent on file)
Thanks for the patch. I've applied it and uploaded a new version of hickle. Cheers, Edward
Bug#972239: closing 972239
close 972239 0.8.4-3 thanks
Bug#949750: closing 949750
close 949750 0.6.3-2 thanks
Bug#915900: closing 915900
close 915900 0.9.2-1 thanks
Bug#911856: closing 911856
close 911856 1.10.2-1 thanks FTBFS was fix by adjusting the pybuild call.
Bug#868680: Unicode data table needs updating for python 3.6
The kitchen.text.display module contains code for measuring the width of unicode characters. When the unicode character standard is updated there are new characters introduced that need to be considered by this algorithm. Sometime a new version of python includes an updated list of unicode characters and their width. The failing test is warning us that the list of character sizes in the kitchen module is out of date. As it stands the module will work exactly the same with python 3.5 or 3.6 The results will be more actuate once the table of unicode characters is updated to match the list included with python 3.6 -- Edward.
Bug#868680: Unicode data table needs updating for python 3.6
The file kitchen/text/display.py needs updating because the unicodedata in python 3.6 has changed. This is causing the test failure. The module includes a function to update the data table, but if this change is made then the test suite will fail when run with python 3.5 The test suite should be changed so the failing test is skipped on python 3.6 Upstream will make a new release at some point that is updated for python 3.6, then the test can be changed to skip on python 3.5
Bug#755657: marked as pending
tag 755657 pending thanks Hello, Bug #755657 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/python-model-mommy.git;a=commitdiff;h=0a42dd8 --- commit 0a42dd88eff4a181d0c675fd175884e8b95d65de Author: Edward Betts <edw...@4angle.com> Date: Tue May 31 09:31:58 2016 +0100 New upstream release. diff --git a/debian/changelog b/debian/changelog index 7cda1ed..41c283b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,16 @@ -python-model-mommy (1.2-2) UNRELEASED; urgency=medium +python-model-mommy (1.2.6-1) unstable; urgency=medium + [ Edward Betts ] + * New upstream release. (Closes: #745093, #755657, #814781) + * Build Python 3 package. + * Fix lintian warning: dep5-copyright-license-name-not-unique + * Update Standards-Version to 3.9.8 (no changes) + * Update to debhelper 9 + + [ Ondřej Nový ] * Fixed VCS URL (https) - -- Ondřej Nový <n...@ondrej.org> Tue, 29 Mar 2016 22:11:14 +0200 + -- Edward Betts <edw...@4angle.com> Tue, 31 May 2016 07:32:57 +0100 python-model-mommy (1.2-1) unstable; urgency=low
Bug#818066: FTBFS: pep8 module is now in python-pep8 package
Source: nwdiag Version: 1.0.3-4 Severity: serious Justification: fails to build from source Building the package fails in the test suite because the pep8 module is now in the python-pep8 package. The Build-Depends for this package need to be updated. Here is the failing part of the build. dh_auto_test -O--buildsystem=pybuild I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose .SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSSE..SSS.SSS.SSS.SSS.SSS.SSS.SSSE.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSSE == ERROR: Failure: ImportError (No module named pep8) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in loadTestsFromName addr.filename, addr.module) File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/<>/.pybuild/pythonX.Y_2.7/build/nwdiag/tests/test_pep8.py", line 6, in import pep8 ImportError: No module named pep8 == ERROR: Failure: ImportError (No module named pep8) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in loadTestsFromName addr.filename, addr.module) File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/<>/.pybuild/pythonX.Y_2.7/build/packetdiag/tests/test_pep8.py", line 6, in import pep8 ImportError: No module named pep8 == ERROR: Failure: ImportError (No module named pep8) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in loadTestsFromName addr.filename, addr.module) File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/<>/.pybuild/pythonX.Y_2.7/build/rackdiag/tests/test_pep8.py", line 6, in import pep8 ImportError: No module named pep8 -- Ran 312 tests in 3.979s FAILED (SKIP=120, errors=3)
Bug#818060: FTBFS: pep8 module is now in python-pep8 package
Source: shortuuid Version: 0.4.3-1 Severity: serious Justification: fails to build from source Building the package fails in the test suite because the pep8 module is now in the python-pep8 package. The Build-Depends for this package need to be updated. Here is the failing part of the build: debian/rules override_dh_auto_test make[1]: Entering directory '/<>' set -e ; \ python2.7 build2.7/lib.*-2.7/shortuuid/tests.py Traceback (most recent call last): File "build2.7/lib.linux-x86_64-2.7/shortuuid/tests.py", line 5, in import pep8 ImportError: No module named pep8 debian/rules:16: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' debian/rules:7: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Edward.
Bug#818057: FTBFS: pep8 module is now in python-pep8 package
Source: actdiag Version: 0.5.3-5 Severity: serious The pep8 module is now in python-pep8 package, so the Build-Depends for this package needs to be updated. -- Edward.
Bug#802101: Contextify has been merged into Node, this module is no longer required
https://github.com/brianmcd/contextify/blob/master/README.md says: > As of Node 0.12, Contextify has been merged into Node (thanks to @domenic), > replacing the native vm module. The code has been improved on since then, so > if at all possible, you should use a newer Node and the native vm module. This package is no longer required and should removed from Debian. -- Edward.
Bug#802122: marked as pending
tag 802122 pending thanks Hello, Bug #802122 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/python-tzlocal.git;a=commitdiff;h=6c7fa2f --- commit 6c7fa2f29d7af0ce3a555fe271b31dc9b51e2099 Author: Edward Betts <edw...@4angle.com> Date: Mon Oct 26 11:31:10 2015 + unset TZ during build, so tests don't fail diff --git a/debian/changelog b/debian/changelog index abe7bd3..6a9f824 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +python-tzlocal (1.2-2) unstable; urgency=medium + + * debian/rules: unset TZ, so tests don't fail (Closes: #802122) + + -- Edward Betts <edw...@debian.org> Sun, 25 Oct 2015 08:45:30 + + python-tzlocal (1.2-1) unstable; urgency=low * Initial release. (Closes: #797503)
Bug#802066: marked as pending
tag 802066 pending thanks Hello, Bug #802066 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/django-jinja.git;a=commitdiff;h=e8922f1 --- commit e8922f12b4de93a276dafa3ec4062aadcdfcce74 Author: Edward Betts <edw...@4angle.com> Date: Sat Oct 17 14:08:30 2015 +0100 Ready for release. diff --git a/debian/changelog b/debian/changelog index 37c10fe..ec77dcb 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -django-jinja (1.4.1-2) UNRELEASED; urgency=medium +django-jinja (1.4.1-2) unstable; urgency=medium * Update Vcs-* control headers. * Remove unused Build-Depends. @@ -7,7 +7,7 @@ django-jinja (1.4.1-2) UNRELEASED; urgency=medium upstream git repository but it isn't included in the release tarball. The Python 3.5 unittest modules tries to load the module even if there is not test suite. This fails because the module isn't designed to be run outside -django. Disable dh_auto_test. (Closes: #801932) +django. Disable dh_auto_test. (Closes: #801932, #802066) -- Edward Betts <edw...@4angle.com> Fri, 16 Oct 2015 18:07:50 +0100
Bug#756895: Ugrade 1.13 - 1.14 fails
The subject says 1.13 - 1.14, but 1.14 isn't in Debian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#328802: very old package, should this be removed?
I agree the package should be removed. -- Edward Betts [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
