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 1sZ0fo-00Fmuo-Sv for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 31 Jul 2024 04:10:48 +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 1sZ0fm-0005ak-Kk for pgsql-pkg-debian@arkaria.postgresql.org; Wed, 31 Jul 2024 04:10:46 +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 1sZ0fm-0005ac-EX for pgsql-pkg-debian@lists.postgresql.org; Wed, 31 Jul 2024 04:10:46 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sZ0fk-002MtQ-1D for pgsql-pkg-debian@lists.postgresql.org; Wed, 31 Jul 2024 04:10:45 +0000 Received: by mail-lj1-x22e.google.com with SMTP id 38308e7fff4ca-2f029e9c9cfso83514261fa.2 for ; Tue, 30 Jul 2024 21:10:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722399042; x=1723003842; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=AT9XvqVsSHJEu+jagcYRonjndXohTirJT2DYeK/4lvI=; b=jq2aoVvZRA41M1n+KDP0zdQPbICbY8YSfaEmsZEf1Ta30OAlyg3hupWN3fw/N2HYvD GihJ+nlpE9SHaBqxF4CbsahdEx3WQ26Xy5aQ9DAykk+JkuM/PFlOKNBJJLepcXIcjgbj jhL8TNPSBbf2uwfQWutTVIdxb84+DnmJpRIvgsQVUR0LVawYmOoCUIuSm7vfSqUx3i7c RxR4MNL1QC1UT+gc/NMJETPA7pq4Xdo8ijNEDnM5y2KyNW9EjDdybkiotE4q/1skWo0F /eFxB8Q6OA9Pjtg7TEDKw+3ruwULJ47IRGkv5tPwPdlGs51iNT7O8ctHOzgqaMjAzdXX 9bfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722399042; x=1723003842; h=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=AT9XvqVsSHJEu+jagcYRonjndXohTirJT2DYeK/4lvI=; b=btgfAeHflebb5oBDlsJWlgGixowfb74ifTcBsdIHe0ZltkSztedJLRhTl1hZez/zN8 3yUCIZmEfQhYdxfxL7Wo1BMQ4AbObxON3w6BB1CPtID24tBpwcS/xk9eFa2zKL8UIuSx FllBwBFIA2f/Myf4RO47Dfn5ylO+UIultTIIJ/7XQbDtViXB8HbGAfxyxgKgoET2sofz r2JnrNOgRmsj7cU5z/dMAFhWmuuc236ul2qThGAmzKOsKES221kWEAHw2wPfnKnQkJDx FtwyH0aYFCNpDFnN39zaUPWUmBOYB6b3GPxuRNpjK7sVhIIomEPalNuKKySN0OYDpka1 7/mw== X-Gm-Message-State: AOJu0YwmzWPowrD0QAjQZfyMKhYoa7ivNYihb9K7rPfa/BWKMjfBXY/h e8DOJiGYwVv95vrQ1qcJZ8EOcc4i9YxYsgnMg6y/zE/zSzEJXP3o/qTMCD0iLG/dAAju6O0fTFM +S1ruiwW6PA+M9/2547pTK8SENbCRL0oo X-Google-Smtp-Source: AGHT+IHluQ1kR9klZAQAYlSfDx4QGZMYBwadza+0oJP/8+zFj+YcwQaWx1Ge+dPpi66/epa5waWmOiYsEEyhktnm/s8= X-Received: by 2002:a2e:a30e:0:b0:2ef:18ae:5cbd with SMTP id 38308e7fff4ca-2f12ee289ddmr106771541fa.27.1722399041825; Tue, 30 Jul 2024 21:10:41 -0700 (PDT) MIME-Version: 1.0 References: <4e3e01a0-bc53-45cf-8f53-54781ae28cf4@pgmasters.net> <9BDDFA98-9637-4BC4-BBF6-45CF03DBCD9D@debian.org> In-Reply-To: From: Bradford Boyle Date: Tue, 30 Jul 2024 21:10:30 -0700 Message-ID: Subject: Re: The end of 32-bit PostgreSQL support? To: 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 Re: Christoph Berg > * When re-uploading all extensions to Debian to transition them from > 16 to 17, disable extensions on 32-bit archs. Adding this should do > the trick: > > Build-Depends: architecture-is-64-bit , > > That way, people could still build extension packages manually if > they really wanted (dpkg-buildpackage -Ppkg.postgresql.32-bit). Do you have script to help with re-uploading all extensions and/or updating Build-Depends for a package? Or is it mostly a manual process? If there is no automation, is there anything I can do to assist with this? -- Bradford