From: Peter Korsgaard <peter@korsgaard.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: wireguard-tools-1.0.20210914.tar.xz hash changed
Date: Mon, 26 Aug 2024 09:36:57 +0200 [thread overview]
Message-ID: <87y14jbuqu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87a5h6e4fk.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Wed, 21 Aug 2024 09:11:11 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
Hello Jason,
Was this change done on purpose?
> Hi Jason,
> Did you recently upgrade xz on git.zx2c4.com? I see that the hash of
> wireguard-tools-1.0.20210914.tar.xz changed:
> http://autobuild.buildroot.org/results/d63b8f5b14487f6d79c9779bb7fe4829fae0653b/build-end.log
> We have a backup of the original file on sources.buildroot.net:
> mkdir a b
> wget -q -P a
> https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20210914.tar.xz
> wget -q -P b https://sources.buildroot.net/wireguard-tools/wireguard-tools-1.0.20210914.tar.xz
> sha256sum */*
> 942ed32d1d6631932c82ff86c91ae8428d4c90bfec231a14ebdf6c29f068e60b
> a/wireguard-tools-1.0.20210914.tar.xz
> 97ff31489217bb265b7ae850d3d0f335ab07d2652ba1feec88b734bc96bd05ac
> b/wireguard-tools-1.0.20210914.tar.xz
> The uncompressed tarball is identical:
> unxz */*xz
> sha256sum */*tar
> 22d6d0b12ec69be002313a89dbe2c08c07d48c5b93af528189ceab351b3b718d
> a/wireguard-tools-1.0.20210914.tar
> 22d6d0b12ec69be002313a89dbe2c08c07d48c5b93af528189ceab351b3b718d
> b/wireguard-tools-1.0.20210914.tar
> It would be great if we could have a bit-identical .tar.xz.
> --
> Bye, Peter Korsgaard
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2024-08-26 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 7:11 Peter Korsgaard
2024-08-26 7:36 ` Peter Korsgaard [this message]
2024-08-26 8:35 ` Jason A. Donenfeld
2024-08-26 9:02 ` Peter Korsgaard
2024-08-26 9:04 ` Jason A. Donenfeld
2024-08-26 9:14 ` Peter Korsgaard
2024-08-26 9:19 ` Kim Nilsson
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=87y14jbuqu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).