Yes, I was attempting to add a Solaris x86 (AMD Opteron SunFire V20z) to a
loadbalanced pool of Sparc Solaris apache mod_dav_svn servers (accessing the
common fsfs repo over NFS)
So I tried your "solution/workaround" (create a x86 repo and cp the
dav/activities.pag over the Sparc file) and magically my commits are
Of course seems to rule out mixing architectures in my svn pool...
Not a huge deal if I can switch over to my new faster Operton nodes all at
once and this is the final incompatibility...
Can anyone opine on the risks of calling this solution final?
Data Center Services
Sr. System Administrator
Information Resources & Technology
School of Medicine Stanford University
650-723-8390, option 6
From: Keven Ring [mailto:firstname.lastname@example.org]
Sent: Thursday, July 07, 2005 1:46 PM
Subject: Re: svn: Can't close activity db: Error string not specified yet
I'm not sure if I have a "solution" to this, or if I really broke
something without knowing it, but it is related.
In my case, I have a subversion repository on a Sun workstation, running
Solaris 9, SVN 1.2.0. Temporarily, we are copying the contents of this
repository over to a Linux box (running FC4, with a freshly compiled SVN
1.2.1). It seems that I get this exact same error message when I check
files into the Linux box.
The "solution" was to copy the activities.pag file from a repository
that I created on the Linux box via SVN 1.2.1 into the dav directory of
the repository copied from the Sun box. Performing this simple task did
not appear to cause any ill effects when checking the files into the
So, my thinking is (and this may coincide with what Ben was saying) is
that this file is really platform specific, in that it uses a database
access via APR based on what APR thinks is available.
So, before I charge off and run the repository on Linux, I should really
ask, how platform independent is the rest of the SVN repository? BTW,
the repository is using the FSFS.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jul 8 07:16:36 2005