Seven and a half years after the ITP was filed and with the combined work of many individuals, it's finally done -- all the dependencies required to build LXD are now in unstable. I'm waiting for one bug [1] to be resolved before asking for sponsorship, but I would like to solicit review of the package lxd, which can be viewed on salsa at [2].
I have put the resulting binary packages through their paces as best
as I can locally, testing various configurations (systemd vs SysV init
on the host and in containers), creation of containers and virtual
machines, different guest Linux distributions, etc. However, given the
complexity of LXD, I'd appreciate focused inspection and feedback prior
to the initial upload to NEW. Specifically:
* Handling of the systemd and SysV init scripts (originally sourced
from old LXD 3.x Ubuntu .debs)
* The {pre,post}{inst,rm} scripts (again, originally from old Ubuntu
.debs)
* The approach in d/rules to statically compile the lxd-agent binary
* Anything else that might jump out as potentially problematic or
error-prone down the road
Thanks!
Mathias
[1] -- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010843
[2] -- https://salsa.debian.org/go-team/packages/lxd
signature.asc
Description: This is a digitally signed message part
