You can't mix svn and svk commits against the same repo. It confuses svk (not svn).
You can use svk readonly, of course.
Actually, that's not quite right. While svk's depot must only be used by svk, the usual usage is to mirror a regular subversion repository with svk into a svk depot, then work with it from there using svk. Any changes in the svn repository are pulled in with svk sync, and any changes to the mirrored copy are applied to the backing subversion repository.
Except that http://svk.elixus.org/?SVKFAQ
says "Given an svk repository, do you have to use it via svk, or can you use svn programs to access it?
Short answer: svn programs that only read the repository are working fine; those who actually write in the repository would bypass svk and make it fail. "
Vital difference: This will work: svk mirror svn://wherever //svnrepo/mirror # do svk things with //svnrepo/mirror # do svn things with svn://wherever
This won't work: svk mirror svn://wherever //svnrepo/mirror # do svk things with //svnrepo/mirror # do svn things wioth file://$HOME/.svk/local/svnrepo/mirror
signature.asc
Description: OpenPGP digital signature
