[Live-demo] [OSGeo] #992: chroot build method: sahana does not start

[OSGeo]

#992: chroot build method: sahana does not start
----------------------+-----------------------------------------------------
 Reporter:  kalxas    |       Owner:  live-demo@…              
     Type:  defect    |      Status:  new                      
 Priority:  critical  |   Milestone:  OSGeoLive6.0RC1          
Component:  LiveDVD   |    Keywords:  6.0 beta9                
----------------------+-----------------------------------------------------
Changes (by hamish):

 * cc: rediguana, flavour (added)


Comment:

 We've done our best at fixing a lot of the permissions problems. What
 remains are just under 1000 files in the web2py file tree which seem to be
 created by these two commands in the install_sahana.sh script:

 {{{
 sudo -H -u "$USER_NAME" python web2py.py -S eden -M \
    -R applications/eden/static/scripts/tools/noop.py

 [...]

 sudo -H -u "$USER_NAME" python web2py.py -S eden -M \
    -R applications/eden/static/scripts/tools/compile.py
 }}}

 which I assume is byte compiling the .pyc files, but it seems that it is
 doing more as well?

 the trouble is that the user at build time (UID 1000) is not the same as
 the user at run time (UID 999), so all of the files which # 999 wants to
 write to are owned by another (non-existent) user. In any event, the user
 shouldn't be owning files outside of the home dir*.

 [*] if they need to be writable, we can make them belong to a group which
 the user has write permissions for, but we need to know which files need
 that.

 Also a long-term goal is to allow additional users to be added later (in a
 VM or install-from-disc), so locking it to the single user account isn't
 desirable.


 So, how to go about running the above web2py.py commands if "$USER_NAME"
 won't exist later?


 thanks,
 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/992#comment:2>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.