#49539: git-flow: fatal: unable to access 'https://github.com/nvie/gitflow.git/': SSL certificate problem: Couldn't understand the server certificate format -----------------------------+------------------------------ Reporter: nhoj.patrick@… | Owner: jason-macports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: git-flow | -----------------------------+------------------------------ Comment (by ryandesign@…): Replying to [comment:8 jason-macports@…]:
Replying to [comment:7 ryandesign@…]:
Replying to [comment:5 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 ([https://github.com/nvie/shFlags `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 [https://github.com/blog/1547-release-your-software 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. -- Ticket URL: <https://trac.macports.org/ticket/49539#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X