On Sun, Mar 27, 2022 at 09:50:42AM -0300, Andreas Hasenack wrote:
> I was going over fixing the postgresql FTBFS[1] reported[2] in this
> list a few days ago, and saw that the failure was due to postgresql
> not yet supporting llvm-14. Current jammy build was using llvm-13.
> Ok, so looks like llvm-defaults changed from 13 to 14 with
> 0.51ubuntu1[3] on March 12th (wasn't that after FF?)
Yes, it's after FF. We know that LLVM releases always land late wrt our
release schedule. This was called out on
https://discourse.ubuntu.com/t/jammy-jellyfish-release-schedule/23906 - no
explicit FFe, just a known part of our toolchain updates.
> Christian found a patchset, which I applied and uploaded, but to my
> surprise llvm-14, even though it's the default in jammy, is in
> universe[4]. UPDATE: was in universe, looks like Doko just moved it
> into main a few hours ago.
> The end results now, with the above update, is that we will have
> postgresql-14 switching from llvm13 to llvm14 one day before beta
> freeze. Release team, should I revert the postgresql change and adjust
> build-depends so it picks llvm-13?
I think you should proceed with the LLVM 14 build. There's time still for
any regressions to be found and fixed.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
