From: Jaft <jaft.r@outlook.com>
To: "54311@debbugs.gnu.org" <54311@debbugs.gnu.org>,
Maxime Devos <maximedevos@telenet.be>,
Tobias Geerinckx-Rice <me@tobias.gr>
Subject: [bug#54311] [PATCH] gnu: tint2: Update to 17.0.2.
Date: Wed, 9 Mar 2022 22:16:38 +0000 (UTC) [thread overview]
Message-ID: <DM5PR04MB3772C5E0A06B2150B148C144990A9@DM5PR04MB3772.namprd04.prod.outlook.com> (raw)
In-Reply-To: <45349612-98FB-4846-96C1-38A229245BED@tobias.gr>
> On Wednesday, March 9, 2022, 03:57:51 PM CST, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>
>
>
>
>
> What Maxime means is that some forges (like GitHub) generate these archives on the fly, instead of the author uploading a 'stable' file. You can usually tell them apart by the URL, but I forget GitLab's conventions.
>
> These archives might be cached for a while but if they are regenerated the hash could change even if the unpacked data didn't. This has happened in the past and breaks e.g. guix time-machine even if 'fixed' on master.
>
> Hence we prefer git-fetch when available, or tarballs that look human-generated.
>
> Kind regards,
>
> T G-R
Ahhh; I see. Thanks a ton for the explanation, Tobias. I'll get this switched over to git-fetch, Maxime, while I look over your other feedback.
next prev parent reply other threads:[~2022-03-09 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 19:34 [bug#54311] [PATCH] gnu: tint2: Update to 17.0.2 Wamm K. D
2022-03-09 20:28 ` Maxime Devos
2022-03-09 20:30 ` Maxime Devos
2022-03-09 21:46 ` Jaft
2022-03-09 21:57 ` Tobias Geerinckx-Rice via Guix-patches via
2022-03-09 22:16 ` Jaft [this message]
2022-03-09 20:31 ` Maxime Devos
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM5PR04MB3772C5E0A06B2150B148C144990A9@DM5PR04MB3772.namprd04.prod.outlook.com \
--to=jaft.r@outlook.com \
--cc=54311@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).