public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Go 1.25.3 release is botched at Google
Date: Sun, 2 Nov 2025 08:05:58 +0100	[thread overview]
Message-ID: <2b875d1c-50ef-4679-bb41-3e1cf89791b3@gmail.com> (raw)

Hi,

apparently, the pre-built Go 1.25.3 release, both the
* prebuilt tarballs at https://goloang.org/dl, and
* source tarball at https://dl.google.com/go
are compressed twice with gzip but is named as tar.gz instead of tar.gz.gz

Therefore, the checksums are incorrect, and the downloaded
file cannot be uncompressed with a single tar xzf command.

Uncompressing the tarballs once with gzip makes them match
the expected checksum and can be extracted with tar xvf.

Adding downloadfilename=<basename>.tar.gz.gz makes it download
and extract ONCE, so the result is the <basename>.tar.gz tarball file
instead of the extracted sources or prebuilt stuff.



             reply	other threads:[~2025-11-02  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-02  7:05 Böszörményi Zoltán [this message]
2025-11-02 16:18 ` [OE-core] Go 1.25.3 release is botched at Google Marko, Peter
2025-11-03  6:23   ` Böszörményi Zoltán

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=2b875d1c-50ef-4679-bb41-3e1cf89791b3@gmail.com \
    --to=zboszor@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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