Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtfiS-00DToU-PP for pgsql-admin@arkaria.postgresql.org; Fri, 20 Oct 2023 02:58:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qtfiQ-00BkDU-4Y for pgsql-admin@arkaria.postgresql.org; Fri, 20 Oct 2023 02:58:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qtfiP-00BkDM-Gc for pgsql-admin@lists.postgresql.org; Fri, 20 Oct 2023 02:58:22 +0000 Received: from mail-yb1-xb35.google.com ([2607:f8b0:4864:20::b35]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qtfiI-001M9D-FA for pgsql-admin@lists.postgresql.org; Fri, 20 Oct 2023 02:58:20 +0000 Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-d9c687f83a2so359345276.3 for ; Thu, 19 Oct 2023 19:58:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697770693; x=1698375493; darn=lists.postgresql.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=XqT8xwJ6O/n++sio6nnvP+Xb63Q9CvfLQfueVwtx2pg=; b=kAHKsm+luTh/8nXRUp46XYQc0aDt2/oL0ZmkYCJeoRZVpIlMoxUWka6Xm2NTdn6NfI S/5/5C3X1kneWvVLx1loH3JDwm/qMfLAFeG07ookwuUGMZza7jvmRd/OVps9RZAT+BM7 OdXfdWI3GNZiOJRT/oODlVdPo1vyfYVdMA2TQ3Kuy4I3W6ytqreuRa9+C2P+SAcxEh6F ANbMBKOlkZ4FF/DogUao0H/uQdm3Pp7yzDLe9wGs7OxnWD+q25LwTq2aefKXomcuuDM2 Y3bpyCDv11KdHXebVpftRtwBEFHZKpPo00dYnjv5eb8OJUXfsCRCkJWyiYDSxiDLoEqY aAXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697770693; x=1698375493; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=XqT8xwJ6O/n++sio6nnvP+Xb63Q9CvfLQfueVwtx2pg=; b=lnrbgLiLVjT39Tbb7kNte26J/T4fYS8EVYIB/flmPW34xqYfC4K7q4fbe0Z9qELXrt e/PvYtOI/A5xvAXk+gBDqS4yYHSxAmEfh0cg/U7ISq2Uo2kD4w8UAul3ySUdqc316XgF Yu+L62usH47u5q87nqRST+0ES+eouPPuTpQ5Jh930SSDv2l1PeHNIkbNu7AW+2nrjyrr 69WSn4BO9g2c4Up6oq48yVN4O9Rp5TpyFGZiG5Z7DrEXhRI0IuO+VaejWi7h2Uyy9bKB TVn7SFYtV0wVVXYwo+7D/wkHgaVBUpVs8ikJb3pptE6NKAGa2eTSAPImzlSSU+UiWfQ7 R12g== X-Gm-Message-State: AOJu0YzMi/HTrbQ80JH1I+xRW4aujQbOIPLZsbaUe5bjp72GQiGibD7m YZbBL2vsJ7nShvQpj7u1wIyCM0sCMG4= X-Google-Smtp-Source: AGHT+IHQvv8Fb4GogUS/3MFYy3BNWjP3iJxwsk5gEQLQl9+fy8YGEQXrLkjumQ3peNT0H8CwJHPu/g== X-Received: by 2002:a5b:891:0:b0:d9a:c8fe:2658 with SMTP id e17-20020a5b0891000000b00d9ac8fe2658mr629331ybq.34.1697770693331; Thu, 19 Oct 2023 19:58:13 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:d509:606b:cffe:5a41? ([2600:1700:bd2c:b810:d509:606b:cffe:5a41]) by smtp.googlemail.com with ESMTPSA id u1-20020a25ab01000000b00d9cc49edae9sm256305ybi.63.2023.10.19.19.58.12 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Oct 2023 19:58:12 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------Il0N8MWtt0tWokwi1EVFbnn8" Message-ID: <0b63f7bb-01dc-4c96-8179-8039fa608b71@gmail.com> Date: Thu, 19 Oct 2023 21:58:12 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Binaries for EOL version? Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: <0aeb11d2-039b-edff-1514-299652e73936@gmx.net> <3368392.1697736614@sss.pgh.pa.us> <40e90793-744f-4d8a-8b86-82495bc154ce@gmail.com> <52456b74-c817-42b3-91f9-6c656d9413c5@uvic.ca> <1dac15f4-51b3-4aac-bd5c-bf773b64e189@gmail.com> <119cb52d-782c-413f-bd77-e0571abf5161@uvic.ca> From: Ron In-Reply-To: <119cb52d-782c-413f-bd77-e0571abf5161@uvic.ca> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------Il0N8MWtt0tWokwi1EVFbnn8 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/19/23 16:12, Evan Rempel wrote: > I'm not arguing if the yum-archive.postgresql.org should or should not > permit browsing. I'm trying to give you a solution that you can implement > today to acquire the packages that you need. As if I haven't considered that (and instantly dismissed it, since Ubuntu and Windows). > > IMHO I applaud the fact that these packages are more difficult to get than > the currently supported and tested versions. I can't see a reason why > anyone would want to still be running them, but lets give credit where > credit is due. The packages are still available even if I can't see a > reason to run them. If someone needs to install another package in an existing EOL system, they'd need to download that package from the archive. > > Evan. > > On 2023-10-19 14:05, Ron wrote: >> >> A repository is a bunch of web pages.  I can curl every package under >> download.postgresql.org/pub, so why can't we curl every package under >> yum-archive.postgresql.org? >> >> On 10/19/23 15:21, Evan Rempel wrote: >>> No. The original request was for the RPMs from a yum repository. You >>> have to use a yum capable system. >>> >>> >>> On 2023-10-19 13:02, Ron wrote: >>>> >>>> Even Ubuntu and Windows? >>>> >>>> On 10/19/23 14:44, Evan Rempel wrote: >>>>> You can do that on any host and use the yum download only or if you >>>>> want it all use reposync. >>>>> Then you can copy the actual RPMS anywhere you want. >>>>> >>>>> Evan. >>>>> >>>>> On 2023-10-19 12:06, Ron wrote: >>>>>> >>>>>> Ah.  But I can't do that, since the server is behind many firewalls, >>>>>> and only has access to an internal RHEL mirror. >>>>>> >>>>>> The "current" binaries are all accessible via web browser (and curl), >>>>>> so it puzzles me why yum-archive isn't. >>>>>> >>>>>> I opened Redmine issue 7892 to make them available. >>>>>> >>>>>> On 10/19/23 13:38, Evan Rempel wrote: >>>>>>> The packages you need are definitely on the postgresql yum server. >>>>>>> The repository can not be browsed, but if you add the yum repository >>>>>>> definition file as documented at the bottom of the page >>>>>>> https://yum.postgresql.org/repopackages/#pgredhatoldrepos >>>>>>> >>>>>>> you will be able to do a "yum install amcheck_next96" easily. >>>>>>> >>>>>>> cat << EOF > /etc/yum.repos.d/pgdg-96.repo >>>>>>> [pgdg96] >>>>>>> name=PostgreSQL 9.6 RPMs for RHEL/CentOS 6 >>>>>>> baseurl=https://yum-archive.postgresql.org/9.6/redhat/rhel-6-x86_64 >>>>>>> enabled=1 >>>>>>> gpgcheck=0 >>>>>>> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG >>>>>>> EOF >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2023-10-19 10:54, Ron wrote: >>>>>>>> >>>>>>>> On 10/19/23 12:30, Tom Lane wrote: >>>>>>>> [snip] >>>>>>>>> amcheck was not part of the Postgres source tree until v10. >>>>>>>>> It might exist in some form for 9.6, but you'd have to look >>>>>>>>> outside the standard distribution channels >>>>>>>> >>>>>>>> amcheck_next96 binary RPM were absolutely distributed by >>>>>>>> download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-6. >>>>>>>> >>>>>>>> I downloaded amcheck_next96-1.4.1 when I downloaded 9.6.22, but did >>>>>>>> not download amcheck_next96-1.4.5 with 9.6.24. >>>>>>>> >>>>>>>> If push comes to shove, I can probably install the 1.4.1 RPM along >>>>>>>> side 9.6.24. >>>>>>>> >>>>>>>> -- >>>>>>>> Born in Arizona, moved to Babylonia. >>>>> >>>> >>>> -- >>>> Born in Arizona, moved to Babylonia. >>> >> >> -- >> Born in Arizona, moved to Babylonia. > -- Born in Arizona, moved to Babylonia. --------------Il0N8MWtt0tWokwi1EVFbnn8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 10/19/23 16:12, Evan Rempel wrote:
I'm not arguing if the yum-archive.postgresql.org should or should not permit browsing. I'm trying to give you a solution that you can implement today to acquire the packages that you need.

As if I haven't considered that (and instantly dismissed it, since Ubuntu and Windows).


IMHO I applaud the fact that these packages are more difficult to get than the currently supported and tested versions. I can't see a reason why anyone would want to still be running them, but lets give credit where credit is due. The packages are still available even if I can't see a reason to run them.

If someone needs to install another package in an existing EOL system, they'd need to download that package from the archive.


Evan.

On 2023-10-19 14:05, Ron wrote:

A repository is a bunch of web pages.  I can curl every package under download.postgresql.org/pub, so why can't we curl every package under yum-archive.postgresql.org?

On 10/19/23 15:21, Evan Rempel wrote:
No. The original request was for the RPMs from a yum repository. You have to use a yum capable system.


On 2023-10-19 13:02, Ron wrote:

Even Ubuntu and Windows?

On 10/19/23 14:44, Evan Rempel wrote:
You can do that on any host and use the yum download only or if you want it all use reposync.
Then you can copy the actual RPMS anywhere you want.

Evan.

On 2023-10-19 12:06, Ron wrote:

Ah.  But I can't do that, since the server is behind many firewalls, and only has access to an internal RHEL mirror.

The "current" binaries are all accessible via web browser (and curl), so it puzzles me why yum-archive isn't.

I opened Redmine issue 7892 to make them available.

On 10/19/23 13:38, Evan Rempel wrote:
The packages you need are definitely on the postgresql yum server. The repository can not be browsed, but if you add the yum repository definition file as documented at the bottom of the page
https://yum.postgresql.org/repopackages/#pgredhatoldrepos

you will be able to do a "yum install amcheck_next96" easily.

cat << EOF > /etc/yum.repos.d/pgdg-96.repo
[pgdg96]
name=PostgreSQL 9.6 RPMs for RHEL/CentOS 6
baseurl=https://yum-archive.postgresql.org/9.6/redhat/rhel-6-x86_64
enabled=1
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG
EOF




On 2023-10-19 10:54, Ron wrote:

On 10/19/23 12:30, Tom Lane wrote:
[snip]
amcheck was not part of the Postgres source tree until v10. 
It might exist in some form for 9.6, but you'd have to look
outside the standard distribution channels

amcheck_next96 binary RPM were absolutely distributed by download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-6.

I downloaded amcheck_next96-1.4.1 when I downloaded 9.6.22, but did not download amcheck_next96-1.4.5 with 9.6.24.

If push comes to shove, I can probably install the 1.4.1 RPM along side 9.6.24.

--
Born in Arizona, moved to Babylonia.


--
Born in Arizona, moved to Babylonia.


--
Born in Arizona, moved to Babylonia.


--
Born in Arizona, moved to Babylonia.
--------------Il0N8MWtt0tWokwi1EVFbnn8--