Updating from Ubuntu-20.04 LTE installation
Hi Mark,
thank you for the fast solution of our subscription problem - which brings me to the next step:
Our installation was done by "apt-get install" in Ubuntu 20, thus still running MM 3.2.2 (and python 3.8.2).
Do you have any advise, how to upgrade from there to your current version? I know this might be a bit dangerous, but with today's VMs the risk is much less than it used to be:
Do you think it would be possible, just to replace the code and library parts, keeping the database and config files as is?
If not, what would you do when you have to keep the system running (except for maintenance time, of course)?
Thank you again and and have a nice relaxed weekend
Peter
On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote:
Our installation was done by "apt-get install" in Ubuntu 20, thus still running MM 3.2.2 (and python 3.8.2).
Do you have any advise, how to upgrade from there to your current version? I know this might be a bit dangerous, but with today's VMs the risk is much less than it used to be:
It shouldn't be difficult, but I can't give you details because I don't know exactly how the Debian/Ubuntu package installs things. Also I don't know whether "current version" refers to the 3.3.1 release or the head of the https://gitlab.com/mailman/mailman master branch.
Do you think it would be possible, just to replace the code and library parts, keeping the database and config files as is?
Yes. It should be fairly straightforward. You first need to find where
the Mailman Core package is. You should be able to just replace the
contents of the mailman package directory with ours. You may be able
to do this via pip
pip install --upgrade mailman
globally or within Mailman's virtualenv if it is installed in a virtualenv.
However, there are caveats. There are Debian patches at
<https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big 0002
patch replaces importlib_resources with importlib.resources because
importlib_resources is not available in Debian. Most of the patches
apply to tests, and for the actual working code, we fixed this
differently as of Mailman 3.3.1, so I don't think you need the Debian
patches.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, May 23, 2020, at 8:28 PM, Mark Sapiro wrote:
On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote:
Our installation was done by "apt-get install" in Ubuntu 20, thus still running MM 3.2.2 (and python 3.8.2).
Do you have any advise, how to upgrade from there to your current version? I know this might be a bit dangerous, but with today's VMs the risk is much less than it used to be:
It shouldn't be difficult, but I can't give you details because I don't know exactly how the Debian/Ubuntu package installs things. Also I don't know whether "current version" refers to the 3.3.1 release or the head of the https://gitlab.com/mailman/mailman master branch.
Do you think it would be possible, just to replace the code and library parts, keeping the database and config files as is?
Yes. It should be fairly straightforward. You first need to find where the Mailman Core package is. You should be able to just replace the contents of the
mailmanpackage directory with ours. You may be able to do this via pippip install --upgrade mailman
globally or within Mailman's virtualenv if it is installed in a virtualenv.
This is probably not a good idea, global install quite often breaks a lot of stuff (Like I broke Yum on my work computer since I wanted something newer than 10yo python packages).
A better idea would be to install Mailman from scratch inside a virtualenv somewhere in /opt/mailman and then letting it consume the same configurations. I think Ubuntu/Debian have their configurations in /etc/mailman3/ and Mailman Core installed anywhere should just pick that up without any special work.
Same goes for Postorius/Django stuff. You can switch to a different Django project and just point to Debian/Ubuntu's settings.py (location of which should be in README.debian of the Debian package I presume).
However, there are caveats. There are Debian patches at <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big
0002patch replaces importlib_resources with importlib.resources because importlib_resources is not available in Debian. Most of the patches apply to tests, and for the actual working code, we fixed this differently as of Mailman 3.3.1, so I don't think you need the Debian patches.-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
participants (3)
-
Abhilash Raj -
Mark Sapiro -
Peter Adebahr