Date: Sat, 2 Jul 2011 14:45:13 -0400 From: Alexander Kabaev <kabaev@gmail.com> To: "Hartmann, O." <ohartman@zedat.fu-berlin.de> 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: <20110702144513.5c5b9f75@kan.dnsalias.net> In-Reply-To: <4E0EC86E.9050608@zedat.fu-berlin.de> References: <4E0EC86E.9050608@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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. -- Alexander Kabaev [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iD8DBQFOD2c+Q6z1jMm+XZYRAr4OAJwL5BHanHJGgFPsn6FdsqBPye2JXwCfYswL u/+5f/EOSY6TOzF02WMcqLE= =OyLi -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110702144513.5c5b9f75>