all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Fredrik Salomonsson <plattfot@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: btrfs and subvolumes for root, take 2
Date: Wed, 28 Nov 2018 18:17:33 +0100	[thread overview]
Message-ID: <87lg5d15qq.fsf@gnu.org> (raw)
In-Reply-To: <877eh1otpy.fsf@gmail.com> (Fredrik Salomonsson's message of "Sun, 25 Nov 2018 11:14:17 -0800")

Hello Fredrik,

Fredrik Salomonsson <plattfot@gmail.com> skribis:

> guix archive --authorize < /gnu/store/cw55zvxzi3d9cjmhfvxsryz31jxb1y6k-guix-0.15.0-1.4876bc8/share/guix/berlin.guixsd.org.pub
> guix pull --commit=d9f8e84 --substitute-urls="http://berlin.guixsd.org http://mirror.hydra.gnu.org"
> guix system init /mnt/etc/config.scm /mnt --substitute-urls="http://berlin.guixsd.org http://mirror.hydra.gnu.org"

The Guile backtrace you sent shows that /etc/ssl already existed when
your system booted and was not a symlink.  This led the “activation
code” of GuixSD to fail:

  https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/build/activation.scm#n320

The solution is to remove /etc/ssl (is it coming from another distro
previously installed on this device?).  You can boot a separate medium, 
mount the root partition, and “rm -rf /etc/ssl” from there.  Or you can,
at the boot REPL that you get after the backtrace, type something like:

  ,use (guix build utils)
  (delete-file-recursively "/etc/ssl")
  ,q

Note that you might have similar issues with /etc/pam.d, for instance,
if there’s such a stale directory.

HTH,
Ludo’.

       reply	other threads:[~2018-11-28 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877eh1otpy.fsf@gmail.com>
2018-11-28 17:17 ` Ludovic Courtès [this message]
2018-12-02  4:51   ` btrfs and subvolumes for root, take 2 Fredrik Salomonsson
2018-12-02 14:31     ` Ludovic Courtès
2018-12-03  1:56       ` Fredrik Salomonsson

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=87lg5d15qq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=plattfot@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 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.