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 1tfbQ2-003d1r-Be for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 05 Feb 2025 09:10:02 +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 1tfbQ1-00D7CG-2k for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 05 Feb 2025 09:10:01 +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 1tfbQ0-00D7C7-Sg for pgsql-pkg-debian@lists.postgresql.org; Wed, 05 Feb 2025 09:10:00 +0000 Received: from mout-p-101.mailbox.org ([80.241.56.151]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tfbPx-003P99-2z for pgsql-pkg-debian@postgresql.org; Wed, 05 Feb 2025 09:10:00 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-101.mailbox.org (Postfix) with ESMTPS id 4YnvZS5LBBz9t4k; Wed, 5 Feb 2025 10:09:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=df7cb.de; s=MBO0001; t=1738746592; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=RMFksLjNvxdzaCV56snKfErPUtSxa17FbVw0v9dup20=; b=o1fnmxCUcbbq/dT48m+XH2sG8PFDrDE5tkTWq1KIkN8e+sZLHvy0irYRn0B1oWSk7F39MA eGx7rixJ7ipMuuEAuA/D7dZpCaVtHbrwccqHIs/dQw/RafcWzrm+f66MhrGsrse9C0TFPX J4BrrJFocHHUSVcRCn+99Ew4MkKwAOvBZPPtyUTz4p5jQeH2dQh09EM2zni6gY5bm95hkx mL533vanSeyyutaUKSXbnnZmMksf6bGvccpcvFONXDN1X9fYDCtMlq3p4n/eGOd5XEVh6t Qhlv3vaGAteji7F4LCnt5Bk1lrIhelkjnYX20fnX79Vv7l6b/dwsfhgJZ/H/Mg== Date: Wed, 5 Feb 2025 10:09:51 +0100 From: Christoph Berg To: Bradford Boyle Cc: pgsql-pkg-debian@postgresql.org Subject: Re: PgBouncer 1.24.0 - New upstream version Message-ID: Mail-Followup-To: Christoph Berg , Bradford Boyle , pgsql-pkg-debian@postgresql.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4YnvZS5LBBz9t4k List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Bradford Boyle > I think we could go without tests on bullseye since it seems like we are > nearing the trixie release and bullseye will become old old stable. > (Correct me if I am wrong on this point, I'm making this assumption > based on the trixie freeze dates). There's probably little value in > creating extra work here. Or we just don't update the package on bullseye, leaving it at 1.23.1. But there is still the autopkgtest, so we still have test coverage there. > It looks like d/rules for pgbouncer will skip the tests if nocheck is in > DEB_BUILD_OPTIONS -- is this something that can be configured via the Jenkins > YAML? I am not very familiar with the Jenkins job builder YAML and I didn't see > any usages of that in the current set of jobs. Or would I need to update > generate-pgdg-source to include an additional tweak to disable the tests on > older platforms? Any of these would work. DEB_BUILD_OPTIONS=nocheck would have to be set in the sbuild-package script. That's probably the easiest way forward. The extra test dependencies need annotating with so the build doesn't try to install them. Christoph