From: Nils Gillmann <niasterisk@grrlz.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: add lispf4
Date: Tue, 09 Feb 2016 02:31:51 +0100 [thread overview]
Message-ID: <87twliekjc.fsf@grrlz.net> (raw)
In-Reply-To: <20160208201442.GB2854@jasmine> (Leo Famulari's message of "Mon, 8 Feb 2016 15:14:42 -0500")
Leo Famulari <leo@famulari.name> writes:
> On Mon, Feb 08, 2016 at 12:17:51PM +0100, Nils Gillmann wrote:
>> Leo Famulari <leo@famulari.name> writes:
>> > On Sun, Feb 07, 2016 at 05:50:12PM +0100, Nils Gillmann wrote:
>
> [...]
>
>> >> * gnu/packages/lisp.scm (lispf4): New variable.
>
>> The diff looks okay for me, I only ended up with 2 (let*) because
>> of the package I took as an example.
>> Works for me, and if you have no further corrections I should do,
>> it's done on my side.
>
> Pushed, thanks for bearing with me :)
Thanks!
But now as I did guix pull and installed it from there, and do
not run it inside guix environment, I encounter an error I did
not see coming as it worked in the environment.
niasterisk@khazad-dum ~$ guix package -i lispf4
The following package will be installed:
lispf4 0.0.0-1-174d876 /gnu/store/7rkw1rhn4ijap9b936waspki03260lpb-lispf4-0.0.0-1-174d876
56 packages in profile
niasterisk@khazad-dum ~$ lispf4
Can't open 'SYSATOMS'
niasterisk@khazad-dum ~$ ls -al /gnu/store/7rkw1rhn4ijap9b936waspki03260lpb-lispf4-0.0.0-1-174d876/bin/
total 200
dr-xr-xr-x 2 root guixbuild 4096 Jan 1 1970 ./
dr-xr-xr-x 3 root guixbuild 4096 Jan 1 1970 ../
-r--r--r-- 3 root guixbuild 94972 Jan 1 1970 BASIC.IMG
-r-xr-xr-x 7 root guixbuild 92088 Jan 1 1970 lispf4
-r--r--r-- 7 root guixbuild 2105 Jan 1 1970 SYSATOMS
I checked ~/.guix-profile/bin/ and it's there, all three files.
For what I know, SYSATOMS includes allowed commands, that's it.
My guix checkout I develop with is in my home folder, permissions
for my daily user and all checked in guix environment.
Any Ideas?
--
ng / ni*
krosos.sdf.org
next prev parent reply other threads:[~2016-02-09 1:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 18:45 [PATCH] gnu: add lispf4 Nils Gillmann
2016-02-06 22:14 ` Leo Famulari
2016-02-07 0:01 ` Nils Gillmann
2016-02-07 10:59 ` Ricardo Wurmus
2016-02-07 11:09 ` Ricardo Wurmus
2016-02-07 15:09 ` Nils Gillmann
2016-02-18 11:38 ` [PATCH] gnu: add lispf4 (Update) Nils Gillmann
2016-02-18 11:48 ` Ricardo Wurmus
2016-02-07 16:50 ` [PATCH] gnu: add lispf4 Nils Gillmann
2016-02-08 0:36 ` Leo Famulari
2016-02-08 11:17 ` Nils Gillmann
2016-02-08 20:14 ` Leo Famulari
2016-02-09 1:31 ` Nils Gillmann [this message]
2016-02-09 7:16 ` Efraim Flashner
2016-02-09 10:30 ` Nils Gillmann
2016-02-10 5:36 ` Leo Famulari
2016-02-10 13:48 ` Nils Gillmann
2016-02-12 4:00 ` Leo Famulari
2016-02-14 3:52 ` Nils Gillmann
2016-02-14 8:10 ` Ricardo Wurmus
2016-02-14 21:31 ` Nils Gillmann
2016-02-14 21:36 ` Ricardo Wurmus
2016-02-14 4:05 ` Nils Gillmann
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=87twliekjc.fsf@grrlz.net \
--to=niasterisk@grrlz.net \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).