Some bundles install correctly using sugar-install-bundle but not through the Journal

[bemasc]

The bundle at

 http://dev.laptop.org/~bemasc/ACBLSCOR-1.xo

installs and runs perfectly using the sugar-install-bundle command at the Terminal, but fails to install or run when launched from the Journal. The Journal only unpacks the bundle partially. For example, it unpacks the contents of ACBLSCOR.activity/, but not ACBLSCOR.activity/activity/.

It is worth noting that this bundle was not created using bundlebuilder. Bundlebuilder does not support symlinks, and I need correct handling of symlinks inside this bundle. Therefore, the bundle is created by the "bundle.sh" script included in the .xo.

Until this is fixed, I have to tell users to install this using wget and sugar-install-bundle, because they cannot use Browse and the Journal.

[erikos]

Do you mean #165? Please state what version you are using.

[erikos]

The installation has been fixed with #165. Uninstalling your activity does not work, though.

Traceback (most recent call last):
  File "/home/erikos/sugar-jhbuild/install/lib/python2.5/site-packages/jarabe/desktop/homebox.py", line 111, in __erase_confirmation_dialog_
response_cb
    registry.uninstall(bundle)
  File "/home/erikos/sugar-jhbuild/install/lib/python2.5/site-packages/jarabe/model/bundleregistry.py", line 317, in uninstall
    bundle.uninstall(install_path, force)
  File "/home/erikos/sugar-jhbuild/install/lib/python2.5/site-packages/sugar/bundle/activitybundle.py", line 375, in uninstall
    self._uninstall(install_path)
  File "/home/erikos/sugar-jhbuild/install/lib/python2.5/site-packages/sugar/bundle/bundle.py", line 194, in _uninstall
    os.rmdir(os.path.join(root, name))
OSError: [Errno 20] Not a directory: '/home/erikos/Activities/ACBLSCOR.activity/dosemu_install/dosemu/drive_z'

The file it chokes is a broken symbolic link.
Activities/ACBLSCOR.activity/dosemu_install/dosemu/drive_z: broken symbolic link to `freedos'

[erikos]

The installation of the activity bundles is fixed - we follow up the symlink problem in ticket #171.