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 1tWX8r-00HJgR-Du for pgsql-pkg-debian@arkaria.postgresql.org; Sat, 11 Jan 2025 08:46:49 +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 1tWX8q-007LMq-Aq for pgsql-pkg-debian@arkaria.postgresql.org; Sat, 11 Jan 2025 08:46:47 +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 1tWX8q-007LMj-2I for pgsql-pkg-debian@lists.postgresql.org; Sat, 11 Jan 2025 08:46:47 +0000 Received: from mail-oa1-x35.google.com ([2001:4860:4864:20::35]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tWX8m-00131T-1O for pgsql-pkg-debian@postgresql.org; Sat, 11 Jan 2025 08:46:47 +0000 Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-2adc2b6837eso53168fac.1 for ; Sat, 11 Jan 2025 00:46:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736585202; x=1737190002; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=fPvLxWg1okMHX48ukWHa7/a7v5zstZQDcfGimAOm4MQ=; b=Zu2nqDPQUhXNglLOcMEc8UEiFxkqlZiyM1FzpQQwnoT+m0pcYT2osbdBtr3Z6otl2f V5DWP2SXOSBC6n5z+O9f54k1zxT8u+aWhYlhaHQdnSngHb0VqWXTL6yHNNgcFKY3bzrX BHF0bygTNPn2iJjFc/emfoIE5H2vCnYsibzx/K+aNd6bIQsWh5oWM4huLqvlB/KwyFX+ iDBFsf5QgXqHzu1uxvUTzWvUKo+U979wFt4PhZagmOzNBe2pp3FTYYuF4YFkzP2SsTy3 tL2XkZsto9ocfk096ZCxO0zVGY0sEgr6eAZwVJ0ZKjGHBJZOof8hBxTMibgAufjPBdN9 l7eA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736585202; x=1737190002; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=fPvLxWg1okMHX48ukWHa7/a7v5zstZQDcfGimAOm4MQ=; b=Yb/zTc6Xvxk1+gqgjW9B75JvnJ0NhKxY/yGhfeo+F24czNspgGEwGj8otxdxfb0OuW 6QK+OWP6Y3YWDWZmVKfwgwWjLPbwbPIgb3Z02KBOSX98wo8qjEW3cW1JLdV5Crzc8wE8 K3lUZjiFErOJ2wd4EAaadA5l3V0LcHpc7W2v640SYbA9Ox0UjC9Z900QA24ZZfMZVdhZ Raj4riwyst8ukD3gxISGLl1wHHtVNx8/8skcKvZmRglFxTCBU/xc2PPGSlRKQyW4Nfpk PwTXbdzapqWm9cS9loFR8xCrHnDdfDQqpIjvcGUBJ5YDObIfkKmITfGAq89/tA8yzMtY Qp2Q== X-Gm-Message-State: AOJu0YyXifu2z/w2IU4z333fidK5zgYrNOZDKkh4QIx8oTDzaE2UKgPQ viaRSo2EK2+hpIySxnDNuyoc8ZEfUpnLJldpNlFhl789pVeHt/mMufM6nw3Z+kogMrkhPUKGSUl 1ijz3I0gWGmxQVEOGA9eBWOfDvKsRLKyT X-Gm-Gg: ASbGncvEw5YAuI8Jg+lTULOK/gKJ+GhMLoWhMWr5sAGC8ms12a3s21Q7hmTKYLd57ey zX4qoLx/H5vRhoMY0V9cQZDBluHqKZtVgm6hgmg== X-Google-Smtp-Source: AGHT+IFtMIJMILVGclwtxcWTd0/A7cnpdYj2ff1wVcD0C28LrjHhtRFxOOubJqetc5Y+SDy7LzEzyQ0x+NYTA3oGufI= X-Received: by 2002:a05:6870:ff0a:b0:29e:362b:2162 with SMTP id 586e51a60fabf-2aa067a3c95mr7286561fac.20.1736585200981; Sat, 11 Jan 2025 00:46:40 -0800 (PST) MIME-Version: 1.0 From: Bradford Boyle Date: Sat, 11 Jan 2025 00:46:30 -0800 X-Gm-Features: AbW1kvYNojzxWKKu2OYBofDjJVVtmhWWm7Khn6SG7vdOJvf6YcJX8AgJmk1FW6Y Message-ID: Subject: PgBouncer 1.24.0 - New upstream version 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, PgBouncer 1.24.0 was recently released [0]. I've updated the Debian package with this new version but I am running into some issues with the autopkgtests. The autopkgtests passes on Salsa's CI but is failing on my both my local system and jengus [1]. On my local system, the test fails to create a new regress cluster because port 5432 is already in use. I recently switched my sbuild configuration from schroot to unshare. It looks like the unshare backend doesn't create a new network namespace when running the autopkgtests. If I stop the main postgres cluster on my machine before running sbuild/autopkgtest, then the test passes. After reviewing the autopkgtest docs [2] and the test script, I think we might need to add isolation-container to the test's restrictions. On my local system, this causes the test to be skipped since the unshare backend doesn't provide this capability. I will try to look in to this some more in the next few days, but I wanted to check and see if anyone had run into similar issues with building and testing other packages. -- Bradford [0]: https://github.com/pgbouncer/pgbouncer/releases/tag/pgbouncer_1_24_0 [1]: https://jengus.postgresql.org/job/pgbouncer-binaries/101/architecture=amd64,distribution=sid/ [2]: https://people.debian.org/~eriberto/README.package-tests.html