[Sugar-devel] clash of user- and system-installed activities (was: Release Physics-3)

Jonas Smedegaard dr at jones.dk
Fri Aug 28 17:36:24 EDT 2009

On Fri, Aug 28, 2009 at 10:15:09PM +0100, Gary C Martin wrote:
>On 28 Aug 2009, at 21:42, Walter Bender wrote:
>> On Fri, Aug 28, 2009 at 11:53 AM, Jonas Smedegaard<dr at jones.dk> wrote:
>>> On Fri, Aug 28, 2009 at 02:15:29PM +0100, Gary C Martin wrote:
>>>> Hi Dave,
>>>> Do you have Physics-2 installed on the SoaS? Depending on the SoaS 
>>>> version you have, the early ones had Activities installed in non- 
>>>> standard places, with non user permissions, and sometimes symbolic 
>>>> links :-( You would need to drop down into terminal, find and 
>>>> remove that Physics.activity folder. Then the normal install 
>>>> process should work as normal.
>>>> FWIW: On old SoaS, my first task would be to drop into the Terminal 
>>>> and clean this all up manually, so that all the *.activity 
>>>> directories were migrated the expected ~/Activities, and ownership 
>>>> permissions of them given back to the user (recursive chown on 
>>>> ~/Activities). In the current SoaS activities are installed from 
>>>> their .xo bundles so this is no longer an issue :-)
>>> Is this an issue specific to SoaS and/or Physics, or generally a 
>>> limitation of current Sugar that older system-installed Activities 
>>> disturb newer user-installed ones?
>>> (or did I get it wrong that that was the actual issue here?)
>> I think you got it right.

Thanks for the confirmation, Walter :-)

>Dave reported (off-list) that a manual deletion of v2, reboot, and
>then install of v3 worked fine. My radar was going off regarding the
>addition of MIME support, as I have a few hairs standing up on the
>back of my neck about how Sugar deals with that step. Almost no
>activities except pre-installed Fructose have exercised this code path
>much, sugar-install-bundle was doing odd things as I was having to
>reboot for the activity to show up, so I assume it was silently
>borking some place, but installing an .xo via Journal (equiv. Browse
>download) was running just fine.

Not quite sure I understand this fully, but seems to be tied to b tied 
to doing system installs directly into the running system - as opposed 
to installing into a packaging environment and use that for the final 

In other words, I will try to keep this in the back of my head but for 
now don't expect it to be a problem for Debian-packages Sugar 

thanks for elaborating!

  - Jonas

* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: Digital signature
Url : http://lists.sugarlabs.org/archive/sugar-devel/attachments/20090828/2c8662c7/attachment.pgp 

More information about the Sugar-devel mailing list