Bug#1010843: Bash completion filename conflict with LXD

2022-06-17 Thread Mathias Gibbens
On Wed, 2022-05-11 at 17:18 -0300, Antonio Terceiro wrote: > It turns out that that portion of our debian/rules is deprecated as > that > is already handled by the upstream build system. This needs an > upsteam > change, which I submitted in the link above. lxc 5.0.0 was just recently tagged [1]

Bug#1010843: Bash completion filename conflict with LXD

2022-05-11 Thread Antonio Terceiro
Control: forwarded -1 https://github.com/lxc/lxc/pull/4115 Control: tag -1 + upstream confirmed On Wed, May 11, 2022 at 11:20:37AM +, Mathias Gibbens wrote: > Source: lxc > Version: 1:4.0.11-1 > > Hi, > > While reviewing the LXD packaging I've been working on, it was > noticed [1] that the

Bug#1010843: Bash completion filename conflict with LXD

2022-05-11 Thread Mathias Gibbens
Source: lxc Version: 1:4.0.11-1 Hi, While reviewing the LXD packaging I've been working on, it was noticed [1] that the bash completion file that's being shipped needs to be renamed. Since the LXD client executable is `lxc`, the installed path would be /usr/share/bash-completion/completions/lxc