Problems with linaro-android_toolchain-4.6-2011.07 rebuilds
asac at linaro.org
Mon Aug 8 10:39:41 UTC 2011
ok spads from IS gave better suggestion than using umask in .bashrc.
Now, we propose that you set alias for git like:
alias git='UMASK=002 git'
Please update accordingly.
On Mon, Aug 8, 2011 at 11:51 AM, Alexander Sack <asac at linaro.org> wrote:
> this should be fixed now. folks, please use:
> umask 002
> in your .bashrc -> ssh git.linaro.org -> change .bashrc there.
> I guess from now on we could consider to use gerrit for toolchain etc. too.
> On Sun, Aug 7, 2011 at 8:16 PM, James Westby <james.westby at linaro.org> wrote:
>> On Sun, 7 Aug 2011 02:25:17 +0100, Zach Pfeffer <zach.pfeffer at linaro.org> wrote:
>>> I'm seeing the same thing:
>>> $git push linaro HEAD
>>> Counting objects: 5, done.
>>> Delta compression using up to 4 threads.
>>> Compressing objects: 100% (2/2), done.
>>> Writing objects: 100% (3/3), 454 bytes, done.
>>> Total 3 (delta 1), reused 0 (delta 0)
>>> error: insufficient permission for adding an object to repository
>>> database ./objects
>>> fatal: failed to write object
>>> error: unpack failed: unpack-objects abnormal exit
>>> To ssh://firstname.lastname@example.org/srv/git.linaro.org/git/android/toolchain/manifest.git
>>> ! [remote rejected] HEAD -> toolchain-11.07-release (n/a (unpacker error))
>>> error: failed to push some refs to
>>> Any ideas Paul?
>> The issue is that someone is pushing to these trees with a UMASK that
>> prevents others in the group from writing some files to them. If you are
>> pushing something that contains an object that needs to go in a dir
>> created by someone pushing with a restrictive UMASK you will see this.
>> You can file an RT ticket to get a chmod -R g+w on these trees.
>> Please also make sure that if you are pushing to git.linaro.org you set
>> your UMASK on that system to allow group write on files/dirs that you
> - Alexander
More information about the linaro-dev