unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Tomáš Čech" <sleep_walker@gnu.org>
Cc: 25852@debbugs.gnu.org
Subject: bug#25852: Users not updating their installations of Guix
Date: Wed, 8 Mar 2017 03:45:47 -0500	[thread overview]
Message-ID: <20170308084547.GA7436@jasmine> (raw)
In-Reply-To: <20170308062542.hfypmvgp2o6il2xf@penguin>

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

On Wed, Mar 08, 2017 at 07:25:42AM +0100, Tomáš Čech wrote:
> Unless I'm missing some other commit, this won't work.
> 
> When I perform these steps:
> 1] ./configure && make && sudo make install (or package installation)
> 2] mkdir /gnu/store
> 3] attempt to start daemon will fail as there is no guix-daemon in
>   @localstatedir@/guix/profiles/per-user/root/guix-profile/bin/guix-daemon
>   because there is no guix-daemon in /gnu/store

I haven't used `make install`. Does this change break it? On my system,
the old @bindir@ method didn't yield a usable guix-daemon.service
either, because there is no '/usr/local/bin/guix-daemon'.

The binary tarball that we distribute includes the guix-daemon in its
store, and the '/var/guix/...' path works too.

There were lots of people trying to follow the Binary Installation
instructions in the manual [0] and getting stuck on step 5. They weren't
able to symlink the systemd service file, and they had to edit the file
too.

With this change, the instructions in the manual should work whether or
not the user copies or symlinks the service file.

[0]
https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-03-08  8:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 21:11 bug#25852: Users not updating their installations of Guix Leo Famulari
2017-02-24  5:42 ` Pjotr Prins
2017-03-02 18:16 ` sirgazil
2017-03-04 20:29 ` Tomáš Čech
2017-03-04 22:43   ` Leo Famulari
2017-03-05  7:56     ` Tomáš Čech
2017-03-05  9:25       ` Pjotr Prins
2017-03-05  9:43         ` Tomáš Čech
2017-03-06 14:52           ` Ricardo Wurmus
2017-03-07  6:54             ` Pjotr Prins
2017-03-06 21:12 ` Ludovic Courtès
2017-03-06 21:34   ` Leo Famulari
2017-03-07  6:33     ` Tomáš Čech
2017-03-07 19:51       ` Leo Famulari
2017-03-07 20:58         ` Tomáš Čech
2017-03-07 22:22           ` Leo Famulari
2017-03-08  6:25             ` Tomáš Čech
2017-03-08  8:45               ` Leo Famulari [this message]
2017-03-08  9:24                 ` Tomáš Čech
2017-03-08 18:15                   ` Leo Famulari
2017-03-09  7:38                     ` Efraim Flashner
2017-03-09 10:58               ` Ludovic Courtès
2017-03-09 12:42                 ` Tomáš Čech
2017-03-09 15:42                   ` Ludovic Courtès
2017-03-07  7:32   ` Mark H Weaver
2017-03-07 10:35     ` Ludovic Courtès
2017-03-11  1:48       ` Mark H Weaver
2017-05-10 13:12         ` Ludovic Courtès
2017-05-10 14:13           ` myglc2
2017-05-10 20:16             ` Ludovic Courtès
2017-05-12  6:06               ` Ricardo Wurmus
2017-05-12  8:29                 ` Ludovic Courtès
2017-05-12 17:10                   ` myglc2

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=20170308084547.GA7436@jasmine \
    --to=leo@famulari.name \
    --cc=25852@debbugs.gnu.org \
    --cc=sleep_walker@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.
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).