Mailman 3 May 2015 - Mailman-Developers

Re: [Mailman-Developers] help with ImportError: No module named 'psycopg2'
by Abhilash Raj 28 May '15

28 May '15

On Wed, 27 May 2015 21:44:51 +0300 Danil Smirnov <danil(a)smirnov.la> wrote: > I'm still trying to get Mailman 3 ready for the production. > > I've set parameters for the production and trying to make post-update: > > --- > > (venv)[root@host mailman-bundler]# bin/mailman-post-update > + '[' False == False ']' > + mkdir -p /var/spool/mailman-web/static > + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin > collectstatic --clear --noinput --verbosity 0 > + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin compress > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_link.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_settings.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_removal.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/archival_options.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/unsubscribe.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/login.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscription_requests.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscriptions.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_tasks.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/confirm_delete.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/summary.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_mailmansettings.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/members.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_subscribe.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_index.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/metrics.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_profile.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscriptions.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings_legacy.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscription_preferences.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/memberoptions.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/held_messages.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_sent.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/index.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_preferences.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/confirm_dialog.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_confirm_delete.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/site_settings.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscribe.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/errors/generic.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_new.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Error parsing template > /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/new.html: > Invalid template name in 'extends' tag: ''. Got this from the > 'postorius_base_template' variable. > Found 'compress' tags in: > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_posts.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/message_new.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/api.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/reattach.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_profile.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/login.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/message.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/index.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/register.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/schemaupgrade.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/404.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/overview.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/thread_list.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/500.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/private.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/base.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/search_results.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/thread.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_public_profile.html > /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/notimplemented.html > Compressing... done > Compressed 3 block(s) from 20 template(s). > +++ /usr/local/src/mailman-bundler/bin/django-read-settings > DATABASES.default.NAME > ++ dirname mailman3 > + dbdir=. > + mkdir -p . > + > syncdb_cmd='/usr/local/src/mailman-bundler/bin/mailman-web-django-admin > migrate' > + [[ ! -t 1 ]] > + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin migrate > Operations to perform: > Synchronize unmigrated apps: postorius, compressor, > django_extensions, paintstore, django_gravatar, rest_framework, > haystack, crispy_forms > Apply all migrations: sessions, admin, auth, default, contenttypes, > hyperkitty Synchronizing apps without migrations: > Creating tables... > Installing custom SQL... > Installing indexes... > Running migrations: > No migrations to apply. > Your models have changes that are not yet reflected in a migration, > and so won't be applied. > Run 'manage.py makemigrations' to make new migrations, and then > re-run 'manage.py migrate' to apply them. > + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin > update_index Indexing 0 emails > + '[' '!' -f /usr/sbin/postmap ']' > + /usr/local/src/mailman-bundler/bin/mailman aliases > Traceback (most recent call last): > File "/usr/local/src/mailman-bundler/venv-3.4/bin/mailman", line 9, > in <module> > load_entry_point('mailman==3.0.0', 'console_scripts', 'mailman')() > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/bin/mailman.py", > line 98, in main initialize(config_path) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/initialize.py", > line 191, in initialize initialize_2(propagate_logs=propagate_logs) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/initialize.py", > line 163, in initialize_2 config.db = getUtility(IDatabaseFactory, > utility_name).create() File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/factory.py", > line 59, in create database.initialize() > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/base.py", > line 110, in initialize self.engine = create_engine(url) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/engine/__init__.py", > line 386, in create_engine return strategy.create(*args, **kwargs) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/engine/strategies.py", > line 75, in create dbapi = dialect_cls.dbapi(**dbapi_args) > File > "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", > line 554, in dbapi import psycopg2 > ImportError: No module named 'psycopg2' > > --- > > But: > > pip install psycopg2 > You are using pip version 6.1.1, however version 7.0.1 is available. > You should consider upgrading via the 'pip install --upgrade pip' > command. Requirement already satisfied (use --upgrade to upgrade): > psycopg2 in /usr/local/src/venv/lib/python2.7/site-packages There are actually 2 virtualenvs for mailman. One is the default one that you are working in, another one(venv-3.4) is probably automatically created by mailman-bundler as you can see in the logs above. This should fix your problem. $ source /usr/local/src/mailman-bundler/venv-3.4/bin/activate $ pip install psycopg2 $ (reactivate your original venv) > > > Please advice. > > Danil > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > https://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: > http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: > https://mail.python.org/mailman/options/mailman-developers/raj.abhilash1%40… > > Security Policy: http://wiki.list.org/x/QIA9 -- thanks, Abhilash Raj

3 3

help with ImportError: No module named 'psycopg2'
by Danil Smirnov 27 May '15

27 May '15

