From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>, Syed Fahar Abbas <fahar(dot)abbas(at)enterprisedb(dot)com>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
Subject: | Re: pgAdmin 3.0 builds |
Date: | 2018-04-17 14:23:02 |
Message-ID: | 20180417142302.GC6815@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Re: Dave Page 2018-04-16 <CA+OCxoxQdTWbGYNjEd2dRePuwWzMSQw4ynfuJ4PfCvdB=7EwNA(at)mail(dot)gmail(dot)com>
> > The python part is causing headaches - the move from flask-babel to
> > flask-babelex is hurting because that's not available in Debian, and
> > the move as such is controversial:
> > https://github.com/mattupstate/flask-security/issues/715
>
> Hmm, we had to update as flask_babel isn’t working with modern versions of
> Babel.
>
> > At the moment this looks like a huge time sink to package.
>
> Can flask_babelex be built as a private package and installed in the
> pgAdmin web/ directory? That’s what Devrim does with a bunch of the dips
> for the RPMs.
That part turned out to be easier than I had thought. I had already
packaged babelex because it's a dependency of flask-security 3.0.0,
but never uploaded it because flask-security 1.7.5 seemed good enough.
Done now.
flask-security 3.0.0 has the additional problem that it wants
python-speaklater, but that seems to be dead upstream and got removed
from Debian years (?) ago, so I think we'll stay with 1.7.5 for now.
Packages for pgadmin4 3.0 will appear on the mirrors in about one hour.
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2018-04-17 14:25:19 | Re: pgAdmin 3.0 builds |
Previous Message | pgAdmin 4 Jenkins | 2018-04-17 09:24:05 | Jenkins build is back to normal : pgadmin4-master-python35 #574 |