From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AF37BC32792 for ; Thu, 3 Oct 2019 17:29:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8E84920830 for ; Thu, 3 Oct 2019 17:29:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730762AbfJCR3r (ORCPT ); Thu, 3 Oct 2019 13:29:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38530 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730558AbfJCR3q (ORCPT ); Thu, 3 Oct 2019 13:29:46 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E5CE41DB8; Thu, 3 Oct 2019 17:29:45 +0000 (UTC) Received: from krava (ovpn-204-51.brq.redhat.com [10.40.204.51]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3A19A60BEC; Thu, 3 Oct 2019 17:29:39 +0000 (UTC) Date: Thu, 3 Oct 2019 19:29:38 +0200 From: Jiri Olsa To: Andrii Nakryiko Cc: Julia Kartseva , Alexei Starovoitov , "labbott@redhat.com" , "acme@kernel.org" , "netdev@vger.kernel.org" , Andrey Ignatov , Yonghong Song , "jolsa@kernel.org" , Daniel Borkmann , "md@linux.it" , "debian-kernel@lists.debian.org" Subject: Re: libbpf distro packaging Message-ID: <20191003172938.GA17036@krava> References: <20190823092253.GA20775@krava> <20190826064235.GA17554@krava> <20190828071237.GA31023@krava> <20190930111305.GE602@krava> <8B38D651-7F77-485F-A054-0519AF3A9243@fb.com> <20191003111029.GC23291@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.redhat.com [10.5.110.71]); Thu, 03 Oct 2019 17:29:46 +0000 (UTC) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Oct 03, 2019 at 09:24:21AM -0700, Andrii Nakryiko wrote: > On Thu, Oct 3, 2019 at 4:10 AM Jiri Olsa wrote: > > > > On Thu, Oct 03, 2019 at 12:50:08AM +0000, Julia Kartseva wrote: > > > Hi Jiri, > > > > > > v0.0.5 is out: [1] which brings questions regarding further maintenance > > > of rpm. > > > Who'll maintain the most recent version of rpm up-to-date? > > > > I will do that on fedora/rhel side now > > > > > Are you looking into making the procedure automated and do you need any > > > help from the side of libbpf devs if so? In particular, we can have the *.spec file > > > in GH mirror synchronized with the most recent tag so you can take it from the > > > mirror along with tarball. > > > > some notification of new tag/sync would be great > > Hey Jiri! You can watch Github repo for new releases, see > https://help.github.com/en/articles/watching-and-unwatching-releases-for-a-repository. cool, I was hoping there's something like this thanks, jirka > > > > > the spec file update is not a big deal because I need to do its > > changelog update anyway.. but I can put the fedora rpm spec in > > GH repo for reference, I will do a pull request for that > > > > jirka > > > > > Thanks! > > > > > > [1] https://github.com/libbpf/libbpf/releases/tag/v0.0.5 > > > > > > On 9/30/19, 11:18 AM, "Julia Kartseva" wrote: > > > > > > > Thank you Jiri, that's great news. > > > > > > > > > On 9/30/19, 4:13 AM, "Jiri Olsa" wrote: > > > > > > > > > > heya, > > > > > FYI we got it through.. there's libbpf-0.0.3 available on fedora 30/31/32 > > > > > I'll update to 0.0.5 version as soon as there's the v0.0.5 tag available > > > > > > > > >