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 1sdOdZ-00FDDs-OH for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 12 Aug 2024 06:34:37 +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 1sdOdX-00DlHw-7V for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 12 Aug 2024 06:34:35 +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 1sdOdW-00DlHn-V6 for pgsql-pkg-debian@lists.postgresql.org; Mon, 12 Aug 2024 06:34:35 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sdOdQ-004J1a-59 for pgsql-pkg-debian@postgresql.org; Mon, 12 Aug 2024 06:34:33 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2f149845d81so44996501fa.0 for ; Sun, 11 Aug 2024 23:34:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723444466; x=1724049266; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=xuHLWlrohrfoZHWgaWgSwrVFHWNb0oU4oV8fsN14NKs=; b=SlxSaL/0fg8/PtJL+hhzH3Cfd+COGJoKcaWnmc8a0/x5akMIPJZUpKmUdRhDBAEl6S m88F2bcTDm8hI6W5nQx9GcPbsylBPc5rq+LcOdzmBKgmPg039A5Il46oImll398iiz3X lOQHiVXYRgLr5BcIxACV3YNU1s6zV6fffBldevnfUqeTy9lZ0rBB3xrk+uccBOcsFQSk +cRpEYjLxwoQlGlMAIIw4qeXPS1Ot9WTSV3RQgnosBsMQ0XLFK1NF/acOMlmeGWVUO7U 0Txnes3soq/0/e1Ryhunh16+1KyVWQ88SKy7lRFKnZRTQKNQnBqXhQUzvL5PjA/cI2Iq OULg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723444466; x=1724049266; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=xuHLWlrohrfoZHWgaWgSwrVFHWNb0oU4oV8fsN14NKs=; b=VR2Jd7vzYaaHQzBAwFEQ9LSbo6TjDgO4vKmSmYjz47l3WOb0c7PXogGx9etLS1FfSN O7RoZwQOM9i/SV76IttUrSDIrKqNwjd1plRRhU/fOuektRkwXei2BtFGScm5Z1DmhQe4 C4JRfeTcuwl5exOkfqNQ5IOuglcH3b2J/MQ3czK2C1Ip1bkQZ0Lkj+l3ilIZ/3rTz6/7 S1WN0NYZv9Pxqzg+nJwA8+0wHlN8cxHdup2JCBvAZGeJ6rjiPcAVtqrRfkGgAToCn1PF iqkQIouFfNBEEbFb/aFTGj4kwcGWh6+sJKzR9JI3/kOgsXFm6atV3cJNrwk2oKUSsWGy FzGQ== X-Gm-Message-State: AOJu0YyaZVDpMO0g3MeHUsQlOhiO2nma4FWjfr/d5aHpXc9fSFjIkJWk XQf+y/Ins7oBHcBjuFzK5YuSpd6ojuq34Nvi4YtKJw426iw3I5n1fq4nZTIeZOP8JQpqEUaD5uu wQlg0XIrtsaOM7z5cufgs2XBdiFxrnJsr X-Google-Smtp-Source: AGHT+IGmlNaydsR9XuAELpPtexsw5rrOt/Ok/HgTI7PEM2P8tHVx7L1WMhaq0aogvk8P1LNtHCExasX4p0BAYvCQWIw= X-Received: by 2002:a2e:4c02:0:b0:2ef:206c:37c4 with SMTP id 38308e7fff4ca-2f1a6ce6eacmr56360611fa.33.1723444466094; Sun, 11 Aug 2024 23:34:26 -0700 (PDT) MIME-Version: 1.0 From: Bradford Boyle Date: Sun, 11 Aug 2024 23:34:14 -0700 Message-ID: Subject: vip-manager and vip-manager2 FTBFS To: pgsql-pkg-debian@postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi All, The package golang-etcd-server-dev was updated from 3.4.30 to to 3.5.15 at the end of July. This version of etcd introduced a couple of changes to import paths that caused vip-manager and vip-manager2 to FTBFS in sid [1, 2]. I've prepared patches for both packages to update the import paths [3, 4]. With these patches, both packages build on sid and autopkgtests pass. However, bookworm has etcd 3.4.23 and noble has 3.4.30 so the patches break the build on older distributions. I don't believe this is an issue for vip-manager since this pakcage provides vip-manager 1.x which hasn't had a new release since 2022. vip-manager2 has had a release as recently as three weeks ago. If we want to build updated packages of vip-manager2 for both bookworm and trixie on pgdg, we would need to apply different patches for etcd 3.4 and 3.5. I suppose we could also just disable vip-manager2 for any distribution besides sid and trixie but I don't have a sense of how popular this package is and if that is a viable solution for this particular package. Before updating these packages, I wanted to see if there was any input on how to handle these packages on older distributions. Thanks, -- Bradford [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078322 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078323 [3]: https://salsa.debian.org/postgresql/vip-manager/-/commit/ac57eaba565013c462da95276db4824af3069beb [4]: https://salsa.debian.org/postgresql/vip-manager2/-/commit/244ba273f40125861603403064171e2736a2978d