nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Branch coping issue

Satish_Jadhav

Hi,

I have one old branch ABC, I copied the workarea from ABC to new branch XYX.
ABE has a1234 unix group
XYZ has x1234 unix group.

Now when I edit the new workarea sometime I am getting the group and owner of file changed to old branch that is to old unix group a1234 from x1234

What can be done for this?

Find more posts tagged with

Comments

nipper

Does this happen after submit ? You may need to change the submit.cfg

Satish_Jadhav

This happens when I try to edit a file. When I try to edit the file in new branch and when copy it back to teamsite, the permission of file changes to Old branch unix group and gives message that you do not have permission to change.

nipper

check the permissions on the workarea and the branch. Also look in iwhome/etc/iw.cfg and post the entries about branch_security and workarea_security

Migrateduser

Are you having the Files copied over from the Old branch to the new branch using the Copy to functionality of Teamsite? If yes, then the permissions on the file are copied from the old branch to the new branch. If you did not have edit permission in the old branch, you may not be able to edit the file.

One way to get rid of this is to change the permissions back to ones favourable to you by configuring the Submit.cfg and submitting the file in the new branch.

-Dixit

Adam Stoller

Hi,

I have one old branch ABC, I copied the workarea from ABC to new branch XYX.
ABE has a1234 unix group
XYZ has x1234 unix group.

Now when I edit the new workarea sometime I am getting the group and owner of file changed to old branch that is to old unix group a1234 from x1234

What can be done for this?

Unless you take explicit steps to change the behavior, the default behavior when you edit a file in TeamSite involves re-creating the file with the updated contents, and as such the file is shown as modified by you, with your primary group as the group owner.

If you set the group permissions (chgrp) on all the directories and then do a chmod g+s on all the directories - then all files and directories created within those directories will automatically inherit the group ownership from the parent directory.

After all of that - then the submit.cfg can be used to ensure the proper access bits and such are set when the file finally gets submitted.