From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jelle Licht Subject: bug#26752: Ansible & others' problems with wrapped '.ansible-real' scripts Date: Sat, 21 Mar 2020 22:45:27 +0100 Message-ID: <87mu89bcw8.fsf@jlicht.xyz> References: <507e6445fa33cdf78510af1c0fbda307@waegenei.re> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:55598) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jFlwT-0006u6-0j for bug-guix@gnu.org; Sat, 21 Mar 2020 17:46:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jFlwR-0007U5-VB for bug-guix@gnu.org; Sat, 21 Mar 2020 17:46:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42335) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jFlwR-0007Ts-S3 for bug-guix@gnu.org; Sat, 21 Mar 2020 17:46:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jFlwQ-0007bN-Gw for bug-guix@gnu.org; Sat, 21 Mar 2020 17:46:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <507e6445fa33cdf78510af1c0fbda307@waegenei.re> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Brice Waegeneire , 26752@debbugs.gnu.org Hi Brice Waegeneire writes: > Hello, > > Arun Isaac writes: >> FWIW, I fixed our ansible package in >> https://issues.guix.info/issue/33777 . This is not a general solution, >> but at least our ansible package works at the moment. > > If this bug is about ansible malfunctioning then it should be closed, > Arun fixed it in 01cb4d47570c38812492bbc331b7b818e1b69fbb. I've tested > it myself successfully with the command from the IRC report[0] (linked > in the merged issue[2]). > On the other hand If it's about fixing it with the new wrap-script from > Ricardo I can send a patch, but the derivation will need guile as a new > input. I would be okay with closing it, as ansible works fine right now. If the current solution is deemed too brittle, or if the intent behind the new wrap-script is that we use it everywhere we can, then not of course. - Jelle