如何解决'致命：索引包失败'？ [英] 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 
在/home/ira/code/ros/sam_slam/ethzasl_mapping/.git/中初始化空的Git存储库
 remote：计数对象：784，完成。 
 remote：压缩对象：100％（238/238），完成。 
致命：远程端意外挂断| | 18 KiB / s 
致命：早期EOFs：31％（244/784），52.00 KiB | 18 KiB / s 
致命：索引包装失败
 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 
在/home/ira/code/ros/sam_slam/ethzasl_mapping/.git/中初始化的空的Git存储库
 remote ：计数对象：784，完成。 
 remote：压缩对象：100％（238/238），完成。 
致命：远程端意外挂断| | 18 KiB / s 
致命：早期EOFs：31％（244/784），52.00 KiB | 18 KiB / s 
致命：index-pack失败
 ira @ ira-K42JP：〜/ code / ros / sam_slam $ 
  

如何解决它？

谢谢〜

解决方案

除非您使用不寻常的协议组合（如 Git检出问题 [fatal：early EOFs] ），这是GitHub服务器打嗝的标志。

请参阅其 GitHub系统状态页面：

  2012年5月25日 - 发生轻微中断
 
上午06:44 PST 
所有系统恢复正常。 
 
 06:30 am PST 
调查间歇性'远端意外挂断'错误
  

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

I run:

  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$

How to solve it?

Thank you~

解决方案

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.

See its GitHub system status page:

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 

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

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