This never used to be the case. Since the --template-scripts parameter was added, suddenly deb's are generated that install in usr/local/lib instead of user/lib.
E: python-watchdog: file-in-usr-local usr/local/lib/python2.7/dist-packages/watchdog-0.6.0.egg-info/SOURCES.txt
Ofcourse it helps to add a --python-install-lib flag, nevertheless this is a regression and should be fixed.
It seems that ubuntu's python does this. So it's not caused by fpm at all.
Right, the default behavior of fpm is to use whatever python's default install location is. On ubunut thi sis /usr/local/lib/python... - after installing your packages, python should be able to find them.
The resulting package should be installed the exact same way a 'python setup.py install' or 'easy_install somepackage' would be installed.
Yeah you're right. It's just strange that lintian error just popped up out of nowhere. I just added the flag to change the install lib directory. Maybe you like what I did with fpm: https://github.com/specialunderwear/debianize.sh
hah, I ignore pretty much everything lintian says - most of lintian is about debian policy, practically none of which is meaningful in my life. ;)
Sure, but this one is about separating software you should remove with apt, from software you should remove by hand or with pip.