Upgradeability of 2.1.* releases?
Hello,
Where could I find how smooth is the upgrade between different 2.1.* releases? Are there any tools for the conversion of the configuration, if it is not completely automagical?
I work for SUSE and we have 2.1.14 on SLE 11, but for https://bugs.launchpad.net/mailman/+bug/775294 it seems the only redress is upgrade to the latest release, right?
Meanwhile, because of CVE-2016-6893 we will probably upgrade to 2.1.15, but from that to 2.1.26 is still a long way to go.
Any advice?
Thank you,
Matěj Cepl
-- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
Thou shalt not nede to be afrayed for any bugges by night. -- Coverdale's 1535 translation of Psalm 91 (or Christopher Higley's 1972 thesis explaining why programmers' are nocturnal beasts)
On 6/6/2018 7:54 AM, Matěj Cepl wrote:
Where could I find how smooth is the upgrade between different 2.1.* releases? Are there any tools for the conversion of the configuration, if it is not completely automagical?
Generally, if you're upgrading via source (instead of some distro's package), going from 2.1.x to current is automagic. Most of the problems seem to be with packages, which may have been customized for different file locations.
See- https://wiki.list.org/DOC/4.80%20How%20do%20I%20upgrade%20from%20Mailman%202...
If you're back at 2.1.15, I'd definitely update.
Later,
z!
On 06/06/2018 07:54 AM, Matěj Cepl wrote:
Hello,
Where could I find how smooth is the upgrade between different 2.1.* releases? Are there any tools for the conversion of the configuration, if it is not completely automagical?
You could read the UPGRADING document in the source distribution.
To upgrade any 2.1.5+ release to the latest release is very straightforward except 2.1.18+ requires that you have the Python dnspython package. This is discussed in the "UPGRADING FROM 2.1.5+ to 2.1.18+" section of the UPGRADING document.
When 'make install' detects a version change, it runs Mailman/versions.py which does any necessary conversions.
Any advice?
Just do it. Unpack the current Mailman 2.1.26 release (or wait for 2.1.27 which is coming soon, or grab the branch from <https://code.launchpad.net/~mailman-coders/mailman/2.1> which is what's running on the @python.org lists), run 'configure' with the same options as you used on the current install and then 'make install'.
Also note that every time a list is instantiated, its data_version is checked against that of the installation and if it is older, it is automatically upgraded.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Carl Zwanzig -
Mark Sapiro -
Matěj Cepl