build failing on debian

[aarons]

I am currently running the 1.1.9 package on my debian box, but wanted to try out the 1.2.0 RC. I successfully built this on my ubuntu machine, but on the debian machine it fails with this:

running build_scripts
error: cannot copy tree 'build/scripts-2.5': not a directory

I dug into this a little and discovered one difference between the two machines is that on ubuntu if I run "python setup.py egg_info" it completes fine, but the same command on the debian box results in:

#python setup.py egg_info
/usr/lib/python2.5/distutils/dist.py:263: UserWarning: Unknown distribution option: 'entry_points'
warnings.warn(msg)
/usr/lib/python2.5/distutils/dist.py:263: UserWarning: Unknown distribution option: 'include_package_data'
warnings.warn(msg)
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help

error: invalid command 'egg_info'

now both machines actually have the egg_info.py files in the right place and all the required packages are installed, it seems, but even if I manually import setuptools.command.egg_info in setup.py it still says it's not a valid command. The behavior is the same with both python 2.5 and 2.6.

Any help would be greatly appreciated.

Also, is it expected behavior that deluge-gtk 1.2.0 cannot connect to a 1.1.9 daemon on another machine?

[andar]

Perhaps you need to update your setuptools installation?

It is expected that a 1.2 client will not connect to a 1.1 daemon as the protocol has changed significantly.

[aarons]

The problem was not at all what I suspected. It was only from debugging other problems (such as all cron jobs failing with 'permission denied') that I fixed it. I had a bad line in /etc/pam.d/common-account for pam_krb5.so. Instead of just 'sufficient' it was ' [default=bad success=ok user_unknown=ignore service_err=ignore system_err=ignore]' which I must have changed while trying to figure out some kerberized ssh problem. I don't understand PAM enough to understand the difference, and I also don't know why the python build was failing from it, but my build now succeeds.

But now that the build has finished, I have another question before I install it:

I'm currently downloading something very very slowly with my current deluged installation. If I shut that down and upgrade deluged, will my downloads resume? If they won't resume automatically, will they resume if I re-add the .torrent (which is something I always had to do when restarting 1.1.9 anyway)?

And finally, the deluge debian directory in subversion doesn't actually work. It appears that Christian Greco has a patch against that to get the debs built. Is there any way we could get those changes made directly to the upstream deluge source?

[andar]

But now that the build has finished, I have another question before I install it:

I'm currently downloading something very very slowly with my current deluged installation. If I shut that down and upgrade deluged, will my downloads resume? If they won't resume automatically, will they resume if I re-add the .torrent (which is something I always had to do when restarting 1.1.9 anyway)?

And finally, the deluge debian directory in subversion doesn't actually work. It appears that Christian Greco has a patch against that to get the debs built. Is there any way we could get those changes made directly to the upstream deluge source?

It should resume your torrent just fine.

The debian/ folder is quite old and should probably be removed.. We could possibly look into updating it in tree.