From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/trace-cmd: bump to version 2.9.1
Date: Sat, 29 Aug 2020 16:30:48 +0200 [thread overview]
Message-ID: <20200829163048.38790541@windsurf.home> (raw)
In-Reply-To: <20200829134529.17445-1-egorenar-dev@posteo.net>
Hello,
On Sat, 29 Aug 2020 15:45:29 +0200
Alexander Egorenkov <egorenar-dev@posteo.net> wrote:
> - This also fixes gcc 10 issues
Do we have autobuilder reports of those build issues ?
> diff --git a/package/trace-cmd/0001-Cross-compilation-fixes.patch b/package/trace-cmd/0001-Cross-compilation-fixes.patch
> new file mode 100644
> index 0000000000..07428204fe
> --- /dev/null
> +++ b/package/trace-cmd/0001-Cross-compilation-fixes.patch
All patches need a description + Signed-off-by, and should be generated
with "git format-patch -N" when the upstream project uses git, which I
guess is the case here.
> diff --git a/package/trace-cmd/trace-cmd.hash b/package/trace-cmd/trace-cmd.hash
> index c6447f34d4..91c0512d5f 100644
> --- a/package/trace-cmd/trace-cmd.hash
> +++ b/package/trace-cmd/trace-cmd.hash
> @@ -1,4 +1,4 @@
> # Locally computed
> -sha256 3b3f564cc6ee30341051ccb7589b42f3abe4e676a21c029c7c127c7edf5bdcf0 trace-cmd-trace-cmd-v2.7.tar.gz
> -sha256 ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6 COPYING
> +sha256 f7d591ac13ac3de004aa69fa3c2d333f620bb29ad0fec064ec215f488588b333 trace-cmd-trace-cmd-v2.9.1.tar.gz
> +sha256 b1d04b850c1c7471b0f0896f6c6f0fcfc9f07e2dd183a5f5826af269fe9e88fb COPYING
The hash of COPYING has changed, what are the changes ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-08-29 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 13:45 [Buildroot] [PATCH 1/1] package/trace-cmd: bump to version 2.9.1 Alexander Egorenkov
2020-08-29 14:30 ` Thomas Petazzoni [this message]
[not found] ` <87blitqxva.fsf@posteo.net>
2020-08-29 17:03 ` Thomas Petazzoni
2020-08-30 12:06 ` Alexander Egorenkov
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=20200829163048.38790541@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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