Date: Sun, 03 Jul 2011 11:15:50 +0200 From: "Hartmann, O." <ohartman@zedat.fu-berlin.de> To: Alexander Kabaev <kabaev@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: devel/subversion: svn: Couldn't perform atomic initialization Message-ID: <4E103346.1060206@zedat.fu-berlin.de> In-Reply-To: <20110702144513.5c5b9f75@kan.dnsalias.net> References: <4E0EC86E.9050608@zedat.fu-berlin.de> <20110702144513.5c5b9f75@kan.dnsalias.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/02/11 20:45, Alexander Kabaev wrote: > On Sat, 02 Jul 2011 09:27:42 +0200 > "Hartmann, O."<ohartman@zedat.fu-berlin.de> wrote: > >> Hello. >> 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/3.7.7.1 issue, which has been fixed >> in sqlite-3.7.7.2. 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, >> Oliver >> >> 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 3.7.7.1 version committed today. > Done - and it works fine. Thanks. But why 3.7.7.1 and not 3.7.7.2? Thanks, anyway. Regards, Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E103346.1060206>