Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d4C9Q-0004Im-Md for pgsql-pkg-yum@arkaria.postgresql.org; Fri, 28 Apr 2017 20:06:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d4C9O-0007k6-Td for pgsql-pkg-yum@arkaria.postgresql.org; Fri, 28 Apr 2017 20:05:58 +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.84_2) (envelope-from ) id 1d4C9O-0007jw-GV for pgsql-pkg-yum@postgresql.org; Fri, 28 Apr 2017 20:05:58 +0000 Received: from mail-io0-x233.google.com ([2607:f8b0:4001:c06::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1d4C9K-0003yn-Dw for pgsql-pkg-yum@postgresql.org; Fri, 28 Apr 2017 20:05:57 +0000 Received: by mail-io0-x233.google.com with SMTP id a103so74416618ioj.1 for ; Fri, 28 Apr 2017 13:05:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=crunchydata-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=1LNz/ryE+goB788AbtyzvUUVm5FaD2T3w8TD2PGMMvI=; b=YtqdzW4HRBpClJ09M+TMOlTAE2LKCI4fNOVYSH120y3NvQIJc2Dn3QWjbR/tOHaM2S MVgS3Xi0bWCmVANbockZUuvTwDhCtViwEFTntidzUuHdKPM3uH0KNommHsQ4LQfw6zlv dOm8UcK8wQQ1weYRmKJZbNV61FPrKOOy43+HbFbtd024HBfUDUR873Ga862pM0a6GpoQ 5es0Vb5F986xcW3YroX1jmrgGtJAfZmRHNJhpdbZXgI9+SNqg84eDzOXAfrXUyH8u1Gt S3F5W795dbP2gn4/yDshjcUU36Z0cnyKw9+HgS4XBN2nIf1xXRISxJ5jbPOqMGVFehb4 ZvRA== 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; bh=1LNz/ryE+goB788AbtyzvUUVm5FaD2T3w8TD2PGMMvI=; b=QYdMoV5E6Fw1rkVEZ1QY8xyY98dA8VNw7qtXYrX8WcwEAWo9MgbMSA3Q930iq5U33Z MJNelCh6uVRuiN0ZOXpiB2s/xqEeADC2Qw1caATFeyZnvqXmlAV/8dnIyTMrAUrKppSC 5I5wWlifjHTIaXrUVKesq+ouci9zqEbxGz5JVkJW+7ulGt4Zi4QX6Ju45uiO1V8ZujaL 2dEeEMHefP3doJryFtNeWsp0sbVPRfBRduO0z5A1R3fJlw7nsvwpt3DA5747MgU2svMN bahEqoBK3bZR2rArpgZGvyWeSlOHsqe8lBXPQy0t84cEKon3etj2pBaVj6WrTB/mEBsy JpQg== X-Gm-Message-State: AN3rC/5T5vNPjkxjUHs0sIdrgdar2GyoD3maB8cL1i8uoLttUWLbUNFA dd/Gnvz4QRF3m0qtFO+lbcbp5fpieg== X-Received: by 10.157.46.44 with SMTP id q41mr4777753otb.129.1493409952382; Fri, 28 Apr 2017 13:05:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.115.69 with HTTP; Fri, 28 Apr 2017 13:05:11 -0700 (PDT) In-Reply-To: <1493386507.11169.12.camel@gunduz.org> References: <1493289313.3032.46.camel@gunduz.org> <1493386507.11169.12.camel@gunduz.org> From: John Harvey Date: Fri, 28 Apr 2017 16:05:11 -0400 Message-ID: Subject: Re: pgadmin4 RPM broken? To: pgsql-pkg-yum Content-Type: multipart/alternative; boundary=001a113ddb94b7570d054e3f99d4 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-yum Precedence: bulk Sender: pgsql-pkg-yum-owner@postgresql.org --001a113ddb94b7570d054e3f99d4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Devrim, Thanks for putting all of the changes in. They all work great! On Fri, Apr 28, 2017 at 9:35 AM, Devrim G=C3=BCnd=C3=BCz wrote: > > > 4) When I try building with the current pgadmin4 specfile on RHEL7, I g= et > > an error at patch-time: > > Reversed (or previously applied) patch detected! Assume -R? [n] > > > > I'm not sure why this occurs. I'll keep investigating. > > Can't reproduce -- can you please clean up your repo and try again? I keep seeing it even in a clean repo, but I'll try to dig a little deeper. It could definitely be something in my environment. I'll try to provide more helpful information if it is something that's a problem. I found two more specfile recommendations today after some more testing: 1) I would suggest adding "BuildRequires: pgadmin4-python-simplejson" to the pgadmin4 specfile. Without it, I see this trace in the build log: Generating code-snippet.rst for some of the important classes... Traceback (most recent call last): File "build_code_snippet.py", line 61, in from pgadmin.browser.utils import NodeView File "pgadmin4/BUILD/pgadmin4-1.3/web/pgadmin/browser/__init__.py", line 19, in from pgadmin.settings import get_setting File "pgadmin4/BUILD/pgadmin4-1.3/web/pgadmin/settings/__init__.py", line 19, in from pgadmin.utils.ajax import make_json_response, bad_request File "pgadmin4/BUILD/pgadmin4-1.3/web/pgadmin/utils/ajax.py", line 15, in import simplejson as json ImportError: No module named simplejson make[1]: [code_snippet] Error 1 (ignored) sphinx-build -b html -d _build/doctrees . _build/html The build continues even with the failure, but my guess is that it's not ideal. 2) I think that two Requires lines may need to change, specifically around python-itsdangerous Requires: python3-itsdangerous >=3D 0.24 Requires: python-itsdangerous >=3D 0.24 On CentOS 7, python-itsdangerous-0.23-2.el7.noarch is available from the @extras packages On RHEL 7, python-itsdangerous-0.23-2.el7.noarch is available from the @rhel-7-server-extras-rpms packages Unfortunately, these are too low of a version. I'm guessing we want to use the PGDG-built version. I think that these lines should actually now be moved to: Requires: pgadmin4-python-itsdangerous >=3D 0.24 Is that a correct assumption? After making those two modifications (and ignoring the patchfile, which I'm investigating), I am able to build and install pgadmin4 successfully with the new specfile, which is pretty awesome. Thanks! -John --001a113ddb94b7570d054e3f99d4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Devrim,

Thanks for putting all of the changes in.=C2=A0 They all w= ork great!

O= n Fri, Apr 28, 2017 at 9:35 AM, Devrim G=C3=BCnd=C3=BCz &= lt;devrim@gunduz.org= > wrote:
> 4) When I try building with the current pgadmin4 specfile on RHE= L7, I get
> an error at patch-time:
> Reversed (or previously applied) patch= detected!=C2=A0 Assume -R? [n]
>
> I'm not sure why this occurs.=C2=A0 I'll keep investigating.
Can't reproduce -- can you please clean up your repo and try aga= in?

