Apache OpenOffice (AOO) Bugzilla – Issue 1686
Several developers are no longer able to add new directories
Last modified: 2003-12-06 14:52:32 UTC
Trying to add a directory in installation/setup2/script/linux called 1.1.1 I got the following error message: cvs.clt2 add: warning: unrecognized response `DBD::mysql::st execute failed: You have an error in your SQL syntax near ')' from cvs server cvs.clt2 add: warning: unrecognized response ` and HELM_ACTION.NAME = "VersionControl - Add"' from cvs server cvs.clt2 add: warning: unrecognized response ` and HELM_ROLE.ROLE_ID ' at line 9 at /var/svscan/tigris-cvs-pserver/pcheck.pl line 250.' from cvs server cvs.clt2 add: 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 hr doesnt have <Add> access to project 1.1.1 cvs.clt2 [add aborted]: there is a version in 1.1.1 already It seems that for some reason CVS tries to add something to a projet of the same name as the directory. Developer Hans-Joachim Lankenau (hjs) had a similar problem yesterday, in that case I (hr) was able to add that directory. Now I've this problem but Martin Hollmichel (mh) is is able to add the directory.
added CC
I was not able to reproduce this behavior with my account, but it's possible that there is another trigger for this defect once one already has developer permissions in a project - hr mentioned that he previously had been able to add a directory and now can no longer. Our engineers are looking at this now. This has been assigned internally as PCN 5769. This is also being changed to a P2 priority, as this is not a critical businees impairment - a workaround is to simply have another user create the directories in the meantime.
Update: Further research has been done on this defect, and we believe it's related to a CVS empty perl query that we've seen before in other situations. There is some speculation that an upgrade to version 1.1 of CVS will fix this - this is going into testing.
Hi, This may be addressed in the short term by the affected users changing their passwords, and has worked in other cases of permissioning problems. However, we are still looking into the root cause. Thank you Kat
We are not able to reproduce this error (neither on SC 1.0.8 nor 1.1).
closing - this one can be reopened if the issue reappears.