Re: trytond
2017-04-06 2:10 GMT+02:00 Hartmut Goebel <h.goe...@crazy-compilers.com>: > Am 05.04.2017 um 22:03 schrieb Catonano: > > > > > > Has the daemon environment anything to do with this ? > > Be the source with you;: > > https://hg.tryton.org/trytond/file/4.2.3/trytond/backend/ > sqlite/database.py#l261 > > So it seem the database name needs to be ":memory:" or or you need to > use a full-qualified path to avoid the ned to configure the trytond. > Thank you Hartmut. This tip was substantial, I was lost I could build trytond
Re: trytond
Am 05.04.2017 um 22:03 schrieb Catonano: > > > Has the daemon environment anything to do with this ? Be the source with you;: https://hg.tryton.org/trytond/file/4.2.3/trytond/backend/sqlite/database.py#l261 So it seem the database name needs to be ":memory:" or or you need to use a full-qualified path to avoid the ned to configure the trytond. -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
Re: trytond
Catonano transcribed 3.1K bytes: > In trying to build trytond (mind the d) 4.2.3, tests fail and I see this > message Heh. I finally get what you tried to tell me a couple of weeks ago when we talked about GNU Health.. so tryton is different from what I am working on :) > == > ERROR: setUpClass (trytond.tests.test_copy.CopyTestCase) > -- > Traceback (most recent call last): > File > "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_copy.py", > line 15, in setUpClass > activate_module('tests') > File > "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_tryton.py", > line 47, in activate_module > create_db() > File > "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_tryton.py", > line 398, in create_db > transaction.database.create(transaction.connection, name) > File > "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/backend/sqlite/database.py", > line 269, in create > with sqlite.connect(path) as conn: > OperationalError: unable to open database file > > This "unable to open database file" appears tens of times > > The tests use pysqlite (which is python@2 only) > > Has the daemon environment anything to do with this ? Most likely, I think the tests want to connect to an sqlite database. But I see that you use an environmental variable already, so without looking into the application itself I can't reply anything useful. Someone else might have more insights. > The package is here > http://paste.lisp.org/display/343575 > > Thanks in advance
trytond
In trying to build trytond (mind the d) 4.2.3, tests fail and I see this message == ERROR: setUpClass (trytond.tests.test_copy.CopyTestCase) -- Traceback (most recent call last): File "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_copy.py", line 15, in setUpClass activate_module('tests') File "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_tryton.py", line 47, in activate_module create_db() File "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/tests/test_tryton.py", line 398, in create_db transaction.database.create(transaction.connection, name) File "/tmp/guix-build-python2-trytond-4.2.3.drv-1/trytond-4.2.3/trytond/backend/sqlite/database.py", line 269, in create with sqlite.connect(path) as conn: OperationalError: unable to open database file This "unable to open database file" appears tens of times The tests use pysqlite (which is python@2 only) Has the daemon environment anything to do with this ? The package is here http://paste.lisp.org/display/343575 Thanks in advance