try it like this:

run-standalone.sh python build_fSchedule.py

hmm, I've used py2deb many times to package witter, and today I'm seeing the same error as mentioned in this thread. I suspect something may have changed in the underlying py2deb package that has regressed function. Not exactly sure what is wrong, will see if I can figure it out

ok, so the problem seems to be there is aline in py2deb line 90 which is a new check to see if the path it's been passed starts with a /
the problem here is that the py2deb script given in the devel pages which were linked to earlier says to set the dir to "src"
where src is a subfolder of the current folder holding your project.

the check is wrong because the text says DON'T start with a / but the it actually checks you MUST start with a /

so I reversed the logic, but it then immediately falls over with the subfolders of src which it gets pass with the leading /

so I just commented out the whole check and everything appears to run fine. I'm not sure what this was trying to protect against, but it's broken.

JFYI, I just moved my packaging script from py2deb to the current version of pypackager.

EDIT: The following note concerned py2deb, and not the current version of pypackager, which works great without any hacks. I got confused by playing with both packagers simultaneously.

On my n900 environment, it complained about an 'import *' in the script, but after commenting that out it works great - generates the source tarball as well as a finished deb package to try out before uploading to the autobuilder.

/usr/lib/python2.5/site-packages/py2deb.py - comment out line #635:

Code:

           #from subprocess import *