Apache OpenOffice (AOO) Bugzilla – Issue 126
no update for OpenOffice alias possible
Last modified: 2003-12-06 14:52:32 UTC
Once you've have done a checkout of the OpenOffice alias, you are not able to do an update to that alias. You have to update each module seperatly
Reassigned to jeremy for ownership (to coordinate support from chris toward resolution) Please verify this has been resolved, then close issue.
Martin, I am trying to verify and resolve old issues, is this still a problem? --jeremy
Martin is not in office, but... Yes, this is still a problem. We recommend in the build manual to do an initial cvs co -rOpenOffice609 OpenOffice OpenOffice is a CVS alias in the modules file. To update you have to cvs update <module> <module> ... and can't just cvs update
I found in some documentation re: alias based checkouts that CVS checkout takes a module name (and thusly an alias to those modules) whereas update takes a directory name (or a string of individual modules). I'm assuming that you *should* be able to update by the name of, or from w/i the uppermost directory where you have your repository checked out to locally. Would this make sense? Also, was your local repository created by your first co? Or did you set-up your repository and co into (the difference being certain update functions only work from the top most dir on repositories existing before the initial checkout.) I am continuing to work this issue, please let me know if any of this helps. --jeremy
To transfer jeremy's issues and as this relates to the technical infrastructure, reassigning to kat for ownership (to coordinate technical support as required toward resolution).
Hi, Has this issue been resolved or does it require further investigation? Kat
closing due to lack of activity.
Sorry for the late answer. This issue has not been resolved yet. User would expect that after the initial checkout of some module, the specification of CVSROOT is not needed anymore. But in the root directory there are nore CVS admin files and so the user has to specifiy CVSROOT again. so a simple cvs update <module> does not work. and a cvs update without any parameters doesn't work, too.
I got some more strong requests for that feature -> P2
I will investigate this further.
Kat, this might give you some more tests to run to figure out if this will solve hte problem or not ok I am going to assume Linux here...but I think that is what Martin is using anyway..I don't know how to do what I am going to tell you to do with wincvs. with bash: export CVSROOT=<insert proper cvs root here> cvs co OpenOffice (in the same window so the CVSROOT env var is still set and in the same directory that you just checked the files out into) cvs update History: this might work as the cvs client looks at the CVSROOT env var to see how to update directories that it doesn't know exactly where they came from....this (*might*) work...this is info only for Kat...but might be helpful.
Ref 4492 internal. The behavior is improper and will be adressed by the upgrade if not sooner. I am sorry for the delay on this issue. Kat
Our cvs engineer has clarified the difficulties here for me. I appologize for my earlier confusion on this. The reason it is not updating the alias is that there is no CVS/Repository value associated with it, and the only one that could possibly be associated is /, and then he reports there could be difficulties with permissions. A work around he proposed is that within the checkout directory (ex. Openoffice) running a script that would go through and update each directory (this is in bash): for dir in * ; do ( cd $dir ; cvs update ) ; done Based on this information I am marking the issue resolved. Thank you Kat
As mentioned on the qa dev list on March 5th I will close all resolved duplicate 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.