{"thread":{"id":"34034","subject":"Git server, chroot, git gc --auto and \"uname: not found\"","startedAt":"2013-06-05T16:37:28Z","lastAt":"2013-06-05T16:37:28Z","messageCount":1,"participants":["Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"219461","messageId":"vpqip1sfr93.fsf@anie.imag.fr","threadId":"34034","inReplyTo":null,"subject":"Git server, chroot, git gc --auto and \"uname: not found\"","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-06-05T16:37:28Z","receivedAt":"2013-06-05T16:37:28Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Hi,\n\nI'm having issues with a Git hosting in a chroot (based on fusion\nforge). The problem is that receive-pack triggers a \"git gc --auto\",\nwhich itself triggers a \"git repack\", which is a shell-script.\n\nThe shell script needs basic commands [1], which are not available within the\nchroot.\n\nIs there a clean solution to this problem?\n\nI guess the right solution is \"send a patch that ports git-repack.sh to\nC\" (I thought we already had the server-side in C only, but just\ndiscovered it isn't the case), but I wont have time for that (not soon\nat least).\n\nThanks,\n\n[1] uname, used in git-sh-setup, and then /bin/rm /usr/bin/find /bin/sed\n/usr/bin/tr /bin/mkdir /bin/chmod and /bin/mv according to strace.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"}]}