[Bugs] #2452 UNSP: Sugar should not offer to upgrade system activities
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Thu Oct 21 10:26:46 EDT 2010
#2452: Sugar should not offer to upgrade system activities
------------------------------------------+---------------------------------
Reporter: lfaraone | Owner: tomeu
Type: enhancement | Status: new
Priority: Unspecified by Maintainer | Milestone: Unspecified by Release Team
Component: sugar | Version: Unspecified
Severity: Unspecified | Keywords:
Status_field: Unconfirmed | Distribution: Ubuntu
Seeta_dev: |
------------------------------------------+---------------------------------
Comment(by lfaraone):
Replying to [comment:1 walter]:
> We have discussed this ad nauseum. The consensus (I'll look for the
thread) was that we want to let users install new versions in
~/Activities/ but not over-write the installed versions in /usr/share. We
also have support for a list of activities that cannot be deleted. That
said, it sounds like the problem you are describing is better
characterized by our not properly tagging a upgrade for which versions of
Sugar it runs on and by our not bundling with the activity any
dependencies that may be distro-specific. I'd suggest opening a new ticket
specific to the activity that failed to install properly.
Sometimes is that XO-bundled activities that are not pure-python are
bundling
dependencies that we *already package* in Ubuntu, but for some reason the
bundle's precompiled version is not binary-compatible with Ubuntu. From a
system distribution standpoint, we don't want globally installed
activities to
be updated via the Sugar updater.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/2452#comment:2>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list