Hi.

Getting back to this...

Some log of what I'm doing.

• First git fetch; git pull on all parts.

Started new envs to simplify rollback etc.

• activate the new 3.5 venv.

( I run the commands one at a time, but this is more compact in text form:)

cd git/mailman; python setup.py build; python setup.py install cd ../mailman-hyperkitty; python setup.py build; python setup.py install deactivate

activate 2.7 venv, then

cd ../mailmanclient; python setup.py build; python setup.py install cd ../django-mailman3; python setup.py build; python setup.py install cd ../postorius; python setup.py build; python setup.py install cd ../hyperkitty; python setup.py build; python setup.py install

So far no errors. Just warnings.

Backups:

• deployment directory (as user with rw in directory)
  ...

  tar -cvzf backup.tgz deployment_directory

• postgres databases (as user with postgres-priv)
  ...

  pg_dump maiman | gzip -9 > mailman.bak.gz pg_dump mailmanweb | gzip -9 > mailmanweb.bak.gz

Create new .wsgi-file based on mailman-suite (I used the kludge in the script to get the python path correct) Change apache2.conf to point to new venv and new wsgi-version Updated the mailman3wrapper.sh I use for init to start the service.

I could not get hyperkitty interface to run so I deactivated it and set mailman as index instead. It complains that a column is missing, but I cannot get the migrate script to run so I decided that I do not need the archiver as I currently don't use it. So I will have to get back to this and either remove the archiver completely or get it to run.

So the line with ^$ in urls.py now is

url(r'^$', RedirectView.as_view(url=reverse_lazy('list_index'))),

instead, and the line "hyperkitty," is commented in the django application list.

cheers. // David

On Tue, Aug 8, 2017 at 6:48 PM, Mark Sapiro <mark@msapiro.net> wrote:

On 08/08/2017 04:42 AM, David Krantz wrote:

...

What is the rekommended way to upgrade to the newest version? (newest _usable_ version, of course)? Is it docker-only with a migration from the current solution to a docker based? If so, any ideas or pointers on how to go about this?

You may find this wiki article helpful <https://wiki.list.org/x/17891998>.

I started with bundler on both this (lists.mailman3.org) and the mail.python.org installs, but have been updating from the heads of the various gitlab branches since very early on.

At the moment, these installations are somewhat ahead of the 3.1 release, but I am not updating as the latest core has dropped Python 3.4 support, and I haven't yet installed Python 3.5 or 3.6 on these (Ubuntu 14.04) servers. (I will probably install 3.6 from source at some point.)

Please feel free to ask here if you have more specific questions.

-- 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 https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/