From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: core-updates warning: Not ready for GuixSD deployment Date: Thu, 4 Jan 2018 12:31:19 -0500 Message-ID: <20180104173119.GA6465@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40093) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eX9Mp-0008Uf-EJ for guix-devel@gnu.org; Thu, 04 Jan 2018 12:32:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eX9MR-0002Q4-G3 for guix-devel@gnu.org; Thu, 04 Jan 2018 12:31:47 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:49583) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eX9MQ-0002MV-Sj for guix-devel@gnu.org; Thu, 04 Jan 2018 12:31:23 -0500 Received: from localhost (c-73-165-108-70.hsd1.pa.comcast.net [73.165.108.70]) by mail.messagingengine.com (Postfix) with ESMTPA id 8463B7E183 for ; Thu, 4 Jan 2018 12:31:21 -0500 (EST) Content-Disposition: inline List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I recommend you do not reconfigure any systems that are important based on the current core-updates branch. After applying the proposed fix for GPM [0], I reconfigured my headless GuixSD system using core-updates. 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. [0] --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlpOZOMACgkQJkb6MLrK fwi69Q/+Pm7wRsLZb0IP1nABL0HWz/9d8CqzJEsPxyyMscuFDg+HohpJ+cqFU0OF smGO2UoH3jFjfhdh97YlJ9odWudEGMM4XpxFAkr34fYd2LK92Umqb6xJB5kNMA98 jK9ap3jv4yxcOSMwWaiYwkgFkbHopJNTGXoX3bH4sFAWvijYUZlB6koO8F1/62l5 SiuXgZpDYJhQgW18udDpMryknCv4GyYfznfH3Vt7Vl7HjTLaOS318bxugAAYlvAj GxqzNqd4x5b0AJEn9UlTcPC9NgiYlWBq9qrH/XUb7TsAansec/6CBBIoKP9g4VNq 45uliPiPoGcWer9Az/Lukc4rnlcvAFhbMDTt+p+Hx3EFdS9rSnSyTjeyEA8n3Et4 Dh1lW1weSZqreFw0RmxTVwfRbUTQ1vfax9pPzCeH+Wka5hAxmEZPbMNoP9d97dMY 79XbGXkpHxW1XUnxhYVe+OGAt91sZFfhUP4wNe+KMRgYH0nDZDJkXjfjQpqC7YX8 6S65Ys4/oShDMDf+Pw3DSswztQawoZBFZCyxaYviN4k6ebRBtDWNq8cPwAWc4ZFr O3ktCSemdWBy3fDrGuSvOALobYZuqvqWX4j7PSOnvfFNj4tow5yePYbQB2XaqfrU /jDkGvbPO4sPqCfZ+Z7L/sF3FsQsQ03QOlipyd58U5F/MIGuGsI= =IIDv -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--