Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1102797 > unrolled thread

Bug#1010843: Bash completion filename conflict with LXD

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1010843: Bash completion filename conflict with LXD Mathias Gibbens <mathias@calenhad.com> - 2022-05-11 13:30 +0200
    Bug#1010843: Bash completion filename conflict with LXD Antonio Terceiro <terceiro@debian.org> - 2022-05-11 22:30 +0200
      Bug#1010843: Bash completion filename conflict with LXD Mathias Gibbens <mathias@calenhad.com> - 2022-06-17 15:10 +0200

#1102797 — Bug#1010843: Bash completion filename conflict with LXD

[Multipart message — attachments visible in raw view] — view raw

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. However, that
conflicts with a file installed by the lxc package [2]. From d/rules
[3] it looks like symlinks are made of the actual lxc command names
(`lxc-*`) to the supplied completions file.

  Would it be possible to rename how that base file is named when it is
installed to /usr/share/bash-completion/completions/, so it won't
conflict if LXD installs its bash completion in the correction
location?

Thanks,
Mathias

[1] -- https://salsa.debian.org/go-team/packages/lxd/-/merge_requests/1
[2] -- https://packages.debian.org/sid/amd64/lxc/filelist
[3] -- https://salsa.debian.org/lxc-team/lxc/-/blob/master/debian/rules#L41

[toc] | [next] | [standalone]

#1102840

[Multipart message — attachments visible in raw view] — view raw

Control: forwarded -1 https://github.com/lxc/lxc/pull/4115
Control: tag -1 + upstream confirmed

On Wed, May 11, 2022 at 11:20:37AM +0000, 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 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. However, that
> conflicts with a file installed by the lxc package [2]. From d/rules
> [3] it looks like symlinks are made of the actual lxc command names
> (`lxc-*`) to the supplied completions file.
> 
>   Would it be possible to rename how that base file is named when it is
> installed to /usr/share/bash-completion/completions/, so it won't
> conflict if LXD installs its bash completion in the correction
> location?

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.

[toc] | [prev] | [next] | [standalone]

#1106811

[Multipart message — attachments visible in raw view] — view raw

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], which is the first release
that includes the corrected bash completion filename. It looks like the
biggest change is switching the build system over to meson. Would
someone be able to work on updating the lxc package with the new
release?

Thanks,
Mathias

[1] -- https://github.com/lxc/lxc/tags

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web