unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: jgart <jgart@dismail.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org, Guix Help <help-guix@gnu.org>
Subject: Re: what might be wrong with my nightly function?
Date: Wed, 16 Nov 2022 06:55:21 -0600	[thread overview]
Message-ID: <20221116065521.GC3853@dismail.de> (raw)
In-Reply-To: <A8D19BEE-016A-4271-BE7F-EE69F2ABE489@lepiller.eu>

On Wed, 16 Nov 2022 07:08:10 +0100 Julien Lepiller <julien@lepiller.eu> wrote:
> Haven't tested and you didn't share what was the issue. The obvious thing I see is #:olive-hash is (base32 "…") by default, so the origin uses (sha256 (base32 (base32 "…"))) by default

Thanks for catching that one!

I think the other issue is the way I am constructing the version and
then calling it at the command line:

guix doesn't like this:

guix build -L . olive@3302c36


;; let's tracking nightlies!
(define* (make-olive-nightly #:key olive-commit olive-hash)
    (package (inherit olive)
      (name "olive")
      (version (string-take olive-commit 7))
      (source
        (origin
          (method git-fetch)
          (uri (git-reference
	         (url "https://github.com/olive-editor/olive")
	         (commit olive-commit)))
          (file-name (git-file-name name version))
          (sha256
            (base32 olive-hash))))
      (build-system cmake-build-system)
      (arguments `(,@(package-arguments olive)
                 #:tests? #f))))
  
(define-public olive-3302c36
  (make-olive-nightly
    #:olive-commit "3302c3633c665fd32152217f254b53654945f2dd"
    #:olive-hash "0pp6dxn53aw6iiy9wnbkkmg8mcqpx8wy6nify8j4hrzvzrmks82c"))


      reply	other threads:[~2022-11-16 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16  1:37 what might be wrong with my nightly function? jgart
2022-11-16  6:08 ` Julien Lepiller
2022-11-16 12:55   ` jgart [this message]

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=20221116065521.GC3853@dismail.de \
    --to=jgart@dismail.de \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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.
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).