karmic build of a firefox extension behaves oddly

[Brian Murray]

Binary package hint: mozilla-devscripts

I'm followed the instructions at https://wiki.ubuntu.com/MozillaTeam/Extensions/Packaging to create an extension which is available at https://edge.launchpad.net/~gm-dev-launchpad/+archive/ppa. The source code is at https://code.edge.launchpad.net/~brian-murray/firefox-extensions/lp-improvements.ubuntu.

When I try to build the package on karmic now it behaves quite oddly and does not show up as an extension anymore. However, if I build it on Jaunty the extension behaves correctly. I'd imagine this is due to some change in mozilla-devscripts but I'm not certain how extension building works at all.

[Benjamin Drung (bdrung)]

This is a bug in the install.rdf parser. There are different formats used for install.rdf. Currently following extensions do not work:

mozilla-stumbleupon
lp-improvements
ctxextensions (remove install.rdf.patch - this patch is a workaround)
pwdhash (remove install.rdf.patch - this patch is a workaround)

[Launchpad Janitor (janitor)]

This bug was fixed in the package mozilla-devscripts - 0.16

---------------
mozilla-devscripts (0.16) unstable; urgency=low

  [ Benjamin Drung <email address hidden> ]
  * xpi.mk:
    - List all phony target and run dh_clean for all packages. These changes
      makes it possible to use xpi.mk without cdbs in a simple way.
      - update src/xpi.mk
    - MOZ_EXTENSION_PKG is defined in either case, removing missing case handler
      - update src/xpi.mk
    - rename stamp-* targets to *-stamp, merge stamp-extension-install into
      xpi-install, merge xpi-clean into clean
      - update src/xpi.mk
    - Guess common license file names if MOZ_XPI_DOCUMENTED_LICENSE_FILES is
      not set.
      - update src/xpi.mk
    - simplify xpi-depends-stamp rule
      - update src/xpi.mk
    - override files on xpi extraction (otherwise running build target would
      require user interaction)
      - update src/xpi.mk
    - only list packages in ${xpi:Depends} if they are available in the archive
      and add lsb-release as dependency
      - update src/xpi.mk
      - update debian/control
    - rename ${xpi:Depends} to ${xpi:Recommends} and keep ${xpi:Depends} for
      backwards compatibility
      - update src/xpi.mk
    - add ${xpi:Provides} and ${xpi:Enhances} to support the Debian policy for
      packaging extensions: http://wiki.debian.org/Teams/DebianMozExtTeam
      - update src/xpi.mk
    - "mkdir -p" can be run in all cases
      - update src/xpi.mk
    - add sanity check for xpi file and fail with useful error messages
      - update src/xpi.mk
    - support different types of install.rdf files (LP: #422898)
      - update src/xpi.mk
    - add MOZ_EXT_NAME option (used for calculating xpi:Provides)
      - update src/xpi.mk
  * packaging:
    - allow uploads done by Debian Maintainers
      - update debian/control
  * med-xpi-{pack,unpack}:
    - add parenthesis to $1 to avoid problems if $1 is empty
      - update src/med-xpi-pack
      - update src/med-xpi-unpack
    - replace \n in echo commands with an extra empty echo command to avoid
      bashism (Closes: #547755)
      - update src/med-xpi-pack
      - update src/med-xpi-unpack

  [ Alexander Sack <email address hidden> ]
  + mozclient: use stable awesome-browser branding branch for firefox-3.0
    - update src/mozclient/firefox-3.0.conf
  + xpi.mk:
    - install extension tree to /usr/share or /usr/lib based on Architecture:
      field in debian/control for the target package
      - update src/xpi.mk

 -- Alexander Sack <email address hidden> Fri, 02 Oct 2009 12:56:50 +0100