all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Cook source disappeared
Date: Sun, 24 Jul 2016 12:45:57 -0400	[thread overview]
Message-ID: <20160724164557.GB2527@jasmine> (raw)
In-Reply-To: <20160724162513.GA17850@jocasta.intra>

On Sun, Jul 24, 2016 at 06:25:14PM +0200, John Darrington wrote:
>      https://www.gnu.org/software/guix/packages/issues.html
>      
> But if I understand correctly, that is not going to do anything if hydra's internal
> cache is good.  From what Andraes says, we only noticed this because we happened to
> loose the cache.

No, it checks the URLs without consulting Hydra's cache. It does not
check the content itself (the hashes).

From that page, I noticed the issues with Cook and Aegis last year but —
considering the situation, and not knowing that Hydra's cache was not
backed up — I decided to work on other things. The cache would never
have deleted the source code as long as the packages remained in our
tree.

This project is trying to address the problem:
https://www.softwareheritage.org/

I wonder if Guix can use that archive as a last resort?

  reply	other threads:[~2016-07-24 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23 18:46 Cook source disappeared Andreas Enge
2016-07-23 19:23 ` Leo Famulari
2016-07-23 20:17   ` Andreas Enge
2016-07-24  1:58   ` John Darrington
2016-07-24 13:12     ` Efraim Flashner
2016-07-24 15:41       ` Leo Famulari
2016-07-24 16:25       ` John Darrington
2016-07-24 16:45         ` Leo Famulari [this message]
2016-07-24 18:10           ` Efraim Flashner
2016-07-24 18:15             ` Andreas Enge
2016-07-25  8:14           ` Ludovic Courtès
2016-07-24 18:15     ` Andreas Enge
2016-07-24 18:53       ` John Darrington

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=20160724164557.GB2527@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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.