1

I'm working on a ClearCase repository. Some of the files in it have, for some reason, execution permissions while they shouldn't (they're text files basically). I'll also mention I'm a user without root privilege.

If I check them out, change their permissions (the usual way, not with ct permission -chmod, which doesn't work), then try to check them back in - I'm told that:

ct: Error: By default, won't create version with data identical to predecessor.

How do I override this default? Or am I going about this the wrong way?

Scransom
  • 3,175
  • 3
  • 31
  • 51
einpoklum
  • 118,144
  • 57
  • 340
  • 684

1 Answers1

2

Regarding cleartool checkin, the correct option would be:

-ide/ntical

(meaning cleartool -ide or cleartool -identical: short and long form of the identical option)

Checks in the element even if the predecessor version is identical to the checked-out version.
By default, the checkin operation is canceled in such cases.

But in your case, this should not be needed: you do not need to checkin a protect change.

Try first a cleartool protect command (not cleartool permission)

cleartool protect -chmod 644 aFile

(provided the restrictions allow the command to work, with or without ACLs)

Check also your umask (for instance 002) used in your view (if you are on Unix)

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • Actually, the ONLY way to change the permissions after adding to source control is to use ct protect -chmod... Check out, followed by chmod and checkin isnt likely to work. – Brian Cowan May 20 '20 at 15:22
  • @BrianCowan I agree. I don't remember having to do any `co`/`ci` when I used `ct protect`. – VonC May 20 '20 at 15:29
  • `ide/ntical`? Typo with the slash? – einpoklum May 20 '20 at 15:32
  • 1
    @einpoklum No typo: it is the "IBM documentation" way to indicate the long and short form of an option `-ide` or `-identical` – VonC May 20 '20 at 15:35