Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fY5pF-0002LL-OE for pgadmin-hackers@arkaria.postgresql.org; Wed, 27 Jun 2018 08:29:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fY5pC-0005VR-TB for pgadmin-hackers@arkaria.postgresql.org; Wed, 27 Jun 2018 08:29:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fY5pC-0005VK-OU for pgadmin-hackers@lists.postgresql.org; Wed, 27 Jun 2018 08:29:14 +0000 Received: from mail-wr0-x234.google.com ([2a00:1450:400c:c0c::234]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fY5p8-0003Uv-PA for pgadmin-hackers@postgresql.org; Wed, 27 Jun 2018 08:29:13 +0000 Received: by mail-wr0-x234.google.com with SMTP id l2-v6so514357wro.7 for ; Wed, 27 Jun 2018 01:29:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PjnnTk2sZP9dVsPcv4a/ifAEltiV8OWC/g8M0PTRBcY=; b=bnvVGn+yFPC7B43qpZ03IT3/ZMCtD8yZ5x017HWKFMLJlI0jL1wu5r/8CEP2cH6j0x v/SMEgpTei5Wy9WsDl6HcdFZGW8O0ps3d74Fk+aBjmmnygRvBMcRg3pxiceD649AcJjw rWo1Vc0SGZrq6JR2fNCBIxYtQAy88rSv2UC7AxpCAkPeQeRHpyB6P988SnV2oK/+HhP/ hukHT5RCL8GsNV98zGM/fz8YRLXhKurfcIMP6rbbcYODowtVhlpn4m23TZI27wit+HFf nVUO6q9ERzPenxdwllF/rDXknE0ssiL7NIPoaHa+RidJnQbuTsgwp2UzsIJ6NLAfBTkJ JMtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PjnnTk2sZP9dVsPcv4a/ifAEltiV8OWC/g8M0PTRBcY=; b=pfWoOI42CwubdIazDscWax4H/M90KfCV/NZ//WqhYae+UEZkVrxhVBLJdJd8oO+K9L cXJHxqxxm5EK/mFaYo0PjQFRR6QeiyKB00cgCphU675lYYyMng/gjoY9aIEjYwveTkUH Y6uzonCRzJ+aZY3S0JXA0neJ3AWaQiHY4Ftf2EuXNRMI/DvM/DK8IfezCMT8jMrU3owh Gbg39lt1ySWvqyWJmrd6yiWYRLUU1ZYSVtKE0vsfmlZ5r0ZpGbGcDO1rGVS1TDl/wHY2 SIG8Sl1GjURSsmFsXMldLCgaEOR08fEbq/8NpupiOJeVX9UcZMD64DpiOyVX6y4VrHIY 2lgg== X-Gm-Message-State: APt69E0AcvSGP7zLv9Qee0yO8p6pnxCE5kI/utC7TeO2jXgrIIT7wd4s hn+8N+l+FsLhSf+A6vagt+2P1aWFHI6z3r7fZ0SWxg== X-Google-Smtp-Source: AAOMgpegMoJUs7nZLsDDikii3p5nOCZPPzynuWFc9PNy3ioOcS/fIN87GHylncEqn6+8NpIhdwtE5LnAgibtCgPordU= X-Received: by 2002:adf:e590:: with SMTP id l16-v6mr4015953wrm.190.1530088148642; Wed, 27 Jun 2018 01:29:08 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1c:2907:0:0:0:0:0 with HTTP; Wed, 27 Jun 2018 01:29:07 -0700 (PDT) In-Reply-To: <20180626192819.GA32582@msg.df7cb.de> References: <20180626192819.GA32582@msg.df7cb.de> From: Dave Page Date: Wed, 27 Jun 2018 09:29:07 +0100 Message-ID: Subject: Re: pgAdmin v3.1 candidate builds and source... To: Christoph Berg Cc: Syed Fahar Abbas , =?UTF-8?B?RGV2cmltIEfDnE5Ew5xa?= , pgadmin-hackers Content-Type: multipart/alternative; boundary="00000000000093632e056f9b6816" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000093632e056f9b6816 Content-Type: text/plain; charset="UTF-8" On Tue, Jun 26, 2018 at 8:28 PM, Christoph Berg wrote: > Re: Dave Page 2018-06-26 RD6QNxA5ynH-X+-rPN7jA@mail.gmail.com> > > ... can be found at https://developer.pgadmin.org/builds/2018-06-26-3.1/ > > and dpage/pgadmin4:2018-06-26-3.1 on Docker Hub. > > > > Fahar; please verify for release on Thursday. > > > > Note that these are the first builds from the new fully automated build > > system, and both the Windows and Mac versions now use Python 3, so please > > be sure to test with extra care! > > Hmm, ModuleNotFoundError: No module named 'sshtunnel' > > Could you perhaps announce new versions that need new python modules a > bit earlier, so we have time to package them? > Good point. Not entirely sure how the mechanics of that would work, given that we're trying to shorten release cycles down to a couple of weeks (ideally). That said, for all other builds we're giving up trying to maintain Python packages. Instead, we're going to be shipping a pre-built Python venv as part of the package, built using Python 3.6. Whilst it's not perfect from a "following the packaging rules" perspective, in other cases we're having to install modules privately for pgAdmin anyway to avoid conflicts with older, vendor supplied versions, so it's really just a different evil rather than a new one. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --00000000000093632e056f9b6816 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Jun 26, 2018 at 8:28 PM, Christoph Berg <<= a href=3D"mailto:myon@debian.org" target=3D"_blank">myon@debian.org>= wrote:
Re: Dave Page 2018-06-26 &= lt;CA+OCxow1BDDXK9K1d-pnSAoBE5O=3D+RD6QNxA5ynH-X+-rPN7jA@mail.gmail.com> > ... can be found at https:= //developer.pgadmin.org/builds/2018-06-26-3.1/
> and dpage/pgadmin4:2018-06-26-3.1 on Docker Hub.
>
> Fahar; please verify for release on Thursday.
>
> Note that these are the first builds from the new fully automated buil= d
> system, and both the Windows and Mac versions now use Python 3, so ple= ase
> be sure to test with extra care!

Hmm, ModuleNotFoundError: No module named 'sshtunnel'

Could you perhaps announce new versions that need new python modules a
bit earlier, so we have time to package them?

Good point. Not entirely sure how the mechanics of that would work, = given that we're trying to shorten release cycles down to a couple of w= eeks (ideally).

That said, for all other builds we= 're giving up trying to maintain Python packages. Instead, we're go= ing to be shipping a pre-built Python venv as part of the package, built us= ing Python 3.6. Whilst it's not perfect from a "following the pack= aging rules" perspective, in other cases we're having to install m= odules privately for pgAdmin anyway to avoid conflicts with older, vendor s= upplied versions, so it's really just a different evil rather than a ne= w one.=C2=A0

--
Dave Page
Blog: http://pgsnake.blogspot.com<= br>Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterpri= se PostgreSQL Company
--00000000000093632e056f9b6816--