From: ludo@gnu.org (Ludovic Courtès)
To: carl hansen <carlhansen1234@gmail.com>
Cc: 22402@debbugs.gnu.org
Subject: bug#22402: info guix pages
Date: Tue, 19 Jan 2016 10:01:53 +0100 [thread overview]
Message-ID: <87a8o2djsu.fsf@gnu.org> (raw)
In-Reply-To: <CAHEkXCR1eCAW1wG_kbfm6bQt5x=PLFyjHcYHHZx-U3kBfbpT9w@mail.gmail.com> (carl hansen's message of "Mon, 18 Jan 2016 19:55:48 -0800")
carl hansen <carlhansen1234@gmail.com> skribis:
> On Mon, Jan 18, 2016 at 5:47 PM, Leo Famulari <leo@famulari.name> wrote:
>
>> On Mon, Jan 18, 2016 at 03:43:35PM -0800, carl hansen wrote:
>> > I do
>> > "info guix"
>> > and I don't get the info pages, although OTHER info pages work
>> > and INFOPATH seems correct.
>> > BUt if I am root then I do get
>> > info guix correctly.
>> > I can see the files are there in the file system.
>> > It seems that the guix.info should be automatically accessible
>> > to regular users, or do I have to do some additonal step?
>> > Or is it just me?
>>
>> Are you using GuixSD or Guix on a "foreign distro"?
>>
>
> ubuntu
Where is Guix installed? If you used the “binary installation” method,
Guix is installed in /root/.guix-profile, which is why you only get to
see its manual when running ‘info’ as root.
HTH,
Ludo’.
next prev parent reply other threads:[~2016-01-19 9:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 23:43 bug#22402: info guix pages carl hansen
2016-01-19 1:47 ` Leo Famulari
2016-01-19 3:55 ` carl hansen
2016-01-19 9:01 ` Ludovic Courtès [this message]
2016-01-19 9:34 ` carl hansen
2016-01-19 10:45 ` Ludovic Courtès
2016-01-19 16:42 ` Efraim Flashner
2016-01-19 17:17 ` Thompson, David
2016-01-19 22:02 ` Leo Famulari
2016-01-20 0:45 ` carl hansen
2016-01-20 4:24 ` Leo Famulari
2016-01-21 1:26 ` carl hansen
2016-01-21 3:21 ` Leo Famulari
2016-01-20 23:23 ` Ludovic Courtès
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=87a8o2djsu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22402@debbugs.gnu.org \
--cc=carlhansen1234@gmail.com \
/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).