Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gob2: add a hash file
Date: Wed, 9 Dec 2015 16:02:55 +0000	[thread overview]
Message-ID: <566850AF.4020602@imgtec.com> (raw)
In-Reply-To: <56684F62.1020205@zacarias.com.ar>

Hi Gustavo,

On 09/12/15 15:57, Gustavo Zacarias wrote:
> On 09/12/15 12:41, Vicente Olivert Riera wrote:
> 
>> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>> ---
>>   package/gob2/gob2.hash | 2 ++
>>   1 file changed, 2 insertions(+)
>>   create mode 100644 package/gob2/gob2.hash
>>
>> diff --git a/package/gob2/gob2.hash b/package/gob2/gob2.hash
>> new file mode 100644
>> index 0000000..3678bdd
>> --- /dev/null
>> +++ b/package/gob2/gob2.hash
>> @@ -0,0 +1,2 @@
>> +# Locally calculated
>> +sha256
>> f7ee84c07ca88ae96e5a60461957cc4dd0aa69d61804433d1c85de3d50be8026 
>> gob2-2.0.20.tar.xz
> 
> Hi Vicente.
> Why not
> http://ftp.acc.umu.se/pub/gnome/sources/gob2/2.0/gob2-2.0.20.sha256sum ?
> Regards.
> That's the official upstream and there's a mismatch, oops.

Well, we currently download this tool from here:

http://ftp.5z.com/pub/gob/

And the tarball downloaded from there has the hash value I wrote in my
.hash file.

If you say that's the official upstream, then the .mk file needs to be
updated as well.

Regards,

Vincent.

> Regards.

  reply	other threads:[~2015-12-09 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 15:41 [Buildroot] [PATCH] gob2: add a hash file Vicente Olivert Riera
2015-12-09 15:57 ` Gustavo Zacarias
2015-12-09 16:02   ` Vicente Olivert Riera [this message]
2015-12-09 16:04     ` Vicente Olivert Riera
2015-12-09 16:10       ` Gustavo Zacarias
2015-12-12 13:34 ` 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=566850AF.4020602@imgtec.com \
    --to=vincent.riera@imgtec.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