Apache OpenOffice (AOO) Bugzilla – Issue 2206
Can't cvs update using ssh tunnel
Last modified: 2003-12-06 14:52:32 UTC
A cvs update in e.g. sal fails: cvs server: Updating . cvs update: warning: unrecognized response `DBD::mysql::st execute failed: You have an error in your SQL syntax near ')' from cvs server cvs update: warning: unrecognized response ` and HELM_ACTION.NAME = "VersionControl - Update"' from cvs server cvs update: warning: unrecognized response ` and HELM_ROLE.ROLE_' at line 9 at /var/svscan/tigris-cvs-pserver/pcheck.pl line 250.' from cvs server cvs update: warning: unrecognized response `DBD::mysql::st fetchrow_arrayref failed: fetch() without execute() at /var/svscan/tigris-cvs-pserver/pcheck.pl line 252.' from cvs server User mrauch doesnt have <Update> access to project oo cvs server: Updating systools cvs [server aborted]: cannot make directory /usr/local/anoncvs/locks/CVSROOT/Emptydir: Permission denied cvs [server aborted]: cannot make directory /usr/local/anoncvs/locks/CVSROOT/Emptydir: Permission denied My actions before have been: Setup ssh tunnel: ssh -x -g -2 -L 2401:localhost:2401 tunnel@openoffice.org In another shell: cd /usr/src/openoffice/salexport CVSROOT=:pserver:mrauch@localhost:/cvs cvs login [entered password] cvs update -d -P -r OO641B . A cvs checkout went successfully, as well as an update using the anoncvs@anoncvs.openoffice.org server. Some modules however do work, e.g. helpcontent. (I haven't really found a pattern; it *might* be that directories added after the move to tigris work and those before don't.)
Hi, Do you have a directory with modules from mixed checkout locations (for example both anoncvs.openoffice.org and openoffice.org through the tunnel)? I have gotten the error you describe when this is the case on my machine and I am not logged in to the other location, and the portion of the error 'User mrauch doesnt have <Update> access to project oo' which I know preceeds each module on the anoncvs server. If this is not the case, any further information you could provide would be helpful. Thank you Kat
Yes, that was the problem.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.