From: Jelle Licht <jlicht@fsfe.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26752@debbugs.gnu.org
Subject: bug#26752: Ansible & others' problems with wrapped '.ansible-real' scripts
Date: Thu, 22 Jun 2017 18:02:07 +0200 [thread overview]
Message-ID: <CAPsKtfJ8rZ86RZiayXuZbYfeEUroAubvCsgKxZJDdg17Oijrnw@mail.gmail.com> (raw)
In-Reply-To: <874lx2w926.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
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.
Thanks,
Jelle
2017-05-03 12:04 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:
> Jelle Licht <jlicht@fsfe.org> skribis:
>
> > I had some problems getting current ansible package to work. It seems
> that
> > the bin/ansible script which is created as part of the
> python-build-system
> > via a call to `wrap-program' interferes with certain expectations ansible
> > has regarding how it and its subcommands are called.
> >
> > This mechanism does not work well with our generated created
> .ansible-real.
> > See [1] for a similar issue that has since been worked around in the
> newest
> > version of ansible.
> >
> > For now, I have a similar workaround that add some guix-specific checks
> to
> > ansible looking for being called as .ansible-real, though I do consider
> > this a hack. This problem is indicative of a bigger issue: the fact that
> > wrap-program currently leads to subtle bugs for lots of scripts. There
> has
> > been some noise on #guix about solving this problem in general.
>
> For the record, the discussion is visible here:
> <https://gnunet.org/bot/log/guix/2017-05-02#T1370586>.
>
> I think it’s bad for a program to rely on argv[0], but I also think
> those .thing-real are kinda ugly. :-)
>
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 2163 bytes --]
next prev parent reply other threads:[~2017-06-22 16:03 UTC|newest]
Thread overview: 14+ 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 [this message]
2017-06-22 19:03 ` Ludovic Courtès
2019-02-04 7:50 ` Ricardo Wurmus
2019-02-04 7:50 ` [bug#29951] " Ricardo Wurmus
2019-02-04 18:05 ` Ludovic Courtès
2019-02-04 18:05 ` [bug#29951] " Ludovic Courtès
2019-02-06 22:14 ` Ludovic Courtès
2019-02-06 22:14 ` [bug#29951] " 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPsKtfJ8rZ86RZiayXuZbYfeEUroAubvCsgKxZJDdg17Oijrnw@mail.gmail.com \
--to=jlicht@fsfe.org \
--cc=26752@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.