[Bugs] #2174 UNSP: FTBFS: sugar.bundle.bundle.MalformedBundleException: Activity bundle /home/sascha.silbe/sugar-jhbuild/source/pippy must specify either class or exec
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Sun Jan 30 07:42:45 EST 2011
#2174: FTBFS: sugar.bundle.bundle.MalformedBundleException: Activity bundle
/home/sascha.silbe/sugar-jhbuild/source/pippy must specify either class or
exec
------------------------------------------+---------------------------------
Reporter: sascha_silbe | Owner: lfaraone
Type: defect | Status: closed
Priority: Unspecified by Maintainer | Milestone: 0.90
Component: Pippy | Version: Git as of bugdate
Severity: Blocker | Resolution: fixed
Keywords: | Status_field: Needinfo
Distribution: | Seeta_dev:
------------------------------------------+---------------------------------
Changes (by sascha_silbe):
* status: new => closed
* resolution: => fixed
Comment:
Replying to [comment:1 m_anish]:
> Can you try building again from the latest pippy/mainline snapshot. I
also used to get a deprecation warning that exec must be used instead of
class, but the build never failed.
Yes, the [http://git.sugarlabs.org/sugar-
toolkit/mainline/commit/e11b7d319626691a18db3b3e87f5f66c04102695 commit]
that removed support for <code>class</code> was [http://git.sugarlabs.org
/sugar-toolkit/mainline/commit/acd8095a29f2f922acce3e907fb71a6019eff113
reverted] a day later because [ticket:2175#comment:1 too many activities
broke].
> The relevant
[http://git.sugarlabs.org/projects/pippy/repos/mainline/commits/c91ec26a92cbb4697876227990912ea530dbd1d9
commit] is here.
Thanks! I can confirm that the latest git version of Pippy doesn't trigger
the corresponding warnings.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/2174#comment:3>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list