Hi ! On 10/07/2018 12:40, Jonathan Dowland wrote: > Hey folks,
> I was pleased to see the last LXD dependency that we were tracking has > finally made it into Debian, so the path is likely clear for LXD itself > now (unless we need to catch up on some newer dependencies since the > analysis was done: https://wiki.debian.org/LXD) Actually, yes, it's a bit outdated. I'm currently working on the dependancies needed for 3.0.1, see this edited output of dh-make-golang estimate (some entries were false positive, due to different import path that'll need to be patched, or an apparently useless for in the case of go4): github.com/lxc/lxd github.com/juju/persistent-cookiejar github.com/frankban/quicktest github.com/CanonicalLtd/go-sqlite3 github.com/mpvl/subtest github.com/CanonicalLtd/go-grpc-sql github.com/CanonicalLtd/raft-http github.com/CanonicalLtd/raft-test github.com/CanonicalLtd/raft-membership github.com/CanonicalLtd/dqlite github.com/ryanfaerman/fsm github.com/nbio/st github.com/juju/gomaasapi github.com/juju/collections github.com/flosch/pongo2 gopkg.in/CanonicalLtd/candidclient.v1 gopkg.in/juju/names.v2 The original plan was to start with lxd 2.0, but upstream is slow to release a new 2.0 version, apparently they're too busy on 3.x and it's a bit in the backlog. Since there were some merge mistakes in the past that trigger new deps which are only fixed as patches in the Ubuntu package, it means quite a lot of hunting work. Also I injured both my hands meanwhile, which mean I couldn't spend much time on it... But that's better now ! So I started working on 3.0 deps - just yesterday, actually. I plan to work on this more during Debcamp, hopefully I'll find time to at least fill all the ITP until then and start working on some. Help welcome, of course, I plan to put all those under the Go-team umbrella. Feel free to fill ITPs and start working on any of them, just make sure you're following the Go team new workflow for consistency with other LXD deps [1]. > What's the status of the LXD package itself? Barely started. I have started to sort out build/test/runtime deps and the like - it's not possible to simply get the ones from Ubuntu package which work differently (bundling everything in a single source, vendoring go-lxc, etc, which is not acceptable in Debian). Of course it still makes sense to reproduce some stuff from the Ubuntu packaging, but it's not a straightforward "port". > In the middle of this whole > process Alioth went away and was replaced by Salsa. I found the > following Salsa project but no packaging sources: > > https://salsa.debian.org/lxc-team/lxd This project has been created empty during the migration. Putting lxc-team in CC, as I can't initialize this repo myself (I only have "developper" access, and I'd need to be master or owner. Antonio, you're owner, could you please give the lxc-team group master access ? Cheers, [1] https://go-team.pages.debian.net/workflow-changes.html -- nodens
