Hi Tobias, On 11/2/25 13:43, Dr. Tobias Quathamer wrote:
Moreover, the package golang-github-charmbracelet-x cannot migrate due to autopkgtest failures in two other packages in testing, golang-github- charmbracelet-bubbletea and golang-github-charmbracelet-huh, which are both too old to cope with the new golang-github-charmbracelet-x package.
The usual question here is: is this breakage a mere autopkgtest issue, or would the user also experience breakage if binaries from golang-github-charmbracelet-x would migrate and/or get installed, but the binaries from golang-github-charmbracelet-bubbletea and golang-github-charmbracelet-huh stay at the version as currently in testing? If there is breakage for the user, it's best to add a versioned Breaks to the right binaries from golang-github-charmbracelet-x. With those versioned Breaks in place, the migration software will also trigger the tests with binaries from both sources from unstable.
If this is merely a test issue (and you don't want to add the Breaks), I can pull some strings behind the scene.
Paul
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature