git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Git push error
@ 2008-05-18  7:30 Marcus
  2008-05-18  8:09 ` Peter Baumann
  0 siblings, 1 reply; 6+ messages in thread
From: Marcus @ 2008-05-18  7:30 UTC (permalink / raw)
  To: git

Can anybody tell me what the following error means?

-----------------
sh-3.00# git push ssh://me@git.domain.org/gitroot/project/projectmain.git master
Password:
fatal: exec pack-objects failed.
Broken pipe
-------------------

Thanks,

Marcus

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Git push error
  2008-05-18  7:30 Git " Marcus
@ 2008-05-18  8:09 ` Peter Baumann
  0 siblings, 0 replies; 6+ messages in thread
From: Peter Baumann @ 2008-05-18  8:09 UTC (permalink / raw)
  To: Marcus; +Cc: git

On Sun, May 18, 2008 at 08:30:36AM +0100, Marcus wrote:
> Can anybody tell me what the following error means?
> 
> -----------------
> sh-3.00# git push ssh://me@git.domain.org/gitroot/project/projectmain.git master
> Password:
> fatal: exec pack-objects failed.
> Broken pipe
> -------------------
> 

You don't have git (especially git-pack-objects) in your path on the
remote end. Try

	ssh me@git.domain.org git --version

to see if your $PATH isn't setup correctly on ssh logins.

-Peter

^ permalink raw reply	[flat|nested] 6+ messages in thread

* git push error
@ 2024-03-20  7:17 jjb8256
  2024-03-20  8:45 ` Kristoffer Haugsbakk
  2024-03-20 11:52 ` rsbecker
  0 siblings, 2 replies; 6+ messages in thread
From: jjb8256 @ 2024-03-20  7:17 UTC (permalink / raw)
  To: git

Hi:
    git push 时发现如下报错,尝试无法修改,请帮忙,谢谢!

$ git push
Enumerating objects: 9, done.
Counting objects: 100% (8/8), done.
Delta compression using up to 8 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 701 bytes | 233.00 KiB/s, done.
Total 5 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
remote: The gitlab-shell hooks have been migrated to Gitaly, see https://gitlab.com/gitlab-org/gitaly/issues/1226
To http://10.11.15.10/ks-rd-fw/git-train-2022.git
 ! [remote rejected] develop -> develop (pre-receive hook declined)
error: failed to push some refs to 'http://10.11.15.10/ks-rd-fw/git-train-2022.git'

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: git push error
  2024-03-20  7:17 git push error jjb8256
@ 2024-03-20  8:45 ` Kristoffer Haugsbakk
  2024-03-20  8:51   ` Kristoffer Haugsbakk
  2024-03-20 11:52 ` rsbecker
  1 sibling, 1 reply; 6+ messages in thread
From: Kristoffer Haugsbakk @ 2024-03-20  8:45 UTC (permalink / raw)
  To: jjb8256; +Cc: git

On Wed, Mar 20, 2024, at 08:17, jjb8256@sina.com wrote:
> Hi:
>     git push 时发现如下报错,尝试无法修改,请帮忙,谢谢!
>
> $ git push
> Enumerating objects: 9, done.
> Counting objects: 100% (8/8), done.
> Delta compression using up to 8 threads
> Compressing objects: 100% (5/5), done.
> Writing objects: 100% (5/5), 701 bytes | 233.00 KiB/s, done.
> Total 5 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
> remote: The gitlab-shell hooks have been migrated to Gitaly, see
> https://gitlab.com/gitlab-org/gitaly/issues/1226
> To http://10.11.15.10/ks-rd-fw/git-train-2022.git
>  ! [remote rejected] develop -> develop (pre-receive hook declined)
> error: failed to push some refs to
> 'http://10.11.15.10/ks-rd-fw/git-train-2022.git'

The pre-receive hook on the server failed. That means that whatever you
pushed is wrong according to that script.

See `man githooks`.

--
Kristoffer

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: git push error
  2024-03-20  8:45 ` Kristoffer Haugsbakk
@ 2024-03-20  8:51   ` Kristoffer Haugsbakk
  0 siblings, 0 replies; 6+ messages in thread
From: Kristoffer Haugsbakk @ 2024-03-20  8:51 UTC (permalink / raw)
  To: Kristoffer Haugsbakk; +Cc: git, jjb8256

On Wed, Mar 20, 2024, at 09:45, Kristoffer Haugsbakk wrote:
> On Wed, Mar 20, 2024, at 08:17, jjb8256@sina.com wrote:
>> [snip]
>> https://gitlab.com/gitlab-org/gitaly/issues/1226
>> [snip]
>
> The pre-receive hook on the server failed. That means that whatever you
> pushed is wrong according to that script.
>
> See `man githooks`.
>
> --
> Kristoffer

You should also look at the the message that the remote sent:

    remote: The gitlab-shell hooks have been migrated to Gitaly, see
    https://gitlab.com/gitlab-org/gitaly/issues/1226

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: git push error
  2024-03-20  7:17 git push error jjb8256
  2024-03-20  8:45 ` Kristoffer Haugsbakk
@ 2024-03-20 11:52 ` rsbecker
  1 sibling, 0 replies; 6+ messages in thread
From: rsbecker @ 2024-03-20 11:52 UTC (permalink / raw)
  To: jjb8256, git

On Wednesday, March 20, 2024 3:17 AM, jjb8256@sina.com wrote:
>    git push 时发现如下报错,尝试无法修改,请帮忙,谢谢!
>
>$ git push
>Enumerating objects: 9, done.
>Counting objects: 100% (8/8), done.
>Delta compression using up to 8 threads
>Compressing objects: 100% (5/5), done.
>Writing objects: 100% (5/5), 701 bytes | 233.00 KiB/s, done.
>Total 5 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
>remote: The gitlab-shell hooks have been migrated to Gitaly, see
>https://gitlab.com/gitlab-org/gitaly/issues/1226
>To http://10.11.15.10/ks-rd-fw/git-train-2022.git
> ! [remote rejected] develop -> develop (pre-receive hook declined)
>error: failed to push some refs to 'http://10.11.15.10/ks-rd-fw/git-train-2022.git'

This looks like a problem with the pre-receive hook on your GitLab installation on the server-side, or that script is rejecting the push. This probably should be referred to the GitLab team for support (possibly at your company).

--Randall


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2024-03-20 11:52 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-03-20  7:17 git push error jjb8256
2024-03-20  8:45 ` Kristoffer Haugsbakk
2024-03-20  8:51   ` Kristoffer Haugsbakk
2024-03-20 11:52 ` rsbecker
  -- strict thread matches above, loose matches on Subject: below --
2008-05-18  7:30 Git " Marcus
2008-05-18  8:09 ` Peter Baumann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).