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 1rSmdt-00FshF-Hs for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 24 Jan 2024 23:26:50 +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 1rSmdq-009YeD-IG for pgsql-pkg-yum@arkaria.postgresql.org; Wed, 24 Jan 2024 23:26:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSmdq-009Ye5-Ak for pgsql-pkg-yum@lists.postgresql.org; Wed, 24 Jan 2024 23:26:46 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rSmdn-003YH9-6o for pgsql-pkg-yum@postgresql.org; Wed, 24 Jan 2024 23:26:44 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-5f0629e67f4so64767147b3.3 for ; Wed, 24 Jan 2024 15:26:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=macaroon.net; s=20190412google; t=1706138801; x=1706743601; darn=postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=EFxp77l7R2ZXlPoEE/1jevBThId6K4Fu3NGFHLVb4PQ=; b=gjjMC30dKM2836PAy10b0OrIAs4Lye01Up6y+/s8tjb67N6ogozGfPVtlPOWUZrsiV V4CtNqYzWyLetP+uOSl+7SuyyqeO2pdGV0Uoq4ujUAAmjIdz6Eip0jjVW4svhIjeF6x1 BVv9Ed7Vrh/W+KmTvJ6bTgfXLEtjjI4Fr0/sCdE2360FNEELwKHYBjkk62Y4xh5EMDjB /i+zg3fHK0kgz5ZJHpWgWO+hUyDnYlepe6t00VW+IvlpD5tufPxl/DXDbpEOy0rWYqF0 XIQfJnXxyumZYrcSc5zr416rk4U67ZVtb1PMRxhH0huexXyzKeD1EFbvnX8i7FbBTFdt sPiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706138801; x=1706743601; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=EFxp77l7R2ZXlPoEE/1jevBThId6K4Fu3NGFHLVb4PQ=; b=JKJs1S3GbswPBZXh5n1avDhqtk/BRkcgKbk63entGWYf0o+izzFd2sAgu7/Jwp0nTz qL+pDchAqFzzYiElnzLVhfD9gOJPd1D9CLO7EWBDKAXThIHOlCH6Sjb7tNJ0/8mw4Hwi 1grfWXxCF9oTn/TrGknBj9s6m+XlraSOUh/mUUrDepY7Lsj8MyJRd+es6kZxQZEnAEcY PT+fByYJ1Uj5dLPbjq1SyjNC4UAxOKsdS7TcMaPflhmfyyeUEjFaKqcugY7S10v9zpQW HB9r4RPpU0A+n6ttckO1uk7FLejEzFng7ekUL+U0EMJo+RIpwzLrWKvUWln5Vtvi8y2E wTJQ== X-Gm-Message-State: AOJu0YyZ4cU9kBb/Cm/U1X8q43cCUptVy106j5I53W3y7QbGTdv2innd 2AfBM3ZeQczHFA7V4jgSgl8IVb8M261ckLHiO/MFaPGpbQHb8cDKK2y/MCiaFMMge+e1Iier2SL KvgezrTE9ziZS7IuMPVqrLULljtgG9G8ZjpkeFbh9oTSRCt97eDo= X-Google-Smtp-Source: AGHT+IGm1BjHHvHAK9AswSaQxPu8M4b8CSxLPzK4SSEwnUNt1RvbfrKS9mjsyE/Un1DLgvOmO9p2vDy0clQ8x1Muvw8= X-Received: by 2002:a81:7cc4:0:b0:5ff:545c:ba11 with SMTP id x187-20020a817cc4000000b005ff545cba11mr1497155ywc.57.1706138800965; Wed, 24 Jan 2024 15:26:40 -0800 (PST) MIME-Version: 1.0 From: Cameron Murdoch Date: Thu, 25 Jan 2024 00:26:30 +0100 Message-ID: Subject: RHEL8: barman broken by new psycopg2 package? To: pgsql-pkg-yum@postgresql.org Cc: postgres-core@usit.uio.no Content-Type: multipart/alternative; boundary="0000000000002b5c25060fb9656c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002b5c25060fb9656c Content-Type: text/plain; charset="UTF-8" Hi, python3-psycopg2-2.9.9-2PGDG.rhel8.x86_64.rpm is built as a python 3.9 package but python3-barman-3.9.0-1PGDG.rhel8.noarch.rpm is still on python 3.6. This broke our backup servers before I downgraded psycopg2. I see that pyscopg2 has dropped support for python 3.6, so I don't know what the correct fix is. Build python3-barman for python39? Build packages for both python 3.6 and python 3.9, using the latest psycopg2 that supports 3.6? On my rhel8 systems there seems to be a "standard" that packages that start with "python3-" are built for python36 so at the very least the name is confusing. Thanks Cameron --0000000000002b5c25060fb9656c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,<= br style=3D"color:rgb(46,52,54);font-family:"Source Code Pro";fon= t-size:13.3333px;font-style:normal;font-variant-caps:normal;font-weight:400= ;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none= ;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text= -decoration:none">
python3-psycopg2-2.9.9-2PG= DG.rhel8.x86_64.rpm is built as a python 3.9 package but pyth= on3-barman-3.9.0-1PGDG.rhel8.noarch.rpm is still on python 3.= 6. This broke our backup servers before I downgraded psycopg2.

I see that pyscopg2 has dropped support for python 3.= 6, so I don't know what the correct fix is. Build python3-barman for py= thon39? Build packages for both python 3.6 and python 3.9, using the latest= psycopg2 that supports 3.6?

On my rhel8 systems there seems to be a "standard" th= at packages that start with "python3-" are built for python36 so = at the very least the name is confusing.

Thanks
Cameron
--0000000000002b5c25060fb9656c--