Ohai, On Fri, Sep 23, 2016 at 11:25:15AM -0600, Anthony Fok wrote: > > I think that an ITP that has been inactive this long could be taken over by > > another interested party without it being a hijack, all things considered. > > (I think some QA script might move it to RFP soon anyway). > > > > Adnan, how's it going? > > > > There's a pkg-lxc team already. Since this package is/will be very > > inter-related to > > LXC, perhaps it should be developed in that team? Team CCed. Are they > > interested? > > Are you in pkg-lxc already?
Yes, Adnan is in pkg-lxc and technically the team is interested (given it falls into the same software stack) to have the whole stack available in Debian. But I must admit I personally have no use for it and not enough Go knowledge to package it properly. > > What's the state of the Ubuntu package? Could that make a good starting > > point? How > > much hacking before that would be suitable for an experimental upload at > > least? Yes, taking the Ubuntu package is a start is what we did with the other LXC components and that worked out pretty well so far. > I took a quick look at the package source obtained via: > > dget -u > http://archive.ubuntu.com/ubuntu/pool/main/l/lxd/lxd_2.2-0ubuntu1.dsc ... > So, I guess the first step would be to package > golang-gopkg-flosch-pongo2.v3, golang-gopkg-inconshreveable-log15.v2, > golang-gopkg-lxc-go-lxc.v2 and golang-petname, or simply grab these > existing Ubuntu packages, make a few minor changes to debian/control > and debian/changelog, file ITPs to the Debian BTS, and finally upload > them to Debian. > > I do not see too many hurdles after that, at least I hope not. ;-) IIRC that's similar to what Adnan told me the last time we talked about LXD. > Also, should the Debian lxd be team-maintained by the pkg-lxc team or > the pkg-go team? What do you think? Whatever works? :-) Stack-wise it's more pkg-lxc, language-wise pkg-go... I'd guess it will need coordination to both, LXC and other Go uploads at times too. Greets Evgeni
