[Tinyerp-users] Re: pos
Thank you but it seems that both links the same in your page. Fixed. The main reason is that we have about 150 modules to upload and I prefer not loosing too much time releasing them manually. We have to create new automated releasing and testing scripts for this. Your are doing a disservice to the project at this point:These Modules with missing Sources have been uploded about 4 month ago. Many user claimed they are missing, many bad discussions arose. This is not good for the communities sprit. On the other hand: As you stated at the last German community Meeting, there should be a new one-click publication mechanism in 4.2 (I've not tested 4.2 yet). With this it should be a matter of one hour or so to release the modules. (N.B. Anyway I don't believe, you published the modules manually in the first place.) And on even another hand: You need to implement the tools for automated publication anyway. You could have done earier and save a lot of bad discussions. Regards Hartmut Goebel IT-Security In Complex Environments www.goebel-consult.de ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Re: Windows: Could not connect to server
I've the same problem here. MY analysis: - The server is listening and answering requests. - The Clients sends an xmlrpc request for /xmlrpc/db and gets an error 404 not found. The body contains No such page. - Same when i try ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Re: Windows: Could not connect to server
I solved the problem: 1) I'm running Python 2.5, which changed SimpleXMLRPCServer.py. Solution: Either a) switch to Python 2.4 or b) copy Python2.4 SimpleXMLRPCServer.py into the tinyerp-server directory (copying into the python-lib directory is not recomented). You may get the file diectly from the SVN at http://svn.python.org/view/*checkout*/python/tags/r244/Lib/SimpleXMLRPCServer.py?rev=52384 2) This did not solve the problem, since there was another one: a memory leak in sgmlop.so. I discovered this after removing the ThreadingMixIn from SimpleThreadedXMLRPCServer in bin/netsvc.py. When the clients connected, the memory leak was reported. The solution for this was to reinstall sgmlop.so. On my system, this was part of the python-reportlab RPM which has no update available yet. So I removed sgmlop.so and installed sgmlop seperatly: easy_install sgmlop ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
