Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | cvs co -rOO641C helpcontent not possible, useless error messages | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Martin Hollmichel <nesshof> |
Component: | _openoffice.org CVS (obsolete) | Assignee: | Unknown <non-migrated> |
Status: | CLOSED FIXED | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P1 (highest) | CC: | issues, stx123, zahedab2 |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- | ||
Issue Depends on: | |||
Issue Blocks: | 2308 |
Description
Martin Hollmichel
2001-11-29 13:39:07 UTC
*** Issue 2336 has been marked as a duplicate of this issue. *** in CVSROOT/val-tags there is no OO641C It seems, that a newly created tag it maintained in CVSROOT/valtags anymore. that means that we are not able any more to use new tags. Hi Martin, On which server is this? When attempting the command you specified on openoffice.org I received no error message: [kat@dhcp113 kat]$ cvs -d :pserver:kat@localhost:/cvs co -rOO641C OpenOffice cvs server: Updating helpcontent cvs server: Updating helpcontent/prj U helpcontent/prj/build.lst U helpcontent/prj/d.lst cvs server: Updating helpcontent/unx cvs server: Updating helpcontent/unx/common <snip> I found similar behavior on anoncvs.openoffice.org (a checkout proceeded, no immediate assertion failures as you reported). Could you please attempt the checkout again and see if you receive the same error? Thank you Kat It seems that somehow the OO641C tag is in the CVSROOT/val-tags file. checkout of OO641C is working now. It is not working for all the other tags we introduced since Tuesday evening and it still does not work for new created tags. Martin, Could you please give examples of these tags? Do you notice any pattern to this point? I will enter the issue for internal investigation. Thank you Kat I have tagged the test module with mh_test_OO a few minutes ago. I see the error now. Entered as pcn6723, I will keep you updated on it's progress. Thank you Kat Any news? The developers working on this believe they have the failure tracked to a new way we are doing /cvs symlink translation, but do not yet have a well tested solution. The developer is estimating end of day Wednesday for a fix to this issue. This does not take into account release engineering, staging and qa. The fix to the symlink issue should ge smoothly into the current version, but I can provide a better estimate of time to site once the fix is completed. The original issue has been addressed by the engineers, but has exposed another issue that they are continuing to work on into tonight. As soon as the final code changes have been made they will be tagged and pushed to the staging server. The secondary issue is still being worked on as of this evening. It is felt a solution is close at hand though, and I will keep you updated on progess. Thank you Kat A fix to the secondary issue is being tested by the developers today. If all tests pass this will be ready to proceed to release engineering and be staged. I will keep you updated on its status. Thank you Kat The fix did not pass all tests to the satisfaction of the developers. They have now switched to the secondary stradegy where val-tags is written to earlier than at first checkout. Kat A patch based on the secondary strategy has been committed. The backport to 1.1 has been requested, after which it will go to release engineering and be staged for further testing. Kat We are currently in the process of internal debugging prior to opening up for wider testing. This phase is planned for completion end of day tomorrow, but may have to be extended if major issues arise. Kat The preliminary debugging has been done and a new cvs rpm has been installed on the staging server for further testing. Kat tagging on the staging box seems to be ok, as far as I see, all the other cvs commands are still working ;-). If all are agreed then we can proceed with this update to the production server. There will be no downtime required, as it involves only an rpm install and a restart of the pserver which should not affect cvs sessions. Thank you Kat The new cvs rpm has been installed on the production site as was discussed on the call this morning to address this issue. I am marking the issue resolved. Please reopen the issue if there are any problems. Thank you Kat As agreed by Louis I will close these resolved fixed kat (support)-owned issues now. If you have trouble with that, please re-open the issue. As agreed by Louis I will close these resolved fixed kat (support)-owned issues now. If you have trouble with that, please re-open the issue. |