Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-30 Thread Michael Stapelberg
Thanks! Filed #94 for the security issue. Will contact the wanna-build team directly. On Tue, Jan 30, 2018 at 8:45 PM, Emilio Pozuelo Monfort wrote: > On 30/01/18 08:54, Michael Stapelberg wrote: > > This would also be very helpful for fixing security issue #888777. > > You need to talk to t

Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-30 Thread Emilio Pozuelo Monfort
On 30/01/18 08:54, Michael Stapelberg wrote: > This would also be very helpful for fixing security issue #888777. You need to talk to the wanna-build team if you want to be able to schedule binNMUs for your language rebuilds, just like the ocaml and haskell teams do. For this particular case, fee

Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-29 Thread Michael Stapelberg
This would also be very helpful for fixing security issue #888777. On Sun, Jan 28, 2018 at 8:31 PM, Michael Stapelberg wrote: > Friendly ping? Still interested in getting this set up. > > On Mon, Jan 8, 2018 at 6:56 PM, Michael Stapelberg > wrote: > >> Thanks for the clarification. >> >> So, wh

Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-28 Thread Michael Stapelberg
Friendly ping? Still interested in getting this set up. On Mon, Jan 8, 2018 at 6:56 PM, Michael Stapelberg wrote: > Thanks for the clarification. > > So, what’s the next step in this process? Should I file a bug somewhere? > An RT ticket? An email? > > On Sun, Jan 7, 2018 at 11:26 AM, Julien Cri

Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-08 Thread Emilio Pozuelo Monfort
On 07/01/18 11:26, Julien Cristau wrote: > On Sat, Jan 6, 2018 at 19:19:13 +0100, Michael Stapelberg wrote: > >> On Sat, Jan 6, 2018 at 6:30 PM, Julien Cristau wrote: >> >>> also implications on visibility of unreleased security updates, so the >>> set of people with access needs to stay limited

Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-08 Thread Michael Stapelberg
Thanks for the clarification. So, what’s the next step in this process? Should I file a bug somewhere? An RT ticket? An email? On Sun, Jan 7, 2018 at 11:26 AM, Julien Cristau wrote: > On Sat, Jan 6, 2018 at 19:19:13 +0100, Michael Stapelberg wrote: > > > On Sat, Jan 6, 2018 at 6:30 PM, Julien

Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-07 Thread Julien Cristau
On Sat, Jan 6, 2018 at 19:19:13 +0100, Michael Stapelberg wrote: > On Sat, Jan 6, 2018 at 6:30 PM, Julien Cristau wrote: > > > also implications on visibility of unreleased security updates, so the > > set of people with access needs to stay limited. > > > Just to confirm: is this a side-effe

Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-06 Thread Michael Stapelberg
On Sat, Jan 6, 2018 at 6:30 PM, Julien Cristau wrote: > [moving this off the (now archived) bug] > Thanks for the pointer! > > On Sat, Jan 6, 2018 at 18:00:48 +0100, Michael Stapelberg wrote: > > > On Sat, Dec 2, 2017 at 8:20 PM, Julien Cristau > wrote: > > > > > On Sat, Jul 29, 2017 at 12:2

Re: Bug#870056: nmu: robustirc-bridge_1.7-1

2018-01-06 Thread Julien Cristau
[moving this off the (now archived) bug] On Sat, Jan 6, 2018 at 18:00:48 +0100, Michael Stapelberg wrote: > On Sat, Dec 2, 2017 at 8:20 PM, Julien Cristau wrote: > > > On Sat, Jul 29, 2017 at 12:25:03 +0200, Michael Stapelberg wrote: > > > > > This is the first binNMU I schedule, mostly to see

Bug#870056: nmu: robustirc-bridge_1.7-1

2017-07-29 Thread Michael Stapelberg
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu This is the first binNMU I schedule, mostly to see how this all works before I file a larger one. I realized that robustirc-bridge (and other Go binary packages) were built using the Go 1.7