Opened 7 years ago

Closed 3 years ago

#49539 closed defect (worksforme)

git-flow: fatal: unable to access 'https://github.com/nvie/gitflow.git/': SSL certificate problem: Couldn't understand the server certificate format

Reported by: nhojpatrick (John Patrick) Owned by: gorticus (Jason Mitchell)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: petrrr
Port: git-flow

Description (last modified by ryandesign (Ryan Schmidt))

git-flow won't install, tried clean then install. Issue looks very similar to #45704

if I do git config --list it does show user.name and user.email.

$ /usr/bin/git --version
git version 2.4.9 (Apple Git-60)

$ git --version
git version 2.6.2

$ xcodebuild -version
Xcode 7.1
Build version 7B91b

Attachments (1)

main.log (90.6 KB) - added by nhojpatrick (John Patrick) 7 years ago.

Download all attachments as: .zip

Change History (15)

Changed 7 years ago by nhojpatrick (John Patrick)

Attachment: main.log added

comment:1 Changed 7 years ago by nhojpatrick (John Patrick)

Missed adding this;

--->  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
Last edited 7 years ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:2 Changed 7 years ago by ryandesign (Ryan Schmidt)

Cc: jason-macports@… removed
Description: modified (diff)
Owner: changed from macports-tickets@… to jason-macports@…
Summary: git-flow install fails on El Capitangit-flow: fatal: unable to access 'https://github.com/nvie/gitflow.git/': SSL certificate problem: Couldn't understand the server certificate format

#45704 was about the error:

fatal: unable to access 'https://github.com/nvie/gitflow.git/': Unknown SSL protocol error in connection to github.com:-67674

That is different from the error in your log, which is:

fatal: unable to access 'https://github.com/nvie/gitflow.git/': SSL certificate problem: Couldn't understand the server certificate format

I am not able to reproduce this problem. Maybe there was a temporary server issue which has already been resolved? Please try again.

comment:3 Changed 7 years ago by nhojpatrick (John Patrick)

I had been trying for a few days without success before reporting. Just tried again, still without success.

Last login: Sun Nov  1 16:40:30 on console
$ sudo port clean git-flow
Password:
--->  Cleaning git-flow
$ sudo port install git-flow
--->  Computing dependencies for git-flow
--->  Fetching archive for git-flow
--->  Attempting to fetch git-flow-0.4.1_2.darwin_15.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_15.noarch.tbz2 from http://lil.fr.packages.macports.org/git-flow
--->  Attempting to fetch git-flow-0.4.1_2.darwin_15.noarch.tbz2 from http://nue.de.packages.macports.org/macports/packages/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
$ tail -50 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_git-flow/git-flow/main.log
:debug:main universal variant already exists, so not adding the default one
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main No need to upgrade! getopt 1.1.6_0 >= getopt 1.1.6_0
:msg:main --->  Computing dependencies for git-flow:info:main .:debug:main Checking for conflicts against git-flow
:debug:main Searching for dependency: git-flow-devel
:debug:main Didn't find receipt, going to depspec regex for: git-flow-devel
:debug:main Searching for dependency: git-flow-avh
:debug:main Didn't find receipt, going to depspec regex for: git-flow-avh
:debug:main Searching for dependency: git-flow-hf
:debug:main Didn't find receipt, going to depspec regex for: git-flow-hf
:debug:main Searching for dependency: git
:debug:main Found Dependency: receipt exists for git
:debug:main Searching for dependency: getopt
:debug:main Found Dependency: receipt exists for getopt
:msg:main 
:debug:main Executing org.macports.main (git-flow)
:debug:archivefetch archivefetch phase started at Sun Nov  1 17:18:25 GMT 2015
:msg:archivefetch --->  Fetching archive for git-flow
:debug:archivefetch Executing org.macports.archivefetch (git-flow)
:info:archivefetch --->  git-flow-0.4.1_2.darwin_15.noarch.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
:msg:archivefetch --->  Attempting to fetch git-flow-0.4.1_2.darwin_15.noarch.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/git-flow
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found
:msg:archivefetch --->  Attempting to fetch git-flow-0.4.1_2.darwin_15.noarch.tbz2 from http://lil.fr.packages.macports.org/git-flow
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found
:msg:archivefetch --->  Attempting to fetch git-flow-0.4.1_2.darwin_15.noarch.tbz2 from http://nue.de.packages.macports.org/macports/packages/git-flow
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found
:debug:fetch fetch phase started at Sun Nov  1 17:18:28 GMT 2015
: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/': SSL certificate problem: Couldn't understand the server certificate format
: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
$

