From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org, Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH 1/1] package/go/go-bin: re-introduce go-src hash
Date: Tue, 11 Feb 2025 08:30:44 +0100 [thread overview]
Message-ID: <874j115463.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250210191802.426552-1-thomas.perale@mind.be> (Thomas Perale's message of "Mon, 10 Feb 2025 20:18:02 +0100")
>>>>> "Thomas" == Thomas Perale <thomas.perale@mind.be> writes:
> The commit b4006287f8 "package/go: security bump to version 1.23.6"
> removed the go source from the go-bin package `.hash` file.
> Since that commit, a number of autobuild errors for the host-go-bin
> package started spawning during the 'legal-info' step.
> Because the package 'go-bin' defines the '_ACTUAL_SOURCE_TARBALL'
> variable the source hash is still required for the legal-info.
> Similarly to the 'nodejs' package, the hash files for both the `go-bin`
> and `go-src` package are shared in the `package/go` directory with the
> help of a symbolic link used to make the subdirectories point to that
> common `.hash` file.
> Fixes:
> https://autobuild.buildroot.org/results/337/33763441a065ddb07e944e26ad8f1f6d43b68592
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Crap, indeed - Sorry for breaking it. I see that Romain has already
applied it.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-11 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 19:18 [Buildroot] [PATCH 1/1] package/go/go-bin: re-introduce go-src hash Thomas Perale via buildroot
2025-02-10 22:15 ` Romain Naour via buildroot
2025-02-11 7:30 ` Peter Korsgaard [this message]
2025-02-11 17:01 ` Peter Korsgaard
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=874j115463.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.perale@mind.be \
/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.