public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>,
	"Daniel Eklöf" <daniel@ekloef.se>
Subject: [gentoo-dev] heads up: codeberg changed gzip impls (?) for ${REPO}/archive/${TAG}.tar.gz files
Date: Mon, 11 Dec 2023 11:47:17 +0100	[thread overview]
Message-ID: <86h6kpaty4.fsf@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

hi,

it seems that codeberg has changed how they produce their archives on
URLs like <https://codeberg.org/dnkl/foot/archive/${tag}.tar.gz> leading
to digest failures like <https://bugs.gentoo.org/919135>, as implied by
the following checks:

  ~$ diff <(<dls/foot-1.16.2.tar.gz gzip -d) <(</var/cache/distfiles/foot-1.16.2.tar.gz gzip -d)
  ~$ diff <(<dls/foot-1.16.2.tar.gz cat) <(</var/cache/distfiles/foot-1.16.2.tar.gz cat)
  Binary files /dev/fd/63 and /dev/fd/62 differ

the above shows that compressed content differs while decompressed
content remains identical.

(dls/foot-1.16.2.tar.gz is downloaded from the master distfiles mirror,
/var/cache/distfiles/foot-1.16.2.tar.gz is fetched from codeberg at
around two in the morning last night)

you might want to regenerate manifests for projects fetching from
/archive/ urls on codeberg.

Daniel, thank you for working on foot.  may I ask that you attach 'meson
dist'-generated files to releases?  you could also use that opportunity
to hash or sign them, if you so desire.

in either case, thank you again.

have a lovely day, all!
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

             reply	other threads:[~2023-12-11 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 10:47 Arsen Arsenović [this message]
2023-12-11 12:47 ` [gentoo-dev] heads up: codeberg changed gzip impls (?) for ${REPO}/archive/${TAG}.tar.gz files Arsen Arsenović
2023-12-11 13:43 ` Eli Schwartz

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=86h6kpaty4.fsf@gentoo.org \
    --to=arsen@gentoo.org \
    --cc=daniel@ekloef.se \
    --cc=gentoo-dev@lists.gentoo.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