Bug#497703: HappyDoc copyright status clarification

2008-09-08 Thread Chris Lamb
Hi Doug, Firstly, thanks for you quick responses. > Since I don't support it any more, and it does not work with some > language constructs from the newer versions of Python, I'm not sure > you want to include it any longer. I'll leave it up to you whether or > not to pull it out of your r

Bug#497703: HappyDoc copyright status clarification

2008-09-08 Thread Doug Hellmann
On Sep 8, 2008, at 3:42 PM, Chris Lamb wrote: Hi Doug, Hi, I understand you are the upstream maintainer of HappyDoc. Yes, that's right. This bug is marked "release critical", meaning that the package is not releasable in this state and will not ship with the upcoming Lenny release.

Bug#497703: HappyDoc copyright status clarification

2008-09-08 Thread Doug Hellmann
On Sep 8, 2008, at 4:21 PM, Doug Hellmann wrote: The source for HappyDoc is available under a BSD license. After reading the ticket, though, I see that at least one of the files referenced was not original source from me. The StructuredText package was released by Zope, Corp. and may h

Bug#497703: HappyDoc copyright status clarification

2008-09-08 Thread Chris Lamb
Hi Doug, I understand you are the upstream maintainer of HappyDoc. In the Debian system, there is an outstanding issue with the HappyDoc package where some of the files distributed in the python-happydoc package refer to licences that are missing from the tarball. You can read the entire details