Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	linux-amarula@amarulasolutions.com,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/3] package/bmap-tools: update GitHub URL
Date: Tue, 7 May 2024 22:09:28 +0200	[thread overview]
Message-ID: <ZjqKeObcP8cjtoHG@landeda> (raw)
In-Reply-To: <87msp1wqqo.fsf@dell.be.48ers.dk>

Peter, All,

On 2024-05-07 18:06 +0200, Peter Korsgaard spake thusly:
> >>>>> "Dario" == Dario Binacchi <dario.binacchi@amarulasolutions.com> writes:
>  > As reported in the README file of the old GitHub URL (i.e.
>  > https://github.com/intel/bmap-tools), "The code at this location is no
>  > longer maintained and will likely be removed in the future. This project
>  > has moved to https://github.com/yoctoproject/bmaptool".
[--SNIP--]
> I wanted to apply this to 2024.02.x, but this change of repo changes the
> hash of the tarball (I guess the name of the toplevel directory
> changed):
> 
> ERROR: while checking hashes from package/bmap-tools//bmap-tools.hash
> ERROR: bmap-tools-3.6.tar.gz has wrong sha256 hash:
> ERROR: expected: 0658afb972e7221aa16fece3f84e29e5102e901c929253d7fb6040bde28243f7
> ERROR: got     : 7a2e1305bf7e06bc4a580cc719f0facf9d99af8d41659b57c0acae4ad93ff45a
> ERROR: Incomplete download, or man-in-the-middle (MITM) attack

Indeed, that's because the top-level dirctory changed, from bmap-tools/
to bmaptools/ as it is generated by github.

I missed that, because I only tested the whole series, which ends up
with a version bump, with an explicit hash change then, which was
correct...

I totally missed the fact that the top-level directory would change,
sorry...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-05-07 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 13:05 [Buildroot] [PATCH v2 1/3] package/bmap-tools: update GitHub URL Dario Binacchi
2024-04-14 13:05 ` [Buildroot] [PATCH v2 2/3] package/bmap-tools: rename Kconfig prompt to bmaptool Dario Binacchi
2024-04-14 13:05 ` [Buildroot] [PATCH v2 3/3] package/bmap-tools: bump to version 3.8.0 Dario Binacchi
2024-04-15 16:29   ` Yann E. MORIN
2024-05-07 16:06 ` [Buildroot] [PATCH v2 1/3] package/bmap-tools: update GitHub URL Peter Korsgaard
2024-05-07 18:58   ` Dario Binacchi
2024-05-07 19:39     ` Peter Korsgaard
2024-05-07 20:10       ` Dario Binacchi
2024-05-07 21:08         ` Peter Korsgaard
2024-05-07 20:09   ` Yann E. MORIN [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=ZjqKeObcP8cjtoHG@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=peter@korsgaard.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