I've got the following port installed, not sure if that makes a difference or not.

$ port installed
The following ports are currently installed:
  apache-ant @1.9.6_0 (active)
  apr @1.5.2_1+universal (active)
  apr-util @1.5.4_0+universal (active)
  autoconf @2.69_5 (active)
  automake @1.15_1 (active)
  bash @4.3.42_0+universal (active)
  bash-completion @2.1_9 (active)
  bzip2 @1.0.6_0+universal (active)
  curl @7.45.0_0+ssl+universal (active)
  curl-ca-bundle @7.45.0_0 (active)
  cyrus-sasl2 @2.1.26_4+kerberos+universal (active)
  db46 @4.6.21_10+universal (active)
  db48 @4.8.30_4+universal (active)
  desktop-file-utils @0.22_0+universal (active)
  dos2unix @7.2_0+universal (active)
  expat @2.1.0_0+universal (active)
  gawk @4.1.3_0+universal (active)
  gdbm @1.11_1+universal (active)
  getopt @1.1.6_0 (active)
  gettext @0.19.6_0+universal (active)
  git @2.6.2_1+bash_completion+credential_osxkeychain+doc+pcre+perl5_16+python27+svn+universal (active)
  glib2 @2.46.1_1+universal (active)
  gmp @6.0.0_1+universal (active)
  gnupg @1.4.19_0+universal (active)
  gnutls @3.3.18_0+universal (active)
  gperf @3.0.4_2+universal (active)
  gzip @1.6_0+universal (active)
  help2man @1.47.2_0+universal (active)
  icu @55.1_0+universal (active)
  jython @2.5.2_0+installer (active)
  kerberos5 @1.13.2_1+universal (active)
  libcomerr @1.42.13_0+universal (active)
  libedit @20150325-3.1_0+universal (active)
  libev @4.20_0+universal (active)
  libffi @3.2.1_0+universal (active)
  libiconv @1.14_0+universal (active)
  libidn @1.32_0+universal (active)
  libmagic @5.25_0+universal (active)
  libtasn1 @4.7_0+universal (active)
  libtool @2.4.6_2+universal (active)
  libusb @1.0.20_0+universal (active)
  libusb-compat @0.1.5_0+universal (active)
  libxml2 @2.9.2_2+universal (active)
  libxslt @1.1.28_1+universal (active)
  lighttpd @1.4.37_0+ssl+universal (active)
  maven2 @2.2.1_3 (active)
  maven3 @3.3.3_0 (active)
  maven_select @0.3_1 (active)
  mercurial @3.5.99_1+bash_completion+universal (active)
  ncurses @6.0_0+universal (active)
  nettle @3.1.1_0+universal (active)
  openldap @2.4.40_1+universal (active)
  openssh @7.1p1_0+kerberos5+universal+xauth (active)
  openssl @1.0.2d_0+universal (active)
  osxfuse @2.8.2_0 (active)
  p5.16-authen-sasl @2.160.0_0 (active)
  p5.16-cgi @4.210.0_0 (active)
  p5.16-digest-hmac @1.30.0_0 (active)
  p5.16-digest-sha1 @2.130.0_4+universal (active)
  p5.16-encode-locale @1.50.0_0 (active)
  p5.16-error @0.170.240_0 (active)
  p5.16-file-listing @6.40.0_1 (active)
  p5.16-gssapi @0.280.0_3+universal (active)
  p5.16-html-form @6.30.0_1 (active)
  p5.16-html-parser @3.710.0_1+universal (active)
  p5.16-html-tagset @3.200.0_4 (active)
  p5.16-http-cookies @6.10.0_1 (active)
  p5.16-http-daemon @6.10.0_1 (active)
  p5.16-http-date @6.20.0_1 (active)
  p5.16-http-message @6.110.0_0 (active)
  p5.16-http-negotiate @6.10.0_1 (active)
  p5.16-io @1.250.0_4+universal (active)
  p5.16-io-html @1.1.0_0 (active)
  p5.16-io-socket-inet6 @2.720.0_0 (active)
  p5.16-io-socket-ip @0.370.0_0 (active)
  p5.16-io-socket-ssl @2.20.0_0 (active)
  p5.16-libwww-perl @6.130.0_0+ssl (active)
  p5.16-lwp-mediatypes @6.20.0_1 (active)
  p5.16-lwp-protocol-https @6.60.0_1 (active)
  p5.16-mime-base64 @3.150.0_0+universal (active)
  p5.16-mozilla-ca @20150826_0 (active)
  p5.16-net-http @6.90.0_0 (active)
  p5.16-net-libidn @0.120.0_4+universal (active)
  p5.16-net-smtp-ssl @1.30.0_0 (active)
  p5.16-net-ssleay @1.720.0_0+universal (active)
  p5.16-socket6 @0.250.0_1+universal (active)
  p5.16-sub-uplevel @0.250.0_0 (active)
  p5.16-svn-simple @0.280.0_4 (active)
  p5.16-term-readkey @2.330.0_0+universal (active)
  p5.16-test-deep @0.119.0_0 (active)
  p5.16-test-exception @0.400.0_0 (active)
  p5.16-test-nowarnings @1.40.0_1 (active)
  p5.16-test-simple @1.1.14_0 (active)
  p5.16-test-warn @0.300.0_1 (active)
  p5.16-uri @1.690.0_0 (active)
  p5.16-www-robotrules @6.20.0_1 (active)
  p5.22-locale-gettext @1.70.0_0+universal (active)
  p11-kit @0.22.1_0+universal (active)
  pcre @8.37_0+universal (active)
  perl5 @5.16.3_0+perl5_16 (active)
  perl5.16 @5.16.3_1+universal (active)
  perl5.22 @5.22.0_0+universal (active)
  pkgconfig @0.28_0+universal (active)
  popt @1.16_0+universal (active)
  py27-docutils @0.12_0 (active)
  py27-requests @2.8.1_0 (active)
  py27-roman @2.0.0_0 (active)
  py27-setuptools @18.3.2_0 (active)
  python2_select @133341_0 (active)
  python3_select @0.0_1 (active)
  python27 @2.7.10_3+universal (active)
  python34 @3.4.3_5+universal (active)
  python_select @0.3_6 (active)
  readline @6.3.003_1+universal (active)
  rsync @3.1.1_0+universal (active)
  ruby @1.8.7-p374_1+universal (active)
  ruby_select @1.1_0 (active)
  scons @2.3.4_0 (active)
  serf1 @1.3.4_0+universal (active)
  spawn-fcgi @1.6.4_0+universal (active)
  sqlite3 @3.8.11.1_0+universal (active)
  sshfs @2.5_0 (active)
  subversion @1.9.2_0+universal (active)
  subversion-perlbindings-5.16 @1.9.2_0+universal (active)
  tcp_wrappers @20_2+universal (active)
  texinfo @6.0_1+universal (active)
  unrar @5.2.7_0+universal (active)
  watch @3.3.11_0+universal (active)
  wget @1.16.3_1+ssl+universal (active)
  xauth @1.0.9_1+universal (active)
  xorg-bigreqsproto @1.1.2_0 (active)
  xorg-inputproto @2.3.1_0 (active)
  xorg-kbproto @1.0.7_0 (active)
  xorg-libice @1.0.9_0+universal (active)
  xorg-libpthread-stubs @0.3_0 (active)
  xorg-libsm @1.2.1_0+universal (active)
  xorg-libX11 @1.6.3_0+universal (active)
  xorg-libXau @1.0.8_0+universal (active)
  xorg-libxcb @1.11.1_0+python27+universal (active)
  xorg-libXdmcp @1.1.2_0+universal (active)
  xorg-libXext @1.3.3_0+universal (active)
  xorg-libXmu @1.1.2_0+universal (active)
  xorg-libXt @1.1.5_1+universal (active)
  xorg-util-macros @1.19.0_0 (active)
  xorg-xcb-proto @1.11_1+python27 (active)
  xorg-xcmiscproto @1.2.2_0 (active)
  xorg-xextproto @7.3.0_0 (active)
  xorg-xf86bigfontproto @1.2.0_0 (active)
  xorg-xproto @7.0.28_0 (active)
  xorg-xtrans @1.3.5_0 (active)
  xz @5.2.2_0+universal (active)
  zlib @1.2.8_0+universal (active)
