After our email conversation the problem is not, that the clearcase vob is non-mastered.
The problem is, that clearcase does not return a valid error code, instead it returns 0 always. So my assumtion was, that a clearcase command failed, whenever it writes something to standard error. In the current case the execution of the clearcase command itself was successful, but there was an additional warning which was written to std-err.
So it was erroneously taken for granted, that the command failed.
This will be changed in one of the next releases by checking whether a useful output was emmited from the clearcase command regardless of the error message.
As a workaround a script could be used, which is configured as clearcase command in the Preferences dialog and which delegates all calls to clearcase and redirects std-err to /dev/null.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After our email conversation the problem is not, that the clearcase vob is non-mastered.
The problem is, that clearcase does not return a valid error code, instead it returns 0 always. So my assumtion was, that a clearcase command failed, whenever it writes something to standard error. In the current case the execution of the clearcase command itself was successful, but there was an additional warning which was written to std-err.
So it was erroneously taken for granted, that the command failed.
This will be changed in one of the next releases by checking whether a useful output was emmited from the clearcase command regardless of the error message.
As a workaround a script could be used, which is configured as clearcase command in the Preferences dialog and which delegates all calls to clearcase and redirects std-err to /dev/null.