Re: Problems with linaro-android_toolchain-4.6-2011.07 rebuilds
On 08/09/2011 07:26 AM, Paul Sokolovsky wrote: > Hello Alexander, > > On Mon, 8 Aug 2011 12:39:41 +0200 > Alexander Sack wrote: > >> 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' > > I understand the logic here - set umask only for git, but would that > really work? I kinda get used that aliases are interactive session > thing, and man reads: > >Aliases are not expanded when the shell is not interactive, >unless the expand_aliases shell option is set using shopt (see >the description of shopt under SHELL BUILTIN COMMANDS below). > > I'm not sure how exactly git over ssh works though. > > > And whatever way of umask setting should be, did IS consider > implementing it via global /etc/profile or via profile templates clones > by adduser or similar tool, to alleviate that burden for the users? There's another way to do this which doesn't require updating UMASK's or aliases. You can use setfacl as described here: https://wincent.com/wiki/Git_repository_access_control I've used this on multiple projects. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with linaro-android_toolchain-4.6-2011.07 rebuilds
Hello Alexander, On Mon, 8 Aug 2011 12:39:41 +0200 Alexander Sack wrote: > 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' I understand the logic here - set umask only for git, but would that really work? I kinda get used that aliases are interactive session thing, and man reads: Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt (see the description of shopt under SHELL BUILTIN COMMANDS below). I'm not sure how exactly git over ssh works though. And whatever way of umask setting should be, did IS consider implementing it via global /etc/profile or via profile templates clones by adduser or similar tool, to alleviate that burden for the users? > > Please update accordingly. > Thanks! > > On Mon, Aug 8, 2011 at 11:51 AM, Alexander Sack > 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. > > > > Thanks! > > > > On Sun, Aug 7, 2011 at 8:16 PM, James Westby > > wrote: > >> On Sun, 7 Aug 2011 02:25:17 +0100, Zach Pfeffer > >> 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://pfeff...@git.linaro.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 > >>> 'ssh://pfeff...@git.linaro.org/srv/git.linaro.org/git/android/toolchain/manifest.git' > >>> > >>> 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 create. > >> > >> Thanks, > >> > >> James > >> > > > > > > > > -- > > > > - Alexander > > > > > -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with linaro-android_toolchain-4.6-2011.07 rebuilds
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. Thanks! On Mon, Aug 8, 2011 at 11:51 AM, Alexander Sack 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. > > Thanks! > > On Sun, Aug 7, 2011 at 8:16 PM, James Westby wrote: >> On Sun, 7 Aug 2011 02:25:17 +0100, Zach Pfeffer >> 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://pfeff...@git.linaro.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 >>> 'ssh://pfeff...@git.linaro.org/srv/git.linaro.org/git/android/toolchain/manifest.git' >>> >>> 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 >> create. >> >> Thanks, >> >> James >> > > > > -- > > - Alexander > -- - Alexander ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with linaro-android_toolchain-4.6-2011.07 rebuilds
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. Thanks! On Sun, Aug 7, 2011 at 8:16 PM, James Westby wrote: > On Sun, 7 Aug 2011 02:25:17 +0100, Zach Pfeffer > 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://pfeff...@git.linaro.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 >> 'ssh://pfeff...@git.linaro.org/srv/git.linaro.org/git/android/toolchain/manifest.git' >> >> 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 > create. > > Thanks, > > James > -- - Alexander ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with linaro-android_toolchain-4.6-2011.07 rebuilds
On Sun, 7 Aug 2011 02:25:17 +0100, Zach Pfeffer 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://pfeff...@git.linaro.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 > 'ssh://pfeff...@git.linaro.org/srv/git.linaro.org/git/android/toolchain/manifest.git' > > 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 create. Thanks, James ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with linaro-android_toolchain-4.6-2011.07 rebuilds
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://pfeff...@git.linaro.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 'ssh://pfeff...@git.linaro.org/srv/git.linaro.org/git/android/toolchain/manifest.git' Any ideas Paul? On 7 August 2011 01:20, Bernhard Rosenkranzer wrote: > Hi, > I have a manifest that reverts everything to what it was in 11.07 > ready to go - but I seem to lack permissions to push it to a new > branch: > > $ git push linaro toolchain-11.07-release > Counting objects: 5, done. > Delta compression using up to 8 threads. > Compressing objects: 100% (2/2), done. > Writing objects: 100% (3/3), 477 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://bernhardrosenkran...@git.linaro.org/srv/git.linaro.org/git/android/toolchain/manifest.git > ! [remote rejected] toolchain-11.07-release -> > toolchain-11.07-release (n/a (unpacker error)) > error: failed to push some refs to > 'ssh://bernhardrosenkran...@git.linaro.org/srv/git.linaro.org/git/android/toolchain/manifest.git' > > Can someone fix this or should I just use master and revert later? > > I've attached the relevant file if anyone wants to push it (it gets > back to 11.07 by simply specifying the correct revisions to pull -- no > need to revert the other repositories). > > ttyl > bero > > On 7 August 2011 01:40, Zach Pfeffer wrote: >> I filed a bug on this and assigned it to bero: >> >> https://bugs.launchpad.net/linaro-android/+bug/822106 >> >> Bero once you're happy with the original build I can cut an 11.07. It >> would be nice t have git and a pinned-manifest to go back to. >> >> -Zach >> >> On 5 August 2011 18:04, Paul Sokolovsky wrote: >>> On Fri, 5 Aug 2011 17:12:50 +0200 >>> Alexander Sack wrote: >>> On Fri, Aug 5, 2011 at 4:13 PM, Paul Sokolovsky wrote: > On Fri, 5 Aug 2011 15:54:22 +0200 > Alexander Sack wrote: > >> ok. seems it really happened. >> >> https://android-build.linaro.org/jenkins/job/linaro-android_toolchain-4.6-2011.07/8/artifact/build/out/android-toolchain-eabi-linaro-4.6-2011.07-0-8-2011-07-25_12-42-06-linux-x86.tar.bz2 >> >> doesnt exist anymore even though its used as our official download >> url for release. >> >> Please figure out what changes landed after that official build, >> revert everything to the release state, respin, and ask paul to put >> the original binary manually back in place so the above URL becomes >> valid again? > > Well, it's built from the release tarball and the same patch, both > stay the same, so end result of the rebuild is the same, just at > different URL (build #12). I've updated daily jobs to use that, and > personal jobs should be updated by developers as needed. I dont think that build is the same. bero added changes somewhere etc. otherwise i doubt he would have respun the built. Please check with him. >>> >>> I see, that's indeed the case. So we apparently need to branch/tag >>> release builds for toolchain just the same as for the platform. In the >>> meantime, we with Bernhard are working on resolving this and bringing >>> original 11.07 build back up. >>> >>> >>> >>> -- >>> Best Regards, >>> Paul >>> >>> Linaro.org | Open source software for ARM SoCs >>> Follow Linaro: http://www.facebook.com/pages/Linaro >>> http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog >>> >> > ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
