unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenny Ballou <kballou@devnulllabs.io>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 32320@debbugs.gnu.org
Subject: [bug#32320] [PATCH] gnu: ansible: update to 2.5.7
Date: Wed, 01 Aug 2018 09:00:38 -0600	[thread overview]
Message-ID: <87zhy6uo6h.fsf@devnulllabs.io> (raw)
In-Reply-To: <878t5qp3ey.fsf@gmail.com>


On 2018年08月01日 14:28 GMT, Oleg Pykhalov wrote:
> Hello,
>
> Kenny Ballou <kballou@devnulllabs.io> writes:
>
>> Update ansible to the latest 2.5.x release.  This also removes the
>> Python 2 only support for Ansible as this is now stable in the 2.5.x
>> line of Ansible.
>
> […]
>
> Builded fine on my machine.
>
>
> Could I ask how do you use ansible-COMMAND commands?
>
> E.g. ‘ansible-galaxy’ outputs that it really runs ‘.ansible-real’ and
> prints the manual page of ‘ansible’ command for me.
>
> Thanks,
> Oleg.

Oleg,

This appears to be a known bug in how Python packages are using
`.command.real` wrappers.  See Bug #26752, "Ansible & others' problems
with wrapped '.ansible.real' scripts":
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26752 and
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31299.

This patch only attempts to update the version of ansible and its
dependencies.  It's possible that the patch is created against the wrong
branch and therefore doesn't include any changes that would fix this
behaviour.  As it is today, the current version of ansible on `master`
exhibits the same behaviour.

Unfortunately, I personally don't have a work around in place for this
yet.

Regards,
-Kenny

  reply	other threads:[~2018-08-01 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 19:17 [bug#32320] [PATCH] gnu: ansible: update to 2.5.7 Kenny Ballou
2018-08-01 14:28 ` Oleg Pykhalov
2018-08-01 15:00   ` Kenny Ballou [this message]
2018-08-13 15:28 ` bug#32320: " Leo Famulari

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=87zhy6uo6h.fsf@devnulllabs.io \
    --to=kballou@devnulllabs.io \
    --cc=32320@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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).