Re: pgAdmin 3.0 builds - Mailing list pgadmin-hackers

Hi

On Thu, Apr 12, 2018 at 2:29 PM, Joao De Almeida Pereira <jdealmeidapereira@pivotal.io> wrote:

Hi Dave,

Did you remove the folder with the builds?

Yes, when I re-built everything. It's now at: https://developer.pgadmin.org/~dpage/v3.0-2/

 

What is the git SHA from which the release is going to be created from?

79edf40141b5886634ef71fb5bf14ec076e2adaf

I'll push the REL-3_0 tag, once Fahar tells me everything looks good (expected to be later today, formal release tomorrow AM).

 

Thanks

Joao

On Thu, Apr 12, 2018 at 4:08 AM Dave Page <dpage@pgadmin.org> wrote:

Hi

On Wed, Apr 11, 2018 at 6:08 PM, Christoph Berg <myon@debian.org> wrote:

Re: Dave Page 2018-04-11 <CA+OCxoxVsHpmYz0rXAq+E5+3GXoHW0oiTv-ha4_ssn+23A0D3w@mail.gmail.com>
> New builds are at https://developer.pgadmin.org/~dpage/v3.0-2/.
>
> These fix the Windows crash that Fahar found (which happened if the user
> had a space in their usename), and fix password encryption/decryption under
> Python 3.
>
> Apologies for the inconvenience again. I still hope to release tomorrow,
> but let me know if that's not enough time and I can do Friday instead.

I won't be able to create the Debian packages this week because I'm at
pgconf.de.

No problem.

 

> >> - This release removes dependencies on QtWebKit and/or QtWebEngine, and
> >> uses the users default browser instead.

This would need more testing anyway.

Should be pretty straightforward - in RPM terms it's a one-line change to remove a "Requires" line from the spec file. Updates to the other dependency packages will almost certainly take a lot more time unfortunately.

 

> >> - Gnome 3.26 or above will require the TopIcons Plus extension to be
> >> installed (or an equivalent). Ubuntu already seems to have this, per my
> >> testing. Fedora does not.

Hmm. This seems to be very desktop specific. What if the user isn't
using Gnome at all?

From my research, Gnome seems to be the only window manager where this is an issue (it seems to be quite a controversial change). We will be working on a better, more permanent solution in the future, however that's a lot of effort, and not something we could hold up 3.0 for.

Thanks. 

--

Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

--

Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company