Repository navigation
Say PGDG serves 1.0~RC1 on Debian 13 and point to the container - #89
Closed
GuanzhouSong wants to merge 1 commit into
Closed
GuanzhouSong wants to merge 1 commit into
GuanzhouSong wants to merge 1 commit into
Conversation
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
2 participants
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 PGDG section still says PGDG publishes 0.116 for Debian 13. Its
trixie-pgdgcandidate is now1.0~RC1-2, so a reader who follows the steps installs a release candidate, and a host that ran an RC can't be upgraded to 1.0. The page now says PGDG lags first-party releases, to install from PGDG only once the candidate is1.0-0or later, and to use DocumentDB Local or the operator on Debian 13 until then.documentdb.io now shows this page as moved, but GitHub readers still land on it.
The pool already has
1.0~RC2sources, but the Debian 13 index still serves RC1 (checked 2026-10-19). RC2 wouldn't help either, since no RC can be upgraded to 1.0.Supersedes #85: #88 replaced the RC page it edits.