From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libseccomp: bump version to 2.2.0
Date: Mon, 30 Mar 2015 23:29:26 +0200 [thread overview]
Message-ID: <20150330232926.2904e95b@free-electrons.com> (raw)
In-Reply-To: <1427638949-3191-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sun, 29 Mar 2015 16:22:28 +0200, Bernd Kuhls wrote:
> diff --git a/package/libseccomp/0001-remove-static.patch b/package/libseccomp/0001-remove-static.patch
Do you think you could try to submit this upstream? If not, maybe we
should just make the package depends on !BR2_STATIC_LIBS.
> diff --git a/package/libseccomp/libseccomp.hash b/package/libseccomp/libseccomp.hash
> index f87633e..6bca5c2 100644
> --- a/package/libseccomp/libseccomp.hash
> +++ b/package/libseccomp/libseccomp.hash
> @@ -1,2 +1,2 @@
> -# Locally computed:
> -sha256 8812c11e407c383f5ad6afb84a88e5a0224477bcfe8ff03f0c548e5abaac841c libseccomp-2.1.1.tar.gz
> +# From https://github.com/seccomp/libseccomp/releases/tag/v2.2.0
> +sha1 5aa8a230f8529d6ee777098550245e43d2247395fdfd5a2176e28cf7236f1b10 libseccomp-2.2.0.tar.gz
Since you're switching to github, I've removed the hash file, because
github does not guarantee to offer identical tarballs for a given
release.
Committed with the hash file removed (for the static issue, I've kept
your patch).
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-30 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 14:22 [Buildroot] [PATCH 1/2] package/libseccomp: bump version to 2.2.0 Bernd Kuhls
2015-03-29 14:22 ` [Buildroot] [PATCH 2/2] package/tor: new package Bernd Kuhls
2015-04-20 2:46 ` Fabio Porcedda
2015-04-20 17:45 ` Bernd Kuhls
2015-03-30 21:29 ` Thomas Petazzoni [this message]
2015-03-31 11:53 ` [Buildroot] [PATCH 1/2] package/libseccomp: bump version to 2.2.0 Thomas Petazzoni
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=20150330232926.2904e95b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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