I keep seeing it even in a clean repo, = but I'll try to dig a little deeper.
It could definitely be s= omething in my environment.
I'll try to provide more helpful = information if it is something that's a problem.


I found two more specfile recommendations today after som= e more testing:

1) I would suggest adding "Bu= ildRequires: pgadmin4-python-simplejson" to the pgadmin4 specfile.

Without it, I see this trace in the build log:
<= div>
Generating code-snippet.rst for some of the importa= nt classes...
Traceback (most recent call last):
=C2=A0= File "build_code_snippet.py", line 61, in <module>
=C2=A0 =C2=A0 from pgadmin.browser.utils import NodeView
=C2= =A0 File "pgadmin4/BUILD/pgadmin4-1.3/web/pgadmin/browser/__= init__.py", line 19, in <module>
=C2=A0 =C2=A0 from pg= admin.settings import get_setting
=C2=A0 File "pgadmin4/BUIL= D/pgadmin4-1.3/web/pgadmin/settings/__init__.py", line 19, i= n <module>
=C2=A0 =C2=A0 from pgadmin.utils.ajax import mak= e_json_response, bad_request
=C2=A0 File "pgadmin4/BUILD/pgadmin4-1.3/web/pgadmin/utils/ajax.py", line 15, in <module= >
=C2=A0 =C2=A0 import simplejson as json
ImportErro= r: No module named simplejson
make[1]: [code_snippet] Error 1 (ig= nored)
sphinx-build -b html -d _build/doctrees =C2=A0 . _build/ht= ml

The build continues even with the failure= , but my guess is that it's not ideal.


2) I think that two Requires lines may need to change, specifically= around python-itsdangerous

Requires: =C2=A0 =C2= =A0 =C2=A0 python3-itsdangerous >=3D 0.24
Requires: =C2=A0= =C2=A0 =C2=A0 python-itsdangerous >=3D 0.24

On CentOS 7, python-itsdangerous-0.23-2.el7.noarch is available from= the @extras packages
On RHEL 7, python-itsdangerous-0.23-2.= el7.noarch is available from the @rhel-7-server-extras-rpms packages
<= div>Unfortunately, these are too low of a version.=C2=A0 I'm guessing w= e want to use the PGDG-built version.

I think that= these lines should actually now be moved to:
Requires: =C2=A0 = =C2=A0 =C2=A0 pgadmin4-python-itsdangerous >=3D 0.24

<= /div>
Is that a correct assumption?


=
After making those two modifications (and ignoring the patchfile, whic= h I'm investigating), I am able to build and install pgadmin4 successfu= lly with the new specfile, which is pretty awesome.

Thanks!
=C2=A0 -John
--001a113ddb94b7570d054e3f99d4--