all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: 28745@debbugs.gnu.org
Subject: bug#28745: tarballs generated on github are generated on demand (leading to different hash sums)
Date: Sun, 8 Oct 2017 11:40:09 +0000	[thread overview]
Message-ID: <20171008114009.3tyhcuioaau6tlya@abyayala> (raw)

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

Past and recent discussion in our IRC channel and on the mailing list
show that we can not rely on tarballs on github keeping the same
hash forever.
According to github they are "generated on demand", leading to
regular hash mismatches.

Since some of our own dependencies are on github (at the very least
guile-git), we need to come up with a solution.

Right now we have around 449 packages with tarball sources from
github in our gnu/packages.
We could:

- Move them all to use git-download and just use
  the commit that has been tagged in the versions that produce
  the tarballs on github.

- Mirror the content somewhere reliable in snapshots for
  some time. Problem here: we start to rely on this "somewhere"
  to be trustworthy and introduce one more point to trust
  (however due to pre-recorded hash sum this is just an annoyance,
  not a grave issue).

- Your idea here.

-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://dist.krosos.org/dist/keys/
https://www.infotropique.org https://krosos.org

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

             reply	other threads:[~2017-10-08 11:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 11:40 ng0 [this message]
2017-10-08 11:44 ` bug#28745: tarballs generated on github are generated on demand (leading to different hash sums) 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171008114009.3tyhcuioaau6tlya@abyayala \
    --to=ng0@infotropique.org \
    --cc=28745@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.