Mailman 3 April 2015 - Mailman-Developers

Re: [Mailman-Developers] Mailman 3 discussion
by Florian Fuchs 21 Apr '15

21 Apr '15

On Mon, Apr 20, 2015 at 22:36:14PM +0300, Danil Smirnov wrote: >2015-04-20 22:22 GMT+03:00 Florian Fuchs <f(a)florianfuchs.com>: >> That looks like incompatible versions of Postorius and mailman.client >> to me. The currently available ones on pypi and launchpad (released >> on Friday) should be working. Did you download them before Friday >> evening (EST) by any chance? > >Nope. I've downloaded very last revision couple of hours ago. OK, the problem was a file name conflict on the Python package index (due to an erroneously omitted pre-release suffix while parsing the version string of a previous beta-release), which eventually led to pypi delivering the previous release's tarball. I've associated a new file with the latest release on pypi so the correct tarball gets installed. Sorry for that... Florian

2 1

Re: [Mailman-Developers] Mailman 3 discussion
by Danil Smirnov 20 Apr '15

20 Apr '15

Look at this please: http://dpaste.com/3N8ABXY

1 0

Re: [Mailman-Developers] Mailman 3 discussion
by Florian Fuchs 20 Apr '15

20 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 20.04.2015 um 20:13 schrieb Danil Smirnov: > I would like to ask too. > > After successful fight with 'virtualenv' buggy version bug > (https://bugs.launchpad.net/mailman/+bug/1445764) I've proceeded to > initial setup through the Postorius web inteface. > > I opened the link http://127.0.0.1:8000/mailman3 in the 'links' > browser and try to add new domain through 'Manage lists' - > 'Domains' - 'Create domain' form. > > When I submit the form, I get the error: > > --- [root@host ~]# links http://127.0.0.1:8000/mailman3 > > > TypeError at /mailman3/domains/new/ (p1 of 18) > > TypeError at /mailman3/domains/new/ That looks like incompatible versions of Postorius and mailman.client to me. The currently available ones on pypi and launchpad (released on Friday) should be working. Did you download them before Friday evening (EST) by any chance? Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVNVHyAAoJEEceGbPdavl74bwIAKOAkO6zAIkTbhFNY4P9VFF0 o3TkeFpf2VVdmiQihQczk7ToTprfnGvu5PFo5jX77AaFyF4gaEOaFSfQ6/wwomwL nPb4XayVolceaa5oJbXmPE5XtVUJwVrUrIz9MXreoPDNS9QldUc1c95VVBPQSwQM 7vY1Bc/i2iMRONyTO2ZLWuvVXQwQrSKLlL4P2A1NR7eStE7z+9D17X8jE14Pq8sA uv9Fxy8KMHilXxmGLPePZ6483a415vy9lNCqde6iXbLLk3Tj4FZRgCmBSbw+m+RB Zgt8rJoqn/lLSpN9W/oKDZI4bn2svHK0gmotwspq8qGM+ZDWDJaVmiGNS3Dql/4= =rko1 -----END PGP SIGNATURE-----

2 1

Re: [Mailman-Developers] [hyperkitty-devel] Mailman Suite 3.0rc1 awaiting an upstream fix
by Pierre-Yves Chibon 20 Apr '15

20 Apr '15

On Mon, Apr 20, 2015 at 08:19:29PM +0200, Aurelien Bompard wrote: > > We are (as in Patrick is) currently working on getting a Fedora 22 builder added > > to the jenkins instance so that we have a python 3.4 available for you folks if > > you so desire :) > > > Fedora 21 has Python 3.4, so that would be enough. That is true, but currently we only have a F20 builder, but good to know that if we do not manage to get the F22 one running, we can also try getting a F21 one up. Thanks, Pierre

1 0

Mailman Suite 3.0rc1 awaiting an upstream fix
by Sumana Harihareswara 20 Apr '15

20 Apr '15

At the PyCon sprint last week, we made a lot of progress towards a 3.0 release and we discussed next steps. I'm very glad so many of us could make it and pitch in. The 3.0rc1 depends on a new Falcon release because there's a bugfix awaiting release in Falcon that fixes a blocker bug for us: https://bugs.launchpad.net/postorius/+bug/1444504 Once that's out, we can put out a release candidate. In order to release 3.0.0 final, we need core native releases for all 5 components of the Mailman suite, with tested installation instructions and with all the components tagged, tested, and on PyPI. We'd also like some infrastructure and workflow improvements before we do that -- for one thing, we ought to set up continuous integration to run our automated tests on every merge. We will probably request a CI server/VM from the Python Software Foundation. We could actually set up CI for HyperKitty (and probably our other components as well) right away using the (no guarantee of uptime/service level) Jenkins installation at http://jenkins.cloud.fedoraproject.org/ if someone followed the instructions at https://fedoraproject.org/wiki/Jenkins@infra#Can_I_add_my_project_to_Jenkin… and add ticket to https://fedorahosted.org/fedora-infrastructure/ . We need to have an i18n setup and I've agreed to take lead on that. And there's further potential wrangling around Launchpad, branches, Bazaar, Git, etc. that I'll write up tomorrow. Hope this helps keep everyone up to date. -- Sumana Harihareswara http://brainwane.net

