Re: [fossil-users] Uppercase/lowercase issue on Windows

2015-01-05 Thread Robert Engelhardt

Hello,


Please do (and thanks for asking!).


I've done so (ticket d6d16fe1aa), but according to Richard's comment 
this seems to be an issue without an (easy) fix. So we have to live with 
it :)


However, as an update for others who stumble upon this, I found a (not 
so magic) workaround:


1. (Temporarily) enable case sensitivity.
2. Do all necessary A - a or a - A renames required to 
synchronize the duplicate file and/or folder names.

3. Commit and (if desired) disable case sensitivity again.

For me this fixed the problem for the current (and future) checkins and 
the display of their contents. Of course in the all files view the 
problem is still visible for checkins in the past, but that doesn't 
bother me.



Forewarning, though: if i'm not mistaken, only a couple of the fossil
devs work on it in Windows (resp. case insensitively).


That's why we (few) Windows fossil users try to widen the test base and 
report on problems we discover ;) We can verify fixes you devs cannot 
test on Windows themselves.


One question though: why is not case sensitive the default on Windows? 
Or put differently: do I have to expect any difficulties if I continue 
to work with the reversed setting (which resolved my problem above and 
will also help in future in case of more renames)?

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Uppercase/lowercase issue on Windows

2015-01-05 Thread Stephan Beal
On Mon, Jan 5, 2015 at 6:10 PM, Robert Engelhardt m...@robert-engelhardt.de
 wrote:

 One question though: why is not case sensitive the default on Windows?


Probably because it would be a by-default semantic difference across
platforms. Just speculating.


 Or put differently: do I have to expect any difficulties if I continue to
 work with the reversed setting (which resolved my problem above and will
 also help in future in case of more renames)?


i can't say - all my systems are case-sensitive by nature. i don't
anticipate any problems in that regard, though, except maybe the occasional
cosmetic one.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Uppercase/lowercase issue on Windows

2014-12-08 Thread Stephan Beal
On Mon, Dec 8, 2014 at 7:44 PM, Robert Engelhardt m...@robert-engelhardt.de
 wrote:

 Was anyone able to reproduce my problem or to understand what's going on
 here? I have the impression that some parts of fossil are (correctly) not
 case sensitive while others are, and in the case demonstrated they somehow
 conflict and result in that strange output…

 May I open a ticket to track this issue?


Please do (and thanks for asking!). Forewarning, though: if i'm not
mistaken, only a couple of the fossil devs work on it in Windows (resp.
case insensitively).

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Uppercase/lowercase issue on Windows

2014-11-26 Thread Robert Engelhardt

Hello,

I received an e-mail apparently sent to the mailing list which for some 
reason doesn't show up in the archives on the web. That's the one I was 
replying to - maybe it didn't get through due to the attached script 
(batch file for Windows)…


Anyway, based on that very helpful input I have created a repository 
which shows the problem. Just two check-ins: the first one with a 
directory A and some files in it, and a second check-in in which this 
directory was renamed to a and some more files were added:


http://ge.tt/2FYa9K52/v/0

Only for the first check-in the file views appears normal - for the 
second check-in, for tip or trunk or even all check-ins the output 
is quite, well, messy…


Thanks for having a look!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Uppercase/lowercase issue on Windows

2014-11-24 Thread Robert Engelhardt

Hello,

 Make sure that you're not looking at the all list - there's a link
 across the top submenu which says trunk - click that. In all view
 you see filenames which appeared in any version.

I'm not looking at the all list (thanks for the info though, I never 
noticed that link so far - might be really useful one day). I'm just 
reviewing one specific check-in.


But even when using the all view I'd expect one entry A and one 
entry a for the directories (before and after the rename), not a 
confusing sequence of A-a-A-a-…
And for only single check-in (where I don't have both folders at the 
same time in the file system, as already Windows forbids that) seeing 
both A and a seems really odd.


The actual directory names are not that secret, so in case you deem it 
useful I can post a screenshot somewhere.


