[Bug 1949579] [NEW] [MIR] postgresql-14

Launchpad Bug Tracker 1949579 at bugs.launchpad.net
Wed Dec 8 14:53:12 UTC 2021


You have been subscribed to a public bug by Christian Ehrhardt  (paelzer):

TL;DR:
We are in the process of clarifying if the dependencies really will be ready to move to PG-14.
If yes => promote PG-14, demote/remove PG-13
If no  => remove PG-14

--- Details ---

postgresql-14 now shows up in Jammy component mismatches.
https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html

That is due to postgresql-common being auto-synced and changing the
default to PG14.

Conceptually this is the same as
- https://bugs.launchpad.net/ubuntu/+source/postgresql-13/+bug/1902059
- https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/1851396
and all the others before it.

It seems we can go PG-13 in 21.04 as it looks rather good on the main PG-13 transition. Yet there are still a bunch of blockers left:
https://release.debian.org/transitions/html/postgresql-14.html

I guess those dependencies will need some time and then 4-8 weeks to get everything in shape.
Until then this will probably clutter update-excuses, therefore I'm tagging this as such to be known.

But for expectation, last time a few took quite a while and some even got removed for a short while.
Open issues are tracked here (thanks to Devrim / Myon for the great work)
https://wiki.postgresql.org/wiki/PostgreSQL_14_Extension_Bugs

Hopefully then eventually (probably ~January) we re-evaluate this and
remove PG-13.

Due to the above this is filed as MIR bug so that one looking at
mismatches can find it, but not meant to be promoted yet until the to-
dos mentioned are resolved - therefore keeping it "invalid" for now..

** Affects: postgresql-14 (Ubuntu)
     Importance: Undecided
         Status: Fix Committed

** Affects: postgresql-common (Ubuntu)
     Importance: Undecided
         Status: Fix Committed


** Tags: jammy server-todo update-excuse
-- 
[MIR] postgresql-14
https://bugs.launchpad.net/bugs/1949579
You received this bug notification because you are a member of Ubuntu Package Archive Administrators, which is subscribed to the bug report.



More information about the ubuntu-archive mailing list