From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@aperture.us>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Christian Stewart via buildroot <buildroot@buildroot.org>,
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 23:05:25 +0200 [thread overview]
Message-ID: <20241023230525.1f991184@windsurf> (raw)
In-Reply-To: <CA+h8R2r0e97u77C9QzSYr_jczF=2zC0+Hz=Y73HUpVh7NGgJUw@mail.gmail.com>
On Wed, 23 Oct 2024 13:36:50 -0700
Christian Stewart <christian@aperture.us> wrote:
> > I'm not actually trying to modify the dependencies specified at all, if
> > the only download location for a specified dependency I need is on
> > https://proxy.golang.org then I'm not sure how I would patch the
> > package to use that instead.
> >
>
> You should report the issue to the upstream repository like I did with
> tailscale, they will update the dependency to a newer version that doesn't
> have the checksums mismatch
I agree... but we should have a way in Buildroot to fix the issue even
if upstream is not responsive or cooperative. So the answer to a
problem cannot only be "let's wait until upstream fixes it".
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 21:05 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
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 [this message]
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=20241023230525.1f991184@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 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.