3 2

Re: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3
by Danil Smirnov 18 Apr '15

18 Apr '15

And fixing the main problem with Python 3.4 path did not help to make "buildout" command successful. I've posted the error message as a comment of my bug report: https://bugs.launchpad.net/mailman/+bug/1445764 2015-04-18 15:21 GMT+03:00 Danil Smirnov <danil(a)smirnov.la>: > 2015-04-18 3:52 GMT+03:00 Mark Sapiro <mark(a)msapiro.net>: >> Please see this wiki page <http://wiki.list.org/x/17891734>. It >> addresses Ubuntu, not CentOS, but talks about prerequisite things >> applicable to both although the apt-get package names may be different >> for Yum. > > This does not help. The error is the same. > > Filled a bug: > https://bugs.launchpad.net/mailman/+bug/1445764 > > Danil

1 0

Re: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3
by Mark Sapiro 18 Apr '15

18 Apr '15

Please see this wiki page <http://wiki.list.org/x/17891734>. It addresses Ubuntu, not CentOS, but talks about prerequisite things applicable to both although the apt-get package names may be different for Yum. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Re: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3
by Mark Sapiro 17 Apr '15

17 Apr '15

On 04/17/2015 12:48 PM, Danil Smirnov wrote: > > Mark, I don't understand you: > # bzr pull > Using saved parent location: > http://bazaar.launchpad.net/~abompard/mailman-bundler/mailman-bundler/ > No revisions or tags to pull. OK, it seems your branch is up to date. I was only concerned because we were sprinting on Mailman 3 at PyCon Monday through Thursday and there have been many changes to mailman-bundler and the packages it pulls in. postorius, mailman.client and mailman3 have all had multiple commits in this time. >> The README.rst in the branch is the latest and differs in some details from the one you referenced. > > I've checked it and don't see any differences before buildout command. I was mistaken. That document is up to date with the branch. >> Something is wrong because it should have installed Python 3.4 in venv-3.4. > > Definitely! > > That's why I'm writing. > > I think it's important for the developers to test what you're going to > release on my new Centos 7 box, > isn't it? Absolutely, and we appreciate your doing so. > I can fill bug report if it is more appropriate. Yes, that would be appropriate. File the bug at <https://bugs.launchpad.net/mailman-bundler/+filebug> and include the full OS version, what Python software you installed prior to running buildout, what steps you followed to install that software and what steps you took before running buildout. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3
by Mark Sapiro 17 Apr '15

17 Apr '15

On April 17, 2015 12:20:48 PM PDT, Danil Smirnov <danil(a)smirnov.la> wrote: > >I've got this branch TODAY so I think it's latest. > >So, does it mean that there is no way to install Mailman 3 using >manual mentioned? There have been at least 13 revs to that branch since Monday. The README.rst in the branch is the latest and differs in some details from the one you referenced. Something is wrong because it should have installed Python 3.4 in venv-3.4. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Android phone with K-9 Mail. [Unpaid endorsement]

2 1

Re: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3
by Mark Sapiro 17 Apr '15

17 Apr '15

On 04/17/2015 11:24 AM, Danil Smirnov wrote: > But I've got the same error again: > > Installing mailman. > The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) > does not exist > /tmp/tmplM1FLA/run: line 2: > /usr/local/src/mailman-bundler/venv-3.4/bin/pip: Нет такого файла или > каталога > While: > Installing mailman. > > I wonder don't I need to do > > ln -s /usr/local/bin/python3.4 /usr/bin/python3.4 > > as the error says? That will probably get around this, but I don't think it should be necessary. At this point, I suspect you haven't activated the venv that you had active when you started. (Every time you start a new shell, you have to activate the venv for that shell.) Note also that the document at <http://mailman-bundler.readthedocs.org/en/latest/> is NOT the latest. I suggest you remove your mailman-bundler branch and get the latest with 'bzr branch lp:mailman-bundler' (or maybe just update yours with 'bzr pull' and remove the venv and venv-3.4 directories), and follow the README.rst in the latest rev. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2