This bug was fixed in the package gtk+3.0 - 3.20.6-1ubuntu1
---------------
gtk+3.0 (3.20.6-1ubuntu1) yakkety; urgency=medium
* Merge with Debian (LP: #1576576). Remaining changes:
+ Install the settings.ini file to set our themes
+ Enable parallel builds
+ Ubuntu specific patches:
- 073_treeview_almost_fixed.patch
- 074_eventbox_scroll_mask.patch
- bzg_gtkcellrenderer_grabbing_modifier.patch
- ubuntu_gtk_custom_menu_items.patch
- print-dialog-show-options-of-remote-dnssd-printers.patch
- uimanager-guard-against-nested-node-updates.patch
- x-canonical-accel.patch
- message-dialog-restore-traditional-look-on-unity.patch
- 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
- restore_filechooser_typeaheadfind
- 0001-calendar-always-emit-day-selected-once.patch
- 0001-gtkwindow-set-transparent-background-color.patch
- ubuntu_fileselector_behaviour.patch
- unity-border-radius.patch
- unity-headerbar-maximized-mode.patch
+ Install a gsettings override to start filechoosers in the cwd
+ Enable Mir backend
gtk+3.0 (3.20.6-1) unstable; urgency=medium
* New upstream release.
* Drop revert-scrolledwindow-Remove-child-before-destroying.patch, merged
upstream.
* Re-enable test-suite.
gtk+3.0 (3.20.5-4) unstable; urgency=medium
* Work around a bug in cdbs which causes the package to FTBFS; see #825135
for further details.
gtk+3.0 (3.20.5-3) unstable; urgency=medium
* Make it simpler to bootstrap the package by marking the build dependencies
which are required to run the test-suite with <!nocheck>.
(Closes: #747392)
* Bump Build-Depends on debhelper to (>= 9.20141010) and dpkg-dev to
(>= 1.17.14) for build dependency restrictions support.
* Temporarily disable the test suite (and its build-dependencies) to allow
building the new gtk-update-icon-cache package. Our buildds don't support
build profiles yet, so we'll have to bootstrap manually for now.
gtk+3.0 (3.20.5-2) unstable; urgency=medium
* Split gtk-update-icon-cache utility out of libgtk-3-bin into a separate
package called gtk-update-icon-cache to break a dependency cycle with
adwaita-icon-theme when building the package. (Closes: #824999)
As the gtk-update-icon-cache binary doesn't actually have any libgtk-3-0
dependency, there is no longer a reason to ship a gtk2 and gtk3 variant.
So from now on we will only ship one implementation built from src:gtk+3.0
and drop the Debian specific -3.0 suffix. To simplify the transition make
libgtk-3-bin depend on gtk-update-icon-cache. Once all theme packages have
been updated, this dependency can be dropped.
* Cherry-pick patch from upstream Git which reverts a commit that was
causing crashes in the filechooser in some applications.
gtk+3.0 (3.20.5-1) unstable; urgency=medium
* New upstream release.
* Refresh patches.
* Bump Standards-Version to 3.9.8.
gtk+3.0 (3.20.4-1) unstable; urgency=medium
* New upstream release.
gtk+3.0 (3.20.3-2) unstable; urgency=medium
* Restore debian/patches/reftest-known-fail.patch so we can mark known
failing tests as non-fatal.
* Drop debian/patches/disable-flaky-textview-margins-reftest.patch and tag
textview-margins.ui as known-fail.
* Mark button-wrapping.ui reftest as known-fail, it currently fails on
mips(64)el and prevents testing migration and important fixes in other
packages reaching testing.
gtk+3.0 (3.20.3-1) unstable; urgency=medium
* New upstream release.
* Drop debian/patches/git_window-Remove-suspicious-branch.patch, merged
upstream and refresh the remaining patches.
* Upload to unstable.
gtk+3.0 (3.20.2-1) experimental; urgency=medium
* New upstream release.
* Drop debian/patches/git_fix_emacs.patch, included in release.
* Add debian/patches/git_window-Remove-suspicious-branch.patch
- from upstream git, reverts a revert in 3.20.2 that causes the
testsuite to fail. Emacs users watch out!
gtk+3.0 (3.20.1-2) experimental; urgency=medium
* Add debian/patches/disable-flaky-textview-margins-reftest.patch
gtk+3.0 (3.20.1-1) experimental; urgency=medium
* New upstream release.
* Drop debian/patches/git_a11y_GTK_CSD_distcheck.patch, included in release.
* Add debian/patches/git_fix_emacs.patch, cherry-picked from upstream git.
Thanks to Matteo F. Vescovi for verifying the commit fixed the emacs
problem.
gtk+3.0 (3.20.0-1) experimental; urgency=medium
* New upstream release.
* Make testsuite fatal again.
* Add debian/patches/git_a11y_GTK_CSD_distcheck.patch
- cherry-pick commit from upstream to use client-side decorations
for a11y tests when running under distcheck.
* Drop debian/patches/reftest-known-fail.patch
* Stop tagging reftests as known fail since they should be fixed now:
- style-properties-nth-child.ui
- label-text-shadow-changes-modify-clip.ui
* Add debian/patches/no-accessibility-dump.patch
- skip this test until someone figures out how to reliably run it
always with CSD enabled, to match testsuite expected data.
gtk+3.0 (3.19.12-1) experimental; urgency=medium
* New upstream development release+snapshot.
* Update (build-)dependencies according to configure.ac changes:
- add wayland-protocols (>= 1.1)
- bump libwayland-dev to 1.9.91
- add libharfbuzz-dev (>= 0.9), libpango1.0-dev
* Temporarily make testsuite non-fatal while investigating.
* libgtk-3-bin.install:
- ship new gtk-query-settings tool.
- ship gtk-builder gettext (its) files.
- run wrap-and-sort on this file while at it.
* Update debian/libgtk-3-0.symbols with new additions.
- also drops an internal unused wayland-related drag and drop symbol.
-- Iain Lane <[email protected]> Fri, 29 Jul 2016 13:48:43 +0100
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1576576
Title:
[needs-packaging] Update to 3.20 needs work and coordination
Status in Mozilla Firefox:
Fix Released
Status in Ubuntu GNOME:
Confirmed
Status in adwaita-icon-theme package in Ubuntu:
Fix Released
Status in gtk+2.0 package in Ubuntu:
Confirmed
Status in gtk+3.0 package in Ubuntu:
Fix Released
Status in ubuntu-settings package in Ubuntu:
Fix Released
Bug description:
The current upstream stable/Debian version is 3.20 but that includes quite
some changes in the css handling which means we are going to need to update/fix
the unity themes and make sure you main application look fine before landing.
The transition needs to be prepared in a staging ppa before being considered,
help is welcome since it's likely the desktop team is not going to have lot of
cycles to work on that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1576576/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
