Package: git Version: 1:2.13.2-3 The dgit test suite has started failing with this message. I looked in various places to try to find out why.
Amongst my attempts where man git-remote-ext man git-push man git-pull dpkg -L git-man | xargs zegrep '\bext\b' 2>/dev/null |less -S dpkg -L git-man | xargs zegrep '\btransport\b' 2>/dev/null |less -S I dug into the git source code to find out what was going on. I found that the source code talks about protocols, not transports. Hence I found the real answer in: man git-config |less +/'protocol.*allow' Please could, at the very least, git-remote-ext document this behaviour: ie specifically, git-remote-ext(1) should say that the feature needs to be explicitly enabled. Secondly, I see from the source code that one can set GIT_ALLOW_PROTOCOL to a :-separated list. Could this please also be documented ? Thirdly: please could incompatible changes be documented somewhere more obvious - how about NEWS.Debian.gz ? Fourthly: if this change was done for security reasons, why has it not been done in stretch ? Thanks for your attention, Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
