Egit 推送操作给出错误：“解压远程端时发生错误”
解压远程端
步骤时发生错误，我遵循的步骤： 在系统 A（远程）上：
- 安装 EGit
- 创建项目
- 共享该项目
- 创建存储库
- 添加该项目并将其提交到存储库
- （共享存储库文件夹）
在系统 B（本地）上：
- 安装 EGit
- 导入项目（通过克隆远程存储库）
- 选择克隆 (不添加）
- 给出远程存储库的路径，如 192.168.10.28\Git\repo
- 检查分支
- 给出目标路径（本地）
- 按照简单的步骤并导入项目
- 修改代码
- 将其提交到本地存储库
- 现在转到存储库视图并推送本地 将存储库内容发送到远程 1
- 错误窗口弹出，显示
“无法连接到任何存储库：\192.168.100.28\Git\repo（推送期间发生内部异常：\192.168.100.28\Git\repo：管道已关闭）”
Error occurred during unpacking the remote end
Steps, which I followed:
On system A (remote):
- Installed EGit
- Create a project
- Share that project
- Create repository
- Add and commit that project to repository
- (share the repository folder)
On system B (local):
- Install EGit
- Import project (by cloning remote repository)
- select clone (not add)
- give the path of remote repository like 192.168.10.28\Git\repo
- check the branch
- give destination path(local)
- follow simple steps and import the project
- Modify the code
- commit it to local repository
- Now go to repository view and push the local repository content to the remote 1
- ERROR window pops up saying
"Can't connect to any repository: \192.168.100.28\Git\repo (An internal Exception occurred during push: \192.168.100.28\Git\repo: Pipe closed)"
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
bug 314107 中提到了 Egit 上唯一的“管道关闭”错误并且与你的情况无关。
您的场景中唯一可疑的元素是远程存储库的地址。
使用文件协议，我将指定：
正如 OP Abhay 注释，目标文件夹受到写保护，这足以触发该错误消息。
The only "pipe closed" error on Egit is mentioned in bug 314107 and isn't related to your case.
The only suspicious element in your scenario is the address of your remote repo.
With the file protocol, I would specify:
As the OP Abhay comments, the destination folder was write protected, which was enough to trigger that error message.
此问题并非 Egit 特有。当 git 无法写入远程系统上的目标文件夹时会发生这种情况。正如另一个答案中所述，这可能是因为该文件夹没有正确的权限。也可能是由于其他原因，例如在我的情况下，文件系统已达到满容量。
This issue is not specific to Egit. It occurs when git cannot write to the destination folder on the remote system. This could be, as noted in another answer, that the folder did not have the correct permissions. It could also be for other reasons, such as in my case where the file system had reached full capacity.