From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Lemmer Webber Subject: Re: "guix deploy" is in git master Date: Sun, 07 Jul 2019 02:55:44 -0400 Message-ID: <87zhlqcozz.fsf@dustycloud.org> References: <87a7drn0ux.fsf@dustycloud.org> <874l3zse7o.fsf@elephly.net> <87muhrfkiz.fsf@sdf.lonestar.org> <87y31bjz3i.fsf@dustycloud.org> <87zhlrjcww.fsf@elephly.net> <87zhlq7ldu.fsf@netris.org> <87y31ajn2x.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50270) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hk5ls-0001rz-9d for guix-devel@gnu.org; Sun, 07 Jul 2019 07:55:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hk5lr-0008CG-2m for guix-devel@gnu.org; Sun, 07 Jul 2019 07:55:56 -0400 Received: from dustycloud.org ([50.116.34.160]:54090) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hk5lo-00089F-E0 for guix-devel@gnu.org; Sun, 07 Jul 2019 07:55:53 -0400 In-reply-to: <87y31ajn2x.fsf@elephly.net> 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" To: Ricardo Wurmus Cc: guix-devel@gnu.org Ricardo Wurmus writes: > Hi Mark, > >> Ricardo Wurmus writes: >> >>> Christopher Lemmer Webber writes: >>> >>>> Ricardo, can you see if 834b8a4110 fixes the problem? >>> >>> It does not seem to fix this problem. >>> =E2=80=9Cgnu/machine/ssh.scm=E2=80=9D still isn=E2=80=99t included. >> >> The problem is that (guix self) has its own logic, independent of the >> *.am files, to determine the set of modules to be compiled and >> installed. That logic needs to be updated when adding a new module >> directory. >> >> I just pushed commit 079c93e1c1dd93639417095000d5e56d8db62d61, which >> should hopefully fix the problem. > > Thank you, this fixes it. Yes, thank you so much Mark! :)