[MacPorts] #69727: emacs-mac-app-devel: Unable to fetch from repo: fatal: the remote end hung up unexpectedly

[MacPorts]

#69727: emacs-mac-app-devel: Unable to fetch from repo: fatal: the remote end hung
up unexpectedly
----------------------------------+----------------------
  Reporter:  George9000           |      Owner:  amake
      Type:  defect               |     Status:  assigned
  Priority:  Normal               |  Milestone:
 Component:  ports                |    Version:
Resolution:                       |   Keywords:
      Port:  emacs-mac-app-devel  |
----------------------------------+----------------------

Comment (by ryandesign):

 I'm not sure why this fails. It could be a problem specific to bitbucket
 and/or the path our network traffic takes to their server.

 But maybe we don't need to investigate why `--shallow-since` doesn't work
 and instead focus on avoiding the need to use it. No other port uses this
 flag.

 You're presumably using it to limit network traffic and disk space so that
 you don't fetch the entire repository when you need just one commit.

 Why not fetch just that one commit then?
 [https://stackoverflow.com/questions/31278902/how-to-shallow-clone-a
 -specific-commit-with-depth-1 git has this capability now]. It didn't used
 to, back when MacPorts git fetching commands were implemented.

 It should be fixed in MacPorts base, then. A problem is that the git (and
 hg) fetching code does things manually instead of using the typical
 `command_exec` method that's used elsewhere in MacPorts base.

 A patch to fix git (and hg) fetching to use `command_exec` was submitted
 in #29093. If we get that fixed, then switching the git fetching procedure
 to fetch just the required commit when one is specified should be fairly
 easy. That method does work to fetch the emacs-mac-app-devel repository on
 my system, when done manually on the command line.

 However, ideally, the port should not fetch from git at all; it should
 fetch from a distfile. Taking a quick look at the bitbucket portgroup it
 seems like it should support that just as github and gitlab do but I see
 at least one problem with the bitbucket portgroup and will look at it more
 later.

-- 
Ticket URL: <https://trac.macports.org/ticket/69727#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS