Hi Free, On Fri, 2023-09-15 at 13:22 +0100, Free Ekanayaka wrote: > Hello! > > as you probably know, the initial fork from: > > https://github.com/cyphar/incus/ > > has now been moved under the LXC project: > > https://github.com/lxc/incus, > > and has definitely gained traction since the initial announcement, > getting support both from the community and from LXD developers that > have now moved to incus (myself included).
Yes, I've been keeping an eye on Incus' development and am glad to see it's off to a good start! > I wanted to wait for the first official incus release before reaching > out to Debian fellows, but since I noticed that you might be working > on updating the LXD package I thought it be good to get in contact. I was also planning to wait for the first official release before diving into packaging for Debian, as I know (at least at first) there was a ton of churn in dependencies and the naming of binaries. But it's never too early to start the conversation. :) As I've thought over things more, I think the ideal path forward would be to have both LXD and Incus available in Debian. That will give users the most freedom to choose what they want to install on their systems, and if down the road either of the projects winds down we can help them migrate to the other project as needed. > As Debian developer myself, incus maintainer and original author of > dqlite/libraft (which have now been forked too into the new "cowsql" > project https://github.com/cowsql, used by incus), I'd of course love > to see Debian switching to incus and cowsql, and in that case I'd > like to help out with packaging and maintainership. Of course! The more the merrier! LXD is currently team-maintained under the Go Team, although in practice I'm the only one performing uploads. I would envision a similar setup for the packaging of Incus, and would welcome your help with it. I haven't seen any RFP/ITPs for cowsql, go-cowsql, or the fork of raft; are you planning to work on getting those packaged for Debian? If not, eventually I'll get around to them. :) The only heartburn I have is with the fork of raft -- from a quick inspection, it looks like the package has the same name (both for the package and shared library) as Canonical's version of raft which is already packaged. Would it be too much work to change the name of the fork, so it would be trivial to have co-installed versions of raft? > Within the incus team we have discussed possible Debian-specific > migration strategies and we'd have ideas about how to handle it, so > users experience the least possible disruption. I'd certainly like to see that. Debian is tracking the LTS releases, and it would be a good release goal for trixie to have a migration path from LXC -> Incus for users if they wish. > I'd like to know what are your feelings around these topics, and of > course I understand if you prefer to just sit on the sidelines for > now. Speaking strictly for myself, I'm planning to switch to Incus once it hits a "1.0 LTS" sort of release. As such, I'll have a vested interest in getting it into Debian. I'll be glad to collaborate with you or anyone else who would like to work on the Debian packaging. And for the foreseeable future I'll also keep LXD up to date with its LTS releases for those who choose to stay with it. Mathias
signature.asc
Description: This is a digitally signed message part
