Bug#985416: Bug#986565: unusable with current git
Hi, >> On Wed, 21 Apr 2021 10:12:03 + Damyan Ivanov 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
Bug#986565: unusable with current git
Hi everyone, * Lisandro Damián Nicanor Pérez Meyer [210423 21:06]: > Hi! Indeed it's not working again, so reopening the bug. > > On Wed, 21 Apr 2021 10:12:03 + Damyan Ivanov wrote: > > Sigh. Now git reverted to using /usr/lib again, and git-flow is broken. It appears some more coordination between git and related packages would be in order. Right now, the versions in testing do not work together: git 1:2.30.2-1 installs into /usr/lib git-flow 1.12.3-2 installs into /usr/libexec I guess git 1:2.31.1-1 will be stuck in unstable? Please somehow coordinate on what the correct path is/should be. Thanks, Chris
Bug#986565: unusable with current git
reopen 986565 thanks Hi! Indeed it's not working again, so reopening the bug. On Wed, 21 Apr 2021 10:12:03 + Damyan Ivanov wrote: > Package: git-flow > Version: 1.12.3-2 > Followup-For: Bug #986565 > > Control: reopen -1 1.12.3-2 > > Sigh. Now git reverted to using /usr/lib again, and git-flow is broken. > > Reverting the changes in 1.12.3-2 would fix it. > > Reading https://bugs.debian.org/985416 (the bug report in git about changing > the path), I am left with the impression that the proper fix is to ship > /usr/bin/git-flow. Perhaps the other scripts need to be in /usr/bin too. > > > HTH, > Damyan > > > -- System Information: > Debian Release: 11.0 > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), > (500, 'stable'), (500, 'oldstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages git-flow depends on: > ii git [git-core] 1:2.31.1-1 > ii git-core1:2.15.0~rc0-1 > > git-flow recommends no packages. > > git-flow suggests no packages. > > -- no debconf information > >
Bug#986565: unusable with current git
Package: git-flow Version: 1.12.3-2 Followup-For: Bug #986565 Control: reopen -1 1.12.3-2 Sigh. Now git reverted to using /usr/lib again, and git-flow is broken. Reverting the changes in 1.12.3-2 would fix it. Reading https://bugs.debian.org/985416 (the bug report in git about changing the path), I am left with the impression that the proper fix is to ship /usr/bin/git-flow. Perhaps the other scripts need to be in /usr/bin too. HTH, Damyan -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages git-flow depends on: ii git [git-core] 1:2.31.1-1 ii git-core1:2.15.0~rc0-1 git-flow recommends no packages. git-flow suggests no packages. -- no debconf information
Bug#986565: unusable with current git
Package: git-flow Version: 1.12.3-1 Severity: grave Tags: patch Today 'flow' is not a supported git command: $git flow git: 'flow' is not a git command. See 'git --help'. The most similar commands are reflog show Running it under strace reveals that git looks for commands under /usr/libexec/git-core, while git-flow installs things under /usr/lib/git-core Perhaps this is caused by a change in the search path in git and git-flow needs to adapt. Replacing /usr/lib/git-core with /usr/libexec/git-core in debian/install.mk seems to fix the problem. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages git-flow depends on: ii git [git-core] 1:2.31.0-1 ii git-core1:2.15.0~rc0-1 git-flow recommends no packages. git-flow suggests no packages. -- debconf-show failed
