From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: Guix binary tarball Date: Fri, 15 May 2015 19:37:48 +0200 Message-ID: <20150515173748.GA15397@debian> References: <20150515164602.GA13539@debian> <87382xwyoz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47777) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtJYg-0004DO-H6 for guix-devel@gnu.org; Fri, 15 May 2015 13:38:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YtJYe-00046e-CP for guix-devel@gnu.org; Fri, 15 May 2015 13:38:02 -0400 Content-Disposition: inline In-Reply-To: <87382xwyoz.fsf@gnu.org> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?iso-8859-15?Q?Court=E8s?= Cc: guix-devel@gnu.org On Fri, May 15, 2015 at 07:14:04PM +0200, Ludovic Courtès wrote: > What were the symptoms on your machine? Did guix-build{,er} turn out > to have different UID/GID? We did not try it; our first aim was to get back to sshing into the machine (luckily, we still had a terminal open somewhere). Maybe guix would have worked. > > As a consequence, we could not ssh into the machine any more > > (!). > I don’t see how this could happen. Try "chown 30000.30001 $HOME". Then ssh into the machine asks for the passphrase instead of using the public-private key pair. > > Could these directories be left out of the tarball and only their > > contents be kept in? > No. Maybe we can fix it by using two tar invocations with different > --owner. Well, you never know what permissions the directories have on the target machine, and these are also changed. Maybe one needs to untar with particular options. Andreas