On 6/11/07, Bill Mill <bill.mill@gmail.com> wrote:
> /c/test/Common$ svn ci -m "Resurrected PQEbay"
> Adding PQEbay
> svn: Commit failed (details follow):
> svn: Cannot verify lock on path '/PQ_CODE/Common/PQEbay/FilterConstants.cs';
> no matching lock-token available
>
> PQEbay has the svn:needs-lock property on it, could that be causing the problem?
No, the svn:needs-lock property is completely orthogonal to the
existence of locks. The book explains in more detail.
The problem here is that PQEbay/FilterConstants.cs is locked in the
repository. Use 'svn info URL" to see information about the lock.
(i.e. who locked it and when.)
If your working copy doesn't have the lock-token for the file, you'll
have to break it forcibly with 'svn unlock --force'.
> If so, how can I remove it, or do anything to allow myself to check in?
>
> I've tried to lock the dir, but it's not checked in, so I get a catch-22
> situation:
Directories aren't lockable, only files are.
> == Issue 2 ==
>
> The second issue occurs when I've tried to delete a branch after
> merging its changes into the trunk:
>
> /c/test/branches$ svn status
> D ThreadedBoxCache
> D ThreadedBoxCache\boxCache.cs
> [snip]
> D ThreadedBoxCache\Interop.MSCommLib.dll
> D ThreadedBoxCache\InventoryGroupSorter.cs
> D ThreadedBoxCache\frmSortStation.resx
>
> /c/test/branches$ svn ci -m "Deleting ThreadedBoxCache branch"
> Deleting branches\ThreadedBoxCache
> svn: Commit failed (details follow):
> svn: Cannot verify lock on path '/snarf.root/APPLICATION/SecondSort/SortStation/
> branches/ThreadedBoxCache/clsLotGroupBox.cs'; no matching lock-token available
Once again, the clsLotGroupBox.cs is locked in the repository,
probably by someone else.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 11 22:19:52 2007