kfogel@collab.net (kfogel@collab.net) wrote:
> Dan Allen <dan@mojavelinux.com> writes:
> > That maybe gives me one checkout and then we are back to checksum
> > errors. I am running the dev version of subversion 0.20.1 I really
> > need to setup a revisioning system for my team project and I don't
> > want to use CVS. Can anyone point me to a version of subversion
> > that I can use for now that actually allows me to checkout without
> > errors. I know I sound like a real complainer here, but I just need
> > to get on my feet with the versioning software and then I can worry
> > about upgrading for enhancements later.
>
> Hmmm. This is a new problem -- we've never seen checksum errors on
> checkout when the client is new, the server is new, and the repository
> was created with a new svnadmin. ("new" here meaning >= 0.20 or so.)
>
> This needs investigation.
>
> Is your repository data private to your company? If you can't put it
> up for public download, can you give me private access to it? I would
> need:
>
> 1. The dumpfile from which the new repository was created.
> 2. The httpd.conf for your Apache2 (/usr/local/apache2/conf/httpd.conf)
> 3. The output of your session on the client side; we need to see
> the actual checksum error.
> 4. The data that goes into /usr/local/apache2/logs/error_log during
> the checkout.
> 5. The ethereal trace.
> 6. (optional) the repository itself, preferable in tar.gz form :-).
> Remember to shut down Apache before tarring it up.
>
> I am pretty sure we/I can track this down, with that information.
> Without the information, we'll need some other reproduction recipe,
> otherwise there's very little chance of finding the cause.
>
> In any case, can you at least show the client-side transcript?
I could give you a url, but as a just discovered, you will check out
my repository without a single error, because I just did it from a
remote computer. The problem only occurs (and unfortunately exactly
what I kept doing over and over) when I access my local computer
through my router by making a hostname request (hence the request
leaves the subnet, goes out to the internet and comes back home). I
am beginning to thing this is just a router issue that creates some
hicup that kills webdav. I could do more ethereal traces on it, but
perhaps you could just get the community to research the following
scenerio, since most people have linksys routers anyway:
install apache2
install subversion mod
setup virtual host to svn.mydomain.com on port 8080 (since cable
companies block 80)
from the computer which hosts the repository, attempt a local
checkout by accessing http://svn.mydomain.com:8080/project
I bet more than the money in my pocket that will fail most of the
time.
Dan
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Daniel Allen, <dan@mojavelinux.com>
http://www.mojavelinux.com/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"I used to herd dairy cows. Now I herd linux users. Apart
from the isolation, I think I preferred the cows. They were
better in conversation, easier to milk, and if they annoyed me
enough, I could shoot them and eat them."
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 29 21:51:38 2003