[Mailman-Users] Proceeding with caution - Upgrading mailman using rpm via yum

[Brad Knowles]

At 7:08 AM -0400 10/11/06, Joyce, Wesley K. wrote:

>  Greetings, what action should I take pre and post upgrading
>  mailman from 2.1.5.35 to 2.1.8 using YUM?

First off, we have only three-digit version numbers.  So, 2.1.5.35 is 
not one of our versions, and we have no idea what may have been done 
to this code.

Secondly, we are not the people who created your binary package 
management system, so we have no idea how this system may interact 
badly with our software, or in what weird ways things may fail.


These kinds of questions should be asked of those people who 
developed your binary package management system -- at least so far as 
it pertains to whatever they may have done to our code.

>                                             What specifically
>  should I back up, and do I need to edit or run any commands
>  after the upgrade.  I am nervous about doing this upgrade,
>  cause it would really hurt if mailman got broken.

Again, we didn't create those versions, so we don't know precisely 
what to tell you to backup.  If you had used our canonical source 
version, then I'd tell you to back up all of /usr/local/mailman, and 
that would get all Mailman configuration files, all the list 
archives, all the stuff currently sitting in one of the queue 
directories, etc....

But your binary packaged version probably stores stuff in different 
places, so you'd want to find out what those are and then back them 
up.

-- 
Brad Knowles, <brad at stop.mail-abuse.org>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

     -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
     Assembly to the Governor, November 11, 1755

  Founding Individual Sponsor of LOPSA.  See <http://www.lopsa.org/>.