ansible @1.9.4.1 Git clone failed - SSL certificate problem: Couldn't understand the server certificate format

[breun (Nils Breunese)]

Running sudo port install ansible on my OS X 10.11.3 installation fails with the following lines in the log:

:info:fetch fatal: unable to access 'https://github.com/ansible/ansible.git/': SSL certificate problem: Couldn't understand the server certificate format
:info:fetch Command failed: /usr/bin/git clone -q https://github.com/ansible/ansible.git /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_ansible/ansible/work/ansible-1.9.4-1 2>&1
:info:fetch Exit code: 128
:error:fetch org.macports.fetch for port ansible returned: Git clone failed
:debug:fetch Error code: NONE
:debug:fetch Backtrace: Git clone failed
    while executing
"gitfetch"
    (procedure "portfetch::fetch_main" line 14)
    invoked from within
"portfetch::fetch_main org.macports.fetch"
    ("eval" body line 1)
    invoked from within
"eval $procedure $targetname"

[breun (Nils Breunese)]

Running git clone ​​https://github.com/ansible/ansible.git/ in my terminal works fine by the way.

Also, does the full repository need to be cloned? The release tarball for 1.9.4.1 is just 977 KB, while the Git repository currently comes in at 37.53 MiB.

[adfernandes (Andrew Fernandes)]

I don't know about the SSL certificate problem; that sounds like a git/github issue.

Regarding the release tarball, there is a long-standing issue with ansible that the release tarball actually doesn't work properly because it is missing submodules. This was covered in-depth in one of the ansible issues on GitHub.

So the short answer is that yes, you really do need to clone the entire repo because of the large number of submodules that are required.

[ryandesign (Ryan Carsten Schmidt)]

It looks like as of ansible 2.0.0.1 they are using the GitHub Releases service to offer a properly-made source tarball:

​https://github.com/ansible/ansible/releases

So the port could switch to that (using github.tarball_from releases).

[adfernandes (Andrew Fernandes)]

Replying to ryandesign@…:

It looks like as of ansible 2.0.0.1 they are using the GitHub Releases service to offer a properly-made source tarball:

​https://github.com/ansible/ansible/releases

So the port could switch to that (using github.tarball_from releases).

I'm working on the update now; the official online docs still say to install from git clone --recursive, so I'm going to keep with that. I spent too long trying trusting ansible's "just use the source tarball" in the past to trust their release process.

[adfernandes (Andrew Fernandes)]

With respect to the original subject of this ticket, works for me across multiple locations and hosts.

Updating to 2.0.0.2-1 in r145208.