Re: [Mailman-Users] Upgrading from 2.0b5 to 2.1a2
[Note: I'm moving this discussion to malman-developers. -baw]
"JAA" == Jose A Accino jaccino@ieev.uma.es writes:
JAA> Is there any clean way to make a smooth upgrade from 2.0b5 to
JAA> lates 2.1a2? (I'm making that just to check the upgrade
JAA> process, using a spare machine and a copy of the actual
JAA> lists).
JAA> Making a 2.1a2 fresh installation (without lists) runs fine.
JAA> However, I've been unable to upgrade the old lists. Here are
JAA> the main points:
There's two ways to upgrade, neither of which has gotten a lot of testing. Based on you're message I tried the first way, and I'm about to check in a bunch of patches to make that go smoother. I'll try the second way soon.
Install a fresh virgin MM2.1 in /usr/local/mailman and then move lists from /home/mailman (MM2.0.x) to /usr/local/mailman. This way lets you migrate lists one at a time, gaining confidence in the new system in measured increments. I will probably upgrade {python,zope}.org this way.
Install MM2.1 overtop an existing MM2.0.x installation and have everything just magically work. I'll probably upgrade wooz.org's production lists this way.
Both ought to work, and ought to be easy. After the checkins, here's a recipe that makes #1 easy:
Do a fresh install of MM2.1 in /usr/local/mailman according to the instructions.
Copy or move `mylist' by first moving /home/mailman/lists/mylist to /usr/local/mailman/lists/mylist and /home/mailman/archives/private/mylist.mbox to /usr/local/mailman/archives/private
BTW, I used rsync for this, just cause it's a cool tool and I can actually remember how to invoke it with the right options. :)
That's it. Everything else should just work, except for possibly two minor complications.
If your web server is going to support both installations, it's possible you'll have two different base urls, one for your MM2.0.x installation and one for your MM2.1 installation. If so, you'll need to manually change each moved list's web_page_url attribute.
Fortunately, I'm about to add a script called `fix_url' which will reset a list's web_page_url to mm_cfg.DEFAULT_URL. So if you configure mm_cfg.py correctly, then run fix_url, you should be golden. I.e.
% bin/withlist -l -r fix_url mylist
Same dealie with your MTA, i.e. your wrapper aliases may point to two different directories. Here, because I use Postfix and glued them together as described in README.POSTFIX, all I needed to do was run bin/genaliases and the new list aliases got installed.
I'm sure that if you use Exim and glued them together as per README.EXIM, you probably don't need to do anything. (I'm still waiting on contributions for better gluing instructions for Sendmail, qmail, and any others.)
-Barry
barry@zope.com (Barry A. Warsaw) writes:
There's two ways to upgrade, neither of which has gotten a lot of testing.
Well, I had actually used the 'hard' way (not actually an upgrade at all), installing a fresh MM2.1.a2, editing mm_cfg.py for defaults and re-creating the lists (not a lot, fortunately), and re-importing users again (BTW: I first used sync_members but it gave me the 'ValueError: unsupported format character '(' (0x28) at index 12' that I reported on another msg.).
AFAIK, it seems to be running (almost) fine. Well, currently I have only found:
A problem on Spanish catalog (J.C. Rey kindly solved it on a snap)
The 'ImportError: No module named mimelib.address' related to cron tasks.
I removed the -s on MM's crontab and didn't got more errors.
- One 'mimelib.Errors.BoundaryError: Couldn't find terminating boundary'
in Parser.Py (only got it once so I'm not sure about what does it mean...)
Regards,
JA.
At 10:47 AM 7/26/01 +0200, Jose A. Accino wrote:
- The 'ImportError: No module named mimelib.address' related to cron tasks.
I removed the -s on MM's crontab and didn't got more errors.
- One 'mimelib.Errors.BoundaryError: Couldn't find terminating boundary'
in Parser.Py (only got it once so I'm not sure about what does it mean...)
Did you install mimelib-0.4 before running mailman? It's not part of the mailman kit.
- The 'ImportError: No module named mimelib.address' related to cron tasks.
I removed the -s on MM's crontab and didn't got more errors.
- One 'mimelib.Errors.BoundaryError: Couldn't find terminating boundary'
in Parser.Py (only got it once so I'm not sure about what does it mean...)
Did you install mimelib-0.4 before running mailman? It's not part of the mailman kit.
Yes, of course. The Python mimelib.__version__ test returns the '0.4' version number.
From the msgs I've found at the archives about cron jobs problem, it seems
that it's related to sys.path. I remember having read also something about the boundaries problem. I'm not sure if they are actually solved in latest CVS snapshot, however...
JA.
On Thu, Jul 26, 2001 at 10:47:36AM +0200, Jose A. Accino wrote:
- The 'ImportError: No module named mimelib.address' related to cron tasks.
I removed the -s on MM's crontab and didn't got more errors.
Was this with a recent CVS Snapshot ? I checked in some changes that should permanently fix all these problems, and Barry checked in some changes before that that made the most glaring problems go away by not starting qrunner from cron anymore.
"TW" == Thomas Wouters thomas@xs4all.net writes:
TW> Was this with a recent CVS Snapshot ? I checked in some
TW> changes that should permanently fix all these problems, and
TW> Barry checked in some changes before that that made the most
TW> glaring problems go away by not starting qrunner from cron
TW> anymore.
Also, alpha 3 should have all those changes...
участники (4)
-
barry＠zope.com -
Jose A. Accino -
Ron Jarrell -
Thomas Wouters