Sync with upstream version

[tony37]

This repository shows several commits yet the version number is still 1.

[vipulgupta2048]

@tony37 Would that really matter, what version an application is. If the development and maintenance are going at a fast pace or a major new feature has been released. Then a change of versions could be taken into account. Do provide more details on the same.

[quozl]

@vipulgupta2048 the problem is real, but the cause is not obvious.

Problem is that activity/activity.info shows v1, so if a bundle is made from this repository now, it will not be installed on a Sugar system that already has v1 from activities.sugarlabs.org.

Cause is that @ezequielpereira did add dependency missing warning feature but without releasing a new version.

I've checked by unpacking the bundle from activities.sugarlabs.org, and commit 51f60ec is identical to v1. So I have tagged it v1 and pushed the tag.

An activity maintainer, if you'd like to take that role, would fix the bugs and release a v2. That's what @tony37 is effectively suggesting by opening this issue. See Modifying Activities - Checklist Maintainer for what steps are needed.

Also, this activity is a wrapper around an upstream project, and there's a new version upstream, so it would be sensible to merge that too.

[rhl-bthr]

• Sync with upstream project
• Update version number
• ASLO release