* New upstream stable release (FIREFOX_25_0_BUILD3)
- see LP: #1245414 for USN information
[ Chris Coulson <email address hidden> ]
* Refresh patches
- update d/p/test-fixes/xpcshell-docshell-no-writes-to-appdir.patch
- update d/p/test-integration/xpcshell-write-time-for-failed-test.patch
- update debian/patches/ubuntu-ua-string-changes.patch
- update d/p/test-fixes/xpcshell-exthandler-no-writes-to-appdir.patch
- update d/p/test-integration/automation-output-junit-xml.patch
- update d/p/test-integration/mochitest-allow-test-manifest-for-browser-chrome.patch
- update d/p/test-integration/xpcshell-disable-tests-which-need-appdir-write-access.patch
- update debian/patches/unity-menubar.patch
* Drop patches
- remove d/p/test-fixes/xpcshell-docshell-no-writes-to-appdir.patch
- remove d/p/test-fixes/xpcshell-contentprefs-no-writes-to-appdir.patch
- remove d/p/test-fixes/mochitest-browser-plugincrash-with-no-crashreporter.patch
- update debian/patches/series
* Refactor the test results post-process script a bit so that it can use
regular expressions in the configuration
- update debian/testing/filter_results
- update debian/testing/results-filter-manifest.json
- update debian/tests/post-process
* Run mochitest-plain in 5 chunks, similar to upstream. This should fix
some test failures we see that seem to be caused by some tests not
cleaning up properly (seems to fix LP: #1158781 and LP: #1194448)
- update debian/testing/run_mochitest.in
- update debian/tests/control
- move debian/tests/mochitest => debian/tests/mochitest-1
- add debian/tests/mochitest-2
- add debian/tests/mochitest-3
- add debian/tests/mochitest-4
- add debian/tests/mochitest-5
* Drop d/p/test-integration/test-sameoriginpolicy-debug.patch now that
we run mochitest-plain in chunks
* Add OCSPStaplingServer binary to testsuite
- update debian/firefox-testsuite.install.in
- update debian/build/rules.mk
* Don't let make check failures fail the build for now, as there are some
jit test failures
- update debian/build/testsuite.mk
* Try to stop the buildd's from terminating the build during long links
(use a hack based on the one for the Chromium package)
- add debian/build/keepalive-wrapper.py
- update debian/build/rules.mk
[ Jamie Strandboge <email address hidden> ]
* add debian/usr.bin.firefox.apparmor.13.10 for dbus policy
* debian/rules: conditionally use usr.bin.firefox.apparmor.13.10 on saucy
and higher, otherwise usr.bin.firefox.apparmor.12.04
* debian/usr.bin.firefox.apparmor.12.04: use ibus abstraction
-- Chris Coulson <email address hidden> Mon, 28 Oct 2013 10:16:16 +0000
This bug was fixed in the package firefox - 25.0+build3- 0ubuntu0. 13.10.1
--------------- 0ubuntu0. 13.10.1) saucy-security; urgency=low
firefox (25.0+build3-
* New upstream stable release (FIREFOX_ 25_0_BUILD3)
- see LP: #1245414 for USN information
[ Chris Coulson <email address hidden> ] fixes/xpcshell- docshell- no-writes- to-appdir. patch integration/ xpcshell- write-time- for-failed- test.patch patches/ ubuntu- ua-string- changes. patch fixes/xpcshell- exthandler- no-writes- to-appdir. patch integration/ automation- output- junit-xml. patch integration/ mochitest- allow-test- manifest- for-browser- chrome. patch integration/ xpcshell- disable- tests-which- need-appdir- write-access. patch patches/ unity-menubar. patch fixes/xpcshell- docshell- no-writes- to-appdir. patch fixes/xpcshell- contentprefs- no-writes- to-appdir. patch fixes/mochitest -browser- plugincrash- with-no- crashreporter. patch patches/ series testing/ filter_ results testing/ results- filter- manifest. json tests/post- process testing/ run_mochitest. in tests/control tests/mochitest => debian/ tests/mochitest -1 tests/mochitest -2 tests/mochitest -3 tests/mochitest -4 tests/mochitest -5 integration/ test-sameorigin policy- debug.patch now that firefox- testsuite. install. in build/rules. mk build/testsuite .mk build/keepalive -wrapper. py build/rules. mk
* Refresh patches
- update d/p/test-
- update d/p/test-
- update debian/
- update d/p/test-
- update d/p/test-
- update d/p/test-
- update d/p/test-
- update debian/
* Drop patches
- remove d/p/test-
- remove d/p/test-
- remove d/p/test-
- update debian/
* Refactor the test results post-process script a bit so that it can use
regular expressions in the configuration
- update debian/
- update debian/
- update debian/
* Run mochitest-plain in 5 chunks, similar to upstream. This should fix
some test failures we see that seem to be caused by some tests not
cleaning up properly (seems to fix LP: #1158781 and LP: #1194448)
- update debian/
- update debian/
- move debian/
- add debian/
- add debian/
- add debian/
- add debian/
* Drop d/p/test-
we run mochitest-plain in chunks
* Add OCSPStaplingServer binary to testsuite
- update debian/
- update debian/
* Don't let make check failures fail the build for now, as there are some
jit test failures
- update debian/
* Try to stop the buildd's from terminating the build during long links
(use a hack based on the one for the Chromium package)
- add debian/
- update debian/
[ Jamie Strandboge <email address hidden> ] usr.bin. firefox. apparmor. 13.10 for dbus policy firefox. apparmor. 13.10 on saucy firefox. apparmor. 12.04 usr.bin. firefox. apparmor. 12.04: use ibus abstraction
* add debian/
* debian/rules: conditionally use usr.bin.
and higher, otherwise usr.bin.
* debian/
-- Chris Coulson <email address hidden> Mon, 28 Oct 2013 10:16:16 +0000