Bug#768073: LXC team take over ITP?

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] LXD packaging

Clément Hermann-2
On 17/12/2017 21:39, Clément Hermann wrote:

> On 04/12/2017 21:40, Clément Hermann wrote:
>> So, I did some work on golang-gopkg-flosch-pongo2
>> <https://anonscm.debian.org/cgit/pkg-go/packages/golang-gopkg-flosch-pongo2.git/>
>> (#839748), since I had no answer.
>> It should be fit for release but I would need someone (from the pkg-go
>> team) to review and upload.
>>
>
> It's been completely reworked, hopefully it can be reviewed and uploaded
> soon.

It's in NEW right now.

>> I also started working on golang-gopkg-lxc-go-lxc.v2-dev (ITP: #883488).
>>
>> That's the last dependancy for LXD.
>>
>
> And it's waiting for review and upload as well, in the pkg-go repository.
>

I'm almost done, hopefully will have something ready for review this
weekend :)


>> So I started looking packaging LXD stable-2.0 as well, and asked to join
>> the pkg-lxc team (pending approval).
>
> Unfortunately I had no response so far... Ping ? My Alioth username is
> nodens-guest.
>

(Friendly) ping ?


Cheers,

\

Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] Bug#768073: LXD packaging

Evgeni Golov-2
Hi,

On Wed, Dec 20, 2017 at 05:59:42PM +0100, Clément Hermann wrote:

> On 17/12/2017 21:39, Clément Hermann wrote:
>
> > On 04/12/2017 21:40, Clément Hermann wrote:
> >> So, I did some work on golang-gopkg-flosch-pongo2
> >> <https://anonscm.debian.org/cgit/pkg-go/packages/golang-gopkg-flosch-pongo2.git/>
> >> (#839748), since I had no answer.
> >> It should be fit for release but I would need someone (from the pkg-go
> >> team) to review and upload.
> >>
> >
> > It's been completely reworked, hopefully it can be reviewed and uploaded
> > soon.
>
> It's in NEW right now.

Cool!

>
> >> I also started working on golang-gopkg-lxc-go-lxc.v2-dev (ITP: #883488).
> >>
> >> That's the last dependancy for LXD.
> >>
> >
> > And it's waiting for review and upload as well, in the pkg-go repository.
> >
>
> I'm almost done, hopefully will have something ready for review this
> weekend :)

Awesome! I tried doing this in [1], but the test suite didn't like me :(

> >> So I started looking packaging LXD stable-2.0 as well, and asked to join
> >> the pkg-lxc team (pending approval).
> >
> > Unfortunately I had no response so far... Ping ? My Alioth username is
> > nodens-guest.
> >
>
> (Friendly) ping ?

Sorry, busy with life atm, but now Alioth just said "Member Added
Successfully" :))

Welcome!

Evgeni

[1] https://anonscm.debian.org/cgit/pkg-lxc/golang-gopkg-lxc-go-lxc.v2.git/

Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] Bug#768073: Bug#768073: LXD packaging

Clément Hermann-2
On 21/12/2017 10:31, Evgeni Golov wrote:

>>>> I also started working on golang-gopkg-lxc-go-lxc.v2-dev (ITP: #883488).
>>>>
>>>> That's the last dependancy for LXD.
>>>>
>>>
>>> And it's waiting for review and upload as well, in the pkg-go repository.
>>>
>>
>> I'm almost done, hopefully will have something ready for review this
>> weekend :)
>
> Awesome! I tried doing this in [1], but the test suite didn't like me :(

yes, it's basically impossible to run the tests in the build system: the
unprivileged ones need a working LXC setup with cgroups (I actually have
trouble with them with my user out of a chroot), and the privileged one
aren't skipped because fakeroot...

I discussed this a bit on #pkg-go and I decided to loose the tests for
the initial packaging, and plan to setup the tests in autopkgtest instead.

There is still some work to be done, I hope I'll find time to finish
this weekend.

>>>> So I started looking packaging LXD stable-2.0 as well, and asked to join
>>>> the pkg-lxc team (pending approval).
>>>
>>> Unfortunately I had no response so far... Ping ? My Alioth username is
>>> nodens-guest.
>>>
>>
>> (Friendly) ping ?
>
> Sorry, busy with life atm, but now Alioth just said "Member Added
> Successfully" :))
>
> Welcome!

Thanks :)


--
nodens

Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] Bug#768073: LXD packaging (and lxc-go plus a little bit of salsa)

Clément Hermann-2
In reply to this post by Evgeni Golov-2
Hi,


I've resumed active work on LXD, the last dependency
(golang-gopkg-lxc-go-lxc.v2 - #883488) is almost done (pending review
and upload).

Regarding lxc-go, I suggest we archive the previous attemps, since it
will live in pkg-go repository (using gitlab Archive feature on Salsa).
Same for the lxd ubuntu package that has been imported: I think it will
be much easier to create a new package from scratch using
dh-make-golang. Of course, I intent to cherry-pick bits of Ubuntu
packaging where it makes sense.

Speaking of Salsa, can someone grant me access to lxc-team ?

on LXD packaging per se, the only difference with other go packages will
probably be that pkg-go team switched to a workflow without pristine-tar
(see https://pkg-go.alioth.debian.org/workflow-changes.html if you're
interested). And, of course, that the repo is in lxc-team namespace.


Is there anything regarding lxc-team packaging style/workflow I should
be aware of? From what I saw, the workflow seems to be using gbp with
pristine star branch, UNRELEASED target distribution until the package
is ready to upload, so very similar to what I'm used to in pkg-perl.
Please correct me if I'm wrong! :)


Cheers.

--
nodens

Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] Bug#768073: LXD packaging (and lxc-go plus a little bit of salsa)

Clément Hermann-2
On 03/02/2018 16:52, Clément Hermann wrote:
> Hi,
> Is there anything regarding lxc-team packaging style/workflow I should
> be aware of? From what I saw, the workflow seems to be using gbp with
> pristine star branch, UNRELEASED target distribution until the package
> is ready to upload, so very similar to what I'm used to in pkg-perl.
> Please correct me if I'm wrong! :)

Except pristine star-> pristine-tar, obviously, I had a brain
autocorrect bug. ;)


Cheers,

--
nodens

Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] Bug#768073: LXD packaging (and lxc-go plus a little bit of salsa)

Jonathan Dowland
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)

What's the status of the LXD package itself? 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




Thanks & best wishes

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄⠀⠀⠀⠀

Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] Bug#768073: LXD packaging (and lxc-go plus a little bit of salsa)

Clément Hermann-2
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

Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] Bug#768073: LXD packaging (and lxc-go plus a little bit of salsa)

Clément Hermann-2
On Tue, 10 Jul 2018 13:51:35 +0200 =?UTF-8?Q?Cl=c3=a9ment_Hermann?=
<[hidden email]> wrote:

> 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):

People interested, please check the up-to-date list in the Gobby doc at
gobby.debian.org/Teams/Go/lxd-dep-packaging
(or the export at
https://gobby.debian.org/export/Teams/Go/lxd-dep-packaging). It contains
comments, #ITPs, etc.

To avoid packaging useless deps, we'll probably wait until 3.0.2 for a
proper LXD package (see comments in #905068).

Thanks to people already helping, with packaging or sponsoring!

Cheers,

--
nodens

Reply | Threaded
Open this post in threaded view
|

Bug#768073: [pkg-lxc-devel] Bug#768073: LXD packaging (and lxc-go plus a little bit of salsa)

Jonathan Dowland
Clément Hermann wrote:
> 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):

I updated https://wiki.debian.org/LXD with the list from your email, and
then

>People interested, please check the up-to-date list in the Gobby doc at
>gobby.debian.org/Teams/Go/lxd-dep-packaging (or the export at
>https://gobby.debian.org/export/Teams/Go/lxd-dep-packaging). It
>contains comments, #ITPs, etc.

I'd never heard of Gobby before. I've linked to it from the wiki page,
but it doesn't seem to make sense to try and track this in two places.
It's kind-of unfortunate to have introduced yet-another-collaborative
editor. I'd delete the list from the wiki page and point at the Gobby
doc except I don't know how accessible that is yet, and I don't know
if the list there is current to now, either.

https://salsa.debian.org/lxc-team/lxd doesn't exist still but I guess
it wouldn't until the dependencies were done.


--

Jonathan Dowland

12