On 12/12/2018 18:08, Shengjing Zhu wrote: > On Thu, Dec 13, 2018 at 1:00 AM Emilio Pozuelo Monfort <po...@debian.org> > wrote: >> >> On 08/12/2018 15:39, Shengjing Zhu wrote: >>> Package: release.debian.org >>> Severity: normal >>> User: release.debian....@packages.debian.org >>> Usertags: binnmu >>> >>> nmu anbox_0.0~git20181014-1 . amd64 arm64 armhf . unstable . -m "Rebuild >>> against lxc3. (Closes: #915821)" >>> >> >> Why is this needed? Your package anbox depends on lxc and liblxc1 so no >> binNMU >> should be necessary. If anbox is unusable, there may be something else that >> is >> wrong. > > Launching a lxc container needs a configuration file, and the > configuration key is different for lxc2 and lxc3. > I think such breakage is not covered by liblxc so version. > > Anbox upstream determines the lxc version at build time, to choose > what configure key to use. > > https://github.com/anbox/anbox/blob/73b8b63/src/anbox/container/lxc_container.cpp#L50
Sounds like something that should be done at runtime. For now, a rebuild would fix users that have newer lxc, but it would be possible to have the old one with a rebuilt anbox if you don't force a minimum version. Thus you should probably do a maintainer upload bumping the build and runtime dep to ensure you get the newer configuration. Emilio
