some of the packages in the selected branch are locked

[yonatan.lehman]

Not sure how this happened but I have a package tree where the child packages are in version control and the parent isn't.

When I try to do on  the parent package "Add branch to version control" I get a dialog with

"some of the packages in the selected branch are locked"

This happens whether the sub-packages are checked in or checked out
observations:
1) I can't see any lock indications (blue or red exclamation marks) in the project tree
2) Configure Tab>Security>Locks is grayed out
3) Using EA 14.0
4) We have just ramping up with EA - I don't think we use locking
5) I tried doing in the Windows TortoiseSVN>ReleaseLock and that did show locked files on the 1st run, and none on the 2nd run, and also TortoiseSVN>Cleanup (which didn't indicate that it did anything)
- but bottom line, when I try to put some of the parent packages into version control I get the "selected branch are locked" messages
ideas?
Thanks

[Geert Bellekens]

Not sure how this happened but I have a package tree where the child packages are in version control and the parent isn't.

When I try to do on  the parent package "Add branch to version control" I get a dialog with

"some of the packages in the selected branch are locked"

This happens whether the sub-packages are checked in or checked out
observations:
1) I can't see any lock indications (blue or red exclamation marks) in the project tree
2) Configure Tab>Security>Locks is grayed out
3) Using EA 14.0
4) We have just ramping up with EA - I don't think we use locking
5) I tried doing in the Windows TortoiseSVN>ReleaseLock and that did show locked files on the 1st run, and none on the 2nd run, and also TortoiseSVN>Cleanup (which didn't indicate that it did anything)
- but bottom line, when I try to put some of the parent packages into version control I get the "selected branch are locked" messages
ideas?
Thanks

Maybe the message is worded wrong, but I think the "add branch" function is meant to add a whole branch, to version control, adding a file for each sub-package recursively.
I can imagine that EA doesn't want to do that if some of the packages have already been added to version control.

I think you have the following options:

- 1. Add package to version control one by one
- 2. Temporarily move the version controlled packages to a different branch, then add the branch to version control, and then move the existing packages back
- 2. Remove version control from all packages and start fresh with "add branch"

PS. You can automate this stuff using scripts if it's too much work to do manually.

Geert

[yonatan.lehman]

Hi Geert the Savior!

It actually does work in similar cases - it's only these specific cases that are problematic.
I suspect that I did a very large add branch to insert an entire tree of packages and this was interrupted by a system crash or internet failure ( we has some terrible weather a few weeks ago).

From what I could see the add branch did indeed work recursively - but bottom-up - or rather from the leaves to the trunk. That's why I have cases such as this:
[locked package]   A
    package A_B
        [locked package]   A_B_C

Where it create A_B_C and A but not A_B

Doing Add branch to Version control on package A_B works fine as long as any existing packages under it are checked out

But in a few particular cases it does not work and I get the "some of the packages in the selected branch are locked" - even if they are checked out.

How do I remove version control from a package/branch ? I did not see an option for that

Thanks

[Geert Bellekens]

Removing a package from version control:
Select the package, and use the option Configure | Package-VC

Geert