Hi Aloïs, On 10-11-2020 00:38, Aloïs Micard wrote: > I've uploaded a new version of golang-github-pkg-term [1], and by > doing so, broke the build of golang-github-c-bata-go-prompt [2] & > golang-github-jaguilar-vt100 [3].
Ack. So, the new golang-github-pkg-term Breaks the version of golang-github-c-bata-go-prompt and golang-github-jaguilar-vt100 in testing? Then, declare that. Or doesn't "broke the build" imply that? > I've updated the packaging of the later two, and uploaded them to > unstable, where the build of the 3 packages now succeed [4][5][6]. > > But sadly, the migration to testing for golang-github-pkg-term > won't happen because it would break the testing build of > golang-github-pkg-term & golang-github-c-bata-go-prompt. > > In the meantime, these packages won't migrate to testing because > golang-github-pkg-term is not migrating. > > I don't know what kind of fix I should made to allow these packages > to migrate to testing. > > Have you an idea? Fix the package relations. If the new version of something breaks the old version of something else, it should declare that with a versioned Breaks. Paul
signature.asc
Description: OpenPGP digital signature
