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: Thu, 22 Jun 2017 18:02:07 +0200 Message-ID: References: <874lx2w926.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c0b080048d08705528e9be3" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dO4ZV-0006kO-DF for bug-guix@gnu.org; Thu, 22 Jun 2017 12:03:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dO4ZS-0002ir-98 for bug-guix@gnu.org; Thu, 22 Jun 2017 12:03:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58893) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dO4ZS-0002iP-6L for bug-guix@gnu.org; Thu, 22 Jun 2017 12:03:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dO4ZR-0008ES-RP for bug-guix@gnu.org; Thu, 22 Jun 2017 12:03:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <874lx2w926.fsf@gnu.org> 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.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 26752@debbugs.gnu.org --94eb2c0b080048d08705528e9be3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=C3=A8s : > Jelle Licht 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 ansib= le > > 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 tha= t > > 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: > . > > I think it=E2=80=99s bad for a program to rely on argv[0], but I also thi= nk > those .thing-real are kinda ugly. :-) > > Ludo=E2=80=99. > --94eb2c0b080048d08705528e9be3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The current ansible package = is still brokenin the same way.

Is there already an acce= ptable 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=C3=A8s <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-sy= stem
> 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 n= ewest
> version of ansible.
>
> For now, I have a similar workaround that add some guix-specific check= s to
> ansible looking for being called as .ansible-real, though I do conside= r
> this a hack. This problem is indicative of a bigger issue: the fact th= at
> 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=E2=80=99s bad for a program to rely on argv[0], but I also think=
those .thing-real are kinda ugly.=C2=A0 :-)

Ludo=E2=80=99.

--94eb2c0b080048d08705528e9be3--