On 28 Aug 2009, at 21:42, Walter Bender wrote: > On Fri, Aug 28, 2009 at 11:53 AM, Jonas Smedegaard<d...@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. > > -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. Regards, --Gary _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel