'actions' menu missing due to wrong API code in plugins

[KFJ]

Hugin has a new python interface, and the plugins which are installed together with the application show up in an 'actions' menu. To make sure that the plugins will function with the version of hugin they're installed together with, they are coded as to which API versions they will function with. This is done by setting two lines in the plugin like this:

# @api-min 2011.1
# @api-max 2011.5

these lines would mean that the plugin is all right with API versions (or hugin versions) 2011.1 to 2011.5. If the API version is outside the indicated values, the plugin will not load.

When I looked at the plugins coming with the 2011.4 package for Kubuntu 12.4, I noticed that the actions menu was missing altogether, and being the guy who wrote the python interface, I quickly figured out the problem was that the API codes were wrong. The remedy is simple; the API code in the plugins has to be adapted to the hugin version. The idea is to test-run the plugins once before committing to distribure and then tag them appropriately. The plugins coming with hugin are definitely fine up to 2011.4, but they're tagged to only work up to 2011.2. Obviously the test-run was omitted and noone adapted the API version tag.

So the bug is easily fixed: in all plugins being dissiminated in the hugin 2011.4 package, api-max should be set to 2011.4. This affects all python files going to /usr/local/share/hugin/date/plugins and -/plugins-templates.

[Andreas Metzler (k-launchpad-downhill-at-eu-org)]

This is fixed in 2011.4.0+dfsg-4, just uploaded to Debian/unstable.

[Launchpad Janitor (janitor)]

This bug was fixed in the package hugin - 2011.4.0+dfsg-5

---------------
hugin (2011.4.0+dfsg-5) unstable; urgency=low

  * Set PythonLibs_FIND_VERSION to make sure the library corresponding to
    pyversions -d is found. (Otherwise we will get a FTBFS if e.g.
    python3.2-dev is *also* installed.)

 -- Andreas Metzler <email address hidden> Sun, 17 Jun 2012 13:26:26 +0200