From: Ben Hutchings <ben@decadent.org.uk>
To: Ian Rogers <irogers@google.com>,
debian-kernel@lists.debian.org, waldi@debian.org
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: Getting the latest and greatest Linux perf features on every Debian kernel
Date: Mon, 10 Jan 2022 00:54:31 +0100 [thread overview]
Message-ID: <f59da80e6b4d053246fec4ef263ae4ca7aa1277f.camel@decadent.org.uk> (raw)
In-Reply-To: <CAP-5=fUczsXmo4xk2Yi=H6zUhmpixFaz9An=ixKotx=z0GOp0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On Sun, 2021-11-21 at 18:18 -0800, Ian Rogers wrote:
> Hi,
>
> I'd love to package Linux perf as per Arnaldo's prepared tarball for
> Debian. If I could get help on the Debian side it would be great! The
> actions that are needed are:
>
> 1) package Arnaldo's tarball for Debian, presumably the build in the
> sources for linux-perf-5.10 will be a good starting point. The package
> will be linux-perf and replace the current metapackage of the same
> name.
I don't think this buys us anything over building from the kernel tree
(i.e. the linux source package), but will wait to see what Arnaldo
says.
> 2) create an updated linux-base that removes /usr/bin/perf
>
> 3) upload the updated linux-base and linux-perf packages for
> maintainer approval to https://mentors.debian.net/
linux-base is maintained by the kernel team on salsa.debian.org, where
you can send merge requests. If linux-perf is to be a separate source
package, I think it should be maintained in the same way.
> 4) some how get the previous Debian linux-perf-[45].* packages removed
[...]
They will be removed from the Debian archive through a periodic
cleanup.
Ben.
--
Ben Hutchings
I say we take off; nuke the site from orbit.
It's the only way to be sure.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-09 23:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 6:34 Getting the latest and greatest Linux perf features on every Debian kernel Ian Rogers
2021-11-12 14:39 ` Arnaldo Carvalho de Melo
2021-11-22 2:18 ` Ian Rogers
2021-11-22 12:54 ` Moessbauer, Felix
2021-11-22 16:57 ` Ian Rogers
2021-11-23 7:46 ` Moessbauer, Felix
2022-01-09 23:54 ` Ben Hutchings [this message]
2022-01-10 18:44 ` Arnaldo Carvalho de Melo
2022-12-23 1:43 ` Ian Rogers
2022-12-25 11:51 ` Andi Kleen
2022-12-26 16:12 ` Moessbauer, Felix
2022-12-26 19:15 ` Ben Hutchings
2023-01-10 1:32 ` Ian Rogers
2023-01-13 22:06 ` Ben Hutchings
2022-01-09 23:41 ` Ben Hutchings
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=f59da80e6b4d053246fec4ef263ae4ca7aa1277f.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=acme@kernel.org \
--cc=debian-kernel@lists.debian.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=waldi@debian.org \
/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).