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 1ta66O-00G9ZA-D3 for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 21 Jan 2025 04:43:00 +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 1ta66L-00B8UM-OO for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 21 Jan 2025 04:42:57 +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 1ta66L-00B8U1-I8 for pgsql-pkg-debian@lists.postgresql.org; Tue, 21 Jan 2025 04:42:57 +0000 Received: from mail-oi1-x22e.google.com ([2607:f8b0:4864:20::22e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ta66J-000fWQ-1D for pgsql-pkg-debian@postgresql.org; Tue, 21 Jan 2025 04:42:56 +0000 Received: by mail-oi1-x22e.google.com with SMTP id 5614622812f47-3eba50d6da7so1195315b6e.2 for ; Mon, 20 Jan 2025 20:42:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737434575; x=1738039375; darn=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=cVBAWr4uf/YMYVJzny5C9S7qVOkkEkwWyDo32SAhTzM=; b=J2YGmKGFV22VTusxIKE7olp7/bWLdocVoSlSrud4qIVbAkUcJt/OHUO02T5W0UGjvb UsymqpWcuHphRvKlhciM8e431xrjErFySh2E6NY4YEZd3LJtCvDQzkLKqhH/jlL+I/FS fGwOtrcMsqTZjZKIOpgrBuh0JWk4I4yZDfkJUCH3YzwEt1O0uIaK7w+h/k0AmIx8OaXA znciOb5bsSyULFAWFlin4QqACO+gmheNfgxK9J0sztTcAJGX5fhPEu+AsKRgdJLfXaMi Rd+ujhIiDlCse58n/s2BzOiP3+7vTJpHwzNB+3d1fNxFl3Wr/vkhlJiNvfH0FR8ba/Wh YwVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737434575; x=1738039375; 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=cVBAWr4uf/YMYVJzny5C9S7qVOkkEkwWyDo32SAhTzM=; b=IZAeGQZOZPPAnCzZ0dFZWJF2bJ3hhRth1KyCnD8xQ7lNi3gkmSpBi6/uB4IGz9YnbZ 75BXsEcZo1V1jta9TwUtE7QsjWJXcBO8PbpaRNH+SLFDe7o5COE3cHW1YGBTmS6hDLQ+ SmNGjQ0tr9jgJWeaifSn80Y5TDmMiO+DyVMFxw1557aq74q34aEkUTF3ZUE8S07GOqBN SRB6hJaf67vxIauhY6IyXWpK2c8FwKtuxaokmuMNkgYmwZzV1IUnPWUUUa6Ha7VE+XFm wUXgsnP11+B6CRcHfZkMf53jvSCI0HyWM9A5J9tdzxwBCIaesAUAAlX8oD0umZ+mKPOa M/yA== X-Gm-Message-State: AOJu0Yy3QjfahRYBGkd/hLs5Q/mbJsOBSz3T2CswFj4HYqmbssHCXc1M l6ctsHbcyb2BXTSqOs4xUNuGMvruljv+3/20LUduO7oKvHqmTyNby4q1W3x022U6bJ5uIVpACYn sSHmSLz4YBYDIFeKMpalazyPjF0c= X-Gm-Gg: ASbGnctX0TFENEqWBN/9o7GdZT1ivgIz6v0QMVc0nTpGFWgPUrwW5ztXP0snvdaLxQD 1mCzh4ALpLiGErBinwPzkZGKfScrCvHXkb9+xPMkj6uBhVbnGZWE= X-Google-Smtp-Source: AGHT+IFR02zY4B37Mbn9jMOllkIQbmsBriIQwPIioIUzTYq6hjkH9M5Ox3hT1Crqcu/61vG7fz1KucBbam9PNtiRa88= X-Received: by 2002:a05:6871:538b:b0:29e:51ca:68b4 with SMTP id 586e51a60fabf-2b1c0932297mr8843622fac.19.1737434575154; Mon, 20 Jan 2025 20:42:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Bradford Boyle Date: Mon, 20 Jan 2025 20:42:44 -0800 X-Gm-Features: AbW1kvZuiYPydbVVihkcn3jVrWg4ejqL_ykM5rn6ihI2SLDXa5w3KznN_pX2_A0 Message-ID: Subject: Re: PgBouncer 1.24.0 - New upstream version To: Brian Cosgrove Cc: 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 Brian, I was looking at the package for pgBouncer 1.24.0 again today and it looks like the tests are failing [0]. After reading through the logs, it looks like psycopg in testing and unstable was updated to 3.2.4 this past Friday. I am able to reproduce the test failures in dev environment by updating the version in requirements.txt. Should we disable the main test suite for now to unblock the upload of 1.24.0? Regards, --Bradford [0]: https://salsa.debian.org/postgresql/pgbouncer/-/jobs/6962351