[Bug 202799] sysutils/ansible: SHEBANG_FILES breaks ansible_python_interpreter and makes it impossible to manage non-freebsd hosts

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Aug 31 20:49:26 UTC 2015


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202799

            Bug ID: 202799
           Summary: sysutils/ansible: SHEBANG_FILES breaks
                    ansible_python_interpreter and makes it impossible to
                    manage non-freebsd hosts
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: merlin at merlinsbox.net
                CC: lifanov at mail.lifanov.com
             Flags: maintainer-feedback?(lifanov at mail.lifanov.com)
                CC: lifanov at mail.lifanov.com

The recent change to the port Makefile adding shebangfix and SHEBANG_FILES has
broken ansible.  According to the ansible developers, ansible modules must use
the shebang line "#!/usr/bin/python" because that is what it looks for in order
to replace when ansible_python_interpreter is overridden.

Since this change, I was unable to manage linux hosts from my freebsd machine. 
In order to fix it, I had to rebuild the port with the following diff of the
Makefile:

/usr/ports/sysutils/ansible # diff Makefile Makefile.fixed
24,28c24,25
< SHEBANG_FILES=        lib/ansible/runner/action_plugins/synchronize.py \
<               lib/ansible/modules/core/*/*.py \
<               lib/ansible/modules/core/*/*/*.py \
<               lib/ansible/modules/extras/*/*.py \
<               lib/ansible/modules/extras/*/*/*.py
---
> SHEBANG_FILES=        lib/ansible/runner/action_plugins/synchronize.py
> 

As per discussion with upstream developers, all shebang lines in modules should
NOT be fixed.  This did indeed re-enable the use of ansible_python_interpreter
which allowed my linux hosts to be managed again.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list