Sudden problem with SVN server from devel:tools:scm on openSUSE 12.3

[Johannes Weberhofer]

Since the end of last week my SVN server is having a problem accessing the sqlite database:

# sudo -u wwwrun svnadmin verify /srv/svn/
* Überprüfe Metadaten des Projektarchivs ...
svnadmin: E200029: Konnte »rep-cache«-Datenbank des Projektarchivs nicht öffnen
svnadmin: E200029: Couldn't perform atomic initialization
svnadmin: E200029: Couldn't perform atomic initialization
svnadmin: E200030: SQLite wurde für 3.7.17 kompiliert, läuft aber mit 3.7.14.1

It looks, as if openSUSE 12.3 has packaged sqlite 3.7.14.1 but subversion has been built with 3.7.14; any idea how to fix that issue?

Best regards,
Johannes

[Tomáš Chvátal]

Post by Johannes Weberhofer
# sudo -u wwwrun svnadmin verify /srv/svn/
* ÜberprÃŒfe Metadaten des Projektarchivs ...
svnadmin: E200029: Konnte »rep-cache«-Datenbank des Projektarchivs nicht
öffnen svnadmin: E200029: Couldn't perform atomic initialization
svnadmin: E200029: Couldn't perform atomic initialization
svnadmin: E200030: SQLite wurde fÌr 3.7.17 kompiliert, lÀuft aber mit
3.7.14.1
It looks, as if openSUSE 12.3 has packaged sqlite 3.7.14.1 but subversion
has been built with 3.7.14; any idea how to fix that issue?
Best regards,
Johannes

There is sqlite 3.7.17 in the same repository so you SHOULD migrate to sqlite
provided in the svn project.

Cheers

Tom

[Johannes Weberhofer]

Hello Tom,

the sqilte provided by svn repository is older than the one provided by openSUSE 12.3; I fear, I'll get some problems when I downgrade, as there is a large number or packages dependent on libsqlite3.so.0()(64bit)

Best regards,
Johannes

Post by Tomáš Chvátal

Post by Johannes Weberhofer
Since the end of last week my SVN server is having a problem accessing the
# sudo -u wwwrun svnadmin verify /srv/svn/
* Überprüfe Metadaten des Projektarchivs ...
svnadmin: E200029: Konnte »rep-cache«-Datenbank des Projektarchivs nicht
öffnen svnadmin: E200029: Couldn't perform atomic initialization
svnadmin: E200029: Couldn't perform atomic initialization
svnadmin: E200030: SQLite wurde für 3.7.17 kompiliert, läuft aber mit 3.7.14.1
It looks, as if openSUSE 12.3 has packaged sqlite 3.7.14.1 but subversion
has been built with 3.7.14; any idea how to fix that issue?
Best regards,
Johannes

There is sqlite 3.7.17 in the same repository so you SHOULD migrate to sqlite
provided in the svn project.
Cheers
Tom

[Stephan Kulow]

Post by Johannes Weberhofer
Hello Tom,
the sqilte provided by svn repository is older than the one provided by
openSUSE 12.3; I fear, I'll get some problems when I downgrade, as there
is a large number or packages dependent on libsqlite3.so.0()(64bit)

Then don't use the devel:tools:scm:svn repository

Greetings, Stephan

[Johannes Weberhofer]

Post by Stephan Kulow

Post by Johannes Weberhofer
Hello Tom,
the sqilte provided by svn repository is older than the one provided by
openSUSE 12.3; I fear, I'll get some problems when I downgrade, as there
is a large number or packages dependent on libsqlite3.so.0()(64bit)

Then don't use the devel:tools:scm:svn repository
Greetings, Stephan

I thought, those repos should extend the system's functionality without negative influence on the base system (and, indeed it worked until last week). However, I'll try to downgrade.

Best regards,
Johannes

[Andrew Daugherity]

Post by Johannes Weberhofer

Post by Stephan Kulow

Post by Johannes Weberhofer
Hello Tom,
the sqilte provided by svn repository is older than the one provided by
openSUSE 12.3; I fear, I'll get some problems when I downgrade, as there
is a large number or packages dependent on libsqlite3.so.0()(64bit)

Then don't use the devel:tools:scm:svn repository
Greetings, Stephan

I thought, those repos should extend the system's functionality without negative influence on the base system (and, indeed it worked until last week). However, I'll try to downgrade.
Best regards,
Johannes

Well, it looks like sqlite3 in this repo has been upgraded to 3.7.17, so there's no downgrade necessary, but rather an upgrade. I'm with you about being wary of replacing system libraries, but that is indeed the fix here. I don't know why this used to not be necessary for subversion from the d:t:scm:svn project, but it is now. I just got hit by it on SLES 11 SP3 (same error, different system sqlite version).

When investigating this, I noticed an apparent packaging bug: the subversion package used to require a specific version of sqlite, but no longer does. It seems like maintaing this versioned dependency would prevent installing a broken svn.

openSUSE 12.3 deps (13.1 is similar):
$ rpm -qR subversion|grep sqlite
libsqlite3-0 >= 3.7.14.1
libsqlite3.so.0()(64bit)

Factory and d:t:scm:svn package:
$ rpm -qR subversion|grep sqlite
libsqlite3.so.0()(64bit)

Was the version dependency intentionally removed, or is this just an oversight)? With it in place, installing or upgrading svn from this repo would require the matching libsqlite3-0, and avoid this issue.


Thanks,
Andrew

[Johannes Weberhofer]

Post by Andrew Daugherity

Post by Johannes Weberhofer

Post by Stephan Kulow

Post by Johannes Weberhofer
Hello Tom,
the sqilte provided by svn repository is older than the one provided by
openSUSE 12.3; I fear, I'll get some problems when I downgrade, as there
is a large number or packages dependent on libsqlite3.so.0()(64bit)

Then don't use the devel:tools:scm:svn repository
Greetings, Stephan

I thought, those repos should extend the system's functionality without negative influence on the base system (and, indeed it worked until last week). However, I'll try to downgrade.
Best regards,
Johannes

Well, it looks like sqlite3 in this repo has been upgraded to 3.7.17, so there's no downgrade necessary, but rather an upgrade. I'm with you about being wary of replacing system libraries, but that is indeed the fix here. I don't know why this used to not be necessary for subversion from the d:t:scm:svn project, but it is now. I just got hit by it on SLES 11 SP3 (same error, different system sqlite version).
When investigating this, I noticed an apparent packaging bug: the subversion package used to require a specific version of sqlite, but no longer does. It seems like maintaing this versioned dependency would prevent installing a broken svn.
$ rpm -qR subversion|grep sqlite
libsqlite3-0 >= 3.7.14.1
libsqlite3.so.0()(64bit)
$ rpm -qR subversion|grep sqlite
libsqlite3.so.0()(64bit)
Was the version dependency intentionally removed, or is this just an oversight)? With it in place, installing or upgrading svn from this repo would require the matching libsqlite3-0, and avoid this issue.
Thanks,
Andrew

Dear Andreas,

I have created (https://build.opensuse.org/request/show/249968) a update that solves this issue for newer distributions of opensuse.
As a sqlite version >=3.7.14.1 is required by the current svn version I think there is no simple solution to upgrade SLES to svn 1.8. You could try to install sqlite from devel:tools:scm:svn, but that could negatively impact other software on you system :-(

Best regards,
Johannes