Permission denied: '/etc/init.d/openerp-server'

[sylvainbannier]

Some permission error when bulding with a normal user :

While:
  Installing openerp-initd-server.

An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File "/mnt/home/syban/projets/inra-cra/trunk/openerp.buildout/eggs/zc.buildout-1.5.2-py2.7.egg/zc/buildout/buildout.py", line 1805, in main
    getattr(buildout, command)(args)
  File "/mnt/home/syban/projets/inra-cra/trunk/openerp.buildout/eggs/zc.buildout-1.5.2-py2.7.egg/zc/buildout/buildout.py", line 584, in install
    installed_files = self[part]._call(recipe.install)
  File "/mnt/home/syban/projets/inra-cra/trunk/openerp.buildout/eggs/zc.buildout-1.5.2-py2.7.egg/zc/buildout/buildout.py", line 1297, in _call
    return f()
  File "/mnt/home/syban/projets/inra-cra/trunk/openerp.buildout/eggs/collective.recipe.template-1.9-py2.7.egg/collective/recipe/template/__init__.py", line 80, in install
    output=open(self.output, "wt")
IOError: [Errno 13] Permission denied: '/etc/init.d/openerp-server'

it seems that the script tries to write to /etc/init.d without suficient permission.

Therefore no openerp-server script is created.

proposal :
create a script with sudo before writing the template in [openerp-initd-server] from profiles/base.cfg

[sylvainbannier]

currently testing this solution

another permission issue

Updating timezone-setup.
/tmp/tmpTo_RX_/run: 1: cannot create /etc/timezone: Permission denied

[kdeldycke]

You're absolutely right. Currently the README says to "not run the script as root", but this is wrong.

Currently I run this script as root in local VMs to quickly create dev and tests environments.

I aim to make this script nicer and sysadmin-friendly but this goal often conflicts with making a fully-automated script. I think these two goals can be reached by making openerp.buildout a little bit more modular. But I'm not sure how, so I need ideas and contributions from people using it in real life.

[kdeldycke]

I've just clarified this situation in the README file in commit c6b4c41 .

Is that enough to close this ticket ?