[pkg-lxc-devel] Bug#768073: LXC team take over ITP?

[Adnan Hodzic]

Hey Jonathan (and everybody else),

Sorry about delayed reply.

> Adnan, how's it going?

Awhile back I started packaging process. I basically re-packaged the LXD
Ubuntu package. As Evgeni mentioned it "is what we did with the other LXC
components and that worked out pretty well so far."

However, with LXD, build would fail due to all the "golang-* dependencies
which are missing from Debian. I also planned on re-packaging these as
well, but I got sidetracked by things from "real life".

>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?

I think Evgeni, gave a perfect answer for this one:

>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.

...

>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?

Basically if we resolved the issue with missing golang-* dependencies, we
could probably have it uploaded within same day.

@Anthony and @Evgeni,

>> 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.

Yep, this is our only and main obstacle.

>> 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.

I love this suggestion. If we could make this cooridnation happen, and both
teams do their part of the job that would be the perfect fusion.

I admit and acknowledge your frustration about this ITP being here for this
long. I think I explained why I stopped where I stopped, but I also admit
that I could've been more update to date with my communication.

If anyone wants to "hijack" this ITP from me, be my guest. Regardless, I
would still like to do the work that I claimed the responsibility for, and
get LXD into Debian.

At this point, I think we just need to align the efforts between pkg-go and
pkg-lxc teams, and we'll see LXD in Debian in no time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-lxc-devel/attachments/20160926/0a1d214a/attachment.html>