Re: pgAdmin v3.1 candidate builds and source...
От | Khushboo Vashi |
---|---|
Тема | Re: pgAdmin v3.1 candidate builds and source... |
Дата | |
Msg-id | CAFOhELc2oFoN_ic3a6oW6nt-9W3=ADgczfZxdE9VjHcj1emL_Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgAdmin v3.1 candidate builds and source... (Christoph Berg <myon@debian.org>) |
Ответы |
Re: pgAdmin v3.1 candidate builds and source...
|
Список | pgadmin-hackers |
Hi Christoph,
On Sat, Jun 30, 2018 at 9:46 PM, Christoph Berg <myon@debian.org> wrote:
Thanks,Re: Dave Page 2018-06-28 <CA+OCxoyu6KQamBfgV2kF2uB2AYsty7Hh yeSsvTa1yuTdANWimw@mail.gmail. com>
> > 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
Khushboo
В списке pgadmin-hackers по дате отправления: