From owner-freebsd-questions@FreeBSD.ORG Fri Jul 1 07:21:53 2011 Return-Path: Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD26B1065670; Fri, 1 Jul 2011 07:21:53 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 9D23C8FC0A; Fri, 1 Jul 2011 07:21:53 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1QcY2y-0007E7-G4>; Fri, 01 Jul 2011 09:21:52 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1QcY2y-0005z3-Dr>; Fri, 01 Jul 2011 09:21:52 +0200 Message-ID: <4E0D7590.7060403@zedat.fu-berlin.de> Date: Fri, 01 Jul 2011 09:21:52 +0200 From: "O. Hartmann" Organization: Freie =?ISO-8859-1?Q?Universit=E4t_Berlin?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110630 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG, freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: Subject: devel/subversion: svn: Couldn't perform atomic initialization svn: database schema has changed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 07:21:54 -0000 Since yesterday I receive on any try on a commit this error message from my subversion server: svn: Couldn't perform atomic initialization svn: database schema has changed svn: Your commit message was left in a temporary file: Searching for this error (which appeared after portsupdate via portmaster yesterday) reveal several postings saying this is due to a bug in SQLite 3.7.7/3.7.7-1, which has been fixed already in 3.7.7-2. As far as I realize, SQLite was part of an update these days, so I'm wondering if anybody else has been sumbled into the problem. Or is this problem caused by something else? I'm a bit like a dead man in the water since no commit to the server is possible anymore. At this very moment, I recompile sqlite and everything that depends on it, hoping it could only be triggered by some errornes portmaster thingis. Thanks in advance, Oliver