Thanks!

Kind regards,
Robert Engelhardt
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Uppercase/lowercase issue on Windows

2014-11-24 Thread Warren Young
On Nov 24, 2014, at 3:41 PM, Robert Engelhardt m...@robert-engelhardt.de 
wrote:

 The actual directory names are not that secret, so in case you deem it useful 
 I can post a screenshot somewhere.

It sounds like you know how to recreate it, so how about you just make a fresh 
Fossil repo and set up the problem.  Then you can post it here for people to 
play with.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Uppercase/lowercase issue on Windows

2014-11-24 Thread Robert Engelhardt

Hello,


I got curious. I've attached a bat file which gets a similar effect to
that described on Windows. My Files view is a little more mysterious [...]


Yes, that looks familiar! I was just trying to recreate the issue with a 
test repository, but so far were only able to achieve such a layout by 
repeatedly renaming directory a to A and vice versa between the 
check-ins - which I didn't do in the original repository, there it was a 
one time rename. But in the end I had a similar screen…


From what I see in your example, it seems to me that fossil orders the 
*files* alphabetically, and thus mixes in the differently named folders 
A and a under which it knows them.
I admit that having a file system which is aware of the uppercase vs. 
lowercase difference, while in the repository case sensitivity is 
disabled by default, is quite tricky, but the output here is undesired 
and confusing (at least from my point of view).


If desired, I'll continue with my test repository tomorrow and provide 
in then.


Kind regards,
Robert
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] Uppercase/lowercase issue on Windows

2014-11-21 Thread Robert Engelhardt

Hello all,

I'm using fossil 1.30 [45a366a0a0] on Windows. I have the following problem:

I have under version control a directory A which was later renamed to 
a. It contains the files w, x, y and z. Although fossil should 
not be case sensitive on Windows (i.e., the respective setting is set to 
FALSE and was also never changed in the past), it for some reasons knows 
both the old and the new name of the directory.
So while there's actually only one folder with four files in it, looking 
at the »Files« view in the fossil UI I see both A with files w and 
x, and a with y and z (I assume files w and x were added 
prior to the renaming, and y and z later). Additionally, looking at 
the »files« (or »folders«) link of a specific check-in, I have a wild 
mix of entries A\w, a\y, A\x and a\z - in reality there are even 
more alternating entries of the same directory again and again… This 
looks confusing and doesn't seem right to me.


Any idea how to solve that and sync fossils understanding of the 
directory with the actual file system situation? I tried a fossil move 
A a or fossil move A\w a\w, but that just gave me a cannot rename … 
to … since another file named … is currently under management error 
message. I'd like to cleanup the mess I somehow created ;) Thanks for 
any hint!

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Uppercase/lowercase issue on Windows

2014-11-21 Thread Stephan Beal
On Fri, Nov 21, 2014 at 10:14 AM, Robert Engelhardt 
m...@robert-engelhardt.de wrote:

 I have under version control a directory A which was later renamed to
 a. It contains the files w, x, y and z. Although fossil should
 not be case sensitive on Windows (i.e., the respective setting is set to
 FALSE and was also never changed in the past), it for some reasons knows
 both the old and the new name of the directory.
 So while there's actually only one folder with four files in it, looking
 at the »Files« view in the fossil UI I see both A with files w and x,
 and a with y and z (I assume files w and x were added prior to
 the renaming, and y and z later). Additionally, looking at the »files«
 (or »folders«) link of a specific check-in, I have a wild mix of entries
 A\w, a\y, A\x and a\z - in reality there are even more alternating
 entries of the same directory again and again… This looks confusing and
 doesn't seem right to me.


Make sure that you're not looking at the all list - there's a link across
the top submenu which says trunk - click that. In all view you see
filenames which appeared in any version.


 move A a or fossil move A\w a\w, but that just gave me a cannot rename
 … to … since another file named … is currently under management error
 message.


That's because of the case-insensitivity - those are equivalent which
case-sensitivity is off.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users