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 1flDcr-00023Z-TY for pgsql-general@arkaria.postgresql.org; Thu, 02 Aug 2018 13:26:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1flDcq-0005Kj-6C for pgsql-general@arkaria.postgresql.org; Thu, 02 Aug 2018 13:26:44 +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 1flDcp-0005Kb-SZ for pgsql-general@lists.postgresql.org; Thu, 02 Aug 2018 13:26:43 +0000 Received: from mail-lj1-x242.google.com ([2a00:1450:4864:20::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1flDcm-0005pB-Ha for pgsql-general@postgresql.org; Thu, 02 Aug 2018 13:26:43 +0000 Received: by mail-lj1-x242.google.com with SMTP id q127-v6so1901421ljq.11 for ; Thu, 02 Aug 2018 06:26:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zqUuu6Dy94dp459LZNgkuTq7ciboWtSglz0OAagMR9g=; b=pgOQ4eiIH/jC2ryU5A99WYQN4yVDujvPsN4qkTHjwy4EvAZBTXMEHMfpcM/VtA/hgv tzvCwuvKV/K8QH0Fs38//V28h2sOuKq/kAJzqxU4JPGbEe5YJz2EHP6HiSYXQxxavM/I WroMfI+uvUGZprQ0fOFU59DeVYLm2YFJeUVid94itxUCS9/8y9Lp68neOv2miyVygLn6 2d1RMaAHhSsxo8IFCNWnFBnFe6GSBDZmwqxDcbKR/259meE6Vsu2p0gnDDq4CcGh8HtO XLVOWO2lO8U07W9/zlF5/JUhaykjvOtATUYEWR1EmjQp6Qnn48UkLPQGqrgSrEGnAhHq NmEA== 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=zqUuu6Dy94dp459LZNgkuTq7ciboWtSglz0OAagMR9g=; b=qAm6SLJJhUwial6dV6kqLC/yOCkCqgsbdioUpq+Qnjo2kA7G0wxf1T0piAfohHVayL XpaU4Kr8Pu35CxH2tIC5wbc93TcXoGAMlpJ4eNPaH06OcAd02beURqMAYaRTEIzjAGDz O+IQMcHD+UQsKLKZKBf3Cvubs3kMYklOrX8rWA2wymYUS20Gyvshx8Dxl4sS58m6/sZg OXeWLbeempa3I1DLhmjn6qCVlZvO+l96XiM+KijfnnoXFCia+q7D1cUHuUsWKkw1G7v6 wSmrlIW1bvAxTCRTOGL83CGz5V6zW403Rvd4RXY6F/0lbEVfmZTKUj1ri7eS0ZIfB/ME qbnw== X-Gm-Message-State: AOUpUlE7pzA0Bit9jAhzERQOf5c+fLcESuAh2EEK0atfl+CvIF7TKgHB x4R95B6wAXh25tnpfeFV6R22eahCFcpMqgKadKK0fqnZ X-Google-Smtp-Source: AAOMgpeNjx9hGdXc5cI1vWufgUAQSoYS2zor5gFVApRQUnD/YWOUzleI2loH3N0L9NvPVHug7ezm8HS5x/fQEoOH93M= X-Received: by 2002:a2e:5f89:: with SMTP id x9-v6mr2229557lje.16.1533216399274; Thu, 02 Aug 2018 06:26:39 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:c40c:0:0:0:0:0 with HTTP; Thu, 2 Aug 2018 06:26:38 -0700 (PDT) In-Reply-To: <6c09d174-7f63-5e84-fedb-31ddbb74a3c6@aklaver.com> References: <6c09d174-7f63-5e84-fedb-31ddbb74a3c6@aklaver.com> From: Alexandru Lazarev Date: Thu, 2 Aug 2018 16:26:38 +0300 Message-ID: Subject: Re: Who and How is responsible for released installations packages and 3rd party packs? (e.g. on https://yum.postgresql.org/9.6/redhat/rhel-7.3-x86_64/) To: Adrian Klaver , pgsql-pkg-yum@lists.postgresql.org Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000d7b51c057273c229" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000d7b51c057273c229 Content-Type: text/plain; charset="UTF-8" What about 3rd party libraries like plv8 - Who and How (based on which criteria, which versions) build RPM and upload them there? + adding more relevant mail list On Thu, Aug 2, 2018 at 3:47 PM, Adrian Klaver wrote: > On 08/01/2018 10:53 PM, Alexandru Lazarev wrote: > >> Hi PG Community, >> >> In my company I found that PG Installation on deployed OS Images are >> takne from here: https://yum.postgresql.org/9.6/redhat/rhel-7.3-x86_64/ >> >> We are using PG 9.6.5 or 9.6.7 + pgpool + plv8 + others >> >> Some or RPMs for CentOS are taken from that URL (PG Installation, plv8). >> >> My question is: >> Who is building RPMs and uploading to that URL? What are the criteria to >> build one RPM or other and their versions? >> > > https://www.postgresql.org/download/linux/redhat/ > > https://yum.postgresql.org/ > > > Why I am asking: >> I saw on URL there are PG 9.6.8 and 9.6.9 - Are there maintained only >> latest 2 build releases? >> >> plv8 - there are versions 2.0.0-1 and 2.1.0, since latest plv8 are >> already 2.3.7 and latest for 2.1.X is 2.1.3 contating major fixes >> >> >> Thanks, >> AlexL >> > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > --000000000000d7b51c057273c229 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
What about 3rd party libraries like plv8 - Who and Ho= w (based on which criteria, which versions) build RPM and upload them there= ?

+ adding more relevant mail list
=

On Thu, Aug 2, 20= 18 at 3:47 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 08/01/201= 8 10:53 PM, Alexandru Lazarev wrote:
Hi PG Community,

In my company I found that PG Installation on deployed OS Images are takne = from here: https://yum.postgresql.org/9.6= /redhat/rhel-7.3-x86_64/

We are using PG 9.6.5 or 9.6.7 + pgpool + plv8 + others

Some or RPMs for CentOS are taken from that URL (PG Installation, plv8).
My question is:
Who is building RPMs and uploading to that URL? What are the criteria to bu= ild one RPM or other and their versions?

https://www.postgresql.org/download/lin= ux/redhat/

https://yum.postgresql.org/

Why I am asking:
I saw on URL there are PG 9.6.8 and 9.6.9 - Are there maintained only lates= t 2 build releases?

plv8 - there are versions 2.0.0-1 and 2.1.0, since latest plv8 are already = 2.3.7 and latest for 2.1.X is 2.1.3 contating major fixes


Thanks,
AlexL


--
Adrian Klaver
adrian.klave= r@aklaver.com

--000000000000d7b51c057273c229--