14 Nov
2006
14 Nov
'06
3:41 p.m.
On Nov 14, 2006, at 9:56 AM, Stephen Waterbury wrote:
Yes, it has been fixed in trunk, but has there been a maintenance release in the Twisted release series that had the problem? If so, then the ball is in the debian package maintainers' court; if not, it's still in Twisted's.
I agree it might have been nice to have a maintenance release, but the problem apparently doesn't affect anybody but Debian. They're allowed to (and are capable enough to) apply patches to fix debian packaging issues in upstream source. So saying that twisted *has* to have a release that fixes it before debian can is a bit wrong. But a 2.5 release is coming soon now, so, it'll be fixed then. James