Hi, >> On Wed, 21 Apr 2021 10:12:03 +0000 Damyan Ivanov <d...@debian.org> wrote:
>>> Sigh. Now git reverted to using /usr/lib again, and git-flow is broken. Why sigh? Directories such as /usr/lib/git-core and /usr/libexec/git-core are internal to git. Other packages should not install to either directory. This is not a new thing: the standard way to contribute new git subcommands has been to install them to $PATH from the start. Version 2.31.0-1 of Debian's Git package changed an internal directory from /usr/lib/git-core to /usr/libexec/git-core. That caused problems for people, so 2.31.1-1 reverted the change. See https://bugs.debian.org/985416 for more details, including these should install to /usr/bin/ instead. The exact location where git stores its commands is an implementation detail that packages are not meant to rely on. If I had known about these callers, then I would have filed some preparatory bugs instead of making that change in 2.31.0-1. The change was in experimental for a long time before then, so one way to prevent future such issues is to test against git from experimental. If git-flow wants to depend on Git internals, contacting the git package maintainers is appreciated. That is especially true when the internal details you're depending on are changing. Thanks and hope that helps, Jonathan
