Many thanks for your help. I tried running the command you suggest: python setup.py sdist
but I get the following error, even if I am running the command as root: running sdist running egg_info writing requirements to test.egg-info/requires.txt writing test.egg-info/PKG-INFO writing top-level names to test.egg-info/top_level.txt writing dependency_links to test.egg-info/dependency_links.txt writing entry points to test.egg-info/entry_points.txt writing paster_plugins to test.egg-info/paster_plugins.txt reading manifest file 'test.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'test.egg-info/SOURCES.txt' warning: sdist: missing required meta-data: url warning: sdist: missing meta-data: either (author and author_email) or (maintainer and maintainer_email) must be supplied creating test-0.1dev creating test-0.1dev/test creating test-0.1dev/test.egg-info creating test-0.1dev/test/config creating test-0.1dev/test/controllers creating test-0.1dev/test/i18n creating test-0.1dev/test/i18n/ru creating test-0.1dev/test/i18n/ru/LC_MESSAGES creating test-0.1dev/test/lib creating test-0.1dev/test/model creating test-0.1dev/test/public creating test-0.1dev/test/public/css creating test-0.1dev/test/public/images creating test-0.1dev/test/templates creating test-0.1dev/test/tests creating test-0.1dev/test/tests/functional creating test-0.1dev/test/tests/models making hard links in test-0.1dev... hard linking MANIFEST.in -> test-0.1dev error: Operation not permitted Many thanks for any clue as to what I am doing wrong. Michael Pedersen-2 wrote: > > On Mon, Oct 15, 2012 at 9:34 AM, sk78 <[email protected]> wrote: >> Thanks for your reply. >> Yes, I had already generated the test-0.1dev-py2.6.egg file by typing >> sudo >> python setup.py bdist_egg and then copied the generated egg file from the >> project/dist/ folder to the other computer where I want to deploy. I had >> installed easy_install on the computer. But when I tried: sudo >> easy_install >> test-0.1dev-py2.6.egg I got the error message I mentioned. >> Do I need to copy anything else other than the egg file onto the >> deployment >> computer to make it work? >> Many thanks again. > > Using the "bdist_egg" to install is usually going to be problematic. > The reason for this is that the egg is built in a binary mode. This > means that if, for any reason, the remote system is unable use the egg > (different Python version, for one example), easy_install will try to > find the egg of PyPI. Since your egg doesn't exist there yet, it > fails. > > The better solution, in my opinion, is to use "python setup.py sdist" > which will build a source .tar.gz file which is portable across > environments. That will result in something you can safely install on > the remote site. > > -- > Michael J. Pedersen > My Online Resume: http://www.icelus.org/ -- Google+ > http://plus.ly/pedersen > Google Talk: [email protected] -- Twitter: pedersentg > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. > > > -- View this message in context: http://old.nabble.com/Deployment-problem-of-TG-tp34547430p34562487.html Sent from the Turbogears General mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
