James Y Knight wrote:
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.
Just to set the record straight: I did not say that "twisted had to have a release that fixes it before debian could"; I said that doing so would "put the ball in their court" (i.e., give debian no excuse not to include the patched release), and that that (a patch release) would have been in twisted's interest, since the problem was small but annoying and just made twisted look bad. By this time it is moot, of course, and I've already said too much, but I hate being misrepresented. Bleah. Steve