From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Corrupt .drv files
Date: Tue, 12 Jul 2016 11:03:33 +0200 [thread overview]
Message-ID: <20160712090333.GA5688@solar> (raw)
In-Reply-To: <87inwbkzaf.fsf@gnu.org>
On Tue, Jul 12, 2016 at 10:59:04AM +0200, Ludovic Courtès wrote:
> So did they contain random bytes?
I do not know, since I did not look at the files with a hex editor
(we should package hexedit...).
Andreas
next prev parent reply other threads:[~2016-07-12 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160711081921.GA1651@solar>
[not found] ` <87k2gsjooh.fsf@gnu.org>
2016-07-11 21:49 ` Corrupt .drv files Ludovic Courtès
2016-07-11 22:04 ` Andreas Enge
2016-07-12 8:59 ` Ludovic Courtès
2016-07-12 9:03 ` Andreas Enge [this message]
2016-07-12 17:30 ` Kei Kebreau
2016-07-14 15:17 ` Andreas Enge
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=20160712090333.GA5688@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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).