Hello!
Over the weekend, I attempted to install the Mailman Suite on Debian Stretch. My goal is to set up some low volume mailing lists for family and friends. I ran into some problems, and I'm hoping to get some feedback on my overall approach before I make my second attempt. :-)
I figured the safest thing to do would be to use pip to install the latest released version of all the components (core, postorius, hyperkitty, etc.). I copied the files from the mailman-suite repository to set up a Django project and got it mostly working with Apache and mod_wsgi.
Unfortunately, I was unable to log into the web interface; when I tried, I got a server error like this:
Exception Type: TypeError at /accounts/login/ Exception Value: authenticate() takes exactly 0 arguments (3 given)
Some research leads me to believe this is happening because authenticate() was changed in Django 1.10, and so I must be using a newer version of Django than the app expects.
Given that I installed via Pip, I assumed the right version of Django would automatically be installed... I'm open to the possibility that I am misunderstanding how Pip works, or that postorius's and/or hyperkitty's dependency information is incorrect.
The two alternatives I am weighing right now are:
Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration.
Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.)
Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python.
Which is the least crazy option?
-- Ben
On 04/09/2018 10:01 AM, Benjamin Ragheb wrote:
The two alternatives I am weighing right now are:
Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration.
Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.)
Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python.
Which is the least crazy option?
If you are comfortable with 2), I think that's the better option. After PyCon in May when we release 3.2 and the rest of the suite, you should be able to install everything with pip and have it work. I'm not sure what the issues are now with a pip install.
There is a 3rd option. See <https://packages.debian.org/stretch-backports/mailman3-full>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, Apr 10, 2018, at 12:14 AM, Mark Sapiro wrote:
If you are comfortable with 2), I think that's the better option. After PyCon in May when we release 3.2 and the rest of the suite, you should be able to install everything with pip and have it work. I'm not sure what the issues are now with a pip install.
Thanks, Mark. It wasn't clear to me by poking around how stable/unstable the master branches were, but if you think they should be stable enough for a hobby server, that's good enough for me.
If I get things working and I'm feeling bold enough to contribute back to the documentation, are there guidelines? The Contributor Guide covers the technical stuff... should I just submit a merge request in GitLab?
-- Ben
participants (2)
-
Benjamin Ragheb -
Mark Sapiro