From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Cirrus CI for macOS branches 16 and 15 broken |
Date: | 2024-08-18 23:50:11 |
Message-ID: | 1230240.1724025011@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Mon, Aug 19, 2024 at 10:55 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> What this smells like is that MacPorts has to do some kind of database
>> update as a result of its major version change, and there are code
>> paths that are not expecting that to get invoked. It makes sense
>> that unprivileged "port outdated" would fail to perform the database
>> update, but not quite as much for "sudo port unsetrequested installed"
>> to fail. That case seems like a MacPorts bug; maybe worth filing?
> Huh. Right, interesting theory. OK, I'll push that patch to use
> 2.10.1 anyway, and report what we observed to see what they say.
Actually, it's a bug that it's trying to force an upgrade on us, isn't
it? Or does the CI recipe include something that asks for that?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2024-08-19 00:00:00 | Re: Emitting JSON to file using COPY TO |
Previous Message | Thomas Munro | 2024-08-18 23:44:39 | Re: Cirrus CI for macOS branches 16 and 15 broken |