Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n4nvw-00013i-CQ for pgsql-www@arkaria.postgresql.org; Tue, 04 Jan 2022 17:49:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n4nvv-0003ak-7m for pgsql-www@arkaria.postgresql.org; Tue, 04 Jan 2022 17:49:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n4nvu-0003ab-N3 for pgsql-www@lists.postgresql.org; Tue, 04 Jan 2022 17:49:15 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n4nvs-0008BD-3O for pgsql-www@lists.postgresql.org; Tue, 04 Jan 2022 17:49:13 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:References:In-Reply-To:Subject:Cc: To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version:Sender: Reply-To:Content-ID:Content-Description; bh=3TV9/Xk534bN6MFpSehMgEYchY9AOB4gIu0jRnKQwgY=; b=brMxFDWldKm7xPIV/34PCGMNfA i2rqth6PEF65d7muw8hyDKECzkXh8TLIGila1EOzOQgiBwsmqe/WZ1hpOY5/b47EnTmcjTh/NKy9Q +YI5H8M78pnRWhZxD3VPZJRWFl28tj+HJw5La3zdZDzX4v3tVj4z8nKtc9zGtvkertAGRc0WPt2AW zmcTT+LKgOf8renYZR5wGyoGw5XzX156vWkAyBdg/wkDxAUNE5b3CrxpqXfKuA4bSx3aicmNPLWKc tcdfKjFKBOk3VPW7naESSu7YdskO/jE5VhMZsr7Mi4wRT8KpPVQCbJ0qUCMz4YgsOErikqeGmF+4A mjhX5eQg==; Received: from meldrar.postgresql.org ([87.238.57.231] helo=webmail.postgresql.org) by meldrar.postgresql.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n4nvn-0008Hy-Ny; Tue, 04 Jan 2022 17:49:09 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Wed, 05 Jan 2022 04:49:06 +1100 From: Justin Clift To: =?UTF-8?Q?Devrim_G=C3=BCnd=C3=BCz?= Cc: Jonathan Wright , "Jonathan S. Katz" , pgsql-www@lists.postgresql.org Subject: Re: Add AlmaLinux as Specifically Supported Distro In-Reply-To: <9a1462c68c1c96f3d91ce5a5aae0473487ce2e31.camel@gunduz.org> References: <8a29a8f8b9cb28ae010b77fcdbf709e70d1c9d56.camel@gunduz.org> <7efd7c0f73bedf467a038ae0f1e76a066b8cbf11.camel@gunduz.org> <9a1462c68c1c96f3d91ce5a5aae0473487ce2e31.camel@gunduz.org> Message-ID: <21cd5cf6865df80e0fb2b3a15dda90cb@postgresql.org> X-Sender: justin@postgresql.org User-Agent: Roundcube Webmail/1.3.17 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-01-05 04:41, Devrim Gündüz wrote: > Hi, > > On Tue, 2022-01-04 at 11:01 -0600, Jonathan Wright wrote: >> Gotcha.  Anything I need to do for listing Alma then (realizing >> tests/builds won't happen on it directly)?  I send patches if needed. > > As I explained before, unless community decides otherwise7, Rocky will > be listed there. I already buildpackages on 11 separate platforms (plus > Rocky for testing), and no intention to add another "clone". Are we able to indicate on the download page that our CentOS RPMs "should" work on AlmaLinux, though we haven't tested it ourselves? Seems a bit unfair to completely leave them off the list. + Justin