Whenever I access deluge web, it starts in ?dev=true mode by default. This leads to errors, since I don't package ext-base-debug.js and ext-all-debug.js (they're not included when you run `python setup.py sdist`). If I manually add '?dev=false', it works properly.
I don't think that is the reason, I suspect the actual reason is because you are running a version that includes 'dev' in the number and webui will automatically be set to dev mode. I think sdist should actually export those two debug files, I'll have a look.
That doesn't explain why it worked with previous version (520fc233719a0557b327a156df0637284ab54beb): I packaged it the same way, it too had 'dev' in version string, was missing those two debug files, yet started with ?dev=false by default and worked fine
It's strange, but I re-checked this on three different architectures (i686, arm and mipsel), and it's all the same, the way I described it. As a workaround, for now I'll symlink the missing ext-base-debug.js and ext-all-debug.js to ext-base.js and ext-all.js, respetively, in the packages.
OK, I updated to HEAD, changed version string to '2.0.0.20150902', and now it works in ?dev=false by default. I wonder why it behaved differently before? I also packaged those missing debug .js for development mode to work if triggered manually. A bug in sdist command to skip them?
Thanks to this commit http://git.deluge-torrent.org/deluge/co ... 6d74c3e10a
`python setup.py install` can now be used to generate more slim packages. I just need to edit 'RELEASE-VERSION' to not include 'dev' (this is outside git tree, of course), and all debug files will be skipped. And WEB UI doesn't start in dev mode by default if there's no 'dev' in version string too.
Deluge
