unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <niasterisk@grrlz.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: add lispf4
Date: Wed, 10 Feb 2016 14:48:43 +0100	[thread overview]
Message-ID: <87oaboislg.fsf@grrlz.net> (raw)
In-Reply-To: <20160210053649.GC18281@jasmine> (Leo Famulari's message of "Wed, 10 Feb 2016 00:36:49 -0500")

Leo Famulari <leo@famulari.name> writes:

> On Tue, Feb 09, 2016 at 11:30:21AM +0100, Nils Gillmann wrote:
>> Efraim Flashner <efraim@flashner.co.il> writes:
>> > On Tue, 09 Feb 2016 02:31:51 +0100
>> > Nils Gillmann <niasterisk@grrlz.net> wrote:
>
> [...]
>
>> >
>> >> 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.
>
> [...]
>
>> > If you replace the install phase sometimes you have to change the permissions
>> > yourself. Try searching for #o555.
>> 
>> Okay, thanks.
>> I tried this but it doesn't change in the environment.
>> On another system, in Debian, the permissions (in my users home)
>> are:
>> SYSATOMS: 644
>> lispf4: 755
>> BASIC.IMG 644
>> 
>> without changes, current lispf4 from master:
>> niasterisk@khazad-dum ~/projects/guix_project/guix [env]$ ./pre-inst-env guix build lispf4
>> /gnu/store/7rkw1rhn4ijap9b936waspki03260lpb-lispf4-0.0.0-1-174d876
>> /gnu/store/871yzidvz2h4kpjx9sb116b0lshr88dn-lispf4-0.0.0-1-174d876-doc
>> niasterisk@khazad-dum ~/projects/guix_project/guix [env]$ 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-- 4 root guixbuild 94972 Jan  1  1970 BASIC.IMG
>> -r-xr-xr-x 8 root guixbuild 92088 Jan  1  1970 lispf4
>> -r--r--r-- 8 root guixbuild  2105 Jan  1  1970 SYSATOMS
>> 
>> If I try 555 for both files, the output with the rights is below.
>> I wonder, do I need to set it to 644 as it happens on the Debian
>> system? Should I use guix system vm to test this? I expected that
>> environment behaves like what pushed as a patch...
>
> I'm not sure — did you figure out a solution to the problem with the
> package?

Yes and no.
I am not sure, as I don't know Guix enough currently.
On Debian, compiled in $HOME I get 644 on SYSATOMS + BASIC.IMG.
If this is the default, should I just assume for a moment that
this will be okay to set for (chmod) in the install procedure and
patch it as such?

I'm distracted by problems out of my control currently, but I'm
still trying to get this solved.
-- 
ng

  reply	other threads:[~2016-02-10 13:48 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
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 [this message]
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=87oaboislg.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).