All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python: bump to 2.7.10
Date: Thu, 18 Jun 2015 00:04:58 +0200	[thread overview]
Message-ID: <5581EF0A.8030601@mind.be> (raw)
In-Reply-To: <1434490571-16422-1-git-send-email-thomas.petazzoni@free-electrons.com>

On 06/16/15 23:36, Thomas Petazzoni wrote:
> diff --git a/package/python/python.hash b/package/python/python.hash
> index f741e85..6258ec2 100644
> --- a/package/python/python.hash
> +++ b/package/python/python.hash
> @@ -1,2 +1,4 @@
> -# Locally calculated after checking pgp signature
> -sha256	90d27e14ea7e03570026850e2e50ba71ad20b7eb31035aada1cf3def8f8d4916	Python-2.7.9.tar.xz
> +# From https://www.python.org/downloads/release/python-2710/
> +md5	c685ef0b8e9f27b5e3db5db12b268ac6	Python-2.7.10.tar.xz
> +# Locally calculated
> +sha256	1cd3730781b91caf0fa1c4d472dc29274186480161a150294c42ce9b5c5effc0	Python-2.7.9.tar.xz
                                                                                                   ^^
                                                                                                   10

 With that fixed:
 Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

 It's a pity that it's not possible to check against such mistakes in the 
check-hash script.


 Regards,
 Arnout

-- 
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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-06-17 22:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 21:36 [Buildroot] [PATCH] python: bump to 2.7.10 Thomas Petazzoni
2015-06-17 22:04 ` Arnout Vandecappelle [this message]
2015-06-22 22:12   ` Yann E. MORIN
2015-06-22 21:14 ` 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=5581EF0A.8030601@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.