Created on 2020-12-31.09:01:14 by narcisgarcia, last changed 2 months ago by ced.
If Tryton-server supports re/installing modules, I think this issue is not invalid.
Tryton-server is already selecting between 2 modules sources, as:
Then the fix is to override stock directory for those modules that have a local installation: /usr/local/lib over /usr/lib
And to me, to find a workaround, I want to know where is the point that Tryton-server decides per each module what source path to load from.
This is the expected behaviour as you mixed installing packages from two sources (which is not recommended) the server gets the on it finds first. As you installed the server from debian packages it's expected to pick the modules from the same path.
Please use the system administrator support section of our discussion server for support.
I have Tryton-server and Tryton-client 5.0 installed from Debian 10 repositories, and working. I want this Apt/Deb software base.
I install new modules versions from downloads.tryton.org/5.0 (once unpacked, "pip3 install /tmp/unpacked --upgrade") and restart trytond service.
When I enter to Tryton-client (GUI), it still shows modules at distro version; as not upgraded.
Note: I have a custom module installed and this one yes, is loaded by Tryton.
Where is the point where Tryton decides per each module what source path to load from?
|2020-12-31 14:56:00||ced||set||status: chatting -> invalid|
|2020-12-31 14:28:30||narcisgarcia||set||status: invalid -> chatting|
|2020-12-31 10:02:58||narcisgarcia||set||messages: + msg63724|
nosy: + pokoli
status: unread -> invalid
Showing 10 items. Show all history (warning: this could be VERY long)