--Sig_/eLCFLU41i_AWTsBqDFMYbwD
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
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?
>=20
> Is there a workaround? Any help or hint is appreciated.
>=20
> Thanks in advance,
> Oliver
>=20
> 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:
>=20
Update database/sqlite3 port to the 3.7.7.1 version committed today.
--=20
Alexander Kabaev
--Sig_/eLCFLU41i_AWTsBqDFMYbwD
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (FreeBSD)
iD8DBQFOD2c+Q6z1jMm+XZYRAr4OAJwL5BHanHJGgFPsn6FdsqBPye2JXwCfYswL
u/+5f/EOSY6TOzF02WMcqLE=
=OyLi
-----END PGP SIGNATURE-----
--Sig_/eLCFLU41i_AWTsBqDFMYbwD--