Thanks, Free and Stéphane. Based on your comments, I think the best path forward will be to keep LXD packaging as-is for the trixie release, although its version will be stuck at the 5.0 LTS snapshot unless someone else steps in to further update it. I don't want to try to do any potentially tricky transition from LXD -> Incus right at system upgrade time that depends on interacting with a running daemon. But we can add a NEWS entry or similar to LXD's packaging informing people they should migrate to Incus prior to trixie+1 (forky) when LXD would be removed from Debian.
Mathias On Wed, 2023-12-13 at 21:14 -0500, Stéphane Graber wrote: > Currently lxd-to-incus looks for the existing running LXD daemon to > validate the user configuration ahead of migrating the data to Incus, > that's why we need the LXD Go package for it, we actively interact with the > LXD API before shutting it down for the migration. > > So if you want to get rid of LXD in Trixie, you're going to want to run the > migration tool from preinst which doesn't seem ideal. Or at least put in a > debconf prompt to force the user to go and run the migration logic before > being allowed to continue with their system upgrade. > > An alternative is to turn the lxd and lxd-client packages into orphans, so > they can still be on the system and running when the user installs Incus > and runs the migration tool. Downside of this approach is that the user may > not be aware of this situation and as those binaries wouldn't be in the > archive anymore, there's no way for them to pull incus onto the system. > > Stéphane > > On Wed, Dec 13, 2023, 6:07 p.m. Free Ekanayaka <fr...@debian.org> wrote: > > > Hello Mathias, > > > > thanks for the thoughtful write-up. > > > > I'm pretty much on board with everything you said. > > > > The only detail I'm not totally sure about is whether it would actually > > be beneficial to have trixie ship LXD 5.0 (at commit ^1364ae4). It's > > true that it'd be an out-of-date LXD, but it might be handy for folks > > upgrading from bookworm and not wanting to contextually migrate to > > Incus, but rather leave that as a separate step later down the road. > > > > It's kind of a minor point, and something that I believe won't be such a > > big deal in practice. So I'd be also perfectly fine not shipping the LXD > > binary at all in trixie. > > > > Free
signature.asc
Description: This is a digitally signed message part
