http://bugs.meego.com/show_bug.cgi?id=5610
pohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #1 from pohly <[email protected]> 2010-08-23 01:55:04 PDT --- (In reply to comment #0) > Second, runtest.py intentionally contains [email protected]:<something> as > repo > URL for SyncEvolution and Synthesis. The purpose is that it allows the > following work flow: > - make some change on the test machine in /work/runtests/head > - as user "nightly": run tests > - as normal user: commit to gitorious.org commit 4a52bd669fbfbef80f6122eabbe33cef6d706e2d Author: Patrick Ohly <[email protected]> Date: Mon Aug 23 10:10:59 2010 +0200 runtests.py: avoid ssh access to gitorious.org in nightly checkout The nightly test account only has anonymous read access to gitorious.org via the git:// protocol. But for normal users patching the files, access via ssh is needed to commit changes. Work around this by temporarily patching the URL for origin. "git remote set-url" would be more elegant than Perl, but only recent git versions have that. > Permissions should be set such that this shared access to /work/runtests is > possible. commit 155a3490145eb53c122bcd8fcb3eff1aff059ea6 Author: Patrick Ohly <[email protected]> Date: Mon Aug 23 10:44:50 2010 +0200 runtests.py: make repos group-writable The usage model for the nightly repos is that the "nightly" user updates them and other users modify them to try out changes before committing them. This relies on group-writable repos. Despite umask 0002 and drwxrwsr-x permissions of the work area this didn't work, group only had read permission. This patch adds an explicit chmod and sets "sharedRepository = group" to fix this after a fresh clone. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
