On Tue, Jan 23, 2018, at 10:07 AM, Abhilash Raj wrote:
On Tue, Jan 23, 2018, at 12:34 AM, Henrik Rasmussen wrote:
I am currently using Docker-mailman rolling releases and with great respect to the maintainer's time it was my impression from @maxking that rolling releases was likely to be one week behind the development.
In my report of https://gitlab.com/mailman/mailman/issues/444 @msapiro commented that #444 is a duplicate of #406 (closed) which was fixed by ! 322 (merged), but !322 was merged a month ago.
Thinking that I wasn't up to speed, I did a
docker pull quay.io/ maxking/mailman-core:rollingonly got 'XXXXXXXXXXXX: Already exists'. Alsodocker imagesshows 'quay.io/maxking/mailman-core
rolling 1654a3226db8 7 weeks ago 179.3 MB'.Not to be umpolite, did I misunderstand the concept?
Not at all, this probably is something wrong with my build system. You can email to me directly in-future, in case you find the images aren't updated.
I remember setting up weekly builds, but maybe they aren't working for some reason. I will look into to tonight.
It looks like mailman-web build is currently broken (Due to Django 2.0 being installed on Python2), I will try to fix it soon.
It is a simple change, mostly upgrading pip to the latest version. If that doesn't work (docs say that it should, Pip 9.x doesn't try to install Django 2.0 on a Python 2 environment, so ideally it should), we can pin the django to < 2.0.
-- Abhilash Raj maxking@asynchronous.in