On 9/28/22 23:18, sascha.rissel@gmail.com wrote:
pip install wheel
After this, I deleted the venv again and startet anew, again. But this time, I explicitly did (as Stephen suggested above) prior to
pip install wheel mailman psycopg2-binary\<2.9
This time, it ran through without errors, although "wheel" is also contained in the latter command. Can you explain that?
Apparently, if you run pip install wheel mailman psycopg2-binary\<2.9
pip attempts to build lazr.delegates which is a mailman dependency
before it fully installs wheel. Thus the need to pip install wheel
first.
However, with both virtualenv 20.0.17/python 3.8.10 and virtualenv 20.4.2/python 3.9.10 virtualenv venv installs wheel in
site-packages in the venv as does python3 -m virtualenv venv, but
python3 -m venv venv does not. But, at least in my case, with venv
built with python3 -m venv venv and not containing wheel in
site-packages pip install wheel mailman psycopg2-binary\<2.9 runs
without error.
Second question: There is still no directory "/etc/mailman3" created, where I can create mailman.cfg in.
Does this maybe result from the fact that in first instance, I tried to install mailman3-full via "apt-get install" and removed it again via "apt-get remove"; with manually deleting /etc/mailman3 afterwards.
Shall I create /etc/mailman3 manually and adding "mailman" system user permissions?
Yes, as the doc says at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mailm..., "After this, create a configuration file at /etc/mailman3/mailman.cfg for Mailman Core:"
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan