From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id OAPwFUo7PF9mVAAA0tVLHw (envelope-from ) for ; Tue, 18 Aug 2020 20:34:18 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id qC/GEUo7PF85RQAA1q6Kng (envelope-from ) for ; Tue, 18 Aug 2020 20:34:18 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id E7BB19404E0 for ; Tue, 18 Aug 2020 20:34:17 +0000 (UTC) Received: from localhost ([::1]:43266 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k88JE-0005yE-Tx for larch@yhetil.org; Tue, 18 Aug 2020 16:34:16 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:51698) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k88J5-0005y1-D5 for guix-devel@gnu.org; Tue, 18 Aug 2020 16:34:07 -0400 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]:42625) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k88J3-00017L-F3 for guix-devel@gnu.org; Tue, 18 Aug 2020 16:34:07 -0400 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 488B45BE; Tue, 18 Aug 2020 16:34:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 18 Aug 2020 16:34:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=famulari.name; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=mesmtp; bh=0uDwS72/Dsn0jitcTsiPp3ko ev2YK97kWpuCdFMmi9s=; b=R/fMI74NjYLonLvS3mPPnk+8d3ua8Ecc+TxZA85p Yl80uX32DTbRwyxyLFu5s1xJuSSY2jJWCSwM7XQstEiRcd1P85AagM1bDSAlWVdx LSzYXfrB4BsHvO0IoxSQV1dYORH98aFAAZ0i8gFIGaDuxmcVutm1xSuJJrzZqQgu qvY= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=0uDwS7 2/Dsn0jitcTsiPp3koev2YK97kWpuCdFMmi9s=; b=g/6kleO9RUzuMpMOYmW+TM z2lgGOoxzkWXG/O/XQ+4OdNoMtnwUlXZLW0FvHkOfuewcGGH56W5IXz2JG2Ij+ES yPwo04xadJnQQ2qiT07tKxbJ6FEC91iNilbSpO4hoPK52WaNKxSkCk4NRyz7TnfO KREIfEBxc2ns/rZ0epNMCH1/phMVV0DeAvnZQMbZWV0ZwDNiP31TCJ4I4VJItrN1 lBJ7SWMSPYq0B7iXxFhFXZvIkctJNQMbvuoDiCpSsmziVJGKcT7XMJGEaXzNc/rg uqX2thVh4/UAmLn6gbvMCWTJIFMW6CGWm+W8HyPGndVLmNgJ9DXB3oixkeciCHiw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddtiedgudefudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttd ertddttddvnecuhfhrohhmpefnvghoucfhrghmuhhlrghrihcuoehlvghosehfrghmuhhl rghrihdrnhgrmhgvqeenucggtffrrghtthgvrhhnpeeukeektdffvddtudegjeegtdevhf eufeeivdejiedtieegtdevjedvjeehffevgfenucfkphepudejvddrheeirddvvddrheej necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheplhgvoh esfhgrmhhulhgrrhhirdhnrghmvg X-ME-Proxy: Received: from localhost (unknown [172.56.22.57]) by mail.messagingengine.com (Postfix) with ESMTPA id 75E8630600A6; Tue, 18 Aug 2020 16:34:01 -0400 (EDT) Date: Tue, 18 Aug 2020 16:33:53 -0400 From: Leo Famulari To: HiPhish Subject: Re: Questions about Git and workflow Message-ID: <20200818203353.GA26961@jasmine.lan> References: <2818350.e9J7NaK4W3@ixtreme-m5740> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2818350.e9J7NaK4W3@ixtreme-m5740> Received-SPF: pass client-ip=64.147.123.21; envelope-from=leo@famulari.name; helo=wout5-smtp.messagingengine.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/18 16:34:02 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=famulari.name header.s=mesmtp header.b=R/fMI74N; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=g/6kleO9; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -1.21 X-TUID: zf2wktXQSyFx On Tue, Aug 18, 2020 at 08:38:39PM +0200, HiPhish wrote: > My first question is regarding `guix git authenticate`. The first time I ran it > after a `git clone ...` and `guix environment guix` I got an error saying that > the `keyring` branch cannot be found. So I did a `git checkout --track origin/ > keyring`, but I got a different error instead: > > $ guix git authenticate 9edb3f66fd807b096b48283debdcddccfea34bad "BBB0 > 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA" > Authenticating commits 9edb3f6 to ec32c85 (3 new commits)... > guix git: error: commit ec32c8591eb111023db514800145532a1e454125 not > signed by an authorized key: F5DA 2032 4B87 3D0B 7A38 7672 0DB0 FF88 4F55 > 6D79 > > Finally I did a `git pull` on both the `keyring` and the `master` branch and > the check passed. > > So my first question is: did I do it correctly? If not, what is the correct > workflow? It sounds like you did it correctly. After bringing the 'keyring' branch up to date, the authentication succeeded. If you want to explore more, compare the keyring branch before and after you updated it. > My second question is regarding the `.po` files which get changed during the > build process. Git shows me a number of language-specific files as modified, even > though I never touched them by hand. Should those changes be commited? Should > I include them when I send a patch? Why are they even version-controlled if > they get changed automatically? I ignore these changes. When they occur I do `git checkout po` to erase them. I don't really know what's "correct" here but we can expect some minor annoyances like this in the development environment. > My last question is about the local state directory. The manual says the pass > my current local state directory (by default `/var`) to `./configure`, but then > my store gets mutated. I would prefer not to store my weird experiments where > my day-to-day packages lie. I know I can revert at any time, but I'd rather > not. I instead created `./var` and passed `$(pwd)/var` to `./configure`. The > question is, is this the way to go? When I tried building a package (`/pre- > inst-env guix install go-github-com-junegunn-fzf`) Guix complained that there > was no deamon running, so do I need a second shell running the deamon (`sudo - > E ./pre-inst-env guix-daemon --build-users-group=guixbuild`) as well? I recommend not using a different local state directory. There should not be any negative (or even observable) effects of your experimental artifacts being in /gnu/store. I haven't tried managing multiple stores but I assume you'd need to run a separate daemon for each, configured for the correct directories.