Apache OpenOffice (AOO) Bugzilla – Issue 831
Problems with an entire subdir...
Last modified: 2003-12-06 14:52:32 UTC
Although I have just checked out the whole 5.2 subdir on my laptop (I am using wincvs). ALthough everything sems to be fine... Whwnever you try to access any document inside the sdk1.0 subtree, you always get an empy page and the message inside the html states: !-- Servlet-Specific template --> <!-- WARNING: Include: Error reading file /usr/local/tigris/data/helm/htdoc/api/www//5.2/sdk1.0/SOapi1.0/com/sun/star/xml/ sax.html --> This is happening with all the files in sdk1.0 subdir. The other one , which I did just in the same way, "reference" is ok. Please help! I have been fiddling with this for almost a week to no point.. Thanks Max
Assigning to Kat for fisrt-level technical support
Accepting the issue and will engage other resources as necessary. It appears that the files are in /cvs/api/www/5.2/sdk1.0 but not in /usr/local/tigris/data/helm/htdocs on the server. I will keep you updated of the progress of this issue. Thank you Kat
Tracking as issue 3890 pcn.
Kat, Please remember to give regular updates here, since Max does not have access to PCN (Max - PCN is projects.collab.net, an internal issue tracking area where we track SourceCast, Tigris, etc issues)
Were the CVS files in this project unpacked from a tar file? There remains a strange problem with at least some files, including eg. api/www/common/ref/global-index-b.html. The comment in the logs in /cvs/ for this file says the last revision is 1.2 and the comment corresponding to that revision says: top level build from 5/4/2001 The first log entry says: revision 1.1 date: 2001/03/28 14:50:53; author: mi; state: Exp; new checkin after repository was cleared If I understand correctly, the suggestion is that /cvs/api/www was cleared out, but /usr/local/tigris/data/helm/htdoc/api/www was not. That guess matches with the timestamps in the files in /usr/local/tigris/data/helm/htdoc, which date to before 2001/03/28. If this is what was done, then it is no surprise that the system is not working correctly; it is almost never correct to physically delete the ,v files and start fresh. The procedure described above is one which should be expected to fail. A more reasonable procedure would have been to use cvs to delete all the files (cvs delete -f -r), do cvs commit, and then add the new versions of the files. This will help ensure that anyone who has checked out a copy of the CVS tree will be able to update correctly. Anyway, I've triggered an update to the 5.2/sdk1.0 stuff -- but I haven't addressed the other issues caused by the problems described above. Doing so will involve blowing away whatever is currently there and replacing it with the stuff in CVS: is that alright? I'm guessing the answer is yes, but want to make sure before I make such changes on the live site.
> Doing so > will involve blowing away whatever is currently there and replacing > it with the stuff in CVS: is that alright? I'm guessing the answer is yes, > but want to make sure before I make such changes on the live site. Yes, please do that at your easieset convenience. Thank you for the good hints.
Hi Ed, Thank you for your help. That worked just ok. That also teached me a lesson with CVS :-| Would you please trigger the same update you did for 5.2/skd1.0 for 5.2/reference,too ? Thank you and apologies for the extra work. Max
Max, Does the update still need to be triggered for 5.2/reference or is everything working for you? I had some feedback from an engineer here that everything appeared to be ok. Thank you Kat
Yep, I still need it. It may look as it is ok. But there are a bunch of files missing. Please do trigger the update for reference as required. Thanks. Max
Did a clean checkout under /usr/local/tigris/data/helm/htdoc/api/www/5.2/reference. Max, please close the issue unless you'd like me to do more.
Perfect!. Thanks. Max
Closing issue.