[MIR] postgresql-16

Bug #2044074 reported by Athos Ribeiro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postgresql-16 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

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

That is due to postgresql-common and postgresql-15 being synced and changing the default to PG16.

Conceptually this is the same as
- https://bugs.launchpad.net/ubuntu/+source/postgresql-15/+bug/1998305
- https://bugs.launchpad.net/ubuntu/+source/postgresql-14/+bug/1949579
- 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 with PG-16 in 24.04 as it looks rather good on the main PG-16 transition.
Debian is dedicated to move as well in time for their next release and in fact the transition there is already completed.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

I confirmed that it is just a rename, it still behaves the same.

postgresql 16.1-1 is only in proposed (16.0-2 is in noble non-proposed), I'm only promoting the one in main. It should carry over that attribute when migrating and is held in main by postgresql-common [1] which does the switch of the default to 16 and is held back by that mismatch atm.

All but the -dev package are usually in main, no new packages added doing the same promotion as with v15 in lunar.

My preparation checks still looked normal
...
postgresql-pltcl-16 16.1-1 in noble s390x: universe/database/optional/100% -> main
Dry run; no publications overridden.

But after confirming all is good the actual promotion did show me:
...
libpq-dev 16.1-1 in noble amd64: main/libdevel/optional/100% -> main
...
libpq-dev 16.1-1 in noble amd64 remained the same

See the difference of universe -> main vs main->main.

So it seems someone did the same at the same time ?!

The only thing not promoted by whatever/whoever was the source, so I've completed this by

./change-override -c main -s noble-proposed --source-only postgresql-16
Override component to main
postgresql-16 16.1-1 in noble: universe/misc -> main
Override [y|N]? y
1 publication overridden.

I'm not touching it with more, potentially conflicting, changes right now.
lets give the archive a few hours for a full publishing round and see if it really is good or if it needs more.

Note: Gianfranco also asked me to unblock pgrouting by removing old builds against -15 from propose, which I did

[1]: https://launchpad.net/ubuntu/+source/postgresql-common/256

Changed in postgresql-16 (Ubuntu):
status: New → Fix Committed
Changed in postgresql-16 (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.