[Mailman-Users] Why Not Upgrade to 2.1.8?
> Our Mailman was recently upgraded to 2.1.5. I have seen many posts on this list from people who are running 2.1.5 (or earlier). I am wondering why someone would recently upgrade to 2.1.5 instead of to 2.1.8, which is the current release? -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Why Not Upgrade to 2.1.8?
At 09:18 AM 8/25/2006, Barry Finkel wrote: >I have seen many posts on this list from people who are running >2.1.5 (or earlier). I am wondering why someone would recently >upgrade to 2.1.5 instead of to 2.1.8, which is the current release? Barry, I know one reason we don't upgrade every time one comes out is we want to be sure everything is stable. I'm sure it is, but sometimes people talk about a feature not working right in a release and we think we know everything's working properly in the one we have, so why upgrade. Also, we usually hire someone to come in and help us with upgrades like this. If the upgrade process were really cut and dried, and there was virtually no possibility that something weird could happen, then maybe us non-guru folks would attempt it. Is there a document explaining the upgrade process, and is it considered a pretty simple thing to do? Allan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Why Not Upgrade to 2.1.8?
Barry Finkel wrote: > > Our Mailman was recently upgraded to 2.1.5. > >I have seen many posts on this list from people who are running 2.1.5 >(or earlier). I am wondering why someone would recently upgrade to >2.1.5 instead of to 2.1.8, which is the current release? End original message. - I suspect a lot of these people are using an RHEL distribution and the RPM they supply which is usually a version or three behind the latest. As easy as mailman is to install from source, I can't really see a reason to use the RPM other than to remain compliant with Redhat's way of doing things. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Why Not Upgrade to 2.1.8?
Allan Trick wrote: >At 09:18 AM 8/25/2006, Barry Finkel wrote: > > >I have seen many posts on this list from people who are running > >2.1.5 (or earlier). I am wondering why someone would recently > >upgrade to 2.1.5 instead of to 2.1.8, which is the current release? > >Barry, > >I know one reason we don't upgrade every time one comes out is we >want to be sure everything is stable. I'm sure it is, but sometimes >people talk about a feature not working right in a release and we >think we know everything's working properly in the one we have, so >why upgrade. Security for one. Much of the impetus for releasing later versions in the 2.1.X branch was for that reason. See http://www.gnu.org/software/mailman/security.html for some more info on that. The release notes for each release also explain any other changes. >Also, we usually hire someone to come in and help us with upgrades >like this. If the upgrade process were really cut and dried, and >there was virtually no possibility that something weird could happen, >then maybe us non-guru folks would attempt it. Is there a document >explaining the upgrade process, and is it considered a pretty simple >thing to do? The process is described in the UPGRADING file that is part of the source for each release. I found it pretty simple. It basically comes down to a few simple steps as long as you have a version of Python that is recent enough for the package. If you are already running 2.1.5 then that is covered for installing 2.1.8. 1. Download the tarball. 2. Extract the files from the tarball. 3. Run configure (you may need to change a few options there to get it to set things up properly, mainly to do with what group your MTA and web server execute under and what owner/group mailman execute as). 4. Run make 5. Stop mailman and your MTA while doing the install. (Use bin/mailmanctl stop to shutdown mailman). 6. Run make install 7. Start your MTA and mailman ( bin/mailmanctl start. The only thing I can see that may complicate things is if you used an RPM or other package to install that does not use the standard file locations for mailman. If everything goes well, it is literally less than 30 minutes to do all of this and you only have to keep mailman and your MTA off line for maybe 5 or 10 minutes. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Why Not Upgrade to 2.1.8?
On 8/25/06 8:07 AM, "Dragon" <[EMAIL PROTECTED]> wrote: > Security for one. Much of the impetus for releasing later versions in > the 2.1.X branch was for that reason. I don't know what, if anything, RedHat is doing about backporting the security changes. For things in general, they are pretty good about backporting upstream security fixes. Some, at least, of the ones present in 2.1.8 may be present in RedHat's current 2.1.5. Or not, of course. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
