Redirect bookworm entry script to default-branch webconfig#8
Draft
d4rken wants to merge 1 commit into
Draft
Conversation
The deployed bg-update.sh on 2025/bookworm feeders fetches this entry script from the bookworm branch, which currently hardcodes a clone of the bookworm branch and so perpetually reinstalls the old webconfig. Point it at the default-branch webconfig so a single Update Feeder run migrates the feeder onto the channel-aware webconfig; after that this branch is no longer consulted. Downloads to a temp file and runs it rather than eval-piping.
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
1 participant
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 deployed
bg-update.shon 2025/bookworm feeders fetchesupdate-webconfig.shfrom thebookwormbranch. That copy currently hardcodesgit clone -b bookworm, so clicking Update permanently reinstalls the old bookworm webconfig.This points the entry script at the default-branch (
master) webconfig: it downloadsmaster'supdate-webconfig.shto a temp file and runs it, so a single Update run installs the channel-aware webconfig. After that first upgrade the channel system takes over and this branch is no longer consulted.Draft on purpose — merge only at go-live, after the default branch carries the release code.