From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: Christian Stewart <christian@aperture.us>,
James Hilliard <james.hilliard1@gmail.com>,
Anisse Astier <anisse@astier.eu>
Subject: Re: [Buildroot] [PATCH v4 1/2] package/pkg-golang.mk: allow packages to override download GOPROXY
Date: Wed, 23 Oct 2024 21:25:45 +0200 [thread overview]
Message-ID: <20241023212545.28838fc1@windsurf> (raw)
In-Reply-To: <CA+h8R2o--yr=J8bmo6R=rBStYLxwOW+fvEKQ3zfLuKrdZznCCA@mail.gmail.com>
Hello,
On Wed, 23 Oct 2024 09:35:16 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
> It is a proxy, not a download URL. The intent of the entire Go module
> system is to be based on source control under the hood. We should be able
> to check out the git repositories of the underlying source without having
> to use the Google proxy.
>
> If we make a habit of ignoring these hash mismatches it will become very
> easy for people to stuff code into a release on GitHub and then change the
> tag to something else later, leaving behind the old record in GOPROXY and
> tricking maintainers into reviewing the wrong code on the modified GitHub
> tag.
>
> There must be some reason why your package is having this issue. With
> anchore quill package we found that it was git lfs with test files causing
> the problem.
I continue to agree with Christian. If using caching proxies is needed
to avoid downloading the "real" upstream because the real upstream has
changed/is broken, things are severely wrong.
Instead, I would recommend to patch netbird to resolve this issue. I
know this requires patches to be applied *before* the vendoring step,
but that it something that anyway would be useful to have. So I would
suggest to find a way to do that. Perhaps some special patch extension,
like package/<foo>/*.vendoring-patch or some other better name, that
would be applied before the vendoring step takes place?
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
next prev parent reply other threads:[~2024-10-23 19:25 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 16:31 [Buildroot] [PATCH v4 1/2] package/pkg-golang.mk: allow packages to override download GOPROXY James Hilliard
2024-08-05 16:31 ` [Buildroot] [PATCH v4 2/2] package/tailscale: new package James Hilliard
2024-08-06 1:14 ` Christian Stewart via buildroot
2024-08-12 20:17 ` Christian Stewart via buildroot
2024-08-19 19:57 ` Christian Stewart via buildroot
2024-08-05 17:34 ` [Buildroot] [PATCH v4 1/2] package/pkg-golang.mk: allow packages to override download GOPROXY Christian Stewart via buildroot
2024-08-05 20:31 ` Thomas Petazzoni via buildroot
2024-08-05 22:01 ` James Hilliard
2024-08-06 1:07 ` Christian Stewart via buildroot
2024-08-06 14:50 ` Thomas Petazzoni via buildroot
2024-08-06 15:49 ` James Hilliard
2024-08-06 16:13 ` Christian Stewart via buildroot
2024-08-06 16:43 ` James Hilliard
2024-08-06 16:57 ` Thomas Petazzoni via buildroot
2024-08-06 18:53 ` Christian Stewart via buildroot
2024-10-23 15:21 ` James Hilliard
2024-10-23 16:35 ` Christian Stewart via buildroot
2024-10-23 17:30 ` James Hilliard
2024-10-23 19:25 ` Thomas Petazzoni via buildroot [this message]
2024-10-23 19:49 ` James Hilliard
2024-10-23 20:36 ` Christian Stewart via buildroot
2024-10-23 21:05 ` Thomas Petazzoni via buildroot
2024-10-23 21:51 ` James Hilliard
2024-10-25 20:11 ` Christian Stewart via buildroot
2024-10-26 4:58 ` Christian Stewart via buildroot
2024-10-26 4:59 ` Christian Stewart via buildroot
2025-02-05 12:51 ` Christian Stewart via buildroot
2025-02-05 14:02 ` James Hilliard
2025-02-05 15:45 ` Arnout Vandecappelle via buildroot
2025-02-05 18:02 ` James Hilliard
2025-02-05 20:01 ` Christian Stewart via buildroot
2025-02-05 20:38 ` James Hilliard
2025-02-05 21:22 ` Christian Stewart via buildroot
2025-02-05 21:53 ` Arnout Vandecappelle via buildroot
2025-02-05 22:05 ` James Hilliard
2025-02-05 22:25 ` Christian Stewart via buildroot
2025-02-05 21:55 ` James Hilliard
2025-02-05 22:18 ` Christian Stewart via buildroot
2025-02-05 22:56 ` James Hilliard
2025-02-05 23:31 ` Christian Stewart via buildroot
2025-02-05 23:45 ` James Hilliard
2025-02-05 17:56 ` [Buildroot] Fwd: " Christian Stewart via buildroot
2025-02-05 18:45 ` James Hilliard
2025-02-06 19:31 ` Fiona Klute via buildroot
2025-02-07 17:35 ` James Hilliard
2025-02-07 17:50 ` Christian Stewart 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=20241023212545.28838fc1@windsurf \
--to=buildroot@buildroot.org \
--cc=anisse@astier.eu \
--cc=christian@aperture.us \
--cc=james.hilliard1@gmail.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