From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] 2017.02.x: update hash file for libnl 3.2.27 patch
Date: Fri, 30 Jun 2017 19:07:47 +0200 [thread overview]
Message-ID: <fa1ecb7a-c3e6-16e7-86b5-76128c996814@mind.be> (raw)
In-Reply-To: <1498841436-24941-1-git-send-email-julien.boibessot@free.fr>
On 30-06-17 18:50, julien.boibessot at free.fr wrote:
> From: Julien BOIBESSOT <julien.boibessot@armadeus.com>
>
> Corresponding patch is generated on the fly by github. It seems like
> generation method has changed, resulting to slightly different patch,
> so update BR hash file accordingly.
So this is problematic. While the tarballs generated by git(hub) are
reproducible, the patch files are not. Makes sense, since it has abbreviated
sha1s for the tree objects embedded in them and these will need to become longer
over time.
I see no better solution than to disable hashes for bit-downloaded patches
entirely...
Regards,
Arnout
>
> Signed-off-by: Julien BOIBESSOT <julien.boibessot@armadeus.com>
> ---
> package/libnl/libnl.hash | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/package/libnl/libnl.hash b/package/libnl/libnl.hash
> index eafba4a..9b6b512 100644
> --- a/package/libnl/libnl.hash
> +++ b/package/libnl/libnl.hash
> @@ -1,3 +1,4 @@
> # From https://github.com/thom311/libnl/releases/download/libnl3_2_27/libnl-3.2.27.tar.gz.sha256sum
> sha256 4bbbf92b3c78a90f423cf96260bf419a28b75db8cced47051217a56795f58ec6 libnl-3.2.27.tar.gz
> -sha256 b7bb929194eefc56c786a7e1ae5176b54713f9013ccec63760f232742ae80361 3e18948f17148e6a3c4255bdeaaf01ef6081ceeb.patch
> +# Locally computed
> +sha256 a308873157080f1e2e6693b2a151e15d8dfe77884b073ba3dc9bd42772dd1aef 3e18948f17148e6a3c4255bdeaaf01ef6081ceeb.patch
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-06-30 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 16:50 [Buildroot] [PATCH] 2017.02.x: update hash file for libnl 3.2.27 patch julien.boibessot at free.fr
2017-06-30 17:07 ` Arnout Vandecappelle [this message]
2017-07-02 21:55 ` Thomas Petazzoni
2017-07-02 22:32 ` Peter Korsgaard
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=fa1ecb7a-c3e6-16e7-86b5-76128c996814@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.