* running git as root
@ 2009-06-13 15:25 Marco Nelissen
2009-06-13 15:42 ` Michael J Gruber
2009-06-13 17:49 ` Alex Riesen
0 siblings, 2 replies; 7+ messages in thread
From: Marco Nelissen @ 2009-06-13 15:25 UTC (permalink / raw)
To: git
When running as root, git fails a number of test cases that expect it
to fail on read-only repositories (for example 't0004-unwritable.sh').
I was thinking of either changing the code so that it checks
permissions itself when opening files as root, or add a prerequisite
to those test cases so that they are skipped when running as root.
What would be the preferred way?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: running git as root
2009-06-13 15:25 running git as root Marco Nelissen
@ 2009-06-13 15:42 ` Michael J Gruber
2009-06-14 1:42 ` Marco Nelissen
2009-06-13 17:49 ` Alex Riesen
1 sibling, 1 reply; 7+ messages in thread
From: Michael J Gruber @ 2009-06-13 15:42 UTC (permalink / raw)
To: Marco Nelissen; +Cc: git
Marco Nelissen venit, vidit, dixit 13.06.2009 17:25:
> When running as root, git fails a number of test cases that expect it
> to fail on read-only repositories (for example 't0004-unwritable.sh').
> I was thinking of either changing the code so that it checks
> permissions itself when opening files as root, or add a prerequisite
> to those test cases so that they are skipped when running as root.
> What would be the preferred way?
The preferred ways is to build git as non-root user. This is true even
more so for running the test suite.
Michael
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: running git as root
2009-06-13 15:42 ` Michael J Gruber
@ 2009-06-14 1:42 ` Marco Nelissen
0 siblings, 0 replies; 7+ messages in thread
From: Marco Nelissen @ 2009-06-14 1:42 UTC (permalink / raw)
To: git
On Sat, Jun 13, 2009 at 8:42 AM, Michael J
Gruber<git@drmicha.warpmail.net> wrote:
> Marco Nelissen venit, vidit, dixit 13.06.2009 17:25:
>> When running as root, git fails a number of test cases that expect it
>> to fail on read-only repositories (for example 't0004-unwritable.sh').
>> I was thinking of either changing the code so that it checks
>> permissions itself when opening files as root, or add a prerequisite
>> to those test cases so that they are skipped when running as root.
>> What would be the preferred way?
>
> The preferred ways is to build git as non-root user. This is true even
> more so for running the test suite.
This is not possible on BeOS, where there is only one user, and it is
the super user.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: running git as root
2009-06-13 15:25 running git as root Marco Nelissen
2009-06-13 15:42 ` Michael J Gruber
@ 2009-06-13 17:49 ` Alex Riesen
2009-06-14 1:41 ` Marco Nelissen
2009-06-14 6:08 ` Nanako Shiraishi
1 sibling, 2 replies; 7+ messages in thread
From: Alex Riesen @ 2009-06-13 17:49 UTC (permalink / raw)
To: Marco Nelissen; +Cc: git
2009/6/13 Marco Nelissen <marcone@xs4all.nl>:
> When running as root, git fails a number of test cases that expect it
> to fail on read-only repositories (for example 't0004-unwritable.sh').
> I was thinking of either changing the code so that it checks
> permissions itself when opening files as root, or add a prerequisite
> to those test cases so that they are skipped when running as root.
There is such a prerequisite already (POSIXPERM), but what caused
you to run the _tests_ as root?
> What would be the preferred way?
Use the prerequisite would sound right when not the
strangeness of the idea.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: running git as root
2009-06-13 17:49 ` Alex Riesen
@ 2009-06-14 1:41 ` Marco Nelissen
2009-06-14 6:08 ` Nanako Shiraishi
1 sibling, 0 replies; 7+ messages in thread
From: Marco Nelissen @ 2009-06-14 1:41 UTC (permalink / raw)
To: git
On Sat, Jun 13, 2009 at 10:49 AM, Alex Riesen<raa.lkml@gmail.com> wrote:
> 2009/6/13 Marco Nelissen <marcone@xs4all.nl>:
>> When running as root, git fails a number of test cases that expect it
>> to fail on read-only repositories (for example 't0004-unwritable.sh').
>> I was thinking of either changing the code so that it checks
>> permissions itself when opening files as root, or add a prerequisite
>> to those test cases so that they are skipped when running as root.
>
> There is such a prerequisite already (POSIXPERM), but what caused
> you to run the _tests_ as root?
POSIXPERM doesn't appear to be quite right for this. For example, the
't1301-shared-repo.sh' test has the POSIXPERM prereq, but it runs fine
as root, because it merely validates that permissions are preserved.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: running git as root
2009-06-13 17:49 ` Alex Riesen
2009-06-14 1:41 ` Marco Nelissen
@ 2009-06-14 6:08 ` Nanako Shiraishi
2009-06-14 21:40 ` Marco Nelissen
1 sibling, 1 reply; 7+ messages in thread
From: Nanako Shiraishi @ 2009-06-14 6:08 UTC (permalink / raw)
To: Alex Riesen; +Cc: Marco Nelissen, git
Quoting Alex Riesen <raa.lkml@gmail.com>:
> 2009/6/13 Marco Nelissen <marcone@xs4all.nl>:
>> When running as root, git fails a number of test cases that expect it
>> to fail on read-only repositories (for example 't0004-unwritable.sh').
>> I was thinking of either changing the code so that it checks
>> permissions itself when opening files as root, or add a prerequisite
>> to those test cases so that they are skipped when running as root.
>
> There is such a prerequisite already (POSIXPERM), but what caused
> you to run the _tests_ as root?
>
>> What would be the preferred way?
>
> Use the prerequisite would sound right when not the
> strangeness of the idea.
I think somebody needs to repost an old patch from the archive.
http://thread.gmane.org/gmane.comp.version-control.git/116729/focus=118385
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: running git as root
2009-06-14 6:08 ` Nanako Shiraishi
@ 2009-06-14 21:40 ` Marco Nelissen
0 siblings, 0 replies; 7+ messages in thread
From: Marco Nelissen @ 2009-06-14 21:40 UTC (permalink / raw)
To: Nanako Shiraishi; +Cc: Alex Riesen, git
On Sat, Jun 13, 2009 at 11:08 PM, Nanako Shiraishi<nanako3@lavabit.com> wrote:
> Quoting Alex Riesen <raa.lkml@gmail.com>:
>
>> 2009/6/13 Marco Nelissen <marcone@xs4all.nl>:
>>> When running as root, git fails a number of test cases that expect it
>>> to fail on read-only repositories (for example 't0004-unwritable.sh').
>>> I was thinking of either changing the code so that it checks
>>> permissions itself when opening files as root, or add a prerequisite
>>> to those test cases so that they are skipped when running as root.
>>
>> There is such a prerequisite already (POSIXPERM), but what caused
>> you to run the _tests_ as root?
>>
>>> What would be the preferred way?
>>
>> Use the prerequisite would sound right when not the
>> strangeness of the idea.
>
> I think somebody needs to repost an old patch from the archive.
>
> http://thread.gmane.org/gmane.comp.version-control.git/116729/focus=118385
That's almost identical to the patch I wanted to submit, except for
the name 'SANITY', which doesn't make much sense I think.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2009-06-14 21:40 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-13 15:25 running git as root Marco Nelissen
2009-06-13 15:42 ` Michael J Gruber
2009-06-14 1:42 ` Marco Nelissen
2009-06-13 17:49 ` Alex Riesen
2009-06-14 1:41 ` Marco Nelissen
2009-06-14 6:08 ` Nanako Shiraishi
2009-06-14 21:40 ` Marco Nelissen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).