Package: git-debrebase Version: 9.12 Severity: normal
The issue is that when I try to update tyo a new release I get this complaint: $ git debrebase new-upstream 20.05 git-debrebase: snag detected (-fanchor-treated): old anchor is recognised due to --anchor, cannot check upstream I don't understand what it is complaining about and whilst -fanchor is described in man 1 git-debrebase -fanchor-treated is not. So documenting this would be good. If you explain it to me I could try and document it myself and supply a patch. The situation is this: I prepared a package (armnn 19.11) using dgit and the dgit-maint-debrebase process. https://browse.dgit.debian.org/armnn.git/log/ a while ago. I copied it to salsa, where my collaborator Francis added some more patches to both upstream and debian/ dir (He also did a load of psuedomerging which I _think_ included operations not permitted in a git debrebasing repo - it was certainly messy). https://salsa.debian.org/deeplearning-team/armnn The task is now to update to 20.05 release (from https://github.com/ARM-software/armnn) If I just "dgit clone armnn", make sure it knows about upstream and "git debrebase new-upstream 20.08" I get the above issue. I also get the same complaint if I take my existing repo, cherry-pick the good patches out of the above salsa mess, and then try to git debrebase new-upstream 20.08 git-debrebase thinks the anchor is the initial "Add debian dir with initial packaging" which seems correct. Adding -fanchor-treated makes the rebase proceed as expected, but I'd like to understand why that is needed rather than blindly adding it.
