unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Brian Woodcox <bw@inskydata.com>
To: help-guix@gnu.org
Subject: Re: Having a problem invoking curl only when using guix pull
Date: Thu, 16 May 2019 15:49:58 -0600	[thread overview]
Message-ID: <AA832F67-4C12-460A-AB61-31D9D86E743E@inskydata.com> (raw)
In-Reply-To: <3483615C-9CB3-4184-B1F4-A4D19542FCA5@inskydata.com>

> 
> Hi,
> 
> I’m having problems with a piece of code.
> 
> ;; Retrieve git commit date
> (define get-commit-date (lambda _
>  (let* ((out (open-input-pipe (format #f "curl --silent '~a'" %api-url)))
>         (str (get-string-all out))
>         (queryResults (json-string->scm str))
>         (date (cdr (hash-get-handle (cdr (hash-get-handle (cdr (hash-get-handle queryResults "commit")) "author")) "date"))))
>         (display "Contacting github for commit date...\n")
>         (close-pipe out)
>         date)))
> 
> This code sits above my package code and I use it to dynamically populate my some values when building my package.
> 
> Everything works great and I can install the package locally without any problems.
> 
> My issue occurs if I try to issue a guix pull to bring this in through a separate channel.
> 
> When I do that I always get /gnu/store/…-bash-minimal-4.4.23/bin/bash: curl: command not found.
> 
> Any help would be greatly appreciated.
> 
> Thanks.
> 

So I’ve worked on this further and I was able to get the curl command to run.

In the end, it turns out that the networking service is not available when building a package.

It’s probably not worth the trouble to make it work.

  parent reply	other threads:[~2019-05-16 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 22:23 Having a problem invoking curl only when using guix pull Brian Woodcox
2019-05-16  3:13 ` ison
2019-05-16 21:49 ` Brian Woodcox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-16 22:53 Brian Woodcox
2019-05-17  0:21 ` John Soo
2019-05-17  0:31   ` Brian Woodcox
2019-05-17  1:04   ` Tobias Geerinckx-Rice

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=AA832F67-4C12-460A-AB61-31D9D86E743E@inskydata.com \
    --to=bw@inskydata.com \
    --cc=help-guix@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.
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).