Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Chris Dimich <chris.dimich@boundarydevices.com>
Cc: Gary Bisson <bisson.gary@gmail.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	Refik Tuzakli <tuzakli.refik@gmail.com>,
	buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>,
	Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH 5/7] package/freescale-imx/imx-gpu-g2d: bump version to 6.4.3.p4.2
Date: Sat, 17 Sep 2022 22:15:02 +0200	[thread overview]
Message-ID: <20220917221502.3673b1c3@windsurf> (raw)
In-Reply-To: <20220824192604.2549356-12-chris.dimich@boundarydevices.com>

On Wed, 24 Aug 2022 12:26:02 -0700
Chris Dimich <chris.dimich@boundarydevices.com> wrote:

> -sha256  39fe307916e19a0892a514621121086e276a43858af90230372a1344852116a2  imx-gpu-g2d-6.4.3.p2.0-arm.bin
> -sha256  2642a49e088daae4cf568a150d01e7c095995e8a6ff1883c02c3fa6d26d254b3  imx-gpu-g2d-6.4.3.p2.0-aarch64.bin
> -sha256  ea58636bf34f589048fcd46e38497c47229fde8498df086ff5fb52f9ef8e15ee  COPYING
> -sha256  50099e283cfd307f84f159aeb1a6f462351320273dbcdb80d7f2c9db0494b71c  EULA
> +sha256  0ba9806c4efa0154fc9f7be406e42bc2c50b975abd32cbe322cf7bcf6ae0d350  imx-gpu-g2d-6.4.3.p4.2-arm.bin
> +sha256  ff50ddfee2d989798a2aba84ef9114e01f8d867293891dc0aacfab1640cbf8a3  imx-gpu-g2d-6.4.3.p4.2-aarch64.bin
> +sha256  4c89574f9a76e861919f80fef84bac30e4ba7fb8732b0fcda4b26d400239f517  COPYING
> +sha256  4c89574f9a76e861919f80fef84bac30e4ba7fb8732b0fcda4b26d400239f517  EULA

This hash seems wrong. You have the same hash for the COPYING file and
the EULA file, and the EULA file hash is incorrect:

>>> imx-gpu-g2d 6.4.3.p4.2-aarch64 Patching
>>> imx-gpu-g2d 6.4.3.p4.2-aarch64 Collecting legal info
ERROR: EULA has wrong sha256 hash:
ERROR: expected: 4c89574f9a76e861919f80fef84bac30e4ba7fb8732b0fcda4b26d400239f517
ERROR: got     : 423c76762d50b82fedd3e15c48e436d7272a7e130f9ebb910f76489345707cf6
ERROR: Incomplete download, or man-in-the-middle (MITM) attack

Could you check this on your side, and send an updated version?

When you send an updated version, please always resend the full series,
and increment the version number (using the -v option of git
format-patch).

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:[~2022-09-17 20:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 19:25 [Buildroot] [PATCH 1/7] toolchain/toolchain-external: update Arm AArch64 toolchain 11.2-2022.02 Chris Dimich
2022-08-24 19:25 ` [Buildroot] [PATCH 2/7] package/weston: add BR2_PACKAGE_WESTON_DEPRECATED_WL_SHELL config Chris Dimich
2022-08-24 19:25 ` [Buildroot] [PATCH 3/7] package/freescale-imx/kernel-module-imx-gpu-viv: bump to version 6.4.3.p4.2 Chris Dimich
2022-08-24 19:25 ` [Buildroot] [PATCH 4/7] package/freescale-imx/imx-gpu-viv: " Chris Dimich
2022-08-24 19:25 ` [Buildroot] [PATCH 5/7] package/freescale-imx/imx-gpu-g2d: bump version to 6.4.3.p4.2 Chris Dimich
2022-08-24 19:25 ` [Buildroot] [PATCH 6/7] package/freescale-imx/imx-vpu-hantro-vc: bump version to 1.7.0 Chris Dimich
2022-08-24 19:25 ` [Buildroot] [PATCH 7/7] package/freescale-imx/imx-vpu-hantro-daemon: add package Chris Dimich
2022-08-24 19:25 ` [Buildroot] [PATCH 1/7] toolchain/toolchain-external: update Arm AArch64 toolchain 11.2-2022.02 Chris Dimich
2022-08-28 15:29   ` Yann E. MORIN
2022-08-24 19:25 ` [Buildroot] [PATCH 2/7] package/weston: add BR2_PACKAGE_WESTON_DEPRECATED_WL_SHELL config Chris Dimich
2022-08-28 15:15   ` Yann E. MORIN
2022-09-02 18:22     ` Chris Dimich
2022-08-24 19:26 ` [Buildroot] [PATCH 3/7] package/freescale-imx/kernel-module-imx-gpu-viv: bump to version 6.4.3.p4.2 Chris Dimich
2022-08-28 15:44   ` Yann E. MORIN
2022-08-29 12:51     ` Gary Bisson
2022-09-02 18:43       ` Yann E. MORIN
2022-08-24 19:26 ` [Buildroot] [PATCH 4/7] package/freescale-imx/imx-gpu-viv: " Chris Dimich
2022-08-24 19:26 ` [Buildroot] [PATCH 5/7] package/freescale-imx/imx-gpu-g2d: bump version to 6.4.3.p4.2 Chris Dimich
2022-09-17 20:15   ` Thomas Petazzoni [this message]
2022-08-24 19:26 ` [Buildroot] [PATCH 6/7] package/freescale-imx/imx-vpu-hantro-vc: bump version to 1.7.0 Chris Dimich
2022-09-17 20:21   ` Thomas Petazzoni
2022-08-24 19:26 ` [Buildroot] [PATCH 7/7] package/freescale-imx/imx-vpu-hantro-daemon: add package Chris Dimich
2022-09-17 20:26   ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2022-08-24  2:48 [Buildroot] [PATCH 1/7] toolchain/toolchain-external: update Arm AArch64 toolchain 11.2-2022.02 Chris Dimich
2022-08-24  2:48 ` [Buildroot] [PATCH 5/7] package/freescale-imx/imx-gpu-g2d: bump version to 6.4.3.p4.2 Chris Dimich
2022-08-24  2:49 ` Chris Dimich

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=20220917221502.3673b1c3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=bisson.gary@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=chris.dimich@boundarydevices.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.de_schampheleire@nokia.com \
    --cc=tuzakli.refik@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox