Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Sebastian Michel <sebastian.michel@oss.othermo.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/wireguard-tools: switch to git-based source download
Date: Mon, 16 Nov 2026 10:38:58 +0100	[thread overview]
Message-ID: <87zev915fx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <f5679391-fea4-4ad3-a0dc-01e7031dbd7b@oss.othermo.de> (Sebastian Michel's message of "Mon, 16 Nov 2026 09:15:27 +0100")

>>>>> "Sebastian" == Sebastian Michel <sebastian.michel@oss.othermo.de> writes:

Hello,

 > Ah sorry, I should have given more context here.
 > I am having the issue for package `wireguard-tools-1.0.20250521`,
 > which was the previous release of that package in buildroot.
 > I suspect that wireguard-tools was re-packaged for some reason and
 > then uploaded using the same file name.
 > To prevent this from happening again in the future, I created this patch.
 > Take a look at the following log.
 > The first downloads hash verification fails, source:
 > https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20250521.tar.xz
 > The second download succeeds, source:
 > https://sources.buildroot.net/wireguard-tools/wireguard-tools-1.0.20250521.tar.xz

Ahh, indeed, so the immeditate issue is only for 2025.02.x, where we
could change to git download OR simply to always fetch from
sources.buildroot.net.

Longer term we could indeed change master to fetch from git in case
similar issues occur in the future.


 >> Ahh, as the author of cgit, Jason would probably like to know about 
 >> that. Did you contact him?

 > Not yet, thanks for the suggestion. I'll contact Jason to report the
 > issue with the cgit snapshot download.

I had a look at the wireguard-tools-1.0.20250521.tar.xz differences, and
the .tar files are identical, but the .xz output differs, so it is most
likely caused by a (security) update of xz on the git.zx2c4.com machine.

I don't know how the cgit archive logic works. If there is come caching
then he could perhaps replace the 20250521 file with the copy we have on
sources.buildroot.net?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-11-16  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13  9:26 [Buildroot] [PATCH] package/wireguard-tools: switch to git-based source download Sebastian Michel
2026-11-14 14:00 ` Peter Korsgaard
2026-11-16  8:15   ` Sebastian Michel
2026-11-16  9:38     ` Peter Korsgaard [this message]

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=87zev915fx.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=sebastian.michel@oss.othermo.de \
    /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