fix: postgresql-{16,17,18}-oci-entrypoint build silently produced broken packages #78605
+12
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #78604
Related:
Summary
The builds for all postgresql oci-entrypoint-base packages are broken without this PR. The entrypoint files downloaded from the Docker, Inc. upstream repository during build time only contain the text "404: Not found." See linked issue for more details.
Pre-review Checklist
Note: To the best of my understanding, none of the checklists from the template apply to this PR, as it strictly fixes an issue with existing build files without bumping any version fields.
The only thing I assume might be necessary is actually increasing the epoch field for these packages.Yep, as per epoch-bot's complaints, I've bumped the epoch fields to force rebuilds across the board.For new package PRs only
For new version streams
For package updates (renames) in the base images
For security-related PRs
For version bump PRs
For PRs that add patches