problems installing mailman3 under gentoo and upgrading mailman2 to mailman3
Hi. I am having a great deal of difficulty installing mailman3 using gentoo and sendmail. Also, I want to upgrade my old mailman2 data to mailman3.
What I have done so far is to install the mailman3 packages from my repository and got this: django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman version 3.3.2 (apparently the core), postorius version 1.3.3 and hyperkitty version 1.3.3. I also have mariadb and postgresql already installed.
Now trying to read your documentation, it seems it wants me to reinstall some packages using pip in the home directory of the mailman user in a python virtual environment, that was the first thing. But I would like to avoid multiple package managers wherever possible -- gentoo is already a lot of maintainance without dealing with pip's maintainance. The binaries also seem to be different from my gentoo packages.
So, how do I proceed with getting mailman3 up and working, configuring the database, configs, etc and I guess after doing that upgrading mailman2 and getting sendmail to interface properly with mailman3?
Thanks in advance for any suggestions.
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.com
On 3/12/21 7:36 PM, John Covici wrote:
Hi. I am having a great deal of difficulty installing mailman3 using gentoo and sendmail. Also, I want to upgrade my old mailman2 data to mailman3.
What I have done so far is to install the mailman3 packages from my repository and got this: django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman version 3.3.2 (apparently the core), postorius version 1.3.3 and hyperkitty version 1.3.3. I also have mariadb and postgresql already installed.
Are these gentoo packages? If so, I have no idea how they are configured.
Now trying to read your documentation, it seems it wants me to reinstall some packages using pip in the home directory of the mailman user in a python virtual environment, that was the first thing. But I would like to avoid multiple package managers wherever possible -- gentoo is already a lot of maintainance without dealing with pip's maintainance. The binaries also seem to be different from my gentoo packages.
Our documantation generally covers installing from source. If you are installing gentoo packages, you should be looking at gentoo docs and going to gentoo for help.
We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB.
So, how do I proceed with getting mailman3 up and working, configuring the database, configs, etc and I guess after doing that upgrading mailman2 and getting sendmail to interface properly with mailman3?
Importing lists from Mailman 2 is done with the mailman import21
command. See
<https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/docs/import.html>.
Importing archives is done with the Django management
hyperkitty_import command. See
<https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#importing-the-current-archives>
For sendmail, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.html#sendmail>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I don't think this reply got to the mailing list, so I am sending it again, sorry if its a duplicate. On Sat, 13 Mar 2021 00:33:58 -0500, Mark Sapiro wrote:
On 3/12/21 7:36 PM, John Covici wrote:
Hi. I am having a great deal of difficulty installing mailman3 using gentoo and sendmail. Also, I want to upgrade my old mailman2 data to mailman3.
What I have done so far is to install the mailman3 packages from my repository and got this: django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman version 3.3.2 (apparently the core), postorius version 1.3.3 and hyperkitty version 1.3.3. I also have mariadb and postgresql already installed.
Are these gentoo packages? If so, I have no idea how they are configured.
Anyway I can tell, there was no configuration (we call them use flags) they just seemed to install the files in what seems to be the correct places.
Now trying to read your documentation, it seems it wants me to reinstall some packages using pip in the home directory of the mailman user in a python virtual environment, that was the first thing. But I would like to avoid multiple package managers wherever possible -- gentoo is already a lot of maintainance without dealing with pip's maintainance. The binaries also seem to be different from my gentoo packages.
Our documantation generally covers installing from source. If you are installing gentoo packages, you should be looking at gentoo docs and going to gentoo for help.
We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB.
I sort of am installing from source, gentoo installs from source. No one on the gentoo users mailing list seems to be able to help me, except to tell me to use a different mailing list mechanism called mlmmj.
So, how do I proceed with getting mailman3 up and working, configuring the database, configs, etc and I guess after doing that upgrading mailman2 and getting sendmail to interface properly with mailman3?
Importing lists from Mailman 2 is done with the
mailman import21command. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/docs/import.html>. Importing archives is done with the Django managementhyperkitty_importcommand. See <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#importing-the-current-archives>For sendmail, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.html#sendmail>
Thanks.
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.com-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.com
On 13/3/21 8:53, John Covici wrote:
We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB.
I sort of am installing from source, gentoo installs from source. No one on the gentoo users mailing list seems to be able to help me, except to tell me to use a different mailing list mechanism called mlmmj.
From the perspective of someone who was in the same place (but installing in a FreeBSD S.O.), I would recommend you to follow the "virtualenv" guide but without executing the "env" commands. It will produce a system wide mailman3 installation but it will work (as it is for me since a few moths ago)
I writed down a step by step path of my installation and it could be of your interest (maybe you have to locate and install some packages by different name, but I think it will be not much difference). It could provide you a overall view of all the processes implied.
I'ts here: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128
On Sat, 13 Mar 2021 03:25:41 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 13/3/21 8:53, John Covici wrote:
We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB.
I sort of am installing from source, gentoo installs from source. No one on the gentoo users mailing list seems to be able to help me, except to tell me to use a different mailing list mechanism called mlmmj.
From the perspective of someone who was in the same place (but installing in a FreeBSD S.O.), I would recommend you to follow the "virtualenv" guide but without executing the "env" commands. It will produce a system wide mailman3 installation but it will work (as it is for me since a few moths ago)
I writed down a step by step path of my installation and it could be of your interest (maybe you have to locate and install some packages by different name, but I think it will be not much difference). It could provide you a overall view of all the processes implied.
I'ts here: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128
Thanks, by the env commands you mean the creation and activation commands? I will certainly look at your thread.
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.com
Hi.
Am 13.03.21 um 04:36 schrieb John Covici:
Hi. I am having a great deal of difficulty installing mailman3 using gentoo and sendmail.
Mailman in gentoo is kind of maintainerless (will be in a few days, I suppose) and so this method can not be recommended.
We installed using pip in a regular useraccount.
regards, Bernd
On 13/3/21 9:44, John Covici wrote:
On Sat, 13 Mar 2021 03:25:41 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 13/3/21 8:53, John Covici wrote:
We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB.
I sort of am installing from source, gentoo installs from source. No one on the gentoo users mailing list seems to be able to help me, except to tell me to use a different mailing list mechanism called mlmmj.
From the perspective of someone who was in the same place (but installing in a FreeBSD S.O.), I would recommend you to follow the "virtualenv" guide but without executing the "env" commands. It will produce a system wide mailman3 installation but it will work (as it is for me since a few moths ago)
I writed down a step by step path of my installation and it could be of your interest (maybe you have to locate and install some packages by different name, but I think it will be not much difference). It could provide you a overall view of all the processes implied.
I'ts here: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 Thanks, by the env commands you mean the creation and activation commands?
I mean the part when you activate the virtualenv (Virtualenv setup & activate virtualenv) in https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-insta...
The servers in which I was migrating from mailman2 were jailed servers and I didn't want to add more virtualization layers (and I read some articles documenting problems using virtualenv in FreeBSD) so, I prefered to install all of it system wide as it was before with mailman2.
I will certainly look at your thread.
What happened to the maintainer? This is an increasing problem these days.
On Sat, 13 Mar 2021 05:00:50 -0500, Bernd Wurst wrote:
Hi.
Am 13.03.21 um 04:36 schrieb John Covici:
Hi. I am having a great deal of difficulty installing mailman3 using gentoo and sendmail.
Mailman in gentoo is kind of maintainerless (will be in a few days, I suppose) and so this method can not be recommended.
We installed using pip in a regular useraccount.
regards, Bernd
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/
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.comOn Sat, 13 Mar 2021 05:42:53 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 13/3/21 9:44, John Covici wrote:
On Sat, 13 Mar 2021 03:25:41 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 13/3/21 8:53, John Covici wrote:
We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB.
I sort of am installing from source, gentoo installs from source. No one on the gentoo users mailing list seems to be able to help me, except to tell me to use a different mailing list mechanism called mlmmj.
From the perspective of someone who was in the same place (but installing in a FreeBSD S.O.), I would recommend you to follow the "virtualenv" guide but without executing the "env" commands. It will produce a system wide mailman3 installation but it will work (as it is for me since a few moths ago)
I writed down a step by step path of my installation and it could be of your interest (maybe you have to locate and install some packages by different name, but I think it will be not much difference). It could provide you a overall view of all the processes implied.
I'ts here: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 Thanks, by the env commands you mean the creation and activation commands?
I mean the part when you activate the virtualenv (Virtualenv setup & activate virtualenv) in https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-insta...
The servers in which I was migrating from mailman2 were jailed servers and I didn't want to add more virtualization layers (and I read some articles documenting problems using virtualenv in FreeBSD) so, I prefered to install all of it system wide as it was before with mailman2.
I will certainly look at your thread.
Now one thing came up while trying to create the database, I got a traceback complaining about a revision error because gentoo had a slightly different version (3.3.2) instead of 3.3.3 using pip. When I upgrade mailman, am I going to have to do something to the database as well and why should the database have some kind of reference to the mailman version?
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.comOn 3/13/21 11:14 AM, John Covici wrote:
Now one thing came up while trying to create the database, I got a traceback complaining about a revision error because gentoo had a slightly different version (3.3.2) instead of 3.3.3 using pip. When I upgrade mailman, am I going to have to do something to the database as well and why should the database have some kind of reference to the mailman version?
I don't know why this is an issue. You shouldn't need to do anything with the database when you upgrade. Please post the full traceback and error message.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, 13 Mar 2021 14:46:55 -0500, Mark Sapiro wrote:
On 3/13/21 11:14 AM, John Covici wrote:
Now one thing came up while trying to create the database, I got a traceback complaining about a revision error because gentoo had a slightly different version (3.3.2) instead of 3.3.3 using pip. When I upgrade mailman, am I going to have to do something to the database as well and why should the database have some kind of reference to the mailman version?
I don't know why this is an issue. You shouldn't need to do anything with the database when you upgrade. Please post the full traceback and error message.
Sorry I can't reproduce it, after dropping and recreating the database the error went away, but it was in alembic and it was talking about an invalid revision and gave a long hex string.
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.com
On Mar 13, 2021, at 1:09 PM, John Covici <covici@ccs.covici.com> wrote:
On Sat, 13 Mar 2021 14:46:55 -0500, Mark Sapiro wrote:
On 3/13/21 11:14 AM, John Covici wrote:
Now one thing came up while trying to create the database, I got a traceback complaining about a revision error because gentoo had a slightly different version (3.3.2) instead of 3.3.3 using pip. When I upgrade mailman, am I going to have to do something to the database as well and why should the database have some kind of reference to the mailman version?
I don't know why this is an issue. You shouldn't need to do anything with the database when you upgrade. Please post the full traceback and error message.
Sorry I can't reproduce it, after dropping and recreating the database the error went away, but it was in alembic and it was talking about an invalid revision and gave a long hex string.
My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2).
But that’s just my guess without looking at the traceback.
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una covici@ccs.covici.com <mailto:covici@ccs.covici.com>
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote:
On Mar 13, 2021, at 1:09 PM, John Covici <covici@ccs.covici.com> wrote:
On Sat, 13 Mar 2021 14:46:55 -0500, Mark Sapiro wrote:
On 3/13/21 11:14 AM, John Covici wrote:
Now one thing came up while trying to create the database, I got a traceback complaining about a revision error because gentoo had a slightly different version (3.3.2) instead of 3.3.3 using pip. When I upgrade mailman, am I going to have to do something to the database as well and why should the database have some kind of reference to the mailman version?
I don't know why this is an issue. You shouldn't need to do anything with the database when you upgrade. Please post the full traceback and error message.
Sorry I can't reproduce it, after dropping and recreating the database the error went away, but it was in alembic and it was talking about an invalid revision and gave a long hex string.
My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2).
That is sort of what happened, except in the opposite direction, it was from 3.3.3 to 3.3.2. My question is therefore, do I have to update this alembic_version when I upgrade mailman to a newer version? That is what I was getting at.
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.comOn 3/13/21 7:08 PM, John Covici wrote:
On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote:
My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2).
That is sort of what happened, except in the opposite direction, it was from 3.3.3 to 3.3.2. My question is therefore, do I have to update this alembic_version when I upgrade mailman to a newer version? That is what I was getting at.
Abhilash's conjecture is that the error was due to a Mailman version accessing a database that had been previously accessed by a newer version so that the version_num in the alembic_version table didn't exist in mailman/database/alembic/versions/. This normally would not occur on an upgrade of Mailman, but if you went from a gentoo Mailman core to a version obtained by pip, it's possible that the gentoo Mailman had an alembic version that wasn't known to the pip Mailman even though the pip Mailman was newer.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, 13 Mar 2021 22:51:46 -0500, Mark Sapiro wrote:
On 3/13/21 7:08 PM, John Covici wrote:
On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote:
My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2).
That is sort of what happened, except in the opposite direction, it was from 3.3.3 to 3.3.2. My question is therefore, do I have to update this alembic_version when I upgrade mailman to a newer version? That is what I was getting at.
Abhilash's conjecture is that the error was due to a Mailman version accessing a database that had been previously accessed by a newer version so that the version_num in the alembic_version table didn't exist in mailman/database/alembic/versions/. This normally would not occur on an upgrade of Mailman, but if you went from a gentoo Mailman core to a version obtained by pip, it's possible that the gentoo Mailman had an alembic version that wasn't known to the pip Mailman even though the pip Mailman was newer.
OK, thanks.
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.com
participants (5)
-
Abhilash Raj -
Bernd Wurst -
Guillermo Hernandez (Oldno7) -
John Covici -
Mark Sapiro