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 1rsZvk-007xNA-8o for pgsql-pkg-debian@arkaria.postgresql.org; Fri, 05 Apr 2024 03:07:52 +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 1rsZvj-00FyB7-Bp for pgsql-pkg-debian@arkaria.postgresql.org; Fri, 05 Apr 2024 03:07:51 +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 1rsZvj-00FyAO-5Z for pgsql-pkg-debian@lists.postgresql.org; Fri, 05 Apr 2024 03:07:51 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rsZvd-000iNg-R3 for pgsql-pkg-debian@lists.postgresql.org; Fri, 05 Apr 2024 03:07:50 +0000 Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2d700beb6beso18724981fa.2 for ; Thu, 04 Apr 2024 20:07:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712286464; x=1712891264; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9LjUzZIeA6dhwQAbbSVKxTZqJkITHJgVQzEF9zWtHmk=; b=av3zyoKyfq1lX0FhvWy2qARXoT2pTx88P/aRk9nxuejnA29hypuKpaZm6oUcgsDPBg lZvAALseUe9UKfEiW6Q9rUGIBFGxmDpxB8pDi/AbL8rWgsrwm7bgbRCR+eARsBDV+JS9 4xsDUI1c35N9RJqt8ZHZ15YdL/loxeWbsKnHi8yVHcYTkFClaTM9+FcBy4SbPY+vjzGW SqQ/eb6dDLRpq7pjdcETs3QEJHqbhdxwlLt4UdOzmOqJWfLAw5oNzr3jsMF61mPGubov 8DX0RSLB6XqMh2fyL7xyKzeWWavdO2FpccjimY18YyV9gjwC0WgQ0MVu4gS1z7BypKZG xLNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712286464; x=1712891264; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9LjUzZIeA6dhwQAbbSVKxTZqJkITHJgVQzEF9zWtHmk=; b=BDpaylHjOStou74kHUqCxz3FEzAb1EDQ5RTe+uN7cOnb0Mxai/oRnmtQ4MdMzgbah6 UqCi6bGONYbTBjwB6sBmSXfooH8fSHRC3pmbnYUDkGu2BTZbfD6etM6SGVbsAOce3+4J GdYdzRr2PzRo4Mi8xJier7SpvF3w4YhofqYfphZV+DLV1Uid04ps6pl3JnUDus+jlyZ0 tu6FVD6FdWh7sEqqjGDLbD+RejM44FZt0ajisX2WSKKMTCZ6/SK/4TPY8VXvpDZ3WojK b/F4QFvbKkE4roA6uSTfAXrbgzf0W5EbJ+NepV9Za2mx8aygr5pXd4GDvCOScdGRhFUF mAAg== X-Gm-Message-State: AOJu0Yy8uhXTf6tRgQHycj7nr4T9F3aQpmS1iwNKztrFySHDFIXqyFOa qiIO/JOQcgWhz4fhYLj/5OvQibhhUVdmzKx3u0++AMiX4sPGgBn+2+FGYAeP/qjSm7p6L0kXTtC VLTyj1JKixekGOXfuxfUgCsGwNeM= X-Google-Smtp-Source: AGHT+IGO+oHVEMMLW2y3ulT1SoEz9bSQSDoN1xmb1NzR0W/ZxUhmrtwaOIe07QRRINWG33qDj+041Yk9DpKH6LMX67E= X-Received: by 2002:a2e:2ac3:0:b0:2d3:f3fe:48ac with SMTP id q186-20020a2e2ac3000000b002d3f3fe48acmr187656ljq.27.1712286463685; Thu, 04 Apr 2024 20:07:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bradford Boyle Date: Thu, 4 Apr 2024 20:07:31 -0700 Message-ID: Subject: Re: Fix FTBFS for prometheus-sql-exporter To: Christoph Berg Cc: pgsql-pkg-debian@lists.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 Christoph, > I had to revert the patch on the older distributions since go was > unhappy: I forgot to mention it in my original email, but I thought the patch might be an issue on older distributions. In the future, is there a way I can trigger a snapshot build on pgdgbuild before notifying the mailing list? > I'm a bit worried that Ubuntu noble also needed the revert; we might > need to un-revert it there if they change the toolchain before the > release. It looks like the replacement API is only available in github.com/prometheus/client_golang@v1.19.0 and Ubuntu noble (as of 20240404) still is on 1.18.0. Unless 1.19.0 gets uploaded to noble, the patch shouldn't need to be un-reverted. I will keep an eye on this. --Bradford