I'm still trying to get Mailman 3 ready for the production. I've set parameters for the production and trying to make post-update: --- (venv)[root@host mailman-bundler]# bin/mailman-post-update + '[' False == False ']' + mkdir -p /var/spool/mailman-web/static + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin collectstatic --clear --noinput --verbosity 0 + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin compress Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_link.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_settings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_removal.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/archival_options.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/unsubscribe.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/login.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscription_requests.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscriptions.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_tasks.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/confirm_delete.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/summary.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_mailmansettings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/members.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/mass_subscribe.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_index.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/metrics.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_profile.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscriptions.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/settings_legacy.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_subscription_preferences.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/memberoptions.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/held_messages.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_activation_sent.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/index.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/user_address_preferences.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/confirm_dialog.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_confirm_delete.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/site_settings.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/subscribe.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/errors/generic.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/domain_new.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Error parsing template /usr/local/src/mailman-bundler/eggs/postorius-1.0.1-py2.7.egg/postorius/templates/postorius/lists/new.html: Invalid template name in 'extends' tag: ''. Got this from the 'postorius_base_template' variable. Found 'compress' tags in: /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_posts.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/message_new.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/api.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/reattach.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_profile.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/login.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/message.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/index.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/register.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/schemaupgrade.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/404.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/overview.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/thread_list.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/500.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/private.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/base.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/search_results.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/thread.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/user_public_profile.html /usr/local/src/mailman-bundler/eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/templates/hyperkitty/errors/notimplemented.html Compressing... done Compressed 3 block(s) from 20 template(s). +++ /usr/local/src/mailman-bundler/bin/django-read-settings DATABASES.default.NAME ++ dirname mailman3 + dbdir=. + mkdir -p . + syncdb_cmd='/usr/local/src/mailman-bundler/bin/mailman-web-django-admin migrate' + [[ ! -t 1 ]] + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin migrate Operations to perform: Synchronize unmigrated apps: postorius, compressor, django_extensions, paintstore, django_gravatar, rest_framework, haystack, crispy_forms Apply all migrations: sessions, admin, auth, default, contenttypes, hyperkitty Synchronizing apps without migrations: Creating tables... Installing custom SQL... Installing indexes... Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. + /usr/local/src/mailman-bundler/bin/mailman-web-django-admin update_index Indexing 0 emails + '[' '!' -f /usr/sbin/postmap ']' + /usr/local/src/mailman-bundler/bin/mailman aliases Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/bin/mailman", line 9, in <module> load_entry_point('mailman==3.0.0', 'console_scripts', 'mailman')() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/bin/mailman.py", line 98, in main initialize(config_path) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/initialize.py", line 191, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/initialize.py", line 163, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/factory.py", line 59, in create database.initialize() File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/base.py", line 110, in initialize self.engine = create_engine(url) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/engine/__init__.py", line 386, in create_engine return strategy.create(*args, **kwargs) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/engine/strategies.py", line 75, in create dbapi = dialect_cls.dbapi(**dbapi_args) File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 554, in dbapi import psycopg2 ImportError: No module named 'psycopg2' --- But: pip install psycopg2 You are using pip version 6.1.1, however version 7.0.1 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Requirement already satisfied (use --upgrade to upgrade): psycopg2 in /usr/local/src/venv/lib/python2.7/site-packages Please advice. Danil

1 0

Re: [Mailman-Developers] mailman 3 and mysql
by Barry Warsaw 27 May '15

27 May '15

On May 27, 2015, at 04:49 PM, Danil Smirnov wrote: >1) Does this also relate to Postorius and HyperKitty db configuration >set in file production.py? Can I use MySQL for them?.. Others can provide more detailed answers but it might be a good idea to keep all three components in the same database. At least that makes it easier to maintain. >2) What is better for production - to keep SQLite use or install PostgreSQL? >The manual told me that I have to use 'full-blown database server' >which is not true for SQLite I think?... I'd like for SQLite to be appropriate for production, but it might not be. Because of the way SQLite does locking (also, in the Python layer), you might get some database lock errors. We've seen a few of these reported in the past; it usually means a transaction hasn't been properly closed (aborted or committed) in one process. Remember, MM3 has no list-locks any more. None of that should happen with a client/server based DB. I guess I'd say that we'd love to get more production experience with MM3 backed by SQLite, so use that if you feel like you can help debug any problems that *might* occur. If you don't want to be bothered, stick with PG for now, or if you know MySQL well, try to adapt the PG support to it and contribute! :) Cheers, -Barry

1 0

Re: [Mailman-Developers] mailman 3 and mysql
by Barry Warsaw 27 May '15

27 May '15

