Update to 17.5, 16.9, 15.13, 14.18, 13.21 #1340
Conversation
|
Hmm, I wonder if updating The copies in 13.21 were last updated 5 years ago (https://github.com/postgres/postgres/tree/REL_13_21/config) but in 17.5 they're barely a year old (https://github.com/postgres/postgres/tree/REL_17_5/config). We could do some build tests to find out, or we could just remove them and find out downstream. 🙈 (I think |
|
Oh, we're pulling those from a specific commit, and it's a commit that's older than the file in 13.21 (2017 vs 2020), so we're already doing net worse than upstream and we should absolutely remove these lines! ✨ |
When we added these lines, we needed newer files than PostgreSQL had upstream, but the situation has changed and we were pinned to a specific commit from 2017 - the _oldest_ PostgreSQL release version has a file from 2020.
Changes: - docker-library/postgres@437897c: Merge pull request docker-library/postgres#1340 from infosiftr/update - docker-library/postgres@b234702: Remove explicit config.guess/config.sub updates - docker-library/postgres@2667482: Update to 17.5, 16.9, 15.13, 14.18, 13.21
The automated update keeps failing build tests for various (flaky build type) reasons, so I'm opening this to explicitly race the retries and see if we can get to success or more clear failures (especially ones that aren't the ongoing issues we've been seeing for days on gnu.org).