Hey
Am 09.01.2024 um 16:53 schrieb Lena Voytek:
Hi Patrick,
Thanks for the reply. I looked into it again and realized this bug
only shows up if the bash-completion package is installed beforehand.
If so, then due to upstream commit 064328f7dd307916 the install
directory changes to /usr/share/bash-completion/completions. This
actually causes an issue in Ubuntu, but it looks like Debian's build
system handles it correctly as is. Sorry for the invalid issue!
Hm good point, thanks for testing. I think in this case it would be
"build" safer also in not clean environments to b-d on bash-completion
and let glusterfs then use the correct path.
I will test it in the next days if it builds clean in both ways
On Tue, Jan 9, 2024 at 2:49 AM Patrick Matthäi <patr...@linux-dev.org>
wrote:
Hi Lena,
Am 02.01.2024 um 15:29 schrieb Lena Voytek:
Source: glusterfs
Version: 11.1-3
Followup-For: Bug #1059859
X-Debbugs-Cc:l...@voytek.dev
Here is the patch
Thanks for your patch, but building it on sid gives me this error:
find debian/tmp/usr/lib -type f -name \*.la -delete dh_install
Failed to copy
'/usr/share/bash-completion/completions/gluster.bash': No such
file or directory at /usr/share/dh-exec/dh-exec-install-rename
line 70, <> line 2. dh_install: error:
debian/glusterfs-cli.install (executable config) returned exit
code 127 make[1]: *** [debian/rules:34: override_dh_install] Error
127 make[1]: Leaving directory '/build/glusterfs-11.1' make: ***
[debian/rules:20: binary] Error 2
