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 1/1] package/avrdude: fix tarball hash
Date: Wed, 10 Mar 2021 22:24:37 +0100	[thread overview]
Message-ID: <20210310212437.GR2737665@scaer> (raw)
In-Reply-To: <20210310191802.264463-1-fontaine.fabrice@gmail.com>

Fabrice, All,

On 2021-03-10 20:18 +0100, Fabrice Fontaine spake thusly:
> tarball hash is broken since commit
> 03fa36df7e6aca0f4a1c8ae2fe691c0cda6ddc7a
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/712167620d46ed0175da89dfe77a8db2534b925d

Up[dating a hash file should be accompanied by explanations why it has
to be updated. If you look the commit log for 03fa36df7e6, you will
notice that there is an explicit mention about the hash.

So we have an issue, because that hash is what I computed when I applied
03fa36df7e6, and it is still what I get here on my machine right now.

This means that, once again, the svn download backend does not easily
allow generating reproducible archives... :-(

The issue happens on my autobuilder, so I will be able to investigate.

Regards,
Yann E. MORIN.

> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/avrdude/avrdude.hash | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/avrdude/avrdude.hash b/package/avrdude/avrdude.hash
> index c7b4bf85bc..e0f11f8e73 100644
> --- a/package/avrdude/avrdude.hash
> +++ b/package/avrdude/avrdude.hash
> @@ -1,3 +1,3 @@
>  # Locally computed
> -sha256  a74532a61d07e43fc598ade4202e9a8c8697bce3e6031c5be6f51da651595f99  avrdude-r1450-br1.tar.gz
> +sha256  28887d8cdd31c3090f5d49c297abd859a845eafc36104185e7584dbef0920a19  avrdude-r1450-br1.tar.gz
>  sha256  201babc7da198873304a77a30dbfc7ca449c9bba52df2dffa4cca0009dbdfcb2  avrdude/COPYING
> -- 
> 2.30.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

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

  reply	other threads:[~2021-03-10 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 19:18 [Buildroot] [PATCH 1/1] package/avrdude: fix tarball hash Fabrice Fontaine
2021-03-10 21:24 ` Yann E. MORIN [this message]
2021-03-10 21:29   ` Yann E. MORIN

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=20210310212437.GR2737665@scaer \
    --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