From b3115fd7c355b43dcfc7b9cfd53104e5540f842f Mon Sep 17 00:00:00 2001 From: Alex Vandiver Date: Tue, 28 Nov 2023 17:52:38 +0000 Subject: [PATCH] Revert "ci: Temporarily upgrade postgresql-client-common before upgrading." This reverts commit 2ec288a9837eb1395d870d4ca05f9ed7eaf2f12d. Debian fixed this in https://salsa.debian.org/postgresql/postgresql-common/-/commit/7df2322ef5d37417afd7dcc3a7ed77a6a5a14820, and it was released as version 257: https://metadata.ftp-master.debian.org/changelogs//main/p/postgresql-common/postgresql-common_257_changelog --- .github/workflows/production-suite.yml | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/.github/workflows/production-suite.yml b/.github/workflows/production-suite.yml index 9362db61c4..c636b374fe 100644 --- a/.github/workflows/production-suite.yml +++ b/.github/workflows/production-suite.yml @@ -280,17 +280,6 @@ jobs: sudo mkdir -p "${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 run: sudo /tmp/production-upgrade