On May 27, 2015, at 03:39 PM, Danil Smirnov wrote: >As I see on page >https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html > >Mailman 3 should work with MySQL/MariaDB database. Well, that page is careful to say that SQLAlchemy, the ORM layer we use, is compatible with MySQL, but it doesn't claim that Mailman 3 actually is. Currently we only officially support SQLite and PostgreSQL. We test all the time with the former, and try to keep the latter functional (that will actually get better once our gitlab CI integration is working). TL;DR: We want to be able to support any FLOSS database backend that SQLAlchemy supports, but we need contributions and testing for databases other than SQLite and PostgreSQL. Cheers, -Barry

2 1

mailman 3 and mysql
by Danil Smirnov 27 May '15

27 May '15

As I see on page https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html Mailman 3 should work with MySQL/MariaDB database. Could you please help me put right configuration to the [database] section of mailman.cfg file? Thanks. Danil

1 0

Re: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks
by Abhilash Raj 26 May '15

26 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, 25 May 2015 17:19:17 +0530 Bhavesh Goyal <bhavesh.goyal093(a)gmail.com> wrote: > Widget Specifications: > > The Tasks widget gives the admin, a list of pending tasks which > require his immediate attention on the dashboard. The tasks > particularly include those of 'Held Messages' (pending for > moderation) and 'Subscription Requests'. A Task is added to the To - > Do List for admin automatically, whenever a message sent by an user > to a list is held for moderation or whenever a user makes a request > for a subscription (through list-join). > > That Being said, > I ve made a prototype for The widget 'model' which adds a 'task' > entry for the admin, whenever a new message is queued for moderation > or a subscription request is made (through list-join). The model can > then further be iterated to create views for postorius to generate > list of all tasks to be displayed on the dashboard. > > Approach : > > The 'Tasks' model and the REST API used to query the model are > implemented in the core I think a better idea would be to keep everything in Postorius. Held messages and subscription requests are already available through the REST API, and hence can easily be used to create the `Tasks` model in Postorius. Barry, Florian thoughts? - -- thanks, Abhilash Raj -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVYw4jAAoJEJ2bK6Bh0KZ8AisP/05yxnMO0xG/Ye82QRHIm6mv 1wncgXvNL2UG7qW8pQevFQaAnhf5zrb4DZA12qFtYUGMbArWfpE5dDNyAaRrKQBT joKb9p/tvAwIS1aqH7fudcU7p60jgluoHDs4KfR39jNPgSZSkrv2z5jlZiLJew5X bZt6S/28fYH9nqYAFueoR4SnLIVCLA3SQ6tkuywPKPbPqT7DsHk1lQHcJdZVa/zu zKtgj5lsrALAMlL1vMuGll5CCPLRlzHjCud646KDQse1Vm/lzjcqtacq7LO2D4CN qEcnWfPbWtKVjiYF8le0kSlumGJ754t/drxty9ZZGEWAOinZVQ0gkiHRcNQpdo5V 4nePnLYZlx0SFY1E+3mIouqO0lpwMXY6IY1zw2gd9Uu8/XI9D3+vLcdwZF7yGYHl 7p7G03B//zg9Qd3I/PaCjDKUDAFu5otphSCylN392nPenUrznfQef/t7MQQFepqc kVP43O4rBo1OwEumuFRjs9FcC8sAi2RVoH+CvYXv36xBMALJtERm0q0gg8Xt0AIy LvkqQ+tHtcljoMwLXpe0Z3TqNO4V1VbjHMOCUIvmdGUx4r0gBD6hrEM3mgr+Xcg5 JHswGOswDiG/CDS66Ksn0PWD6EC9BvQAi+HUyD03rHYwlsbanwM+CtE9crb1GxF1 oSp4R3qdwtDO/+13Dx2z =AZeK -----END PGP SIGNATURE-----

3 3

Re: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks
by Bhavesh Goyal 26 May '15

26 May '15

Hi ! On Tue, May 26, 2015 at 6:20 AM, Barry Warsaw <barry(a)list.org> wrote: >Bhavesh, can you describe why a task model in the core is a better way to > go? > > I thought of implementing the model in core in the first place because I thought it may would have been good to have the user tasks available on hand even when one is not having access to the postorius web UI. Second: I was able to track every moderation or subscription event 'directly' through the core, making it (a little)easier to add an entry in contrast to a postorius model, for which the existing REST properties accompanied with a logic would have been used to detect a new incoming event. But, Now on a whole, Yes I agree, I should have discussed the thought before, the reason being now I get the idea of postorius and the core complementing each other always on the same machine and the 'need' of Tasks more in the web dashboard rather than in the core. Also, as Barry said, if the logic behind moderations change in coming time, Yes, It would affect the overall functionality of the tasks model too. Thus, It would rather be a better choice to use the the existing REST calls and use a postorius model instead. :) Thanks for your consideration and making the idea clear :) -- Regards, Bhavesh Goyal, Computer Science Engineering, IIIT Hyderabad

