Re: what's going on with lapwing?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <adunstan(at)postgresql(dot)org>, pgbuildfarm(at)rjuju(dot)net
Subject: Re: what's going on with lapwing?
Date: 2025-03-06 15:45:08
Message-ID: CA+Tgmob2tgRCE5wp0zBRuk-akFthXpqAzm5H55j+GyZY9CavmA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 5, 2025 at 9:49 PM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> FWIW I installed the client version 19.1 this morning and forced a run on HEAD
> and lapwing is back to green.

Thanks, appreciate it.

By the way, is there a particular reason why we're keeping Debian 7
coverage in the buildfarm? I don't want to be in a huge rush to kill
platforms people still care about, but it was pointed out to me
off-list that this is quite an old release -- it seems Debian 7 was
first released in 2013, last released in 2016, EOL in 2018. I assume
that not too many people are going to install a PostgreSQL release
that comes out in 2025 on an OS that's been EOL for 7 years (or 12
years if the BF page is correct that this is actually Debian 7.0).
Somewhat oddly, I see that we have coverage for Debian 9, 11, 12, and
13, but not 8 or 10. Is there a theory behind all of this or is the
current situation somewhat accidental?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-03-06 15:54:26 Re: Commit fest 2025-03
Previous Message vignesh C 2025-03-06 15:38:02 Re: Commit fest 2025-03