this point was raised several times before, and it was opposed by
infra, so you'd need to ask them. Here I'm sure everybody is +1 ;)
On Tue, May 13, 2008 at 6:31 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> I've rewritten fix-permissions.sh to use absolute path
Raphaël Piéroni wrote:
+1 (obviously)
Dan, i will use the script after work.
where is fix-permission.sh located?
/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
It was originally just for fixing permissions in the
m2-snapshot-repository, but now you can run it there
+1 from me, if it's safe (I'm not qualified to say, personally).
-john
On May 13, 2008, at 9:31 PM, Dan Fabulich wrote:
I've rewritten fix-permissions.sh to use absolute paths for find
and chmod, and removed the "-user ${USER}" check. I believe this
modified sc
On Wed, May 14, 2008 at 3:31 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> >
> > I've rewritten fix-permissions.sh to use absolute paths for find and
> > chmod, and removed the "-user ${USER}" check. I believe this modified
> > script should be
+1 to have this very useful script to unblock us with these annoying
problems of permissions.
Arnuad
On Wed, May 14, 2008 at 3:31 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
>
> I've rewritten fix-permissions.sh to use absolute paths for find and
> chmod, and removed the &
I've rewritten fix-permissions.sh to use absolute paths for find and
chmod, and removed the "-user ${USER}" check. I believe this modified
script should be safe to be configured setuid root. That way, anybody
could run it and clean up anyone's fix-permissions errors, e
han
a simple setuid wrapper script, that just takes a user as a command line
argument and runs fix-permissions.sh as that user. Maybe they'd like that
better?
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Mauro Talevi wrote:
Brian E. Fox wrote:
Good idea. Is the script still there? I seemed to have a hard time
finding it.
/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
I think we should move it one level up.
And possibly enhance script to take repo name as mandatory
Brian E. Fox wrote:
Good idea. Is the script still there? I seemed to have a hard time
finding it.
/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
I think we should move it one level up.
-
To
eleasing Maven Surefire due to permissions.
Right now it's every developer's responsibility to run fix-
permissions
when he/she deploys. This creates a problem, because it's easy for
developers to forget to run the script and get other later developers
in trouble.
It seems lik
ix-permissions
> > when he/she deploys. This creates a problem, because it's easy for
> > developers to forget to run the script and get other later developers
> > in trouble.
> >
> > It seems like it'd be better to make fix-permissions.sh a setuid roo
Good idea. Is the script still there? I seemed to have a hard time
finding it.
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Monday, January 14, 2008 6:39 PM
To: Maven Developers List
Subject: fix-permissions.sh
I'm blocked from releasing Maven Surefire d
he script and get other later developers
> in trouble.
>
> It seems like it'd be better to make fix-permissions.sh a setuid root
> script that can fix permissions wherever they're broken, so it can by
> run by t
rs in
trouble.
It seems like it'd be better to make fix-permissions.sh a setuid root
script that can fix permissions wherever they're broken, so it can by run
by the people currently suffering.
Good idea? Bad idea?
-Dan
--
14 matches
Mail list logo
