From: Jelle Licht <jlicht@fsfe.org>
To: Brice Waegeneire <brice@waegenei.re>, 26752@debbugs.gnu.org
Subject: bug#26752: Ansible & others' problems with wrapped '.ansible-real' scripts
Date: Sat, 21 Mar 2020 22:45:27 +0100 [thread overview]
Message-ID: <87mu89bcw8.fsf@jlicht.xyz> (raw)
In-Reply-To: <507e6445fa33cdf78510af1c0fbda307@waegenei.re>
Hi
Brice Waegeneire <brice@waegenei.re> writes:
> Hello,
>
> Arun Isaac <arunisaac@systemreboot.net> 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
prev parent reply other threads:[~2020-03-21 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 20:08 bug#26752: Ansible & others' problems with wrapped '.ansible-real' scripts Jelle Licht
2017-05-03 10:04 ` Ludovic Courtès
2017-06-22 16:02 ` Jelle Licht
2017-06-22 19:03 ` Ludovic Courtès
2019-02-04 7:50 ` Ricardo Wurmus
2019-02-04 18:05 ` Ludovic Courtès
2019-02-06 22:14 ` Ludovic Courtès
2019-02-04 10:32 ` Arun Isaac
2018-05-07 17:25 ` Danny Milosavljevic
2020-03-21 20:25 ` Brice Waegeneire
2020-03-21 21:45 ` Jelle Licht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu89bcw8.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--cc=26752@debbugs.gnu.org \
--cc=brice@waegenei.re \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).