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

This reverts commit 2ec288a983.
Debian fixed this in
7df2322ef5,
and it was released as version 257:
https://metadata.ftp-master.debian.org/changelogs//main/p/postgresql-common/postgresql-common_257_changelog
This commit is contained in:
Alex Vandiver 2023-11-28 17:52:38 +00:00 committed by Anders Kaseorg
parent 1d52d08803
commit b3115fd7c3
1 changed files with 0 additions and 11 deletions

View File

@ -280,17 +280,6 @@ 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