Skip to content

backport gdal upstream fix - #273

Merged
3nids merged 1 commit into
mainfrom
fix-gdal
Aug 31, 2026
Merged

3nids merged 1 commit into
mainfrom
fix-gdal

Conversation

@3nids

@3nids 3nids commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@3nids
3nids merged commit 761aa84 into main Aug 31, 2026
5 of 7 checks passed
@3nids
3nids deleted the fix-gdal branch August 31, 2026 13:37
3nids added a commit that referenced this pull request Aug 31, 2026
The port-version bump from #273 (python-extension-args.patch) never
reached the version database: the post-merge "Auto update version db"
workflow computed it but failed to push (403), so consumers resolving
through the baseline kept getting git-tree 28458c5 — the unpatched
tree — and the macOS -std=c++11 build failure with it.

Generated with the same command the workflow runs.
3nids added a commit that referenced this pull request Aug 31, 2026
Both "Format vcpkg.json" and "Check versions" run tools that rewrite
files in place and exit 0 regardless, so neither step asserted anything
-- PR #273 went green while leaving the version database stale, and the
only thing that would have caught it was the post-merge job, whose push
is currently rejected with a 403.

Compare the working tree after each step and fail with a message saying
what to run locally. Scoped by pathspec so unrelated stray files cannot
trip them, and using git status rather than git diff so that a brand new
versions/<x>-/<port>.json is caught too.
3nids added a commit that referenced this pull request Aug 31, 2026
* Update versions.db for gdal 3.13.3#1

The port-version bump from #273 (python-extension-args.patch) never
reached the version database: the post-merge "Auto update version db"
workflow computed it but failed to push (403), so consumers resolving
through the baseline kept getting git-tree 28458c5 — the unpatched
tree — and the macOS -std=c++11 build failure with it.

Generated with the same command the workflow runs.

* ci: make the static checks actually fail

Both "Format vcpkg.json" and "Check versions" run tools that rewrite
files in place and exit 0 regardless, so neither step asserted anything
-- PR #273 went green while leaving the version database stale, and the
only thing that would have caught it was the post-merge job, whose push
is currently rejected with a 403.

Compare the working tree after each step and fail with a message saying
what to run locally. Scoped by pathspec so unrelated stray files cannot
trip them, and using git status rather than git diff so that a brand new
versions/<x>-/<port>.json is caught too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant