On Sat, Dec 25, 2021 at 02:25:06PM +0000, Evgeni Golov wrote: > > > On December 25, 2021 12:35:45 PM UTC, Antonio Terceiro <terce...@debian.org> > wrote: > >On Fri, Dec 24, 2021 at 06:04:04AM +0000, Mathias Gibbens wrote: > >> Source: lxc > >> Version: 1:4.0.10-1 > >> Severity: normal > >> > >> Work on packaging LXD for Debian (ITP #768073) is getting pretty > >> close to completion. I've recently started testing the LXD package that > >> I am able to build locally, making sure everything is working properly > >> before it's uploaded to NEW once the few remaining dependencies make it > >> through NEW themselves. > >> > >> LXD depends on the liblxc1 package, but not on the lxc package > >> itself. However, there are a few files currently shipped in the lxc > >> package that LXD needs to properly start. Specifically, the apparmor > >> profiles (all of /etc/apparmor.d/, except /etc/apparmor.d/usr.bin.lxc- > >> start) and the /usr/lib/<arch>-linux-gnu/lxc/rootfs/ directory. > >> > >> I'm hoping we can figure out a nice way to make these dependencies of > >> LXD available without having to pull in lxc itself (plus its own > >> dependencies). The easiest way might be to just move them to liblxc1, > >> which both lxc and LXD packages will depend on. Or, there might be some > >> other solution that could work. > > > >They probably would need to be provided by a (NEW) lxc-common package. > >If we ever need to transition to liblxc2, we don't want both liblxc* > >packages providing those files. > > On Ubuntu, this package us called liblxc-common, which we probably > should also use, to make life of other consumers easier?
Sure! I didn't check there first.
signature.asc
Description: PGP signature
