All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Asaf Kahlon <asafka7@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-rtoml: bump to version 0.10.0
Date: Tue, 6 Feb 2024 14:45:57 +0100	[thread overview]
Message-ID: <ZcI4FZx1kKqT8Xwk@landeda> (raw)
In-Reply-To: <c48e9859-c68f-46ca-8d76-4af73535f488@mind.be>

Arnout, All,

On 2024-02-06 09:49 +0100, Arnout Vandecappelle via buildroot spake thusly:
> On 05/02/2024 18:21, James Hilliard wrote:
> > On Mon, Feb 5, 2024 at 4:29 AM Arnout Vandecappelle <arnout@mind.be> wrote:
> > > On 11/01/2024 06:22, James Hilliard wrote:
> > > > Migrate from setuptools-rust to maturin infrastructure.
> > > > 
> > > > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> > > > ---
> > > >    package/python-rtoml/python-rtoml.hash | 2 +-
> > > >    package/python-rtoml/python-rtoml.mk   | 6 +++---
> > > >    2 files changed, 4 insertions(+), 4 deletions(-)
> > > > 
> > > > diff --git a/package/python-rtoml/python-rtoml.hash b/package/python-rtoml/python-rtoml.hash
> > > > index 04d22ed1a4..59f17d9d62 100644
> > > > --- a/package/python-rtoml/python-rtoml.hash
> > > > +++ b/package/python-rtoml/python-rtoml.hash
> > > > @@ -1,4 +1,4 @@
> > > >    # Locally calculated after vendoring
> > > > -sha256  821a430ab6587bdaaf7cb95044e8e0d99c77c6aed0adce5a370045b270f7ee20  rtoml-0.8.0.tar.gz
> > > > +sha256  987d3d9e9d56761b17c3e4e172937cbcc793bf24b0ebb2730647a9a2cf86c789  rtoml-0.10.0.tar.gz
> > > 
> > >    Same problem:
> > > 
> > > ERROR: while checking hashes from package/python-rtoml//python-rtoml.hash
> > > ERROR: rtoml-0.10.0.tar.gz has wrong sha256 hash:
> > > ERROR: expected: 987d3d9e9d56761b17c3e4e172937cbcc793bf24b0ebb2730647a9a2cf86c789
> > > ERROR: got     : 624cc1ff2b3fdea42aeee3a4d1537d37431ec001870dfee1e04a12bd3076a2d3
> > Hmm, I'm unable to reproduce this issue.

Turned out that Arnout's setup was slightly borked, and he was using a
1.35 tar to create the archvies...

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

  reply	other threads:[~2024-02-06 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  5:22 [Buildroot] [PATCH 1/1] package/python-rtoml: bump to version 0.10.0 James Hilliard
2024-02-05 11:28 ` Arnout Vandecappelle via buildroot
2024-02-05 17:21   ` James Hilliard
2024-02-06  8:49     ` Arnout Vandecappelle via buildroot
2024-02-06 13:45       ` Yann E. MORIN [this message]
2024-02-06 13:44 ` Yann E. MORIN
2024-07-22 12:50 ` 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=ZcI4FZx1kKqT8Xwk@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=arnout@mind.be \
    --cc=asafka7@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.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 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.