public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bradford Boyle <[email protected]>
To: [email protected]
Subject: Re: The end of 32-bit PostgreSQL support?
Date: Tue, 30 Jul 2024 21:10:30 -0700
Message-ID: <CAOMoQbRQPkL6PfJoeYkHRKATJJnwnbwUadiHOv_Vh_K=7nCX-A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAOMoQbQak2uyt5oGUaTWHPn3nWo+Q97JWGMWM-bqq6yFWFw+gw@mail.gmail.com>
<[email protected]>
<CABUevEz8tX53wT-1pLXGVSndavCxKBCy47i-5_jpNKtsy7T5cA@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CAOMoQbTdRq4t2hxxi2xMLHE8W-xR2d-XL2AK3WqzH5Eb9YODVg@mail.gmail.com>
<[email protected]>
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 <!pkg.postgresql.32-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
view thread (16+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: The end of 32-bit PostgreSQL support?
In-Reply-To: <CAOMoQbRQPkL6PfJoeYkHRKATJJnwnbwUadiHOv_Vh_K=7nCX-A@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox