Hello Frank,
The only way that EA can retrieve the package file from the SVN server and import it, is if there is no lock on the file in the SVN repository.
If you are not connected to the server, then the file status query that occurs when building the Package Control menu will fail, with an error message. If you got past that, the "checkout" operation would fail with an error message. The import would not happen!
If you were connected to the server, then the file status should be reported as locked by you and the menu item "check-out", should be disabled.
When EA constructs the Package Control menu, it queries SVN for the file status. If there is no connection to the server, you will see an error message at this stage. If there is a connection, then the Check-in and Check-out menu items are enabled and disabled in accordance with who holds a lock on this file. If you checked-out a package, it should be locked by you. If the file is not locked by you, it will be shown as VC-locked and the check-out menu item will be enabled.
If you have left a package checked-out to yourself, then the only way that you will see this "VC locked" package icon and have the check-out menu item enabled when you re-open a model the next day, is when another user has broken or stolen the lock from you, using Subversion directly, and then subsequently released the lock.
There is some fine print in the EA User Guide that says, "we strongly urge you not to directly manipulate EA's version controlled package files, outside of EA." This is the reason for that fine print.
If you find that this is the cause of this problem and you realise that a package is checked-in, when it should be check-out to you, it is possible to use Subversion directly to put the package file back into the correct state and then reload the package from the model database (as opposed to reloading from the package XMI file) to refresh the package icon. (Right-click - "Contents | Reload package")
At this point the package will be shown as "checked-out" to you and you can subsequently "check-in" the previous days modifications.
You can also use the command "Compare with version on disk" to show the differences between what is in your model and what is in the HEAD revision in version control.
I hope this helps.
best regards,
Howard Britten.