Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iD8T3-0001Ut-7j for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 25 Sep 2019 14:40:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iD8T2-00057C-3h for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 25 Sep 2019 14:40:32 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1iD8T1-00054S-QB for pgsql-pkg-yum@lists.postgresql.org; Wed, 25 Sep 2019 14:40:31 +0000 Received: from mail-io1-xd2f.google.com ([2607:f8b0:4864:20::d2f]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iD8Sz-0005BX-ET for pgsql-pkg-yum@postgresql.org; Wed, 25 Sep 2019 14:40:31 +0000 Received: by mail-io1-xd2f.google.com with SMTP id r26so14411170ioh.8 for ; Wed, 25 Sep 2019 07:40:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ot63WfWYf1I1y/msS0NimLqppaNjrFyzd9JKA4K69Ls=; b=XbKZx2tPmQ/eNIvVXQtHoIg+BeMt2YLPIVATyq+xvlsyJMHRbFO+b2C1YolCZq8xVQ yDqY2EvvOHAumQIoVwsLIj4kOWcH8fOJ8Gmu/WvaZFP07+fRy/jWb0kOgGM3VoOSIZ6W TxcpLRlL1prRXocDTHjXDcsM3q8dlcFRvS1n4Y5qAXhBFwAb8QL/6Z2yCNE4fqmtrfC0 KsRkB1hfmOily8lfjGuhPmehyzXQT9QMFMAw8+uIYFB1youH472YKz+XF/A3I0iM0QrM bdG9Q1g8GbDoRuHTCNiFz3Mxe46rUNulaQLrWkbA9wkDSLORjirgAA+wo0QQXjZBP3gM HRuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ot63WfWYf1I1y/msS0NimLqppaNjrFyzd9JKA4K69Ls=; b=JLvrxq0JF+nK2ASQRRgPH2Rt+DUasdiHpeAvKLvHfJRH7/FNQIHbKx5zyOTOB6NIdW eFahRoWi0evXt97cmVTrghSisAJ4HhjZ2ORUByctSBx6n958QJB/W/7hLUpEBDAZ5oUq aaE/Z+vwGljdTfIwUatOCgd6OZYlfpwcmaFtISHFVeh4bdzyCPFB6aRv+O0bbTuL7D9D MsnXqYE64YHtLaAF4/B1t9EuMGZPDsXiUcrhwQLA8IjQGZGhnEDVpcogCsOqHl1II0hl cQ3sbqvgVNJfyFjaLm9O9JvDpUCRYvtPMn3nu2dhNySttsW1bvYjO4ZDz1tGxRMjHFYj hY4w== X-Gm-Message-State: APjAAAVYLIp2loF/gOJC0uNBcwFNDAB8qDLQGnBHE33NEseJCuTvuPH9 rtHDQOJypB/vJLmYzXjHJp+p4kc0LlY7eVh+T94= X-Google-Smtp-Source: APXvYqzruYbh4RxvyGzBnrWqHd0WVUJXn/MRQnPM5he+3VGJmv7RLjDDiX0gmTPYMdNrokujG3LcAuRfUaI51v2Y8sQ= X-Received: by 2002:a6b:8e57:: with SMTP id q84mr9548287iod.41.1569422427244; Wed, 25 Sep 2019 07:40:27 -0700 (PDT) MIME-Version: 1.0 References: <20190913213909.GA22849@telsasoft.com> <3ac9fab65998527517ec0b604e2b1ea5b2526ee3.camel@gunduz.org> <20190924225425.GA4242@telsasoft.com> In-Reply-To: <20190924225425.GA4242@telsasoft.com> From: Joe McEttrick Date: Wed, 25 Sep 2019 10:40:16 -0400 Message-ID: Subject: Re: cannot install postgis30 / rhel7 To: Justin Pryzby Cc: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= , pgsql-pkg-yum@postgresql.org Content-Type: multipart/alternative; boundary="0000000000004750f6059361a27b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000004750f6059361a27b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Confirm fixed for postgis30_10. Thanks! On Tue, Sep 24, 2019 at 6:54 PM Justin Pryzby wrote: > On Tue, Sep 24, 2019 at 10:18:42PM +0100, Devrim G=C3=BCnd=C3=BCz wrote: > > On Fri, 2019-09-13 at 16:39 -0500, Justin Pryzby wrote: > > > --> Processing Dependency: sqlite-libs >=3D 3.7 for package: > proj61-6.1.0- > > > 1.rhel7.x86_64 > > > --> Finished Dependency Resolution > > > Error: Package: proj61-6.1.0-1.rhel7.x86_64 (pgdg10) > > > Requires: sqlite-libs >=3D 3.7 > > > > Pushed new updates to the repo. Can you please test? > > > > They are in 9.4 to 11 (both stable and testing repos) and v12 (testing) > > repositories. > > Confirmed I was able to install postgis30_11 (but didn't test the upgrade= , > since we already worked around it to be able to install 12b4). > > I think maybe the version number will sort wrong, same as the issue I > reported > with postgresql12-12beta1: > |postgis30_11-3.0.0alpha4-4.rhel7.x86_64 > > Maybe it should be ~alpha4 or something? > > On Thu, May 23, 2019 at 09:55:00AM -0500, Justin Pryzby wrote: > > I'm wondering how versioning on PGDG RPMs is intended to work. > > Yum seems to thinks that the "nightly builds" are of higher version > number than > > beta. > > > > [pryzbyj@dev ~]$ yum list --enablerepo=3D'pgdg12-updates-testing' > --showdu postgresql12 > > ... > > Installed Packages > > postgresql12.x86_64 > 12.0-devel_20190502_1PGDG.rhel7 > @pgdg12-updates-testing > > Available Packages > > postgresql12.x86_64 > 12beta1-1PGDG.rhel7 > pgdg12-updates-testing > > > > [pryzbyj@dev ~]$ sudo yum --enablerepo=3Dpgdg12-updates-testing install > postgresql12{-server,-debuginfo,-contrib} #12beta1-1PGDG.rhel7.x86_64 > > Package matching postgresql12-server-12beta1-1PGDG.rhel7.x86_64 already > installed. Checking for update. > > Package matching postgresql12-debuginfo-12beta1-1PGDG.rhel7.x86_64 > already installed. Checking for update. > > Package matching postgresql12-contrib-12beta1-1PGDG.rhel7.x86_64 alread= y > installed. Checking for update. > > Nothing to do > > > > I made it work like this: > > [pryzbyj@dev ~]$ sudo yum --enablerepo=3Dpgdg12-updates-testing downgra= de > postgresql12{,-libs,-server,-debuginfo,-contrib}-12beta1-1PGDG.rhel7.x86_= 64 > > > > ..which seems to prove that's what's going on. > > > > I recall that debian handles that using "~", like 12~beta1. > > > > At least, it should be called 12devel and 12beta1 for consistency? Or > > 12.0devel and 12.0beta1. > > > --0000000000004750f6059361a27b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Confirm fixed for postgis30_10.

Thanks!=

On Tue, Sep 24, 2019 at 6:54 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
On Tue, Sep 24, 2019 at 10:18:42PM= +0100, Devrim G=C3=BCnd=C3=BCz wrote:
> On Fri, 2019-09-13 at 16:39 -0500, Justin Pryzby wrote:
> > --> Processing Dependency: sqlite-libs >=3D 3.7 for package= : proj61-6.1.0-
> > 1.rhel7.x86_64
> > --> Finished Dependency Resolution
> > Error: Package: proj61-6.1.0-1.rhel7.x86_64 (pgdg10)
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Requires: sqlite-libs &g= t;=3D 3.7
>
> Pushed new updates to the repo. Can you please test?
>
> They are in 9.4 to 11 (both stable and testing repos) and v12 (testing= )
> repositories.

Confirmed I was able to install postgis30_11 (but didn't test the upgra= de,
since we already worked around it to be able to install 12b4).

I think maybe the version number will sort wrong, same as the issue I repor= ted
with postgresql12-12beta1:
|postgis30_11-3.0.0alpha4-4.rhel7.x86_64

Maybe it should be ~alpha4 or something?

On Thu, May 23, 2019 at 09:55:00AM -0500, Justin Pryzby wrote:
> I'm wondering how versioning on PGDG RPMs is intended to work.
> Yum seems to thinks that the "nightly builds" are of higher = version number than
> beta.
>
> [pryzbyj@dev ~]$ yum list --enablerepo=3D'pgdg12-updates-testing&#= 39; --showdu postgresql12
> ...
> Installed Packages
> postgresql12.x86_64=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A012.0-devel_20190502_1PGDG.rhel7=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0@pgdg12-updates-testing
> Available Packages
> postgresql12.x86_64=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A012beta1-1PGDG.rhel7=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pgdg12-updates-testing
>
> [pryzbyj@dev ~]$ sudo yum --enablerepo=3Dpgdg12-updates-testing instal= l postgresql12{-server,-debuginfo,-contrib} #12beta1-1PGDG.rhel7.x86_64
> Package matching postgresql12-server-12beta1-1PGDG.rhel7.x86_64 alread= y installed. Checking for update.
> Package matching postgresql12-debuginfo-12beta1-1PGDG.rhel7.x86_64 alr= eady installed. Checking for update.
> Package matching postgresql12-contrib-12beta1-1PGDG.rhel7.x86_64 alrea= dy installed. Checking for update.
> Nothing to do
>
> I made it work like this:
> [pryzbyj@dev ~]$ sudo yum --enablerepo=3Dpgdg12-updates-testing downgr= ade postgresql12{,-libs,-server,-debuginfo,-contrib}-12beta1-1PGDG.rhel7.x8= 6_64
>
> ..which seems to prove that's what's going on.
>
> I recall that debian handles that using "~", like 12~beta1.<= br> >
> At least, it should be called 12devel and 12beta1 for consistency?=C2= =A0 Or
> 12.0devel and 12.0beta1.


--0000000000004750f6059361a27b--