From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id yEulCrYscmXBRQEA9RJhRA:P1 (envelope-from ) for ; Thu, 07 Dec 2023 21:36:06 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id yEulCrYscmXBRQEA9RJhRA (envelope-from ) for ; Thu, 07 Dec 2023 21:36:06 +0100 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 B4D5D4592A for ; Thu, 7 Dec 2023 21:36:05 +0100 (CET) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=disroot.org header.s=mail header.b=GKlvjAS7; dmarc=pass (policy=reject) header.from=disroot.org; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1701981365; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=RTDE2i47AWTCQ4kU0Z/wvtf1TCQC9Ax3lw7E8rmszz0=; b=SP5iO6MaE1Cb1IUks8WuG/kvgIRISZK4DPx+6nKpfjpLnmneIbFvZqucHzfaCxGGhwVGIC Zt+EtyaBQUl5bwyp+Vf2rKEqw1UWD4rsaevfkbF9U2WerkIiE8t/wIqwB5OkSqDNaOZMgD YJ1+c/ITFLWZtVigh0MLr85kBpMCcyX7kuk0OwG0K1Zo0fwTYL6EdcREj8JQnWfS50dZ7t m1PoDLapJie0czFlINo4XGKJerOj5XVxQnt00sdVW2cdZW1kf98W0B3dxOPRLzh1Ez4Jhx Y4MBvu0cEs2b6/M2yx2QUCRV6qLwuyCDfmZt0rd/OAPrCxJ8AuHucsjIIJppvA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1701981365; a=rsa-sha256; cv=none; b=BwnnoKXjI3sye/yZEQ/OrvyVcGRTuyxj57KhfmZlF3Kct3IVyz2lvfbFXo/AHn/TZGa12o bfjmoNaqSHTxeyfIUy3bOk9OGWDhjm7Rj8fanTDVscCZpq19HetomkwREu8MaNIIbl/mE+ VNKgq1kXQuPeVEFy1DOhnc5FygWNHVCHRmM/fXe43Vs2cYmSN6WaNdQwPCN1Ja27xNW8TD wwYzgiy7lB39XvT+1glMkMuNmisrIHxT5k4lS0kaAm53zeif+d6LrG6sgzex1XIv7vtJgc tgBddUuGP10mjoSw7hVInAB6v298rt4SLHSZeDmI3BzPMYEvUECkZR4EMNbyIw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=disroot.org header.s=mail header.b=GKlvjAS7; dmarc=pass (policy=reject) header.from=disroot.org; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rBL5v-0004r0-9x; Thu, 07 Dec 2023 15:35:39 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rBL5s-0004qR-Dh for help-guix@gnu.org; Thu, 07 Dec 2023 15:35:36 -0500 Received: from layka.disroot.org ([178.21.23.139]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rBL5o-0003JB-L2 for help-guix@gnu.org; Thu, 07 Dec 2023 15:35:36 -0500 Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 979164195C; Thu, 7 Dec 2023 21:35:23 +0100 (CET) X-Virus-Scanned: SPAM Filter at disroot.org Received: from layka.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDb_Mui7ZoAR; Thu, 7 Dec 2023 21:35:21 +0100 (CET) References: <87zfyuit2g.fsf@disroot.org> <20231201141224.6169bfea.koszko@koszko.org> <87sf4liww5.fsf@disroot.org> <20231201210717.0d3d8ec4.koszko@koszko.org> <87zfyor03l.fsf@disroot.org> <20231205202834.05ce97e3.koszko@koszko.org> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1701981321; bh=ybh2mOQY36YOVEgON2i4J6dgJ8XhkQ7B4IaOKIuoMS4=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=GKlvjAS78hcpltB/IU2LKnkN7yCqXNb6sMMXe9j4Om3dqqJrLMIth8vCR0K9xeHP2 KgONuz90xgOVepfBNS/DTZkY+0vOoS55isQw/OsJEn1wyyCpmeT8FxJVSPA7IHf2It kYhe2CffjWRHjrsmYvtVhXOJDB3oY5C/liSnLXZyrMet3EWxwu8/n72q7VxS9fG++i g++KCoZHBLFUe1edpkld8gD7PyvGIaHcFnaIk5pMfH4jEZyV5dR0fCaTzOL4IQUZFd l1aKHDTvSaFP+77+uPX31J9MetyQUJgzI+IIJy/goXBt+u8mGlUtaFsd9ssfI/jap1 gzBci0IJlWl8Q== From: Mauritz Stenek To: Wojtek Kosior Cc: help-guix@gnu.org Subject: Re: SSH error guix pull Date: Thu, 07 Dec 2023 14:33:18 -0600 In-reply-to: <20231205202834.05ce97e3.koszko@koszko.org> Message-ID: <87zfyl3g55.fsf@disroot.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=178.21.23.139; envelope-from=mstenek@disroot.org; helo=layka.disroot.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx11.migadu.com X-Migadu-Spam-Score: -9.42 X-Spam-Score: -9.42 X-Migadu-Queue-Id: B4D5D4592A X-TUID: G6ANNFvSFS/b On 2023-12-05 at 13:28, Wojtek Kosior wrote: > [[PGP Signed Part:Undecided]] >> Thanks Wojtek for your kind help (my comments below). >>=20 >> Status update: I got it running! > > Great to hear that :) > >> [...] >>=20 >> and that's it: the setup that works. >>=20 >> However, The error `guix pull` ssh error only goes away after I=20 >> ssh to a remote computer: `$ ssh root@repo.local`; this command=20 >> somehow triggers something that makes `git pull` work. Odd. > > Hmm. Since the SSH agent remembers SSH key password, it'd make=20 > sense > that one has to first "unlock" a key in an interactive CLI=20 > session > before Guix can use it non-interactively. If this also happens=20 > with > passwordless keys, then it's indeed odd. Nevertheless, I guess=20 > a > hypothetical solution would be to allow Guix to =E2=80=94 when desired = =E2=80=94=20 > call > SSH with access to its TTY/PTY :) Would you mind showing me how? Thanks Wojtek. > > Best > Wojtek > > > -- (sig_start) > website: https://koszko.org/koszko.html > fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A > follow me on Fediverse:=20 > https://friendica.me/profile/koszko/profile > > =E2=99=A5 R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ=3D=3D | =C3=B7=20 > c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ=3D=3D > =E2=9C=9D YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ=3D=3D | ?=20 > U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=3D > -- (sig_end) > > > On Tue, 05 Dec 2023 11:44:57 -0600 Mauritz Stenek=20 > wrote: > >> Thanks Wojtek for your kind help (my comments below). >>=20 >> Status update: I got it running! >>=20 >> Perhaps I should clarify that I'm running a very light setup --=20 >> Desktop services with dwm (I tried to go even leaner, but I=20 >> couldn't get the xorg server to work w/o a login manager); I'm=20 >> unsure if this is affecting the ssh setup. >>=20 >> This is what I did (the superflouos commented lines show my=20 >> tweaks=20 >> to the doc's suggestion[1]): >>=20 >> (1) I created an ssh agent -- as per the shepherd docs[1] with=20 >> some tweaks. I added the `&` to the recommended bash setup to=20 >> send=20 >> the job to the background: >>=20 >> ``` >> if [[ ! -S ${XDG_RUNTIME_DIR-$HOME/.cache}/shepherd/socket ]];=20 >> then >> shepherd & >> fi >> ``` >>=20 >> (2) I commented out `(shepherd service)` import and the=20 >> `(perform-service-action 'shepherd 'daemonize)` expression in=20 >> the=20 >> `init.scm` file: >>=20 >> ``` >> (use-modules ;; (shepherd service) >> ((ice-9 ftw) #:select (scandir))) >>=20 >> ;; Send shepherd into the background >> ;; (perform-service-action 'shepherd 'daemonize) >>=20 >> ;; Load all the files in the directory 'init.d' with a suffix=20 >> '.scm'. >> (for-each >> (lambda (file) >> (load (string-append "init.d/" file))) >> (scandir (string-append (dirname (current-filename))=20 >> "/init.d") >> (lambda (file) >> (string-suffix? ".scm" file)))) >> ``` >>=20 >> (3): I removed the conditional export of the auth sock varible=20 >> in=20 >> the `.bash_profile` file: >>=20 >> ``` >> #if [[ ! -n ${SSH_CONNECTION} ]]; then >> SSH_AUTH_SOCK=3D${XDG_RUNTIME_DIR-$HOME/.cache}/ssh-agent/socket >> export SSH_AUTH_SOCK >> #fi >> ``` >>=20 >> and that's it: the setup that works. >>=20 >> However, The error `guix pull` ssh error only goes away after I=20 >> ssh to a remote computer: `$ ssh root@repo.local`; this command=20 >> somehow triggers something that makes `git pull` work. Odd. >>=20 >>=20 >> [1]:=20 >> https://www.gnu.org/software/shepherd/manual/html_node/Managing-User-Ser= vices.html >>=20 >> On 2023-12-01 at 14:07, Wojtek Kosior =20 >> wrote: >>=20 >> > [[PGP Signed Part:Undecided]]=20=20 >> >> Starting service root... >> >> Service root started. >> >> Service root running with value #t. >> >> Service root has been started. >> >> Uncaught exception while loading configuration file=20 >> >> '/home/mst/.config/shepherd/init.scm': (goops-error #f "No=20 >> >> applicable method for ~S in call ~S" (#<=20 >> >> service-actions=20=20=20 >> >> (1)> (service-actions shepherd)) ())=20=20=20=20 >> >> ``` >> >>=20 >> >> which I don't know how to fix.=20=20 >> > >> > I see=E2=80=A6 I've never been using shepherd alone, in separation=20 >> > from=20 >> > Guix >> > but I see that my Guix-generated user shepherd config has=20 >> > this >> > >> > --8<---------------cut=20 >> > here---------------start------------->8--- >> > (action 'root 'daemonize) >> > --8<---------------cut=20 >> > here---------------end--------------->8--- >> > >> > >> > while the example you linked to uses >> > >> > --8<---------------cut=20 >> > here---------------end--------------->8--- >> > (perform-service-action 'shepherd 'daemonize) >> > --8<---------------cut=20 >> > here---------------start------------->8--- >> > >> > >> > Anyway, if there's no strong reason for not using Guix home,=20 >> > I'd=20 >> > suggest >> > using it. I mean the `guix home` command and its=20 >> > subcommands.=20 >> > It >> > handles =E2=80=94 among others =E2=80=94 shepherd configuration. The = link I=20 >> > gave >> > earlier was about using SSH through Guix home.=20=20 >>=20 >> Yes, I still need to explore Guix Home -- baby steps. >>=20 >> >> > Btw, there's perhaps another solution =E2=80=94 pull from local=20 >> >> > git=20 >> >> > checkout. >> >> > You can pass a filesystem path instead of a url when=20 >> >> > running=20 >> >> > `guix >> >> > pull`. This might later cause some issues if you try to=20 >> >> > `sudo=20 >> >> > guix >> >> > system reconfigure` but that's another topic=E2=80=A6=20=20=20=20 >> >>=20 >> >> I was able to install a package like this but it's not=20 >> >> ideal.=20=20 >> > >> > You can also set serve a cloneable git repo over HTTP on=20 >> > localhost=E2=80=A6 >> > Here's a sample script for this that I happen to have written=20 >> > for my own >> > purposes just today ;) >> > >> > --8<---------------cut=20 >> > here---------------start------------->8--- >> > #!/usr/bin/env -S guix repl -- >> > !# >> > >> > ;; SPDX-License-Identifier: CC0-1.0 >> > >> > ;; Copyright (C) 2023 Wojtek Kosior >> > ;; >> > ;; Available under the terms of Creative Commons Zero v1.0=20 >> > Universal. >> > >> > (use-modules ((guix gexp) #:select >> > (gexp file-append mixed-text-file program-file=20 >> > lower-object)) >> > ((gnu packages version-control) #:select (git)) >> > ((gnu packages web) #:select (lighttpd)) >> > ((guix store) #:select (run-with-store=20 >> > with-store=20 >> > %store-monad)) >> > ((guix monads) #:select (mlet mbegin return)) >> > ((guix derivations) #:select >> > (built-derivations derivation-output-path=20 >> > derivation-outputs))) >> > >> > (define here >> > (dirname (current-filename))) >> > >> > (define git-http-backend >> > (file-append git "/libexec/git-core/git-http-backend")) >> > >> > (define lighttpd-config >> > (mixed-text-file "lighttpd.conf" >> > "\ >> > server.document-root =3D \"/dev/null\" >> > server.modules =3D ( \"mod_alias\", \"mod_cgi\",=20 >> > \"mod_setenv\") >> > server.port =3D 8098 >> > >> > alias.url =3D ( \"/guix\" =3D> \"" git-http-backend "\" ) >> > cgi.assign =3D (\"\" =3D> \"\") >> > >> > setenv.add-environment =3D ( >> > \"GIT_PROJECT_ROOT\" =3D> \"" here "\" + \"/.git\", >> > \"GIT_HTTP_EXPORT_ALL\" =3D> \"\" >> > ) >> > ")) >> > >> > (define run-lighttpd-guix-repo-server >> > (program-file "run-lighttpd-guix-repo-server" >> > #~(system* #$(file-append lighttpd=20 >> > "/sbin/lighttpd") "-D" >> > "-f" #$lighttpd-config))) >> > >> > (system* >> > (with-store store >> > (run-with-store store >> > (mlet %store-monad ((script-drv (lower-object >> > run-lighttpd-guix-repo-server))) >> > (mbegin %current-monad >> > (built-derivations (list script-drv)) >> > (return (derivation-output-path >> > (assoc-ref (derivation-outputs script-drv)=20 >> > "out")))))))) >> > --8<---------------cut=20 >> > here---------------end--------------->8--- >> > >> > >> > One can write it as, say, "serve-git-repo.scm" in a git=20 >> > project >> > checkout (possibly also listing it in `.git/info/exclude` to=20 >> > have git >> > ignore it). Then `chmod +x` it and run =E2=80=94 if all goes OK, it=20 >> > should >> > serve the repo at: http://localhost:8098/guix >> > >> > It's then possible to do e.g. >> > >> > --8<---------------cut=20 >> > here---------------start------------->8--- >> > guix pull --url=3Dhttp://localhost:8098/guix >> > --8<---------------cut=20 >> > here---------------end--------------->8--- >> > >> > The benefit is that the aforementioned `guix system=20 >> > reconfigure`=20 >> > seems >> > to work afterwards (although the local git repo server needs=20 >> > to=20 >> > be >> > running during this time). >> > >> > Voila! We no longer need to rely on remote git servers=20 >> > availability :) >> > It'd make sense to also spawn this HTTP server through=20 >> > shepherd. >> > And to generalize it to be able to serve multiple repos at=20 >> > once=20 >> > =E2=80=94 for >> > example a custom Guix tree, a channel other than "guix" and=20 >> > some >> > software projects=20=20 >>=20 >> Cool! I will definitely give this a try! >>=20 >>=20 >> > >> > Best >> > Wojtek >> > >> > >> > -- (sig_start) >> > website: https://koszko.org/koszko.html >> > fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79=20 >> > FD1A >> > follow me on Fediverse:=20 >> > https://friendica.me/profile/koszko/profile >> > >> > =E2=99=A5 R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ=3D=3D | =C3=B7=20 >> > c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ=3D=3D >> > =E2=9C=9D YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ=3D=3D | ?=20 >> > U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=3D >> > -- (sig_end) >> > >> > >> > On Fri, 01 Dec 2023 12:37:58 -0600 Mauritz Stenek=20 >> > wrote: >> >=20=20 >> >> On 2023-12-01 at 07:12, Wojtek Kosior =20 >> >> wrote: >> >>=20=20=20 >> >> > [[PGP Signed Part:Undecided]] >> >> > Hi >> >> >=20=20=20=20 >> >> >> However, on a full Guix system I keep getting this error: >> >> >>=20 >> >> >> ``` >> >> >> guix pull: error: Git error: error authenticating: no=20 >> >> >> auth=20 >> >> >> sock=20 >> >> >> variable >> >> >> ``` >> >> >>=20 >> >> >> and, for the life of me, I just can't get it to work.=20=20=20=20 >> >> > >> >> > Maybe you're not running ssh user agent daemon under your=20 >> >> > user?=20 >> >> > You >> >> > need it for this to work. >> >> > >> >> > You can probably spawn it in a number of ways. One of=20 >> >> > them=20 >> >> > would be >> >> > through Guix home. See this[1] Guix manual node for info=20 >> >> > about >> >> > ssh-agent's home service :) >> >> > >> >> > Also, you're not running `guix pull` with sudo, are you?=20 >> >> > It=20 >> >> > wouldn't >> >> > work this way because sudo erases environment variables,=20 >> >> > including >> >> > "SSH_AUTH_SOCK". >> >> > >> >> > Btw, on my fully Guixified laptop I am using Guix home=20 >> >> > without >> >> > ssh-agent configured and yet I do have ssh-agent running=20 >> >> > under=20 >> >> > my user. >> >> > I'm not sure what started it=E2=80=A6=20=20=20=20 >> >>=20 >> >> Seems like that is the situation. I actually tried to run=20 >> >> the=20 >> >> ssh-agent user service example in the shepherd manual=20 >> >> (https://www.gnu.org/software/shepherd/manual/html_node/Managing-User= -Services.html)=20 >> >> -- verbatim -- and I get this error: >> >>=20 >> >> ``` >> >> Starting service root... >> >> Service root started. >> >> Service root running with value #t. >> >> Service root has been started. >> >> Uncaught exception while loading configuration file=20 >> >> '/home/mst/.config/shepherd/init.scm': (goops-error #f "No=20 >> >> applicable method for ~S in call ~S" (#<=20 >> >> service-actions=20=20=20 >> >> (1)> (service-actions shepherd)) ())=20=20=20=20 >> >> ``` >> >>=20 >> >> which I don't know how to fix. >> >>=20 >> >> Other than that example, I'm at a loss with ssh. >> >>=20=20=20 >> >> >=20=20=20=20 >> >> >> (disclaimer: I'm a total scheme/guile neophyte -- and am=20 >> >> >> learning=20 >> >> >> as I go)=20=20=20=20 >> >> > >> >> > As all of us, haha :D=20=20=20=20 >> >>=20 >> >> :D >> >>=20=20=20 >> >> > >> >> > Btw, there's perhaps another solution =E2=80=94 pull from local=20 >> >> > git=20 >> >> > checkout. >> >> > You can pass a filesystem path instead of a url when=20 >> >> > running=20 >> >> > `guix >> >> > pull`. This might later cause some issues if you try to=20 >> >> > `sudo=20 >> >> > guix >> >> > system reconfigure` but that's another topic=E2=80=A6=20=20=20=20 >> >>=20 >> >> I was able to install a package like this but it's not=20 >> >> ideal. >> >>=20=20=20 >> >> > Good luck and happy hacking!=20=20=20=20 >> >>=20 >> >> Thanks! I can tell you, it is a journey. >> >>=20=20=20 >> >> > Wojtek >> >> > >> >> > [1]=20 >> >> > https://guix.gnu.org/manual/devel/en/html_node/Secure-Shell.html >> >> > >> >> > >> >> > -- (sig_start) >> >> > website: https://koszko.org/koszko.html >> >> > fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79=20 >> >> > FD1A >> >> > follow me on Fediverse:=20 >> >> > https://friendica.me/profile/koszko/profile >> >> > >> >> > =E2=99=A5 R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ=3D=3D | =C3=B7=20 >> >> > c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ=3D=3D >> >> > =E2=9C=9D YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ=3D=3D | ?=20 >> >> > U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=3D >> >> > -- (sig_end) >> >> > >> >> > >> >> > On Thu, 30 Nov 2023 19:47:43 -0600 Mauritz Stenek=20 >> >> > wrote: >> >> >=20=20=20=20 >> >> >> I'm trying out Guix and created a personal (private)=20 >> >> >> channel=20 >> >> >> with=20 >> >> >> some custom packages. I access my git repo with ssh. >> >> >>=20 >> >> >> Using Guix on a foreign distro, pulling from my git repo=20 >> >> >> works=20 >> >> >> fine after applying this strategy:=20 >> >> >> https://issues.guix.gnu.org/31285. >> >> >>=20 >> >> >> However, on a full Guix system I keep getting this error: >> >> >>=20 >> >> >> ``` >> >> >> guix pull: error: Git error: error authenticating: no=20 >> >> >> auth=20 >> >> >> sock=20 >> >> >> variable >> >> >> ``` >> >> >>=20 >> >> >> and, for the life of me, I just can't get it to work. >> >> >>=20 >> >> >> (disclaimer: I'm a total scheme/guile neophyte -- and am=20 >> >> >> learning=20 >> >> >> as I go) >> >> >>=20 >> >> >> Please help. >> >> >>=20=20=20=20=20 >> >> > >> >> > [[End of PGP Signed Part]]=20=20=20=20 >> >>=20 >> >>=20=20=20 >> > >> > [[End of PGP Signed Part]]=20=20 >>=20 >>=20 > > [[End of PGP Signed Part]] --=20 Mauritz Stenek