All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@aperture.us>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Anisse Astier <anisse@astier.eu>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 1/1] package/tailscale: new package
Date: Mon, 29 Jul 2024 22:10:51 +0200	[thread overview]
Message-ID: <20240729221051.2e84f11f@windsurf> (raw)
In-Reply-To: <CA+h8R2rym0T+bcy3mUUSXKxwYtNH7KuTV0oUV-7PdCQdA6L5jQ@mail.gmail.com>

On Mon, 29 Jul 2024 12:26:46 -0700
Christian Stewart <christian@aperture.us> wrote:

> This was solved already on Tailscale master branch:
> 
> https://github.com/tailscale/tailscale/issues/12859#issuecomment-2239157563
> 
> It was fixed in this commit:
> 
> https://github.com/tailscale/tailscale/commit/0f57b9340b1449de811a9dacd098a769192c4344

Thanks for having looked into this!

> I don't see a release yet with this commit. We could either take the
> latest master commit hash for now or apply a patch with this commit.

I think applying a patch doesn't work because this error happens during
the vendoring step, which is part of the download step, and is
therefore *before* we apply any patches.

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

  parent reply	other threads:[~2024-07-29 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27 20:23 [Buildroot] [PATCH v3 1/1] package/tailscale: new package James Hilliard
2024-07-29 18:33 ` Thomas Petazzoni via buildroot
2024-07-29 19:26   ` Christian Stewart via buildroot
2024-07-29 19:29     ` Christian Stewart via buildroot
2024-07-29 20:10     ` Thomas Petazzoni via buildroot [this message]
2024-07-30 15:15       ` James Hilliard

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=20240729221051.2e84f11f@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.