$

comment:4 Changed 7 years ago by nhojpatrick (John Patrick)

I've also tried to manually clone what I believe is failing when executed via ports;

Both of the following work;

$ /usr/bin/git clone https://github.com/nvie/gitflow.git
$ git clone https://github.com/nvie/gitflow.git

So issue is with mac ports and where/how it loads ssl certs. Only a guess...

comment:5 Changed 7 years ago by gorticus (Jason Mitchell)

Unfortunately, I will not be able to look at this until next week, and I don't have El Capitan, if it really makes a difference.

Has anyone tried to install git-flow-avh? The nvie version is quite old, with no commits since 2012-09-25.

The other option might be to try using the release tarballs, though I'm not sure that works using using the github port group.

comment:6 Changed 7 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:7 in reply to:  5 ; Changed 7 years ago by ryandesign (Ryan Schmidt)

Replying to jason-macports@…:

The other option might be to try using the release tarballs, though I'm not sure that works using using the github port group.

Of course it does. That's the preferred way of using the github portgroup. Fetching from a git repository should always be a last resort. Read the documentation in the github portgroup file for more information.

comment:8 in reply to:  7 ; Changed 7 years ago by gorticus (Jason Mitchell)

Replying to ryandesign@…:

Replying to jason-macports@…:

The other option might be to try using the release tarballs, though I'm not sure that works using using the github port group.

