netdev - Re: libbpf distro packaging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AAB8D5C3-807A-4EE3-B57C-C7D53F7E057D@fb.com>
Date:   Fri, 11 Oct 2019 21:14:19 +0000
From:   Julia Kartseva <hex@...com>
To:     Jiri Olsa <jolsa@...hat.com>
CC:     Alexei Starovoitov <ast@...com>,
        Andrii Nakryiko <andrii.nakryiko@...il.com>,
        "labbott@...hat.com" <labbott@...hat.com>,
        "acme@...nel.org" <acme@...nel.org>,
        "debian-kernel@...ts.debian.org" <debian-kernel@...ts.debian.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Andrey Ignatov <rdna@...com>, Yonghong Song <yhs@...com>,
        "jolsa@...nel.org" <jolsa@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        "md@...ux.it" <md@...ux.it>
Subject: Re: libbpf distro packaging

Hi Jiri,

systemd folks published libbpf CentOS 7 package in systemd corp repo: [1],
so guess that proves that deps from other repo are fine.

Rebuild is fairly simple: [2]

[1] https://copr.fedorainfracloud.org/coprs/mrc0mmand/systemd-centos-ci/build/1053694/
[2] https://github.com/systemd/systemd/pull/13744#issuecomment-541168076

On 10/8/19, 12:40 AM, "Jiri Olsa" <jolsa@...hat.com> wrote:
>
> On Mon, Oct 07, 2019 at 12:25:51AM +0000, Julia Kartseva wrote:
> > 
> > I wonder what are the steps to make libbpf available for CentOS {7|8} as well?
> > One (likely the quickest) way to do that is to publish it to Fedora's EPEL [1].
> > 
> > I have a little concern about dependencies, namely elfutils-libelf-devel and 
> > elfutils-devel are sourced directly by CentOS repos, e.g. [2], not sure if 
> > dependencies from another repo are fine.
> > 
> > Thoughts? Thanks!
>
> I think that should be ok, I'll ask around and let you know
>
> jirka