Bug#698508: nmu

2014-07-10 Thread Bastian Blank
On Sun, Oct 06, 2013 at 04:16:20PM -0700, Kees Cook wrote: > I'm not very familiar with cdebootstrap; why does it need to be statically > linked? cdebootstrap is a tool to bootstrap Debian systems. Sometimes it is a chicken and egg problem to do this. Sometimes people even like to do this on non

Bug#698508: nmu

2013-10-06 Thread Kees Cook
On Mon, Oct 07, 2013 at 01:08:44AM +0200, Bastian Blank wrote: > On Sun, Oct 06, 2013 at 03:47:10PM -0700, Kees Cook wrote: > > I don't want to ship a static library for libseccomp unless there is a > > demonstrated requirement to do it. > > I'm thinking about using it in cdebootstrap, which needs

Bug#698508: nmu

2013-10-06 Thread Bastian Blank
On Sun, Oct 06, 2013 at 03:47:10PM -0700, Kees Cook wrote: > I don't want to ship a static library for libseccomp unless there is a > demonstrated requirement to do it. I'm thinking about using it in cdebootstrap, which needs to be statically linked. Okay, I can also do a source copy, it is small

Bug#698508: nmu

2013-10-06 Thread Kees Cook
On Sun, Oct 06, 2013 at 11:13:10PM +0200, Bastian Blank wrote: > I intend to NMU this. There is no reason for not shipping static > libraries, it is even built. Users are free to use them, while packages > should not. I don't want to ship a static library for libseccomp unless there is a demonstra

Bug#698508: nmu

2013-10-06 Thread Bastian Blank
I intend to NMU this. There is no reason for not shipping static libraries, it is even built. Users are free to use them, while packages should not. This package was never in testing, so no security support is available anyway. Bastian -- Every living thing wants to survive. --