Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
Cc: buildroot@buildroot.org, "Miquèl Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/gdb: add hash of licence files
Date: Fri, 13 Dec 2024 10:09:57 +0100	[thread overview]
Message-ID: <20241213100957.0b0a2a2f@windsurf> (raw)
In-Reply-To: <20241211-add_gdb_hash-v1-1-eb02d192b6c1@bootlin.com>

Hello Thomas,

Thanks for the patch! See some comments below.

On Wed, 11 Dec 2024 18:42:50 +0100
Thomas Bonnefille <thomas.bonnefille@bootlin.com> wrote:

> Adds sha512 hash of the license files for GDB.
> 
> Signed-off-by: Thomas Bonnefille <thomas.bonnefille@bootlin.com>

This patch triggers some "make check-package" warnings.

WARNING: package/gdb/gdb.hash:10: separation does not match expectation (https://nightly.buildroot.org/#adding-packages-hash)
WARNING: package/gdb/gdb.hash:11: separation does not match expectation (https://nightly.buildroot.org/#adding-packages-hash)
WARNING: package/gdb/gdb.hash:12: separation does not match expectation (https://nightly.buildroot.org/#adding-packages-hash)
WARNING: package/gdb/gdb.hash:13: separation does not match expectation (https://nightly.buildroot.org/#adding-packages-hash)

To help avoid such warnings, I have https://paste.ack.tf/0859f0
in .git/hooks/post-commit.

Also, we normally use sha256 for license files hashes, and in fact even
for locally calculated hashes in general. We only use sha512 when it's
what provided by upstream. I guess sha512 has been used here for the
special ARC version of GDB because sha512 was used for the other gdb
versions who hash is provided by upstream. But I believe for the
license file we should be consistent with what we do in other packages,
and use sha256.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-12-13  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 17:42 [Buildroot] [PATCH] package/gdb: add hash of licence files Thomas Bonnefille via buildroot
2024-12-13  9:09 ` Thomas Petazzoni via buildroot [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=20241213100957.0b0a2a2f@windsurf \
    --to=buildroot@buildroot.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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