Hi Guillem, Am Mittwoch, 10. Dezember 2014 15:30:06 UTC+1 schrieb Guillem Barba: > > > This is strange, it is not mentioned in tryton.cfg of the module in >>> error, nor do I find the entry somewhere in our (production) >>> installation. >>> But it seems to be in the database. >>> >> The error means that there is another module that depends on this module. >> So you need to find for another module that depends on this module. >> >> On filesystem, you must check the modules folder of the trytond >> instalation, and also the installed eggs. >> >> >> On database you can check the ir_module_module and the >> ir_module_module_dependency tables. It may be there if the database was ran >> on another trytond server which has the module and it's dependencies. >> > > Have you updated the module list? It is done when you up upgrade some > module so you can do something like: > ./bin/trytond -c <trytond.conf> -d <database> -u email_queue > > It will update the module list and install this missing dependency. > > That was the magic hint, thank you! For the records; In ir_module_module and the ir_module_module_dependency, the email_queue-module was not included. Means, in the database was no need for that module!
The package causing the trouble was nereid_project, which was in the production database in version 3.0.3.x (no need for email_queue), while on the new system it was version 3.0.6.1 (with need for email_queue, which was as well installed!). So, by running the update trytond -d <database> -u email_queue and afterwards trytond -d <database> -u all the problem was solved. That leads to the question: is The inability of '-u all' to solve all dependencies properly a bug or a feature? Thanks again Axel
