Bug#729426: Tighten versioned dependency on SQLite3

2013-11-12 Thread James McCoy
On Tue, Nov 12, 2013 at 03:27:07PM -0600, Peter Samuelson wrote: > [Wouter Bolsterlee] > > svn: E200029: Couldn't perform atomic initialization > > svn: E200030: SQLite compiled for 3.8.0.2, but running with > > 3.7.13 > > Thanks. The problem is that there's 3 different op

Bug#729426: Tighten versioned dependency on SQLite3

2013-11-12 Thread Wouter Bolsterlee
Peter Samuelson schreef op di 12-11-2013 om 15:27 [-0600]: > [...] > It's been suggested we use runtime detection of SQLite features in > libsvn1, but that's not really convenient: if I remember correctly, the > build process involves compiling SQL queries which may use newer SQLite > features. I'

Bug#729426: Tighten versioned dependency on SQLite3

2013-11-12 Thread Peter Samuelson
reassign 729426 libsvn1 forcemerge 721878 729426 thanks [Wouter Bolsterlee] > svn: E200029: Couldn't perform atomic initialization > svn: E200030: SQLite compiled for 3.8.0.2, but running with > 3.7.13 Thanks. The problem is that there's 3 different opinions on this depe

Bug#729426: Tighten versioned dependency on SQLite3

2013-11-12 Thread Wouter Bolsterlee
Package: subversion Hi, It seems the subversion dependency on libsqlite3-0 (via libsvn1) needs tighter versioning. Currently a mismatch can result in errors like these: svn: E200029: Couldn't perform atomic initialization svn: E200030: SQLite compiled for 3.8.0.2, but running wit