devel/subversion: svn: Couldn't perform atomic initialization
ohartman at zedat.fu-berlin.de
Sun Jul 3 09:15:52 UTC 2011
On 07/02/11 20:45, Alexander Kabaev wrote:
> On Sat, 02 Jul 2011 09:27:42 +0200
> "Hartmann, O."<ohartman at zedat.fu-berlin.de> wrote:
>> Since two days now I realize on several recently ports-updated
>> servers a failure of the subversion server running on those servers.
>> Sneaking around the internet I found several issues exactly targeting
>> this error with an sqlite 3.7.7/18.104.22.168 issue, which has been fixed
>> in sqlite-22.214.171.124. At this very moment, our subversion servers in
>> question has all recently been updated and it seems, they all fail
>> the same way. Does anyone also realize this behaviour shown below
>> when commiting?
>> Is there a workaround? Any help or hint is appreciated.
>> Thanks in advance,
>> Transmitting file data .svn: Commit failed (details follow):
>> svn: Couldn't perform atomic initialization
>> svn: database schema has changed
>> svn: Your commit message was left in a temporary file:
> Update database/sqlite3 port to the 126.96.36.199 version committed today.
Done - and it works fine. Thanks. But why
188.8.131.52 and not 184.108.40.206?
More information about the freebsd-stable