ci: Temporarily upgrade postgresql-client-common before upgrading.

This works around a failure in the current postgresql-client-common
and postgresql-client-15 packages; it exists primarily to improve
the signal on our CI builds, as the failure is a real failure caused
by the package upgrade process.
This commit is contained in:
Alex Vandiver 2023-09-15 09:39:38 -04:00 committed by Tim Abbott
parent db8229ae32
commit 2ec288a983
1 changed files with 11 additions and 0 deletions

View File

@ -288,6 +288,17 @@ jobs:
sudo mkdir -p "${dirs[@]}" sudo mkdir -p "${dirs[@]}"
sudo chown -R github "${dirs[@]}" sudo chown -R github "${dirs[@]}"
- name: Temporarily bootstrap PostgreSQL upgrades
# https://chat.zulip.org/#narrow/stream/43-automated-testing/topic/postgres.20client.20upgrade.20failures/near/1640444
# On Debian, there is an ordering issue with post-install maintainer
# scripts when postgresql-client-common is upgraded at the same time as
# postgresql-client and postgresql-client-15. Upgrade just
# postgresql-client-common first, so the main upgrade process can
# succeed. This is a _temporary_ work-around to improve CI signal, as
# the failure does represent a real failure that production systems may
# encounter.
run: sudo apt-get update && sudo apt-get install -y --only-upgrade postgresql-client-common
- name: Upgrade production - name: Upgrade production
run: sudo /tmp/production-upgrade run: sudo /tmp/production-upgrade