Bug#896165: linux: request packaging of bpftool
On Fri, Dec 14, 2018 at 11:16:10AM +0100, Simon Horman wrote:
> On Wed, Nov 28, 2018 at 07:49:50PM -0800, Noah Meyerhans wrote:
> > On Tue, Nov 27, 2018 at 09:50:17AM -0800, Jakub Kicinski wrote:
> > > > > Please see https://salsa.debian.org/kernel-team/linux/merge_requests/72
> > > >
> > > > Ugh. We cannot currently package bpftool in Debian. There are several
> > > > GPLv2-only files in its source tree, and it links unconditionally
> > > > against the GPLv3 libbfd. :(
> > >
> > > If we relicense the GPLv2-only files to be GPLv2-only OR BSD-2-Clause
> > > - like the majority of bpftool sources - would that work?
> > >
> > > I wanted to make sure GPLv2-only + BSD-2-Clause will satisfy the
> > > license requirement when linking against libbfd, before I start chasing
> > > people for acks on the relicense :)
> >
> > Yes, the BSD 2-clause license is OK. GPLv2 or greater would be OK, too.
> > It's really just GPLv2-only in this case that's causing the problem.
>
> Hi,
>
> the following merge-commit, which has been accepted into bpf-next
> for inclusion in v4.21, addresses the problem raised above by
> clarifying that the licence of bpftool is GPLv2-only + BSD-2-Clause.
>
> commit 00842be52f2015c3c1028e16b565f325f4ca20fc
> Merge: 8f9a8a619311 907b22365115
> Author: Daniel Borkmann <daniel@iogearbox.net>
> Date: Thu Dec 13 12:08:45 2018 +0100
>
> Merge branch 'bpf-bpftool-license-update'
>
> Jakub Kicinski says:
>
> ====================
> We are changing/clarifying the license on bpftool to GPLv2-only +
> BSD-2-Clause for all files. Current license mix is incompatible
> with libbfd (which is GPLv3-only) and therefore Debian maintainers
> are apprehensive about packaging bpftool.
>
> Acks include authors of code which has been copied into bpftool (e.g.
> JSON writer from iproute2, code from tools/bpf, code from BPF samples
> and selftests, etc.)
>
> Thanks again to all the authors who acked the change!
> ====================
>
> Acked-by: Roman Gushchin <guro@fb.com>
> Acked-by: YueHaibing <yuehaibing@huawei.com>
> Acked-by: Yonghong Song <yhs@fb.com>
> Acked-by: Stanislav Fomichev <sdf@google.com>
> Acked-by: Sean Young <sean@mess.org>
> Acked-by: Jiri Benc <jbenc@redhat.com>
> Acked-by: David Calavera <david.calavera@gmail.com>
> Acked-by: Andrey Ignatov <rdna@fb.com>
> Acked-by: Joe Stringer <joe@wand.net.nz>
> Acked-by: David Ahern <dsahern@gmail.com>
> Acked-by: Alexei Starovoitov <alexei.starovoitov@gmail.com>
> Acked-by: Petar Penkov <ppenkov@stanford.edu>
> Acked-by: Sandipan Das <sandipan@linux.ibm.com>
> Acked-by: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: John Fastabend <john.fastabend@gmail.com>
> Acked-by: Taeung Song <treeze.taeung@gmail.com>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
> Acked-by: Daniel Borkmann <daniel@iogearbox.net>
> CC: okash.khawaja@gmail.com
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Hi Noah,
I believe that the above commit resolves the licence problem that was
raised earlier. Is it possible to find a way to move forwards on packaging
bpftool?
Reply to: