We need to prepare UCS 5.1-0 for the backport of postgresql-15 to 5.0-9 too. +++ This bug was initially created as a clone of Bug #57779 +++ Keycloak 26 doesn't support postgesql-11 any longer. One idea is to backport postgesql-15 from Debian Bookworm (UCS 5.2) to 5.0-9, but if we do that we need to ensure that: * the postgresql migration works (ideally via diagnostic module) * if we don't do a forced migration but e.g. via diagnostic module, then we have a transition phase, where we need to ensure that the new postgresql-common (248) works with the old postgresql-11 * the update from 5.0-9 to 5.2-0 works (via 5.1-0 / Debian bullseye)
Cherry picked package postgresql-common[173254] version 248 from 5.0-0-0[83]/errata5.0-9[703] to 5.1[84]/[0] Cherry picked package postgresql-common[173254] version 248 from 5.1-0-0[84]/None[0] to 5.2[85]/[0] 3f1f719cd | Dummy patch to trigger repo-ng version timestamping 82e870237 | fixup Package: postgresql-common Version: 248A~5.1.0.202412031601 Branch: 5.1-0 979e33b26 | Dummy patch to trigger repo-ng version timestamping Package: postgresql-common Version: 248A~5.2.0.202412031613 Branch: 5.2-0 Cherry picked package postgresql-15[173256] version 15.8-0+deb12u1 from 5.0-0-0[83]/errata5.0-9[703] to 5.1[84]/[0] Cherry picked package postgresql-15[173256] version 15.8-0+deb12u1 from 5.1-0-0[84]/None[0] to 5.2[85]/[0] 597169d12 | Dummy patch to trigger repo-ng version timestamping Package: postgresql-15 Version: 15.8-0+deb12u1A~5.1.0.202412031628 Branch: 5.1-0 0adf3b757 | Dummy patch to trigger repo-ng version timestamping Package: postgresql-15 Version: 15.8-0+deb12u1A~5.2.0.202412031657 Branch: 5.2-0
5618937f6d0 | Backport postgresql-15 32a4bfe5b61 | Add metapackage univention-postgresql-15 Package: univention-appcenter Version: 10.0.14 Branch: 5.1-0 Package: univention-pkgdb Version: 14.0.7 Branch: 5.1-0 Package: univention-postgresql Version: 13.0.4 Branch: 5.1-0
OK, update works