Comment 0 for bug 2052850
Revision history for this message
| Sergio Durigan Junior (sergiodj) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
[Impact]
* MRE for latest stable fixes of Postgres 12, 14, and 15 released on February 2024.
* Regular update of Postgres 16 on Noble (development release).
[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:
- CVE-2024-0985
Current versions in supported releases that got updates:
Special cases:
- Since there is 1 CVE being fixed here, we will push this through the security pocket.
Standing MRE - Consider last updates as template:
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
- https:/
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:/