Hi,

In Subversion 1.6 'svn lock <file>' in a read-only workspace fails as expected
and no lock is created either in the workspace or in the repository.

In Svn 1.7/1.8 'svn lock <file>' still fails, but it creates a repository-side
lock (see below). Is this a regression or was the change intentional?

> svn st -u abc
Status against revision:   1633
> svn lock abc
svn: E200031: sqlite[S8]: attempt to write a readonly database
svn: E200031: Additional errors:
svn: E200031: sqlite[S8]: attempt to write a readonly database
> svn st -u abc
     O        1633   abc
Status against revision:   1633

All the best,

fergus

Reply via email to