Bug#1101983: zigpy-zigate: rebuild creates empty package

2025-04-04 Thread Edward Betts
I tried removing PYBUILD_AFTER_INSTALL from debian/rules and patching pyproject.toml, this works when I build with regular debuild, but fails using sbuild. Not figure out what is causing the sbuild failure yet. pyproject.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/

Bug#1098627: marked as pending in scriv

2025-03-23 Thread Edward Betts
On 2025-03-20 23:35, Colin Watson wrote: I noticed that this commit has been in git for nearly a month, and is tagged as debian/1.5.1-2, but hasn't been uploaded. Did something go wrong with your upload? Hi Colin, Thanks for your message. I've uploaded the package. Cheers, -- Edward.

Bug#1098627: marked as pending in scriv

2025-02-22 Thread Edward Betts
Control: tag -1 pending Hello, Bug #1098627 in scriv 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/scriv/-/commit/0478e033989480a1843197d

Bug#1064886: sqlite-utils: Fails with "ModuleNotFoundError"

2024-03-07 Thread Edward Betts
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 t

Bug#1053267: hickle: test_H5NodeFilterProxy fails with h5py 3.9.0: Unable to delete attribute (no write intent on file)

2023-10-02 Thread Edward Betts
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)

2023-10-01 Thread Edward Betts
Thanks for the patch. I've applied it and uploaded a new version of hickle. Cheers, Edward

Bug#972239: closing 972239

2020-11-07 Thread Edward Betts
close 972239 0.8.4-3 thanks

Bug#949750: closing 949750

2020-09-02 Thread Edward Betts
close 949750 0.6.3-2 thanks

Bug#915900: closing 915900

2018-12-15 Thread Edward Betts
close 915900 0.9.2-1 thanks

Bug#911856: closing 911856

2018-11-08 Thread Edward Betts
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

2017-08-16 Thread Edward Betts
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 characte

Bug#868680: Unicode data table needs updating for python 3.6

2017-08-14 Thread Edward Betts
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 c

Bug#755657: marked as pending

2016-05-31 Thread Edward Betts
0a42dd88eff4a181d0c675fd175884e8b95d65de Author: Edward Betts 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

Bug#818066: FTBFS: pep8 module is now in python-pep8 package

2016-03-13 Thread Edward Betts
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

Bug#818060: FTBFS: pep8 module is now in python-pep8 package

2016-03-13 Thread Edward Betts
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:

Bug#818057: FTBFS: pep8 module is now in python-pep8 package

2016-03-13 Thread Edward Betts
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

2016-02-02 Thread Edward Betts
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

Bug#802122: marked as pending

2015-10-26 Thread Edward Betts
6c7fa2f29d7af0ce3a555fe271b31dc9b51e2099 Author: Edward Betts 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

Bug#802066: marked as pending

2015-10-17 Thread Edward Betts
e8922f12b4de93a276dafa3ec4062aadcdfcce74 Author: Edward Betts 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

Bug#756895: Ugrade 1.13 -> 1.14 fails

2014-08-03 Thread Edward Betts
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?

2005-09-19 Thread Edward Betts
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]