** Description changed: [Impact] * MRE for latest stable fixes of Postgres 14, 16, and 18 released on November 2026. [Test Case] * The Postgres MREs traditionally rely on the large set of autopkgtests to run for verification. In a PPA, those are all already pre-checked to be good for this upload. [Regression Potential] * Upstream tests are usually great and in addition in the Archive there are plenty of autopkgtests that in the past caught issues before being released. But nevertheless there always is a risk for something to break. Since these are general stable releases I can't pinpoint them to a most-likely area. - usually this works smoothly except a few test hiccups (flaky) that need to be clarified to be sure. Pre-checks will catch those to be discussed upfront (as last time) [Other Info] * This is a reoccurring MRE, see below and all the references * CVEs addressed by this MRE: - - <List CVEs if needed> + - CVE-2026-6460 + - CVE-2026-116306 + - CVE-2026-116329 + - CVE-2026-16237 + - CVE-2026-120146 + - CVE-2026-116310 + - CVE-2026-116332 + - CVE-2026-120143 + - CVE-2026-116304 + - CVE-2026-120152 + - CVE-2026-120150 + - CVE-2026-116328 + - CVE-2026-116315 + - CVE-2026-116317 + - CVE-2026-116321 + - CVE-2026-116327 + - CVE-2026-116331 + - CVE-2026-116322 + - CVE-2026-116312 + - CVE-2026-116335 + - CVE-2026-116336 + - CVE-2026-6467 + - CVE-2026-120153 + - CVE-2026-116303 + - CVE-2026-116303 + - CVE-2026-116311 + - CVE-2026-116316 + - CVE-2026-120149 + - CVE-2026-116333 + - CVE-2026-120144 + - CVE-2026-120148 + - CVE-2026-120145 + - CVE-2026-120154 + - CVE-2026-14661 + - CVE-2026-120142 + - CVE-2026-18447 + - CVE-2026-120139 + - CVE-2026-120141 + - CVE-2026-120151 + - CVE-2026-116326 + - CVE-2026-116326 + - CVE-2026-116309 + - CVE-2026-116320 + - CVE-2026-116319 + - CVE-2026-116307 + - CVE-2026-116323 + - CVE-2026-120147 + - CVE-2026-116308 + - CVE-2026-116325 + - CVE-2026-116313 + - CVE-2026-116318 + - CVE-2026-116330 + - CVE-2026-116314 + - CVE-2026-16240 + Current versions in supported releases that got updates: - postgresql-14 | 14.24-0ubuntu0.22.04.1 | jammy-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x - postgresql-16 | 16.15-0ubuntu0.24.04.1 | noble-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x - postgresql-18 | 18.6-0ubuntu0.26.04.1 | resolute-updates | source, amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x - postgresql-18 | 18.6-3build2 | stonking | source, amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x - postgresql-18 | 18.6-3build2 | tenacious | source, amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x + postgresql-14 | 14.24-0ubuntu0.22.04.1 | jammy-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x + postgresql-16 | 16.15-0ubuntu0.24.04.1 | noble-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x + postgresql-18 | 18.6-0ubuntu0.26.04.1 | resolute-updates | source, amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x + postgresql-18 | 18.6-3build2 | stonking | source, amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x + postgresql-18 | 18.6-3build2 | tenacious | source, amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x Special cases: - - <Describe special cases here.> + - Tenacious will be a sync from Debian. As usual we test and prep from the PPA and then push through SRU/Security as applicable. Once ready, the test packages should be available at https://launchpad.net/~canonical-server/+archive/ubuntu/postgresql-sru- preparation/+packages
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2171171 Title: Backport postgresql for tenacious cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-14/+bug/2171171/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
