Update to 20.0

Bug #1161422 reported by Chris Coulson on 2013-03-28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Launchpad Janitor (janitor) wrote :
Download full text (13.7 KiB)

This bug was fixed in the package firefox - 20.0+build1-0ubuntu0.12.10.3

firefox (20.0+build1-0ubuntu0.12.10.3) quantal-security; urgency=low

  * New upstream stable release (FIREFOX_20_0_BUILD1)
    - see LP: #1161422 for USN information

  * Update globalmenu-extension to 3.9
    - Firefox 20 compatibility fixes
    - This is the last version of this addon, and will be dropped in the
      next Firefox release
  * Drop patches fixed upstream
    - remove debian/patches/ionmonkey-hardfp-support.patch
    - update debian/patches/series.in
  * firefox-gnome-support needs explicit dependency on libnotify
    - update debian/control{,.in}
  * Add support for autopkgtest, package the xpcshell, reftest and
    mochitest testsuites and migrate the xpcshell-tests, reftest, crashtest,
    jstestbrowser and mochitest targets to this. Note that tests that can't
    be ran as an autopkgtest (eg, if they require write permissions to the
    application directory) will still be ran at build time
    - add firefox-testsuite package in debian/control.in
    - update debian/control
    - add debian/firefox-testsuite.install.in
    - add debian/firefox-testsuite.links.in
    - update debian/build/mozbuild.mk
    - update debian/rules
    - drop xpcshell-tests, reftest, crashtest, jstestbrowser and mochitest
      targets from debian/build/testsuite.mk, add xpcshell-tests-build
      and the ability to run xpcshell-tests with our own reduced manifest
    - add debian/tests/control
    - add debian/tests/crashtest
    - add debian/tests/jstestbrowser
    - add debian/tests/mochitest
    - add debian/tests/reftest
    - add debian/tests/xpcshell-tests
    - add debian/testing/run_mochitest.in
    - add debian/testing/run_xpcshell_tests.in
    - add debian/testing/run_reftest.in
    - add debian/testing/testrunhelper.py
    - update debian/config/mozconfig.in to always build with --enable-tests
    - add debian/testing/xpcshell-build.ini
  * Ensure that the directory provider returns all searchplugin paths during
    the search service xpcshell tests
    - add d/p/test-fixes/xpcshell-search-fix-browser-dirprovider.patch
    - update debian/patches/series.in
  * Fix various tests that assume that either the application directory or
    test directory can be written to
    - add d/p/test-fixes/xpcshell-docshell-no-writes-to-appdir.patch
    - add d/p/test-fixes/xpcshell-contentprefs-no-writes-to-appdir.patch
    - add d/p/test-fixes/xpcshell-exthandler-no-writes-to-appdir.patch
    - add d/p/test-fixes/xpcshell-ctypes-no-writes-to-appdir.patch
    - add d/p/test-fixes/xpcshell-xpcom-no-writes-to-testdir-or-appdir.patch
    - add d/p/test-fixes/xpcshell-libpref-no-writes-to-testdir.patch
    - update debian/patches/series.in
  * Export NO_PNG_PKG_MANGLE as optipng breaks tests that are dependent
    on image format / size
    - update debian/build/mozbuild.mk
  * Don't test that the addon selection dialog appears in test_bug596343.js,
    as we disable this
    - add d/p/test-integration/xpcshell-disable-addon-select-dialog-test-for-adt.patch
    - update debian/patches/series
  * Don't write a log file to the script directory from mochitest
    - ...

Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
description: updated
Mark Burgess (mcburgess136) wrote :

I don't know if i'm doing this right......re bug 1161422, I can't update my newest releases. what do I do?

Maybe you need to provide a little more informations, which ubuntu release? Which sources.list do you have? Did you run apt-get update?

And of course opening a new bug with ubuntu-bug firefox would help a lot, since it will provide so many useful informations.

Feel free to link the new bug here or privately to me

Chris Coulson (chrisccoulson) wrote :

To be honest, you'd be better off first asking somewhere like http://askubuntu.com/ or http://ubuntuforums.org/forum.php, and only reporting a bug once you've actually established that one exists. Your comment suggests that you're looking for help rather than wanting to report a bug

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers