Thunderbird 8 transition

Builds are available for testing in ppa:ubuntu-mozilla-security/ppa

This bug was fixed in the package enigmail - 2:1.3.2-0ubuntu1.3

---------------
enigmail (2:1.3.2-0ubuntu1.3) oneiric-security; urgency=low

  * Rebuild for Thunderbird 8 (LP: #894593)
  * Change TBIRD_SDK path to be generic instead of version specific
    - update debian/rules
 -- Chris Coulson <email address hidden> Thu, 24 Nov 2011 19:22:21 -0600

This bug was fixed in the package lightning-extension - 1.0+build1-0ubuntu0.11.10.2

---------------
lightning-extension (1.0+build1-0ubuntu0.11.10.2) oneiric-security; urgency=low

  * New upstream stable release (CALENDAR_1_0_BUILD1) (LP: #894593)

  * Add db/mork/Makefile.in to the tarball
    - update debian/rules
 -- Chris Coulson <email address hidden> Thu, 24 Nov 2011 19:12:35 -0600

thunderbird (8.0+build1-0ubuntu0.11.10.1) oneiric-security; urgency=low

  * New upstream stable release v8.0 (THUNDERBIRD_8_0_BUILD1)

  * Update messagingmenu-extension to 0.8.3
    - This version backs out the change made in 7.0.1+build1+nobinonly-0ubuntu2
      that didn't fix LP#850229
  * Don't disable our bundled addons on upgrade
    - update debian/vendor.js
  * Move custom scripts to debian/build
    - move debian/get-xpi-id.py to debian/build/get-xpi-id.py
    - move debian/refresh-supported-locales.pl to
       debian/build/refresh-supported-locales.pl
    - move debian/extract-file.py to debian/build/extract-file.py
    - move debian/testsuite.mk to debian/build
    - update debian/rules
  * Shrink the default mozconfig right down so that we use mostly upstream
    defaults, rather than overriding them with our own options. It is still
    possible to override them though. We also drop the pkg-config checks in
    debian/rules which allowed a fallback build configuration when dependencies
    aren't satisfied. Really, the build should just fail here rather than
    continuing in some undesirable fallback mode
    - update debian/thunderbird-dev.links.in
    - update debian/mozconfig.in
    - update debian/control.in
    - update debian/rules
  * Refresh build-depends, as this hasn't been done for a while:
    - Drop patchutils, libxft-dev, libxinerama-dev, libgnome2-dev, sharutils
      and bzip2. These don't appear to be needed
    - Drop liborbit2-dev - only appears to be required if there is no libidl
    - Add libglib2.0-dev, libext-dev, libfontconfig1-dev and libpango1.0-dev,
      as the configure script checks for these directly
    - Add minimum versions to libgconf2-dev, libgnomevfs2-dev, yasm and
      libgnomeui-dev
    - Specify minimum versions for libnspr4-dev, libcairo2-dev, libsqlite3-dev
      and libnss3-dev when using system versions of those libs
  * Introduce a branch config file (debian/config/branch.mk) which holds
    settings which shouldn't be merged between branches (eg, whether
    the crash reporter should be enabled)
    - add debian/config/branch.mk
    - update debian/rules
  * Move debian/locales.* to debian/config
    - move debian/locales.shipped => debian/config/locales.shipped
    - move debian/locales.unavail => debian/config/locales.unavail
    - update debian/rules
    - update debian/build/refresh-supported-locales.pl
  * Move debian/mozconfig.in to debian/config
  * Touch debian/control.in during clean to force a refresh of debian/control,
    so we can check if it is out-of-date and fail if it is
    - update debian/rules
  * Refresh patches:
    - update debian/patches/ctypes-callback-reentry-fix.patch
    - update debian/patches/theme-refresh-compose-toolbar-icons.patch
    - update debian/patches/theme-refresh-message-header-buttons.patch
  * Drop the mozilla-devscripts dependency. We were only using this for creating
    tarballs anyway. Instead, implement our own get-orig-source target, which
    also fixes some problems we were having
    - update debian/control.in
    - remove debian/moz-rev.sh
    - update debian/rules
 ...