Fix the pgmodeler image build - #49
Merged
Merged
Conversation
…repo The base image (ghcr.io/printeers/pgmodeler:latest) moved to Ubuntu questing, for which apt.postgresql.org publishes no repository, so the image has not built since v0.12.3. PGDG only serves the LTS releases; noble's postgresql-client-18 runs fine on questing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
-pgmodelerimage variant has not built since v0.12.3, and failed againfor v0.12.4: the base image (
ghcr.io/printeers/pgmodeler:latest) moved toUbuntu questing (25.10), and apt.postgresql.org publishes no repository for
it, so the build dies on
PGDG only serves the LTS codenames (jammy, noble), and questing's own repo
carries postgresql-client 17, not the 18 that must match the embedded
postgres. So take the client from the noble repo explicitly instead of
deriving the codename from the base image; those binaries run fine on
questing.
Verified by building the image locally and running the ipp repo's
trek-pristine command against it: pgmodeler-cli starts, testdata insertion
through psql works, and it exits 0 with no diff statements.
Needs a release afterwards so a working
-pgmodelerimage exists forv0.12.4's logging change (ipp is pinned to 0.12.3-pgmodeler until then).