Current ansible-9999.ebuild has two issues: 1. It fails at compile stage due to missing files (upstream changed the way to generate man pages): * The specific snippet of code: * a2x -f manpage docs/man/man1/${_man}.1.asciidoc.in || die "Failed generating man page (${_man})"; a2x: ERROR: missing SOURCE_FILE: docs/man/man1/ansible.1.asciidoc.in 2. Fails with the following error at install stage (after removing man pages related code from ebuild): ... reading manifest template 'MANIFEST.in' /usr/lib64/python2.7/distutils/filelist.py:61: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal ... UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 24: ordinal not in range(128) Propose new ebuild to resolve above issues and: - bump EAPI to 6 (EXAMPLES rewritten with dodoc) - add python3.5 support (https://docs.ansible.com/ansible/python_3_support.html) - add support for tests (with patch to handle correctly portage custom $HOME environment) Reproducible: Always Steps to Reproduce: 1.emerge app-admin/ansible
Created attachment 471718 [details] ansible-9999.ebuild Proposed ebuild
Created attachment 471950 [details, diff] ansible-9999.ebuild.patch Please always supply your changes as a unified diff.
it's my understanding that ansible still doesn't work with python3 at all (they are slowly working on it), so not applying that piece. There were also spacing issues in the patch (spaces instead of tabs), there were also windows line endings everywhere. A 9999 version cannot be keyworded, so I have removed those again.
Hi Matthew (In reply to Matthew Thode ( prometheanfire ) from comment #3) > it's my understanding that ansible still doesn't work with python3 at all > (they are slowly working on it), so not applying that piece. > That's not *quite* true. See https://docs.ansible.com/ansible/dev_guide/developing_python3.html and https://docs.ansible.com/ansible/python_3_support.html. If you set up a virtualenv and install Ansible using pip and Python 3, it does work. I have successfully done it numerous times. You can try for yourself.
Ebuild version 9999, or live ebuild, in my understanding introduced long time ago specially for extreme bleeding edge policy. Python3 support in ansible perfectly fits this policy. Ansible does not produce errors on install with python3 and majority of core features work. $ ansible --version ansible 2.4.0 config file = /home/lik/.ansible.cfg configured module search path = ['/home/lik/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib64/python3.5/site-packages/ansible executable location = /usr/lib/python-exec/python3.5/ansible python version = 3.5.3 (default, Mar 9 2017, 00:05:11) [GCC 5.4.0] $ ansible localhost -m setup -a 'filter=ansible_lsb' -o 127.0.0.1 | SUCCESS => {"ansible_facts": {"ansible_lsb": {"codename": "n/a","description": "Gentoo Base System release 2.3","id": "Gentoo","major_release": "2","release": "2.3"}},"changed": false} What are the next steps for revising support for python3 in ansible-9999.ebuild?
fair enough, adding python3_5
