diff options
| author | bwarsaw | 2000-09-27 20:06:01 +0000 |
|---|---|---|
| committer | bwarsaw | 2000-09-27 20:06:01 +0000 |
| commit | f7368649541ac522f32344d80734715ebc91384a (patch) | |
| tree | 69eea281627c2f59bdf8f3994f243c149177d4a6 | |
| parent | dc92b491038da118651d5ecdfbe9c5171b51305d (diff) | |
| download | mailman-f7368649541ac522f32344d80734715ebc91384a.tar.gz mailman-f7368649541ac522f32344d80734715ebc91384a.tar.zst mailman-f7368649541ac522f32344d80734715ebc91384a.zip | |
Added some recommendations about upgrading template files, and about
the need to re-run configure (running config.status isn't
sufficient).
| -rw-r--r-- | UPGRADING | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -27,8 +27,19 @@ UPGRADING FROM PREVIOUS VERSIONS Mailman URLs. Refer to your web server documentation for details. + Mailman will NOT upgrade the template files for existing lists. + Chuq Von Rospach gives some useful advice in this message to the + users mailing list: + + http://www.python.org/pipermail/mailman-users/2000-September/007523.html + UPGRADING FROM 2.0 beta to 2.0 final + You MUST re-run configure; running config.status is not sufficient + due to some recent changes in the autoconf scripts. You can do a + head of config.status if you don't remember the options you + originally ran configure with. + The cron jobs for Mailman 2.0 final have changed considerably, including the frequency with which they run. You should reload misc/crontab.in for the `mailman' user to get the right settings. |