From: ludo@gnu.org (Ludovic Courtès)
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: bug#28745 <28745-done@debbugs.gnu.org>
Subject: bug#28745: [PATCH] tarballs generated on github are generated on demand (leading to different hash sums)
Date: Fri, 20 Oct 2017 23:04:43 +0200 [thread overview]
Message-ID: <871slxcyz8.fsf@gnu.org> (raw)
In-Reply-To: <87k1zv7pos.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 15 Oct 2017 23:10:43 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> I could finish a script that helped me finding all of our affected
> packages, verify that only the hash but not the content of the archives
> had changed, as well as automate the hash update for those safe to
> update.
Great job!
> Attached is the patch and the scripts I used. I think we might
> want to reuse some of it to extend guix lint to warn packagers that
> archives coming from .*github.*archives URL are not guaranteed to be
> stable and that it would be better, if available, to use manually
> uploaded releases archives.
Unfortunately, it’s become commonplace to publish nothing else than a
Git tag. Now, in those cases, we could also use ‘git-fetch’, which
wouldn’t be affected by problems with generated tarballs.
Thoughts?
> PS: I've also uploaded the scripts here:
> https://notabug.org/apteryx/fiasco for ease of cloning. Any comments
> about my nascent (ab)use of Scheme are welcome!
The code looks nice!
> From 774a764149ecb0e234ae09c9a0a273af671c3c86 Mon Sep 17 00:00:00 2001
> From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
> Date: Sun, 15 Oct 2017 22:17:12 -0400
> Subject: [PATCH] gnu: packages: Fix the hashes of mutated GitHub archives.
>
> Fixes bug https://bugs.gnu.org/28745.
>
> * gnu/packages/audio.scm (csound): Fix hash.
> * gnu/packages/engineering.scm (fritzing): Likewise.
> * gnu/packages/erlang.scm (erlang): Likewise.
> * gnu/packages/fonts.scm (font-google-material-design-icons): Likewise.
> * gnu/packages/graphics.scm (ogre): Likewise.
> * gnu/packages/java.scm (java-plexus-interpolation, antlr3): Likewise.
> * gnu/packages/serialization.scm (yaml-cpp): Likewise.
> * gnu/packages/version-control.scm (libgit2): Likewise.
I’ve checked the hashes by running:
./pre-inst-env guix build -S --no-substitutes csound fritzing erlang \
font-google-material-design-icons ogre java-plexus-interpolation \
antlr3 yaml-cpp libgit2 --max-jobs=2
and everything went well.
Pushed as fd75eb6cd4e5c689f9e6ce7dd8d87f423778d308, thanks!
Ludo’.
next prev parent reply other threads:[~2017-10-20 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 11:40 bug#28745: tarballs generated on github are generated on demand (leading to different hash sums) ng0
2017-10-08 11:44 ` ng0
2017-10-08 21:18 ` Jan Nieuwenhuizen
2017-10-08 21:58 ` Ricardo Wurmus
2017-10-16 3:10 ` bug#28745: [PATCH] " Maxim Cournoyer
2017-10-20 21:04 ` Ludovic Courtès [this message]
2017-10-22 3:13 ` Maxim Cournoyer
2017-10-22 10:48 ` Ricardo Wurmus
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=871slxcyz8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28745-done@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.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.
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).