group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #37421
[Bug 1903978] [NEW] New upstream microreleases 9.5.24 10.15, 12.5 and 13.1
Public bug reported:
[Impact]
* MRE for latest stable fixes of Postgres release on August 13th.
[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]
* Upstreams tests are usually great and in additon in the Archive there
are plenty of autopkgtests that in the past catched issues before being
released.
But never the less 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 hickups (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
* This includes a fix for CVE:
CVE-2020-25695
---
Current versions in supported releases:
postgresql-9.5 | 9.5.23-0ubuntu0.16.04.1 | xenial-updates
postgresql-10 | 10.14-0ubuntu0.18.04.1 | bionic-updates
postgresql-12 | 12.4-0ubuntu0.20.04.1 | focal-updates
postgresql-12 | 12.4-1 | groovy
postgresql-13 | 13.0-6build1 | hirsute-proposed/universe
Special cases:
- Hirsute will as usual be synced from Debian.
I already see
postgresql-13 | 13.1-1 | unstable | source, amd64, arm64, armhf, i386, ppc64el, s390x
- 21.04 also has a postgresql-12 and while that is on the way to be
removed and fulyl replaced by 13 that is too far out. Therefore we will
upload 12.5 to Hirsute as well.
- I have checked with Debian (they are affected by the same FTFBS and test
fails of bug 1903573) but they will just remove postgresql-12 from
testing. We can't do that yet on hirsute without breaking too much
Last relevant related stable updates: 9.5.23, 10.14 and 12.4
You'll see that the last update was missed, so I'll combined them.
Standing MRE - Consider last updates as template:
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676
- pad.lv/1752271
- pad.lv/1786938
- pad.lv/1815665
- pad.lv/1828012
- pad.lv/1833211
- pad.lv/1839058
- pad.lv/1863108
- pad.lv/1892335
As usual we test and prep from the PPA and then push through
SRU/Security as applicable.
** Affects: postgresql-9.5 (Ubuntu Xenial)
Importance: Undecided
Status: Triaged
** Affects: postgresql-10 (Ubuntu Bionic)
Importance: Undecided
Status: Triaged
** Affects: postgresql-12 (Ubuntu Focal)
Importance: Undecided
Status: Triaged
** Affects: postgresql-12 (Ubuntu Groovy)
Importance: Undecided
Status: Triaged
** Affects: postgresql-12 (Ubuntu Hirsute)
Importance: Undecided
Status: Triaged
** Affects: postgresql-13 (Ubuntu Hirsute)
Importance: Undecided
Status: In Progress
** Changed in: postgresql-10 (Ubuntu Bionic)
Status: New => Triaged
** Changed in: postgresql-12 (Ubuntu Focal)
Status: New => Triaged
** Changed in: postgresql-12 (Ubuntu Groovy)
Status: New => Triaged
** Changed in: postgresql-13 (Ubuntu Hirsute)
Status: New => Triaged
** Changed in: postgresql-9.5 (Ubuntu Xenial)
Status: New => Triaged
** No longer affects: postgresql-12 (Ubuntu)
** Changed in: postgresql-12 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: postgresql-12 (Ubuntu Hirsute)
Status: Invalid => Won't Fix
** Description changed:
[Impact]
- * MRE for latest stable fixes of Postgres release on August 13th.
+ * MRE for latest stable fixes of Postgres release on August 13th.
[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.
+ * 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]
- * Upstreams tests are usually great and in additon in the Archive there
- are plenty of autopkgtests that in the past catched issues before being
- released.
- But never the less 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 hickups (flaky) that need to be
- clarified to be sure. Pre-checks will catch those to be discussed upfront (as last time)
+ * Upstreams tests are usually great and in additon in the Archive there
+ are plenty of autopkgtests that in the past catched issues before being
+ released.
+ But never the less 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 hickups (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
- * This includes a fix for CVE:
- CVE-2020-25695
+ * This is a reoccurring MRE, see below and all the references
+ * This includes a fix for CVE:
+ CVE-2020-25695
---
Current versions in supported releases:
- postgresql-9.5 | 9.5.23-0ubuntu0.16.04.1 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
- postgresql-10 | 10.14-0ubuntu0.18.04.1 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x
- postgresql-12 | 12.4-0ubuntu0.20.04.1 | focal-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
- postgresql-12 | 12.4-1 | groovy | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
- postgresql-13 | 13.0-6build1 | hirsute-proposed/universe | source, riscv64
-
+ postgresql-9.5 | 9.5.23-0ubuntu0.16.04.1 | xenial-updates
+ postgresql-10 | 10.14-0ubuntu0.18.04.1 | bionic-updates
+ postgresql-12 | 12.4-0ubuntu0.20.04.1 | focal-updates
+ postgresql-12 | 12.4-1 | groovy
+ postgresql-13 | 13.0-6build1 | hirsute-proposed/universe
Special cases:
- Hirsute will as usual be synced from Debian.
- I already see
- postgresql-13 | 13.1-1 | unstable | source, amd64, arm64, armhf, i386, ppc64el, s390x
+ I already see
+ postgresql-13 | 13.1-1 | unstable | source, amd64, arm64, armhf, i386, ppc64el, s390x
- 21.04 also has a postgresql-12 but that is on the way to be removed and postgesql-common already points to -13.
-
Last relevant related stable updates: 9.5.23, 10.14 and 12.4
You'll see that the last update was missed, so I'll combined them.
Standing MRE - Consider last updates as template:
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676
- pad.lv/1752271
- pad.lv/1786938
- pad.lv/1815665
- pad.lv/1828012
- pad.lv/1833211
- pad.lv/1839058
- pad.lv/1863108
- pad.lv/1892335
As usual we test and prep from the PPA and then push through
SRU/Security as applicable.
** Description changed:
[Impact]
* MRE for latest stable fixes of Postgres release on August 13th.
[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]
* Upstreams tests are usually great and in additon in the Archive there
are plenty of autopkgtests that in the past catched issues before being
released.
But never the less 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 hickups (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
* This includes a fix for CVE:
CVE-2020-25695
---
Current versions in supported releases:
postgresql-9.5 | 9.5.23-0ubuntu0.16.04.1 | xenial-updates
- postgresql-10 | 10.14-0ubuntu0.18.04.1 | bionic-updates
- postgresql-12 | 12.4-0ubuntu0.20.04.1 | focal-updates
- postgresql-12 | 12.4-1 | groovy
- postgresql-13 | 13.0-6build1 | hirsute-proposed/universe
+ postgresql-10 | 10.14-0ubuntu0.18.04.1 | bionic-updates
+ postgresql-12 | 12.4-0ubuntu0.20.04.1 | focal-updates
+ postgresql-12 | 12.4-1 | groovy
+ postgresql-13 | 13.0-6build1 | hirsute-proposed/universe
Special cases:
- Hirsute will as usual be synced from Debian.
I already see
postgresql-13 | 13.1-1 | unstable | source, amd64, arm64, armhf, i386, ppc64el, s390x
- - 21.04 also has a postgresql-12 but that is on the way to be removed and postgesql-common already points to -13.
+ - 21.04 also has a postgresql-12 and while that is on the way to be
+ removed and fulyl replaced by 13 that is too far out. Therefore we will
+ upload 12.5 to Hirsute as well
Last relevant related stable updates: 9.5.23, 10.14 and 12.4
You'll see that the last update was missed, so I'll combined them.
Standing MRE - Consider last updates as template:
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676
- pad.lv/1752271
- pad.lv/1786938
- pad.lv/1815665
- pad.lv/1828012
- pad.lv/1833211
- pad.lv/1839058
- pad.lv/1863108
- pad.lv/1892335
As usual we test and prep from the PPA and then push through
SRU/Security as applicable.
** Description changed:
[Impact]
* MRE for latest stable fixes of Postgres release on August 13th.
[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]
* Upstreams tests are usually great and in additon in the Archive there
are plenty of autopkgtests that in the past catched issues before being
released.
But never the less 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 hickups (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
* This includes a fix for CVE:
CVE-2020-25695
---
Current versions in supported releases:
postgresql-9.5 | 9.5.23-0ubuntu0.16.04.1 | xenial-updates
postgresql-10 | 10.14-0ubuntu0.18.04.1 | bionic-updates
postgresql-12 | 12.4-0ubuntu0.20.04.1 | focal-updates
postgresql-12 | 12.4-1 | groovy
postgresql-13 | 13.0-6build1 | hirsute-proposed/universe
Special cases:
- Hirsute will as usual be synced from Debian.
I already see
postgresql-13 | 13.1-1 | unstable | source, amd64, arm64, armhf, i386, ppc64el, s390x
- - 21.04 also has a postgresql-12 and while that is on the way to be
- removed and fulyl replaced by 13 that is too far out. Therefore we will
- upload 12.5 to Hirsute as well
+ - 21.04 also has a postgresql-12 and while that is on the way to be
+ removed and fulyl replaced by 13 that is too far out. Therefore we will
+ upload 12.5 to Hirsute as well.
+ - I have checked with Debian (they are affected by the same FTFBS and test
+ fails of bug 1903573) but they will just remove postgresql-12 from
+ testing. We can't do that yet on hirsute without breaking too much
Last relevant related stable updates: 9.5.23, 10.14 and 12.4
You'll see that the last update was missed, so I'll combined them.
Standing MRE - Consider last updates as template:
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676
- pad.lv/1752271
- pad.lv/1786938
- pad.lv/1815665
- pad.lv/1828012
- pad.lv/1833211
- pad.lv/1839058
- pad.lv/1863108
- pad.lv/1892335
As usual we test and prep from the PPA and then push through
SRU/Security as applicable.
** Changed in: postgresql-12 (Ubuntu Hirsute)
Status: Won't Fix => Triaged
** Changed in: postgresql-13 (Ubuntu Hirsute)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1903978
Title:
New upstream microreleases 9.5.24 10.15, 12.5 and 13.1
Status in postgresql-9.5 source package in Xenial:
Triaged
Status in postgresql-10 source package in Bionic:
Triaged
Status in postgresql-12 source package in Focal:
Triaged
Status in postgresql-12 source package in Groovy:
Triaged
Status in postgresql-12 source package in Hirsute:
Triaged
Status in postgresql-13 source package in Hirsute:
In Progress
Bug description:
[Impact]
* MRE for latest stable fixes of Postgres release on August 13th.
[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]
* Upstreams tests are usually great and in additon in the Archive there
are plenty of autopkgtests that in the past catched issues before being
released.
But never the less 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 hickups (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
* This includes a fix for CVE:
CVE-2020-25695
---
Current versions in supported releases:
postgresql-9.5 | 9.5.23-0ubuntu0.16.04.1 | xenial-updates
postgresql-10 | 10.14-0ubuntu0.18.04.1 | bionic-updates
postgresql-12 | 12.4-0ubuntu0.20.04.1 | focal-updates
postgresql-12 | 12.4-1 | groovy
postgresql-13 | 13.0-6build1 | hirsute-proposed/universe
Special cases:
- Hirsute will as usual be synced from Debian.
I already see
postgresql-13 | 13.1-1 | unstable | source, amd64, arm64, armhf, i386, ppc64el, s390x
- 21.04 also has a postgresql-12 and while that is on the way to be
removed and fulyl replaced by 13 that is too far out. Therefore we will
upload 12.5 to Hirsute as well.
- I have checked with Debian (they are affected by the same FTFBS and test
fails of bug 1903573) but they will just remove postgresql-12 from
testing. We can't do that yet on hirsute without breaking too much
Last relevant related stable updates: 9.5.23, 10.14 and 12.4
You'll see that the last update was missed, so I'll combined them.
Standing MRE - Consider last updates as template:
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676
- pad.lv/1752271
- pad.lv/1786938
- pad.lv/1815665
- pad.lv/1828012
- pad.lv/1833211
- pad.lv/1839058
- pad.lv/1863108
- pad.lv/1892335
As usual we test and prep from the PPA and then push through
SRU/Security as applicable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/xenial/+source/postgresql-9.5/+bug/1903978/+subscriptions
Follow ups
