New upstream microreleases 9.5.24 10.15, 12.5 and 13.1

[Christian Ehrhardt ]

[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 CVEs:
   CVE-2020-25694
   CVE-2020-25695
   CVE-2020-25696

---

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.

---

Interim test state

Xenial
https://bileto.ubuntu.com/excuses/4331/xenial.html
Good except the following which are all masked in hints-ubuntu
 bareos/14.2.6-3
 libreoffice/1:5.1.6~rc2-0ubuntu1~xenial10
 pdns/4.0.0~alpha2-3build1: amd64
 pgpool2/3.4.3-1: amd64

Bionic
https://bileto.ubuntu.com/excuses/4332/bionic.html
Good except the following which are all masked in hints-ubuntu
 pdns/4.1.1-1
 pglogical/2.1.1-1
 postgresql-multicorn/1.3.4-1

Focal
https://bileto.ubuntu.com/excuses/4333/focal.html
Many i386 dependency issues - all masked in hints-ubuntu
Good except the following which are all masked in hints-ubuntu
 postgresql-multicorn/1.3.4-31-g9ff7875-3
 diaspora-installer/0.7.6.1+debian1

Groovy
https://bileto.ubuntu.com/excuses/4334/groovy.html
Many i386 dependency issues - all masked in hints-ubuntu
The rest are the usual suspects which are ok
 pdns/4.3.0-4build2
 pglogical/2.3.2-1
 pglogical-ticker/1.4.0-2

[Christian Ehrhardt  (paelzer)]

PPAs
X: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4331/+packages
B: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4332/+packages
F: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4333/+packages
G: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4334/+packages
H: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4335/+packages

[Christian Ehrhardt  (paelzer)]

As expected the hirsute FTBFS are gone with the updates, but we need some testing to be able to push it further.

[Christian Ehrhardt  (paelzer)]

I have added an overview of the test results (on PPAs) to the description as I can more easily "update" it to the later state. So far everything LGTM. Will need to recheck once more tests got through on the busy autopkgtest.u.c

[Christian Ehrhardt  (paelzer)]

Special cases I:
euslisp in groovy was reset with 9.27+dfsg-6
Currently we have 9.27+dfsg-7 in Hirsute.

The tests in general seem to work in [1] devel but never did on the older version in groovy [2].
Since the test expectations had a reset there and no successful run that counts as "valid".

[1]: https://autopkgtest.ubuntu.com/packages/euslisp/hirsute/ppc64el
[2]: https://autopkgtest.ubuntu.com/packages/euslisp/groovy/ppc64el

[Christian Ehrhardt  (paelzer)]

Special Cases II:
libreoffice @ groovy @ arm* - known to be flaky and flaking around - annoying but nothing to stop this

[Christian Ehrhardt  (paelzer)]

Focal - asterisk @ armhf resolved

[Christian Ehrhardt  (paelzer)]

Special Cases III:
postgesql-rum æ armhf is one of the (unfortunate) flaky test env cases. Not related to the actual upload [1]. I have restarted it (the queue is too long to wait) and ran it locally (good).
Furthermore the very same PostgreSQL source code in Groovy has tested successfully already [2]
and the package itself is also the same F/G
 postgresql-rum | 1.3.6-2 | focal/universe | source
 postgresql-rum | 1.3.6-2 | groovy/universe | source

Therefore we can already assume that postgresql-rum will complete on a retry, but due to the 5k test queue that will take a while.

[1]: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ci-train-ppa-service-4333/focal/armhf/p/postgresql-rum/20201113_113310_58535@/log.gz
[2]: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ci-train-ppa-service-4334/groovy/armhf/p/postgresql-rum/20201113_004959_07de2@/log.gz

[Christian Ehrhardt  (paelzer)]

Overall it seems all tests are good or known bad cases.
I think we are good to release this through security, I'll ping Marc to consider this.

[Brian Murray (brian-murray)]

The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release

[Christian Ehrhardt  (paelzer)]

Hmm these got updated through -security already.
Missed the bug update due to changelogs.
Setting them to released manually now.