Oh shit! It seems Subversion/Subclipse did not like that renaming at all. While on my system everything looked ok (no local modification were shown with Subclipse, svn up on the command line just said everything ok), there are indeed now 2 files of each license.txt and notice.txt. in different cases. Only the lowercase versions should exist.

And the thing is: It seems I can't fix it since I'm using Windows as well. I deleted that directory for test cases. Now when failing with the update SVN leaves this directory in a completely inconsistent state (thought it is some kind of transactional??). I don't know how to change that, tried unlock and cleanup which neither allow me to delete NOTICE.txt and LICENSE.txt afterwards.

So can anybody with a case-sensitive file system please fix this problem for me? Or do we need infrastructure?

Sorry for any inconveniences. And sorry, Markus, for insisting on a problem to be fixed on your side.

Joerg

On 24.04.2007 20:58, Josias Thöny wrote:

the issue itself (change file name to lower case for license.txt and notice.txt) has been fixed in SVN. Unfortunately, this leads to the behaviour you observed, there is no way to influence the order of SVN actions (first delete old version, later check out new version). There is no other way than deleting the template block before updating or doing the update multiple times as it seems to have worked for you.

I'm using windows for testing and I'm having the same problem. However, I cannot fix it. Neither deleting the directory nor multiple updates seem to work. I'm using subversion command line client 1.4.3.

From your mails it seems you wanted to rename the files from upper to lower case. But the repository now contains both the upper- and lower case files, see:

http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/src/blocks/template/resources/META-INF/
I think that just doesn't work with windows.
Are the uppercase files still needed?

Josias


Regards
Joerg

On 23.04.2007 21:25, Markus Angst wrote:
Hello,

There is a problem in the Cocoon SVN repository that probably only affects Windows users. There are four files in /src/blocks/template/resources/META-INF/:

LICENSE.txt, NOTICE.txt, license.txt and notice.txt.

As case doesn't matter for Windows, this creates problems on checking out and updating Lenya. It seems to be possible to work around it temporarily by updating three times, but this is annoying and should be corrected imho.

Thanks!
Markus Angst

PS: I will not be reading the Cocoon mailing list. If you have questions please send a cc to the Lenya mailing list. Thanks!


update -r HEAD C:/lenya/lenya-1.4-dev
Updating external location at: C:/lenya/lenya-1.4-dev/externals/cocoon_2_1_x
     Command completed abnormally.
     svn: Error aborting report
svn: Cannot read from to
'C:\lenya\lenya-1.4-dev\externals\cocoon_2_1_x\src\blocks\template\resources\META-INF\.svn\text-base\LICENSE.txt.svn-base':
path refers to directory or read access is denied
     Updating external location at:
C:/lenya/lenya-1.4-dev/src/modules/bxe/resources/bxe
     At revision 1659.
     Updating external location at:
C:/lenya/lenya-1.4-dev/src/modules/kupu/resources/kupu
     At revision 42274.
     At revision 531560.

update -r HEAD C:/lenya/lenya-1.4-dev
Updating external location at: C:/lenya/lenya-1.4-dev/externals/cocoon_2_1_x
     Restored
C:/lenya/lenya-1.4-dev/externals/cocoon_2_1_x/src/blocks/template/resources/META-INF/notice.txt
     Command completed abnormally.
     svn: Error aborting report
svn: Cannot read from to
'C:\lenya\lenya-1.4-dev\externals\cocoon_2_1_x\src\blocks\template\resources\META-INF\.svn\text-base\NOTICE.txt.svn-base':
path refers to directory or read access is denied
     Updating external location at:
C:/lenya/lenya-1.4-dev/src/modules/bxe/resources/bxe
     At revision 1659.
     Updating external location at:
C:/lenya/lenya-1.4-dev/src/modules/kupu/resources/kupu
     At revision 42274.
     At revision 531560.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to