> -----Original Message-----
> From: news [mailto:n...@ger.gmane.org] On Behalf Of Dan Poirier
> Sent: vrijdag 22 januari 2010 12:59
> To: users@subversion.apache.org
> Subject: Re: svn diff 'path not found' and 'Error reading spooled REPORT
> request response'
>
> We've found an (apparently) simpler case of what looks like the same
> error:
>
> $ svn ls https://domain.example/dir1/PROJECT/trunk/README
> README
> $ svn cat https://domain.example/dir1/PROJECT/trunk/README
> svn: '/!svn/bc/23694/dir1/PROJECT/trunk/README' path not found
>
> I don't see any command line options, or options for mod_dav_svn, to log
> more information as it runs. Would rebuilding subversion with
> --enable-debug and --enable-maintainer-mode provide more information to
> see what's going on here?
>
> Or is this a simple case of a corrupted repository? In which case, any
> suggestions on how to proceed? It's not too late to re-run cvs2svn and
> recreate the changes we made since last time, if cvs2svn was what
> corrupted it and we can fix that before running it again.
>
> Thanks for any help on how to proceed,
> Dan
At which level in this url is your repository located?
Can you quote the relevant porting from your apache config? (Most likely the
<Location> block).
My guess is that your repository is located on the root of the webserver and
this can give some issues if not configured correctly. (Sometimes request
are handled via mod_dav and sometimes via the other handlers). As /!svn is
mapped on that root url, it has to get back in mod_dav or you get all kinds
of strange errors.
If you are just setting up your server I would recommend setting it up with
a 'svn/' or 'repos/' prefix via a location tag as shown in most examples, as
that makes the installation easier and better maintainable if some unrelated
apache settings change.
Bert
