On 2021-07-26 at 17:54:07, Evan Miller wrote: > What did you do before the bug happened? (Steps to reproduce your issue) > > $ git clone -v git@xxxxxxxxxx:macports/macports-ports.git > Cloning into 'macports-ports'... > remote: Enumerating objects: 1223319, done. > remote: Counting objects: 100% (685/685), done. > remote: Compressing objects: 100% (341/341), done. > remote: Total 1223319 (delta 289), reused 608 (delta 252), pack-reused 1222634 > Receiving objects: 100% (1223319/1223319), 244.46 MiB | 1.09 MiB/s, done. > Connection to github.com closed by remote host. This message is the relevant detail here. This means that the connection was reset, which could be due to the remote host (GitHub), but is more likely due to a network issue of some sort. You'll have to do normal network troubleshooting to see why that might be. It could very well be related to the fact that you're running a nearly 14-year old operating system, but I just can't say for certain. It's not a bug in Git, however. Even if the data is otherwise transferred successfully, Git will exit unsuccessfully if this happens, and that will result in your data not being checked out. -- brian m. carlson (he/him or they/them) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
