[pkg-go] RFS: golang-bugsnag-go
Potter, Tim (Cloud Services)
timothy.potter at hpe.com
Wed Sep 9 03:21:02 UTC 2015
On 9 Sep 2015, at 10:46 am, Dmitry Smirnov <onlyjob at debian.org> wrote:
> On Tuesday 08 September 2015 22:55:13 Potter, Tim wrote:
>> On 3 Sep 2015, at 11:56 pm, Tianon Gravi <tianon at debian.org> wrote:
>>> On 26 May 2015 at 18:53, Potter, Tim (Cloud Services)
>>> <timothy.potter at hp.com> wrote:
>>>> I had a chat to tianon on the weekend and he suggested that libcontainer
>>>> did not need to be split out from golang-docker-dev
> Actually I think it might be a good idea to ship standalone "libcontainer" as
> part of it successor "runc" (which is already in NEW)…
Well, if that turns out to be the case then most or all of the dependencies should
be already packaged for this. From memory I managed to build libcontainer
but several big unpackaged pieces were required, notably bugsnag and revel. I
think we’re well on our way to getting that done though.
>>> Heh, I'm working on packaging "notary" now (as a dep for Docker 1.8+)
>>> and it depends on bugsnag. Any chance you'd be interested in renaming
>>> the source/binary packages there and updating the packaging? :)
>> Sure thing! I think Dmitry has done this for most of the other packages I
>> did as part of this work (thanks Dmitry!) but according to my DDPO page
>> there is still bugsnag and a couple of dependencies to go.
> I've just uploaded "bugsnag-panicwrap" and "bugsnag-go" will follow once
> "panicwrap" is accepted. I specifically updated names of all binary packages
> for policy compliance.
Great! I’ve done some more work and renamed the following packages that
are also required for bugsnag:
I’ll send out separate RFS’s for them.
Also required is an update to golang-gocheck, which I’ve filed a bug for ages
ago and pushed the required update to alioth already:
More information about the Pkg-go-maintainers