Hi Aloïs, On 10-11-2020 23:31, Aloïs Micard wrote: > I've now read the documentation here [1].
Hmm, I don't think that page describes your situation. [POLICY] looks more appropriate. [POLICY] https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks > Just to confirm, does the following changes > looks goods to you? > > - I'll add the following to d/control of golang-github-pkg-term > > ``` > Breaks: golang-github-c-bata-go-prompt (<<0.2.3+git20181109.b6d2b43-2), > golang-github-jaguilar-vt100 (<<0.0~git20201024.81de19c-1) > ``` Yes. Depending on how you support backports or other schemes, you could add a tilde (~) at the end. > (the version indicated here are the newest that haven't migrated to > testing) I assume you have the right version. > - And made a new release + upload it to unstable. > > To sum up: > > Is declaring that new version of golang-github-pkg-term breaks > old version of golang-github-c-bata-go-prompt & > golang-github-jaguilar-vt100 > enough to make the 3 packages migrate to testing? If nothing else is broken, yes. The migration software will trigger the autopkgtests together with such a relation. Paul
