Issue 57

Summary: If I check out OpenOffice, there's a problem with solenv/inc/startup/macosx/macros.mk.
Product: Infrastructure Reporter: issues@www <issues>
Component: _openoffice.org CVS (obsolete)Assignee: Unknown <non-migrated>
Status: CLOSED FIXED QA Contact: issues@www <issues>
Severity: Trivial    
Priority: P3 CC: issues, nesshof, pluby
Version: current   
Target Milestone: ---   
Hardware: PC   
OS: Windows NT   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description issues@www 2000-10-25 18:25:25 UTC 
It seems that CVS tries to checkout MACOSX/macros.mk and then macosx/macros.mk. 
On WinNT this results in CVS stating, that it moves away macros.mk, when 
checking out macosx/macros.mk.
On Unix this would be not a problem, but Windows filesystems are not
case sensitive.
Comment 1 Unknown 2000-10-25 18:32:31 UTC 
This issue is with solenv rather than the WWW project.
Patrick Luby doesn't seeem to have an Issuezilla acccount orI would
assign to him.
Comment 2 Martin Hollmichel 2000-10-31 18:31:43 UTC 
I don't know exactly what the problem is. I guess that there is a starup/macosx 
and a MACOSX tree on the cvs server. I can't reproduce this on our cvs mirror.

Shane, can you please check the tree and communicate with patrick what has to 
be done.
Comment 3 pluby 2000-10-31 18:57:15 UTC 
Shane,



This can only be solved by removing the solenv/inc/startup/macosx directory from 

the CVS tree. Unfortunately, cvs remove will leave the directory so it must be 

permanently purged from the CVS tree. Also, don't worry about the purging as that 

directory is an exact duplicate of the solenv/inc/startup/MACOSX directory.



Patrick
Comment 4 Unknown 2000-11-01 13:19:37 UTC 
As requested, I have removed the macosx dir from the server.
Comment 5 michael.bemmer 2003-03-24 08:23:42 UTC 
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.
Comment 6 michael.bemmer 2003-03-24 08:28:09 UTC 
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.