All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Floris Bos <bos@je-eigen-domein.nl>,
	buildroot@buildroot.org, Heiko Thiery <heiko.thiery@gmail.com>,
	linux-amarula@amarulasolutions.com,
	"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/ipmitool: add hash for enterprise-numbers.txt
Date: Fri, 23 Aug 2024 09:55:50 +0200	[thread overview]
Message-ID: <20240823095550.012ac485@windsurf> (raw)
In-Reply-To: <20240823063318.961358-1-dario.binacchi@amarulasolutions.com>

On Fri, 23 Aug 2024 08:33:18 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:

> Fixes:
> - http://autobuild.buildroot.org/results/5ae5ee948d99679cd50d1115a7d46f4368347b4f
> 
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>

I believe it is not possible to do that
because https://www.iana.org/assignments/enterprise-numbers.txt is not a
"versioned" URL, and that file is regularly updated, so this hash will
become broken at some point in the future, causing breakage.

So basically, we need one of the two following options:

(Best)      Find a URL for enterprise-numbers.txt that is versioned, so
            that we know what we fetch is stable

(Less Best) Add something like BR_REALLY_NO_CHECK_HASH_FOR that
            continues to disable the hash check even when
            BR2_DOWNLOAD_FORCE_CHECK_HASHES is enabled

Best regards,

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-08-23  7:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23  6:33 [Buildroot] [PATCH 1/1] package/ipmitool: add hash for enterprise-numbers.txt Dario Binacchi
2024-08-23  7:55 ` 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=20240823095550.012ac485@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bos@je-eigen-domein.nl \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=heiko.thiery@gmail.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.