Re: [Buildroot] [PATCH v2 2/3] package/ripgrep: bump to version 14.0.3

From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
	sebastian.weyer@smile.fr,
	Antoine Coutant <antoine.coutant@smile.fr>,
	James Hilliard <james.hilliard1@gmail.com>,
	buildroot@buildroot.org, romain.naour@smile.fr
Subject: Re: [Buildroot] [PATCH v2 2/3] package/ripgrep: bump to version 14.0.3
Date: Sun, 31 Dec 2023 12:01:58 +0100	[thread overview]
Message-ID: <ZZFKJtLm9ko7L6se@landeda> (raw)
In-Reply-To: <ZZEzoC30PnpTgqLa@landeda>

All,

On 2023-12-31 10:25 +0100, Yann E. MORIN spake thusly:
> On 2023-12-30 20:44 +0100, Yann E. MORIN spake thusly:
> > On 2023-12-30 19:00 +0100, Thomas Petazzoni via buildroot spake thusly:
> > > Note that I also encountered some hash mismatch on some Rust/Cargo
> > > package recently, and BR was falling back to sources.buildroot.net. I
> > > did not have the time to investigate at the time (I was looking into
> > > another issue, and didn't want to enter an infinite recursion of
> > > problem solving quest). And now, I don't remember with which package I
> > > encountered this. But yes, it seems like we have a reproducibility
> > > issue.
[--SNIP--]
> I took some time to try and pinpoint the issue. Alas, I have no clue,
> just more questions.
[--SNIP--]
> As a reminder, commit e27a700f3e contains the core infra fix just after
> the conversion of ripgrep to the cargo infra. Here's a little summary of
> what happens
> 
>                             e27a700f3e      master
>     Ubuntu 16.04.7;
>       - native              OK              KO +
>     Fedora 39:
>       - native              KO *            KO +
>       - ./utils/docker-run  OK              KO +
> 
> So, we have two issues:
>   - the cargo version has an impact on the vendoring
>   - the build environment has an impact on the vendoring.

So, turned out that, on F39, we hit the tar 1.35 issue on e27a700f3e.
Building host-tar before trying to vendor ripgrep fixes the issue.

So, at least, that's that: we *can* reproduce the proper hash for
ripgrep at the time it was bumped.

So, we're now left with just the cargo version issue... Which is in fact
rather good news: we do not have an unknown dependency on the build
environment.

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