Repository navigation
Track existing pydicom trixie request and refresh the merged debdiff - #6
Merged
Merged
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
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 local draft proposed a new trixie-pu request even though Karsten had already filed #1148120. Mark that draft superseded and point tracking to the existing release-team request, preventing a duplicate submission.
Refresh the debdiff to the Debian Med trixie source that includes merged MR !1. Its changelog, control, gbp.conf, patch and patch series matched the previously built source (2,117 tests passed, 535 skipped); retain the known debrebuild CI failure in the historical draft.
Validation: shell syntax, patch sanity checks and README/fixes.yaml consistency passed. Documentation whitespace checked; preserved the exact validated debdiff, including its nested patch context whitespace.