From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id QLVYAkIgPF8VeQAA0tVLHw (envelope-from ) for ; Tue, 18 Aug 2020 18:38:58 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id wBCWOUEgPF9dXgAAbx9fmQ (envelope-from ) for ; Tue, 18 Aug 2020 18:38:57 +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 5DB889402C2 for ; Tue, 18 Aug 2020 18:38:57 +0000 (UTC) Received: from localhost ([::1]:50648 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k86Vc-0005mT-4m for larch@yhetil.org; Tue, 18 Aug 2020 14:38:56 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:48342) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k86VU-0005mK-Cw for guix-devel@gnu.org; Tue, 18 Aug 2020 14:38:48 -0400 Received: from mout01.posteo.de ([185.67.36.65]:53639) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k86VS-0007sk-2M for guix-devel@gnu.org; Tue, 18 Aug 2020 14:38:48 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 1D84516005C for ; Tue, 18 Aug 2020 20:38:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1597775921; bh=S/ks/fzJGopx2D2KDNcINCP/KiDS18wuzu9hZXlq0n4=; h=From:To:Subject:Date:From; b=gZhWMq7/Z3YGFkuVRY5UZgnrPZqXLYjHZqpu+8U8YOKCJpVpcnzbOHMK6luq5jkUt KqgksCO69QwTSUZsAShfrRbq0+4aVGsg99OByVZ7TsHdOJcImcain1L9cis5wRKJ6k tV6jgDhUy6LQXD1avIBw4k6I3SYo1LaHi3LAHE5zktrG66UIU4icE2s/ivk5HD0hDs nGtkGZEDOrg0/NeASdYdPM5FN7WA7j6Nl6iJcwS5evW4IUCjekiDzla3E53LHJyinr VH0cWIIn5hAizBoekV6hUBSpbPHDN9JOroLhInmiaL4xmfcyTOjn2HfFXQQeGIk91N phnfoLIeheXxw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4BWKS01P56z6tmJ for ; Tue, 18 Aug 2020 20:38:39 +0200 (CEST) From: HiPhish To: guix-devel@gnu.org Subject: Questions about Git and workflow Date: Tue, 18 Aug 2020 20:38:39 +0200 Message-ID: <2818350.e9J7NaK4W3@ixtreme-m5740> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Received-SPF: pass client-ip=185.67.36.65; envelope-from=hiphish@posteo.de; helo=mout01.posteo.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/18 12:36:24 X-ACL-Warn: Detected OS = Linux 3.11 and newer X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=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: , 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=posteo.de header.s=2017 header.b=gZhWMq7/; dmarc=pass (policy=none) header.from=posteo.de; 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: -0.71 X-TUID: qU/68IbHVKU2 Hello everyone, I am trying to get more serious about Guix, and I have a few questions about how to develop Guix and the associated Git workflow. The manual in chapter 14.1 (Building from Git) explains most things pretty well. 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? 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? 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? Thank you in advance.