beingryu Posted November 21, 2011 Report Share Posted November 21, 2011 Hi, we are evaluating version 4.0; it seems really great so far. You guys did a great job. However we are suffering read-only property issue. We love to work as in so-called SVN-mode, so we checked off 'Update and Checkin operations set files as read-only' option in preferences. But it *inconsistently* sets files as read-only. Please take an investigation on this issue. Thanks. Link to comment Share on other sites More sharing options...
psantosl Posted November 21, 2011 Report Share Posted November 21, 2011 Wow! Thanks for the heads up! We'll take a look into it and try to get it fixed before the week ends. Link to comment Share on other sites More sharing options...
psantosl Posted November 22, 2011 Report Share Posted November 22, 2011 Hi there, After investigation down here we found it can only happen after merge. Is that true? Can you confirm it? I mean, update, switch to branch, uncheckout and everything else should be working. Does it match with your "random behavior"? Link to comment Share on other sites More sharing options...
beingryu Posted November 22, 2011 Author Report Share Posted November 22, 2011 I'm not sure but you might be right. I remember that it happened around switching between branches. Link to comment Share on other sites More sharing options...
psantosl Posted November 22, 2011 Report Share Posted November 22, 2011 Switching shouldn't be an issue. It must be merging. Do you mean that? Thanks, pablo Link to comment Share on other sites More sharing options...
beingryu Posted November 23, 2011 Author Report Share Posted November 23, 2011 Unfortunately i wasn't able to reproduce the problem as you told Could you tell me the detailed step to reproduce it please? FYI in past, we just messed around read-only property - turned off repeatedly when the property turned back on. After doing it several times the property wasn't turned on anymore. Link to comment Share on other sites More sharing options...
psantosl Posted November 23, 2011 Report Share Posted November 23, 2011 ?? Ok, the only scenario I can think of is: 0- you branch from /main into /task001 1- You modify foo.c in /main 2- You modify foo.c in /task001 3- you merge -> your file gets readonly back! (a bug!) Link to comment Share on other sites More sharing options...
danipen Posted November 28, 2011 Report Share Posted November 28, 2011 Hi beingryu, Plastic SCM has by default the setting to set files as readonly when checkin/update. Also, when you change the preference and set it OFF, the files are not set to non-readonly at that moment. So, the following scenario could seem a extrange behavior: Imagine that you update your workspace with the preference ON, and then you set the preference OFF. The files are not changed at that moment. After setting OFF the preference, you switch to branch, and only those files that are changed and was written to disk, are written without the readonly preference, so some files are ok (non-readonly), but others are not ok (are still readonly). If you want to setup all your files in your workspace, you need to re-write all the files in your workspace again (update forced) after change the preference. Please, could you confirm if this behavior is related with your issue? Thanks in advance, and best regards. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.