From: contact.ng0@cryptolab.net
To: guix-devel@gnu.org
Subject: Mailman3 frontend number one: postorius.
Date: Sun, 29 Jan 2017 23:26:11 +0000 [thread overview]
Message-ID: <20170129232617.19235-1-contact.ng0@cryptolab.net> (raw)
I've changed postorius to use python-2 only, but maybe I am wrong again.
Harmut have sent me this link and paste from it some days ago: <https://gitlab.com/mailman/mailman-bundler/issues/28#note_21121520>
Maybe only a fully functional Mailman-service will show wether this is wrong or right, but changing the used python version is trivial as it builds with both and I've added all 3rd level dependencies in both versions (py2 and py3) where available.
next reply other threads:[~2017-01-29 23:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 23:26 contact.ng0 [this message]
2017-01-29 23:26 ` [PATCH 1/6] gnu: Add python-defusedxml contact.ng0
2017-01-29 23:26 ` [PATCH 2/6] gnu: Add python-openid contact.ng0
2017-01-29 23:26 ` [PATCH 3/6] gnu: Add python-django-allauth contact.ng0
2017-01-29 23:26 ` [PATCH 4/6] gnu: Add python-django-gravatar2 contact.ng0
2017-01-29 23:26 ` [PATCH 5/6] gnu: Add python-django-mailman3 contact.ng0
2017-01-29 23:26 ` [PATCH 6/6] gnu: Add postorius contact.ng0
2017-01-30 8:48 ` Hartmut Goebel
2017-01-30 9:10 ` ng0
2017-01-30 9:20 ` Hartmut Goebel
2017-01-30 10:12 ` ng0
2017-01-29 23:31 ` Mailman3 frontend number one: postorius ng0
2017-01-30 11:22 ` postorius, v2 contact.ng0
2017-01-30 11:22 ` [PATCH 1/6] gnu: Add python-defusedxml contact.ng0
2017-01-30 11:22 ` [PATCH 2/6] gnu: Add python-openid contact.ng0
2017-01-30 11:22 ` [PATCH 3/6] gnu: Add python-django-allauth contact.ng0
2017-01-30 11:22 ` [PATCH 4/6] gnu: Add python-django-gravatar2 contact.ng0
2017-01-30 11:22 ` [PATCH 5/6] gnu: Add python-django-mailman3 contact.ng0
2017-01-30 11:22 ` [PATCH 6/6] gnu: Add postorius contact.ng0
2017-01-31 13:40 ` postorius, v2 Hartmut Goebel
2017-02-02 11:51 ` Hartmut Goebel
2017-02-02 12:13 ` ng0
2017-02-02 12:28 ` Python packaging rules again (was: postorius, v2) Hartmut Goebel
2017-02-02 21:28 ` postorius, v2 ng0
2017-02-05 1:28 ` ng0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170129232617.19235-1-contact.ng0@cryptolab.net \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.