[Live-demo] [OSGeo] #1215: ossim ipython profile not working from chroot

[OSGeo]

#1215: ossim ipython profile not working from chroot
---------------------+------------------------------------------------------
 Reporter:  hamish   |       Owner:  live-demo@…              
     Type:  defect   |      Status:  new                      
 Priority:  major    |   Milestone:  OSGeoLive7.0             
Component:  LiveDVD  |    Keywords:  ossim, ipython           
---------------------+------------------------------------------------------
 Hi,

 the install_ipython.sh script pre-seeds a profile for ossim, but the funny
 thing insists on writing to $HOME but doesn't like being run as sudo -u.
 So the workaround for 6.5 was to run as root in the install script then
 move the files over to $USER_HOME. that isn't working anymore.

 {{{
 mkdir -p "$USER_HOME"/.config/
 ipython profile create osgeolive
 mv ~/.ipython "$USER_HOME"/.config/ipython
 }}}

 but it is causing an error: (chroot's "root" home dir is /roots/)

 {{{
 /usr/lib/python2.7/dist-packages/IPython/utils/path.py:296: UserWarning:
 IPython parent '/roots' is not a writable location, using a temp
 directory.
   " using a temp directory."%parent)
 [ProfileCreate] Generating default config file:
 u'/tmp/tmpTWZYb5/profile_osgeolive/ipython_config.py'
 [ProfileCreate] Generating default config file:
 u'/tmp/tmpTWZYb5/profile_osgeolive/ipython_qtconsole_config.py'
 [ProfileCreate] Generating default config file:
 u'/tmp/tmpTWZYb5/profile_osgeolive/ipython_notebook_config.py'
 mv: cannot stat `/roots/.ipython': No such file or directory
 sed: can't read /home/user/.config/ipython/profile_osgeolive/*.py: No such
 file or directory
 cp: cannot stat `/home/user/.config/ipython': No such file or directory
 ./install_ipython.sh: 72: ./install_ipython.sh: cannot create
 /home/user/.config/ipython/profile_osgeolive/ipython_notebook_config.py:
 Directory nonexistent
 cp: cannot stat
 `/home/user/.config/ipython/profile_osgeolive/ipython_notebook_config.py':
 No such file or directory
 }}}

 maybe "su -" as the $USER would work instead? someone with access to the
 chroot environ might have to play to see what works..


 thanks,
 Hamish

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