Opened 10 years ago
Closed 10 years ago
#45704 closed defect (worksforme)
defect: git-flow install fails on Yosemite on git clone
Reported by: | george.cooper@… | Owned by: | gorticus (Jason Mitchell) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.2 |
Keywords: | Cc: | ||
Port: | git-flow |
Description (last modified by neverpanic (Clemens Lang))
running sudo port install git-flow gives me:
---> Computing dependencies for git-flow ---> Fetching archive for git-flow ---> Attempting to fetch git-flow-0.4.1_2.darwin_14.noarch.tbz2 from http://packages.macports.org/git-flow ---> Attempting to fetch git-flow-0.4.1_2.darwin_14.noarch.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/git-flow ---> Attempting to fetch git-flow-0.4.1_2.darwin_14.noarch.tbz2 from http://lil.fr.packages.macports.org/git-flow ---> Fetching distfiles for git-flow Error: org.macports.fetch for port git-flow returned: Git clone failed Please see the log file for port git-flow for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_git-flow/git-flow/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port git-flow failed
Log output:
:notice:fetch ---> Fetching distfiles for git-flow :debug:fetch Executing org.macports.fetch (git-flow) :debug:fetch Executing: /usr/bin/git clone -q https://github.com/nvie/gitflow.git /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_git-flow/git-flow/work/gitflow-0.4.1 2>&1 :info:fetch fatal: unable to access 'https://github.com/nvie/gitflow.git/': Unknown SSL protocol error in connection to github.com:-67674 :info:fetch Command failed: /usr/bin/git clone -q https://github.com/nvie/gitflow.git /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_git-flow/git-flow/work/gitflow-0.4.1 2>&1 :info:fetch Exit code: 128 :error:fetch org.macports.fetch for port git-flow 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" :info:fetch Warning: targets not executed for git-flow: org.macports.activate org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:fetch Please see the log file for port git-flow for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_git-flow/git-flow/main.log
If I attempt to clone the repo directly it's fine, so I don't believe this is a git or network configuration issue on my end.
Change History (8)
comment:1 Changed 10 years ago by neverpanic (Clemens Lang)
Description: | modified (diff) |
---|---|
Keywords: | git-flow removed |
Owner: | changed from macports-tickets@… to jason-macports@… |
comment:2 Changed 10 years ago by gorticus (Jason Mitchell)
Works for me on Yosemite, w/
$ /usr/bin/git --version git version 1.9.3 (Apple Git-50)
What's the OS version, Xcode version, etc.?
Have you tried ticket:42063#comment:8? Of course, it requires you to install Macports git
first.
comment:3 Changed 10 years ago by george.cooper@…
/Applications/Xcode.app/Contents/Developer/usr/bin/git: /usr/lib/libpcre.0.dylib (compatibility version 1.0.0, current version 1.1.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5) /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)
xcodebuild -version: Xcode 6.1 Build version 6A1052d
And Yosemite Build 14A389
What file do I edit to set git_path? I don't have the one referenced in the other ticket.
comment:4 Changed 10 years ago by gorticus (Jason Mitchell)
On Macports v2.3.2, a quick find
yields:
$ find /opt/local/ -name port_autoconf.tcl /opt/local/libexec/macports/lib/port1.0/port_autoconf.tcl
with 47: variable git_path "/usr/bin/git"
.
One interesting note:
$ xcodebuild -version Xcode 6.1 Build version 6A1052c
What does your $ git --version
show?
comment:5 Changed 10 years ago by george.cooper@…
I've since installed the MacPorts git, so I've included both that and the built-in version query:
/usr/bin/git --version git version 1.9.3 (Apple Git-50) git --version git version 2.1.2
Changing git_path fixed it completely. Is it safe to leave that setting that way when doing future selfupdates?
comment:6 follow-up: 8 Changed 10 years ago by gorticus (Jason Mitchell)
Glad you have a workaround. It's probably safe to use until you want to do a selfupdate, at which time, if I remembered, I'd swap back and see how far I could get.
BTW, and this is a long shot, did you set user.email
and user.name
in your ~/.gitconfig
?
BBTW, I'm not sure I can resolve/close this ticket. My only Action is leave as new...
comment:7 Changed 10 years ago by george.cooper@…
Okay, I'll just proceed accordingly. And yea, I had set user.email and user.name in ~/.gitconfig, as well as github.user
comment:8 Changed 10 years ago by neverpanic (Clemens Lang)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Replying to jason-macports@…:
Glad you have a workaround. It's probably safe to use until you want to do a selfupdate, at which time, if I remembered, I'd swap back and see how far I could get.
It's safe to leave this value at /opt/local/bin/git
. Note that the next selfupdate (that actually installs a newer version of MacPorts, all others won't touch the file) might revert the change.
This is Apple's bug, not ours. Please file a radar. There's not much (or rather, nothing in excess of what I already did in #42063) we can do about it.
When reporting bugs against ports, please Cc the maintainer, if any.
The problem is:
This is a duplicate of #42063, where we were never able to figure out what's wrong. You can try the suggested steps there, and you can also try opening a bug report with Apple about this. It might also be something like OpenSSL's http://rt.openssl.org/Ticket/Display.html?id=2771 (user/pw guest/guest).