Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python: bump to 2.7.10
Date: Tue, 23 Jun 2015 00:12:19 +0200	[thread overview]
Message-ID: <20150622221219.GD7547@free.fr> (raw)
In-Reply-To: <5581EF0A.8030601@mind.be>

Arnout, All,

On 2015-06-18 00:04 +0200, Arnout Vandecappelle spake thusly:
> 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
>  It's a pity that it's not possible to check against such mistakes in the 
> check-hash script.

Indeed, but I really can't see an obvious way to do it.

All I can think of is, if a .hash file contains a hash for a version we
do not have, then we should fail.

Hoever, that definitely very difficult to check, as for soem packages,
we have multiple versions, and even then, what if the archive name is
different? and all weird ocrner cases?

In the end, I think we'll have to live with that, and be very careful
when reviewing patches that touch the .hash files.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-06-22 22:12 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
2015-06-22 22:12   ` Yann E. MORIN [this message]
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=20150622221219.GD7547@free.fr \
    --to=yann.morin.1998@free.fr \
    --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