Of course it does. That's the preferred way of using the github portgroup. Fetching from a git repository should always be a last resort. Read the documentation in the github portgroup file for more information.

Sorry for seeming obtuse. I meant that the nvie git-flow repo uses a submodule (`shFlags`), and GitHub does not include them in the autogenerated archive/release files. So, the only way I see to build the package is to clone the git repo and submodule update --init ex post facto. The same setup afflicts the hubflow version too. Only the avh addition has it's own refactored version included directly and not in an submodule.

comment:9 in reply to:  4 Changed 7 years ago by gorticus (Jason Mitchell)

Replying to nhoj.patrick@…:

I've also tried to manually clone what I believe is failing when executed via ports;

Both of the following work;

$ /usr/bin/git clone https://github.com/nvie/gitflow.git
$ git clone https://github.com/nvie/gitflow.git

So issue is with mac ports and where/how it loads ssl certs. Only a guess...

Did you try the suggestion in the ticket you previously mentioned here?

I recommend using git-flow-avh instead, unless you require legacy functionality.

comment:10 Changed 7 years ago by nhojpatrick (John Patrick)

not used git-flow-avh in anger but it looks like it does the job okay.

should this defect be marked as won't fixed or deprecated? so others know not to use it and to use git-flow-avh instead?

comment:11 Changed 7 years ago by adfernandes (Andrew Fernandes)

Similar to #50467

comment:12 in reply to:  8 Changed 7 years ago by ryandesign (Ryan Schmidt)

Replying to jason-macports@…:

Replying to ryandesign@…:

Replying to jason-macports@…:

The other option might be to try using the release tarballs, though I'm not sure that works using using the github port group.

Of course it does. That's the preferred way of using the github portgroup. Fetching from a git repository should always be a last resort. Read the documentation in the github portgroup file for more information.

Sorry for seeming obtuse. I meant that the nvie git-flow repo uses a submodule (`shFlags`), and GitHub does not include them in the autogenerated archive/release files. So, the only way I see to build the package is to clone the git repo and submodule update --init ex post facto. The same setup afflicts the hubflow version too. Only the avh addition has it's own refactored version included directly and not in an submodule.

You said "release tarballs"; I assumed you meant a manually-(developer-)generated tarball attached to a GitHub release object. The developer is responsible for including all source code in this tarball necessary to build their software.

But I see that you're actually referring to the automatically-generated "tarball" and "archive" tarballs, which indeed do not include submodules, and may therefore not be suitable.

The developers of git-flow appear not offer any GitHub releases, perhaps because their last release was in 2011, years before GitHub introduced the release feature. Perhaps you can encourage the developers to release a new version, including creating a GitHub release object and attaching the full source code tarball to it, as is customary GitHub software release procedure these days.

comment:13 Changed 3 years ago by nhojpatrick (John Patrick)

ticket can be close i kept trying to use mac ports and getting this problem with different ports i wanted to use, now switched to homebrew and the apps i need don't have these types of issues

comment:14 Changed 3 years ago by mf2k (Frank Schima)

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.