From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?55m944GE54aK77yg55u45pKy6YGT?= Subject: Re: Guix on Android works, guix pull fails on guile-ssh build in the check phase Date: Sun, 13 May 2018 16:02:33 +0000 Message-ID: <3A1F69D1-E7F1-4CA3-883C-7FECA8169F37@sumou.com> References: <9D99F62D-95A3-4D1F-A960-A55AE3D0B36E@sumou.com> <87tvrce0dd.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38101) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fHtSQ-0003yh-5m for help-guix@gnu.org; Sun, 13 May 2018 12:02:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fHtSL-0007z8-9i for help-guix@gnu.org; Sun, 13 May 2018 12:02:46 -0400 Received: from mccarthy.hcoop.net ([69.90.123.73]:38323) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fHtSL-0007ya-5y for help-guix@gnu.org; Sun, 13 May 2018 12:02:41 -0400 Received: from [89.24.39.231] (helo=[10.1.10.1]) by mccarthy.hcoop.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1fHtSI-0000V8-Jw for help-guix@gnu.org; Sun, 13 May 2018 12:02:38 -0400 In-Reply-To: <87tvrce0dd.fsf@gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org On May 13, 2018 2:49:02 AM UTC, Chris Marusich wro= te: >If those failures occur on the latest version of guile-ssh, it might be >helpful to open a bug report upstream: > >https://github=2Ecom/artyom-poptsov/guile-ssh I filed it=E2=80=94thanks for notifying me of this, prior to that I only r= eported it to Artyom via email, as instructed by the failed build of guile-= ssh=2E He hasn't responded=2E=20 >How did you invoke "guix pull"? Based on your suggested plan of >attack, >it sounds like you modified the Guix source locally (on your Android >system), recompiled it, and then tried to use "guix pull" from that >newly built version=2E Something like that=2E Is that right? I didn't modify it in any way=E2=80=94it's run from the 0=2E14=2E0 armhf b= inary download=2E=20 What I wrote about=E2=80=94modifying it=E2=80=94I'm simply thinking about= =2E I would still hope the failure is fixed upstream as it shouldn't be fai= ling on guix rebuild=2E=20 The =E2=80=9Choops to jump through=E2=80=9D I was referring to are the set= up on Android side=E2=80=94you need to symlink /gnu and /var every reboot, = create /etc/resolv=2Econf etc=2E But no modifications to Guix per se are ne= cessary=E2=80=A6=20 >If you don't tell "guix pull" where to get the Guix source from, it >gets >the latest version from the Git repository hosted on Savannah=2E If it >does that, then it will use the package definitions from that version, >which means it won't use any of the local changes you made=2E I think >what you need to do, if you want to disable the guile-ssh tests, is >something more like this: > > guix pull --url=3Dfile:///path/to/your/custom/guix/repo > >You might also need to use the --commit or --branch options, as >described in the manual (see: "(guix) Invoking guix pull")=2E You might >not need to specify the "file://" prefix in the URL; I can't remember=2E > >If you invoke "guix pull" in this way, you are telling it to use the >version specified by what you have *committed* in your custom Guix >repo=2E >Make sure you commit the change that disables guile-ssh tests, or it >won't be included when "guix pull" fetches from the repo=2E > >If you do "guix pull" in this way, it should build the custom version >of >guile-ssh that you made which disables the tests=2E I haven't tried this >myself, though, so no guarantees! I hope it helps=2E Thanks for this guide=E2=80=94I'll try to experiment with it, if guile-ssh= doesn't get fixed soon=E2=80=A6=20 -- =E7=99=BD=E3=81=84=E7=86=8A=EF=BC=A0=E7=9B=B8=E6=92=B2=E9=81=93