unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: core-updates warning: Not ready for GuixSD deployment
Date: Wed, 10 Jan 2018 09:51:16 -0800	[thread overview]
Message-ID: <20180110175116.GC32702@jasmine.lan> (raw)
In-Reply-To: <87d12irs8g.fsf@gnu.org>

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

On Wed, Jan 10, 2018 at 10:13:51AM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > After rebooting, I found that my user's numerical ID had changed, so I
> > no longer owned any of my files. Not being able to read ~/.ssh means you
> > can't log in remotely.
> >
> > Additionally, several of root's "dotfiles" had been replaced with their
> > default versions, erasing my modifications. For example,
> > ~root/.bash_profile no longer contained my modifications.
> >
> > Finally, my users's password no longer worked. I fixed this as root
> > before I noticed that my user's files were inaccessible; I don't know if
> > I could have avoided the password reset by re-chowning my files.
> 
> Long story short: this should be fixed by
> 
>   https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates&id=4610ab7c9a5327df0d475262817bc081a5891aa8
> 
> Below is the message I wrote as I was investigating, if you’re curious.
> :-)

Thanks, I was very curious :)

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

      reply	other threads:[~2018-01-10 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 17:31 core-updates warning: Not ready for GuixSD deployment Leo Famulari
2018-01-08 10:50 ` Ludovic Courtès
2018-01-10  9:13 ` Ludovic Courtès
2018-01-10 17:51   ` Leo Famulari [this message]

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=20180110175116.GC32702@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).