Created attachment 46505 [details]
public ssh2 key

Nurali,

What project is this for?

louis

For native language support to access cvs account

Of course. So, to elaborate, this is for the Uzbeki language project, and you are the lead. (I tend to have a 
lousy memory; my apologies.)

Support, please ask ops to upload this key.

Thanks
louis

Hi,

Thank you for contacting CollabNet Customer Support. Based on the information
that has been provided to us, we will initiate this task & provide you an update
as soon as we have adequate information. 

Thanks,
Harsha
Support Operations.

The public key has been uploaded. Please do verify the same and let me know can
I proceed to close the case.

Thanks,
Harsha
Support Operations.

I make a connection with openoffice.org via ssh tunnel. And checked out uzbek 
project. I edited www/index.html but cannot commit this changes. i use 
cervisia to commit changes. Error was: CVS: * Please send an email TO: the 
submitter 
CVS: (particularly, if from outside Sun) 
CVS: advising that the code has been committed, 
CVS: and gratefully recognizing the contribution. 
' 'www/index.html' 2>&1
cvs [server aborted]: "commit" requires write access to the repository
[Exited with status 1]

Anybody can guide me?

Hi.

Today under windows i committed my changes. But under linux couldn't. Harsha 
public key worked. 

Hi Nurali,

It seems that you are able to commit the changes in windows platform but not in
linux. So,can you please send me the error message if you are still facing in linux.

Thanks,
Harsha
Support Operations. 

In linux also committed.

So, I have translated po files and  creat uz.sdf file. To whom I should send
this file? What i need do next?

nurali:

Let's keep issues distinct :-)

So, you can commit changes to cvs both in Linux and Windows? Great. Let's close this issue.


As to procedures for l10n work, please use the dev@l10n.openoffice.org. You might also want to query 
us on IRC (irc.freenode.net, #dev.openoffice.org)

thanks
louis

Yes, you may close this issue.

rosolving as discussed in jabber

closing