[Twisted-Python] (Mis)indented Posts

Gerrat Rickert grickert at coldstorage.com
Mon Jul 27 14:53:56 EDT 2009

>-----Original Message-----
>From: twisted-python-bounces at twistedmatrix.com [mailto:twisted-python-
>bounces at twistedmatrix.com] On Behalf Of Gerrat Rickert
>Sent: Monday, July 27, 2009 10:54 AM
>To: Twisted general discussion
>Subject: Re: [Twisted-Python] (Mis)indented Posts
>>-----Original Message-----
>>From: twisted-python-bounces at twistedmatrix.com [mailto:twisted-python-
>>bounces at twistedmatrix.com] On Behalf Of Jean-Paul Calderone
>>Sent: Monday, July 27, 2009 9:07 AM
>>To: Twisted general discussion
>>Subject: Re: [Twisted-Python] (Mis)indented Posts
>>On Mon, 6 Jul 2009 08:46:39 -0400, Gerrat Rickert
>><grickert at coldstorage.com> wrote:
>>> [snip]
>>>>I really don't know how that could be specific to the twisted python
>>>>list. I notice in the referenced message, Mark Sapiro says that
>>>>rebuilding the archives from the mbox file generated correct
>>>>for him. Well, I just did that, ("mmarch --wipe twisted-python") and
>>>>it generated the same incorrect bad threading.
>>>>Perhaps it's a bug in mailman 2.1.9-9ubuntu1 which has been fixed
>>>>already upstream?
>>>Thanks for testing this James.  Before I send this back to the
>>>list, could you tell me, would that be a "stock" 2.1.9-9ubuntu1
>>>installation you rebuilt on?  ie. is there any custom configuration
>>>specific to this list that could be causing this odd behaviour
>>>of a bug with the ubuntu version)?  [please excuse my ignorance if
>>>question doesn't make sense - I know nothing about mailman...I just
>>>to stop hijacking threads when I post here]
>>I was reminded of this thread when I came across what appears to be
>>bug on the Tahoe list:
>>  http://allmydata.org/pipermail/tahoe-dev/2009-July/thread.html
>>Notice multiple posts in threads they don't look like they belong to,
>>well as many threads which have nonsensical levels of indentation.
>>I'm not sure if anyone ever answered your question about twisted-
>>mailman installation being "stock" or not.  If not, then I think I can
>>confirm that it is.  There is also no configuration that would alter
>>behavior, as far as I know.  We've probably set a few options via the
>>interface, but I don't think any of those should affect this behavior.
>Thanks for the reply, Jean-Paul (until now, nobody did answer my
>...I'll forward this back to the mailman list - maybe they can
>if it's an Ubuntu-specific issue.
>	Gerrat

...and now (finally), we get to the heart of the issue:
as explained by Mark Sapiro, on the mailman list:
>Ubuntu is based on Debian.
>I have just confirmed by testing that this problem is caused by the
Debian Mailman patch "30_pipermail_threads.patch".
>This patch can be found by following the links from
<http://patch-tracking.debian.net/package/mailman> (I don't want to give
a more specific URL >because the URLs below this level are unstable).
>Thus, the problem potentially exists in all Debian/Ubuntu Mailman
packages. The patch attempts to fix Debian bug  #167758
<http://bugs.debian.org/cgi->bin/bugreport.cgi?bug=167758>, and it may
do that, but it clearly breaks this.
>I'll try to report this to Debian.

Thanks all for your help - hopefully this will be resolved in the near


More information about the Twisted-Python mailing list