Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
	Louis-Paul Cordier <lpdev@cordier.org>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/5] package/libva: switch to meson
Date: Mon, 30 Jan 2023 22:11:49 +0100	[thread overview]
Message-ID: <20230130221149.459c14d6@windsurf> (raw)
In-Reply-To: <20230130174339.36794-2-bernd.kuhls@t-online.de>

On Mon, 30 Jan 2023 18:43:36 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:

> -# From https://github.com/intel/libva/releases/download/2.17.0/libva-2.17.0.tar.bz2.sha1sum
> -sha1  997f7b3111bc5a4d32ec72e9d7f9fcfca41e4923  libva-2.17.0.tar.bz2
>  # Locally computed
> -sha256  f3e5eb27c305e05a9bb62703d1915a127301cc0c4f9f209025767432230c4eac  libva-2.17.0.tar.bz2
> +sha256  8940541980ef998a36cd8f6ad905e81838ea4ddf56dc479ed2bebd12711e6001  libva-2.17.0.tar.gz

Are you sure about this hash?

ERROR: libva-2.17.0.tar.gz has wrong sha256 hash:
ERROR: expected: 8940541980ef998a36cd8f6ad905e81838ea4ddf56dc479ed2bebd12711e6001
ERROR: got     : 2f3bb42b54c6c10f23ba61c00402354b7e408c6325d69cf7b353cf35e1f025c0
ERROR: Incomplete download, or man-in-the-middle (MITM) attack

Could you double check?

Thanks!

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:[~2023-01-30 21:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 17:43 [Buildroot] [PATCH 1/5] package/libva: bump version to 2.17.0 Bernd Kuhls
2023-01-30 17:43 ` [Buildroot] [PATCH 2/5] package/libva: switch to meson Bernd Kuhls
2023-01-30 21:11   ` Thomas Petazzoni via buildroot [this message]
2023-02-08  8:57   ` Thomas Petazzoni via buildroot
2023-01-30 17:43 ` [Buildroot] [PATCH 3/5] package/libva-utils: bump version to 2.17.1 Bernd Kuhls
2023-01-30 21:12   ` Thomas Petazzoni via buildroot
     [not found]   ` <20230130221242.2aa95b6e__49270.7143466518$1675113191$gmane$org@windsurf>
2023-01-30 21:22     ` Bernd Kuhls
2023-02-08  8:57   ` Thomas Petazzoni via buildroot
2023-01-30 17:43 ` [Buildroot] [PATCH 4/5] package/intel-mediadriver: bump version to 23.1.0 Bernd Kuhls
2023-01-30 21:15   ` Thomas Petazzoni via buildroot
     [not found]   ` <20230130221514.2d58df14__31334.1615417571$1675113344$gmane$org@windsurf>
2023-01-30 21:30     ` Bernd Kuhls
2023-01-30 21:39       ` Thomas Petazzoni via buildroot
2023-01-30 21:49         ` Bernd Kuhls
2023-01-30 22:04           ` Thomas Petazzoni via buildroot
2023-01-30 22:05           ` Thomas Petazzoni via buildroot
2023-01-30 22:00     ` Bernd Kuhls
2023-01-31 17:26       ` Peter Seiderer
2023-02-08  8:58   ` Thomas Petazzoni via buildroot
2023-01-30 17:43 ` [Buildroot] [PATCH 5/5] package/intel-mediasdk: " Bernd Kuhls
2023-02-08  8:58   ` Thomas Petazzoni via buildroot
2023-01-30 21:11 ` [Buildroot] [PATCH 1/5] package/libva: bump version to 2.17.0 Thomas Petazzoni via buildroot

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=20230130221149.459c14d6@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd.kuhls@t-online.de \
    --cc=eric.le.bihan.dev@free.fr \
    --cc=lpdev@cordier.org \
    --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