Re: Fixed output derivation hash mismatch - why?

[Chris Marusich <cmmarusich@gmail.com>]

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

Mark H Weaver <mhw@netris.org> writes:

> I think the problem is here:
>
>   (define hash (sha256
>                 (base32
>                  "1r3v22qkypccqifzbww5lrn6hf1chi23m6zzkyvb8bvg457nxslq")))
>
> Remove the 'sha256'.  It should just be this:
>
>   (define hash (base32
>                 "1r3v22qkypccqifzbww5lrn6hf1chi23m6zzkyvb8bvg457nxslq"))
>
> Within 'origin' records, the 'sha256' is the field name, part of the
> constructor syntax.  Here, you are not within an 'origin' constructor,
> and the 'sha256' is instead a procedure which computes the sha256 hash
> of its argument.

This was the problem!  I misunderstood what the daemon was telling me,
and I didn't realize that "sha256" was the field name.

I knew a second pair of eyes would help!  Thank you for helping me to
see more clearly, Mark.  :-)

-- 
Chris

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