Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bsG6Z-00040z-Kv for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 06 Oct 2016 21:21:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bsG6Y-0008Ag-LR for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 06 Oct 2016 21:21:26 +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 1bsG6Y-0008Aa-DU for pgsql-pkg-yum@postgresql.org; Thu, 06 Oct 2016 21:21:26 +0000 Received: from ns5.gunduz.org ([107.170.136.15] helo=ns1.gunduz.org) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bsG6U-0006r3-HK for pgsql-pkg-yum@postgresql.org; Thu, 06 Oct 2016 21:21:25 +0000 Received: from asus-laptop-03-gunduz-org (unknown [88.248.122.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ns1.gunduz.org (Postfix) with ESMTPSA id 8DD753FCFF; Thu, 6 Oct 2016 21:21:19 +0000 (UTC) Message-ID: <1475788875.3515.44.camel@gunduz.org> Subject: Re: Amazon Linux RPM Changes From: Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= To: Jason Petersen , pgsql-pkg-yum@postgresql.org Date: Fri, 07 Oct 2016 00:21:15 +0300 In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-WbuOVEWOqGhbKC7w1Kw0" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 X-Pg-Spam-Score: -4.5 (----) 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 --=-WbuOVEWOqGhbKC7w1Kw0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Jason, On Thu, 2016-10-06 at 14:00 -0600, Jason Petersen wrote: > We install PGDG as part of a CloudFormation template we offer to construc= t > and configure a cluster on EC2. The template included installation of the > pgdg-ami201503-95-9.5-2.noarch.rpm package directly from a PGDG URL. >=20 > Unfortunately, this package was removed, causing deployment issues for us= ers > of our template. While I understand replacing it with the -3 variant (whi= ch > uses HTTPS URLs), I don=E2=80=99t understand why older versions were remo= ved. In > every other Red Hat OS, they remain; seemingly only the Amazon Linux vari= ants > were removed. Apologies, and sorry for the inconvenience. That was not supposed to happen= . We don't have any archives, so cannot see what went wrong :-( If that is the o= nly broken package, I will be more than happy to provide -2.noarch using the sa= me spec. > Why were the older Amazon repo RPMs removed, Again, probably a part of a manual cleanup that I did :( > and what is the policy going forward on their removal? n-2 release, but please note that repo RPMs change *very* rarely under norm= al circumstances: For example, I don't expect any change in next few years, to= be honest, unless postgresql.org infrastructure changes, so I'd rely on the ve= ry latest RPM, but: > Solution? >=20 > I noticed one of the OSes has a -latest.rpm variant. Well, that was a part of a longer term plan, like an installer, but I faile= d to complete, because: (See below) > If this could be provided for all OSes, it makes installation much simpl= er > (it could be implemented by a symlink). We=E2=80=99ve had to write our ow= n scripts > (here > 623df48d/update_dockerfiles#L20-L35> and here > ce9490cd/community/rpm.sh#L107-L146>) to ensure we have the =E2=80=9Crigh= t=E2=80=9D version > for a given Red Hat OS. Being able to append -latest.rpm to all URLs woul= d be > a fantastic improvement and let us remove this knowledge from our codebas= e. I picked up a different route: https://git.postgresql.org/gitweb/?p=3Dpgrpms.git;a=3Dblob;f=3Dscripts/Inst= allPGDGRepoRPM.sh Instead of trying to find the latest, and given that I don't plan to change repo files in foreseeable future, within the script, I created a temp repo which would download and install the repo RPM. See=C2=A0 https://git.postgresql.org/gitweb/?p=3Dpgrpms.git;a=3Dblob;f=3Dscripts/Inst= allPGDGRepoRPM.sh#l102 as an example. For the -latest thing: I am open to any scripting ideas in here. Regards, --=20 Devrim G=C3=9CND=C3=9CZ EnterpriseDB: http://www.enterprisedb.com PostgreSQL Dan=C4=B1=C5=9Fman=C4=B1/Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR --=-WbuOVEWOqGhbKC7w1Kw0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJX9sBLAAoJENjDPf6Sz261emMQAK6/1eaBcp3Xy/db3jVVli2u 3vBU8VzI2MizN2DcMWR/hiGoR7iJCU7nKEfXAsHib3BaDVb3tPVb6TW8gyCPPXiJ mQnd9ZFWtO5KuuYmtwnFWbkU+FC4YpNMvHxYwA42FN1bQcn/FOTL3QAYu+aPlDJb HW3GhzcX6d6mCfLrfZkLU9ZV7KsXCWzllNz/f8Z78HuQkWa6ta972r2+JYzLhynE J/0rCZyGc8c3qEQdY81NyNpNECwZghh7zw9C/z1shbPpZsHMgYqMs2C7xSBA9jv+ 00qy/+P7DYua1vVZLGQKfItkAWT5cXMyRZNIGFH4ZCVS7fNn6RtGdjnYcSCLjCkA fPaM08tDuCjavWqq6r6UlH1i637b1J6Gk5YYya7TxrTa7FAEiiBPHZLFFCD/RutV BptO8MsxWr6X81KQ+NLmxjd+VJ5tqKvjfWD6GbMNbhqEof5JrWwzjRIVf3To26Q2 hvaB8bIACJ/7wthrJutGUnqpkcCDSN/dqNHXpVK2fdFBSphqNKNbug7SP7Rscs9e fjUovfewKG2aON3R8jk1I7TlL445zYF2yYaOQMquhc5g+i94l3+cdh68k6dkjkBC sBtCLXYhvR+kZA94vnReH/ZR+gllFJBR6GGEEcfeI+S9OcOEFBN08kmFxrWqI1Fb ucHmpYVW6SAQ58LCPVMP =6kYF -----END PGP SIGNATURE----- --=-WbuOVEWOqGhbKC7w1Kw0--