1 0

[Project Discussion] Approach for Implementing Admin Tasks
by Bhavesh Goyal 25 May '15

25 May '15

Widget Specifications: The Tasks widget gives the admin, a list of pending tasks which require his immediate attention on the dashboard. The tasks particularly include those of 'Held Messages' (pending for moderation) and 'Subscription Requests'. A Task is added to the To - Do List for admin automatically, whenever a message sent by an user to a list is held for moderation or whenever a user makes a request for a subscription (through list-join). That Being said, I ve made a prototype for The widget 'model' which adds a 'task' entry for the admin, whenever a new message is queued for moderation or a subscription request is made (through list-join). The model can then further be iterated to create views for postorius to generate list of all tasks to be displayed on the dashboard. Approach : The 'Tasks' model and the REST API used to query the model are implemented in the core <https://code.launchpad.net/~bhavesh-goyal093/mailman/Tasks-Core>. Methods such as create and delete are implemented in the mailmanclient <https://code.launchpad.net/~bhavesh-goyal093/mailman.client/Tasks-REST> for communicating with core's REST API. The Corresponding class for Tasks model is created in postorius <https://code.launchpad.net/~bhavesh-goyal093/postorius/Tasks-postorius> models to expose its 'objects' attribute to be used latter, for generating views for a complete list of tasks on the dashboard. Moderation tasks are added though the 'hold' chain for incoming messages and the membership command 'join' is used to make an entry for a subscription task. The Complete Prototype discussed is given in the links: https://code.launchpad.net/~bhavesh-goyal093/mailman/Tasks-Core https://code.launchpad.net/~bhavesh-goyal093/mailman.client/Tasks-REST https://code.launchpad.net/~bhavesh-goyal093/postorius/Tasks-postorius -- Regards, Bhavesh Goyal, Computer Science Engineering, IIIT Hyderabad

1 0

Re: [Mailman-Developers] [Project Discussion] Assigining Default Priority levels to user tasks
by David Andrews 23 May '15

23 May '15

At 03:13 PM 5/23/2015, Bhavesh Goyal wrote: >Brief Introduction to Related Project content: > >The To - Do List proposed in the project ><https://www.google-melange.com/gsoc/project/details/google/gsoc2015/bhavesh…>, >'Dashboard for Admins' gives the admin, a list of pending tasks which >require his immediate attention. The tasks particularly include those of >'Held Messages' (pending for moderation) and 'Subscription Requests'. > >Now, among the pile of pending tasks, some Tasks may be of higher >importance than the others to the admin which he can quickly mark to get >them completed first, the next time he sets up to clear the pending list. >Thus color supported Priority Levels have been given and can be set with >each of the tasks, sorting the important ones out from others. Please don't make color as the only way priorities are conveyed. A sizable percentage of the population, particularly males, are color blind, and others are blind and won't see the colors. Dave David Andrews and long white cane Harry. E-Mail: dandrews(a)visi.com or david.andrews(a)nfbnet.org

1 0

[Project Discussion] Assigining Default Priority levels to user tasks
by Bhavesh Goyal 23 May '15

23 May '15

Brief Introduction to Related Project content: The To - Do List proposed in the project <https://www.google-melange.com/gsoc/project/details/google/gsoc2015/bhavesh…>, 'Dashboard for Admins' gives the admin, a list of pending tasks which require his immediate attention. The tasks particularly include those of 'Held Messages' (pending for moderation) and 'Subscription Requests'. Now, among the pile of pending tasks, some Tasks may be of higher importance than the others to the admin which he can quickly mark to get them completed first, the next time he sets up to clear the pending list. Thus color supported Priority Levels have been given and can be set with each of the tasks, sorting the important ones out from others. Discussion Statement : Whenever a new task gets added automatically ( when someone makes a subscription request for instance), what priority level should it be assigned. ? One Approach can be to keep a separate level of 'unprioritised' tasks and assigning a specific color value to this level (uncolored may be), separating them out from the others as the ones with 'priority level not set'. Other Solutions which I think can exist can be, choosing a default priority value for the newly added ones from among low/medium/high (only), limiting the number of colors to 3 instead of 4 for may be a more simpler (memorable) operation. Project Link: https://www.google-melange.com/gsoc/project/details/google/gsoc2015/bhavesh… -- Regards, Bhavesh Goyal, Computer Science Engineering, IIIT Hyderabad

1 0