threads / discuss / 31491

Problems with repack during push

Subject: Problems with repack during push

## tl;dr

3 messages between Sep 10, 2012 and Sep 10, 2012.

replies: 2people: 2as markdown or json

Rob Marshall· Sep 10, 2012, 16:16 UTC · lore
Hi,
Whenever I do a git push origin of a new branch I see:

Auto packing the repository for optimum performance. /usr/local/libexec/git-core/git-sh-setup: line 241: uname: command not found /usr/local/libexec/git-core/git-repack: line 56: rm: command not found /usr/local/libexec/git-core/git-repack: line 85: mkdir: command not found /usr/local/libexec/git-core/git-repack: line 85: rm: command not found fatal: 'repack' appears to be a git command, but we were not able to execute it. Maybe git-repack is broken? error: failed to run repack

If I do a 'git repack' it works fine, so are these messages coming from the remote server?

Thanks,
Rob
Matthieu Moy· Sep 10, 2012, 16:26 UTC · re: Rob Marshall · lore

Re: Problems with repack during push

Rob Marshall <Rob.Marshall17@gmail.com> writes:
> If I do a 'git repack' it works fine, so are these
> messages coming from the remote server?

I guess so, and your remote server has a restricted environment (chroot or so) with very few commands allowed, which prevents shell-scripts from executing properly.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Rob Marshall· Sep 10, 2012, 16:54 UTC · re: Matthieu Moy · lore

Re: Problems with repack during push

OK, thanks. I'll check with the guy who set up the server.
Rob
On 9/10/12 12:26 PM, Matthieu Moy wrote:
Show 9 quoted lines
> Rob Marshall <Rob.Marshall17@gmail.com> writes:
>
>> If I do a 'git repack' it works fine, so are these
>> messages coming from the remote server?
>
> I guess so, and your remote server has a restricted environment (chroot
> or so) with very few commands allowed, which prevents shell-scripts from
> executing properly.
>

← back to recent threads