group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #34364
[Bug 1863108] [NEW] New upstream microreleases 9.5.21 10.12 11.7 and 12.2
Public bug reported:
[Impact]
* MRE for latest stable fixes of Postgres release on Feb 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-1720 (Affects 9.6-12, so all but xenial)
---
Current versions in supported releases:
postgresql-9.5 | 9.5.19-0ubuntu0.16.04 xenial
postgresql-10 | 10.10-0ubuntu0.18.04.1 bionic
postgresql-11 | 11.5-1eoan
postgresql-12 | 12.1-2build1 focal
Special cases:
- Focal will as usual be synced from Debian.
I already see https://buildd.debian.org/status/fetch.php?pkg=postgresql-12&arch=s390x&ver=12.2-1&stamp=1581600108&raw=0
Last relevant related stable updates: 9.5.21, 10.12, 11.5 and 12.2
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
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-11 (Ubuntu Eoan)
Importance: Undecided
Status: Triaged
** Affects: postgresql-12 (Ubuntu Focal)
Importance: Undecided
Status: In Progress
** No longer affects: postgresql-11 (Ubuntu)
** Changed in: postgresql-10 (Ubuntu Bionic)
Status: New => Triaged
** Changed in: postgresql-11 (Ubuntu Eoan)
Status: New => Triaged
** Changed in: postgresql-12 (Ubuntu Focal)
Status: New => Triaged
** Changed in: postgresql-9.5 (Ubuntu Xenial)
Status: New => Triaged
** Description changed:
[Impact]
* MRE for latest stable fixes of Postgres release on Feb 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-1720
---
Current versions in supported releases:
postgresql-9.5 | 9.5.19-0ubuntu0.16.04 xenial
postgresql-10 | 10.10-0ubuntu0.18.04.1 bionic
postgresql-11 | 11.5-1eoan
postgresql-12 | 12.1-2build1 focal (will sync 12.2-1 from Debian)
Special cases:
- Focal will as usual be synced from Debian.
Last relevant related stable updates: 9.5.21, 10.12, 11.5 and 12.2
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
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 Feb 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-1720
---
Current versions in supported releases:
postgresql-9.5 | 9.5.19-0ubuntu0.16.04 xenial
postgresql-10 | 10.10-0ubuntu0.18.04.1 bionic
postgresql-11 | 11.5-1eoan
- postgresql-12 | 12.1-2build1 focal (will sync 12.2-1 from Debian)
+ postgresql-12 | 12.1-2build1 focal
Special cases:
- Focal will as usual be synced from Debian.
+ I already see https://buildd.debian.org/status/fetch.php?pkg=postgresql-12&arch=s390x&ver=12.2-1&stamp=1581600108&raw=0
Last relevant related stable updates: 9.5.21, 10.12, 11.5 and 12.2
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
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 Feb 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-1720
+ * This includes a fix for CVE: CVE-2020-1720 (Affects 9.6-12, so all but xenial)
---
Current versions in supported releases:
postgresql-9.5 | 9.5.19-0ubuntu0.16.04 xenial
postgresql-10 | 10.10-0ubuntu0.18.04.1 bionic
postgresql-11 | 11.5-1eoan
postgresql-12 | 12.1-2build1 focal
Special cases:
- Focal will as usual be synced from Debian.
I already see https://buildd.debian.org/status/fetch.php?pkg=postgresql-12&arch=s390x&ver=12.2-1&stamp=1581600108&raw=0
Last relevant related stable updates: 9.5.21, 10.12, 11.5 and 12.2
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
As usual we test and prep from the PPA and then push through
SRU/Security as applicable.
** Changed in: postgresql-12 (Ubuntu Focal)
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/1863108
Title:
New upstream microreleases 9.5.21 10.12 11.7 and 12.2
Status in postgresql-9.5 source package in Xenial:
Triaged
Status in postgresql-10 source package in Bionic:
Triaged
Status in postgresql-11 source package in Eoan:
Triaged
Status in postgresql-12 source package in Focal:
In Progress
Bug description:
[Impact]
* MRE for latest stable fixes of Postgres release on Feb 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-1720 (Affects 9.6-12, so all but xenial)
---
Current versions in supported releases:
postgresql-9.5 | 9.5.19-0ubuntu0.16.04 xenial
postgresql-10 | 10.10-0ubuntu0.18.04.1 bionic
postgresql-11 | 11.5-1eoan
postgresql-12 | 12.1-2build1 focal
Special cases:
- Focal will as usual be synced from Debian.
I already see https://buildd.debian.org/status/fetch.php?pkg=postgresql-12&arch=s390x&ver=12.2-1&stamp=1581600108&raw=0
Last relevant related stable updates: 9.5.21, 10.12, 11.5 and 12.2
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
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/1863108/+subscriptions
Follow ups
