2017-06-05 19:27 GMT+02:00 Danny Milosavljevic <[email protected]>:
> Hi Jelle, > > On Mon, 5 Jun 2017 18:32:10 +0200 > Jelle Licht <[email protected]> wrote: > > > Some possible directions on resolving this issue: > > - Debug the multiple thousand lines of test code to see exactly where/how > > the test fails when using the system SQLite library > > - Package the right version of the SQLite amalgation [1] that is now > > bundled, although the amalgation should be functionally equivalent to the > > normal SQLite version. > > I see that apsw bundles SQLite 3.9.2. Does it work when you replace it > with the external version 3.9.2 - amalgation or not ? > Getting version 3.9.2 to build turned out to be a bit of a hassle; some nonsense about a fossil(?) generated manifest missing or what not. > > I don't necessarily mean permanently - just to find out whether the tests > work normally then. > > Also, Perhaps diff the bundled SQLite 3.9.2 and the released SQLite 3.9.2 > amalgation of the same version ? > A diff between bundled SQLite 3.9.2 and release 3.9.2. amalgation reveals no (functional) differences, so at least there will be no extra set of patches to maintain. > [...] > It seems that the actual upstream for apsw at [1] has continued development since we packaged it. Incidentally, our sqlite package is a bit outdated. If I update sqlite to the latest version (3.20.1), as well as change the python-apsw upstream to [1], the package seems to build and pass the `check' phase with no issues. [1] : https://github.com/rogerbinns/apsw
