ports/158589: devel/subversion-freebsd: 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:

Sat Jul 2 09:10:10 UTC 2011

>Number:         158589
>Category:       ports
>Synopsis:       devel/subversion-freebsd: 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:
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 02 09:10:09 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Hartmann, O.
>Release:        FreeBSD 9.0-CURRENT/amd64, FreeBSD 8.2-STABLE/amd64
>Organization:
FU Berlin
>Environment:
>Description:
Since a portmaster maintanance of the ports two days ago, commiting changes to the subversion system on several hosts fails with the following error message:

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:

Digging the net reveals several issues with sqlite-3.7.7, sqlite-3.7.7.1 which are calimed to be solved in sqlite-3.7.7.2. See GOOGLE result by searching for the error message, Linux folks seem to have the same problem.

Seel also ports/158532.

>How-To-Repeat:
Update to sqlite-3.7.7 with recent subversion-freebsd/subversion.
>Fix:
It is said that the problem has been fixed in sqlite-3.7.7.2

>Release-Note:
>Audit-Trail:
>Unformatted: