You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ak...@apache.org> on 2007/07/26 03:28:15 UTC
[m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Enrique,
You have files in the m2 snapshot repo from a deploy which need to have the
group rw permissions
added to them here on people.apache.org:
/www/people.apache.org/repo/m2-snapshot-repository
Please fix this. Make sure you massage permissions on each deployment.
We need to either fix maven's deploy plugin or make sure we massage
permissions after each deploy.
I think Trustin had a fix for it at some point but I don't think the maven
guys incorporated it.
Alex
Re: [m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Posted by Emmanuel Lecharny <el...@gmail.com>.
Thanks David !
I successfully deployed shared-xxx with the settings-xml you provided.
Saddly, the <password> setting does not work... I will have to copy my
laptop private key on people.a.o.
E.
On 7/27/07, David Jencks <da...@yahoo.com> wrote:
> <settings>
> <servers>
> <server>
> <id>apache-snapshots</id>
> <username>your-apache-username</username>
> <passphrase>ssh-passphrase</passphrase>
> <directoryPermissions>775</directoryPermissions>
> <filePermissions>664</filePermissions>
> </server>
> <server>
> <id>apache.snapshots</id>
> <username>your-apache-username</username>
> <passphrase>ssh-passphrase</passphrase>
> <directoryPermissions>775</directoryPermissions>
> <filePermissions>664</filePermissions>
> </server>
> </servers>
> </settings>
>
> might work. If your apache username is the same as your local
> username it can be ommitted. If you don't have an ssh passphrase it
> can be ommitted. I didn't look to see how apacheds identifies the
> snapshot repo, but you only need the entry for the id actually used :-)
>
> hope this helps
> david jencks
>
> On Jul 27, 2007, at 12:11 AM, Emmanuel Lecharny wrote:
>
> > Hi,
> >
> > I just have to deploy shared, but I don't have my usual computer. Can
> > someone provide me a settings.xml file ?
> >
> > Thanks !
> >
> > On 7/27/07, Enrique Rodriguez <en...@gmail.com> wrote:
> >> On 7/25/07, David Jencks <da...@yahoo.com> wrote:
> >>> we did a couple of experiments here and we think you need to:
> >>>
> >>> set umask 2 in .bashrc. For non-interactive remote shell access
> >>> such as
> >>> through scp this is the file executed, not .bash_profile
> >>>
> >>> in ~/.m2/settings.xml set
> >>>
> >>> <directoryPermissions>775</directoryPermissions>
> >>> <filePermissions>664</filePermissions>
> >>> for each repository you are deploying to. We're not so sure
> >>> about the 2nd
> >>> point, but this works for me and we found that the source file
> >>> permissions
> >>> do have an effect on the target file permissions together with
> >>> the umask,
> >>> and these settings affect what maven presents as the source file
> >>> permissions.
> >>
> >> The combination of both of these settings (.bashrc && settings.xml)
> >> worked for me. Nice!
> >>
> >> With just umask it didn't work.
> >>
> >> Enrique
> >>
> >
> >
> > --
> > Regards,
> > Cordialement,
> > Emmanuel Lécharny
> > www.iktek.com
>
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Posted by David Jencks <da...@yahoo.com>.
<settings>
<servers>
<server>
<id>apache-snapshots</id>
<username>your-apache-username</username>
<passphrase>ssh-passphrase</passphrase>
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
</server>
<server>
<id>apache.snapshots</id>
<username>your-apache-username</username>
<passphrase>ssh-passphrase</passphrase>
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
</server>
</servers>
</settings>
might work. If your apache username is the same as your local
username it can be ommitted. If you don't have an ssh passphrase it
can be ommitted. I didn't look to see how apacheds identifies the
snapshot repo, but you only need the entry for the id actually used :-)
hope this helps
david jencks
On Jul 27, 2007, at 12:11 AM, Emmanuel Lecharny wrote:
> Hi,
>
> I just have to deploy shared, but I don't have my usual computer. Can
> someone provide me a settings.xml file ?
>
> Thanks !
>
> On 7/27/07, Enrique Rodriguez <en...@gmail.com> wrote:
>> On 7/25/07, David Jencks <da...@yahoo.com> wrote:
>>> we did a couple of experiments here and we think you need to:
>>>
>>> set umask 2 in .bashrc. For non-interactive remote shell access
>>> such as
>>> through scp this is the file executed, not .bash_profile
>>>
>>> in ~/.m2/settings.xml set
>>>
>>> <directoryPermissions>775</directoryPermissions>
>>> <filePermissions>664</filePermissions>
>>> for each repository you are deploying to. We're not so sure
>>> about the 2nd
>>> point, but this works for me and we found that the source file
>>> permissions
>>> do have an effect on the target file permissions together with
>>> the umask,
>>> and these settings affect what maven presents as the source file
>>> permissions.
>>
>> The combination of both of these settings (.bashrc && settings.xml)
>> worked for me. Nice!
>>
>> With just umask it didn't work.
>>
>> Enrique
>>
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
Re: [m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi,
I just have to deploy shared, but I don't have my usual computer. Can
someone provide me a settings.xml file ?
Thanks !
On 7/27/07, Enrique Rodriguez <en...@gmail.com> wrote:
> On 7/25/07, David Jencks <da...@yahoo.com> wrote:
> > we did a couple of experiments here and we think you need to:
> >
> > set umask 2 in .bashrc. For non-interactive remote shell access such as
> > through scp this is the file executed, not .bash_profile
> >
> > in ~/.m2/settings.xml set
> >
> > <directoryPermissions>775</directoryPermissions>
> > <filePermissions>664</filePermissions>
> > for each repository you are deploying to. We're not so sure about the 2nd
> > point, but this works for me and we found that the source file permissions
> > do have an effect on the target file permissions together with the umask,
> > and these settings affect what maven presents as the source file
> > permissions.
>
> The combination of both of these settings (.bashrc && settings.xml)
> worked for me. Nice!
>
> With just umask it didn't work.
>
> Enrique
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Posted by Enrique Rodriguez <en...@gmail.com>.
On 7/25/07, David Jencks <da...@yahoo.com> wrote:
> we did a couple of experiments here and we think you need to:
>
> set umask 2 in .bashrc. For non-interactive remote shell access such as
> through scp this is the file executed, not .bash_profile
>
> in ~/.m2/settings.xml set
>
> <directoryPermissions>775</directoryPermissions>
> <filePermissions>664</filePermissions>
> for each repository you are deploying to. We're not so sure about the 2nd
> point, but this works for me and we found that the source file permissions
> do have an effect on the target file permissions together with the umask,
> and these settings affect what maven presents as the source file
> permissions.
The combination of both of these settings (.bashrc && settings.xml)
worked for me. Nice!
With just umask it didn't work.
Enrique
Re: [m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Posted by David Jencks <da...@yahoo.com>.
we did a couple of experiments here and we think you need to:
set umask 2 in .bashrc. For non-interactive remote shell access such
as through scp this is the file executed, not .bash_profile
in ~/.m2/settings.xml set
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
for each repository you are deploying to. We're not so sure about
the 2nd point, but this works for me and we found that the source
file permissions do have an effect on the target file permissions
together with the umask, and these settings affect what maven
presents as the source file permissions.
this is all too easy to mess up -- a lot of geronimo comitters have
problems with this too.
thanks
david jencks
On Jul 25, 2007, at 8:57 PM, Alex Karasulu wrote:
> You know we did do this or at least I know a few of us did it but
> we still get this issue.
> It's very strange. I have 'umask 0002' in my .bash_profile which
> is equivalent to having
> it in .cshrc when using bash shell.
>
> Alex
>
> On 7/25/07, David Jencks <da...@yahoo.com> wrote:
> If you set umask to 2 (not 22) on people.apache.org you won't have
> this problem. You have to set it in the place so it works for ssh
> access. For me that is in .cshrc
>
> thanks
> david jencks
>
> On Jul 25, 2007, at 6:28 PM, Alex Karasulu wrote:
>
>> Enrique,
>>
>> You have files in the m2 snapshot repo from a deploy which need to
>> have the group rw permissions
>> added to them here on people.apache.org:
>>
>> /www/people.apache.org/repo/m2-snapshot-repository
>>
>> Please fix this. Make sure you massage permissions on each
>> deployment.
>>
>> We need to either fix maven's deploy plugin or make sure we
>> massage permissions after each deploy.
>> I think Trustin had a fix for it at some point but I don't think
>> the maven guys incorporated it.
>>
>> Alex
>>
>>
>
>
Re: [m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Posted by Alex Karasulu <ak...@apache.org>.
You know we did do this or at least I know a few of us did it but we still
get this issue.
It's very strange. I have 'umask 0002' in my .bash_profile which is
equivalent to having
it in .cshrc when using bash shell.
Alex
On 7/25/07, David Jencks <da...@yahoo.com> wrote:
>
> If you set umask to 2 (not 22) on people.apache.org you won't have this
> problem. You have to set it in the place so it works for ssh access. For
> me that is in .cshrc
> thanks
> david jencks
>
> On Jul 25, 2007, at 6:28 PM, Alex Karasulu wrote:
>
> Enrique,
>
> You have files in the m2 snapshot repo from a deploy which need to have
> the group rw permissions
> added to them here on people.apache.org:
>
> /www/people.apache.org/repo/m2-snapshot-repository
>
> Please fix this. Make sure you massage permissions on each deployment.
>
> We need to either fix maven's deploy plugin or make sure we massage
> permissions after each deploy.
> I think Trustin had a fix for it at some point but I don't think the maven
> guys incorporated it.
>
> Alex
>
>
>
>
>
Re: [m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Posted by David Jencks <da...@yahoo.com>.
If you set umask to 2 (not 22) on people.apache.org you won't have
this problem. You have to set it in the place so it works for ssh
access. For me that is in .cshrc
thanks
david jencks
On Jul 25, 2007, at 6:28 PM, Alex Karasulu wrote:
> Enrique,
>
> You have files in the m2 snapshot repo from a deploy which need to
> have the group rw permissions
> added to them here on people.apache.org:
>
> /www/people.apache.org/repo/m2-snapshot-repository
>
> Please fix this. Make sure you massage permissions on each deployment.
>
> We need to either fix maven's deploy plugin or make sure we massage
> permissions after each deploy.
> I think Trustin had a fix for it at some point but I don't think
> the maven guys incorporated it.
>
> Alex
>
>
Re: [m2-snapshot-repo] Permissions need to be massaged to allow group read write access
Posted by Enrique Rodriguez <en...@gmail.com>.
OK, done. I'm aware of the issue and (usually) remember to 'chmod'
after each deploy.
Enrique
On 7/25/07, Alex Karasulu <ak...@apache.org> wrote:
> Enrique,
>
> You have files in the m2 snapshot repo from a deploy which need to have the
> group rw permissions
> added to them here on people.apache.org:
>
> /www/people.apache.org/repo/m2-snapshot-repository
>
> Please fix this. Make sure you massage permissions on each deployment.
>
> We need to either fix maven's deploy plugin or make sure we massage
> permissions after each deploy.
> I think Trustin had a fix for it at some point but I don't think the maven
> guys incorporated it.
>
> Alex
>
>
>