I'm sorry but I don't understand what you mean. In brief: - does it work in Debian? I'm not an Ubuntu user, so I haven't tested it in Ubuntu, but it should work as I can't think of any type of difference in both distributions that could affect to the package. In fact, Ubuntu people take it as it is from Debian, without modifying a line - does the previous version work in your system? -
2011/6/14 davidrsmorris <[email protected]>: > Important detail: this is when running the Sid package under Ubuntu > (natty). > That's calling it from my home directory. > It worked initially; I had purged the unpatched version, which had > correctly setup ~/web2py. > Installing the new package worked, but I touched __init__.py to test > the same error on > another machine, which was a clean install. I don't understand what you did. Did it work before you create the __init__.py file or it did't work unless you created it. Could you open a terminal and do this: mkdir /tmp/testw2py cd /tmp/testw2py web2py and then, close it, and send me the terminal output if it fails in some way? Regards. José L. > > Of course, putting __init__.py does not work, and neither does > anything else, including moving the entire ~/web2py directory so that > the package will recreate it. > > On Jun 14, 2:23 am, José Luis Redrejo Rodríguez <[email protected]> > wrote: >> 2011/6/13 davidrsmorris <[email protected]>: >> >> > The patched package only produces "deposit" in web2py folder. >> > I then get the following fatal error message: >> >> > Traceback (most recent call last): >> > File "/usr/bin/web2py", line 87, in <module> >> > if not >> > os.path.exists(module_web2py_applications):open(module_web2py_applications, >> > 'w').close() >> > IOError: [Errno 2] No such file or directory: '/home/dmorris/Downloads/ >> > applications/__init__.py' >> >> How are you launching web2py? from a shell o from the menu?, I guess >> you're launching it from the shell, but in a directory where you've >> created manually the applications directory. If not, please, tell me >> how are you launching it and what was in the directory previously. If >> it was not empty, some of the needed directories might have not been >> created. This is not related to the latest web2py package version, it >> would have happen with any previous version of it.
