如何解决致命问题:索引包失败? [英] How to solve'fatal: index-pack failed'?

问题描述

我跑步:

  ira@ira-K42JP:~/code/ros/sam_slam$ git clone       git://github.com/ethz-asl/ros-mapping.git ethzasl_mapping
  Initialized empty Git repository in       /home/ira/code/ros/sam_slam/ethzasl_mapping/.git/      
  remote: Counting objects: 784, done.
  remote: Compressing objects: 100% (238/238), done.
  fatal: The remote end hung up unexpectedlyiB | 18 KiB/s   
  fatal: early EOFs:  31% (244/784), 52.00 KiB | 18 KiB/s   
  fatal: index-pack failed
  ira@ira-K42JP:~/code/ros/sam_slam$
  ira@ira-K42JP:~/code/ros/sam_slam$ git clone       git://github.com/ethz-asl/ros-mapping.git ethzasl_mapping
  Initialized empty Git repository in       /home/ira/code/ros/sam_slam/ethzasl_mapping/.git/
  remote: Counting objects: 784, done.
  remote: Compressing objects: 100% (238/238), done.
  fatal: The remote end hung up unexpectedlyiB | 18 KiB/s   
  fatal: early EOFs:  31% (244/784), 52.00 KiB | 18 KiB/s   
  fatal: index-pack failed
  ira@ira-K42JP:~/code/ros/sam_slam$

如何解决?

谢谢〜

推荐答案

除非您使用的是不寻常的协议组合(例如"

Unless you are using an unusual protocol combination (like in "Git checking out problem [fatal: early EOFs]"), this is a sign of a GitHub server hiccup.

请参见其 GitHub系统状态页面:

May 25, 2012 – minor interruption occurred

06:44 am PST
All systems are back to normal.

06:30 am PST
Investigating intermittent 'remote end hung up unexpectedly' errors 

似乎还有一些残留的副作用，在GitHub提到的官方解决时间"之后仍然可以看到.

It seems to have some residual side-effects which can still be seen after the official "resolution time" mentioned by GitHub.

这篇关于如何解决致命问题:索引包失败?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！