From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [GSoC19] Motivation
Date: Thu, 04 Apr 2019 12:11:01 +0200 [thread overview]
Message-ID: <87imvunkqy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAGCTLNRDiCJXoNOintN_BayTD0SL3QSUZGBcTLHEWsO6wozkgw@mail.gmail.com> (Mohamed Dawod's message of "Thu, 4 Apr 2019 09:08:35 +0200")
>>>>> "Mohamed" == Mohamed Dawod <mhm.dawod@gmail.com> writes:
>>
>> >>>>> Peter Korsgaard <peter at korsgaard.com <mhm.dawod@gmail.com>> writes:
>> > Sorry, I bumped wget yesterday:
>>
> No problem, I will find some other package to update.
> But I noticed that my patch is slightly different of yours
> This id my patch :
> Signed-off-by: Mohamed Dawod <mhm.dawod@gmail.com>
>> ---
>> diff -Naur wget/wget.hash wget2/wget.hash
>> --- a/package/wget.hash 2019-04-03 14:38:50.133423838 +0200
>> +++ b/package/wget.hash 2019-04-03 15:09:44.834238846 +0200
>> @@ -1,6 +1,6 @@
>> # Locally calculated after checking pgp signature
>> -# https://ftp.gnu.org/gnu/wget/wget-1.20.1.tar.lz.sig
>> +# https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz.sig
>> # with key 1CB27DBC98614B2D5841646D08302DB6A2670428
>> -sha256 0f63e84dd23dc53ab3ab6f483c3afff8301e54c165783f772101cdd9b1c64928
>> wget-1.20.1.tar.lz
>> +sha256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
>> wget-1.20.2.tar.lz
>> # Locally calculated
>> sha256 e79e9c8a0c85d735ff98185918ec94ed7d175efc377012787aebcf3b80f0d90b
>> COPYING
>> diff -Naur wget/wget.mk wget2/wget.mk
>> --- a/package/wget.mk 2019-04-03 14:38:50.133423838 +0200
>> +++ b/package/wget.mk 2019-04-03 14:40:12.080507178 +0200
>> @@ -4,7 +4,7 @@
>> #
>>
>> ################################################################################
>>
>> -WGET_VERSION = 1.20.1
>> +WGET_VERSION = 1.20.2
>> WGET_SOURCE = wget-$(WGET_VERSION).tar.lz
>> WGET_SITE = $(BR2_GNU_MIRROR)/wget
>> WGET_DEPENDENCIES = host-pkgconf
>>
> The difference is new sha256sum of the new package.
> I downloaded the new package from the link "
> https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz"
> then I run the command $sha256sum wget-1.20.2.tar.lz
> how can the checksum be different ?
Ehh, I don't know. I just tried it again here:
wget https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz
--2019-04-04 12:09:23-- https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.lz
Resolving ftp.gnu.org (ftp.gnu.org)... 209.51.188.20, 2001:470:142:3::b
Connecting to ftp.gnu.org (ftp.gnu.org)|209.51.188.20|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2134961 (2.0M) [application/x-tar]
Saving to: ?wget-1.20.2.tar.lz?
wget-1.20.2.tar.lz 100%
[===================================================================>] 2.04M 2.12MB/s in 1.0s
2019-04-04 12:09:24 (2.12 MB/s) - ?wget-1.20.2.tar.lz? saved [2134961/2134961]
sha256sum wget-1.20.2.tar.lz
84d3cbece8c08e130a8da0a72cf6e543a2adf58ca8ecf28726560b06243d4ce6 wget-1.20.2.tar.lz
Which matches current git.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-04-04 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 19:07 [Buildroot] [GSoC19] Motivation Mohamed Dawod
2019-04-01 19:44 ` Thomas Petazzoni
2019-04-02 3:14 ` Mohamed Dawod
2019-04-03 22:14 ` Mohamed Dawod
2019-04-04 5:56 ` Peter Korsgaard
2019-04-04 7:08 ` Mohamed Dawod
2019-04-04 10:11 ` Peter Korsgaard [this message]
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=87imvunkqy.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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