Candidate Mailman 2.0.13 patch
As some of you have noticed, Mailman 2.0.12 has some compatibility problems with Python 1.5.2. In order to correct this, and a few other minor problems, I want to soon release a version 2.0.13. This time, however I'd like to enlist your help. ;)
I have uploaded a candidate patch for 2.0.12 -> 2.0.13 at this url:
http://sf.net/tracker/index.php?func=detail&aid=585643&group_id=103&atid=300103
I would appreciate it if someone (or a few someones) could give this patch a try. I'm essentially running it on python.org/zope.org, however I'm using Python 2.1.3 in my production environment. I have done some limited testing with Python 1.5.2 and this patch and it seems to go okay.
I'd especially like to hear from those of you experiencing problems with MailCommandHandler, if you are running MM2.0.12 with Python 1.5.2. Does this patch fix things for you? Does it produce any other tracebacks or warnings in logs/error?
Thanks for any feedback you can provide. If I get some positive feedback (or at least, no negative feedback) in a few days, I'd do a formal release. I expect that to be largely similar to this patch, with perhaps some documentation updates, unless other problems are uncovered by your testing.
Thanks! -Barry
On Wed, 24 Jul 2002, Barry A. Warsaw wrote:
As some of you have noticed, Mailman 2.0.12 has some compatibility problems with Python 1.5.2. [...] I'd especially like to hear from those of you experiencing problems with MailCommandHandler, if you are running MM2.0.12 with Python 1.5.2. Does this patch fix things for you? Does it produce any other tracebacks or warnings in logs/error?
Hi!
I am running Mailman 2.0.12 with Python 1.5.2 on a linux box, and had problems with torequests.. with this candidate patch they seem to be fixed, as all messages in the queue have now been processed and the queue is clear :-)
Thanks for the good work you've been doing all this time :-) Best regards, Sot.
"ST" == Sotiris Tsimbonis <stsimb@irc.gr> writes:
ST> I am running Mailman 2.0.12 with Python 1.5.2 on a linux box,
ST> and had problems with torequests.. with this candidate patch
ST> they seem to be fixed, as all messages in the queue have now
ST> been processed and the queue is clear :-)Excellent! Thanks for the feedback.
ST> Thanks for the good work you've been doing all this time :-)You're very welcome! -Barry
Barry,
As I'm running Mailman 2.0.12 on RedHat 6.2, therefore with Python 1.5.2 from the RPM in the original install, and since I've had the problem twice now, I went right for it.
After realizing that I couldn't paste the text into a Pico window (the longest lines broke, giving patch errors) I got it patched, configured, and installed without error. I sent a message to my test list and got instant response, with no addition to the error log. However, since I tried each message one at a time this morning, there hadn't been an error logged since. At least here it's only new subscriber confirmations that seem to break things.
I subscribed one of my addresses to a list that requires the confirmation, received the confirmation request, replied to it, and was welcomed - so I guess the thing is currently working.
Now I'm counting on you to release this patch so that the 2.0.13 to 2.0.14 patch will work on my machine, or perhaps document some way I can remove this patch before installing the real patch to 2.0.13 when the time comes.
Van
"Barry A. Warsaw" wrote:
As some of you have noticed, Mailman 2.0.12 has some compatibility problems with Python 1.5.2. In order to correct this, and a few other minor problems, I want to soon release a version 2.0.13. This time, however I'd like to enlist your help. ;)
I have uploaded a candidate patch for 2.0.12 -> 2.0.13 at this url:
http://sf.net/tracker/index.php?func=detail&aid=585643&group_id=103&atid=300103
I would appreciate it if someone (or a few someones) could give this patch a try. I'm essentially running it on python.org/zope.org, however I'm using Python 2.1.3 in my production environment. I have done some limited testing with Python 1.5.2 and this patch and it seems to go okay.
I'd especially like to hear from those of you experiencing problems with MailCommandHandler, if you are running MM2.0.12 with Python 1.5.2. Does this patch fix things for you? Does it produce any other tracebacks or warnings in logs/error?
Thanks for any feedback you can provide. If I get some positive feedback (or at least, no negative feedback) in a few days, I'd do a formal release. I expect that to be largely similar to this patch, with perhaps some documentation updates, unless other problems are uncovered by your testing.
Thanks! -Barry
Mailman-announce mailing list Mailman-announce@python.org http://mail.python.org/mailman/listinfo/mailman-announce
--
Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted@whidbey.com?subject=Subscribe_QOTD
For web hosting and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/
Glad it's working for you now.
"GAVH" == G Armour Van Horn <vanhorn@whidbey.com> writes:
GAVH> Now I'm counting on you to release this patch so that the
GAVH> 2.0.13 to 2.0.14 patch will work on my machine, or perhaps
GAVH> document some way I can remove this patch before installing
GAVH> the real patch to 2.0.13 when the time comes.When the official 2.0.13 patch is released (let's hope there will be no 2.0.14 <wink>) and you go to apply it with the patch program, you will get warnings that some chunks are already applied. You'll be asked if you want to undo the patch... just answer "no". Patch will leave you with some .rej files which you can ignore.
Alternatively, if you haven't customized your system, you can of course just download the full 2.0.13 release tarball, run configure with exactly the same options, and install the new version right overtop the old version.
-Barry
participants (4)
-
barry＠python.org -
barry＠zope.com -
G. Armour Van Horn -
Sotiris Tsimbonis