netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Julia Kartseva <hex@fb.com>, Alexei Starovoitov <ast@fb.com>,
	"labbott@redhat.com" <labbott@redhat.com>,
	"acme@kernel.org" <acme@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Andrey Ignatov <rdna@fb.com>, Yonghong Song <yhs@fb.com>,
	"jolsa@kernel.org" <jolsa@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"md@linux.it" <md@linux.it>,
	"debian-kernel@lists.debian.org" <debian-kernel@lists.debian.org>
Subject: Re: libbpf distro packaging
Date: Thu, 3 Oct 2019 09:24:21 -0700	[thread overview]
Message-ID: <CAEf4BzamREOTYvspbg5yp1igg8pY_0MQu93Y34w1t_WT9VJXNg@mail.gmail.com> (raw)
In-Reply-To: <20191003111029.GC23291@krava>

On Thu, Oct 3, 2019 at 4:10 AM Jiri Olsa <jolsa@redhat.com> 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.

>
> 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" <hex@fb.com> wrote:
> >
> > > Thank you Jiri, that's great news.
> > >
> > > > On 9/30/19, 4:13 AM, "Jiri Olsa" <jolsa@redhat.com> 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
> >
> >
> >

  reply	other threads:[~2019-10-03 17:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 19:04 libbpf distro packaging Julia Kartseva
2019-08-13 12:24 ` Jiri Olsa
2019-08-13 14:11   ` Daniel Borkmann
2019-08-13 18:26     ` Andrii Nakryiko
2019-08-13 18:23   ` Andrii Nakryiko
     [not found]     ` <FA139BA4-59E5-43C7-8E72-C7B2FC1C449E@fb.com>
2019-08-20 22:27       ` Julia Kartseva
2019-08-21 21:09         ` Jiri Olsa
2019-08-23  9:22           ` Jiri Olsa
2019-08-23 16:00             ` Alexei Starovoitov
2019-08-26  6:42               ` Jiri Olsa
2019-08-27 22:30                 ` Julia Kartseva
2019-08-28  7:12                   ` Jiri Olsa
2019-09-30 11:13                     ` Jiri Olsa
2019-09-30 18:18                       ` Julia Kartseva
2019-10-03  0:50                         ` Julia Kartseva
2019-10-03 11:10                           ` Jiri Olsa
2019-10-03 16:24                             ` Andrii Nakryiko [this message]
2019-10-03 17:29                               ` Jiri Olsa
2019-10-07  0:25                       ` Julia Kartseva
2019-10-08  7:39                         ` Jiri Olsa
2019-10-11 21:14                           ` Julia Kartseva
2019-10-16 10:01                             ` Jiri Olsa
2019-12-19 21:37                               ` Julia Kartseva
2019-12-20 13:58                                 ` Jiri Olsa
2020-03-05  0:22                                   ` Julia Kartseva
2020-03-05 14:18                                     ` Jiri Olsa
2020-03-10 14:57                                       ` Jiri Olsa
2020-03-10 17:18                                         ` Julia Kartseva
2020-03-10 17:49                                           ` Jiri Olsa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEf4BzamREOTYvspbg5yp1igg8pY_0MQu93Y34w1t_WT9VJXNg@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=acme@kernel.org \
    --cc=ast@fb.com \
    --cc=daniel@iogearbox.net \
    --cc=debian-kernel@lists.debian.org \
    --cc=hex@fb.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=labbott@redhat.com \
    --cc=md@linux.it \
    --cc=netdev@vger.kernel.org \
    --cc=rdna@fb.com \
    --cc=yhs@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).