| 154
|
|
|
Chris Coulson |
14.0.1+build1-0ubuntu0.12.04.1 |
11 years ago
|
 |
|
| 153
|
|
|
Micah Gersten |
13.0.1+build1-0ubuntu0.12.04.1 |
11 years ago
|
|
|
| 152
|
|
|
Chris Coulson |
13.0+build1-0ubuntu0.12.04.1 |
11 years ago
|
|
|
| 151
|
|
|
Chris Coulson |
12.0+build1-0ubuntu0.12.04.1 |
12 years ago
|
|
|
| 150
|
|
|
Chris Coulson |
11.0+build1-0ubuntu4 |
12 years ago
|
|
|
| 149
|
|
|
Chris Coulson |
11.0+build1-0ubuntu3 |
12 years ago
|
|
|
| 148
|
|
* Update globalmenu-extension to 3.0.1
- Reduce our memory footprint a bit, which wasn't really a lot anyway
- Avoid the use of the component manager for accessing commonly used
services, where "commonly used" means "accessed when building every
menu item". This should save some CPU cycles when building or
refreshing menus
- Try to recycle menuitems when they are removed from a menu by
adding contiguous blocks of removed items to a "free list" which
is emptied asynchronously, and reusing the items in this list when
new items are added in place of the removed items. This means that
refreshing the history menu contents when the menu is opened no
longer alters the menu structure, but results in a shifting of
properties between existing nodes instead. This has a few benefits:
+ With no layout changes, unity-panel-service doesn't request
the entire menu structure, which significantly reduces dbus traffic
and makes it much faster to refresh the menu contents
+ The size of the menu doesn't change when it is refreshed, which
eliminates the flicker that used to occur when opening the history
menu.
+ The HUD can refresh our menus now without triggering layout updates
(assuming that menu layout really hasn't changed, eg, by adding
a bookmark)
- Remove all use of the global observer service for sending our own
internal notifications around
- Clean up the way we ensure that the correct edit commands are
enabled by just installing our own popupshowing handler rather
than using an additional notification to fix things up after the
default handler runs
- Get rid of a static initializer
- Don't support older than Firefox 11
- Fix some GError leaks
- Hide the internal menu when creating a native menu, rather than
waiting for confirmation that the native menu is registered
successfully. We don't try to create a native menu if we don't
find a menu service to register the menu with anyway
- Keep menu contents updated whilst the menu is open, rather than
just whilst it is opening
|
Chris Coulson |
11.0+build1-0ubuntu2 |
12 years ago
|
|
|
| 147
|
|
* New upstream stable release (FIREFOX_11_0_BUILD1)
* Clean up search plugin installation now that we build our own
language packs:
- Drop the recursive symlink from /usr/lib/firefox-addons/searchplugins,
which lintian kept complaining about
- Don't effectively symlink distribution/searchplugins to searchplugins,
as they have different layouts and this avoids the same data being
iterated over twice
- Revert to the upstream layout in distribution/searchplugins
- Simplify distro-locale-searchplugins.patch, as we don't need to swap the
loading order of common / locale-specific searchplugin paths now.
$LIBDIR/distribution/searchplugins/common is no longer a symlink
to $LIBDIR/searchplugins, so there is no need to have the ability for
locale-specific plugins to override common ones. They already override
those in $LIBDIR/searchplugins
- add debian/firefox-locale.preinst.in, which will end up in all
language packs to assist the symlink -> folder transition
- update debian/firefox.dirs.in
- update debian/firefox.install.in
- update debian/firefox.links.in
- update debian/firefox.preinst.in
- update debian/patches/distro-locale-searchplugins.patch
- update debian/rules
* Fix LP: #807733 - Firefox doesn't restart after upgrades where the version
changes. Don't include the version number in the install path, as Firefox
cannot re-exec itself. In doing this, we also move the distribution.ini
back in to our installation directory, as that never made sense in
/usr/lib/firefox-addons
- update debian/firefox-dev.install.in
- update debian/firefox-dev.links.in
- update debian/firefox-locale.preinst.in
- update debian/firefox.lintian-overrides.in
- update debian/firefox.preinst.in
- update debian/rules
* Expose distribution/extensions in /usr/lib/firefox-addons, to allow
administrators to add extensions that they want to add to default user
profiles, and that they want the addon manager to keep updated. We lost
this functionality when upgrading from Firefox 3.6, due to the loss of
/etc/firefox/profile
- update debian/firefox.dirs.in
- update debian/firefox.install.in
- update debian/firefox.links.in
- update debian/firefox.postinst.in
|
Chris Coulson |
11.0+build1-0ubuntu1 |
12 years ago
|
|
|
| 146
|
|
|
Chris Coulson |
11.0~b7+build1-0ubuntu1 |
12 years ago
|
|
|
| 145
|
|
|
Chris Coulson |
11.0~b6+build1-0ubuntu1 |
12 years ago
|
|
|
| 144
|
|
|
Chris Coulson |
11.0~b5+build1-0ubuntu1 |
12 years ago
|
|
|
| 143
|
|
|
Chris Coulson |
11.0~b4+build1-0ubuntu1 |
12 years ago
|
|
|
| 142
|
|
|
Chris Coulson |
11.0~b3+build2-0ubuntu1 |
12 years ago
|
|
|
| 141
|
|
|
Chris Coulson |
11.0~b2+build1-0ubuntu1 |
12 years ago
|
|
|
| 140
|
|
* New upstream release from the beta channel (FIREFOX_11_0b1_BUILD1)
- Fix LP: #875266 - Firefox ignores GNOME3 proxy settings
- Fix LP: #857153 - Needs to get accessibility settings from GSettings
* Update globalmenu-extension to 2.0.3
* Ensure that the crash reporter is disabled if rebuilt by Ubuntu
derivatives, as there will be no crash symbols for those
- update debian/rules
* Only add "Ubuntu" to the UA string when being built for Ubuntu
- update debian/rules
* Drop obsolete Debian menu file
- remove debian/firefox.menu.in
- don't create a 32x32 xpm icon in debian/rules
- drop the imagemagick build-depend in debian/control
* Temporarily disable ipdl tests due to build failures. These aren't
enabled upstream, anyway
- update debian/config/mozconfig.in
* Always set the update channel - not setting it at build-time on release
builds breaks the extensions.checkCompatibility pref. The only things
using it at runtime are nsBlocklistService, Test Pilot (beta + aurora)
and the about dialog (where the channel is hidden anyway)
- update debian/rules
- update debian/firefox.install.in
* Don't declare an extra DEB_ENABLE_THUMB2 variable, as it's only used
for the mozconfig. Just do the "if DEB_HOST_ARCH == armel" check
directly there instead
- update debian/rules
- update debian/config/mozconfig.in
* Fix LP: #898883 - IPC xpcshell tests hang the buildd's. Give all
xpcshell tests an X display, as plugin-container won't work without one
- update debian/build/testsuite.mk
* Turn on all IPC xpcshell tests again
- update debian/build/testsute.mk
* Drop the default-apps xml file from lucid and maverick - there is
already one provided by gnome-control-center, which means that ours
is only relevant for nightly builds. It's not worth the extra
complexity for this
- remove debian/firefox.xml.in
- update debian/firefox-gnome-support.install.in
- update debian/rules
* Ship Test Pilot as a distribution addon, like upstream. This means
that the addon manager can update it. It does also mean that it will
remain installed in users profiles if they try the beta or aurora
builds, but the Feedback button is disabled on release builds
- update debian/firefox.install.in
- fixes LP: #913357
* Drop patches fixed upstream
- remove debian/patches/fix-build-failure-without-yarr-jit.patch
- remove debian/patches/fix-cursor-handling.patch
- update debian/patches/series
* Keep the firefox-kde-support suggest on releases older than precise
for now
- update debian/rules
* Ensure that we suggest kmozillahelper on lucid
- update debian/rules
* Ensure that we replace kubuntu-firefox-installer on lucid
- update debian/rules
* Don't build with --disable-gconf on precise and newer. There won't be
a hard runtime requirement on this from Firefox 12 anyway, and this
keeps us closer to the upstream configuration
- update debian/config/mozconfig.in
- update debian/rules
* Call xvfb-run with "-a" in case there are other servers running on the
builder
- update debian/build/testsuite.mk
* Really fix LP: #898883 - IPC xpcshell tests hang the build. What was
actually happening is plugin-container would fail to start because all
available X connections had been used up by many instances of dbus-launch,
spawned each time an xpcshell tried to talk to the session bus. Because
we run all of the xpcshell tests with one Xvfb instance, the buses
accumulate until the available X connections all run out. To fix this, run
all tests requiring a display inside dbus-launch, so we create just a
single bus for all xpcshell tests
- update debian/build/testsuite.mk
- update debian/control{,.in}
* Add Ligurian to locale blacklist, as we don't support this in Ubuntu
- update debian/config/locales.blacklist
|
Chris Coulson |
11.0~b1+build1-0ubuntu1 |
12 years ago
|
|
|
| 139
|
|
|
Chris Coulson |
10.0+build1-0ubuntu1 |
12 years ago
|
|
|
| 138
|
|
|
Chris Coulson |
10.0~b6+build1-0ubuntu1 |
12 years ago
|
|
|
| 137
|
|
|
Chris Coulson |
10.0~b5+build1-0ubuntu1 |
12 years ago
|
|
|
| 136
|
|
|
Chris Coulson |
10.0~b4+build1-0ubuntu1 |
12 years ago
|
|
|
| 135
|
|
|
Chris Coulson |
10.0~b3+build2-0ubuntu1 |
12 years ago
|
|
|
collapse all