From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Jelle Licht <jlicht@fsfe.org>,
26752@debbugs.gnu.org, 29951@debbugs.gnu.org
Subject: bug#26752: Ansible & others' problems with wrapped '.ansible-real' scripts
Date: Wed, 06 Feb 2019 23:14:04 +0100 [thread overview]
Message-ID: <87lg2s5zv7.fsf@gnu.org> (raw)
In-Reply-To: <87tvhkhu15.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 04 Feb 2019 08:50:14 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>> Jelle Licht <jlicht@fsfe.org> skribis:
>>
>>> The current ansible package is still brokenin the same way.
>>>
>>> Is there already an acceptable way of working around this problem?
>>> Otherwise I could send my (extremely hacky) workaround that adds a specific
>>> condition in the ansible source code to check for .ansible-real.
>>
>> For now I think we have to go with the hack. Make sure to add a comment
>> linking to this bug report.
>
> There is a way to get around this. It’s presented in #29951:
>
> https://issues.guix.info/issue/29951
BTW, there’s also this patch series on this topic:
https://issues.guix.info/issue/27003
What to do?
Ludo’.
next prev parent reply other threads:[~2019-02-06 22:15 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 [this message]
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
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=87lg2s5zv7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26752@debbugs.gnu.org \
--cc=29951@debbugs.gnu.org \
--cc=jlicht@fsfe.org \
--cc=rekado@elephly.net \
/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).