From: Ricardo Wurmus <rekado@elephly.net>
To: Adonay Felipe Nogueira <adfeno@hyperbola.info>
Cc: 33993@debbugs.gnu.org
Subject: bug#33993: Missing Texinfo documentation for Guix itself
Date: Sun, 06 Jan 2019 10:10:31 +0100 [thread overview]
Message-ID: <871s5qrw1k.fsf@elephly.net> (raw)
In-Reply-To: <79d26d32-b9d4-7e8a-4457-bb4c0fd01c81@hyperbola.info>
Adonay Felipe Nogueira <adfeno@hyperbola.info> writes:
> This copy of Guix (in Trisquel 8.0 Flidas amd64) was installed using the
> shell script installer (for which I became root for that, that is, used
> `sudo -i'). The binary version downloaded was 0.16.0.
>
> At least after pulling and upgrading the recipes based on commit
> "5a7899fd88c1c463d3b75ac9077ccd183ddec914" (I didn't test this before
> pulling, sorry), the Texinfo documentation for Guix itself seems to be
> mising, even from root's profile.
The installer script creates links from
/var/guix/profiles/per-user/root/current-guix/share/info to
/usr/local/share/info. Is the former directory populated as you would
expect?
> Interestingly, despite "$GUIX_PROFILE/share/info" not having the Texinfo
> documentation as described, "/usr/local/share/info" has at least some
> "dir."* files that seem to come from Guix. While "guix"{,"."*}".info.gz"
> are present in the form of broken symbolic links, each of which pointing
> to their counterparts in
> "/var/guix/profiles/per-user/root/current-guix/share/info".
This is odd. Do the files exist in
/var/guix/profiles/per-user/root/current-guix/share/info? Can you
please show us the output of “ls -la /usr/local/share/info” and “ls -la
/var/guix/profiles/per-user/root/current-guix/share/info”?
--
Ricardo
next prev parent reply other threads:[~2019-01-06 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 2:56 bug#33993: Missing Texinfo documentation for Guix itself Adonay Felipe Nogueira
2019-01-06 9:10 ` Ricardo Wurmus [this message]
2019-01-06 17:35 ` Adonay Felipe Nogueira
2019-01-08 17:41 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s5qrw1k.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=33993@debbugs.gnu.org \
--cc=adfeno@hyperbola.info \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.