Hi Helmut, On Thu, 27 Apr 2023 15:00:05 +0200 Helmut Grohne <hel...@subdivi.de> wrote: > Attempting to unpack lxd-client/5.0.2-3+b2 from Debian bookworm > on a minimal Debian bullseye with lxc/1:4.0.6-2+deb11u1 > installed, causes an unpack error from dpkg due to > /usr/share/bash-completion/completions/lxc being contained in both packages.
It looks like you're trying to install the version of lxd from testing on a bullseye system? Mixing packages from different releases isn't supported [1]. Furthermore, there hasn't yet been a stable release of Debian that shipped lxd, so there's no way lxd-client might be upgraded before lxc when upgrading from bullseye to bookworm. As such, I don't know if it's really worthwhile to try to address this situation that would only occur when the end-user has already broken key assumptions about how their system is configured. The packaging of lxc was updated during the bookworm development cycle to properly name its bash completion file and de-conflict with lxd packaging [2]. Upgrading lxc packages from bullseye -> bookworm should work smoothly; after the upgrade is complete users will then also be able to `apt install lxd` if they so wish, and they won't encounter the packaging conflict. > Please ensure that lxd-client has sufficient Breaks and Replaces declarations. Does that address your concern? Mathias [1] -- https://wiki.debian.org/DontBreakDebian [2] -- https://bugs.debian.org/1010843
signature.asc
Description: This is a digitally signed message part
