public inbox for [email protected]  
help / color / mirror / Atom feed
From: Khushboo Vashi <[email protected]>
To: Christoph Berg <[email protected]>
Cc: Dave Page <[email protected]>
Cc: Syed Fahar Abbas <[email protected]>
Cc: Devrim GÜNDÜZ <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Subject: Re: pgAdmin v3.1 candidate builds and source...
Date: Mon, 2 Jul 2018 09:57:26 +0530
Message-ID: <CAFOhELc2oFoN_ic3a6oW6nt-9W3=ADgczfZxdE9VjHcj1emL_Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CA+OCxow1BDDXK9K1d-pnSAoBE5O=+RD6QNxA5ynH-X+-rPN7jA@mail.gmail.com>
	<[email protected]>
	<CA+OCxozp8Zsj+NTF8hBt46oDJku6oFA6ayTex4jkjyXNsR84Xw@mail.gmail.com>
	<[email protected]>
	<CA+OCxoyu6KQamBfgV2kF2uB2AYsty7HhyeSsvTa1yuTdANWimw@mail.gmail.com>
	<[email protected]>

Hi Christoph,

On Sat, Jun 30, 2018 at 9:46 PM, Christoph Berg <[email protected]> wrote:

> Re: Dave Page 2018-06-28 <CA+OCxoyu6KQamBfgV2kF2uB2AYsty7Hh
> [email protected]>
> > > That said, the web/pgadmin/static/*/generated/ directories have
> > > disappeared from the tarball, so pgadmin doesn't load anymore. Could
> > > you please put them back, as I don't think rebuilding them via yarn is
> > > feasible? Because that's not packaged either...
> > >
> >
> > OK, please go grab the tarball again, from thttps://www.postgresql.org/
> > ftp/pgadmin/pgadmin4/v3.1/source/. The MD5 checksum should be:
> >
> > f057bf46055d4f7b07a42ae984f499dd  pgadmin4-3.1.tar.gz
> >
> > This should contain the missing files.
> >
> > Sorry about that - stupid case-sensitivity bug in a script :-(
>
> Hi,
>
> the tarball works fine now, thanks!
>
> Good to hear this.

> I could finally build the packages now. (There were some issues with
> the python3.7 update happening in Debian at the same time, which broke
> a few bits, but I managed to work around.)
>
> One user raised the same issue that pgAdmin is not working with python
3.7. He found that the issue is with psycopg2 (Ref:
https://github.com/psycopg/psycopg2/issues/714) as async and await are now
keywords and we are using async in pgAdmin 4.

So, I am curious to know how you have fixed this issue?


> Cheers,
> Christoph
>
> Thanks,
Khushboo


view thread (19+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: pgAdmin v3.1 candidate builds and source...
  In-Reply-To: <CAFOhELc2oFoN_ic3a6oW6nt-9W3=ADgczfZxdE9VjHcj1emL_Q@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox